Archived - Beta test MLAT software for Raspberry Pi

[bhaal]

Small comparison of accuracy: FA PiAware MLAT (viewed from VRS) Vs. FR24 fr24feed+F-feeders MLAT

famlat1.jpgfr24mlat1.png


Also, I am seeing that fr24feed is disconnecting from the server fairly regularly, re fr24feed.log:

2016-03-08 20:18:05 | [feed][n]disconnected
2016-03-08 20:18:05 | [feed][n]waiting 6 seconds
2016-03-08 20:18:11 | [feed][n]YBBN50@83.140.21.66:8099/UDP
2016-03-08 20:18:11 | [feed][n]connecting
2016-03-08 20:18:20 | [mlat][i]Pinging the server
2016-03-08 20:18:33 | [feed][n]connected via TCP (fd 11)
2016-03-08 20:18:33 | [feed][n]working

2016-03-08 20:20:19 | [feed][n]disconnected
2016-03-08 20:20:19 | [feed][n]waiting 7 seconds
2016-03-08 20:20:20 | [time][i]Time synchronized correctly, offset -0.0017 seconds, drift 0.0000 seconds/minute
2016-03-08 20:20:22 | [mlat][i]Pinging the server
2016-03-08 20:20:22 | [mlat][i]Stats 0/0
2016-03-08 20:20:26 | [feed][n]YBBN50@83.140.21.66:8099/UDP
2016-03-08 20:20:26 | [feed][n]connecting
2016-03-08 20:20:42 | [mlat][i]Pinging the server
2016-03-08 20:20:42 | [mlat][i]Stats 0/0
2016-03-08 20:20:47 | [feed][n]connected via TCP (fd 11)
2016-03-08 20:20:47 | [feed][n]working

[Olov]

Is a radarcape considered to be a GPS equipped FR24 receiver or does it have to be a receiver issued by FR24?

Thanks!

Right now, Radarcapes are not used in volounteer MLAT calculations, but very very soon you (as a Radarcape owner) will be able to get a software update for the Radarcape that supports time sync.

Radarcapes are however already used in high-precision MLAT calculations.

[Olov]

Small comparison of accuracy: FA PiAware MLAT (viewed from VRS) Vs. FR24 fr24feed+F-feeders MLAT

[ATTACH=CONFIG]7137[/ATTACH][ATTACH=CONFIG]7138[/ATTACH]


Also, I am seeing that fr24feed is disconnecting from the server fairly regularly, re fr24feed.log:

2016-03-08 20:18:05 | [feed][n]disconnected
2016-03-08 20:18:05 | [feed][n]waiting 6 seconds
2016-03-08 20:18:11 | [feed][n]YBBN50@83.140.21.66:8099/UDP
2016-03-08 20:18:11 | [feed][n]connecting
2016-03-08 20:18:20 | [mlat][i]Pinging the server
2016-03-08 20:18:33 | [feed][n]connected via TCP (fd 11)
2016-03-08 20:18:33 | [feed][n]working

2016-03-08 20:20:19 | [feed][n]disconnected
2016-03-08 20:20:19 | [feed][n]waiting 7 seconds
2016-03-08 20:20:20 | [time][i]Time synchronized correctly, offset -0.0017 seconds, drift 0.0000 seconds/minute
2016-03-08 20:20:22 | [mlat][i]Pinging the server
2016-03-08 20:20:22 | [mlat][i]Stats 0/0
2016-03-08 20:20:26 | [feed][n]YBBN50@83.140.21.66:8099/UDP
2016-03-08 20:20:26 | [feed][n]connecting
2016-03-08 20:20:42 | [mlat][i]Pinging the server
2016-03-08 20:20:42 | [mlat][i]Stats 0/0
2016-03-08 20:20:47 | [feed][n]connected via TCP (fd 11)
2016-03-08 20:20:47 | [feed][n]working

Thanks for the comparison! We will look at this carefully, might take a few days to a week before I can comment it further.

[Olov]

