TTN GATEWAY central

[arjanvanb (Arjan)]

No luck registering for me. I’m seeing it fetching the configuration:

CNFG: Load online user config state change to 6
FREQ: APP_URL_Buffer: https://account.thethingsnetwork.org/api/v2/frequency-plans/EU_863_870
HTTP: Starting connection
HTTPS: Connection Opened: Starting TLS Negotiation
HTTP: Wait for TLS Connect
MON: SYS Stack size: 2855
MON: heap usage: 227KB (233KB), free: 111KB
HTTP: TLS Connection Opened: Starting Clear Text Communication
HTTP: Got 1232 bytes
HTTP: Connection Closed
HTTP: Close active socket 1

…but then it logs LORA: Configuration failed, retry (like it did for @mongoose and @mschelter two weeks ago), and seems to restart with Reboot reason: 0x13:

CNFG: Load online user config state change to 7

CNFG: Configuring LoRa module
LORA: Changing state from 2 to 4
LORA: Starting reconfiguration
LORA: version: 01
LORA: Configuration failed, retry
LORA: Starting reconfiguration
LORA: version: 01
LORA: Configuration failed, retry
LORA: Starting reconfiguration
MON: SYS Stack size: 2855
MON: heap usage: 151KB (233KB), free: 188KB
LORA: version: 01
LORA: Configuration failed, retry
LORA: RESET MODULE
LORA: ChaSNTP: State change from 0 to 0
SNTP: State change from 0 to 0

Click for full log

**************************
*   The Things Network   *
*      G A T E W A Y     *
**************************
Firmware name: AmazingAckermann, type: 0, version: 1.0.0, commit: 917719b9, timestamp: 1498499973
Bootloader revision: 1, commit: 7167873a, timestamp: 1496411298
Build time: Jun 26 2017 19:59:53
Reboot reason: 0x13
BOOT: (persisted info) 6F 72 72 65 01 03 83 2C E7 16 05 49 92 3A 54 B7 




WIFI: Entering state 0
WIFI: Entering SCAN state 0

MAIN: Initialisation complete
LORA: Changing state from 0 to 0

MAIN: Leaving state 0
MAIN: Entering state 1
FLASH: Magic bytes found: wifi config present
FLASH: Magic bytes found: activation data present
FLASH: Magic bytes not found: no stored FOTA data present
FLASH: Loading Firmware Data
CNFG: (Firmware HASH (sha256)) FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
FLASH: Loading WiFi Data
CNFG: WiFi SSID:      redacted
CNFG: WiFi key:       redacted
CNFG: WiFi conn_type: 1
CNFG: WiFi sec_type:  4
FLASH: Loading Activation Data
CNFG: Gateway ID:         arjanvanb-gw-1
CNFG: Gateway Key:        ttn-account-v2.W4...redacted...GLyDA
CNFG: Account Server URL: https://account.thethingsnetwork.org
CNFG: Locked:             true
CNFG: Locked first time:  false

MAIN: Leaving state 1
MAIN: Entering state 2
INET: State change to 0
LORA: Initialisation complete
LORA: Changing state from 0 to 1
WIFI: Entering state 1
ETH: IP Address: 0.0.0.0 
WIFI: Entering state 4
WIFI: Entering SCAN state 1
SNTP: State change from 0 to 1
Scan is completed successfully
WIFI: Entering SCAN state 2
WIFI: Entering SCAN state 5
WIFI: Entering SCAN state 0
WIFI: Entering state 2
WIFI: Disabling modules
Head magic match void: trying to free an already freed block, ignore
SNTP: State change from 1 to 1
WIFI: Entering state 3
WIFI: Enabling modules for client
WIFI: Entering state 6


>WIFI: IP Address: 0.0.0.0 
CB: INET: Gateway has WiFi
INET: State change to 2
INET: Connected to a network, waiting for DHCP lease, checking validity with ping
SNTP: State change from 1 to 2
WIFI: IP Address: 192.168.178.53 
LORA: Wait init complete, waiting for application.
LORA: Changing state from 1 to 2
MON: SYS Stack size: 3961
MON: heap usage: 147KB (156KB), free: 192KB
INET: State change to 3
INET: Ping probe
INET: Error sending probe on Eth
INET: Ping response from MRF24WN, set as default
INET: State change to 4
SNTP: State change from 2 to 3
SNTP: State change from 3 to 4
SNTP: State change from 4 to 5
SNTP: State change from 5 to 6
SNTP: State change from 6 to 7
INET: State change to 5

