| PM | Quote | Reply | Full Topic |
| Joined: | Wednesday Jun 6th, 2018 |
| Location: | Rijeka, Croatia |
| Posts: | 19 |
| Status: |
Offline
|
I did the firmware update. For a couple of days it seemed OK, but now it's the same as before.
Any other ideas? 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? Or something...?
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? 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?
I'm just throwing ideas at you, because this behaviour looks like that.
| Close Window |