Guide to install PiAware on Raspberry Pi 4

What sdcard image are you using? Have you tried the piaware sdcard image?

If you’re using the piaware sdcard image, what problems do you see?

If you’re not using the piaware sdcard image, what image are you using, what instructions did you follow, and what problems do you see?

Hi,
I’m starting with Raspberry pi 4 and, looking at the Raspberry Pi OS – Raspberry Pi I realized that the raspbian buster is not there anymore. How to install the piaware and dump1090-fa within this new “Raspbian OS Desktop” , not Buster ?

Thanks in advanced

It’s the same they just changed the names.
Also you really don’t need the desktop version because you don’t need a monitor / keyboard.
The lite version is what i would recommend but then i don’t know what else you want to do with the RPi.

There are multiple guides available …

The piaware image obviously is its own image and you don’t get a Desktop.
Using Raspbian OS Desktop as a base will work fine though for abcd567’s guide and my guide as well.

1 Like

Thanks wiedehopf,
I’ve already prepared the sd card with the Raspbian OS Desktop" and, it’s expected that my Raspberry Pi arrives next monday. So, I’ll make a trial according your advises.
I’ll give news about.
Thanks again!

Hi,
My Raspberry arrived early, yesterday, and I’ve installed dump1090-fa and piaware 4.0.
Everything seems to be OK but “dump1090 is NOT producing data on localhost:30005”.
It works on Ubuntu (PC). It’s not a antena issue, I supose.
My flightware site shows everything red and says I’m running Piaware 3.8.1.

Any clue ?

You have two sites now, did you copy the feeder id?

1 Like

No. How to retrive it?

It is on the website, where you see your first feeder, the one that is offline. How you add it the new install depends on whether you installed the image or an add-on. Surely @abcd567 has written a tutorial about this somewhere here :slight_smile:

1 Like

Yes, I realized the problem is I have a new feeder-id for my Raspberry and my Flightware site shows my feeder-id from ubuntu installation. How to add a new station id ?

If you want to keep the new station, just click on the orange bar on the website, and you can chose between both stations. The older station will be deleted after a while

You’re not being very detailed, where are you observing that?

In case you’re seeing that on the local map at /dump1090-fa check the following:
Do you have the SDR connected?
Check the log for dump1090-fa:
Debug commands · wiedehopf/adsb-wiki Wiki · GitHub

Get it working locally you can always worry about feeding after that.

@vsqz44
For your PI4, you can either use an existing Station Number & feeder ID or claim a new Station Number & feeder ID.

@wiedehopf and @abcd567

After this feeder-id replacement, I got that:

pi@raspberrypi:~ $ systemctl status dump1090-fa
● dump1090-fa.service - dump1090 ADS-B receiver (FlightAware customization)
Loaded: loaded (/lib/systemd/system/dump1090-fa.service; enabled; vendor pres
Active: activating (auto-restart) (Result: exit-code) since Sun 2021-03-07 09
Docs: PiAware - ADS-B and MLAT Receiver - FlightAware
Process: 2891 ExecStart=/usr/share/dump1090-fa/start-dump1090-fa --write-json
Main PID: 2891 (code=exited, status=1/FAILURE)

sudo piaware-status
PiAware master process (piaware) is running with pid 3747.
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.

Your feeder ID is xxxxxxxxxxxx (configured at /etc/piaware.conf:7)

But, everything is working within Radarbox24. So, dump1090-fa is OK.

No … probably you misconfigured rb-feeder.
It needs to be in network mode otherwise it’s gonna hog the SDR.
Might also be fr24feed if you have that configured wrong.

Anyhow you didn’t show the output of the log but used the status command so it’s impossible to know why dump1090-fa failed to run properly.
See the command i linked to check the log.

1 Like

It is obvious to me:
The most likely reason (other than a wrong or faulty dongle) is that the dongle is not available for the dump1090-fa as it is being used either by RB24 or FR24 feeders. These two 24’s have merged feeder with decoder, and as a result created nuisance for a novice trying to feed multiple sites.

2 Likes

After 10 minutes disconected from power, I got this:

sudo piaware-status
PiAware master process (piaware) is running with pid 595.
PiAware ADS-B client (faup1090) is running with pid 656.
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-fa) is running with pid 493.

dump1090-fa (pid 493) 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 xxxxxxxxxxxxxxxxxxxxx
I have now the new feeder-id but, still NOT producing data

sudo journalctl --no-pager -u dump1090-fa
– Logs begin at Sun 2021-03-07 09:54:05 -03, end at Sun 2021-03-07 10:25:07 -03. –
Mar 07 09:54:09 raspberrypi systemd[1]: Started dump1090 ADS-B receiver (FlightAware customization).
Mar 07 09:54:10 raspberrypi dump1090-fa[493]: Sun Mar 7 09:54:10 2021 -03 dump1090-fa 4.0 starting up.
Mar 07 09:54:10 raspberrypi dump1090-fa[493]: rtlsdr: using device #0: Generic RTL2832U (Realtek, RTL2832U, SN 00001000)
Mar 07 09:54:10 raspberrypi dump1090-fa[493]: Detached kernel driver
Mar 07 09:54:10 raspberrypi dump1090-fa[493]: Found Rafael Micro R820T tuner
Mar 07 09:54:11 raspberrypi dump1090-fa[493]: rtlsdr: enabling tuner AGC
Mar 07 09:54:11 raspberrypi dump1090-fa[493]: Allocating 4 z

Now I’m getting planes on the map !! But, on my site remains the old feeder-id and, therefore, everything red.

Log-in to your Flightaware account, go to this page and follow instructions to claim the new station with new feede id you already got: https://flightaware.com/adsb/piaware/claim