I followed instructions to install dump1090-fa & piaware but nothing doesn't feel to work properly

Hello. Sorry for disturbing you. This is my first time, second try, to install and use ADS-B setup @abcd567

I tried to install dump1090 using these instructions: ADS-B dump1090 and tried to install piaware, but those didn’t work, I searched and found that these doesn’t support my CPU architecture, which is x86_64.

So I purged everything and started over and used this site instead: GitHub - abcd567a/debian11 Everything worked actually fine and I actually could install everything without errors.

Did I do something wrong when I followed the instructions from the first link to the point where I have to blacklist rtl28xxu and do the rt_test -t and then do the things in the second link? I’ve read that if there is to different dump1090 installations it will screw up the dump1090.

I followed the instructions in the second link but didn’t do anytrhing after “For USA only - dump978-fa”.

Should I fix this spiderweb of problems or just purge whole HDD and start over again and follow some spesific instructuins or what? I’ve basically already searched lot of websites to fix probles like how to create Makefile because it was missing and something was in wrong directory etc.

I’ve execute these commands and they are in Terminal when I’m writing this:
sudo systemctl status dump1090-fa
sudo lsusb
sudo journalctl -u dump1090-fa
if you want the results, I copy them for you

I just want working dump1090-fa & piaware ADS-B setup and I am thankful for creating the package that supports amd64 / x86_64 architecture.

I don’t want to make very long post so ask if you need to know something.I hope you can help me. Thanks.

If on the first site (ADS-B dump1090) you did NOT execute instructions quoted below, then you did NOT install dump1090 Malcolm Robb. In this case do not worry, you have piaware & dump1090-fa packages installed only from second site (GitHub - abcd567a/debian11). You do NOT have to purge whole HDD and start over again.

Please post output of following commands:

uname -m

lsb_release -a 

sudo journalctl -u dump1090-fa -n 15

sudo journalctl -u piaware -n 20

 

Please confirm that you did NOT execute these steps given on the first site.

 

Thanks for fast reply.

uname -m: x86_64
lsb_release -a: No LSB modules are available.
Distributor ID: Debian
Description: Debian GNU/Linux 11 (bullseye)
Release: 11
Codename: bullseye
sudo journalctl -u dump1090-fa -n 15:
– Journal begins at Sun 2022-03-20 21:55:27 EET, ends Sun 2025-04-13 20:10:19 EEST. –
Apr 13 17:15:57 raspberry dump1090-fa[598]: adaptive: available dynamic range (35.9dB) >= required dynamic range (30.0dB), stopping downwards scan here
Apr 13 18:15:57 raspberry dump1090-fa[598]: adaptive: start periodic scan for accetable dynamic range at increased gain
Apr 13 18:15:57 raspberry dump1090-fa[598]: adaptive: changing gain from 49.6dB (step 28) to 58.6dB (step 29) because: periodic re-probing of dynamic range gain upper bound
Apr 13 17:15:57 raspberry dump1090-fa[598]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)
Apr 13 18:16:07 raspberry dump1090-fa[598]: adaptive: available dynamic range (25.9dB) < required dynamic range (30.0dB), switching to downward scan
Apr 13 18:16:07 raspberry dump1090-fa[598]: adaptive: changing gain from 58.6dB (step 29) to 49.6dB (step 28) because: probing dynamic range gainlower bound
Apr 13 18:16:07 raspberry dump1090-fa[598]: rtlsdr: tuner gain set to 49.6dB (gain step 28)
Apr 13 18:16:17 raspberry dump1090-fa[598]: adaptive: available dynamic range (35.9dB) >= required dynamic range (30.0dB), stopping downwards scan here
Apr 13 19:16:17 raspberry dump1090-fa[598]: adaptive: start periodic scan for accetable dynamic range at increased gain
(and the same thing again as I just wrote)

Apr 10 16:40:39 raspberry piware[1046]: 2775 msgs recv’d from dump1090-fa (174 in last 5m); 2775 msgs sent to FlightAware
Apr 10 16:45:39 raspberry piware[1046]: 3025 msgs recv’d from dump1090-fa (250 in last 5m); 3025 msgs sent to FlightAware
Apr 10 16:50:39 raspberry piware[1046]: 3257 msgs recv’d from dump1090-fa (232 in last 5m); 3257 msgs sent to FlightAware
Apr 10 16:55:39 raspberry piware[1046]: 3452 msgs recv’d from dump1090-fa ( in last 5m); 3452 msgs sent to FlightAware
Apr 10 17:00:39 raspberry piware[1046]: 3634 msgs recv’d from dump1090-fa (182 in last 5m); 3634 msgs sent to FlightAware
Apr 10 17:05:39 raspberry piware[1046]: 3786 msgs recv’d from dump1090-fa (152 in last 5m); 3786 msgs sent to FlightAware
Apr 10 17:08:21 raspberry piware[1046]: lost connection to dump1090-fa via faup1090
Apr 10 17:08:21 raspberry piware[1046]: faup1090 exited normally
Apr 10 17:08:21 raspberry piware[1046]: reconnectig to dump1090-fa
Apr 10 17:08:21 raspberry sudo[2451]: piaware : PWD=/ ; USER=root ; COMMAND=/bin/netstat --program --tcp --wide --all --numeric
Apr 10 17:08:22 raspberry sudo[2451]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=999)
Apr 10 17:08:22 raspberry sudo[2451]: pam_unix(sudo:session): session opened for user root
Apr 10 17:08:22 raspberry piaware[2451]: no ADS-B data program seen listening on port 30005 for 1 seconds, next check in 60s
Apr 10 17:08:30 raspberry piaware[2451]: piaware (process 1046) is shutting down because it received a shutdown signal (SIGTERM) from the system…
Apr 10 17:08:30 raspberry piaware[2451]: removing pidfile /run/piaware/piaware.pid
Apr 10 17:08:30 raspberry piaware[2451]: piaware (process 1046) is exiting…
Apr 10 17:08:30 raspberry systemd[1]: Stopping FlightAware ADS-B uploader…
Apr 10 17:08:22 raspberry systemd[1]: piaware.service: Succeeded.
Apr 10 17:08:22 raspberry systemd[1]: Stopped FlightAware ADS-B uploader.
Apr 10 17:08:22 raspberry systemd[1]: piaware.service: Consumed 7.352s CPU time.
If I understand right, my piaware/FlightAware is turned off, I feel so stupid now.

Yes, I did NOT execute those steps given in the first link.

I face similar issue when I install dump1090-fa on Debian running in Virtual Machine in Windows computer. Are you using Virtual Machine?

If you are not using Virtual Machine, and your Debian is directly installed on HDD, then this intermittent behavior is possibly because the dongle is not firmly inserted into USB port, or the dongle is flaky. Try to plug the dongle in another USB port of your computer.

Hey, I tested to fit the dongle to different USB port and restarted piaware and it worked! And yes I didn’t use Virtual Machine. But thank you for helping me and thank you from the amd64/x86_64 package in github, I appreciate that.

2 Likes