We are having issues with time jump.
Everytime we power cycle the Hypervisor or Windows 10 time on AR Embedded changes for two hours back.
If I warm restart only AR Embedded time is not changed.
When I Restart only Windows and AR Embedded is not restarted in this case then time on AR Embedded is shifted for two hours back. In the logger there are no entries about time jump or time change so this really makes no sense. Same happens when restart with restart button on APC3100.
Did you see below help for time syn. setting on Hypervisor?
FAQ/ “What should be considered when synchronizing the time between Automation Runtime and the GPOS?”
It will be helpful.
We also don’t want any time synchronization from NTP servers, we just want that AR Emb and Windows Hypervisor are not lossing time and are allways synchronized.
the following registry entry must be set to “1” for this: (DWORD (32-bit)): HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation\RealTimeIsUniversal
Have tried to recreate the problem but the time stays. Coulege has also reported that time had changed during production when no changes or restarts had been made.
But we will see if this still happens, when the registry entry is added.
We are now facing another issue while in production and no powerfails, no uploading of software, just out of plain sight.
It’s Warning - 30993 > Time jump - software time.
We don’t know why would this be happening, CPU is not overloaded.
We are not using NTP time synchronization.
Any suggestions what should we check?
Upgrade Runtime? Current version is H4.93 as in pictures above.
I can see that the time also was changed several times by online communication (warning 2075).
To understand better what’s happening, may I ask if you do this time setting manually by Automation Studio or some other tool that uses online communication with the PLC, or by the machine visualization?
If it’s a hypervisor system, NTP could be activated in the PLC and / or in the GPOS system (but it must not be activated in both systems!).
I’m sorry, but the only idea that I have right now is again double-checking if NTP isn’t active in Windows and isn’t active in the PLC also…
Maybe other Community users have more ideas?
We have unchecked this box now and will see if it will help in this situation.
But anyway we don’t have access to the internet in the network.
Also I didn’t mention before, we are using Hypervisor Windows and AR Embedded, the network is set up on ETH1 for AR Embedded and ETH2 for Windows to communicate with SCADA system, these two networks are connected together in one switch. Not sure if this has any influence on the time synchronization.
I don’t think that the switch / ethernet configuration does influence the time settings in the RTC.
Yes, this is the Windows setting I meant. I don’t know what happens in Windows when NTP is activated but the server cannot be reached, but deactivating it to test if the behavior changes is the right choice.
Please keep us informed if anything has changed after deactivating it, thanks.
We haven’t had any issues with time jump since we added the registry entry and disabled in the windows “Synchronize with an Internet time server”.
