Gateway with dwm-daemon on Raspberry pi

Hi Ben,

thanks for the output file!

In the outputs I can see, that your Raspberry is running Kernel: 4.14.98-v7+
while the dwm.ko module is compiled for Kernel: 4.14.50-v7+
That’s the reason why the Kernel Module dwm.ko could not load. It provides communication between the DWM1001 and the DWM Daemon.

Can you please check that the Raspberry Image you have used is reflashed in whole to the SD card?
What is the size of your SD card?

Thanks!
Cheers, TDK

Hi

Re-flashing the Pi has fixed it. Thank goodness no more soldering for now!

Many thanks,

Ben.

Hi Ben,

Ok, great! What we suspect might happened is that your system has been updated either automatically by Raspberry or you have triggered that. The dwm.ko module must run on the kernel version 4.14.50-v7+ so Raspberry can update anything but not the Kernel.

Can you please verify if anything like that might happened? If so, please disable the kernel update on your Raspberry or if that is not possible then disable completely the system update.

Thanks!
Cheers, TDK

Yes, an enthusiastic staffer “made sure everything was up to date”. Not unreasonable in many situations, but clearly not this one.

Many thanks for the support.

Ben.

1 Like

Just hopping in here, is there a reason the GPIO header needs to have long pins? Wouldn’t something like this work too? https://www.antratek.nl/raspberry-pi-gpio-tall-header-2x20?___SID=U

Hi,

sure, that connector should be Ok.

Cheers,
TDK

Hi guys,
i have many problems like u had , the web manager did not see any device…
then i flashed again the raspian image do to that kernel issue, and now the web manager sees the node unit but can’t see any tags or anchors…
also when i access minicom :

  • minicom -b 115200 -o -D /dev/ttyS0
    or minicom -b 115200 -o -D /dev/serial0
    and tap enter tiwce i could not acceess dwm app, there is no response in minicom.
    Any help ?

Hi Ahmed,

it is strange that you do not see any output on the minicom. That means either the Firmware is not on the module or something is wrong with the communication with the board - please check the wiring/soldering and reflash the module to ensure it contains correct firmware.

Can you please go through the following steps and send me the outputs/feedback?

  1. Which Raspberry hardware revision are you using? If possible please send a picture of the Raspberry with the DWM1001.
  2. Is the DWM1001 reflashed with the R2 binary?
  3. Which Raspberry Image are you using? The official one from the Release 2?
  4. Please send outputs of the commands on the failing system:
  5. lsmod
  6. ls -la /dev/dwm0
  7. ps ax | grep dwm
  8. uname -a
  9. dmesg
  10. tail -n50 -f /var/log/dwm-daemon.log
  11. Check that /etc/dwm1001/dwm1001.config contains the same PANID as your other running Anchors.
  12. A screenshot of what you see on the Web Manager.

Cheers,
TDK

1/using Raspberry pi 3 model B V1.2 2015.

2/ yes fw2 :
aazzz

3/ using the DRTLS_raspbian_R2.0 from release 2 files.

4/
5/ lsmod

6/
pi@raspberrypi:~ $ ls -la /dev/dwm0
crw------- 1 root root 200, 0 Apr 16 10:05 /dev/dwm0

7/
pi@raspberrypi:~ $ ps ax | grep dwm
426 ? Sl 0:20 /usr/local/bin/dwm-proxy -c /etc/dwm1001/dwm1001-proxy.config
427 ? Sl 0:01 /usr/local/bin/dwm-daemon -c /etc/dwm1001/dwm1001.config -l /var/log/dwm-daemon.log
1695 pts/0 S+ 0:00 grep --color=auto dwm
pi@raspberrypi:~ $

8/
pi@raspberrypi:~ $ uname -a
Linux raspberrypi 4.14.50-v7+ #1122 SMP Tue Jun 19 12:26:26 BST 2018 armv7l GNU/Linux
pi@raspberrypi:~ $ ^C

9/dmesg_command.txt (48.5 KB)

10/
pi@raspberrypi:~ $ tail -n50 -f /var/log/dwm-daemon.log

2019-04-15 16:52:16.575 INFO [436] [leaps::core::run@60] starting…
2019-04-15 16:52:21.636 INFO [612] [leaps::core::mq_looper@302] Client decada95ceb5c0b0 reconnect
2019-04-15 16:52:22.670 INFO [612] [leaps::mq::client::mosquitto::on_connect@159] Client decada95ceb5c0b0 Connection Accepted.
2019-04-15 16:52:22.670 INFO [612] [leaps::mq::client::mosquitto::on_disconnect@166] Client decada95ceb5c0b0 disconnected(rc=7)
2019-04-15 16:52:26.672 INFO [612] [leaps::core::mq_looper@302] Client decada95ceb5c0b0 reconnect
2019-04-15 16:52:27.673 INFO [612] [leaps::mq::client::mosquitto::on_connect@159] Client decada95ceb5c0b0 Connection Accepted.
2019-04-15 16:52:31.725 INFO [612] [leaps::core::mq_looper@319] Client decada95ceb5c0b0 ip addresses updated
2019-04-15 16:53:01.760 INFO [612] [leaps::core::mq_looper@319] Client decada95ceb5c0b0 ip addresses updated

