ABB AC500-S - Page 63

RUN (module passivation): Alternating blinking of ERR1 and ERR2 LEDs
AI581-S
UP 24VDC 2W
4SAI
Safety Analog Input
3.8
UP
3.9
ZP
3.4
3.7
3.0
I2-
3.1
FE
3.2
I3-
3.3
FE
3.5
3.6
ERR1
2.9
ZP
2.8
UP
2.3
2.4
2.5
2.1
2.7
2.6
2.2I1+
2.0
I0+
ERR2
4.9
ZP
4.8
UP
4.7
4.2I3+
4.0
I2+
4.6
4.5
4.4
4.3
4.1
PWR
1.9
ZP
1.8
UP
1.7
1.4
1.0
I0-
1.2
I1-
1.3
FE
1.1
FE
1.5
1.6
ADDR
x10H
ADDR
x01H
C
4
3
B
2
A
1
9
0
8
F
7
E
6
D
5
C
4
3
B
2
A
1
9
0
8
F
7
E
6
D
5
PROFIsafe communication is up and running. The safety application is running with a present module error.
The module and, as a result, all its channels are passivated. Possible reasons for module passivation are:
n PROFIsafe communication failure (CRC error)
n PROFIsafe watchdog timeout exceeded
n Undervoltage/overvoltage detected (Device_Fault status bit = 1)
The fail-safe value “0” is transferred to the Safety PLC for all passivated input channels, if the connection to
the PROFIsafe F-Host is possible. The safety application continuously attempts to establish a communica-
tion to the Safety CPU, if the communication is broken. All passivated output channels have a state of “0”.
A state transition to another RUN mode is only possible if the detected error is gone.
PROFIsafe status bits in the F-Host for Safety I/O module (if communication is possible!):
OA_Req_S = 0
FV_activated_S = 1
Device_Fault = 1 (in case of undervoltage/overvoltage detected) and/or CE_CRC = 1 (in case of communi-
cation error) and/or WD_timeout = 1 (in case of watchdog timeout)
Process data bits in the Safety I/O module process image:
PROFIsafe diagnostic bit = 0
Channel process value = 0
Reintegration request bit = 0
AC500-S Safety Modules
Generic Safety I/O module behaviour > Safety I/O module states
30.03.2017 AC500-S 63