CALCU Block

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)

I/O terminal

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

Data reference

Data setting

Condition testing

Status manipulation

Terminal connection

Process I/O

Software I/O

Function block

INCalculation

inputx x x x x

Q01 to Q07

nth calculation

inputx x x x x

OUTCalculation

outputx x x x x x

J01 to J03

nth calculation

outputx x x x x

SUBAuxiliary output

x x x x

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

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

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)

Functions of General-Purpose Calculation Blocks (CALCU, CALCU-C)

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

*1:

I/O terminal

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

Data reference

Data setting

Condition testing

Status manipulation

Terminal connection

Process I/O

Software I/O

Function block

INCalculation

inputx x x x x

Q01 to Q03

nth calculation

inputx x x x x

Q04 to Q07

nth calculation

inputx x

OUTCalculation

outputx x x x x x

J01nth

calculation output

x x x x x

J02 to J03

nth calculation

outputx x

SUBAuxiliary output

x x x x

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

*1:

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.

The medium-speed scan period can only be used for the FFCS series, KFCS2, KFCS, LFCS2, and LFCS.*1:

SEE ALSO

For more information about the types of input processing, output processing, and alarm processing 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)



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)

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

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



Blocks (CALCU, CALCU-C)

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/LFCS2For 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

Specification

Error detection condition(*1)CPV data

status Input value of data status

communication source RV RV1 to

RV7 (*2)Calculation processing

Compensation-computing Type

BAD BAD RV

NR (*3)

BAD Normal QST

Do not communicate. NR (*3)

NR (*3) Normal NR (*3)

All-detection Type

BAD BAD The priority order is from RV to RVn(*4). BAD BAD

NR (*3)

NR (*3) Normal NR (*3) Do not communicate.

Non-detecting Type Normal NR (*3) Do not communicate.

-: Ignore (dont care) RV1 to RV7 means the logic sum of the data statuses from RV1 to RV7.An NR entry in the table indicates a condition where the data status is neither BAD nor QST.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.

*1:*2:*3:*4:

Calculated input value error detection specification

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

RV RV1 to

RV7 (*3)Calculation processing

QST is passed

QST is not passed

Compensation-computing Type

BAD - - BAD BAD

- BAD Normal QST QST

QST QST Normal QST NR

QST NR Normal QST NR

NR QST Normal NR NR

NR NR Normal NR NR

BAD - - BAD BAD



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].

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 AlgorithmThe 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.

All-detection Type

- BAD - BAD BAD

QST QST Normal QST NR

QST NR Normal QST NR

NR QST Normal QST NR

NR NR Normal NR NR

Non-detecting Type - - Normal NR NR

-:Ignore (dont care) Conditions are tested starting from the top, and if a condition is met, the subsequent conditions are ignored.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.

*1:*2:*3:

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 ALSO

For more information about the closing processing of trend data, refer to:" 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 Item for Totalization: Choose [RV] or [CPV]. The default is [RV].



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

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 ParametersThe 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 CheckA 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 ALSO

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

SEE ALSO

For more information about suppressing the system alarms on calculation error, refer to:" 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"



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.

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.

Data Items CALCU, CALCU-CThe 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)

SEE ALSO

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

CPV Range Limit: Choose [Valid] or [Invalid]. The default is [Invalid].

SEE ALSO

For more information about PV range limit, refer to: 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 Item Data NameEntry Permitted or Not

(*1)Range Default

MODE Block mode x -----O/S(AUT)

ALRM Alarm status ----- NR

AFLS Alarm flashing status ----- -----

AFAlarm detection specification

----- -----

AOFSAlarm masking specification

----- -----

RV Calculated input value ----- 0

RAW Raw input dataValue in the unit at the connection destination

-----



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)

RV1 to RV7Calculated input value 1 to 7

----- 0

RAW1 to RAW7

Raw input data 1 to 7Value in the unit at the connection destination

-----

CPV Calculated output value (*2) CPV engineering unit value SL

SUM Totalizer valueValue in the same engineering unit as CPV

0

CPV1 to CPV3

Calculated output value 1 to 3

----- 0

P01 to P08Calculation parameters 1 to 8

x ----- 0

EERL Error statement number ----- 0

ERRC (*3) Error code ----- 0

OPMK Operation mark x 0 to 64 0

UAID User application ID x ----- 0

x: Entry is permitted unconditionallyBlank: Entry is not permitted: Entry is permitted conditionallyEntry is permitted when the data status is CALERRC denotes a detailed error code and a class error code

