The Myth of the One True Fieldbus: Why Your Network Choice Isn't a Religious War

If you've been in industrial networking for more than a week, you've heard it: "EtherNet/IP is the only way to go," or "PROFINET is the future, everything else is legacy," or my personal favorite, "If you're not using OPC UA, you're living in the dark ages." Baloney. I've spent decades watching plants run perfectly fine on Modbus and others stumble with the newest TSN gear. The truth is, there is no single "best" protocol, and the sooner you stop treating this like a religious war, the better your network—and your sanity—will be.

This isn't about being wishy-washy. I have a strong opinion: you should pick your protocol based on what your machines actually need, not on what the vendor booth gave you for free. And more importantly, you should stop trying to replace everything and start making what you have work better. Let me bust some myths that I see every day on the plant floor.

Myth: "We need to standardize on one protocol to simplify things"

I get the appeal. One protocol, one set of tools, one training manual. But here's the reality: your plant is a mix of old and new, and that's not going to change overnight. The OPC Foundation, which knows a thing or two about this, points out that protocols are layered—Modbus, PROFINET, and EtherNet/IP connect field devices and PLCs, while OPC UA and MQTT carry data securely to SCADA, MES, and cloud systems (OPC Foundation). So you're always going to have a mix. Trying to force everything onto one protocol is like trying to make every vehicle in your fleet a forklift—it just doesn't work.

Instead, embrace the layering. Use the fieldbus that your PLCs and drives speak natively, and use OPC UA or MQTT to get that data up to the higher levels. It's not an either/or; it's a both/and.

Is OPC UA really the answer to everything?

OPC UA is great, don't get me wrong. It's vendor-neutral, platform-independent, and has built-in encryption and authentication, making it the backbone for IIoT and IT/OT integration (OPC Foundation). It's standardized as IEC 62541 (IEC 62541 OPC UA Standard). It's even scalable up to MES/ERP systems over TCP/IP (EtherCAT Technology Group). But here's the thing: OPC UA is not a fieldbus. It doesn't control your servo drives in real time. If you try to use it for high-speed motion control, you're going to have a bad time.

So no, OPC UA is not the answer to everything. It's the answer for getting data off the plant floor and into the cloud, not for moving a robot arm. Use it where it belongs, and use a real-time Ethernet protocol for the control loop.

What's the difference between real-time Ethernet and standard Ethernet, anyway?

This is where people get confused. Standard Ethernet, like what you have in your office, is fine for sending emails and browsing the web. But in industrial control, you need determinism—you need to know that a packet will arrive in a guaranteed amount of time, every time. That's what real-time protocols like PROFINET, EtherCAT, and Sercos do. PROFINET supports real-time (RT) and isochronous real-time (IRT) classes for motion control (OPC Foundation). EtherCAT was developed for short cycle times of ≤100 µs and jitter of ≤1 µs (EtherCAT Technology Group). Sercos can achieve synchronization accuracy much less than 1 µs (Sercos International).

But here's the kicker: not every application needs that level of performance. If you're just monitoring temperatures in a warehouse, standard Ethernet with a little care might be fine. The key is to match the protocol's capability to your actual need, not to the marketing hype.

Is EtherNet/IP just for Rockwell shops?

It's true that EtherNet/IP is especially common in North America on Rockwell/Allen-Bradley platforms (OPC Foundation). But that doesn't mean it's a walled garden. EtherNet/IP runs the Common Industrial Protocol (CIP) over standard Ethernet and TCP/UDP (ODVA EtherNet/IP). CIP is a strictly object-oriented protocol that is media-independent and supported by hundreds of vendors (ODVA Common Industrial Protocol). So you can mix and match brands. It also supports secure communication via CIP Security, which can help with IEC 62443 compliance (ODVA EtherNet/IP).

So stop dismissing EtherNet/IP as a proprietary thing. It's open, and it runs on standard, unmodified Ethernet, which makes IT/OT convergence easier (ODVA EtherNet/IP). If your plant is in North America and your integrators know it, it's a perfectly good choice.

Table: Quick Comparison of Common Industrial Protocols