RobotGuide
Labs/CAN vs EtherCAT: What Actually Differs

Lab 3 / 15 · Animation · comparison

CAN vs EtherCAT: What Actually Differs

Two buses running side by side — one fights for every frame, the other arrives like a train on schedule.

Math: High school math is enoughNo coding neededNo hardware needed≈ 5 min

Number of slaves

Nodes4

With more nodes CAN's arbitration overhead becomes clearly visible; EtherCAT's frame simply grows longer.

Readouts

CAN jitter—
EtherCAT jitter—
One full cycle (CAN / EtherCAT)—

Frame timing is drawn to the scale of 1Mbps CAN / 100Mbps EtherCAT, simplified to build intuition — not a precise simulation.

What problem this lab solves

Both are called «buses», but CAN and EtherCAT are an order of magnitude apart in determinism. Pick wrong and no amount of software fixes it — this is a high-frequency tiebreaker question in electronics job interviews.

How to read the figure

Top is CAN: variable frame length, arbitration for the line, more nodes means more collisions, jitter grows with load. Bottom is EtherCAT: the master sends one ring frame, slaves read and write on the fly as it passes, one frame sweeps all nodes, the period is set by the master clock, jitter stays in microseconds. Watch the last metric: at the same node count, who can guarantee 1kHz without breaking.

Hands-on

Move the slave count from 2 to 8 and watch how much each bus's period jitter rises. CAN visibly degrades; EtherCAT barely moves — that is what «deterministic» means.

Related topics

Next labs (in play-learn order)