dump1090 no MLAT displayed


#1

Hello,
I’m new to FA and piaware; I’ve just setup 3.1.0 where I had dump1090 running. The log is reporting [Errno 111] Connection refused
Looking for help to get MLAT displayed…
Thanks,
YM

Jan 17 14:02:57 raspberrypi piaware[3235]: piaware version 3.1.0 is running, process ID 3235
Jan 17 14:02:57 raspberrypi piaware[3235]: your system info is: Linux raspberrypi 4.4.38-v7+ #938 SMP Thu Dec 15 15:22:21 GMT 2016 armv7l GNU/Linux
Jan 17 14:02:58 raspberrypi piaware[3235]: Connecting to FlightAware adept server at piaware.flightaware.com/1200
Jan 17 14:02:59 raspberrypi piaware[3235]: Connection with adept server at piaware.flightaware.com/1200 established
Jan 17 14:02:59 raspberrypi piaware[3235]: TLS handshake with adept server at piaware.flightaware.com/1200 completed
Jan 17 14:02:59 raspberrypi piaware[3235]: FlightAware server certificate validated
Jan 17 14:02:59 raspberrypi piaware[3235]: encrypted session established with FlightAware
Jan 17 14:03:00 raspberrypi piaware[3235]: ADS-B data program ‘dump1090’ is listening on port 30005, so far so good
Jan 17 14:03:00 raspberrypi piaware[3235]: Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 49.xxx --lon 2.xxx
Jan 17 14:03:00 raspberrypi piaware[3235]: Started faup1090 (pid 3296) to connect to dump1090
Jan 17 14:03:00 raspberrypi piaware[3235]: logged in to FlightAware as user xxxxxxx
Jan 17 14:03:00 raspberrypi piaware[3235]: piaware received a message from dump1090!
Jan 17 14:03:01 raspberrypi piaware[3235]: multilateration data requested
Jan 17 14:03:01 raspberrypi piaware[3235]: Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --input-type dump1090 --results beast,connect,localhost:30104 --results beast,listen,30105 --results ext_basestation,listen,30106 --udp-transport 70.42.6.224:9355:3965543721
Jan 17 14:03:01 raspberrypi piaware[3235]: piaware has successfully sent several msgs to FlightAware!
Jan 17 14:03:01 raspberrypi piaware[3235]: mlat-client(3307): fa-mlat-client 0.2.6 starting up
Jan 17 14:03:01 raspberrypi piaware[3235]: mlat-client(3307): Using UDP transport to 70.42.6.224 port 9355
Jan 17 14:03:01 raspberrypi piaware[3235]: mlat-client(3307): Listening for Beast-format results connection on port 30105
Jan 17 14:03:01 raspberrypi piaware[3235]: mlat-client(3307): Listening for Extended Basestation-format results connection on port 30106
Jan 17 14:03:01 raspberrypi piaware[3235]: mlat-client(3307): Connection to localhost:30005 lost: [Errno 111] Connection refused
Jan 17 14:03:01 raspberrypi piaware[3235]: mlat-client(3307): Reconnecting in 0.5 seconds
Jan 17 14:03:02 raspberrypi piaware[3235]: mlat-client(3307): Beast-format results connection with ::1:30104: [Errno 111] Connection refused
Jan 17 14:03:02 raspberrypi piaware[3235]: mlat-client(3307): Input connected to localhost:30005
Jan 17 14:03:02 raspberrypi piaware[3235]: mlat-client(3307): Input format changed to BEAST, 12MHz clock
Jan 17 14:03:31 raspberrypi piaware[3235]: 90 msgs recv’d from dump1090; 90 msgs sent to FlightAware
Jan 17 14:03:32 raspberrypi piaware[3235]: mlat-client(3307): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
Jan 17 14:04:03 raspberrypi piaware[3235]: mlat-client(3307): Beast-format results connection with ::1:30104: [Errno 111] Connection refused
Jan 17 14:04:33 raspberrypi piaware[3235]: mlat-client(3307): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
Jan 17 14:05:03 raspberrypi piaware[3235]: mlat-client(3307): Beast-format results connection with ::1:30104: [Errno 111] Connection refused
Jan 17 14:05:34 raspberrypi piaware[3235]: mlat-client(3307): Beast-format results connection with 127.0.0.1:30104: [Errno 111] Connection refused
Jan 17 14:06:04 raspberrypi piaware[3235]: mlat-client(3307): Beast-format results connection with ::1:30104: [Errno 111] Connection refused


#2

You need a version of dump1090 that is mlat-aware and listening on port 30104.
dump1090-fa and dump1090-mutability are suitable; the original antirez dump1090 and malcolmrobb’s fork are not suitable.

Alternatively you can feed mlat results from port 30105 to a separate system e.g. VRS for display.


#3

Thanks!

Uninstalled dump1090 and replaced it by dump1090-mutability. Changed beast input port 30004 to 30104.

Works now.