Implementing Channel Sounding concurrent distance measuring

[Rubix]

Hi,

I'm trying to test Channel Sounding with concurrent measurements using one initiator and two reflectors on nRF54L15 DKs.

From replies in other DevZone threads, it seems this is now supported in the latest samples. However, the required configuration changes weren’t specified.

Could someone clarify what settings need to be adjusted (e.g., in prj.conf, device tree, or sample parameters) to enable one-initiator / multi-reflector Channel Sounding?

[Simonr]

Hi

We have an unofficial sample project showcasing how to have multiple connections for Channel sounding, so you can use that as reference. We are currently working on more official support for this as well.

6710.Channel_sounding_Abdir-Reflector_control_point.zip

Best regards,

Simon

[Rubix]

Hi Simon,

Do you know which board this sample project was originally designed for?

I'm trying to build it on the nRF54L15DK (NCS version 3.1.1), and I’m seeing some issues that make me think the configuration may have been meant for a device with more RAM.

Examples:
– CONFIG_BT_CHANNEL_SOUNDING_REASSEMBLY_BUFFER_SIZE was set to 5600, but the Kconfig range for the nRF54L series limits it to 4800.
– The build then fails during the final linking stage with a RAM overflow:
region 'RAM' overflowed by 68030 bytes (coming from .noinit / .bss).

TF-M builds fine, but the Zephyr application image never gets produced, which suggests that some of the app-side buffer sizes or Bluetooth configs exceed the available RAM for the 54L15.

Before I start reducing buffers manually, I wanted to confirm whether this project was created for a different Nordic SoC (e.g., nRF54H20, nRF52840, or nRF5340), which would explain the mismatched ranges.

[Triscuit]

Hi Simon, 

The code you provided, for the initiator and reflector C code, am I correct in saying that they are both single connection program? It does not store multiple reflectors nor is it capable of switching between multiple devices. The Python program is made for multilateration, however, it requires multiple initiator inputs. Does this mean we have to implement the switching logic ourselves?