Would it be possible to (temporary) cut the SPI connections to the SX1301 and connect a Pi (zero?) to run the ic880 software? If we can place a “smart” connector we easly can change back to original (placing jumpers), If someone is interested (Netherlands) I offer to help / investigate.
I guess if bought through disty (farnell/newark) could try RMA/Return procedure as defective/under warranty/not fit for purpose (can use these forum threads etc as ‘evidence’ 
:-
http://uk.farnell.com/help-how-to-return-a-product#
Though they do (try) to apply a 21 day limit…that would be invalid under warranty or consumer sales law (at least in UK) unless they try to get out by claiming its a B2B sale vs B2C…but then these are supposed to be sold for ‘community’/maker use not just for commercial/biz use - and TTN dont offer an alternate option anymore I believe…
…any refund then going to a Laird, Multitech, iMST, Rak…etc etc system as alternate? (at least until community assured TTN GW’s good to go based on any future fix/iteration…)
Hi all
Over the last few weeks, we have been doing internal tests to validate our assumptions with the blocking issue of the LoRa module. These tests have taken a long time than we anticipated after releasing the 1.0.4 beta version. The variation between LoRa module and the gateway board creates a time related problem between the two and is the main contributor for the reboot loop. Fixing this would take 5-6 weeks time during which we will involve some of the active beta testers from the community. Besides this, we are also working on updating the software build from Harmony version 1.0 to 2.0.
All of these changes would be reflected in 1.0.5 version which should be out by week 30 and in the meanwhile will inform you of the updates leading upto the release.
—
The Things Products Team
6 Likes
The firmware of the mPCIe card can be updated by @TTP or is it closed sourced from @OccamSmart ?
A good solution can be to implement a 100% compatible pico gateway, porting the code picoGW_mcu from STM32 to PIC24. And picoGW_hal and picoGW_packet_forwarder to PIC32.
This way, if the TTN gateway still does not work fine, you can throw away the TTN motherboard and save the mPCIe card to buil a DIY pico gateway.
Thanks for the update! Will this beta be available via GitHub or will you contact beta testers directly?
I just purchased and set up a new TTN Gateway along with a TTN Uno and TTN Node, following the great YoiuTube Videos and other documentation. After setting up the TTN Gateway, I “forgot” the temporary TTN AP Wifi SSID.
About every hour or two, the Wifi LED starts blinking, sometimes fast and sometimes slow, losing it’s Wifi comnection and the Gateway is no longer seen by the TTN Network. I noticed that when this happens, The TTN AP Wifi SSID is active, which I think means that the Gateway went into setup mode. The Gateway is located in a place where the Wifi signal is strong.
If I just reboot the Gateway, it recconnects with my Wifi and the TTN network and data starts showing up from my two nodes.
To reply on to my own problems: after simply ticking the box to allow for beta firmware and a reset, my gateway is now upgraded from 1.0.2 to 1.0.4b and has not gone down (without coming back up) anymore. I’m doing some ping tests to see if it actually stays up, but at least the issue of not coming back up has been resolved for me.
Some other thing I noticed: I chose not to hang the gateway from the window but to put it on it’s back. However the white plastic edge of the cover prevents the (foldable) antenna to go up in a 90 degree angle.
If I position the gateway upside down (on it’s white cover) the antenna can fold, but I’d make a small recess on the white cover to allow the gateway to stand flat (instead of hanging) with the ability for the antenna to fold in an upward angled fashion in a next hardware revision.
Two weeks ago I’ve ordered one of those affordable PICkit 3 programmers to try if that would make any difference. And it did! 
Last night I’ve uploaded the latest firmware with updated bootloader as described on the GitHub firmware page and now the gateway actually starts receiving and sending messages. It is still rebooting frequently like 25 times in the last 12 hours once there is a MQTT error like this
[2018-06-17 08:12:24] LORA: Kick LoRa module with ACK after not acked it for 60s
[2018-06-17 08:12:29] MON: SYS Stack size: 2870
[2018-06-17 08:12:29] MON: TCPIP Stack size: 3787
[2018-06-17 08:12:29] MON: APP Stack size: 3294
[2018-06-17 08:12:29] MON: LoRa Stack size: 3859
[2018-06-17 08:12:29] MON: heap usage: 278KB (279KB), free: 60KB
[2018-06-17 08:12:39] MON: SYS Stack size: 2870
[2018-06-17 08:12:39] MON: TCPIP Stack size: 3787
[2018-06-17 08:12:39] MON: APP Stack size: 3294
[2018-06-17 08:12:39] MON: LoRa Stack size: 3859
[2018-06-17 08:12:39] MON: heap usage: 278KB (279KB), free: 60KB
[2018-06-17 08:12:42] MQTT: Sending status packet
[2018-06-17 08:12:45] MQTT: Sending status failed
[2018-06-17 08:12:45]
[2018-06-17 08:12:45] MAIN: MQTT error
[2018-06-17 08:12:45]
[2018-06-17 08:12:45] MAIN: Leaving state 5
[2018-06-17 08:13:08] SNTP: State change from 0 to 0
[2018-06-17 08:13:08] SNTP: State change from 0 to 0
[2018-06-17 08:13:08]
[2018-06-17 08:13:08]
[2018-06-17 08:13:08]
[2018-06-17 08:13:08] **************************
[2018-06-17 08:13:08] * The Things Network *
[2018-06-17 08:13:08] * G A T E W A Y *
[2018-06-17 08:13:08] **************************
[2018-06-17 08:13:08] Firmware name: AmazingAckermann, type: 0, version: 1.0.4, commit: a7beae91, timestamp: 1525259181
[2018-06-17 08:13:08] Bootloader revision: 2, commit: c463e87e, timestamp: 1519396960
[2018-06-17 08:13:08] Build time: May 2 2018 11:07:39
[2018-06-17 08:13:08] Reboot reason: 0x10
[2018-06-17 08:13:08] BOOT: (persisted info) 6F 72 72 65 01 10 BC 79 EF FE F9 BA 77 6B 2C E7@TTP, how come this user did not get 1.0.3 when the beta checkbox was not enabled, while 1.0.3 still seems to be the stable version according to Releases · TheThingsProducts/gateway · GitHub ? Or has 1.0.3 been revoked altogether?
Or in other words: which version does one get when having beta enabled/disabled, and which is the recommended setting?
(For me, 1.0.2 and 1.0.4 yield a reboot loop, while 1.0.3 does not, where the 1.0.3 on my SD card is commit 2c56ce0, Mar 22 2018 12:21:52 while the official release was April 4th. The checksums 757211...2039b8 from the 1.0.3 release does not match the checksums 8793f2...489c20 as linked as “stable” from gateway/firmware/README.md at develop · TheThingsProducts/gateway · GitHub)
Thanks, we needed an update after so many weeks of silence. Looks like I will just have to hang in there. The gateway has operated for only 15 minutes in the last 4 days
I had a similar experience. I upgraded to 1.0.4 by checking the “Beta Updates” checkbox in the Gateway setup. The Gateway ran for an hour and rebooted. Then it ran for about 20 hours until an MQTT error, rebooted 20 times within about 5 minutes and is again stable.
Here is what it looked like duringthe first and second reboot.
How did you add timestamps to the Serial console??
MQTT: Sending UPLINK failed: -1
MAIN: MQTT error
MAIN: Leaving state 5
MAIN: Entering state 6
INET: State change to 0
WIFI: Disabling modules
SNTP: State change from 7 to 8
CB: Disconnect
Head magic match void: trying to free an already freed block, ignore
SNTP: State change from 8 to 1
WIFI: Entering state 3
MON: SYS Stack size: 2845
MON: TCPIP Stack size: 3787
MON: APP Stack size: 3294
MON: LoRa Stack size: 3797
MON: heap usage: 185KB (279KB), free: 154KB
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.4, commit: a7beae91, timestamp: 1525259181
Bootloader revision: 1, commit: 7167873a, timestamp: 1496411298
Build time: May 2 2018 11:07:39
Reboot reason: 0x10
BOOT: (persisted info) 6F 72 72 65 01 10 57 3E 46 F8 0B 62 38 36 B1 82
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)) 65 0D 50 41 6F 3C 7A 21 B0 6A 61 4A FF BE C3 DD 3F 8A 2C 8F D1 98 70 9F 71 EF C5 53 6A 7D 31 AF
FLASH: Loading WiFi Data
CNFG: WiFi SSID: AO-HOME
CNFG: WiFi key: ***
CNFG: WiFi conn_type: 1
CNFG: WiFi sec_type: 4
FLASH: Loading Activation Data
CNFG: Gateway ID: burns_park_north_ttn_gateway
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
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.4, commit: a7beae91, timestamp: 1525259181
Bootloader revision: 1, commit: 7167873a, timestamp: 1496411298
Build time: May 2 2018 11:07:39
Reboot reason: 0x10
BOOT: (persisted info) 6F 72 72 65 01 10 57 3E 46 F8 0B 62 38 36 B1 82Looks like this bug is similar to the issue reported on GitHub Reboot after MQTT error · Issue #21 · TheThingsProducts/gateway · GitHub
Initially I logged using PuTTY but now I’ve connected the gateway to a RaspberryPi as suggested by this topic: Raspberry Pi to monitor serial output of a node or TNN Gateway, and alert on Slack or Telegram
@nestorayuso the firmware of the mPCIe card is indeed closed sourced from Occam.
@jurrien the beta would be available via Github and leading upto that we will contact the testers if we need some help.
I am not sure if this is an issue but I have noticed that if I log onto the TTN Console to view my gateway, especially from a second computer when I already have a session open on another, it seems to crash the gateway. i.e. when I log on it is always saying something like “last message 19 seconds ago” etc which means it has been working, but while I watch no new messages from the gateway are received. If I log off and back on again, sometimes it has come back… May just be coincidence since the gateway is down more than it is up.
Has anyone else noticed this?
Is this only for The Things Gateway or for others too?
I do not experience this with my Raspi + iC880A logged in on my laptop and tablet.
I only have the Things Gateway
Hello, TTN Community
I ordered a TTN Gateway in Aug 2016 and finally it arrived 2 months ago (I Know!). I have not been able to make it work with neither WiFi or Ethernet. It seems either the gateway is broken or there is a bug while joining. I have sent several emails and TTN guys told me it was a software bug 1.5 months ago, and the result is the same: The gateway keeps rebooting and does not connect.
Steps I have followed:
I have written emails to TTN but they have not helped me with this issue. Anybody here has the same problem? How did you solve it?
I can see a red led being turned on, next to the lora chip, and it suddenly reboots. On the TTN Activation Website, it basically blocks at “Configuring…”
Thanks a lot!!
Hello!
How to reset counters on overview gateway page and what happens when its reached 99999
Thanks
Dont worry about it…They just keep on truckin’ !
2 of my gateways at least have gone >100k:
Received Messages 144629 (iMST Lite GW)
Received Messages 130108 (TTN GW)
And I’m sure others have far more than those
(I hear talk of some >1Mmsg but cant confirm)