Rak7246 Showing as Disconnected on Things Network

Hi

I have a RAK7246 set up to use the Things Stack Community Edition.

I followed instructions here to setup: RAK7246G Quick Start Guide | RAKwireless Documentation Center

I am based in Australia. On the Things Stack Console, I selected a Frequency Plan = AU_915_928_FSB_2

The Gateway shows as Disconnected in the Things Stack Console.

Details of my device:
sudo gateway-version
Raspberry Pi Zero W Rev 1.1, OS “10 (buster)”, 5.10.63+.
RAKWireless gateway RAK7246 version 4.2.0R install from firmware.
Gateway ID: XXXXXXXXXXXXXXXX.

Packet Forwarder Config is shown below.

I have two test devices, both previously connected to TTN. One is still on V2 Console, another has been removed from V2 and is now registered on the new V3 Community Edition alongside the RAK. I have seen traffic for nether in the time since I set up the RAK7246.

Logs for the RAK7246 appear to show join requests from both devices. This is confirmed by checking the packet data on the https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/ which indicates that Message Integrity Code (MIC) is as expected.

Any idea what is the problem(s) here?

PACKET FORWARDER CONFIG:

“gateway_conf”: {
“gateway_ID”: “XXXXXXXXXXXXXXXX”,
/* change with default server address/ports, or overwrite in local_conf.json /
“server_address”: “router.au.thethings.network”,
“serv_port_up”: 1700,
“serv_port_down”: 1700,
/
adjust the following parameters for your network /
“keepalive_interval”: 10,
“stat_interval”: 30,
“push_timeout_ms”: 100,
/
forward only valid packets /
“forward_crc_valid”: true,
“forward_crc_error”: false,
“forward_crc_disabled”: false,
/
gps enable */
“gps_tty_path”: “/dev/ttyAMA0”,
“fake_gps”: false,
“ref_latitude”: 10,
“ref_longitude”: 20,
“ref_altitude”: -1,
“autoquit_threshold”: 20

DEVICE LOGS:

For other’s reference, I obtained the log by using the following:
cd /opt/ttn-gateway/packet_forwarder/lora_pkt_fwd
then
Running:
./lora_pkt_fwd

Output begins with the following:
*** Beacon Packet Forwarder for Lora Gateway ***
Version: 4.0.1
*** Lora concentrator HAL library version info ***
Version: 5.0.1;


INFO: Little endian host
INFO: found global configuration file global_conf.json, parsing it
INFO: global_conf.json does contain a JSON object named SX1301_conf, parsing SX1301 parameters
INFO: lorawan_public 1, clksrc 1
INFO: no configuration for LBT
INFO: antenna_gain 0 dBi
INFO: Configuring TX LUT with 16 indexes
INFO: radio 0 enabled (type SX1257), center frequency 917200000, RSSI offset -166.000000, tx enabled 1, tx_notch_freq 0
INFO: radio 1 enabled (type SX1257), center frequency 917900000, RSSI offset -166.000000, tx enabled 0, tx_notch_freq 0
INFO: Lora multi-SF channel 0> radio 0, IF -400000 Hz, 125 kHz bw, SF 7 to 12
INFO: Lora multi-SF channel 1> radio 0, IF -200000 Hz, 125 kHz bw, SF 7 to 12
INFO: Lora multi-SF channel 2> radio 0, IF 0 Hz, 125 kHz bw, SF 7 to 12
INFO: Lora multi-SF channel 3> radio 0, IF 200000 Hz, 125 kHz bw, SF 7 to 12
INFO: Lora multi-SF channel 4> radio 1, IF -300000 Hz, 125 kHz bw, SF 7 to 12
INFO: Lora multi-SF channel 5> radio 1, IF -100000 Hz, 125 kHz bw, SF 7 to 12
INFO: Lora multi-SF channel 6> radio 1, IF 100000 Hz, 125 kHz bw, SF 7 to 12
INFO: Lora multi-SF channel 7> radio 1, IF 300000 Hz, 125 kHz bw, SF 7 to 12
INFO: Lora std channel> radio 0, IF 300000 Hz, 500000 Hz bw, SF 8

Your TTN server address points to TTN V2.
It should be au1.cloud.thethings.network, that is what I use and it works.

Try to change

“server_address”: “router.au.thethings.network”,

to

“server_address”: “au1.cloud.thethings.network”,
1 Like

Thanks. It’s working now!
%$#%$# sure I tried that yesterday. Along with several others. …

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