*1:

*2:*3:

Data Item Data NameEntry Permitted or Not

(*1)Range Default

MODE Block mode x -----O/S(AUT)

ALRM Alarm status ----- NR

AFLS Alarm flashing status ----- -----

AFAlarm detection specification

----- -----

AOFSAlarm masking specification

----- -----

RV Calculated input value ----- 0

RAW Raw input dataValue in the unit at the connection destination

-----


----- 0

RAW1 to RAW3

Raw input data 1 to 3Value in the unit at the connection destination

-----


16Byte NULL

CPV Calculated output value (*2) CPV engineering unit value SL

SUM Totalizer valueValue in the same engineering unit as CPV

0

CPV1 Calculated output value 1 16Byte NULL

CPV2 to CPV3

Calculated output value 2 and 3

----- 0


x ----- 0


x 16Byte NULL



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

z In Data NormalizationThe 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)

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)

EERL Error statement number ----- 0

ERRC (*3) Error code ----- 0

OPMK Operation mark x 0 to 64 0

UAID User application ID x ----- 0

x: Entry is permitted unconditionallyBlank: Entry is not permitted: Entry is permitted conditionallyEntry is permitted when the data status is CALERRC denotes a detailed error code and a class error code

*1:

*2:*3:

SEE ALSO

For more information about valid block modes for CALCU block and CALCU-C block, refer to:1.3.2, "Valid Block Modes for Each Calculation 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.

RVN: After normalizationRV: Before normalization (Engineering Unit Data)SHi: Scale high-limit of the connected dataSLi: Scale low -limit of the connected data

RVN: After normalizationRV: Before normalizationSHi: Scale high-limit of the connected dataSLi: Scale low -limit of the connected data



z Convert Output Data to Engineering Unit DataWhen 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

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)

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

z Input LimitationIf 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.

CPV: Before normalization (Engineering Unit Data)CPVN: After normalizationSHo: 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)

CPV: Before normalization (Engineering Unit Data)CPVN: After normalizationSHo: 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)

Formula number

Range Normalizing input dataConverting output to engineering

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

3 MSH:MSLRVN = (RV - MSL) / (MSH -MSL)

CPV = CPVN (MSH - 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)

9 MSH1:MSL1RVN = (RV - MSL1) / (MSH1 -MSL1)

CPV = CPVN (MSH1 - MSL1) + MSL1

10MSH1:MSL1 (Difference)

RVN = RV / (MSH1 - MSL1) CPV = CPVN (MSH1 - MSL1)

11 MSH2:MSL2RVN = (RV - MSL2) / (MSH2 -MSL2)

CPV = CPVN (MSH2 - MSL2) + MSL2

12MSH2:MSL2 (Difference)

RVN = RV / (MSH2 - MSL2) CPV = CPVN (MSH2 - MSL2)



The data value will be restricted within the range of SH and SL-(SH-SL).

(SH/SL: Range of the connected or referenced data)

If the connected data or referenced data is a difference type data.

The data value will be restricted within the range between positive and negative of (SH-SL).

(SH/SL: Range of the connected or referenced data)

However, the values beyond the limitation can be visualized on Tuning View.

z Output LimitationIf Normalization of Input/Output Signal is defined with Yes, the output will be restricted as follows:

CPV


(SH/SL: Range of the CPV)

If the connected data or referenced data is a non-difference type data.


(SH/SL: Range of the connected or manipulated data)

If the connected data or referenced data is a difference type data.

The data value will be restricted within the range between positive and negative of (SH-SL).

(SH/SL: Range of the connected or manipulated data)

However, the values after limitation can be visualized on Tuning View.

z Designating In/Out Data NormalizationData normalization can be designated for each calculation block on the Function Block Detail Builder of the general-purpose calculation block.

The settings regarding the calculation block in/out data normalization as well as the general-purpose calculation details and function block details can be printed out on the builder and printed out through self-documentation.

z Regarding DT or NX terminal of BDA-L, BDSET-1L/BDSET-2L BlockWhen a general-purpose calculation block is referencing or setting the data of a DT01 to DT16 or a NX01 to NX16 terminal of a BDA-L, BDSET-1L/BDSET-2L block, the data normalization and the range limitation will be performed according to the range of the data connected to the corresponding J01 to J16 terminal.

The data normalization and range limitation according to the range of the data connected to the J01 to J16 terminals are performed only when the connected data is normalizable.

