Product Engineering · 802.11ac

What Products Can Be Built With a Wi-Fi 5 Module? A Practical Engineer’s Catalogue

Published by Zukaka  ·  Last updated August 22, 2026  ·  22 min read

A decade after 802.11ac shipped, its modules are still the quiet workhorses of embedded wireless. The reason is a balance the newer generations spend more watts and silicon to reach: genuine dual-band throughput around one gigabit, multi-user MIMO, a rock-solid ath10k/Linux driver base, and a Mini-PCIe or half-height card that drops into an existing carrier with ~5 W typical power. This guide walks seven products you can actually build with that platform today, using capability figures you can verify and a refusal list that keeps you out of the corners where Wi-Fi 5 is the wrong tool. Each entry follows the same quick scan — the core job, what the module actually delivers, and the specific condition under which you would upgrade — so you can treat the whole page as a decision cheat-sheet rather than a sales tour.

One framing note before the catalogue: product fit and spec-sheet impressiveness are different axes, and this guide optimizes for the former. A module only matters relative to the job it carries — so each product below is defined by its job first, and the module’s numbers are cited only where they actually bind (link budget, power, thermal, driver, form factor). Where a number does not bind the product, we say so plainly rather than lean on it.

The Wi-Fi 5 module baseline that everything hangs on

Every product below rests on the same platform spine. The exemplar is the Qualcomm QCA9880 a 3×3 mini/PCMCIA-ac 802.11ac wave-1 part, whose datasheet numbers define what you can count on before you touch an enclosure:

Three of those rows deserve emphasis because they cascade into the product catalogue:

• 3×3 with ~1.3 Gbps. Three streams give real multi-antenna spatial benefit — better reach and resilience in multipath than a 2×2 client, which matters for AP and bridge roles.
• Proven dual-band at ~5 W. A modest power and thermal budget means the module fits passively cooled outdoor APs and vehicle boxes without exotic heatsinking — a key constraint for the products that follow.
• ath10k and OpenWrt. A mature, audited Linux driver path gives you mesh, custom QoS, roaming and security-patch cadence without a closed SDK — decisive for long-lifecycle infrastructure.

The corollary ceiling: no 6 GHz, no 1024-QAM, and peak 256-QAM 80 MHz service. That honest cap is exactly what the “wrong tool” section at the end turns into a rule.

Outdoor wireless AP and CPE

The first and clearest Wi-Fi 5 product is the outdoor access point or customer-premises unit — a pole-top or wall-mounted radio reaching subscribers or guests. Without making up field numbers, the engineering fit is straightforward against the table:

• Throughput is ample. A 3×3 802.11ac AP at 80 MHz serves typical residential or small-business client loads comfortably; the module stays calm at ~5 W, and an I-Temp build (industrial range) survives a sunlit enclosure.
• MU-MIMO is a wave-2 accent, not a blocker. A wave-1 QCA9880 is single-user MIMO, which is fine for the client counts of a small AP; a denser site just steps up to a wave-2 part — the Wi-Fi 6 / 6E module profile in this series covers that jump.
• The real work is the enclosure, not the radio. Outdoor APs live inside the metal/plastic and antenna story explained in the enclosure RF guide; the Wi-Fi 5 radio simply provides a stable, proven RF core.

The one honest gap worth naming: this 802.11ac AP tops out where clients are dense and the uplink is narrow. It is the right module for cost-conscious, one-radio-per-site outdoor service — and a capable but second-tier choice for a multi-gig campus floor. If your outdoor product is a single-radio CPE feeding a modest subscriber count, the module’s dual-band, ~1.3 Gbps PHY and I-Temp option are more than enough, and the price and thermal budget are the real deciders.

Vehicle and transport terminals

Buses, rail fleets and last-mile logistics share a harder radio problem: a radio must roam across infrastructure while serving passengers on its own access point — two jobs a dual-band 802.11ac module handles by giving each a band. This is the classic dual-radio-by-band split:

• Backhaul rides one band (say 5 GHz) talking to roadside or depot infrastructure as a station.
• Passenger access rides the other band (2.4/5) as an independent AP, so riders connect to the moving network.

