Industrial Ethernet/IP: Ethernet on the Factory Floor

Why Industrial Ethernet?

Standard office Ethernet is designed for file transfers and email — a 200 ms delay on an email is irrelevant. In a factory with 200 robots, 50 PLCs, and 300 sensors, a 200 ms delay could mean a robot arm colliding with a workpiece.

Industrial Ethernet adapts standard Ethernet (IEEE 802.3) protocols and hardware for factory environments, adding deterministic timing, environmental hardening, and high-availability features.

Office Ethernet vs Industrial Ethernet

The EtherNet/IP Protocol

EtherNet/IP (where IP stands for Industrial Protocol, not Internet Protocol) is one of the most widely deployed industrial Ethernet protocols. Developed by Rockwell Automation and managed by the ODVA organization, it runs over standard TCP/IP and UDP/IP — meaning it works through conventional Ethernet switches and routers and can coexist with IT traffic on the same network.

CIP: The Core Layer

CIP (Common Industrial Protocol) is the unified application layer used by EtherNet/IP (as well as DeviceNet and CompoNet). CIP models every device as a collection of objects with attributes and services.

Example: a VFD (Variable Frequency Drive) on the network exposes:

• Identity Object: manufacturer name, model number, serial number
• Connection Object: cyclic connection configuration
• Assembly Object: input data (actual speed, current, status) and output data (speed command, run/stop command)

CIP Communication Types

1. Implicit (I/O Messaging): cyclic data exchange over UDP at a fixed rate (e.g., every 10 ms). Used for real-time control — reading sensors and sending commands.

2. Explicit Messaging: request/response over TCP. Used for configuration and diagnostics — reading device parameters, uploading programs, querying alarm status.

Think of implicit messaging as an open phone line (continuous data stream) and explicit messaging as text messages (request then reply).

Managed Switches: The Network Backbone

In an office, you plug in an unmanaged switch and it works. In a factory, managed switches are essential because they provide:

VLANs (Virtual LANs)

VLANs logically separate traffic on the same physical hardware. Example:

• VLAN 10: control traffic (PLCs + I/O) — highest priority
• VLAN 20: SCADA/HMI traffic — high priority
• VLAN 30: IT/office traffic — normal priority

Without VLANs, a large email attachment (10 MB) can delay a critical safety valve control signal.

Quality of Service (QoS)

QoS prioritizes critical messages. The switch reads the priority tag in each Ethernet frame (802.1p) and forwards control messages first, even when the network is congested.

Network Monitoring

Managed switches provide SNMP and MIBs for monitoring:

• Port status (speed, errors, congestion)
• Loop detection
• Event logging
• Alerts via email or SNMP traps

Deterministic Communication

In standard Ethernet, when two devices transmit simultaneously, a collision occurs and retransmission happens after a random delay. Acceptable for email; catastrophic for control.

Deterministic communication means every message arrives within a guaranteed time window — no random delays. This is achieved through:

1. Full-duplex switches: eliminate collisions entirely (each port transmits and receives simultaneously)
2. QoS and 802.1p priorities: critical messages pass first
3. Time scheduling: in TSN, a portion of bandwidth is reserved for deterministic control traffic

Ring Topology: No Downtime Allowed

Imagine a single cable feeding 15 workstations on a production line. If it breaks — the entire line stops. The solution: ring topology.

How It Works

Devices connect in a closed loop. Normally, data flows in one direction. If a cable breaks or a switch fails, the ring "reroutes" data in the opposite direction within less than 50 ms (some protocols achieve under 20 ms).

Common Redundancy Protocols

DLR is the preferred choice for device-level EtherNet/IP networks. It operates without managed switches — the devices themselves support the ring protocol.

TSN: The Future of Industrial Ethernet

TSN (Time-Sensitive Networking) is a set of IEEE 802.1 standards that make standard Ethernet capable of carrying deterministic, time-critical data on the same network as regular IT traffic.

Key TSN Standards

• 802.1AS (Time Synchronization): synchronizes clocks across all devices to sub-microsecond accuracy. Every device in the plant knows the exact same time.

• 802.1Qbv (Time-Aware Shaper): divides time into "windows" — a reserved period for deterministic control traffic and a period for regular traffic. Neither interferes with the other.

• 802.1Qcc (Stream Reservation): reserves guaranteed bandwidth for specific data streams across the entire network path.

• 802.1CB (Frame Replication): duplicates critical packets across multiple paths for seamless redundancy with zero loss.

Why TSN Matters

Before TSN, each industrial protocol (EtherNet/IP, PROFINET, EtherCAT) needed its own proprietary solutions for determinism. TSN unifies this at the Ethernet layer itself — any protocol can leverage it. This promises a future where control (OT) and information (IT) converge on a single, deterministic network.

Industrial Ethernet Protocol Comparison

Practical Network Design

When designing an EtherNet/IP network for a factory, follow these principles:

1. Segment the network: use VLANs or physically separate networks for control and IT
2. Use industrial managed switches: Cisco IE, Stratix (Allen-Bradley), Scalance (Siemens)
3. Design DLR rings: for each production cell, connect devices in a ring
4. Enable QoS: give top priority to implicit CIP traffic
5. Use industrial-grade cabling: shielded Cat5e/Cat6 with M12 connectors
6. Add an industrial firewall: between the control network (OT) and the IT network
7. Document everything: IP addresses, VLANs, topology diagrams

Practical Example: Bottling Line

In a bottling line running at 600 bottles per minute:

• Device level (DLR Ring): 8 remote I/O stations, sensors, servo drives — 5 ms cycle time
• Control level (Star/Ring): 3 PLCs connected via managed switch — coordination data every 10 ms
• Supervisory level (Star): SCADA station + Historian server — data every 1 second
• Firewall: separates the control network from the corporate office network

Each level has its own VLAN and distinct QoS policies.

Summary

Industrial Ethernet is not simply office Ethernet in a factory. It is a complete ecosystem of hardened hardware, deterministic protocols, managed switches, and disciplined network design. EtherNet/IP with CIP offers flexibility and broad device support, while TSN promises a future where control and IT converge on a single deterministic network. Engineers who understand these concepts can design reliable, secure industrial networks.