| PM | Quote | Reply | Full Topic |
| Joined: | Saturday Apr 29th, 2006 |
| Location: | Singapore |
| Posts: | 5500 |
| Status: |
Offline
|
What actually is supposed to happen when a running timer is stopped? I'm guessing, whatever was supposed to happen after it expires - isn't meant to happen at all? When a timer (after being stopped) gets reused again, does it count down from the newly given value or from the value it reached when it was last stopped?
Corect. When you stop a timer, the event does not get activatedWhen you start a timer it is always with a new value, there is no Restart timer action
Is it possible that all "wait for timer" actions are left waiting on some stack and then pop all up in a (random?) sequence after this timer finally expires?
No, each timer has its own track ie timer value and Response or next action
Is there a debugging tool I could use? Can Comfigurator, or some simple terminal emulator listen on some port and collect status and event information through several days?
There is a Bus Monitor under Tools that monitors the Bus messages. However Timers do not transmit on the Bus
You can see the status of Timers in the Timers page Press Show Status in Timer Status. This shows the remaining timer value when you press.
You say that it works OK for a few days, and then it does not. That seems to indicate that something external has changed?
What about wgeb you reset. Dioes it start to work?
| Close Window |