MAIN: Leaving state 2
MAIN: Entering state 3

CNFG: Load online user config state change to 4
HTTP: Close active socket 0
HTTP: Starting connection
HTTPS: Connection Opened: Starting TLS Negotiation
HTTP: Wait for TLS Connect
HTTP: TLS Connection Opened: Starting Clear Text Communication
HTTP: Got 1280 bytes
HTTP: Connection Closed
HTTP: Close active socket 1
CONF: Parsing response token: HTTP/1.1 200 OK
CONF: ROUTER URL: mqtts://bridge.eu.thethings.network:8883

CNFG: Load online user config state change to 6
FREQ: APP_URL_Buffer: https://account.thethingsnetwork.org/api/v2/frequency-plans/EU_863_870
HTTP: Starting connection
HTTPS: Connection Opened: Starting TLS Negotiation
HTTP: Wait for TLS Connect
MON: SYS Stack size: 2855
MON: heap usage: 227KB (233KB), free: 111KB
HTTP: TLS Connection Opened: Starting Clear Text Communication
HTTP: Got 1232 bytes
HTTP: Connection Closed
HTTP: Close active socket 1

CNFG: Load online user config state change to 7

CNFG: Configuring LoRa module
LORA: Changing state from 2 to 4
LORA: Starting reconfiguration
LORA: version: 01
LORA: Configuration failed, retry
LORA: Starting reconfiguration
LORA: version: 01
LORA: Configuration failed, retry
LORA: Starting reconfiguration
MON: SYS Stack size: 2855
MON: heap usage: 151KB (233KB), free: 188KB
LORA: version: 01
LORA: Configuration failed, retry
LORA: RESET MODULE
LORA: ChaSNTP: State change from 0 to 0
SNTP: State change from 0 to 0

TTN Console shows:

Before this loop, I easily got to Step 2 “Connect” and moved on to Step 3, “Configure” while still connected to gateway’s AP. Next, when connected to the internet again in Step 4, “First message” the LEDs loop until 3 continous lights (“Activated”) and I see some LEDs flashing on the LoRaWAN board. I’ve repeated a few times by holding down the reset button while powering up.

@rish

While on step 2 of the activation process - “Connect to the gateways WiFi access point Things-Gateway-XXXX”, make sure to forget the WiFi access point from your computer once you move to step 3. Otherwise it will keep interfering with the gateway.

…@rish, but Step 3 needs this connection, doesn’t it? So, one should only connect to the internet after Step 3?

@Leondegeling

The lora board seemed to be well in place but I found that with a little force I could wiggle it around slightly and push it in just a bit further.

Did you do all that by only removing the white cover, or did you also remove part of the black casing?

@Leondegeling

Can you push gently the LoRa module into it’s socket? En then power cycle the gateway. Maybe even keep a little force on it while running. Just to check if it might be cause by a bad connection.

Any specific place or direction to apply that force?

In my case http://things-gateway/info is accessible on my WiFi network and says Gateway Card: 868Mhz and I see LEDs flashing, so it’s surely (partly) connected.

[Leondegeling]

I just removed the white cover and pushed the loracard a bit further in it connector, however in my case the info-page showed that the lora card was not recognised so I figure on your gateway the loracard is connected correctly.

[arjanvanb (Arjan)]

@comadan

Yesterday it was working fine, but this morning it tries to update the firmware, but when it is done downloading the new one it says it does not match expected size, and then reboots and tries updating again.

If you’re in a hurry getting it running again, then maybe it helps to disable “Automatically update gateway” in TTN Console?

(If it does not, then maybe going back to factory settings first might help? But: I’ve no idea, just things I’d try lacking documentation.)

[bsiege]

Are there any FW updates yet? Cannot find any announcements or release notes.

[frank]

Gateway actived and securely connected, but keeps rebooting.
After a reboot it does not reconnect. After a minute or so all 5 leds will be turned on for a brief moment, followed by some blinking, followed by the next reboot.

