Hi Richard, I'm not sure that ts2phc solution fits well. The idea under the Annex A is to propagate some information from the serial link to master port. Should be an async thread into linuxPTP that gathers these information and updates the ptp messages accordingly.
Your code save my job every day, thanks for this. ciao luigi Il giorno mer 28 ott 2020 alle ore 18:31 Richard Cochran < richardcoch...@gmail.com> ha scritto: > On Wed, Oct 28, 2020 at 09:35:36AM +0100, Luigi 'Comio' Mantellini wrote: > > thanks for your reply. I'm referring to G.8271/Y.1366 document: > > https://www.itu.int/rec/T-REC-G.8271-202003-I/en > > The new standard added a protocol on top of TOD/1PPS link as defined in > the > > cited Annex A. > > Thanks for the link. Now I see. > > > > On Tue, Oct 27, 2020 at 08:03:34PM +0100, Luigi 'Comio' Mantellini > wrote: > > > > Dear All, > > > > > > > > I'm trying to understand if I can support the G.8271 Annex A.1.3 > directly > > > > via LinuxPTP. > > The Annex defines Yet Another Binary ToD message. > > I don't see ts2phc supporting dozens and dozens of different binary > ToD format. > > Instead, I would write a stand alone program that groks the Binary ToD > and serves standard NMEA RMC sentences on a local TCP port. > > Then configure ts2phc by setting > > ts2phc.nmea_remote_host > ts2phc.nmea_remote_port > > appropriately. > > (This is exactly the approach I am using to support some random GPS > device that doesn't produce usable RMC sentences.) > > 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
