Closed avbentem closed 6 years ago
I upgraded this afternoon to Firmware name: AmazingAckermann, type: 0, version: 1.0.3, commit: 2c56ce09, timestamp: 1522846485
and see LORA errors, after the first reboot a time-out (never seen this before) not an improvement, actually worse as before ....
2018-04-04 17:45:45.375022 LORA: UART TIMEOUT
2018-04-04 17:45:45.375061 LORA: Configuration succeeded
2018-04-04 17:45:45.375065 LORA: Starting operation
2018-04-04 17:45:45.375068 LORA: Changing state from 6 to 8
2018-04-04 17:45:51.436553 LORA: Changing state from 8 to 5
2018-04-04 17:45:51.436590 LORA: GOING ASYNC
2018-04-04 17:45:51.436594 LORA: Changing state from 5 to 11
2018-04-04 17:46:51.734110 LORA: Kick LoRa module with ACK after not acked it for 60s
2018-04-04 17:47:52.067410 LORA: Kick LoRa module with ACK after not acked it for 60s
2018-04-04 17:48:52.414499 LORA: Kick LoRa module with ACK after not acked it for 60s
2018-04-04 17:49:52.769109 LORA: Kick LoRa module with ACK after not acked it for 60s
2018-04-04 17:50:53.112584 LORA: Kick LoRa module with ACK after not acked it for 60s
2018-04-04 17:51:53.474841 LORA: Kick LoRa module with ACK after not acked it for 60s
2018-04-04 17:52:53.840829 LORA: Kick LoRa module with ACK after not acked it for 60s
2018-04-04 17:53:54.176918 LORA: Kick LoRa module with ACK after not acked it for 60s
2018-04-04 17:54:54.528266 LORA: Kick LoRa module with ACK after not acked it for 60s
2018-04-04 17:55:54.879097 LORA: Kick LoRa module with ACK after not acked it for 60s
2018-04-04 17:56:55.245150 LORA: Kick LoRa module with ACK after not acked it for 60s
2018-04-04 17:57:55.618957 LORA: Kick LoRa module with ACK after not acked it for 60s
2018-04-04 17:58:55.996203 LORA: Kick LoRa module with ACK after not acked it for 60s
2018-04-04 17:59:56.358381 LORA: Kick LoRa module with ACK after not acked it for 60s
2018-04-04 18:00:56.732491 LORA: Kick LoRa module with ACK after not acked it for 60s
2018-04-04 18:01:57.104779 LORA: Kick LoRa module with ACK after not acked it for 60s
2018-04-04 18:02:57.456434 LORA: Kick LoRa module with ACK after not acked it for 60s
2018-04-04 18:03:57.816745 LORA: Kick LoRa module with ACK after not acked it for 60s
2018-04-04 18:04:58.188847 LORA: Kick LoRa module with ACK after not acked it for 60s
Today things were not resolved by pressing the Mode button. Instead, it needed a power cycle, after which it started to receive LoRa packets again. Again, the gateway was running just fine until the failure was initiated by a firmware upgrade check. I did not check the LEDs on the board. It's running 1.0.3 (commit: 2c56ce0, timestamp: 1521721252, Build time: Mar 22 2018 12:21:52) from an SD card, as 1.0.4 gives me a reboot loop.
Full logs, all timestamps added by a Raspberry Pi that monitors the serial output:
If my notes don't fail me, then since my May 12th comment I've pressed the Mode button to resolve this problem:
So today it was again running fine until it did its daily reboot for a firmware upgrade check, after which the LoRa module just failed to receive any LoRa packets. Today I had to press the Mode button 3 times to get things working again. Regardless wether or not receiving LoRa packets, only the main (power?) LED is illuminated on the card, while during the restart the LED marked "1" (in the row of 5) was on one or two times shortly too.
(Using ethernet though WiFi is configured too. And still running 1.0.3 from an SD card, commit: 2c56ce09, timestamp: 1521721252, Build time: Mar 22 2018 12:21:52, as 1.0.4 is giving me a reboot loop. As an aside, it's not clear to me if 1.0.3 or 1.0.4 is the current stable release if one would not use an SD card.)
And some more human interventions pressing the Mode button, approximate times again:
Reboot reason: 0x10
)This is related to #47 as the gateway controller was unable to maintain UART connection with the LoRa module and is also addressed in 1.0.5
.
Once again, please feel free to re-open it if the issue persists in 1.0.5
.
I've indeed not run into this issue since I updated to 1.0.5 on July 17th.
(Last occurrence on Monday July 16th, using 1.0.3.)
This is a bug report.
What do you want to do? What do you expect?
After an (unexpected) reboot the gateway's LoRa module should start receiving LoRa packets.
What went wrong? What is missing?
FAILMQTT: Sending status failed
andMAIN: MQTT error
, and rebooted.LORA: UART WRITE ERROR!
errors, but eventually reportedLORA: Configuration succeeded
andLORA: Starting operation
.LORA: UART TIMEOUT
beforeLORA: Configuration succeeded
, but that is also seen in cases where the LoRa module truly starts just fine, and was also seen in version 1.0.1.)LORA: Starting operation
it was not receiving any LoRa packets at all. (It showed neither anyLORA: Accepted packet
norLORA: Packet dropped! Bad CRC
.)The gateway is using ethernet. It seems the same LEDs were on before and after the manual reboot. An LMiC test node is sending many packets on alternating frequencies and spreading factors. That test node was not touched at all when pressing the Mode button, while its packets were received just fine again after that manual intervention. So surely packets should have been received before the manual reboot was triggered.
What firmware is running on your gateway?
Version 1.0.3 beta channel, loaded using an SD card, using the factory bootloader.
As an aside:
What do the logs show?
After an expected reboot today 08:49 UTC (which upgraded from 1.0.1 to 1.0.3), all was fine until a
FAILMQTT: Sending status failed
at 15:50 UTC (17:50 Amsterdam time; all timestamps added by a Raspberry Pi that monitors the serial output):After this reboot it got a network connection, and got as far as:
So, the log shows
LORA: Configuration succeeded
above, despite all errors that are also logged. It then loads new firmware, but as the SD card with 1.0.3 is still inserted I don't think it would even be using that. Also, it shows it's indeed the same version:All fine. Eventually it gets to:
After this it simply does not see any LoRa data coming in, not even with bad CRC either. It is sending status messages though, and TTN Console shows it's connected and updates "Last Seen". But the logs just repeat and repeat:
...and every now and then also:
Pressing the mode button to reset the gateway fixes all this.
Any Screenshots or Photos?