5. System Functions After Upgrade
5-2
TI 33K01B10-50E
Execution Timing of Function Blocks
The execution timing of function blocks (or CENTUM instruments) differs as shown below
depending on the type of FCS. In upgraded FCS, to execute function blocks in exactly the same
timing as before the upgrade, control drawings must be created considering the execution order
of the control drawings and the function blocks contained in the drawings.
Table Execution Timing
System Scan period Execution order of function blocks
CENTUM V
CFCS2
CFSS
Standard: 1 sec
High speed: 200 msec
At every scan period, executed in the following order:
Updateofinternaltimersandpulsecounters→annunciator
messages→feedbackcontrolinstruments→sequence
tables
CENTUM-XL
EFCS
EFCS-H2,
H4
Standard: 1 sec
High speed: 500 msec/200 msec
At every scan period, executed in the following order:
Updateoftimersandpulsecounters→switchinstruments
→batchstatusindicators→sequencetable→feedback
controlinstruments→annunciatormessages
CENTUM VP
RFCS5-V
RFCS5-XL
FFCS-V
Standard:1sec(xed)
Middle speed: 1 sec/500 msec/200 msec
High speed: 500 msec/200 msec/
100 msec/50 msec
At every scan period, executed in the following order:
Functionblocks→annunciatormessages→SEBOL/
SFC Function blocks are executed in the order of control
drawings;withinadrawing,intheorderoffunctionblock
numbers.
Support of YS Instruments
The YS instrument blocks (installed via LCS card) supported in CENTUM V and CENTUM -XL
systems are included in the standard software.
Support of LD1 and LCU
CLDU and ULDU cannot be used.
Substitute YS instruments for them.
Communication with Subsystem
It is recommended to substitute an ALR111 card for CFGW, EFGW and RS4 card.
IOP
Care should be exercised with regards to IOP because its behavior changes between before
and after upgrade. Particularly, if any block includes calculation using a tag IOP or a sequence
conditional on IOP, you need to review the IOP behavior.
Mar. 27, 2015-00