-
Notifications
You must be signed in to change notification settings - Fork 405
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
RadioLib 6.4.1 LoRaWAN isseu #948
Comments
Your debug output appears incomplete, there should be much more before it actually fails with -1106. Also, please remove all (or most of) the SPI mess to keep logs readable and the page scrollable :) |
Maybe like that?
|
@jgromes, could you have a look? Still on mobile, haven't had time to look at the actual fix you added. |
There was an error in the data rate check, my fault. @nmaas87 I pushed a fix, could you try it out? |
Thanks @jgromes - trying it right now and getting back to you |
Yes, thanks a lot @jgromes / @StevenCellist - that fixed it :). |
@nmaas87 thanks for testing it out. Unfortuantely the bug pretty much breaks LoraWAN in 6.4.1, so we will need to release 6.4.2 patch ... |
Hopefully it's so fast after 6.4.1 that nobody notices / bothers :) and thanks you two!! |
hello, |
@altinem did you at least search for what the -4 error means? It's on this page: https://jgromes.github.io/RadioLib/group__status__codes.html, literally the first result I got when googling "radiolib error codes". In there, you will find that -4 is Also, please don't revive old threads that have been resolved and are rather obviously unrelated to your problem. If your problem persists, open a new Issue or Discussion and include all the necessary information, such as the code you are actually running. |
Describe the bug
Short feedback for you (@StevenCellist / @jgromes) and the PR #942 , I tried a STM32WL55 module with the latest 6.4.1 patch, as well as with 6.4.0 and 6.3.0 in EU868 state with the LoRaWAN reference example.
6.3.0 - works flawlessly
6.4.0 - node.restore() does not work, but initial joining/OTAA does work
6.4.1 - initial joining/OTAA does not work with reference to the region code / status / error code:
I have not tried other modules yet, but maybe there is a bigger issue here at hand?
Debug output below:
To Reproduce
Expected behavior
Starting connection to LoRaWAN as usual
Additional info (please complete):
The text was updated successfully, but these errors were encountered: