YOKOGAWA Centum-XL - Page 75

Appendix 4. Functions Related to Upgrade
App.4-6
TI 33K01B10-50E
Table Functions Related to Upgrade Before R5.03.00 (6/7)
Item Function
CENTUM V or
CENTUM-XL
CENTUM VP Measures
Handling
when IOP
occurs.
Limitation on
operation when
an IOP occurs.
Limited only by tags directly linked to input cards.
PresenceorabsenceofIOPdetectionsisspecied
throughinstrumentdetailedspecications.
SpecifyingYesin[Limitation
on operation when IOP
occurs] in the function
block detail builder allows
operation in the current
mode not only without
sending BAD to PV-value
data statuses but also
without falling-back to block
mode manually.
Switch
instrument/
MC
instrument
Apply to MV
values when
setting CSV
values
Possible to rewrite
MV values of switch
instrument/MC
instrument directly from
other functional blocks
such as a sequence
table
If CSV values of switch
instrument/MC instrument
are rewritten from other
functional blocks such
as a sequence control
block, the CSV values are
applied to the MV values
at the timing when the
switch instrument/MC
instrument start next time
CSV values are applied to
the MV values immediately
if you specify “Yes” in “Apply
to MV values when setting
CSV values of switch
instrument/MC instrument”
in FCS properties
Timer/soft
counter/pulse
train counter
block (TM/
CTS/CTP)
Action in PALM Pre-alarm status (PALM)
of block status occurs
at the same time as
the time up status “DV
(remaining time of timer)
≤0”(CTUP)
If block status reaches
the time up status “DV
(remaining time of timer)
≤0,”pre-alarmstatus
(PALM) of block status is
released
Pre-alarm status (PALM)
of block status occurs at
the same time as the time
up status “DV (remaining
timeoftimer)≤0”(CTUP)if
you specify “Yes” in “PALM
action of TM/CTS/CTP:
PALM continues after CTUP
occurs” in FCS properties
Action at the
time of IOP
Action resulting
from specifying
IOP detection
The action resulting from specifying IOP detection in
IOP/at the time of IOP occurrence and PV in IOP/at
the time of IOP occurrence is different between XL or
earlier and CS or later
The action resulting from
specifying IOP detection
in IOP/at the time of IOP
occurrence and PV in
IOP/at the time of IOP
occurrence becomes the
same as that in XL if you
specify “Yes” in “Action
at the time of IOP is
compatible with XL” in FCS
properties
CALCU data
range
Normalization
of CALCU data
and range limit
Numerical data
is processed with
normalized data in the
range between -1 and
+1, so there is no data
that exceeds the high
and low limits of the
scale
Numerical data
is processed with
engineering unit data and
there is data outside the
scale, so computational
blocks need to be added
to provide limits to the
range
If the data to be referred
to/set at the connection
destination of IN terminal/
Qnn terminal or OUT
terminal/Jnn terminal of
CALCU, or in computational
expressions is within the
PV range (SH/SL), within
the SV range (SSH/SSL),
or within the MV range
(MSH/MSL), the data is
handled as the normalized
data in the computational
expressions. Then, if each
data exceeds the range at
the connection destination,
the data is limited so that it
comes within the range.
Mar. 27, 2015-00