apologies for the late response. I can confirm your observation is correct. It is a bug in PANS. Thanks for the feedback!
To summarize the issue:
Tag in low power mode with BLE enabled and is in range with the network - power management works correctly and the average current is ~15uA (with stationary detection enabled).
Tag in low power mode with BLE enabled and is out of the network (it seeks for the network) - the average power consumption would be > 425 uA - this is a bug in PANS.
Solution options:
Disable completely BLE on the Tags.
In case BLE is necessary - then disable BLE when the node is out of the network and enable it again when being back.
We have not investigated yet the exact cause of the issue but we can do some bugfix / customization if you need an update soon. Please contact us via https://www.leapslabs.com/ in that case.
@leapslabs, you mention solution option 2, disable BLE when the node is out of network. How can that, be done automatically? Maybe with code in user space?
Any clue?
Thanks!
Ramiro
@leapslabs Do you plan to update the software to remove this bug, a BLE based search is a very good idea (battery wise) and it would be great to have that functionality. This bug combined with the fact that an out-of-network range tag keeps searching for UWB network and consumes high current even in low power mode is really limiting to developing a battery powered tag. Thanks!