mDot Send msg doesn't work

[Alberto Lucchesi]

Hi,

I have a mDot and a multiconnect Conduit MTCDT-H5 and I tried to send a “hello” from mDot to multiconnect following the example and the video tutorial, but even if all seems to be ok I do not see the message in the Node-Red Debug window.
I have MTCDT-H5 firmware 1.4.1.

Here are the pics of:

– multiconnect LoRa Configuration
https://cloud.caen.it/public.php?service=files&t=b76bd957659f2d083f9358214a21e9b1

– Node-Red configuration
https://cloud.caen.it/public.php?service=files&t=6592a1735464334649b1154b9fffe18d

– mDot console
https://cloud.caen.it/public.php?service=files&t=b4d518ba10b88d8256edd05cfd440b12

I tried also to se the at+ACK=1, in that case when I send at+send=hello I received “Operation Timed Out – ACK not received”.

What I’m doing wrong?

Thanks
Alberto

[Steve Kovarik]

Hello Alberto

You configuration looks OK. If you log into the Conduit and select “status & logs”
then “statistics” and then select the “LoRa” tab, do you see a device show up
under Node Address? Do you see any Pkts-up or Pkts-down.
If you issue ati to the mDot, what is the firmware level?

[Alberto Lucchesi]

Hello,

here is the screenshot of the logs:
https://cloud.caen.it/public.php?service=files&t=f35a6baacdc152df8adc891dd9f772dc

taken after at+join command.
after the at+send=hello command (that returns OK) nothing change in the log.

Here are the Mdot information:
MultiTech mDot
Firmware: 0.1.4
Library : 0.0.9

Thanks
Alberto

[Alberto Lucchesi]

Hello,

an update, I upgraded the mDot firmware following the instructions, now the firmware is:
MultiTech mDot
Firmware: 2.0.16-1-mbed141
Library : 2.0.17-1-mbed141

doing the same tests now the logs are different:

here the screenshot:
https://cloud.caen.it/public.php?service=files&t=7f7392dc12866c145eafefccefe9210a

with new firmware, adding at+ACK=1 then sending a msg I received OK instead of error as with the original firmware, but in any case I do not receive msg in debug window of MTCDT-H5.

[Steve Kovarik]

Hi Alberto

Thanks for upgrading your mDot firmware to the latest.
It now appears the Conduit is receiving packets from the mDot.
If you ssh into the Conduit Ethernet port and login with admin/admin
and you can verify the Conduit is receiving packets using MQTT as shown at
this link http://www.multitech.net/developer/software/lora/conduit-mlinux-lora-communication/
The “data” in the received packet is in a Base64 format so you would need to
convert it back to ASCII http://www.hcidata.info/base64.htm

Regarding Node-Red, try deleting your flow, “Deploy” it, reboot the Conduit
then try re-creating the flow with a LoRa-input node, and debug-output node than “Deploy” and retest.

[Alberto Lucchesi]

Hello,

something seems to work, using the command:
” nc –udp –listen –local-port 1784″, I can see the data from the mDot and converting from Base64 format to Ascii I verify the message is right.
If I use the command:
” mosquitto_sub -t lora/+/+ -v” I do not recevi the message, nothing happens on conduit side while from mDot side the outpur is exactly as the previous command (so it seems message is sent”.
Why the first command works and the second not?
I also tried to send a message back to mDot (the echo if the msg) follwing the instruction on the link you gave me, using the Sample Node.js App.
Also with this app in the conduit I don’t see msg arrived and also in mDot I do not see the echo…

Best Regards,
Alberto

[Author]

Posts