[cyberjunky]

So still no joy.

I resetted the wifi and other settings by holding button for 5 secs, after that led 1 on, led 2 flashing, connected with laptop to it’s AP, selected existing gw, selected Wired Internet, during this time got normal looking output on serial like list of local APS etc etc. After clicking ‘Configure’ I got output like below, then after the last line with MON: heap usage, it starts rebooting (showing Reboot reason: 0x43), no serial output anymore. I see all 5 leds on and going off every 5 seconds, and even see LAN status leds going off.

Anyone knows what to do, that Firmware HASH looks silly???
How to proceed, how to contact support, get money back, what are the options???

Click for the full log (Scrambled some private data with XXXX)

**************************
*   The Things Network   *
*      G A T E W A Y     *
**************************
Firmware name: AmazingAckermann, type: 0, version: 1.0.0, commit: 917719b9, timestamp: 1498499973
Bootloader revision: 1, commit: 7167873a, timestamp: 1496411298
Build time: Jun 26 2017 19:59:53
Reboot reason: 0x43
BOOT: (persisted info) 6F 72 72 65 01 03 9C 76 58 6F E5 1F 80 00 CC 58 




WIFI: Entering state 0
WIFI: Entering SCAN state 0

MAIN: Initialisation complete
LORA: Changing state from 0 to 0

MAIN: Leaving state 0
MAIN: Entering state 1
FLASH: Magic bytes found: wifi config present
FLASH: Magic bytes found: activation data present
FLASH: Magic bytes not found: no stored FOTA data present
FLASH: Loading Firmware Data
CNFG: (Firmware HASH (sha256)) FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 
FLASH: Loading WiFi Data
CNFG: WiFi SSID:      Things-Gateway-001EC03XXXXX
CNFG: WiFi key:       thethings
CNFG: WiFi conn_type: 4
CNFG: WiFi sec_type:  4
FLASH: Loading Activation Data
CNFG: Gateway ID:         XXXXXX-gw
CNFG: Gateway Key:        ttn-account-v2.luNjZpepfpB6DoitL32PPqNb9z_zCNmDwoNzZHWaojCM2bbQ7rm5HBdbjpFI8sNfQJpYtcg1PwaXXXXXX
CNFG: Account Server URL: https://account.thethingsnetwork.org
CNFG: Locked:             false
CNFG: Locked first time:  true

MAIN: Leaving state 1
MAIN: Entering state 2
INET: State change to 0
LORA: Initialisation complete
LORA: Changing state from 0 to 1
WIFI: Entering state 1
ETH: IP Address: 0.0.0.0 
WIFI: Entering state 4
WIFI: Entering SCAN state 1
Scan is completed successfully
WIFI: Entering SCAN state 2
WIFI: Entering SCAN state 5
WIFI: Entering SCAN state 0
WIFI: Entering state 2
WIFI: Disabling modules
Head magic match void: trying to free an already freed block, ignore
WIFI: Entering state 3
SNTP: State change from 0 to 1
INET: Gateway has Ethernet
INET: State change to 2
INET: Connected to a network, waiting for DHCP lease, checking validity with ping
WIFI: Enabling modules for server
WIFI: Entering state 6


>WIFI: IP Address: 192.168.84.1 
SNTP: State change from 1 to 2
CB: ETH: IP Address: 192.168.178.118 
INET: State change to 3
INET: Ping probe
INET: Error sending probe on WiFi
INET: Ping response from PIC32INT, set as default
INET: State change to 4
LORA: Wait init complete, waiting for application.
LORA: Changing state from 1 to 2
SNTP: State change from 2 to 3
SNTP: State change from 3 to 4
MON: SYS Stack size: 3967
MON: heap usage: 147KB (156KB), free: 192KB
SNTP: State change from 4 to 5
SNTP: State change from 5 to 6
SNTP: State change from 6 to 7
INET: State change to 5

MAIN: Leaving state 2
MAIN: Entering state 3

