OTA capture dont show the CS procedure running

RE: OTA capture dont show the CS procedure running

Abhinav152 — Mon, 15 Sep 2025 14:42:13 GMT

This issue was a setup-related issue

RE: OTA capture dont show the CS procedure running

tesc — Fri, 04 Jul 2025 14:20:35 GMT

Hi,

Right, so from the first part of the log it looks like channel sounding is running fine.

What exactly is the issue, is it that you can't see the channel sounding in the sniffer trace?

If yes: Is the sniffer new enough (or upgraded enough) that it will show packets related to channel sounding, which is a relatively new feature of Bluetooth? That is - does the sniffer support the sniffing of channel sounding?

Regards,
Terje

RE: OTA capture dont show the CS procedure running

Abhinav152 — Thu, 03 Jul 2025 07:28:16 GMT

Hi tesc can you please check the logs and let me know the issue

RE: OTA capture dont show the CS procedure running

Abhinav152 — Tue, 01 Jul 2025 09:55:19 GMT

Hi, i have taken a log from the nrf examples. Below is the attached file. Can you help check asi am doing the same steps as yours. devzone.nordicsemi.com/.../cutecom.log

RE: OTA capture dont show the CS procedure running

tesc — Mon, 30 Jun 2025 12:19:02 GMT

Hi,

Do you have any logs from the device as well? You may have to set the appropriate BT_CS_DE_LOG_LEVEL_* for getting verbose enough logs. On the other hand, the most verbose log levels may introduce bottlenecks from the logging system.

Regards,
Terje