When the data connected to the J01 to J16 terminal is changed, CALCU that referencing the previously connected data may become invalid element. In this case, you need to perform the operations for resolving the invalid elements.

z Normalizable Data (Data Connection)What data item can be normalized is automatically determined on the control drawing builder.

The normalizable data items (Data Connection) are listed below. In this table, the numbers that represent different formulas are the same as in the table of In/Out Data Normalization.

Regulatory Control Blocks

Table 1.33-8 Relevant Data Item: Regulatory Control Blocks (Data Connection)

Normalization of input/output signal: Select No or YesDefault: No

Model name

Relevant data item Range Fomula number



PVI HH / LL / PH / PL / PV / PVP SH:SL 1

VL SH:SL (Difference) 4

PVI-DV HH / LL / PH / PL / PV / PVP / SV / SVH / SVL SH:SL 1

DL / DV / VL SH:SL (Difference) 4

PID

CSV / HH / LL / PH / PL / PV / PVP / RSV / SV / SVH / SVL SH:SL 1

MH / ML / MV / OPHI / OPLO / PMV / RLV1-2 / RMV MSH:MSL 3

DB / DL / GW / VL / DV SH:SL (Difference) 4

PI-HLD


MH / ML / MSH / MSL / MV / OPHI / OPLO / PMV / RLV1-2 / RMV

MSH:MSL 3


PID-BSW



DL / LK / VL / DV SH:SL (Difference) 4

BIAS MSH:MSL (Difference) 6

ONOFF


MV / PMV / RMV MSH:MSL 3

DL / VL / DV SH:SL (Difference) 4

ONOFF-E




ONOFF-G



DB / DL / VL / DV SH:SL (Difference) 4

ONOFF-GE



DB / DL / VL / DV SH:SL (Difference) 4

PID-TP




PD-MR


CALC / MH / ML / MR / MV / OPHI / OPLO / PMV / RMV MSH:MSL 3


PI-BLEND

CSV / HH / LL / PH / PL / PV / RSV / SVH / SVL / SV SH:SL 1

MH / ML / MV / OPHI / OPLO / PMV / RMV MSH:MSL 3

RP MSH:MSL (Difference) 6

DL / VL / DV DSL:DSH (Difference) 8

PID-STC




MLD MH / ML / MV / OPHI / OPLO MSH:MSL 3

MLD-PVI

HH / LL / PH / PL / PV / PVP SH:SL 1

MH / ML / MV / OPHI / OPLO MSH:MSL 3


MLD-SW CSV / SV / SVH / SVL SSH:SSL 2

MH / ML / MV / OPHI / OPLO / PMV MSH:MSL 3



BIAS / RP SSH:SSL (Difference) 5

MC-2 ANSP / FV / PH / PL SH:SL 1

MC-2E ANSP / FV / PH / PL SH:SL 1

MC-3 ANSP / FV / PH / PL SH:SL 1

MC-3E ANSP / FV / PH / PL SH:SL 1

RATIO

HH / LL / PH / PL / PV / PVP SH:SL 1

CSV / RSV / SV / SVH / SVL SSH:SSL 2

CALC / MH / ML / MV / OPHI / OPLO / PMV / RMV MSH:MSL 3


RP SSH:SSL (Difference) 5

BIAS MSH:MSL (Difference) 6

PG-L13 (*1) CALC / MH / ML / MV / OPHI / OPLO / Y01-14 MSH:MSL 3

BSETU-2 LL / PH / PL / PV SH:SL 1

MH / ML / MV / OPHI / OPLO / PRE MSH:MSL 3

BSETU-3 LL / PH / PL / PV SH:SL 1

MH / ML / MV / OPHI / OPLO / PRE MSH:MSL 3

VELLIM


MH / ML / MV / OPHI / OPLO / PMV / RMV MSH:MSL 3

DL / DMVM / DMVP / DV SSH:SSL (Difference) 5

SS-H/M/L PV / RV1-3 SH:SL 1

AS-H/M/L PV / RV1-3 SH:SL 1


SS-DUAL HH / LL / PH / PL / PV / PVP / RV1-2 / SV SH:SL 1

DL / DV / VL SH:SL (Difference) 4

FOUT CSV / SV SSH:SSL 2

FFSUM

PV SH:SL 1

CSV / SV / SVH / SVL SSH:SSL 2



