Acceptance Is a Test Record, Not a Handshake
Most drone jammer projects fail acceptance in one of two ways: either no one documents the measurements, or testing is conducted under conditions that never occur in the field—using a dummy load instead of an antenna, bench testing at 22° instead of operating inside a sealed enclosure exposed to sunlight, or testing a single frequency instead of the full band.
This article outlines what to measure on a module prior to integration and what to measure on the finished head before handover, including records that allow each result to be verified six months later. It follows theselection guideand theband and power referenceUse these two to select the configuration, then use this one to verify it works.
Part 1: Module Bench Tests
Bench tests answer one question: Does the module meet its specifications across the entire band at its in-service temperature? Five measurements cover this.
1. Output power across the band, not at the band center
Drive the module at its rated input and sweep the full specified range in 5 to 10 MHz steps, recording the output at each step. The critical metric is the spread between the center and the edges. A module rated for 50 W that delivers 50 W at the center and 34 W at the band edges will create a coverage gap precisely where the threat hops.
Record: sweep table, ambient temperature, supply voltage at the module terminals, and the power meter used. If the module has an internal detector, compare its reading against the external meter; a 1 dB discrepancy is common and should be noted before relying on field telemetry.
2. Gain flatness and small-signal response
Measure gain at both low drive and rated power. Some modules compress earlier than the datasheet suggests, and a link that hops across the band will experience both extremes. A flatness within 2 dB across the operating range is a reasonable target for a well-behaved design; wider variation indicates the antenna and power budget need additional margin.
3. Harmonics and spurious emissions
Connect a spectrum analyzer via an appropriate attenuator and verify second and third harmonics, as well as any non-harmonic spurs. This is not bureaucracy: an unfiltered 2.4 GHz module can emit energy at 4.8 GHz—and more critically, into GNSS and licensed bands. Log the worst spur, including its frequency and level relative to the carrier.
Repeat the measurement with the antenna connected, not just into a load. A poor antenna match shifts the amplifier's operating point and can significantly increase harmonic levels.
4. VSWR protection behavior
Deliberately introduce a mismatch and verify the module's behavior. Two acceptable responses are: folding back output while remaining active, or shutting down and retrying. Unacceptable behaviors include: continuing at full power despite the mismatch, or shutting down permanently without a recovery path. Use a step mismatch, hold it for at least 30 seconds, and record the output response and recovery time.
This test detects more real-world failures than any other. Field failures are primarily caused by damaged cables and water ingress in connectors, both of which trigger this exact condition.
5. Thermal runaway at rated power
Run the module at its rated continuous power for at least 30 minutes in the intended enclosure and orientation, with ambient temperature at the upper end of the deployment range. Log flange temperature, case temperature, and output power every minute. A drop exceeding 0.5 dB during operation indicates thermal compression. If the flange temperature continues rising after 30 minutes, the heatsink is undersized—not that it needs more time to stabilize.
Record: ambient conditions, enclosure type, airflow, temperatures at 0/10/20/30 minutes, and output drift.
Bench Acceptance Checklist
| Test | Method | Pass condition | Record saved |
|---|---|---|---|
| Output power | Sweep full band from 5 to 10 MHz in steps at rated drive. | Within the specified tolerance of rated power at all steps | Sweep table with meter and attenuator values |
| Flatness | Low gain at band edges and center | Variation within the agreed range, typically 2 dB | Gain table and test frequency list |
| Harmonics and spurs | Sweep spectrum into load and antenna | Lowest spur below the agreed limit; no in-band spurs | Analyze screenshot with reference level noted |
| VSWR protection | Step mismatch held for 30 seconds | Foldback or shutdown with recovery; no fault latch | Output trace and recovery time |
| Thermal runaway | 30 minutes at rated power in the final enclosure | Output drift below 0.5 dB, temperature stable | Temperature and power log |
Part 2: Field Acceptance for Installed Head
Once the head is mounted, the question shifts from "does the module work" to "does the installation work at its location." Take three measurements using a spectrum analyzer or a receiver with logging enabled.
1. Baseline sweep before power-on
Sweep the target bands at your intended operating positions with the jamming head disabled. This baseline is essential for distinguishing your own harmonics from ambient signals later. Save the trace with a timestamp and note the antenna used.
2. Coverage sweep with the head engaged inside the protected volume
Take measurements at the corners and center of the protected volume at the height where the threat is expected to fly. The requirement is not a single value: it is a continuous raised floor across each target band, with no gap wider than the hop range of the link you are denying. Gaps typically occur at band edges, which aligns exactly with predictions from the bench flatness test.
3. Leak check outside the protected volume
Inspect the perimeter: doorways, windows, service penetrations, cable ducts, and the corridor beyond. The pass criterion is that the raised floor inside must not extend outside at a level that affects neighboring users or the site's systems. Record locations where the floor level drops off and where it does not.
Field Acceptance Checklist
| Check | Method | Pass condition | Record saved |
|---|---|---|---|
| Pre-install baseline | Band sweep with head off at planned positions | Stable trace with no unexplained peaks | Timestamped trace files |
| In-volume coverage | Corners plus center, threat altitude | Continuous raised floor per target band | Per-position screenshots and band list |
| Boundary leakage | Doorways, windows, ducts, corridors | No matching level found outside the volume | Coverage map with measured points |
| Device health | Forward and reverse power, temperature | Within the limits agreed upon at handover | Export telemetry |
| Documentation | Serial numbers, firmware versions, antenna models | Complete and compatible with installed units | Transfer file |
Writing Acceptance Criteria That Withstand Review
Vague criteria are the most common source of disputes, and they're avoidable. Four rules make a specification testable.
- State the condition, not just the value."50 W continuous at the antenna connector, measured at 28 V input and 40° ambient" is testable. "High power output" is not.
- Define the measurement point.Connector, antenna input, or a specified distance from the antenna. All three yield different values, and all are valid when recorded.
- Specify who performs the measurement and the tool used.The instrument class and calibration date must be listed in the acceptance section, not discovered afterward.
- Agree on failure behavior.Retest window, replacement terms, and whether a marginal result is accepted with a written note.
The same rigor applies to any distance claim, including ours. A range figure is meaningless without specifying the receiver model, altitude, antenna orientation, and terrain. Always ask for test conditions before accepting a number.
Most Common Issues
Across field returns, a few causes repeat: connectors that filled with water after the first rain, cables kinked during installation causing mismatches, heatsinks mounted against surfaces with no airflow, and firmware limits reducing power in bands nobody tested. None of these show up on bench tests of the module alone—all are caught by the field checklist above.
Compliance Notice
Acceptance testing does not grant authorization. Modules are components; the final device, its power limits, allowed frequency bands, and operation are the integrator's responsibility and must comply with local regulations. Interfering with public mobile networks, aviation navigation, emergency services, or life-safety systems is prohibited in most jurisdictions regardless of output power. Document the agreed operating envelope with the end user in writing before commissioning.
Where to Go Next
If you're still deciding on the configuration, start withselection guideand verify the numbers against theband and power table. If you're ready to test, our team can send the measured data for the models in your band plan, and thedrone jammer module rangeLists continuous power, supply voltage, and connector type for each unit.
