"If you are on a normal PC laptop and not on an RPi, i’d recommend using readsb instead of dump1090-fa: Automatic installation for readsb · wiedehopf/adsb-scripts Wiki · GitHub
Generally readsb might be nicer than dump1090-fa. Just to reiterate, this needs to be done before running this script. Or you can rerun this install script after installing readsb. You’ll have to reconfigure airspy_adsb as this install overwrites the configuration."
Whats the difference between both?
readsb doesn’t have adaptive gain.
But it has actual range outline which many people fancy.
Otherwise it’s mostly a different flavor. (forked from dump1090-fa 3 years ago or so … then you’re linking my version which was forked from Mictronics readsb 2 years ago?)
ohhw i didn’t know there was another version…
well…
i use dump1090-fa now… and i think; i will use that 
I thought; maybe there is a significant difference between the two
Well i answered that from a home receiver perspective.
It has the ability to establish outbound network connections and has lots of stuff required make a combined display with more than 1000 aircraft work.
At least when i last checked it can also handle higher messages rates coming in via the network. But that’s not of interest to home users 
So installing it will remove dump1090-fa, but you can uninstall it and reinstall dump1090-fa and it should use your old config.
Just in case you want to try it.
You can use it to get a historic replay (/?replay), a historic heatmap (?/heatmap) and historic traces per aircraft using persistent storage: GitHub - wiedehopf/tar1090: Provides an improved webinterface for use with ADS-B decoders readsb / dump1090-fa
But that requires some willingness to tinker, i don’t support those features for cookie cutter automatic installs.
Oh i think dump1090-fa will not show winds aloft, readsb will if the data is being interrogated (depends on where you are).
Oh, this is good news. I can avoid using modesmixer2 if I replace dump1090-fa by readsb.
Currently I use dump1090-fa + modesmixer2 to make connection in order to feed adsbhub and many other private sites using following parameter in modesmixer2:
--outConnect [data-format]:[site address]:[site port]
I run one of each! 
I’m trying to install readsb on a PC running Ubuntu and it fails. FA Flightstick (orange) is plugged in. dump1090-fa was not removed. Should I have shut down dump before running the readsb install script?
--------------
All done! Webinterface available at http://192.168.1.140/tar1090
--------------
--------------
Sep 16 17:49:50 adsb2 systemd[1]: Started readsb ADS-B receiver.
Sep 16 17:49:50 adsb2 readsb[375753]: readsb version: wiedehopf git: 4403418 (commited: Tue Sep 14 17:20:52 2021 0200)
Sep 16 17:49:50 adsb2 readsb[375753]: Error opening the listening port 30002 (Raw TCP output): bind: Address already in use
Sep 16 17:49:50 adsb2 systemd[1]: readsb.service: Main process exited, code=exited, status=1/FAILURE
Sep 16 17:49:50 adsb2 systemd[1]: readsb.service: Failed with result 'exit-code'.
Sep 16 17:49:54 adsb2 systemd[1]: Stopped readsb ADS-B receiver.
Sep 16 17:49:54 adsb2 systemd[1]: Started readsb ADS-B receiver.
Sep 16 17:49:54 adsb2 readsb[376451]: readsb version: wiedehopf git: 4403418 (commited: Tue Sep 14 17:20:52 2021 0200)
Sep 16 17:49:54 adsb2 readsb[376451]: Error opening the listening port 30002 (Raw TCP output): bind: Address already in use
Sep 16 17:49:54 adsb2 systemd[1]: readsb.service: Main process exited, code=exited, status=1/FAILURE
Sep 16 17:49:54 adsb2 systemd[1]: readsb.service: Failed with result 'exit-code'.
Sep 16 17:50:25 adsb2 systemd[1]: readsb.service: Scheduled restart job, restart counter is at 2.
Sep 16 17:50:25 adsb2 systemd[1]: Stopped readsb ADS-B receiver.
Sep 16 17:50:25 adsb2 systemd[1]: Started readsb ADS-B receiver.
Sep 16 17:50:25 adsb2 readsb[376797]: readsb version: wiedehopf git: 4403418 (commited: Tue Sep 14 17:20:52 2021 0200)
Sep 16 17:50:25 adsb2 readsb[376797]: Error opening the listening port 30002 (Raw TCP output): bind: Address already in use
Sep 16 17:50:25 adsb2 systemd[1]: readsb.service: Main process exited, code=exited, status=1/FAILURE
Sep 16 17:50:25 adsb2 systemd[1]: readsb.service: Failed with result 'exit-code'.
Sep 16 17:50:30 adsb2 systemd[1]: Stopped readsb ADS-B receiver.
Sep 17 10:17:51 adsb2 systemd[1]: Started readsb ADS-B receiver.
Sep 17 10:17:51 adsb2 readsb[596867]: readsb version: wiedehopf git: e36cc8a (commited: Tue Sep 14 19:17:22 2021 0200)
Sep 17 10:17:51 adsb2 readsb[596867]: Error opening the listening port 30002 (Raw TCP output): bind: Address already in use
Sep 17 10:17:51 adsb2 systemd[1]: readsb.service: Main process exited, code=exited, status=1/FAILURE
Sep 17 10:17:51 adsb2 systemd[1]: readsb.service: Failed with result 'exit-code'.
Sep 17 10:17:56 adsb2 systemd[1]: Stopped readsb ADS-B receiver.
Sep 17 10:17:56 adsb2 systemd[1]: Started readsb ADS-B receiver.
Sep 17 10:17:56 adsb2 readsb[597586]: readsb version: wiedehopf git: e36cc8a (commited: Tue Sep 14 19:17:22 2021 0200)
Sep 17 10:17:56 adsb2 readsb[597586]: Error opening the listening port 30002 (Raw TCP output): bind: Address already in use
Sep 17 10:17:56 adsb2 systemd[1]: readsb.service: Main process exited, code=exited, status=1/FAILURE
Sep 17 10:17:56 adsb2 systemd[1]: readsb.service: Failed with result 'exit-code'.
--------------
--------------
ERROR: readsb service didn't start.
common issues: SDR not plugged in.
the webinterface will show an error until readsb is running!
Well that’s the issue, they are trying to use the same ports (as the log states).
Yeah i think i’m only disabling it, not removing it.
Anyhow just remove or disable it yourself?
I did that and rebooted. It’s working now. Thanks!
That’s what happen to me too, had to remove it manually.
I ran the install script a few times with the same failure. Maybe (?) the script doesn’t disable dump1090-fa since v6.x.
I wanted to try readsb on a box I’m setting up as a reference station to compare with my main station with Airspy. The reference is using the orange Flightstick. Just waiting for my Minicircuits splitter.
Better than me. I am using a cheap Y splitter that has two cables soldered together. It’s after the LNB so not important to be impedance matched IMO.
I just wanted to make sure I had a good splitter so my main station didn’t suffer too much from insertion loss.
With tax and shipping included, this costs about half of what you will pay if you buy from Minicircuits.
That’s as much as the LNA. I have enough gain… I can afford to lose a fed dB there on the tail of LNA.
I got myself a commercial license for my Airsquitter (Jetvision).
Now all ports are open and i played around with it.
Set up a Raspberry, grab the raw data from that device, parsed it through modesmixer2.
then i installed readsb with tar and graphs 1090 in network mode.
Works flawless, even the current range is displayed.
Tried it with dump1090-fa and never got it working.
So this is an additional clear “plus” for readsb over dump1090
Wow, are you going “commercial”? Switching careers? 
Where is the setting in tar1090 to draw the range plot? Thanks.
The range plot is working only if you’re using readsb. It will not show up if you’re using dump1090-fa
The switch to show/hide can be found in the map menu of tar1090. If readsb is not use, the switch simply does nothing
Not really… it was just because… well, i cannot tell a real “good” reason. Just for fun.
You can do it just fine with beast-splitter.
But yeah this is all in one …
That would have been my choice if… well if you would not have shared the better solution with readsb
