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.

CC2640R2F: How implemtation of the new direction finding capability (AoA) in BLE 3, is different with respect to BLE 5.1 ?

Part Number: CC2640R2F
Other Parts Discussed in Thread: CC2640

Hi,

I just noticed that in the post below Clément has mentioned:

"on CC2640, the RTLS is based on BLE 3. If you want RTLS based on BLE 5, then you need to migrate to CC2642 / CC2652"
https://e2e.ti.com/support/wireless-connectivity/bluetooth/f/538/t/852440?tisearch=e2e-sitesearch&keymatch=Angle%2520of%2520Arrival

Could you please shed some lights on the following questions :

1. Have you implemented the AoA direction-finding capability in the BLE 5 stack at all? (Even for CC2642 / CC2652) If yes which example in which SDK covers that?

2. Can implementation of AoA direction-finding capability on the BLE 5 stack lead to higher precision or better results with respect to using BLE 3? If yes, why?

3. Except for the precision in the question above, what are there the other possible differences? (for example how the range is different? ) 

4. Why 3 devices have used to implements the AoA example instead of 2? Can't it still be implemented on the BLE 3 with just 2 devices?


Thanks 
Regards

  • Hi John,

    The AoA feature is implemented for the BLE5-stack, and similar to the CC2640R2, there is a SimpleLink Academy for AoA. The RTLS example projects for BLE 5, rtls_master/rtls_passive/rtls_slave, can be found under the ble5stack examples module. 

    The main differences between these two comes down to the available RAM on the devices. The CC2640R2 does not have enough memory to store all data for one RTLS event, and so it will take longer to get angle data - compared to a CC26x2 device. You will also find that the implementation of the RTLS functionality, as this is on top of the BLE 3 and BLE 5 stack respectively, will slightly differ for the two SKDs.

    Best regards,

    Vetle

  • Hi Vetle, 

    Thanks for your response. 

    Can you also tell me why 3 devices are used in the example both for BLE 3 and BLE 5? just two should be enough  

    Moreover, how one is supposed to know that the CC2640R2  is NOT BLE 5 compliant? AoA is supposed to be a BLE 5.1 optional capability, you say the CC2640R2  "supports BLE 5" but you implemented the AoA on the BLE 3 stack! Alright 
    Can you please just refer me to a link that gives this information? Maybe in the SimpleLink CC2640R2 SDK (3.30.00.20) 

    Regards

  • Vetle G said:

    The CC2640R2 does not have enough memory to store all data for one RTLS event, and so it will take longer to get angle data - compared to a CC26x2 device. 



    Could you also explain a bit more about this? Are you talking about the passive device? if yes is that why it does not make a BLE connection directly to the slave device? 

    Thanks

  • Could you provide an answer?
    Thanks a lot

  • Hi,

    The AoA format in BLE 3 is TI proprietary solution which embedded the tone inside advertising payload.

    AoA format for BLE 5 is BT 5.1 specified solution, which adds the tone at the end of the connection packets after CRC.

    All these information can be found in the software users guide:

    AoA for CC2640r2 BLE3

    AoA for CC13x2_26x2 BLE5

    There is not enough RAM/Flash on CC2640r2 to implement BT5.1 specified solution for master and slave devices.

    CC2640r2 passive can do AoA with BT5.1 format AoA packets.

    If you only wants 2 devices solution, you can go to CC2642/CC2652 device and follow the SimpleLink Academy Task 1 Option 3.

    http://dev.ti.com/tirex/content/simplelink_academy_cc13x2_26x2sdk_3_30_03_00/modules/rtls_toolbox_ble5/ble_aoa/ble_aoa.html