Ethercat Cycle Time - Configuration Overview; Object Description; Fig. 51 Bk1250, "Bk1250" Tab - Beckhoff BK11 0 Series Documentation

Parameterization and commissioning
6.4.8

EtherCAT cycle time - configuration overview

The EtherCAT cycle time with which the couplers can be operated should be considered in conjunction with
the achieved K-bus cycle time. The cycle time achieved with the K-bus terminals is shown in the BK1250 tab
(or BK1120 / BK1150).
Fig. 51: BK1250, "BK1250" tab
If the EtherCAT cycle time exceeds the K-bus cycle time both systems operate in synchronous mode. The K-
bus is started after an EtherCAT telegram and copies its inputs into the memory. They are retrieved with the
next EtherCAT telegram, i.e. the inputs are always one cycle old.
If the EtherCAT cycle is shorter than the K-bus cycle, the K-bus operates asynchronous relative to
EtherCAT. Faster polling than "Estimated Cycle (offline)" is therefore possible but may lead to outdated input
data or outputs not being set in time via the K-bus.
The EtherCAT cycle applied to the BK1120 / BK1150 (BK1250) should therefore be significantly greater than
the "Estimated Cycle (offline)" (min. 250 µs, depending on the Bus Terminal configuration). Online control in
the system through "Max. Cycle (online)" or "CouplerState" is recommended.
6.4.9

Object description

6.4.9.1 Standard objects
Index 1000: Device type
Device type (read only) of the EtherCAT slave.
Index 1008 Device name
Device name (read only, value: e.g. BK1120-0000-0000) of the EtherCAT slave.
Index 1009 Hardware version
Hardware version (read only) of the EtherCAT slave.
Index 100A Software version
Version (read only, value: e.g. 07 (B7)) of the firmware (chip for processing the I/O signals) of the EtherCAT
slave.
64 Version: 4.1 BK11x0, BK1250