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.

CC2642R: AoA examples not working

Part Number: CC2642R

I'm trying to do a quick test of AoA using the CC2642R  (x2) + BoostXL-AoA.

I would like to use the RTSL_UI example initially to have a display of the angle.

If I use the SDK simplelink_cc13x2_26x2_sdk_5_10_00_48  and the 

C:\ti\simplelink_cc13x2_26x2_sdk_5_10_00_48\tools\ble5stack\rtls_agent\rtls_ui

The Master is recognised, but scans never detect the Slave.

If I program the target board with simplelink_cc13x2_26x2_sdk_5_20_00_52 Responder, then the board is picked up in the scans. I can connect, and RSSI measurements work.
However in Connected mode when trying to run the AoA, the errors:

Fail to set AoA parameters

DEBUG: Message="AoA failed to init, status = ", Value=5

If I run Connectionless mode, there are no errors but the Angle is always 0.

If I use SDK 5.20 for everything, then the connections work, but the AoA display mode has been removed from the app. RSSI is displayed.
I can use the python scripts to store csv and there see the IQ values. Is there no way to show the angle for a demo of the system, either in a GUI or Python text?

What is causing the "Message="AoA failed to init, status = ", Value=5"

Thanks in advance,

Ben

  • Hey Ben,

    I've assigned a colleague to comment on your post.

  • Hi Ben, 

    Please refer to https://e2e.ti.com/support/wireless-connectivity/bluetooth-group/bluetooth/f/bluetooth-forum/1023057/cc2642r-comments-on-the-aoa-updates-for-sdk-5-20 

    You can review the Simplelink Academy modules under the RTLS Toolbox folder to get more details on the way to store the IQ data either using the python script or the RTLS UI.

    I hope this will help,

    Best regards,

  • Hi Clement,

    I am trying to do a quick evaluation of the technology so don't want to get into IQ angle estimation at this stage. I can run the SDK 5,20 and record IQ data OK but this doesn't help at the moment.

    So if I run the SDK 5.10 can you tell me why the Slave is never detected?

    If I program the target with SDK 5.20 and keep the 5.10 UI and Master, the newly named Responder is detected in the scan and I can now connect but I get the error DEBUG: Message="AoA failed to init, status = ", Value=5. Can you tell me what that error is?

    Best regards,

    Ben

  • Hi Ben,

    I am afraid the demo without proper estimation algorithms would provide bad experience. Of course you can run the demo in SDK 5.10, but I am not sure this should be considered as an "evaluation".

    A couple of ideas I can think of are

    • make sure to use the RTLS UI and the embedded code (master and slave) from the same SDK version
    • when you change the version of the RTLS UI used, make sure to force refresh the page (Ctrl+F5). Otherwise the web browser keeps some stuff in cache. Then close the RTLS UI, reset all the devices, and re-launch the RTLS UI

    I hope this will help,

    Best regards,

  • Hi Clement,

    Using SDK5.10 the Slave was never discovered. Do you believe this example should work? I tried CCS and Clang compiled version, I tried Debug and Release versions, none were detected in the scan. If I just changed the target to SDK5.20 Responder, it was detected in the scan and I could connect (but then the AoA error occurred). so the target board is working and my process for programming is working. The Master board is also working.

    The target board is the CC2642R1 Develoment Kit Rev.B

    So to your knowledge this example should still work? Anything I should watch out for?

    Best regards,

    Ben

  • Hi,

    Yes, I am sure the example works.

    As you have mentioned, we have renamed our examples between SDK 5.10 and 5.20. The scan results are filtered based on the devices names contained in the advertisement data. If you are not using the same SDK versions, the device name won't be recognized.

    Best regards,

  • That's interesting as that is backwards from what I am seeing. I downloaded 5.10 first and tried that so there was no mix up of versions. I'll try a BLE scanner app  with 5.10 and see what the target is reporting.