Parameterization And Commissioning; Start-Up Behavior Of The Bus Coupler; Ekxxxx - Optional Distributed Clocks Support; Fig. 31 Flow Chart Showing Start-Up Behavior Of The Bus Coupler - Beckhoff BK11 0 Series Documentation

Parameterization and commissioning

6 Parameterization and commissioning
6.1

Start-up behavior of the Bus Coupler

Immediately after being switched on, the Bus Coupler checks, in the course of a self test, all the functions of
its components and the communication on the K-bus/E-bus. The red I/O LED blinks while this is happening
After completion of the self-test, the Bus Coupler starts to test the attached Bus Terminals (the "Bus
Terminal Test"), and reads in the configuration. The Bus Terminal configuration is used to generate an
internal structure list, which is not accessible from outside. In case of an error, the Bus Coupler enters the
Stop state. Once the start-up has completed without error, the Bus Coupler enters the fieldbus start state.
Fig. 31: Flow chart showing start-up behavior of the Bus Coupler
The Bus Coupler can be made to enter the normal operating state by switching it on again once the fault has
been rectified.
6.2

EKxxxx - Optional Distributed Clocks support

Basic principles Distributed Clocks (DC)
The EtherCAT Distributed Clocks system comprises local clocks that are integrated in the EtherCAT slaves
and are synchronized by the EtherCAT master via special datagrams. Not all EtherCAT slaves support the
Distributed Clocks procedure. It is only supported by slaves whose function requires it. In the TwinCAT
System Manager a slave indicates its DC capability by showing "DC" in the settings dialog.
Fig. 32: DC tab for indicating the Distributed Clocks function
46 Version: 4.1 BK11x0, BK1250