DRTLS DWM1001 Gateway stop working

[leapslabs]

Hi Ricardo,

it looks like you have multiple Raspberry running there? If so it looks like your DWM Daemon and Proxy settings are not correct. You can have multiple Daemons but you should have only one Proxy.

See this post for more information on the data chain of the Gateway:

10 000 m² area to cover with RTLS web manager also

Hi Ahmed, The data chain looks like this: Anchor/Tag – Bridge – Kernel Module – DWM Daemon – DWM Proxy – MQTT Broker – DRTLS Web Manager / MQTT client A simplified data flow of the uplink data (from the Edge node toward the Server) can be like this: The Gateway will collect all the Location and IoT data which it can see from the in-range Anchors and Tags. The data will then be forwarded to the DWM Daemon (which will be one per Gateway, so there will be as many Daemons as DWM1001 modules run…

It is completely fine to have multiple Raspberry / Gateway, but they must be configured correctly as follow:

1. You should choose one DWM Proxy on one of the Raspberry to be used. All DWM Daemons on all Raspberries / Gateways should point to the selected DWM Proxy and to the same MQTT Broker. The MQTT Broker can be either on the selected Raspberry or on Cloud. See /etc/dwm1001/dwm1001.config
2. One DWM Proxy should be pointed to the MQTT Broker which you are going to use. The other DWM Proxy just leave them default, i.e. they will be pointed to its localhost MQTT Broker, which is unused.

If you suspect the module might be broken then check output of the dmesg command. It should not contain SPI errors.

I hope this would help.

Cheers,
TDK