Problem configuring Anchors with acas

Hi there,

I am testing the dwm1001-dev and I am trying to set a first module as anchor initiator. The system receives my commands and responds quite well: i can get system info, set the module as an anchor initiator through the nmi command and so on. When using the acas command, it keeps doing an echo of the first character i send and I do not receive acas: ok!

I appen here my shell interface:
[000321.010 INF] sys: fw2 fw_ver=x01030001 cfg_ver=x00010700
[000321.010 INF] uwb0: panid=x0001 addr=xDECAEC0E38B25704
[000321.020 INF] mode: tn (act,twr,np,le)
[000321.020 INF] uwbmac: disconnected
[000321.020 INF] uwbmac: bh disconnected
[000321.030 INF] cfg: sync=0 fwup=0 ble=0 leds=1 le=1 lp=0 stat_det=1 (sens=1) mode=0 upd_rate_norm=10 upd_rate_stat=10 label=DW5704
[000321.040 INF] enc: off
dwm> acas 1 0 0 1 1 2 0
acas 1acas 1 0 0 1 1 2 0
acas 1

Usage: acas <fw_upd>
dwm> "

Do you have any ideas on this?

Hi Alatoplasto,

What is the uart configuration ? I wonder if the issue could be due to the carriage return / line feed character configuration. What does the device return if you send only “acas” ?



I connected my Pc to the DEV board through the USB connector and I am using Termite for commands. UART is configured with:
Baud rate: 115200
Data bits: 8
Stop bits: 1
Parity: none
Flow control: none
And it appends a “carriage Return”

If I send only acas i get:
“Usage: acas < inr> < bridge> < enc> < leds > < ble> < uwb> < fw_upd>”

All commands with 0 or 1 numerical command works, eg. “si”, “nmg”, “nma” or “gc 14”, “gg 14”, “gs 14” and so on… when using commands with more characters like acas, it does not work.


Hi Alastoplasto,

Hat seems fairly odd, I’ve never experienced that. Can you try a different serial connection software, such as teraterm ? I’ve used it extensively and it woks perfectly with it usually.

acas 0 0 0 1 1 2 0

What does that return ? In my case i have “acas: ok”


Thank You!

With Teraterm it works perfectly, answering acas:ok.

I tested it with Termite and Terminal and both showed the same issue, I don’t know why. At least now we know it…

Thank you again!