Dear Richard,

I hope this email finds you well.

I have been encountering this problem when trying to connect multiple PTP 
clients to a PTP grandmaster via a switch. When there is only one client on the 
network, the master_offset converges and the machine is kept nicely in sync. 
However, when I connect a second client, the following errors flood the stdout 
and the machine loses synchronisation (by which I mean it still stays in s2, 
but offset diverges and is wildly unstable)

I understand from previous mailing list replies that this could be caused by 
the hardware not being able to process the delay requests quickly enough, but 
even after setting the grandmaster sync to 1Hz, I still have these messages 
flooding my screen, at a much higher rate.

So far, I have tried setting logMinDelayReqInterval -1
And assume_two_step 1

To try and fix this issue, but to no avail.

Would really appreciate any help.

Best Regards,
Lyndon

Appendix: Error Messages
ptp4l[72426.115]: port 1: received DELAY_REQ without timestamp
ptp4l[72426.121]: port 1: received DELAY_REQ without timestamp
ptp4l[72426.122]: port 1: received DELAY_REQ without timestamp
ptp4l[72426.123]: port 1: received SYNC without timestamp
ptp4l[72426.130]: port 1: received SYNC without timestamp
ptp4l[72426.134]: port 1: received DELAY_REQ without timestamp
ptp4l[72426.138]: port 1: received SYNC without timestamp
...
_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users

Reply via email to