I blew up my MDBT42s somehow. It still works, but days ago I overloaded one of the LED pins and was curious about the bad battery runtime and the high amps (> 40 mA) even with everything switched off.
Pulled everything apart to sort it out, put it back together (minus LED, don't need it) - yes D27 is gone.
So I replaced it with a spare device, unfortunately not with external antenna (just ordered replacements yesterday)
I run tests again and ran into issues again after ~30 minutes runtime and ~160 - 200 simulated laps with two Pucks:
the lap array is limited to 200 entries, so process.memory().free stays way above 400 mostly
at some point everything freezes. No display updates, no button reponses, amps at ~15 mA (also with Backlight on which is only a few mA) all the time, no BLE connection possible, no advertising either
doing it a second time I tried to stay connected via Web Console, after ~ 10 minutes I lost connection, reconnected and monitored memory a few times.
This is the final output before and after reconnect and before the freeze:
Espruino is a JavaScript interpreter for low-power Microcontrollers. This site is both a support community for Espruino and a place to share what you are working on.
OK - some updates:
I blew up my
MDBT42s
somehow. It still works, but days ago I overloaded one of the LED pins and was curious about the bad battery runtime and the high amps (> 40 mA) even with everything switched off.Pulled everything apart to sort it out, put it back together (minus LED, don't need it) - yes
D27
is gone.So I replaced it with a spare device, unfortunately not with external antenna (just ordered replacements yesterday)
I run tests again and ran into issues again after ~30 minutes runtime and ~160 - 200 simulated laps with two Pucks:
process.memory().free
stays way above 400 mostlydoing it a second time I tried to stay connected via Web Console, after ~ 10 minutes I lost connection, reconnected and monitored memory a few times.
This is the final output before and after reconnect and before the freeze:
The errors happened just when calling
process.memory()
Any ideas someone?
I'll remove the logging into RAM completely now and see if that helps.