GPY deepsleep High current

[kjm]

@bouchard-claude My 40uA deepsleep is just the gpy, does not include any current drawn by an expansion board.

[bouchard.claude]

@kjm said in GPY deepsleep High current:

@bouchard-claude My 40uA deepsleep is just the gpy, does not include any current drawn by an expansion board.

Make sense. My 280 uA is measured without any expansion board either.

[Gijs]

@tuftec we are aware the command sqnsupgrade.info() gives the information you need, and then coredumps (this also happened in r2, and sometimes in r1, especially on pybytes versions, ). Its not really 'mission critical' (there are other ways to get the information that do not coredump), but we will look at solving it, Thanks!
Gijs

[bouchard.claude]

@Gijs Thanks for the info. I wont worry about this then. would you be able to help us figuring out what is the deepsleep current we should be getting while powered by VIN with nothing plugged in? I'm not sure if I should contact pycom by email for this king of info?

thanks

[Gijs]

That is definitely something I want to work on bringing together! A table of some sort with current specifications of what to expect in certain scenarios. For now, it can wildly vary with firmware versions (and LTE modem firmwares) as you probably followed above and in other threads as well. I cannot tell you when it will be finished, but when its done, it will be on the documentation!

[bouchard.claude]

Hi @Gijs , did you had time to work on this in the past weeks? This issue is preventing us from moving to preprod as we are draining the battery way too fast for the application. and it will be important for me to understand what to expect of the pycom platform.

Thanks!

[Gijs]

I did not get started on this (Im only on parttime and there's lots of 'higher priority' issues to solve first, its still on my list though!). What I can tell you, is that ~220uA for deepsleep is is quite high, we're expecting around ~40uA (my colleague @peterp did some work on the pysense / pytrack deepsleeping as well, to bring the current draw even further down, theres some additional info on that here: https://github.com/pycom/pycom-libraries/issues/132). It could potentially be related to the modem firmware and my colleague attached the beta firmware here for NB-IoT, or email me at support@pycom.io for the Cat-M1 firmware (it requires some additional updating instructions)

On the Pysense / Pytrack there is an option to cut the power to the module, bringing the deepsleep current closer to 0 (we use a PIC on the pysense / pytrack that keeps track of the wakeup time and turns the power back on)

[peterp]

Allow me to add some more comments. 220uA in deepsleep is too much, this is not expected. Outside of an Expansion board, just supplying vin and gnd, it should be 20-21 uA in deepsleep (with 3.75V supply). In an Expansion board 3.1 I see it as low as 57uA.

Do you have jumpers (which) and/or SD card inserted? 57uA is without any.