FlightAware Discussions

Required packages for running piaware, and more about mlats

Thanks. I should have been more specific. I meant that as a question directed to @abcd567 asking him whether his setup is keeping in sync consistently or if it’s just getting lucky sometimes.

Few minutes ago I checked my stats, mlat button is red.

Now you see me, now you dont…

1 Like

I see.

You could always install a linux onto an USB stick from another USB stick while using the EeePC for example.
You could probably install it onto the harddrive but i get the impression you want to keep even that old Windows intact :wink:

Nicely explained here:
Anyone working with the new x86 Raspbian

That way you could use the EeePC for your piaware needs without any VM problems.
(Could well be that the WiFi will not work but maybe you have some ethernet cable)

1 Like

Thanks. Yes, I’m considering trying this next. Actually there is quite a bit of info out there about putting Linux on an Asus Eee PC. It looks a bit daunting and not entirely foolproof. But I don’t mind taking a chance mucking it up, though if I could keep from blowing away Windows on it, that would be nice. I also have an old RPi B+ that I’ve never used. But that’s probably not capable enough.

That’s plenty.
Write piaware to an sd-card and you are all good.

2 Likes

:heart: RPi rocks :heart:

.

1 Like

… and if you must use x64_x86, then

:heart: Raspberry Pi Desktop rocks :heart:

.

2 Likes

Trying to fine-tune my VM setup (piaware running on Ubuntu 16 on VMware Player 6 on WIndows 10 (32-bit) on Asus Eee PC netbook circa 2010 with Atom CPU). Reduced size of VM memory to minimum (512 MB) in order to reduce memory pressure on the host OS (Windows 10). Shutdown all other apps on the laptop. So far, so good. Real test will be if it stays in sync for an extended period of time.

System rebooted overnight. I’ve since turned off automatic updates.

cpk@ubuntu:~$ sudo systemctl status piaware -l
● piaware.service - FlightAware ADS-B uploader
   Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2019-03-06 21:32:06 PST; 17min ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 775 (piaware)
   CGroup: /system.slice/piaware.service
           ├─ 775 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
           ├─1112 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout
           └─1117 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,loc

Mar 06 21:34:16 ubuntu piaware[775]: mlat-client(1117): Beast-format results connection with ::1:30104: connection established
Mar 06 21:37:43 ubuntu piaware[775]: 477 msgs recv'd from dump1090-fa (477 in last 5m); 477 msgs sent to FlightAware
Mar 06 21:42:43 ubuntu piaware[775]: 1123 msgs recv'd from dump1090-fa (646 in last 5m); 1123 msgs sent to FlightAware
Mar 06 21:47:43 ubuntu piaware[775]: 1776 msgs recv'd from dump1090-fa (653 in last 5m); 1776 msgs sent to FlightAware
Mar 06 21:49:15 ubuntu piaware[775]: mlat-client(1117): Receiver status: connected
Mar 06 21:49:15 ubuntu piaware[775]: mlat-client(1117): Server status:   synchronized with 190 nearby receivers
Mar 06 21:49:15 ubuntu piaware[775]: mlat-client(1117): Receiver:   86.3 msg/s received       28.5 msg/s processed (33%)
Mar 06 21:49:15 ubuntu piaware[775]: mlat-client(1117): Server:      0.0 kB/s from server    0.0kB/s TCP to server     0.3kB/s UDP to serve
Mar 06 21:49:15 ubuntu piaware[775]: mlat-client(1117): Results:  1.8 positions/minute
Mar 06 21:49:15 ubuntu piaware[775]: mlat-client(1117): Aircraft: 4 of 6 Mode S, 16 of 16 ADS-B used

● piaware.service - FlightAware ADS-B uploader
   Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2019-03-06 21:32:06 PST; 32min ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 775 (piaware)
   CGroup: /system.slice/piaware.service
           ├─ 775 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
           ├─1112 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout
           └─1117 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,loc

Mar 06 21:49:15 ubuntu piaware[775]: mlat-client(1117): Aircraft: 4 of 6 Mode S, 16 of 16 ADS-B used
Mar 06 21:52:43 ubuntu piaware[775]: 2477 msgs recv'd from dump1090-fa (701 in last 5m); 2477 msgs sent to FlightAware
Mar 06 21:57:43 ubuntu piaware[775]: 3184 msgs recv'd from dump1090-fa (707 in last 5m); 3184 msgs sent to FlightAware
Mar 06 22:02:43 ubuntu piaware[775]: 3800 msgs recv'd from dump1090-fa (616 in last 5m); 3800 msgs sent to FlightAware
Mar 06 22:04:15 ubuntu piaware[775]: mlat-client(1117): Receiver status: connected
Mar 06 22:04:15 ubuntu piaware[775]: mlat-client(1117): Server status:   synchronized with 222 nearby receivers
Mar 06 22:04:15 ubuntu piaware[775]: mlat-client(1117): Receiver:   99.4 msg/s received       26.7 msg/s processed (27%)
Mar 06 22:04:15 ubuntu piaware[775]: mlat-client(1117): Server:      0.0 kB/s from server    0.0kB/s TCP to server     0.3kB/s UDP to serve
Mar 06 22:04:15 ubuntu piaware[775]: mlat-client(1117): Results:  4.1 positions/minute
Mar 06 22:04:15 ubuntu piaware[775]: mlat-client(1117): Aircraft: 3 of 11 Mode S, 10 of 10 ADS-B used
● piaware.service - FlightAware ADS-B uploader
   Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2019-03-06 21:32:06 PST; 48min ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 775 (piaware)
   CGroup: /system.slice/piaware.service
           ├─ 775 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
           ├─1112 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout 
           └─1117 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,loc

Mar 06 22:04:15 ubuntu piaware[775]: mlat-client(1117): Aircraft: 3 of 11 Mode S, 10 of 10 ADS-B used
Mar 06 22:07:43 ubuntu piaware[775]: 4312 msgs recv'd from dump1090-fa (512 in last 5m); 4312 msgs sent to FlightAware
Mar 06 22:12:43 ubuntu piaware[775]: 4736 msgs recv'd from dump1090-fa (424 in last 5m); 4736 msgs sent to FlightAware
Mar 06 22:17:43 ubuntu piaware[775]: 5327 msgs recv'd from dump1090-fa (591 in last 5m); 5327 msgs sent to FlightAware
Mar 06 22:19:16 ubuntu piaware[775]: mlat-client(1117): Receiver status: connected
Mar 06 22:19:16 ubuntu piaware[775]: mlat-client(1117): Server status:   synchronized with 253 nearby receivers
Mar 06 22:19:16 ubuntu piaware[775]: mlat-client(1117): Receiver:   88.2 msg/s received       22.7 msg/s processed (26%)
Mar 06 22:19:16 ubuntu piaware[775]: mlat-client(1117): Server:      0.0 kB/s from server    0.0kB/s TCP to server     0.3kB/s UDP to serve
Mar 06 22:19:16 ubuntu piaware[775]: mlat-client(1117): Results:  8.2 positions/minute
Mar 06 22:19:16 ubuntu piaware[775]: mlat-client(1117): Aircraft: 8 of 12 Mode S, 10 of 10 ADS-B used
● piaware.service - FlightAware ADS-B uploader
   Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2019-03-06 21:32:06 PST; 1h 3min ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 775 (piaware)
   CGroup: /system.slice/piaware.service
           ├─ 775 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
           ├─1112 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout
           └─1117 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,loc

