calendar objects 1 hour late: Daylight saving / Summer time
DeltaXRay
Posts: 8
I have some complex Calendar objects triggering a range of Parameter Presets in a BLU-100, and have them all working exactly as I want, BUT, everything happens one hour after the times in the calendars.
A first thought was to check that daylight saving is set correctly in the file and the PCs. It is.
Then I realised that we're in summer now, so if an event is specified to occur at 12:00hrs in summer, and a winter clock was being used, then the event would happen an hour earlier; not an hour later. Perhaps the BLU always presumes standard/winter time and it's adding an hour for summer?
This behaviour applies in the BLU units and in London Architect when off-line. Why would all events happen exactly one hour late?
Thanks
A first thought was to check that daylight saving is set correctly in the file and the PCs. It is.
Then I realised that we're in summer now, so if an event is specified to occur at 12:00hrs in summer, and a winter clock was being used, then the event would happen an hour earlier; not an hour later. Perhaps the BLU always presumes standard/winter time and it's adding an hour for summer?
This behaviour applies in the BLU units and in London Architect when off-line. Why would all events happen exactly one hour late?
Thanks
0
Comments
However, I had already set the Time Zone in File Preferences to 'GMT' and had the Daylight Saving set to 'Standard' with the correct dates for the UK.
I re-set them again just to be sure, but the logic outputs from the calendar objects are still active exactly one hour after the time on the local machines. (I needn't have mentioned the Parameter Presets in my opening post, because the output state of the calendar objects is visible in LA and also on an LED wired to a logic output on the BLU device).
To illustrate purely from London Architect running offline:
When GMT is 12 noon, BST will be 13:00. The local machines correctly show the time as 13:00. When a calendar event in LA is set to trigger a high output at 12:00, the output goes high at 13:00.
I'm puzzled.