# 978 users - Quick how to?

**URL:** <https://discussions.flightaware.com/t/978-users-quick-how-to/39567>\
**Category:** ADS-B Flight Tracking\
**Created:** [August 26, 2018, 4:41pm UTC](https://discussions.flightaware.com/t/978-users-quick-how-to/39567 "2018-08-26T16:41:34Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![w7psk](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/w7psk/32/136650_2.png) [@w7psk](https://discussions.flightaware.com/u/w7psk)\
**Post date:** [August 26, 2018, 4:41pm UTC](https://discussions.flightaware.com/t/978-users-quick-how-to/39567/1 "2018-08-26T16:41:35Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Dxista](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/dxista/32/137056_2.png) [@Dxista](https://discussions.flightaware.com/u/Dxista)\
**Post date:** [August 26, 2018, 4:46pm UTC](https://discussions.flightaware.com/t/978-users-quick-how-to/39567/2 "2018-08-26T16:46:46Z")

</div>

Not up to speed on UAT, but I think using the ADS-B Receiver Project’s image is the easiest way to do it.

---

<div class="post-metadata">

**Author:** ![SoNic67](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/sonic67/32/119872_2.png) [@SoNic67](https://discussions.flightaware.com/u/SoNic67)\
**Post date:** [August 26, 2018, 11:16pm UTC](https://discussions.flightaware.com/t/978-users-quick-how-to/39567/3 "2018-08-26T23:16:00Z")

</div>

Like @Dxista said use the [ADS-B Project](https://github.com/jprochazka/adsb-receiver). 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

---

<div class="post-metadata">

**Author:** ![glennblum](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/glennblum/32/113376_2.png) [@glennblum](https://discussions.flightaware.com/u/glennblum)\
**Post date:** [August 28, 2018, 12:28am UTC](https://discussions.flightaware.com/t/978-users-quick-how-to/39567/4 "2018-08-28T00:28:40Z")

</div>

That is how I have it set up. I am running both the 1090 mutability and the 978 UAT

---

<div class="post-metadata">

**Author:** ![SoNic67](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/sonic67/32/119872_2.png) [@SoNic67](https://discussions.flightaware.com/u/SoNic67)\
**Post date:** [August 30, 2018, 11:02am UTC](https://discussions.flightaware.com/t/978-users-quick-how-to/39567/5 "2018-08-30T11:02:10Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![ericcarlson](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/ericcarlson/32/116578_2.png) [@ericcarlson](https://discussions.flightaware.com/u/ericcarlson)\
**Post date:** [August 30, 2018, 1:26pm UTC](https://discussions.flightaware.com/t/978-users-quick-how-to/39567/6 "2018-08-30T13:26:05Z")

</div>

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](http://flightaware.com). For example, here is a tracked UAT flight: [Flight Track Log ✈ N512MT 29-Aug-2018 - FlightAware](https://flightaware.com/live/flight/N512MT/history/20180829/0716Z/tracklog)

---

<div class="post-metadata">

**Author:** ![SoNic67](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/sonic67/32/119872_2.png) [@SoNic67](https://discussions.flightaware.com/u/SoNic67)\
**Post date:** [August 30, 2018, 3:50pm UTC](https://discussions.flightaware.com/t/978-users-quick-how-to/39567/7 "2018-08-30T15:50:18Z")

</div>

I wonder if me using dump1090-fa instead of mutability one prevents transmission…

---

<div class="post-metadata">

**Author:** ![ericcarlson](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/ericcarlson/32/116578_2.png) [@ericcarlson](https://discussions.flightaware.com/u/ericcarlson)\
**Post date:** [August 30, 2018, 5:16pm UTC](https://discussions.flightaware.com/t/978-users-quick-how-to/39567/8 "2018-08-30T17:16:26Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![SoNic67](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/sonic67/32/119872_2.png) [@SoNic67](https://discussions.flightaware.com/u/SoNic67)\
**Post date:** [August 30, 2018, 6:41pm UTC](https://discussions.flightaware.com/t/978-users-quick-how-to/39567/9 "2018-08-30T18:41:43Z")

</div>

Yes, I have the package install, not the SD image.

---

<div class="post-metadata">

**Author:** ![W1MDS](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/w1mds/32/66750_2.png) [@W1MDS](https://discussions.flightaware.com/u/W1MDS)\
**Post date:** [July 11, 2019, 4:00pm UTC](https://discussions.flightaware.com/t/978-users-quick-how-to/39567/10 "2019-07-11T16:00:41Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![glennblum](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/glennblum/32/113376_2.png) [@glennblum](https://discussions.flightaware.com/u/glennblum)\
**Post date:** [July 11, 2019, 4:47pm UTC](https://discussions.flightaware.com/t/978-users-quick-how-to/39567/11 "2019-07-11T16:47:55Z")

</div>

Did you serialize the SDR like it showing in the instructions?

---

<div class="post-metadata">

**Author:** ![abcd567](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/abcd567/32/113769_2.png) [@abcd567](https://discussions.flightaware.com/u/abcd567)\
**Post date:** [July 11, 2019, 5:42pm UTC](https://discussions.flightaware.com/t/978-users-quick-how-to/39567/12 "2019-07-11T17:42:04Z")

</div>

> [@W1MDS](#):
>
> I have a pi 3 b+ with a 3A power running 3.7.1. It’s not seeing the 978 sdr (NooElec Smart)

### In Piaware SD Card image, _by default_ dump978 is disabled AND dump1090 is enabled.

# (A) To enable dump978-fa (in addition to dump1090-fa which is enabled by default)

# You _MUST_ Serialize Dongles to run both.

> [@How to Install and Configure Piaware 5.0 SD card image - Quickstart Guide](https://discussions.flightaware.com/t/how-to-install-and-configure-piaware-5-0-sd-card-image-quickstart-guide/48262/1):
>
> ### 6 - Configure UAT 978
> 
> ```auto
> sudo piaware-config uat-receiver-type sdr
> sudo piaware-config rtlsdr-device-index 00001090
> sudo piaware-config uat-sdr-device driver=rtlsdr,serial=00000978
> 
> # Reboot Pi to implement configuration settings
> sudo reboot
> 
> ```

.  
.

# (B) Enabling only one of the two (dump1090-fa OR dump978-fa)

> [@How to Install and Configure Piaware 5.0 SD card image - Quickstart Guide](https://discussions.flightaware.com/t/how-to-install-and-configure-piaware-5-0-sd-card-image-quickstart-guide/48262/1):
>
> ### 9 - USING ONLY ONE FREQUENCY (978 Mhz OR 1090 Mhz)
> 
> **9.1 - If you want to run 978 Mhz only**  
> In this case, you will need only one dongle, but you will have to disable dump1090-fa by following command
> 
> ```auto
> sudo piaware-config uat-receiver-type sdr
> sudo piaware-config receiver-type none
> sudo systemctl restart piaware
> 
> ```
> 
> To re-enable dump1090-fa (requires an additional dongle for dump1090-fa)
> 
> ```auto
> sudo piaware-config receiver-type rtlsdr
> sudo systemctl restart piaware
> 
> ```
> 
> **9.2 - If you want to run 1090 Mhz only**  
> In this case, you will need only one dongle, but you will have to disable dump978-fa by following command
> 
> ```auto
> sudo piaware-config receiver-type rtlsdr
> sudo piaware-config uat-receiver-type none
> sudo systemctl restart piaware
> 
> ```
> 
> To re-enable dump978-fa (requires an additional dongle for dump978-fa)
> 
> ```auto
> sudo piaware-config uat-receiver-type sdr
> sudo systemctl restart piaware
> 
> ```

---

<div class="post-metadata">

**Author:** ![W1MDS](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/w1mds/32/66750_2.png) [@W1MDS](https://discussions.flightaware.com/u/W1MDS)\
**Post date:** [July 11, 2019, 7:00pm UTC](https://discussions.flightaware.com/t/978-users-quick-how-to/39567/13 "2019-07-11T19:00:44Z")

</div>

_I got this error_

 ![Error serialized dongle.jpg](https://us1.discourse-cdn.com/flex019/uploads/flightaware/original/3X/9/0/903f1516739e7351a7b2358d997ce33ca2529b05.jpeg)

---

<div class="post-metadata">

**Author:** ![wiedehopf](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/wiedehopf/32/114045_2.png) [@wiedehopf](https://discussions.flightaware.com/u/wiedehopf)\
**Post date:** [July 11, 2019, 7:02pm UTC](https://discussions.flightaware.com/t/978-users-quick-how-to/39567/14 "2019-07-11T19:02:39Z")

</div>

> [@W1MDS](#):
>
> _I got this error_

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.

---

<div class="post-metadata">

**Author:** ![W1MDS](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/w1mds/32/66750_2.png) [@W1MDS](https://discussions.flightaware.com/u/W1MDS)\
**Post date:** [July 11, 2019, 7:18pm UTC](https://discussions.flightaware.com/t/978-users-quick-how-to/39567/15 "2019-07-11T19:18:31Z")

</div>

is there a test command I can use to know it is working?

---

<div class="post-metadata">

**Author:** ![abcd567](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/abcd567/32/113769_2.png) [@abcd567](https://discussions.flightaware.com/u/abcd567)\
**Post date:** [July 11, 2019, 7:28pm UTC](https://discussions.flightaware.com/t/978-users-quick-how-to/39567/16 "2019-07-11T19:28:54Z")

</div>

`sudo systemctl status dump978-fa `

`sudo systemctl status piaware `

---

<div class="post-metadata">

**Author:** ![jepolch](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jepolch/32/114457_2.png) [@jepolch](https://discussions.flightaware.com/u/jepolch)\
**Post date:** [April 23, 2021, 3:40pm UTC](https://discussions.flightaware.com/t/978-users-quick-how-to/39567/17 "2021-04-23T15:40:25Z")

</div>

@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?

---

<div class="post-metadata">

**Author:** ![wiedehopf](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/wiedehopf/32/114045_2.png) [@wiedehopf](https://discussions.flightaware.com/u/wiedehopf)\
**Post date:** [April 23, 2021, 4:55pm UTC](https://discussions.flightaware.com/t/978-users-quick-how-to/39567/18 "2021-04-23T16:55:33Z")

</div>

> [@jepolch](#):
>
> how to permanently disable dump978-fa on my primary 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:

```auto
sudo piaware-config uat-receiver-type none

```

---

<div class="post-metadata">

**Author:** ![jepolch](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jepolch/32/114457_2.png) [@jepolch](https://discussions.flightaware.com/u/jepolch)\
**Post date:** [April 23, 2021, 5:32pm UTC](https://discussions.flightaware.com/t/978-users-quick-how-to/39567/19 "2021-04-23T17:32:50Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![wiedehopf](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/wiedehopf/32/114045_2.png) [@wiedehopf](https://discussions.flightaware.com/u/wiedehopf)\
**Post date:** [April 23, 2021, 5:44pm UTC](https://discussions.flightaware.com/t/978-users-quick-how-to/39567/20 "2021-04-23T17:44:04Z")

</div>

> [@jepolch](#):
>
> First, it’s a Debian PC running Piaware Debian Package Add-on.

As stated then … uninstall dump978-fa as i wrote.

> [@wiedehopf](#):
>
> If it wasn’t a piaware image then uninstalling is the way to go.

I suppose … if it was a piaware image then setting the receiver to other would already have disabled dump978-fa 🙂

[Next page](https://discussions.flightaware.com/t/978-users-quick-how-to/39567.md?page=2)
