On Wed, May 10, 2023 at 05:10:10PM -0300, Elder Costa wrote:
> Yes, I did read it. Several times. Unfortunately it is still not clear
> what it really means. That line was exactly the reason why I thought
> there would be some sort of clock resynchronization if there were a
> bigger than threshold difference between the local and the master's
> clock, in the first place. So, could you elaborate a little for mine
> and maybe other novice users? Or point to a more detailed reference?
step_threshold
The maximum offset the servo will correct by changing the clock
frequency (phase when using nullf servo) instead of stepping the
clock. When set to 0.0, the servo will never step the clock ex‐
cept on start. It's specified in seconds. The default is 0.0.
The ptp4l program estimates the client/server time offset by using the
PTP. Once the offset estimate is obtained, an action is taken to
correct the client's clock. There are two possible corrective
actions:
1. Set (aka step aka jump) the client clock to match the server's clock.
2. Slew the client clock (by changing the frequency to make it run
faster or slower) until it matches the server's clock.
By default, the ptp4l program uses method #2.
But if you set --step_threshold=X, the program will use method #1
whenever the estimated offset exceeds X.
HTH,
Richard
_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users
