0% found this document useful (0 votes)
154 views10 pages

Calculation Blocks for Engineers

The document discusses the General-Purpose Calculation Blocks (CALCU, CALCU-C) function blocks. It describes that these blocks execute predefined calculation algorithms and can handle both numeric and string data. The blocks perform input processing, calculation, output processing, and alarm checking. They can be configured for periodic or one-shot execution at different scan rates. The document also provides details on specific functions like error handling, totalization, normalization, and output limiting.

Uploaded by

Dinar Lubis
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
154 views10 pages

Calculation Blocks for Engineers

The document discusses the General-Purpose Calculation Blocks (CALCU, CALCU-C) function blocks. It describes that these blocks execute predefined calculation algorithms and can handle both numeric and string data. The blocks perform input processing, calculation, output processing, and alarm checking. They can be configured for periodic or one-shot execution at different scan rates. The document also provides details on specific functions like error handling, totalization, normalization, and output limiting.

Uploaded by

Dinar Lubis
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 10

1.

33 General-Purpose Calculation Blocks (CALCU, CALCU-C) Page 1 of 17

1.33 General-Purpose Calculation Blocks (CALCU,


CALCU-C)
The General-Purpose Calculation Blocks (CALCU, CALCU-C) are used when defining arbitrary calculation
algorithms.

„ General-Purpose Calculation Blocks (CALCU, CALCU-C)


▼ Connection
The General-Purpose Calculation Block (CALCU) is a function block that executes pre-defined arbitrary
calculation algorithms. Calculation algorithms are defined using the general-purpose calculation expression
description language.
The Calculation Block with String I/O (CALCU-C) has the same function as the General-Purpose Calculation
Block (CALCU), but the former has I/O terminals that can handle string data and a part of the I/O data is
used only for string data.
Here is a function block diagram of the General-Purpose Calculation Blocks (CALCU, CALCU-C).

Figure 1.33-1 Function Block Diagram of General-Purpose Calculation Blocks (CALCU, CALCU-C)

The following tables show the connection types and connection destinations of the I/O terminals of General-
Purpose Calculation Blocks (CALCU, CALCU-C).
Table 1.33-1 Connection Types and Connection Destinations of the I/O Terminals of General-Purpose
Calculation Block (CALCU)

Connection type(*1) Connection destination(*1)


I/O terminal Data Data Condition Status Terminal Process Software Function
reference setting testing manipulation connection I/O I/O block
Calculation
IN x x Δ x x x
input
Q01 nth
to calculation x x Δ x x x
Q07 input
Calculation
OUT x x x x x x
output
J01 nth
to calculation x x Δ x x x
J03 output
Auxiliary
SUB x Δ x x x
output

file:///C:/Program%20Files%20(x86)/Yokogawa/IA/iPCS/Products/CENTUMVP/Pro... 25/12/2014
1.33 General-Purpose Calculation Blocks (CALCU, CALCU-C) Page 2 of 17

*1: x: Connection available


Blank: Connection not available
Δ: Connection is available only when connecting to a switch block (SW-33, SW-91) or inter-station data link
block (ADL).

Table 1.33-2 Connection Types and Connection Destinations of the I/O Terminals of General-Purpose
Calculation Block with String I/O (CALCU-C)

Connection type(*1) Connection destination(*1)


I/O terminal Data Data Condition Status Terminal Process Software Function
reference setting testing manipulation connection I/O I/O block
Calculation
IN x x Δ x x x
input
Q01 nth
to calculation x x Δ x x x
Q03 input
Q04 nth
to calculation x Δ x
Q07 input
Calculation
OUT x x x x x x
output
nth
J01 calculation x x Δ x x x
output
J02 nth
to calculation x Δ x
J03 output
Auxiliary
SUB x Δ x x x
output
*1: x: Connection available
Blank: Connection not available
Δ: Connection is available only when connecting to a switch block (SW-33, SW-91) or inter-station data link
block (ADL).

