Best WiFi 5 Wave 2 Modules Reviewed: QCA9984, MT7615D Selection Guide for Industrial IoT

Selecting the right WiFi 5 Wave 2 module for your industrial IoT gateway, enterprise access point, or embedded system requires evaluating real-world performance, chipset ecosystem maturity, and OEM/ODM customization options. This guide reviews the leading Wave 2 module solutions including Qualcomm QCA9984 (4×4:4, 1.73 Gbps PHY) and MediaTek MT7615D (4×4:4, 1.73 Gbps PHY), comparing their host interfaces, thermal characteristics, driver support, and deployment suitability.

A Wave 2 module is distinguished from Wave 1 by three mandatory additions: 160 MHz channel bandwidth (contiguous or 80+80 MHz non-contiguous), 4 spatial streams (4×4:4 MIMO configuration), and downlink MU-MIMO supporting transmission to up to 4 clients simultaneously. Transmit beamforming (TxBF) using Null Data Packet (NDP) sounding was also elevated from optional in Wave 1 to mandatory in Wave 2 certification.

As of 2026, WiFi 5 Wave 2 modules remain widely deployed in industrial IoT gateways, enterprise access points, embedded wireless systems, and legacy equipment upgrades. The mature chipset ecosystem ensures competitive pricing, proven driver support across Linux kernels 4.4 through 6.x, and validated interoperability with over a decade of WiFi client devices. Below we review the top module options and their ideal use cases.

For a comprehensive overview of the WiFi module ecosystem from Wave 2 through WiFi 7, refer to our WiFi module complete guide.

1. How a WiFi 5 Wave 2 Module Works: Architecture and Core Mechanisms

1.1 Physical Layer Architecture

The Wave 2 physical layer (PHY) operates exclusively in the 5 GHz UNII bands (5.15–5.35 GHz and 5.47–5.85 GHz, depending on regional regulatory domain). The PHY employs Orthogonal Frequency Division Multiplexing (OFDM) with 256 subcarriers per 80 MHz channel segment, of which 234 are data subcarriers, 8 are pilot subcarriers, and 14 are guard/null subcarriers. When operating in 160 MHz mode (either contiguous or 80+80 MHz non-contiguous), the subcarrier count doubles to 512, with 468 data subcarriers available for user data transmission.

Each spatial stream in a 4×4:4 configuration is transmitted through a dedicated antenna chain comprising its own RF front-end, power amplifier (PA), low-noise amplifier (LNA), and baseband processing path. The QCA9984, for example, integrates four complete transmit/receive chains with digital predistortion and PA linearization circuitry to maintain spectral mask compliance at 20 dBm output power per chain.

1.2 MU-MIMO Transmission Mechanism

The defining architectural innovation in Wave 2 is downlink Multi-User MIMO (DL MU-MIMO). Unlike Wave 1’s Single-User MIMO (SU-MIMO), where the entire channel bandwidth is allocated to one client at a time per transmission opportunity, DL MU-MIMO uses spatial division to serve multiple clients concurrently within the same frequency-time resource.

The process follows four sequential steps:

• Channel Sounding: The AP transmits a Null Data Packet Announcement (NDPA) followed by a Null Data Packet (NDP). Each intended client receives the NDP and measures the channel state information (CSI) across all subcarriers and spatial dimensions.
• Beamforming Feedback: Each client returns a compressed beamforming report — a quantized representation of the steering matrix — back to the AP. The feedback granularity in 802.11ac is 2 bits per angle for the Givens rotation representation, with configurable subcarrier grouping (Ng = 1, 2, or 4).
• Precoding Matrix Computation: The AP computes a precoding (steering) matrix from the aggregated feedback. The goal is to orthogonalize the spatial streams such that each client’s data arrives with minimal inter-user interference at its respective receive antennas.
• Simultaneous Transmission: The AP transmits precoded data frames to up to 4 clients in a single Physical Layer Protocol Data Unit (PPDU). Each client decodes only its own spatially filtered stream, treating energy from other clients’ streams as low-level noise.

The MU-MIMO group size is limited to 4 clients per transmission in 802.11ac Wave 2, and all clients in a MU group must use the same channel bandwidth (80 MHz or 160 MHz). The AP can maintain multiple MU groups in memory and switch between them on a per-transmission basis.

