Beckhoff EK1960 Series, Operating Instructions Manual

Page: 128 / 145

Operation
EK1960 128 Version: 1.3.1
4.15 Project design limits of the EK1960
Project design limits
The maximum project design size of the EK1960 is limited by the available memory. This is man-
aged dynamically. The values specified in the following table are therefore only guide values and
may differ from the actual values, depending on the safety project.
Process image size max. 1486 bytes per data direction
(maximum memory size 0x1E00 for 3 buffers, ie with the same size of
input and output process data, a maximum size of 1280 bytes per data
direction is possible. Only straight start addresses are possible, so fill
bytes must be taken into account)
TwinSAFE connections 128 max.
(up to 255 CRCs in total; 1 CRC is required for a TwinSAFE connection
with 1 or 2 byte safe data.)
Supported hardware for
EK1960 TwinSAFE connections EL1904 (all)
EL2904 (all)
EL2902 (all)
EL6900 (all - max. 14 byte safe data)
EL6930 (all - max. 14 byte safe data)
EL6910 (all - max. 126 byte safe data)
EJ6910 (all - max. 126 byte safe data)
KL1904 (from 2008)
KL2904 (from 2008)
KL6904 as slave (from 2008)
AX5805 (all)
AX5806 (all)
Safe data per TwinSAFE
connection maximum 126 byte (telegram length 255 byte)
TwinSAFE blocks maximum 512 (ESTOP with complete input and output mapping)
TwinSAFE groups 128 max.
TwinSAFE user 40 max.
Standard PLC inputs dynamic (memory-dependent), max. 1024 byte
Standard PLC outputs dynamic (memory-dependent), max. 1024 byte
TwinSAFE connection
Only one TwinSAFE connection is possible between two TwinSAFE components. For communica-
tion with a EL6900, for sample, a connection with up to 14 bytes safe user data can be used.
4.16 Behavior when restarting
If the TwinSAFE logic program is restarted due to an EtherCAT restart or a login / logout on the logic
component (without a download), all TwinSAFE groups to which TwinSAFE Connections are assigned go to
the ERROR state.
TwinSAFE logic components with local inputs and outputs can have TwinSAFE groups that have no
TwinSAFE connections assigned. If these TwinSAFE groups use local outputs, these would be set after an
EtherCAT restart without error acknowledgment. If this behavior is not wanted, this must be taken into
account in the corresponding TwinSAFE logic.
CAUTION
Local outputs in TwinSAFE groups without TwinSAFE connections
If local outputs are not allowed to be switched on automatically after a restart of the TwinSAFE logic (in
TwinSAFE groups in which no TwinSAFE connections are created), this must be taken into account by the
user application.