TSN vs Standard Industrial Ethernet: A Qbv Guide
Read more...
IIoT Protocols Compared: An Engineer's 2026 Framework
OPC UA, MQTT, Modbus, EtherNet/IP, and PROFINET do not provide the same kind of industrial communication. Modbus exchanges process data through defined read and write commands. EtherNet/IP and PROFINET are industrial Ethernet technologies for automation networks. OPC UA adds an interoperability architecture and information models. MQTT routes published messages through a broker.
This comparison stays at that role level. It does not rank the protocols by speed, cost, security, market share, or regional popularity because the bound sources do not support a fair common benchmark.
TL;DR: Compare these protocols by the job they perform. Modbus, EtherNet/IP, and PROFINET commonly face industrial devices and control systems. OPC UA represents and exchanges structured industrial information. MQTT provides brokered publish/subscribe transport. A system may use more than one, but the sources do not justify a universal stack or winner.
industrial sensor fundamentals
IIoT Protocol Roles at a Glance
The safest comparison is functional. Each source describes its own protocol, so the table records supported roles without converting vendor claims into cross-protocol scores.
| Protocol | Conservative role supported by the bound source | What this comparison does not claim |
|---|---|---|
| Modbus | Application-layer commands for reading and writing industrial process data; it can be carried over serial networks or Ethernet via TCP/IP | Installed-base rank, security level, migration cost, or performance |
| EtherNet/IP | Industrial Ethernet using CIP in its upper layers; it uses standard Ethernet and supports TCP/IP and UDP, including cyclic data transmission | Regional dominance, lower cost, or superiority over PROFINET |
| PROFINET | Industrial Ethernet for automation, with device integration, diagnostics, and communication alongside TCP/IP traffic | Market leadership, cycle-time advantage, or universal motion-control fit |
| OPC UA | Platform-independent industrial interoperability with information models, client-server services, and PubSub concepts | Automatic interoperability in every product, a security ranking, or a prescribed deployment layer |
| MQTT | Brokered publish/subscribe transport that can carry OPC UA PubSub data | A standardized industrial information model or a complete control architecture by itself |
The Modbus Organization describes Modbus as an application-layer protocol for exchanging process data. Its commands read and write device data, while the physical network can vary, including serial media and Ethernet through TCP/IP (Modbus Organization).
ODVA describes EtherNet/IP as standard Ethernet and TCP/IP combined with CIP for industrial automation, with UDP available for cyclic data transmission (ODVA). PI describes PROFINET as an industrial Ethernet standard with device integration, diagnostics, and concurrent TCP/IP communication (PI). These descriptions support distinct protocol identities, not a winner between them.
How OPC UA and MQTT Differ
OPC UA and MQTT overlap at a transport boundary but solve different problems. OPC UA defines a broad architecture for industrial information exchange. Its Part 1 overview includes the AddressSpace and information-model concepts, client-server roles, services, and an OPC UA form of publish/subscribe (OPC Foundation).
MQTT is the brokered transport option in this comparison. An OPC Foundation explanation of OPC UA PubSub distinguishes OPC UA's data context from MQTT transport and says MQTT can carry OPC UA PubSub communication for WAN or cloud-oriented connectivity (OPC Connect).
Transport and meaning are separate concerns. MQTT routes messages between publishers and subscribers. An application still needs an agreed payload and topic design. OPC UA supplies standardized concepts for representing and relating information. Neither fact proves that every project needs both.
For a focused treatment, see how OPC UA and MQTT compare.
Where Modbus Fits
Modbus defines commands, addressing, and data formatting for industrial devices. The same application-layer protocol can operate over different lower-level networks. This makes it useful to describe a device interface without implying that Modbus defines the entire network or IIoT architecture.
A Modbus integration also depends on device documentation. The bound introduction explains that manufacturers normally provide mappings between device variables and Modbus registers. That is a narrower, supportable distinction from OPC UA's explicit information-model framework.
This article does not infer that Modbus is obsolete, insecure, cheap, slow, or due for replacement. Those conclusions require deployment-specific evidence that is outside the bound source set.
How EtherNet/IP and PROFINET Fit
EtherNet/IP and PROFINET both address industrial communication over Ethernet, but their defining ecosystems and mechanisms differ. EtherNet/IP uses CIP for its upper layers. PROFINET defines its own industrial Ethernet technology, device integration, and diagnostic facilities.
These facts distinguish EtherNet/IP and PROFINET from MQTT and OPC UA at a high level, but they do not choose between the industrial Ethernet options. The bound pages are maintained by their respective organizations and make promotional claims about performance, availability, and adoption. Without a neutral common test, those claims should not become a scorecard.
For an actual system, the relevant evidence starts with the supported protocol and conformance information for the controllers, devices, and engineering tools already in scope. Required communication behavior should then be checked against the applicable specifications and product documentation. This is a compatibility check, not a general rule that one industrial Ethernet protocol belongs in a particular geography or industry.
PROFINET applications and use cases EtherNet/IP setup guide
Can These Protocols Be Used Together?
Yes, but the evidence supports coexistence rather than one mandatory architecture. A device or controller may expose data through Modbus, EtherNet/IP, or PROFINET. Another component may represent data with OPC UA or publish messages through MQTT. OPC UA PubSub may itself use MQTT transport.
Those possibilities do not establish a required field-edge-cloud stack. Gateways, brokers, servers, and clients add their own configuration and operational requirements. The right combination depends on supported interfaces and the information that must cross each boundary.
A bounded selection review can ask:
- Which protocols do the actual endpoints support?
- Is the exchange device data, structured information, or brokered messages?
- Does the consumer require an agreed information model, or only an agreed payload?
- Which protocol versions, profiles, and product conformance statements apply?
- What behavior must be validated in the target network and equipment?
This checklist avoids unsupported claims about latency, security, scale, cost, or market position. Those properties need requirements, product documentation, and testing specific to the deployment.
Frequently Asked Questions
What is the difference between MQTT and OPC UA?
MQTT provides brokered publish/subscribe transport. OPC UA defines an industrial interoperability architecture with information models, client-server services, and PubSub. They can be used together because OPC UA PubSub can use MQTT as a transport.
Is Modbus still relevant to IIoT projects?
Modbus remains relevant when existing industrial devices expose process data through its read and write commands. An IIoT design can retain that device-facing exchange while another component presents the data to higher-level systems.
How do EtherNet/IP and PROFINET differ from MQTT?
EtherNet/IP and PROFINET are industrial Ethernet technologies for automation networks. MQTT is a brokered publish/subscribe transport. The distinction is their role in the system, not a universal ranking.
Conclusion
A precise IIoT protocol comparison begins by separating roles. Modbus provides industrial read and write commands. EtherNet/IP and PROFINET provide industrial Ethernet communication. OPC UA provides an interoperability architecture and information modeling. MQTT provides brokered publish/subscribe transport.
That role map is useful without a star rating or a universal prescription. Choose only after matching the actual endpoints, information needs, applicable profiles, and required behavior of the system being designed.
About the Author: Rihards Niparts is a Sales Engineer working with industrial sensors and IIoT connectivity.
What is the difference between MQTT and OPC UA?
MQTT provides brokered publish/subscribe transport. OPC UA defines an industrial interoperability architecture with information models, client-server services, and PubSub. They can be used together because OPC UA PubSub can use MQTT as a transport.
Is Modbus still relevant to IIoT projects?
Modbus remains relevant when existing industrial devices expose process data through its read and write commands. An IIoT design can retain that device-facing exchange while another component presents the data to higher-level systems.
How do EtherNet/IP and PROFINET differ from MQTT?
EtherNet/IP and PROFINET are industrial Ethernet technologies for automation networks. MQTT is a brokered publish/subscribe transport. The distinction is their role in the system, not a universal ranking.
