The Things Gateway not forwarding packets

Gateways TTKG - The Things Kickstarter Gateway
1

My TTG has been running for years, successfully moved to V3 about a year ago. 4 days ago all my devices stopped having messages forwared. In the console my GW still kept sending status messages. I went through the configuration routine of the GW, testing different wifi’s. All seems well (config correct: true, broker connected: true), but under " “Packet forwarding” no packets are registrered up or down. I have tested using another antenna. I will take my devices near another GW in my area to confirm they are transmitting, but at least 6 devices stopped having messages forwared at the same time. When I schedule downlinks, I see no response in GW live data. As the GW seems connected to the broker I am unsure what info to share. I think the status messages from GW seems suspicious, only memory usage has a value > 0.

“data”: {
“@type”: “type.googleapis.com/ttn.lorawan.v3.GatewayStatus”,
“time”: “2022-09-21T19:54:49Z”,
“boot_time”: “1970-01-01T00:00:00Z”,
“versions”: {
“platform”: “The Things Gateway v1 - BL r1-7167873a (2017-06-02T13:48:18Z) - Firmware v1.0.9-4510ddac (2022-07-22T11:45:32Z)”,
“model”: “The Things Kickstarter Gateway v1”,
“firmware”: “v1.0.9-4510ddac”
},
“metrics”: {
“load_1”: 0,
“rxin”: 0,
“load_5”: 0,
“temp”: 0,
“load_15”: 0,
“rxok”: 0,
“lmst”: 0,
“lmnw”: 0,
“cpu_percentage”: 0,
“txok”: 0,
“txin”: 0,
“lpps”: 0,
“memory_percentage”: 83.91771,
“lmok”: 0
}

From the device:

Version Info
Hardware: v1
Bootloader: r1-7167873a (2017-06-02T13:48:18Z)
Firmware: v1.0.9-4510ddac (2022-07-22T11:45:32Z)
Network
Uptime: 1589
Connected: true
Interface: WIFI
Wifi SSID: GNX76D825
Configuration
Activation locked: true
Config correct: true
Region: EU_863_870_TTN
Gateway Card: 868Mhz
Packet forwarding
Broker connection: true
Packets up: 0
Packets down: 0
Miscellaneous
External storage:

My plan forward is to use an AirSpy to look for obvious radio pollution @868mHz, and to investigate if the gateway has a serial port I can listen to for diagnostics.

I will happily share more details if you will help me troubleshoot.

1 Like
2

So its a device problem rather than TGW problem? (per title?) - what devices - full details please… are all 6 the same? Comment implies you have more devices… and they are ok?

What are you seeing in the Console GW page?

1 Like
3

Thanks for replying.
I believe it is a GW problem, the devices not having their messages forwarded I believe is just a symptom, just as all your computers would loose connection if you disconnect your router. There is no other GW close enough to my home to have reliable multi-GW coverage, that’s why I have to take a device and travel to be 100% certain messages will be forwarded by another GW. I use a myriad of devices, for instance Rocket Scream Mini Ultra Pro. They have been working for years, until I lost connection with all at the same time 4 days ago.

In the console GW I am seeing “Receive gateway status” every 30 sec, with contents as in the original post, e.i. lot’s of 0 values for metrics. No other types of messages, i.e. no messages tx or rx.

{
“name”: “gs.status.receive”,
“time”: “2022-09-21T20:35:06.364659258Z”,
“identifiers”: [
{
“gateway_ids”: {
“gateway_id”: “prometheus”
}
}
],
“data”: {
“@type”: “type.googleapis.com/ttn.lorawan.v3.GatewayStatus”,
“time”: “2022-09-21T20:35:08Z”,
“boot_time”: “1970-01-01T00:00:00Z”,
“versions”: {
“model”: “The Things Kickstarter Gateway v1”,
“firmware”: “v1.0.9-4510ddac”,
“platform”: “The Things Gateway v1 - BL r1-7167873a (2017-06-02T13:48:18Z) - Firmware v1.0.9-4510ddac (2022-07-22T11:45:32Z)”
},
“metrics”: {
“temp”: 0,
“rxin”: 0,
“lmnw”: 0,
“load_15”: 0,
“lpps”: 0,
“txin”: 0,
“memory_percentage”: 83.91771,
“lmst”: 0,
“lmok”: 0,
“cpu_percentage”: 0,
“rxok”: 0,
“load_1”: 0,
“txok”: 0,
“load_5”: 0
}
},
“correlation_ids”: [
“gs:conn:01GDGRS9VYX4W90A5QTVAYRE5K”,
“gs:status:01GDGW5SFWSYQDYWFV924VPFT8”
],
“origin”: “ip-10-100-13-127.eu-west-1.compute.internal”,
“context”: {
“tenant-id”: “CgN0dG4=”
},
“visibility”: {
“rights”: [
“RIGHT_GATEWAY_STATUS_READ”
]
},
“unique_id”: “01GDGW…”
}

1 Like
4

If I check the following sites, your gateway seems up

id=prometheus

gateways

5

Dont be fooled by this - I see lots of zeros in the Metrics also… fact you are atleast seeing the status messages suggests high probably all good with GW and connection to back end… no data from any devices getting through (check individual device detail pages)?

Status from one of mine for comparison:

  "name": "gs.status.receive",
  "time": "2022-09-21T20:44:16.234256318Z",
  "identifiers": [
    {
      "gateway_ids": {
        "gateway_id": "g-s3-testgw001-ttkgw-hp10"
      }
    }
  ],
  "data": {
    "@type": "type.googleapis.com/ttn.lorawan.v3.GatewayStatus",
    "time": "2022-09-21T20:44:18Z",
    "boot_time": "1970-01-01T00:00:00Z",
    "versions": {
      "firmware": "v1.0.9-4510ddac",
      "platform": "The Things Gateway v1 - BL r1-7167873a (2017-06-02T13:48:18Z) - Firmware v1.0.9-4510ddac (2022-07-22T11:45:32Z)",
      "model": "The Things Kickstarter Gateway v1"
    },
    "metrics": {
      "lmst": 0,
      "cpu_percentage": 0,
      "lmok": 0,
      "lmnw": 0,
      "txok": 0,
      "txin": 0,
      "rxin": 1338,
      "temp": 0,
      "lpps": 0,
      "memory_percentage": 84.95543,
      "load_1": 0,
      "load_15": 0,
      "rxok": 1338,
      "load_5": 0
    }
  },
  "correlation_ids": [
    "gs:conn:01GDGGPNTTXG2FQVZVDTG6G1GT",
    "gs:status:01GDGWPJFA0QM2MKTC1SFH5G5H"
  ],
  "origin": "ip-10-100-4-241.eu-west-1.compute.internal",
  "context": {
    "tenant-id": "CgN0dG4="
  },
  "visibility": {
    "rights": [
      "RIGHT_GATEWAY_STATUS_READ"
    ]
  },
  "unique_id": "01GDGWPJFAJR598VGXFMMT43DE"
1 Like
6

I just confirmed my end nodes are working as expected by bringing some of them within range of another GW. So the problem is situated with the gateway. Any ideas?

1 Like
7

Looks like the receive-path is broken. This can be caused by eg. antenna, antenna-connector, cable between connector and circuit board , receiver destroyed by ESD or nearby lightning…
Do you use an external antenna on the roof? Does the gateway receive any near-by nodes?
Or a firmware -problem: does the gateway still use the right frequencies and parameters?

1 Like
8

I have tested the antenna, will attach a spectrum analyzation next. I changed to a simpler antenna, also checked.
I started logging serial output from the GW and am worried about the following:
LORA: Kick LoRa module with ACK after not acked it for 60s
It keeps repeating.
I have not been able to find a description of the LG8271 status leds, anyone know where to find it?
The GW is rebooting a lot now, typically with Reboot reason: 0x10. Also:
MQTT: Sending status failed
MAIN: MQTT error

1 Like
9
  • The Things Network *
  •  G A T E W A Y     *

Firmware name: AmazingAckermann, type: 0, version: 1.0.9, commit: 4510ddac, timestamp: 1658490332
Bootloader revision: 1, commit: 7167873a, timestamp: 1496411298
Build time: Jul 22 2022 11:46:27
Reboot reason: 0x03
BOOT: (persisted info) 6F 72 72 65 01 03 25 94 6D 67 7E 52 11 31 4B 16

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)) 50 82 79 E3 5B E2 15 C1 5F AB BA F4 03 78 1E E5 B7 01 37 A0 F0 56 DB D1 AC 7D EB 26 99 C5 C4 60
FLASH: Loading WiFi Data
CNFG: WiFi SSID: GNX76D825
CNFG: WiFi key: ***
CNFG: WiFi conn_type: 1
CNFG: WiFi sec_type: 4
FLASH: Loading Activation Data
CNFG: Gateway ID: prometheus
CNFG: Gateway Key: ***
CNFG: Account Server URL: https://eu1.cloud.thethings.network/
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 2
WIFI: Disabling modules
Head magic match void: trying to free an already freed block, ignore
WIFI: Entering state 3
15:16:08: WIFI: Enabling modules for client
WIFI: Entering state 6

