EtherCAT Network Topologies Explained: Line, Star, Tree & Ring

VT SW6EC P1

In simple terms, an EtherCAT topology is the physical wiring layout used to connect your main controller (PLC) to field devices like servo drives, remote I/O modules, and sensors. Unlike older industrial buses that force you into a single rigid wiring style, EtherCAT supports four flexible network structures: Line (Daisy-Chain), Star, Tree, and Ring (Cable Redundancy) topologies.

However, wiring an EtherCAT network topology comes with one major catch: it does not behave like standard office Ethernet. Standard two-port slaves only chain in a straight line, so if you need to branch your cables into a star or tree, you’ll need a specialized EtherCAT junction slave instead of a standard IT Ethernet switch. We’ll look at how each topology works, when and where to make choices, and how to wire your cabinet without dropping a frame.

This engineering guide breaks down the complete physical layer architecture—jump directly to a section below or test fault isolation in the interactive simulator:

Line vs. Star/Tree vs. Ring: Choosing the Right EtherCAT Topology

Because EtherCAT supports up to 65,535 slave nodes per network segment without cascaded switch limits, the machine’s mechanical layout should dictate your network architecture—not the other way around. Evaluating criticality and modular maintenance requirements determines which topology fits your machine.

Topology TypeHardware NeededFault Tolerance & IsolationBest-Fit Machine Application
Linear (Daisy-Chain)Zero extra junctions (Slave IN to OUT)Low: Any single power loss or broken wire drops all downstream nodes.Compact, fixed-frame single machines where all drives share one cabinet power supply.
Star / Tree Topology1-In-2-Out (T-Tap) or 1-In-5-Out (Star) ESC JunctionHigh (Branch Isolation): A severed drop-line or powered-off station is bypassed automatically.Multi-station cells, robotic tool changers (ethercat hot connect), AGVs, and modular optional stations.
Cable Redundancy (Ring)2nd Ethernet port on Master PLCMaximum: Survives a complete main trunk cable cut by feeding frames from both ends.Continuous process plants, tunnel boring machines, and high-availability power infrastructure.
Table 1: Engineering decision matrix for Linear, Star/Tree, and Redundant Ring topologies.

1. EtherCAT Line Topology (Bus / Daisy-Chain Structure)

The most basic EtherCAT network topology is the line topology (or bus or daisy-chain topology). Most EtherCAT slaves have two RJ45 ports: an IN port that receives frames from upstream, and an OUT port that sends the frame downstream to the next device. But two recurring nightmares plague machine builders with a pure daisy-chain:

  • Drag-Chain Cable Fatigue on Moving Gantry: A flexing cable on a moving gantry will fail, breaking the entire daisy-chain return path and taking down unrelated safety I/O and HMI panels downstream.
  • Optional Machine Modules & Tool Changers: Most modern machines come with robotic EOATs that are capable of swapping out grippers mid cycle, or optional inspect stations which only ship on some customer orders (unplugging a node in a linear chain kills the entire bus).
EtherCAT line topology bus daisy chain wiring diagram from master PLC to 2-port slaves
Figure 1: EtherCAT Line Topology strings two-port slaves sequentially from IN to OUT without branching hardware.

2. EtherCAT Star Topology (Centralized Multi-Port Branching)

In an ethercat star topology, a multi-port ethercat junction slave acts as a central distribution hub. A compact DIN-rail ESC junction can be installed to split a single main trunk from the PLC into multiple individual drop lines that radiate out to individual servos, vision cameras, or remote I/O islands. For localized T-tap drop lines, a 1-In-2-Out module is available, while a 1-In-5-Out hub is offered for central cabinet distribution.

EtherCAT star topology wiring diagram using a 6-port 1-In-5-Out ESC junction hub
Figure 2: EtherCAT Star Topology splits a single main trunk into five isolated point-to-point drop-lines via a central ESC junction.

3. EtherCAT Tree Topology & EtherCAT Hot Connect

