ABB AC500-S - 6.2 Checklist for creation of safety application program

6.2 Checklist for creation of safety application program
Nr. Item to check Fulfilled (Yes / No)? Comment
1. Verify that only safety signals are used for all safety
functions.
2. Verify that not only safety application project is loaded
to SM560-S Safety CPU but also the relevant non-
safety application project is loaded to PM5xx Non-
safety CPU.
V
erify that programs are saved from RAM memory to
the Flash memory.
("Create boot project") is done.
3. Verify that F-Parameters for all Safety I/Os and other
F-Devices set in F-Parameter Editor are the same as
those listed in CoDeSys Safety
, see Global Varia-
bles / PROFIsafe (
Ä Chapter 4 “Configuration and
programming” on page 165).
4. F_Source_Add is the virtual address (different to
F_Device_Add which is also physical). F-Host can
handle more than one F_Source_Add, if required,
e.g., for PROFIsafe Master - Master coupling of dif-
ferent network islands. V
erify that no ambiguous
F_Source_Add settings for various F-Devices were
set for the given safety application.
Note:
The rule “F_Source_Add <> F_Dest_Add for the
given F-Device” is automatically checked by PS501
Control Builder Plus V2.2.1 (or newer) / Automation
Builder 1.0 (or newer).
5. Validate iParameters. Two options are available:
A) V
alidate that all iParameters (Input delay, channel
configuration, etc.) for all Safety I/Os and other F-
Devices are correct with a given F_iPar_CRC value
using appropriate functional validation tests for those
parameters (contact ABB technical support if ques-
tions arise)
or
B) Use a special verification procedure defined in
Ä Chapter 6.5 “Verification procedure for safe iPara-
meter setting in AC500-S Safety I/Os” on page 412 to
validate each iParameter and then carry out only
functional safety validation tests of your application
(no need to check each single iParameter value). You
have to provide a report confirming that all iParame-
ters were checked as described in
Ä Chapter 6.5
“Verification procedure for safe iParameter setting in
AC500-S Safety I/Os” on page 412.
Make sure that all F_iPar_CRC are > 0.
Checklists for AC500-S Commissioning
Checklist for creation of safety application program
30.03.2017AC500-S406