The UAT SkyView is independent: http://pi/skyview978
(with pi being the address of your pi)
With only one dongle you can deactivate dump1090-fa if you want UAT only.
Also always good to check the serials with:
rtl_test
I stopped dump1090 after confirming the dongle works. Serial #s look good and I have the right url for the Skyview map.
1 Like
sudo journalctl -eu dump1090-fa
sudo journalctl -eu dump978-fa
(please provide the info from those logs)
pi@Pi3Ofc:~ $ sudo journalctl -eu dump1090-fa
May 04 13:56:18 Pi3Ofc systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
May 04 13:56:18 Pi3Ofc systemd[1]: dump1090-fa.service: Unit entered failed state.
May 04 13:56:18 Pi3Ofc systemd[1]: dump1090-fa.service: Failed with result ‘exit-code’.
May 04 13:56:26 Pi3Ofc systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
May 04 13:56:26 Pi3Ofc systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
May 04 13:56:26 Pi3Ofc dump1090-fa[26044]: Sat May 4 13:56:26 2019 CDT dump1090-fa 3.6.3 starting up.
May 04 13:56:26 Pi3Ofc dump1090-fa[26044]: rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000978)
May 04 13:56:26 Pi3Ofc systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
May 04 13:56:26 Pi3Ofc systemd[1]: dump1090-fa.service: Unit entered failed state.
May 04 13:56:26 Pi3Ofc systemd[1]: dump1090-fa.service: Failed with result ‘exit-code’.
May 04 13:56:56 Pi3Ofc systemd[1]: dump1090-fa.service: Service hold-off time over, scheduling restart.
May 04 13:56:56 Pi3Ofc systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
May 04 13:56:56 Pi3Ofc systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
May 04 13:56:56 Pi3Ofc dump1090-fa[26182]: Sat May 4 13:56:56 2019 CDT dump1090-fa 3.6.3 starting up.
May 04 13:56:56 Pi3Ofc dump1090-fa[26182]: rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000978)
May 04 13:56:56 Pi3Ofc systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
May 04 13:56:56 Pi3Ofc systemd[1]: dump1090-fa.service: Unit entered failed state.
May 04 13:56:56 Pi3Ofc systemd[1]: dump1090-fa.service: Failed with result ‘exit-code’.
May 04 13:57:26 Pi3Ofc systemd[1]: dump1090-fa.service: Service hold-off time over, scheduling restart.
May 04 13:57:26 Pi3Ofc systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
May 04 13:57:26 Pi3Ofc systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
May 04 13:57:26 Pi3Ofc dump1090-fa[26319]: Sat May 4 13:57:26 2019 CDT dump1090-fa 3.6.3 starting up.
May 04 13:57:26 Pi3Ofc dump1090-fa[26319]: rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000978)
May 04 13:57:26 Pi3Ofc systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
May 04 13:57:26 Pi3Ofc systemd[1]: dump1090-fa.service: Unit entered failed state.
May 04 13:57:26 Pi3Ofc systemd[1]: dump1090-fa.service: Failed with result ‘exit-code’.
May 04 13:57:57 Pi3Ofc systemd[1]: dump1090-fa.service: Service hold-off time over, scheduling restart.
May 04 13:57:57 Pi3Ofc systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
May 04 13:57:57 Pi3Ofc systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
May 04 13:57:57 Pi3Ofc dump1090-fa[26466]: Sat May 4 13:57:57 2019 CDT dump1090-fa 3.6.3 starting up.
May 04 13:57:57 Pi3Ofc dump1090-fa[26466]: rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000978)
May 04 13:57:57 Pi3Ofc systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
May 04 13:57:57 Pi3Ofc systemd[1]: dump1090-fa.service: Unit entered failed state.
May 04 13:57:57 Pi3Ofc systemd[1]: dump1090-fa.service: Failed with result ‘exit-code’.
May 04 13:58:27 Pi3Ofc systemd[1]: dump1090-fa.service: Service hold-off time over, scheduling restart.
May 04 13:58:27 Pi3Ofc systemd[1]: Stopped dump1090 ADS-B receiver (FlightAware customization).
May 04 13:58:27 Pi3Ofc systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
May 04 13:58:27 Pi3Ofc dump1090-fa[26613]: Sat May 4 13:58:27 2019 CDT dump1090-fa 3.6.3 starting up.
May 04 13:58:27 Pi3Ofc dump1090-fa[26613]: rtlsdr: using device #0: Generic RTL2832U OEM (Realtek, RTL2838UHIDIR, SN 00000978)
May 04 13:58:27 Pi3Ofc systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
May 04 13:58:27 Pi3Ofc systemd[1]: dump1090-fa.service: Unit entered failed state.
May 04 13:58:27 Pi3Ofc systemd[1]: dump1090-fa.service: Failed with result ‘exit-code’.
lines 960-1001/1001 (END)
Trying to use the wrong dongle. You don’t have the serial configured correctly in /etc/default/dump1090-fa
Or are you on the sd-card install?
pi@Pi3Ofc:~ $ sudo journalctl -eu dump978-fa
May 04 13:03:45 Pi3Ofc dump978-fa[11350]: raw-port: listening for connections on [::]:30978
May 04 13:03:45 Pi3Ofc dump978-fa[11350]: json-port: listening for connections on 0.0.0.0:30979
May 04 13:03:45 Pi3Ofc dump978-fa[11350]: json-port: listening for connections on [::]:30979
May 04 13:03:45 Pi3Ofc dump978-fa[11350]: linux; GNU C++ version 6.2.0 20161010; Boost_106100; UHD_003.009.005-0-unknown
May 04 13:03:45 Pi3Ofc dump978-fa[11350]: Detached kernel driver
May 04 13:03:46 Pi3Ofc dump978-fa[11350]: Found Rafael Micro R820T tuner
May 04 13:03:46 Pi3Ofc dump978-fa[11350]: Reattached kernel driver
May 04 13:03:46 Pi3Ofc dump978-fa[11350]: Detached kernel driver
May 04 13:03:46 Pi3Ofc dump978-fa[11350]: Found Rafael Micro R820T tuner
May 04 13:03:47 Pi3Ofc dump978-fa[11350]: Exact sample rate is: 2083333.135571 Hz
May 04 13:03:47 Pi3Ofc dump978-fa[11350]: [R82XX] PLL not locked!
May 04 13:03:47 Pi3Ofc dump978-fa[11350]: SoapySDR: using maximum manual gain 49.6 dB
May 04 13:03:47 Pi3Ofc dump978-fa[11350]: SoapySDR: using stream setting buffsize=262144
May 04 13:04:15 Pi3Ofc dump978-fa[11350]: [::]:30978: accepted a connection from [::1]:42536
May 04 13:23:51 Pi3Ofc dump978-fa[11350]: Caught signal 15, exiting
May 04 13:23:51 Pi3Ofc systemd[1]: Stopping dump978 ADS-B UAT receiver…
May 04 13:23:51 Pi3Ofc dump978-fa[11350]: Reattached kernel driver
May 04 13:23:51 Pi3Ofc systemd[1]: dump978-fa.service: Main process exited, code=exited, status=1/FAILURE
May 04 13:23:51 Pi3Ofc systemd[1]: Stopped dump978 ADS-B UAT receiver.
May 04 13:23:51 Pi3Ofc systemd[1]: dump978-fa.service: Unit entered failed state.
May 04 13:23:51 Pi3Ofc systemd[1]: dump978-fa.service: Failed with result ‘exit-code’.
May 04 13:23:51 Pi3Ofc systemd[1]: Started dump978 ADS-B UAT receiver.
May 04 13:23:51 Pi3Ofc dump978-fa[17004]: raw-port: listening for connections on 0.0.0.0:30978
May 04 13:23:51 Pi3Ofc dump978-fa[17004]: raw-port: listening for connections on [::]:30978
May 04 13:23:51 Pi3Ofc dump978-fa[17004]: json-port: listening for connections on 0.0.0.0:30979
May 04 13:23:51 Pi3Ofc dump978-fa[17004]: json-port: listening for connections on [::]:30979
May 04 13:23:51 Pi3Ofc dump978-fa[17004]: linux; GNU C++ version 6.2.0 20161010; Boost_106100; UHD_003.009.005-0-unknown
May 04 13:23:51 Pi3Ofc dump978-fa[17004]: Detached kernel driver
May 04 13:23:52 Pi3Ofc dump978-fa[17004]: Found Rafael Micro R820T tuner
May 04 13:23:52 Pi3Ofc dump978-fa[17004]: Reattached kernel driver
May 04 13:23:52 Pi3Ofc dump978-fa[17004]: Detached kernel driver
May 04 13:23:53 Pi3Ofc dump978-fa[17004]: Found Rafael Micro R820T tuner
May 04 13:23:53 Pi3Ofc dump978-fa[17004]: Exact sample rate is: 2083333.135571 Hz
May 04 13:23:53 Pi3Ofc dump978-fa[17004]: [R82XX] PLL not locked!
May 04 13:23:53 Pi3Ofc dump978-fa[17004]: SoapySDR: using maximum manual gain 49.6 dB
May 04 13:23:53 Pi3Ofc dump978-fa[17004]: SoapySDR: using stream setting buffsize=262144
May 04 13:24:21 Pi3Ofc dump978-fa[17004]: [::]:30978: accepted a connection from [::1]:42538
May 04 14:01:53 Pi3Ofc dump978-fa[17004]: Caught signal 15, exiting
May 04 14:01:53 Pi3Ofc systemd[1]: Stopping dump978 ADS-B UAT receiver…
May 04 14:01:54 Pi3Ofc systemd[1]: dump978-fa.service: Main process exited, code=exited, status=1/FAILURE
May 04 14:01:54 Pi3Ofc systemd[1]: Stopped dump978 ADS-B UAT receiver.
May 04 14:01:54 Pi3Ofc systemd[1]: dump978-fa.service: Unit entered failed state.
May 04 14:01:54 Pi3Ofc systemd[1]: dump978-fa.service: Failed with result ‘exit-code’.
May 04 14:01:54 Pi3Ofc systemd[1]: Started dump978 ADS-B UAT receiver.
May 04 14:01:54 Pi3Ofc dump978-fa[27599]: raw-port: listening for connections on 0.0.0.0:30978
May 04 14:01:54 Pi3Ofc dump978-fa[27599]: raw-port: listening for connections on [::]:30978
May 04 14:01:54 Pi3Ofc dump978-fa[27599]: json-port: listening for connections on 0.0.0.0:30979
May 04 14:01:54 Pi3Ofc dump978-fa[27599]: json-port: listening for connections on [::]:30979
May 04 14:01:54 Pi3Ofc dump978-fa[27599]: linux; GNU C++ version 6.2.0 20161010; Boost_106100; UHD_003.009.005-0-unknown
May 04 14:01:54 Pi3Ofc dump978-fa[27599]: Detached kernel driver
May 04 14:01:54 Pi3Ofc dump978-fa[27599]: Found Rafael Micro R820T tuner
May 04 14:01:55 Pi3Ofc dump978-fa[27599]: Reattached kernel driver
May 04 14:01:55 Pi3Ofc dump978-fa[27599]: Detached kernel driver
May 04 14:01:55 Pi3Ofc dump978-fa[27599]: Found Rafael Micro R820T tuner
May 04 14:01:55 Pi3Ofc dump978-fa[27599]: Exact sample rate is: 2083333.135571 Hz
May 04 14:01:55 Pi3Ofc dump978-fa[27599]: [R82XX] PLL not locked!
May 04 14:01:55 Pi3Ofc dump978-fa[27599]: SoapySDR: using maximum manual gain 49.6 dB
May 04 14:01:56 Pi3Ofc dump978-fa[27599]: SoapySDR: using stream setting buffsize=262144
May 04 14:02:24 Pi3Ofc dump978-fa[27599]: [::]:30978: accepted a connection from [::1]:42540
lines 171-229/229 (END)
BTW,
I have only one dongle on this pi3.
So disable dump1090-fa
sudo systemctl disable --now dump1090-fa
Might also need to set
sudo piaware-config receiver-type none
so piaware doesn’t start it.
If you can’t wait you can build and install whole piaware 3.7.1 package like this:
sudo apt install -y build-essential debhelper tcl8.6-dev autoconf python3-dev python3-venv dh-systemd libz-dev
git clone --branch dev https://github.com/flightaware/piaware_builder.git
cd piaware_builder/
./sensible-build.sh stretch
cd package-stretch
dpkg-buildpackage -b
cd ..
sudo dpkg -i piaware_3.7.1_armhf.deb
sudo reboot
But this is what I get now from piaware-status:
PiAware master process (piaware) is running with pid 563.
PiAware ADS-B client (faup1090) is running with pid 712.
PiAware ADS-B UAT client (faup978) is not running.
PiAware mlat client (fa-mlat-client) is running with pid 981.
Local ADS-B receiver (dump1090-fa) is running with pid 562.dump1090-fa (pid 562) is listening for connections on port 30005.
dump978-fa (pid 565) is listening for 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.dump1090 is producing data on localhost:30005.
Why there is “faup978 is NOT connected to the ADS-B UAT receiver.”?
You have built and installed piware data feeder.
Did you built and install dump978-fa also?
What is the output of following commands?
apt-cache policy dump978-fa
apt-cache policy skyview978
Yup build both.
sudo apt install build-essential debhelper dh-systemd libboost-system-dev libboost-program-options-dev libboost-regex-dev libboost-filesystem-dev libsoapysdr-dev librtlsdr-dev pkg-config libncurses5-dev libbladerf-dev
git clone --depth 1 --branch dev https://github.com/flightaware/dump978.git
git clone --depth 1 --branch dev https://github.com/flightaware/dump1090.git
cd dump1090
dpkg-buildpackage -b
cd ../dump978
dpkg-buildpackage -b
sudo dpkg -i ../dump1090-fa_3.7.1_armhf.deb
sudo dpkg -i ../dump978-fa_3.7.1_armhf.deb
Both your commands say 3.7.1 installed
I had the same issue with faup978 as varnav, actually skyview978 was not working either. I had to manually install skyview978 package using dpkg. I rebuilt and reinsatalled piaware 3.7.1.
I ended up running the following commands, then faup978 started working.
sudo piaware-config uat-receiver-type sdr
sudo piaware-config rtlsdr-device-index 00001090
sudo piaware-config uat-sdr-device driver=rtlsdr,serial=00000978
I think the first line did something, I believe it told me the 2nd two were already there…
1 Like
Perfect! It works now.
PiAware master process (piaware) is running with pid 645.
PiAware ADS-B client (faup1090) is running with pid 904.
PiAware ADS-B UAT client (faup978) is running with pid 914.
PiAware mlat client (fa-mlat-client) is not running.
Local ADS-B receiver (dump1090-fa) is running with pid 644.dump1090-fa (pid 644) is listening for connections on port 30005.
dump978-fa (pid 651) is listening for connections on port 30978.
faup1090 is connected to the ADS-B receiver.
faup978 is connected to the ADS-B UAT receiver.
piaware is connected to FlightAware.dump1090 is producing data on localhost:30005.
But it seems that dump978 is not mentioned too often here.
This is NOT a piaware SD card image. It is a package install. The command sudo piaware-config [parameter] [value] will NOT change settings of dump1090-fa and dump978-fa.
To change the settings of dump1090-fa, edit file:
sudo nano /etc/default/dump1090-fa
To change the settings of dump978-fa, edit file:
sudo nano /etc/default/dump978-fa
Please see following parts of Post#15
.
.
1 Like
Probably that serial part worked as I did that already. So looks like sudo piaware-config uat-receiver-type sdr did actual magic.
1 Like
Most likely you are right.
This is new stuff for us all, so we will gradually discover the fine details.
1 Like
Probably best way to check if it works at all is by this command
journalctl -u piaware | grep 978
I see many
0 msgs recv’d from dump978-fa (0 in last 5m); 0 msgs sent to FlightAware
Looks like it works, but my receiver picks nothing. That’s another story, will need to play with antenna, filter, etc.
Yes, you are right. Setting uat-receiver-type sdr in piaware config tells piaware to get data from dump978-fa.
By default uat-receiver-type is set to none, and piaware closes connection to dump978-fa.
I just set the uat-receiver-type to none, and piaware stopped receiving dump978 messages. I then set uat-receiver-type to sdr, and piaware opened connection to dump978-fa and again started receiving dump978 messages.
I have now added this command in piaware installation part of post 16.
BTW great manual you have there, just I recommend to use:
git clone --depth 1 --branch v3.7.1 https://github.com/flightaware/dump978.git
git clone --depth 1 --branch v3.7.1 https://github.com/flightaware/dump1090.git
Will be faster and no need to checkout.
1 Like