EtherNet/IP - Knowledge Base

General EtherNet/IP wiki page covering CIP fundamentals, messaging types, Assembly Objects, and integration pitfalls.

Categories:

What EtherNet/IP Is

EtherNet/IP (EtherNet Industrial Protocol) is an industrial networking protocol that runs the Common Industrial Protocol (CIP) over standard Ethernet TCP/IP. It is widely used in PLC-based automation and frequently appears in building automation crossover projects where PLC data must be bridged to BACnet or Modbus supervisory systems.

EtherNet/IP is managed by the ODVA and shares CIP with DeviceNet and ControlNet.

EtherNet/IP CIP protocol stack and messaging types

Core Concepts

ConceptDescription
CIPCommon Industrial Protocol — the shared application layer that defines objects, services, and messaging
Assembly ObjectData containers that group I/O points for exchange between devices
EDS FileElectronic Data Sheet — XML file describing a device’s supported objects and parameters
DataFromDeviceAssembly containing values read from the device (inputs)
DataToDeviceAssembly containing values written to the device (outputs)

Messaging Types

TypeTransportTypical Use
Explicit (Class 3)TCPConfiguration, diagnostics, on-demand reads
Implicit (Class 1)UDP multicastCyclic I/O exchange at fixed intervals

Most gateway integrations use explicit messaging. Implicit messaging requires tighter timing and PLC scanner configuration.

Integration Risks

[!WARNING] The #1 configuration mistake is using DATA_TABLE_READ for points that require write access. Writes fail silently — the gateway reads successfully but the PLC never receives setpoint commands.

[!NOTE] Always classify each point as read-only or read/write before configuration. Common write-required points include setpoints, commands, and limit values.

Other common pitfalls:

  • Missing or mismatched EDS files preventing PLC auto-configuration
  • Assembly Object name/size mismatch between gateway config and PLC scanner
  • Firewall rules blocking CIP traffic (TCP 44818, UDP 2222)

Need more help?

If this page does not resolve the issue, contact Chipkin support with the product model, protocol details, and any diagnostics you have already captured.

Open Chipkin Support