RAK7200 OTAA - join failed

Issue: when attempting to join ttn network, getting a fail. at+join results OTAA Join start OK, then join retry counts to 5, then fails.

I followed the doc on rakwireless. after two attemps I followed the docs on ttn. after 4 attempts, I tried with a different firmware, both on 3.1.0.12 and 3.1.0.13 is the same. ttn console does not show anything. Changed region to AU915 and back to EU868, no improvement. Changed to lora class B and C, same, join failed, no connection on ttn, blank console. a gateway is 300m away.

On 3.1.0.13 I noticed that when attempting to input at+set_config=lora:work_mode:0, AT format error:80 appears, but I am not sure anymore if it was when setting the work mode, or after setting work mode 0 and running device:status

Details:

at+version
OK3.1.0.12

at+get_config=device:status
OK.


===============Device Status List================
Board Core: S76G_B
MCU: STM32L073RZ
LoRa chip: SX1276

Battery Voltage = 3.836 V
Support Gps:true
gps_timeout: 100s
gps_format:standard LPP format
No signal with Satellite.

MPU9250 sensor:
Acceleration(g) of X,Y,Z:
0.98,0.26,0.06
Gyro(degress/s) of X,Y,Z:
2.21,0.06,0.06
Magnetometer(uT) of X,Y,Z:
51.60,-69.30,-32.70

===================List End======================


at+get_config=lora:status
OK Work Mode: LoRaWAN
Region: EU868
Send_interval: 600s
Auto send status: false.
Join_mode: OTAA
DevEui: 00DC9BB91BD52902
AppEui: 70B3D57ED002DF32
AppKey: C2F8E302A071017314BACC6F7A407819
Class: A
Joined Network:false
IsConfirm: false
AdrEnable: true
EnableRepeaterSupport: false
RX2_CHANNEL_FREQUENCY: 869525000, RX2_CHANNEL_DR:0
RX_WINDOW_DURATION: 3000ms
RECEIVE_DELAY_1: 1000ms
RECEIVE_DELAY_2: 2000ms
JOIN_ACCEPT_DELAY_1: 5000ms
JOIN_ACCEPT_DELAY_2: 6000ms
Current Datarate: 0
Primeval Datarate: 5
ChannelsTxPower: 0
UpLinkCounter: 0
DownLinkCounter: 0

at+join
OTAA:
DevEui:00DC9BB91BD52902
AppEui:70B3D57ED002DF32
AppKey:C2F8E302A071017314BACC6F7A407819
OTAA Join Start…
OK
[LoRa]:Join retry Cnt:1
[LoRa]:Join retry Cnt:2
[LoRa]:Join retry Cnt:3
[LoRa]:Join retry Cnt:4
[LoRa]:Join retry Cnt:5
[LoRa]:Joined Failed!

Full log after switching to 3.1.0.11:

at+version
OK3.1.0.11

at+set_config=lora:join_mode:0
join_mode:OTAA
OK

at+set_config=lora:class:0
Class:A
OK

at+set_config=lora:region:EU868
No switch region.Current region:EU868
OK

at+set_config=lora:dev_eui:00DC9BB91BD52902
OK

at+set_config=lora:app_eui:70B3D57ED002DF32
OK

at+set_config=lora:app_key:C2F8E302A071017314BACC6F7A407819
OK

at+join
OTAA:
DevEui:00DC9BB91BD52902
AppEui:70B3D57ED002DF32
AppKey:C2F8E302A071017314BACC6F7A407819
OTAA Join Start…
OK
Configuration OK!
lorasend_interval: 600s
Table magic error! base_addr:0x802e200
MPU9250 Init OK
GPS Init OK

Selected LoRaWAN 1.0.2 Region: EU868
Initialization OK,Current work_mode:LoRaWAN, join_mode:OTAA, Class: A
gps_timeout: 100s

at+version
OK3.1.0.11

at+get_config=device:status
OK.


===============Device Status List================
Board Core: S76G_B
MCU: STM32L073RZ
LoRa chip: SX1276

Support Gps:true
gps_timeout: 100s
gps_format:standard LPP format
No signal with Satellite.

MPU9250 sensor:
Acceleration(g) of X,Y,Z:
0.02,-1.00,0.06
Gyro(degress/s) of X,Y,Z:
2.23,0.09,0.07
Magnetometer(uT) of X,Y,Z:
59.10,-51.75,-45.90

===================List End======================


at+get_config=lora:status
OK.


==============LoRaWAN Status List================
Work Mode: LoRaWAN
Region: EU868
Send_interval: 600s
Auto send status: true.
Send_interval work at sleep
Join_mode: OTAA
DevEui: 00DC9BB91BD52902
AppEui: 70B3D57ED002DF32
AppKey: C2F8E302A071017314BACC6F7A407819
Class: A
Joined Network:false
IsConfirm: false
AdrEnable: true
EnableRepeaterSupport: false
RX2_CHANNEL_FREQUENCY: 869525000, RX2_CHANNEL_DR:0
RX_WINDOW_DURATION: 3000ms
RECEIVE_DELAY_1: 1000ms
RECEIVE_DELAY_2: 2000ms
JOIN_ACCEPT_DELAY_1: 5000ms
JOIN_ACCEPT_DELAY_2: 6000ms
Current Datarate: 5
Primeval Datarate: 5
ChannelsTxPower: 0
UpLinkCounter: 0
DownLinkCounter: 0
===================List End======================


