Access Official Technical PDF

Share Summary:LinkedInEmail

For industrial wireless deployments, radio compliance is part of designing reliable equipment for operation in shared spectrum. DFS compliance is especially relevant to Wi-Fi devices that use specified 5 GHz U-NII bands, where systems must respond appropriately when radar is detected. A client device may not perform radar detection itself, but its behavior still matters: it must follow the applicable channel-change and transmission rules when its master detects radar.

A Bureau Veritas test report for the Marvell W8997-M1216 wireless LAN and Bluetooth module provides a practical example. The report evaluates a client operating without radar-detection capability under FCC Part 15, Subpart E, and the cited U-NII DFS procedures. Its findings show how test scope depends on device operating mode—and why passing a client-mode test should not be mistaken for evidence that every DFS requirement applies to that client.

DFS compliance depends on the device’s operating role

Dynamic Frequency Selection (DFS) is a set of requirements for devices operating in certain U-NII frequency bands. The report identifies the module’s relevant operating ranges as 5250–5350 MHz and 5470–5725 MHz. Within a wireless system, a device may act as a master, a client that detects radar, or a client that does not detect radar. The required tests differ across those roles.

In the reported configuration, the W8997-M1216 was a client without radar detection. Radar test signals were introduced to the master device, not to the client. The master’s response could then prompt the client to stop using the affected channel or move with the master. This arrangement reflects a key distinction for system integrators: a client’s DFS obligations are determined by how it operates in the system, not simply by the fact that it can connect over a DFS channel.

The report tested the client across 20 MHz, 40 MHz and 80 MHz bandwidth modes. It identifies channel move time, channel closing transmission time and non-occupancy period as applicable requirements for this operating mode. DFS detection threshold, channel availability check time and U-NII detection bandwidth were listed as not applicable to the client without radar detection.

What the channel-change tests evaluate

When radar is detected by the master, the wireless system must manage its transition away from the affected channel. Two related measurements help characterize that response:

  • Channel closing transmission time covers the period in which the device may continue transmitting after the radar event, including permitted control transmissions associated with moving channels.
  • Channel move time measures how long the system takes to move off the channel after the radar signal ends.

The report lists a 10-second channel move time limit. It also specifies a channel closing transmission allowance of 200 milliseconds, plus an aggregate of 60 milliseconds over the remainder of the 10-second period for intermittent control signals required to facilitate a channel move. The report states that the applicable channel closing and channel move tests passed. Its results should be read in the context of the particular sample, test setup and operating mode documented in the report.

Testing was conducted with radar signal waveforms and a master-client arrangement, using channel loading during relevant measurements. The report describes Radar Type 0 for the channel move and channel closing tests. It also notes that testing covered the three bandwidth modes, with the 80 MHz mode used for representative plots. For product teams, this illustrates why test planning needs to account for bandwidth configuration as well as the device’s role.

Why the non-occupancy period matters

A channel that has been identified as containing radar cannot simply be reused immediately. The report gives a minimum non-occupancy period of 30 minutes. For the associated test, the client and master established a link on the test frequency, and the system used channel loading. After radar was introduced to the master, the original frequency was monitored for the required period.

The report also describes a separate non-associated test with the master turned off. During the 30-minute observation, the client made no transmissions in the DFS band after power-up. This check addresses a different system condition from the associated test: it examines whether the client transmits when it is not connected to its master.

A further non-co-channel test checked that the unit did not operate co-channel with the radar after detection. In addition, the report’s appendix documents observations of beacon behavior following power-up in 20 MHz, 40 MHz and 80 MHz modes. Together, these checks help assess whether a client’s behavior remains consistent with the tested DFS operating conditions.

Interpreting the report for product development

The W8997-M1216 report records passing results for the applicable channel move, channel closing transmission, non-occupancy, non-associated and non-co-channel tests. It does not report a pass for every DFS test category: several are marked not applicable because the unit was tested as a client without radar detection. That distinction is important when reviewing compliance documentation or defining requirements for a complete wireless product.

The report also applies to a specific engineering sample, firmware version, antenna configurations and test arrangement. It states that its findings concern the identified test sample and are not automatically representative of a production lot or other product configuration. Integrators and manufacturers should therefore confirm that the final design and intended operating modes match the scope of the relevant compliance evidence.

Practical implications for industrial teams

For engineers and technical decision-makers, the central lesson is to map DFS requirements to the complete operating architecture. Identify which device acts as the master, whether clients perform radar detection, and how channel changes are coordinated. Then verify that the applicable test evidence covers intended frequency bands, bandwidths, firmware and antenna arrangements.

DFS compliance is not just a radio-module checkbox. A client that relies on a master still needs to behave correctly during channel moves, observe the non-occupancy conditions and avoid unintended transmissions in tested scenarios. Reviewing those behaviors at the system level helps teams interpret certification reports accurately and make better-informed decisions when integrating wireless equipment into industrial products.

Access Official Technical PDF

About The Author