How to install piaware on a Raspberry running pi24-2.3.1.img

(1) Remove half-installed piaware

sudo apt --fix-broken install  

(2) Remove Bullseye repository

sudo rm /etc/apt/sources.list.d/piaware-bullseye.list  

sudo dpkg --purge piaware-repository 

(3) Add Buster repository

wget https://flightaware.com/adsb/piaware/files/packages/pool/piaware/p/piaware-support/piaware-repository_7.2~bpo10+1_all.deb   

sudo dpkg -i piaware-repository_7.2~bpo10+1_all.deb

(4) Install piaware

sudo apt update   

sudo apt install piaware  

(5) Claim piaware If you already dont have an existing feeder ID

https://flightaware.com/adsb/piaware/claim

If you already have a feeder ID, do NOT claim as above. Instead configure piaware with it by following command
(Replace xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx by you actual feeder-d

sudo piaware-config feeder-id xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx  

sudo systemctl restart piaware   

 

Good catch :+1:

 

Hi abcd567

I really appreciate your effort to help us, who primarily feed fr24.
I ran into this message:
wget https://flightware.com/adsb/piaware/files/packages/pool/piaware/p/piaware-support/piaware-repository_7.2~bpo10+1_all.deb

–2022-03-17 18: 12: 06-- https://flightware.com/adsb/piaware/files/packages/pool/piaware/p/piaware-support/piaware-repository_7.2~bpo10+1_all. deb
Resolving flightware.com (flightware.com) … 18.222.0.235
Connecting to flightware.com (flightware.com) | 18.222.0.235 |: 443 … connected.
ERROR: The certificate of ‘flightware.com’ is not trusted.
ERROR: The certificate of ‘flightware.com’ does not have a known issuer.

Does the file piaware-repository_7.2 ~ bpo10+1_all.deb differ from this file I allready had downloaded: piaware-repository_7.2_all.deb?

I only use raspberry to my weatherstation and feeding FR24. Don’t know much about debian, linux and all the other - I know much more about dos and windows!

Regards
Per

Maybee I should change it to flightaware :laughing:

Yes, the bpo10+1 version is for buster, the other one is for bullseye.

Now it looks much better. Maybee there is a little problem with MLAT:

I just have to try to read a bit about MLAT and a possible solution.

You have done an excellent job. Maybe you should make a little guide about these hints - in the same way as your very excellent guides in the FR24 forum

Regards
Per

Step 6 (2)

Nothing changed - MLAT worked fine before:
Screen Shot 03-17-22 at 08.45 PM



But what about this log:

 

The decoder is not working. Reboot RPi and check logs again.

Which decoder have you installed? Please post output of following commands:

apt-cache policy dump1090-fa   

apt-cache policy dump1090-mutability  
   
apt-cache policy readsb

Please also post config of fr24feed as you are using Pi24 image. In Pi24 image, fr24feed controls decoder
(When posting here, replace fr24 key by xxxxx for privacy reasons)

cat /etc/fr24feed.ini  

Decoder not running.
As you started with FR24 check this:

apt-cache policy dump1090-fa:
dump1090-fa:
Installed: (none)
Candidate: 7.2~bpo10+1
Version table:
7.2~bpo10+1 500
500 http://flightaware.com/adsb/piaware/files/packages buster/piaware armhf Packages

apt-cache policy dump1090-mutability :
dump1090-mutability:
Installed: 1.15~20180310.4a16df3+dfsg-6
Candidate: 1.15~20180310.4a16df3+dfsg-6
Version table:
*** 1.15~20180310.4a16df3+dfsg-6 500
500 Index of /raspbian buster/main armhf Packages
100 /var/lib/dpkg/status

apt-cache policy readsb:
N: Unable to locate package readsb

cat /etc/fr24feed.ini:
pi@raspberrypi:~ $ cat /etc/fr24feed.ini
receiver=“dvbt”
fr24key=“xxxxxxxxxxxx”
path=“/usr/lib/fr24/dump1090”
bs=“no”
raw=“no”
logmode=“1”
windowmode=“0”
logpath=“/var/log/fr24feed”
mpx=“no”
mlat=“yes”
mlat-without-gps=“yes”

Not sure - here is the log from :/var/log/fr24feed/fr24feed.log:

@PerLaustsen

OPTION-1

Add this line to file /etc/fr24feed.ini

procargs= " --net " 

Save file, then restart fr24feed

sudo systemctl restart fr24feed  

Now check status of piaware

sudo systemctl status piaware  

OPTION 2 (Preferred and better option)

Step-1
In file /etc/fr24feed.ini, delete following two lines:

receiver="dvbt" 
path="/usr/lib/fr24/dump1090"

Add following two lines

receiver="avr-tcp" 
host="127.0.0.1:30002" 

Save and Close file

Step-2
Issue following command

sudo nano /etc/default/dump1090-mutability

In file opened, scroll down to this line:

START_DUMP1090=“no”

Change no to yes, so the line becomes:

START_DUMP1090=“yes”

Save file.

Step-3
Reboot Pi and after reboot check status.

There is no files of this name in etc directory

Oops… I gave name of Radarbox24 file by mistake.

The correct file name of Flightradsr24 is
/etc/fr24feed.ini

Thanks for the help - it’s running perfectly now, but without your help I would have given up feeding FlightAware.

1 Like

Glad to know your install is working now.

Just curious to know weather you used option-1 or option-2. Although both options solve the problem, they have different strategies.

In Pi24 image, the dump1090-mutability is configured to be controlled by fr24feed, and only fr24feed can get its feed directly, but data availability on network at its ports 30002, 30003, 30005 are blocked. Hence other sites feeding software say dump1090 is not running, although it is running.

In option-1, a line procargs=" --net " is added. This open the dump1090-mutability’s data ports on network, and other sites feeder start getting data from dump1090-mutabity.

In option-2, the lines added (receiver=avr-tcp and host=127.0.0.1:30002), pull out dump1090-mutability from control of fr24feed, and blockage of its ports 30002, 30003, and 30005 is removed. Other sites feeder softwsre now start getting data from it.

There was one more restriction put on dump1090-mutability by fr24feed. It was blocked from starting automatically at boot. It was started by fr24feed when it started. To remove this restriction, in file /etc/default/dump1090-mutability , the setting START_DUMP1090=no was changed from no to yes.

I first tried Option 1, then I decided to try Option 2, and this is my fr24feed.ini file to day:
Screen Shot 03-19-22 at 12.22 PM

Per

1 Like

 

:+1: :+1: :+1:

 

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.