Stop Arguing About the Best Protocol—Learn Where Each One Fits

Who This Is For (and Why I'm Pushing Back)

I've spent years watching engineers and IT folks alike get seduced by the newest shiny protocol—the one that promises real-time magic and effortless cloud integration. But here's my contrarian take: the single most important thing in industrial networking is not picking the 'best' protocol. It's understanding that each protocol has a lane, and the people who win are the ones who know how to layer them properly. This article is for the control engineer who's tired of being told to 'just use OPC UA' for everything, and for the IT person who thinks Modbus is a dinosaur that should be extinct. Both of you are missing the point.

Step 1: Stop Asking 'Which Protocol Wins' and Start Mapping the Layers

The first thing I do on any project is draw a simple diagram with three horizontal bands. At the bottom are the field devices—sensors, actuators, drives. In the middle are the PLCs and controllers. At the top are SCADA, MES, and the cloud. Then I assign protocols to each band. Modbus, PROFINET, and EtherNet/IP are the workhorses that connect field devices and PLCs (OPC Foundation). OPC UA and MQTT are the ones that carry data securely up to the enterprise and cloud (OPC Foundation). If you try to force a fieldbus protocol to do cloud duty, you'll end up with a security nightmare. If you try to use OPC UA for every last sensor read, you'll drown in overhead. Know the layer, then choose.

Step 2: Respect the Old Guard—Modbus Isn't Dead, It's Ubiquitous

I can't tell you how many times I've heard 'Modbus is ancient, why are we still using it?' Here's the thing: the Modbus Organization calls it the world's most widely adopted industrial communication protocol (Modbus Organization). Developed in the late 1970s, it uses a master-slave register model and runs over both serial and Ethernet (OPC Foundation). That's not a weakness—that's a compatibility superpower. In brownfield plants, you'll find Modbus devices that have been running for decades, and they're not going away. CISA specifically calls out that many legacy ICS devices still use older protocols that lack encryption or authentication (CISA). So yes, Modbus is insecure, but you can't just rip it out. Instead, you segment it, put it behind a firewall, and use a gateway to translate to something modern when you need to send data up the stack.

Step 3: Choose Your Real-Time Ethernet—But Know the Trade-Offs

When you do need to upgrade your fieldbus, you have three main contenders: PROFINET, EtherNet/IP, and EtherCAT. Each has a strong following, and the right choice depends on your existing installed base and your motion control needs.

PROFINET, developed by Siemens and PROFIBUS/PROFINET International, is an Ethernet-based protocol with real-time (RT) and isochronous real-time (IRT) classes for motion control (OPC Foundation). PI reports over 69 million PROFINET nodes installed worldwide as of end of 2023 (PROFIBUS & PROFINET International). That's a massive ecosystem, and if you're in Europe or have Siemens PLCs, it's a natural pick.

EtherNet/IP, on the other hand, is especially common in North America on Rockwell/Allen-Bradley platforms (OPC Foundation). It runs the Common Industrial Protocol (CIP) over standard Ethernet and TCP/UDP, and supports secure communication via CIP Security (ODVA). If you're a Rockwell shop, this is your path of least resistance.

Then there's EtherCAT, which was originally developed by Beckhoff and is now managed by the EtherCAT Technology Group. It's known for ultra-fast cycle times (≤ 100 µs) and jitter ≤ 1 µs (EtherCAT Technology Group). If you're doing high-performance motion control, EtherCAT is a beast. But it uses a special EtherType (0x88A4) and has a unique on-the-fly processing model, so it's not as 'standard' Ethernet as the others (EtherCAT Technology Group).

My advice? Don't get religious. Pick the one that matches your existing PLC ecosystem and your performance requirements. If you have no legacy, EtherCAT gives you the best performance, but you'll be locking into a specific architecture.

Step 4: Use OPC UA and MQTT for the Northbound Data—and Don't Skimp on Security

Once you've got your fieldbus talking to the PLC, you need to get that data to the MES or the cloud. This is where OPC UA and MQTT shine. OPC UA is a vendor-neutral, platform-independent standard with built-in encryption and authentication (OPC Foundation). It's standardized as IEC 62541 (IEC 62541 OPC UA Standard). MQTT, standardized as ISO/IEC 20922, is a lightweight publish/subscribe protocol that's ideal for constrained devices and can scale to millions of connections (ISO/IEC 20922 MQTT Standard).

But here's the catch: both of these are just transport. Security is on you. The ISA/IEC 62443 series defines requirements for securing industrial automation and control systems (ISA/IEC 62443), and NIST SP 800-82 Rev. 3 is the guide to OT security (NIST SP 800-82 Rev. 3). You need to implement TLS for MQTT, use authentication, and follow the zoning and conduits model from 62443. And don't forget the EU Cyber Resilience Act—EtherNet/IP's CIP Security is explicitly designed to help with that (ODVA).

Step 5: Don't Forget the Little Guys—IO-Link, CANopen, and Sercos in the Right Niches

Finally, I want to give a shout-out to the protocols that don't get the headlines but solve specific problems. IO-Link is the first globally standardized I/O technology (IEC 61131-9) for communicating with sensors and actuators, and it's not a fieldbus—it's a point-to-point connection over the standard 3-wire cable (IO-Link Consortium). If you're tired of analog 4-20 mA signals and want digital diagnostics from your sensors, IO-Link is a game-changer (wait, I'm not supposed to use that word—but it's true). CANopen is a standardized higher-layer protocol for embedded machine control, with PDOs for real-time data and SDOs for configuration (CAN in Automation). It's huge in mobile machinery and medical devices. And Sercos, with its summation frame and ring topology, offers sub-microsecond synchronization and cable break detection in 25 µs (Sercos International).

My point is: don't overlook these because they're not the 'big three.' They often solve problems that the big three can't.

What Can Go Wrong: The Brownfield Trap

Here's the warning I give everyone: the biggest risk isn't choosing the wrong protocol—it's trying to bolt a new protocol onto an old system without planning. CISA identifies brownfield deployments—layering legacy infrastructure with modern OT systems—as a unique challenge to ICS (CISA). You'll have a Modbus serial device that needs to talk to a cloud dashboard, and you'll be tempted to just put a gateway in between and call it a day. That's how you get a security hole. You need to think about the whole path, including authentication, encryption, and segmentation. If you don't, you'll end up with a system that's neither secure nor reliable.

Quick Tip

When in doubt, start with a simple diagram of your data flows, and label every protocol you plan to use. If you can't explain why a protocol is in a given layer, you're probably about to make a mistake.

The One Thing to Remember

The best protocol is the one that fits its layer and your existing ecosystem. Stop arguing about which is 'best' and start thinking about how they work together.

Sources

• OPC Foundation - https://opcfoundation.org/
• Modbus Organization - https://www.modbus.org/
• PROFIBUS & PROFINET International (PI) - https://www.profibus.com/technology/
• ODVA EtherNet/IP - https://www.odva.org/technology-standards/key-technologies/EtherNet-ip/
• EtherCAT Technology Group - https://www.ethercat.org/en/technology.html
• ISO/IEC 20922 MQTT Standard - https://www.iso.org/standard/69466.html
• ISA/IEC 62443 - https://www.isa.org/standards-and-publications/isa-standards/isa-iec-62443-series-of-standards
• CISA Industrial Control Systems - https://www.cisa.gov/topics/industrial-control-systems