This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

CC2745R10-Q1: About Channel Sounding

Part Number: CC2745R10-Q1

Hi Team, 

On CC2745R10‑Q1 EVM with SDK 9.14.00.39, our customer runs ble_device_car_node_with_distance.py but no distance is reported.

Device discovery and CS start seem OK; the distance field stays empty/None, no exceptions.

After checking the BLE SDK USER GUIDE, all the steps are performed.

Could you advise if this is a known issue with 9.14.00.39 and what configuration or patches are required to obtain distance?

Any recommended debug flags/logs to verify CS measurements would also help.

Happy to share logs and project details.
Thanks,
Mike

 

(.venv) C:\ti\simplelink_lowpower_f3_sdk_9_14_00_39\tools\ble\ble_agent>cd examples

(.venv) C:\ti\simplelink_lowpower_f3_sdk_9_14_00_39\tools\ble\ble_agent\examples>python ble_device_car_node_with_distance-Arrow.py
Logging to file: C:\ti\simplelink_lowpower_f3_sdk_9_14_00_39\tools\ble\ble_agent\examples\ble_device_car_node_with_distance-Arrow_log\01_15_2026_14_01_05_ble_device_car_node_with_distance-Arrow.log
<RTLSNode(BLE Device, started 29072)> []
Start Scanning for peer devices
Start Scanning
00:00:00:00:00:00: scan enabled
Adv report detected
Adv report detected
Adv report detected
Adv report detected
Adv report detected
Adv report detected
Adv report detected
Adv report detected
Adv report detected
adv local name: Key Node
Create a connection with [239, 64, 150, 223, 10, 12] as a central
00:00:00:00:00:00: scan disabled
Connection created with: Key Node, connection handle: 0
Connection Data
----------------------------------------------------------------------
Status:                 0
Opcode:                 5
Address Type:           ADDRTYPE_PUBLIC_ID
Device Address:         0C:0A:DF:96:40:EF
Connection Handle:      0
Connection Role:        8
Connection Interval:    24
Connection Latency:     0
Connection Timeout:     2000
Clock Accuracy:         0
----------------------------------------------------------------------
Waiting for pairing events from peer Key Node...
Pairing Encrypted Event Received
Pairing Complete
Connection Handle:     0
State:                 4
Status:                0
------------------------------------------------------
Connections: {'Key Node': 0}
***** read local cap *****
***** read remote cap *****
Remote Capabilities
----------------------------------------------------------------------
_io: []
event: 64
conn_handle: 0
status: 0
num_config: 4
max_procedures: 0
num_antennas: 1
max_ant_path: 4
role: 3
optional_modes: 1
rtt_cap: 0
rtt_aa_only_n: 255
rtt_sounding_n: 0
rtt_random_payload_n: 255
nadm_sounding: 0
nadm_random_seq: 0
optional_cs_sync_phy: 6
no_fae: 1
ch_sel_3c: 0
cs_based_ranging: 0
t_ip1_cap: 120
t_ip2_cap: 120
t_fcs_cap: 448
t_pm_csap: 0
t_sw_cap: 0
snr_tx_cap: 0
----------------------------------------------------------------------
***** security enable *****
Security Enable
----------------------------------------------------------------------
_io: []
event: 67
conn_handle: 0
status: 0
----------------------------------------------------------------------
***** set default settings *****
***** create config for connection *****
Create Config
----------------------------------------------------------------------
_io: []
event: 65
conn_handle: 0
status: 0
config_id: 0
state: 1
main_mode: 2
sub_mode: 255
main_mode_min_steps: 0
main_mode_max_steps: 0
main_mode_repetition: 0
mode_zero_steps: 3
role: 0
rtt_type: 0
cs_sync_phy: 1
channel_map: [252, 255, 127, 252, 255, 255, 255, 255, 255, 31]
ch_m_repetition: 1
ch_sel: 0
ch3c_shape: 0
ch3c_jump: 0
rfu0: 0
t_ip1: 3
t_ip2: 3
t_fcs: 6
t_pm: 2
rfu: 0
----------------------------------------------------------------------
***** procedure enable *****
***** procedure enable *****
***** procedure enable *****
***** procedure enable *****