ABB AC500-S Safety User Manual page 29

ID Behaviour
13. One executes "Login" com-
n
mand in CoDeSys Safety
and uses "setpwd" PLC
Browser command to set a
new password, e.g.,
"PWD1" for SM560-S
Safety CPU.
n Power off/on is executed for
SM560-S, but CoDeSys
Safety window remains
open on end-user PC.
One executes "Login" com-
n
mand in CoDeSys Safety
and enters the new pass-
word "PWD1", which was
set in Step 1. One uses
"setpwd" PLC Browser
command to set a new
password, e.g., PWD2, for
SM560-S Safety CPU.
n Power off/on is executed for
SM560-S, but CoDeSys
Safety window remains
open on end-user PC.
n 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 successfully
login to SM560-S Safety
CPU.
14. After power-on, Safety I/O
module goes to SAFE STOP
state with both ERR LEDs =
ON.
15. No login to SM560-S Safety
CPU is possible.
16. After the boot project is loaded
to SM560-S Safety CPU, some-
times the PM5xx CPU seems to
do nothing for about 45 sec-
onds until its ERR-LED is
switched on.
30.03.2017
Overview of AC500-S Safety PLC
Potential Cause
CoDeSys Safety instance
attempts to login to SM560-S
Safety CPU with an old pass-
word.
The configured F_Dest_Add
value in PS501 Control Builder
Plus / ABB Automation Builder
project is not equal to the PRO-
FIsafe address switch value on
the Safety I/O module.
Wrong "Communication param-
eters..." settings are used.
Timeout in PM5xx CPU.
AC500-S
Troubleshooting
Remedy
After resetting SM560-S 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 PS501 Control Builder
Plus / ABB Automation Builder
project is equal to the PROFI-
safe address switch value on
the Safety I/O module.
Check that correct settings of
"Communication parame-
ters ..." are used in CoDeSys
Safety to connect to SM560-S
Safety CPU.
Such situation can be observed
very seldom. There is no
remedy for this behaviour of
PM5xx CPU at the moment.
29