Re: [Linuxptp-users] No Effect of setting DelayAssymetry value in config file

2023-01-12 Thread Gururaj Badiger
> 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 wrote: > That was a typo. I set it to 20 nanoseconds. > Monitor comparing the reference timing of Dev2 with Delay

Re: [Linuxptp-users] No Effect of setting DelayAssymetry value in config file

2023-01-12 Thread Gururaj Badiger
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 wrote: > On Thu, Jan 12, 2023 at 04:21:11PM +0530, Gururaj Badiger

Re: [Linuxptp-users] No Effect of setting DelayAssymetry value in config file

2023-01-12 Thread Miroslav Lichvar
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 >

[Linuxptp-users] No Effect of setting DelayAssymetry value in config file

2023-01-12 Thread Gururaj Badiger
Hello, I have been using ptp4l and my setup has 3 devices. 1. Dev1 running with ptp4l LEADER 2. Dev2 is running with ptp4l FOLLOWER. 3. Also a Waveform Monitor Waveform Monitor takes Black inputs generated by Dev1 and Dev2 devices. In this setup, Dev2 is locked to Dev1 PTP Leader. Now, when I