I bought RAK 5146 concentrator, and I see it on the list of concentrators integrated into ChirpStack (CS):
The easiest way is to install the ChirpStack Gateway OS (full image). After flashing that to an SD card, please follow these instructions: Getting started - ChirpStack open-source LoRaWAN® Network Server documentation.
Yes, exactly. I found this before your answer and installed CS G OS on my RPi 4. Works perfectly.
But I found that the documentation for ChirpStack has a mistake. The link to this image is outdated. I found it because OS under this link didn’t have my RAK 5146 device on the configuration list. So I deleted an old version URL from that link, and this way, I found the latest version.
I would appreciate a pull-request with the documentation fix 
Ok, I made a fork, but first, I’ll show you where the problem is:
@brocaar Do you plan to accept this PR?
I see what you mean. Actually, the link is correct as this is the old v3 documentation so it should point to the latest v3 image. What I should do however is put a warning on these pages pointing to the latest documentation version: Downloads - ChirpStack open-source LoRaWAN® Network Server documentation.
I am lost I have a project on developing a gateway based on rak5146 SPI with raspberry pi 3 when i have flashed the chirpstack gateway os with rpi i dont find the rak5146 in the list and when i have followed the repo of GitHub - RAKWireless/rak_common_for_gateway and i have fixed the server ip which is the adress of my vm and where i started the app service and network service and bridge service and i have configured my gateway id but still never seen in the CS app please help me i am lost and i have only 2 weeks to finalize the project of my internship
The RAK5146 is supported in the latest Gateway OS. You will find it under the SX1302 tab.
I have done it with ChirpStack Gateway OS but i am encountering same problem of gateway never seen when i am using Raspberry Pi OS
Hello @brocaar. I am using RAK5146 USB, I have a mici pcie to usb converter plugged into the beaglebone black. I configured the USB port and claimed the device. I downloaded the HAL driver for SX1302, even though RAK5146 utilizes SX1303 however I found that SX1302 also works as a HAL driver for the SX1303 chipset. Then I changed the configurations on the global_conf.json file and stated the com type and com port of the RAK5146, then I also added us915 to the beginning of the command and event topics. Later I installed chirpstack server following this guide:
https://www.chirpstack.io/docs/getting-started/debian-ubuntu.html?search=
The chirpstack server seems to work and I can access the web UI. Then I installed chirpstack-gateway-bridge on my beaglebone black. On the .toml file, default semtech udp port was 1700 so I changed the default values in the global_conf.json for the packet forwarder. I also typed the server address as my VM’s address where chirpstack is installed. Then I ran the packet forwarder and print the logs into the console. I am receiving multiple packets in a second so RAK5146 is working. However, the packets are not forwarder to mqtt broker, so the problem must have been with the chirpstack-gateway-bridge. When I logged chiprstack-gateway-bridge, I see that it has been sucessfully connected to the mqtt broker. I thought maybe the firewall must be an issue bat I can emulate packets to my mqtt broker installed on my VM from BBB, so there is no problem with that either. What could be the issue or what could I be missing I have spent almost a week on it trying to figure out, tried almost every solution but I think it will be a such small detail that I am missing. Please help me man.
It sounds like you are using the UDP Packet Forwarder and there are frames getting picked up by the RAK5146. Does the Gateway Bridge indicate that frames are being received? You may need to increase logging verbosity to see such logs.
You must add the subband as well. I.e “us915_0” or “us915_1”. Keep in mind Chirpstack uses 0 indexing for the subband while most other things do not, so just make sure your subbands do align between device and topic prefix.
Did you check the statuses for the services:
sudo systemctl status chirpstack-gateway-bridge
sudo systemctl status chirpstack
sudo systemctl status mosquitto
and journal
sudo journalctl -f -n 100 -u chirpstack
PS. I use the RAK5146 but the SPI model.
The system was already set to DEBUG, so logging verbosity was not the issue. Initially, I installed Debian because I was more familiar with it, even though my project required OpenWRT. OpenWRT involves cross-compilation and handles the kernel differently, which added complexity.
Since ChirpStack-related packages are readily available on Debian, I started with it. However, after encountering several issues, I decided to switch to OpenWRT. While working on OpenWRT, I faced segmentation faults due to how the kernel manages the stack, but after consulting forums, I managed to resolve them. Interestingly, what didn’t work on Debian functioned properly on OpenWRT. I am getting LoRaWAN packets on my VM where chirpstack is installed.
Although I’m curious about the root cause of the issue, I have a tight deadline, so I’ll have to overlook it for now. Nonetheless, thanks for the help! Do you guys have any recommendation about running a LoRaWAN gateway on OpenWRT OS, or have any concerns. I would really like to hear your opinions.
Yes the services are working. I manage to work it on OpenWRT instead of Debian. I dont know the root cause unfortunately.
Should I add the subband on chirpstack.toml under enable_regions as well. I guess in this post you meant on global_conf.json.
The default Chirpstack.toml should already have us915_0 and us915_1 enabled, but if they are not in the enabled regions array you should add them, or at least your subband. I was actually talking about the command and event topics though, they should start with us915_x. I am not familiar with the global_conf.json file.