WIFI: IP Address: 0.0.0.0
SNTP: State change from 0 to 1
15:16:13: 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
LORA: Wait init complete, waiting for application.
LORA: Changing state from 1 to 2
15:16:16: MON: SYS Stack size: 3965
MON: TCPIP Stack size: 3828
MON: APP Stack size: 8008
MON: LoRa Stack size: 3909
MON: heap usage: 179KB (188KB), free: 160KB
15:16:18: INET: State change to 3
INET: Ping probe
INET: Error sending probe on Eth
SNTP: State change from 2 to 6
15:16:22: WIFI: IP Address: 192.168.1.245
15:16:26: MON: SYS Stack size: 3959
MON: TCPIP Stack size: 3828
MON: APP Stack size: 7987
MON: LoRa Stack size: 3909
MON: heap usage: 179KB (188KB), free: 160KB
15:16:34: SNTP: State change from 6 to 1
15:16:35: SNTP: State change from 1 to 2
15:16:36: SNTP: State change from 2 to 3
MON: SYS Stack size: 3959
MON: TCPIP Stack size: 3787
MON: APP Stack size: 7987
MON: LoRa Stack size: 3909
MON: heap usage: 179KB (188KB), free: 160KB
15:16:37: SNTP: State change from 3 to 4
15:16:38: SNTP: State change from 4 to 5
SNTP: State change from 5 to 6
SNTP: State change from 6 to 7
15:16:46: MON: SYS Stack size: 3959
MON: TCPIP Stack size: 3787
MON: APP Stack size: 7987
MON: LoRa Stack size: 3909
MON: heap usage: 180KB (188KB), free: 160KB
15:16:56: MON: SYS Stack size: 3959
MON: TCPIP Stack size: 3620
MON: APP Stack size: 7987
MON: LoRa Stack size: 3909
MON: heap usage: 180KB (188KB), free: 160KB
15:17:06: MON: SYS Stack size: 3959
MON: TCPIP Stack size: 3607
MON: APP Stack size: 7987
MON: LoRa Stack size: 3909
MON: heap usage: 180KB (188KB), free: 160KB
15:17:16: MON: SYS Stack size: 3959
MON: TCPIP Stack size: 3589
MON: APP Stack size: 7987
MON: LoRa Stack size: 3909
MON: heap usage: 180KB (188KB), free: 160KB
15:17:18: INET: Ping Timeout of :60 seconds
INET: Ping probe
INET: Error sending probe on Eth
INET: Ping response from MRF24WN, set as default
INET: State change to 4
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 1077 bytes
15:17:24: HTTP: Connection Closed
HTTP: Close active socket 1
CONF: Parsing response token: HTTP/1.1 200 OK
CONF: ROUTER URL: mqtts://eu1.cloud.thethings.network:8881

