I have RTL SDR on RPi with piaware since about 1 year, working well, few days ago checking my lat/lon I though I might be out maybe ~5 metres ?, so using gmaps got better lat/lon, reentered lat/lon through FA i/f, also, edited TZ to Sydney - not sure if that is relevant ?, just noticed since few days my MLAT dropped to zero ?
● piaware.service - FlightAware ADS-B uploader
Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2024-09-14 15:36:10 AEST; 31s ago
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Main PID: 1318917 (piaware)
Tasks: 4 (limit: 3930)
CPU: 1.163s
CGroup: /system.slice/piaware.service
├─1318917 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
├─1318940 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat →
└─1318943 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 →
Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): fa-mlat-client 0.2.13 starting up
Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): Using UDP transport to 206.253.80.201 port 5406
Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): Listening for Beast-format results connection on port 30105
Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): Listening for Extended Basestation-format results connecti>
Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): Route MTU changed to 1500
Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): Input connected to localhost:30005
Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): Input format changed to BEAST, 12MHz clock
Sep 14 15:36:14 rpi2 piaware[1318917]: piaware received a message from dump1090-fa!
Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): Beast-format results connection with ::1:30104: connection>
Sep 14 15:36:14 rpi2 piaware[1318917]: piaware has successfully sent several msgs to FlightAware!
Sep 14 15:36:10 rpi2 piaware[1301073]: faup1090 exited with SIG SIGTERM
Sep 14 15:36:10 rpi2 piaware[1301073]: multilateration data no longer required, disabling mlat client
Sep 14 15:36:10 rpi2 piaware[1301073]: fa-mlat-client exited with SIG SIGTERM
Sep 14 15:36:10 rpi2 piaware[1301073]: removing pidfile /run/piaware/piaware.pid
Sep 14 15:36:10 rpi2 piaware[1301073]: piaware (process 1301073) is exiting…
Sep 14 15:36:10 rpi2 piaware[1318917]: creating pidfile /run/piaware/piaware.pid
Sep 14 15:36:10 rpi2 piaware[1318917]: ****************************************************
Sep 14 15:36:10 rpi2 piaware[1318917]: piaware version 9.0.1 is running, process ID 1318917
Sep 14 15:36:10 rpi2 piaware[1318917]: your system info is: Linux rpi2 6.6.26-v8+ #1754 SMP PREEMPT Thu Apr 11 14:49:11 BST 2024 aarch64 GNU/Linux
Sep 14 15:36:12 rpi2 piaware[1318917]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Sep 14 15:36:12 rpi2 piaware[1318917]: Connection with adept server at piaware.flightaware.com/1200 established
Sep 14 15:36:12 rpi2 piaware[1318917]: TLS handshake with adept server at piaware.flightaware.com/1200 completed
Sep 14 15:36:12 rpi2 piaware[1318917]: FlightAware server certificate validated
Sep 14 15:36:12 rpi2 piaware[1318917]: encrypted session established with FlightAware
Sep 14 15:36:13 rpi2 piaware[1318917]: adept reported location: -…
Sep 14 15:36:13 rpi2 piaware[1318917]: logged in to FlightAware as user …
Sep 14 15:36:13 rpi2 piaware[1318917]: my feeder ID is …
Sep 14 15:36:13 rpi2 piaware[1318917]: site statistics URL: voyteke ADS-B Feeder Statistics - FlightAware
Sep 14 15:36:13 rpi2 piaware[1318917]: ADS-B data program ‘dump1090-fa’ is listening on port 30005, so far so good
Sep 14 15:36:13 rpi2 piaware[1318917]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout …
Sep 14 15:36:13 rpi2 piaware[1318917]: Started faup1090 (pid 1318940) to connect to dump1090-fa
Sep 14 15:36:13 rpi2 piaware[1318917]: UAT support disabled by local configuration setting: uat-receiver-type
Sep 14 15:36:13 rpi2 piaware[1318917]: multilateration data requested
Sep 14 15:36:13 rpi2 piaware[1318917]: 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 206.253.80.201:5406:2932494521
Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): fa-mlat-client 0.2.13 starting up
Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): Using UDP transport to 206.253.80.201 port 5406
Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): Listening for Beast-format results connection on port 30105
Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): Listening for Extended Basestation-format results connection on port 30106
Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): Route MTU changed to 1500
Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): Input connected to localhost:30005
Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): Input format changed to BEAST, 12MHz clock
Sep 14 15:36:14 rpi2 piaware[1318917]: piaware received a message from dump1090-fa!
Sep 14 15:36:14 rpi2 piaware[1318917]: mlat-client(1318943): Beast-format results connection with ::1:30104: connection established
Sep 14 15:36:14 rpi2 piaware[1318917]: piaware has successfully sent several msgs to FlightAware!
Sep 14 15:36:45 rpi2 piaware[1318917]: 233 msgs recv’d from dump1090-fa; 233 msgs sent to FlightAware
when it failed
Sep 10 14:28:18 rpi2 piaware[3070594]: mlat-client(3070619): Server status: synchronized with 209 nearby receivers
Sep 10 14:43:19 rpi2 piaware[3070594]: mlat-client(3070619): Server status: not synchronized with any nearby receivers