Mon 15 Apr 17:01:20 UTC 2019
Starting daemon dwm-daemon with command ‘/usr/local/bin/dwm-daemon’ and options ‘-c /etc/dwm1001/dwm1001.config -l /var/log/dwm-daemon.log’…

2019-04-15 17:01:21.703 INFO [442] [leaps::core::run@60] starting…
2019-04-15 17:01:26.723 INFO [650] [leaps::core::mq_looper@302] Client decada95ceb5c0b0 reconnect
2019-04-15 17:01:27.757 INFO [650] [leaps::mq::client::mosquitto::on_connect@159] Client decada95ceb5c0b0 Connection Accepted.
2019-04-15 17:01:36.769 INFO [650] [leaps::core::mq_looper@319] Client decada95ceb5c0b0 ip addresses updated
2019-04-15 17:02:06.804 INFO [650] [leaps::core::mq_looper@319] Client decada95ceb5c0b0 ip addresses updated
2019-04-16 09:06:42.477 INFO [650] [leaps::mq::client::mosquitto::on_disconnect@166] Client decada95ceb5c0b0 disconnected(rc=7)
2019-04-16 09:06:42.478 INFO [650] [leaps::core::mq_looper@302] Client decada95ceb5c0b0 reconnect
2019-04-16 09:06:43.478 INFO [442] [leaps::core::run@134] stopping…
2019-04-16 09:06:48.812 INFO [442] [leaps::mq::client::mosquitto::on_disconnect@166] Client decada95ceb5c0b0 disconnected(rc=7)

Tue 16 Apr 09:07:17 UTC 2019
Starting daemon dwm-daemon with command ‘/usr/local/bin/dwm-daemon’ and options ‘-c /etc/dwm1001/dwm1001.config -l /var/log/dwm-daemon.log’…

2019-04-16 09:07:19.681 INFO [440] [leaps::core::run@60] starting…
2019-04-16 09:07:24.740 INFO [596] [leaps::core::mq_looper@302] Client decada95ceb5c0b0 reconnect
2019-04-16 09:07:25.772 INFO [596] [leaps::mq::client::mosquitto::on_connect@159] Client decada95ceb5c0b0 Connection Accepted.
2019-04-16 09:07:34.783 INFO [596] [leaps::core::mq_looper@319] Client decada95ceb5c0b0 ip addresses updated
2019-04-16 09:08:42.818 INFO [596] [leaps::core::mq_looper@319] Client decada95ceb5c0b0 ip addresses updated
2019-04-16 10:05:05.646 INFO [596] [leaps::mq::client::mosquitto::on_disconnect@166] Client decada95ceb5c0b0 disconnected(rc=7)
2019-04-16 10:05:05.647 INFO [596] [leaps::core::mq_looper@302] Client decada95ceb5c0b0 reconnect
2019-04-16 10:05:06.649 INFO [440] [leaps::core::run@134] stopping…
2019-04-16 10:05:12.003 INFO [440] [leaps::mq::client::mosquitto::on_disconnect@166] Client decada95ceb5c0b0 disconnected(rc=7)

Tue 16 Apr 10:05:40 UTC 2019
Starting daemon dwm-daemon with command ‘/usr/local/bin/dwm-daemon’ and options ‘-c /etc/dwm1001/dwm1001.config -l /var/log/dwm-daemon.log’…

2019-04-16 10:05:42.817 INFO [427] [leaps::core::run@60] starting…
2019-04-16 10:05:47.897 INFO [556] [leaps::core::mq_looper@302] Client decada95ceb5c0b0 reconnect
2019-04-16 10:05:48.936 INFO [556] [leaps::mq::client::mosquitto::on_connect@159] Client decada95ceb5c0b0 Connection Accepted.
2019-04-16 10:05:57.948 INFO [556] [leaps::core::mq_looper@319] Client decada95ceb5c0b0 ip addresses updated
2019-04-16 10:06:27.983 INFO [556] [leaps::core::mq_looper@319] Client decada95ceb5c0b0 ip addresses updated
2019-04-16 13:18:03.294 INFO [556] [leaps::mq::client::mosquitto::on_disconnect@166] Client decada95ceb5c0b0 disconnected(rc=7)
2019-04-16 13:18:03.295 INFO [556] [leaps::core::mq_looper@302] Client decada95ceb5c0b0 reconnect
2019-04-16 13:18:04.296 INFO [556] [leaps::mq::client::mosquitto::on_connect@159] Client decada95ceb5c0b0 Connection Accepted.
2019-04-16 13:28:21.353 INFO [556] [leaps::mq::client::mosquitto::on_disconnect@166] Client decada95ceb5c0b0 disconnected(rc=7)
2019-04-16 13:28:21.354 INFO [556] [leaps::core::mq_looper@302] Client decada95ceb5c0b0 reconnect
2019-04-16 13:28:22.355 INFO [556] [leaps::mq::client::mosquitto::on_connect@159] Client decada95ceb5c0b0 Connection Accepted.