XCPL MH / ML / MV / OPHI / OPLO / PMV / PV MSH:MSL 3


SPLIT

CSV / RSV / SRH1-2 / SRL1-2 / SV / SVH / SVL SSH:SSL 2

MV1 MSH1:MSL1 9

RP1 MSH1:MSL1 (Difference)

10

MV2 MSH2:MSL2 11

RP2 MSH2:MSL2 (Difference)

12

PTC PH / PV SH:SL 1

DL SH:SL (Difference) 4

ALM-R Irrelevant to normalization

SLCD CSV / PH / PL / PV / RSV / SV / SVH / SVL SH:SL 1

DL / DV SH:SL (Difference) 4

SLPC CSV / PH / PL / PV / RSV / SV / SVH / SVL SH:SL 1

DL / DV SH:SL (Difference) 4

CSV / PH / PL / PV / RSV / SV / SVH / SVL SH:SL 1



Calculation Blocks

Table 1.33-9 Relevant Data Item: Calculation Blocks (Data Connection) (1/2)

SLMC DL / DV SH:SL (Difference) 4

SMST-111 CSV / PH / PL / PV / RSV / SV / SVH / SVL SH:SL 1

SMST-121 PH / PL / PV SH:SL 1

SMRT

PH / PL / PV SH:SL 1


DL SH:SL (Difference) 4

SBSD PH / PL / PV SH:SL 1

SLBC PH / PL / PV SH:SL 1

SLCC

PV SH:SL 1

RSV / SV SSH:SSL 2

DV SH:SL (Difference) 4

STLD PV SH:SL 1

SV, X02 to X14, PH, PL of PG-L13 are not normalizable.*1:

Model name Relevant data item Range Fomula number

ADD CPV SH:SL 1

MUL CPV SH:SL 1

DIV CPV SH:SL 1

AVE CPV SH:SL 1

SQRT CPV SH:SL 1

EXP CPV SH:SL 1

LAG CPV SH:SL 1

INTEG CPV SH:SL 1

LD CPV SH:SL 1

RAMP CPV SH:SL 1

LDLAG CPV SH:SL 1

DLAY CPV SH:SL 1

DLAY-C CPV SH:SL 1

AVE-M CPV / PREV SH:SL 1

AVE-C CPV / PREV SH:SL 1

FUNC-VAR CPV SH:SL 1

TPCFL CPV SH:SL 1

ASTM1 CPV SH:SL 1

ASTM2 CPV SH:SL 1

AND Irrelevant to normalization OR Irrelevant to normalization NOT Irrelevant to normalization SRS1-S Irrelevant to normalization SRS1-R Irrelevant to normalization SRS2-S Irrelevant to normalization SRS2-R Irrelevant to normalization WOUT Irrelevant to normalization OND Irrelevant to normalization OFFD Irrelevant to normalization



Table 1.33-10 Relevant Data Item: Calculation Blocks (Data Connection) (2/2)

Faceplate Blocks

Table 1.33-11 Relevant Data Item: Faceplate Blocks (Data Connection)

SFC Blocks

Table 1.33-12 Relevant Data Item: SFC Blocks (Data Connection)

TON Irrelevant to normalization TOFF Irrelevant to normalization GT Irrelevant to normalization GE Irrelevant to normalization EQ Irrelevant to normalization BAND Irrelevant to normalization BOR Irrelevant to normalization BNOT Irrelevant to normalization CALCU CPV SH:SL 1

CALCU-C CPV SH:SL 1


SW-33 Irrelevant to normalization SW-91 Irrelevant to normalization DSW-16 CPV / SD01-16 SH:SL 1

DSW-16C Irrelevant to normalization DSET SV / SVH / SVL SH:SL 1

DSET-PVI CPV / HH / LL/ PH / PL/ PVP / SV / SVH / SVL SH:SL 1


BDSET-1L DT01-DT16 Depending on the connected data 1 to 12

BDSET-1C Irrelevant to normalization BDSET-2L DT01-DT16 / NX01-NX16 Depending on the connected data 1 to 12

BDSET-2C Irrelevant to normalization BDA-L DT01-DT16 Depending on the connected data 1 to 12

BDA-C Irrelevant to normalization


INDST2 PV / SV / SVH / SVL SH:SL 1

INDST2S SV / SVH / SVL SH:SL 1

MH / ML / MV MSH:MSL 3

INDST3 PV / SV / SVH / SVL SH:SL 1