„ Functions of General-Purpose Calculation Blocks (CALCU,


CALCU-C)
The CALCU and CALCU-C blocks perform input processing, calculation processing, output processing, and
alarm processing.
The processing timings available for the CALCU and CALCU-C blocks are a periodic startup and a one-shot
startup. Selections available for the scan period used to execute a periodic startup include the basic scan
period, the medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the FFCS series, KFCS2, KFCS, LFCS2, and LFCS.

SEE For more information about the types of input processing, output processing, and alarm processing
ALSO possible for the CALCU and CALCU-C blocks, refer to:
1.3.1, "Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block"
For more information about the input processing, refer to:
3, “Input Processing” in the Function Blocks Overview (IM 33K03E21-50E)
For more information about the output processing, refer to:
4, “Output Processing” in the Function Blocks Overview (IM 33K03E21-50E)
For more information about the alarm processing, refer to:
5, “Alarm Processing - FCS” in the Function Blocks Overview (IM 33K03E21-50E)

file:///C:/Program%20Files%20(x86)/Yokogawa/IA/iPCS/Products/CENTUMVP/Pro... 25/12/2014
1.33 General-Purpose Calculation Blocks (CALCU, CALCU-C) Page 3 of 17

z Input Processing of General-Purpose Calculation Blocks (CALCU,


CALCU-C) when a Calculation Input Value Error is Detected
The CALCU and CALCU-C blocks perform special input processing when an abnormal calculation input value
is detected.

z Exact Totalization Pulse Train Input of General-Purpose Calculation


Blocks (CALCU, CALCU-C)
When the input signal conversion is specified with [Exact Totalization Pulse Train Input], the totalization can
use the calculation output value (CPV).

z Calculation Processing of General-Purpose Calculation Blocks


(CALCU, CALCU-C)
The CALCU and CALCU-C blocks perform computation using arbitrarily defined calculation algorithms and
their setup parameters.

z Alarm Processing Specific to General-Purpose Calculation Blocks


(CALCU, CALCU-C)
The “calculation error alarm check,” which is one of the alarm checks performed by the CALCU and CALCU-C
blocks, is specific to these two function blocks.

z Calculation Output Value Range limit of General-Purpose


Calculation Blocks (CALCU, CALCU-C)
The calculation output value (CPV) can be limited in range between SL-(SH-SL) and SH (*1).
*1: SL= CPV scale low limit; SH= CPV scale high limit

z In/Out Data Normalization of General-Purpose Calculation Blocks


(CALCU, CALCU-C): FFCS Series/KFCS2/LFCS2
In CENTUM-XL system, the In/Out data of general-purpose calculation blocks are normalized values. In
CENTUM VP system, the In/Out data of general-purpose calculation blocks can be either normalized values
or engineering unit data values according to the designation on the builder. Designating to use the
normalized In/Out data of general-purpose calculation blocks can retain consistency when migrating a
CENTUM-XL calculations to CENTUM VP system.

„ Input Processing when a Calculation Input Value Error is


Detected
▼ Calculated Input Value Error Detected
Define the calculation value error detection condition of the CALCU and CALCU-C blocks and the data status
of the calculation output value (CPV) when an error is detected in “Calculated input value error detected” of
Function Block Detail Builder. By default, this setting is set as “0: Non-Detecting Type.”
In connection with these settings, a method by which the data status (IOP, IOP-, OOP, NRDY) related to the
process control input/output generated with the calculation input values (RV, RVn) is communicated to the
calculation output value (CPV) will furthermore be determined. The data status of the calculation output
values (CPV1 to CPV3) is always NR (normal) regardless of the setting in [Calculated input value error
detected] item.
Table 1.33-3 Specification of Calculation Input Value Error Detection of General-Purpose Calculation

