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.

LPSTK-CC1352R: Detection by 2x RX sets simultaneously, 1x LPSTK-CC1352R working as the TX

Part Number: LPSTK-CC1352R
Other Parts Discussed in Thread: LAUNCHXL-CC26X2R1,

Hi everyone,

I have the following scenario, 2x receiving setups (RX) LAUNCHXL-CC26X2R1, each connected with a BOOSTXL-AOA, each running on a separate laptop, using the RTLS_UI.

As the transmitting unit (TX) I have 1x LPSTK-CC1352R, modified with this soffware flashed on it (https://e2e.ti.com/support/wireless-connectivity/bluetooth/f/bluetooth-forum/983980/lpstk-cc1352r-aoa-example-rtls_slave-lpstk-cc1352r?tisearch=e2e-sitesearch&keymatch=LPSTK-CC1352R#)

My question now is: can the LPSTK-CC1352R set up a connection with 2 receiving setups (RX) LAUNCHXL-CC26X2R1 at the same time or can it only handle one at a time? Right now, when I test it, it only connects to one RX unit, and the other one rests, but I would like to have them both connected at the same time. Is there a chance to change something in the software for the LPSTK?

Thanks in advance,
Best regards.

  • Hi,

    If you are using connectionless-AoA then the number of deices synchronized with a target is unlimited. In other words, you can have as many locators as you want.

    If you are using connection-AoA, each receiver (rtls_master) will have to establish a Bluetooth Low Energy connection with the target. As a result, the number of locator is limited to the number of Bluetooth Low Energy connections the target can simultaneously maintain. This number depends on the RAM available and on the connection interval. With a smaller connection interval, collisions risks increase and make the connections more likely to be dropped.

    In summary, I recommend to use connectionless-AOA if you are planning to have several independent locators.

    Please review our documentation for additional details about connectionless-AoA and connection-AOA.

    Regards,

  • Hi Clément

    thanks a lot for your quick reply, I will try that out.

    The last time I was using the connectionless-AoA option I tested it with a 0* angle (straight ahead) 2m away, the result that came out was totally inaccurate (see attachment)...where as with the same testing set (2m, 0* angle) using connected-AoA it worked fine. 

    Regards,

  • Hi,

    We do not provide the localization algorithms for connectionless-AoA.

    For connetionless-AoA you should use the IQ data and apply your algorithms.

    Best regards,

  • Hi,

    So the connectionless-AoA will not work correctly with the RTLS_UI?

    The .csv sheet I downloaded when using the RTLS_UI does not include any IQ data.

    Does this require running the non-visual demo to receive IQ data, or how do I receive that data?

    extract from documentation:

    "In the case of connectionless AoA, the host MCU selects the periodic advertisement the rtls_master has to synchronize with.

    The rtls_master synchronizes with the periodic advertisements sent by the rtls_slave. The rtls_master can then do I/Q sampling and calculate angles base on the CTE appended to the periodic advertisements.

    As a reminder, the rtls_passive is not involved for connectionless AoA."

    Regards,

  • Hi,

    The non-visual demo - especially the script rtls_connectionless_aoa_example_with_rtls_util.py - will allow you to collect the IQ ata in a .csv file.

    If is was not clear, IQ data extraction is described by the Bluetooth Core specifications. This is the way the radio samples the CTEs. Algorithms to compute AoA use these IQ data. 

    I hope this will help,

    Regards,