Power Consumption

[Qmick01]

Hi All,

I have been running the Pax counter on the TTGO LORA OLED board using Lipo battery packs.
A 20Ah pack lasts about 30 days with a 600 second sleep cycle and BLE only enabled. Additionally the OLED is off and the onboard LEDs are all removed.

I don't think the TTGO board is the best for my uses as I have seen commercial LORA devices which sample things and contain an 8 or 9 ah battery and have a 10 year life span even though they may send data every hour.

Has anyone spent any time testing the Pax counter code on different boards to get maximum power efficiency or have any other tips to extend battery life?

Thanks in advance.

[cyberman54]

It's not the board hardware, it's the application. Wifi and/or BLE sniffing draws far more power than all other board components. Thus, it makes no sense to compare a wifi/BLE sniffer with a simple sensor LORA application.

Nevertheless, there are some boards with lower power consumption in sleep mode, than TTGO 1.6.1. But this won't leverage lifetime of a battery powered sniffing application. The relevant impact comes from sniffing duration and dutycycle.

[Qmick01]

Thanks.
The present configuration uses two transmit cycles, one for battery and one for PAX. Would reducing that to a single transmission save power?

[cyberman54]

again, the power consumption comes not from transmit cycles, but from sniffing duration.

[Qmick01]

Thanks for your reply. I think the sniffing cycle I have used is 30 seconds. If I shorten that period does it have an impact on the results or the connection process? I seem to recall I had tried it on a 15 second cycle but then the devices couldn't reconnect if they lost contact with a gateway.

…

On Mon, 14 Aug 2023, 06:05 Verkehrsrot, ***@***.***> wrote: again, the power consumption comes not from transmit cycles, but from sniffing duration. — Reply to this email directly, view it on GitHub <#987 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AOZZCO7FEPJGFT4ZHXOIRGDXVGWYTANCNFSM6AAAAAA3O3CGOU> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>