RE: Optimizing Power Consumption in BLE Geofencing Project and Enabling DFU on nRF52820 SoC / nRF52833DK

Simonr — Tue, 28 Jan 2025 14:20:24 GMT

First off, what will the use case of this geofencing be on your end. Bluetooth LE doesn't have very high range and can never be 100% fault proof in terms of reliability.

1. Yes, I think you should be lower the power consumption of the central_and_peripheral_hr. During advertising and connections lowering it below 100µA might be to expect too much, depending on the parameters you require of course. You can use the Online Power Profiler for some estimates on what to expect in various Bluetooth operations. Since you see current consumption on multiple mA's I'm guessing debugging/logging and serial is enabled, as those tend to draw a lot of power. That being said. These current consumption plots seem very strange, and it doesn't seem like an application operating as expected. Can you show me how the PPK2 is connected to the device you're measuring on exactly?

2. DFU is not really relevant to this ticket's subject, and I'd strongly recommend you create a new topic on the DFU issue, as it's much easier to have an overview if we have one ticket per topic, so please create a new one on the DFU topic and an engineer proficient in DFU will take a look.

3. In System ON low power mode (assuming you refer to the modes specified in the product specification, the radio will be turned off, so a geofencing solution (or anything using the radio) won't be able to run at single digit µA current consumption. The RTC can run in low power idle modes though, but not much else. It is normal to use this if you only need to wake up and advertise every now and then, so the device can spend most of its time in this mode and wake up every minute or so to do an advertisement/connection of some kind.

Best regards,

Simon