CNFG: Load online user config state change to 6
15:17:26: FREQ: APP_URL_Buffer: https://eu1.cloud.thethings.network/api/v2/frequency-plans/EU_863_870_TTN
HTTP: Starting connection
MON: SYS Stack size: 2845
MON: TCPIP Stack size: 3581
MON: APP Stack size: 3249
MON: LoRa Stack size: 3909
MON: heap usage: 193KB (272KB), free: 146KB
HTTPS: Connection Opened: Starting TLS Negotiation
HTTP: Wait for TLS Connect
HTTP: TLS Connection Opened: Starting Clear Text Communication
HTTP: Got 1680 bytes
15:17:32: 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 3
LORA: Starting reconfiguration
LGMD:Answer, cmd: 0x31, size: 1
[00]LGMD:Answer, cmd: 0x31, size: 1
LGMD:Command, cmd: 0x3A, size: 0
LGMD:Answer, cmd: 0x3A, size: 16
Version, hwrev: 1, major: 1, minor: 4, band: 1
Serial: 4C-47-38-35-30-31-36-30-31-36-37-31
LGMD:Command, cmd: 0x34, sie: 1
[00]LGMD:Answer, cmd: 0x34, size: 1
LGMD:Command, cmd: 0x34, sie: 1
[00]LGMD:Answer, cmd: 0x34, size: 1
LGMD:Command, cmd: 0x35, sie: 1
[00]LGMD:Answer, cmd: 0x35, size: 1
LGMD:Command, cmd: 0x35, sie: 1
[00]LGMD:Answer, cmd: 0x35, size: 1
LGMD:Command, cmd: 0x35, sie: 1
[00]LGMD:Answer, cmd: 0x35, size: 1
LGMD:Command, cmd: 0x35, sie: 1
[00]LGMD:Answer, cmd: 0x35, size: 1
LGMD:Command, cmd: 0x35, sie: 1
[00]LGMD:Answer, cmd: 0x35, size: 1
15:17:33: LGMD:Command, cmd: 0x35, sie: 1
[00]LGMD:Answer, cmd: 0x35, size: 1
LGMD:Command, cmd: 0x35, sie: 1
[00]LGMD:Answer, cmd: 0x35, size: 1
LGMD:Command, cmd: 0x35, sie: 1
[00]LGMD:Answer, cmd: 0x35, size: 1
LGMD:Command, cmd: 0x36, sie: 1
[00]LGMD:Answer, cmd: 0x36, size: 1
15:17:36: MON: SYS Stack size: 2845
MON: TCPIP Stack size: 3581
MON: APP Stack size: 3249
MON: LoRa Stack size: 3857
MON: heap usage: 189KB (273KB), free: 149KB
15:17:41: SNTP: State change from 0 to 0
SNTP: State change from 0 to 0

  • The Things Network *
  •  G A T E W A Y     *