Vehicles add brutal mechanical realities that the module’s temperature and vibration rating carry — the reason I-Temp and the rugged Mini-PCIe form factor matter here more than the radio’s Mbps. Rust, heat soak and motion decide survival; the Wi-Fi 5 platform’s ~5 W and durable footprint keep it viable for transport. If the vehicle also needs Bluetooth for diagnostics or pass-through, combine with a BLE part — see the specialist module field guide. And because a moving bus or train repeats the same handover thousands of times a day, the availability of proven 802.11r fast-roaming — backed by the mature ath10k stack — is a genuine reliability feature for this role, not a footnote.

Industrial IoT and automation gateways

An IIoT gateway sits on a factory or field site, collecting sensor/PLCs/MES data and delivering it over a dependable Wi-Fi uplink. Wi-Fi 5 wins here not on peak speed but on determinism and longevity:

• Determinism under modest load. Sensor telemetry is small-packet and delay-tolerant; a 3×3 ac part has huge airtime margin for this, and the mature driver handles many concurrent clients predictably.
• Longevity and I-Temp. Industrial products live 7–10 years, run −40 °C to +85 °C, and need a driver/security patch path for their whole life. An 802.11ac module with ath10k in mainline Linux and a dual-sourced footprint is the safe bet here; the temperature and lifecycle reasoning is expanded in the industrial module temperature guide.
• Roaming and failover. Meshing or failover across access points is well-supported by the driver stack, which is hard to replicate cheaply with a closed platform.

The honest limit: if your gateway must push many concurrent high-rate streams (multi-camera analytics), the per-client and aggregate ceilings of 802.11ac bind. For the dominant telemetry model — many small packets, tolerant latency, long life — Wi-Fi 5 is still a rational, costed choice.

Point-to-point and point-to-multipoint bridges

Bridging two buildings, linking a camera to a switch, or running a polled PtMP sector to distributed clients is the role where 802.11ac’s per-chain power and driver maturity shine hardest. The operative number is link budget, not headline speed:

Two engineering truths make bridges a Wi-Fi 5 habit:

• Directional gains and module power compound. A high-gain sector plus a solid per-chain TX turns a modest radio into a multi-hundred-metre link; the trade-offs of 5 vs 6 GHz for reach are covered in the wireless bridge guide.
• PtMP needs a sector and good scheduling. 802.11ac’s driver and MAC handle polled point-to-multipoint timing well on mature code. For latency-critical PtMP, Wi-Fi 6’s OFDMA is genuinely better — an honest upgrade rule rather than a Wi-Fi 5 failure.

Bridging is also where the “no 6 GHz” ceiling is felt most: in markets that opened 6 GHz, a clean wide channel can outrun 5 GHz contested spectrum. If your bridge needs maximum greenfield throughput and the band is legal, step up a generation.

Single-board-computer expansion

The prototype-to-product bridge is the SBC tier: Raspberry Pi/NXP/i.MX-class boards, industrial single-board computers, and bring-your-own carriers that need a drop-in wireless card. This is the easiest Wi-Fi 5 slot to justify, because the interface and driver fit perfectly:

• Mini-PCIe fits the carriers. An 802.11ac Mini-PCIe card is a known quantity for countless ARM SBC carriers and OpenWrt boards.
• ath10k is supported out of the box. No proprietary userspace daemon; your OS image and updating pipelines just include the kernel module. Development is fast, and management via standard Linux wireless tools is complete.
• Cost and availability. Mature 802.11ac modules are among the cheapest, and dual-sourced, wireless modules you can stock — the choice for a high-volume device that only needs dependable gigabit Wi-Fi. The module selection guide covers how to compare generations for exactly this build.

The upgrade path is simple: when a product must jump to Wi-Fi 6, an M.2 or Mini-PCIe ax module swaps in where the board and uplink allow — but for most SBC-based devices shipping today, the 802.11ac card still does the job at the best price.

Surveillance and video backhaul

IP cameras and the links that carry their streams care about sustained uplink bandwidth and low jitter more than burst speed. A 3×3 802.11ac module reliably transports multiple video streams:

