ABB AC500-S - Page 65

RUN (user acknowledgement request): Alternating blinking of ERR1 & 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 without any errors but waits
for the acknowledgment of a module reintegration (module error is gone).
The fail-safe value “0” is still transferred to the Safety CPU for all passivated input channels. All passivated
output channels have a state of “0”. The PROFIsafe diagnostic bits for all channels have the state of “0” to
indicate that fail-safe values are transferred.
The OA_Req_S bit is reported as “1”.
As soon as the safety application of the Safety CPU sets OA_C (positive edge), the Safety I/O module goes
to RUN (ok) state if no further errors are detected. One has to send the positive edge to the Safety I/O
module until OA_Req_S starts delivering “0”.
PROFIsafe status bits in the F-Host for Safety I/O module:
OA_Req_S = 1
FV_activated_S = 1
Device_Fault = 0
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 65