OPC UA vs S7, EtherNet/IP and Modbus: How to Read PLCs for OEE

Key takeaways

• OPC UA is the first choice when the PLC has a server: named values, a known data model and built-in security.
• The PLC's own protocol is the fallback: S7, EtherNet/IP or Modbus work on most installed PLCs.
• Most plants end up with a mix, read by one gateway.
• Read only, either way. OEE never writes to a PLC.
• Older native protocols often lack built-in security, so network zones matter more for them.

There is no single right way to read PLCs for OEE. Use OPC UA where the PLC offers a server, because its values carry names and meaning. Use the PLC's own protocol where it does not, which is most older PLCs. A gateway can speak both and send one stream of data upstream.

Fabrico, OEE and light MES software with AI cameras, connects a machine through its PLC, a Fabrico IoT device or an AI camera. Which protocol is used on which machine is agreed for each plant with Fabrico's technical team.

What do you find on a real plant floor?

The installed base decides more than any preference. In practice:

• Central European plants often run Siemens S7 controllers on PROFINET.
• US-owned plants often run Allen-Bradley controllers on EtherNet/IP.
• Packaging and helper equipment, such as checkweighers and labellers, often speaks Modbus.
• Machines older than about 15 years may offer a serial port, or nothing at all.

Industrial Ethernet now makes up about eight in ten new network nodes. But new nodes are not the installed base, and the installed base skews older.

What does OPC UA give you that native protocols do not?

OPC UA, also known as IEC 62541, is a platform-independent standard. Its servers publish type definitions, so a client reads what a value means, not just its number. Its security covers authentication, integrity and confidentiality.

The cost of OPC UA is availability. Many older PLCs have no server at all, and on some newer ones it must be switched on or licensed. Our guide to OPC UA for OEE covers the data side.

When is the native protocol the better choice?

• When the PLC has no OPC UA server, which is common on older controllers.
• When enabling a server would need a program change the plant does not want.
• For simple devices such as checkweighers that only offer Modbus.

A gateway can read the native protocol on the machine side and offer the data upstream in one form. For the Modbus side, see our guide to Modbus TCP vs RTU.

Worked example: one plant, four protocols

Sample line (illustrative numbers, not a customer). A plant has three packaging lines and 15 machines to connect. The ports are the usual defaults; confirm them for each device.

So 6 of the 15 machines are read over OPC UA and 9 over native protocols. One gateway per line handles all four. The firewall needs one allow rule per protocol from the gateway down, and nothing coming in.

The 9 native machines need a tag or register map each. The 6 OPC UA machines need their nodes checked, which is faster when they follow a companion specification.

How do you keep both kinds of connection safe?

1. Read-only accounts on every OPC UA server, and no write functions used on native protocols.
2. Encrypted OPC UA, with certificates trusted on both sides.
3. Zones for native protocols. Keep them inside the OT zone, reachable only from the gateway.
4. Sensible read rates. Read only the values OEE needs, so the PLC is not loaded.
5. Outbound only from the gateway to the OEE system.

Our guide to PLC connectivity for OEE covers the network layout, and OPC UA vs MQTT explains how the data travels upstream.

Which mistakes do plants make when choosing a protocol?

• Waiting for OPC UA everywhere, so older machines stay unconnected for years.
• Turning on an OPC UA server with no security, because it was quicker at commissioning.
• Letting the OEE system reach PLCs directly instead of through one gateway.
• Using write functions on a native protocol to reset counters. Read only, always.

Where does Fabrico fit?

Fabrico is a computer vision enabled Manufacturing Performance Platform. OEE and light MES come first, read from whichever signal each machine offers.

• Automatic downtime logging from PLC tags, IoT devices or cameras.
• The operator confirms the reason in one tap, whatever protocol logged the stop.
• OEE live by line and shift, with every loss priced in money.
• A pilot on one line, so the protocol mix is proven before it is copied.

There is no free plan and there are no tiers: each plant gets a quote. See the product on the computer vision OEE page, and the basics in what a PLC is.

Frequently asked questions

Is OPC UA better than S7 for OEE?

Where the PLC offers an OPC UA server, usually yes. Values come with names and types, and the connection can be encrypted with user accounts. Where it does not, the S7 protocol through a gateway works fine for OEE, as long as access stays read-only and inside the OT zone.

Does OPC UA slow down the PLC?

It can add load if a client reads too much too often. For OEE, read only the few values you need, at a sensible rate, and ask your controls engineer to check the load. Most OEE reading is light compared with what the PLC does to run the machine.

Can older Siemens S7 PLCs be read over OPC UA?

Not directly if the PLC has no server. A gateway can read the PLC over the S7 protocol and offer the data as OPC UA or another format upstream. The PLC program does not need to change for that.

Which protocol is more secure for OEE?

OPC UA, when it is set up with encryption, trusted certificates and a read-only account. Many older native protocols have little or no built-in security. For those, keep the traffic inside the OT zone and let only the gateway reach the PLCs.

Do you need a gateway to read PLCs for OEE?

Usually yes. A gateway speaks each PLC's protocol on the machine side and sends one stream of data upstream. It also keeps the OEE system from reaching into the OT network, because the gateway opens every connection itself.

Map your plant's protocols with us

Bring your machine list with PLC makes and models. We will show how each one connects and what its stops cost.

Request a demo · Contact us