ABB AC500-S Safety User Manual page 24

Overview of AC500-S safety PLC
Troubleshooting
ID Behavior
1. Safety CPU is in RUN or DEBUG
RUN state, but all safety I/O mod-
ules suddenly go to RUN (module
passivation) state.
2. No log in is possible to the safety
CPU from CODESYS Safety
project.
3. During closing or saving of the
project, modification of CODESYS
Safety project, etc. with
Automation Builder, you may see
that no reaction comes from the
Automation Builder and/or
CODESYS Safety project. It is as
if the application hangs.
4. Your safety digital input channel is
occasionally passivated with an
internal error diagnostic message
on V2 non-safety CPU (Err. Class:
E3, Comp.: 14, Device: 1 ... 10,
Module: 31, Channel: 31, ID: 43).
5. DX581-S module is powered on,
but no power supply is connected
to UP clamps of DX581-S
module.
6. Some channels of a safety I/O
module or a complete safety I/O
module is occasionally passivated
without a reason (wiring is correct,
etc.).
7. With the increased number of
safety I/O modules in the system,
it takes longer to execute "Create
boot project" command for the
safety CPU.
8. After log in to CODESYS Safety,
one can observe a long list of
internal constants with a green
font color for PROFIsafe F-Host
instances.
24
Potential cause
Your program may contain end-
less loop which prevents safety
CPU to send valid safety tele-
grams to safety I/O modules in a
proper time manner (within config-
ured watchdog time).
CODESYS visualization was con-
nected directly to the safety CPU,
which blocks the connection to
the safety CPU.
Only one connection to the safety
CPU is allowed at a time.
The user management of
Automation Builder requires that
you confirm your log-on creden-
tials for safety components and
issues a log-on message box
which is not in the foreground.
Your previous log-on session has
expired.
One of potential reasons is that
your input signal frequency
exceeded an allowed input
channel signal frequency
Ä allowed frequency ranges:
Chapter 3.3.2 on page 62.
Wiring error on DX581-S module
when +24 V DC is connected to at
least one of the safety digital
output clamps of DX581-S. As a
result, DX581-S is powered on
through safety digital outputs.
No proper electrical contact
between a safety I/O module and
TU582-S terminal unit.
The safety CPU is a single-
threaded system. The more safety
I/O modules are in the system,
the higher is the internal cycle
time of the safety CPU to process
safety I/O relevant data.
In CODESYS Safety, the option
"Replace constants" is selected.
3ADR025091M0208, 12, en_US
Remedy
Check (debug) your safety appli-
cation program and make sure
that no endless loop(s) are in your
safety application program.
Disconnect CODESYS visualiza-
tion from the safety CPU.
Find a log-on message in the
background of your Windows
desktop, log-on and continue your
previous actions. Set longer user
log-on session time for
Automation Builder if this behavior
repeats Ä [4].
Check that your input signal does
not exceed the allowed digital
input signal frequency.
Check the wiring of DX581-S and
disconnect +24 V DC from the
safety digital output clamp(s).
Make sure that you pressed the
safety I/O module into TU582-S
terminal unit with a force of at
least 100 N, as prescribed in
AC500-S checklists.
Currently, there is no possibility to
change this behavior other than to
split safety I/Os to different safety
CPUs, so that each safety CPU
has less safety I/Os to handle.
Go in CODESYS Safety menu to
"Project è Options è Build"
Unselect option "Replace
constants" .
2020/06/19