1.3 Transmit Beamforming (TxBF)

Transmit beamforming in Wave 2 uses explicit feedback based on NDP sounding, as specified in the IEEE 802.11ac-2013 standard. The AP transmits a known sounding frame, the client measures the channel, and returns quantized beamforming feedback. This explicit mechanism is mandatory in Wave 2 certification and ensures deterministic beamforming gain regardless of client chipset vendor.

The typical beamforming gain in Wave 2 systems ranges from 3 to 6 dB at the receiver, translating to approximately 1.4x to 2x improvement in received signal strength. In practice, this extends the usable range by 20–40% at the same data rate, or allows operation at one MCS level higher at a given range compared to non-beamformed transmission.

2. WiFi 5 Wave 2 Module Speed: Theoretical Peak Rate and Real-World Throughput

2.1 Theoretical Peak PHY Rate

The IEEE 802.11ac Wave 2 PHY rate is determined by the following formula:

The maximum PHY rate configuration for WiFi 5 Wave 2 is:

Configuration Parameter	Value
Channel Bandwidth	160 MHz (contiguous) or 80+80 MHz (non-contiguous)
Spatial Streams	4 (4×4:4 MIMO)
Modulation and Coding	256-QAM, MCS 9, 5/6 coding rate
Guard Interval	400 ns (short GI)
Peak PHY Rate	3.47 Gbps

For the more commonly deployed 80 MHz configuration, the peak PHY rate at 4×4:4 with 256-QAM and 400 ns GI is 1.73 Gbps. At 3×3:3 with 80 MHz, the peak is 1.3 Gbps, identical to the maximum Wave 1 configuration.

2.2 Real-World TCP Throughput

Achievable TCP/IP throughput in real-world deployments is substantially lower than the PHY peak due to MAC layer overhead, channel contention, client capability limitations, and host CPU processing constraints. Based on Qualcomm QCA9984 reference design measurements and validated by third-party testing from SmallNetBuilder (2017–2018), the following throughput figures represent realistic expectations:

Test Scenario	80 MHz, 4×4:4	160 MHz, 4×4:4
TCP Downlink (single client, close range)	720 Mbps	1,050 Mbps
TCP Uplink (single client, close range)	680 Mbps	950 Mbps
TCP Downlink (4 concurrent clients, MU-MIMO)	580–720 Mbps (aggregate)	750–950 Mbps (aggregate)
TCP Downlink (10 concurrent clients, high density)	400–560 Mbps (aggregate)	500–680 Mbps (aggregate)
Industrial IoT (100-packet latency, 95th percentile)	6–12 ms	5–10 ms

Source: Qualcomm QCA9984 Reference Design Application Notes (2016); SmallNetBuilder 802.11ac Wave 2 AP Roundup (2017–2018). All measurements at 5-meter line-of-sight, DFS-channel-free environment, WPA2-AES encryption enabled.

2.3 Factors Affecting Real-World Throughput

Understanding why real-world throughput falls below theoretical peaks is essential for accurate deployment planning:

• MAC Protocol Overhead (15–25%): Frame aggregation (A-MPDU up to 256 frames per PPDU, A-MSDU up to 4 MSDUs per frame), acknowledgment frames, DCF interframe spacing (DIFS), and contention window backoff collectively consume 20–30% of the channel airtime even under optimal conditions.
• Client Capability Bottleneck (20–40%): Most client devices in 2026 — including laptops, smartphones, and IoT sensors — are equipped with 1×1:1 or 2×2:2 WiFi 5 radios. When a Wave 2 4×4:4 AP serves such clients, the effective PHY rate is determined by the client’s maximum capability, not the AP’s. MU-MIMO partially mitigates this by serving multiple low-capability clients simultaneously, but the per-client throughput remains individually limited.
• Co-Channel Interference and DFS (10–30%): The 5 GHz unlicensed band is shared with radar systems (DFS channels), neighboring APs, and other wireless services. Rate adaptation algorithms respond to detected interference by stepping down MCS levels. In dense urban deployments with 15+ visible APs on the same channel, PHY rate retention can drop to 50–65% of the maximum achievable rate.
• Host CPU and Bus Bottleneck (5–15%): Embedded Wave 2 modules connected via PCIe 2.0/3.0 rely on the host processor for TCP/IP stack processing, NAT routing, and encryption. The Qualcomm IPQ8064 (dual-core Cortex-A15 at 1.4 GHz) exhibits a TCP throughput ceiling of approximately 1.2 Gbps under full-duplex conditions, limiting the 160 MHz PHY potential.

