![ABB AC500-S Safety User Manual Download Page 67](http://html.mh-extra.com/html/abb/ac500-s/ac500-s_safety-user-manual_2916067.webp)
3.2.2.2
Transitions between Safety I/O module states
ID*
From
To
Description
(1)
INIT
RUN (ok)
Safety I/O module comes to this state directly
after INIT during a normal start-up
(2)
RUN (ok)
INIT
Powering off/on
(3)
INIT
RUN (module
passivation)
PROFIsafe watchdog, PROFIsafe communication
error or undervoltage/overvoltage was detected
directly after INIT.
The Safety I/O module can reach this state also
after powering off/on the Safety I/O module if
Safety CPU with PROFIsafe F-Host continues
running and brings Safety I/O module to a fail-
safe RUN (module passivation) state after pow-
ering off/on
(4)
RUN (module
passivation)
INIT
Powering off/on
(5)
INIT
SAFE STOP
Fatal error(s) (CPU test, RAM test, etc. failed)
took place
(6)
SAFE STOP
INIT
Powering off/on
(7)
RUN (ok)
RUN (channel
passivation and
reintegration)
Channel error was identified by the Safety I/O
module. The tests (whenever it is possible) are
continued for the given channel to be able to see
if the error is gone (e.g., wiring error was cor-
rected). As soon as the error is gone, the module
sets “Reintegration request” bit = “1” for the given
channel.
(8)
RUN (channel
passivation &
reintegration)
RUN (ok)
n
The channel error is gone.
n
“Reintegration request” bit = 1 is set for the
given channel by the Safety I/O module.
n
“Acknowledge reintegration” bit (positive
edge) is set by PROFIsafe F-Host for the
given channel
(9)
RUN (ok)
SAFE STOP
Fatal error(s) (CPU test, RAM test, etc. failed)
took place
(10)
RUN (ok)
RUN (module
passivation)
PROFIsafe watchdog, PROFIsafe communication
error or undervoltage/overvoltage was detected.
(11)
RUN (ok)
RUN (module
passivation with
a command)
“activate_FV_C = 1” command was sent from the
Safety CPU
(12)
RUN (channel
passivation &
reintegration)
SAFE STOP
Fatal error(s) (CPU test, RAM test, etc. failed)
took place
(13)
RUN (module
passivation)
SAFE STOP
Fatal error(s) (CPU test, RAM test, etc. failed)
took place
AC500-S Safety Modules
Generic Safety I/O module behaviour > Safety I/O module states
30.03.2017
AC500-S
67