Who is brave enough?
You can restart the whole gateway initiation process by reseting the gateway in case it gets lost (reseting means holding the reset button while powering up), or you can connect using Ethernet. Both are fine in case you lose WiFi. So no real risk here.
After mailing TTN (no reply yet), letting my frustration off to BoRRoz after he removed my post, sorry man! I again took some time to find out what is going on.
I removed the LORA board from the GW and switch it on.
Then it starts with Reboot Reason: 0x03 (which means āpowered on/cyleā I guess) after that it starts rebooting with Reason: 0x10, so this code mean I guess again āno LORA board foundā see first part of log.
Plugged in the LORA board, and low and behold it got online. See second part of log in attachment.
So I went to start configuring my TTN Node again, so I can send my first packet, but alas, after a few minutes the gw started rebooting again, and since I have no TTN coverage I could stop configuring my node.
Could it be that ACKing the Lora board too late (see last part) or no response in time, initiates a reboot?
LORA: Kick LoRa module with ACK after not acked it for 60s
minicom.txt (10.1 KB)
...or click to view the above attachment inline
With LoRa board removed
**************************
* The Things Network *
* G A T E W A Y *
**************************
Firmware name: AmazingAckermann, type: 0, version: 1.0.0, commit: 47310d1b, timestamp: 1513612100
Bootloader revision: 1, commit: 7167873a, timestamp: 1496411298
Build time: Dec 18 2017 16:48:39
Reboot reason: 0x10
BOOT: (persisted info) 6F 72 72 65 01 03 1C 54 18 6F E5 0F 90 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 found: FOTA data present
FLASH: Loading Firmware Data
CNFG: (Firmware HASH (sha256)) 75 E3 BC B7 B1 9D 15 A3 02 84 D8 EA AE 09 02 8F 7C 9A 23 14 79 96 D5 92 61 B9 95 A1 57 A1 AC C0
FLASH: Loading WiFi Data
CNFG: WiFi SSID: Things-Gateway-00HIDDEN
CNFG: WiFi key: ***
CNFG: WiFi conn_type: 4
CNFG: WiFi sec_type: 4
FLASH: Loading Activation Data
CNFG: Gateway ID: mines-gw
CNFG: Gateway Key: ***
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
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
SNTP: State change from 0 to 0
SNTP: State change from 0 to 0
Switched off, inserted LoRa board, and switched on
**************************
* The Things Network *
* G A T E W A Y *
**************************
Firmware name: AmazingAckermann, type: 0, version: 1.0.0, commit: 47310d1b, timestamp: 1513612100
Bootloader revision: 1, commit: 7167873a, timestamp: 1496411298
Build time: Dec 18 2017 16:48:39
Reboot reason: 0x03
BOOT: (persisted info) 6F 72 72 65 01 03 9C 74 18 6F E5 1F 90 00 CC D8
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 found: FOTA data present
FLASH: Loading Firmware Data
CNFG: (Firmware HASH (sha256)) 75 E3 BC B7 B1 9D 15 A3 02 84 D8 EA AE 09 02 8F 7C 9A 23 14 79 96 D5 92 61 B9 95 A1 57 A1 AC C0
FLASH: Loading WiFi Data
CNFG: WiFi SSID: Things-Gateway-00HIDDEN
CNFG: WiFi key: ***
CNFG: WiFi conn_type: 4
CNFG: WiFi sec_type: 4
FLASH: Loading Activation Data
CNFG: Gateway ID: mines-gw
CNFG: Gateway Key: ***
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
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: INET: State change to 3
INET: Ping probe
INET: Error sending probe on WiFi
LORA: Wait init complete, waiting for application.
LORA: Changing state from 1 to 2
SNTP: State change from 2 to 6
MON: SYS Stack size: 3965
MON: heap usage: 147KB (156KB), free: 192KB
ETH: IP Address: 192.168.178.118
INET: Ping Timeout
INET: Ping probe
INET: Error sending probe on WiFi
INET: Ping response from PIC32INT, set as default
INET: State change to 4
SNTP: State change from 6 to 1
INET: Initiated NTP request.
SNTP: State change from 1 to 2
SNTP: State change from 2 to 6
SNTP: State change from 6 to 1
INET: Initiated NTP request.
SNTP: State change from 1 to 2
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 1470 bytes
MON: SYS Stack size: 2847
MON: heap usage: 231KB (233KB), free: 108KB
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
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
MON: SYS Stack size: 2847
MON: heap usage: 152KB (233KB), free: 187KB
LORA: Configuration succeeded
LORA: Starting operation
LORA: Changing state from 4 to 6
LORA: Changing state from 6 to 3
LORA: GOING ASYNC
LORA: Changing state from 3 to 9
CNFG: Load online user config state change to 9
MAIN: Leaving state 3
MAIN: Entering state 4
FLASH: Loading FOTA Data
FIRM: Requesting key ...
HTTP: Starting connection
HTTPS: Connection Opened: Starting TLS Negotiation
HTTP: Wait for TLS Connect
MON: SYS Stack size: 2847
MON: heap usage: 246KB (262KB), free: 92KB
HTTP: TLS Connection Opened: Starting Clear Text Communication
HTTP: Got 568 bytes
HTTP: Connection Closed
HTTP: Close active socket 1
FIRM: Starting download
FIRM: available bytes: 79
FIRM: (Downloaded FOTA key) 75 E3 BC B7 B1 9D 15 A3 02 84 D8 EA AE 09 02 8F 7C 9A 23 14 79 96 D5 92 61 B9 95 A1 57 A1 AC C1
FIRM: (Stored FOTA key) 75 E3 BC B7 B1 9D 15 A3 02 84 D8 EA AE 09 02 8F 7C 9A 23 14 79 96 D5 92 61 B9 95 A1 57 A1 AC C1
FIRM: Firmware is already downloaded
MAIN: No new firmware available
MAIN: Leaving state 4
MAIN: Entering state 5
MQTT: GOT IP: 52.169.76.203
Connecting to: 52.169.76.203
MQTT: Connection Opened: Starting TLS Negotiation
MQTT: Wait for SSL Connect
MQTT: TLS ready: Connect MQTT
RQMQTT: Connected
*************************
MAIN: Gateway bridging
*************************
MQTT: Sending status packet
MQTT: Report reboot error: 0103
MQTT: Sending status succeeded: 0
MON: SYS Stack size: 2847
MON: heap usage: 262KB (266KB), free: 76KB
MON: SYS Stack size: 2847
MON: heap usage: 262KB (266KB), free: 76KB
MON: SYS Stack size: 2847
MON: heap usage: 262KB (266KB), free: 76KB
MQTT: Sending status packet
MQTT: Sending status succeeded: 1
MON: SYS Stack size: 2847
MON: heap usage: 262KB (266KB), free: 76KB
MON: SYS Stack size: 2847
MON: heap usage: 262KB (266KB), free: 76KB
LORA: Kick LoRa module with ACK after not acked it for 60s
MON: SYS Stack size: 2847
MON: heap usage: 262KB (266KB), free: 76KB
MQTT: Sending status packet
MQTT: Sending status succeeded: 2
MON: SYS Stack size: 2847
MON: heap usage: 262KB (266KB), free: 76KB
MON: SYS Stack size: 2847
MON: heap usage: 262KB (266KB), free: 76KB
MON: SYS Stack size: 2847
MON: heap usage: 262KB (266KB), free: 76KB
MQTT: Sending status packet
MQTT: Sending status succeeded: 3
MON: SYS Stack size: 2847
MON: heap usage: 262KB (266KB), free: 76KB
MON: SYS Stack size: 2847
MON: heap usage: 262KB (266KB), free: 76KB
LORA: Kick LoRa module with ACK after not acked it for 60s
MON: SYS Stack size: 2847
MON: heap usage: 262KB (266KB), free: 76KB
MQTT: Sending status packet
MQTT: Sending status succeeded: 4
MON: SYS Stack size: 2847
MON: heap usage: 262KB (266KB), free: 76KB
MON: SYS Stack size: 2847
MON: heap usage: 262KB (266KB), free: 76KB
MON: SYS Stack size: 2847
MON: heap usage: 262KB (266KB), free: 76KB
MQTT: Sending status packet
MQTT: Sending status succeeded: 5
MON: SYS Stack size: 2847
MON: heap usage: 262KB (266KB), free: 76KB
MON: SYS Stack size: 2847
MON: heap usage: 262KB (266KB), free: 76KB
LORA: Kick LoRa module with ACK after not acked it for 60s
MON: SYS Stack size: 2847
MON: heap usage: 262KB (266KB), free: 76KB
MQTT: Sending status packet
MQTT: Sending status succeeded: 6
MON: SYS Stack size: 2847
MON: heap usage: 262KB (266KB), free: 76KB
MON: SYS Stack size: 2847
MON: heap usage: 262KB (266KB), free: 76KB
MON: SYS Stack size: 2847
MON: heap usage: 262KB (266KB), free: 76KB
MQTT: Sending status packet
MQTT: Sending status succeeded: 7
MON: SYS Stack size: 2847
MON: heap usage: 262KB (266KB), free: 76KB
MON: SYS Stack size: 2847
MON: heap usage: 262KB (266KB), free: 76KB
LORA: Kick LoRa module with ACK after not acked it for 60s
MON: SYS Stack size: 2847
MON: heap usage: 262KB (266KB), free: 76KB
MQTT: Sending status packet
MQTT: Sending status succeeded: 8
MON: SYS Stack size: 2847
MON: heap usage: 262KB (266KB), free: 76KB
MON: SYS Stack size: 2847
MON: heap usage: 262KB (266KB), free: 76KB
MON: SYS Stack size: 2847
MON: heap usage: 262KB (266KB), free: 76KB
MQTT: Sending status packet
MQTT: Sending status succeeded: 9
MON: SYS Stack size: 2847
MON: heap usage: 262KB (266KB), free: 76KB
-----------------------STARTING REBOOTING HERE ;-(((
2 Likes
The block of foam is glued to the board, isnāt it? I could lift the board, but only to a certain degree. Unsure how much force one could apply without voiding warranty.
(One could also remove part of the black cover to get better access, which needs one to remove two torx screws hidden behind two of the four bottom cover caps. This makes the PCB come loose, and makes it easy to get the antenna connector out of the way.)
@arjanvanb Yes, itās glued, but if you push up the plastic fasteners and pull out of the slot then itāll be fine. The board will bend a bit. The glue on the LORA board side will loosen. Why they glued it I donāt know; seems like overkill.
- The only WiFi networks shown (for me) are 2.4GHz based, so I think it is save to assume the module does not do 5GHz networks (checked the module specs and it is 2.4 only)
- Your Mac probably has multiple and better WiFi antennas
To mitigate this, I use a router that allows me to set up guest wifi networks.
The router I have allows for up to 4 separate SSIDs - very useful for isolating tech devices on Wifi and has great traffic monitoring capability
1 Like
That seems normal and does not cause a reboot. Iām seeing it in the log of a gateway that has uptime of > 10 hours.
I believe that in the first instance we need a lot more detailed documentation and logging with regards the the procedure the board goes through at startup; with this information the community can then perform some help diagnose of issues and possibly make recommendations based off logs and code. This however needs The Things Network to publish good full documentation detailing status/error codes, given that most backers have waited over two years patiently for the gateways and for them to arrive with what seems on the face of it to be a fundamental issue that could/should have been detected in QA/certification isnāt ideal, but I for one am willing to assist and work through this with other of the community, but we need TTN to
1.acknowlege there is an issues/issues
2.group issues based on symptoms
3.open communications with user forums
4.establish versions of hardware/firmware
and origin of manufacturing that have issues.
all this needs to be public
sorry for the rant, but I feel direction is needed
8 Likes
No luck.
Re-seating the LoRa-board (which by itself already seemed to be seated well) did not help for me, also not when I left out the foam block altogether and applied some more downwards pressure to the board. (The length of the white plastic fasteners makes the board to not be parallel to the main PCB. It seems that thereās quite some pressure on the board, but Iām not an expert.)
Also powering without the board once and re-seating afterwards, did not change things: I still get one or more LORA: Configuration failed, retry, eventually followed by a reboot showing Reboot reason: 0x13 (where Iāve also seen Reboot reason: 0x53.)
As an aside: patience helps to make the glue come loose. Lifting the board will put some tension on the glue, which will come loose slowly. My LG8271 LoRa board says on its bottom side:
LG8501601782
LG-X271
REV: C
I think in my case it started correctly once because I left the gateway untouched for a day or two. That is also one thing I have noticed, it you donāt have it powered on for some them and then do, it seems to connect most of the times once for a short while, and after that it fails every time, until you switch it of for some time again. Strangeā¦
I can put it in an isolated VLAN but most āstandardā users donāt have that option.
But you are correct. Anyone within your network can change the wifi settings of the gateway without authentication.
Hey guys,
is it possible to change the gateways config to send all packages to a private ālora gateway bridgeā? As i mentioned in this post Parking sensor with TTN gateway I like to use parking sensors with the TTN Gateway. The problem is that it is not possible to change the devAddr of the parking sensors, because they are hardcoded (0x70030051).
I installed the lora gateway bridge on a linux machine in my LAN and tried to change the router id of the gateway via
ttnctl gateways edit <GATEWAY_ID> --router-id 192.168.2.121
But I dont receive any up- or downlink at the bridge. After rebooting the gateway it has problems with the config.
Is there a published list of firmware versions and features/fixes anywhere? and a process for manually updating?
does anyone know what the USB socket next to the reset button is for ?
(Iām the author of the LoRa Gateway Bridge / LoRa Server project) I donāt think this is possible. The LoRa Gateway Bridge expects the packet-forwarder UDP protocol. The TTN gateway uses their own Protobuf over MQTT format (if Iām not mistaken).
Thanks for your response.
Do you have an idea how I could use my parking sensors with fix devAddr which be filtered by TTN? Is it possible with the TTN Gateway? Or do I have do buy or build my own gateway and configure the packet forwarder?
Sorry, I donāt know if / how this works with the TTN gateway.
In that case it is a major unacceptable vulnerability, perhaps one the TTN tech guys can comment on this further.