Do you see something in the V3-console Gateway Live Data?
Every 30 seconds there should be a message from your gateway concerning the gateway status.
If you use BasicsStation, the Gateway-traffic log stays empty for the firmware version beeing.
1 Like
Hi Wolfgang, thanks - no there are no messages coming in, see screenshot 
I have an LT22222 that I have also had no joy in migrating ! I am still receiving its data at ThingSpeak? Even if I turn off my gateway, I still get data from my LT22222 so it must be going via another gateway.
It is rather easy to switch the LPS8 back to Semtech UDP. I would propose to do this and watch, wether the data of the gateway appear again in the console.
I have a similar constellation (LPS8, LT22222, LT33222) running without problems with TTN V3 ( TTS CE) and Semtech UDP.
Thanks for your advice Wolfgang.
Iām still unable to get my LPS8 connected on TTN V3, TTS CE. Gone through the manuals, this forum and some tutorial videos, but Iām not seeing anything wrong. Iām in Australia so there are 8 FSB bands to choose from. FSB2 says its used by TTN, so I assume I should use that one?
The gateway traffic on the gateway itself and in the ttn console is empty. On the gateway LogRead there is an error - I canāt find any clues to resolve this, maybe its connected?:
[main] failed to start the concentrator.
Should I delete the gateway and start again? I think Iāve deleted the gateway from the V2 console (does that have any bearing?) My firmware version is lgw-5.4.1635422883
That means the packet forwarder will not run and wonāt connect to TTN (V3 or otherwise).
This is the up to date firmware for the LPS8.
Where did you find the Firmware-Version lgw-5.4.1635422883?
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