EtherCAT configurations
The EK3100 is an EtherCAT master with automatic configuration. This means that all EtherCAT Terminals must be present when the system is switched on. Since the boot-up of the EK3100 generally takes considerably longer than the start-up of the EtherCAT slave devices, the latter can be operated on the same power supply. With decentralized EtherCAT slaves, care must be taken that they are switched on earlier or at the same time as the supply voltage.
Switching EtherCAT devices on or off during the runtime
If one or more EtherCAT devices should fail during the operating phase, an error response is generated on the PROFIBUS. The input data of all EtherCAT devices are then invalid and the output data are no longer accepted. This also applies to the devices that are still in operation on the EK3100. If you wish to use the option to plug in or unplug devices during the runtime, a further “Sync Unit” must be configured. This is not possible with an EK3100. In this case, use a CX803x.
EtherCAT topology
All EtherCAT devices must be entered in the order in which they map themselves on the EK3100 and thus on the EtherCAT master. EtherCAT devices are automatically addressed; with a few exceptions all EtherCAT Bus Terminals are equipped with an EtherCAT ASIC. EtherCAT Terminals without an ASIC are, for example, EL9400, EL9070 and other EL9xxx. You can identify these EtherCAT Terminals using the technical data "Message to E-bus". If there is a "-" here, this terminal need not be taken into account for the mapping.
EtherCAT devices are registered in the direction of the EtherCAT telegram.
Sample configuration with EK1100 EtherCAT coupler
Sample configuration with EPxxxx EtherCAT Box
Example configuration with EK1122 (2-port EtherCAT junction in protection class IP20)
The counting direction is to be observed when using an EK1122!
If EtherCAT junction 1 on the EK1122 is connected, then the EtherCAT frame is forwarded here first (1); if junction 1 is not connected the frame on junction 2 is sent (2), only after that does the sequence continue with the E-bus on the right-hand side (3).
If neither junction is used, then junctions 1 and 2 are bridged, so to speak, and the EtherCAT frame goes directly to the E-Bus on the right-hand side.
Example configuration with EP1122 (2-port EtherCAT junction in protection class IP65)
The counting direction is to be observed when using an EP1122! It is comparable with the EK1122.
If EtherCAT junction 1 on the EP1122 is connected, then the EtherCAT frame is forwarded here first (1); if junction 1 is not connected the frame on junction 2 is sent (2), only after that does the sequence continue with the EtherCAT connection on the right-hand side (3).
If neither junction is used, then junctions 1 and 2 are bridged, so to speak, and the EtherCAT frame goes directly to the EtherCAT connection on the right-hand side.
No Hot Swap during operation You cannot use EP1122 and EK1122 on an EKxxxx for Hot Swap and also not for connection and disconnection during operation. EP1122 and EK1122 are suitable only for topology extension (star) on an EKxxxx. |
Note restrictions
Please note the following restrictions when you use the EK3100 Bus Coupler with EtherCAT devices:
- Only EtherCAT devices from Beckhoff are supported. To use EtherCAT device from other manufacturers, use the CX8031 Embedded PC instead.
- The EK3100 Bus Coupler does not support hot-plug. All EtherCAT devices have to be connected before the Bus Coupler can be started. The EtherCAT configuration must not be changed during operation. An EtherCAT interrupt generates an error and invalidates the data.
- Only one Sync Unit is supported.
- The EK3100 Bus Coupler does not support distributed clocks. EtherCAT devices requiring distributed clocks cannot be used.
- Use only EtherCAT devices from Beckhoff, which are listed in the GSD file.
- Gateway terminals are not supported. These also include ASI and IO-Link terminals. To use gateway terminals, use the CX8031 Embedded PC instead.
- EtherCAT K-bus Couplers, such as the BK11x0 or the BK1250, are not supported