How to setup RPi Zero + RAK831 gateway for V3?

Gateways RAK Gateways
1

I hope this “movement” to V3 was not only to force home builders to buy commercial gateways :slight_smile:

Is there step-by-step guide for placing the gateway based on RAK831 gateway module and Raspberry Pi Zero W?
They are connected via RAK-Raspberry Pi shield by ch2i. The r.pi is connected via USB-Ethernet adapter and powered by PoE injector.

2

Certainly not. And you should know better…
My homebuild gateways migrated to V3 without any issues.

Any steps depend largely on the software being used, what software are you using?

3

Probably:

4

What exactly do you mean here?

5

@s54mtb I have lots of these built using Charle’s interface card and following his sw repository instructions. Mine mostly use @kersing Jac’s MPPF (use instructions in repository to change the start.sh last line etc.). (I also use same set up for many RAK Pilots and equivalent custom housing builds etc. with the interface card swapped to RAK’s 831 interposer board). Migration is ‘simple’.:

  1. Set up new V3 GW instance and generate an API key allowing GW fn - keep it safe.
  2. Log into the GW Rpi0W, navigate up the directory tree and head to and edit the global_conf.json file (likely directory if you follow standard build is /opt/loragw (or your equivalent)
  3. Scroll down to the “gateway_conf” section of the file and tidy up/edit to reflect your version of this set up:
"gateway_conf": {
        "gateway_ID": "B827EBFFFEXXXXXX",
        "ref_altitude": 55.0,
        "description": "Genesis-S3_TestGW016_Rak-no3, RPi0W+Rak831+CH2i i/f boa$
        "servers": [
            {
                "server_address": "eu1.cloud.thethings.network:1881",
                "serv_gw_id": "g-s3-testgw016-pi0w-831no3-hp10",
                "serv_type": "ttn",
                "serv_gw_key": "NNSXS.NDQMVP....<the API key you saved earlier!>
                "serv_enabled": true
            },
            {
                "serv_port_up": 1688,
                "serv_type": "gwtraf",
                "serv_enabled": false,
                "server_address": "127.0.0.1",
                "serv_port_down": 1689
            },

Note add the 1881 port to server address if using the MPPF (Thanks to Jac for hand-holding & pointing out the gotchas when I missed that during my 1st set up of such a config)

If there are other servers called out (e.g. 127.0.0.1 simply check to see if set as false, also as you will see the version above tidies up and removes some listed ‘back-up’ servers which no longer apply.

In addition lower down the file if not already populated you might want to update the latitude and longitude details if using fixed GPS data in console etc.

Save your edits (over write existing), reboot the GW (shutdown -r now) and with a following wind after approx 5 mins you should see an active GW in V3 - having local node Txing helps speed up traffic capture and recognition by NS/Backend…

Any problems come back here and detail (please dont make us guess!) what you have done of what has gone wrong/problems seen…

Good Luck!

6

Excellent. That’s all I needed. Thank you.

7

there is no file global_conf.json on the balena gateway:

slika
slika1099×650 42.1 KB

There are two folders under /opt:

root@ea0d4f3:/# ls /opt
gwexporter ttn-gateway

Where exactly is global_conf.json file ?

8

You didnt say you were doing a Balena install! My suggestions and experience was based on Charles/ch2i (see link posted by Bluejedi) build and board you called out and modifying for V3… if Balena you will need to look elsewhere and get help from others - I believe Jac @kersing uses this and has done own builds using his MPPF & Balena…He did ask 10 days ago what Sw you were using!..