| ECS Home Automation and Security Archives |
| Subject: From: Date: | Need suggestions for the DST logic changes David Mccoll Sat, 03 Mar 2007 18:10:22 -0800 |
ECS Legacy / DOS DST logic change. A closer look at both events show the state of the "DST In Effect" item can not be 100%known until one of the dates passes. This doesn't work unless the machine is on 24/7/365. My original DST Logic | | If Month Is April | And Day Is Sunday | And Date Is LE 7 | And Hour Is Now 2AM | Then Hour Add 1 | Then D.S.T. In Effect Set True | Else If D.S.T. In Effect Is True | And Month Is October | And Day Is Sunday | And Date Is GE 25 | And Hour Is Now 2AM | Then Hour Subtract 1 | Then D.S.T. In Effect Set False | End I used this filter in the ECS startup event to help if the clock was upset. | If Month Is April | And Date Is GT 7 | Or Month Is GT April | And Month Is LT October | Or Month Is October | And Date Is LT 25 | Then D.S.T. In Effect Set True Proposed DST event for 2007 | | If Month Is March | And Day Is Sunday | And Date Is GE 8 | And Date Is LE 14 | And Hour Is Now 2AM | Then Hour Add 1 | Then D.S.T. In Effect Set True | | Else If D.S.T. In Effect Is True | And Month Is November | And Day Is Sunday | And Date Is LE 7 | And Hour Is Now 2AM | Then Hour Subtract 1 | Then D.S.T. In Effect Set False | End Adding this filter to the "ECS Startup" event helps, but it misses a few days. | If Month / Date Is GE 3/15 | And Month / Date Is LE 11/1 | Then D.S.T. In Effect Set True | If Month / Date Is GE 11/7 | And Month / Date Is LE 3/7 | Then D.S.T. In Effect Set False Your feedback appreciated.