Many thanks for that - so far I’ve not been able to find any clues as to how to fix that for the LPS8 
Not sure where I got that firmware from, but yesterday I updated to the version you linked above, and still no joy I’ve also deleted the gateway from the console and created a new one. I’ve also noticed these errors in the system log:
Fri Nov 5 15:30:08 2021 daemon.err uhttpd[1213]: Error: no such table: livepkts
Fri Nov 5 15:30:09 2021 daemon.err uhttpd[1213]: Error: no such table: gwdb
I have emailed Dragino for help, no response yet…
update: Another message I see in the log:
[up] getaddrinfo on address au1.cloud.thethings.network (PORT 1700) returned Try again
when you upgade the lates firmware with your gateway,this error of failed to start the concentrator still occur?
the latest frimware at Dragino Download Server ./downloads/LoRa_Gateway/LPS8/Firmware/Release/lgw--build-v5.4.1636008262-20211104-1446/
Yes, even after the firmware upgrade the concentrator error is still there…
Did you check"Preserve Settings" before firmware update? If you did, maybe the LPS8 preserved some old (wrong) values.
Indeed that was the conclusion I came to at end of this thread
Only way to get back online was a full reset to bypass any (partial or incomplete) settings carry over. In my case I decided to stick with UDP (for now) but suspect same could have applied with a simultaneous move to BS… I may reconsider when a demonstrated proven path to BS on new firmware emerges…
1 Like
Upgraded my DLOS8 gateway and have connected to Basic Station.
I no longer see the status messages every 30 seconds, so hoping it is working correctly as I want the GPS location to populate my gateway automatically.
I believe it is working as I have seen one DevAddr packet hit TTN Console, though I do see odd things, for instance when I save data in basic station I see the following:
The “Finished station” concerns me?
Sat Nov 6 13:59:18 2021 user.notice root: Start station
Sat Nov 6 13:59:24 2021 user.notice iot_keep_alive: Internet Access OK: via 3g-cellular
Sat Nov 6 13:59:24 2021 user.notice iot_keep_alive: XX ping ETH1 139.130.4.5 via eth1 fail
Sat Nov 6 13:59:24 2021 user.notice iot_keep_alive: XX ping WiFi 8.8.4.4 via wlan0-2 fail
Sat Nov 6 13:59:28 2021 daemon.err uhttpd[1362]: Daemon pid=9545 running...
Sat Nov 6 13:59:28 2021 user.notice root: Finished station
Secondly the “Time sync rejected” I keep seeing?
2021-11-06 02:05:47.911 [SYN:INFO] Time sync qualities: min=97 q90=143 max=554 (previous q90=144)
2021-11-06 02:05:47.911 [SYN:VERB] Time sync rejected: quality=554 threshold=143
2021-11-06 02:06:15.215 [SYN:INFO] MCU/SX130X drift stats: min: -2.9ppm q50: -8.6ppm q80: -11.7ppm max: -13.8ppm - threshold q90: -13.3ppm
2021-11-06 02:06:15.216 [SYN:INFO] Mean MCU drift vs SX130X#0: -8.8ppm
2021-11-06 02:06:19.417 [SYN:VERB] Time sync rejected: quality=191 threshold=143
2021-11-06 02:06:20.968 [___:INFO] lgw_receive:1155: FIFO content: 1 85 2 7 95
lgw_receive:1174: [4 17]
Note: LoRa packet
2021-11-06 02:06:48.821 [SYN:INFO] Time sync qualities: min=72 q90=141 max=191 (previous q90=143)
2021-11-06 02:06:59.322 [SYN:INFO] MCU/SX130X drift stats: min: +1.0ppm q50: +5.2ppm q80: +8.1ppm max: -10.5ppm - threshold q90: -10.0ppm
2021-11-06 02:06:59.323 [SYN:INFO] Mean MCU drift vs SX130X#0: -0.7ppm
2021-11-06 02:07:24.527 [SYN:VERB] Time sync rejected: quality=193 threshold=141
2021-11-06 02:07:43.430 [SYN:INFO] MCU/SX130X drift stats: min: +1.0ppm q50: +2.9ppm q80: +4.8ppm max: +7.6ppm - threshold q90: +7.1ppm
Wolfgang, I left “preserve settings” unchecked.
I’m a novice on this stuff so I’m trying anything I can think of. I noticed this:
In TTN V3 console, the global_conf.json that can be downloaded has server address as “au1.cloud.thethings.network” . However if I use WinSCP to look at the global_conf.json on the gateway in /etc/lora, it lists the server as “router.au.thethings.network”. If I edit the file directly on the gateway and reboot, it just seems to overwrite the file with the original setting.
That doesn’t seem to have anything to do with the packet forwarder not starting though?
Thanks Jeff-UK, the link to that article did not work or me - says page does not exist or is private…
Maybe this hint can help you:
“Please note, the global_conf.json file will be overwrite by the match region files in /etc/lora/cfg-30x when change settings in the web. So user need to change the files in /etc/lora/cfg-cfg-30x instead of global_conf.json”
It’s from wiki.dragino.com
1 Like
Today I installed the latest firmware on one of my LIG16s and startet BasicsStation. The data-packages are transferred to TTS-CE and the applications.
But: The Home-screen of the LIG16 shows the status of AWS-IoT Core Station service (Station is not running) and “Gateway-traffic” is still empty.
So back to Semtech UDP.
Hi Wolfgang, Thanks for taking the time to look into this, much appreciated! Dragino think that my hardware might be faulty, so I’ll park this up until I can get a replacement gateway…
Many thanks to all those that have tied to help 
1 Like
Got mine on Basic station but GPS just doesn’t work; support haven’t been helpful as yet.
I used minicom to connect to ttyGPS and can see the GPS data so I know its there;
but in TTN Console I dont get any antenna_locations at all
Dragino have helped to further troubleshoot my LPS8 problem and it seems to be a hardware problem (at least that’s what I understand - related to the the “failed to start concentrator” message I was getting. My new LPS8 is now working fine.
2 Likes
Just to confirm the latest firmware update for the LPS8 (lgw-5.4.1640315898 dated 24 Dec 2021) does not fix these issues. When configured as TTN Basic Station:
- the ‘LoRa log’ page does not show any Logreads, all empty
- the ‘Gateway Traffic’ page shows an empty graph
- the ‘System Log’ page shows LoRa log under section ‘Previous Log: station’, with many ‘Time sync rejected’ messages
2022-01-11 08:42:34.028 [SYN:INFO] MCU/SX130X drift stats: min: +0.0ppm q50: +4.8ppm q80: +6.4ppm max: +10.0ppm - threshold q90: +8.9ppm
2022-01-11 08:42:34.028 [SYN:INFO] Mean MCU drift vs SX130X#0: 4.8ppm
2022-01-11 08:42:40.093 [___:INFO] lgw_receive:1155: FIFO content: 1 c9 1 7 db
lgw_receive:1174: [3 17]
Note: LoRa packet
2022-01-11 08:42:50.980 [S2E:VERB] RX 924.4MHz DR5 SF7/BW125 snr=10.2 rssi=-17 xtime=0x7E0000634CAE34 - updf mhdr=40 DevAddr=260D9B01 FCtrl=80 FCnt=18 FOpts=[] 01C2F08411 mic=806341944 (17 bytes)
2022-01-11 08:42:50.981 [___:INFO] lgw_receive:1155: FIFO content: 1 b4 2 5 11
lgw_receive:1174: [6 17]
Note: LoRa packet
2022-01-11 08:42:57.131 [SYN:VERB] Time sync rejected: quality=209 threshold=134
2022-01-11 08:43:03.098 [___:INFO] lgw_receive:1155: FIFO content: 1 d5 2 7 d9
lgw_receive:1174: [3 17]
Note: LoRa packet
2022-01-11 08:43:18.134 [SYN:INFO] Time sync qualities: min=81 q90=134 max=209 (previous q90=134)
2022-01-11 08:43:18.134 [SYN:INFO] MCU/SX130X drift stats: min: -1.0ppm q50: +2.9ppm q80: +3.8ppm max: +8.1ppm - threshold q90: +7.6ppm
2022-01-11 08:43:18.134 [SYN:INFO] Mean MCU drift vs SX130X#0: 2.9ppm
However, the TTN console is showing my gateway is active, and i get 0% packet loss so it seems to be working just fine for the moment.
I upgraded my firmware (not preserving any settings) because with version 4-Nov-2021 my gateway crashed every other day; i hope the latest version fixes this.
2 Likes
In my case i am back on November firmware - because the December version caused a lot of disconnections from internet. With both versions Basic station is not sending the status data every 30 seconds - so i am back to semtech UDP.
2 Likes
New Firmware today. Still no status data every 30 seconds - so again back on November and semtech UDP.
1 Like
can’t you see the gateway online at TTN status by Basic Station at all?
Only when a node is sending some data it shows actice. After a few minutes of recieving no data it shows disconnected.
Today I made an update of my LIG16 to the latest firmware and switched to Basic Station.
Basic Station seems to work but still there is nothing shown in “Gateway Traffic”.
In the console the status is shown as “connected”, “Last activity” is only updated if there is a message from a node - that is ok for me.
It seems like no regularly status messages are sent from the LIG16 to TTS CE (or these messages are not shown anymore).