Timeline for Time delay without using delay() and millis()
Current License: CC BY-SA 3.0
8 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Mar 21, 2017 at 3:07 | review | First posts | |||
Mar 21, 2017 at 7:40 | |||||
Mar 18, 2017 at 2:47 | comment | added | dandavis | i would "upgrade" to relays to latching, or at least driven by a 1-bit state machine, like an "SR Latch" that the MCU can read and write. That way, an MCU crash won't affect the relays at all. | |
Mar 17, 2017 at 22:59 | comment | added | SDsolar | I use double loops. The outer loop is your entire delay time, (say, 10 minutes = 10,000 ms divided by the duration of the inner loop delays) and the inner loop is how often you need to check for a condition that necessitates calling some function, (maybe every 1000 ms) - so your halt times are determined by the inner loop delay. And the outer loop can be used to update a display on a less-periodic basis. The 50 day thing is not relevant. | |
Mar 17, 2017 at 20:28 | comment | added | Edgar Bonet | See How can I handle the millis() rollover?. In short: the correct way to handle the rollover is to write rollover-safe code, like in the standard example Blink Without Delay. | |
Mar 17, 2017 at 11:27 | answer | added | Majenko | timeline score: 4 | |
Mar 17, 2017 at 11:07 | answer | added | dannyf | timeline score: 0 | |
Mar 17, 2017 at 6:54 | answer | added | SMFSW | timeline score: 2 | |
Mar 17, 2017 at 6:15 | history | asked | Vignesh | CC BY-SA 3.0 |