Dynamic Frequency Selection (DFS) allows 5 GHz Wi-Fi devices to detect radar signals and switch channels automatically. Regulators require DFS testing before they certify a device for sale. Here’s what you need to know before you start:
- Which 5 GHz bands trigger mandatory DFS testing
- How FCC and ETSI timing requirements compare
- What your test sample needs before testing begins
- Why most DFS tests fail on the first attempt
Which 5 GHz Bands Require DFS Testing
Regulators require DFS on the same two 5 GHz sub-bands worldwide: 5.25–5.35 GHz and 5.47–5.725 GHz. The table below shows which U-NII bands require DFS testing and which don’t.
| Band | Frequency Range | DFS Required |
| U-NII-1 | 5.150–5.250 GHz | No |
| U-NII-2A | 5.250–5.350 GHz | Yes |
| U-NII-2C | 5.470–5.725 GHz | Yes |
| U-NII-3 | 5.725–5.850 GHz | No |
A device that only operates in U-NII-1 and/or U-NII-3 skips DFS testing entirely. A device that operates anywhere in U-NII-2A or U-NII-2C requires DFS testing, even when it also supports the DFS-exempt bands.
FCC vs. ETSI DFS Requirements
FCC and ETSI set nearly identical DFS timing limits, though the underlying frameworks differ in how they define detection thresholds. The table below compares the core requirements under FCC 47 CFR §15.407 and ETSI EN 301 893.
| Requirement | FCC / ISED | ETSI EN 301 893 |
| Channel Availability Check | ≥60 seconds | ≥60 seconds (longer on select channels) |
| Channel Move Time | ≤10 seconds | ≤10 seconds |
| Channel Closing Transmission | 200 milliseconds + an aggregate of 60 milliseconds over the remaining Channel Move Time | ≤1000 ms total |
| Non-Occupancy Period | ≥30 minutes | ≥30 minutes |
| Detection Threshold | −64 dBm or −62 dBm, based on EIRP | Based on bandwidth and EIRP class |
Channel Closing Transmission and Detection Threshold are where the frameworks diverge most. For Channel Closing Transmission time, ETSI sets a flat 1000ms limit while FCC only allows 60ms after the first 200ms. For Detection Threshold, FCC rules set a flat −64 dBm threshold for devices with 200 mW to 1 W EIRP and −62 dBm for lower-power devices. ETSI assigns threshold levels by bandwidth and power class instead, so your lab needs your device’s exact EIRP and channel bandwidth before it can select the correct test parameters.
What Your Device Needs Before DFS Testing Starts
DFS testing can’t start without the right sample and support equipment on hand. Missing pieces here cause most schedule delays.
| Requirement | Why It Matters |
| RF Sample with a 50-Ohm Connector (SMA Preferred) | Allows the lab to inject radar waveforms directly into the receiver. |
| Configurable Modulation and Data Rate | Confirms DFS performance across every mode the device supports. |
| Settable Country Code | Enables testing under the regulatory domain of the target market. |
| Companion Device and Traffic Generation Method | Establishes the traffic link monitored during a channel move and sets the desired channel loading |
| Accessible DFS Enable/Disable Control | Allows the lab to isolate DFS behavior from other channel-selection logic. Significantly decreases test time. |
| Firmware Version and Documented Test Scripts | Enables the lab to reproduce the exact configuration used for each result. |
Common Reasons Devices Fail DFS Testing
Most DFS failures trace back to gaps in preparation, not device design flaws.
| Failure Point | What It Costs You |
| No DFS Disable Function in Firmware | The lab cannot isolate radar response from normal channel-selection logic. Significantly increases test time. |
| No Companion Device on Hand or Traffic Generation Method | The lab cannot generate the traffic link needed for monitoring at the required channel loading amount. |
| Incomplete Configuration Documentation | The lab cannot confirm which settings resulted in a pass or a fail. |
| Limited Logging Access | The lab cannot verify that the device met the required channel-move time. |
Work With an Accredited DFS Test Lab
Choose a lab that holds accreditation in every market where you plan to sell your device. MiCOM Labs holds direct authority across five major markets.
| Accreditation | Market |
| FCC TCB | United States |
| ISED FCB | Canada |
| RED Notified Body | European Union |
| UKCA Approved Body | United Kingdom |
| MIC RCB | Japan |
That direct authority lets MiCOM Labs move your certification through in days instead of weeks, because your results don’t wait on a separate regulator review in each market.
Contact MiCOM Labs to scope your device’s DFS test plan.
FAQ
Do all 5 GHz devices need DFS testing?
No. Only devices that transmit in U-NII-2A or U-NII-2C require DFS testing, and that rule applies regardless of product category. It covers far more than routers and access points, including:
- Fixed-wireless radios
- Drones
- Industrial IoT sensors
How long does DFS testing take?
Bench time scales with the number of channel-and-bandwidth combinations your device supports, since the lab has to run the full radar test suite against each one. Confirm your device’s complete channel list and power classes before requesting a quote, so your lab can scope the timeline accurately rather than estimating from a partial spec.
What happens if a device fails DFS testing?
A failed test blocks certification until you resolve the issue. Most fixes are firmware-level changes to timing or threshold behavior and typically require retesting only the affected channels, not the entire test suite.
Does DFS apply outside the US and the EU?
Yes. These markets regulate the same radar-sensitive 5 GHz frequencies, and each requires its own compliance testing before granting market access, independent of the FCC and ETSI figures above:
- Canada
- United Kingdom
- Japan
Can I reuse ETSI test results for FCC certification, or vice versa?
No. Every regulator requires its own compliance test report, even when the radio hardware doesn’t change between markets. Budget for a separate DFS test campaign for every region you’re certifying in.
Is DFS the same requirement as TPC?
No, though regulators test them together. DFS moves your device off a channel when it detects radar. Transmit Power Control (TPC), instead, limits interference range by capping transmit power in the same bands. Your lab evaluates both in one campaign, but a pass on one doesn’t guarantee a pass on the other.