The EtherCAT tree topology is a combination of linear daisy-chains and star junctions. It is a multi-layered hierarchy with the master as the root, the junctions as the trunk and the short servo chains as the branches. Each moving gantry or optional workcell has its own isolated drop line. EtherCAT Hot Connect groups in the master software allow stations attached to the junction’s output ports to be powered down, unplugged or hot-swapped during live production without causing a master bus fault.

EtherCAT tree topology hierarchical branching diagram combining ESC junctions and servo daisy chains
Figure 3: EtherCAT Tree Topology combines trunk ESC junctions with localized servo daisy-chains and Hot Connect branches.

Hardware vs. Software Hot Connect Responsibilities

It is important to mention that an ESC junction provides the physical layer port isolation required for Hot Connect, but hardware alone is only half the setup. The junction handles the physical branching, while your PLC programmer still needs to configure “Hot Connect Groups” in the EtherCAT master software to prevent bus faults when unplugging tools.

Engineering Note: For actual panel builds, designers typically deploy compact DIN-rail modules like the Valtoris VT-SW3EC (3-port) for localized drop-lines, or the VT-SW6EC (6-port) for central cabinet distribution to ensure physical layer isolation.

4. EtherCAT Ring Topology (Cable Redundancy Structure)

When absolute uptime is required, engineers extend a linear or tree layout into a Ring Topology by routing the final slave’s OUT port back to a second Ethernet interface (Redundancy Port) on the master PLC:

  • Normal Ring Operation: The Main Port from the master transmits process frames downstream (IN → OUT) to exchange data, and the Redundancy Port transmits frames upstream (OUT → IN) without changing process data.
  • During a Cable Break: If a cable break occurs between Slave #2 and Slave #3, the adjacent ESC chips immediately detect the link loss and automatically turn on internal auto-loopback on both ends of the cable break. The Main Port’s frame goes to Slaves #1–#2 and returns. The Redundancy Port’s frame comes from the other end and goes to the remaining slaves, achieving a zero-downtime switchover within a single cycle.
EtherCAT ring topology cable redundancy normal operation vs wire cut auto-loopback
Figure 4: EtherCAT Ring Topology (Cable Redundancy) automatically loops back on both sides of a severed trunk wire within a single cycle.

How EtherCAT Actually Moves Data (Physical Line vs. Logical Ring)

Looking at the four diagrams above, you might notice something strange: only the Ring topology physically wires the last device back to the PLC. In a Line, Star, or Tree layout, the final slave’s OUT port is left completely empty. So how does the data frame ever return to the master?

The answer is the core architectural rule that separates EtherCAT from standard office Ethernet—and the exact reason why standard IT switches fail on an EtherCAT bus: no matter how you wire your devices physically, EtherCAT always moves data inside a closed “Logical Ring.”

The secret is inside your standard Cat5e Ethernet cable. Unlike older serial buses that share a single wire pair and need termination resistors or an active RS485 hub for star vs. daisy-chain wiring, standard 100Mbps Ethernet is full-duplex—meaning each cable contains separate wire pairs for sending (TX) and returning (RX) data. According to the EtherCAT Technology Group (ETG) Functional Principle, a single data frame travels through your network in two steps:

  1. Processing “On-the-Fly”: As the Ethernet frame passes through a slave’s dedicated EtherCAT Slave Controller (ESC) chip, the slave reads its assigned output data and inserts its input data while the frame is moving at wire speed. This introduces only a few nanoseconds of hardware propagation delay.
  2. Automatic Loopback (Auto-Close): Every ESC chip continuously monitors the link status of its downstream port. When the last slave in a segment detects that nothing is plugged into its OUT port, its internal hardware switch automatically loops the signal back onto the return RX pair toward the master.

Hence, irrespective of whether your physical layout is a straight line, a vertical drop-tree or an EtherCAT star topology, the underlying protocol is always a single closed Logical Ring. Thus the bulky TCP/IP stacks are avoided and usable process data represents more than 90% of each Ethernet frame.

