forlesswera.blogg.se

Due to the reason above the dwm-daemon is not running (i.e.The reason can be either:Ī) The connector is not correctly soldered -> Please recheck the soldering and connection of the module to the Raspberry board.ī) The Device Tree (DT) for some reason is not correct -> Have you done any changes in the DT or any changes in the Raspberry image? Please send output of this command The Kernel Module cannot communicate reliably with the DWM1001-DEV via SPI.The dmesg outputs show I think the main issue: They will increment everytime the data is received correctly from the AN/TN). The firmware seems to work all OK and it can receive the Location and IoT from the Anchors/Tags (see counters fw_ul_loc_ok, fw_ul_iot_ok, bh_ul_ok in the stg outputs. Question in the /etc/dwm1001/nfig, 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.?! If all the configuration from PANID to every thing is correct why doesn’t work. So, many problems i am working on those issues more than a week now! Once i double checked the configuration on the site now i have the minicom working … this is the good news.īut, the web manager isn’t working it only shiw the bridge node, no tag and no anchor !

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). Okay i have some good news and then i have some very bad news :įor 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