RAK7244 Firmware Update - GPS/Gateway offline

Dear All,
Ive updated my brand new RAK7244 Developer with the latest firmware from the support website. All is fine on the RPi4 but when i check Chirpstack or TTN the gateway never comes online. Last Seen is never, GPS is not seen.
Anything specific you need to adapt when you installed the latest firmware to get the gateway up and running?
I’ve used the lastest build RAK7244_4.2.6_20210108.img from the RAK doc website. Any suggestion what i forget to adapt? Thanks

Solved it myself.

Just don’t use the image from RAK Wireless on the support website.
Rebuild your own by getting the latest Raspberry Pi 4 Lite Image

step1 : Download and install latest Raspberry Pi OS Lite

step2 : Use “sudo raspi-config” command, enable spi and i2c interface, disable login shell over serial and enable serial port hardware.

step3 : Clone the installer and start the installation (More installation options can be found in “sudo ./install.sh --help”).

  $ sudo apt update; sudo apt install git -y
  $ git clone https://github.com/RAKWireless/rak_common_for_gateway.git ~/rak_common_for_gateway
  $ cd ~/rak_common_for_gateway
  $ sudo ./install.sh

step4 : Next you will see some messages as follow. Please select the corresponding hardware model.

  Please select your gateway model:
  *	 1.RAK2245
  *	 2.RAK7243/RAK7244 no LTE
  *	 3.RAK7243/RAK7244 with LTE
  *	 4.RAK2247(USB)
  *	 5.RAK2247(SPI)
  *	 6.RAK2246
  *	 7.RAK7248 no LTE (RAK2287 SPI + raspberry pi)
  *	 8.RAK7248 with LTE (RAK2287 SPI + LTE + raspberry pi)
  *	 9.RAK2287 USB
  *	 10.RAK5146 USB
  Please enter 1-10 to select the model:

step5 : Wait a moment and the installation is complete.

step6 : For more other features, please use “sudo gateway-config”.

1 Like

Thanks for the trick but not working too for me :frowning: I have a RAK2287 (SPI version with GPS and EU868) board mounted on RAK2287 Hat on a PI4, so I selected choice 7 (RAK2287 SPI + pi) but it did an install with a start script that references SX1301 and not 1302 like I have on my board and for sure script fails at startup :frowning:
Desperate to get that gateway working with TTS :frowning: manufacturer image doesn’t work and manual install too or suffers the same bug… Don’t know if I can select an other board that could work in list ?

I followed @Timo 's instructions.

It seems working for me on my RAK7248 (no LTE).
Manually started lora_pkt_fwd and I can see it is using SX1302:

[email protected]:/opt/ttn-gateway/packet_forwarder/lora_pkt_fwd $ sudo ./lora_pkt_fwd
*** Packet Forwarder ***
Version: 2.0.1
*** SX1302 HAL library version info ***
Version: 2.0.1;
***
INFO: Little endian host
INFO: found configuration file global_conf.json, parsing it
INFO: global_conf.json does contain a JSON object named SX130x_conf, parsing SX1302 parameters
INFO: com_type SPI, com_path /dev/spidev0.0, lorawan_public 1, clksrc 0, full_duplex 0
INFO: antenna_gain 0 dBi
INFO: Configuring legacy timestamp
INFO: no configuration for SX1261
INFO: Configuring Tx Gain LUT for rf_chain 0 with 16 indexes for sx1250
INFO: radio 0 enabled (type SX1250), center frequency 867500000, RSSI offset -215.399994, tx enabled 1, single input mode 0
INFO: radio 1 enabled (type SX1250), center frequency 868500000, RSSI offset -215.399994, tx enabled 0, single input mode 0
INFO: Lora multi-SF channel 0>  radio 1, IF -400000 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora multi-SF channel 1>  radio 1, IF -200000 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora multi-SF channel 2>  radio 1, IF 0 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora multi-SF channel 3>  radio 0, IF -400000 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora multi-SF channel 4>  radio 0, IF -200000 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora multi-SF channel 5>  radio 0, IF 0 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora multi-SF channel 6>  radio 0, IF 200000 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora multi-SF channel 7>  radio 0, IF 400000 Hz, 125 kHz bw, SF 5 to 12
INFO: Lora std channel> radio 1, IF -200000 Hz, 250000 Hz bw, SF 7, Explicit header
INFO: FSK channel> radio 1, IF 300000 Hz, 125000 Hz bw, 50000 bps datarate
INFO: global_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters
INFO: gateway MAC address is configured to AA555A0000000000
INFO: server hostname or IP address is configured to "127.0.0.1"
INFO: upstream port is configured to "1700"
INFO: downstream port is configured to "1700"
INFO: downstream keep-alive interval is configured to 10 seconds
INFO: statistics display interval is configured to 30 seconds
INFO: upstream PUSH_DATA time-out is configured to 100 ms
INFO: packets received with a valid CRC will be forwarded
INFO: packets received with a CRC error will NOT be forwarded
INFO: packets received with no CRC will NOT be forwarded
INFO: GPS serial port path is configured to "/dev/ttyAMA0"
INFO: Reference latitude is configured to 0.000000 deg
INFO: Reference longitude is configured to 0.000000 deg
INFO: Reference altitude is configured to 0 meters
INFO: Beaconing period is configured to 0 seconds
INFO: Beaconing signal will be emitted at 869525000 Hz
INFO: Beaconing channel number is set to 1
INFO: Beaconing channel frequency step is set to 0Hz
INFO: Beaconing datarate is set to SF9
INFO: Beaconing modulation bandwidth is set to 125000Hz
INFO: Beaconing TX power is set to 27dBm
INFO: global_conf.json does contain a JSON object named debug_conf, parsing debug parameters
INFO: got 2 debug reference payload
INFO: reference payload ID 0 is 0xCAFE1234
INFO: reference payload ID 1 is 0xCAFE2345
INFO: setting debug log file name to loragw_hal.log
INFO: found configuration file local_conf.json, parsing it
INFO: local_conf.json does contain a JSON object named gateway_conf, parsing gateway parameters
INFO: gateway MAC address is configured to E45F01FFFE17C690
INFO: packets received with a valid CRC will be forwarded
INFO: packets received with a CRC error will NOT be forwarded
INFO: packets received with no CRC will NOT be forwarded
This is uart for GPS.
INFO: [main] TTY port /dev/ttyAMA0 open for GPS synchronization
CoreCell reset through GPIO17...
Opening SPI communication interface
Note: chip version is 0x10 (v1.0)
INFO: using legacy timestamp
INFO: LoRa Service modem: configuring preamble size to 8 symbols
ARB: dual demodulation disabled for all SF
INFO: [main] concentrator started, packet can now be received
INFO: concentrator EUI: 0x0016c001ff19cda1
INFO: [down] PULL_ACK received in 0 ms
WARNING: [gps] GPS out of sync, keeping previous time reference
WARNING: [gps] GPS out of sync, keeping previous time reference
INFO: [modify_os_time] local_time=1633657199, gps_time=1633657198
INFO: [modify_os_time] The difference between the system time(1633657199) and the GPS time(1633657198) is less than 10 seconds. Use the system time.
INFO: [down] PULL_ACK received in 0 ms
INFO: [down] PULL_ACK received in 0 ms

##### 2021-10-08 01:40:29 GMT #####
### [UPSTREAM] ###
# RF packets received by concentrator: 0
# CRC_OK: 0.00%, CRC_FAIL: 0.00%, NO_CRC: 0.00%
# RF packets forwarded: 0 (0 bytes)
# PUSH_DATA datagrams sent: 0 (0 bytes)
# PUSH_DATA acknowledged: 0.00%
### [DOWNSTREAM] ###
# PULL_DATA sent: 3 (100.00% acknowledged)
# PULL_RESP(onse) datagrams received: 0 (0 bytes)
# RF packets sent to concentrator: 0 (0 bytes)
# TX errors: 0
### SX1302 Status ###
# SX1302 counter (INST): 30908560
# SX1302 counter (PPS):  30425622
# BEACON queued: 0
# BEACON sent so far: 0
# BEACON rejected: 0
### [JIT] ###
src/jitqueue.c:440:jit_print_queue(): INFO: [jit] queue is empty
#--------
src/jitqueue.c:440:jit_print_queue(): INFO: [jit] queue is empty
### [GPS] ###
# Valid time reference (age: 0 sec)
# GPS coordinates: latitude -37.78557, longitude 145.17219, altitude 80 m
##### END #####

JSON up: {"stat":{"time":"2021-10-08 01:40:29 GMT","lati":-37.78557,"long":145.17219,"alti":80,"rxnb":0,"rxok":0,"rxfw":0,"ackr":0.0,"dwnb":0,"txnb":0,"temp":0.0}}
INFO: [up] PUSH_ACK received in 0 ms
INFO: [down] PULL_ACK received in 0 ms

Thanks for the details, I did a whole reinstall with OS image supplied by Rak and this time it’s working fine either on internal Chirpstack server or connected at TTN :wink: