We are building a beacon that transmits 10 bytes of payload every every 211ms. No connection is required. We need continous broadcasting. According to the battery life estimator, we should be getting more than 200 days of life from our CR2016 (90mAh).
In reality, though, we are getting around 7 days of battery life.
We started with the ble_app_barebone sample app and used it as our starting point. There is nothing else going with i2c, spi, uart, etc (or at least there shouldn't be). My question is what should we be looking at to improve the power consumption?
I looked at the ble_eddystone_beacon_with_hibernation_or_deep_sleep_mode to see if we could be using the deep_sleep mode, but that seems to stop broadcasting altogether, if I am understanding the code correctly. Can I go into a deep-sleep between broadcasts every 211ms?
Hi dirjud,
Since your requirement is advertise continually non connectable advertising events, the you should use extended sleep mode, so that the device can sleep between non-connectable intervals.
In the SW example that you mentioned, the device is going to deep sleep or hibernation, once the non-connectable advertisement is stopped. Please check user_app_on_adv_nonconn_complete().
The sleep mode while is it advertising is extended sleep mode.
static const sleep_state_t app_default_sleep_mode = ARCH_EXT_SLEEP_ON;
It’s not possible to put the device into hibernation or deep sleep mode between advertising intervals.
I would recommend checkingDA14531 Sleep Mode Tutorial (HTML)document.
Thanks, PM_Dialog
So all I do is set:
and now it will sleep between advertizements? I have a new battery life test going to see how much that helps.
Thanks.
Hi dirjud,
是的,you could verify it using the Power Profiler from the SmartSnippets toolbox - the device sleeps between advertising intervals.
http://lpccs-docs.dialog-semiconductor.com/UM-B-083/power_profiler/powerProfiler.html
Thanks, PM_Dialog