radarspotting.com/forum/index.ph … 978.0.html
Seems they created a link to FlightAware as well.
Anybody tried this?
Ton.
modesdeco2/modesmixer2 will emit FATSV, I believe, but you still need piaware to forward that to FlightAware, so the question doesn’t really make sense 
If i understand well it does a lot more than just forwarding data. I think it has become a full PiAware replacement with many more options than PiAware without losing the FlightAware feeding possibility.
Can you point me to something in the release thread that says that, because I don’t see it?
edit: Only thing I can see confirms what I thought - modesmixer2 will generate FATSV, but you still need piaware to do the forwarding:
radarspotting.com/forum/index.ph … l#msg21919
implemented the first stage of data processing for send data to FlightAware. Added TCP server, which outputs data into the same filtered format as FlightAware fork of dump1090_mr produces.This is achieved by adding to the command line the option:
–outServer fatsv:Port
The support program piaware, which establishes an encrypted session to FlightAware and forwards data is still required.
Ok, Overlooked that one. you saved me a lot of work. 
Thanks,
Ton.
I’m torn between dump1090-mutability’s lighttpd web stats and the new modesdeco2/modesmixer2 web stats. Anybody out there strongly prefer one over the other?
I strongly prefer dump1090-mutability because I wrote it … and I can edit the layout as needed.
You can have both though - should be no problem to feed modesmixer2 from dump1090, or vice versa.
From what i have seen on the web, i haven’t installed it (never touch what’s working), the modesdeco/modesmixer looks better. So if you can change the output the way you want to, make it look better.
But now we are talking nice-to-haves, no needs.
Oh, sure, I’m no web designer, I’d agree that modesmixer2 looks nicer – but my point was more that I (and everyone else) have the option of changing dump1090’s layout.
You can’t change modesmixer2’s layout, there is no source code available and the webpages are stashed inside the binary.
So do the right thing and make us happy! 
So I actually have a bit of a comparison to show you guys. Lets hope it all works, can’t guarantee these links will be live forever but for the time being:
Virtual Radar: pharmdrew.com
ACARS (acarsdeco2): pharmdrew.com/acars.php
modesmixer2: pharmdrew.com/modesmixer.php
dump1090-mutability: pharmdrew.com/d1090m.php
I just did a fresh boot on these machines so give them some time to populate
Virtual Radar: pharmdrew.com
Really well done. Probably exactly what i would need.
ACARS (acarsdeco2): pharmdrew.com/acars.php
I’m not using ACARS (yet). Also misses the eye-candy the first option contains.
modesmixer2: pharmdrew.com/modesmixer.php
Love the technical screens. Gives me a better idea what i am receiving. Yes, i love the different views on the information and the links between the screens.
dump1090-mutability: pharmdrew.com/d1090m.php
This is what we have now, right? Maybe a bit later version from what i am running now.
If i needed to choose it would be between 1 and 3 where 3 would probably win.
Hope this helps,
Ton.
I tend to agree with you Tom. I was posting that more for you guys to get a sample of what you are choosing from but I still appreciate it. ACARS doesn’t have the nice pretty looking map features but I gotta tell you some of those messages are fun to read sometimes (99% of the non-automated ones have some degree of joking it seems).
The developer of modesmixer2/modesdeco2/acarsdeco2 deserves a nice website as opposed to the use of the following thread for his releases: radarspotting.com/forum/index.ph … 8.135.html
Tried running ModesDeco2 with an AirSpy mini/RTL on boot-up but it fails to start (dump1090 isn’t running).
Can anyone tell me how to fix it in rc.local or help me write an init.d script to run it at startup.
Cheers.
Here’s my rc.local output.
#
# This script is executed at the end of each multiuser runlevel.
# Make sure that the script will "exit 0" on success or any other
# value on error.
#
# In order to enable or disable this script just change the execution
# bits.
#
# By default this script does nothing.
# Print the IP address
_IP=$(hostname -I) || true
if "$_IP" ]; then
printf "My IP address is %s
" "$_IP"
fi
/home/pi/adsb-receiver/build/adsbexchange/adsbexchange-maint.sh &
/home/pi/adsb-receiver/build/dump978/dump978-maint.sh &
/home/pi/adsb-receiver/build/portal/logging/flights-maint.sh &
/home/pi/adsb-exchange/adsbexchange-maint.sh &
/home/pi/modes/modesdeco2 --rbs --web 9090 --beast 30005 --localtime --metric &
exit 0
I have tried ModesDeco2 in Feb 2015, but quickly reverted to dump1090-mutability, because of much less planes as compared to dump1090-mutability.
Please see these posts:
Post #1376 - Installed modesDeco2 and stopped using dump1090-mutability
Post #1380 - member bramj reported seeing less planes with ModesDeco2 compared to plane seen with dump1090-mutability.
Post #1383 - I also noted seeing less planes with ModesDeco2
Next few posts - Tried changing settings, no use.
Post #1397 - Stopped using modesDeco2 and reverted to dump1090-mutability.
Does ModesDeco2 work with Mode A/C, MLAT and wideband 2.4Mhz reception?
Maybe the feed for MLAT was not working well.
I don’t think that modesdeco uses 2.4MHz bandwidth for decoding which makes quite a difference to performance. It can decode mode a/c and you can label inputs from MLAT though.
It does also support airspy, and I think prog (airspy developer) contributed to that, so it should give decent results.
Thanks @abcd567.I got better results with ModesDeco2 and RTL than dump1090-muta but that was like 8 months back.
Apparently ModesDeco2 doesn’t work with AirSpy Mini @ 3 MSPS sample rate and 6MSPS breaks the Rpi2’s USB.
Just out of curiosity, tried latest version of modesdeco2 today.
(1) downloaded “modesdeco2_rpi2_20150815.tgz” from the link given on page radarspotting.com/forum/index.ph … l#msg13471
(2) Run following commands
sudo tar xvf modesdeco2_rpi2_20150815.tgz
sudo service piaware stop
sudo service dump1090-mutability stop
./modesdeco2 --gain 49.6 --avrmlat 30002 --beast 30005 --rbs --msg 30003 --web 8080 --location 43.5xx:-79.6xx &
sudo service piaware start
(3) Checked Map on http: // :8080 - works fine, but fewer planes
Checked if MLAT is working
cat /tmp/piaware.out
Found
piaware version 2.1-5 is running, process ID 899
Connecting to FlightAware adept server at piaware.flightaware.com/1200
ADS-B data program ‘modesdeco2’ is listening on port 30005, so far so good
Starting faup1090: /usr/lib/piaware/helpers/faup1090 --net-bo-ipaddr localhost --net-bo-port 30005 --stdout --lat 43.5xx --lon -79.6xx
05/13/2016 15:02:33 Started faup1090 (pid 917) to connect to modesdeco2
05/13/2016 15:02:33 Connection with adept server at piaware.flightaware.com/1200 established
05/13/2016 15:02:34 FlightAware server SSL certificate validated
05/13/2016 15:02:34 encrypted session established with FlightAware
05/13/2016 15:02:34 autoUpdate is not configured in /etc/piaware or by piaware-config
05/13/2016 15:02:34 manualUpdate is not configured in /etc/piaware or by piaware-config
05/13/2016 15:02:34 multilateration support enabled (use piaware-config to disable)
05/13/2016 15:02:34 logged in to FlightAware as user abcd567
05/13/2016 15:02:34 piaware received a message from modesdeco2!
05/13/2016 15:02:34 piaware has successfully sent several msgs to FlightAware!
05/13/2016 15:02:34 multilateration support enabled (use piaware-config to disable)
05/13/2016 15:02:34 multilateration data requested, enabling mlat client
05/13/2016 15:02:34 Starting multilateration client: /usr/lib/piaware/helpers/fa-mlat-client --input-connect localhost:30005 --results beast,connect,localhost:30104 --results beast,connect,feed.adsbexchange.com:30106 --results ext_basestation,listen,30106 --udp-transport 70.42.6.198:7625:1610365398
05/13/2016 15:02:35 mlat(927): fa-mlat-client 0.2.4 starting up
05/13/2016 15:02:35 mlat(927): Using UDP transport to 70.42.6.198:7625
05/13/2016 15:02:35 mlat(927): Listening for Extended Basestation-format results connection on port 30106
05/13/2016 15:02:35 mlat(927): Input connected to localhost:30005
05/13/2016 15:02:35 mlat(927): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
05/13/2016 15:02:35 mlat(927): Beast-format results connection with feed.adsbexchange.com:30106: connection established
05/13/2016 15:03:03 73 msgs recv’d from modesdeco2; 73 msgs sent to FlightAware
05/13/2016 15:03:06 mlat(927): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
05/13/2016 15:03:36 mlat(927): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
05/13/2016 15:04:06 mlat(927): Beast-format results connection with localhost:30104: [Errno 111] Connection refused
Any idea how to make MLAT work?
Seems problem of setting of port 30104 in modesdeco2.
Settings in piaware:
piaware-config -mlatResultsFormat “beast,connect,localhost:30104”
My setup (piaware V3.0~dev) is a little different
#mlat-results-format beast,connect,localhost:30104 beast,listen,30105 ext_basestation,listen,30106
This is so I can poll the RPIs from VRS.
30005 for ads-b
30106 for MLAT
I could have changed 30106 to be the more efficient beast format.