Re: [Linuxptp-users] Get PTP but no Sync
On Wed, May 20, 2020 at 03:40:16PM +0200, Werner Macho wrote: > If the output of this: > > ># phc_ctl ens2f1 get cmp > phc_ctl[2350429.937]: clock time is 1589981848.451319038 or Wed May 20 > 15:37:28 2020 > phc_ctl[2350429.937]: offset from CLOCK_REALTIME is -37001639797ns > > now means that the NTP-synced clock of the PC where all this is running > (CLOCK_REALTIME) is -37001639797ns offset of the PHC on NIC ens2f1 > than this is exactly what I needed. Yes, the -37 seconds part reflects the UTC - TAI offset. > If someone could please confirm this one last question. I think you have what you need with phc_ctl. Thanks, Richard ___ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
Re: [Linuxptp-users] Accuracy in Software Timestamp Mode
On Thu, May 21, 2020 at 09:26:59AM -0400, cpham2...@comcast.net wrote: > My master clock and PTP clients on are a local network with no > PTP-support switches. There are 4 switches along the path between > the master clock and the clients. When I ran linuxptp in hardware > timestamp mode in the same network setting, I achieved great > results: 90% of master offsets is within 1 micro-sec. In software > timestamp mode the master offsets are higher than expected. Is > there anything I can do to improve the accuracy? I am afraid that your results are in fact typical. There is a long and non-deterministic path from the frames on the wire to the software time stamp somewhere in the networking stack. Sorry, Richard ___ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
