Hi everyone,
I’m using DOIT ESP32 DEVKIT V1 and UWB DWM3000-MAX-CA to test localization,
my sketch are Initiator and Responder Examples in Makerfabs-ESP32-UWB-DW3000 library from Github to do it.
About hardware, I have connected between 2 board like Makerfabs board
I have read Device ID: deca0302, prove SPI is Ok,
But I debugged and see break point poll for reception of a frame or error/timeout
I don’t still understand the reason
May you help me solve the problem?
Hi @quangtuqorvo, unfortunately, this is not a supported software by Qorvo. We can try to help if you are using our SDK with the supported hardware targets.
I will leave this post open in case you are able to get help from the forum community.
1 Like
Hi quangtuqorvo,
I remember there is an example folder that name ise range in the library(Makerfabs-ESP32-UWB-DW3000-main).
Did you use that examples range_tx and range_rx?
Could you send any logs or serial output?
If you give some details, maybe i can help you..
1 Like
Hi fatih_basaris, thank for your help,
I exactly use range_tx and range_rx of library to precision in location tracking but program is still in Polling for reception of a frame or error/timeout
status_reg value at Initiator is 0x18200F7 and at Responder is 0x6F00.
After that, I change POLL_TX_TO_RESP_RX_DLY_UUS, POLL_RX_TO_RESP_TX_DLY_UUS, RESP_RX_TIMEOUT_UUS and set dwt_starttx(DWT_START_TX_IMMEDIATE) and add delay about 800 us in Responder.
With that, I have distance, but it’s incorrectly (about 50000 m).
Hi again.
1-Did you use the values in the original examples? and how was the result?
2-You said that I have distance, but it’s incorrectly (about 50000 m).
I think that error is usually caused by the timestamps being incorrect or inconsistent. This may be due to:
- Timing parameters not matching the hardware.
- Responder responding too early or too late.
- Antenna delay values incorrectly set.
- Time stamps incorrectly read or calculated.
Best regards..