![planeplotter modesmixer2 planeplotter modesmixer2](https://64.media.tumblr.com/6958bae31a3a4bcfd0aaa793ce1b0a1e/84aa4144665c2134-ea/s640x960/7534859b45ed9dabb375c3efd44495836526ff9e.jpg)
However, Piaware also has a back-channel on port 30004 that Piaware normally uses to send MLAT positions back to input port 30004 on dump1090 in Beast binary format.
![planeplotter modesmixer2 planeplotter modesmixer2](https://aws1.discourse-cdn.com/business5/uploads/flightaware/original/2X/3/38e05f57d391c2d5e7f8b39e3a646e76b670fb59.png)
If you examine the FlightAware flow disgram, you will see that normal sharing data is received from modesmixer2 on port 30005, the same port used by PlanePlotter and ppup1090 for autonomous uploading to PlanePlotter servers. 01:52:11 5746 msgs recv'd from modesmixer2 (1872 in last 5m) 5746 msgs sent to FlightAware 01:51:46 mlat(2313): Server: 2.7 kB/s from server 0.0kB/s TCP to server 10.0kB/s UDP to server 01:47:11 3874 msgs recv'd from modesmixer2 (1902 in last 5m) 3874 msgs sent to FlightAware 01:42:11 1972 msgs recv'd from modesmixer2 (1831 in last 5m) 1972 msgs sent to FlightAware 01:37:59 server is sending alive messages we will expect them 01:37:11 141 msgs recv'd from modesmixer2 141 msgs sent to FlightAware 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.
#Planeplotter modesmixer2 serial#
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.