file:///C:/Program%20Files%20(x86)/Yokogawa/IA/iPCS/Products/CENTUMVP/Pro... 25/12/2014
1.33 General-Purpose Calculation Blocks (CALCU, CALCU-C) Page 4 of 17

Blocks (CALCU, CALCU-C)

Error detection condition(*1)


CPV data Input value of data status
Specification RV1 to Calculation
RV status communication source
RV7 (*2) processing
BAD – – BAD RV
NR
Compensation- BAD Normal QST
(*3)
computing Type Do not communicate.
NR
NR (*3) Normal NR (*3)
(*3)
BAD – – BAD The priority order is from RV to RVn
– BAD – BAD (*4).
All-detection Type
NR
NR (*3) Normal NR (*3) Do not communicate.
(*3)
Non-detecting Type – – Normal NR (*3) Do not communicate.
*1: -: Ignore (don’t care)
*2: “RV1 to RV7” means the logic sum of the data statuses from RV1 to RV7.
*3: An “NR” entry in the table indicates a condition where the data status is neither BAD nor QST.
*4: The IOP and IOP- of a status to be communicated have higher priority. An IOP will be transmitted if an NRDY
has been generated for an input value with higher priority, and an IOP has been generated at the same time for
an input value with lower priority.

The following processing is performed if the data status of a calculation output value (CPV) becomes a bad
data value (BAD) or a questionable data value (QST) according to the specification of the calculation input
value error detection.
• If the data status of a calculation output value (CPV) becomes a bad data value (BAD)
The calculation processing is aborted, the value immediately before the error is retained and the
connected destination of OUT terminal will hold this retained previous value. The previous good CPV is
held and accessible from SUB terminal. If CPV overshoot is set to the block, the data from the OUT
terminal is not affected by the CPV change caused by main calculation input (RV) abnormality. However,
the CPV after overshoot can be accessed using SUB terminal.
• If the data status of a calculation output value (CPV) becomes a questionable data value (QST)
The calculation input values (RV, RVn) retain the values immediately before the error generation. The
calculation processing is continued using these values and the calculation output value (CPV) is updated.

z Input Processing for Data Status QST: FFCS Series/KFCS2/LFCS2


