Channel Sounding RAS RREQ and RRSP at the same time

[Bruno Randolf]

Testing with NCS 3.0.1 and nRF54L15-DK. I would like my devices to be able to work as channel sounding initiator as well as reflector role. In my own code I have integrated the code from samples channel_sounding_ras_initiator and channel_sounding_ras_reflector, and that works so far. However, when I enable CONFIG_BT_RAS_RREQ=y and CONFIG_BT_RAS_RRSP=y at the same time, even with CONFIG_BT_RAS_RRSP_AUTO_ALLOC_INSTANCE=n then I fail to get results on the initiator side (the reflector side works fine). I always get the error "Tried to parse empty step data".

You can easily reproduce this by adding 

CONFIG_BT_RAS_RRSP=y
CONFIG_BT_RAS_RRSP_AUTO_ALLOC_INSTANCE=n

to channel_sounding_ras_initiator.

[Bruno Randolf]

Hi Simon! Yes, thank you! That fix helps to get the sample running. When I activate CONFIG_BT_RAS_RRSP_AUTO_ALLOC_INSTANCE=y I get some warnings, but it still works:

W: Peer is not subscribed to status characteristic.
W: Notify overwritten failed: -22

I assume that has to do with the GATT ranging roles you mentioned.

My use case is that I would like to be able to do CS between any two devices on demand, which means for one device the role is not fixed to initiator or reflector but it should be able to do both. I am not doing this in parallel or on the same link. It's more like device A could be initiator and then device B should be reflector. Or in an other moment B could be the initiator and A the reflector. Do you think that is feasible? It seems we are close...

[Simonr]

Hi

This does indeed seem feasible to me, what exactly are you missing in your application now, and are there further action points from our side? The warnings seem to refer to you trying to enable notifications but that not being enabled on the peer side. I don't think you need to implement notifications here.

Best regards,

Simon