Hello Group
Originally I installed PiAware over 2 year ago on top of Raspian along with various other clients like FR24 etc, until this latest V4 I always updated PiAware from “My ADSB” with no issues but when I try now I get a message back saying it can’t update due to broken packages.
I’ve been in touch with Tech support and they advise starting from scratch and flash the with PIAware then re register and request my old data to be included alternatively contact this group,
So hopefully fingers crossed 
someone can offer a better way rather than have to re-install all the other clients which at this point I don’t know how to go about it without Raspian .
Best Regards
Paul
What are the exact errors you see when trying to upgrade?
Hi Thanks for your reply, see copied message below.
Feeder Type: PiAware (Debian Package Add-on) 3.8.0
Feeder Mode: Mode-S (1090 MHz)
Multilateration (MLAT): Supported / Enabled (synchronized with 562 nearby receivers)
[2020-11-03 09:11 GMT] run-apt-get(13062): 0 upgraded, 0 newly installed, 0 to remove and 344 not upgraded.
[2020-11-03 09:11 GMT] run-apt-get(13062): Reading state information…
[2020-11-03 09:11 GMT] run-apt-get(13062): Building dependency tree…
[2020-11-03 09:11 GMT] run-apt-get(13062): The following information may help to resolve the situation:
[2020-11-03 09:11 GMT] run-apt-get(13062): requested an impossible situation or if you are using the unstable
[2020-11-03 09:11 GMT] run-apt-get(13062): distribution that some required packages have not yet been created
[2020-11-03 09:11 GMT] run-apt-get(13062): The following packages have unmet dependencies:
[2020-11-03 09:11 GMT] update request complete
[2020-11-03 09:11 GMT] run-apt-get(13062): piaware : Depends: tcl-tls (>= 1.7.16-1+fa1~bpo8) but 1.6.7+dfsg-1.2 is to be installed
[2020-11-03 09:11 GMT] aborting upgrade…
[2020-11-03 09:11 GMT] run-apt-get(13062): E: Unable to correct problems, you have held broken packages.
[2020-11-03 09:11 GMT] mlat-client(10941): Server: 0.1 kB/s from server 0.0kB/s TCP to server 0.9kB/s UDP to server
[2020-11-03 09:11 GMT] mlat-client(10941): Receiver status: connected
[2020-11-03 09:11 GMT] mlat-client(10941): Aircraft: 8 of 19 Mode S, 25 of 25 ADS-B used
[2020-11-03 09:11 GMT] mlat-client(10941): Server status: synchronized with 567 nearby receivers
[2020-11-03 09:11 GMT] 118563 msgs recv’d from dump1090-fa (817 in last 5m); 118563 msgs sent to FlightAware
@Mancpaul
It is not difficult to start from scratch and make a fresh install of Raspbian & all feeders. Use a spare microSD card to make the fresh install, leaving your existing installation intact.
Plesse follow the guide below:
1 - Download and write Raspberry Pi OS (32-bit) Lite image on a microSD card.
https://downloads.raspberrypi.org/raspios_lite_armhf_latest
2 - Enable SSH & WiFi
While the microSD card is still in the card reader of your Laptop/Desktop, in File Explorer (Windows) or Finder (Mac) click on drive letter of the microSD card (labelled boot) to open it. It will open folder /boot which has many files & few folders.
2.1 - SSH
In the folder /boot , create a new text file and name it ssh
For further details, please see "For Beginners - How-to SSH to RPi - Setup Putty in Windows”
For Raspberry Pi OS
username = pi
default password = raspberry
.
2.2 - WiFi (only if required)
Raspbian Image - Howto Enable & Configure WiFi Before First Boot
3 - Slip microSD card in RPi and Power up.
4 - Install piaware and dump1090-fa
wget https://flightaware.com/adsb/piaware/files/packages/pool/piaware/p/piaware-support/piaware-repository_4.0_all.deb
sudo dpkg -i piaware-repository_4.0_all.deb
sudo apt-get update
sudo apt-get install piaware
sudo piaware-config allow-auto-updates yes
sudo piaware-config allow-manual-updates yes
sudo apt-get install dump1090-fa
sudo reboot
5 - Configure Station ID
Alternative-1:
Get a brand new station number & feeder id
Log-in to your Flightaware account, go to this page and follow instructions to claim a new station https://flightaware.com/adsb/piaware/claim
Alternative-2:
Configure an Existing Station
(a) - Find existing station’s feeder-id (Unique Identifier)
Log-in to your Flightaware account, go to “My ADSB” / stats page
flightaware.com/adsb/stats/user/ ,
and look for 32-digit Unique Identifier: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (shown inside red rectangle in the screenshot below)
.
(b) - SSH and configure station id:
sudo piaware-config feeder-id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
# Replace xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
# by your actual feeder-id
sudo systemctl restart piaware
5- Install FR24 feeder
5.1 - Retrieve your existing fr24 key
Go to page https://www.flightradar24.com and login to your account
After login, go to your stats page. On stats page you will find your fr24 key. Copy the key and paste in Notepad and save the Notepad.
See screenshots below.
Screenshot 1 of 2
Screenshot 2 of 2
5.2 - Install fr24feed
Give following command
sudo bash -c "$(wget -O - https://repo-feed.flightradar24.com/install_fr24_rpi.sh)"
The above command will run installation for some time, then automatically start signup process. The signup process will halt and ask for email address.
Case 1:
If you do not have a fr24 sharing key, or want a brand new key, continue inputting your email and other details. A new key will be generated and saved in file /etc/fr24feed.ini . FR24 will also send this key to you by email for your records.
Case 2:
If you already have a key, then do not enter any details. Instead break the siugnup process by pressing Ctrl and C keys together. This will result in display of ^C and command prompt "pi@piaware:~ $" . Please see screenshot below.
5.3 - Configure FR24
Give following command
sudo nano /etc/fr24feed.ini
Above command will open the config file. It will have following text
bs=yes
raw=yes
mlat="yes"
mlat-without-gps="yes"
(5.3.1) Delete all above lines by:
- bring cursor to the top line
- keep pressed Ctrl key and repeatedly press K key till the file becomes blank.
(5.3.2) Copy paste following in this file (replace "xxxxxxxxxxxxxxx" by the key you have copied from your stats page).
receiver="beast-tcp"
fr24key="xxxxxxxxxxxxxxx"
host="127.0.0.1:30005"
bs="no"
raw="no"
logmode="1"
logpath="/var/log/fr24feed"
mlat="yes"
mlat-without-gps="yes"
(5.3.3) Save file (Ctrl+o) and Close (Ctrl+x).
(5.3.4) Restart FR24 feeder
sudo systemctl restart fr24feed
(5.3.5) Check status:
fr24feed-status
[ ok ] FR24 Feeder/Decoder Process: running.
[ ok ] FR24 Stats Timestamp: 2020-03-14 06:15:24.
[ ok ] FR24 Link: connected [UDP].
[ ok ] FR24 Radar: T-CYYZ9.
[ ok ] FR24 Tracked AC: 1.
[ ok ] Receiver: connected (4 MSGS/0 SYNC).
[ ok ] FR24 MLAT: ok [UDP].
[ ok ] FR24 MLAT AC seen: 1.
(5.3.6) Check status in browser on following address:
ip-of-pi:8754
NOTE
If you want a new key at any time after installation, you can signup again by following command. Complete signup and obtain a new key, which will automatically be saved in config file /etc/fr24feed.ini as well as sent to you by email.
sudo fr24feed --signup
CAUTION:
Never use FR24 setting receiver="dvbt" .
This setting will install dump1090-mutability ver 1.14, which will conflict/compete for dongle with dump1090-fa, and result in a mess
6 - Install Planefinder feeder
6.1 - Issue following commands
wget http://client.planefinder.net/pfclient_4.1.1_armhf.deb
sudo dpkg -i pfclient_4.1.1_armhf.deb
6.2 To recover Planefinder sharecode from existing microSD card
(This step to be done before shutting down Pi and removing/reimaging existing microSD card)
cat /etc/pfclient-config.json
Above command will output following long line of code. The sharecode is the last item in this line. Copy-pate it in a text file and save the file
{“tcp_address”:“127.0.0.1”,“tcp_port”:“30005”,“select_timeout”:“10”,“data_upload_interval”:“10”,“connection_type”:“1”,“aircraft_timeout”:“30”,“data_format”:“1”,“latitude”:“xx.xxxx”,“longitude”:“yy.yyyy”,“sharecode”:“zzzzzzzzzzzzz”}
6.3 - Go to page IP-of-PI:30053 to complete configuration
7- Install RadarBox24 feeder
sudo bash -c "$(wget -O - http://apt.rb24.com/inst_rbfeeder.sh)"
sudo rbfeeder --setkey xxxxxxxxxx --no-start
## Replace xxxxx by your actual key
## Press Ctrl+C to break log output.
sudo systemctl restart rbfeeder
8 - Graphs by Wiedehopf
sudo bash -c "$(wget -q -O - https://raw.githubusercontent.com/wiedehopf/graphs1090/master/install.sh)"
This generally means that there is a problem with the repository config.
What is the output of
ls /etc/apt/sources.list.d/
dpkg -l 'piaware*'
apt-cache policy piaware-repository
apt-cache policy piaware
apt-cache policy tcl-tls
cat /etc/os-release
Thanks again for your help.
pi@raspberrypi:~ ls /etc/apt/sources.list.d/
piaware.list raspi.list rb24.list teamviewer.list
pi@raspberrypi:~
pi@raspberrypi:~ dpkg -l 'piaware*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-===============================-====================-====================-====================================================================
ii piaware 3.8.0~bpo8+1 armhf Open Aviation Data Exchange Protocol for ADS-B FlightFeeders
ii piaware-repository 3.5.3 all Installs the PiAware apt repository configuration.
pi@raspberrypi:~
pi@raspberrypi:~ apt-cache policy piaware-repository
piaware-repository:
Installed: 3.5.3
Candidate: 4.0~bpo8+1
Version table:
4.0~bpo8+1 500
500 http://flightaware.com/adsb/piaware/files/packages jessie/piaware armhf Packages
*** 3.5.3 100
100 /var/lib/dpkg/status
pi@raspberrypi:~
pi@raspberrypi:~ apt-cache policy piaware
piaware:
Installed: 3.8.0~bpo8+1
Candidate: 4.0~bpo8+1
Version table:
4.0~bpo8+1 500
500 http://flightaware.com/adsb/piaware/files/packages jessie/piaware armhf Packages
*** 3.8.0~bpo8+1 100
100 /var/lib/dpkg/status
pi@raspberrypi:~
pi@raspberrypi:~ $ apt-cache policy tcl-tls
Ok. And the output from the last two commands?
(I would suggest reimaging anyway. You appear to have an install that is based on the jessie version of Raspbian. Upstream Debian stopped supporting this version in June)
1 Like
Thanks guys 
Looking like i’ll have do a new install especially after reading last message about debian no longer supported.
abcd567 your instructions are brilliant cheers, should make things a lot easier for me.
Best regards
Paul
2 Likes