Differences in Roles in LEAPS on the QM33120WDK2

Wireless Connectivity Ultra-Wideband
1

The LEAPS guide allows you to specify roles for each node, such as nmp, nma, nmi, nmt, nmtl, and nmb. However, the differences between these roles are not explained. Could you explain the differences between these roles?

Also, on the MDEK1001, a node configured as nmp could retrieve location information from a node configured as nmt. Is this possible on the QM33120WDK2? I think I configured it the same way, but I can’t get any information from nmp.

When I connect a node configured as nmp to a PC and request a location (using commands like lec, les, or leaps_loc_get), I want to retrieve the location of a node configured as nmt.

2

Looping in @leapslabs for comment.

3

I’ve come back to the MDEK1001 (DWM1001-DEV).

If I set nmp on 1001, it becomes a passive tag:

tn (pasv,twr,np,le)

However, if I set nmp on 33120WDK2, it becomes a passive anchor:

an (pasv,-)

Since the anchor doesn’t have le, it seems impossible to calculate the position. Is there a reason why this setting changed? I need this feature…

Is there a way without adding a Raspberry Pi or a modem or something?

4

I configured a node with passive tags via TCS.

mode: tn (pasv,twr,np,le)

However, I still can’t receive the location of the active tag.

Here are the passive tag outputs from the DWM1001-DEV and QM33120WDK2. The biggest difference is that when I check the anchor list, 1001 appears in the list, but 33120 does not.

DWM1001-DEV

dwm> si
[000070.730 INF] sys: fw2 fw_ver=x01030001 cfg_ver=x00010700
[000070.730 INF] uwb0: panid=x1234 addr=xDECA2D7DF41583B3
[000070.740 INF] mode: tn (pasv,twr,np,le)
[000070.740 INF] uwbmac: connected
[000070.740 INF] uwbmac: bh disconnected
[000070.750 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=DW83B3
[000070.760 INF] enc: off
[000070.760 INF] ble: addr=D9:6A:A4:13:85:66
dwm> la
[000075.040 INF] AN: cnt=4 seq=x04
[000075.040 INF]    0) id=000000000000CD2D seat=0 seens=235 map=0000 pos=0.00:0.00:0.00
[000075.050 INF]    1) id=0000000000009422 seat=1 seens=212 map=0000 pos=1.20:0.00:0.00
[000075.060 INF]    2) id=000000000000CD1D seat=2 seens=100 map=0000 pos=0.00:1.20:0.00
[000075.060 INF]    3) id=000000000000870B seat=3 seens=80 map=0000 pos=1.20:1.20:0.00
[000075.070 INF]
dwm> lec
dwm> POS,0,5530,0.21,2.03,-0.33,90,x09
POS,0,5530,0.21,2.01,-0.37,89,x09
POS,0,5530,0.21,2.00,-0.39,89,x09
POS,0,5530,0.20,1.97,-0.43,88,x09
POS,0,5530,0.20,1.99,-0.40,91,x09
POS,0,5530,0.21,2.01,-0.34,91,x09
POS,0,5530,0.20,1.99,-0.38,89,x09
POS,0,5530,0.19,1.99,-0.38,90,x09
POS,0,5530,0.20,1.99,-0.39,90,x09
POS,0,5530,0.28,2.06,-0.28,96,x09
POS,0,5530,0.26,2.03,-0.34,89,x09
POS,0,5530,0.24,2.01,-0.36,90,x09
POS,0,5530,0.23,1.99,-0.40,88,x09
POS,0,5530,0.32,2.05,-0.25,96,x09
POS,0,5530,0.30,2.02,-0.30,89,x09
POS,0,5530,0.27,2.02,-0.32,90,x09
POS,0,5530,0.26,2.02,-0.32,91,x09
POS,0,5530,0.24,1.94,-0.42,84,x09
POS,0,5530,0.34,2.04,-0.27,96,x09
POS,0,5530,0.31,2.02,-0.34,89,x09

QM33120WDK2

leaps> si
[000004.740 INF] release: LEAPS RTLS v1.1.0-a25271
[000004.740 INF] sys: main main_ver=x02060001 cfg_ver=x01040000 batt=empty:0mV:NoCharger board=LC14_B pwr_cnt=0 rst_cnt=0
[000004.741 INF] uwb: ch9 prf64 plen128 pac8 txcode11 rxcode11 baud6800 phrmodeext phrratestd sfdtypeieee4a sfdto129 stsmodeoff stslen64 pdoamodem0
[000004.742 INF] uwb: tx_pwr=x34/xEEEEEEEE sts:shr:phr:data=26.5:26.5:26.5:26.5[dB] cpl=FCC/ETSI pgcnt=239 temp=25
[000004.743 INF] uwb: lna=1 pa=0 rf1=1 rf2=0 xtaltrim=37 tx_delay=16426 rx_delay=16426
[000004.745 INF] uwb: panid=x1234(sys_cfg=x1234) panid_mask=xFFFF addr=xDECA6879129093CC
[000004.754 INF] mode: tn (pasv,twr,np,le)
[000004.755 INF] uwbmac: connected prof=2 (manual)
[000004.787 INF] uwbmac: bh disconnected
[000004.787 INF] cfg: sync=0 fwup=1 ble=1 leds=1 le=1 lp=0 uab=1 stat_det=0 mode=0 upd_rate_norm=2 upd_rate_stat=2 label=ID93CC
[000004.788 INF] enc: off
[000004.788 INF] ble: addr=68:79:12:90:93:CD
leaps> la
[000020.058 INF] AN: cnt=0 seq=x00
[000020.059 INF]
leaps> lec
leaps>

@leapslabs
Could you please let me know if the API within LEAPS has changed and this feature is not available on the 33120WDK2 or if I have configured something wrong?

5

Hi,

In PANS RTLS (MDEK1001) there was an option to use the device in listener mode by configuring it in UWB passive mode.

In LEAPS RTLS (QM33120WDK2) this option is not available. The UWB passive mode will not collect the positions from the Tags and hence cannot print it using the les command.

It is necessary to have a host gateway software to configure the device with backhaul and to provide bridging between the UWB and the Ethernet/WiFi network.

  • In the UDK / QM33120WDK2 this is done using the LEAPS Gateway Linux daemon running on the Raspberry Pi.
  • Another option is to have a dedicated gateway hardware where the LEAPS Gateway firmware runs on an MCU to provide the data bridging between the UWB and Ethernet/WiFi network. We do provide this gateway hardware. Please feel free to contact us to find out more about this option.

I hope this helps.

Cheers,
TDK

6

Hello.

I’m so sad to hear that this feature is gone.

I wanted to build this kit using only that kit, without any additional hardware, but that seems impossible.

Where can I find information on the second piece of hardware you suggested? I visited the LEAPS website, but I couldn’t find anything other than the WDK2.

7

Hi,

You can still use a Raspberry Pi connected to the LC14 device via the USB as shown here

Please contact us via info@leapslabs.com and we will provide you with more information about our products. They are not listed yet on our website.

Thanks,
TDK