at+set_config=lora:region:AU915

Selected LoRaWAN 1.0.2 Region: AU915
OK

at+set_config=lora:region:EU868

Selected LoRaWAN 1.0.2 Region: EU868
OK

at+join
OTAA:
DevEui:00DC9BB91BD52902
AppEui:70B3D57ED002DF32
AppKey:C2F8E302A071017314BACC6F7A407819
OTAA Join Start…
OK
[LoRa]:Join retry Cnt:1
[LoRa]:Join retry Cnt:2
[LoRa]:Join retry Cnt:3
[LoRa]:Join retry Cnt:4
[LoRa]:Join retry Cnt:5
[LoRa]:Joined Failed!
Go to Sleep
OK

Update after getting back on 3.1.0.13:

at+run
The AT Command is invalid

@pr89 where do you got 3.1.0.13 firmware? It isn’t on the RAK download site:
https://downloads.rakwireless.com/LoRa/RAK7200-Tracker/Firmware/

BR,
Jeroen

The 3.1.0.13 is the latest release, directly visible on the downloads page (https://downloads.rakwireless.com/LoRa/RAK7200-Tracker/Firmware/RAK7200_Latest_Firmware.zip).
The older ones are in the history-release folder

ttn console does not show anything.


From the gateway console?
Whether the gateway is connected to TTN correctly?

No, the App console on ttn.

We do not have a gateway (yet), the area is supposed to be well covered according to ttn mapper.

Yesterday, I did let the app console run, while I went to a place where a ttn gateway is installed. The node wakes up every 600s and tries to connect to ttn, but it did not work either, so failure by distance should not be the case. Settings are correct, too, Device EUI, App EUI and Appkey is from ttn, deleted the device once and made a new one to be sure.

Each Node and Gateway must be set in same Frequency band and same frequency point to be able to connecte with each other! Can you confirm that these are all the same?

I don’t have access to the gateway.

I checked the reference for LoRaWAN 1.0.2, EU868 should be used here. Is it correct that the standard setting of the RAK7200 is to try 5 different frequencies within the EU868 range?

What else can I try? changing DR, tx?

It is recommended that you have your own gateway!!!You can’t connect without knowing someone else’s configuration!!! :neutral_face: :neutral_face: :neutral_face:

aha thanks, stupid me, mist it :wink:

@Nicholas I can understand that, thanks. However, this would defeat the whole purpose of having a LoRaWAN GPS tracker, or not?

Can be closed. Changed the location today, I get a connection here. Thanks!

Final note: The AT format error reported in post 1 is non-critical, but appears after first run. I did just setup our second device, here is the log. P.s. LoRA works. GPS is still an issue on both, I’ll have to check on that next.

at+version
OK3.1.0.13

at+set_config=lora:join_mode:0
join_mode:OTAA
OK

at+set_config=lora:class:0
Class:A
OK

at+set_config=lora:region:EU868
No switch region.Current region:EU868
OK

at+set_config=lora:dev_eui:0056C313F2AC0B46
OK

at+set_config=lora:app_eui:70B3D57ED002E01E
OK

at+set_config=lora:app_key:A956EAE716E57680A19B714AD999E6E3
OK
OTAA:
DevEui:0056C313F2AC0B46
AppEui:70B3D57ED002E01E
AppKey:A956EAE716E57680A19B714AD999E6E3
OTAA Join Start…
OK
AT format error.
[LoRa]:Join retry Cnt:1
[LoRa]:Join retry Cnt:2
[LoRa]:Join retry Cnt:3
[LoRa]:Join retry Cnt:4
[LoRa]:Joined Successed!

at+get_config=lora:status
OK Work Mode: LoRaWAN
Region: EU868
Send_interval: 600s
Auto send status: false.
Join_mode: OTAA
DevEui: 0056C313F2AC0B46
AppEui: 70B3D57ED002E01E
AppKey: A956EAE716E57680A19B714AD999E6E3
Class: A
Joined Network:true
IsConfirm: unconfirm
AdrEnable: true
EnableRepeaterSupport: false
RX2_CHANNEL_FREQUENCY: 869525000, RX2_CHANNEL_DR:3
RX_WINDOW_DURATION: 3000ms
RECEIVE_DELAY_1: 1000ms
RECEIVE_DELAY_2: 2000ms
JOIN_ACCEPT_DELAY_1: 5000ms
JOIN_ACCEPT_DELAY_2: 6000ms
Current Datarate: 1
Primeval Datarate: 5
ChannelsTxPower: 0
UpLinkCounter: 0
DownLinkCounter: 0

at+get_config=device:status
OK.


===============Device Status List================
Board Core: S76G_B
MCU: STM32L073RZ
LoRa chip: SX1276

Battery Voltage = 3.318 V
Support Gps:true
gps_timeout: 100s
gps_format:standard LPP format
No signal with Satellite.

MPU9250 sensor:
Acceleration(g) of X,Y,Z:
0.18,0.07,0.95
Gyro(degress/s) of X,Y,Z:
0.13,1.22,0.17
Magnetometer(uT) of X,Y,Z:
-17.10,20.40,5.55

===================List End======================


The error resulted from inability to send configuration during the join process.
You need to go outside to collect GPS data.

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