CODESYS Β· Track 06 Β· CODESYS as a fieldbus master

One Frame, Every Slave

CODESYS is a fieldbus master for EtherCAT, PROFINET, EtherNet/IP, Modbus and more. EtherCAT is the clever one: instead of addressing each device separately, a single frame flies down the line and every slave reads its outputs and writes its inputs as the frame passes through β€” "processing on the fly." Watch one frame service the whole network in a single lap.

⚑ on-the-flyπŸ” one frame, one cycleESI devices
01 Β· Processing on the fly

The frame that does everything in one pass

The master sends one EtherCAT frame down the chain. As it reaches each slave, that slave grabs its piece and inserts its inputs β€” in hardware, in nanoseconds, without stopping. The frame loops back to the master with all the data, every cycle. Run it and watch the single frame read/write all four slaves in one trip.

the one EtherCAT frame slave exchanged this pass slave waiting
cycle time

That's why EtherCAT is so fast: there's no per-device round trip β€” one frame, one lap, the whole network's I/O exchanged with microsecond precision. You add slaves by importing their ESI description files into the device tree (Track 05), just like a GSDML for PROFINET.

02 Β· The fieldbuses CODESYS masters

One tool, many networks

⚑ EtherCAT β€” the fast, deterministic favourite. On-the-fly processing, sub-millisecond cycles, distributed clocks for sync. ESI device files.

🌐 PROFINET & EtherNet/IP β€” talk to Siemens/Rockwell-world devices. GSDML/EDS files, cyclic provider-consumer exchange.

πŸ”’ Modbus TCP/RTU β€” the universal fallback (see the Schneider academy). Great for meters, sensors and legacy gear.

🚐 CANopen / J1939 β€” for CAN-based drives, vehicles and mobile machinery. All configured in the same device tree.

03 Β· Check yourself

Why so fast?

What makes EtherCAT exchange a whole network's I/O so much faster than polling each device?