ABB AC500-S Safety User Manual page 26

Overview of AC500-S safety PLC
Troubleshooting
ID Behavior
13. ● One executes "Login" com-
mand in CODESYS Safety
and uses "setpwd" PLC
browser command to set a
new password, e.g., "PWD1"
for the safety CPU.
● Power off/on is executed for
the safety CPU, but
CODESYS Safety window
remains open on end-user
PC.
● One executes "Login" com-
mand in CODESYS Safety
and enters the new password
"PWD1", which was set in
Step 1. One uses "setpwd"
PLC browser command to set
a new password, e.g., PWD2,
for the safety CPU.
● Power off/on is executed for
the safety CPU, but
CODESYS Safety window
remains open on end-user
PC.
● One executes "Login" com-
mand in CODESYS Safety
and an error message is
shown "You have entered a
wrong PLC password!". After
pressing "OK" , you still have
a possibility to enter a new
password "PWD2" and suc-
cessfully log in to safety CPU.
14. After power-on, safety I/O module
goes to SAFE STOP state with
both ERR LEDs = ON.
15. No log in to the safety CPU is
possible.
16. After the boot project is loaded to
the safety CPU, sometimes the
V2 non-safety CPU seems to do
nothing for about 45 seconds until
its ERR-LED is switched on.
17. After power-on of the safety CPU,
it may happen that the safety
CPU does not go to RUN mode.
DIAG LED is ON and no boot
project is loaded to the safety
CPU. If you attempt to log in to
the safety CPU, then the following
error message can be seen in
CODESYS Safety: "No program
on the controller! Download the
new program?".
26
Potential cause
CODESYS Safety instance
attempts to log in to the safety
CPU with an old password.
The configured F_Dest_Add value
in Automation Builder project is
not equal to the PROFIsafe
address switch value on the
safety I/O module.
Wrong "Communication parame-
ters..." settings are used.
Timeout in V2 non-safety CPU.
Safety CPU power dip function is
triggered if the pause between the
power-off and the following
power-on phase is less than 1.5 s.
The boot project is still on the
safety CPU, but not loaded due to
power dip detection. Thus, there
is no need to reload any boot
project to the safety CPU.
3ADR025091M0208, 12, en_US
Remedy
After resetting the safety CPU
password, close CODESYS
Safety instance and open it again.
The error message will not appear
again.
Make sure that F_Dest_Add value
in Automation Builder project is
equal to the PROFIsafe address
switch value on the safety I/O
module.
Check that correct settings of
"Communication parameters..."
are used in CODESYS Safety to
connect to the safety CPU.
Such situation can be observed
very seldom. There is no remedy
for this behavior of V2 non-safety
CPU at the moment.
Do power-off and power-on of the
safety CPU with a pause between
power-off and power-on phase ³
1.5 s.
2020/06/19