Industrial Automation Communication Protocols
OPC UA
Full Name: Open Platform Communications Unified Architecture
Inventor: OPC Foundation
Why Use: Platform-independent, secure, and scalable communication for industrial automation systems.
Devices Supported: Theoretically unlimited; based on network architecture.
Communication Cable: Ethernet (Cat5e/Cat6) or wireless
How to Establish Communication: Install OPC UA server and client software. Configure endpoints and
security settings. Connect client to server via IP and port.
OPC DA
Full Name: OPC Data Access
Inventor: OPC Foundation
Why Use: Real-time data exchange based on Microsoft COM/DCOM. Used in legacy Windows-based
systems.
Devices Supported: Limited by DCOM configuration and Windows resources.
Communication Cable: Ethernet (Cat5/Cat5e)
How to Establish Communication: Install OPC DA server and client. Configure DCOM settings. Connect via
ProgID and network address.
OPC DDE
Full Name: OPC Dynamic Data Exchange
Inventor: Microsoft
Why Use: Older communication method for exchanging data between applications on Windows.
Devices Supported: Very limited, mostly for local data exchange.
Communication Cable: Not applicable (local communication)
How to Establish Communication: Use DDE-aware applications and configure topics and items for data
sharing.
Modbus
Full Name: Modbus Protocol
Inventor: Modicon (now Schneider Electric)
Why Use: Simple and open protocol for serial and Ethernet communication with PLCs and sensors.
Devices Supported: Up to 247 devices (Modbus RTU), many more in TCP/IP.
Communication Cable: RS-485, RS-232, Ethernet (Cat5e/Cat6)
How to Establish Communication: Define master-slave or client-server configuration, set slave ID and baud
rate, and connect devices using appropriate cable.
Profibus
Full Name: Process Field Bus
Inventor: Siemens and others
Why Use: Widely used in factory automation and process control.
Devices Supported: Up to 126 devices
Communication Cable: RS-485 (twisted pair) or fiber optic
How to Establish Communication: Install Profibus DP master, assign device addresses, and connect using
bus cables and terminators.
TCP/IP
Full Name: Transmission Control Protocol / Internet Protocol
Inventor: Vint Cerf and Bob Kahn
Why Use: Standard protocol suite for Internet and LAN communications.
Devices Supported: Unlimited (based on IP addressing)
Communication Cable: Ethernet (Cat5e/Cat6) or fiber optic
How to Establish Communication: Assign IP addresses, configure ports, and connect devices using Ethernet
switches or routers.
Kepware
Full Name: Kepware (Industrial Connectivity Software)
Inventor: Kepware Technologies
Why Use: Integrates multiple protocols into a single interface for SCADA, MES, and other systems.
Devices Supported: Varies based on license and hardware
Communication Cable: Depends on underlying protocol (Ethernet, serial, etc.)
How to Establish Communication: Install KEPServerEX, configure device drivers and tags, and connect
clients via OPC or MQTT.
CodeSys
Full Name: Controller Development System
Inventor: 3S-Smart Software Solutions
Why Use: IEC 61131-3 compliant PLC programming and communication tool.
Devices Supported: Depends on controller and network
Communication Cable: Ethernet, serial, or fieldbus
How to Establish Communication: Use CodeSys IDE to configure controller communication and deploy
projects over the network.
IEC 61850
Full Name: IEC 61850 Communication Networks and Systems in Substations
Inventor: IEC Technical Committee
Why Use: Standardized communication in substations and electrical grid systems.
Devices Supported: Hundreds; structured around logical nodes and data models.
Communication Cable: Ethernet (Cat6/fiber optic)
How to Establish Communication: Configure IEDs (Intelligent Electronic Devices), define data models (SCL),
and communicate via GOOSE or MMS.
IEC 104
Full Name: IEC 60870-5-104
Inventor: IEC
Why Use: Telecontrol communication protocol for electrical engineering and power system automation.
Devices Supported: Many; based on client-server model
Communication Cable: Ethernet
How to Establish Communication: Configure master/slave setup with IP addresses and ASDU settings, and
establish TCP/IP link.
Client-Server
Full Name: Client-Server Architecture
Inventor: Developed as a distributed computing concept
Why Use: Reliable model for data exchange where clients request and servers respond.
Devices Supported: Depends on server capacity and network
Communication Cable: Ethernet, wireless
How to Establish Communication: Define server and client software roles, assign network settings, and
manage requests/responses.
PTP
Full Name: Precision Time Protocol
Inventor: IEEE
Why Use: Synchronizes clocks throughout a computer network.
Devices Supported: Many, based on multicast
Communication Cable: Ethernet
How to Establish Communication: Configure master and slave clocks, ensure hardware timestamping
support, and connect via LAN.
SPTP
Full Name: Single Pair Ethernet Time Protocol (assumed)
Inventor: Not formally defined; likely vendor-specific or industry variant
Why Use: Used for time sync or data transfer in compact Ethernet systems.
Devices Supported: Varies
Communication Cable: Single-pair Ethernet cable
How to Establish Communication: Follow vendor-specific configuration guides.
