Ranging quality is NOT OK after a while

RE: Ranging quality is NOT OK after a while

Elfving — Mon, 15 Sep 2025 14:15:22 GMT

I see. Well CS_DE_QUALITY_OK being false would mean that the sample is discardable, my coworker expands a bit on this here as well. My first thought is that this would be due other external factors, like rf noise or objects being in the way. Though if you do not think that is applicable, and if it happens after the same amount of time every time then it does sound like a bug, eg. a memory leak. It is still a bit strange to me that it would impact the range as well though.

Could you try lowering the memory, and see if that makes the issue happen even sooner?

Regards,

Elfving

RE: Ranging quality is NOT OK after a while

Triscuit — Thu, 11 Sep 2025 18:24:59 GMT

Hi Elfving. This project I would say is very heavily modified, since I have been working on this for the past few months. I took the original sample and added a lot onto it, but the CS connection and ranging procedure are pretty much the same as the original. Oh Sorry, I think 'ranging quality is NOT OK' is my own message, it is just in an else statement for when the CS_DE_QUALITY_OK is false in the ranging_data_cb function. Another question I have is, if I were to reverse the devices and use three initiators connect to one reflector, would that make concurrent channel sounding possible? Because right now I am using three reflectors and one initiator. Is the initiator doing more work by starting it or would it be the same since the reflector also has to hold a stable connection? And sometimes when it is ranging it says parsing empty step data, is there any way to reduce or stop this? Thank you so much.

Sincerely,

Triscuit

RE: Ranging quality is NOT OK after a while

Elfving — Thu, 11 Sep 2025 08:31:36 GMT

[quote user="Triscuit"]By sequentially it is connecting and disconnecting from one node at the time. I am just not sure how data quality would be affected?[/quote]

No, me neither. The sequential way is what we currently recommend as well, though I guess what you say about RAM resources could make sense.

[quote user="Triscuit"]Right now I implemented a GATT messaging system where after the initiator ranges it would send the readings to my laptop via Bluetooth GATT, and the laptop would calculate the trilateration results. However, I noticed that when it sends the readings wirelessly as well as range at the same time, the distance at which it can range decreases, going from over 20m to not even 10m. Would this be because the device is holding two concurrent connections, making it split its radio, resulting in worse readings? Or would this just be a software bug?[/quote]

Ah so one reason why we recommend doing this sequentially is to avoid multiple connections potentially colliding, as we haven't yet optimized the SDC to avoid this for channel sounding. So even though you do things correctly by having the CS connections sequentially, it could be best if you did the GATT messaging in a timeslot of its own as well. Although I am surprised that this would result in just a worse range/ readings.

Is this project something heavily modified, or essentially the default samples with a few additions? I guess it could be a bug, but I wouldn't expect any in the default samples.

[quote user=""]ranging quality is NOT OK[/quote]

Btw, I am not immediately seeing where this could be coming from in the initiator. This isn't your own error message, right?

Regards,

Elfving

RE: Ranging quality is NOT OK after a while

Triscuit — Tue, 09 Sep 2025 17:46:47 GMT

Hi,

Yes I am using the channel sounding with ras samples. I am using 54l15 dk's and VCS version 3.0.99. By sequentially it is connecting and disconnecting from one node at the time. I am just not sure how data quality would be affected? Maybe because the device is now using more memory as it should so it does not have enough resources to dedicate to the ranging?

This brings me to another point. Right now I implemented a GATT messaging system where after the initiator ranges it would send the readings to my laptop via Bluetooth GATT, and the laptop would calculate the trilateration results. However, I noticed that when it sends the readings wirelessly as well as range at the same time, the distance at which it can range decreases, going from over 20m to not even 10m. Would this be because the device is holding two concurrent connections, making it split its radio, resulting in worse readings? Or would this just be a software bug?

Thank you.

Sincerely,

Triscuit

RE: Ranging quality is NOT OK after a while

Elfving — Mon, 08 Sep 2025 11:29:53 GMT

Hi,

I assume this is based on the nRF/ nordic channel sounding samples, that you are using SDC, and nRF54L15DKs? What NCS version are you using? And by doing it sequentially, you connect and disconnect from one node at the time?

Regards,

Elfving