BSI Irrelevant to normalization PBS5C Irrelevant to normalization PBS10C Irrelevant to normalization

HAS3C PV / SV / SVH / SVL SH:SL 1



_SFCSW Irrelevant to normalization _SFCPB Irrelevant to normalization

PV / SV / SVH / SVL SH:SL 1



UNIT Instrument Blocks

Table 1.33-13 Relevant Data Item: UNIT Instrument Blocks (Data Connection)

Valve Pattern Monitors

The valve pattern monitor block does not have normalizable data item.

Off-site Blocks

Table 1.33-14 Relevant Data Item: Off-site Blocks (Data Connection)

FF Faceplate Blocks

Table 1.33-15 Relevant Data Item: FF Faceplate Blocks (Data Connection)

_SFCAS MH / ML / MV MSH:MSL 3


_UTSW Irrelevant to normalization _UTPB Irrelevant to normalization

_UTAS PV / SV / SVH / SVL SH:SL 1


_UTSW-SN Irrelevant to normalization _UTPB-SN Irrelevant to normalization

_UTAS-SN PV / SV / SVH / SVL SH:SL 1



FSBSET

PV / SV / SVH / SVL / SVPR SH:SL 1

MV / OPHI / OPLO MSH:MSL 3

DL1 / DL2 / DV SH:SL (Difference) 4

BLEND MPSV / PV / SV / SVH / SVL / SVPR SH:SL 1

Model name

Relevant data item Range Fomula number

FF-AI HH / LL / OUT_V / PH / PL / PV SH:SL 1

FF-DI Irrelevant to normalization

FF-CS BKCL_IN / MH / ML / MV / OPHI / OPLO / SEL1- SEL3 / BKCL_SL1 - BKCL_SL3

MSH:MSL 3

FF-PID

BKCL_OUT / CSV / HH / LL / PH / PL / PV / RCAS_OUT / RSV SH:SL 1

BKCL_IN / MH / ML / MV / OPHI / OPLO / RMV / ROUT_OUT MSH:MSL 3

DH SH:SL (Difference)

4

FF-RA

BKCL_OUT / CSV / HH / LL / PH / PL / PV / RCAS_OUT / RSV SH:SL 1

BKCL_IN / MH / ML / MV / OPHI / OPLO MSH:MSL 3

DH SH:SL (Difference)

4

FF-AO BKCL_OUT / CSV / FST_VAL / PV / RCAS_OUT / RSV SH:SL 1

MV / OPHI / OPLO / READBACK MSH:MSL 3

FF-DO Irrelevant to normalization FF-OS CSV / SV SSH:SSL 2

FF-SC OUT1_V / OUT2_V SH:SL 1

FF-IT CPV SH:SL 1

FF-IS CPV SH:SL 1

FF-MDI Irrelevant to normalization



z Normalizable Data (Terminal Connection)CPV is normalized or converted according to the range of itself.

z Data That Irrelevant to Data NormalizationThe following data are irrelevant to data normalization.

Data connected through switch blocks (SW-33, SW-91)

Data connected through inter-station data link block

Data connected through process I/O

Data connected through software I/O

Data connected to SUB terminal

Data connected through sequence connection

Data connected to MI, NB, CR and GM terminals of self-tuning PID controller block (PID-STC)

Data connected to MV1 to MV8 items of a cascade signal distributor block (FOUT)

Data connected to MV, MSH, MSL, MH, ML and RMV items of YS blocks

Data items that indicating the high and low limits (SH/SL/SSH/SSL/MSH/MSL/DSH/DSL/MSH1/MSL1/MSH2/MSL2)

If you want to normalize the above data, you can connect the data to a PVI block first and then connect to the calculation block.

z CENTUM-XL Compatible Action if CPV is not substituted in Calculation

If the normalization of input/output signal is enabled and the CPV is not substituted in the calculation, at the end of the calculation script, CPV=RV will be affixed.

In this case, the action will be as follows:

FF-MDO Irrelevant to normalization FF-MAI Irrelevant to normalization FF-MAO Irrelevant to normalization

SEE ALSO

For more information about terminal connection, refer to:2.2, Terminal Connection in the Function Blocks Overview (IM 33K03E21-50E)

CPV: CPV is substituted by RV and output through OUT terminal.digital filter: Activated (*1)totalization: Activated (*1)

In CENTUM-XL, the calculation blocks do not have digital filter and totalization features. *1:



CALCU Block

Documents

Transcript of CALCU Block