LoRa : MTDotBox can join network but packets are not received
Home › Forums › Conduit: AEP Model › LoRa : MTDotBox can join network but packets are not received
Tagged: lora dotbox mtdotbox conduit
- This topic has 4 replies, 4 voices, and was last updated 8 years, 10 months ago by
Bryan Tran.
-
AuthorPosts
-
June 22, 2016 at 4:17 am #13480
Quentin
ParticipantHello,
I am running in some issues with my Conduit AEP (firmware 1.2.2, Lora Network Server 1.0.8) and my MTDotBox (firmware 2.0.0). The DotBox can join my Lora network but after that when I send messages from the DotBox nothing is received on the Conduit and ‘No Free Channel’ is displayed on the DotBox.
Also, if I check the ‘Public’ option on the Conduit GUI in the LoRa settings the DotBox can not even join the network (‘No Free Channel’ is also display).I am using ‘nc –udp –listen –local-port 1784’ to monitor what is passing through LoRa on the Conduit and all I can see when I select ‘LoRa Demo’ on the DotBox is the following:
admin@mtcdt:~# nc --udp --listen --local-port 1784
lora/00-80-00-00-00-00-b3-89/packet_recv {"chan":0,"codr":"4/5","data":"AKE9dxxE4+WUibMAAAAAgAAAFWDehzw=","datr":"SF12BW125","freq":868.10000000000002,"lsnr":9.1999999999999993,"modu":"LORA","rfch":0,"rssi":-41,"size":23,"stat":1,"time":"2016-06-22T08:57:12.357749Z","tmst":3295851500}
lora/00-80-00-00-00-00-b3-89/joined
lora/00-80-00-00-00-00-b3-89/packet_sent {"codr":"4/5","data":"IMAE/zSGR3VQpp+EDMT7DxWL3Sc2FgYAu0P69Rl1X1XW","datr":"SF12BW125","freq":868.10000000000002,"ipol":true,"modu":"LORA","ncrc":false,"powe":11,"rfch":0,"size":33,"tmst":3296851500}
Is there a log file I can check to help me troubleshoot this?
Also, I noticed in /var/config/lora/lora-network-server.conf this option:
"whitelist":{
"enabled":true,
"devices":[
]
}
Maybe this is causing the problem? If the whitelist is enable with an empty list of devices could it block all incoming data?
Any help would be much appreciated!
June 22, 2016 at 8:29 am #13484Bryan Tran
ModeratorHi Quentin,
There is a new firmware with a latest libmDot 1.0.8 version that I have attached it in your support case (5071851). Please, download and give it a try and see if it helps.
Thanks,
BT
June 24, 2016 at 5:05 am #13626Sylvain Delagrange
ParticipantThe new WH resolves the issue, thanks !
SylvainJune 24, 2016 at 10:59 am #13630Lawrence Griffiths
ParticipantBryan Tran, I seen the same issue (Conduit AEP (firmware 1.2.2 & MTDotBox firmware 2.0.0) then it started working. Bryan I’m about to send units out for a site survey. Should I Hold and put new firmware on Box??
June 24, 2016 at 11:20 am #13632Bryan Tran
ModeratorLawrence,
1. You could compile the source code yourself – https://developer.mbed.org/teams/MultiTech/code/MTDOT-BOX-EVB-Factory-Firmware/ – and then upload it to your mdot-BOX. You just want to make sure the following:
a. To compile it with the latest libmDot version 1.0.8. High light the libmDot folder on the left pannel and click on ‘Revision’ button, then select ‘revision 14’. Click ‘switch’ button.
b. Edit the following file to fix the issue with – at+gsdf that shows blank.
CmdGetSurveyDataFile.cpp:
————————-int32_t CmdGetSurveyDataFile::action(std::vector<std::string> args)
{
mDot::mdot_file file;
int buf_size = 512;
char buf[buf_size];
int read = 0; //BT – Edit it right here – Initialize it with a default value of 0
int read_size;file = _dot->openUserFile(file_name, mDot::FM_RDONLY);
if (file.fd < 0) {
setErrorMessage(“Failed to open file”);
return 1;
}
…c. Recompile and upload it to your device.
2. Create a support portal that I can attach a bin file that I have already compiled and you just need to upload it to your device.
Thanks,
BT
-
AuthorPosts
- You must be logged in to reply to this topic.