No planes being received

I built a PiAware a few weeks back. It was a Raspberry Pi 3 using a FlightAware Pro Stick Plus, connected to an external antenna up on the roof.

All was working well. Was receiving about 100 planes at a time, and about 2000-2500 planes per day.

It was fine for about 10 days but, unknown to me, after that it dropped significantly. Nothing changed. Same Pi. Same antenna. Same SDR.

I used a different Pi, rebuilt the software and tried a different antenna. It is still the same.

I can’t work out what tests I need to run, because there seem to be about 101 differing scripts to run.

FlightAware support told me to run "sudo bash -c “$(wget -nv -O” but it does nothing.

If you are able to SSH connect to your Pi, could you run Sudo piaware-status and share your output conditions?

1 Like

Thank you.

This is the result.

PiAware master process (piaware) is running with pid 489.

PiAware ADS-B client (faup1090) is running with pid 564.

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 480.

dump1090-fa (pid 480) 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 eb6ecb61-6bfe-497a-9b7d-2b19df865e93 (from /var/cache/piaware/feeder_id)

I’ve re-installed dump1090-fa and it’s looking a little bit healthier, but still only one aircraft being received at this moment.

PiAware master process (piaware) is running with pid 489.

PiAware ADS-B client (faup1090) is running with pid 546.

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 480.

dump1090-fa (pid 480) is listening for ES connections on port 30005.

faup1090 is connected to the ADS-B receiver.

piaware is connected to FlightAware.

dump1090 is producing data on localhost:30005.

Your feeder ID is eb6ecb61-6bfe-497a-9b7d-2b19df865e93 (from /var/cache/piaware/feeder_id)

Yes, I now see that the last status shows dump 1090 is producing data.

What is output of following command?

sudo journalctl -u piaware -n 30 | grep msgs

 

The output of above command on my RPi working OK is shown in screenshot below:

Click on Screenshot to See larger Size

Doing it on a phone in bed, so apologies!

But this is the result.

pi@adsb-feeder:~ $ sudo journalctl -u piaware -n 30 | grep msgs
Jul 24 21:29:22 adsb-feeder piaware[493]: 0 msgs recv’d from dump1090-fa; 0 msgs sent to FlightAware
Jul 24 21:34:22 adsb-feeder piaware[493]: 0 msgs recv’d from dump1090-fa (0 in last 5m); 0 msgs sent to FlightAware
Jul 24 21:35:10 adsb-feeder piaware[493]: piaware has successfully sent several msgs to FlightAware!
Jul 24 21:39:22 adsb-feeder piaware[493]: 22 msgs recv’d from dump1090-fa (22 in last 5m); 22 msgs sent to FlightAware
Jul 24 21:44:22 adsb-feeder piaware[493]: 47 msgs recv’d from dump1090-fa (25 in last 5m); 47 msgs sent to FlightAware
Jul 24 21:49:22 adsb-feeder piaware[493]: 75 msgs recv’d from dump1090-fa (28 in last 5m); 75 msgs sent to FlightAware
Jul 24 21:54:22 adsb-feeder piaware[493]: 101 msgs recv’d from dump1090-fa (26 in last 5m); 101 msgs sent to FlightAware
Jul 24 21:59:22 adsb-feeder piaware[493]: 117 msgs recv’d from dump1090-fa (16 in last 5m); 117 msgs sent to FlightAware

Great! Your dump1090-fa and piaware are working OK. Let us see how many aircraft are being sent to FA. The output of following command will show it:

sudo journalctl -u piaware -n 60 | grep Aircraft

 

Screenshot below shows output of above command on my RPi which is working OK:

Click on Screenshot to See Larger Size

1 Like

Check dump1090-fa has set your dongle’s gain to what value by following command:

sudo journalctl -u dump1090-fa -n 10 | grep dB

 

Above command shows that gain is set to 58.6 dB on my system

Click on Screen Shot to See Larger Size

 

Wild ass guess, Antenna / cable problems. The Pi and associated hardware are working.

Pull up the FlightAware page for your system. Recall how the coverage graph on your main page looked before the signal strength dropped. If you touch the “Show position distribution for:” box at the top of the coverage graph you can select a different day on the drop down calendar. Select July 5th or earlier, there you can see you were receiving signals are received in the 150-200 mile range. Sometime on the 6th, your range dropped into the first zone, like the antenna or cable or the connection between the two developed a problem. Look for water damage at the cable connection as that is the most vulnerable point. Make sure the cable connection is tight. Maybe a storm and winds wiggled something. Water in the cable causes the signals to degrade. Could even be some critter decided to taste your cable insulation for their dinner. Do you have an different cable you can connect? even a shorter one with the dongle and raspberry pi hanging in the non-rain wind. Diagnosing problems like we see often is best solved by replacing cables or other parts one at a time and seeing what happens.

You install Graphs1090 as those will show you how the software and hardware from the dongle and Pi are processing data. Super useful diagnostic tool: Graphs for dump1090 -- my version with install script

Have some fun working out what is happening and might be handy to get the whole system down to your workbench so you can put the antenna near a window and sit next to your computer and see how things are working while you swap parts around. Best wishes and welcome to a fun hobby.

This doesn’t look good.

pi@adsb-feeder:~ $ sudo journalctl -u piaware -n 60 | grep aircraft

Jul 25 03:33:52 adsb-feeder piaware[493]: no new messages received in 3890 seconds, it might just be that there haven’t been any aircraft nearby but I’m going to try to restart everything, just in case…

pi@adsb-feeder:~ $ sudo journalctl -u dump1090-fa -n 10 | grep dB

Jul 25 03:35:45 adsb-feeder dump1090-fa[7262]: adaptive: available dynamic range (45.0dB) >= required dynamic range (30.0dB), continuing upward scan

Jul 25 03:35:45 adsb-feeder dump1090-fa[7262]: adaptive: changing gain from 44.dB (step 26) to 48.0dB (step 27) because: probing dynamic range gain upper bound

Jul 25 03:35:45 adsb-feeder dump1090-fa[7262]: rtlsdr: tuner gain set to 48.0 d (gain step 27)

Jul 25 03:35:55 adsb-feeder dump1090-fa[7262]: adaptive: available dynamic range (45.0dB) >= required dynamic range (30.0dB), continuing upward scan

Jul 25 03:35:55 adsb-feeder dump1090-fa[7262]: adaptive: changing gain from 48.dB (step 27) to 49.6dB (step 28) because: probing dynamic range gain upper bound

Jul 25 03:35:55 adsb-feeder dump1090-fa[7262]: rtlsdr: tuner gain set to 49.6 d (gain step 28)

Jul 25 03:36:05 adsb-feeder dump1090-fa[7262]: adaptive: available dynamic range (45.0dB) >= required dynamic range (30.0dB), continuing upward scan

Jul 25 03:36:05 adsb-feeder dump1090-fa[7262]: adaptive: changing gain from 49.dB (step 28) to 58.6dB (step 29) because: probing dynamic range gain upper bound

Jul 25 03:36:05 adsb-feeder dump1090-fa[7262]: rtlsdr: tuner gain set to about 58.6 dB (gain step 29) (tuner AGC enabled)

I would venture to say @astrodeveloper is on it. I highly doubt it is a software issue after looking at the graph you posted where there was a sudden drop off with data while data, although in miniscule amounts, is still being sent over time. Check your antenna connections as astrodeveloper recommended and remove any LNAs or filters which may be in place and see if things improve. I have had many an LNA/adapter/splitter/filter up and go resulting in little even no data being received. Don’t be afraid to substitute a lesser antenna directly connected to your SDR such as those you generally receive with a SDR to make sure that is not the problem as well. If you have a spare RTL-SDR on hand do not be afraid to try that as well.

1 Like

Have ordered a cheap ADSB antenna so I can check it out. Will find out tomorrow.

Stay tuned!

3 Likes

Your partner is complaining, I hope :crossed_fingers:

Right, new antenna arrived, albeit it only one of the little ones that sometimes come free with SDRs.

Using a new, high power plug/cable to ensure it’s getting all the power it needs.

Took the Pi into the garden.

Fired it up. No different…

I am tempted to replace the SDR, but it’s a lot to spend if it’s not the problem!

Did you try re-imaging your microSD card with latest piaware image? It will not cost you anything. If this does not solve the problem, and you have a spare microSD card, write piaware image on it & try it.

I have just tried a fresh install of ADSB.im as I have used this before ok as well.

If that doesn’t work, I should have a spare SD card somewhere…

The reception is just bad, the software is likely working fine.

I’m convinced it’s more than just a faulty antenna/reception.

We shall see…