A satellite receiver sensitivity report should identify the plane where input power is defined. Record how the delivered level was established and its uncertainty.
Why this matters in the industry
Source settings, fixture loss and receiver input levels are different quantities. A report that mixes them can make two otherwise valid tests appear inconsistent.
The technical reasoning
A receiver sensitivity report needs the stimulus reference plane, error criterion and uncertainty associated with the inferred level. Source settings and nominal path loss are not enough when small threshold differences matter. Include repeated observations and the method used to estimate the threshold, preserving any uncertainty from route characterization or receiver state.
How uncertainty affects the engineering decision
Uncertainty belongs to a particular result and measurement model. Contributions may include source calibration, route characterization, connector repeatability, drift and processing, but their importance depends on the quantity. In a suitable linear model, independent standard uncertainties may be combined through sensitivity coefficients and a root-sum-of-squares calculation. Correlated contributions need their covariance considered. An expanded uncertainty additionally requires a stated coverage factor and interpretation; an unlabeled plus-or-minus value leaves that meaning unclear.
How to structure the investigation
State the physical input interface, waveform, initial receiver state and performance criterion. Include measured external loss and the applicable correction data. Record repeatability observations and test duration so another team can reproduce the result under the same assumptions.
List the contributions with units, distribution assumptions and evidence. Distinguish the standard deviation of repeated observations from uncertainty in their estimated mean, and avoid using repeated readings to claim that an unresolved bias disappears. For acceptance work, define the decision rule before examining borderline results. A guard band can alter an acceptance boundary, but its width must follow the agreed uncertainty and risk model.
Worked example or engineering scenario
Two reported thresholds differing by 0.3 dB cannot automatically be ranked if the methods have comparable or larger unresolved uncertainty. The conclusion must consider their common and independent contributions.
Evidence to collect
| Record | Purpose |
|---|---|
| Name the input plane | Defines the tested state and scope of the comparison. |
| Record waveform and state | Makes the stimulus or route condition reproducible. |
| Include path correction | Supports interpretation of variation and possible confounding effects. |
| State the success criterion | Connects the observation with the stated engineering decision. |
Trade-offs and common interpretation errors
No universal percentage or dB allowance fits every RF measurement. A result near a limit can have a different decision implication from the same central value with smaller uncertainty. Report the observed value, uncertainty basis and rule separately so a reviewer can understand the conclusion without reconstructing an undocumented policy.
What the result can support
Report the measurement model and reception observations alongside the estimated threshold.
A dial reading or generator setting alone is not a complete sensitivity measurement.
Further technical reading
Related industry knowledge
- Satellite IF Isolation: Protecting Independent Monitoring Branches
- Frequency Conversion and Satellite Harmonic Measurements
Numerical scenarios are illustrative assumptions, not reported measurements of a supplied product or installation.