We are currently almost in the production phase and have some problems concerning the BHI160B in combination with nRF52832 (running zephyr).
Our application has two main states. During the normal state we are using the activity recognition only for detecting the activity of the user. Our product is worn on the wrist and we've noticed that the activity recognition is not really accurate, most of the time it is not even recognized when a user is in a vehicle. Is there a way to improve these results? Implementation:
result |= bhy_enable_virtual_sensor(VS_TYPE_ACTIVITY_RECOGNITION, VS_WAKEUP, 1, 0, VS_FLUSH_NONE, 0, 0);
result |= bhy_install_sensor_callback(VS_TYPE_ACTIVITY_RECOGNITION, VS_WAKEUP, sensors_callback_activity_recognition);
In the second state we only use the pick-up and significant motion to detect if the device is picked up and worn again. All other sensors of the BHI160B are disabled and uninstalled in this state. However the current consumption is still really high ~500uA. After disabling the gesture recognition, current consumption is only ~40uA, see attachments. 460uA seems to be a lot when only using the gesture recognition, is there a way to improve this?
Thank you in advance.
Solved! Go to Solution.
It is better to contact the local FAE to get more support.
According to what you said, BHI160B fw need be update. Currently sadly are unable to support and share it directly within the community. If you have any further requests, please visit https://www.bosch-sensortec.com/about-us/contact/contact-form, and use the contact form to submit your request. Thanks for your understanding.