Ok have a spare B+ and older flightaware stick. Wanted to experiment with 978 and wondered how one goes about setting up a dedicated 978 system. I would only use the standard antenna that came with a dongle I have laying around doing nothing. Just to experiment.
just curious.
Not up to speed on UAT, but I think using the ADS-B Receiver Project’s image is the easiest way to do it.
Like @Dxista said use the ADS-B Project. I would use the manual install, choosing Yes only to the 978. Scroll on that page for instructions.
You might need to install netcat manually before with:
apt-get install netcat
That is how I have it set up. I am running both the 1090 mutability and the 978 UAT
I have a question. Dump978 seems to output the decoded signals on port 30001.
In the dump1090-fa config file I have edited, at NET_OPTIONS, --net-ri-port 30001
Is that sending the UAT data to piaware and hence to piaware servers? If so, I assume it is ignored, because the planes that I see with UAT-only don’t get displayed. If they have ModeS also, they get displayed as MLAT.
Note that there are many combinations of transponder equipment installed. For example there are aircraft that appear to have a legacy Mode S transponder plus UAT. The legacy Mode S transponder can be MLAT’d by FlightAware where we don’t have UAT coverage.
UAT data, when your piaware is properly configured to feed it, will appear on flightaware.com. For example, here is a tracked UAT flight: Flight Track Log ✈ N512MT 29-Aug-2018 - FlightAware
I wonder if me using dump1090-fa instead of mutability one prevents transmission…
dump1090-fa will work. If you are on an sd card image of PiAware though, it may be difficult to configure dump978 to feed properly. I recommend a package install if you’re trying to setup dump978.
Yes, I have the package install, not the SD image.
I have a pi 3 b+ with a 3A power running 3.7.1. It’s not seeing the 978 sdr (NooElec Smart). Any suggestions. I am a noob.
Did you serialize the SDR like it showing in the instructions?
.
.
You misspelled the command, there is an extra w.
Copy the command with Ctrl-C and then do a right click in putty to paste it.
is there a test command I can use to know it is working?
sudo systemctl status dump978-fa
sudo systemctl status piaware
@abcd567 Old thread, I know, but I need to know how to permanently disable dump978-fa on my primary receiver. dump978-fa is running on my secondary receiver. Should I just uninstall dump978-fa? Thanks!
PS. Or does dump978-fa need to be running on the primary receiver in order to receive/process UAT from the secondary receiver?
Well how did you enable it … ?
Really you’re also not stating if you’re running the piaware image.
If it wasn’t a piaware image then uninstalling is the way to go.
You probably need this:
sudo piaware-config uat-receiver-type none
First, it’s a Debian PC running Piaware Debian Package Add-on. In another thread @obj advised me to run piaware-config uat-receiver-type other on the primary ADS-B receiver PC. Please let me know if you need more information.
Here’s my setup:
PC1 running Q4OS (Debian)
adminq@q4os-desktop:/etc/default$ sudo piaware-status
[sudo] password for adminq:
PiAware master process (piaware) is running with pid 12617.
PiAware ADS-B client (faup1090) is running with pid 12633.
PiAware ADS-B UAT client (faup978) is not running.
PiAware mlat client (fa-mlat-client) is running with pid 12629.
Local ADS-B receiver (dump1090-fa) is running with pid 12546.
Local ADS-B UAT receiver (dump978) is not running.
dump1090-fa (pid 12546) is listening for ES connections on port 30005.
no program appears to be listening for UAT connections on port 30978.
faup1090 is connected to the ADS-B receiver.
faup978 is NOT connected to the ADS-B UAT receiver.
piaware is connected to FlightAware.
got ‘couldn’t open socket: connection refused’
dump978 is NOT producing data on localhost:30978.
dump1090 is producing data on localhost:30005.
PC2 running Linux Mint (Debian - Q4OS wouldn’t install on this PC)
joe@adsb-uat:~$ sudo piaware-status
[sudo] password for joe:
PiAware master process (piaware) is running with pid 1039.
PiAware ADS-B client (faup1090) is not running.
PiAware ADS-B UAT client (faup978) is running with pid 2972.
PiAware mlat client (fa-mlat-client) is not running.
Local ADS-B receiver (dump1090) is not running.
Local ADS-B UAT receiver (dump978-fa) is running with pid 2932.
no program appears to be listening for ES connections on port 30005.
dump978-fa (pid 2932) is listening for UAT connections on port 30978.
faup1090 is NOT connected to the ADS-B receiver.
faup978 is connected to the ADS-B UAT receiver.
piaware is connected to FlightAware.
got ‘couldn’t open socket: connection refused’
dump1090 is NOT producing data on localhost:30005.
dump978 is producing data on localhost:30978.
As stated then … uninstall dump978-fa as i wrote.
I suppose … if it was a piaware image then setting the receiver to other would already have disabled dump978-fa 