Codesys V3.5.19.7, Wago 750-8212 FW:04.04.03(26).
Changing clock in wbm updates dates of new alarms in Alarm Manager but time does not change. Any steps I am missing? Have this on multiple of the same CPU.
me too… frustrating. any fix?
I do not think the existing alarms will be re-time stamped. This is saved to a file, but new alarms should have the correct time. I recommend using NTP to keep the clock up to date.
@WagoKurt , after logging into various CPUs, I see they are all displaying the current time correctly now. Unsure if there is any sort of time sync delay between the runtime application and Wago CPU clock. The issues I was seeing were immediately after updating the clock, setting a test alarm and noticing the time was not updated while the date was. Existing entries didn’t change as expected.
Will monitor my steps a little closer the next time I commission a new one out of the box to see if I get the same results. Not really a big deal if there’s some sort of delay between changing the clock and the application updating. Can live with that.
All of these have NTP when possible.
1 Like