I’ve setup four DWM1001-dev devices as anchors (one is anchor initialiser -> ain(act,real,-) , the other three just anchors an(act,-,-)). I have a fifth DWM device setup as an active tag (tn(act,twr,np,le)). I first tested the system in VM using the minicom in UART shell mode. Running les command prints ranges from tag to each anchor and also the location solution. No problem!
I then did the same connecting the tag to my Raspberry Pi 3B (note: it’s not a 3B+). I connected the tag to the Pi via usb, ran the UART shell, issued the les command and got position back.
I then attempted to run the example script provided; tag_cfg executable (following procedure outlined in 220.127.116.11 of Firmware User Guide). Upon running the executable, I get the following error: “Unable to open UART […] UART: Ensure it is not in use by another application” (first attached file). Fine, I thought, I’ll try connecting to to the Pi via the headers (the same setup as figure 9 of the Firmware User Guide). I get exactly the same error.
I then tried to communicate to it in UART shell mode using minicom (connecting to serial0 as per 18.104.22.168 of Firmware User guide) over header connection (figure 9). The shell opens, but it keeps trying to send the string Ubuntu, second attachment.
Does anyone have any suggestions as to why I can’t connect to it over UART using the API example, and why it has this strange behaviour in UART shell mode over header connection?
I tried to connect over SPI, and it appears to be working (although the anchors, excluding initialiser, powers off after a few seconds).
Thanks for your help,