Interactive Topology Fault & Auto-Loopback Simulator

Click the red button below to see what happens to downstream devices when Node #2 (S2) loses power or gets unplugged:

A. Linear Daisy-Chain (Line) ALL 4 NODES ONLINE

PLC S1 S2 S3 S4 Logical Ring intact across S1 → S2 → S3 → S4

B. Star/Tree via 1-In-5-Out Junction ALL 4 NODES ONLINE

ESC JUNCTION 1-In / 5-Out Out 2: S1 Out 3: S2 Out 4: S3 Out 5: S4
Diagnostic Status: Both networks are healthy. The EtherCAT frame traverses every slave in deterministic order and returns to the PLC with zero lost frames.

The #1 Mistake: Standard Ethernet Switch vs. Dedicated EtherCAT Switch (Junction)

After seeing the 1-In-5-Out branching in the simulator above, a common question comes up: “Can I just use a standard 5-port or 8-port unmanaged Ethernet switch to split my EtherCAT trunk?” On the outside, both devices have standard RJ45 ports and use Cat5e cables—making a cheap office or industrial TCP/IP switch the #1 commissioning mistake on the shop floor.

You cannot use a standard Ethernet switch inside a real-time EtherCAT segment for two hardware reasons: first, a standard switch uses store-and-forward memory queues (reading MAC tables before forwarding packets), which injects random queuing jitter that breaks Distributed Clocks (DC) servo synchronization. Second, standard switch chips cannot perform the nanosecond Port Auto-Close loopback shown above to keep the EtherCAT logical ring intact. Even though engineers often search for an “EtherCAT switch” or industrial EtherCAT hub, the device you actually need is a dedicated EtherCAT junction slave built on internal ESC silicon:

Technical ParameterStandard Ethernet Switch (Unmanaged / Managed)Dedicated EtherCAT Switch / Junction
Internal SiliconStandard IEEE 802.3 Store-and-Forward ASICDedicated Cascaded EtherCAT Slave Controllers (ESC)
Frame ForwardingReads MAC table, buffers complete packet, queues & forwardsProcesses frames on-the-fly in deterministic port order (IN 1 → Out 2..6)
Processing Latency10 µs to several milliseconds (variable queuing jitter)Nanosecond-level hardware propagation delay (Zero jitter)
Distributed Clocks (DC)Unsupported (destroys servo axis synchronization)Full hardware Distributed Clocks (DC) timestamp compensation
Branch Disconnect BehaviorDrops port link; cannot close internal EtherCAT logical ringInstant hardware Port Auto-Close isolates broken drop-lines
Table 2: Architectural comparison between standard MAC switches and dedicated ESC hardware junctions.

Standard switches inspect destination MAC addresses and buffer packets in memory queues. Because an EtherCAT telegram is a broadcast/summation frame (EtherType 0x88A4) that must visit every slave sequentially and loop back to the master, a standard switch introduces random microsecond jitter that breaks Distributed Clocks (DC) synchronization. By contrast, a dedicated 6-port EtherCAT switch splitter (junction slave) contains internal ESC chips that route the frame strictly out Port 2, receive its loopback, route it out Port 3, and so on—preserving nanosecond determinism.

✖ Standard Ethernet Switch (Store & Forward) MAC Address Lookup + Memory Queue Buffer Frame 3 Frame 2 Wait… Variable Jitter! Latency: 10 µs – 2 ms (Random Queuing Delay) Result: Breaks Distributed Clocks (DC) & drops cyclic frames ✔ Dedicated EtherCAT ESC Junction (On-the-Fly) Hardware ESC Silicon + Distributed Clocks (T0) Zero Buffer • Direct Pass Latency: Nanosecond Hardware Delay (Zero Jitter) Result: Sub-microsecond servo sync across all 5 branches
Figure 6: Standard switches queue packets in memory (causing jitter), whereas dedicated ESC junctions process frames on-the-fly with nanosecond determinism.

