La command parameters

Wireless Connectivity Ultra-Wideband
1

Hi, everyone

What does seens, lqi, fl, map mean in the La command parameters?

Thanks,
Varn

2

Hi, i recommend to see the DWM1001 API Guide PDF.

This is the “la” command response

6.31 la
Show anchor list.
Example:
dwm> la
[003452.590 INF] AN: cnt=4 seq=x03
[003452.590 INF] 0) id=DECA5419E2E01151 seat=0 idl=0 seens=0 col=0 cl=000F nbr=000F fl=4002 opt=03C1B046 hw=DE41010
0 fw=01010101 fwc=7B033F01
[003452.600 INF] 1) id=DECA78A55EB00CA8 seat=1 idl=1 seens=119 col=0 cl=000F nbr=0000 fl=0000 opt=03C1B042 hw=DE410
100 fw=01010101 fwc=7B033F01
[003452.620 INF] 2) id=DECAFCED8D50111C seat=2 idl=1 seens=103 col=0 cl=000F nbr=0000 fl=0000 opt=03C1B042 hw=DE410
100 fw=01010101 fwc=7B033F01
[003452.640 INF] 3) id=DECA51421A901150 seat=3 idl=0 seens=81 col=0 cl=000F nbr=0000 fl=0000 opt=03C1B042 hw=DE4101
00 fw=01010101 fwc=7B033F01

4

Hi,

Yes I have seen that, but I want to know what the ‘seens’ and ‘col’ and ‘cl’ and ‘nbr’ mean?

Other parameters such as ID and seat number, I am aware what it means.

Thanks.

5

Hi,

the values are rather for internal use. But I can provide some information here:

  1. seens is the amount of times the anchor’s beacons have been received. It’s a 8 bit counter.
  2. cl and nbr are related with clustering map occupation (seat occupation).
  3. col is no longer available in R2.

Cheers,
TDK

1 Like
7

Hi,

Thanks for the reply. So that means if seens is 0, there is something wrong with the Anchor right? It means it hasn’t received any Beacon messages?

Thanks,
Varn.

8

Hi Varn,

yes, that’s correct. It means that Anchor’s beacons have not been seen.

Cheers,
TDK

10

Hi,

Thanks for the reply. Any way to resolve it? Do we have to restart the Anchor?

Thanks,
Varn.

11

Hi Varn,

can you please describe first your setup and the issues what you have seen?

Cheers,
TDK

13

Hi,

Basically, we have placed around 35 Anchors at a distance of 20 meters apart. They have good LOS too, except for a few pillars here and there.
We have noticed that, sometimes the seat number of Anchors changes to -1 and gets updated to a positive value. We were trying to debug why this happens.

Hence, the Tag location gets stuck at certain instances and gets updated back after like 5 seconds.

Hence we were wondering if it is due to the Anchors seat number updation that the Tag location issues are observed?

Thanks