I added a U-blox 7 GPS dongle to my mobile PiAware feeder, and finally got it working. PiAware does automatically update the location of the feeder. However, I have not been able to figure out the update frequency.
How often will PiAware update the GPS location from the GPS software and dongle?
Check out
I think that you need to move a certain distance before piaware will update.
Could you describe the procedure to add the GPS dongle to the RPi/Piaware? I have a couple of dongles here and it would be interesting to use it in this application.
There is an post in the thread Adding GPS to Raspberry Pi running PiAware / Dump1090? by @evangelyul that mostly worked for me. There is one correction that has to be made. The line that reads
“and in /etc/rc/local add (before the exit 0)“
should read
“and in /etc/rc.local add (before the exit 0)”
Hi Jon,
The information in the post by @evangelyul in that thread was what I used to get the GPS working. I did miss the entry from @Cristov9000 from earlier this year that mentioned 8-10 minute update cycle
I was hoping a member of the FlightAware staff would chime in with some particulars.
Thank you,
Thank you. I was on that thread, but could not remember a thing about it. A ‘senior moment’ as they say.
Thanks again.
There is an easier method these days if you don’t need to utilize PPS and/or setup for Stratum1:
## INSTALL GPS SUPPORT (w/GPSD BUG OVERRIDE) ##
sudo apt install -y gpsd gpsd-clients python-gps
sudo ln -s /lib/systemd/system/gpsd.service /etc/systemd/system/multi-user.target.wants/
sudo sed -i '/ListenStream=\[::1\]:2947/d' /lib/systemd/system/gpsd.socket #IPV6 LOOPBACK BUG
sudo systemctl enable gpsd
sudo systemctl restart gpsd
Ideally, you don’t even need to incorporate the two small hacks I have above, just do the install line, but the last time I messed with this a few months back, there was still a couple bugs within the GPSD service causing issues, especially with running properly on boot. FWIW anyhow. I can’t answer to how often it updates, but FA picks up on GPSD automatically if it’s a running service. Do the above, plug in the USB and take a nap. I have a couple how-to posts to get PPS going, etc here somewhere if you need to go that route for a Stratum1 server with the atomic driver.
The local piaware gets location info at whatever rate gpsd reports at - typically once a second.
Location info is sent to the FA servers when the location moves by >0.001 degree (roughly 100m at the equator), or every 5 minutes otherwise: piaware/programs/piaware/health.tcl at master · flightaware/piaware · GitHub
So - You’re saying that if I light this bad-boy up at Mach1, a ~290ms poll-rate would be too frequent? Time to pump up the baud rate for this monkey-show… 
@obj - thanks for the info mate.
@obj Thank you, that is exactly what I was looking for.
Now to figure out why mine doesn’t seem to be updating as expected.
Does ‘gpsmon’ show proper output?
I’m not really sure what gpsmon is supposed to show. The cgps utility shows a 3D FIX, usually with four or more satellites used. I have continued to poke at this when I’ve been out in the car.
I can now get my stats page on FlightAware to update more regularly. All I have to do is once the little green light on the GPS dongle is flashing (which seems to indicate a 3D FIX), from the stats page just restart PiAware. I’m not sure why this seems to work, but it does. Rebooting the Pi does not work. Perhaps if gpsd is not working when PiAware starts up, it doesn’t look at the gps anymore. I just don’t know. I think my next step will be to add a cron job to run 5 minutes and 15 minutes after the startup of the PiAware to restart PiAware.
Something like this(I doctored the coords, not that I really care)
/dev/gps0 u-blox>
┌──────────────────────────────────────────────────────────────────────────────┐or":12}
│Time: 2020-05-29T23:13:55.000Z Lat: 39 21' 92.02345" Non: 938 21' 917.234566" W│":"u-blox","subtype":"SW ROM CORE 3.0
└───────────────────────────────── Cooked TPV ─────────────────────────────────┘08.068Z","flags":1,"native":0,"bps":9
┌──────────────────────────────────────────────────────────────────────────────┐
│ GNRMC GNVTG GNGGA GNGSA GPGSV GLGSV GNGLL │false,"timing":false,"split24":false,
└───────────────────────────────── Sentences ──────────────────────────────────┘
┌──────────────────┐┌────────────────────────────┐┌────────────────────────────┐
│Ch PRN Az El S/N ││Time: 231355.00 ││Time: 231355.00 │
│ 0 2 56 23 16 ││Latitude: 3921.12345 N ││Latitude: 3921.12345 │
│ 1 5 70 50 8 ││Longitude: 12921.23456 W ││Longitude: 12921.23456 │
│ 2 12 165 38 22 ││Speed: 9.703 ││Altitude: 938.1 │
│ 3 15 150 3 0 ││Course: ││Quality: 1 Sats: 08 │
│ 4 18 254 35 17 ││Status: A FAA: A ││HDOP: 1.15 │
│ 5 20 207 4 0 ││MagVar: ││Geoid: -30.5 │
│ 6 21 254 20 17 │└─────────── RMC ────────────┘└─────────── GGA ────────────┘
│ 7 25 199 61 21 │┌────────────────────────────┐┌────────────────────────────┐
│ 8 26 321 8 0 ││Mode: A3 Sats: 2 5 12 18 25 ││UTC: RMS: │
│ 9 29 338 62 24 ││DOP: H=1.15 V=2.30 P=2.57 ││MAJ: MIN: │
│10 31 287 13 0 ││TOFF: 0.072023360 ││ORI: LAT: │
│11 70 39 20 0 ││PPS: ││LON: ALT: │
└────── GSV ───────┘└──────── GSA + PPS ─────────┘└─────────── GST ────────────┘
piaware will log about what it’s doing with GPS locations. Have you looked at the logs? What do they say?
@obj your suggestion to look at the logs has revealed something that I had missed. I already knew it took sometime for the GPS dongle to acquire a FIX, but I didn’t realize that once it does the local Software recognizes the change in locations. What doesn’t seem to update is the GPS location on the feeders stat page. Restarting PiAware after the GPS dongle has acquired a FIX the allows the feeders stat page to update the GPS location as it changes.
What did the piaware logs say, exactly?
Did you wait at least 5 minutes after the location update happened for the stats page to update?
Hi @obj, As I couldn’t remember exactly what they said, I went for a drive this afternoon.
I started PiAware at approximately June 2, 2020 @ 13:11 local time. While driving I noted a 3D FIX had been acquired sometime around 13:17 local time. I drove for over 15 minutes and checked the stats page for this feeder. It was still showing Location Set date and time of 30 May 2020 10:53 AM, I restarted PiAware at approximately 13:36 local time, drove for a few minutes and now the stats page sows Location Set 2 June 2020 1:44 PM.
Unfortunately, the output of the sudo journalctl -f -u piaware command is too much to be included in this reply. And as I don’t know what you would be looking for I have just included the first few lines of the first start and the restart. If you want the entire log file just let me know and provide a method for me to send it to you. I noticed the date and time changed suddenly partway through the first snippet I included, I can only conclude the time and date of the pi changed at that point in time.
Jun 01 16:17:20 piaware piaware[509]: creating pidfile /run/piaware/piaware.pid
Jun 01 16:17:20 piaware piaware[509]: ****************************************************
Jun 01 16:17:20 piaware piaware[509]: piaware version 3.8.1 is running, process ID 509
Jun 01 16:17:20 piaware piaware[509]: your system info is: Linux piaware 4.19.97-v7+ #1294 SMP Thu Jan 30 13:15:58 GMT 2020 armv7l GNU/Linux
Jun 01 16:17:20 piaware piaware[509]: GPS: Connected to gpsd 3.17 at localhost/2947
Jun 01 16:17:21 piaware piaware[509]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Jun 01 16:17:21 piaware piaware[509]: Connection with adept server at piaware.flightaware.com/1200 established
Jun 01 16:17:22 piaware piaware[509]: TLS handshake with adept server at piaware.flightaware.com/1200 completed
Jun 01 16:17:22 piaware piaware[509]: FlightAware server certificate validated
Jun 01 16:17:22 piaware piaware[509]: encrypted session established with FlightAware
Jun 01 16:17:22 piaware sudo[561]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=list /usr/bin/netstat --program --tcp --wide --all --numeric
Jun 01 16:17:22 piaware sudo[563]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/netstat --program --tcp --wide --all --numeric
Jun 01 16:17:22 piaware sudo[563]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 01 16:17:22 piaware sudo[563]: pam_unix(sudo:session): session closed for user root
Jun 01 16:17:23 piaware piaware[509]: adept reported location: 43.83130, -79.35283, 150ft AMSL
Jun 01 16:17:23 piaware piaware[509]: Receiver location changed, restarting dump1090 and skyaware978
Jun 01 16:17:23 piaware piaware[509]: attempting to restart dump1090..
Jun 01 16:17:23 piaware sudo[577]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=list /usr/sbin/invoke-rc.d --query dump1090-fa restart
Jun 01 16:17:23 piaware sudo[579]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/invoke-rc.d --query dump1090-fa restart
Jun 01 16:17:23 piaware sudo[579]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 01 16:17:23 piaware sudo[579]: pam_unix(sudo:session): session closed for user root
Jun 01 16:17:23 piaware piaware[509]: attempting to restart dump1090-fa using 'systemctl --no-block try-restart dump1090-fa.service < /dev/null'...
Jun 01 16:17:23 piaware sudo[590]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=list /usr/bin/systemctl --no-block try-restart dump1090-fa.service
Jun 01 16:17:23 piaware sudo[592]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/systemctl --no-block try-restart dump1090-fa.service
Jun 01 16:17:23 piaware sudo[592]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 01 16:17:23 piaware sudo[592]: pam_unix(sudo:session): session closed for user root
Jun 01 16:17:23 piaware piaware[509]: dump1090 restart appears to have been successful
Jun 01 16:17:23 piaware piaware[509]: attempting to restart skyaware978..
Jun 01 16:17:23 piaware sudo[602]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=list /usr/sbin/invoke-rc.d --query skyaware978 restart
Jun 01 16:17:23 piaware sudo[604]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/invoke-rc.d --query skyaware978 restart
Jun 01 16:17:23 piaware sudo[604]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 01 16:17:23 piaware sudo[604]: pam_unix(sudo:session): session closed for user root
Jun 01 16:17:23 piaware piaware[509]: attempting to restart skyaware978 using 'systemctl --no-block try-restart skyaware978.service < /dev/null'...
Jun 01 16:17:23 piaware sudo[615]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=list /usr/bin/systemctl --no-block try-restart skyaware978.service
Jun 01 16:17:23 piaware sudo[617]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/systemctl --no-block try-restart skyaware978.service
Jun 01 16:17:23 piaware sudo[617]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 01 16:17:23 piaware sudo[617]: pam_unix(sudo:session): session closed for user root
Jun 01 16:17:23 piaware piaware[509]: skyaware978 restart appears to have been successful
Jun 01 16:17:23 piaware piaware[509]: logged in to FlightAware as user va3kxp
Jun 01 16:17:23 piaware piaware[509]: my feeder ID is 1aef65e4-a3ca-4cfd-b696-c30b6643a86b
Jun 01 16:17:23 piaware piaware[509]: site statistics URL: https://flightaware.com/adsb/stats/user/va3kxp#stats-115450
Jun 01 16:17:23 piaware sudo[626]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/netstat --program --tcp --wide --all --numeric
Jun 01 16:17:23 piaware sudo[626]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 01 16:17:23 piaware sudo[626]: pam_unix(sudo:session): session closed for user root
Jun 01 16:17:23 piaware piaware[509]: ADS-B data program 'dump1090-fa' is listening on port 30005, so far so good
Jun 01 16:17:23 piaware piaware[509]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 43.831 --lon -79.353
Jun 01 16:17:23 piaware piaware[509]: Started faup1090 (pid 635) to connect to dump1090-fa
Jun 01 16:17:23 piaware piaware[509]: UAT support disabled by local configuration setting: uat-receiver-type
Jun 01 16:17:23 piaware piaware[509]: multilateration data requested
Jun 01 16:17:23 piaware sudo[636]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/netstat --program --tcp --wide --all --numeric
Jun 01 16:17:23 piaware sudo[636]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 01 16:17:23 piaware sudo[636]: pam_unix(sudo:session): session closed for user root
Jun 01 16:17:23 piaware piaware[509]: Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --results beast,listen,30105 --results ext_basestation,listen,30106 --udp-transport 70.42.6.225:5765:3212157679
Jun 01 16:17:24 piaware piaware[509]: mlat-client(645): fa-mlat-client 0.2.11 starting up
Jun 01 16:17:24 piaware piaware[509]: mlat-client(645): Using UDP transport to 70.42.6.225 port 5765
Jun 01 16:17:24 piaware piaware[509]: mlat-client(645): Listening for Beast-format results connection on port 30105
Jun 01 16:17:24 piaware piaware[509]: mlat-client(645): Listening for Extended Basestation-format results connection on port 30106
Jun 01 16:17:24 piaware piaware[509]: mlat-client(645): Route MTU changed to 1500
Jun 01 16:17:24 piaware piaware[509]: mlat-client(645): Input connected to localhost:30005
Jun 01 16:17:24 piaware piaware[509]: mlat-client(645): Input format changed to BEAST, 12MHz clock
Jun 01 16:17:24 piaware piaware[509]: mlat-client(645): Lost connection to localhost:30005
Jun 01 16:17:24 piaware piaware[509]: mlat-client(645): Reconnecting in 30.0 seconds
Jun 01 16:17:24 piaware piaware[509]: lost connection to dump1090-fa via faup1090
Jun 01 16:17:24 piaware piaware[509]: faup1090 exited normally
Jun 01 16:17:24 piaware piaware[509]: will reconnect to dump1090-fa in 30 seconds
Jun 01 16:17:25 piaware piaware[509]: mlat-client(645): Beast-format results connection with ::1:30104: [Errno 111] Connection refused
Jun 02 17:11:43 piaware sudo[682]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/netstat --program --tcp --wide --all --numeric
Jun 02 17:11:43 piaware sudo[682]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 02 17:11:43 piaware sudo[682]: pam_unix(sudo:session): session closed for user root
Jun 02 17:11:43 piaware piaware[509]: ADS-B data program 'dump1090-fa' is listening on port 30005, so far so good
Jun 02 17:11:43 piaware piaware[509]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 43.831 --lon -79.353
Jun 02 17:11:43 piaware piaware[509]: Started faup1090 (pid 694) to connect to dump1090-fa
Jun 02 17:11:43 piaware piaware[509]: 0 msgs recv'd from dump1090-fa; 0 msgs sent to FlightAware
Jun 02 17:11:43 piaware piaware[509]: timed out waiting for alive message from FlightAware, reconnecting...
Jun 02 17:11:43 piaware piaware[509]: multilateration data no longer required, disabling mlat client
Jun 02 17:11:44 piaware piaware[509]: fa-mlat-client exited normally
Jun 02 17:11:44 piaware piaware[509]: reconnecting in 5 seconds...
Jun 02 17:11:44 piaware piaware[509]: piaware received a message from dump1090-fa!
Jun 02 17:11:44 piaware piaware[509]: mlat-client(645): Exiting on connection loss
Jun 02 17:11:49 piaware piaware[509]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Jun 02 17:11:49 piaware piaware[509]: Connection with adept server at piaware.flightaware.com/1200 established
Jun 02 17:11:50 piaware piaware[509]: TLS handshake with adept server at piaware.flightaware.com/1200 completed
Jun 02 17:11:50 piaware piaware[509]: FlightAware server certificate validated
Jun 02 17:11:50 piaware piaware[509]: encrypted session established with FlightAware
Jun 02 17:11:50 piaware sudo[769]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/netstat --program --tcp --wide --all --numeric
Jun 02 17:11:50 piaware sudo[769]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 02 17:11:50 piaware sudo[769]: pam_unix(sudo:session): session closed for user root
Jun 02 17:11:50 piaware piaware[509]: logged in to FlightAware as user va3kxp
Jun 02 17:11:50 piaware piaware[509]: my feeder ID is 1aef65e4-a3ca-4cfd-b696-c30b6643a86b
Jun 02 17:11:50 piaware piaware[509]: site statistics URL: https://flightaware.com/adsb/stats/user/va3kxp#stats-115450
Jun 02 17:11:50 piaware piaware[509]: multilateration data requested
Jun 02 17:11:50 piaware sudo[782]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/netstat --program --tcp --wide --all --numeric
Jun 02 17:11:50 piaware sudo[782]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 02 17:11:50 piaware sudo[782]: pam_unix(sudo:session): session closed for user root
Jun 02 17:11:50 piaware piaware[509]: Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --results beast,listen,30105 --results ext_basestation,listen,30106 --udp-transport 70.42.6.224:17719:417293192
Jun 02 17:11:51 piaware piaware[509]: mlat-client(791): fa-mlat-client 0.2.11 starting up
Jun 02 17:11:51 piaware piaware[509]: mlat-client(791): Using UDP transport to 70.42.6.224 port 17719
Jun 02 17:11:51 piaware piaware[509]: mlat-client(791): Listening for Beast-format results connection on port 30105
Jun 02 17:11:51 piaware piaware[509]: mlat-client(791): Listening for Extended Basestation-format results connection on port 30106
Jun 02 17:11:51 piaware piaware[509]: mlat-client(791): Route MTU changed to 1500
Jun 02 17:11:51 piaware piaware[509]: mlat-client(791): Input connected to localhost:30005
Jun 02 17:11:51 piaware piaware[509]: mlat-client(791): Input format changed to BEAST, 12MHz clock
Jun 02 17:11:51 piaware piaware[509]: mlat-client(791): Beast-format results connection with ::1:30104: connection established
Jun 02 17:12:12 piaware piaware[509]: piaware has successfully sent several msgs to FlightAware!
Jun 02 17:12:14 piaware piaware[509]: 12 msgs recv'd from dump1090-fa (12 in last 1m); 9 msgs sent to FlightAware
Jun 02 17:17:14 piaware piaware[509]: 99 msgs recv'd from dump1090-fa (87 in last 5m); 96 msgs sent to FlightAware
Jun 02 17:17:30 piaware piaware[509]: gpsd reported location: 43.75478, -79.35209, 146m (WGS84)
Jun 02 17:17:30 piaware piaware[509]: Receiver location changed, restarting dump1090 and skyaware978
Jun 02 17:17:30 piaware piaware[509]: attempting to restart dump1090..
Jun 02 17:17:30 piaware sudo[1053]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/invoke-rc.d --query dump1090-fa restart
Jun 02 17:17:30 piaware sudo[1053]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 02 17:17:30 piaware sudo[1053]: pam_unix(sudo:session): session closed for user root
Jun 02 17:17:30 piaware piaware[509]: attempting to restart dump1090-fa using 'systemctl --no-block try-restart dump1090-fa.service < /dev/null'...
Jun 02 17:17:30 piaware sudo[1064]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/systemctl --no-block try-restart dump1090-fa.service
Jun 02 17:17:30 piaware sudo[1064]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 02 17:17:30 piaware sudo[1064]: pam_unix(sudo:session): session closed for user root
Jun 02 17:17:30 piaware piaware[509]: dump1090 restart appears to have been successful
Jun 02 17:17:30 piaware piaware[509]: attempting to restart skyaware978..
Jun 02 17:17:30 piaware sudo[1074]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/invoke-rc.d --query skyaware978 restart
Jun 02 17:17:30 piaware sudo[1074]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 02 17:17:30 piaware sudo[1074]: pam_unix(sudo:session): session closed for user root
Jun 02 17:17:30 piaware piaware[509]: attempting to restart skyaware978 using 'systemctl --no-block try-restart skyaware978.service < /dev/null'...
Jun 02 17:17:30 piaware sudo[1085]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/systemctl --no-block try-restart skyaware978.service
Jun 02 17:17:30 piaware sudo[1085]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 02 17:17:30 piaware sudo[1085]: pam_unix(sudo:session): session closed for user root
Jun 02 17:17:30 piaware piaware[509]: skyaware978 restart appears to have been successful
Jun 02 17:17:30 piaware piaware[509]: Restarting faup1090
Jun 02 17:17:31 piaware piaware[509]: faup1090 exited with SIG SIGHUP
Jun 02 17:17:31 piaware piaware[509]: reconnecting to dump1090-fa
Jun 02 17:17:31 piaware piaware[509]: mlat-client(791): Beast-format results connection with ::1:30104: connection lost
Jun 02 17:17:31 piaware piaware[509]: mlat-client(791): Lost connection to localhost:30005
Jun 02 17:17:31 piaware piaware[509]: mlat-client(791): Reconnecting in 30.0 seconds
Jun 02 17:17:32 piaware sudo[1114]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/netstat --program --tcp --wide --all --numeric
Jun 02 17:17:32 piaware sudo[1114]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 02 17:17:32 piaware sudo[1114]: pam_unix(sudo:session): session closed for user root
Jun 02 17:17:32 piaware piaware[509]: ADS-B data program 'dump1090-fa' is listening on port 30005, so far so good
Jun 02 17:17:32 piaware piaware[509]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 43.831 --lon -79.353
Jun 02 17:17:32 piaware piaware[509]: Started faup1090 (pid 1124) to connect to dump1090-fa
Jun 02 17:17:46 piaware piaware[509]: Receiver location changed, restarting dump1090 and skyaware978
Jun 02 17:17:46 piaware piaware[509]: attempting to restart dump1090..
Jun 02 17:17:46 piaware sudo[1127]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/invoke-rc.d --query dump1090-fa restart
Jun 02 17:17:46 piaware sudo[1127]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 02 17:17:46 piaware sudo[1127]: pam_unix(sudo:session): session closed for user root
Jun 02 17:17:46 piaware piaware[509]: attempting to restart dump1090-fa using 'systemctl --no-block try-restart dump1090-fa.service < /dev/null'...
Jun 02 17:17:46 piaware sudo[1138]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/systemctl --no-block try-restart dump1090-fa.service
Jun 02 17:17:46 piaware sudo[1138]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 02 17:17:46 piaware sudo[1138]: pam_unix(sudo:session): session closed for user root
Jun 02 17:17:46 piaware piaware[509]: dump1090 restart appears to have been successful
Jun 02 17:17:46 piaware piaware[509]: attempting to restart skyaware978..
Jun 02 17:17:46 piaware sudo[1148]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/sbin/invoke-rc.d --query skyaware978 restart
Jun 02 17:17:46 piaware sudo[1148]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 02 17:17:46 piaware sudo[1148]: pam_unix(sudo:session): session closed for user root
Jun 02 17:17:46 piaware piaware[509]: attempting to restart skyaware978 using 'systemctl --no-block try-restart skyaware978.service < /dev/null'...
Jun 02 17:17:46 piaware sudo[1159]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/systemctl --no-block try-restart skyaware978.service
Jun 02 17:17:46 piaware sudo[1159]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 02 17:17:46 piaware sudo[1159]: pam_unix(sudo:session): session closed for user root
Jun 02 17:17:46 piaware piaware[509]: skyaware978 restart appears to have been successful
Jun 02 17:17:46 piaware piaware[509]: Restarting faup1090
Jun 02 17:17:47 piaware piaware[509]: faup1090 exited with SIG SIGHUP
Jun 02 17:17:47 piaware piaware[509]: reconnecting to dump1090-fa
After the restart
Jun 02 17:36:12 piaware piaware[3489]: creating pidfile /run/piaware/piaware.pid
Jun 02 17:36:12 piaware piaware[3489]: ****************************************************
Jun 02 17:36:12 piaware piaware[3489]: piaware version 3.8.1 is running, process ID 3489
Jun 02 17:36:12 piaware piaware[3489]: your system info is: Linux piaware 4.19.97-v7+ #1294 SMP Thu Jan 30 13:15:58 GMT 2020 armv7l GNU/Linux
Jun 02 17:36:12 piaware piaware[3489]: GPS: Connected to gpsd 3.17 at localhost/2947
Jun 02 17:36:13 piaware piaware[3489]: gpsd reported location: 43.74451, -79.35447, 136m (WGS84)
Jun 02 17:36:13 piaware piaware[3489]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Jun 02 17:36:14 piaware piaware[3489]: Connection with adept server at piaware.flightaware.com/1200 established
Jun 02 17:36:14 piaware piaware[3489]: TLS handshake with adept server at piaware.flightaware.com/1200 completed
Jun 02 17:36:14 piaware piaware[3489]: FlightAware server certificate validated
Jun 02 17:36:14 piaware piaware[3489]: encrypted session established with FlightAware
Jun 02 17:36:14 piaware sudo[3496]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=list /usr/bin/netstat --program --tcp --wide --all --numeric
Jun 02 17:36:14 piaware sudo[3498]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/netstat --program --tcp --wide --all --numeric
Jun 02 17:36:14 piaware sudo[3498]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 02 17:36:14 piaware sudo[3498]: pam_unix(sudo:session): session closed for user root
Jun 02 17:36:14 piaware piaware[3489]: logged in to FlightAware as user va3kxp
Jun 02 17:36:14 piaware piaware[3489]: my feeder ID is 1aef65e4-a3ca-4cfd-b696-c30b6643a86b
Jun 02 17:36:14 piaware piaware[3489]: site statistics URL: https://flightaware.com/adsb/stats/user/va3kxp#stats-115450
Jun 02 17:36:15 piaware piaware[3489]: multilateration data requested
Jun 02 17:36:15 piaware sudo[3511]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/netstat --program --tcp --wide --all --numeric
Jun 02 17:36:15 piaware sudo[3511]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 02 17:36:15 piaware sudo[3511]: pam_unix(sudo:session): session closed for user root
Jun 02 17:36:15 piaware piaware[3489]: Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --results beast,listen,30105 --results ext_basestation,listen,30106 --udp-transport 70.42.6.225:6463:1022437266
Jun 02 17:36:15 piaware sudo[3521]: piaware : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/netstat --program --tcp --wide --all --numeric
Jun 02 17:36:15 piaware sudo[3521]: pam_unix(sudo:session): session opened for user root by (uid=0)
Jun 02 17:36:15 piaware sudo[3521]: pam_unix(sudo:session): session closed for user root
Jun 02 17:36:15 piaware piaware[3489]: ADS-B data program 'dump1090-fa' is listening on port 30005, so far so good
Jun 02 17:36:15 piaware piaware[3489]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 43.744 --lon -79.356
Jun 02 17:36:15 piaware piaware[3489]: Started faup1090 (pid 3530) to connect to dump1090-fa
Jun 02 17:36:15 piaware piaware[3489]: UAT support disabled by local configuration setting: uat-receiver-type
Jun 02 17:36:15 piaware piaware[3489]: mlat-client(3520): fa-mlat-client 0.2.11 starting up
Jun 02 17:36:15 piaware piaware[3489]: mlat-client(3520): Using UDP transport to 70.42.6.225 port 6463
Jun 02 17:36:15 piaware piaware[3489]: mlat-client(3520): Listening for Beast-format results connection on port 30105
Jun 02 17:36:15 piaware piaware[3489]: mlat-client(3520): Listening for Extended Basestation-format results connection on port 30106
Jun 02 17:36:15 piaware piaware[3489]: mlat-client(3520): Route MTU changed to 1500
Jun 02 17:36:15 piaware piaware[3489]: mlat-client(3520): Input connected to localhost:30005
Jun 02 17:36:15 piaware piaware[3489]: mlat-client(3520): Input format changed to BEAST, 12MHz clock
Jun 02 17:36:16 piaware piaware[3489]: mlat-client(3520): Beast-format results connection with ::1:30104: connection established
Jun 02 17:36:16 piaware piaware[3489]: piaware received a message from dump1090-fa!
Jun 02 17:36:23 piaware piaware[3489]: piaware has successfully sent several msgs to FlightAware!
Jun 02 17:36:46 piaware piaware[3489]: 21 msgs recv'd from dump1090-fa; 21 msgs sent to FlightAware
Jun 02 17:37:23 piaware piaware[3489]: gpsd reported location: 43.74495, -79.35397, 140m (WGS84)
Not entirely clear why, but it looks like the gps location data is not actually making it upstream.
I’ll try to find some time to look into that properly.
Hi @obj, have you found the time to look into this yet?
I only use GPS with PPS for precise timing and my Stratum 1 NTPsec server.
For my static PiAware solution, it is much more precise to pick the exact coordinates of my antenna location from Apple or Google maps and enter them once and for all in the tool; compared to that, GPS fluctuates more, so I switched to static.