3. Complete Technical Feature Set of WiFi 5 Wave 2 Modules

3.1 Channel Bandwidth and Spectral Configuration

Wave 2 supports four channel bandwidth modes: 20 MHz, 40 MHz, 80 MHz, and 160 MHz. The 160 MHz mode can be implemented as a single contiguous 160 MHz block (available in UNII-1 through UNII-3 in the United States under FCC Part 15.407) or as two non-contiguous 80 MHz blocks (80+80 MHz mode) that may reside in different UNII sub-bands. The 80+80 MHz mode offers flexibility in regulatory domains where contiguous 160 MHz spectrum is unavailable, such as the EU’s ETSI EN 301 893 framework where DFS restrictions limit contiguous channel availability.

In practice, the 80 MHz channel width is the most commonly deployed configuration for Wave 2 modules in industrial and enterprise environments as of 2026. 160 MHz operation requires clear spectrum availability across both sub-bands, which is challenging in dense urban and industrial settings where radar DFS events and co-channel interference are prevalent. According to yuneng deployment data across 200+ industrial sites, approximately 35% of Wave 2 installations use 80 MHz only, 55% operate at 80 MHz with dynamic channel selection capability, and only 10% operate at 160 MHz — primarily in rural or suburban point-to-point bridge applications.

3.2 Modulation and Coding Scheme (MCS)

802.11ac Wave 2 supports MCS 0 through MCS 9, identical to Wave 1. The modulation formats span BPSK (MCS 0) through 256-QAM (MCS 8 and 9), with coding rates of 1/2, 2/3, 3/4, and 5/6. The following table maps the key MCS indices to their parameters at 80 MHz with 3 spatial streams:

MCS Index	Modulation	Coding Rate	Data Rate (1 SS, 80 MHz, 400 ns GI)
0	BPSK	1/2	6.5 Mbps
4	16-QAM	3/4	39.0 Mbps
7	64-QAM	5/6	65.0 Mbps
8	256-QAM	3/4	78.0 Mbps
9	256-QAM	5/6	86.7 Mbps

At the maximum 4×4:4 configuration with 160 MHz and MCS 9, the single-stream rate of 86.7 Mbps is multiplied by 4 streams and 2x subcarriers (160 MHz vs 80 MHz), yielding 3.47 Gbps.

3.3 MIMO Configuration and Antenna Requirements

Wave 2 modules support 4×4:4 MIMO configuration, meaning 4 transmit antennas, 4 receive antennas, and up to 4 spatial streams. Each spatial stream requires a dedicated RF chain including PA, LNA, mixer, and baseband ADC/DAC. For the Qualcomm QCA9984, the reference design specifies 4 U.FL connectors (or MHF4 for embedded designs) with 50-ohm impedance-controlled trace routing to the antenna ports.

OEM/ODM designers integrating Wave 2 modules must account for antenna isolation requirements. For 4×4 MIMO operation, the minimum recommended isolation between any two antenna elements is 15 dB, with 20 dB or higher preferred for optimal MU-MIMO performance. Antenna correlation coefficients below 0.3 are necessary to realize the spatial multiplexing gain of 4 spatial streams. In practice, this mandates antenna element spacing of at least half-wavelength (approximately 30 mm at 5 GHz center frequency) and preferably orthogonal polarization diversity.

3.4 Coverage, Penetration, and Latency Performance

The 5 GHz band used by WiFi 5 Wave 2 modules inherently offers shorter range and poorer wall penetration compared to 2.4 GHz due to higher path loss (Friis transmission equation: path loss increases by 6 dB per doubling of frequency). Under typical industrial deployment conditions with 20 dBm transmit power per chain (80 mW EIRP per chain, up to 320 mW total for 4 chains), the following coverage characteristics apply:

• Open office / line-of-sight: 30–50 meters at full MCS 9 data rate; up to 80 meters at MCS 4 (16-QAM) or lower.
• Light industrial (drywall, glass, metal shelving): 15–30 meters with 2–3 dB per-wall penetration loss.
• Heavy industrial (concrete walls, reinforced flooring): 8–20 meters, with concrete penetration loss of 8–12 dB per wall at 5 GHz.
• Outdoor point-to-point (directional antenna): Up to 200–500 meters with high-gain panel antennas (12–18 dBi).

Latency performance for Wave 2 modules in industrial IoT applications is driven primarily by channel access delay and frame aggregation length. With MU-MIMO enabled, 95th percentile one-way latency for 100-byte UDP packets measures 3–8 ms under light load and 6–12 ms under 50% channel utilization. Disabling MU-MIMO and using SU-MIMO increases latency by 20–40% under multi-client traffic due to sequential transmission queuing.

4. Power Supply Specifications and Thermal Characteristics

4.1 Power Consumption by Configuration

Power consumption is a critical selection criterion for embedded and industrial Wave 2 module integration. The following data is sourced from Qualcomm QCA9984 and MediaTek MT7615D/MT7612E datasheets and validated by yuneng lab measurements:

Chipset / Module	Configuration	Active TX (20 dBm/chain)	Idle (DTIM Beacon)	Sleep
Qualcomm QCA9984	4×4:4, 80/160 MHz	5.1 W	0.8 W	0.15 W
MediaTek MT7615D	4×4:4, 80/160 MHz	4.5 W	0.6 W	0.10 W
MediaTek MT7612E	2×2:2, 80 MHz	1.8 W	0.3 W	0.05 W

The power supply design for Wave 2 modules must account for peak current draw during active transmission. For a QCA9984-based design at 3.3V VDD, the peak current is approximately 1.55 A (5.1 W / 3.3V). A minimum power supply rating of 2.0 A (6.6 W) is recommended with 20% headroom, plus additional margin for peripheral circuitry (clock generators, level shifters, FEMs if external).

4.2 Operating Temperature Range

Industrial-grade WiFi 5 Wave 2 modules are specified for an operating temperature range of -20°C to +70°C ambient. Select chipsets, including the Qualcomm QCA9984 with industrial-grade packaging, support extended temperature ranges of -40°C to +85°C. For designs operating at high temperature extremes (+70°C ambient), passive heatsinks with a minimum surface area of 15 cm² are recommended for 4×4:4 modules to maintain junction temperatures below 105°C. For extended -40°C operation, ceramic capacitor selection (X7R or X8R dielectric) and low-temperature solder (SAC305) are required to prevent solder joint fatigue.

5. Industry Application Scenarios for WiFi 5 Wave 2 Modules

5.1 Industrial IoT and Factory Automation

In industrial IoT gateways, Wave 2 modules provide the throughput and client capacity needed for aggregating data from multiple sensor networks, PLCs, and vision systems. A typical deployment involves a Wave 2 industrial gateway collecting data from 20–50 wireless sensors and 5–10 cameras, aggregating 200–400 Mbps of upstream traffic, and forwarding through a wired backhaul. The MU-MIMO feature is particularly valuable in this scenario, as it allows the gateway to simultaneously serve multiple low-data-rate sensors without time-division latency penalties.

5.2 Enterprise Access Points

Enterprise APs using Wave 2 modules (e.g., Qualcomm IPQ8064 + QCA9984 reference design) serve 50–100 concurrent clients with aggregate TCP throughput of 600–900 Mbps at 80 MHz. The mandatory TxBF in Wave 2 extends usable coverage in enterprise office environments, reducing the number of APs required for a given coverage area by 15–25% compared to Wave 1 deployments. Controller-based AP platforms typically disable 160 MHz mode in enterprise deployments due to DFS event frequency in dense channel plans.

5.3 Embedded Wireless Modules for OEM/ODM

OEM/ODM manufacturers embedding Wave 2 modules into custom products benefit from the mature PCIe 2.0/3.0 host interface, comprehensive Linux driver support (ath10k, mt76), and standardized M.2 Key E (2230/2280) and Mini PCIe form factors. The MT7612E in 2×2:2 configuration is popular for battery-powered embedded designs, drawing 1.8 W active TX. For higher-throughput designs, the QCA9984 in Mini PCIe format provides the full 4×4:4 capability.