11/
#######################################################################

DWM Kernel Module settings

UWB network PANID

Allowed values: 16-bit number in decimal, hexadecimal or octal format

panid = 0x394E

UWB encryption

Allowed values: true/false

enc_en = false

UWB encryption key

Allowed values: 128-bit number in hexadecimal format

enc_key = “333333339999999944444444EEEEEEEE”

UWB firmware update

Allowed values: true/false

uwb_fwup = true

UWB mode

Allowed values: 0=Off 1=Passive 2=Active

uwb_mode = 2

and we have an anchor example si command azeazeaxqdsqsd

12/ web manager

Hi Ahmed,

On the last picture there is some progress I think as both the Daemon and the proxy are reported on the webmanager.

Do you have an anchor configured as initiator in your network ?

Thanks
Yves

i did further research on my own and configurations , now the web manager works but accuracy not that much good.
but the minicom serial connection is still non functional.

Hi Ahmed,

where was the issue? What have you done to get it working? Please share the details so we can know how to help further.

Thanks!
Cheers, TDK

see when u change anything at all it goes back to point zero and no response from the web manager to anchors and tags …
i think we have to change nothing.
it doesn’t work at all :confused:

Hi Ahmed,

Can you connect to the bridge node from the raspberry pi using the minicom -D /dev/serial0 command in a terminal and then sending “enter” twice ?

If the bridge node (dwm1001) does not answer, then there is a base issue and the web manager will not work. If it does’nt work, most likely it means the soldering is not correct.

Thanks
Yves

the minicom on serial0 doesn’t work at all . but even though , yesterday the web manager worked for some time :

as seen in the picture,
for the soldering i verified the continuity of pins 1,2,4,6,9,14,17,20,25 and uart 8,10 and spi 19,21,23,24 all good so what’s the problem?

we cannot say that the soldering is not good when continuity is in fact good for the essential pins

Ok I see, but I don’t understand why minicom to serial 0 doesn’t work if the soldering is good…

The fact it worked only for some time make me think the connection may not be reliable, but I may be wrong. Have you done any update on the raspberry pi ? If yes, please re flash the sd card with the original image and prevent from performing any update on the raspberry pi.

of course i understand that i have to not do any update from the discussion above and the problems i had already …
i don’t think pi could do any update on its own .
also in the tera term when i plug the tag the tag shows no node bridge with command lb. but the web manager detect the bridge node … which is very confusing when all units have same panID .
will try to solder another unit and test or reflash again.

azeasqsd

Hi Amhed,

On my network, the tag does not report BN with LB command (I have the same output as you) but the initiator anchor does. You should try on an anchor to see if it can see the bridge node.

Yves

Okay i have some good news and then i have some very bad news :
for those who are getting problems with the minicom serial0 mode u have to configurate the pi as followed in this site : Enable serial port on Raspberry Pi – Charles's Blog

i suggest decawave engineering team to modify the raspian image to be pre-configurated with serial on and spi on but with the right configuration of serial ( i mean disabling bluetooth option at the config file) .
once i double checked the configuration on the site now i have the minicom working … this is the good news.
But, the web manager isn’t working it only shiw the bridge node , no tag and no anchor !
so, many problems i am working on those issues more than a week now!
if all the configuration from PANID to every thing is correct why doesn’t work.
question in the /etc/dwm1001/dwm1001.config , if my panid is 0x394E then enc key must be enc_key = “333333339999999944444444EEEEEEEE” ? like the picture i guess i am correct already so why why it doesn’t work.??!
gggd

Hi Amhed,

The encryption key and the panId are not related. Encryption key can be set to encrypt UWB packets with AES. But currently you have disabled this option as per “enc_en=false”. I would recommend you to preserve this setting until you have a stable network.

Have you tried to run “LA” command on the bridge node (so on the minicom -D /dev/serial0) ?
Can you see your network anchors there ?

Thank you,
Yves