ABB AC500-S Safety User Manual page 140

Configuration and programming
System configuration and programming > Instantiation and configuration of safety modules / definition of variable names
Furthermore, each F-Device has a special "I/O Mapping" tab in which variable names for input
and output signals, PROFIsafe diagnostic bits, etc. can be defined.
Fig. 69: Example with AI581-S module for variable mapping
It is also valid for DX581-S and DI581-S safety modules; the only difference is the number of
input and output channels. Each process channel (Input 0 - Input 3 for AI581-S) has additionally
the following bits:
● one bit for safe diagnostic (Safe_Diag bit) to be able to differentiate if the process value is
the real process state or "0" value due to channel or module passivation.
● one bit Rei_Req for channel reintegration request, which can be used in the safety applica-
tion program as a signal that external error (e.g., sensor wiring error) was fixed and the
channel can be reintegrated in the safety control. Higher overall system availability can be
expected for end-customers, because they can selectively decide which channels have to
be acknowledged and which not.
● one bit Ack_Rei for channel reintegration if the error was fixed (e.g., external sensor wiring
was corrected). One can also define one variable as a BYTE for all Ack_Rei bits and use
0xFF value to acknowledge all errors at once.
140
DANGER!
One can also use generic device configuration view from "DI581-S
Parameters" , "DX581-S Parameters" or "AI581-S Parameters" tab to edit
module and channel parameters. However, change of safety I/O parameters
using generic device configuration view is not recommended due to poten-
tial user mistakes during the parameter setting using integer numbers.
DANGER!
If data types like Unsigned16, Unsigned32, Integer16, Integer32 or Float32,
which require more than one byte, are used in PROFIsafe data, note the fol-
lowing. The byte order in such data types depends on the used PROFIsafe
device endianness and selected AC500 CPU type. V2 CPU supports big-endian
and V3 CPU supports little-endian. Make sure that the symbolic variables are
mapped properly and the delivered safety data is correctly represented in your
safety application.
3ADR025091M0208, 12, en_US 2020/06/19