For a calculation block input, if its data status is QST, the QST status can be passed to the calculated output
value. For passing the QST status, check the option of [Pass calculation block's input QST status to CPV] on
[Constant 3] tab of FCS properties sheet.
When the option is checked or unchecked, the behaviors of CPV data status vary as follows:
Table 1.33-4 Relationship of CALCU and CALCU-C Block's Data Status of Input (RVn) and Data Status of
CPV

Error detection condition(*1)(*2) CPV data status


Calculated input value error
detection specification RV1 to Calculation QST is QST is not
RV
RV7 (*3) processing passed passed
BAD - - BAD BAD
- BAD Normal QST QST
QST QST Normal QST NR
Compensation-computing Type
QST NR Normal QST NR
NR QST Normal NR NR
NR NR Normal NR NR
BAD - - BAD BAD

file:///C:/Program%20Files%20(x86)/Yokogawa/IA/iPCS/Products/CENTUMVP/Pro... 25/12/2014
1.33 General-Purpose Calculation Blocks (CALCU, CALCU-C) Page 5 of 17

- BAD - BAD BAD


QST QST Normal QST NR
All-detection Type QST NR Normal QST NR
NR QST Normal QST NR
NR NR Normal NR NR
Non-detecting Type - - Normal NR NR
*1: -:Ignore (don’t care)
*2: Conditions are tested starting from the top, and if a condition is met, the subsequent conditions are ignored.
*3: If any one of RV1 to RV7 input statuses is BAD, it is denoted as BAD. If none of RV1 to RV7 input statuses is bad
while one of them is QST, it is denoted as QST.

TIP Notice that when this option is checked, the closing processing of trend data and the closing data of
report, the quality flag of OPC may be affected.

SEE For more information about the closing processing of trend data, refer to:
ALSO "„ Closing Data Processing Based on Data Status" in 1.7.2, "Structure of the Closing Processed Data "
in the Human Interface Stations Reference Vol.2 (IM 33K03F22-50E)
For more information about the closing data of report, refer to:
"„ Detailed Format Design – Closed-Topic Dialog Box Detail Definition Sheet" in 2.4.2, "Detailed
Format Design – Closing Data" in the Optional Functions Reference (IM 33K03N10-50E)
For more information about the quality flag of OPC, refer to:
"z Setting Quality Flag Tables" in "„ HIS Setup Window" in 1.2 "Engineering Related to OPC" in the
Optional Functions Reference (IM 33K03N10-50E)

„ Data for Totalization when Input Signal Conversion is Exact


Totalization Pulse Train
▼ Data Item for Totalization
When the input signal conversion is specified with [Exact Totalization Pulse Train Input], the totalization can
use the calculation outut value (CPV) instead of the integration of the calculation input value (RV).
[Exact Totalization Pulse Train Input] can be specified on the Function Block Detail builder for the item of
[Input Signal Conversion].
Data Item for Totalization: Choose [RV] or [CPV].
The default is [RV].
Moreover, if the [Input Signal Conversion] is specified with another type of conversion, the totalization can
only use the calcaulation output [CPV], cannot use the calculation input [RV].

„ Calculation Algorithm
The General-Purpose Calculation Blocks (CALCU, CALCU-C) execute algorithms that are defined using the
general-purpose calculation expression description language.
The calculation input values, calculated output values and set parameters of the General-Purpose Calculation
Block (CALCU) all use double-precision floating-point data type.
The calculation input values (RV4 to RV7) and calculated output values (CPV2, CPV3) of the General-Purpose
Calculation Block with String I/O (CALCU-C) all use string data type. When data of other function block is
referred or set using element symbols and a description of data items without specifying I/O terminal
connections in a calculation expression description, terminal connections of the specified I/O data are
performed automatically during compiling. The I/O terminals used here are different from those connected in
the Function Block Detail Builder.

file:///C:/Program%20Files%20(x86)/Yokogawa/IA/iPCS/Products/CENTUMVP/Pro... 25/12/2014
1.33 General-Purpose Calculation Blocks (CALCU, CALCU-C) Page 6 of 17

The input signals that are directly specified in the calculation expression description become the target of
calculation input error detection.

SEE For more information about the general-purpose calculation expression description language, refer to:
ALSO 1.47, "General-Purpose Arithmetic Expressions"

z Restriction on the General-Purpose Calculation Blocks (CALCU,


CALCU-C)
• Up to eight input terminal connections and four output terminal connections can be defined on the
Function Block Detail Builder.
• Up to 24 input data and 12 output data can be referred or set as the element symbols and data items in a
calculation expression.
• However, for using alphanumeric strings in CALCU-C, a maximum of 6 character strings and 6 numeric
strings can be used.
• Data of other FCS cannot be used in an arithmetic/logic calculation expression.

„ Set Parameters
The parameters of the General-Purpose Calculation Blocks (CALCU, CALCU-C) are shown as follows.
• Calculation parameters 1 to 4 (P01 to P 04)
Engineering unit data values.
• Calculation parameters 5 to 8 (P05 to P08)
Engineering unit data values in the case of General-Purpose Calculation Block (CALCU).
A string data of up to 16 standard-width characters or 8 double-width characters can be used for the
General-Purpose Calculation Block with String I/O (CALCU-C).

„ Computation Error Alarm Check


A computation error alarm (CERR) is generated if a calculation error occurs during the processing of a user-
defined calculation formula.
If a computation error alarm (CERR) is generated, the calculation processing stops and an error message
containing an error generation statement number and an error code is output. The error occurrence
statement number is set to the data item ERRL, and the previous value is held as the calculated output value
(CPV). The ERRL can be accessed from other function block, since it is handled as a parameter. Under this
circumstance, the system alarm may occur. However, if the setting item of [Suppress system alarm when
CALCU calculation error occurs] is specified on the builder, the system alarm message will not occur.
If a computation error occurs, the computation executes again from the beginning of the calculation in the
next scan. If the second computation is completed correctly, the computation error alarm (CERR) returns to
normal. The value at the error occurrence is held in ERRL.
On the builder, if the setting item of [Suppress system alarm when CALCU calculation error occurs] is
specified, when the calculation error occurs, the CPV data status will not change to BAD but the alarm status
will change to CERR.

SEE For more information about suppressing the system alarms on calculation error, refer to:
ALSO "„ Suppress System Alarm when CALCU Calculation Error Occurs : FFCS Series/KFCS2/LFCS2" in
1.33, "General-Purpose Calculation Blocks (CALCU, CALCU-C)"
For more information about the description of calculation errors and the calculation error handling, refer
to:
1.47.7, "Error Handling"

file:///C:/Program%20Files%20(x86)/Yokogawa/IA/iPCS/Products/CENTUMVP/Pro... 25/12/2014
1.33 General-Purpose Calculation Blocks (CALCU, CALCU-C) Page 7 of 17

„ Suppress System Alarm when CALCU Calculation Error


Occurs : FFCS Series/KFCS2/LFCS2
▼ Suppress system alarm when CALCU calculation error occurs
When running the CALCU or CALCU-C calculations, if a calculation error occurs, a system alarm message will
be initiated. However, this message can be suppressed by specifying the setting item of [Suppress system
alarm when CALCU calculation error occurs] on the “Constant 3” tab of FCS Properties. By default, this
option is not enabled.

SEE For more information about the calculation errors, refer to:
ALSO 1.47.7, "Error Handling"

„ CPV Range Limit: FFCS Series/KFCS2/LFCS2


▼ CPV range limit
The CPV Range Limit can be applied to limit the calculation output value (CPV) within a specified range. The
CPV can be limited in range between SL-(SH-SL) and SH.
When CPV is smaller than the low limit of SL-(SH-SL), the low limit will be used. When CPV is greater than
the high limit of SH, the high limit will be used.
The CPV range limit is different from the PV range limit, only limit the calculation output value (CPV). The
limited calculation output value will go through digital filter and used for totalization. The CPV Range Limit
functions only when the block mode is AUT.
The CPV Range Limit can be specified on Function Block Detail builder.
CPV Range Limit: Choose [Valid] or [Invalid].
The default is [Invalid].

SEE For more information about PV range limit, refer to:


ALSO “„ PV Range Limit: FFCS Series/KFCS2/LFCS2” in 3.1.1, “Input Signal Conversions Common to
Regulatory Control Blocks and Calculation Blocks” in the Function Blocks Overview (IM 33K03E21-50E)

„ Data Items – CALCU, CALCU-C


The table below shows the data items of the General-Purpose Calculation Block (CALCU):
Table 1.33-5 Data Items of General-Purpose Calculation Block (CALCU)

Entry Permitted or Not


Data Item Data Name Range Default
(*1)
O/S
MODE Block mode x -----
(AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
Alarm detection
AF ----- -----
specification
Alarm masking
AOFS ----- -----
specification
RV Calculated input value ----- 0
Value in the unit at the connection
RAW Raw input data -----
destination

file:///C:/Program%20Files%20(x86)/Yokogawa/IA/iPCS/Products/CENTUMVP/Pro... 25/12/2014
1.33 General-Purpose Calculation Blocks (CALCU, CALCU-C) Page 8 of 17

Calculated input value 1


RV1 to RV7 ----- 0
to 7
RAW1 to Value in the unit at the connection
Raw input data 1 to 7 -----
RAW7 destination
CPV Calculated output value Δ (*2) CPV engineering unit value SL
Value in the same engineering unit
SUM Totalizer value 0
as CPV
CPV1 to Calculated output value
----- 0
CPV3 1 to 3
Calculation parameters 1
P01 to P08 x ----- 0
to 8
EERL Error statement number ----- 0
ERRC (*3) Error code ----- 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
*1: x: Entry is permitted unconditionally
Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*2: Entry is permitted when the data status is CAL
*3: ERRC denotes a detailed error code and a class error code

The table below shows the data items of the General-Purpose Calculation Block with String I/O (CALCU-C):
Table 1.33-6 Data Items of General-Purpose Calculation Block with String I/O (CALCU-C)

Entry Permitted or Not


Data Item Data Name Range Default
(*1)
O/S
MODE Block mode x -----
(AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
Alarm detection
AF ----- -----
specification
Alarm masking
AOFS ----- -----
specification
RV Calculated input value ----- 0
Value in the unit at the connection
RAW Raw input data -----
destination
Calculated input value 1
RV1 to RV3 ----- 0
to 3
RAW1 to Value in the unit at the connection
Raw input data 1 to 3 -----
RAW3 destination
Calculated input value 4
RV4 to RV7 16Byte NULL
to 7
CPV Calculated output value Δ (*2) CPV engineering unit value SL
Value in the same engineering unit
SUM Totalizer value 0
as CPV
CPV1 Calculated output value 1 16Byte NULL
CPV2 to Calculated output value 2
----- 0
CPV3 and 3
Calculation parameters 1
P01 to P04 x ----- 0
to 4
Calculation parameters 5
P05 to P08 x 16Byte NULL
to 8

file:///C:/Program%20Files%20(x86)/Yokogawa/IA/iPCS/Products/CENTUMVP/Pro... 25/12/2014
1.33 General-Purpose Calculation Blocks (CALCU, CALCU-C) Page 9 of 17

EERL Error statement number ----- 0


ERRC (*3) Error code ----- 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
*1: x: Entry is permitted unconditionally
Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*2: Entry is permitted when the data status is CAL
*3: ERRC denotes a detailed error code and a class error code

SEE For more information about valid block modes for CALCU block and CALCU-C block, refer to:
ALSO 1.3.2, "Valid Block Modes for Each Calculation Block"

„ Calculation Block In/Out Data Normalization


▼ Normalization of Input/Output Signal
By designating on the builder, the calculation can be performed using the normalized values for the data
connected to the IN terminal, Q01 to Q07 terminals, OUT terminal, J01 to J03 terminals of a general-purpose
calculation block and the data set to or referenced by the general-purpose calculation block according to the
PV range (SH, SL), SV range (SSH, SSL), MV range (MSH, MSL) of the data.
The I/O terminals for numerical data and the numerical variables in the CALCU-C function block are also
affected by this feature. The numerical input and output terminals of CALCU-C function block are as follows:
• Input Terminals for Numerical Data: IN, Q01 to Q03
• Output Terminals for Numerical Data: OUT, J01
• Numerical variables that referenced or defined by the expressions in the CALCU-C function block

Even though the I/O normalization is specified on the builder, the CENTUM-XL
calculation expressions are not free from problems. After the CENTUM-XL migration,
the application debugging is necessary.

z In Data Normalization
The input engineering unit data (RV) of a calculation block can be normalized before used in the calculation.
When normalizing the RV, the range of the general-purpose calculation block will be ignored but the range of
the block connected to IN terminal or Q01 to Q07 terminal will be used. The normalization is performed with
the following formula:
RVN = (RV – SLi) / (SHi – SLi)
RVN: After normalization
RV: Before normalization (Engineering Unit Data)
SHi: Scale high-limit of the connected data
SLi: Scale low -limit of the connected data
For the data item, such as DV or DL, that is differentiated from other data items, the normalization is
performed with the following formula:
RVN = RV / (SHi – SLi)
RVN: After normalization
RV: Before normalization
SHi: Scale high-limit of the connected data
SLi: Scale low -limit of the connected data

file:///C:/Program%20Files%20(x86)/Yokogawa/IA/iPCS/Products/CENTUMVP/Pro... 25/12/2014
1.33 General-Purpose Calculation Blocks (CALCU, CALCU-C) Page 10 of 17

z Convert Output Data to Engineering Unit Data


When outputing the calculated data, the normalized data can be converted to engineering unit data. When
converting CPV to an engineering unit data, the range of the CPV will be used. When converting CPV1 to
CPV3 and other internal variables to engineering unit data, the ranges of the blocks connected to J01 to J03
terminal will be used.
The conversion is performed with the following formula:
CPV = CPVN x (SHo – SLo) + SLo
CPV: Before normalization (Engineering Unit Data)
CPVN: After normalization
SHo: Scale high-limit of the connected data (for CPV1 to CPV3 and other internal variables)
Scale high-limit of CPV (for CPV)
SLo: Scale low-limit of the connected data (for CPV1 to CPV3 and other internal variables)
Scale low-limit of CPV (for CPV)
For the data item, such as DV or DL, that is differentiated from other data items, the conversion is
performed with the following formula:
CPV = CPVN x (SHo – SLo)
CPV: Before normalization (Engineering Unit Data)
CPVN: After normalization
SHo: Scale high-limit of the connected data (for CPV1 to CPV3 and other internal variables)
Scale high-limit of CPV (for CPV)
SLo: Scale low-limit of the connected data (for CPV1 to CPV3 and other internal variables)
Scale low-limit of CPV (for CPV)
The formulas for normalizing the input data and for converting the output data to engineering unit data in
related to ranges are shown in the table below:
Table 1.33-7 In/Out Data Normalization

Formula Converting output to engineering


Range Normalizing input data
number unit data
1 SH:SL RVN = (RV - SL) / (SH - SL) CPV = CPVN × (SH - SL) + SL
2 SSH:SSL RVN = (RV - SSL) / (SSH - SSL) CPV = CPVN × (SSH - SSL) + SSL
RVN = (RV - MSL) / (MSH -
3 MSH:MSL CPV = CPVN × (MSH - MSL) + MSL
MSL)
4 SH:SL (Difference) RVN = RV / (SH - SL) CPV = CPVN × (SH - SL)
5 SSH:SSL (Difference) RVN = RV / (SSH - SSL) CPV = CPVN × (SSH - SSL)
6 MSH:MSL (Difference) RVN = RV / (MSH - MSL) CPV = CPVN × (MSH - MSL)
7 DSH:DSL RVN = (RV - DSL) / (DSH - DSL) CPV = CPVN × (DSH - DSL) + DSL
8 DSH:DSL (Difference) RVN = RV / (DSH - DSL) CPV = CPVN × (DSH - DSL)
RVN = (RV - MSL1) / (MSH1 -
9 MSH1:MSL1 CPV = CPVN × (MSH1 - MSL1) + MSL1
MSL1)
MSH1:MSL1
10 RVN = RV / (MSH1 - MSL1) CPV = CPVN × (MSH1 - MSL1)
(Difference)
RVN = (RV - MSL2) / (MSH2 -
11 MSH2:MSL2 CPV = CPVN × (MSH2 - MSL2) + MSL2
MSL2)
MSH2:MSL2
12 RVN = RV / (MSH2 - MSL2) CPV = CPVN × (MSH2 - MSL2)
(Difference)

z Input Limitation
If “Normalization of Input/Output Signal” is defined with Yes, the input data will be restricted as follows:
• If the connected data or referenced data is a non-difference type data.

file:///C:/Program%20Files%20(x86)/Yokogawa/IA/iPCS/Products/CENTUMVP/Pro... 25/12/2014

You might also like