Why does AT+JOIN=1:0:8:8 always times out at least once. Eventually the 3172 will join the network usually on the second attempt. How can I get the device to have a better chance of joining on the first attempt?
AT+JOIN=1:0:8:8
<< OK
<< +EVT:JOIN_FAILED_RX_TIMEOUT
<< +EVT:JOINED
Difficult to say anything without seeing the logs from the gateway and LNS.
What LoRaWAN region, what LNS, what Gateway are you using?
@beegee - thanks again
LoRaWAN network region is US915, I am using a RAK7268V2 and the gateway an LoRaWAN server.
Here is a snippet of the log that shows with the RAK3172 connected. The log is rather verbose. Is there something in particular that I can send?
Thu Mar 12 01:41:35 2026 daemon.info nwkSrv[4864]: nsDeduplicateJoinFrameTimerHandler: Permitted to join, Join-DevNonce:245c
Thu Mar 12 01:41:35 2026 daemon.info nwkSrv[4864]: Mote ac1f09fffe1396ee Joined addr 02f121e7
It would be interesting to see the packet logs in the gateway.
This would show if the LNS answers the first join request or ignores it.
What RUI3 version are you using on the RAK3172?
Are you using AT commands from a host MCU or terminal?
On the RAK3172, enable additional debug output with AT+DEBUG=1, it will show more information.
Hi @beegee ! Again, thanks for all your help. Very much appreciated!
I am using a RAK7268V2 as the gateway and LoRaWAN server. The logging is quite verbose. Is there a way to filter the log to show only pertinent items to help debug the join command?
What RUI3 version are you using on the RAK3172?
RUI_4.0.6_RAK3172-E
Are you using AT commands from a host MCU or terminal?
Actually, both.
On the RAK3172, enable additional debug output with AT+DEBUG=1, it will show more information.
I did not realize this was a supported command. Thanks for letting me know. Below is the output, other than ChannelsDatarate:0 I am not sure how much insight this provides. Any feedback?
'>> AT+JOIN=1:0:8:8
<< OK
<< +EVT:JOIN_FAILED_RX_TIMEOUT
<< Frequency:902300000
<< Rx1Frequency:902500000
<< RxCFrequency:923300000
<< RxC Datarate:8
<< ChannelsDatarate:0
<< AdrAckCounter:0
<< ChannelsTxPower:0
<< +EVT:JOINED
<< Frequency:902300000
<< Rx1Frequency:902500000
<< RxCFrequency:923300000
<< RxC Datarate:8
<< ChannelsDatarate:2
<< AdrAckCounter:0
<< ChannelsTxPower:0
Thanks again!!
Use the packet logger, it only shows LoRaWAN packets.I don’t think the syslog will be helpful.
Can you update to latest version V4.2.3 please. Many bugs have been fixed since 4.0.6
Thanks for using the DEBUG output.
Actually this seems to be one of the problems that are fixed in newer RUi3 versions.
There is only one join request, but two +EVT: responses, the first one saying failed, the second one saying success.
Again, this might be related to RUI3 V4.0.6 (quite old actually) and might be fixed already with RUI3 V4.2.3