Quote:
"The specification calls for something to happen at a specific time, not after a specific 7-day delay, and to me, that calls for a real-time clock, not a timer."
The specification calls for something to happen at a specific time ONLY AFTER a specific 7-day interval has elapsed. (See Post #1)
IMO this primarily is THE REQUIREMENT INTENDED TO BE SATISFIED WHEN ONE FIRST DESIGNED A TIMER.
Quote:
"The Day_Of_Week AOI does not reset a "day counter" - it returns the actual day of the week calculated from the date, so will always be correct if the date is set correctly."
Again, if we are researching the "scope" of this thread, we arrive at the conclusion that it is nothing more than : A WAY TO RESET A COUNTER AT 18:00 HOURS EVERY GIVEN SUNDAY.
The WallClockTime AND the DayOfTheWeek AOI implemented logic NEEDS TO RESET A COUNTER which's .acc value has to be recorded priorly to "zero-ing". It is the most elegant way to do it for most of the " helpers" within any automation forum.
However, when the request for help comes from someone not too familiar with the full capabilities of a system, I have always thought that a more basic alternative COULD BE considered and not completely (and rudely) dismissed.
Maybe the Midwest KISS engineering attitude is the culprit! Yep, the one that created Logix...