Hi Richard, Hi All, sorry if I'm returning on this topic.
The Annex A (serial interface) handles the following messages: - Time Event Message (TEM) that contains: the timestamp (48bit integer), flags (leap61m leap59, ...), and the currentUTCOffset - Time Announce message (TAM) that is very similar the PTP announce message - GNSS Status message, with information laike type of time source, status, alarms (I don't know if we really need this) Reading the standard I understood that interfaces cannot be source or sink at the same time (siee Table A.1). For this reason, the port can be configured to be just a sink or a source of signals (slave only or master only). Time Event Message is triggered on 1PPS rising edge. The message must be sent after 1ms after rising edge and be finished within 500ms. It's very similar to sync message and measuring the timestamp at 1PPS edge (T_1PPS) and the timestamp contained into the event time message (T_TEM), we can easily calculate the time offset (T_1PPS - T_TEM). The announce message should br managed by protocol as a normal PTP Announce message to handle the BMC and select the grandmaster (I suppose). >From my protocol picture I think that ts2phc is not the best solution because: - this cover only sink scenario (slave). What about source scenario (master) - TAM cannot be handled in this way - We cannot select automatically the best source between the serial and the other eth interface Do you have any suggestions in order to handle the message (announcement in primis). An idea that I have is to have a sort of "RAW_SERIAL" transport that translate the TEM messages into SYNC and TAM to PTP Announce. But I am not sure to invest this way. Again, your suggestions regarding the software design are really appreciated. Thanks a lot in advance, luigi Il giorno mer 28 ott 2020 alle ore 18:55 Richard Cochran < richardcoch...@gmail.com> ha scritto: > On Wed, Oct 28, 2020 at 06:47:29PM +0100, Luigi 'Comio' Mantellini wrote: > > > The idea under the Annex A is to propagate some information from the > serial > > link to master port. > > What "information" are we talking about? > > For setting GM attributes in ptp4l, you should use the management > interface. > > > Should be an async thread into linuxPTP that gathers these information > and > > updates the ptp messages accordingly. > > I don't think this is needed. > > > Your code save my job every day, thanks for this. > > Glad to hear that feedback! > > Thanks, > Richard > -- *Luigi 'Comio' Mantellini* My Professional Profile <http://www.linkedin.com/in/comio> *"UNIX is very simple, it just needs a genius to understand its simplicity." [cit.]*
_______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
