- Joined
- Jul 30, 2026
- Messages
- 121
- Thread Author
- #1
Short answer: There is no universal good messages-per-second value because traffic density, antenna view, gain, filtering and decoder definitions differ. Use messages per second as a repeatable local metric together with aircraft count, range and strong-message percentage.
Before you start
- Use 1090 MHz Mode S and ADS-B as the initial target unless the project specifically requires 978 MHz UAT in a region where it is used.
- Record antenna type and height, coax length, receiver gain, decoder version and a fixed observation window before comparing changes.
Step-by-step method
- Step 1: Choose the same time of day and day type for comparisons. Record at least 24 hours when evaluating a permanent station change.
- Step 2: Save average and percentile message rates, unique aircraft, maximum and percentile range, receiver gain and decoder version.
- Step 3: Change one variable, such as gain or filter, and compare the full distribution. A higher peak MPS during a traffic wave does not prove the change helped.
- Step 4: Check strong-signal statistics and CRC/error indicators. If MPS falls at maximum gain while strong-message percentage is high, reduce gain and retest.
Concrete example
A rural station averaging 80 MPS can be excellent for its traffic and horizon, while an airport station may exceed several hundred. The useful question is whether the same station moves from 80 to 105 MPS with more aircraft and unchanged conditions after a controlled improvement.How to judge the result
A good rate is stable for the site's traffic, accompanied by broad coverage and free of overload or sample-loss indicators. Preserve a rolling baseline instead of copying another station's number.What to record
- Compare unique aircraft, maximum range, messages per second and the shape of the polar coverage plot over equal time periods.
- Use at least 24 hours for a meaningful station baseline because traffic direction and density vary throughout the day.
- A higher message rate with fewer distant aircraft can indicate overload, local traffic changes or a different gain compromise rather than a universal improvement.
Common mistakes
- Changing several hardware, software or RF variables at once, which removes the controlled comparison needed to identify the cause.
- Treating one autoscaled screenshot or one unusually good result as proof without recording the settings and repeating the test.
- Optimizing only for MPS can favour dense nearby traffic while reducing distant-aircraft coverage, so always read it with range and aircraft metrics.