Edit: some partial conclusions:
While beeing unable to measure some uA situations, I can infer from the figures below that:
a- the "normal" power consumption when no code is beeing executed and display is ON is rather like 300 - 350 uA.
b- switching off the display does save around 70 uA or 20 % from normal power consumption,
c- going to deep sleep saves may be 130 - 140 uA or 40 % from normal power consumption,
d- the Idd from the 32L476DISCOVERY is totally unappropriated to measure varying uAs as it switches from on range to another and interrupts power supply precisely at the amperages in normal power consumption mode with LCD OFF.
So my measures are as follow:
Display BLE uart Measure Comment
===== ======= ======= ========
ON connected 570 uA figures are fluctuating ??? BLE UART influence ?
OFF connected 500 uA figures are fluctuating ??? BLE UART influence ?
deep sleep connected 430 uA figures are fluctuating ??? BLE UART influence ? Lower than OFF
back ON connected 570 uA same as ON connected
ON not connected 220 uA jumping between 200 and 590 possibly advertising effects, peaks at 890 uA
OFF not connected 39 uA But reboots with no obvious reason!!! Self ranging ampmeter not switching correctly ????????
deep sleep not connected 37 uA But reboots with no obvious reason!!! Self ranging ampmeter not switching correctly ????????
back ON not connected ? uA Never clear display
Interestingly, reconnecting the ble uart (web ide) OR booting from an usb power bank, does stop all reboots and gives back the same behaviour and figures... So it really seems that the multi meter approach of the 32L476DISCOVERY is in default with those power variations. Unfortunately, the code of this part of the board is not open source: you can not know how measures are by the integrated coprocessor.
© Espruino, powered by microcosm.
Report a problem