You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When hooking up the SHT21 directly to my node's power and ground, I measured the sleeping current to be around 5.7uA. Experimenting with the powerManager feature, I connected SHT21 to D5=GND, D6=VCC. The power consumption jumped to ~152uA while sleeping.
I then tried connecting SHT21 GND directly to Node GND and D6=VCC, still 152uA while sleeping.
I guess I could try different pins for GND, VCC, but I'm wondering if powering the pin down might leak a bit...
Hi, thanks for reporting it. Basically what you are saying is that even if you have the OFF before the sleep as I can see from the logs, still looks like there is current flowing through the pin. I'll try to reproduce it (the poweroff function just writes low to the vcc pin even if the debug output saying something about the ground pin which is wrong) and meanwhile marking it as a bug
Arduino IDE 1.8.6, MySensors 2.2, NodeManager 1.8, StampNode (Atmega328p), NRF24 SMD
When hooking up the SHT21 directly to my node's power and ground, I measured the sleeping current to be around 5.7uA. Experimenting with the powerManager feature, I connected SHT21 to D5=GND, D6=VCC. The power consumption jumped to ~152uA while sleeping.
I then tried connecting SHT21 GND directly to Node GND and D6=VCC, still 152uA while sleeping.
I guess I could try different pins for GND, VCC, but I'm wondering if powering the pin down might leak a bit...
NM:INIT:INO=SolarEnv v1.0
0 NM:INIT:LIB VER=2.2.0 CP=RNONA---
0 NM:INIT:RBT p=255
16 NM:BFR:INIT
12779 NM:PWR:ON p=6
12845 NM:STP:ID=21 M=0
12861 NM:PWR:OFF p=5
12976 NM:STP:HW V=3169 F=1 M=912
13025 NM:PWR:ON p=6
13680 NM:LOOP:BATTERY(201):SET t=38 v=3.16
14876 NM:LOOP:SHT21(1):SET t=0 v=75.04
15056 NM:LOOP:SHT21(2):SET t=1 v=40.21
16121 NM:PWR:OFF p=5
16138 NM:SLP:SLEEP s=1200
The text was updated successfully, but these errors were encountered: