-
Notifications
You must be signed in to change notification settings - Fork 213
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
Connecting to AWS IotCore LNS #994
Comments
It seems the LMIC library is outputting on sub-band 2, even though sub-band 1 is specified in code. Not sure how to get the node to output using sub-band 1. I have done the following in the LMIC setup :
As well as the following in the platformio.ini:
|
Sorry you're having problems.
Best regards, |
Hi Terry, thanks for the response. Your comment 1 fixed the sub-band mismatch I was having. Your comment 2 makes sense (although I don't know how to implement that right now and will save that for another time. Defining the sub-bands explicitly now that they match seems to be okay for testing purposes) I am now getting a ping showing in the gateway logs. However the pings are few far between. Like 10-20 minutes between logs. Here is what the log looks like from the basic station: Looks to be the CRC is failing. and the TX power of the node is very low? (notes)
and for the LMIC to listen on SF8:
Here is the second ping i've gotten thus far:
|
UPDATE: Seems the gateway was picking up some other lora signal. Hence why the receive was weak, few and far between, and had a changing packet size. The node is sending a join accept (len = 23) every ten seconds. The gateway is not picking this up. I have also gotten rid of the sub-band 1 declaration in the code. At least I know the gateway does seem to pick up RF signals, leading me to think something is wrong with the node. |
I am trying to connect a LilyGo T-Beam to a Raspberry Pi running basic station on AWS IOT Core LNS. I have the basic station part working. Any help is very much appreciated. I am pretty stuck at the moment. Happy to provide any and all information if needed.
I am not sure if the T-beam (Node) running the MMCI library is working correctly.
Environment:
Here is some MCCI log output:
Here is the Router Config from basics station if it may be helpful:
I also have a support thread going on AWS IQ: https://repost.aws/questions/QUsqYcZCQURlq5xFqm9myXaA/aws-iot-lorawan-unable-to-connect-node-to-gateway
The text was updated successfully, but these errors were encountered: