Which low cost gateway has GPS timestamp?

I need a full LoRaWAN compliant 8ch gateway which has GPS and sends timestamp with absolute UTC in metadata to TTN server.

Currently i am using a MatchX1701 with legacy semtech packet forwarder. This works, but i want a second gateway.

What are my options for a gateway that is

  • ready out of the box (means no hardware tinkering required)
  • below EUR 250
  • TTN compatible (at least without major tinkering)
  • sends timestamp ?

Indoor is satisfying, semi-outdoor would be a bonus.

TTIG and LorixOne currently don’t send timestamp.
What about the IMST?

I would also been intersted in knowing which (if any) gateways with GPSs deals with the leap seconds issue correctly.

When a GPS is first powered on an gets a fix, then the secons boundary, from 1PPS, should be within tens of nS. However the time the GPS shows will only be correct when its had an over the air update of the current value of leap seconds. This can take up to 12.5 minutes from the GPS powering on, and there is always to potential for that update to be missed.


TTIG (“after the bugs are fixed”)?

ttig doesn’t have gps.

maybe this one fits

That is ambitious even for a high end GPS with OXCO… .Wich will cost alone much more than a “low cost LoRa gateway”

Maybe, but the datasheets of standard GPSs claim circa 30nS, although since I have no way of verifying it, could be fake news.

30nS is 9m.

TTIG with working NTP would be suitable for me, GPS not a must.

9m in vacuum… much less in electrical cable.Typical velocity factors

Sorry to be picky about that, but building NTP devices is some kind of sports and there are many factors to note. I know, you guys want to build location services for LoRa, but even for a Indoor Gateway, there will be too much temperature differences to get accurate results over time.

I doubt it… bad resolution

Not a location service, just a time service with precision +/- 500ms.

I was aware of the variations in velocity factors in cable, I spent 15 years installing LANs, when I started I built my own TDR gear for measuring cables.

The leap second ‘problem’ is not an issue that should affect TTN localisation, as long as the timing goes from the 1PPS edge.

Although my self I wonder if it will be possible to time arrival of packets (to do localisation) to with say the required 333nS to get even 100m accuracy.

Ouch… ok, sorry. That should be less a problem.
:roll_eyes: Why we discuss about PPS nanosecond accuracy, when we need absolute timestamps, gained probably from UART? :clock1: I think for this the Mikrotik Gateways could be a step forward, because they have OS support for GPS disciplined NTP on board, although not pps. Also Multitech has NTP
And for your demands NTP on the receiving gateway over the backhaul network like pool.ntp.org should be accurate enough.

And not to forget about raspberry pi based gateways under some linux. There you can use pps. But there is much tuning needed according to temperature and workload. Good examples here. And Here.

Well, allright - but is there a suitable gateway out of the box which sends timestamps, generated either by GPS with PPS (but not without), or NTP? Besides MatchX 1701?

may be you can try this one, they have an amazing firmware with integrated LoRa server on it (but no GPS). I’m always wondering if adding cheap USB GPS device could works as expected?

Last but not least, $149 and if you want 4G add $100, not bat :wink:

Interesting unit, thanks für the hint.

What about Dragino LG308, does anyone here know if it sends timestamps?

LoRa Spec:
1 x SX1308+2 x 1257 LoRa Tranceiver
1 x SX1276 LoRa Tranceiver
1 x GPS module for LoRa localization

Dragino spec does not list GPS.

I always missed this LinkLab Shield, GW and GPS, simple and efficient



There are two issues: first the firmware doesn’t support it, though you could build your own firmware from their open source repos for earlier kits which would.

The other is that you need the PPS connection from the GPS to the SX1301 chip. Probably you could modify the board to insert that.

And then you probably don’t want a laggy USB interface, but rather to use a hardware UART. The console one is definitely exposed, it looks like one of the others is but you probably have to rebuild the kernel to make it actually work: https://github.com/RAKWireless/WisCore/wiki/Introduce-uart

If the UART is running at 115200 baud then a single character takes 8.6us to send.

That represents a distance of 2.6km.