5.4 Legacy Equipment Upgrades

End-of-life 802.11n and Wave 1 enterprise equipment can be upgraded to Wave 2 capability through module-level replacement where the form factor (Mini PCIe) and interface (PCIe) are compatible. The increased 256-QAM efficiency and MU-MIMO support provide 2–4x throughput improvement over 802.11n (which peaks at 450 Mbps PHY rate with 3×3:3, 40 MHz, 64-QAM). This approach extends the service life of existing hardware platforms by 3–5 years at a fraction of full platform replacement cost.

6. WiFi 5 Wave 2 Module Selection Guide for OEM/ODM and Wholesale Buyers

6.1 Configuration Selection by Application

Application	Recommended Configuration	Recommended Chipset	Key Selection Rationale
Industrial IoT Gateway	2×2:2, 80 MHz	MT7612E	Low power (1.8 W), adequate throughput for sensor aggregation
Enterprise AP	4×4:4, 80 MHz	QCA9984 / IPQ8064	MU-MIMO for 50–100 clients, proven host CPU integration
Point-to-Point Bridge	4×4:4, 160 MHz	QCA9984	Maximum throughput in low-interference outdoor links
Battery-Powered Sensor	1×1:1, 20 MHz	MT7610E	Lowest power consumption (~0.5 W), sufficient for low-data sensors
Legacy AP Upgrade	3×3:3, 80 MHz	QCA9882	Pin-compatible with many Wave 1/802.11n Mini PCIe slots

6.2 Regulatory Compliance Considerations

WiFi 5 Wave 2 modules must comply with regional regulatory requirements for 5 GHz band operation. Key regulatory domains and their constraints are:

• United States (FCC Part 15.407): Allows 160 MHz contiguous channels using UNII-1 (5.15–5.25 GHz) and UNII-3 (5.725–5.85 GHz) bands. UNII-2 and UNII-2 Extended bands (5.25–5.35 GHz, 5.47–5.725 GHz) require DFS radar detection. Maximum conducted transmit power: 20 dBm per chain (80 mW) for UNII-1, 23 dBm (200 mW) for UNII-3.
• European Union (ETSI EN 301 893): Requires DFS on all channels above 5.25 GHz. Maximum EIRP: 200 mW (23 dBm) for indoor-only devices. 160 MHz contiguous operation is severely constrained by DFS requirements; 80+80 MHz non-contiguous mode is more practical.
• China (SRRC): Limits 5 GHz operation to 5.725–5.85 GHz band with a maximum of 20 dBm EIRP. 160 MHz channel bandwidth is available in this band but with limited channel count. SRRC certification adds 4–8 weeks to project timelines.
• Japan (MIC Article 2, Paragraph 1): Permits 5.15–5.35 GHz with DFS and 5.47–5.725 GHz with DFS. Maximum EIRP: 200 mW (23 dBm). 160 MHz operation requires DFS on all channels.

6.3 Host Interface and Driver Compatibility

The majority of WiFi 5 Wave 2 modules use PCIe 2.0 or 3.0 as the host interface, with USB 3.0 available on select modules (e.g., MediaTek MT7612U). For PCIe-based modules, the following driver compatibility matrix applies:

Driver	Supported Chipsets	Minimum Kernel	MU-MIMO Support
ath10k	QCA9884, QCA9984, QCA9888	4.4+ (4.14+ LTS recommended)	Yes (kernel 4.4+)
mt76	MT7615D, MT7612E	5.4+	Yes (kernel 5.4+)
iwlwifi	Intel 8260/8265 (Wave 2)	4.6+	No (SU-MIMO only)

For embedded Linux designs using OpenWrt 21.02+ or Yocto Kirkstone (4.0), ath10k and mt76 drivers are included and fully supported. Windows driver support is available through the respective vendor Windows Update Catalog packages, but industrial and embedded deployments overwhelmingly use Linux-based host systems.

7. Engineering Selection Summary and Key Takeaways

WiFi 5 Wave 2 modules deliver a mature, well-characterized wireless solution for industrial and enterprise applications requiring throughput up to 1 Gbps TCP, support for 50–100 concurrent clients, and reliable operation across extended environmental ranges. The following conclusions are drawn from IEEE 802.11ac standard specifications, chipset vendor datasheets, and yuneng field deployment data across 200+ industrial sites:

1. Wave 2 is the definitive 802.11ac implementation. All mandatory features of the 802.11ac-2013 standard — 160 MHz bandwidth, 4 spatial streams, DL MU-MIMO, mandatory TxBF — are realized only in Wave 2. Any 802.11ac module not supporting these features is a Wave 1 device with inherently limited multi-client capability and spectral efficiency.
2. Real-world throughput is 30–50% of theoretical PHY peak. A 4×4:4 Wave 2 module at 80 MHz delivers 600–900 Mbps TCP downlink in typical enterprise environments, while 160 MHz operation reaches 800–1,200 Mbps under favorable conditions. Plan deployment capacity based on measured TCP throughput, not PHY rate.
3. MU-MIMO benefit is deployment-dependent. In environments with 4+ concurrent active clients, MU-MIMO provides 1.5–2.5x aggregate throughput improvement over SU-MIMO. In single-client or low-density deployments, MU-MIMO offers no throughput benefit, and Wave 2 modules operate identically to Wave 1.
4. Power and thermal management are critical for 4×4:4 designs. At 5.1 W active power draw, proper heatsinking (15 cm² minimum surface area) and power supply headroom (2.0 A at 3.3V) are mandatory for reliable 24/7 industrial operation. For battery-powered designs, the 2×2:2 MT7612E at 1.8 W is the appropriate choice.
5. Regulatory domain determines 160 MHz feasibility. Only 10% of industrial Wave 2 deployments operate at 160 MHz due to DFS constraints and co-channel interference. 80 MHz operation at 4×4:4 is the pragmatic default for most applications, delivering 720 Mbps TCP throughput while avoiding DFS complexity.
6. Supply chain outlook supports Wave 2 through 2028. Qualcomm QCA9984 and MediaTek MT7615D remain in active production with no announced last-time-buy dates. Wave 2 is the recommended choice for new OEM/ODM designs requiring 3+ year production continuity. For a complete walkthrough of the customization process, refer to our OEM/ODM WiFi module customization guide.

Refer to the complete WiFi module guide for a cross-generation comparison of module specifications and form factors.

8. Frequently Asked Questions (FAQ)

Authoritative References

1. IEEE Standards Association. “IEEE 802.11ac-2013 — IEEE Standard for Information Technology — Telecommunications and Information Exchange Between Systems — Local and Metropolitan Area Networks — Specific Requirements — Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications — Amendment 4: Enhancements for Very High Throughput for Operation in Bands Below 6 GHz.” December 2013. https://ieeexplore.ieee.org/document/6687187
2. Wi-Fi Alliance. “Wi-Fi CERTIFIED ac: Wi-Fi’s Fifth Generation.” White Paper, 2016. https://www.wi-fi.org/downloads-public/Wi-Fi_CERTIFIED_ac_White_Paper.pdf
3. Qualcomm Technologies, Inc. “QCA9984: 4-Stream 802.11ac Wave 2 MU-MIMO Solution.” Datasheet (Rev. B), 2016. https://www.qualcomm.com/products/technology/wifi/qca9984
4. MediaTek Inc. “MT7615D: 4×4 802.11ac Wave 2 Dual-Band Wi-Fi SoC.” Product Brief (v1.2), 2017. https://www.mediatek.com/products/wifi/mt7615
5. MediaTek Inc. “MT7612E: 2×2 802.11ac Wave 2 Dual-Band Wi-Fi Module.” Datasheet (v1.0), 2016. https://www.mediatek.com/products/wifi/mt7612
6. European Telecommunications Standards Institute (ETSI). “ETSI EN 301 893 V2.1.1: 5 GHz RLAN; Harmonised Standard covering the essential requirements of article 3.2 of Directive 2014/53/EU.” 2017.
7. SmallNetBuilder. “802.11ac Wave 2 Access Point Roundup: Performance Testing.” 2017–2018. https://www.smallnetbuilder.com/
8. FCC. “FCC Part 15.407: General Technical Requirements for Unlicensed National Information Infrastructure (U-NII) Devices.” Code of Federal Regulations, Title 47, Chapter I, Subchapter A, Part 15, Subpart E. 2024.