Timeline for Using 555 as an external Watchdog
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 25, 2015 at 23:38 | answer | added | Stephan Noller | timeline score: 4 | |
| Jan 25, 2015 at 20:52 | comment | added | Stephan Noller | Will give it a try - but nevertheless - would feel saver with an external fallback, still. Any ideas on this? | |
| Jan 25, 2015 at 20:15 | comment | added | Gerben |
GSM communication shouldn't block the arduino code. You should at least be able to work around any blocking code that is in the library. Something like while(!Serial.available() && millis()-starttime<10000){wdt_reset()}.
|
|
| Jan 25, 2015 at 17:02 | comment | added | Stephan Noller | Because it is not reliable and way too fast. I am running on reduced clock speed which means maximum watchdog cycle would be 3-4seconds. GSM communication takes time... | |
| Jan 25, 2015 at 14:57 | comment | added | Ignacio Vazquez-Abrams | Why can't you use the internal watchdog for this? | |
| Jan 25, 2015 at 14:46 | history | asked | Stephan Noller | CC BY-SA 3.0 |