On Mon, Nov 27, 2023 at 08:18:54AM +0000, Hopf, Daniel wrote:
> Thanks Richard,
>
> Then maybe I misunderstood the output of ptp4l.
> I am specifically confused about the lines indicating "master
> offset" (which in my log started popping up after ~80 seconds, but
> sometimes don't show up even after 15 minutes) - what changed in the
> state of the synchronization that the logs suddenly changed from
> reporting "rms ... max ... freq ..." lines to reporting "master
> offset"?
That is only the reporting of the offset.
The offset reporting is rate limited by:
summary_interval
The time interval in which are printed summary statistics of the
clock. It is specified as a power of two in seconds. The statis‐
tics include offset root mean square (RMS), maximum absolute
offset, frequency offset mean and standard deviation, and path
delay mean and standard deviation. The units are nanoseconds and
parts per billion (ppb). If there is only one clock update in
the interval, the sample will be printed instead of the statis‐
tics. The messages are printed at the LOG_INFO level. The de‐
fault is 0 (1 second).
So when the Sync message period changes, the reporting format also changes.
HTH,
Richard
_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users
