TTN GATEWAY central 3


I am trying to bring my TTN gateway online. I get stuck in the forth step of activation. What I am currently seeing is LED1 on, LED2 on (online via ethernet cable), LED3 slowly flashing (activating). This goes on for about 1 minute, then reboot of the device and it starts over again.

I have read about the Lora module issue and tried several different fixation methods and also measured contact of the pins between the module and the board. Everything is fine from my point of view. Also the modules LED do shine during the activation.

So I tried to connect to the UART debug port to see what is happening. I have an FTDI-UART-USB converter, I soldered the RX and GND cable to the SUB D connector and connected them to the UART pinout of the TTN Gateway. However, I do see random chars in the terminal (see picture) and no proper text. I even used an osziloscope and verified the baudrate to be 115200.

AND… I have flashed the latest available firmware images from github, but they all behave the same.

What is wrong, please help.


if you have 3 wires connected… switch Rx/Tx

I tried to switch. But if I had connected Tx instead of Rx, I would not see anything, right?

I do see a voltage of 3.3 Volts between GND and RX on the gateway. Can the gateway be changed to 5V?

really ? your lucky if it still works because you put 5V on the UART

Obviously, the FTDI UART converter seems to have a jumper switch for that as seen in this picture from the FAQ. I just wonder if this would make any difference


I got a new version 1.0.6 pushed on May 17th, which apparently might be needed if TTN updates the server certificate some day after July 2019:

With this patch we add the ISRG Root X1 CA to the gateway firmware. After 8 July 2019, many servers that use Let’s Encrypt will start serving a certificate chain which leads to this new root, and therefore it must be trusted by clients such as the gateway.

So, for those not having automatic updates enabled: you’d better do so, I’d assume.

1 Like

Sadly this is only disaster avoidance. I still miss basic functions like disabling WLAN when not needed.

1 Like

Did already somebody tried to re-purpose the mpcie card of the ttn-gateway with a raspberry? There are out some mpcie-hat’s like this one. Electrically this should work. Mechanically the TTN-Card is a bit long but no show-stopper. And since this is basically a modem, maybe there is a chance that this runs with existing Raspberry based gateway software or with minimal tweaking? I will check this later, but maybe somebody has already some know-how to share?

1 Like

Is this still a valid product? That last message makes me think I should save $350. I am new to the LoRaWan world and getting ready to setup a network in Kansas. So I want to spend my money right.

why should you ? sound like buying a whole car only to repurpose the engine :sunglasses:

There are cheaper better products available by now. Check RAKs gateway offerings (plenty about them on the forum)


While i can.
I hate car comparisons. But you started: I have a usable camper trailer but the towing car is no more usable and will be replaced. Or technically: The TTN Kickstarter Gateway is simply not state of the art. Never was. The geeky community gives much love on Raspberry Pi’s as base for their LoRa Gateway. Nobody forked TTN GW code for good. Open sourced code from TTN KS GW has zero evolved. Now there is an update where only a expiring certificate will be replaced. With a RPi i can disable WLAN, i can add PoE,i have a console, a Firewall, IPv6, can do crypto, use VLAN and and and… Like the Multitech Gateway i owned long before the TTN GW was delivered. That’s it.


LOL :rofl:

But to give it some credit, the kickstarter campaign success took a lot of companies by surprise and made them take notice of a market segment they hadn’t noticed before.
A shame the gateway took too long to get to ‘market’ and is more or less a technical dead end due to the technologies used. Too much embedded knowledge required to build and improve the code where there are easier and cheaper options available.


Purchased a RAK… Here goes nothing…

1 Like

In one of our ‘The Things gateways’ -that does not pass the stage of 1 led lit and the second one blinking fast- we see the following serial debug output “dump” (see below)
We are wondering if someone can tell what the “DRV PHY init failed” means, since this seems to be different from all dumps seen before. Looking for similar things on google leads to believe it is something to do with the ethernet chip.
Can anyone give a tip/answer/solution?

We did in the mean time successfully reprogram the PIC32 using MPLAB IPE and a PICkit 3, but that did not help…


after running fine from day one (dec’17) my gateway seems to have issues for no obvious reason nor clear indication on ui-side. it’s shown ‘not connected’ in TTN-console since two days. all LEDs are lit up as usual, /info showing this:


uptime counting up (just powercycled), and even ‘packets up’ is increasing if i’m sending something - where the real strangeness starts:
i can see the packet in the device’s data-stream in console, but not in the gateway’s traffic.

since firmware was last updated in may i assume it must be something on the stack side that changed more recently.

one thing that might be worth mentioning: the gateway’s got a 5 character long ID which was possible to assign back in the days - now it seems to be asking for 6+. but since there was no reason to reset so far it’s still that way.


I’ve put off my TTN gw off from the original box, hoping now it works, seems to be updated to 1.0.7 firmware and I have 2 questions:

  • is the reboot loop definitively solved? was just a software issue?
  • what’s the difference between to bootloader V1 and V2? Do I need to update to V2?


Hello, I’ve been reading posts for a few hours and feel like I’m better understanding the issues surrounding TTN Gateway … and I’m still a little lost. I have a few questions I’m having trouble finding answers for.

I have:

Version Info
Hardware:  v1
Bootloader:  r1-7167873a (2017-06-02T13:48:18Z)
Firmware:  v1.0.0-917719b9 (2017-06-26T17:59:33Z)

I finally got around to booting it up and it connected to Ethernet and showed up on my console immediately! Woohoo!

But …

  1. Is there a Wiki someplace where I can find all of the “pages” available on the device from my local network? Reading various posts I found: http://things-gateway.local/info Are there more?

  2. I see people talking about firmware updates - and obviously mine needs an update - but I’m not seeing a Wiki page or specific instructions on how to force the OTA update they claim exists. Or is my firmware too old to support the OTA? And if I have to use the SD card, where is the Wiki page that explains the process?

I’m fully aware - now - that this is not a real heavy duty gateway, and seems to only sort of work. Seems like most people are moving to other - better supported - solutions. I do want to get the most out of what I have here first, and then move forward to explore what I’ll want to upgrade to.

Thanks in advance.

BTW … how do I get invited to the Slack channel?

I have installed this gateway, which is connected to TTN and fully working properly with my “The Things Node” and test Sketch and also my Raspberry Pi HAT with test python program.

I then fitted an outdoor antenna high on the roof - a Delock Lora 868 omnidirectional antenna fed via about 10 metres of 50 ohm coax.


You can see it perched on the left of the TV aerial.

The gateway continues to work but, having taken the TTN Node for a few local trips, I am most disappointed with the range. Even when I hold the node in my hand, with almost clear “line of sight” to the gateway, the signal strength fades right out beyond a few hundred metres.

OK - it is in an “urban environment” - but LoRa was touted as working over “kilometers” in an urban environment.

Is there a way that I can benchmark test whether the gateway is “getting out” as it should with this external antenna arrangement?

I would be more than happy to provide the gateway ID (suburb of London, England) so that a third party can test access and confirm it is behaving as prescribed.

Any comments or assistance greatly appreciated.