-
Notifications
You must be signed in to change notification settings - Fork 19
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
USI_I-NUCLEO-LRWAN1 Does not answer to join accept #29
Comments
Hello, I am sorry for the late reply, regarding to the screen-shot, I can see data rate for the join-accept frame from the server is DR0 on RX2, but I am not sure if the default data rate for RX2 is DR0 or DR3, you can try to change the data rate for RX2 by the command below: AT+RX2DR=3 I want to know the fw version you are using for the test, can you please share me the fw version by the command below? thanks!! AT+VER |
Hello, After 2 weeks with everything unplugged. I did power on the gateway and the node. AT+RX2DR=3 did not change anything. FW Version is 1.0.1 4.0.1 SM42 1.1 |
Hi guys Also: There is currently a bug in the firmware (4.0.x) that it does not save the RX2DR with WDCT sometimes. I have not found a solution yet. Hopefully, they will provide us with a fix very soon, we have a production release awaiting and got modules with the new buggy firmware. Edit: There is even one more bug in the firmware as if you use AT+JOIN=1 you won't get a response if it failed. So you always have to poll by using AT+JSTA |
Couldn't we use a version that didn't have the problem? (looks like it's from 4.0.x) |
Hello yes, the module would not stop to transmit join request until succeed to join on the concentrator, and after firmware version 4.0.2 the module will report join status proactively. thanks!! |
I have the same problem. Did you find any solutions? |
On 2021-02-08 17:04, Jezek-David wrote:
I have the same problem. Did you find any solutions?
--
You are receiving this because you commented.
Reply to this email directly, view it on GitHub [1], or unsubscribe
[2].
Links:
------
[1]
#29 (comment)
[2]
https://github.com/notifications/unsubscribe-auth/ABFEDM5OFAPOUU7ZI2BVRNDS6A7UHANCNFSM4KT2BYYQ
unfortunately not, and worse, no support from the manufacturer, that is,
it is an expensive and useless kit for me so far
I keep looking, if I find something to inform you, I would be very
grateful if I could do the same
|
Near the same here, solution was to use something else....
Le jeu. 11 févr. 2021 à 12:04, reinaldoaf <notifications@github.com> a
écrit :
… On 2021-02-08 17:04, Jezek-David wrote:
> I have the same problem. Did you find any solutions?
>
> --
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub [1], or unsubscribe
> [2].
>
> Links:
> ------
> [1]
>
#29 (comment)
> [2]
>
https://github.com/notifications/unsubscribe-auth/ABFEDM5OFAPOUU7ZI2BVRNDS6A7UHANCNFSM4KT2BYYQ
unfortunately not, and worse, no support from the manufacturer, that is,
it is an expensive and useless kit for me so far
I keep looking, if I find something to inform you, I would be very
grateful if I could do the same
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#29 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACUD2AY7LZHPJ2OZQ5VUJN3S6O2TLANCNFSM4KT2BYYQ>
.
|
Hello,
I run the at_master example from I-NUCLEO-LRWAN2 eval pack.
I did update the firmaware to set my app id and app key using LoRa_SetAppID() and LoRa_SetKey().
It worked correctly. I'm collecting data through TTN.
Then I did reboot the device and from that point, the app is no more functionnal.
Using gateway logs from TTN. I can see that after a join request, the gateway sent a "Join Accept" frame. (see screenshot)
If I sniff the serial port for AT commands, I can see that the modem answers "OK" to the "at+join=1" but does not send the "+JoinAccepted" as I think it should. See logs below :
`
`
Do you have any idea of what may happen ?
Thanks
Julien
The text was updated successfully, but these errors were encountered: