I am using a RAK3172-T board (with TCXO). When I send AT+VER?, the reply is:
RUI_4.0.6_RAK3172-T
I have two doubts:
On your website, I only see firmware for RAK3172-E. If I flash RUI_4.2.1_RAK3172-E on my RAK3172-T board, will it work properly? Or is there a separate firmware for the -T version?
From the factory, my new RAK3172-T board already has DevEUI, AppEUI, and AppKey stored. Can I directly use these values for my production deployment with TTN, or is it recommended to generate new ones in TTN?
Thank you for your support. I have a couple of clarifications regarding the RAK3172 (with TCXO):
From the factory, the module comes with DevEUI, AppEUI (JoinEUI), and AppKey already provisioned. Can we directly use these factory values for connecting to TTN/LoRaWAN and also for our company production, or do we need to generate new ones in the TTN console?
If I perform a full chip erase and then re-flash the firmware, the AT command version changes (for example, default shows V1.5.11). Is version 1.5.11 sufficient for LoRaWAN operation, or do you recommend upgrading to the latest firmware release?
DevEUI is a unique ID, created with our LoRa Alliance manufacture number, you can use it. AppEUI is the same for all RAK3172 and AppKey is generated from the DevEUI and AppEUI, you can use them as well as they are provided.
AT command version is irrelevant, LoRaWAN works with all versions.
The important version is the RUI3 version, the latest is RUI3 V4.2.2.
There is 3 files has same name with RUI_4.2.2_RAK3172-T,RUI_4.2.2_RAK3172-T_bl,RUI_4.2.2_RAK3172-T_final. which one is final?
RUI_4.2.2_RAK3172-T_final this one is final?
Same for RUI_4.2.2_RAK3172-E, RUI_4.2.2_RAK3172-E_bl, RUI_4.2.2_RAK3172-E_final. which one is final?
RUI_4.2.2_RAK3172-E_final?
Thank you so much for the great support. I have one more doubt regarding the AppEUI.
As @beegee mentioned, all RAK3172 modules use the same AppEUI. However, when I compared a RAK3172-E and a RAK3172-T, I noticed a slight difference.
Can you please confirm:
Is the AppEUI always fixed and the same for all modules?
Or does it change based on manufacturing batch, for example every few months or yearly?
This will help us to understand whether the difference I saw is expected.
APPEUI is usually derived from your LNS (LoRaWAN Network Server). Although there are devices in the market (those plug-and-play with fixed APPEUI), for modules like RAK3172, you can configure it whatever value that will fit on your LNS.
Hi Carlrowan,
I am going to send data to a single application under TTN thru the gateway (LoraWan). The data will come from at least 10 RAK3172-T modules with sensors through a gateway. So If same appeui means, it will be ok to register and Working.
When I checked 3 modules of the same type, all of them had the same default APPEUI from your factory settings.
As Beegee mentioned, all modules ship with the same APPEUI, so I planned to use that for bulk registration in TTN without generating a new one for each device.
Anyway, I already have a checkpoint in my testing process. If any conflicts occur, I will overwrite the module with my application’s default APPEUI and proceed with bulk registration.
For my understanding only i am asking you about that appeui will update or will not update frequently in your factory?
The APPEUI is fixed for now but I cannot guarantee that the APPEUI will not change in the future from our end. I can say this because there is no general rule when it comes to APPEUI.
Therefore it is advisable that you create a process that is not dependent on one APPEUI for it to be future proof.
Nevertheless, if you proceed as you plan, you can still use the current APPEUI on our modules which is fixed and same depending on the region and specific module.
For example, RAK3172’s APPEUI on EU868 is AC1F09FFF8683172. You can easily spot 868 and 3172.
During production, the new RAK3172 modules already come with AT firmware (sometimes 4.2.2, sometimes older) from your factory.
Before uploading my Arduino sketch (sensor reading + LoRaWAN uplink), do I need to re-flash every module with the latest AT firmware (RAK3172-E_latest_final.hex 4.2.2) ?
Or can I directly upload my Arduino sketch regardless of the existing AT firmware version?
For example, if the version is for different variants of 4.2.x, it is unlikely that there are major updates. But if it goes to 4.3.x or 5.x.x, then you have to check first on the release notes if there are breaking changes.
