Improving Bluetooth Channel Sounding Measurements with nRF54L15 DK and SDK 2.9.0 for Indoor Positioning

[apes25]

Hello everyone,

Our team is developing an indoor positioning solution and is exploring Bluetooth channel sounding as a core technology. We are currently using the nRF54L15 DK and have been working with the channel sounding examples provided in Nordic Semiconductor SDK version 2.9.0.

During our initial testing, we've observed significant noise in our measurements, resulting in an error of approximately 4 meters. This is impacting the accuracy of our results, and we are seeking guidance on the following:

• Noise Reduction and Configuration: Are there specific configuration parameters or settings within the sample code that can be adjusted to minimize noise and improve measurement accuracy?
• Scalability with Multiple Tags and Anchors: To achieve broader coverage and more robust positioning, we are investigating the feasibility of using multiple reflectors acting as tags and multiple initiators serving as anchors. How would implementing this multi-tag, multi-anchor architecture affect system performance and complexity? and wich parameter shoud we adjust on the example to achive it?

We understand that channel sounding is currently an experimental feature in SDK 2.9.0, but we are keen to investigate its potential for our application. Our objective is to achieve reliable indoor positioning with reasonable accuracy for real-time device tracking.

Any examples, documentation, or shared experiences would be greatly appreciated.

Thank you in advance for your assistance!

Best regards,

[Kenneth]

Hello,

I am not sure what algorithms you are using here, your own or those in the samples. The algorithm in the samples are not very accurate and are mostly to test data flow of between radio and application. So switching algorithm should likely help.

It's possible to setup several anchors and reflectors, this is the same as for normal BLE connections. Be aware that all tracking occurs in connected mode, so this will limit the number. The number of connections will take up time, so you need to balance the number of connections and intervals, this will be application dependent so I am not able to give any best case numbers here on the amount of devices etc.

Hope that helps,
Kenneth