PLC time set to 1.1.2000 by NTP server

Ask Questions
1

The customer replaced the PC and did not set it up as an NTP server. After alerting him to this fact, he still has not started the server, there are some complications within Windows.

My PLCs:
PLC1 X20CP1586 = NTP client (server 1 = PC), also set as NTP server #2
PLC2 X20CP1685 = NTP client (server 1 = PC, server 2 = PLC1)
PLC3 … PLCn same configuration as PLC2.

If the NTP server is not functional on the PC for any reason, the time is set to 1.1.2000 in all PLCs.
Unfortunately, from AR x4.90 onward, the time in the PLC cannot be set either online or with a function from the program. In this situation it is a serious problem because the “time schedules” work with a nonsensical time.

Why does the PLC not detect if the NTP server is not configured at the given IP address?

Has anyone encountered this problem?

2

In the AsArCfg library some Ntp function blocks are available which can start/stop NTP server/client.

image
image878×166 34.6 KB

Perhaps you could stop the NTP services, which makes it possible to set the time/date again with other fubs.

1 Like
3

By applying these functions I could actually at least set the times in the PLC.
Many thanks for your help :+1:

4

You could also use the IcmpPing function block from the AsIcmp library to detect if the NTP-server is reachable.

https://help.br-automation.com/#/en/4/libraries/asicmp/fbks/icmpping.html

1 Like