Phoenix Contact RFC 4072S, User Manual, Page: 246 / 272

RFC 4072S
246 / 272
PHOENIX CONTACT 108580_en_02
C 1.2 Programming
Checklist for programming the PROFIsafe system
Equipment identification
Date
Editor Test engineer
Comment
No
.
Requirement Yes
1 Have the requirements from the applicable standards for the sys-
tem/machine been observed and met in the programming phase?
2 Have the user rights for the safety-related application program been
defined in PLCnext Engineer?
3 Has the complete safety-related application program been created in
PLCnext Engineer?
4 Have additional application-specific programming guidelines been cre-
ated and observed within the program specification for the planning
phase?
5 Are standard input signals exclusively used to program standard opera-
tions (e.g., for the enable principle using the EN_OUT block or for
acknowledgment)?
6 Are the parameterized F-Addresses (F-Source Addresses of PROFIsafe
controllers and F-Destination Addresses of PROFIsafe devices) unique
throughout the network?
7 Is the F_WD_Time calculated for each PROFIsafe device parameterized
in the “Safety Parameters” editor in PLCnext Engineer?
8 Has a project password been defined?
9 Who is authorized to “develop” the safety-related application program? Names:
10 Has a controller password been defined?
11 Has project information been entered in the “Description” field in the
“Properties” editor in the “Project” editor group?
Type:
Location:
12 Are possible reciprocal effects due to exchange variables between the
programming of the standard controller and the iSPNS 3000 in the
RFC 4072S taken into consideration and clear?
13 Has the following been observed when programming/configuring your
safety logic?
– Switching from the safe state (substitute value = 0) to the operating
state can generate an edge change (zero/one edge).
– In the safety logic, take measures to prevent this edge change
resulting in unexpected machine/system startup or restart.
Date Signature (editor)
Date Signature (test engineer)