ID Behaviour Potential Cause Remedy
22. “Enable debug” parameter =
“ON” was set for SM560-S
Safety CPU and correctly
loaded to PM5xx. However, one
still cannot debug on SM560-S
Safety CPU.
CoDeSys Safety projects on
your PC and in SM560-S Safety
CPU are not the same. You
may get also the following mes-
sage window with the text: “The
program has changed! Down-
load the new program?”.
Download your CoDeSys
Safety project from your PC to
SM560-S Safety CPU and
debugging shall be possible
now.
23. After PLC browser command
“reset” for SM560-S Safety
CPU, SM560-S goes to
DEBUG STOP state (Non-
safety mode). Safety I/O mod-
ules go to module passivation
state. If you login to SM560-S
Safety CPU, then you can see
OA_Req_S = TRUE bits in
PROFIsafe instances of F-
Devices. The safety application
is not executed by SM560-S
Safety CPU, but you still can
set OA_C = TRUE for F-
Devices and they will go to
RUN mode. SM560-S remains
in DEBUG STOP state (Non-
Safety) all the time.
PROFIsafe F-Host does not run
in fail-safe mode after PLC
browser command “reset” .
This behaviour will be fixed in
the future versions of SM560-S
Safety CPU. Due to the fact
that SM560-S Safety CPU is in
DEBUG STOP state (Non-
safety mode) all the time, this is
not a safety critical case and
can be easily tolerated.
Overview of AC500-S Safety PLC
Troubleshooting
30.03.2017 AC500-S 31
To Next Page
Loading...
