BLE connection and data transfer

UDK - All-in-One UWB Demo Kit
1

Hello everyone.

I have a QM33120WDK2.
When I connect an LC13 or LC14 to an Android device via BLE using nRF Connect (not LEAPS Manager), the connection keeps getting terminated with status 19. What could be causing this?

Also, can I send tlv or shell commands and receive responses via this BLE connection, as if I were connecting via USB? Alternatively, if I connect a separate MCU to the USB port and send the commands, will the measured location information be transmitted via BLE?

Thank you in advance for your help.

2

Hi,

Thank you for purchasing our product.

The reason the device disconnects is because there is an Auto-disconnect mechanism as described on the link below:
https://docs.leapslabs.com/leaps-rtls/integration-guide/leaps-api/ble-interface/

You can establish the shell over the BLE and that is also described on the link above. Both TLV and Shell APIs are available over the BLE.

Cheers,
TDK

3

Hello

Thank you for your reply. I confirmed that BLE is maintained only when a signal is sent. I solved the command transmission using a different method than BLE.

I also have a question: the Z value of the tag’s position coordinates returned in response to leaps_loc_get is always 0. Is this because all anchors currently have their Z coordinates set to 0? Or is it because there is not enough height difference between the tag and the anchor?

When outputting position coordinates in 3D space, do the X and Y coordinates reflect this height difference?

4

One more question.

leaps_loc_get outputs a list of anchors. How is the order of the output anchors determined?

5

Hi,

When the DL-TDOA is used, the current algorithm can provide only 2D, so the Z axis is indeed always 0.

When using TWR the Z axis is available and should be non-zero. With higher Z separation of the Anchors the accuracy and precision will improve.

The output format of the leaps_loc_get is listed on the link below

Cheers,
TDK