Send/show IoT data in UART shell mode

Wireless Connectivity Ultra-Wideband
, , ,
1

Hi all,

I have 3 DWM1001 nodes, all flashed to DWM1001_PANS_R2.0.hex.

As described in “DWM1001 Gateway Quick Deployment Guide” section 3.2, I have configured one node as initiator, one as bridge and one as tag. Additionally I have enabled “Show incoming IoT data” with the “udi” command on all nodes.

The system infos (si) look as follows:

si for initiator 
# initiator
dwm> si
[001044.570 INF] sys: fw2 fw_ver=x01030001 cfg_ver=x00010700
[001044.570 INF] uwb0: panid=x1234 addr=xDECA4C2980E08796
[001044.580 INF] mode: ani (act,real)
[001044.580 INF] uwbmac: connected
[001044.580 INF] uwbmac: bh disconnected
[001044.590 INF] cfg: sync=0 fwup=0 ble=1 leds=1 init=1 upd_rate_stat=120 label=DW8796
[001044.600 INF] enc: off
[001044.600 INF] ble: addr=E9:1B:2C:B9:5F:A7
si for tag 
# tag
dwm> si
[001138.110 INF] sys: fw2 fw_ver=x01030001 cfg_ver=x00010700
[001138.110 INF] uwb0: panid=x1234 addr=xDECA1C5816D01DB4
[001138.120 INF] mode: tn (act,twr,np,le)
[001138.120 INF] uwbmac: connected
[001138.120 INF] uwbmac: bh disconnected
[001138.130 INF] cfg: sync=0 fwup=0 ble=1 leds=1 le=1 lp=0 stat_det=1 (sens=1) mode=0 upd_rate_norm=1 upd_rate_stat=100 label=DW1DB4
[001138.140 INF] enc: off
[001138.140 INF] ble: addr=F0:6E:11:1A:B7:0E
si for bridge 
# bridge
dwm> si
[001078.450 INF] sys: fw2 fw_ver=x01030001 cfg_ver=x00010700
[001078.450 INF] uwb0: panid=x1234 addr=xDECACC8A34505DB0
[001078.460 INF] mode: bn (act,-)
[001078.460 INF] uwbmac: connected
[001078.460 INF] enc: off
[001078.470 INF] ble: addr=C8:23:62:2C:57:DB

I use the “uui” command on the tag to send some data:

 dwm> uui 11223344 10

But neither the bridge nor the initiator seem to receive something, nothing is output in their UART shells.

The “lb” command on the tag shows no bridges:

# tag
dwm> lb
[001571.590 INF] (null): cnt=0 seq=x00
[001571.590 INF]

But the initiator lists the bridge:

# initiator
dwm> lb
[001509.600 INF] BN: cnt=1 seq=x02
[001509.600 INF]    0) id=0000000000005DB0 seat=1 seens=200 rssi=-77 cl=00000002 nbr=00000000 pos=nan:nan:nan
[001509.610 INF]

Also the line uwbmac: bh disconnected from initiator’s and tag’s system info looks suspicious to me.

Are there some additional configuration steps required to make IoT data transmissions work in UART shell mode?

Peter

2

Hi Peter,

Are you using the bridge node with the raspberry pi to form a gateway ? Just double checking because the bridge node is not meant to be used on its own, it must be paired with a raspberry pi.

Is the gateway PanId correctly set ?

In deed the uwbmac: bh disconnected is symptomatic of the issue. Until you get it connected, you will not be able to send uplink/downlink data.

Thanks
Yves

3

Yves,
when u say that the bridge mode must be paired with the raspberry pi, does this means we cannot use a usb cable between then to establish link? is it necessary to use the header pin to link them?? because the web manager does not show me any anchors or tags of the network and i configured the panid correctly with the one i have.
image

ZZ
ZZ600×501 3.11 KB

4

do i need to do as described in :
4.3.2.2 UART Generic mode example ( dwm1001 firmware user guide ) and run dwm1001_host_api package example in the raspberry so that the web manager works ?

5

The Raspberry Pi is intentionally not part of my setup.

What configuration steps are preformed by the raspberry to pair with the bridge node and to get the backhaul connected? I guess the raspberry sends some special TLVs over SPI or UART, are they documented somewhere?

Peter

6

Hi Peter,

The interface between the raspberry pi and the dwm1001-dev is currently not documented. I’m afraid at the moment the only way to get the backhaul to work will be to pair the device with a raspberry pi.

Thanks
Yves

7

I see, thank you for the information.

8

Yves,

you said that the “interface between the raspberry pi and the dwm1001-dev is currently not documented”. Do you plan to make such documentation available to us in the future? If yes, when? I’ve looked at the communication between the raspberry pi and the dwm1001-dev with the help of a logic analyzer and I think I understand pretty well how it works. However, I still can’t change the backhaul status to connected using a device other than the raspberry pi (we would like to avoid using it in our final setup).

4 Likes