sample Node.js application
Home › Forums › Conduit: mLinux Model › sample Node.js application
- This topic has 10 replies, 2 voices, and was last updated 9 years, 5 months ago by
Brandon Bayer.
-
AuthorPosts
-
October 2, 2015 at 8:30 am #9456
James Coleman
ParticipantHello,
I am interesting in installing the sample Node.js application so I can send LoRA packets from my Conduit to my LoRA mDot and vice versa. I am not clear on the procedure for installing the Node.js application. Would you please provide instructions on how to do this.
Also I am using the following mosquito command to view packets received by the Conduit: # mosquitto_sub -t lora/+/up
Question that I have is when I transmit at+send=hello world from mDot LoRA to Conduit, should I see this received packet on my Conduit ssh console? I don’t see anything on the Conduit ssh console when I send the packet from mDot LoRA to Conduit.Thanks,
James
October 2, 2015 at 9:02 am #9458Brandon Bayer
BlockedJames,
I added instructions to this page for how to install and run the sample app.
On using mosquitto to receive packets, yes, you should see received packets while
mosquitto_sub -t lora/+/up
is running. For debugging, run this command to look at the log:tail -f /var/log/lora-network-server.log
If lora communication isn’t working for you, it’s possible you have a version mismatch. This page lists required versions for compatibility.
-Brandon
-
This reply was modified 9 years, 6 months ago by
Brandon Bayer.
October 2, 2015 at 9:40 am #9463James Coleman
ParticipantBrandon,
Thanks for the information.
I executed the command: tail -f /var/log/lora-network-server.log in
the Conduit ssh command window.I then executed the command below in the mDoT LoRA command shell to send the packe “hello world” to the Conduit.
at+send=hello world
OK
The following information was displayed in Conduit ssh shell. It appears that the Conduit is receiving the packet from the mDoT LoRA based on information provided below. I do so at end of the output shown below that I am getting
Recv’D Frame failed CRC check
Why am I getting this failure message??My mDot LoRA has the following firmware and libm software versions installed.
ati
MultiTech mDot
Firmware: 0.1.4
Library : 0.0.9The Conduit has the following firmware installed.
root@mtcdt:/# opkg list | grep lora
lora-network-server – 0.0.8-r0.0
lora-packet-forwarder – 1.4.1-r8.16
lora-query – 0.0.1-r0.0The Conduit has the following mlinux version installed.
root@mtcdt:/# cat /etc/mlinux-version
mLinux 3.1.0
Built from branch: (detachedfrom4fd069b)
Revision: 4fd069b97a2354995920b52f731d661f0bacb39aBased on this version information, should mosquitto be working properly?
Are these software versions compatible?10:22:7:16|INFO| Transmit message 179 bytes
10:22:37:901|INFO| Parsing 1 rx packets
10:22:37:902|WARNING| Recv’d frame failed CRC check
10:22:6:112|INFO| Addr: 00:00:00:01 MIC Check: passed
10:22:6:125|INFO| Packet accepted from Node 00:00:00:01 GW 00:80:00:00:00:00:9b:cc (127.0.0.1) Seq# 5 ADR disabled SF9BW125
10:22:6:125|INFO| Schedule TX Time on air: 150 ms
10:22:6:127|INFO| SeqNo: beec2930 PrevSeqNo: 00000005 Duplicate: yes10:22:6:127|INFO| Addr: 00:00:00:01 MIC Check: passed
10:22:6:128|INFO| Duplicate Packet accepted from Node 00:00:00:01 GW 00:80:00:00:00:00:9b:cc (127.0.0.1) Seq# 5 ADR disabled SF9BW125
10:22:6:128|INFO| Schedule TX Time on air: 150 ms
10:22:6:128|INFO| Using RX window 2 : 00:00:00:01
10:22:7:10|INFO| Frame transmitted to 00:00:00:01 via GW (00:80:00:00:00:00:9b:cc Chan LC5 127.0.0.1:49940) Seq# 6
10:22:7:16|INFO| Transmit message 179 bytes
10:22:37:901|INFO| Parsing 1 rx packets
10:22:37:902|WARNING| Recv’d frame failed CRC checkOctober 2, 2015 at 9:45 am #9464James Coleman
ParticipantBrandon,
I am now seeing the packets that I send from the mDoT LoRA to the Conduit when using the mosquitto utility. Information that I am receiving is shown below.
root@mtcdt:/# mosquitto_sub -t lora/+/up
{“chan”:2,”cls”:0,”codr”:”4/5″,”data”:”aGVsbG8gd29ybGQ=”,”datr”:”SF9BW125″,”freq”:”912.3″,”lsnr”:”14″,”modu”:”LORA”,”rfch”:0,”rssi”:-21,”seqn”:6,”size”:16,”timestamp”:”2015-10-02T10:42:24Z”,”tmst”:1378025308}{“chan”:2,”cls”:0,”codr”:”4/5″,”data”:”amFtZXMgY29sZW1hbg==”,”datr”:”SF9BW125″,”freq”:”912.3″,”lsnr”:”-0.2″,”modu”:”LORA”,”rfch”:0,”rssi”:-75,”seqn”:7,”size”:20,”timestamp”:”2015-10-02T10:42:55Z”,”tmst”:1408365068}
{“chan”:7,”cls”:0,”codr”:”4/5″,”data”:”ZGVib3JhaCBjb2xlbWFu”,”datr”:”SF9BW125″,”freq”:”913.3″,”lsnr”:”13″,”modu”:”LORA”,”rfch”:1,”rssi”:-23,”seqn”:8,”size”:20,”timestamp”:”2015-10-02T10:43:33Z”,”tmst”:1447168164}
October 2, 2015 at 10:20 am #9465Brandon Bayer
BlockedJames,
That looks good!
-Brandon
October 2, 2015 at 10:34 am #9466James Coleman
ParticipantBrandon,
I need some clarification on sending packets from the Conduit to the mDot LoRA.
When I issue the following Conduit command (root@mtcdt:/home# mosquitto_pub -t lora/00:80:00:00:00:00:9c:c7/down -m ‘{ “data”:”aGVsbG8gd29ybGQ=” }’ to send data to the mDot LoRA, what data should I see on the mDot LoRA console and what do I do to see the data sent from Conduit?After I send a packet from mDot LoRA to Conduit, I have been entering the command at+recv on mDot LoRA platform and I receive the following information.
at+recv
hello worldOK
Is “hello world” the data that is being transmitted from Conduit to mDot LoRA?
Thanks,
James
October 2, 2015 at 10:48 am #9467Brandon Bayer
BlockedJames,
As the below screenshot from this page shows, by default, the AT+SEND command will print out any received data. As mentioned in the documentation, the mDot must transmit 1 packet in order to receive 1 packet. The AT+RECV command will simply print out the data from the last received packet (from when you last issued AT+SEND).
And yes, in that case “hello world” was data transmitted from the Conduit.
-Brandon
October 3, 2015 at 12:55 pm #9471James Coleman
ParticipantBrandon,
I changed the ip address and gateway on my Conduit so I could connect to my work network through a wireless Linksys router. I am able to connect to the Conduit via ssh and ping the Conduit across my network. Also able to send data packet from the LoRA mdot to the Conduit.
I loaded the sample Node.js application. Now I don’t see a data packet coming back from Conduit to LoRA mdot.
Any idea why the Node.js application is not working across my work network?
Thanks,
James
October 5, 2015 at 11:08 am #9490Brandon Bayer
BlockedJames,
No, just changing the ethernet configuration shouldn’t have any affect on the LoRa network.
-Brandon
October 6, 2015 at 6:03 pm #9510James Coleman
ParticipantBrandon,
I am still having issues with not being able to receive data from Conduit to mDot LoRA. I am running the lora-sample-app.js on the Conduit.
What program should I be running on the mDot LoRA?
No data is coming back. I must be missing something.
Thanks,
James
October 7, 2015 at 7:12 am #9516Brandon Bayer
BlockedJames,
Since you are still having trouble, could you open a support case for this? We’ll be able to support you better that way.
-Brandon
-
This reply was modified 9 years, 6 months ago by
-
AuthorPosts
- You must be logged in to reply to this topic.