• Headroom for a camera fleet. With a gigabit-class PHY and dual-band, one radio can backhaul several HD streams (each just a few Mbps) to a switch — this is the surveillance-body of the bridge role.
• Deterministic uplink framing. Mature driver and MPDU handling keep packet flow predictable, meeting the jitter needs of live viewing.
• The honest cap is aggregate and density. For a dense multi-camera AI site or 4K/8K continuous recording, a single 802.11ac radio’s airtime binds; that is a Wi-Fi 6/6E dense-site job and is covered in the tri-band Wi-Fi 6E profile.

For the common perimeter- or multi-camera backhaul install — a handful to a few dozen streams to one aggregation point — Wi-Fi 5 is a proven, cost-efficient core. The multi-device access gateway walk-through shows how such a radio aggregates many edge clients.

Smart-city and public-infrastructure devices

The final category collects controllers with a wireless link to the street: lighting nodes, signage, traffic sensors, environmental monitors, kiosk connectivity. These are high-proliferation, low-cost, low-throughput products where the decisive virtues of 802.11ac are power, price and protocol support:

• Low per-node power. A ~5 W radio and a small controller make for a solar- or mains-thrifty node — critical at street scale. The smart street-lighting remote management guide details this exact node/controller split.
• Many, many peers on one resilient platform. The mature driver and OpenWrt mesh capabilities suit a fleet of thousands of identical nodes with standard, patchable software.
• Wide dual-band and I-Temp. Outdoor poles push enclosure temperatures and band congestion; 5 GHz for data and 2.4 GHz for legacy/control give the controller flexibility.

The refusal is density-and-beacon issues at enormous scale, and the modern 6 GHz choice where that band is open. But as the backbone of distributed public-infrastructure nodes, Wi-Fi 5 remains a widely used, well-understood foundation.

Power and thermal planning that ships

Every product on the list is decided at the edges by watts and degrees, not by the dashboard megabytes. Getting these two right ahead of the build is cheap; fixing them after a prototype is expensive.

Budget the rail, not the radio alone. A 3×3 802.11ac module at ~5 W typical (and up to 5–10 W in sustained high-rate TX) is modest by itself, but it sits on a carrier with a CPU, ethernet, and maybe power-over-ethernet (PoE) front end. The rule of thumb for an outdoor AP or gateway: size the power supply for the peak simultaneous draw of every rail, and confirm the PoE class/PSE can deliver it over the intended cable length — a common cause of intermittent wireless resets under load.

Thermal is the outdoor reality. Indoors, ~5 W vanishes into a case. Outdoors, the same watts sit inside a sealed box in direct sun, so the whole-ground decider is the module’s operating-range headroom. An I-Temp part (−40 to +85 °C die-limited range) leaves margin even when the enclosure rises to 60–70 °C; a commercial part (−20 to +70 °C) may throttle just when you need sustained throughput. This is the exact reasoning the industrial temperature guide walks through, and it applies to all seven categories on this shelf.

Security, roaming and deployment beyond the one-box

Three network-level capabilities separate a Wi-Fi 5 module that enables a real product from one that only lights up a dashboard. They run on the radio’s firmware/driver, so the module choice largely determines how far you can go:

• WPA2 and path to WPA3. The staple enterprise mode — 802.1X/EAP with WPA2 — is mature across ath10k/mac80211. Confirm the module and your clients support the WPA3 minimum your security policy mandates before locking the BOM, since a wave-1-era platform may need a firmware revision for the very latest profile.
• Fast roaming for moving vehicles. Vehicle terminals and fleet nodes depend on low-latency handover between APs. 802.11r and OKC-based fast transition are well-supported, keeping a moving device from dropping on every cell edge — the practical backbone of the transport role above.
• Mesh to cover ground cheaply. OpenWrt wireless mesh lets one wired AP subsidize a field of meshed nodes, which is how smart-city and broadcast-scope ideas keep cost per square kilometre down. The module’s dual-band and ath10k flexibility make it a good mesh building block.

These matter because they are product features: the difference between a single radio and a deployable system is often roaming, mesh and security posture, all governed by the same driver stack you picked earlier.

A rough bill-of-materials look

Cost is usually the quiet reason 802.11ac still wins, so it is worth a rough, named view of where the money goes. Exact numbers move with markets, but the shape of the comparison is durable:

The honest caveat: for the specific products that genuinely need multi-gig or 6 GHz, the newer radio’s capability justifies its premium. But for the seven routine categories on this shelf — where a mature gigabit radio, open drivers, simpler cooling and certified prior art suffice — the total cost of ownership frequently lands lower on 802.11ac, which is precisely why the platform is still in production at scale.

Seven products, one comparison table

Read the last column as the honest ceiling: in every category the module is the right value today, and the upgrade is a specific, nameable condition — a dense floor, a latency-critical sector, multi-gig demand — not a generic “newer is better”. For most products listed, that condition is not met, and 802.11ac remains the financially and technically sound core.

When a Wi-Fi 5 module is the wrong choice

Naming the counter-cases keeps this catalogue honest. Reach for a newer generation when any of these hold:

• You need multi-gig aggregate or per-client speed. The 1.3 Gbps PHY and 5–10 W budget cannot feed or run multi-gig service; step to Wi-Fi 6/6E.
• 6 GHz greenfield is open and you want it. A clean, wide 6 GHz channel beats contested 5 GHz for reach and latency — Wi-Fi 6E / 7 territory.
• Dense many-client latency matters. MU-OFDMA in Wi-Fi 6 schedules many small clients far better than wave-1 single-user 802.11ac.
• WPA3-only or very latest security mandates. Confirm your client and driver support the exact security profile before locking 802.11ac.

The first two are about capacity ceiling, the last two about protocol features — and together they are a handy classifier. If your requirement is mostly “dependable gigabit at cheap watts with a proven driver,” you are in Wi-Fi 5 territory and a newer radio is overspend. If your requirement is “multi-gig / greenfield 6 GHz / very dense micro-latency,” you are genuinely outside what wave-1 802.11ac can deliver, and the upgrade is justified on engineering grounds, not fashion.

A short gate review for your product

1. Confirm the interface. Mini-PCIe vs the newer M.2 (Key A/E) your carrier exposes.
2. Size the uplink. A gigabit-class PHY throttling behind a 100 M port is wasted radio.
3. Match temperature grade. I-Temp (−40 to +85 °C) for outdoor/pole/vehicle; commercial indoor otherwise.
4. Validate the driver path. ath10k’s OpenWrt/mainline support for your OS image and update cadence.
5. Confirm the security profile. WPA2/WPA3 support on both module and the target clients.
6. Test in the real enclosure. Antenna-on-box receive sensitivity and thermal soak, as in the complete selection guide.
7. Tally total cost of ownership. Price, dual-source, cert reuse and CVE-patch responsibility over the product’s lifetime.

A qualification pass for your Wi-Fi 5 product

The catalogue above tells you a product is buildable; this pass tells you the one radio is right before you go to production. A compact, repeatable qualification has a handful of gates, and each maps to a datasheet line you already saw:

1. Throughput at distance. Measure sustained TCP/UDP in both directions at 5, 20 and 40 m indoor, and across the enclosure, recording which MCS the link settles at. Compare against your application’s need — most telemetry products need far less than the module’s ceiling.
2. Thermal soak at duty cycle. Run the unit at its rated upper temperature while sustaining your worst-case stream and confirm no MCS collapse. This turns the temperature-grade row into a real decision, not a sticker.
3. Roaming seam. For vehicle/fleet products, drive (or simulate) handover between two APs and confirm Roam/Roam time fits your session-liveness budget.
4. Power-rail validation. Log the rail at peak TX with a scope/MDM to confirm you sized the power supply and PoE class for simultaneous load — the classic intermittent-reset cause.
5. Certification and spectrum. Re-test any antenna or enclosure change, as the metal enclosure RF guide stresses; and verify the target country’s band/EIRP rules for the 5 GHz channels you intend to enable.
6. Driver and update drill. Confirm your OS image builds ath10k, that you can push a firmware/security update OTA, and whom to hold accountable for CVEs for the product’s life.
7. Dual-source and end-of-life. Qualify a drop-in alternate at the same MCS/thermal points before the BOM locks, as the specialist module guide explains, so one supply shock cannot strand your build.

