ABB AC500-S Safety User Manual page 398

Usage of safety CPU with V3 non-safety CPU PM56xx
Supported data types:
● Standard data types like BYTE, WORD, INT
● Array data types
● Data unit types (DUTs)
DUT objects are automatically created in CODESYS Safety during "Create Safety
Configuration Data" .
● A mixture of the above
Supported features for adding variables:
● Cut, copy, paste, delete and insert of variables via context menu and standard windows
shortcuts.
● Bulk data modification, e.g., copy and paste variables from and to .csv file.
● Filters for each column.
● Undo and redo of changes.
● "Input Assistant" for variable name and type
398
NOTICE!
Since the variable names are generated for both safety and non-safety applica-
tion, it is recommended to use variable names that clearly describe the trans-
mission direction, e.g., "PMtoSM" and "SMtoPM" or "toSM" and "fromSM".
DANGER!
To satisfy the CODESYS Safety programming guidelines
"CODESYS Safety programming guidelines" on page 172, you must follow
these rules:
– Use the prefixes "I_" (non-safety inputs for the safety CPU) and "O_" (non-
safety outputs from the safety CPU) for the variable names of the safety
CPU. The cyclic non-safe data exchange is non-safe. Therefore, do not use
Ä Chapter 4.5 "Safety code analysis tool" on page 181.
any safety prefixes
– Add a description for each variable with at least 10 characters.
NOTICE!
If you use cyclic non-safe data exchange, changes in non-safety programming
environment could lead to new boot project CRC.
NOTICE!
Cyclic non-safe data exchange shares the memory with the PROFIsafe process
data (e.g., safety inputs and outputs) of the configured safety I/O devices, and is
limited to 2048 bytes for each direction.
Automation Builder does not check the size when defining the variables, but
during "Create Safety Configuration Data" .
3ADR025091M0208, 12, en_US
Ä [4].
Ä Chapter 4.4
2020/06/19