RAK3172: +EVT:JOIN_FAILED_TX_TIMEOUT

Hi Team,

Greetings and Good day, trust you are doing well.

I have recently purchased my 2nd batch of 40 pcs RAK3172 from the store. Below the details of the RAK3172.

image

each time i am trying to connect to my ChirpStack i am getting the below error, as such i am not able to join the ChirpStack.

i dont know why this is happening, as my PCB is working fine with the 1st batch of RAK3172 ordered earlier and the same PCB is used with the 2nd batch of RAK3172 modules (i also tested the modules with the Custom PCB as well without success). I am still using the same custom code on RUI3 arduino IDE on the custom PCB.

see the setting in my IDE

On Arduino IDE: *Additional Board Manager URLS:
*

https://raw.githubusercontent.com/RAKWireless/RAKwireless-Arduino-BSP-Index/main/package_rakwireless.com_rui_index.json

I really dont know why this is happening, can someone please shed some light. or if ever i missed something?.

many thanks for your help,
Best Regards,

The modules you bought are the standard RAK3172 without TCXO.

Your code is compiled for the RAK3172-T with TCXO.

That is the reason. You need to compile your code for WisDuo RAK3172 Evaluation Board and NOT for WisDuo RAK3172-T Board

\

Hi Bernd,

Thanks for your swift reponse. I agree with you, just now i change the board to WisDuo RAK3172 Evaluation Board. i tried the same without success.

image

infact correct me if i am wrong. i used the Wis ToolBox and triggered the following AT commands on a bareminim RAK3172 chip but it is still not joining. i believed using the below AT commands that should connect to the network right? (without arduino ide)

i dont know why

many thanks for your help,
Best Regards,

The commands are correct, but did you set the correct LoRaWAN band (region) and made sure the devices are registered correct in your LNS?

You are using RUI3 V4.1.0, that is using LoRaWAN stack version 1.0.3, is this the same LoRaWAN version you setup in Chirpstack?

1 Like

thank you soo much Bernd,

Got it - my bad, you are are absolutely right, see below was the issue. i have change it to 1.0.4, it is working perfectly.

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.