Engineering Tip: Where to Place Your Distributed Clocks (DC) Reference Clock in Star Topologies

The EtherCAT master automatically picks the first DC-capable slave after the PLC as the System Reference Clock (T0) and dynamically measures propagation delays on each branch (in strict depth-first order: IN 1 → Port 2 branch → return to Port 2 → exit Port 3). Never locate your Reference Clock at the end of a removable Hot Connect drop line. Use a hardware ESC junction that natively supports Distributed Clocks (DC) right at the trunk split. This guaranties that sub-microsecond timestamp propagation remains stable even when downstream branches disconnect.

The 4 Golden Rules of EtherCAT Wiring (Ports, Cables, Distance & Power)

Once you have chosen the right topology and replaced standard switches with dedicated ESC junctions, the next hurdle is inside the control cabinet. Because EtherCAT runs at 100Mbps on-the-fly without TCP/IP retries, a single reversed plug or unshielded patch cord will halt the bus. Follow these four wiring rules to avoid commissioning headaches:

Rule 1: Respect IN and OUT Ports (Why Auto MDI/MDI-X Won’t Save Reversed Plugs)

On a standard office switch, any cable can plug into any port. On an EtherCAT slave or junction, port assignment is strictly directional. You will often see datasheets state that ports support Auto MDI/MDI-X. Do not misunderstand this spec: Auto MDI/MDI-X only means the port automatically detects straight-through versus crossover TX/RX wire pairs—it does not allow you to swap the logical IN port with an OUT port.

Furthermore, different automation vendors label their ports inconsistently, leading to frequent miswiring on multi-vendor panels. Always consult the slave’s ESI file or hardware manual to verify the correct IN/OUT port assignments before wiring.

Hardware Vendor / Device TypeUpstream Trunk Input (Port 0)Downstream / Branch Outputs (Port 1..N)Consequence of Reversing IN & OUT
Standalone 6-Port ESC JunctionIN 1 (Bottom-left RJ45)2, 3, 4, 5, 6 (5 Branch Outputs)Topology tree scrambles; downstream slaves fail to enter Operational (OP) state.
Beckhoff / Standard ESC ChipsPort 0 (A) / ECAT IN / X1Port 1 (B), Port 2 (C), Port 3 (D)Master reports topology mismatch against configured ENI file.
Omron / Yaskawa Servo DrivesECAT IN / CN1AECAT OUT / CN1BImmediate loop closure at wrong port; all subsequent drives disappear from scan.
Delta / Generic Remote I/OPORT 1 or INPORT 2 or OUTIntermittent initialization failure or unexpected alias addressing order.
Table 3: Cross-vendor EtherCAT port naming conventions and miswiring symptoms.

Rule 2: Use Shielded Cat5e/Cat6 Cables & High-Flex Drag-Chain Wire

Because 100BASE-TX EtherCAT only transmits on pins 1, 2, 3, and 6, cable selection is critical when routing near high-frequency variable frequency drives (VFDs) and servo motor cables. As documented in the ETG.1600 Official EtherCAT Installation Guideline, using unshielded office patch cords is a recipe for instant bus failure when meeting industrial EtherCAT cable specifications.

Installation ParameterETG Official SpecificationField Engineering Reason
Shielding GradeCat5e SF/UTP or S/FTP (Braided + Foil shield)Foil blocks high-frequency servo PWM switching noise; braid drains low-frequency magnetic induction to ground.
Conductor Count & Gauge4-Wire (Quad) AWG22 preferred over 8-Wire AWG24/26 for long/noisy runsEtherCAT only uses 4 pins. In extreme EMI zones, the 4 unused floating wires in an 8-wire cable can induce unwanted capacitive crosstalk. AWG22 minimizes voltage attenuation up to 100m.
Static Cabinet vs. Drag ChainSolid core for fixed trays; Stranded High-Flex PUR for robotics/gantriesSolid copper conductors work-harden and fracture inside moving drag chains within weeks, causing intermittent Lost Link faults.
RJ45 Connectors360° Metal-shielded RJ45 plugsPlastic RJ45 plugs break the shield drain path right at the ESC port entry, acting as EMI antennas.
Table 4: Summary of official ETG.1600 cable specifications for industrial immunity.

