That’s cool!! The real test though is whether it STAYS in sync after about 15-30 minutes. Remember that initially (after a reboot), the server “trusts” a new feed. But after awhile, if it sees a lot of “dropped” USB data, it will be marked as having an “unstable clock”. If your technique works, I will try to duplicate it on my setup.
Will check again after 20 minutes
1 Like
Can you still run piaware on Linux (or Windows for that matter) with this setup, so that you can see “my skyview”? If so, how?
Does this involve a web server, or is it talking directly to dump1090-fa (which is talking over http)?
Does your setup create a new feed ID (that you had to “claim”), or are you re-using an existing feed ID that is already associated with you?
Yes, it does require a web server.
The installation of web server lighttpd is a dependency for dump1090-fa, and if you check Post #12, item 1.1, you will find that I have installed it as first step in building dump1090-fa.
1 Like
So is this setup a complete Windows-based FA feeder station solution? If not, what functionality is missing?
Are you still in sync?
He is just doing the decoding in Windows.
Then sending the beast data over to a dump1090-fa running in the linux VM.
Each Mode-S/ADS-B packet is up to 112 bits or so and in hexadecimal looks something like this:
02e197b006ca50
a0001498be800030a40000f996bd
(Short and long message type)
beast is a binary protocol to transfer these messages via network.
A receiver clock timestamp (from the 2.4 MHz sample frequency in the receiver) is also transmitted with each message.
1 Like
Seems it is complete, but different in mode of operation that receiving & decoding is done by windows dump1090 (win.1.10.3010.14), while the interface with SkyView map and Piaware data feeder, including mlat feed-back stays with VMware’s dump1090-fa
1 Like
Thanks. That’s a great idea. I will try to duplicate.
Brilliant!! I will try to duplicate. It may take me awhile to get to it though.
Found this interesting. Occasionally my faulty feed was getting sync’ed, but only occasionally. Even the Losers Get Lucky Sometimes (Tom Petty)
journalctl -u piaware | grep 'Receiver status\|Server status'
Mar 05 18:57:26 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 05 18:57:26 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 05 19:12:26 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 05 19:12:26 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 05 19:27:26 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 05 19:27:26 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 05 19:42:27 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 05 19:42:27 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 05 19:57:28 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 05 19:57:28 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 05 20:12:28 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 05 20:12:28 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 05 20:27:28 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 05 20:27:28 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 05 20:42:28 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 05 20:42:28 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 05 20:57:29 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 05 20:57:29 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 05 21:12:29 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 05 21:12:29 ubuntu piaware[756]: mlat-client(812): Server status: synchronized with 240 nearby receivers
Mar 05 21:27:30 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 05 21:27:30 ubuntu piaware[756]: mlat-client(812): Server status: synchronized with 217 nearby receivers
Mar 05 21:42:30 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 05 21:42:30 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 05 21:57:31 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 05 21:57:31 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 05 22:12:32 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 05 22:12:32 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 05 22:27:33 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 05 22:27:33 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 05 22:42:34 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 05 22:42:34 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 05 22:57:34 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 05 22:57:34 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 05 23:12:35 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 05 23:12:35 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 05 23:27:35 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 05 23:27:35 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 05 23:42:36 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 05 23:42:36 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 05 23:57:36 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 05 23:57:36 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 00:12:37 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 00:12:37 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 00:27:37 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 00:27:37 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 00:42:37 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 00:42:37 ubuntu piaware[756]: mlat-client(812): Server status: synchronized with 109 nearby receivers
Mar 06 00:57:38 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 00:57:38 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 01:12:38 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 01:12:38 ubuntu piaware[756]: mlat-client(812): Server status: synchronized with 111 nearby receivers
Mar 06 01:27:39 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 01:27:39 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 01:42:40 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 01:42:40 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 01:57:40 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 01:57:40 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 02:12:41 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 02:12:41 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 02:27:41 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 02:27:41 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 02:42:41 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 02:42:41 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 02:57:41 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 02:57:41 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 03:12:41 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 03:12:41 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 03:27:42 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 03:27:42 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 03:42:42 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 03:42:42 ubuntu piaware[756]: mlat-client(812): Server status: synchronized with 137 nearby receivers
Mar 06 03:57:42 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 03:57:42 ubuntu piaware[756]: mlat-client(812): Server status: not synchronized with any nearby receivers
Mar 06 04:12:43 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 04:12:43 ubuntu piaware[756]: mlat-client(812): Server status: not synchronized with any nearby receivers
Mar 06 04:27:43 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 04:27:43 ubuntu piaware[756]: mlat-client(812): Server status: not synchronized with any nearby receivers
Mar 06 04:42:44 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 04:42:44 ubuntu piaware[756]: mlat-client(812): Server status: not synchronized with any nearby receivers
Mar 06 04:57:44 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 04:57:44 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 05:12:44 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 05:12:44 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 05:27:45 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 05:27:45 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 05:42:46 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 05:42:46 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 05:57:46 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 05:57:46 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 06:12:47 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 06:12:47 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 06:27:48 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 06:27:48 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 06:42:48 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 06:42:48 ubuntu piaware[756]: mlat-client(812): Server status: synchronized with 238 nearby receivers
Mar 06 06:57:48 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 06:57:48 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 07:12:48 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 07:12:48 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 07:27:49 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 07:27:49 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 07:42:49 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 07:42:49 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 07:57:49 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 07:57:49 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 08:12:50 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 08:12:50 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 08:27:51 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 08:27:51 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 08:42:52 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 08:42:52 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 08:57:53 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 08:57:53 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 09:12:53 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 09:12:53 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 09:27:53 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 09:27:53 ubuntu piaware[756]: mlat-client(812): Server status: synchronized with 284 nearby receivers
Mar 06 09:42:54 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 09:42:54 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 09:57:54 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 09:57:54 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 10:12:55 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 10:12:55 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 10:27:55 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 10:27:55 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 10:42:56 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 10:42:56 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 10:57:57 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 10:57:57 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 11:12:57 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 11:12:57 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 11:27:57 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 11:27:57 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 11:42:57 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 11:42:57 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 11:57:58 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 11:57:58 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 12:12:58 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 12:12:58 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 12:27:59 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 12:27:59 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 12:42:59 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 12:42:59 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
Mar 06 12:57:59 ubuntu piaware[756]: mlat-client(812): Receiver status: connected
Mar 06 12:57:59 ubuntu piaware[756]: mlat-client(812): Server status: clock unstable
is there any relation between this and the actual PC clock ?
Planeplotter insists before joining for mlat (GS/MU) to install the NTP
server in Windows - I guess for accurate timing.
Would it make a difference here ?
NTP only gives a rough indication which ADS-B messages to match up to create a receiver timeline by correlation.
For actual MLAT NTP is not nearly precise enough.
Bummer!! It was a great idea, though. I wonder what the heck the problem is. Something to do with the USB data getting “dropped” (could be due to any number of things).
thanks @wiedehopf.
more silly questions please - I try to understand the sequence / mechanism:
even with stratum1 - gps source to NTP ? (apparently incorporated in flightfeeders)
how is the dongle ‘time aware’ ?
how / where from the message gets timestamped ?
is the PC / Rpi clock not taken into account ?
If I’m understanding this correctly, actual time synchronization is not playing a role here.