RTLS System
Table of Contents
- General Information
- Introduction
- General Configuration
- Continuous Connection Information - Setup
- Angle of Arrival - Setup
General Information
- Detailed guide can be found on SimpleLink Academy
- To get usage information for the RTLS Node Manager scripts and GUI please refer to:
tools\ble5stack\rtls_agent\README.md
- In order to edit and view how the RTLS subsystem handles uNPI commands, please refer to the following file:
tools\ble5stack\rtls_agent\rtls\rtls\ss_rtls.py
In order to see a usage example, please refer to:
tools\ble5stack\rtls_agent\examples\rtls_connected.py
which shows how to use a RTLS Coordinator + RTLS Responder + RTLS Passive / Connection Monitor combination for connected AOAtools\ble5stack\rtls_agent\examples\rtls_connectionless.py
which shows how to use a RTLS Coordinator + RTLS Responder combination for connectionless AOA
To access GUI, please refer to the readme file found in
tools\ble5stack\rtls_agent
.
Introduction
This readme contains the following information: 1. How to setup Angle of Arrival (AoA) demo (Both Connected AoA and Connectionless AoA are supported by out of box example) 2. How to setup Continuous Connection Information (CCI) demo
General Configuration
The following is a list of build defines that are set in build_config.opt file for RTLS Coordinator and RTLS Responder.
For more information please refer to
BLE5 Stack User's guide
GAP_BOND_MGR
- GAP_BOND_MGR - Used to include the Bond Manager
HOST_CONFIG
BLE Host Build Configurations
- PERIPHERAL_CFG+CENTRAL_CFG - Used to define host as BLE multi-role
BLE_V41_FEATURES
Configure the stack to use features from the BLE 4.1 Specification
- L2CAP_COC_CFG - Enable L2CAP Connection Oriented Channels
HCI_TL_NONE
- HCI_TL_NONE - No supported HCI commands are available via the Transport Layer's NPI.
Continuous Connection Info - Setup
Software Setup
Continuous Connection Information (CCI) is currently supported on all roles with the following caveats:
RTLS Coordinator
- Coordinator supports BLE multi-role
- Coordinator supports up to 8 BLE connections to Responders
RTLS Responder
- Responder supports BLE multi-role
RTLS Passive / Connection Monitor (CM)
- Passive / CM projects showcase how to utilize the TI Micro BLE Stack as the connection monitor role.
For more information regarding TI Micro BLE Stack, please refer to Micro BLE Stack section under BLE5 Stack User's guide - Passive / CM supports tracking up to 8 BLE connections
Running The Example
The steps to run the out of box example is described in tools\ble5stack\rtls_agent\README.html
Angle of Arrival - Setup
Software Setup
Angle of Arrival (AoA) is currently supported on all roles with the following caveats:
RTLS Coordinator
- Coordinator role will collect I/Q samples
- Coordinator role supports the official BT5.2 Connected and Connectionless AoA implementation
- AoA API's can be accessed by using the RTLS Services host module
RTLS Responder
- Responder will send out a constant tone at the end of the connection packet and it will not collect I/Q samples
- Responder supports the official BT5.2 Connected and Connectionless AoA implementation
- AoA API's can be accessed by using the RTLS Services host module
- The tone length is configured by the user using the CTE Time parameter (refer to
tools\ble5stack\rtls_agent\rtls\rtls\ss_rtls.py
)
RTLS Passive
- Passive supports tracking up to 8 BLE connections
- AoA API's can be accessed by using the RTLS Services host module
Running The Example
The steps to run the out of box example is described in tools\ble5stack\rtls_agent\README.html
- Mind the timing when using both features, if the connection interval is insufficient, it may be that the SW stack won't have enough resources to both keep the BLE connection alive and continuously output results
- The best way to check your timings is by using a Logic Analyzer and debugging the RF RX and TX signals. Refer BLE5-Stack Debugging Guide
Note that the AoA results puts extra strain on the UART and the timing of the system since it involves outputting large chunks of data * Minimum recommended latency (Connection Interval) is 300ms * Maximal recommended latency is 800ms