This may or may not be relevant, but LoRaWAN 1.0.1/1.0.2 did support DR0 for AU915 for join requests. This actually caused other issues with joining as the network server was responding to the join with an instruction to use DR2 which the end node (STM32-based but not RAKWireless) I was using at the time was rejecting.
If the LoRaWAN Network Server and the end node are not in complete agreement as to the regional parameters in use, this could cause the end node to ignore a JOIN ACCEPT message.
I could only get the device connected via ABP which bypassed the issue with the OEM firmware.
Problem was only solved when I started building firmware from ST reference source starting with LoRaWAN Spec 1.0.3 which solved the AU915 regional parameters issue.
I don’t want to seem stupid or lazy .
I found this repositories:
With seems to have the RUI application for RAK3172. Is there any “getting start” on this matter?
For example, being able to use VSCode to compile a version with AT commands and from there start with some small changes to the code.
If there is a link or thread here on the forum about this, I would appreciate it.
I am from Brazil too. I know the Everynet implementation, and if you take a look in the last LoRa Alliance Regional Parameters, you will not see what Everynet implementation: RP002-1.0.4 Regional Parameters .
I good questions is why they did this variant ?
If you take a look in some Brazilians vendors, as Khomp, you will see the explanation about LA915:
Blockquote
When in AU915, the time for RX1 and RX2 windows, they are 1 and 2 seconds and in LA915 the time for RX1 and RX2 windows they are 5 and 6 seconds.
This difference is reflected when performing Class A downlinks. LA915 is the standard
used by ATC (American Tower Company) in ABP mode in the Latin American region, for use in
OTAA mode does not require changing the region.
hi,
these messages
315s533:MAC txDone
320s370:RX_1 on freq 926300000 Hz at DR 10
320s566:IRQ_RX_TX_TIMEOUT
320s566:MAC rxTimeOut
321s382:RX_2 on freq 923300000 Hz at DR 8
321s595:IRQ_RX_TX_TIMEOUT
321s595:MAC rxTimeOut
@beegee
I have a rak3172 application that will need the stm32cube ide + la915
Did you test the la915 on stm32cube too, on rak3172 ?
If yes, can I use the endnode stm32cube example on rak3172 ? Need to change middleware ?
Thanks
LA915 was added to our RUI3, I do not know whether STM32Cube example supports it.
I do not know whether you have to change anything, I am not using STM32CubeIDE nor the STM32 SDK.
Brazilian team. rak unconfirmed uplink is working on LA915 ?
For me, it´s only working using confirmed uplink.
With unconfirmed uplink, the data not reaches my EVERYNET, but with confirmed uplink, the data reachs the eveynet.
Someone having the same problem ?
On stm32cube to RAK3172 i got success on unconfirmed uplink and confirmed.