Rule 3: The 100-Meter Distance Limit (Per Segment, Not Total Network!)

One common misconception with EtherCAT max cable length is that the whole network cannot be longer than 100 meters. In fact, the 100-meter limit is strictly for the point-to-point copper cable between any two active ESC nodes (using AWG22 shielded Cat5e or better).

Every EtherCAT slave and junction acts as a physical layer signal repeater that reshapes and regenerates the electrical waveform. By cascading standalone junctions or slave nodes every 100 meters, a single copper EtherCAT network can span several kilometers across a factory floor without fiber converters. However, hardware junctions cannot bend the laws of physics. If your layout requires a strict 150-meter unbroken gap between two factory buildings without mid-point power access, copper junctions won’t help—you must transition to EtherCAT Fiber Optic converters for that specific run.

Rule 4: Cabinet Grounding, Power & Enclosure Rating

Even double-shielded cables will drop frames if cabinet grounding and power wiring are overlooked:

  • Drain Noise via PG & Metal DIN Rail: Always connect the Protective Ground (PG) pin of the terminal block and mount metal-housed junctions on an unpainted 35mm DIN rail to bleed off high frequency VFD noise (IEC 61000-4-5 Level 3 surge protection).
  • Check Non-Standard Power Buses: AGVs are powered by 48V DC batteries, while most panels run on 24V AC. Older retrofits sometimes run on 24V AC. A non-polarized 9-60V DC / 24V AC input jack means you won’t need extra step-down converters and you won’t fry the board with reversed wires.
  • Match IP40 vs. IP67 to the Location: Compact IP40 RJ45 junctions are perfect inside control cabinets or local junction boxes, exposed wet robotic arms need sealed IP67 M12 blocks.

Field Troubleshooting: Decoding WKC, Lost Links, and CRC Errors

Even if your cabinet is wired strictly by the four rules above, moving drag-chain cables eventually fatigue and RJ45 latches vibrate loose on the shop floor. The good news is that you never have to unplug cables one by one to find a bad wire. Because every ESC chip tracks hardware error counters on each individual port, you can pinpoint the exact faulty cable segment right from your PLC software when EtherCAT lost frames occur:

Master Diagnostic CounterSymptom on the MachineRoot Physical CauseExact Pinpoint & Fix Strategy
Working Counter (WKC) Drops to 0Sudden bus halt; multiple downstream axes fault simultaneously.Each slave increments the frame’s WKC as it passes through. If a node loses power or unplugs, the frame never returns.Move critical drop-lines off the main daisy-chain onto an ESC junction so Port Auto-Close isolates the dead station.
Lost Link Counter Increments (Port A/B)Brief communication dropouts when a gantry moves or vibrates.Physical electrical link dropped for milliseconds—classic sign of a loose RJ45 latch or broken solid-core wire inside a drag chain.Check which slave shows Lost Link on Port 0 (IN). Replace the cable between that slave and its immediate upstream neighbor with high-flex stranded cable.
Rx Error / Frame CRC Error SpikesBus runs fine when idle, but errors climb rapidly as soon as servo drives enable.Electromagnetic interference (EMI) corrupting bits in transit while physical link stays up.Separate Ethernet cables from 400V motor leads by at least 20cm; replace plastic RJ45 connectors with 360° shielded metal plugs; verify cabinet PE bonding.
Invalid Frame / Forwarding ErrorDownstream slaves show errors even though their own cables are brand new.When Slave #3 corrupts a frame due to local EMI, it marks the frame invalid and forwards it downstream.Golden Rule: Ignore downstream forwarding errors. Find the first upstream node where Rx CRC Error > 0—the bad cable is directly upstream of that specific port.
Table 5: Field diagnostic matrix for pinpointing physical layer faults using ESC hardware counters.
Beckhoff TwinCAT 3 Online test showing Valtoris VT-SW6EC EtherCAT junction and Odot remote IO in OP state with zero CRC errors
Figure 7: Live bench verification in Beckhoff TwinCAT 3 (Build 4024.68) — the 6-port junction (recognized as internal cascaded ESC nodes Box 1–4) and downstream Odot CN-8033 remote I/O (Box 5) running in full OP state with 0, 0, 0 CRC errors across all ports.

