Online Power Profiler for Channel Sounding

[NickDeLeenheer]

Hi,

I am currently evaluating the Channel Sounding functionality for indoor localization. I would like to check how much Energy my Initiator and Reflector consume for setting up a connection and during the channel sounding process. This way i can compute it for multiple connections or for 1 connection.

I have seen the online Power profiler, but honestly, i still am a little bit confused in how to use it.

I also tried to understand the timing information available on the paper about channel sounding (https://www.bluetooth.com/channel-sounding-tech-overview/#cscp), but i still don't really understand what is relevant info to fill in the online power profiler.

Kind regards,

Nick De Leenheer

[PaKa]

The Online Power Profiler does not support Channel Sounding so can't really be used to estimate the power consumption. The recommended way to deal with this today is to get a Power Profiler Kit II, nrf-ppk2, and measure the current while running. There is a lot of flexibility in the BT CS spec so you can tweak it a lot and get very different power consumption numbers with trading of aquisition speed and accuracy.

[NickDeLeenheer]

Thanks! I will look into that.

I also have another question if i may ask. The indoor performance of the accuracy of channel sounding (without very fancy algorithms) INDOOR is not good. I was wondering if i can do something with the n_ap (number of antenna paths) to get better accuracy or to mitigate reflections better? Or is it just like this and i can do nothing about it?

Kind regards,

Nick De Leenheer

[PaKa]

using multiple antennas will most likely improve the reliability for indoor measurements. The Bluetooth stack in nRF Connect SDK 3.0.1 (the version you should be using now as it is Bluetooth certified :-)  ) does support multiple antenna paths but the algorithms in the SDK does not so you will have to spin your own to test this.

[NickDeLeenheer]

Hi,

I actually was using NCS 2.9 toolchain. I am now installing 3.0.1... What changed?

[PaKa]

In 2.9.0 the Channel Sounding support was experimental and under development with features missing/not compliant. With the 3.0.1 we had improved the SW maturity to be out of experimental and now Blueteooth qualified with the CS feature.