Increasing sensor update rate in Thingy:52

[Till]

Hi,

I'm looking at increasing the sensor update rates for the Thingy:52, and get more frequent readings into the sample app. Let's assume I want to change the temperature sensor frequency.

Following this question, I assume that it boils down to changing

• TEMP_MIN_INTERVAL in ThingyUtils.java (set the update interval in the app)
• BLE_GAP_ADV_INTERVAL_MIN and BLE_GAP_ADV_INTERVAL_MAX in Utils.java (set the BLE connection interval in the app)
• BLE_TES_CONFIG_TEMPERATURE_INT_MIN in ble_tes.h (set the update interval in the firmware)
• The BLE_GAP_CP_MIN_CONN_INTVL_MIN etc. family of variables in ble_gap.h (BLE connection interval in the firmware) can be left untouched as they give the limiting values.

Will this work? If not, what else do I need to do? Thanks for your time!

(I'm running this version of the app on my Android device.)

[ketil]

Hi,

Are you writing your own app based on the Android source code?

If not, you can increase the sensor update rates in the configuration view of the Android app. For the temperature sensor there is a minimum update rate of 100ms.

Ketil

[Till]

Hi Ketil, thanks for the answer! I'm writing my own app based on the sample app. I'm interested in the maximum possible update rates for all the different sensors. Is it possible to achieve faster update rates than the fastest ones in the configuration view?

[ketil]

Yes, it is possible to get faster update rates for the sensors. You will have to check each individual data sheet for the maximum speed. The limits in Thingy were set after trial and error in order to have all the sensors running at the same time. You should not expect to get much better performance if you need all the sensors running at the same time. If you use only a few sensors you can achieve much higher rates. Also, you are correct in your assumptions of what lines you need to change in firmware and the Android app.

[Till]

Thanks, that makes a lot of sense! I'll also bear in mind that the ultimate limits are given by the connection interval suggestions in the firmware. (BLE_GAP_CP_MIN_CONN_INTVL_MIN mentioned in the question).