RAK2245 - LoRa Concentrator modules


did you install this software ?

(Digiheart) #5

Yes I did,

I even tried multiple times with fresh raspian lite

There are some bugs with that software that I can’t understand.

(Kenyu) #7

Do you mean you try the RAK2245 or RAK831? @fomi

(Digiheart) #8

The RAK2245

(Fomi) #9

Hi, @digiheart
I’ve used the source code https://github.com/RAKWireless/RAK2245-LoRaGateway-RPi-Raspbian-OS on RAK2245+RPi for testing, and got the GPS data successfully as follow:
Please check the red line information, they are GPS data, and ignore the green line error information.
BTW, i’ve just updated Github to remove these additional error information, you can check it again.

(Digiheart) #10

Hi fomi,

Thank you for the help.

I installed a fresh Raspbian and tested the latest commit, and I can confirm that some of the errors during installation are gone and that the amount of warmings is way less. However I still can’t get valid coordinates. I have all antennas plugged in and the device is standing by the window. Here is the output:


Any suggestion?

(Jeff Uk) #11

Dont know if it will help but whilst struggling to get quick fix and consistent/stable location lock on RAK5205 trackers (same/similar GPS chip?) over last few days @paulb called out fact I was inside near window (with low K glass treatments etc.) that might be screwing with timing/multipaths etc. When I took outside all fast and stable…perhaps try same with your GW or at least if GPS on long lead get ant outside window whilst testing?! :wink: Good Luck!..

(Digiheart) #12

Thank you for the advice, however I tried to put the gateway and without any success. Still invalid coordinates

(Fomi) #13

Hi, @digiheart

Have you open the i2c interface according to the Github readme:

If you have done that, i think that you can reduce the rate of i2c and try again.

(Fomi) #14

You can do as the following steps:

step 1. Check the GPS connection as follow:

step 2: Modify the /boot/config.txt file as the following content to reduce the i2c rate:

Then, restart the GW and check the GPS data.

(Fomi) #15

I’ve just updated the Github repo to add a folder for testing GPS fuction.
You can check it.

(Jmfdiaz) #16

Has anyone tries the RAK2245 96Boards IoT Edition? With Orange Pi i96 as a possible target board…

(Digiheart) #17

Still nothing…

I even reinstalled a fresh raspbian, cloned the latest version of your repository, changed baudrate and still returning the same error.


maybe its a good idea to contact the developpers (fomi) direct (PM), you could have a broken board, seems you did everything to fix this.
my 2 cents :wink:

(Kenyu) #19

we should have some update soon. I will keep to update here

(Kenyu) #20

I would like to exchange the hardware in your hand. pls email ken.yu@rakwireless.com


@digiheart @fomi @kenyu I have the same board and same issues, unfortunately. Also on the LoRa Server forum there is somebody else with the same issue (https://forum.loraserver.io/t/raspberry-pi-rak2245-rak2243/3512) The RAK provided LoRa Gateway OS image does provide an utility which prints the NMEA output, which (in my case) prints NMEA data, but it contains corrupted bytes:

$GPTXT,01�01,00,txbuf alloc*7F
$GPTXT,01,01,00,txbuf alloc*7F


@fomi the output I’m seeing looks a lot like this issue: https://portal.u-blox.com/s/question/0D52p00008HKDtfCAH/how-to-use-i2c-to-get-the-nmea-frames

The problem is that sometimes (approximately 1 on 12 character that i read are not good), i got a non-ascii character or i am simply missing one character resulting in a bad frame.

Personally I would have prefered when the GPS was using the Raspberry Pi UART interface like the RAK831. That way no patching of the packet-forwarder would have been needed and it would not break compatibility with other GPS utilities that usually read from an UART interface.

(Fomi) #22

Hi, @brocaar @digiheart

Thanks for your advice.

I’ve discussed with team, and we decide to use uart interface for RAK2245 GPS as usual.

We’ll send you a new RAK2245 Pi Hat board which uses uart for GPS ASAP.

(Kenyu) #23

All, As Fomi mentioned, we will adjust the product strategy and use UART interface as regular model# for RAK2245 Pi Hat, But in order to support the developer who like to Add on cellular Pi Hat, we will assembly with another model# using I2C in Pilot Gateway Pro and RAK provide the workable firmware in that device. Some of the developer already purchase the RAK2245 Pi hat, they can use current firmware to start the testing at least:https://github.com/RAKWireless/RAK2245-LoRaGateway-RPi-Raspbian-OS

We will also contact with the people who have that inhand and exchange the board if they need UART interface to play. Don’t worry everybody:)

(Michael) #24

Hi @kenyu @fomi,
I would also be very happy to get my board exchanged with an UART version. Just found the time to start working on my resion.io image when I learned about the I2C connection of gps module.

Also there was a little mistake with the two included u.FL <-> SMA pigtails. It fits for the LoRa-Antenna, but for the GPS Antenna an Reverse-SMA pigtail would have been needed. Not big deal, because I had the needed parts flying arround. But I think you might want to know. See the picture I took:


Cheers and have a nice weekend!