Open Donis- opened 3 years ago
When using linuxptp as master the SYNC message originTimestamp is filled with 0 since the standard allows it. Windows PTP client tries to sync but ends up with a very inaccurate update:
153408 15:23:54.8987968s - PtpClient returned 1 samples. 153408 15:23:54.8988202s - Intersection successful with 0 dropped samples. 153408 15:23:54.8988420s - 0: Sample:0 SyncDist:4025083000741780 SelectDisp:0 153408 15:23:54.8988623s - Sample 0 chosen. Select Dispersion:00.0000000s SPHO:0 STC:272085 153408 15:23:54.8988881s - Sample 0 offset:-805016535.5779444s delay:+805016536.1483520s dispersion:00.0000020s
When using up ptpd as master the SYNC message originTimestamp is filled with approximate time and windows ptpclient succeeds.
In both cases it's a two step sync with a FOLLOW_UP message.
When using linuxptp as master the SYNC message originTimestamp is filled with 0 since the standard allows it. Windows PTP client tries to sync but ends up with a very inaccurate update:
153408 15:23:54.8987968s - PtpClient returned 1 samples. 153408 15:23:54.8988202s - Intersection successful with 0 dropped samples. 153408 15:23:54.8988420s - 0: Sample:0 SyncDist:4025083000741780 SelectDisp:0 153408 15:23:54.8988623s - Sample 0 chosen. Select Dispersion:00.0000000s SPHO:0 STC:272085 153408 15:23:54.8988881s - Sample 0 offset:-805016535.5779444s delay:+805016536.1483520s dispersion:00.0000020s
When using up ptpd as master the SYNC message originTimestamp is filled with approximate time and windows ptpclient succeeds.
In both cases it's a two step sync with a FOLLOW_UP message.