Mar 06 22:19:16 ubuntu piaware[775]: mlat-client(1117): Aircraft: 8 of 12 Mode S, 10 of 10 ADS-B used
Mar 06 22:22:43 ubuntu piaware[775]: 5911 msgs recv'd from dump1090-fa (584 in last 5m); 5911 msgs sent to FlightAware
Mar 06 22:27:43 ubuntu piaware[775]: 6485 msgs recv'd from dump1090-fa (574 in last 5m); 6485 msgs sent to FlightAware
Mar 06 22:32:43 ubuntu piaware[775]: 7059 msgs recv'd from dump1090-fa (574 in last 5m); 7059 msgs sent to FlightAware
Mar 06 22:34:16 ubuntu piaware[775]: mlat-client(1117): Receiver status: connected
Mar 06 22:34:16 ubuntu piaware[775]: mlat-client(1117): Server status:   synchronized with 206 nearby receivers
Mar 06 22:34:16 ubuntu piaware[775]: mlat-client(1117): Receiver:   97.3 msg/s received       23.1 msg/s processed (24%)
Mar 06 22:34:16 ubuntu piaware[775]: mlat-client(1117): Server:      0.0 kB/s from server    0.0kB/s TCP to server     0.3kB/s UDP to serve
Mar 06 22:34:16 ubuntu piaware[775]: mlat-client(1117): Results:  3.9 positions/minute
Mar 06 22:34:16 ubuntu piaware[775]: mlat-client(1117): Aircraft: 5 of 10 Mode S, 9 of 9 ADS-B used
cpk@ubuntu:~$ journalctl -u piaware | grep 'Receiver status\|Server status'
Mar 06 21:49:15 ubuntu piaware[775]: mlat-client(1117): Receiver status: connected
Mar 06 21:49:15 ubuntu piaware[775]: mlat-client(1117): Server status:   synchronized with 190 nearby receivers
Mar 06 22:04:15 ubuntu piaware[775]: mlat-client(1117): Receiver status: connected
Mar 06 22:04:15 ubuntu piaware[775]: mlat-client(1117): Server status:   synchronized with 222 nearby receivers
Mar 06 22:19:16 ubuntu piaware[775]: mlat-client(1117): Receiver status: connected
Mar 06 22:19:16 ubuntu piaware[775]: mlat-client(1117): Server status:   synchronized with 253 nearby receivers
Mar 06 22:34:16 ubuntu piaware[775]: mlat-client(1117): Receiver status: connected
Mar 06 22:34:16 ubuntu piaware[775]: mlat-client(1117): Server status:   synchronized with 206 nearby receivers
1 Like

OK, I think I can declare this experiment a success (running piaware running on Ubuntu 16 on VMware Player 6 on WIndows 10 (32-bit) on Asus Eee PC netbook circa 2010 with Atom CPU). Setting the VM’s memory size to the minimum (512 MB) and not running any other apps on the host laptop seems to help.

I plan to get piaware / dump1090-fa running on a RPi, as it would consume much less power than the Asus netbook. But this was an interesting experiment, and I learned a lot in the process. Thanks to all of you for your kind help and information throughout this process.

● piaware.service - FlightAware ADS-B uploader
   Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2019-03-07 03:55:32 PST; 42min ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 777 (piaware)

Mar 07 04:21:11 ubuntu piaware[777]: 145 msgs recv'd from dump1090-fa (57 in last 5m); 145 msgs sent to FlightAware
Mar 07 04:26:11 ubuntu piaware[777]: 204 msgs recv'd from dump1090-fa (59 in last 5m); 204 msgs sent to FlightAware
Mar 07 04:26:42 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 04:26:42 ubuntu piaware[777]: mlat-client(913): Server status:   clock unstable
Mar 07 04:26:42 ubuntu piaware[777]: mlat-client(913): Receiver:    3.1 msg/s received        1.7 msg/s processed (56%)
Mar 07 04:26:42 ubuntu piaware[777]: mlat-client(913): Server:      0.0 kB/s from server    0.0kB/s TCP to server     0.0kB/s UDP to server
Mar 07 04:26:42 ubuntu piaware[777]: mlat-client(913): Aircraft: 0 of 0 Mode S, 1 of 1 ADS-B used
Mar 07 04:26:42 ubuntu piaware[777]: mlat-client(913): Out-of-order timestamps: 1
Mar 07 04:31:11 ubuntu piaware[777]: 212 msgs recv'd from dump1090-fa (8 in last 5m); 212 msgs sent to FlightAware
Mar 07 04:36:11 ubuntu piaware[777]: 238 msgs recv'd from dump1090-fa (26 in last 5m); 238 msgs sent to FlightAware
● piaware.service - FlightAware ADS-B uploader
   Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2019-03-07 03:55:32 PST; 46min ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 777 (piaware)
   CGroup: /system.slice/piaware.service
           ├─777 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
           ├─910 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout 
           └─913 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,loca

Mar 07 04:26:42 ubuntu piaware[777]: mlat-client(913): Out-of-order timestamps: 1
Mar 07 04:31:11 ubuntu piaware[777]: 212 msgs recv'd from dump1090-fa (8 in last 5m); 212 msgs sent to FlightAware
Mar 07 04:36:11 ubuntu piaware[777]: 238 msgs recv'd from dump1090-fa (26 in last 5m); 238 msgs sent to FlightAware
Mar 07 04:41:11 ubuntu piaware[777]: 313 msgs recv'd from dump1090-fa (75 in last 5m); 313 msgs sent to FlightAware
Mar 07 04:41:43 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 04:41:43 ubuntu piaware[777]: mlat-client(913): Server status:   clock unstable
Mar 07 04:41:43 ubuntu piaware[777]: mlat-client(913): Receiver:    4.6 msg/s received        2.7 msg/s processed (60%)
Mar 07 04:41:43 ubuntu piaware[777]: mlat-client(913): Server:      0.0 kB/s from server    0.0kB/s TCP to server     0.0kB/s UDP to server
Mar 07 04:41:43 ubuntu piaware[777]: mlat-client(913): Aircraft: 1 of 1 Mode S, 2 of 2 ADS-B used
Mar 07 04:41:43 ubuntu piaware[777]: mlat-client(913): Out-of-order timestamps: 1
● piaware.service - FlightAware ADS-B uploader
   Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2019-03-07 03:55:32 PST; 1h 1min ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 777 (piaware)
   CGroup: /system.slice/piaware.service
           ├─777 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
           ├─910 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout
           └─913 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,loca

