Hi,
I am trying to calculate the distance between two tags present in the network with the help of TWR.
I would like to know if the location of the tag is present in the TWR slot superframe or somewhere else. If it is present in the superframe, how will i be able to access it from the superframe?
Hi Seppe
Thank you for your response.
I am using the DWM1001 hardware and trying to get the location of the Tag with the help of TWR employed with the device.
My requirement to get the location of the tags using TWR and check if any tags present in the network is close to each other and generate a message when two tags are close to each other.
The software which i am using is segger embedded studio for arm.
Is it possible to get the access for the TWR slots so that i can get the location of the tags which are close to each other as it is already using TWR technique for communication?
The examples on Github are simple TWR examples. For this example, one of the devices needs to run the “Initiator” firmware ( ss_twr_init) and the other device the “responder” firmware (ss_twr_resp). The responder will print the distance between the 2 devices over UART.
PANS is a more complete demo that can provide absolute location using fixed infrastructure based on TWR. The Android app only works with the PANS firmware. It is possible to configure one of the devices as a “tag” and an other device as a “anchor”, set up as initiator, allowing to just measure the distance between the 2 devices. Measuring the distance between 2 tags is only possible if a network with 3 or more anchors is set up.
If you have a network set up with >3 anchors it should be possible to calculate the distance between 2 tags based on their absolute position. I don’t think it is possible to do TWR between 2 tags (but I could be wrong in this).
I tried using dwm_node_id_get API provided in the API guide pdf. The API does not seem to be working. Is is possible to use the API’s provided in the API guide in the github examples. And can i use more responders and get the distance from the initiator.
The API guide you mentioned is the API guide for the PANS firmware. Sorry for the confusion, I agree the title of this document can be somewhat misleading.
The examples on Github use revision 2.04 of our deca_driver library. The documentation for this can be found in the “DW1000 Device Driver API Guide” contained in the The DW1000 Application Programming Interface software package, see DW1000_Software_API_Guide_rev2p4.pdf.
I would be possible to create a more advanced setup with multiple responders, but the example we provide on Github does not support this. PANS does provide a more advanced RTLS setup, but we can not release the full source code of this system. It is however possible to connect an external MCU / device to the DWM1001 and use the PANS firmware API over UART, SPI or BLE.