CNFG: Load online user config state change to 4
HTTP: Close active socket 0
HTTP: Starting connection
HTTPS: Connection Opened: Starting TLS Negotiation
HTTP: Wait for TLS Connect
HTTP: TLS Connection Opened: Starting Clear Text Communication
HTTP: Got 1282 bytes
CB: HTTP: Connection Closed
HTTP: Close active socket 1
CONF: Parsing response token: HTTP/1.1 200 OK
CONF: ROUTER URL: mqtts://bridge.eu.thethings.network:8883

CNFG: Load online user config state change to 5
FLASH: Lock Activation Data

CNFG: Gateway activation locked

CNFG: Load online user config state change to 6
FREQ: APP_URL_Buffer: https://account.thethingsnetwork.org/api/v2/frequency-plans/EU_863_870
HTTP: Starting connection
HTTPS: Connection Opened: Starting TLS Negotiation
HTTP: Wait for TLS Connect
HTTP: TLS Connection Opened: Starting Clear Text Communication
HTTP: Got 1232 bytes
HTTP: Connection Closed
HTTP: Close active socket 1

CNFG: Load online user config state change to 7

CNFG: Configuring LoRa module
LORA: Changing state from 2 to 4
LORA: Starting reconfiguration
MON: SYS Stack size: 2873
MON: heap usage: 152KB (235KB), free: 187KB

[arjanvanb (Arjan)]

@cyberjunky

that Firmware HASH looks silly???

Not necessarily; the following line:

CNFG: (Firmware HASH (sha256)) FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 

…probably just indicates it’s the factory firmware. As soon as new firmware is available, such new firmware will have a different value and then the gateway knows it needs to update as the values don’t match. After updating the line above will show the hash of the updated firmware. Later, if a second, third, …, update is available, the values will differ again, and the update is repeated with the then current firmware.

[cyberjunky]

I did another attempt this morning , I just plugged in into power and left it observing what it did.
It had another led sequence than before, it even looked like it was updating firmware, connected to internet and cfg ok.

See this output: on /info:

Version Info	
Hardware:	
v1
Bootloader:	
r1-7167873a (2017-06-02T13:48:18Z)
Firmware:	
v1.0.0-917719b9 (2017-06-26T17:59:33Z)
 	
Network	
Uptime:	
181
Connected:	
true
Interface:	
Ethernet
Wifi SSID:	
Things-Gateway-001EC03XXXXX
 	
Configuration	
Activation locked:	
true
Config correct:	
true
Region:	
EU_863_870
Gateway Card:	
868Mhz
 	
Packet forwarding	
Broker connection:	
false
Packets up:	
0
Packets down:	
0
 	
Miscellaneous	
External storage:
false

But after a while it rebooted, and gave this on /info, no sign of newer fw:
And notice the config correct: false and missing gateway card info:

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

Network	
Uptime:	
84
Connected:	
true
Interface:	
Ethernet
Wifi SSID:	
Things-Gateway-001EC03XXXXX

Configuration	
Activation locked:	
true
Config correct:	
false
Region:	
Gateway Card:	
ND

Packet forwarding	
Broker connection:	
false
Packets up:	
0
Packets down:	
0

Miscellaneous	
External storage:	
false

After this (just left it powered on) it start the 5 secs reboot sequence again, like it did since I received it.
Can anyone shed a light on this, what does activation locked mean for example?

What is the official way to get support on this?

[ErwinE (Erwin Homan)]

Received my TTN gateway and some nodes and uno’s recently. Activation of the gateway does not work.

I am following the steps on the activation website. Sometimes, I do see the gateway’s wireless access point from my laptop, sometimes not. According to the status information on the activation portal, I managed to send the wireless network settings to the gateway several times. Have used my regular wireless settings as well as the guest network’s settings in different attempts.

Right after sending the network settings, the gateway appears to reboot. When the guest network settings were used, it reports status “can not connect to the internet”. Probably something in the home router, even though I can not find any limitations. When the regular wireless network settings were used, the gateway goes into the activation process. A few seconds after, it appears to go into error mode (or timeout): all 5 leds active. There is a slow flash (5 seconds all 5 leds on, then about one second all off).

It might be something very simple, but I can not see much. Is there a way to reset it? On the case, there is no button. Would I be able to access it with a console via a wired connection? What are the protocol, default IP-address and credentials?

[ErwinE (Erwin Homan)]

Tried the reset process several times (by keeping the mode-button while switching on power). Also disabled the laptop’s wifi after sending the network settings to the gateway. Still, no change.

Another experiment with a slightly different outcome. Enabled the personal hotspot of my iPhone and sent the hotspot’s network settings to the gateway from my laptop. The gateway goes from “connecting to the internet” to " still activating". On the iPhone, the gateway is visible as hotspot client. The gateway goes through this process about 3 times, and only then goes into an unclear state (all 5 leds in a slow flash). So, this could mean that there is a problem with accessing an address on the internet (like a domain name that can not be resolved). Note that other clients on the hotspot do have access to the internet.

[vanesp]

I received my Backer Edition Gateway today… and after waiting for such a long time, I had to try it out right away…

And… after all these reports of DOA (Dead On Arrival) gateways, I’m happy to report I got mine active in 3 minutes…

And messages are coming through… from a Marvin node repurposed from kpn to TTN

I just wanted to post a positive message for all those people reading about these problems and despairing. Mine worked out of the box. This weekend I’m going to mount it in a more permanent position with an external antenna (Aurel Ground Plan Omnid-directinal antenna on 868 MHz from Conrad) and do some experiments on range.

Regrettably I’m in a “polder” below sea level at -2m and getting my antenna up high is going to be rather difficult (my roof is only +3m and I’m slightly afraid of lightning given I have a thatched roof)…

Peter

[BoRRoZ]

thank you for this positive post… off course we normally only read about problems

[cyberjunky]

Suggestion: Let the backers who have received a DOA gateway visit the The Dutch Things Conference on Thursday, February 1, free of charge. And perhaps an ttn developer can meet us and bring his flash tools to help us out, or at least have a look at what the cause can be.

[BoRRoZ]

that’s a bad plan… everybody from TTN is very very busy that day… did you see the ttn conference program ?

but a bit more attention to this central topic would be very welcome.

[ErwinE (Erwin Homan)]

Thanks for the heads-up, Peter. The term DOA is not really applicable to my TTN-gateway. The activation process can be followed, and I can see the gateway becoming active on the wireless network. Then, completing the activation process (on the internet) seems to fail and the gateway ends up rebooting forever.

It might be time to have a closer look at the wireless network infrastructure used for internet access, because I feel it is going wrong when the activation process connects to the outside world.

I am trying to connect the TTN-gateway to a FRITZ!Box Fon WLAN 7360, which is the wireless access point, network gateway, router, etc for my home network, with XS4ALL as provider. This has a IPv6 public IP-address. There are two wireless networks running, both on 2.4 GHz with a WPA2 personal key.

Can you provide some details about the router and wireless access point you have used to connect the TTN-gateway to the internet?

[arjanvanb (Arjan)]

@BoRRoZ

everybody from TTN is very very busy

Maybe. But the hardware folks from twtg.io (Tweetonig) might not be working on the conference.

[BoRRoZ]

maybe true… I had expected someone from the design team, with deep knowledge of the product(s) more active in this topic, to answer questions and give support.
I know there is personal support in some cases but I would love to see it also here on the forum for everybody to learn.

[vanesp]

Hi ErwinE,

I connected my TTN Gateway via a wired Ethernet port to two different routers on my Ziggo homenetwork. No changes made to the network settings of the Ziggo Technicolor Tc2710 modem. I have a IPv4 public IP address, but changed nothing.

I connected via WiFi (on a MacBook Pro) to the Gateway only to select an Ethernet connection. After starting activation, after a little while the 4 led’s came on. When I moved the Gateway it took a little longer, (after power cycle it looked for a new flash file) but all 4 leds came on again.

Before switching on the Gateway I did check the seating of the Lora module, but it was well inserted.

Peter

[cyberjunky]

I tried with wired and wifi mode with and without update enabled. With new and already existing gw registration. When it starts or just before the boot loops i dont get any meaningful output from serial header.
If there was personal support given what was the outcome or solution in the end? Do the faulty gw’s have different hw revisions or are they shipped with other firmware versions? I can try to wireshark trace stuff. But from the looks of it seems like a hardware issue or watchdog. Or really major software issue. Why would you reboot a device every 5 seconds.