Industrial IoT (IIoT)
IoT Gateways for Legacy Factory Equipment
Published by IOT Illinois Research & Editorial Team

The press brake on your floor may be thirty years old and still make good parts. The problem is that it says nothing about how it is doing. An industrial gateway is the device that lets old and new equipment talk to modern software without replacing the machine. This article focuses on choosing and configuring a gateway: which protocols you will meet, what features matter, and how to avoid mistakes that show up months later. It is a companion to our broader IIoT retrofit guide for Illinois legacy factory floors, and belongs in Industrial IoT (IIoT).
What a Gateway Actually Does
A gateway sits between the machine and your network. On one side it speaks the language of the equipment, whether that is a serial link, a fieldbus or a vendor protocol. On the other side it speaks something modern systems understand, such as MQTT or OPC UA. In between it translates, tags data with names and units, buffers it when the network drops, and secures the connection. Done well, it also keeps your plant floor separate from your office network.
The Protocols You Will Meet
Older Illinois plants usually have a mix. Knowing what you have is the first step, and a walk through the plant with a maintenance lead is often the fastest way to find out.
| Protocol | Where You Find It | Notes |
|---|---|---|
| Modbus RTU | Meters, drives, older PLCs over RS-485 or RS-232 | Simple and widespread; check baud rate, parity and device address |
| Modbus TCP | Newer devices over Ethernet | Same data model on a network link |
| EtherNet/IP | Allen-Bradley and many North American PLCs | Common in Midwest plants |
| PROFINET | Siemens and European equipment | Real-time Ethernet used on many imported machines |
| OPC UA | Newer controllers and middleware | Structured, secure and vendor neutral |
| BACnet MS/TP | Building systems in plants | Useful for HVAC and air handling data |
| 4-20 mA and discrete I/O | Analog sensors, relays, lights, switches | Needs an I/O module with analog or digital inputs |
Where a machine has no digital port at all, you can still read it: current clamps on motors, vibration sensors on bearings, or a tap on a stack light can tell you whether it is running, idle or faulted. Our guide to reducing downtime with IoT sensor strategies covers which signals to prioritize.
What to Look For When Choosing One
- Protocol coverage: The gateway should support the protocols you have now and a path to what you will want later, especially MQTT and OPC UA outputs.
- Store and forward: If the connection drops, the device should hold data locally and send it afterward, so reports have no holes.
- Security features: Look for encrypted connections, certificate-based authentication, firewall controls, role-based access and a way to receive firmware updates.
- Industrial ratings: Temperature range, vibration tolerance, DIN-rail mounting, and an enclosure suitable for dust and moisture. A Rockford foundry and a Springfield warehouse need different hardware.
- Edge processing: Some gateways can filter, calculate and run small models locally, which links to the placement choices in edge AI for Illinois factories.
- Manageability: Remote configuration and monitoring for many units, rather than a laptop visit to each one.
- Power and connectivity: Wired Ethernet where possible, wireless or cellular where not, with attention to coverage in metal buildings.
Setting It Up Properly
Map Before You Connect
List each machine, its protocol, and the five or ten values that matter: run state, cycle count, fault code, temperature, and so on. Collecting everything sounds helpful but creates noise and cost.
Name Things Consistently
Use a standard naming pattern for plant, line, machine and signal, and include units. Consistent names make dashboards, alerts and later digital models far easier to build, as discussed in digital twins in Illinois manufacturing.
Read, Do Not Write, at First
Start with read-only access. Writing values back into a controller is possible, but it should wait until the team has tested carefully and agreed on safety rules.
Segment the Network
Place gateways in a controlled zone with firewall rules that allow only the traffic you intend. Older machines were never designed to face a network, so the gateway becomes their protection. The guidance in OT cybersecurity for Illinois industrial plants explains the layout.
A Foundry Scenario
Consider a small foundry in the Peoria area with a mix of equipment: a 1990s furnace controller speaking Modbus RTU, newer molding machines on EtherNet/IP, and a set of compressors with no digital output. The plant installs two gateways. One reads the furnace over a serial link and publishes temperature and alarms. The other pulls cycle counts from the molding PLCs. A few current clamps on the compressors report load. Everything flows to one dashboard with a standard naming pattern. Within a quarter the team spots that a compressor runs loaded through lunch breaks, and that the furnace temperature drifts before a recurring defect. None of the machines were replaced. The Peoria Industrial IoT page lists local firms that do this kind of integration.
Common Mistakes
Buying on Price Alone
A cheap gateway without store-and-forward or security updates becomes a liability. Look at total cost, including support.
Ignoring the Serial Details
Many Modbus RTU problems come from wrong baud rates, parity settings, wiring polarity or missing termination on RS-485 lines. Bring the manual and a good cable.
No Plan for Updates
Firmware needs patching. Decide who is responsible, how often, and how you will do it across many units.
Letting It Become Shadow IT
If operations installs gateways without telling IT, security gaps follow. Agree on ownership and network rules before the first install.
What's Coming Next
Expect more equipment to ship with OPC UA and MQTT built in, shrinking the need for translation on new machines. Expect gateways to take on more local analytics and more built-in security features. But older equipment will stay on Illinois floors for years, so translation will remain a practical need. Funding can ease the first project: see Illinois IoT funding and grants, and consider connecting with local firms such as DeGray Automation or ControlLink.
Explore More
Browse more Industrial IoT (IIoT) articles, see the Chicago Industrial IoT directory, and read about industrial IoT in Illinois manufacturing.
Frequently Asked Questions
What is an industrial IoT gateway?
It is a device that connects factory equipment to modern networks and software. It reads data using the machine's own protocol, translates it into a standard format such as MQTT or OPC UA, and sends it securely onward.
Can I connect a machine that has no digital output?
Usually yes. External sensors such as current clamps, vibration sensors or stack light taps can show whether a machine is running or faulted, and an I/O module can bring those signals to the gateway.
What is the difference between Modbus RTU and Modbus TCP?
Modbus RTU runs over serial links such as RS-485, while Modbus TCP runs over Ethernet. They share a similar data model, but RTU needs correct serial settings and wiring.
Do I need a cloud account to use a gateway?
No. Many gateways can send data to a local server or on-site software. Cloud connection is optional and depends on how you want to store, view and analyze the data.
Is it safe to connect old machines to the network?
It can be, if done carefully. Use a gateway as a buffer, keep the connection read-only at first, segment the network and restrict traffic with firewall rules.
How many gateways will my plant need?
It depends on the number of machines, their distance and their protocols. One gateway can often serve several nearby machines, but separate buildings or very different protocols may call for more.
