
RFC 4072S
PHOENIX CONTACT
108580_en_02
2.3.3
Determining F_WD_Time IN/F_WD_Time OUT to be param-
eterized and checking/validating that the safety function
can be implemented
Having calculated the upper and lower limits of the F_WD_TimeIN/F_WD_TimeOUT as
described in the two previous sections, you now need to determine the F_WD_Ti-
meIN/F_WD_TimeOUT watchdog times that are to be parameterized within these limits for
the safety function that is to be implemented. You then need to check/validate that the
required safety function can be implemented using the determined values.
The values are essentially determined as follows:
The relationship between the values for F_WD_Time IN and F_WD_Time OUT is based on
the relationship for the minimum F_WD_Time and the system availability determined in Sec-
.
Example
Based on the maximum possible safety function response time, the following requirement
must be met:
The watchdog times to be parameterized are chosen as follows in the example:
Factor 2 has been chosen here so that it is still possible to later increase the PROFINET
repeat cycles by the monitor factor or the PROFINET update time without endangering sys-
tem availability by exceeding the F_WD_Time monitoring time.
As a result, the values selected in the example project (see
and
) described in
are within the permissible range:
Sum of the watchdog times is less than 200 ms.
(F_WD_Time IN
min
+ F_WD_Time OUT
min
)
<
(F_WD_Time IN + F_WD_Time OUT)
<
(F_WD_Time IN
max
+ F_WD_Time OUT
max
)
F_WD_Time IN
max
+ F_WD_Time OUT
max
= 200 ms
(Upper limit from the safety
function)
F_WD_Time OUT
min
= 24.5 ms
(From the example in
)
F_WD_Time IN
min
= 50 ms
(Assumed for the example
calculation)
F_WD_Time OUT
≈
2 x 24.5 ms
F_WD_Time OUT = 50 ms
F_WD_Time IN = 2 x 50 ms = 100 ms
Minimum F_WD_Time (IN+OUT) < F_WD_Time (IN+OUT) to be parameterized < Maximum F_WD_Time (IN+OUT)
(50 + 24.5) ms
<
(100 + 50) ms
<
200 ms
Summary of Contents for RFC 4072S
Page 22: ...RFC 4072S 22 272 PHOENIX CONTACT 108580_en_02...
Page 68: ...RFC 4072S 68 272 PHOENIX CONTACT 108580_en_02...
Page 82: ...RFC 4072S 82 272 PHOENIX CONTACT 108580_en_02...
Page 142: ...RFC 4072S 142 272 PHOENIX CONTACT 108580_en_02...
Page 154: ...RFC 4072S 154 272 PHOENIX CONTACT 108580_en_02...
Page 222: ...RFC 4072S 222 272 PHOENIX CONTACT 108580_en_02...
Page 234: ...RFC 4072S 234 272 PHOENIX CONTACT 108580_en_02...
Page 254: ...RFC 4072S 254 272 PHOENIX CONTACT 108580_en_02...
Page 264: ...RFC 4072S 264 272 PHOENIX CONTACT 108580_en_02...
Page 268: ...RFC 4072S 268 272 PHOENIX CONTACT 108580_en_02...
Page 271: ......