01:36:45 piaware has successfully sent several msgs to FlightAware! 01:36:45 piaware received a message from modesmixer2! 01:36:41 multilateration data requested, enabling mlat client 01:36:41 multilateration support enabled (use piaware-config to disable) 01:36:41 logged in to FlightAware as user donf99 01:36:41 Started faup1090 (pid 2311) to connect to modesmixer2 01:36:41 ADS-B data program 'modesmixer2' is listening on port 30005, so far so good Here are the relevant piaware log messages showing things are starting up just fine with modesmixer2: However, that issue seems to have been resolved with the latest MLAT-capable version of Piaware. Piaware used to have problems receiving data for normal position reporting on port 30005 from modesmixer2, even though that was the same port used by the expected dump1090 decoder application. I also start the web server and provide my location for modesmixer web page plotting of my coverage and stats and for more efficient position decoding. This simply receives serial data (already decoded) in Beast binary format on USB serial port ttyUSB0 and translates it to an output on port 30005. Modesmixer2 -inSerial /dev/ttyUSB0:3000000:hardware -outServer beast:30005 -web 8080 -location yy.yyyyyy:-xx.xxxxxx
My current modesmixer2 invocation is with: The basic flow of the new Piaware MLAT system is here:
That setup is working very well, feeding data to the PlanePlotter servers via modesmixer2 and ppup1090 on port 30005. Piaware has recently added the capability of doing MLAT processing, I decided to see if I could get this working with my modesmixer2 setup that is receiving serial over USB data from a Mode-S Beast receiver rather than than a dongle using dump1090.
0 kommentar(er)
