[SOLVED] High battery usage (Pro-Mini / RFM69 / Si7021)

[eiten]

@Oumuamua said in High battery usage (Pro-Mini / RFM69 / Si7021):

What's the impact of the step-up converter on power consumption while the circuit is in sleeping mode?

According to the datasheet 18-30μA

[skywatch]

Your sleep interval is set for 1 minute but the comment says 10 minutes.

If you want 10 minutes between sends then you have to change the sleep_interval from 60000 to 600000. (note the extra '0').

[Oumuamua]

Hi,

Thanks for all replies.

@skywatch : thanks! I was running a test with a 1 min loop but didn't change the description.

@Yveaux : have you been able to run up to 63% without the booster? my sensor stops working when the battery is at 2.8v (2x AA)

@eiten : this might be the latest issue I'm having. Even with my limited current measurement, the step-up is actually using a crazy 11mA (not uA) when idle. Same current as when not connected with the board.

Will investigate further and post back.

Thanks all,

[Oumuamua]

Guys, quick update:

Seems the step-up had a problem. Changed to a new one does not use that much current.

[Yveaux]

@Oumuamua said in High battery usage (Pro-Mini / RFM69 / Si7021):

have you been able to run up to 63% without the booster

Yes, just 2xAA, directly powering pro mini 8mhz & nrf24
What brown out level is set in the the atmega fuses? Mine are set to 1.8v (and yes, I realize I'm overclocking the atmega when batteries are low...)

[eiten]

@Oumuamua said in High battery usage (Pro-Mini / RFM69 / Si7021):

the step-up is actually using a crazy 11mA (not uA) when idle. Same current as when not connected with the board.

That is not normal! Do you have a second step up? It seems to be... not normal :face_with_rolling_eyes:

[eiten]

@Oumuamua said in High battery usage (Pro-Mini / RFM69 / Si7021):

Seems the step-up had a problem. Changed to a new one does not use that much current.

Oh... Sorry. I should read all the new messages befor posting again....

[Oumuamua]

Hi all,

Thanks for all the help.

After some testing and letting the node run for some days, it seems that the issue is partially solved: battery consumption is very low when the node is idle.

However, the battery consumption seems to reach full runtime levels when something happens with the gateway. My follow-up question is:

What exactly happens happens when the node sends a message to a gateways that is either unreachable or cannot pass the message on (to a MQTT server, for example)? Shouldn't the node try a couple of times and then move on to sleep as per the code?

I have been working on my home network and had to disconnect / reboot the router, gateway, etc.

Every time it happens, two situations occurred:

• gateway didn't report updates to the MQTT server (probably an issue with the gateway as the sensors are meters away and have -25 to -40 RSSI levels, I reseted the gateway in those few circumstances)

• message reaches the gateway and MQTT server, but the controller didn't record it (Openhab), in which case I rebooted the controller

Many thanks again,

[Oumuamua]

Guys,

Just quick update to help others that may find this topic relevant: problem is solved. Problem was the step-up (probably low quality). Sensor is working well and with very low battery usage (no change in 5 days).

Thanks for the comments.

[mfalkvidd]

nice work @Oumuamua, thanks for reporting back.

[NeverDie]

The product listing for the step-up that the OP is using says:

Sucks the juice out of your batteries.

Sounds like it delivers on what it promises.... :rolling_on_the_floor_laughing: