OPC-UA, Modbus, S7:
Which Protocol and When?
A practical comparison of the three protocols you will encounter most often in industrial data collection — what each one does well, where it falls short, and how to choose the right one for your deployment.
When you connect an edge device to a PLC or controller, the first question is almost always the same: which protocol? Modbus, S7, and OPC-UA are the three you will encounter in the overwhelming majority of industrial environments. They are not interchangeable — each reflects a different era, a different set of priorities, and a different assumption about how machines communicate.
This article is a practical guide — not an exhaustive protocol specification. The goal is to help you choose the right one for a given deployment, and to understand the trade-offs before you wire anything up.
Modbus: The Protocol That Refuses to Die
Modbus was developed in 1979. That is not a typo. It is one of the oldest industrial communication protocols still in active use, and it remains dominant because it is simple, open, and supported by virtually every PLC, drive, and sensor manufactured in the last four decades.
The core model is minimal: a master polls a slave by address and register number, and the slave returns raw integer values. There is no data type system beyond that. A register holds a 16-bit integer. Whether that integer represents a temperature in tenths of a degree, a motor speed in RPM, or a bitfield of status flags is entirely a matter of convention between the device manufacturer and the integrator.
Modbus TCP extends the original serial protocol over standard Ethernet — same register model, same addressing, carried over TCP/IP. This is what you will encounter in most modern deployments.
S7: Native to Siemens, Efficient in Context
The S7 protocol is Siemens' proprietary communication protocol, used natively by the S7-300, S7-400, S7-1200, and S7-1500 PLC families. Unlike Modbus, it understands the internal memory structure of the PLC — data blocks, bit addresses, timers, counters — and can read and write them directly without any register mapping.
In a Siemens-only environment, S7 is the natural choice. It gives you direct access to DB variables by name (in newer firmwares), supports typed reads, and is deeply integrated into TIA Portal configuration. For high-volume data collection from Siemens hardware, it is typically faster and more efficient than any third-party alternative.
The important caveat: on S7-1200 and S7-1500 controllers running firmware 4.x and later, Siemens introduced additional access controls. To read data blocks over S7, the PLC project must have "PUT/GET communication" explicitly enabled in TIA Portal. Without this setting, the connection is refused — something that catches many integrators off guard on first deployment.
OPC-UA: The Modern Standard
OPC Unified Architecture (OPC-UA) is the current generation of the OPC standard, designed from the ground up as a platform-independent, secure, and semantically rich communication protocol for industrial systems. Where Modbus gives you raw integers and S7 gives you PLC memory, OPC-UA gives you a full information model: nodes with names, data types, units, relationships, and history.
OPC-UA is the only one of the three protocols with built-in security: mutual certificate authentication, message signing, and encryption are part of the specification — not an afterthought. It also supports subscriptions, meaning the server pushes data to the client on change rather than requiring constant polling. For high-frequency monitoring, this significantly reduces network overhead.
The trade-off is complexity. An OPC-UA server needs to be configured, its node address space needs to be understood, certificates need to be managed, and the protocol is significantly heavier than Modbus. On older or resource-constrained hardware, OPC-UA server implementations may not be available at all.
When to Use Which
How Simplinx Handles All Three
The SMX-IoT10 supports Modbus TCP, Siemens S7, and OPC-UA natively — configured through the web interface without any scripting or custom drivers. In practice, most production environments use more than one protocol: an older line with Modbus sensors alongside a Siemens S7-1500 and a newer machine with OPC-UA.
The SMX-IoT10 reads all three in parallel, normalises the data into a common format, stores it locally in its edge database, and forwards it to your cloud endpoint — AWS IoT Core, Azure IoT Hub, Google Cloud IoT, or any MQTT broker. The protocol differences at the field level are abstracted away before anything leaves the floor.
This means the choice of protocol is driven by what the device supports, not by what your cloud pipeline can handle. You get the right protocol at the field level and a unified data stream at the cloud level.
Want to Know More About How Simplinx Works?
Talk to our engineering team — we're happy to go deeper on any aspect of the platform.