I’d really appreciate some advice to get my MLAT back again.
I have been running a Debian based flight aware feeder built on a linux netbook for a couple of months. It has worked faultlessly until now.
This morning I used the scripts from here adsbreceiver.net/2016/05/12 … -released/ to upgrade my Dump1090-muta to the latest version by Joe and I supplied all of the required selections.
The install.sh script seemed to go well. The dump1090-mutab maps work and I am feeding data to piaware.
The MLAT feature now doesn’t work.
These are the logs I have been able to get:
returns the following output:
dump1090 is not running
faup1090 is not running
piaware is not running
dump1090-mutabi is listening for connections on port30005
faup1090 is connected to port 30005
piaware is connected to FlightAware
That looks OK to me (but I’m no expert.
When I look at the logs in the Flightaware ADSB stats page, I get the following log messages
Flightaware log extract on mlat:
mlat-client(16555): Input connected to localhost:30005
[2016-09-19 10:37 BST] mlat-client(16555): Input format changed to BEAST, 12MHz clock
[2016-09-19 10:37 BST] got EOF from multilateration client
[2016-09-19 10:37 BST] fa-mlat-client exited with SIG SIGSEGV
[2016-09-19 10:37 BST] ADS-B data program ‘dump1090-muta’ is listening on port 30005, so far so good
[2016-09-19 10:37 BST] Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 55.000 --lon -1.600
[2016-09-19 10:37 BST] Started faup1090 (pid 16561) to connect to dump1090-muta
[2016-09-19 10:37 BST] 133 msgs recv’d from dump1090-muta; 133 msgs sent to FlightAware
[2016-09-19 10:38 BST] Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --results ext_basestation,listen,30106 --udp-transport 220.127.116.11:5461:2075706914
The log goes on to show new attempts to get MLAT going, but they fail it seems because of the EOF from the multilateration client.
This is my adsb flightaware stats page in case expert eyes can spot the problem:
flightaware.com/adsb/stats/user … tats-27881
Many thanks for looking.