Technical data
20.6 Runtimes of the FCs and FBs for redundant I/Os
S7-400H
System Manual, 03/2012, A5E00267695-11
433
Block Runtime in stand-alone/single mode Runtime in redundant mode
FB 452 RED_DIAG Called in OB 72: 160 µs
Called in OB 82, 83, 85:
250 µs + 5 µs / configured module pairs
Under extreme conditions the runtime of FB
RED_DIAG is increased up to 1.5 ms. .
This is the case when the working DB is 60
KB or larger and if there are interrupt trigger
addresses that do not belong to the
redundant I/O.
Called in OB 72: 360 µs
Called in OB 82, 83, 85:
430 μs (basic load) + 6 μs / configured
module pairs
Under extreme conditions the runtime of FB
RED_DIAG is increased up to 1.5 ms. .
This is the case when the working DB is 60
KB or larger and if there are interrupt trigger
addresses that do not belong to the
redundant I/O.
FB 453 RED_STATUS 160 μs 4 μs/ configured module pairs *
number of module pairs)
The runtime depends on the random position
of the module being searched for in the
working DB.
When a module address is not redundant, the
entire working DB is searched. This results in
the longest runtime of FB RED_STATUS.
The number of module pairs is based either
on all inputs (DI/AI) or all outputs (DO/AO).
350 μs + 5 μs / configured module pairs *
number of module pairs)
The runtime depends on the random position
of the module being searched for in the
working DB.
When a module address is not redundant, the
entire working DB is searched. This results in
the longest runtime of FB RED_STATUS.
The number of module pairs is based either
on all inputs (DI/AI) or all outputs (DO/AO).
NOTICE
These are guide values, not absolute values. The actual value may deviate from these
specifications in some cases. This overview is intended as a guide and should help you
estimate how use of the RED_IO library may change the cycle time.
To Next Page
Loading...
