Industrial Wireless Gateways: Connecting the IIoT in Harsh EnvironmentsIndustrial Wireless Gateways: Connecting the IIoT in Harsh Environments

By Dustin Guttadauro, Product Line Manager - Telecom & Fiber, Infinite Electronics  

There's a specific problem that comes up constantly in brownfield IIoT projects: you have a Modbus RTU device on an RS-485 bus that's been running reliably for 15 years, you need its data on a cloud platform for predictive maintenance, and nobody wants to replace the device. The field device works. The protocol works. What's missing is the bridge between the OT world it speaks and the IP world everything else expects. 

That's what an industrial wireless gateway does. It sits between the legacy field device and the IP network — translating protocols, managing connectivity, and surviving the physical environment in between.  

What Does an Industrial Wireless Gateway Do? 

An industrial wireless gateway performs two functions simultaneously: protocol translation and wireless connectivity. Strip away the marketing language, and that's the product. 

Protocol Translation: Bridging OT and IP 

Most OT field devices speak protocols that predate modern IP networks. Modbus RTU, developed in 1979, runs over serial RS-485 or RS-232 links. PROFINET and EtherNet/IP are Ethernet-based but use application-layer protocols that don't map natively to standard IT infrastructure. A SCADA server or cloud platform expecting JSON over MQTT or RESTful API calls can't talk directly to a Modbus RTU device. 

The gateway handles this translation. On one side, it speaks the OT protocol — polling Modbus registers, consuming PROFINET I/O data, reading EtherNet/IP tags. On the other side, it publishes that data in a format the IP network understands: OPC-UA, MQTT, HTTP, or a direct database write. The field device doesn't need to change. The gateway does the conversion. 

Wireless Connectivity: Replacing or Supplementing Cable Runs 

Wireless connectivity solves the cable problem. Some installation points are genuinely impractical to cable: a sensor on a rotating assembly, a meter in a utility vault with no conduit path, and a remote pumping station 10 kilometers from the nearest wired infrastructure. Others are theoretically capable, but the installation cost — trenching, conduit, and pull-through a busy production facility — is prohibitive relative to the monitoring value. 

A wireless gateway at those locations provides network connectivity without requiring a cable run. The gateway connects to the field device (often by a short local cable or serial connection) and transmits data wirelessly to a local access point, a cellular network, or a long-range IoT radio network. 

 Edge Processing: Optional but Increasingly Common 

Higher-end industrial gateways add a third function: local computation before data is transmitted. Rather than streaming every raw sensor reading to the cloud, the gateway applies filtering, aggregation, or anomaly detection locally — forwarding only significant events or summarized data. This reduces bandwidth costs, lowers cloud storage requirements, and maintains basic operation when the WAN link is unavailable. 

Edge processing capability varies significantly across gateway products. For simple data forwarding, it's not needed. For applications where the cloud is the primary processing platform but WAN reliability is uncertain, local buffering and pre-processing are worth the added cost. 

How Does a Gateway Translate OT Protocols to IP Networks? 

The protocol translation layer is where gateways earn their keep in brownfield IIoT deployments. Here's how the most common OT protocols map to IP network targets: 

A few practical notes on protocol translation: 

•       Modbus RTU to Modbus TCP is the most common gateway translation in manufacturing. It's well-supported across gateway products and the conversion is straightforward. If this is your only requirement, gateway selection is primarily a hardware and connectivity decision. 

•       OPC-UA is the preferred target protocol for most modern IIoT platforms and cloud integrations. A gateway that outputs OPC-UA gives you a standard interface that works with virtually any upstream system — SCADA, historian, cloud IoT platform, digital twin software. 

•       MQTT is the right target for high-frequency telemetry to cloud platforms (AWS IoT, Azure IoT Hub, Google Cloud IoT). It's lightweight, efficient over constrained bandwidth, and supported by most industrial IoT platforms. 

