I am experiencing weird clock drift and cannot tell if it is my server causing this issue. My expectation is ignition gets its clock from server/pc where it is running.
The problem is, we haven't event get to 19Apr2025 yet, and now I get that events and I am trying to find a way to detect if my server/pc change system time randomly.
This is currently creating problematic events where my historian starts to log that future time into my database so is there a way to resolve this clock drift events?
If you're working on a system that can't be connected to a normal time server you can buy an atomic clock and synch with that. We had to do that for a prison job once.
Does that mean when ignition gets wrong time, everything is messed up? Is there any fault tolerant settings that can be setup to handle clock drift that much?
We had the same thing happen to one of our development servers. Ignition version 8.1.44, virtual environment, server is getting it's time signal from the same domain controller that the rest of the network uses. From these entries you can see that it jumped 2 days forward, then another 5 days forward.
You can treat these as informational if they are not causing you any issues.
Otherwise you have to deal with this somehow. Perhaps a more reliable NTP source than whatever Windows has built in, which happily "warps" backwards and forwards through time instead of using a slow skew for corrections.
Not sure what type of hardware you're using, but we've had issues with Windows' built in NTP client on certain types of hardware such as the SEL-3355 computer.
A great workaround is to use a third party NTP client such as this free Meinberg one: Meinberg NTP Software Downloads
It also gives you much more flexibility for multiple NTP sources, failover, etc.
