How an IIoT gateway works
An IIoT gateway is an industrial computer that sits between operational equipment and the wider network. On one side it connects to the machines, controllers and sensors, often over serial buses, fieldbuses or digital I/O. On the other it connects to the plant network, a SCADA system or a cloud service over Ethernet, Wi-Fi or cellular. Its job is to turn machine data into a standard, usable form and send on what matters.
Industrial equipment speaks a mix of protocols, many of them decades old and never designed for the internet. The gateway polls each device in its own language, converts raw registers into named, scaled values, applies rules or analytics locally and publishes the results in a modern IT protocol. Because it processes data on site, it cuts bandwidth, keeps working through network outages and keeps the control network separate from the internet.
The term covers a wide range of hardware, from a small fanless box with two serial ports to a rack of edge servers running analytics for a whole plant.
What an IIoT gateway does
Most gateways combine the same core functions, although the balance between them varies with the application.
-
//
Data acquisition. Reads values from PLCs, meters, drives and sensors, by polling or by subscribing to changes.
-
//
Protocol translation. Converts field protocols such as Modbus into OPC UA, MQTT or REST for IT and cloud systems.
-
//
Edge processing. Filters, averages and analyses data locally, from simple threshold alarms to AI models, to cut latency and bandwidth.
-
//
Buffering. Stores data when the uplink drops and forwards the backlog when it returns, so no readings are lost.
-
//
Security. Separates the control network from the internet, encrypts traffic and authenticates to the cloud with certificates.
Protocols an IIoT gateway handles
A gateway’s value lies in the protocols it can speak on each side. The table lists the most common ones.
| Protocol | Side | Physical link | Typical use |
|---|---|---|---|
| Modbus RTU | Field | RS-485 serial | Meters, drives, controllers |
| Modbus TCP | Field | Ethernet | PLCs, HMIs, newer devices |
| PROFINET and EtherNet/IP | Field | Industrial Ethernet | Siemens and Rockwell PLC networks |
| CAN bus and J1939 | Field | CAN | Vehicles, mobile machinery, batteries |
| Digital and analog I/O | Field | Wired signals | Contacts, alarms, 4 to 20 mA sensors |
| OPC UA | Field and IT | Ethernet | Structured, secure data models between OT and IT |
| MQTT | IT and cloud | Ethernet, Wi-Fi, cellular | Lightweight publish and subscribe to cloud platforms |
For simple on and off signals, many gateways also carry isolated digital inputs and outputs; our white paper on DIO vs GPIO for IIoT gateways explains the difference.
Where IIoT gateways are used
Gateways appear wherever existing equipment needs to share data without being replaced or reprogrammed.
-
//
Manufacturing. Machine status, cycle counts and energy use are collected from PLCs and meters for OEE dashboards and maintenance planning.
-
//
Energy and utilities. Substation equipment, solar inverters and battery systems report to a central SCADA or cloud service.
-
//
Building services. HVAC, refrigeration and lighting controllers across many sites are monitored from one dashboard.
-
//
Agriculture and the environment. Weather stations, pumps and storage sensors on remote sites send data over cellular links.
-
//
Transport and mobile machinery. Vehicle CAN data, location and condition readings are gathered and sent back to fleet systems.
IIoT gateway vs IoT gateway and router
An IoT gateway in a home or office links consumer sensors to a cloud app and usually runs on mains power indoors. An IIoT gateway does the same job for industrial equipment, so it adds industrial protocols, isolated serial and I/O ports, wide-range DC power, wide operating temperatures, DIN-rail or wall mounting and a long product life. A router, by contrast, moves IP packets between networks without understanding what is in them. Many industrial gateways include routing and cellular, but the protocol translation and edge processing are what make them gateways.
Edge gateway: the same device, another name
An edge gateway is a gateway that processes data at the edge of the network instead of only passing it through. In practice the term describes the same hardware as an IIoT gateway: you will also see IoT edge gateway and industrial edge gateway used for it. The word “edge” stresses the computing side, such as filtering readings, running rules or AI models and storing data locally when the network is down, while “IIoT” stresses the industrial connections.
An edge gateway is smaller than an edge server. It usually serves one machine, line or cabinet, with a low-power processor, a few gigabytes of memory, isolated serial and digital I/O ports and DIN-rail mounting. When a site needs to pool data from many gateways and cameras, or run several applications and virtual machines together, that work moves up to an edge server, and the gateways feed it.
Choosing an IIoT gateway
Gateways have to survive where the machines are. Check the field ports first, then the environment and connectivity: how many isolated RS-485 or CAN ports, whether digital I/O is needed, the operating temperature range, mounting, and whether the site needs 4G or 5G backhaul. Our white paper on adopting 5G at the edge in IIoT applications covers the cellular side. Processing headroom matters too, because a gateway bought only to forward data often ends up running analytics or AI as the project grows.
Our industrial IoT gateways cover compact fanless systems with serial, Ethernet and cellular options. Our factory gateway case study and smart farming case study show two very different sites.
Quick answers on IIoT gateways
IIoT gateways: common questions
What is an IoT gateway?
A device that links IoT sensors and equipment to a network or cloud. It translates their protocols, often processes data locally and sends it on securely. An IIoT gateway is the industrial version.
What is the difference between a gateway and a PLC?
Control versus data. A PLC runs the machine in real time. A gateway reads data from the PLC and other devices and passes it to IT systems, without taking over control.
Does an IIoT gateway need the cloud?
No. Many gateways send data to an on-site SCADA or historian, or act on it locally. The cloud is one destination, not a requirement.
Can an IIoT gateway run AI?
Yes, if it has the processing power. Gateways with an NPU, GPU or AI accelerator can run models on sensor or camera data at the edge.
What operating system does an IIoT gateway run?
Usually Linux, sometimes Windows IoT. Linux suits containerized gateway software and MQTT brokers, while Windows IoT Enterprise suits sites with Windows-based SCADA tools.
We build IIoT gateways with the serial, I/O and cellular options fitted, the operating system and gateway software configured, and the protocols tested against your equipment as standard before they ship.