Getting RTL-SDR working, can't find piaware-config file

Hi all,

I just installed piaware on an existing Pi4 and everything seems to be working and is recognized on Flightaware but my RTL-SDR V4 is not putting out any data on dump1090. Here is the result of piaware-status…

PiAware master process (piaware) is running with pid 23996.
PiAware ADS-B client (faup1090) is running with pid 326914.
PiAware ADS-B UAT client (faup978) is not running (disabled by configuration settings)
PiAware mlat client (fa-mlat-client) is running with pid 128435.
Local ADS-B receiver (dump1090-fa) is running with pid 326659.

dump1090-fa (pid 326659) is listening for ES connections on port 30005.
faup1090 is connected to the ADS-B receiver.
piaware is connected to FlightAware.

dump1090 is NOT producing data on localhost:30005.

And lsusb…

admin@MQTTraspberrypi:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 0bda:2838 Realtek Semiconductor Corp. RTL2838 DVB-T
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

And …

admin@MQTTraspberrypi:~ $ sudo systemctl status dump1090-fa -l
* dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
     Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; preset: enabled)
     Active: active (running) since Thu 2025-05-22 17:04:24 PDT; 1h 1min ago
       Docs: https://flightaware.com/adsb/piaware/
   Main PID: 326659 (dump1090-fa)
      Tasks: 3 (limit: 3913)
     Memory: 3.0M
        CPU: 7min 17.940s
     CGroup: /system.slice/dump1090-fa.service
             `-326659 /usr/bin/dump1090-fa --quiet --device-type rtlsdr --gain 60 --adaptive-range --fix --lat 50.45228 --lon -119.38985 --max-range 360 --net-ro-port 30002 --net-sbs-port 30003 --net-bi-port 30004,30104 --net-bo-port 300>

May 22 17:04:24 MQTTraspberrypi dump1090-fa[326659]: Detached kernel driver
May 22 17:04:24 MQTTraspberrypi dump1090-fa[326659]: Found Rafael Micro R828D tuner
May 22 17:04:25 MQTTraspberrypi dump1090-fa[326659]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)
May 22 17:04:25 MQTTraspberrypi dump1090-fa[326659]: [R82XX] PLL not locked!
May 22 17:04:25 MQTTraspberrypi dump1090-fa[326659]: [R82XX] PLL not locked!
May 22 17:04:25 MQTTraspberrypi dump1090-fa[326659]: adaptive: using 50% duty cycle
May 22 17:04:25 MQTTraspberrypi dump1090-fa[326659]: adaptive: enabled adaptive gain control with gain limits 0.0dB (step 0) .. 58.6dB (step 29)
May 22 17:04:25 MQTTraspberrypi dump1090-fa[326659]: adaptive: enabled dynamic range control, target dynamic range 30.0dB
May 22 17:04:25 MQTTraspberrypi dump1090-fa[326659]: Allocating 4 zero-copy buffers
May 22 17:04:35 MQTTraspberrypi dump1090-fa[326659]: adaptive: reached upper gain limit, halting dynamic range scan here
lines 1-21/21 (END)

I have searched for the piaware-config file but can’t find it anywhere. I installed the program using @abcd567 method posted here a year or so ago. Found here…

https://github.com/abcd567a/piaware-ubuntu-debian-amd64/blob/master/README.md

Any help getting this working would be greatly appreciated.

Cheers

The method you have used does a package install.

The file piaware-config.txt is NOT available in package install. It is available only in Piaware SD card image.

For package install, the config is saved in file /etc/piaware.conf .
Please see screenshot below.

 

 

1 Like

Hi Paul,

The rtl-sdr.com v4 uses a different chip from most of the other rtl devices. It requires special drivers to work with most software.

See details here and tips on how to install those v4 specific drivers. Note that these “v4” drivers will be backwards compatible with all the rtl devices, so it will not cause any problems. I have two of the v4. They are not ideal for 1090, but do work fine.

RTL-SDR Blog V4 Users Guide

Good luck,
-Dan

1 Like

Okay cool, thank you found that one, it’s empty except for instructions. I’ll need to find all things that need to go in there, maybe it’s just the few lines telling it to look for rtl-sdr and to auto update.

Need to thank you for all your work here to help us get this working, I have seen MANY posts and such you have made over the years, really appreciate the effort.

Cheers

1 Like

Thanks Dan,

I have read about the differences between the V3 and V4…I’ll try the config file update first then if need be find new drivers per your suggestion.

Appreciate the help!

Cheers

Okay still not working…changed the piaware.conf file…here is my piaware.conf file contents…

feeder-id xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
receiver-type rtlsdr
rtlsdr-gain 40
use-gpsd yes

And the result of piaware-status

admin@MQTTraspberrypi:~ $ sudo piaware-status
PiAware master process (piaware) is running with pid 1105.
PiAware ADS-B client (faup1090) is running with pid 1316.
PiAware ADS-B UAT client (faup978) is not running (disabled by configuration settings)
PiAware mlat client (fa-mlat-client) is running with pid 4972.
Local ADS-B receiver (dump1090-fa) is running with pid 781.

dump1090-fa (pid 781) is listening for ES connections on port 30005.
faup1090 is connected to the ADS-B receiver.
piaware is connected to FlightAware.

dump1090 is NOT producing data on localhost:30005.

Your feeder ID is xxxxxxxxxxxxxxxxxxxxxxxxxxxxx (configured at /etc/piaware.conf:17)

Please know that I am only 6 months into learning Linux, computer savvy but Linux deprived.

Thanks

Hi Dan,

I followed the instructions given on that page verbatum and here are the results…

admin@MQTTraspberrypi:~ $ sudo piaware-status
PiAware master process (piaware) is running with pid 1132.
PiAware ADS-B client (faup1090) is not running.
PiAware ADS-B UAT client (faup978) is not running (disabled by configuration settings)
PiAware mlat client (fa-mlat-client) is not running.
Local ADS-B receiver (dump1090) is not running.

no program appears to be listening for ES connections on port 30005.
faup1090 is NOT connected to the ADS-B receiver.
piaware is connected to FlightAware.

got 'couldn't open socket: connection refused'
dump1090 is NOT producing data on localhost:30005.

I’m going to bed. I’ll try again tomorrow.

If you want to try a different image that is known to work with rtl-sdr v4 out of the box, give this a try: https://discussions.flightaware.com/t/a-simple-way-to-feed-ads-b-data/90183

Otherwise piaware-status is kinda inadequate to see what is going on.
As root, looking at the dump1090-fa log will be more useful:

sudo su -
journalctl -u dump1090-fa

piaware status was showing dump1090-fa was running before you tried to install the drivers
Oh, apparently the previous instructions didn’t mention it, you have to use this section of the guide at RTL-SDR Blog V4 Users Guide

Alternative Debian Package Installation Method

Otherwise it’s just not gonna work with most software as they require the driver package to be installed as a dependency.
After doing that you will have to reinstall dump1090-fa.

1 Like

I think you are onto something here…so for me, newbie Linux guy, how do I undo what I did in the first section of those instructions, before I implement the section you mentioned? Or can I just run the second method and it will “fix” what didn’t work in the first method?

I’m hoping Linux doesn’t operate like windoze in that everything you do continues to bloat the registry and clog up the system, no matter what.

Thanks for your help.

Cheers

Here is the result of the journalctl -u dump1090-fa it continues in a loop, over and over.

May 22 11:31:27 MQTTraspberrypi systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.
May 22 11:31:57 MQTTraspberrypi systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is at 48.
May 22 11:31:57 MQTTraspberrypi systemd[1]: Stopped dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
May 22 11:31:57 MQTTraspberrypi systemd[1]: Started dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
May 22 11:31:57 MQTTraspberrypi dump1090-fa[45226]: Thu May 22 11:31:57 2025 PDT  dump1090-fa 8.2~bpo9+1 starting up.
May 22 11:31:57 MQTTraspberrypi dump1090-fa[45226]: rtlsdr: no supported devices found.
May 22 11:31:57 MQTTraspberrypi systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
May 22 11:31:57 MQTTraspberrypi systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.
May 22 11:32:27 MQTTraspberrypi systemd[1]: dump1090-fa.service: Scheduled restart job, restart counter is at 49.
May 22 11:32:27 MQTTraspberrypi systemd[1]: Stopped dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
May 22 11:32:27 MQTTraspberrypi systemd[1]: Started dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
May 22 11:32:27 MQTTraspberrypi dump1090-fa[46105]: Thu May 22 11:32:27 2025 PDT  dump1090-fa 8.2~bpo9+1 starting up.
May 22 11:32:27 MQTTraspberrypi dump1090-fa[46105]: rtlsdr: no supported devices found.
May 22 11:32:27 MQTTraspberrypi systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE

OK, just started reading the thread you posted

If you want to try a different image that is known to work with rtl-sdr v4 out of the box, give this a try: A simple way to feed ADS-B data

and it looks like a very cool solution…past my bedtime, mistakes can be made…I’ll pick this up tomorrow.

Thank you for your help.

That shouldn’t happen regardless of drivers.
Might be an issue with the SDR / USB extension / voltage.

Just run the package install method in the guide and install dump1090-fa after that.
I’m … experienced but when it comes to installing libraries without a package, that’s painful to undo.
Just do the other thing and it should be fine.

That’s old.
What base system is this anyhow?

cat /etc/os-release

If you have a Raspbian bookworm, might be that the rtl-sdr library actually support v4 without having to install the other driver. But maybe that will be the next version i’m not sure.

8.2~bpo9+1
~bpo9 = backport debian 9
debian 9 = Stretch

Below is screenshot from file piaware_builder/sensible-build.sh at https://github.com/flightaware/piaware_builder/

 

Good morning boys,

Thank you again for the help…as requested.

admin@MQTTraspberrypi:~ $ cat /proc/version
Linux version 6.12.25+rpt-rpi-v8 (serge@raspberrypi.com) (aarch64-linux-gnu-gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT Debian 1:6.12.25-1+rpt1 (2025-04-30)

How should I proceed given this current state of affairs?

Cheers

You have given output of wrong command.
@wiedehopf has requested output of following command

Please also post output of following command

lsb_release -a

 

Appologies, here is the result…

admin@MQTTraspberrypi:~ $ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

and…

admin@MQTTraspberrypi:~ $ lsb_release -a  
No LSB modules are available.
Distributor ID:	Debian
Description:	Debian GNU/Linux 12 (bookworm)
Release:	12
Codename:	bookworm

Thank you.

Please upgrade your dump1090-fa to latest ver 10.0.1.
Your current idump1090-fa is too old (ver 8.2), and it is for wrong version of OS, i.e. for Stretch, while your OS is Bookworm.

Please use following commands to upgrade dump1090-fa:

wget https://www.flightaware.com/adsb/piaware/files/packages/pool/piaware/f/flightaware-apt-repository/flightaware-apt-repository_1.2_all.deb
sudo dpkg -i flightaware-apt-repository_1.2_all.deb

Update your apt package sources and install dump1090-fa. This will install all the required dependencies on your Raspberry Pi.

sudo apt update
sudo apt install dump1090-fa 

IMPORTANT: After installing dump1090-fa, reboot Pi
sudo reboot

 

DETAILED INSTRUCTIONS ARE HERE:
https://www.flightaware.com/adsb/piaware/install

1 Like

Okay, progress! We are back to where we were yesterday morning, everything seems to be working but no dump data.

admin@MQTTraspberrypi:~ $ sudo piaware-status
PiAware master process (piaware) is running with pid 1110.
PiAware ADS-B client (faup1090) is running with pid 1286.
PiAware ADS-B UAT client (faup978) is not running (disabled by configuration settings)
PiAware mlat client (fa-mlat-client) is running with pid 5717.
Local ADS-B receiver (dump1090-fa) is running with pid 764.

dump1090-fa (pid 764) is listening for ES connections on port 30005.
faup1090 is connected to the ADS-B receiver.
piaware is connected to FlightAware.

dump1090 is NOT producing data on localhost:30005.

I’ll keep researching to try and find the answer.

Thank you

I’m out of posts for a new user…adding on here…

It seems dump1090 didn’t update…it’s still dump1090-fa 8.2~bpo9+1

here’s the result of journalctl -u dump1090-fa

dump1090-fa.service: Scheduled restart job, restart counter is at 6.
May 22 11:10:46 MQTTraspberrypi systemd[1]: Stopped dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
May 22 11:10:46 MQTTraspberrypi systemd[1]: Started dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization).
May 22 11:10:46 MQTTraspberrypi dump1090-fa[10091]: Thu May 22 11:10:46 2025 PDT  dump1090-fa 8.2~bpo9+1 starting up.
May 22 11:10:46 MQTTraspberrypi dump1090-fa[10091]: rtlsdr: no supported devices found.
May 22 11:10:46 MQTTraspberrypi systemd[1]: dump1090-fa.service: Main process exited, code=exited, status=1/FAILURE
May 22 11:10:46 MQTTraspberrypi systemd[1]: dump1090-fa.service: Failed with result 'exit-code'.

FIXED! And working.

After removing old packages, fix broken packages and installing the RTL drivers per the second method, reinstalling dump1090, and a few other things I can’t recall :zany_face: it’s up and running and producing data live.

Thank you so much everyone for your help, I hope I’ll be able to help someone in my position someday after I learn a LOT more.

Cheers

PS if you want to see my site data it’s

Site 248717 – CYVK – Salmon Valley

1 Like

It’s been up and running all day, just wanted to say thanks again to all who helped, I really appreciate your time.

I’m now researching how to see RSSI on the main screen of Skyaware. I’ll probably post another thread. Being an RF engineer, I like to see this sort of detail. :grinning_face_with_smiling_eyes:

Cheers