Mar 07 04:41:43 ubuntu piaware[777]: mlat-client(913): Aircraft: 1 of 1 Mode S, 2 of 2 ADS-B used
Mar 07 04:41:43 ubuntu piaware[777]: mlat-client(913): Out-of-order timestamps: 1
Mar 07 04:46:11 ubuntu piaware[777]: 397 msgs recv'd from dump1090-fa (84 in last 5m); 397 msgs sent to FlightAware
Mar 07 04:51:11 ubuntu piaware[777]: 460 msgs recv'd from dump1090-fa (63 in last 5m); 460 msgs sent to FlightAware
Mar 07 04:56:11 ubuntu piaware[777]: 504 msgs recv'd from dump1090-fa (44 in last 5m); 504 msgs sent to FlightAware
Mar 07 04:56:43 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 04:56:43 ubuntu piaware[777]: mlat-client(913): Server status:   not synchronized with any nearby receivers
Mar 07 04:56:43 ubuntu piaware[777]: mlat-client(913): Receiver:    1.9 msg/s received        1.0 msg/s processed (54%)
Mar 07 04:56:43 ubuntu piaware[777]: mlat-client(913): Server:      0.0 kB/s from server    0.0kB/s TCP to server     0.0kB/s UDP to server
Mar 07 04:56:43 ubuntu piaware[777]: mlat-client(913): Aircraft: 1 of 1 Mode S, 0 of 0 ADS-B used
● piaware.service - FlightAware ADS-B uploader
   Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2019-03-07 03:55:32 PST; 1h 17min ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 777 (piaware)
   CGroup: /system.slice/piaware.service
           ├─777 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
           ├─910 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout
           └─913 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,loca

Mar 07 04:56:43 ubuntu piaware[777]: mlat-client(913): Aircraft: 1 of 1 Mode S, 0 of 0 ADS-B used
Mar 07 05:01:11 ubuntu piaware[777]: 518 msgs recv'd from dump1090-fa (14 in last 5m); 518 msgs sent to FlightAware
Mar 07 05:06:11 ubuntu piaware[777]: 529 msgs recv'd from dump1090-fa (11 in last 5m); 529 msgs sent to FlightAware
Mar 07 05:11:11 ubuntu piaware[777]: 561 msgs recv'd from dump1090-fa (32 in last 5m); 561 msgs sent to FlightAware
Mar 07 05:11:43 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 05:11:43 ubuntu piaware[777]: mlat-client(913): Server status:   not synchronized with any nearby receivers
Mar 07 05:11:43 ubuntu piaware[777]: mlat-client(913): Receiver:    0.3 msg/s received        0.1 msg/s processed (34%)
Mar 07 05:11:43 ubuntu piaware[777]: mlat-client(913): Server:      0.0 kB/s from server    0.0kB/s TCP to server     0.0kB/s UDP to server
Mar 07 05:11:43 ubuntu piaware[777]: mlat-client(913): Aircraft: 0 of 1 Mode S, 1 of 1 ADS-B used
Mar 07 05:11:43 ubuntu piaware[777]: mlat-client(913): Out-of-order timestamps: 1
● piaware.service - FlightAware ADS-B uploader
   Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2019-03-07 03:55:32 PST; 1h 31min ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 777 (piaware)
   CGroup: /system.slice/piaware.service
           ├─777 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
           ├─910 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout 
           └─913 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,loca

Mar 07 05:11:43 ubuntu piaware[777]: mlat-client(913): Out-of-order timestamps: 1
Mar 07 05:16:11 ubuntu piaware[777]: 635 msgs recv'd from dump1090-fa (74 in last 5m); 635 msgs sent to FlightAware
Mar 07 05:21:11 ubuntu piaware[777]: 793 msgs recv'd from dump1090-fa (158 in last 5m); 793 msgs sent to FlightAware
Mar 07 05:26:11 ubuntu piaware[777]: 945 msgs recv'd from dump1090-fa (152 in last 5m); 945 msgs sent to FlightAware
Mar 07 05:26:44 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 05:26:44 ubuntu piaware[777]: mlat-client(913): Server status:   synchronized with 120 nearby receivers
Mar 07 05:26:44 ubuntu piaware[777]: mlat-client(913): Receiver:   13.1 msg/s received        6.9 msg/s processed (52%)
Mar 07 05:26:44 ubuntu piaware[777]: mlat-client(913): Server:      0.0 kB/s from server    0.0kB/s TCP to server     0.1kB/s UDP to server
Mar 07 05:26:44 ubuntu piaware[777]: mlat-client(913): Results:  2.0 positions/minute
Mar 07 05:26:44 ubuntu piaware[777]: mlat-client(913): Aircraft: 1 of 1 Mode S, 1 of 1 ADS-B used
● piaware.service - FlightAware ADS-B uploader
   Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2019-03-07 03:55:32 PST; 1h 46min ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 777 (piaware)
   CGroup: /system.slice/piaware.service
           ├─777 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
           ├─910 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout 
           └─913 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,loca

Mar 07 05:26:44 ubuntu piaware[777]: mlat-client(913): Aircraft: 1 of 1 Mode S, 1 of 1 ADS-B used
Mar 07 05:31:11 ubuntu piaware[777]: 1023 msgs recv'd from dump1090-fa (78 in last 5m); 1023 msgs sent to FlightAware
Mar 07 05:36:11 ubuntu piaware[777]: 1123 msgs recv'd from dump1090-fa (100 in last 5m); 1123 msgs sent to FlightAware
Mar 07 05:41:11 ubuntu piaware[777]: 1329 msgs recv'd from dump1090-fa (206 in last 5m); 1329 msgs sent to FlightAware
Mar 07 05:41:44 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 05:41:44 ubuntu piaware[777]: mlat-client(913): Server status:   synchronized with 187 nearby receivers
Mar 07 05:41:44 ubuntu piaware[777]: mlat-client(913): Receiver:   11.4 msg/s received        5.5 msg/s processed (48%)
Mar 07 05:41:44 ubuntu piaware[777]: mlat-client(913): Server:      0.0 kB/s from server    0.0kB/s TCP to server     0.1kB/s UDP to server
Mar 07 05:41:44 ubuntu piaware[777]: mlat-client(913): Results:  2.2 positions/minute
Mar 07 05:41:44 ubuntu piaware[777]: mlat-client(913): Aircraft: 0 of 3 Mode S, 4 of 4 ADS-B used
● piaware.service - FlightAware ADS-B uploader
   Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2019-03-07 03:55:32 PST; 2h 3min ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 777 (piaware)
   CGroup: /system.slice/piaware.service
           ├─777 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
           ├─910 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout 
           └─913 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,loca

Mar 07 05:41:44 ubuntu piaware[777]: mlat-client(913): Aircraft: 0 of 3 Mode S, 4 of 4 ADS-B used
Mar 07 05:46:11 ubuntu piaware[777]: 1479 msgs recv'd from dump1090-fa (150 in last 5m); 1479 msgs sent to FlightAware
Mar 07 05:51:11 ubuntu piaware[777]: 1599 msgs recv'd from dump1090-fa (120 in last 5m); 1599 msgs sent to FlightAware
Mar 07 05:56:11 ubuntu piaware[777]: 1747 msgs recv'd from dump1090-fa (148 in last 5m); 1747 msgs sent to FlightAware
Mar 07 05:56:45 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 05:56:45 ubuntu piaware[777]: mlat-client(913): Server status:   clock unstable
Mar 07 05:56:45 ubuntu piaware[777]: mlat-client(913): Receiver:   13.1 msg/s received        5.9 msg/s processed (45%)
Mar 07 05:56:45 ubuntu piaware[777]: mlat-client(913): Server:      0.0 kB/s from server    0.0kB/s TCP to server     0.1kB/s UDP to server
Mar 07 05:56:45 ubuntu piaware[777]: mlat-client(913): Results:  3.9 positions/minute
Mar 07 05:56:45 ubuntu piaware[777]: mlat-client(913): Aircraft: 0 of 0 Mode S, 3 of 3 ADS-B used
● piaware.service - FlightAware ADS-B uploader
   Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2019-03-07 03:55:32 PST; 2h 19min ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 777 (piaware)
   CGroup: /system.slice/piaware.service
           ├─777 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
           ├─910 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout
           └─913 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,loca

