Project Design Limits Of El6910/Ej6910; Sync-Manager Configuration - Beckhoff TwinSAFE EL6910 Operation Manual

4.16

Project design limits of EL6910/EJ6910

Project design limits
The maximum project design size for EL6910/EJ6910 is determined by the available memory. This
is managed 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
TwinSAFE connections
Supported hardware for
TwinSAFE connections of the
EL6910/EJ6910
Safe data per TwinSAFE
connection
PROFIsafe telegram length
TwinSAFE function blocks
TwinSAFE groups
TwinSAFE user
Standard PLC inputs
Standard PLC outputs
TwinSAFE connection
Only one TwinSAFE connection between two TwinSAFE terminals is possible. For communication
with a EL6900, for sample, a connection with up to 14 bytes safe user data can be used.
4.17

Sync-Manager Configuration

Depending on the size of the TwinSAFE project on the TwinSAFE logic, it may be necessary to adjust the
sync manager configuration.
As soon as the following message appears during the saving or downloading of the project, the sync
manager configuration for the device has to be adapted.
EL6910
max. 1486 bytes per data direction
(max. memory size 0x1E00 for three buffers, i.e. with identical input and
output process data sizes, the maximum size is 1280 bytes per data
direction. Only even start addresses are possible, therefore fill bytes may
have to be considered)
maximum 212
(up to 255 CRCs in total; 1 CRC is required for a TwinSAFE connection
with 1 or 2 byte safe data.)
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)
EL6910 (all - max. 126 byte safe data)
KL1904 (from 2008)
KL2904 (from 2008)
KL6904 as slave (from 2008)
AX5805 (all)
AX5806 (all)
maximum 126 byte (telegram length 255 byte)
4 to 16 byte PROFIsafe telegram length (user data 0 - 12 byte)
maximum 512 (ESTOP with complete input and output mapping)
maximum 128
maximum 40
dynamic (memory-dependent), max. 1024 byte
dynamic (memory-dependent), max. 1024 byte
Version: 1.8.0
Operation
121