Did you update the apk?
OOps… Its fixed by R2 app. Thanks Kenneth.
For some reason the compiler is not understanding the the * as a wildcard.
As a workaround we did the following, and it worked for us:
In the ‘Project Explorer’ pane of SES, right click on the Solution and select ‘Options…’
In the Code/External Build section is the Link Command. You will need to edit a part in the middle of this.
Find the snippet that says:
and edit it to say:
Leaving all the rest of the command as it is.
Hope it helps,
Perfect! Works great, thank you @Ryan for the patch.
Now I’m up to the step of creating the hex file… the documentation is very windows-centric (.bat file in a utilities folder with some .exe’s there too).
Does anyone have directions for how to make a hex file under linux?
@Kenneth_Dwyer_DW, is my problem that the build process just isnt supported outside Windows, and that I should move to a windows machine to build my code? Since the earlier virtual box had ubuntu as the OS, I just assumed linux would be supported, but maybe that’s my problem. In any case, is there a plan to release an update with full linux support in the future?
it’s possible to configure the raspberry proxy-server-host over HTTPS?
In /etc/dwm1001/dwm1001-proxy.config it can only change the server_host and server_port.
I need to use mqtt over TLS with X.509 self-signed certificates.
see this post to understand a bit the data chain:
Have you tried to configure the DWM Daemon and DWM Proxy to use the MQTT over TLS ports?
Please see the configuration in files
TLS can be enabled in the Mosquitto Broker configuration file:
I have not tried that but it should work.
can you please share the link?
Are there plans to release the RPi Gateway code or at least documentation so that people can port gateway functionality to their own platforms?
Is it possible to customize the ‘mqtt_topic_prefix’ parameter?
If I go to change it, all requests on “topic uplink” work well with the new prefix. If I perform a downlink (i.e. downlink data iot) through the web interface, the data does not arrive and is not even logged in the proxy_log on the raspberry. It seems that the proxy daemon does not interpret topics other than “dwm/node/+/downlink/+” structure.
It’s possible? Is it possible to work around this problem?
thanks for the feedback. It’s a bug in the DWM Daemon.
The source code is not available yet but it might change (I do not know if and when).
yes some documentations or source codes would be really appreciated.
Is there a plan to open pans’s source code.
Is it possible to get distance from anchor with DWM1001 PANS Release 2?
I found a workaround to the problem. I configured the Mosquitto Bridge section which allows me to remap the topics as I want.
I have another question. In release 1 it was possible to have Proximity data (No RTLS) with a system with 1 anchor and 1 tag.
Is it possible to have this information over MQTT with release 2?
The range must be sent in the uplink data within the user-app. There is an example provided in the release package.
You may need to modify it a bit so it works only with 1 tag, 1 initiator, 1 gateway.
Thanks for the reply.
What example are you referring to?
Can you give me the name of the file?
It seems like there is no plan to do so?
I am facing the same problem. I have tried to remove ‘*’ from the command but still I get the same error. As soon as I build dwm_simple, it deletes the .o file and i get the error. Please help.
Bonjour Monsieur Yves,
J’aurais une question à vous poser, actuellement j’étudie les modules DWM1001-Dev, j’ai suivi le document constructeur “Firmware User Guide” et je suis bloquer à l’étape communication UART. J’ai actuellement trois modules et je souhaiterais obtenir les coordonnées sur un seul axe (axe x). Pouriez-vous m’aidez s’il vous plaît? Auriez-vous une adresse mail ?