New Gateway Registration

Gateways
5

Hi Richard,

Sorry for my late reply.

Regarding your question about handoff: I’m not really sure, I haven’t been really involved in those technical details, but I’m assuming there is a way to deal with nodes sending to multiple gateways. Maybe somebody else can chime in?

Your suggestion about monitoring traffic is an interesting one. Currently, the gateway status monitor only looks at status update packets sent by the gateway (i.e not at packets sent by nodes f.ex.)

To be honest, I think there’s really not a lot of node data incoming at the moment.
In time I think it would be very interesting to also look at node data, for example we could use it to get an idea about the range of each gateway when nodes start to send their GPS coordinaties.

Right now my main focus is on getting some more info on the gateways that are presently active.
Maybe you would like to help think about how we can improve the available information so that we can get a better overview of what is happening where?

1 Like
6

The GPS coordinates are transmitted by the gateway status json, so it would be unnecessary work to add them manually. Yes, i know not all gateways have GPS on board, but if you run the poly_packet_forwarder, u can enter “fake” coordinates (make sure you activate GPS and fake_gps in the configuration).

Further, we will extending the json information shortly so you can add “informal information” like ‘location’ and others.
Keep tuned to the github :slight_smile:

1 Like
7

Sounds good Ruud!
Then the next step will be to encourage people to enter that information on the gateway :slight_smile:

8

Me and Thomas discussed it and decided that we will add these three fields:
desc: a general description of the gateway, max 64 chars
mail: should contain the email of the gateway operator, max 32 chars,
pfrm: contains the gateway platform, so Kerlink, Lorank, MultiTech etc, max 32 chars.
I will add these to the forwarders in the coming days, together with some bug fixes.

2 Likes
9

Just a side note, wouldn’t 32 chars for an email be too few for some corporate addresses (e.g. name.surname kind of email user) and/or long domain names? I mean, my corporate address at the regional government is 35 chars long

10

I will think about it. I ran an analysis on my contact list (approx. 700 emails) and less than 1% did not fit in. We must realise that any maximum will be too short for some people, and that this file is send every 30 sec from every gateway. The question is not, will it fit every possible email address out there, but more will anyone be able to supply a contact address that fits. Usually that is a lot easier. But adding a few chars would not be that bad of course.

11

Just wondering if a task like this could not be done by members of this community, so you can concentrate on higher prio tasks. OpenOffice/LibreOffice have been quite successful with leaving small tasks to the community. These says we do have Github which makes it even better manageable.
Just my 2cts (Unfortunately I can not volunteer since I am not a coder)

12

Ruud actually implemented these 3 fields in the packet forwarder, so they can be used.

Now we should add them to croft so they get forwarder to the database/mqtt.

13

@devlaam Although my Kerlinks have a GPS, I’ve activated fake_gps = true and inserted ref_latitude, ref_longitude and ref_altitude, but I see no location in ttnstatus. You mention you need to activate GPS too, in my global config I have “gps_tty_path”: “/dev/nmea”. Is there anything else I need to do?

Plus, how would I get a description in ttnstatus?

14

Check this message

15

Sending email to info@ttnstatus.org yes, did that but got no t-shirt :frowning:

1 Like
16

@Arjan what is the eui? Sometimes people send me their info, but the gateway does not yet show up through the api/ttnstatus and I can’t add a description. In that case I wait a week or so and try again.

17

@Jorma it seems you found it already, AA555A00080605A2 is now having a description :smile:
The number two is AA555A0008060249, please list it as #2. Can you list them as “TTN Flevoland, Voiceworks #1” and “TTN Flevoland, Voiceworks #2” ?

18

Would be great if the gateway status page also had the option of a visual presentation on a map.

Ewald…

4 Likes
19

Have you checked http://ttn.lpwan.uk/ for a map representation?

20

I see the gateway of @pietervn but mine are not listed on that URL… I did set the fake_gps.

21

Looks like the location information is not available, ttsstatus reports:
{"eui":"AA555A0008060249","location":"0,0","status":"up","last_seen":"2015-12-07 22:58:54","remarks":"TTN Flevoland, Voiceworks #2","created_at":"2015-12-03 16:23:53","updated_at":"2015-12-07 23:00:08"},{"eui":"AA555A00080605A2","location":"0,0","status":"up","last_seen":"2015-12-07 22:58:41","remarks":"TTN Flevoland, Voiceworks #1","created_at":"2015-12-03 16:23:53","updated_at":"2015-12-07 23:00:08"},

Looking at the API results for those euis:
{ "status_packets_count": 10332, "eui": "AA555A00080605A2", "altitude": 0.0,** "latitude": 0.0,** "last_seen": "2015-12-07T22:06:11.501Z", "longitude": 0.0 },
and
{ "status_packets_count": 28023, "eui": "AA555A0008060249", "altitude": 0.0, "latitude": 0.0, "last_seen": "2015-12-07T22:05:54.923Z", "longitude": 0.0 },

No location information either…

Have you set (part of gateway_conf):
"ref_latitude": 52.510113, "ref_longitude": 5.479591, "ref_altitude": 8,
as well as "fake_gps": true, ??
(this is just a random coordinate in lelystad)

22

Yep, did all of that. Running the poly_pkt_fwd

23

I reinstalled the gps_pkt_fwd again and this does seem to work correctly, it’s now sending coordinates…

1 Like
24

I tried to draw them on a map with output of
http://www.ttnstatus.org/gateways
How is this output coming in the url above?

used input as below with range of 3 km

52.37283,4.90041,3
52.37361,4.88664,3
52.3599,4.89861,3
52.10208,5.18013,3
52.69021,4.70053,3
59.43799,2.479339,3
50.97113,5.82451,3
52.34184,4.82978,3
51.52865,-.012691,3
51.40736,-.126244,3
53.21388,6.56654,3
52.4551,1.695549,3
52.18331,5.39639,3
52.09296,5.08608,3
52.6309,4.73459,3
50.13998,8.74368,3
52.08967,5.11413,3
53.18977,6.55738,3
52.5,4.956,3
53.1338,6.5676,3
47.40457,8.49659,3
-3.458772,-.5843257,3
51.44103,-.096742,3
52.21333,5.47029,3
52.39776,5.31575,3
-3.379613,1.5121191,3