HI Miroslav, So are you saying that each time I connect my Slave node, I have to make sure that my GM is running already and if I do so ptp4l should be able to make a step on the first update of the clock and reach synchronization much faster? Is my understanding correct?
On Tue, 6 Aug 2019 at 12:52, Miroslav Lichvar <mlich...@redhat.com> wrote: > On Tue, Aug 06, 2019 at 11:07:35AM +0530, Alexander Sylvester wrote: > > Hello Community, > > > > My master offset is sometimes very big: *ptp4l[741.578]: master offset > > 375396363 s2 freq +1000000 path delay -17200861* > > > > and the nodes take more time to come in the nanosecond range with respect > > to the master clock. Is it possible to increase the servo steering speed > by > > altering the configuration parameters so that the above number comes in > the > > range of +/-10 ns within few seconds. > > The maximum frequency offset is probably limited by the HW/driver. But > there should be no need for increasing that. ptp4l should be able to > make a step on the first update of the clock. Is the GM already > running when ptp4l is started? Maybe you just need to disable > synchronization between the slaves. Alternatively, you allow ptp4l to > make multiple steps. The options are documented in the man page. > > -- > Miroslav Lichvar >
_______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
