Thread: [Linuxptp-users] ptp4l output messages/statistics
PTP IEEE 1588 stack for Linux
Brought to you by:
rcochran
From: Daniel Le <dan...@ex...> - 2014-08-11 22:29:11
|
Hi everyone, I use the command "ptp4l -m -q -i eth1 -s -S" to test my PTP device in slave mode and with software time stamping. It is connected back-to-back with a grandmaster clock. >From the ptp4l output, the last state change message "UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED" indicates successful synchronization with the PTP master clock and the statistics are printed out. However, I don't see the messages about the calculated offset from master, for example "ptp4l[1821225.525]: master offset 17756 s2 adj +1812 path delay 53581", do they only apply to hardware time stamping? If that is the case then which one of the shown statistics is equivalent to "master offset", otherwise what did I miss? / #ptp4l -m -q -i eth1 -s -S ptp4l[889716.134]: port 1: get_ts_info not supported ptp4l[889716.136]: port 1: INITIALIZING to LISTENING on INITIALIZE ptp4l[889716.136]: port 0: INITIALIZING to LISTENING on INITIALIZE ptp4l[889717.665]: port 1: new foreign master 00b0ae.fffe.02d103-1 ptp4l[889721.665]: selected best master clock 00b0ae.fffe.02d103 ptp4l[889721.665]: port 1: LISTENING to UNCALIBRATED on RS_SLAVE ptp4l[889722.412]: port 1: minimum delay request interval 2^-7 ptp4l[889723.071]: rms 5248496 max 5248784 freq +1000000000 +/- 0 delay -214 +/- 0 ptp4l[889724.071]: rms 5246874 max 5247280 freq +1000000000 +/- 0 delay -307 +/- 24 ptp4l[889725.071]: rms 5245931 max 5246144 freq +1000000000 +/- 0 delay -76 +/- 74 ptp4l[889726.071]: rms 5244709 max 5244730 freq +1000000000 +/- 0 delay -148 +/- 107 ptp4l[889727.071]: rms 5247721 max 5251322 freq +1000000000 +/- 0 delay 317 +/- 916 ptp4l[889728.071]: rms 5247639 max 5247912 freq +1000000000 +/- 0 delay -153 +/- 92 ptp4l[889729.071]: rms 5246445 max 5246760 freq +1000000000 +/- 0 delay -151 +/- 93 ptp4l[889730.071]: rms 5245002 max 5245186 freq +1000000000 +/- 0 delay -154 +/- 98 ptp4l[889731.071]: rms 5244443 max 5244774 freq +1000000000 +/- 0 delay -69 +/- 71 ptp4l[889732.071]: rms 5243877 max 5244106 freq +1000000000 +/- 0 delay -39 +/- 42 ptp4l[889733.071]: rms 5246876 max 5248038 freq +1000000000 +/- 0 delay 314 +/- 712 ptp4l[889734.071]: rms 5245014 max 5245174 freq +1000000000 +/- 0 delay -137 +/- 69 ptp4l[889735.071]: rms 5244071 max 5244604 freq +1000000000 +/- 0 delay -115 +/- 114 ptp4l[889736.071]: rms 5243134 max 5243420 freq +1000000000 +/- 0 delay -92 +/- 80 ptp4l[889737.071]: rms 5241706 max 5242180 freq +1000000000 +/- 0 delay -159 +/- 111 ptp4l[889738.071]: rms 5243572 max 5246424 freq +1000000000 +/- 0 delay 728 +/- 1022 ptp4l[889739.071]: rms 5243816 max 5244130 freq +1000000000 +/- 0 delay -80 +/- 72 ptp4l[889740.071]: rms 5242200 max 5242498 freq +1000000000 +/- 0 delay -158 +/- 116 ptp4l[889741.071]: rms 5240775 max 5241232 freq +1000000000 +/- 0 delay -151 +/- 118 ptp4l[889742.071]: rms 5239166 max 5239586 freq +1000000000 +/- 0 delay -198 +/- 113 ptp4l[889743.071]: rms 5240531 max 5242836 freq +1000000000 +/- 0 delay -107 +/- 247 ptp4l[889744.071]: rms 5242046 max 5242508 freq +550000000 +/- 450000000 delay -132 +/- 111 ptp4l[889744.571]: port 1: UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED ptp4l[889745.071]: rms 5240142 max 5240624 freq +99348906 +/- 1926 delay -199 +/- 147 ptp4l[889746.071]: rms 5238484 max 5238688 freq +99341169 +/- 1960 delay -193 +/- 121 ptp4l[889747.071]: rms 5237306 max 5237758 freq +99333375 +/- 1929 delay -136 +/- 102 Thanks! Daniel |
From: Miroslav L. <mli...@re...> - 2014-08-13 08:25:12
|
On Mon, Aug 11, 2014 at 10:29:01PM +0000, Daniel Le wrote: > Hi everyone, > > I use the command "ptp4l -m -q -i eth1 -s -S" to test my PTP device in slave mode and with software time stamping. It is connected back-to-back with a grandmaster clock. > > >From the ptp4l output, the last state change message "UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED" indicates successful synchronization with the PTP master clock and the statistics are printed out. However, I don't see the messages about the calculated offset from master, for example "ptp4l[1821225.525]: master offset 17756 s2 adj +1812 path delay 53581", do they only apply to hardware time stamping? If that is the case then which one of the shown statistics is equivalent to "master offset", otherwise what did I miss? The individual measurements are replaced in the log with the rms values when the sync interval is shorter than summary_interval (1 second by default). See the summary_interval description in the ptp4l man page. -- Miroslav Lichvar |
From: Daniel Le <dan...@ex...> - 2014-08-13 19:05:39
|
Thanks a lot. I change the master's sync interval to be 1 second or longer and see the master offsets are logged instead of rms values. Daniel -----Original Message----- From: Miroslav Lichvar [mailto:mli...@re...] Sent: Wednesday, August 13, 2014 4:25 AM To: Daniel Le Cc: lin...@li... Subject: Re: [Linuxptp-users] ptp4l output messages/statistics On Mon, Aug 11, 2014 at 10:29:01PM +0000, Daniel Le wrote: > Hi everyone, > > I use the command "ptp4l -m -q -i eth1 -s -S" to test my PTP device in slave mode and with software time stamping. It is connected back-to-back with a grandmaster clock. > > >From the ptp4l output, the last state change message "UNCALIBRATED to SLAVE on MASTER_CLOCK_SELECTED" indicates successful synchronization with the PTP master clock and the statistics are printed out. However, I don't see the messages about the calculated offset from master, for example "ptp4l[1821225.525]: master offset 17756 s2 adj +1812 path delay 53581", do they only apply to hardware time stamping? If that is the case then which one of the shown statistics is equivalent to "master offset", otherwise what did I miss? The individual measurements are replaced in the log with the rms values when the sync interval is shorter than summary_interval (1 second by default). See the summary_interval description in the ptp4l man page. -- Miroslav Lichvar |