Hi,
I'm using ptp4l 2.0. On the slave I'm monitoring the lock status ("s2",
"s1", "s0") to detect when the synchroniziation fails, and I configured the
following parameter to be sure the syncronization is always under 10 ms:
step_threshold 0.01
Unfortunately, rarely a spike in the master offset occurs, and the status
goes immediately to "s0". Here is an extract of the journald log, when
there was a single spike of 16 ms:
ptp4l[27813]: [1142331.506] master offset -13771 s2 freq -1359 path
delay 44137
ptp4l[27813]: [1142332.506] master offset 18635 s2 freq +1900 path
delay 41916
ptp4l[27813]: [1142333.506] master offset 13618 s2 freq +1412 path
delay 44137
ptp4l[27813]: [1142334.506] master offset 8180 s2 freq +876 path
delay 44137
ptp4l[27813]: [1142335.506] master offset 5693 s2 freq +633 path
delay 44772
ptp4l[27813]: [1142336.506] master offset 10602 s2 freq +1135 path
delay 45190
ptp4l[27813]: [1142337.506] master offset -8105 s2 freq -744 path
delay 45509
ptp4l[27813]: [1142338.506] master offset -11133 s2 freq -1058 path
delay 45509
ptp4l[27813]: [1142339.506] master offset -18764 s2 freq -1840 path
delay 44772
ptp4l[27813]: [1142340.509] master offset 27093 s2 freq +2773 path
delay 44772
ptp4l[27813]: [1142341.507] master offset -18103 s2 freq -1765 path
delay 53882
ptp4l[27813]: [1142342.507] master offset 16015803 s0 freq -1765 path
delay 53882
ptp4l[27813]: [1142342.507] port 1: SLAVE to UNCALIBRATED on
SYNCHRONIZATION_FAULT
ptp4l[27813]: [1142343.507] master offset -41662 s0 freq -1765 path
delay 53882
ptp4l[27813]: [1142344.507] master offset -38444 s0 freq -1765 path
delay 53882
ptp4l[27813]: [1142345.507] master offset -7516 s0 freq -1765 path
delay 48319
ptp4l[27813]: [1142346.507] master offset -27152 s0 freq -1765 path
delay 48319
ptp4l[27813]: [1142347.507] master offset -9544 s0 freq -1765 path
delay 43823
ptp4l[27813]: [1142348.507] master offset -9858 s0 freq -1765 path
delay 43981
ptp4l[27813]: [1142349.507] master offset 1854 s0 freq -1765 path
delay 43981
ptp4l[27813]: [1142350.507] master offset 4298 s0 freq -1765 path
delay 43981
ptp4l[27813]: [1142351.507] master offset -4977 s0 freq -1765 path
delay 43981
ptp4l[27813]: [1142352.507] master offset -7245 s0 freq -1765 path
delay 44254
ptp4l[27813]: [1142353.507] master offset -3080 s0 freq -1765 path
delay 44254
ptp4l[27813]: [1142354.508] master offset 1994 s0 freq -1765 path
delay 44183
ptp4l[27813]: [1142355.508] master offset -1392 s0 freq -1765 path
delay 44254
ptp4l[27813]: [1142356.508] master offset 1373 s0 freq -1765 path
delay 44254
ptp4l[27813]: [1142357.508] master offset 2262 s0 freq -1765 path
delay 44183
ptp4l[27813]: [1142358.508] master offset 3453 s0 freq -1765 path
delay 44183
ptp4l[27813]: [1142359.508] master offset 5975 s2 freq +3023 path
delay 43826
ptp4l[27813]: [1142359.508] port 1: UNCALIBRATED to SLAVE on
MASTER_CLOCK_SELECTED
ptp4l[27813]: [1142360.508] master offset 1124 s2 freq +3136 path
delay 44183
ptp4l[27813]: [1142361.509] master offset -6295 s2 freq +2388 path
delay 43826
ptp4l[27813]: [1142362.508] master offset -3711 s2 freq +2643 path
delay 43826
ptp4l[27813]: [1142363.508] master offset 4590 s2 freq +3477 path
delay 42508
ptp4l[27813]: [1142364.508] master offset -13466 s2 freq +1658 path
delay 42508
ptp4l[27813]: [1142365.508] master offset 8150 s2 freq +3828 path
delay 41961
ptp4l[27813]: [1142366.508] master offset -7971 s2 freq +2208 path
delay 41961
ptp4l[27813]: [1142367.509] master offset -16345 s2 freq +1354 path
delay 42844
ptp4l[27813]: [1142368.509] master offset -14362 s2 freq +1538 path
delay 42844
Is there any parameter to filter these spikes, in order to use the status
to detect synchronization failures and at the same time be sure that the
real offset is under 10 ms?
Thank you, regards,
Stefano
_______________________________________________
Linuxptp-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linuxptp-users