Firmware name: AmazingAckermann, type: 0, version: 1.0.9, commit: 4510ddac, timestamp: 1658490332
Bootloader revision: 1, commit: 7167873a, timestamp: 1496411298
Build time: Jul 22 2022 11:46:27
Reboot reason: 0x10
BOOT: (persisted info) 6F 72 72 65 01 03 25 94 6D 67 7E 52 11 31 4B 16

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)) 50 82 79 E3 5B E2 15 C1 5F AB BA F4 03 78 1E E5 B7 01 37 A0 F0 56 DB D1 AC 7D EB 26 99 C5 C4 60
FLASH: Loading WiFi Data
CNFG: WiFi SSID: GNX76D825
CNFG: WiFi key: ***
CNFG: WiFi conn_type: 1
CNFG: WiFi sec_type: 4
FLASH: Loading Activation Data
CNFG: Gateway ID: prometheus
CNFG: Gateway Key: ***
CNFG: Account Server URL: https://eu1.cloud.thethings.network/
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 2
WIFI: Disabling modules
Head magic match void: trying to free an already freed block, ignore
WIFI: Entering state 3
15:17:43: WIFI: Enabling modules for client
WIFI: Entering state 6

WIFI: IP Address: 0.0.0.0
SNTP: State change from 0 to 1
15:17:48: 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
LORA: Wait init complete, waiting for application.
LORA: Changing state from 1 to 2
15:17:51: MON: SYS Stack size: 3959
MON: TCPIP Stack size: 3828
MON: APP Stack size: 7999
MON: LoRa Stack size: 3911
MON: heap usage: 179KB (188KB), free: 160KB
15:17:52: CB: INET: State change to 3
INET: Ping probe
INET: Error sending probe on Eth
15:17:54: SNTP: State change from 2 to 6
15:17:57: WIFI: IP Address: 192.168.1.245
15:18:01: MON: SYS Stack size: 3959
MON: TCPIP Stack size: 3619
MON: APP Stack size: 7987
MON: LoRa Stack size: 3911
MON: heap usage: 179KB (188KB), free: 160KB
15:18:08: SNTP: State change from 6 to 1
15:18:09: SNTP: State change from 1 to 2
15:18:11: MON: SYS Stack size: 3959
MON: TCPIP Stack size: 3603
MON: APP Stack size: 7987
MON: LoRa Stack size: 3911
MON: heap usage: 179KB (188KB), free: 160KB
15:18:15: SNTP: State change from 2 to 3
15:18:16: SNTP: State change from 3 to 4
15:18:17: SNTP: State change from 4 to 5
SNTP: State change from 5 to 6
SNTP: State change from 6 to 7
15:18:21: MON: SYS Stack size: 3959
MON: TCPIP Stack size: 3597
MON: APP Stack size: 7987
MON: LoRa Stack size: 3911
MON: heap usage: 180KB (188KB), free: 160KB
15:18:31: MON: SYS Stack size: 3959
MON: TCPIP Stack size: 3589
MON: APP Stack size: 7987
MON: LoRa Stack size: 3911
MON: heap usage: 180KB (188KB), free: 160KB
15:18:41: MON: SYS Stack size: 3959
MON: TCPIP Stack size: 3589
MON: APP Stack size: 7987
MON: LoRa Stack size: 3911
MON: heap usage: 180KB (188KB), free: 160KB
15:18:51: MON: SYS Stack size: 3959
MON: TCPIP Stack size: 3589
MON: APP Stack size: 7987
MON: LoRa Stack size: 3911
MON: heap usage: 180KB (188KB), free: 160KB
15:18:53: INET: Ping Timeout of :60 seconds
INET: Ping probe
INET: Error sending probe on Eth
INET: Ping response from MRF24WN, set as default
INET: State change to 4
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 1076 bytes
15:18:59: HTTP: Connection Closed
HTTP: Close active socket 1
CONF: Parsing response token: HTTP/1.1 200 OK
CONF: ROUTER URL: mqtts://eu1.cloud.thethings.network:8881

