ABB AC500-S Safety User Manual page 327

No. Item to check
6. Verify that CODESYS Safety programming guidelines
were properly used in the safety application program
Ä Chapter 4.4 "CODESYS Safety programming guide-
lines" on page 172.
7. All signals from the non-safety user program on non-
safety CPU, which are evaluated in the safety program
on the safety CPU, have to be also included when the
safety application program is printed out.
8. Has a review of the safety application program been car-
ried out by a person not involved in the program crea-
tion?
9. Has the result of the safety application program review
been documented and released (date/ signature)?
10. Was a backup of the complete safety (see note below)
and non-safety project created before loading programs
on safety and non-safety CPUs?
Note:
● Make sure that file name, change date, title, author,
version, description and CRC of the CODESYS
Safety boot project are documented as a backup.
● No further changes are allowed for safety parts in
Automation Builder project and CODESYS Safety. If
any changes are still done, then they will lead to a
new CODESYS Safety boot project CRC, which will
require re-doing this checklist from the beginning.
11. Verify using CODESYS Safety menu item "Online
è Check boot project in PLC" that offline CODESYS
Safety project and the boot project on the safety CPU are
identical (file name, change date, title, author, version,
description and CRC).
12. If floating-point operations are used, verify that rules pre-
Ä Chapter 3.1.2.2 "Floating-point operations"
sented in
on page 33 are taken into account and do not lead to any
unsafe states in the safety application program.
13. Verify that POU SF_WDOG_TIME_SET is called once in
the safety application program and the watchdog time is
correctly selected.
14. Verify that a password for the safety CPU is set to pre-
vent an unauthorized access to its data.
15. Verify that only authorized personnel has "Write" access
for safety module parameter settings and programs in
Automation Builder and CODESYS Safety projects.
16. Verify that correct value for power supply supervision
using POU SF_MAX_POWER_DIP_SET was set to have
a correct system behavior in case of under- or over-
voltage.
17. Verify that POU SF_SAFETY_MODE is correctly used in
the safety application program to avoid unintended safety
program execution in DEBUG (non-safety) mode.
2020/06/19
Fulfilled (yes / no)?
3ADR025091M0208, 12, en_US
Checklists for AC500-S commissioning
Checklist for creation of safety application program
Comment
327