• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 263 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

LP-EM-CC2745R10-Q1: Measure distance using 9.10.00.83 of the SimpleLink Low Power F3 SDK

Tuan Phan Van
Prodigy 10 points

Part Number: LP-EM-CC2745R10-Q1

I am using 9.10.00.83 of the SimpleLink Low Power F3 SDK to measure distance.

cs_log_140.0cm_0.0deg_2026-03-08_16-07-08.txt 

I want to extract data from hex data to compute the distance. However, the extraction is not correct. Is there any document mention about the structure of hex data?

Thank you very much!

  • 0
    TI__Genius 9505 points

    Hello, 

    Are you evaluating CS? The HCI format you are parsing through for 9.10.00.83 is not Bluetooth LE V6 qualified, so the HCI output is not fully compliant with the specification. If you are following the BLE spec for parsing, you should update to the newest SDK, 9.14.02.16. 

    For 9.10.00.83, as mentioned, the hex data does not follow BLE spec. The output is entirely proprietary. I recommend upgrading to 9.14.02. 

    Thanks,
    Isaac

  • 0 in reply to Isaac Larson
    Prodigy 10 points

    Thanks Isaac,

    Yes, I am watching this video https://www.ti.com/video/6363699718112. I am wondering how it is measured correctly. This video was recorded before the 9.10.00.83 release.

  • +1 in reply to Tuan Phan Van
    TI__Genius 9505 points

    Tuan, 

    The video was recorded using a proprietary demo used for evaluating channel sounding on a radio level. The ranging library which is used for the post processing has been improved greatly since the 9.10 SDK. Additionally, the stack is now Bluetooth LE v6 certified. If you would like to see better distance accuracy, I still recommend upgrading to 9.14.02. Additionally, the HCI raw byte output will be specification compliant on 9.14.02. 

    Thanks,
    Isaac

  • 0 in reply to Isaac Larson
    Prodigy 10 points

    I upgraded to 914.02. However, I still want to evaluate CS on Hex Data because I may need some more information. is there any document that help me verify the extraction is correct?

  • +1 in reply to Tuan Phan Van
    TI__Genius 9505 points

    Hello, 

    The Bluetooth Specification can help you with this. The HCI event description for CS starts at Vol 4, Part E, section 7.7.65.39. The output follows this structure. The data line is just the Step_mode, Step_Channel, Step_Data_Length, and Step_data. You can read more about what is contained in the step data in the HCI_LE_CS_Subevent_Result section of the Bluetooth LE v6 specification (Vol4, Part E, 7.7.65.44). I see that you are using main mode three. I would recommend starting with main_mode 2 if you are still trying to parse the raw data. 

    Thanks,
    Isaac