I think automotive profile is defined here: https://avnu.org/wp-content/uploads/2014/05/Auto-Ethernet-AVB-Func-Interop-Spec_v1.6.pdf . The document doesn't say anything about transport layer or delay mechanism. So I just took the existing automotive profile and switched it to E2E.

This has been practically verified to work on our mobile robots to sync time between several computers and sensors (one of which is considered time master). In mobile robotics, space and weight are limited, so the ability to use a TC-only switch is crucial. Otherwise, the mobile robot behaves very similar to a car in the way that the devices are known a-priori, and the whole system is mainly intended to run as an isolated time domain (i.e. time-consistency between robots is not as crucial as time-consistency inside one robot).

Martin

Dne 07. 03. 22 v 14:27 Richard Cochran napsal(a):

On Mon, Mar 07, 2022 at 01:39:31PM +0100, Martin Pecka wrote:
This allows running an automotive-like network without a time-aware bridge. All 
clients will sync directly with the master e.g. via a simple switch with 
Transparent Clock.
I didn't know about this profile... can you share a link?

Thanks,
Richard


Attachment: smime.p7s
Description: Elektronicky podpis S/MIME

_______________________________________________
Linuxptp-devel mailing list
Linuxptp-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-devel

Reply via email to