MatchX MX1701 gateway: Help needed to (re) integrate it to TTN v3

Gateways
1

Hi all,

I have had a MatchX MX1701 gateway running until about a year ago now (as my device tells me).

As I want it to switch to TTNv3 stack now, I am searching for a howto or any documentation but did only find posts that did not help in my case.

Unfortunately, the vendor has kept me in their backend (I have a working account there, could reach the device there, could update to “0.12”) but somehow, magcally I had a working gateway in the past, that’s why I had been fine with it.

I also am able to log into luci webbackend of that device but I am only shown the “vanilla” part of the OpenWRT there. It shows “Chaos Calmer” as operating system - I guess that is very old… can anything be done?

A person from Berlin on TTN regional group somwhere here seems to have worked with MX1701 but those hints do not say much to me, maybe outdated anyway as they are form 2018.

Now: Where do I put the new address eu1.cloud.thethings.network or what else do I have to do to make it work again?

I have created a GW in the TTN v3 console but so far, no data is shown.

Thanks in advance!
Andreas

2

The manual implies it uses the standard global_conf.json / local_conf.json to configure settings like channel plan and server addresses and runs a classic (if LBT) packet forwarder.

Probably you can use the software that’s already on their by changing the configuration, at a stretch you’d need to identify the scripts that reset the concentrator card and build a newer executable for an MT7628 under Chaos Calmer type OpenWRT, which while admittedly dated is a still a pretty common platform, with cross toolchains available to download, etc.

3

Any luck? I have a few MatchX box-mx1702 gateways I’d like to get on TTNv3.

4

What have you tried so far and what issues are you seeing?

5

Hi cslorabox,

I’ve tried updating my previous global_json.conf from

	"gateway_conf": {

		"server_address": "thethings.meshed.com.au",
		"serv_port_up": 1700,
		"serv_port_down": 1700,
                "servers": [
                   {"server_address": "thethings.meshed.com.au",
                    "serv_port_up":1700,
                    "serv_port_down":1700,
                    "serv_enabled": true }
                ],
		"keepalive_interval": 10,
		"stat_interval": 30,
		"push_timeout_ms": 100,
		"forward_crc_valid": true,
		"forward_crc_error": false,
		"forward_crc_disabled": false,
		"gps_tty_path": "/dev/ttyS1",
		"ref_latitude": 0.0,
		"ref_longitude": 0.0,
		"ref_altitude": 0
	}

to the new ttnv3 servers:

    "gateway_conf": {
    "gateway_ID": "xxxxxxxxx",
    "server_address": "au1.cloud.thethings.network",
    "serv_port_up": 1700,
    "serv_port_down": 1700,
    "servers": [
      {
        "gateway_ID": "xxxxxxxxxxx",
        "server_address": "au1.cloud.thethings.network",
        "serv_port_up": 1700,
        "serv_port_down": 1700,
        "serv_enabled": true
      }
    ],
   		"keepalive_interval": 10,
		"stat_interval": 30,
		"push_timeout_ms": 100,
		"forward_crc_valid": true,
		"forward_crc_error": false,
		"forward_crc_disabled": false,
		"gps_tty_path": "/dev/ttyS1",
		"ref_latitude": 0.0, 
		"ref_longitude": 0.0,
		"ref_altitude": 0

  }

But this is currently leaving me “disconnected”

(Ive checked I can resolve the new addresses from the gateway, so the internet pathway is accessible)
Any thoughts?

6

What does the packet forwarder log show in terms of push/pull acks?