> The option works for me. @Miroslav Lichvar, Could you elaborate how you test this to confirm the behavior? I'll try the same too.
On Thu, 12 Jan 2023 at 17:38, Gururaj Badiger <gururaj.badi...@gmail.com> wrote: > That was a typo. I set it to 20 nanoseconds. > Monitor comparing the reference timing of Dev2 with Delay introduced > Timing of Dev1 (i.e., Dev1 has Delay Asymmetry set to 20ns). > . > > > On Thu, 12 Jan 2023 at 17:22, Miroslav Lichvar <mlich...@redhat.com> > wrote: > >> On Thu, Jan 12, 2023 at 04:21:11PM +0530, Gururaj Badiger wrote: >> > Waveform Monitor takes Black inputs generated by Dev1 and Dev2 devices. >> > >> > In this setup, Dev2 is locked to Dev1 PTP Leader. Now, when I change the >> > "delayAsymmetry '' value of Dev2, from 0 to 20us, we are expecting a >> timing >> > shift in Waveform Monitor. However, we dont see any change. >> > This seems to indicate the value set to parameter delayAsymmetry doesn't >> > have any effect. >> >> The option works for me. Did you set it to 20000 (nanoseconds)? >> What exactly is the monitor comparing, two PPS signals from PHC on the >> server and client? >> >> -- >> Miroslav Lichvar >> >>
_______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