A radio that clears this pass is ready to ship. One that does not has just saved you the far more expensive failure of discovering it in the field — and the gate you fail tells you exactly which upgrade (a better antenna, a higher temperature grade, or a newer-generation module) is the honest fix rather than a guess. It also gives you the evidence to defend that upgrade to a budget owner, because a failed gate is a concrete, measured reason — not an opinion.

Frequently asked questions

What can you build with a Wi-Fi 5 (802.11ac) module?

A Wi-Fi 5 module such as the Qualcomm QCA9880 (3×3, dual-band, ~1.3 Gbps at 80 MHz, ~5 W) is a proven core for outdoor APs and CPE, vehicle and transport terminals, IIoT and automation gateways, point-to-point bridges, SBC expansion, surveillance backhaul and smart-city infrastructure nodes.

Is Wi-Fi 5 still worth using in 2026?

For many products, yes. Wi-Fi 5 wins on power, price, driver maturity and longevity: the QCA9880-class platform runs on the audited open-source ath10k/OpenWrt path with I-Temp (−40 to +85 °C) options, and it is among the cheapest dual-sourced modules you can stock. Its honest caps are no 6 GHz, no 1024-QAM and single-user (wave-1) MIMO.

What are the limitations of a Wi-Fi 5 module?

The corollary ceiling is no 6 GHz, a peak of 256-QAM at 80 MHz, and single-user MIMO on wave-1 parts. That binds dense multi-camera AI sites and greenfield high-throughput deployments, where a multi-gig Wi-Fi 6/6E or Wi-Fi 7 radio is the honest upgrade. For latency-critical point-to-multipoint, Wi-Fi 6’s OFDMA scheduler is genuinely better.

How many clients can a Wi-Fi 5 access point serve?

A 3×3 dual-band 802.11ac AP comfortably handles modest counts — roughly 20–40 concurrent devices typical for a small AP, CPE or vehicle terminal, and many small-packet sensors on an IIoT gateway. For 80+ clients or dense multi-flow load, a multi-user (MU-MIMO/OFDMA) Wi-Fi 6/6E radio is the step-up.

Why is the QCA9880 considered a good industrial Wi-Fi 5 choice?

The QCA9880 is a 3×3 802.11ac Mini-PCIe module with ~20–21 dBm per chain, ~5 W typical draw, dual-band, and I-Temp (−40 to +85 °C) variants. Its mature ath10k/OpenWrt driver path supports mesh, roaming and security patching for a 7–10-year industrial lifecycle without a closed SDK.

Glossary

Wi-Fi 5 (802.11ac)

— the 802.11ac standard; 2.4/5 GHz, 80/160 MHz channels, 256-QAM, wave-1/wave-2 releases.

Wave 1 / Wave 2

— two 802.11ac releases; wave 2 adds 160/80+80 MHz, 4×4 and DL MU-MIMO.

PtMP

— point-to-multipoint; one base serving several remote clients (polled or spatial).

Link budget

— available margin = TX power + gains − path and system losses − sensitivity.

ath10k

— the mainline Linux kernel driver for Qualcomm 802.11ac wireless devices.

I-Temp

— industrial-temperature operating range, typically −40 to +85 °C.

RSSI / MCS

— receive signal strength, and the modulation-coding rate a link sustains at it.

Related Reading

• The complete enterprise WiFi module selection guide
• Choosing the right WiFi module generation
• 2×2 vs 3×3 vs 4×4 MIMO explained
• Wireless AP board RF performance and cost
• Specialist module field guide (CPE, bridge, combo)
• Rural 6 GHz wireless bridge guide

Sources & further reading

• Qualcomm, QCA9880 802.11ac WLAN SoC product brief — qualcomm.com
• Compex Systems, WLE900VX Wi-Fi 5 (802.11ac) industrial module data sheet — PDF
• Linux Wireless, ath10k driver — wireless.wiki.kernel.org
• Wi-Fi Alliance, Wi-Fi generations — wi-fi.org
• IEEE, 802.11ac amendment — IEEE 802.11

Values are representative catalogue figures from vendor data sheets and public sources, and vary by exact part, build and region. Always validate throughput, power, temperature, driver and certification against the specific module ordered before committing a board. 6 GHz operation and band allocations are subject to local regulation.