•       4–20 mA analog signals require a gateway with analog input hardware — not all gateways have this. A gateway that handles Modbus TCP but lacks analog inputs can't connect a 4–20 mA pressure transmitter directly. 

Which Wireless Standard Should You Use? 

Wireless standard selection is a requirements question. There's no universal right answer — the correct standard depends on your data rate, range, latency, power availability, and existing infrastructure. Here's how they compare: 

When Wi-Fi 6 Is the Right Choice 

Wi-Fi 6 makes sense when you have existing wireless infrastructure in the facility and your IIoT devices are within coverage range of access points. It's the highest-bandwidth option at short range, which matters for applications sending large data volumes — video from a vision camera, high-frequency vibration data from an accelerometer, or image data from a process inspection system. 

The constraint is infrastructure dependency. A Wi-Fi 6 gateway needs a nearby access point with good signal quality. In facilities with variable RF environments – lots of metal, moving equipment, interference from welding or VFDs — Wi-Fi 6 reliability depends heavily on a proper RF site survey and AP placement. Don't install a Wi-Fi 6 gateway and assume coverage exists. 

When Cellular (4G LTE or 5G) Is the Right Choice 

Cellular is the standard for remote sites without existing wireless infrastructure and for applications requiring wide-area coverage across large facilities or between facilities. A cellular gateway with a SIM card provides WAN connectivity wherever the carrier network has coverage — no AP infrastructure, no campus network planning. 

4G LTE is sufficient for most IIoT monitoring applications. 5G adds lower latency and higher throughput — relevant for video-intensive applications or private campus networks where latency approaches those of wired connections. For simple sensor telemetry over cellular, 4G LTE is usually the cost-effective choice. 

Cellular gateways for remote or unattended sites should have dual-SIM capability (failover to a secondary carrier if the primary loses signal) and a hardware watchdog that restores connectivity automatically after power events or cellular drops. 

When LoRaWAN Is the Right ChoiceLoRaWAN Is the Right Choice 

LoRaWAN is purpose-built for the problem nobody else solves well: sensors that need to transmit small amounts of data infrequently, over long distances, running on battery power. A tank level sensor at the far end of a storage yard, a temperature sensor in a cold storage facility, a vibration sensor on outdoor rotating equipment — these are LoRaWAN applications. 

The bandwidth limitation is real: LoRaWAN is not suitable for streaming data, video, or any application requiring more than a few hundred bits per second. What it offers instead is range (several kilometres in open environments), very low power consumption (battery life of years on AA cells for infrequent sensors), and the ability to cover large physical areas with a single gateway serving hundreds of end nodes. 

What Environmental Specifications Actually Matter for Industrial Installations? 

This is the section that determines whether the gateway you've specified is still working 18 months after installation. Consumer and commercial gateways fail in industrial environments — not because they're missing features, but because they're not built for the conditions. Here's what to check and why each spec matters at specific installation points: 

The Antenna Problem Most Installations Get Wrong 

A gateway specified with good RF performance, installed in a steel enclosure, with the internal antenna enclosed in metal, will have poor RF performance. This sounds obvious, but it's one of the most common installation errors in industrial wireless deployments. Metal enclosures block radio signals. The solution is external antenna connectors (N-type or SMA) with the antenna mounted outside the enclosure on a bracket or mast, connected by a short RF cable. The antenna location — its height, clearance from metal structures, and line-of-sight to the access point or cell tower — determines the signal quality the gateway sees in actual operation. For challenging RF environments (large metal structures, mobile equipment, dense machinery), a site survey with a spectrum analyzer before installation is not optional. The few hours it takes to survey and plan antenna placement prevents weeks of troubleshooting after installation. 

What Does an Industrial Wireless Gateway Installation Look Like in Practice? 

A mid-size food processing facility needs predictive maintenance data from 40 motors spread across a production floor and a refrigerated warehouse. The motors have vibration and temperature sensors communicating over Modbus RTU on RS-485 buses. The existing plant network doesn't reach the warehouse. 