Mar 07 05:56:45 ubuntu piaware[777]: mlat-client(913): Aircraft: 0 of 0 Mode S, 3 of 3 ADS-B used
Mar 07 06:01:11 ubuntu piaware[777]: 1855 msgs recv'd from dump1090-fa (108 in last 5m); 1855 msgs sent to FlightAware
Mar 07 06:06:11 ubuntu piaware[777]: 2041 msgs recv'd from dump1090-fa (186 in last 5m); 2041 msgs sent to FlightAware
Mar 07 06:11:11 ubuntu piaware[777]: 2193 msgs recv'd from dump1090-fa (152 in last 5m); 2193 msgs sent to FlightAware
Mar 07 06:11:45 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 06:11:45 ubuntu piaware[777]: mlat-client(913): Server status:   synchronized with 169 nearby receivers
Mar 07 06:11:45 ubuntu piaware[777]: mlat-client(913): Receiver:   13.0 msg/s received        4.9 msg/s processed (37%)
Mar 07 06:11:45 ubuntu piaware[777]: mlat-client(913): Server:      0.0 kB/s from server    0.0kB/s TCP to server     0.1kB/s UDP to server
Mar 07 06:11:45 ubuntu piaware[777]: mlat-client(913): Results:  1.3 positions/minute
Mar 07 06:11:45 ubuntu piaware[777]: mlat-client(913): Aircraft: 1 of 2 Mode S, 4 of 4 ADS-B used
● piaware.service - FlightAware ADS-B uploader
   Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2019-03-07 03:55:32 PST; 2h 31min ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 777 (piaware)
   CGroup: /system.slice/piaware.service
           ├─777 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
           ├─910 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout 
           └─913 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,loca

Mar 07 06:11:45 ubuntu piaware[777]: mlat-client(913): Results:  1.3 positions/minute
Mar 07 06:11:45 ubuntu piaware[777]: mlat-client(913): Aircraft: 1 of 2 Mode S, 4 of 4 ADS-B used
Mar 07 06:16:11 ubuntu piaware[777]: 2330 msgs recv'd from dump1090-fa (137 in last 5m); 2330 msgs sent to FlightAware
Mar 07 06:21:11 ubuntu piaware[777]: 2572 msgs recv'd from dump1090-fa (242 in last 5m); 2572 msgs sent to FlightAware
Mar 07 06:26:11 ubuntu piaware[777]: 2826 msgs recv'd from dump1090-fa (254 in last 5m); 2826 msgs sent to FlightAware
Mar 07 06:26:46 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 06:26:46 ubuntu piaware[777]: mlat-client(913): Server status:   clock unstable
Mar 07 06:26:46 ubuntu piaware[777]: mlat-client(913): Receiver:   35.5 msg/s received       11.5 msg/s processed (32%)
Mar 07 06:26:46 ubuntu piaware[777]: mlat-client(913): Server:      0.0 kB/s from server    0.0kB/s TCP to server     0.2kB/s UDP to server
Mar 07 06:26:46 ubuntu piaware[777]: mlat-client(913): Aircraft: 0 of 2 Mode S, 4 of 4 ADS-B used
● piaware.service - FlightAware ADS-B uploader
   Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2019-03-07 03:55:32 PST; 2h 46min ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 777 (piaware)
   CGroup: /system.slice/piaware.service
           ├─777 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
           ├─910 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout 
           └─913 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,loca

Mar 07 06:26:46 ubuntu piaware[777]: mlat-client(913): Aircraft: 0 of 2 Mode S, 4 of 4 ADS-B used
Mar 07 06:31:11 ubuntu piaware[777]: 3039 msgs recv'd from dump1090-fa (213 in last 5m); 3039 msgs sent to FlightAware
Mar 07 06:36:11 ubuntu piaware[777]: 3221 msgs recv'd from dump1090-fa (182 in last 5m); 3221 msgs sent to FlightAware
Mar 07 06:41:11 ubuntu piaware[777]: 3472 msgs recv'd from dump1090-fa (251 in last 5m); 3472 msgs sent to FlightAware
Mar 07 06:41:47 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 06:41:47 ubuntu piaware[777]: mlat-client(913): Server status:   synchronized with 224 nearby receivers
Mar 07 06:41:47 ubuntu piaware[777]: mlat-client(913): Receiver:   32.5 msg/s received       11.2 msg/s processed (34%)
Mar 07 06:41:47 ubuntu piaware[777]: mlat-client(913): Server:      0.0 kB/s from server    0.0kB/s TCP to server     0.1kB/s UDP to server
Mar 07 06:41:47 ubuntu piaware[777]: mlat-client(913): Results:  0.9 positions/minute
Mar 07 06:41:47 ubuntu piaware[777]: mlat-client(913): Aircraft: 4 of 5 Mode S, 4 of 4 ADS-B used
● piaware.service - FlightAware ADS-B uploader
   Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2019-03-07 03:55:32 PST; 3h 6min ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 777 (piaware)
   CGroup: /system.slice/piaware.service
           ├─777 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
           ├─910 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout 
           └─913 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,loca

Mar 07 06:46:11 ubuntu piaware[777]: 3715 msgs recv'd from dump1090-fa (243 in last 5m); 3715 msgs sent to FlightAware
Mar 07 06:51:11 ubuntu piaware[777]: 3994 msgs recv'd from dump1090-fa (279 in last 5m); 3994 msgs sent to FlightAware
Mar 07 06:56:11 ubuntu piaware[777]: 4356 msgs recv'd from dump1090-fa (362 in last 5m); 4356 msgs sent to FlightAware
Mar 07 06:56:47 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 06:56:47 ubuntu piaware[777]: mlat-client(913): Server status:   clock unstable
Mar 07 06:56:47 ubuntu piaware[777]: mlat-client(913): Receiver:   37.8 msg/s received       11.4 msg/s processed (30%)
Mar 07 06:56:47 ubuntu piaware[777]: mlat-client(913): Server:      0.0 kB/s from server    0.0kB/s TCP to server     0.1kB/s UDP to server
Mar 07 06:56:47 ubuntu piaware[777]: mlat-client(913): Results:  5.7 positions/minute
Mar 07 06:56:47 ubuntu piaware[777]: mlat-client(913): Aircraft: 2 of 2 Mode S, 7 of 8 ADS-B used
Mar 07 07:01:11 ubuntu piaware[777]: 4636 msgs recv'd from dump1090-fa (280 in last 5m); 4636 msgs sent to FlightAware
● piaware.service - FlightAware ADS-B uploader
   Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2019-03-07 03:55:32 PST; 3h 16min ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 777 (piaware)
   CGroup: /system.slice/piaware.service
           ├─777 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
           ├─910 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout 
           └─913 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,loca

