NetBurner Community Forum

Thankyou for your extremely prompt response. I apologise for the lack of clarity. I don't believe that the PK70 is not working correctly. I am trying to understand the problem with this specific network implementation utilising the PK70 in conjunction with the standard windows client. Where is this ...

When left to log for an extended period the sync between the PCs drifts out to around 50 ms before correcting by a shift of around 50 ms. I assume that this is at the point where the offset triggers the immediate clock reset due to the check: PhaseCorrection ≤ SystemClockRate ÷ 2 becoming false This...

w32tm stripchart output for Netburner NTP server
delay is reliable
offset is drifting
18:16:15 d +00.0014044s o +00.1200124s
18:16:17 d +00.0014202s o +00.1196326s
18:16:19 d +00.0005767s o +00.1199734s
18:16:21 d +00.0013790s o +00.1195790s
18:16:23 d +00.0009545s o +00.1198901s

w32tm stripchart output for time.windows.com delay is inconsistent and often > 0.1s offset is drifting 17:58:12 d +00.0329220s o +00.1005369s 17:58:14 d +00.0445815s o +00.1041230s 17:58:17 d +00.0315021s o +00.1026311s 17:58:19 d +00.0380554s o +00.1041515s 17:58:21 d +00.0298747s o +00.0989348s

Here are some example w32tm stripchart logs taken from the PC that the PK70 NTP server is attached to

I am using a PK70 NTP server as a stratum 1 NTP server time source for a Windows system running on a LAN. The system requires all PCs on the LAN to be consistently and robustly synced to within 5 milliseconds during system operation. An accuracy of < 1ms offset across all machines is preferable. The...