Conclusion: Build for Maintenance, Not Just Day-One Commissioning

The advantage of a pure linear daisy-chain is in initial panel assembly where no infrastructure hardware is required. But machines don’t work in clean laboratories. A drag chain will flex millions of times over its five year life cycle. Operators will change tooling. Maintenance technicians will shut down individual safety zones.

Designing a resilient ethercat topology means removing single points of failure before the machine ships . Your main control loop is protected from localized cable faults and long term down time through strict Cat5e shielded wiring standards and dedicated hardware ESC junctions that divide your network into isolated star and tree branches.

Hardware Resources: ESC Junctions & ESI XML Files

Eliminate single points of failure in your modular machines with physical layer branch isolation. No matter how your cabinets are laid out, our DIN-rail ESC junctions, available as a 3-port T-tap or a 6-port star distribution hub, are fully integrated into Beckhoff TwinCAT, Omron Sysmac and Codesys using standard ESI XML documents.

Not sure how to branch your specific PLC topology or need a custom quote? Contact our engineering team or email [email protected] for technical support.

Frequently Asked Questions (FAQ)

1. Can I use a Gigabit (1000BASE-T) switch or cable for my EtherCAT network?
The EtherCAT physical layer strictly uses 100BASE-TX (100 Mbps) full-duplex operation. You want to use cat5e or cat6 cables rated for gigabit as they have better shielding. You just want to make sure that you never put a media converter or switch that only supports gigabit in the loop. Dedicated ESC junctions run at 100Mbps exactly for nanosecond determinism.
2. Does an EtherCAT junction require an IP address or web interface configuration?
No. EtherCAT junctions do not use TCP/IP routing and therefore have no MAC or IP addresses assigned to them for web configuration. They act as transparent hardware forwarders on the fly. You simply import the device’s provided ESI (EtherCAT Slave Information) XML file into your master engineering tool (like TwinCAT or Sysmac Studio) for topology mapping.
3. What happens if I accidentally plug the Master PLC into a downstream output port instead of IN?
You can’t set up the network. The master controller will scan the bus and will throw a “Topology Mismatch” or “No Slaves Found” error. Because EtherCAT uses a strict logical ring, the frame must enter the junction through the designated IN port to properly traverse the internal ESC chips and initiate the auto-loopback sequence.
4. Are Valtoris EtherCAT junctions compatible with third-party masters like Omron or Codesys?
Yup. Our junctions are master-agnostic since they are based on standard ETG-certified EtherCAT Slave Controllers (ESC). They work seamlessly with Beckhoff TwinCAT, Omron Sysmac, Codesys based PLCs, Keyence and any other ETG compliant master controller as long as you import our standard XML/ESI file.
5. Can I cascade multiple EtherCAT junctions to create complex branch structures?
Certainly. EtherCAT junctions can be cascaded to form complex tree structures. In EtherCAT a single segment can contain up to 65535 nodes. Each junction adds only about 1 microsecond of hardware propagation delay, so cascading several junctions across different machine modules has virtually no impact on your cyclic task time.
6. Can I leave unused output ports unplugged on a 1-In-5-Out EtherCAT junction?
Yes, no loopback plugs or terminating resistors are needed on unused ports. The internal ESC silicon continuously monitors physical link status on Ports 2 through 6; any unconnected output port is automatically closed internally via hardware auto-loopback, leaving spare ports ready for future machine expansion.