•       Eight industrial wireless gateways are mounted on DIN-rail inside NEMA 4 enclosures at distribution points across the facility. Each gateway handles five sensors via Modbus RTU polling on the local serial bus. 

•       The gateways use Wi-Fi 6 in the main production area, where existing AP infrastructure provides coverage. In the refrigerated warehouse — where running new AP cabling was impractical — two gateways use cellular LTE for WAN connectivity. 

•       All gateways are specified with IP67 ratings (the warehouse reaches 0°C and has condensation), wide-temperature DC power inputs (fed from the 24V DC bus in each panel), and external antenna ports with roof-mounted antennas for the cellular units. 

•       Data is published via MQTT to an edge server, which runs anomaly detection before forwarding alerts to the cloud platform. The gateways buffer locally if the WAN link drops — the maintenance team gets data gaps flagged rather than silent failures. 

The project took six weeks from specification to operational. The main delays were antenna placement planning for the cellular units and validating the Modbus RTU polling configuration against the sensor firmware. The gateways themselves installed in a day per location. 

How Do You Connect Legacy OT Equipment Without Replacing It? 

The concern that comes up most often in brownfield IIoT projects is whether existing equipment has to be replaced to gain connectivity. It usually doesn't. 

A gateway with the right serial ports can read Modbus RTU data from a PLC installed in 2001 with no modification to the PLC. The gateway polls the PLC's registers on the existing RS-485 bus, translates the data to MQTT or OPC-UA, and forwards it to a cloud platform. From the PLC's perspective, it's just another device on the bus asking for data. 

Where equipment does need modification – adding sensors to machines that have none or enabling data from instruments that weren't wired to the controls network – the right addition is often a sensor, not a controller replacement. 

Industrial IoT sensors for vibration, temperature, and pressure can be retrofitted to existing equipment and connected to a gateway's analogue or digital inputs, or directly over a local wireless sensor protocol. The gateway becomes the aggregation point for both legacy Modbus devices and new sensors at the same location. 

Industrial Ethernet switches handle the wired backbone where gateways are too far apart for reliable wireless or where latency requirements favor a wired segment. A hybrid architecture — a wired backbone to distribution points, wireless from the gateway to field devices at those points — is common in large facilities. 

Building Resilient Industrial Networks 

Reliable industrial security depends on more than firewall rules and network segmentation. The underlying physical infrastructure must be designed to support continuous operation in demanding environments. From industrial Ethernet and fiber connectivity to wireless networking and ruggedized connectivity solutions, L-com helps organizations build resilient industrial networks that support security, reliability, and long-term operational performance. 

Frequently Asked Questions (FAQs) 

What is an industrial wireless gateway? 
An industrial wireless gateway connects field devices, sensors, PLCs, and other operational technology (OT) equipment to IP-based networks, cloud platforms, and edge systems. It acts as a bridge between industrial protocols and modern networking infrastructure. 

How do industrial wireless gateways support IIoT deployments? 
Industrial wireless gateways collect data from field devices, translate industrial protocols, and transmit information to monitoring, analytics, and control systems. This allows organizations to connect legacy equipment and expand Industrial Internet of Things (IIoT) initiatives without replacing existing assets. 

Which wireless technology is best for industrial applications? 
The right wireless technology depends on the application. Wi-Fi is often used for high-bandwidth connectivity, cellular supports remote and distributed assets, and technologies such as LoRaWAN are well suited for low-power, long-range sensor deployments. 

Can industrial wireless gateways connect legacy equipment? 
Yes. Many industrial wireless gateways are designed to connect legacy devices that use protocols such as Modbus RTU, BACnet, DNP3, or other industrial communications standards, allowing existing equipment to participate in modern IIoT architectures. 

What should I look for when selecting an industrial wireless gateway? 
Key considerations include protocol support, wireless connectivity options, environmental ratings, power requirements, mounting options, security features, and the ability to operate reliably in the temperature, vibration, moisture, and EMI conditions present at the installation site.