Hi all,
I have 2 DWM3001CDKs that have been programmed with the latest DW3_QM33_SDK_1.0.2 binary for the CLI, but it doesn’t work when connected to battery.
When performing TWR between initiator and responder, everything works fine when both are hooked up to USB, but when one is running off battery, it says SUCCESS but then has RX_TIMEOUT for a second, and then it seems to reboot and then says SUCCESS with a reading again.
@carlos.silva seemed to have fixed it back here: DWM30001CDK standalone operation without connection to USB UART - #14 by carlos.silva, but this still seems to be an issue with this latest release.
I made a video showcasing this issue here: https://youtu.be/zMKBI1GoJoY
In the video the initiator is on the left and the responder is on the right.
To setup the initiator I do SETAPP INITF -CHAN=5 -ADDR=0 -PADDR=1
and then ‘SAVE’ and then I reboot the device, and to setup the responder I do SETAPP RESPF -CHAN=5 -ADDR=1 -PADDR=0
and then ‘SAVE’ and then reboot the device. When both are hooked up via USB it works great. Once I take the responder off USB and hook up an external 5V supply via the micro USB connector (J9)
I am not sure how to modify this new SDK to make it work… I also tried the HEX file provided by @akash found here: QM33 SDK CLI skipping ranging sessions when connected to USB power only - #3 by akash, but this also didn’t work as the USB never enumerated (waited a couple of minutes and never showed up, so I could never set it up via the CLI).