| Modbus TCP | Modbus messaging over TCP/IP Ethernet | TCP port 502 by default | Reading input values and writing output values between a controller and remote I/O over Ethernet. | Supported function codes, register map, byte order, connection limits, and whether the module acts as a server or client. |
| Modbus RTU | Serial communication, commonly RS-485 | No TCP port; serial settings define the link | Connecting distributed I/O over a serial bus, often in installations where Ethernet is not required. | Baud rates, parity, addressing, termination guidance, and supported RS-485 wiring topology. |
| EtherNet/IP | CIP communication over standard Ethernet | TCP 44818 for explicit messaging; UDP 2222 commonly used for I/O messaging | Cyclic I/O exchange and device configuration in EtherNet/IP control systems. | Device role, supported I/O connection types, configuration files, and compatibility with the intended controller. |
| PROFINET | Industrial Ethernet with real-time communication mechanisms | No single TCP port for cyclic real-time I/O; communication can use Ethernet frames directly | Cyclic data exchange between a PROFINET controller and remote I/O devices. | Supported conformance features, device description file (GSDML), diagnostics, and controller compatibility. |
| EtherCAT | Real-time Ethernet fieldbus | EtherType 0x88A4; typically not carried as ordinary TCP/IP traffic | Fast, synchronized process-data exchange between an EtherCAT master and I/O terminals. | Required master support, device description file (ESI), cycle-time needs, and topology requirements. |
| OPC UA | Platform-independent industrial communication; commonly UA TCP | TCP port 4840 is the common default for UA TCP; endpoints can be configured | Structured data exchange with supervisory, integration, or information systems; not necessarily a substitute for real-time fieldbus I/O. | Supported security policies, certificates, data model, server/client roles, and endpoint configuration. |