Official setup to show Gateway on map?

Gateways
21

The coordinate metadata in the application does change. The following shows a couple of instances taken a few minutes apart.

"latitude": XX.83462, "longitude": YY.20914, "altitude": 138
"latitude": XX.83464, "longitude": YY.20927, "altitude": 139
"latitude": XX.83473, "longitude": YY.20941, "altitude": 164

This variability is consistent with what I see direct from the GPS on the Pi when running the following command

cat /dev/ttyS0 | grep GPGGA

The following are the GPS related fragments from the config files.

global_conf.json

"gateway_conf": {
    /* change with default server address/ports, or overwrite in local_conf.json */
    "gateway_ID": "AA555A0000000000",
    /* Devices */
    "gps": true,
    "beacon": false,

...

    /* GPS configuration */
    "gps_tty_path": "/dev/ttyAMA0",
    "fake_gps": true,
    "ref_latitude": 10,
    "ref_longitude": 20,
    "ref_altitude": -1,

local_conf.json

   "gps_tty_path": "/dev/ttyS0",
    "gps":true,
    "fake_gps": false,

It seems to me that I just need to configure the map to accept the GPS coordinates as higher priority than the manually set pointer location, so the GPS coordinates override the manually set location, but I do not seem to be able to achieve this.

22

Just posting an update to this message. I “rebirthed” my gateway a few weeks ago, with a slightly different MAC address. I simply changed one of the two bytes of seemingly random information inserted in the middle of the gateway ID. In my case the gateway ID appeared to be the standard MAC address of the Ethernet NIC, with “FFFE” inserted between the first three bytes (the IANA part) and the last three bytes (the vendor part). I tweaked this to “FFF0” to create a new - also unique ID. I used only a local config rather than the GitHub pull of the local config file by removing the GitHub pull from the startup script.

My gateway has now been running for a couple weeks. It showed up at the correct (GPS defined) location on the public TTN map. It still has not shown up on my private map on the TTN console.

I am guessing the only way to locate my gateway on my map in the TTN Console is to use the pin. Does anybody know if there is a way to have the GPS data also position my gateway automatically on the TTN Console map - just like it appears to do on the public map? I am likely to move my gateway around a little to optimise the location, and would like my TTN Console map to automatically show its new location.

1 Like
23

Chances are good it’s indeed unique (even more so within the TTN infrastructure), but just for the sake of completeness: that’s not guaranteed. See discussion and alternative at DevEUI for non-hardware assigned values and Generated Device EUI clashes with officially assigned EUIs.

24

Arjan - thanks for this. I was not aware that such a discussion existed. It looks like I have followed the deprecated process. Despite that, I would be confident that my “rebirthed” gateway ID will have the same chance of being unique as my original, given both originate from my MAC address, which is by definition already unique. If this proves problematic, I have no problems changing it again in the future.

I am however still keen to see if there is a solution for my initial question relating to the automatic positioning of my GPS enabled gateway on my Gateways map.