Can not observe channel sounding ranging on a Pixel 9 Phone using Nordic Sample ras_reflector <> nRF54L15 tag

Info:

HW: nRF54L15 Tag / DK

nRF: v3.4.0

Dev OS: MacOS 26.5.2

Using nRF Toolbox Android App (most recent version)

on a Google Pixel 9 with build number CP1A.260405.005

Recreate:

  1. Build and flash v3.4.0 nRF Sample ras_reflector to an nRF54L15 Tag: west build -p -b nrf54l15tag/nrf54l15/cpuapp -- -DEXTRA_CONF_FILE=android_ranging.conf
  2. Download nRF Toolbox app on compatible channel sounding phone (Pixel 9 should be supported)
  3. Connect to CS Reflector on Toolbox app
  4. Initiate CS
  5. Observe error as documented in the attached photo

Hello,

We are trying to observe channel sounding functionality from a Pixel 9 phone to an nRF54L15 tag running an unmodified Nordic sample, ras_reflector. We downloaded the nRF Toolbox app onto a Pixel 9 yesterday and connected with the nRF54 tag. The result is shown in the attached photo when we initiate channel sounding.

The sample is built like this: west build -p -b nrf54l15tag/nrf54l15/cpuapp -- -DEXTRA_CONF_FILE=android_ranging.conf

The LED that indicates a connection stays on the entire time after initial connection until we disconnect on the phone side. Can we get some guidance to observe channel sounding functionality?

Thanks,

Matt Hurst

  • Hi Matt, 

    The current NCS v3.4.0 contains a validation check due to a SIG errata (on the Procedure_Interval field of the Initiator's (Pixel) CS_REQ). This was added in the 6.3 Core Spec release. It really is the Pixel that sends parameters that are just out of what the spec defines, resulting in the reflector rejecting the CS request.

    Adding the check resulted in interoperability issues (as observed here), so it was recently reverted. We will add a backport for 3.4.1!

    If you want to temporarily play around with nRF ras_reflector on nRF54L15DK and the nRF Toolbox on the Pixel 10, you can use NCS v3.3.1. Sorry for the inconvenience. 

    Regards,
    Amanda H.

  • Hi Amanda,

    Thanks for the prompt response. Unfortunately, even after building with NCS v3.3.1, we are still not able to get the results we were looking for. We are still getting the same error as before.

    To reiterate, we are using a Pixel 9 and an nRF54L15 Tag. What else can we do to get this working?

    Thanks again,

    Matt

  • Can you test with nRF54L15DK? You can currently use nRF54L15DK with v3.3.1. For the nRF54L15 Tag, please wait for v3.4.1. 

Related