I have looked through the previous posts on this topic and have not found a solution.
When running ‘sudo piaware-status’ I often will see that the output will cycle between “dump1090 is NOT producing data on localhost:30005” and “dump1090 is producing data on localhost:30005”.
Installed (and reinstalled a few times, so maybe not corrupted/broken software) Raspbian Buster and PiAware (Debian Package Add-on) 6.1. Feeder mode: Mode-S (1090 MHz).
FlightAware Pro Stick Plus with FlightAware 1090Mhz antenna.
Pi Model 3B+ V1.3; Revision: a020d3; SoC: BCM2837; RAM: 1GB
I can see that the USB is connected well and there is no under-voltage issue (also using the official RaspberryPi power adapter for the board).
I am also running a FR24 receiver configured as ‘ModeS Beast’ with host IP 127.0.0.1:300005. This is to avoid dump1090-mutability v1.14 conflict with FlightAware’s dump1090-fa.
If dongle is OK then other possibility is intermittent connection between antenna & dongle. This can br due to coax connector is broken or the coax itself is broken from inside.
If you have an indoor antenna like the one shown in the post linked below, you can disconnect your regular antenna’s coax from the ProStick and connect this indoor mag mount antenna and run your setup for few days to see if intermittent behaviour stays or is gone
I have tried with 4 different cables and I have bought 4 different antennas (2 with built-in cables) thinking that these were problems. All to the same effect. Reaching out to this forum was kind of my last-ditch attempt. I am not sure if this is a FA problem as I can’t really tell from the FR24 “sudo service fr24feed status” output as it does not show the dump1090 status.
This can be normal if you are in a very low-traffic area. The piaware-status test is, essentially “did port 30005 produce some data within N seconds”, which is usually fine in most cases but if you have almost no traffic and can have periods where dump1090 is legitimately not producing data because there’s nothing to decode, then you’ll see this type of behaviour.
Please see “Scan 3 of 3” below which shows how adding a Filter Between Antenna and Receiver eliminates unwanted RF signals picked by Antenna. Scans done as described in the Guide linked below:
The scan 1 shows RF noise picked by antenna and processed without any filter , The scans 2 & 3 were done with filters, and show how filters remove this noise.
Scan 1 of 3 - FA Antenna + Generic DVB-T (no internal or external filter)
I had to change the location of my setup on November 29th. But this issue was the same at the original location too (and where I started swapping out hardware and cables).
Interesting! I thought we did not have to use the external filter with the Pro Stick Plus. I used the external filter with the orange Pro Stick and have just added this to the Pro Stick Plus now. Let see how.
There was a change in location on Nov 29th where the LoS is not as fantastic as before. But this issue was evident even at the old location too. Based on some of the advice received I have now added the external filter to the Pro Stick Plus. Let’s see how this helps. Thanks!
FWIW I am actually just a few km away from you, also with a poor LoS, and I do get gaps where there’s just nothing visible (especially if the RSAF is taking a break). Don’t need a filter on a PS+ here, but it’s possible you have a noisier environment than I do.
Thanks! I think the best explanation is that this status output is not caused by software/configuration or physical setup errors, but just the plain fact that there is no data being received.
It’s not necessary all the time, only in case of some interferences close to you.
In one of me previous setups i had the blue ProPlus Stick. Attaching the dedicated dark blue FA filter did not change anything in reception.
But i am living in an area without significant interferences
