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

RFC 4072S
34 / 272
PHOENIX CONTACT 108580_en_02
The following diagram shows the dependency of the iSPNS 3000 cycle time T
ZSPNS
as the
number of F-Devices in the application increases.
Figure 2-6 Cycle time of the iSPNS 3000 T
ZSPNS
Key:
To verify the value of the iSPNS 3000 cycle time roughly determined during the planning
phase, the actual value reached for the iSPNS 3000 cycle time should be read on the display
of the RFC 4072S during the startup phase (S-PLC cycle time).
• For this, open the “S-PLC DETAILS” menu by tapping the “Safety PLC” tile (A in
Figure 2-7 on page 35 ).
HAT The cycle time of the iSPNS 3000 (T
ZSPNS
) can be estimated during the sys-
tem/machine planning phase using the diagram in Figure 2-6 . Here, an applica-
tion program that grows in proportion to the number of F-Devices is taken into
consideration.
T
ZSPNS
Cycle time of the iSPNS 3000 (S-PLC cycle time) [in milliseconds]
TN Number of F-Devices in the application
The cycle time of the iSPNS 3000 (T
ZSPNS
) is marginally dependent
on the size of the safe application program (iSPNS 3000 program
runtime (S-PLC runtime)), the amount of safe process data, and the
number of standard exchange variables for the standard controller.
Both values, iSPNS 3000 cycle time (S-PLC cycle time) and program
runtime (S-PLC runtime), can be viewed in the display of the
RFC 4072S (see Figure 2-7 on page 35 ).
The “Safety Cockpit” editor in the editor group of the “Safety PLC” in
PLCnext Engineer (see Figure 2-8 on page 35 ) displays the
iSPNS 3000 cycle time if the software is connected online to the
RFC 4072S.
108580A006
10 20 30 40 50 60 70 80 0
0
10
2
4
6
8
T / ms
TN
ZSPNS