• State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 51 subscribers
  • Views 191 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.

CCS/LAUNCHXL-CC2640R2: TIme out Error about "all node to set AOA params"

Ningzhi Zhu
Prodigy 10 points
Part Number: LAUNCHXL-CC2640R2

Tool/software: Code Composer Studio

I carefully read the simplelink tutorial:http://dev.ti.com/tirex/content/simplelink_academy_cc13x2_26x2sdk_4_10_01_00/modules/rtls_toolbox_ble5/ble_aoa/ble_aoa.html.

I know it is mainly for cc26x2 now, but I think it also works for LAUNCHXL-CC2640R2. with SDK 3.30 or 3.40.

So My condition is that I use one LAUNCHXL-CC2640R2+BOOSTXL as "MASTER" and one LAUNCHXL-CC2640R2 as "SLAVE".

I can run the rtls_example_with_rtls_util with RSSI and TOF.

But When I want to run AOA with rtls_aoa_into_csv, I have an error about "set aoa params":

I debuged and I think my embedded and python configurations are right. I can connected master and slave and the "is_aoa_support(all_node) "return TRUE.

But I failed to set aoa params.

  • 0
    TI__Mastermind 39800 points

    Hi Ningzhi,

    TI has made the decision to discontinue further development and support of the TI-proprietary Angle of Arrival (AoA) on the CC2640R2. We recommend and welcome our customers using AoA on CC2640R2 to transition from the CC2640R2 to the new RTLS examples based on the Bluetooth 5.1 specification which can be used with the CC26x2R devices. These software examples can be found in the SimpleLink™ CC13x2 and CC26x2 software development kit 3.40 or later which features a Bluetooth 5.1 qualified stack with support of Bluetooth 5.1 Angle of Arrival. To make this transition, here is a list of available resources you can reference: Simple Link Academy, AoA stack users guide, LaunchPad Tool Order Page

    If you have any questions about moving to the Bluetooth 5.1 AoA solution or any questions about the solution itself, please post to E2E!