Thanks Richard,
Then maybe I misunderstood the output of ptp4l.
I am specifically confused about the lines indicating "master offset" (which in
my log started popping up after ~80 seconds, but sometimes don't show up even
after 15 minutes) - what changed in the state of the synchronization that the
logs suddenly changed from reporting "rms ... max ... freq ..." lines to
reporting "master offset"?
Also, as soon as the slave starts showing "master offset" lines, the master
sends its SYNC messages not every 125 ms anymore, but rather only once per
second.
I think this is due to the "automotive-master.cfg" having a "logSyncInterval"
of -3 (= every 125 ms), and the "default.cfg" having a "operLogSyncInterval" of
0 (= every second)? So I assume that the Master first uses "logSyncInterval"
and with the switch to reporting "master offset" lines, it somehow switches to
"operLogSyncInterval" for it's Sync send timeouts?
See this snippet here:
ptp4l[26331.354]: port 1 (eth0): delay timeout
ptp4l[26331.355]: delay filtered 8906 raw 8875
ptp4l[26331.532]: rms 31 max 56 freq +5554 +/- 42 delay 8906 +/- 0
ptp4l[26332.354]: port 1 (eth0): delay timeout
ptp4l[26332.360]: delay filtered 8906 raw 8871
ptp4l[26332.535]: rms 47 max 71 freq +5586 +/- 60 delay 8906 +/- 0
ptp4l[26333.355]: port 1 (eth0): delay timeout
ptp4l[26333.364]: delay filtered 8899 raw 8894
ptp4l[26333.540]: rms 24 max 60 freq +5559 +/- 33 delay 8899 +/- 0
ptp4l[26334.041]: PI servo: sync interval 1.000 kp 0.700 ki 0.300000
ptp4l[26334.041]: master offset -53 s2 freq +5515 path delay 8899
(<---- what triggers this now being shown instead of rms / max / freq?)
ptp4l[26334.356]: port 1 (eth0): delay timeout
ptp4l[26334.364]: delay filtered 8899 raw 8952
ptp4l[26335.042]: master offset 49 s2 freq +5602 path delay 8899
ptp4l[26336.042]: master offset -28 s2 freq +5539 path delay 8899
ptp4l[26337.042]: master offset 12 s2 freq +5571 path delay 8899
ptp4l[26338.043]: master offset -5 s2 freq +5557 path delay 8899
ptp4l[26338.356]: port 1 (eth0): delay timeout
ptp4l[26338.364]: delay filtered 8899 raw 8949
ptp4l[26339.043]: master offset -13 s2 freq +5548 path delay 8899
ptp4l[26340.044]: master offset -118 s2 freq +5439 path delay 8899
ptp4l[26341.044]: master offset -10 s2 freq +5512 path delay 8899
ptp4l[26342.045]: master offset 40 s2 freq +5559 path delay 8899
Thanks,
Daniel
Internal
-----Ursprüngliche Nachricht-----
Von: Richard Cochran <richardcoch...@gmail.com>
Gesendet: Samstag, 25. November 2023 20:32
An: Hopf, Daniel <daniel.h...@continental-corporation.com>
Cc: linuxptp-users@lists.sourceforge.net
Betreff: Re: [Linuxptp-users] Slave takes VERY long to sync to Master using
Automotive profile
CAUTION: This is an external email. Do not click or open any attachments unless
you recognize the sender and know that the content is safe.
(http://links.conti.de/mailcheck)
On Fri, Nov 24, 2023 at 02:59:25PM +0000, Hopf, Daniel wrote:
> Following are the logs of a try where they synced up after ~80 seconds.
> Here's the SLAVE log (I increased neighborPropDelayThresh from 800 to 8000
> and set tx_timestamp_timeout to 100 in my slave config file):
> -(~/linuxptp-latest:$)-> sudo ./ptp4l -f
> ./configs/automotive-slave-DH.cfg -i eth0 -m -l 7
> ptp4l[26253.262]: rms 25054 max 50349 <-- within 50 usec
> ptp4l[26254.264]: rms 2904 max 3109 3 usec
> ptp4l[26255.267]: rms 1722 max 2380 2 usec
> ptp4l[26256.271]: rms 521 max 931 under 1 usec
Why do you say it took 80 seconds? Log suggests client synchronized to within
50 microseconds after one second.
Thanks,
Richard
_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users
