Choosing Wi-Fi technology for industrial controllers: standards, differences, and practical applications
Wi-Fi is appearing more and more often in industrial controllers not because it is “trendy,” but because it solves real implementation problems: it shortens installation time, simplifies modernization projects (brownfield), enables remote diagnostics and updates, and makes integration with IT/IoT systems easier. In practice, it can be found in controllers for machine and control cabinet monitoring, in IoT gateways collecting data from RS-485/Modbus, in logistics (AGV/AMR, pick-by-light), in energy systems (measurement, switchboards, PV/UPS), as well as in HVAC — including heating boiler controllers, where Wi-Fi connects the device with an app, the manufacturer’s cloud, or a BMS.
Choosing the “right Wi-Fi,” however, is not just about selecting a standard. A controller designer has to balance several areas: band (2.4/5/6 GHz), range and stability in a difficult radio environment, latency and throughput, power consumption (especially in sleep mode and battery-powered systems), system security, as well as costs and the risk of the RF design and certification process. Below, we go through these aspects in a way that can be directly translated into design decisions for typical industrial applications.
What a controller actually sends over Wi-Fi and why it matters
Let’s start by briefly “demystifying” throughput. In many industrial controllers, network traffic is surprisingly small: telemetry (temperature, vibration, currents, input/output states), alarms, control commands, periodic reports, and occasional OTA updates. This means that in a huge proportion of deployments, the real problem is not a “lack of megabits,” but stability, range, and resistance to interference, as well as predictable network behavior when dozens of other devices are operating nearby.
There are, however, classes of applications where requirements increase: mobile robots with higher-frequency telemetry, vision systems, transfer of diagnostic logs, real-time integrations with the edge/IT layer, or intensive OTA updates across many devices at once. And it is precisely at these points that the Wi-Fi standard and band begin to become critical.
Wi-Fi standards in industrial controllers: 802.11b/g, Wi-Fi 4, Wi-Fi 5, Wi-Fi 6/6E, and Wi-Fi 7
In this section, I deliberately provide realistic throughput ranges and practical observations regarding range. In the Wi-Fi world, “PHY throughput” (marketing figures) can be many times higher than what we actually get as real TCP/UDP throughput in a shared network. Additionally, range depends more on the band (2.4/5/6 GHz), antenna, enclosure, and environment than on the standard “number” itself, but the standard affects resilience, efficiency, and behavior in congested conditions.
802.11b/g - why they are still encountered
In industry, 802.11b/g appears mainly in modernization projects and older infrastructure. 802.11g nominally provides 54 Mb/s, but in practice (real application traffic) this is usually a few to several Mb/s, depending on signal quality and network load. Range in 2.4 GHz can be decent, but these standards are less efficient in difficult environments and handle congestion less effectively.
Where does this make sense? In “brownfield” applications, where new controllers have to work with existing access points or client devices, and transmissions are light: simple monitoring, terminals, older HMI/SCADA systems. In new projects, it is usually not worth targeting b/g as the “final” choice, but backward compatibility can still be important because some customer infrastructure still requires it.
Wi-Fi 4 (802.11n) - the industrial workhorse
Wi-Fi 4 is currently the most common choice in embedded controllers. Nominally, it is capable of a lot, but more importantly, it is inexpensive, widespread, and well supported by modules and routers. Realistically, in typical embedded configurations with a decent signal, application throughput in the range of several to several dozen Mb/s is often achievable, which is more than enough for telemetry and control.
Wi-Fi 4 in 2.4 GHz is usually chosen where obstacle penetration matters most (boiler rooms, metal-filled halls, technical rooms), which is why it is a great fit for machine monitoring, control of auxiliary equipment, energy systems, and HVAC, as well as service interfaces (AP mode, local GUI).
Wi-Fi 5 (802.11ac) - when you need stable performance in 5 GHz
Wi-Fi 5 brings a major leap in practical throughput in the 5 GHz band, especially when the infrastructure is good and the 2.4 GHz environment is congested. In real deployments, depending on channel width and conditions, application throughput ranging from tens to over one hundred Mb/s is common in good conditions — and this can matter in IoT gateways, richer diagnostics, frequent OTA updates, or wherever the controller is part of a system with higher data “density.”
In 5 GHz, range and obstacle penetration are usually worse than in 2.4 GHz. This does not mean Wi-Fi 5 is “short-range,” but in halls with metal, shelving, and technical walls, dead zones appear more quickly. That is why Wi-Fi 5 often wins in warehouses and modern production halls with a well-designed AP network, as well as in applications where mobile operation parameters matter (logistics, AGV) and where it is desirable to offload the congested 2.4 GHz band.
Wi-Fi 6 (802.11ax) - efficiency and predictability with many devices
Wi-Fi 6 is less about “maximum megabits” and more about how the network behaves when it is crowded: many devices, lots of short packets, occasional traffic spikes, roaming. This matters in plants where hundreds of Wi-Fi clients are operating (terminals, sensors, service devices), and controllers must maintain predictable communication.
Realistic throughput for a single device can be very high in good conditions, but the biggest difference is visible in latency stability and fairer sharing of the medium. Range still depends on the band; Wi-Fi 6 can operate in 2.4 and 5 GHz, so in 2.4 GHz it can still be “range-oriented,” and in 5 GHz “performance-oriented.”
Wi-Fi 6E (6 GHz) and Wi-Fi 7 - where they actually fit in industry
Wi-Fi 6E brings Wi-Fi 6 into the 6 GHz band, and Wi-Fi 7 goes further (including multi-link operation and wider channel widths). In the context of industrial controllers, this needs to be stated clearly: these technologies most often go not into simple microcontroller-based controllers, but into infrastructure and “heavy” devices — industrial computers, advanced gateways/edge devices, robotics, and vision systems.
Why? 6 GHz usually has lower obstacle penetration, and the chipsets are more expensive and more complex (RF front-end, antennas, testing). Still, where very high performance, low jitter, and operation in an environment where 2.4/5 GHz is congested are important, Wi-Fi 6E/7 can make a lot of sense: vision-based QA, streaming data to the edge, fast data synchronization in modern warehouses, or robotic applications in a well-covered network.
Wi-Fi 8 (802.11bn) - the direction of development
Today, Wi-Fi 8 is worth discussing primarily as an emerging technology. The IEEE 802.11bn standard is still under development, and its main goal is not only to further increase maximum throughput, but above all to improve communication reliability, latency stability, and performance in difficult radio environments. From the perspective of industrial controllers, this sounds very promising, because these features are often more important than “yet more gigabits.” For now, however, Wi-Fi 8 should be treated more as a direction worth watching than as a real option for typical embedded deployments.
| Standard | Band | Strengths | Limitations | Typical industrial applications |
|---|---|---|---|---|
| 802.11b/g | 2.4 GHz | Compatibility with older infrastructure, simplicity of deployment | Lower efficiency, weaker performance in congested environments | Brownfield upgrades, older HMI/SCADA systems, light monitoring applications |
| Wi-Fi 4 (802.11n) | 2.4 / 5 GHz | Mature ecosystem, low cost, broad support, a good compromise between range and performance | Lower efficiency than Wi-Fi 6 in networks with high device density | Machine monitoring, HVAC, energy systems, embedded controllers, OTA, service interfaces |
| Wi-Fi 5 (802.11ac) | 5 GHz | High efficiency, less congestion than 2.4 GHz, good conditions for higher data traffic | Weaker obstacle penetration, higher infrastructure requirements | Logistics, warehouses, IoT gateways, more demanding diagnostics, more frequent OTA |
| Wi-Fi 6 (802.11ax) | 2.4 / 5 GHz | Better performance with many devices, more predictable communication, higher medium efficiency | Higher cost and greater complexity than Wi-Fi 4 | Modern plants, environments with a large number of Wi-Fi clients, more advanced IIoT systems |
| Wi-Fi 6E (802.11ax) | 6 GHz | Very high efficiency, low congestion in new infrastructure | Weaker obstacle penetration, higher RF requirements, higher deployment cost | Advanced gateways, edge computing, selected vision systems, and high-end industrial applications |
| Wi-Fi 7 (802.11be) | 2.4 / 5 / 6 GHz | Very high efficiency, low jitter, advanced multi-band operation | High cost, high complexity, limited practical usefulness in typical embedded controllers | Robotics, vision systems, high-end infrastructure, industrial PCs, data-heavy applications |
2.4 GHz vs 5 GHz vs 6 GHz - how to think about the band in typical applications
In practice, the band is one of the most important decisions. Put simply: the higher the frequency, the more “room” there usually is for throughput, but the harder it is to achieve range and penetration. In industrial environments, multipath propagation, reflections from metal, enclosure attenuation, and interference also come into play.
2.4 GHz most often wins in controllers because it “reaches farther” and passes through obstacles better. It is ideal for telemetry and control in distributed points: machine monitoring, energy systems, HVAC, and boilers (boiler rooms are often in basements, behind technical walls). The downside is congestion: many consumer and industrial devices, and sometimes interference from other systems.
5 GHz is often chosen when the controller operates in an environment with good AP infrastructure and there is a need for more stable performance, lower congestion, or better roaming. It is a good direction for warehouses, logistics, AGVs, and IoT gateways that transfer more data or handle multiple streams at once. However, it must be taken into account that 5 GHz coverage usually requires a denser grid of access points.
6 GHz (Wi-Fi 6E/7) is a “premium” band in which excellent performance can be achieved in a new, well-designed network — but it is also the most demanding in terms of range. In controllers, it typically appears when the device is by definition “data-hungry” (e.g. vision-based quality control systems) or when we design a complete ecosystem (device + infrastructure) and can guarantee the radio conditions.
Wi-Fi range in industry: numbers are not enough, the scenario matters
In industrial controllers, range is often underestimated at the prototype stage, because tests in the office go great, and then the device ends up in a metal cabinet, next to a frequency inverter, in a boiler room, or on a production floor full of reflections. Instead of asking “how many meters,” it is better to think in terms of the scenario:
- Will the controller be inside a metal enclosure or near large metal surfaces?
- Does the signal need to pass through several technical walls or a floor/ceiling?
- Is the device mobile, making roaming and stable latency critical?
- Are many networks and clients operating in the same area (dense warehouse, nearby office buildings)?
In practice, if the priority is a reliable connection “in difficult locations,” 2.4 GHz and a well-designed antenna offer the most. If the priority is predictable performance in congestion, a sensibly designed 5 GHz network (Wi-Fi 5/6) can deliver better quality of service, but usually at the cost of denser infrastructure.
Antenna - the underestimated element that can “kill” even the best standard
Many problems attributed to “weak Wi-Fi” are in practice antenna, RF integration, and enclosure mechanics problems. This part can be decisive հատկապես in industrial controllers, where enclosures are metal and devices operate close to EMI sources.
A PCB antenna is cheap and convenient, but very sensitive to what is happening around it: PCB dimensions, ground plane presence, distance from metal elements, wires, connectors, and even the hand of a service technician. An external antenna (or one brought out to a connector), on the other hand, increases the chances of predictable range, especially when the controller is mounted in a metal cabinet or near large metal elements.
In a project, it is worth treating RF as a separate sub-discipline rather than a “small detail.” Most often, it pays to pay attention to three things: the proper antenna clearance zone, sensible RF line routing and impedance matching, and the influence of the enclosure. The gains from moving from Wi-Fi 4 to Wi-Fi 6 will be useless if the antenna “sees metal” a few millimeters away or if the module is shielded like in a Faraday cage.
Certification and regulatory requirements: the cost, time, and risk of the RF project
For R&D managers, this is one of the most “hard” arguments when choosing a technology: the standard and band affect the complexity of testing, and the way RF is implemented (module vs custom design) affects the schedule. In short: in Europe, radio devices are subject to CE/RED requirements, and for exports to the USA, FCC requirements apply. On top of that comes EMC compliance, which is particularly demanding in industry because the environment is “noisy” and devices often operate next to converters, inverters, and contactors.
In practice, there are two paths. The first is ready-made, pre-certified Wi-Fi modules that already have some of the radio testing behind them. This is often the fastest and most cost-effective way to enter the market, because it limits the risk of iterations and lab surprises. The second path is a custom RF design (chip + antenna + layout), which may provide greater control over BOM and mechanics, but usually means more work, greater risk, and a longer validation cycle.
In the decision-making process, it is worth emphasizing that band selection also has consequences: 6 GHz and more complex standards often mean more demanding RF integration and testing. That is why in many industrial controllers, where reliability and deployment time are key, Wi-Fi 4/5 in 2.4/5 GHz on proven modules still wins.
Security at the system level: Wi-Fi is just one part of the puzzle
In industrial controllers, security does not end with “we’ll enable WPA2/WPA3.” You need to look at it systemically: from the firmware chain of trust, through OTA updates, to network segmentation and minimizing the attack surface.
Good practices include limiting network services to only those that are necessary, encrypting application communication (e.g. TLS in MQTT/HTTPS), secure key storage, and update control (signatures, integrity verification). In applications such as boilers and HVAC, the aspect of privacy and secure remote access also comes into play, because devices often communicate over the internet with the manufacturer’s cloud or a service app. In heavy industry, on the other hand, separation from the office network and a clear service access policy are critical, because Wi-Fi can be “the easiest route” to the device.
The practical conclusion is simple: even if we choose Wi-Fi 4, a secure system can be built; and even if we choose Wi-Fi 7, a secure system will not build itself. The Wi-Fi standard helps, but it does not replace a security architecture.
Power consumption: when Wi-Fi becomes the biggest burden
In mains-powered controllers, the topic of energy is often pushed into the background, but in practice it matters in three scenarios. First, when the device is battery-powered or has backup power. Second, when it spends most of its time in sleep mode and wakes up periodically to send a data packet. Third, when it is part of an edge node and communicates intensively with the network, because then the radio can dominate the energy and thermal budget.
Wi-Fi in higher standards and bands can increase energy complexity, but the key is the device’s behavior: how often it connects to the AP, whether it maintains a constant connection, what the security handshake looks like, whether it buffers data and sends it in “batches,” and whether OTA is planned in service windows. In practice, if a device has to run for a long time on a battery, other radio technologies are often considered, and if Wi-Fi must remain, it is designed to minimize active transmission time and the number of wakeups.
How to match the technology to typical industrial applications
Instead of multiplying lists, it is worth adopting a simple logic: most industrial controllers can be divided into those that send little data but must work “everywhere,” and those that send more data and operate in environments with good infrastructure.
The first group includes machine monitoring, energy systems, HVAC/boilers, auxiliary control, and local service interfaces. Here, 2.4 GHz and Wi-Fi 4 standards (and sometimes backward compatibility down to g) usually work best. The priority is range, resilience to installation conditions, and predictable operation in difficult locations.
The second group includes IoT gateways with higher traffic, logistics, some AGV systems, and deployments in modern warehouses and production halls with well-designed Wi-Fi. Here, it often makes sense to move to Wi-Fi 5 or Wi-Fi 6 in 5 GHz, because we gain better performance and behavior in congestion, but it must be accepted that this requires better network coverage and more careful RF planning.
In practice, Wi-Fi 6E/7 appears when we are building a system with high data requirements (vision-based QA, edge systems with large volumes of data) and at the same time have control over the infrastructure. In typical “microcontroller-based” controllers, this is still rare, and if it does appear, it is more likely in gateway/industrial PC-class devices than in simple IO controllers.
Summary: the decision that pays off the most
In industrial controllers, the best Wi-Fi choice is usually not “the highest standard number,” but a combination of three things: a band matched to the environment, RF architecture (antenna + integration), and smooth passage through certification and EMC. That is why, in practice, Wi-Fi 4 in 2.4 GHz still very often wins — because it provides good range, stability in difficult installation conditions, broad compatibility, and a predictable deployment cost. Wi-Fi 5 and Wi-Fi 6 are an excellent step forward where network behavior with many devices and higher traffic matters, especially in 5 GHz, while Wi-Fi 6E/7 are tools for high-end scenarios where the infrastructure and application justify that complexity.