Nr.
Item to check
Fulfilled (Yes / No)?
Comment
16.
Verify that correct value for power supply supervision
using POU SF_MAX_POWER_DIP_SET was set to
have a correct system behaviour in case of under- or
overvoltage.
17.
Verify that POU SF_SAFETY_MODE is correctly
used in the safety application program to avoid unin-
tended safety program execution in DEBUG (Run)
non-safety mode.
18.
Verify that no
“Update Device …”
, Export/Import,
Copy/Paste and Archive related functions in PS501
Control Builder Plus V2.2.1 (or newer) / Automation
Builder 1.0 (or newer) were executed on Safety mod-
ules after the project was validated.
If the functions mentioned above were used and this
lead to a CoDeSys safety boot project with a new
CRC, then a full functional testing of all parts of the
safety-oriented application has to be performed. This
test must be carried out with the machine in its final
configuration including mechanical, electrical and
electronic components, sensors, actuators, and soft-
ware.
19.
Verify using library CRC, shown in CoDeSys Safety,
that only TÜV certified safety libraries with correct
Chapter 4.6.1 “Overview” on page 224
used in the given CoDeSys Safety project to execute
safety functions. All other user-defined libraries have
to be separately validated by the end-user to qualify
for the given safety application.
20.
Make sure that internal POUs from SafetyUtil_CoD-
eSys_AC500_V22.lib and internal actions from Safe-
tyBase_PROFIsafe_AC500_V22_Ext.lib (or older ver-
sions) are not called by end-user program, which
starts from PLC_PRG as the main root.
21.
Make sure that all three system events
(
“CallbackInit”
,
“CallbackReadInputs”
and
“CallbackWriteOutputs”
) in
“Resources
è
Task configuration
è
System Events”
of CoDeSys
Safety remain selected.
Checklists for AC500-S Commissioning
Checklist for creation of safety application program
30.03.2017
AC500-S
408
