leeb
I can't use the RTC (ML1025) as supplied.  I have to add 8 hours to get the correct time to show in ScadaBR and when daylight savings hits, I'll have to adjust that to 7, judging by the code.  Everything is running in the same TZ.

I'd like to propose replacing the existing RTC with a UTC clock instead.  This is better for remote systems logging data as there are no hour gaps or overlaps, no worries about timezone differences.

Alternatively a second clock variable, if the impact is deemed too high.

I'm happy to make the code changes, just want to make sure it's something that makes sense to other folk? 

My consideration is OpenPLC running in Germany, ScadBR running in Africa and the web browser in the USA.  The web client is the only consumer which should translate time for the human.
Quote 0 0
thiagoralves
That’s a good point. Just create another special location (I think ML1028 is available) and put UTC time in there. ML1025 should work well for local time zones (i.e. if you’re reading the time from the local system. It should make the appropriate conversions to have the correct time, including daylight saving time)
Quote 0 0
leeb
It turned out ScadaBR was doing a TZ conversion of it's own, so on top of the TZ adjustment in ML1025, that is why my time is so off.
When using a UTC value, ScadaBR displays the correct time for my TZ.

Pull request submitted -- I'm no expert with git, hope I got it right 🙂
Quote 0 0