Without disturbing existing systems, edge devices make it easy to convert data from a custom fieldbus into open protocols for digital transformation.
If TCP/IP won the “protocol wars” in the ‘90s, then WHY are you still fighting protocol battles on the plant floor today? Because industrial networks were around long before the internet. As far back as the 1960s, machines communicated via serial networks like RS-232, RS-485, and CAN Bus—with specialized proprietary fieldbus protocols like Modbus, Profibus, and DeviceNet.
Even with TCP/IP on Ethernet, specialized protocols remained. Modbus now has a TCP/IP version, Profibus gave way to ProfiNET, DeviceNet to EtherNet/IP, and even some new ones joined the protocol party.
After the industry demanded interoperability, OPC was born—now OPC UA—a big step toward a unified architecture on OT networks. Meanwhile on the IT side, using HTTP and HTTPS was common. It’s how web browsers—and most of the internet—work today.
MQTT Sparkplug came later. A recently named International Standard, it’s built on efficient, secure, and scalable publish/subscribe communications—a great fit for digital transformation projects and the IIoT.
I want to digitally transform, but my existing machines don’t support all these protocols.