-
Notifications
You must be signed in to change notification settings - Fork 212
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The "Margin" field of the "DevStatusAns" command payload is wrongly encoded #130
Comments
I take it that this is not "The Things Network" as the network server? Definitely agree that this is a problem, but I need more context, as I've not seen this in my testing. (Need to figure out what additional test coverage is needed.) |
Yes, sorry for not being clear enough. I'm using the LoRa Server software stack in a development environment. |
OK, cool! Another test case.... Interesting to think about how one could do hardware-in-the-loop testing with this. You will probably find that this version of the LMIC stack doesn't do a great job with MAC command responses. See issue #87 for details. TL;DR: it doesn't built the response as it's parsing the request, so things can go back out of order (or not at all). |
Fix #130: Fix coding of the "Margin" field of the "DevStatusAns" MAC command payload
Tested with Arudino Mega 2560 connected to RFM95 module.
Add the following two lines to
project_config/lmic_project_config.h
:After running a slightly modified version of the
ttn-otaa
sketch, this is the output on the Serial.Basically we can see that the Node is able to join the Lora network (
593337: EV_JOINED
), but fails to send the first uplink packet and keeps retrying.Logging on the AWG ubuntu machine and checking the logs with
journalctl -f -u loraserver
I noticed the following lines appearing right after the node sends the "Packet queued" message:The text was updated successfully, but these errors were encountered: