A newest software based on Raspbian OS for RAK2245 and RAK831 + RPi!

(Fomi Tong) #1

Hi, everyone

In the last two weeks, my team worked hard to develop a newest version software for RAK2245(with UART GPS) + RPi or RAK831 + RPi or RAK7243 without LTE, based on Raspbian OS, and it has a built-in loraserver!!!
Now, i’m very glad to announce that we’ve released it today.
You can download the image from the following link:
and make a SD card system for your RAK2245 + RPi or RAK831 + RPi, according to the document:

In this version, we supply a friendly configuration UI as follow:
People only need to type a command “sudo gateway-config”, then this UI will come.
I think it can simplify the operate steps for the canfigeration of a LoRa gateway.

Now, you can get the gateway ID very simply:

Do you like it? Just download and try. :slight_smile:

note: i’ve modified these contents on 2019/4/24 to update the newest information and firmware.

(Fomi Tong) #2

We’ll update its source code on Github next week. Just focus on this topic. :slight_smile:

(Vladislav Yordanov) #3

Perhaps let us beta test it first before doing any updates to GIT :slight_smile:

(HYH) #4

Hello, I am using this software. I have two questions.

  1. do we need to enter the gateway id in order to connect to TTN?
  2. is there any command allow us to see the log file? i.e. to see the connection, uplink downlink
(Fomi Tong) #5

Hi, @ms042087

Welcome to RAK forum!
All information about RAK831, RAK2245, RAK7243 (LTE) can be found in my topic:

About your questions:

  1. When the gateway power on, it will generate an ID automatically, and you can find it by selecting “3 Edit packet-forwarder config” item in the following page:
    Then you can see the gateway ID:

  2. If want to see the log, you can find the syslog file in the folder </var/log/syslog>.

(HYH) #6

Thanks for answering, now I can see the log file!
I encounter another problem. After looking into the log file, I observe that CRC_FAIL: 100%.
I am not sure if it is a problem of gateway or node
Gateway hardware: RAK831 + Raspberry Pi
Node hardware: Dragino LoRa shield + Arduino Due / UNO (I tried both)
Node software: the Arduino-lmic

frequency: 868EU

Sometimes (Just rarely), the packet can be uploaded to TTN. I found that the RSSI is pretty low but two devices are close to each other. Is there any method to know what the problem is?

(Benoit BRETON) #7

Hi, a new image was publish * RAK2245&RAK831_based_on_Raspbian_OS_V2.3R_20190404.img.zip but i dont find the changelog and nothing on github. Where can i found change ?

(elpis) #8

Any help with this id is not generated ?

(Vladislav Yordanov) #9

What image are you using ?
Is this the local or global config file.
Did you do any configuration beforehand ?

(ZhuQI) #11

Maybe you can get the gateway ID from file /opt/ttn-gateway/packet_forwarder/lora_pkt_fwd/local_conf.json

(Vladislav Yordanov) #12

Thanks, I spoke to him, we resolved the issue :slight_smile:

(Fomi Tong) #13

Hi, @Hobo

I’m sorry for it. This information is old now, in fact, we’ve released another version software for RAK831 & RAK2245 + RPi last week. I’ll write a new tutorial document this week and delete this topic.

BTW, i’ve removed the image based on LoRa Gateway OS from our website, so i need to remove all information about it from our forum too. There will be only one topic about LoRa Gateway OS on RAK forum.

Thank you!

(alfredo) #14

thanks for the great tutorials. Could you please give us a link where the new images are located?

(Fomi Tong) #15

Hi, @danielperez

Please download the image from RAK website:

(alfredo) #16

Thank Fomi: I have the same problem with Gateway ID,
I downloaded the image from the image from RAK website:[https://www.rakwireless.com/en/download/LoRa/RAK2245-Pi-HAT#Firmware ] I have a Lora 2245 with a PI3
Then I setup the gateway with sudo gateway-config
Then I setup Lora concentrator as …Server is Lora Server
Setup Ip
result is… The packet forward has been restarted
then when I try to edit packet forward I found that gateway ID is 00000000000…
do I am missing something ??


(Vladislav Yordanov) #17

Hi @danielperez,


Please refer to the image. You should see the Gateway ID at the top of the Configuration box (area circled in red in the image).


(Fomi Tong) #18

Hi, @danielperez

As @Hobo said, you can get the gateway ID from that UI directly.
In another way, you can also type the command to get the gateway ID as the following picture shows:

1 Like
(alfredo) #19

Using the same installation I can´t open the Lora Application Server web interface. is application server already installed in this version?

(Fomi Tong) #20

Hi, @danielperez

Are you using the 2.3R version image which download from here?

If you are, i think you need to download the 2.4R version image from the same link. Because only 2.4R version image has a built-in loraserver. You can look the names of them, there is “with_loraserver” string included in the correct image name.

Just download and try again. :slight_smile:

(alfredo) #21

Thanks again: Is it possible that a fixed ip was done in dhcp config. That´s because I can´t connect to wlan 0, if I type ifconfig, wlan0 don´t have ips

[email protected]:~ $ ifconfig

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

inet netmask broadcast

inet6 fe80::5c46:1a3:4614:4a5c prefixlen 64 scopeid 0x20

ether b8:27:eb:3a:b0:05 txqueuelen 1000 (Ethernet)

RX packets 136 bytes 16832 (16.4 KiB)

RX errors 0 dropped 4 overruns 0 frame 0

TX packets 78 bytes 11198 (10.9 KiB)

TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536

inet netmask

inet6 ::1 prefixlen 128 scopeid 0x10

loop txqueuelen 1000 (Local Loopback)

RX packets 686 bytes 147768 (144.3 KiB)

RX errors 0 dropped 0 overruns 0 frame 0

TX packets 686 bytes 147768 (144.3 KiB)

TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500

ether b8:27:eb:6f:e5:50 txqueuelen 1000 (Ethernet)

RX packets 0 bytes 0 (0.0 B)

RX errors 0 dropped 0 overruns 0 frame 0

TX packets 0 bytes 0 (0.0 B)

TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0