CNFG: Load online user config state change to 6
15:19:01: FREQ: APP_URL_Buffer: https://eu1.cloud.thethings.network/api/v2/frequency-plans/EU_863_870_TTN
HTTP: Starting connection
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3581
MON: APP Stack size: 3269
MON: LoRa Stack size: 3911
MON: heap usage: 193KB (273KB), free: 146KB
HTTPS: Connection Opened: Starting TLS Negotiation
HTTP: Wait for TLS Connect
HTTP: TLS Connection Opened: Starting Clear Text Communication
HTTP: Got 1680 bytes
15:19:07: 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 3
LORA: Starting reconfiguration
LGMD:Answer, cmd: 0x31, size: 1
[00]LGMD:Answer, cmd: 0x31, size: 1
LGMD:Command, cmd: 0x3A, size: 0
LGMD:Answer, cmd: 0x3A, size: 16
Version, hwrev: 1, major: 1, minor: 4, band: 1
Serial: 4C-47-38-35-30-31-36-30-31-36-37-31
LGMD:Command, cmd: 0x34, sie: 1
[00]LGMD:Answer, cmd: 0x34, size: 1
LGMD:Command, cmd: 0x34, sie: 1
[00]LGMD:Answer, cmd: 0x34, size: 1
LGMD:Command, cmd: 0x35, sie: 1
[00]LGMD:Answer, cmd: 0x35, size: 1
LGMD:Command, cmd: 0x35, sie: 1
[00]LGMD:Answer, cmd: 0x35, size: 1
LGMD:Command, cmd: 0x35, sie: 1
[00]LGMD:Answer, cmd: 0x35, size: 1
LGMD:Command, cmd: 0x35, sie: 1
[00]LGMD:Answer, cmd: 0x35, size: 1
15:19:08: LGMD:Command, cmd: 0x35, sie: 1
[00]LGMD:Answer, cmd: 0x35, size: 1
LGMD:Command, cmd: 0x35, sie: 1
[00]LGMD:Answer, cmd: 0x35, size: 1
LGMD:Command, cmd: 0x35, sie: 1
[00]LGMD:Answer, cmd: 0x35, size: 1
LGMD:Command, cmd: 0x35, sie: 1
[00]LGMD:Answer, cmd: 0x35, size: 1
LGMD:Command, cmd: 0x36, sie: 1
[00]LGMD:Answer, cmd: 0x36, size: 1
LGMD:Command, cmd: 0x37, sie: 1
[00]
LGMD:Answer, cmd: 0x37, size: 1
LGMD:Command, cmd:0x40, size: 1
[00]LGMD:Answer, cmd: 0x40, size: 1
LGMD:Command, cmd:0x31, size: 1
[00]LGMD:Answer, cmd: 0x31, size: 1
LGMD:Command, cmd: 0x30, size: 0
15:19:09: LGMD:Answer, cmd: 0x30, size: 1
LORA: configLora OK
LORA: Configuration succeeded
LORA: Starting operation
LORA: Changing state from 3 to 4
15:19:11: MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3581
MON: APP Stack size: 3269
MON: LoRa Stack size: 3855
MON: heap usage: 189KB (273KB), free: 149KB
15:19:16: LORA: Changing state from 4 to 5

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
15:19:17: HTTP: TLS Connection Opened: Starting Clear Text Communication
HTTP: Got 515 bytes
15:19:19: HTTP: Connection Closed
HTTP: Close active socket 1
FIRM: Starting download
FIRM: available bytes: 79
FIRM: (Downloaded FOTA key) 50 82 79 E3 5B E2 15 C1 5F AB BA F4 03 78 1E E5 B7 01 37 A0 F0 56 DB D1 AC 7D EB 26 99 C5 C4 60
FIRM: (Stored FOTA key) 50 82 79 E3 5B E2 15 C1 5F AB BA F4 03 78 1E E5 B7 01 37 A0 F0 56 DB D1 AC 7D EB 26 99 C5 C4 60
FIRM: Firmware is already downloaded
MAIN: No new firmware available

