Dear all,
Issue:
Since migration to TTN stack v3 no join possible any more. FW upgraded to v3.
Setup:
RAK811 controlled via AT commands in RAK serial tool.
Server:
TTN stack v3
Details:
Initially I tried V2 firmare with TTN v3 and had the same issue, and after FW v3 (see screenshot) the problem remains the same. TTN console shows a “Forward join accepted message” but never finalizing the join.
It seems the device was able to send the join request. But missed the join accept downlink.
Hmm.
1.Is the gateway fully working with other device (if you have any other than RAK811)?
2. Can you see logs on the gateway side if a downlink join accept is really sent?
3. Did you use LoRaWAN version 1.0.2 when you registered the device to TTN?
Dear Carlo,
sorry for the late reply, but it took a while to nail the problem down:
upgraded my Gateway → check
LoRaWAN Version1.0.2 → check
did try the AT commands with my laptop plus the RAKserial-Tool
- setup, join and send possible → check
- set lora mode → strange because no feedback from console and powercycle required
Rearranged back to my Raspberry Pi zero config:
Bytheway, I’m using the " Raspberry Pi LoRa Node pHAT"
Serail AT commands, same behaivor as above (luckily):
*pi@ackerberry:~ $ rak811v3 hard-reset
*pi@ackerberry:~ $ ./rakconnect.sh /dev/serial0
*Connected to /dev/serial0 - CTRL-D to quit
*at+version
*OK V3.0.0.14.H
*at+get_config=lora:status
*OK Work Mode: LoRaWAN
*Region: EU868
*MulticastEnable: false
*DutycycleEnable: false
*Send_repeat_cnt: 0
*Join_mode: OTAA
*DevEui: 00000000XXXXXXXXXX
*AppEui: 70B3D57XXXXXX
*AppKey: 2CF11C6AAE1845CXXXXXXX
*Class: A
*Joined Network:false
*IsConfirm: unconfirm
*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
*at+set_config=lora:join_mode:0
*OK
*at+set_config=lora:work_mode:0
-------->HERE NO RESPONSE
*at+get_config=lora:status
--------->NO RESPONSE FROM NEW COMMANDS
*^C → cancel and reset
*pi@ackerberry:~ $ rak811v3 hard-reset
*pi@ackerberry:~ $ ./rakconnect.sh /dev/serial0
*Connected to /dev/serial0 - CTRL-D to quit
*at+version
*OK V3.0.0.14.H
-----> WORKING AGAIN NORMAL
So my workaround in my Python scripts is to comment all commands which try to setup the basics.
That was also written in another post some time ago.