Mar 07 06:56:47 ubuntu piaware[777]: mlat-client(913): Aircraft: 2 of 2 Mode S, 7 of 8 ADS-B used
Mar 07 07:01:11 ubuntu piaware[777]: 4636 msgs recv'd from dump1090-fa (280 in last 5m); 4636 msgs sent to FlightAware
Mar 07 07:06:11 ubuntu piaware[777]: 4950 msgs recv'd from dump1090-fa (314 in last 5m); 4950 msgs sent to FlightAware
Mar 07 07:11:11 ubuntu piaware[777]: 5318 msgs recv'd from dump1090-fa (368 in last 5m); 5318 msgs sent to FlightAware
Mar 07 07:11:47 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 07:11:47 ubuntu piaware[777]: mlat-client(913): Server status:   synchronized with 254 nearby receivers
Mar 07 07:11:47 ubuntu piaware[777]: mlat-client(913): Receiver:   47.8 msg/s received       17.1 msg/s processed (36%)
Mar 07 07:11:47 ubuntu piaware[777]: mlat-client(913): Server:      0.0 kB/s from server    0.0kB/s TCP to server     0.2kB/s UDP to server
Mar 07 07:11:48 ubuntu piaware[777]: mlat-client(913): Results:  1.9 positions/minute
Mar 07 07:11:48 ubuntu piaware[777]: mlat-client(913): Aircraft: 2 of 4 Mode S, 7 of 7 ADS-B used
● piaware.service - FlightAware ADS-B uploader
   Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2019-03-07 03:55:32 PST; 3h 32min ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 777 (piaware)
   CGroup: /system.slice/piaware.service
           ├─777 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
           ├─910 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout 
           └─913 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,loca

Mar 07 07:11:48 ubuntu piaware[777]: mlat-client(913): Aircraft: 2 of 4 Mode S, 7 of 7 ADS-B used
Mar 07 07:16:11 ubuntu piaware[777]: 5604 msgs recv'd from dump1090-fa (286 in last 5m); 5604 msgs sent to FlightAware
Mar 07 07:21:11 ubuntu piaware[777]: 5958 msgs recv'd from dump1090-fa (354 in last 5m); 5958 msgs sent to FlightAware
Mar 07 07:26:11 ubuntu piaware[777]: 6431 msgs recv'd from dump1090-fa (473 in last 5m); 6431 msgs sent to FlightAware
Mar 07 07:26:48 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 07:26:48 ubuntu piaware[777]: mlat-client(913): Server status:   synchronized with 223 nearby receivers
Mar 07 07:26:48 ubuntu piaware[777]: mlat-client(913): Receiver:   58.0 msg/s received       15.7 msg/s processed (27%)
Mar 07 07:26:48 ubuntu piaware[777]: mlat-client(913): Server:      0.0 kB/s from server    0.0kB/s TCP to server     0.2kB/s UDP to server
Mar 07 07:26:48 ubuntu piaware[777]: mlat-client(913): Results:  6.0 positions/minute
Mar 07 07:26:48 ubuntu piaware[777]: mlat-client(913): Aircraft: 3 of 7 Mode S, 5 of 6 ADS-B used
● piaware.service - FlightAware ADS-B uploader
   Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2019-03-07 03:55:32 PST; 3h 46min ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 777 (piaware)
   CGroup: /system.slice/piaware.service
           ├─777 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
           ├─910 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout 
           └─913 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,loca

Mar 07 07:26:48 ubuntu piaware[777]: mlat-client(913): Aircraft: 3 of 7 Mode S, 5 of 6 ADS-B used
Mar 07 07:31:11 ubuntu piaware[777]: 6905 msgs recv'd from dump1090-fa (474 in last 5m); 6905 msgs sent to FlightAware
Mar 07 07:36:11 ubuntu piaware[777]: 7415 msgs recv'd from dump1090-fa (510 in last 5m); 7415 msgs sent to FlightAware
Mar 07 07:41:11 ubuntu piaware[777]: 7793 msgs recv'd from dump1090-fa (378 in last 5m); 7793 msgs sent to FlightAware
Mar 07 07:41:48 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 07:41:48 ubuntu piaware[777]: mlat-client(913): Server status:   synchronized with 16 nearby receivers
Mar 07 07:41:48 ubuntu piaware[777]: mlat-client(913): Receiver:   78.2 msg/s received       21.3 msg/s processed (27%)
Mar 07 07:41:48 ubuntu piaware[777]: mlat-client(913): Server:      0.0 kB/s from server    0.0kB/s TCP to server     0.3kB/s UDP to server
Mar 07 07:41:48 ubuntu piaware[777]: mlat-client(913): Results:  7.9 positions/minute
Mar 07 07:41:48 ubuntu piaware[777]: mlat-client(913): Aircraft: 3 of 8 Mode S, 7 of 7 ADS-B used
● piaware.service - FlightAware ADS-B uploader
   Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2019-03-07 03:55:32 PST; 4h 1min ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 777 (piaware)
   CGroup: /system.slice/piaware.service
           ├─777 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
           ├─910 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout 
           └─913 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,loca