MAIN: Leaving state 4
MAIN: Entering state 5
MQTT: GOT IP: 63.34.215.128
Connecting to: 63.34.215.128
MQTT: Connection Opened: Starting TLS Negotiation
MQTT: Wait for SSL Connect
15:19:20: 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: 2837
MON: TCPIP Stack size: 3581
MON: APP Stack size: 3269
MON: LoRa Stack size: 3855
MON: heap usage: 284KB (284KB), free: 54KB
15:19:31: MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3581
MON: APP Stack size: 3269
MON: LoRa Stack size: 3855
MON: heap usage: 284KB (287KB), free: 54KB
15:19:41: MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3581
MON: APP Stack size: 3269
MON: LoRa Stack size: 3855
MON: heap usage: 284KB (287KB), free: 54KB
15:19:50: MQTT: Sending status packet
MQTT: Sending status succeeded: 1
MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3581
MON: APP Stack size: 3269
MON: LoRa Stack size: 3855
MON: heap usage: 284KB (287KB), free: 54KB
15:20:01: MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3581
MON: APP Stack size: 3269
MON: LoRa Stack size: 3855
MON: heap usage: 284KB (287KB), free: 54KB
15:20:11: MON: SYS Stack size: 2837
MON: TCPIP Stack size: 3581
MON: APP Stack size: 3269
MON: LoRa Stack size: 3855
MON: heap usage: 284KB (287KB), free: 54KB
15:20:15: LORA: Kick LoRa module with ACK after not acked it for 60s
15:20:20: MQTT: Sending status packet
MQTT: Sending status succeeded: 2

