For the join issue, you may want to check the events in Chirpstack / TTN.
It may due to other issues (incorrect keys, invalid DevNonce…)
Hi @IoTThinks ,
I am not that close to a gateway, from time to time the first JOIN fails… it works in the next try.
1 Like
Hi @beegee ,
anything new on this topic?
I just saw now a new topic using the same configuration (RAK3172 and LA915 region), complaining about possible crash.
Thank you.
Only suggestion I have is to go back to RUI3 V4.1.1
LA915 is very difficult, we do not have gateways that support these region, so we cannot really test much.
Hi @beegee , just to inform you.
About a week running the previous version: RUI3 V4.1.1, no issues.
I will follow the next releases, looking for a fix in the V4.2.0.
Hi @beegee ,
I see there is a new firmaware release, 4.2.1. But, on the release notes I could not find anything related to the LA915 issue.
Please, can you confirm this was really not treated in these update?
I guess the problem is only in the LA915 region…
In case I set AU915 and change the RX delays, and may be other parameters… would that be the same as LA915? Please, give me some indication on what to do.
Thank you,
Iaran
Correct, we did not investigate into the LA915 problems.
I do not know how to change AU195 to work as LA915.
The whole LA915 support was implemented by supporters, not by us.
@beegee ,
What can we do to have an official review/release for the LA915?
Otherwise users of the public network in Brazil will have to keep using the old FW 4.1.1.
Here is the LA915 content:
https://ns.docs.everynet.io/channel_plans/LA915A.html
Or, at least point where in the code this configuration is implemented.
Thank you.
We cannot test LA915, we do not have gateways or LoRaWAN server that supports it.
LA915 is a unofficial LoRaWAN region only supported by Everynet (afaik).
RUI3 is open source and its code is published in our Github repo ==> GitHub - RAKWireless/RAK-STM32-RUI: RUI3 BSP for RAK3172 modules
Unfortunatelly I do not have the knowledge of your system to perform this kind of debug.
I believe the issue should be simple, since it is working on the FW 4.1.1. Maybe some parametrization conflict after the introduction of the stack 1.0.4.
Please, do you have the contacts of this “supporters” who implemented the LA915?
Not sure if I remember, it was in one of these posts:
I tested in Brazil the LA915…but…with STM32LoRaWAN and STM32CubeIDE…
I had to change two files…la915.h and la915.c
I spent 9 weeks to make it work.
I can sent you those files, if you want…
Hi @tcpipchip (Olá Miguel),
first of all thanks for the support. Sure, I would like to receive your modified files. (www.gadotti.eng.br)
I am working in a new board and my intention was to use the RUI3 firmware and follow the oficial releases from Rak Wireless. But, after FW 4.1.1, I am facing a severe crash. Unfortunatelly the LA915 implementation was not further maintained.
I will take a look on the STM32LoRaWAN option as well.
I read in other module documentation about selecting AU915 and just change the RX delays, this would be the LA915. As I can see, it is not that simples, right?
Thanks!
The Tecsus team assisted the RAKWireless team in including LA915 in the RUI. We followed Everynet’s specifications (LA915 · Everynet Network Server).
Our system has been working well with RUI versions 4.2.0 and 4.2.1. Occasionally, we encounter minor issues with downlinks, but nothing critical.
Our company has been using the LoRaWAN network with the RAK3172 module on the LA915 plan in several cities, including São Paulo, São José dos Campos, Campinas, and Rio de Janeiro, and we haven’t encountered any issues so far
Thanks,
Diogo
Hello @diogobranquinho
Can you create a merge request with your changes on RAK-STM32-RUI
We will be more than happy to merge it.
Hi @beegee,
Just to clarify: we didn’t make any code changes ourselves. The RAKWireless team has already included LA915 support in the official RUI firmware. We’re currently using it with the RAK3172 module and RUI versions 4.2.0 and 4.2.1, and it’s working as expected.
So there’s nothing we need to merge — we’re simply using the existing support already available in the latest RUI version.
Best regards,
Diogo
Interesting, so it works for you. But others report problems with LA915.
Wondering why. But again, we still don’t have any LA915 environment for testing.
Setting up a gateway would be no problem, but I can’t find a LoRaWAN server that supports LA915 (beside of Everynet, which is not free to use).
Hi @beegee
Most of the issues were actually opened by our team. There was a misunderstanding due to the fact that both LA915 and AU915 are technically supported by networks in Brazil, which sometimes caused commissioning errors. In June 2024, Everynet Brazil published a guideline called “Política de Dispositivos - Conformidade Mandatória” (https://iot-labs.io/wp-content/uploads/2024/07/Politica-de-Dispositivos-Conformidade-Mandatoria.pdf), which clearly directed everyone to use LA915 correctly. Since then, we haven’t had any further issues.
There are still a few minor issues related to downlink reception failures, but these are directly tied to coverage and device RX sensitivity — not related to the LA915 implementation itself.
Don’t worry about not being able to test LA915 in the field — we’ve tested it extensively, and it works. We have dozens of devices deployed across different cities in Brazil, running perfectly.
If other developers are struggling to implement their code, the root cause is likely elsewhere.
We’re happy to support our fellow developers in Brazil with tips or benchmarks if needed.
Best regards,
Diogo Branquinho
1 Like