Yes please rerun the install, that way you also get the most current feed client:
https://github.com/adsbxchange/adsb-exchange#ads-b-exchange-setup-scripts-airplane
That is super helpful. Thanks a lot
If it didn’t run the restart commands would they have been automatically restarted anyway when I rebooted my Pi next?
Thanks for the advice. I only installed it a few days ago so its probably current
I have deployed the 7.0 super easy with @abcd567 scripts. In the past I had to re-compile by hand, avoid various pitfals… this was very nice!
Only difference on my system was that I had to release the update for tls. I had held back the updates back manually in previous piaware version. Now it’s all good.
1 Like
Thank you for your feedback.
I understand you are referring to installation of pre-built packages of piaware and dump1090-fa 7.0 on UBUNTU 20 AMD64. Am I right?
1 Like
That’s correct. Those were the prebuilt 7.0 packages on Ubuntu 20 AMD64 platform.
1 Like
Worked flawlessly on both Armbian and Rasberry Pi Bullseye OS’es.
No need to input the feeder key when upgrading from 6.1
Also, some packages can be removed after the upgrade to 7.0, maybe add sudo apt autoremove to the list of instructions to keep the system clean and tidy ?
1 Like
Thank you.
Your observations/recommendations are good, but I want to keep instructions in How-To a bare minimum, simple, and uniform for fresh install & upgrade.
In case of fresh install, feeder-id command is a must. In case of upgrade it is not required, but if issued, it does not do any harm. It simply outputs “feeder-id unchanged”.
The command sudo apt autoremove is useful, but this instruction is displayed by apt after installation of package is done, so it is not necessary to include it in the installation How-to.
2 Likes
Debian 11 amd64
Successfully upgraded to ver 7.0 by installing pre-built packages of piaware, dump1090-fa, dump978-fa, and piaware-web.
Simple. Used command “sudo apt install [package-name]”. Please see following How-To:
Debian 11 amd64 - Package install of ver 7.0 piaware, dump1090-fa, piaware-web, dump978-fa
Debian 11 amd64
Kali Linux 2021 amd64
Successfully upgraded to ver 7.0 by installing pre-built packages of piaware, dump1090-fa, dump978-fa, and piaware-web.
Simple. Used command “sudo apt install [package-name]”. Please see following How-To:
Kali 2021 amd64 - Package install of ver 7.0 piaware, dump1090-fa, piaware-web, dump978-fa
Ubuntu 20.04 amd64
Successfully upgraded to ver 7.0 by installing pre-built packages of piaware, dump1090-fa, dump978-fa, and piaware-web.
Simple. Used command “sudo apt install [package-name]”. Please see following How-To:
Ubuntu 20 amd64 - Package install of ver 7.0 piaware, dump1090-fa, piaware-web, dump978-fa
3 Likes
When I woke up today my feeder was down and I cant work out how to revive it. When I go to the IP of the Pi it shows 1090 radio and MLAT are down, but PiAware and FlightAware are still active. I tried running the install scripts linked from this thread again but it didnt help. Should I uninstall dump1090-fa and reinstall it? What else could help?
what is the output of following command?
journalctl -u dump1090-fa -e
pi@raspberrypi:~ $ journalctl -u dump1090-fa -e
Jan 10 12:29:52 raspberrypi systemd[1]: Started dump1090 ADS-B receiver (Flight>
Jan 10 12:29:52 raspberrypi dump1090-fa[6306]: Mon Jan 10 12:29:52 2022 WET du>
Jan 10 12:29:52 raspberrypi dump1090-fa[6306]: rtlsdr: using device #0: Generic>
Jan 10 12:29:52 raspberrypi dump1090-fa[6306]: Kernel driver is active, or devi>
Jan 10 12:29:52 raspberrypi dump1090-fa[6306]: In the first case, please either>
Jan 10 12:29:52 raspberrypi dump1090-fa[6306]: (dvb_usb_rtl28xxu), or enable au>
Jan 10 12:29:52 raspberrypi dump1090-fa[6306]: usb_claim_interface error -6
Jan 10 12:29:52 raspberrypi dump1090-fa[6306]: rtlsdr: error opening the RTLSDR>
Jan 10 12:29:52 raspberrypi systemd[1]: dump1090-fa.service: Main process exite>
Jan 10 12:29:52 raspberrypi systemd[1]: dump1090-fa.service: Failed with result>
Jan 10 12:30:22 raspberrypi systemd[1]: dump1090-fa.service: Scheduled restart >
Jan 10 12:30:22 raspberrypi systemd[1]: Stopped dump1090 ADS-B receiver (Flight>
Jan 10 12:30:22 raspberrypi systemd[1]: Started dump1090 ADS-B receiver (Flight>
Jan 10 12:30:22 raspberrypi dump1090-fa[6356]: Mon Jan 10 12:30:22 2022 WET du>
Jan 10 12:30:22 raspberrypi dump1090-fa[6356]: rtlsdr: using device #0: Generic>
Jan 10 12:30:22 raspberrypi dump1090-fa[6356]: Kernel driver is active, or devi>
Jan 10 12:30:22 raspberrypi dump1090-fa[6356]: In the first case, please either>
Jan 10 12:30:22 raspberrypi dump1090-fa[6356]: (dvb_usb_rtl28xxu), or enable au>
Jan 10 12:30:22 raspberrypi dump1090-fa[6356]: usb_claim_interface error -6
Jan 10 12:30:22 raspberrypi dump1090-fa[6356]: rtlsdr: error opening the RTLSDR>
Jan 10 12:30:22 raspberrypi systemd[1]: dump1090-fa.service: Main process exite>
Jan 10 12:30:22 raspberrypi systemd[1]: dump1090-fa.service: Failed with result>
lines 980-1001/1001 (END)
The dongle is in use by some other program.
Possibly due to wrong settings of FR24 or RB24. Which other feeders have you installed on this Pi?
1 Like
All of them. FR24, ADSBx, RB24, PF, and attempted PP but hit a wall and didnt get back to it yet.
In an effort eliminate possible causes I finished setting up MLAT on RB24, and I’ve just now completed installing PP but it had an error so Im not sure if it worked completely.
I also just unistalled dump1090-fa, purged, and reinstalled as you wrote in another post in the forum… Didnt seem to help. What to do?
Also, is it normal that such a clash between competing feeders would just appear in the middle of the night after several days of perfect feeding to FA, FR24 and ADSBx?
PiAware status page still says not connected to a Mode S reciever
Give following commands, and post output of last command
sudo apt install rtl-sdr
sudo systemctl stop piaware dump1090-fa
rtl_test -t
Ok, thankyou!
pi@raspberrypi:~ $ sudo apt install rtl-sdr
Reading package lists… Done
Building dependency tree… Done
Reading state information… Done
The following NEW packages will be installed:
rtl-sdr
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 55.1 kB of archives.
After this operation, 187 kB of additional disk space will be used.
Get:1 http://ftp.cica.es/mirrors/Linux/raspbian/raspbian bullseye/main armhf rtl-sdr armhf 0.6.0-3 [55.1 kB]
Fetched 55.1 kB in 1s (70.1 kB/s)
Selecting previously unselected package rtl-sdr.
(Reading database … 181773 files and directories currently installed.)
Preparing to unpack …/rtl-sdr_0.6.0-3_armhf.deb …
Unpacking rtl-sdr (0.6.0-3) …
Setting up rtl-sdr (0.6.0-3) …
Processing triggers for man-db (2.9.4-2) …
pi@raspberrypi:~ $ sudo systemctl stop piaware dump1090-fa
pi@raspberrypi:~ $ rtl_test -t
Found 1 device(s):
0: Realtek, RTL2832U, SN: 00001000
Using device 0: Generic RTL2832U
Kernel driver is active, or device is claimed by second instance of librtlsdr.
In the first case, please either detach or blacklist the kernel module
(dvb_usb_rtl28xxu), or enable automatic detaching at compile time.
usb_claim_interface error -6
Failed to open rtlsdr device #0.
In case it helps, the feeder log says there is no ADSB program listening on port 3005… seems to check every minute