1 Like
10

Looks like it is connecting ok to the back end. per Johan may be a receive path issue. Are there any devices where you can send a downlink to check TX path? besides internal fails or externally induced fails (e.g. near proximity lightning strike) this system had early problems with module mounting/connector issues…perhaps temp cycling or time/corrosion has impacted. Have you tried extracting the concentrator module and then re-inserting? Please give that a go and let us know any changes…

What is the LED Status on front panel? You should see 4 solid green with 5th blinking briefly based on occasional Rx data.

1 Like
11

On tx there is no response in the serial debug nor GW console when I schedule downlink.
I extracted the concentrator and cleaned the connectors. I checked them in pairs with the connector pads on the motherboard for continuity, all well. On the concentrator led 4 is red, led 1 is green. If anyone knows their significance, that would be great to know. Or just check what leds are lit on a working TTKG. Leds on the motherboard are as expected: 4 solid, 5th blinking on status uplink. No blinking on device tx, though.

1 Like
12

Hummn, could just be that the card has failed as everything else seems normal. I have had 3 GW’s fail over a 7 year period (all different types, but all old SX1301 based like the TKGW) so depending on age of unit may just be random wareout?! When bought? Still under warranty?

Guess not :frowning:

One thing you cant check for I guess was has there been a close proximity lightning strike - this can render units deaf without showing signs of actual burn out? Has unit ever been run without Antenna attached? can also induce potential latent weakness if not immediate burn out, of the front end as can ESD…

1 Like
13

You are probably right, but I thought I’d give it a shot in finding the point of error. On the point of downlink: my understanding was that the broker would retain scheduled downlinks and only fetch them when a GW receives a tx from a device and a downlink window is established. So I wouldn’t think that scheduling a downlink in the console would immediately signal a GW. Is so, how would the broker know what GW to message?

Anyway, I got different leds on the concentrator when I pressed it down - led 1 and 5 solid green. Still have no idea what they mean, and I am still getting the same lack of transmission looking at the debug output. It would be great if anyone with the same GW could report what leds their concentrators display after initialization.

1 Like
14

Will go pop the cover on one of mine and check after supper :slight_smile: !

1 Like
15

That would be great!
Judging on older (2018) GW logs the “LORA: Kick LoRa module with ACK after not acked it for 60s” seems normal, probably keeping it from entering low-power state or something. I should however have seen something like:
LORA: Accepted packet
MQTT: Sending UPLINK OK

1 Like
16

Ok firstly my bad - its 4 blue not green of course on front panel (S.East) steady with 5th blinking on traffic looking at the pseudo random pattern probably reflecting the dozen plus sensors it can hear close by…

Card has 1 green, there is another green just off board at N.East, a blue at West and 3 green distributed along South side of main board (too dark for me to go looking at board markings to see labeling…)

1 Like
17

Thanks for checking it out.
Judging by the apparent random state of the concentrator leds (sometimes red, sometimes weakly lit etc) I have accepted that the concentrator might be dead. Have ordered a new GW, was looking for an excuse to go 16 channel anyway :slight_smile: Might look for a replacement concentrator in hope of expanding coverage. Thanks for all the input!

1 Like
18

Hummn :thinking: have you checked board power…could be a power feed issue?! A capacitor or regulator just as likely to die as the main card…might be worth measuring around the board/looking for an obvious failed/failing component…

If you want to consider a direct replacement DM me as I still have a few TKGW’s in personal/consulting stock (new, boxed) - not sure where you are for shipping/import costs etc…(Norway?), mine run fine since 1st deployed at start of 2018 baring the odd power outage and relocation for site tests hence keep a few for community users, onward sales etc.

2 Likes
19

I will probably poke around the components as some point, but with no real lead or schematic this can be quite time consuming. Thanks for the offer, but as I have already ordered a new GW I am set for the time being.

1 Like
20

Do you have it as indoor or outdoor gateway?

Especially if it is outdoors check the antenna and if you have coax between gateway and antenna, the coax for continuity or short.