
svshow (Customer) asked a question.
Before the NETTIME instruction appeared I used 6 variables (year,month,...) and once a day set the time remotely thru Modbus. I did not care about $SummerTime flag.
Now NETTIME updates UTC time in PLC and it just applies $TimeZone and $SummerTime to local time calculation. TimeZone I can setup 1 time and forget about it. But $Summertime flag I have to adjust twice a year in this case.
The idea is to have automatically updated flag ST768 ($SummerTime).
I hope someone already thought about it. I created some tests to this logic and seems like only 1 of 4 will work right.
For example:
// DST starts 2nd Sunday of March; 2am
// DST ends 1st Sunday of November; 2am
Done.
Long story short - I have some ideas for DoMore developers regarding SummerTime register.
Developers from Cisco systems made it possible manually set up summertime in their configuration like this:
clock summer-time name recurring 2 Sun Mar 02:00 1 Sun Nov 02:00 60
Where "2 Sun Mar 02:00" means "Second Sunday in March in 2AM"
Where "1 Sun Nov 02:00" means 1st November Sunday in 2am
60 means amount of minutes to play with
For DoMore (for now) idea is simple:
Rise $Summertime On second Sunday of March at 2am and reset it on first Sunday in November at 2am.
Now logic:
If anyone have time to test this and let me know about the results - that will be helpful for all.