PyGate with LoPY4 - High Power Consumption on Deep Sleep
-
@robert-hh Thanks, it was a typo error.
-
Another option is to modify "robert-hh / ATTiny-Watchdog-for-MicroPython" repository to use the ATTiny (85, etc) to turn on/off PyGate with LoPY4 using a MOSFET.
ATTiny 85 power usage :
- active mode, approx. 0.7-3.6 mA @ 3.0V 1-8 MHz;
- in deepsleep mode : 0.1-0.2 uA @ 3.0V without interrupts, 5 uA with interrupts.
http://www.technoblogy.com/show?KX0
https://www.re-innovation.co.uk/docs/sleep-modes-on-attiny85/
https://arduino.stackexchange.com/questions/13983/attiny85-power-consumption-vs-clock-speed -
@rcolistete Thank you for elaborating on this! I had assumed that Pycom products don't need any kind of h/w modification in order to support low-power...The fact that I'm still to measuring 10-12mA in deep sleep mode (even trying the available methods, i.e. pybytes.deepsleep, machine.deepsleep) is really strange for a product series claiming to have been designed for low-power IoT applications.
-
It is really hard to find any low power LoRawan gateway, as gateways are designed to work 24/7.
-
Did you remove the jumper on the header on the PyEthernet module? You can find this next to the large magnetics IC. This jumper allows for a basic current draw for some PoE modules, or they will switch off completely. I believe the current is indeed close to 10mA, but Im not exactly sure. Removing the small jumper removes the default load from the circuit.
Best,
Gijs -
@Gijs Thank you for your recommendation. I don't use the PoE module, only Lopy4 connected to the PyGate. I use (and measure) the current of external power (i.e. Li battery) port of the PyGate.
-
Sorry, read too quickly.
For your solution, I believe the external watchdog timer would be preferable. We have no sort of deepsleep built into the Pygate, like the Pysense 2 and Pytrack 2 have, where the power to the development module is cut off, having only the USB controller pic running to keep track of time, as the general use-case of the Pygate is to be on all the time. You could still try to desolder the LEDs and cut some power there. Other than that, I dont think it is possible without hardware / firmware modifications.
-
@Gijs Thank you for saving me a lot of time! I think it would be a good idea to clarify that in the PyGate datasheet.
-
@rcolistete thank you for indicating this! I've just purchased 2 items of the Nano Power Timer.
I've followed all the instructions given here but it does not work. To be more specific:-
I have connected the power (5V) to the Vin pins and the Vout pins are powering the Extension Board v3.0 (with a LoPy4) via the USB connector of the Ext. Board.
-
Also, I connected the output pin P19 to the DONE pin of the Nano Power.
-
Delay via Dip Switch: 1 min
The issue: Once I plug-in the external input (5V) to the Nano Power, the Extension Board never turns on. If I put the push button of the Nano Power for 1 second then the Extension Board turns on for around 15 seconds and then turns off again.
Any ideas?
-
-
I've tested the SparkFun Nano Power Timer board some months ago, it was working ok, but it wasn't powering Expansion Board.
What about :
- using LiPo/LiIon battery to avoid any USB cable to power Expansion Board ?
- powering LoPy4 directly, from Vin (3.0-5.5V) ?
Why 15 s ? Is there any code in LoPy4 enabling the DONE pin of the Nano Power Timer ?
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login