You are reading a single comment by @Gordon and its replies.
Click here to read the full conversation.
-
Thank you @Gordon for helping me out =)
When it disappears from the air, I cannot see it with anything. Plus it's not sending anything out.
Can you elaborate on the watchdog timer?
Power draw is not important as I am currently running it via mains power (over esp32 3.3v output)
May have to solder the wires for TTL output to use when goes off-line again
user130485
@Gordon
Thanks - looking at the code, you do stop it sending its name over Bluetooth. Usually that would be ok and you would just see the MAC address but in order to find it the IDE then uses scan response data, which can be a bit unreliable if there is a bunch of Bluetooth traffic. I guess that could be it? When you can't connect, can you still see it advertising with the NRF Connect app?
One way to debug is to add a USB-TTL adaptor so you can always communicate with it regardless of Bluetooth state. That really increases power draw though (1mA) so it's something you'd only do for debugging.
One other thing is you could add a watchdog timer. It's super unlikely that you would ever have a lockup, but at least if you do add the watchdog timer you could rule that out