ABB AC500-S Safety User Manual page 45

DEBUG STOP
Without error of severity level 3 or 4
In this non-safe state, a user is able to intervene in safety program execution by setting break-
points, etc., similar to DEBUG RUN state. The safety application program is not executed in
DEBUG STOP (non-safety) state. The PROFIsafe F-Host and F-Devices (SM560-S-FD-1 and
SM560-S-FD-4) of the safety CPU send PROFIsafe telegrams with fail-safe "0" values and set
FV_activated for all safety I/O modules and F-Devices.
If CODESYS online service "RUN" is called in the safety application program, the safety CPU
switches to DEBUG RUN state.
All CODESYS online services are available in this state.
In case of CODESYS online commands "Step in" , "Step over" , "Single cycle" and when the
breakpoint is reached, there is a switch between DEBUG RUN and DEBUG STOP states (tran-
sitions 13 and 14 in Fig. 12 on page 43).
One can go back to a safe RUN state only using powering off/on or "reboot" PLC browser/shell
command on non-safety CPU.
3.1.5.2 Transitions between safety CPU states
Transition From
(Fig. 12 on
page 43)
(1) INIT
(2) RUN
(3) INIT
(4) DEBUG STOP
2020/06/19
Safety CPU - SM560-S / SM560-S-FD-1 / SM560-S-FD-4 > Safety CPU module states
SM560-S
PWR
DIAG
RUN
I-ERR
E-ERR
DANGER!
Since PROFIsafe F-Host continues to run in DEBUG STOP (non-safety) state, it
is possible to reintegrate passivated safety I/O modules and bring them in the
safety RUN state. One can force variables for safety I/O modules, for example,
to activate safety outputs.
In case of or DEBUG RUN (non-safety) or DEBUG STOP (non-safety) mode
activation on safety CPU, the responsibility for safe process operation lies
entirely with the organization and person responsible for the activation of
DEBUG RUN (non-safety) or DEBUG STOP (non-safety) mode.
To
RUN
INIT
DEBUG STOP
INIT
3ADR025091M0208, 12, en_US
With error of severity level 3 or 4
PWR
DIAG
RUN
I-ERR
E-ERR
Description
● Initialization was successful
● Boot project is available and there is no configu-
ration error or any other error of severity level 1
or 2.
Powering off/on or "reboot" PLC browser/shell com-
mand from non-safety CPU
● Initialization was successful
● No boot project is available or error of severity
level 3
● Switch address 0xFF was set on the safety CPU
Powering off/on or "reboot" PLC browser/shell com-
mand from non-safety CPU
AC500-S safety modules
SM560-S
45