Improving Electron Reliability - External Watchdog Timer

[thrmttnw]

@rickkas7

That will likely clear up any potential modem state issues. Just be careful to not get into a rolling cycle of doing that.

Thanks. It sounds like Cellular.off() done the right way is something that would mostly work. I am thinking that I am after something "certain" when all else fails.

So I looked at schematics for a modem reset pin and I found RESET_UC connected to pin PC4, and an example of how to pull it:

Electron Flashing Green - Will not connect until battery removed

We really need a way to double check that the modem is OFF or ON Until then, sparingly try to access the cellular hal directly which does offer a return value. #include "cellular_hal.h" cellular_result_t result = -1; result = cellular_off(NULL); if (result) Serial.println("ERROR!\r\nFailure powering off the modem!"); else Serial.println("OFF!"); result = cellular_on(NULL); if (result) Serial.println("ERROR!\r\nFailure powering on the modem!"); else Serial.println("ON!"); Also…

@rickkas7 In the case mentioned earlier with SEMI_AUTOMATIC mode, I would have to do a Cellular.on() before a Cellular.off() if i used that. So I am thinking that instead I might as well pull the RESET_UC pin right away, before moving on with normal business, whenever starting up and detecting a reset with:

System.resetReason() == RESET_REASON_PIN_RESET

@chipmc have you settled on a criteria for pulling the hard reset line in your applications?