EVB1000's (Anchor-0) LED-6 Flashes, But GUI doesn't Discover

Hello!

Anc-0 (EVB1000) LED-6 Flashes when blinks are received from Tags (0 & 1, but 2)

Tag-0 (EVB1000) ---------------------------------------GUI Discovered Tag-0
Tag-1 (DWM1000+MCU)------------------------------GUI Discovered Tag-1
Tag-2 (DW1000+MCU) New board-----------------Not Discovering Tag-2. Anchor LED indicates receive, but No GUI Display. (In Tag-2, TX, RX LEDs blinking, But SFD & Rx OK not showing up)

All firmware versions are 2.25

How to troubleshoot using DW’s test utilities? Any help highly appreciated.
Thanks in advance:hugs:

-Mash

Hi,

All boards have the same software version 2.25.
Could you also confirm that all nodes are configured the same? Either all are S2, S5 , L2 or L5. See TREK user manual section 3.4.
And what do you mean with “new board”? Is this your own design?
You must have at least 1 EVB spare. If you configure this board as TAG 2, does that work?
/Leo

Hi Leo,
Yes, all settings are same and everything runs with 2.25.
Tag 2.0 is own design and all switch settings / modes are hardcoded.
In fact I see no pkt error in decaranging setup using evb1000
Tag-2 exactly behaves like other two, except not shown in GUI (geo fencing)

Any way out?

If you put you switchoff TAG 2 , and then try the 2nd (or 3rd) evb as TAG2? does that work?
If you switchoff TAG-1, will TAG-2 be shown?
Also, you’re using TREK GUI I guess. it should be version 3.8 (if you use 2.25 in the EVB1000’s)

To trouble shoot , could you focus on the DW1000+MCU board to check if that board is 100% OK?
eg Could you use an EVB1000 and your board for 2 way ranging only , eg by using example code 5a/5b or 6a/6b. Or set all S1 dipswitches on the EVB1000 board on (it sets it to SPI2USB) and start PC Decaranging with EVB1000 and your DW1000 board.
And is the DWM1000 using the same MCU as the DW+MCU?
/Leo

Hi Leo, Could you please shed some light?

I tested one tag at a time. I also upgraded GUI to 3,8, but that didn’t help either.
As mentioned earlier;

  1. Tag-2 blink is received by anchor, consistently (LED-8) indicates that
  2. In DecaRanging mode, I see no error. All packets are 100% received.
  3. Compared the above against DWM1000+MCU, Tag-2 is better in terms of Range vs RX errors.
  4. Same MCU as eval kit is used in 3 cases.

-Mash

Gentle reminder…
Hi Leo, Could you please shed some light?

I tested one tag at a time. I also upgraded GUI to 3,8, but that didn’t help either.
As mentioned earlier;

  1. Tag-2 blink is received by anchor, consistently (LED-8) indicates that
  2. In DecaRanging mode, I see no error. All packets are 100% received.
  3. Compared the above against DWM1000+MCU, Tag-2 is better in terms of Range vs RX errors.
  4. Same MCU as eval kit is used in 3 cases.

-Mash

Reply

|45x45

accutrak

1

1m

(post withdrawn by author, will be automatically deleted in 24 hours unless flagged)

Reply

Bookmark Share Flag Reply

Watching

You will receive notifications because you created this topic.

Suggested Topics

Main Forum

dwm1000dwm1001|0|7|17h|
|NIS Command on Android App

Main Forum

dwm1001|0|14|21h|
|Error in DWM1001 Firmware API Guide V2.2 (dwm_int_cfg_get, dwm_cfg_tag_set )

Main Forum

dwm1001|0|17|1d|
|Raspian image for the gateway

Main Forum

mdek|0|16|1d|
|Gateway mqtt messages reliability

Main Forum

dwm1001|0|19|1d|

There are 8 new topics remaining, or browse other topics in Main Forum