Mar 07 07:41:48 ubuntu piaware[777]: mlat-client(913): Aircraft: 3 of 8 Mode S, 7 of 7 ADS-B used
Mar 07 07:46:11 ubuntu piaware[777]: 8231 msgs recv'd from dump1090-fa (438 in last 5m); 8231 msgs sent to FlightAware
Mar 07 07:51:11 ubuntu piaware[777]: 8650 msgs recv'd from dump1090-fa (419 in last 5m); 8650 msgs sent to FlightAware
Mar 07 07:56:11 ubuntu piaware[777]: 9117 msgs recv'd from dump1090-fa (467 in last 5m); 9117 msgs sent to FlightAware
Mar 07 07:56:48 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 07:56:48 ubuntu piaware[777]: mlat-client(913): Server status:   synchronized with 279 nearby receivers
Mar 07 07:56:49 ubuntu piaware[777]: mlat-client(913): Receiver:   72.6 msg/s received       21.8 msg/s processed (30%)
Mar 07 07:56:49 ubuntu piaware[777]: mlat-client(913): Server:      0.0 kB/s from server    0.0kB/s TCP to server     0.3kB/s UDP to server
Mar 07 07:56:49 ubuntu piaware[777]: mlat-client(913): Results:  7.0 positions/minute
Mar 07 07:56:49 ubuntu piaware[777]: mlat-client(913): Aircraft: 4 of 13 Mode S, 10 of 10 ADS-B used
● piaware.service - FlightAware ADS-B uploader
   Loaded: loaded (/lib/systemd/system/piaware.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2019-03-07 03:55:32 PST; 4h 16min ago
     Docs: https://flightaware.com/adsb/piaware/
 Main PID: 777 (piaware)
   CGroup: /system.slice/piaware.service
           ├─777 /usr/bin/piaware -p /run/piaware/piaware.pid -plainlog -statusfile /run/piaware/status.json
           ├─910 /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout 
           └─913 /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,loca

Mar 07 07:56:49 ubuntu piaware[777]: mlat-client(913): Aircraft: 4 of 13 Mode S, 10 of 10 ADS-B used
Mar 07 08:01:11 ubuntu piaware[777]: 9649 msgs recv'd from dump1090-fa (532 in last 5m); 9649 msgs sent to FlightAware
Mar 07 08:06:11 ubuntu piaware[777]: 10238 msgs recv'd from dump1090-fa (589 in last 5m); 10238 msgs sent to FlightAware
Mar 07 08:11:11 ubuntu piaware[777]: 10687 msgs recv'd from dump1090-fa (449 in last 5m); 10687 msgs sent to FlightAware
Mar 07 08:11:49 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 08:11:49 ubuntu piaware[777]: mlat-client(913): Server status:   synchronized with 211 nearby receivers
Mar 07 08:11:49 ubuntu piaware[777]: mlat-client(913): Receiver:   83.1 msg/s received       21.4 msg/s processed (26%)
Mar 07 08:11:49 ubuntu piaware[777]: mlat-client(913): Server:      0.0 kB/s from server    0.0kB/s TCP to server     0.3kB/s UDP to server
Mar 07 08:11:49 ubuntu piaware[777]: mlat-client(913): Results:  5.5 positions/minute
Mar 07 08:11:49 ubuntu piaware[777]: mlat-client(913): Aircraft: 5 of 10 Mode S, 7 of 7 ADS-B used
cpk@ubuntu:~$ journalctl -u piaware | grep 'Receiver status\|Server status'
Mar 07 04:11:42 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 04:11:42 ubuntu piaware[777]: mlat-client(913): Server status:   not synchronized with any nearby receivers
Mar 07 04:26:42 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 04:26:42 ubuntu piaware[777]: mlat-client(913): Server status:   clock unstable
Mar 07 04:41:43 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 04:41:43 ubuntu piaware[777]: mlat-client(913): Server status:   clock unstable
Mar 07 04:56:43 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 04:56:43 ubuntu piaware[777]: mlat-client(913): Server status:   not synchronized with any nearby receivers
Mar 07 05:11:43 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 05:11:43 ubuntu piaware[777]: mlat-client(913): Server status:   not synchronized with any nearby receivers
Mar 07 05:26:44 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 05:26:44 ubuntu piaware[777]: mlat-client(913): Server status:   synchronized with 120 nearby receivers
Mar 07 05:41:44 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 05:41:44 ubuntu piaware[777]: mlat-client(913): Server status:   synchronized with 187 nearby receivers
Mar 07 05:56:45 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 05:56:45 ubuntu piaware[777]: mlat-client(913): Server status:   clock unstable
Mar 07 06:11:45 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 06:11:45 ubuntu piaware[777]: mlat-client(913): Server status:   synchronized with 169 nearby receivers
Mar 07 06:26:46 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 06:26:46 ubuntu piaware[777]: mlat-client(913): Server status:   clock unstable
Mar 07 06:41:47 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 06:41:47 ubuntu piaware[777]: mlat-client(913): Server status:   synchronized with 224 nearby receivers
Mar 07 06:56:47 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 06:56:47 ubuntu piaware[777]: mlat-client(913): Server status:   clock unstable
Mar 07 07:11:47 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 07:11:47 ubuntu piaware[777]: mlat-client(913): Server status:   synchronized with 254 nearby receivers
Mar 07 07:26:48 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 07:26:48 ubuntu piaware[777]: mlat-client(913): Server status:   synchronized with 223 nearby receivers
Mar 07 07:41:48 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 07:41:48 ubuntu piaware[777]: mlat-client(913): Server status:   synchronized with 16 nearby receivers
Mar 07 07:56:48 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 07:56:48 ubuntu piaware[777]: mlat-client(913): Server status:   synchronized with 279 nearby receivers
Mar 07 08:11:49 ubuntu piaware[777]: mlat-client(913): Receiver status: connected
Mar 07 08:11:49 ubuntu piaware[777]: mlat-client(913): Server status:   synchronized with 211 nearby receivers
2 Likes

This experiment showed that it is perfectly reasonable to run piaware / dump1090-fa in a VM. The VM had 512MB memory running Ubuntu Server version 16 32-bit Linux on VMware Player version 6. This was run on a circa 2010 Asus Eee PC netbook w/ a single-core Intel Atom N450 CPU on Windows 10 32-bit w/ 2 GB memory.

1 Like

So far so good

abcd@ubuntu:~$ journalctl -u piaware | grep 'Receiver status\|Server status'

Mar 07 11:59:17 ubuntu piaware[806]: mlat-client(1009): Receiver status: connected
Mar 07 11:59:17 ubuntu piaware[806]: mlat-client(1009): Server status:   clock unstable
Mar 07 12:14:17 ubuntu piaware[806]: mlat-client(1009): Receiver status: connected
Mar 07 12:14:17 ubuntu piaware[806]: mlat-client(1009): Server status:   synchronized with 95 nearby receivers
Mar 07 12:29:17 ubuntu piaware[806]: mlat-client(1009): Receiver status: connected
Mar 07 12:29:17 ubuntu piaware[806]: mlat-client(1009): Server status:   synchronized with 89 nearby receivers
Mar 07 12:44:17 ubuntu piaware[806]: mlat-client(1009): Receiver status: connected
Mar 07 12:44:17 ubuntu piaware[806]: mlat-client(1009): Server status:   synchronized with 86 nearby receivers
Mar 07 12:59:17 ubuntu piaware[806]: mlat-client(1009): Receiver status: connected
Mar 07 12:59:17 ubuntu piaware[806]: mlat-client(1009): Server status:   synchronized with 112 nearby receivers
Mar 07 13:14:18 ubuntu piaware[806]: mlat-client(1009): Receiver status: connected
Mar 07 13:14:18 ubuntu piaware[806]: mlat-client(1009): Server status:   synchronized with 99 nearby receivers
Mar 07 13:29:18 ubuntu piaware[806]: mlat-client(1009): Receiver status: connected
Mar 07 13:29:18 ubuntu piaware[806]: mlat-client(1009): Server status:   synchronized with 104 nearby receivers
Mar 07 13:44:19 ubuntu piaware[806]: mlat-client(1009): Receiver status: connected
Mar 07 13:44:19 ubuntu piaware[806]: mlat-client(1009): Server status:   synchronized with 101 nearby receivers
Mar 07 13:59:19 ubuntu piaware[806]: mlat-client(1009): Receiver status: connected
Mar 07 13:59:19 ubuntu piaware[806]: mlat-client(1009): Server status:   synchronized with 94 nearby receivers
Mar 07 14:14:19 ubuntu piaware[806]: mlat-client(1009): Receiver status: connected
Mar 07 14:14:19 ubuntu piaware[806]: mlat-client(1009): Server status:   synchronized with 102 nearby receivers
Mar 07 14:29:20 ubuntu piaware[806]: mlat-client(1009): Receiver status: connected
Mar 07 14:29:20 ubuntu piaware[806]: mlat-client(1009): Server status:   synchronized with 96 nearby receivers
Mar 07 14:44:21 ubuntu piaware[806]: mlat-client(1009): Receiver status: connected
Mar 07 14:44:21 ubuntu piaware[806]: mlat-client(1009): Server status:   synchronized with 87 nearby receivers
Mar 07 14:59:21 ubuntu piaware[806]: mlat-client(1009): Receiver status: connected
Mar 07 14:59:21 ubuntu piaware[806]: mlat-client(1009): Server status:   synchronized with 79 nearby receivers
2 Likes

Raspberry Pi Desktop on VMware

2 Likes

The crowning achievement of this thread was 100% due to @abcd567. I am merely reproducing @abcd567’s results and reporting them here. The recipe calls for starting with Raspberry Pi Desktop, and then following @abcd567’s excellent instructions for building and installing dump1090 and piaware (which should replace the READMEs in github.com:flightaware/{dump1090,piaware_builder}). Those precise instructions enabled me to do correct builds for the first time. I am now running dump1090 and piaware in a RPi Desktop VM with 512MB memory running on VMware Player version 6 (free for non-commercial use) on Windows 10 32-bit on an circa 2010 Asus Eee PC model 1005PEB with an Intel Atom CPU and 2GB memory. Note that if your Windows laptop can run it, you would be much better off using VMware Workstation Player version 15 (free for non-commercial use). The dongle is an early model NooElec R820T (Realtek Semiconductor Corp. RTL2838 DVB-T) with the stock indoor antenna near a window. I understand that I would have much better results if I ran dump1090/piaware on a RPi with a better dongle and an outdoor antenna. This was mainly an experiment to determine whether dump1090/piaware can run in a VM on an old Windows laptop, and the answer is definitely YES.

So far, I’ve seen only 7 ‘unstable clock’ periods in about a day and a half:

$ journalctl -u piaware | grep 'Receiver status\|Server status'
Mar 09 21:36:53 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 09 21:36:53 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 150 nearby receivers
Mar 09 21:51:54 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 09 21:51:54 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 199 nearby receivers
Mar 09 22:06:54 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 09 22:06:54 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 207 nearby receivers
Mar 09 22:21:55 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 09 22:21:55 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 205 nearby receivers
Mar 09 22:36:56 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 09 22:36:56 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 43 nearby receivers
Mar 09 22:51:56 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 09 22:51:56 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 182 nearby receivers
Mar 09 23:06:57 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 09 23:06:57 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 218 nearby receivers
Mar 09 23:21:57 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 09 23:21:57 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 190 nearby receivers
Mar 09 23:36:57 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 09 23:36:57 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 1 nearby receivers
Mar 09 23:51:58 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 09 23:51:58 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 212 nearby receivers
Mar 10 00:06:58 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 00:06:58 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 177 nearby receivers
Mar 10 00:21:59 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 00:21:59 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 169 nearby receivers
Mar 10 00:36:59 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 00:36:59 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 183 nearby receivers
Mar 10 00:51:59 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 00:51:59 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 268 nearby receivers
Mar 10 01:07:00 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 01:07:00 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 274 nearby receivers
Mar 10 01:22:00 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 01:22:00 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 112 nearby receivers
Mar 10 01:37:01 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 01:37:01 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 16 nearby receivers
Mar 10 01:52:01 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 01:52:01 raspberry piaware[817]: mlat-client(1886): Server status:   not synchronized with any nearby receivers
Mar 10 03:07:01 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 03:07:01 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 149 nearby receivers
Mar 10 03:22:01 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 03:22:01 raspberry piaware[817]: mlat-client(1886): Server status:   not synchronized with any nearby receivers
Mar 10 03:37:02 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 03:37:02 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 177 nearby receivers
Mar 10 03:52:03 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 03:52:03 raspberry piaware[817]: mlat-client(1886): Server status:   not synchronized with any nearby receivers
Mar 10 04:07:03 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 04:07:03 raspberry piaware[817]: mlat-client(1886): Server status:   not synchronized with any nearby receivers
Mar 10 04:22:03 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 04:22:03 raspberry piaware[817]: mlat-client(1886): Server status:   not synchronized with any nearby receivers
Mar 10 04:37:04 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 04:37:04 raspberry piaware[817]: mlat-client(1886): Server status:   not synchronized with any nearby receivers
Mar 10 04:52:04 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 04:52:04 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 207 nearby receivers
Mar 10 05:07:05 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 05:07:05 raspberry piaware[817]: mlat-client(1886): Server status:   not synchronized with any nearby receivers
Mar 10 05:22:05 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 05:22:05 raspberry piaware[817]: mlat-client(1886): Server status:   not synchronized with any nearby receivers
Mar 10 05:37:05 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 05:37:05 raspberry piaware[817]: mlat-client(1886): Server status:   not synchronized with any nearby receivers
Mar 10 05:52:05 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 05:52:05 raspberry piaware[817]: mlat-client(1886): Server status:   not synchronized with any nearby receivers
Mar 10 06:07:06 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 06:07:06 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 175 nearby receivers
Mar 10 06:22:06 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 06:22:06 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 222 nearby receivers
Mar 10 06:37:06 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 06:37:06 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 131 nearby receivers
Mar 10 06:52:07 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 06:52:07 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 179 nearby receivers
Mar 10 07:07:07 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 07:07:07 raspberry piaware[817]: mlat-client(1886): Server status:   not synchronized with any nearby receivers
Mar 10 07:22:08 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 07:22:08 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 227 nearby receivers
Mar 10 07:37:08 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 07:37:08 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 305 nearby receivers
Mar 10 07:52:09 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 07:52:09 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 253 nearby receivers
Mar 10 08:07:09 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 08:07:09 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 253 nearby receivers
Mar 10 08:22:09 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 08:22:10 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 234 nearby receivers
Mar 10 08:37:10 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 08:37:10 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 214 nearby receivers
Mar 10 08:52:10 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 08:52:10 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 188 nearby receivers
Mar 10 09:07:11 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 09:07:11 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 181 nearby receivers
Mar 10 09:22:11 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 09:22:11 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 248 nearby receivers
Mar 10 09:37:11 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 09:37:11 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 212 nearby receivers
Mar 10 09:52:12 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 09:52:12 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 245 nearby receivers
Mar 10 10:07:13 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 10:07:13 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 235 nearby receivers
Mar 10 10:22:13 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 10:22:13 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 259 nearby receivers
Mar 10 10:37:13 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 10:37:13 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 204 nearby receivers
Mar 10 10:52:14 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 10:52:14 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 252 nearby receivers
Mar 10 11:07:14 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 11:07:14 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 250 nearby receivers
Mar 10 11:22:15 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 11:22:15 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 303 nearby receivers
Mar 10 11:37:15 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 11:37:15 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 274 nearby receivers
Mar 10 11:52:15 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 11:52:15 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 270 nearby receivers
Mar 10 12:07:15 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 12:07:15 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 185 nearby receivers
Mar 10 12:22:16 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 12:22:16 raspberry piaware[817]: mlat-client(1886): Server status:   clock unstable
Mar 10 12:37:16 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 12:37:16 raspberry piaware[817]: mlat-client(1886): Server status:   clock unstable
Mar 10 12:52:16 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 12:52:16 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 155 nearby receivers
Mar 10 13:07:17 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 13:07:17 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 259 nearby receivers
Mar 10 13:22:17 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 13:22:17 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 192 nearby receivers
Mar 10 13:37:18 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 13:37:18 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 243 nearby receivers
Mar 10 13:52:18 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 13:52:18 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 252 nearby receivers
Mar 10 14:07:19 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 14:07:19 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 302 nearby receivers
Mar 10 14:22:19 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 14:22:19 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 243 nearby receivers
Mar 10 14:37:20 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 14:37:20 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 6 nearby receivers
Mar 10 14:52:20 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 14:52:20 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 215 nearby receivers
Mar 10 15:07:20 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 15:07:20 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 276 nearby receivers
Mar 10 15:22:20 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 15:22:20 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 223 nearby receivers
Mar 10 15:37:21 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 15:37:21 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 221 nearby receivers
Mar 10 15:52:21 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 15:52:21 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 247 nearby receivers
Mar 10 16:07:21 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 16:07:21 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 239 nearby receivers
Mar 10 16:22:22 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 16:22:22 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 229 nearby receivers
Mar 10 16:37:22 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 16:37:22 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 205 nearby receivers
Mar 10 16:52:23 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 16:52:23 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 277 nearby receivers
Mar 10 17:07:23 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 17:07:23 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 268 nearby receivers
Mar 10 17:22:24 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 17:22:24 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 211 nearby receivers
Mar 10 17:37:24 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 17:37:24 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 286 nearby receivers
Mar 10 17:52:24 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 17:52:24 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 270 nearby receivers
Mar 10 18:07:25 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 18:07:25 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 255 nearby receivers
Mar 10 18:22:26 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 18:22:26 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 256 nearby receivers
Mar 10 18:37:26 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 18:37:26 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 287 nearby receivers
Mar 10 18:52:27 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 18:52:27 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 261 nearby receivers
Mar 10 19:07:27 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 19:07:27 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 197 nearby receivers
Mar 10 19:22:27 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 19:22:27 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 239 nearby receivers
Mar 10 19:37:27 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 19:37:27 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 228 nearby receivers
Mar 10 19:52:27 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 19:52:27 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 275 nearby receivers
Mar 10 20:07:28 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 20:07:28 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 16 nearby receivers
Mar 10 20:22:28 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 20:22:28 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 212 nearby receivers
Mar 10 20:37:29 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 20:37:29 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 244 nearby receivers
Mar 10 20:52:29 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 20:52:30 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 209 nearby receivers
Mar 10 21:07:30 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 21:07:30 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 302 nearby receivers
Mar 10 21:22:31 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 21:22:31 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 265 nearby receivers
Mar 10 21:37:31 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 21:37:31 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 240 nearby receivers
Mar 10 21:52:32 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 21:52:32 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 265 nearby receivers
Mar 10 22:07:32 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 22:07:32 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 198 nearby receivers
Mar 10 22:22:32 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 22:22:32 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 282 nearby receivers
Mar 10 22:37:33 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 22:37:33 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 86 nearby receivers
Mar 10 22:52:33 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 22:52:33 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 280 nearby receivers
Mar 10 23:07:33 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 23:07:33 raspberry piaware[817]: mlat-client(1886): Server status:   clock unstable
Mar 10 23:22:34 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 23:22:34 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 159 nearby receivers
Mar 10 23:37:34 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 23:37:34 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 222 nearby receivers
Mar 10 23:52:34 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 10 23:52:34 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 144 nearby receivers
Mar 11 00:07:34 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 11 00:07:34 raspberry piaware[817]: mlat-client(1886): Server status:   clock unstable
Mar 11 00:22:34 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 11 00:22:34 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 259 nearby receivers
Mar 11 00:37:34 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 11 00:37:34 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 317 nearby receivers
Mar 11 00:52:35 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 11 00:52:35 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 206 nearby receivers
Mar 11 01:07:35 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 11 01:07:35 raspberry piaware[817]: mlat-client(1886): Server status:   clock unstable
Mar 11 01:22:35 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 11 01:22:35 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 194 nearby receivers
Mar 11 01:37:36 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 11 01:37:36 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 188 nearby receivers
Mar 11 01:52:36 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 11 01:52:36 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 206 nearby receivers
Mar 11 02:07:36 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 11 02:07:36 raspberry piaware[817]: mlat-client(1886): Server status:   clock unstable
Mar 11 02:22:37 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 11 02:22:37 raspberry piaware[817]: mlat-client(1886): Server status:   synchronized with 230 nearby receivers
Mar 11 02:37:37 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 11 02:37:37 raspberry piaware[817]: mlat-client(1886): Server status:   not synchronized with any nearby receivers
Mar 11 02:52:37 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 11 02:52:37 raspberry piaware[817]: mlat-client(1886): Server status:   not synchronized with any nearby receivers
Mar 11 03:07:37 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 11 03:07:38 raspberry piaware[817]: mlat-client(1886): Server status:   not synchronized with any nearby receivers
Mar 11 03:22:38 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 11 03:22:38 raspberry piaware[817]: mlat-client(1886): Server status:   not synchronized with any nearby receivers
Mar 11 03:37:38 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 11 03:37:38 raspberry piaware[817]: mlat-client(1886): Server status:   clock unstable
Mar 11 03:52:39 raspberry piaware[817]: mlat-client(1886): Receiver status: connected
Mar 11 03:52:39 raspberry piaware[817]: mlat-client(1886): Server status:   not synchronized with any nearby receivers

Many thanks to @abcd567!!

1 Like

@suffolk3000

Plesse see this post:

Howto Install Piaware 3.8.1 on 64 bit Raspbian OS / Pi4

 

yes the first install of repo i didnt need it
but i did on second pi4 how strange
now doing it

Are you sure the os on first pi4 was 64-bit? Seems you used 32-bit os. Please give these 2 commamf on first Pi and post output. It will reveal weather you have 32-bit or 64-bit on first Pi4.

uname -a   

cat /etc/os-release   

1 Like

Linux raspberrypi 5.4.51-v8+ #1333 SMP PREEMPT Mon Aug 10 16:58:35 BST 2020 aarch64 GNU/Linux
pi@raspberrypi:/etc/default pi@raspberrypi:/etc/default cat /etc/os-release
PRETTY_NAME=“Debian GNU/Linux 10 (buster)”
NAME=“Debian GNU/Linux”
VERSION_ID=“10”
VERSION=“10 (buster)”
VERSION_CODENAME=buster
ID=debian
HOME_URL=“https://www.debian.org/
SUPPORT_URL=“https://www.debian.org/support
BUG_REPORT_URL=“https://bugs.debian.org/

second pi4
Linux raspberrypi 5.4.51-v8+ #1333 SMP PREEMPT Mon Aug 10 16:58:35 BST 2020 aarch64 GNU/Linux
pi@raspberrypi:/boot pi@raspberrypi:/boot cat /etc/os-release
PRETTY_NAME=“Debian GNU/Linux 10 (buster)”
NAME=“Debian GNU/Linux”
VERSION_ID=“10”
VERSION=“10 (buster)”
VERSION_CODENAME=buster
ID=debian
HOME_URL=“https://www.debian.org/
SUPPORT_URL=“https://www.debian.org/support
BUG_REPORT_URL=“https://bugs.debian.org/

So now i cannot see how first install worked without all the extra stuff you pointed out
but needed on second install pi4
wierd lol

first pi you were correct

pi@raspberrypi:~ uname -a Linux raspberrypi 5.4.51-v7l+ #1333 SMP Mon Aug 10 16:51:40 BST 2020 armv7l GNU/Linux pi@raspberrypi:~
pi@raspberrypi:~ $ cat /etc/os-release
PRETTY_NAME=“Raspbian GNU/Linux 10 (buster)”
NAME=“Raspbian GNU/Linux”
VERSION_ID=“10”
VERSION=“10 (buster)”
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL=“http://www.raspbian.org/
SUPPORT_URL=“http://www.raspbian.org/RaspbianForums
BUG_REPORT_URL=“http://www.raspbian.org/RaspbianBugs

soz

First Pi = armv7l = 32-bit

Second Pi = aarch64 = 64 bit

On first Pi4 you have instslled 32-bit OS, while on 2nd one you indtalled 64-bit version.

1 Like