Limit to message rate handled by Pi3?

Is there a limit to the message rate that can be handled by a Pi3 running 3.5.0?

I’m seeing 1600+/sec but I expect more! Is there a way of telling if the Pi is overloaded?

This is a “top” dump …

top - 08:59:26 up 3 days, 18:01, 2 users, load average: 0.60, 0.51, 0.50
Tasks: 127 total, 1 running, 126 sleeping, 0 stopped, 0 zombie
%Cpu(s): 9.6 us, 1.4 sy, 0.0 ni, 88.6 id, 0.0 wa, 0.0 hi, 0.4 si, 0.0 st
KiB Mem: 947092 total, 305072 used, 642020 free, 38512 buffers
KiB Swap: 0 total, 0 used, 0 free. 168232 cached Mem

Any suggestions or observations (or explanations!) gratefully received!

Kind Regards

In the first line, the load average shows the system load time for the last 1, 5 and 15 minutes.

In the third line, the CPU usage:
CPU usage as a percentage by the user
CPU usage as a percentage by system
CPU usage as a percentage by low priority processes
CPU usage as a percentage by idle processes
CPU usage as a percentage by io wait
CPU usage as a percentage by hardware interrupts
CPU usage as a percentage by software interrupts
CPU usage as a percentage by steal time

Your CPU is idle 88% of the time, so it’s ready to process more.

Run: IP_address/dump1090-fa/data/stats.json

I am most grateful for your reply. I take it then that my Pi is coasting and hardly breaking out into a sweat!

That’s reassuring …

Kind Regards

1 Like

Run: IP_address/dump1090-fa/data/stats.json


This doesn’t mean a great deal to me I’m afraid :cry:

For one minute: “peak_signal”:-0.9,“strong_signals”:4885
That’s what I had too, stronger signals (close-up planes) get clipped and discarded. You can try to reduce the gain by 6…10dB for a day (week) and go from there.

There seems to be a natural limit somewhere around 1600-ish for an omni antenna; you’ll probably need to go to sectorized antennas if you want more than that.
I think it’s a combination of the message collision rate, and TCAS self-limiting in busy environments.


That’s it! Thank you.


Interesting analysis: … ystem.html

1533 is the number of frames per second supported in this instance, but it’s not the number of planes. Each plane is required to transmit location and velocity frames twice a second. They are also required to transmit a flight ID frame every 5 seconds. This means at a bare minimum the plane is transmitting 4.2 frames per second. I’m unsure if the plane is required to transmit it’s position twice a second or position frames twice a second (there is a difference). ADS-B uses a strange compression method called compact position reporting to transmit the latitude and longitude of a plane. Two frames are required for a full latitude and longitude position. I’m going to stick with 4.2 frames a second but it could be 6.2 frames per second.
Taking the number of 4.2 frames per second per plane as a minimum means that there can’t be more than 1533/4.2 = 365 planes visible to a receiver at any one time. Even that’s an unlikely scenario, because at that point there are quite a few frame collisions occurring. Having said that there will always be some collisions. It’s still around 10% which is not insignificant.

To avoid collisions, multiple sectors are needed and multiple RF receivers (one per sector, separate collision domains). One Pi3 can handle all of them IMO.

Hey, @obj, can the FilghtFeeder accommodate multiple receivers? I am tempted to experiment, even if max of what I see is only around 500 simultaneous, adding an extra USB RF receiver and two directional antennas.

Double click post, sorry.

No, it’s not set up for that.

I’m pleased to have initiated a good discussion and most grateful for the information.

Anyone have a Mode S Beast for sale?

Kind Regards



There are a few holes in the analysis that make the numbers a bit different (but the basic concept is right).

ADS-B is not the only traffic on 1090MHz. There is also non-ADS-B Mode S traffic (DF11 acquisition squitters, responses to SSR interrogations, responses to TCAS); there are also mode A/C replies. Many of the Mode S replies are half the length of ADS-B messages so the probability of collisions is lower.

But somewhere around 1500-2000 is not an unreasonable guess.


Great discussion!


My RPi3 Piaware 3.1 runs 1800+ just, mainly in the 1700’s , fine tuning of the gain helped.
I’m in a busy area 10km to the side of Heathrow with reasonably clear horizon and think this is the natural limit for my location - local traffic clobbers the more distant stuff.
I have tried The Mode S Beast, Planefinder and AirSpy - RPi3/Piaware comes out the best but only just.

PS: Piaware is the only one of the above that you can tune the gain, which allows you to maximise planes or messages (in my location).

You can alsof tune the gain from the Airspy (0-21)

I’ve been trying to get my hands on a used one as well. Seems that those that have them are keeping hold of them! Should have done the same when I had one a few years back - alas I sold it when I thought I wasn’t going to be able to support this hobby any longer :unamused:

Heathrow is around 12 miles South West of me, If aircraft are landing towards West my simple setup sees the planes to around 1500 feet then they disappear. Indoor telescopic antenna and a Pi Zero in upstairs bedroom. Aircraft count usually around 1700-2000


This was an 1 year old thread. Why dig it up?

The thread may be old but new users have similar problems and searches bring up older threads.

Wasn’t actually aware of age. Is there a message age limit?


1 Like