Has this been installed/tested on the RPi 3b yet by any chance? Just about to update my Pi and wondering which one to buy?

RPi 3 working fine!

[Olov]

So, my question is: can FR24 utilize a gps enabled pi and use that as a trusted MLAT source?
They do have them here at low cost for those with a little hardware talent:

https://www.adafruit.com/products/746

For more money there is probably plug and play.

Not really.. for a GPS receiver to make things better it has to be connected to the receiver itself. Could possibly work if you could find a DVBT dongle that supports external clock reset!

[Multinet]

unable to connect to FR24 from feeder

Hello

All was working like a charm since few days
But since today 5.47pm my feeder could not connect FR24

I've restarted my Pi but same

here is a log

2016-03-08 18:57:48 | [main][i]FR24 Feeder/Decoder
2016-03-08 18:57:48 | [main][i]Version: 1.0.18-5/generic
2016-03-08 18:57:48 | [main][i]Built on Mar 4 2016 15:21:10 (HEAD-d11ca48.git/Linux/armv7l)
2016-03-08 18:57:48 | [main][i]Copyright 2012-2016 Flightradar24 AB
2016-03-08 18:57:48 | [main][i]****** no link (by me first post!)
2016-03-08 18:57:58 | [main][i]DNS mode: LIBC
2016-03-08 18:57:58 | [main][i]Automatic updates are DISABLED
2016-03-08 18:57:58 | [httpd][i]Server started, listening on 0.0.0.0:8754
2016-03-08 18:57:58 | [main][i]Reader thread started
2016-03-08 18:57:58 | [main][i]Socket server started
2016-03-08 18:57:58 | [bs][i]Initializing server
2016-03-08 18:57:58 | [bs][i]Starting server on 0.0.0.0:30003
2016-03-08 18:57:58 | [reader][i]Initializing reader
2016-03-08 18:57:58 | [reader][i]Connecting to Beast receiver via (tcp://127.0.0.1:30005)
2016-03-08 18:57:58 | [mlat][i]Waiting for MLAT configuration
2016-03-08 18:57:58 | [master][i]Starting processing thread
2016-03-08 18:57:58 | [main][i]MLAT data feed started
2016-03-08 18:57:58 | [bs][e]Could not bind socket to *:30003, errno=98
2016-03-08 18:57:58 | [reader][i]Connected to the receiver, configuring
2016-03-08 18:57:58 | [reader][i]Configured, processing messages
2016-03-08 18:57:59 | [time][i]Synchronizing time via NTP
2016-03-08 18:58:00 | [reader][w]Setting new UTC offset: 0!
2016-03-08 18:59:29 | [time][i]Time synchronized correctly, offset +66.0135 seconds
2016-03-08 18:59:29 | [main][i]Feed Network client started
2016-03-08 18:59:29 | [main][i]RAW data server started
2016-03-08 18:59:29 | [feed][i]Downloading configuration
2016-03-08 18:59:29 | [raw][i]Initializing server
2016-03-08 18:59:29 | [raw][i]Starting server on 0.0.0.0:30334
2016-03-08 18:59:29 | [feed][c]Interval: 5s
2016-03-08 18:59:29 | [feed][c]Latitude: **.***** (anonymous by author)
2016-03-08 18:59:29 | [feed][c]Longitude: **.***** (anonymous by author)
2016-03-08 18:59:29 | [feed][c]GND: YES
2016-03-08 18:59:29 | [feed][c]NonADSB: YES
2016-03-08 18:59:29 | [feed][c]Timestamps: optional
2016-03-08 18:59:29 | [feed][c]Max range AIR: 350.0nm
2016-03-08 18:59:29 | [feed][c]Max range GND: 100.0nm
2016-03-08 18:59:29 | [feed][i]defined 1 server
2016-03-08 18:59:29 | [stats][i]Stats thread started
2016-03-08 18:59:29 | [feed][n]LFBD22@83.140.21.66:8099/UDP
2016-03-08 18:59:29 | [feed][n]connecting
2016-03-08 18:59:30 | [mlat][i]MLAT configuration received, service ENABLED
2016-03-08 18:59:30 | [mlat][i]Starting MLAT with preconfigured position: **.***** (anonymous by author)
2016-03-08 18:59:30 | [mlat][i]MLAT bandwidth reduction active, level 1
2016-03-08 18:59:30 | [mlat][i]Configuring UDP connection udp://mlat-1.fr24.com:19788
2016-03-08 18:59:30 | [mlat][i]Registering MLAT station
2016-03-08 18:59:30 | [mlat][i]Registering MLAT station: SUCCESS
2016-03-08 18:59:32 | [mlat][i]Pinging the server
2016-03-08 18:59:32 | [mlat][i]Stats 0/0
2016-03-08 18:59:50 | [feed][e]Could not connect!
2016-03-08 18:59:50 | [feed][n]Error: Could not connect! (fd -1)
2016-03-08 18:59:50 | [feed][n]waiting 10 seconds
2016-03-08 18:59:52 | [mlat][i]Pinging the server
2016-03-08 18:59:52 | [mlat][i]Stats 0/0
2016-03-08 19:00:00 | [feed][n]LFBD22@83.140.21.66:8099/UDP
2016-03-08 19:00:00 | [feed][n]connecting
2016-03-08 19:00:12 | [mlat][i]Pinging the server
2016-03-08 19:00:12 | [mlat][i]Stats 0/0
2016-03-08 19:00:20 | [feed][e]Could not connect!
2016-03-08 19:00:20 | [feed][n]Error: Could not connect! (fd -1)
2016-03-08 19:00:20 | [feed][n]waiting 19 seconds
2016-03-08 19:00:32 | [mlat][i]Pinging the server
2016-03-08 19:00:32 | [mlat][i]Stats 0/0
2016-03-08 19:00:39 | [feed][n]LFBD22@83.140.21.66:8099/UDP
2016-03-08 19:00:39 | [feed][n]connecting
2016-03-08 19:00:52 | [mlat][i]Pinging the server
2016-03-08 19:00:52 | [mlat][i]Stats 0/0
2016-03-08 19:00:59 | [feed][e]Could not connect!
2016-03-08 19:00:59 | [feed][n]Error: Could not connect! (fd -1)
2016-03-08 19:00:59 | [feed][n]waiting 23 seconds
2016-03-08 19:01:12 | [mlat][i]Pinging the server
2016-03-08 19:01:12 | [mlat][i]Stats 0/0
2016-03-08 19:01:22 | [feed][n]LFBD22@83.140.21.66:8099/UDP
2016-03-08 19:01:24 | [feed][n]connecting
2016-03-08 19:01:32 | [mlat][i]Pinging the server
2016-03-08 19:01:32 | [mlat][i]Stats 0/0
2016-03-08 19:01:42 | [feed][e]Could not connect!
2016-03-08 19:01:42 | [feed][n]Error: Could not connect! (fd -1)
2016-03-08 19:01:42 | [feed][n]waiting 26 seconds
2016-03-08 19:01:51 | [mlat][i]Pinging the server
2016-03-08 19:01:51 | [mlat][i]Stats 0/0
2016-03-08 19:02:08 | [feed][n]LFBD22@83.140.21.66:8099/UDP
2016-03-08 19:02:08 | [feed][n]connecting
2016-03-08 19:02:11 | [mlat][i]Pinging the server
2016-03-08 19:02:11 | [mlat][i]Stats 0/0
2016-03-08 19:02:28 | [feed][e]Could not connect!
2016-03-08 19:02:28 | [feed][n]Error: Could not connect! (fd -1)
2016-03-08 19:02:28 | [feed][n]waiting 30 seconds
2016-03-08 19:02:50 | [mlat][i]Pinging the server
2016-03-08 19:02:50 | [mlat][w]Could not ping MLAT server, result=-1000, number of errors=1
2016-03-08 19:02:58 | [feed][i]Downloading configuration
2016-03-08 19:02:59 | [feed][c]Interval: 5s
2016-03-08 19:02:59 | [feed][c]Latitude: **.***** (anonymous by author)
2016-03-08 19:02:59 | [feed][c]Longitude: **.***** (anonymous by author)
2016-03-08 19:02:59 | [feed][c]GND: YES
2016-03-08 19:02:59 | [feed][c]NonADSB: YES
2016-03-08 19:02:59 | [feed][c]Timestamps: optional
2016-03-08 19:02:59 | [feed][c]Max range AIR: 350.0nm
2016-03-08 19:02:59 | [feed][c]Max range GND: 100.0nm
2016-03-08 19:02:59 | [feed][i]defined 1 server
2016-03-08 19:02:59 | [feed][n]LFBD22@83.140.21.66:8099/UDP
2016-03-08 19:02:59 | [feed][n]connecting
2016-03-08 19:03:14 | [mlat][i]Pinging the server
2016-03-08 19:03:14 | [mlat][w]Could not ping MLAT server, result=-1000, number of errors=2
2016-03-08 19:03:14 | [mlat][i]Terminating connection
2016-03-08 19:03:15 | [mlat][i]Configuring UDP connection udp://mlat-1.fr24.com:19788
2016-03-08 19:03:15 | [mlat][i]Registering MLAT station
2016-03-08 19:03:16 | [mlat][i]Registering MLAT station: SUCCESS
2016-03-08 19:03:19 | [feed][e]Could not connect!
2016-03-08 19:03:19 | [feed][n]Error: Could not connect! (fd -1)
2016-03-08 19:03:19 | [feed][n]waiting 11 seconds

Is there a problem on my side ? I don't touch anything !
Or fr24 side ?

Thanks for your answer
Multinet

[bhaal]

It's dead Jim:

2016-03-09 10:08:57 | [feed][n]disconnected
2016-03-09 10:08:57 | [feed][n]waiting 5 seconds
2016-03-09 10:09:02 | [feed][n]YBBN50@83.140.21.66:8099/UDP
2016-03-09 10:09:02 | [feed][n]connecting
2016-03-09 10:09:08 | [mlat][i]Pinging the server
2016-03-09 10:09:08 | [mlat][i]Stats 0/0
2016-03-09 10:09:28 | [mlat][i]Pinging the server
2016-03-09 10:09:28 | [mlat][i]Stats 0/0
2016-03-09 10:09:48 | [mlat][i]Pinging the server
2016-03-09 10:09:48 | [mlat][i]Stats 0/0
2016-03-09 10:09:49 | [feed][e]Could not connect!
2016-03-09 10:09:49 | [feed][n]Error: Could not connect! (fd -1)
2016-03-09 10:09:49 | [feed][n]waiting 8 seconds
2016-03-09 10:09:57 | [feed][n]YBBN50@83.140.21.66:8099/UDP
2016-03-09 10:09:57 | [feed][n]connecting
2016-03-09 10:10:08 | [mlat][i]Pinging the server
2016-03-09 10:10:08 | [mlat][i]Stats 0/0
2016-03-09 10:10:28 | [mlat][i]Pinging the server
2016-03-09 10:10:28 | [mlat][i]Stats 0/0
2016-03-09 10:10:39 | [feed][e]Could not connect!
2016-03-09 10:10:39 | [feed][n]Error: Could not connect! (fd -1)
2016-03-09 10:10:39 | [feed][n]waiting 5 seconds
2016-03-09 10:10:44 | [feed][n]YBBN50@83.140.21.66:8099/UDP
2016-03-09 10:10:44 | [feed][n]connecting
2016-03-09 10:10:48 | [mlat][i]Pinging the server
2016-03-09 10:10:48 | [mlat][i]Stats 0/0
2016-03-09 10:11:08 | [mlat][i]Pinging the server
2016-03-09 10:11:08 | [mlat][i]Stats 0/0
2016-03-09 10:11:25 | [feed][e]Could not connect!
2016-03-09 10:11:25 | [feed][n]Error: Could not connect! (fd -1)
2016-03-09 10:11:25 | [feed][n]waiting 8 seconds
2016-03-09 10:11:28 | [mlat][i]Pinging the server
2016-03-09 10:11:28 | [mlat][i]Stats 0/0
2016-03-09 10:11:33 | [feed][n]YBBN50@83.140.21.66:8099/UDP
2016-03-09 10:11:33 | [feed][n]connecting
2016-03-09 10:11:48 | [mlat][i]Pinging the server
2016-03-09 10:11:48 | [mlat][i]Stats 0/0
2016-03-09 10:12:08 | [mlat][i]Pinging the server
2016-03-09 10:12:08 | [mlat][i]Stats 0/0
2016-03-09 10:12:14 | [feed][e]Could not connect!
2016-03-09 10:12:14 | [feed][n]Error: Could not connect! (fd -1)
2016-03-09 10:12:14 | [feed][n]waiting 7 seconds
2016-03-09 10:12:21 | [feed][n]YBBN50@83.140.21.66:8099/UDP
2016-03-09 10:12:21 | [feed][n]connecting
2016-03-09 10:12:28 | [mlat][i]Pinging the server
2016-03-09 10:12:28 | [mlat][i]Stats 0/0
2016-03-09 10:12:46 | [stats][i]sent 1825 bytes
2016-03-09 10:12:48 | [mlat][i]Pinging the server
2016-03-09 10:12:48 | [mlat][i]Stats 0/0
2016-03-09 10:13:02 | [feed][e]Could not connect!
2016-03-09 10:13:02 | [feed][n]Error: Could not connect! (fd -1)
2016-03-09 10:13:02 | [feed][n]waiting 7 seconds

[Oblivian]

Looks like the tcp fallbacks not so flash

Sent from my XT1092 using Tapatalk

[bhaal]

Looks like the tcp fallbacks not so flash

It eventually did reconnect, but is frequently disconnecting and reconnecting, always as TCP, not UDP.. Every few mins...

[KK6LDW]

Same on my end:

2016-03-08 18:06:02 | [feed][n]connecting
2016-03-08 18:06:16 | [mlat][i]Pinging the server
2016-03-08 18:06:16 | [mlat][i]Stats 0/0
2016-03-08 18:06:36 | [mlat][i]Pinging the server
2016-03-08 18:06:36 | [mlat][i]Stats 0/0
2016-03-08 18:06:43 | [feed][e]Could not connect!
2016-03-08 18:06:43 | [feed][n]Error: Could not connect! (fd -1)
2016-03-08 18:06:43 | [feed][n]waiting 9 seconds

[Oblivian]

When major outtages server related like this occur (and are posted in a few threads like they are) ya'll should really be raising it with the HD

the right team members do not look at all new threads regularly.. and wont notice for a few days

[bhaal]

But Olov has seen me posting about it... He replied to my comment with the side by side comparison which also had the connection failures in the log I think...

[41south]

Right now, Radarcapes are not used in volounteer MLAT calculations, but very very soon you (as a Radarcape owner) will be able to get a software update for the Radarcape that supports time sync.

Radarcapes are however already used in high-precision MLAT calculations.

Does this mean that Radarcape data is considered for MLAT 3/4?

[piopawlu]

Does this mean that Radarcape data is considered for MLAT 3/4?

Yes,, it has been used for over a year now. However, Radarcape owners need to enable it manually in the Radarcape configuration. It's an opt-in choice as MLAT takes extra bandwidth.

[RIN67630]

Hi elljay,
the latency over USB is not the main problem. GPS mouses do have on the top of USB an additional serial protocol, frequently with a dreadly slow 9600 Baud serial speed. That is fine for navigation, but is inadequate for time critical operations. The latency of this method is probably also in the range of 20ms or more.
If you have identical hardware and identical GPS mice using the same software and the same serial speed the errors might compensate. But if one of the feeder has a 9600Baud mouse and the other one a 115000Baud one, then you will be better off with NTP.

> Not sure why ADS-B doesn't include the time in it's transmissions...
We do need to compare the arrival times between stations, not the send times.