I managed to Upgrade firmware version from 2.0.3.0 => RAK811 Version:3.0.0.3.H successfully (I got RAK811 V1.2).
However, I got two requests:
Is there a new AT Command guide becuase I see some of the commands changed and I need to update my Arduino code accordingly? (Example: lora. is added to some and at+join=otaa is changed to at+join simply).
How to change the baud rate since it is now in 15200 after flashing the new firmware?
Thanks for helping out.
Best regards,
Zabeel (Cool_GuY)
Thanks @Fomi@Hobo for the information. I will try it this afternoon after work. However, 1 more question, to change uart baud rate, we use the previous used at command since in the new table there is no baud change command?
Hello,
I upgraded the firmware to the latest version 3.0.0.4 but when trying the command >>at+uart=9600, X, X, X it gives an error āThe AT Command is invalidā.
Please help with the AT command.
Thanks & Best regards,
Zabeel
Hi, I had the same issue with baud rate, but I managed to connect to ttn after following quick start guide. However, Iāve not managed to make RAK811 work with Arduino- could you kindly share your approach on this.
Thanks
Kimogol
Using wisnode v1.2 and new FW version 3.0.0.4.H managed to change baud rate to 9600
However, AT command: āat+set_config=lora:app_key:ā can not be set at 9600
It does work at 115200 though.
Also āAT+joinā does not work at any of the baud rates. Is it replaced by something else to start to join a network?
Thank you.
Shay
This is very strange, I was playing with a RAK811 yesterday and at+join seemed to work fine. Can you try to enter the authentication parameters and perform a hardware reset after, it should star the join procedure automatically.
Thank you Vladislav for addressing this.
Did as you suggested.
Reply to āat+sendā is āparameter not foundā.
After HW reset getting following, copy-pasted below.
I am guessing the āparameter not foundā in last line is because of the at+join command not being accepted.
Note that I might have wrong authentication parameters. They are still not verified and I have not been able to connect yet to private lora network (not ttn).
" Selected LoRaWAN 1.0.2 Region: US915
Initialization OK,AT Uart work mode:normal mode, Current work_mode:LoRaWAN, join_mode:OTAA, Class: A
Parameter not found. "
Reply to āat+sendā is āparameter not foundā. I think you misunderstand the concept.
You need to configure the device to connect first, you canāt be sending data frames before this is done.
Parameter not found. "
This simply means that when the device tries to initiate the OTAA procedure, there arenāt valid:
dev_eui (Device EUI)
app_eui (Application EUI)
app_key (Application Key)
Those above need to be inserted with the commands below as per the values you have configured in the LoRa Server you are using in the application/device you have input there. Use the commands below, where XX is the values for your LoRa Server.
Thank you for your replies. I will set the correct dev_eui, app_eui and app_key and then try again. I must have been using incorrect values for these before.
Best regards,
Shay
Can you please confirm this:
Using Wisnode v1.2 and FW version 3.0.0.4.H can change baud rate to 9600 as instructed (successfully).
However, AT command: āat+set_config=lora:app_key:ā can not be set at 9600 baud rate.
It works at 115200 but not at 9600.
Thank you.