This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm that you accept these cookies being set.

How to automatically synchronize the time and date for several logic machines?
#21
Have you restarted the Windows time service after changing the parameter? From the log it looks like the time is still rejected. Sync frequency is not a fixed time, check this: https://notes.networklessons.com/ntp-poll-interval
Reply
#22
Dear Admin
Yes, I restarted the Windows for 2 times after changing the parameter.
Test run again today, still the same issue, No time adjustment happens automatically.
Thanks for your efforts.
Richard
Reply
#23
Changing LocalClockDispersion to 0 works for me.

Test script:
Code:
res = io.readproc('ntpd -ddd -nq -p 192.168.0.2 2>&1')
log(res)

Time is updated:
Code:
ntpd: sending query to 192.168.0.2
ntpd: reply from 192.168.0.2: offset:+106.316103 delay:0.000457 status:0x1c strat:1 refid:0x4c434f4c rootdelay:0.000000 reach:0x01
ntpd: no valid datapoints, no peer selected
ntpd: poll:1s sockets:0 interval:1s
ntpd: sending query to 192.168.0.2
ntpd: reply from 192.168.0.2: offset:+106.316103 delay:0.000573 status:0x1c strat:1 refid:0x4c434f4c rootdelay:0.000000 reach:0x03
ntpd: current time is 2023-06-26 13:08:02.956806
ntpd: setting time to 2023-06-26 13:09:49.272909 (offset +106.316103s)

Since this is clearly not an LM issue there's nothing else that we can help with.
Reply
#24
Dear admin,

Yes!!! You are right.
I replaced the old PC with SurfacePro, and set all parameters which mentioned above.
Now, LM5 can automatically synchronize the time with SurfacePro.
Excellent!
Thanks a lot!

Richard
Reply


Forum Jump: