FlightAware Discussions

Piaware message 0 msgs recv'd from dump1090-fa

I have been looking at my system and searching online for information related to this error message.

My setup is a Raspberry Pi Zero W with a Realtek Semiconductor Corp. RTL2838 DVB-T, piaware version 3.8.1

I have checked all possible issues i could think of

  • powersupply, i used 3 different ones, all outputting 5v
  • used multiple cables to make sure it is not a cable issue
  • usb device being recognized using lsusb
  • usb device working at all ( it does produce acarsdec messages without a problem )
  • checked the usb device on another machine (works with laptop and phone)
  • restarted, piaware, reboot etc.
  • restarted faup1090 manually to trigger dump1090-fa
  • fa-mlat-client comes up and get ports assinged
  • ports are listening according to netstat
  • UDP transport to port 14840 is created
  • Using piaware -debug i only see 2 warnings :

2020-05-15 10:56:11Z mlat-client(1796): Warning: Could not create results output ‘beast,listen,30105’: [Errno 98] Address already in use
2020-05-15 10:56:11Z mlat-client(1796): Warning: Could not create results output ‘ext_basestation,listen,30106’: [Errno 98] Address already in use

Eventually the process times out, kicks off a restart of dump1090-fa using faup1090 but the status remains the same.

"2020-05-15 11:01:36Z 0 msgs recv’d from dump1090-fa (0 in last 5m); 0 msgs sent to FlightAware "

pi@piaware:~ $ piaware-status
PiAware master process (piaware) is running with pid 414.
PiAware master process (piaware) is running with pid 1037.
PiAware ADS-B client (faup1090) is running with pid 1442.
PiAware ADS-B client (faup1090) is running with pid 1443.
PiAware ADS-B UAT client (faup978) is not running (disabled by configuration settings)
PiAware mlat client (fa-mlat-client) is running with pid 1259.
PiAware mlat client (fa-mlat-client) is running with pid 1282.
Local ADS-B receiver (dump1090-fa) is running with pid 1410.

dump1090-fa (pid 1410) 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.

Checking the network to be sure ports are available

pi@piaware:~ $ netstat -tulpn
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0* LISTEN -
tcp 0 0* LISTEN -
tcp 0 0* LISTEN -
tcp 0 0* LISTEN -
tcp 0 0* LISTEN -
tcp 0 0* LISTEN -
tcp 0 0* LISTEN -
tcp 0 0* LISTEN -
tcp 0 0* LISTEN -

My knowledge on piaware is minimal yet i think i have excluded most obvious causes like device/network. Setup is completed, lights are green on flightaware but nothing is being send.

I already ordered another dongle to be able to check if the issue is there but this seems more like an application/setup issue to me seeing i can receive other message types and FM radio without a problem.

This issue has been reported by many people which helped me troubleshooting but i am running out of options…perhaps there are things i can check that are missing from the above list, please let me know.

Probably a Fitipower FT0012 or FT0013 tuner.

Those tuners don’t work properly at 1090 MHz, basically zero reception.

Could also be that you have a really bad antenna or extremely strong interference.

1 Like

Yes indeed, it has the Fitipower tuner :frowning:

May 15 08:17:48 piaware dump1090-fa[413]: Found Fitipower FC0012 tuner
May 15 08:17:48 piaware dump1090-fa[413]: rtlsdr: tuner gain set to -9.9 dB
May 15 08:17:48 piaware dump1090-fa[413]: [FC0012] no valid PLL combination found for 1090000000 Hz!

Well, too bad, but at least some closure :wink: Also i feel welcomed by having the answer in the first reply.

So i will use this one for acarsdec or catching radiotraffic and hope to find one that works. At least i know what to check first now. Thanks Wiedehopf!


Use one of the reputable SDRs (beware of knockoffs)
The list above is probably missing some Nooelec SDRs which are proper as well (their antennas are bad beyond belief though).

1 Like

In addition to the tuner issue - I think you have two copies of piaware running somehow.

Hmm yes, i also noticed port busy messages at some point which indicates the same. I guess i was poking around to much to get things working. After a reboot there is just one process now. Thanks for pointing out.

Guess i will go for this a NESDR SMArt v4 RTL-SDR Essentials kit…including 3 crappy antenna’s i guess :wink:

The kit also has some connectors allowing me to connect the antenna from an old Bearcat and i can try to build one by myself using some coax and hook it up.

I’m very new to this but I set up a NESDR SMART connected to an old Pi 2 a couple of days ago and everything worked. But what I did find is it needs quite a lot of power. I’m using a power supply which can output 3A and that’s fine but a 2A supply was insufficient. The SDR gets quite warm as does the Pi CPU. In summary the NESDR works but it needs a good power supply. A powered USB hub might be an alternative.

I am running a Pi Zero but it works, i used a powerbank as a test and check if the usb device remained available. Temperature on the zero was about 35-40 celcius. Perhaps things remained calm seeing no signal was being processed.

Seeing i also ordered a Pi4 i can test it to see what works best. Although it is intended to be a desktop replacement i can use it to run Piaware as well. The Pi4 comes with a 3,0A charger so that should take care of the power. It also has a fan.

1 Like

After connecting the Nooelec receiver things are up and running. I also have it streaming to the internet so I can access my own site from my phone and also let my Son use it while at his mom.

This is my test setup for now, next step is a permanent setup.