← Back to all lessons
Wiring 10
Pro

Wiring 10 — Industrial Ethernet (EtherNet/IP) Star Topology

What you'll learn

Traditional fieldbuses — RS-485 Modbus, PROFIBUS, DeviceNet — were designed when 9600 bps was fast and network management tools barely existed. Industrial Ethernet replaces them with standard 100 Mbit/s (or 1 Gbit/s) TCP/IP infrastructure. That brings a critical advantage beyond raw speed: every device is reachable over IP. Commissioning tools, firmware update servers, SCADA systems, and MES databases all communicate on the same network without protocol gateways. EtherNet/IP, the industrial application layer used by Allen-Bradley and many others, runs implicit (cyclic I/O) and explicit (configuration and messaging) traffic side by side over standard Cat cable and managed switches.

Lab time: ~15 minutes.

Lesson briefing

Industrial Ethernet (EtherNet/IP) Star Topology

Why Industrial Ethernet?

Traditional fieldbuses — RS-485 Modbus, PROFIBUS, DeviceNet — were designed when 9600 bps was fast and network management tools barely existed. Industrial Ethernet replaces them with standard 100 Mbit/s (or 1 Gbit/s) TCP/IP infrastructure. That brings a critical advantage beyond raw speed: every device is reachable over IP. Commissioning tools, firmware update servers, SCADA systems, and MES databases all communicate on the same network without protocol gateways. EtherNet/IP, the industrial application layer used by Allen-Bradley and many others, runs implicit (cyclic I/O) and explicit (configuration and messaging) traffic side by side over standard Cat cable and managed switches.

Shielded Cabling in Industrial Cabinets

A VFD switching 15 kW at 4–16 kHz generates significant radiated and conducted electromagnetic interference. Standard unshielded Cat 6 cable — fine in an office — develops bit errors within metres of a VFD in a switchgear cabinet. Industrial Ethernet uses Cat 5e SF/UTP or S/FTP cables: a foil shield around each twisted pair plus an overall braided screen. The shield attenuates EMI by 30–40 dB across the frequency range of switching noise.

The shield must be connected to protective earth (PE) to be effective. However, it must be bonded at one end only — typically at the switch end, which is the central, well-earthed anchor of the star. Bonding both ends creates a ground loop: any earth-potential difference between two panels drives a circulating current down the shield braid, inducing the very noise you are trying to suppress. Each device's chassis also bonds to PE for touch-safety reasons, but that PE connection is made at the device itself, not via the cable shield.

Star Topology — One Cable per Device to the Switch

Every device connects directly to the managed switch with its own cable run. No daisy-chaining, no T-taps. This is the correct topology for EtherNet/IP star mode and is mandatory for switches that enforce STP/RSTP port states. The advantage over daisy-chain (ring) topologies is straightforward fault isolation: a cable fault or device failure brings down only that one link. The switch's port LEDs and built-in diagnostics immediately identify which device is offline without affecting any other device on the network.

Star vs Ring (DLR / MRP)

The RemoteIO block in this lesson has two Ethernet ports — ETH-IN and ETH-OUT — designed for ring topologies such as EtherNet/IP Device Level Ring (DLR) or PROFINET Media Redundancy Protocol (MRP). In a ring, the cable leaves the switch, daisy-chains through each remote I/O block using ETH-IN → ETH-OUT, and returns to a second switch port. If the cable is cut anywhere in the ring, the protocol detects the fault and switches traffic to the surviving path within milliseconds.

For this lesson, use only ETH-IN — the star connection. ETH-OUT is left unwired. This is the simpler, more common deployment in cabinets where the added complexity of ring management is not needed.

VFD Mains Feed

The VFD's three-phase mains input (L1, L2, L3) and motor output (U, V, W) live in a separate high-voltage cabinet section and are not shown on this canvas. What is wired here is the control-level Ethernet connection from the VFD's communication option module to the switch, and the VFD's PE chassis bond to the ground bar.

The power rail is already wired. The supply feeds the +24 V and 0 V strips, the strips feed the PLC, and the supply's protective earth is bonded to the ground bar. Those greyed, locked wires are the ones Wiring 1A: Power the PLC teaches. You only wire what is new in this lab.

Hints

Hint 1

The power rail (supply, strips, PLC power and the master earth bond) is already fitted and locked. The switch and the remote I/O each still need their own +24V and 0V logic supply from the strips: any free slot of a strip is the same rail.

Hint 2

Sign up to unlock the full hint sequence.

Hint 3

Sign up to unlock the full hint sequence.

Hint 4

Sign up to unlock the full hint sequence.

This lesson uses 9 placed components on the lab canvas. Components are vendor-neutral (no proprietary trademarks); the wiring rules apply to any equivalent industrial part.

Sign up to preview

Create a free account to preview this Pro lab; upgrade to open the interactive circuit.

Sign up to preview →

You might also like

Competency and practice field guide

EtherNet/IP wiring and connection lesson: practice plan

Direct answer

The learner can distinguish cabling, link, IP reachability, device identity, CIP connection, mapped data and application validity.

Written for pLC learners moving beyond link lights to prove an industrial Ethernet I/O connection end to end.

an industrial Ethernet, remote-I/O and IO-Link diagnostics bench with an inspectable controller-to-device signal path while studying EtherNet/IP physical link, addressing, CIP connection, data mapping and quality
System map / 02

NODE 01observable

Scope

Device identity, topology, copper or fiber link, switch port, address, subnet, duplicate detection, CIP object or assembly, connection interval, mapped tags and quality.

NODE 02observable

Signal path

Field device through physical medium, switch, IP path, CIP session and I/O connection, controller mapping, tag quality and application use.

NODE 03observable

Baseline practice

The intended device establishes a stable connection and known data changes arrive with coherent identity, quality and timing.

NODE 04observable

Edge cases

Wrong subnet, duplicate IP, damaged cable, port shutdown, device replacement, assembly mismatch, multicast issue, connection timeout and restart.

NODE 05observable

Fault practice

A device, power, medium, switch, address, identity, CIP, assembly, connection, mapping or application mismatch.

NODE 06observable

Transfer to the job

The network commissioned with current ODVA and vendor guidance, approved segmentation, switch configuration and cybersecurity controls.

Answer surface / 07

Is a link light enough to prove EtherNet/IP is working?

No. It proves a physical-link boundary. Verify address and identity, CIP connection, assembly mapping, data quality and application response separately.

Why can a device ping but still fail PLC I/O?

IP reachability can work while the CIP path, identity, electronic keying, assembly sizes, connection parameters or controller mapping is wrong.