2008102523572200001

<Int> <Ind> <Rev> <Document Map> <Reference Map> Toc C-1
CS 1000/CS 3000
Reference
Function Block Details
IM 33S01B30-01E 8th Edition
CONTENTS
PART-C Function Block Common
C1. Structure of a Function Block .............................................................. C1-1
C2. I/O Connection ...................................................................................... C2-1
C2.1 Data Connection ........................................................................................... C2-3
C2.2 Terminal Connection................................................................................... C2-13
C2.2.1 Connection between Function Blocks ........................................... C2-14
C2.2.2 Connection by a Switch Block (SW-33, SW-91) ............................ C2-16
C2.3 Sequence Connection ................................................................................ C2-19
C2.4 Connection between Control Stations ....................................................... C2-22
C2.5 I/O Connection Information ........................................................................ C2-25
C3. Input Processing .................................................................................. C3-1
C3.1 Input Signal Conversion ............................................................................... C3-5
C3.1.1 Input Signal Conversions Common to Regulatory Control Blocks
and Calculation Blocks.................................................................... C3-7
C3.1.2 Input Signal Conversion for Logic Operation Blocks ...................... C3-18
C3.2 Digital Filter ................................................................................................. C3-19
C3.3 Integration ................................................................................................... C3-22
C3.4 PV/FV/CPV Overshoot ................................................................................ C3-25
C3.5 Calibration ................................................................................................... C3-27
C3.6 Input Processing in the Unsteady State .................................................... C3-29
C3.6.1 Input Processing of the Regulatory Control Block in
Unsteady State ............................................................................. C3-31
C3.6.2 Input Processing of the Calculation Block in Unsteady State ......... C3-33
C3.7 Input Processing for Sequence Connection ............................................. C3-37
C4. Output Processing................................................................................ C4-1
C4.1 Output Limiter ............................................................................................... C4-8
C4.2 Output Velocity Limiter ............................................................................... C4-11
C4.3 Output Clamp .............................................................................................. C4-12
C4.4 Preset Manipulated Output......................................................................... C4-19
C4.5 Output Tracking .......................................................................................... C4-21
C4.6 Output Range Tracking ............................................................................... C4-25
IM 33S01B30-01E 8th Edition : Dec.21,2001-00

C4.7 Manipulated Output Index .......................................................................... C4-28
C4.8 Output Signal Conversion .......................................................................... C4-29
C4.8.1 No-Conversion ............................................................................. C4-32
C4.8.2 Pulse Width Output Conversion .................................................... C4-36
C4.8.3 Communication Output Conversion .............................................. C4-42
C4.8.4 Output Signal Conversion of Logic Operation Blocks .................... C4-43
C4.9 Auxiliary Output .......................................................................................... C4-44
C4.10 Output Processing in Unsteady State ....................................................... C4-48
C4.11 CPV Pushback ............................................................................................ C4-49
C4.12 Output Processing in Sequence Connection ............................................ C4-52
C5. Alarm Processing – FCS ...................................................................... C5-1
C5.1 Input Open Alarm Check .............................................................................. C5-6
C5.2 Input Error Alarm Check ............................................................................... C5-8
C5.3 Input High-High and Low-Low Limit Alarm Check .................................... C5-10
C5.4 Input High and Low Limit Alarm Check ..................................................... C5-13
C5.5 Input Velocity Alarm Check ........................................................................ C5-16
C5.6 Deviation Alarm Check ............................................................................... C5-19
C5.7 Output Open Alarm Check ......................................................................... C5-24
C5.8 Output Fail Alarm Check ............................................................................ C5-26
C5.9 Output High and Low Limit Alarm Check .................................................. C5-27
C5.10 Bad Connection Status Alarm Check ........................................................ C5-29
C5.11 Process Alarm Message ............................................................................. C5-30
C5.12 System Alarm Message .............................................................................. C5-31
C5.13 Deactivate Alarm Detection ........................................................................ C5-32
C5.14 Alarm Inhibition (Alarm OFF) ..................................................................... C5-33
C5.15 Classification of Alarm Actions Based on Alarm Priority ......................... C5-35
C5.15.1 Alarm Display Flashing Actions ..................................................... C5-36
C5.15.2 Repeated Warning Alarm .............................................................. C5-38
C5.16 Alarm Processing Levels ........................................................................... C5-39
C6. Block Mode and Status......................................................................... C6-1
C6.1 Block Mode .................................................................................................... C6-2
C6.1.1 Basic Block Mode ........................................................................... C6-3
C6.1.2 Compound Block Mode .................................................................. C6-5
C6.1.3 Block Mode Transition .................................................................. C6-13
C6.1.4 Block Mode Change Command .................................................... C6-20
C6.1.5 Block Mode Transition Condition ................................................... C6-21
C6.2 Block Status ................................................................................................ C6-27
C6.3 Alarm Status ................................................................................................ C6-28
C6.4 Data Status .................................................................................................. C6-32

C7. Process Timing ..................................................................................... C7-1
C7.1 Process Timing for Regulatory Control Block ............................................ C7-3
C7.1.1 Scan Period .................................................................................... C7-4
C7.1.2 Order of Process Execution ............................................................ C7-7
C7.1.3 Timing of Process I/O ................................................................... C7-11
C7.1.4 Control Period for Controller Block ................................................ C7-26
C7.2 Process Timing of Calculation Block......................................................... C7-30
C7.3 Process Timing for Sequence Control Block ............................................ C7-35
C7.3.1 Execution Timing for Sequence Control Blocks ............................. C7-36
C7.3.2 Output Timing of Sequence Table Blocks (ST16, ST16E) .............. C7-40
C7.3.3 Output Timing of a LC64 Logic Chart Block ................................... C7-41
C7.3.4 Combination of Execution Timing and Output Timing .................... C7-42
C7.3.5 Control Period and Control Phase for Sequence Table Blocks
(ST16, ST16E).............................................................................. C7-43
C7.3.6 Control Period and Control Phase for Logic Chart Block (LC64) .... C7-45

Blank Page
<Toc> <Ind> <C1. Structure of a Function Block> C1-1
C1. Structure of a Function Block

A function block consists of the following components:
• Input and output terminals that exchange data with devices outside of the
external function block
• Four processing functions of input processing, calculation processing, output
processing, and alarm processing
• Constants and variable data used to execute processing functions. Especially,
an abbreviated name called “data item” is assigned to data that is referenced or
set during the operation.
The function block performs input processing, calculation processing, and output
processing in sequence for an input signal read from the input terminal, and writes
an output signal from the output terminal.
This chapter describes an overview of each structural component of the function
block as well as a basic structure of the function block.
■ Basic Structure of the Function Block

The figure below shows a basic structure of the function block.
Other
function
Set input terminal
block
SET
Function block
Alarm
processing
CSV,
SV,
Input terminal etc. Output terminal
Input Input PV, etc. Calculation Output MV, etc. Output

IN OUT
module processing processing processing module
Data items Legend

Flow of input/output signals and data
Alarm processing flow
C010001E.EPS
Figure Basic Structure of the Function Block
IM 33S01B30-01E 7th Edition : Apr.20,2001-00

● Input/Output Terminals
A function block performs data input/output with the process control input/output and other
function blocks via input/output terminals.
An input terminal (IN), set input terminal (SET) and output terminal (OUT) are basic input/
output terminals. The function block has some other input/output terminals according to the
type of the function block used.
SEE ALSO
• For the connection destinations of the input/output terminals, see C2, “I/O Connection.”
• For specific input/output terminals of each function block, see the applicable section of Part-D, “Function
Block Details.”
● Input Processing
Input processing changes an input signal read from the connection destination of the input
terminal of the function block into data that is suitable for calculation processing (control
calculation, numeric calculation, etc). Various types of input processing are performed
according to the type of the function block and the input signal format.
SEE ALSO
• For the basic input processing in the regulatory control block and calculation block, see C3, “Input Pro-
cessing.”
• For input processing specific to each function block, see the applicable section of Part-D, “Function Block
Details.”
● Calculation Processing
Calculation processing reads data obtained by input processing, performs calculation
processing according to the type of the function block, and outputs the processing result.
For example, a regulatory control block reads a process variable (PV), performs computa-
tion for regulatory control, and outputs the computation result as a manipulated value (MV).
Because the calculation processing determines the function of each function block, the
processing contents vary depending on the type of the function block.
SEE ALSO
For the calculation processing of each function block, see the applicable section of Part-D, “Function
Block Details.”

● Output Processing
Output processing outputs data obtained by calculation processing to the connection
destination of the output terminal as an output signal.
Various types of output processing are performed according to the type of the function
block and the output signal format.
SEE ALSO
• For the basic output processing in the regulatory control block and calculation block, see C4, “Output
Processing.”
• For output processing specific to each function block, see the applicable section of Part-D, “Function Block
Details.”
● Alarm Processing
Alarm processing performs various types of alarm check during input processing, calcula-
tion processing and output processing in order to detect a process error. When an error is
detected, the alarm processing reflects the detection of an alarm in the “alarm status” that
is one of the data items of the function block, and also notifies a message indicating the
detection result to the operation and monitoring.
SEE ALSO
• For the basic alarm processing in the function block, see C5, “Alarm Processing - FCS.”
• For the alarm processing specific to each function block, see the applicable section of Part-D, “Function
Block Details.”

● Data Items
A function block retains various data according to the type of the function block in a data-
base, which includes setup parameters and variable data that may be referenced or set
during the operation. Abbreviated names that are assigned to these set parameters and
variable data are generically called “data items.”
For instance, the function block can perform calculation processing based on a specific
data item value and can reflect that processing result in another data item.
The controls of the function block, such as “MAN” (manual) and “AUT” (auto), and the
“block mode” that indicates the output status are some of the data items.
Main data items are as follows:
• Block mode (MODE)
• Block status (BSTS)
• Alarm status (ALRM)
• Process variable (PV)
• Setpoint value (SV)
• Manipulated output value (MV)
SEE ALSO
• For details on the block mode, block status and alarm status, see C6, “Block Mode and Status.”
• For data items that are retained by each function block, see the applicable section of Part-D, “Function
Block Details.”

<Toc> <Ind> <C2. I/O Connection> C2-1
C2. I/O Connection

By performing the I/O connection, data can be exchanged between a function block
and the connection destination according to the connection method.
■ Connection Destination of I/O Connection

With I/O connection, the destination and method of connection for each I/O terminal of a
function block is specified. When the I/O connection is performed, process I/O, software
I/O, communication I/O, fieldbus I/O and other function blocks can be specified as the
connection destination of the function block’s I/O terminal.
● Process I/O
• Analog I/O
• Contact I/O
● Software I/O
• Internal switch (common switch)
• Message output
● Communication I/O
• Word data
• Bit data
● Fieldbus I/O
• Parameter of fieldbus block
● Other Function Blocks

• Data items of other function blocks
• I/O terminals of other function blocks

<Toc> <Ind> <C2. I/O Connection> C2-2
■ I/O Connection Methods
The I/O connection methods include data connection, terminal connection and sequence
connection.
● Data Connection
This is the I/O connection method used for reading and setting data with respect to the
process I/O, software I/O, communication I/O, fieldbus I/O or other function blocks.
● Terminal Connection
This is the I/O connection method used when connecting between cascade control function
blocks or connecting function blocks via a selector switch block (SW-33, SW-91). Data is
exchanged between the terminals of two function blocks.
● Sequence Connection
This is the I/O connection method used for testing whether or not the connection destina-
tion data used by the sequence control satisfies the conditional expression, or for changing
block mode, alarm status, data, etc. of the connection destination.

<Toc> <Ind> <C2.1 Data Connection> C2-3
C2.1 Data Connection

Data connection is used when exchanging data values and data status between a
function block and the data item of the element specified as the connection destina-
tion.
■ Data Connection
Data connection is a method in which the element symbol name and data item name of
various elements containing data are specified as the I/O connection information to indicate
the connection destination of the function block’s I/O terminal. Process I/O, software I/O,
communication I/O, fieldbus I/O or other function blocks can be specified as an element
which contains data.
In data connection, data values and data status are directly exchanged with the data item
of the element specified as the connection destination.
■ Data Reference and Data Setting

In data connection, reading data from the connection destination is called “data reference,”
and writing data into the connection destination from the output terminal of the function
block is called “data setting.”
● Data Reference
Data reference is a type of data connection in which data is read from the connection
destination of the function block’s input terminal. The data value of the connection destina-
tion is read as an input value of the function block in data reference. Also, the data status of
the input data is modified depending upon the data status of the data from the connection
destination.
With data reference, data at the same connection destination can be referenced from I/O
terminals of multiple function blocks. In this case, the same input data is read to each
function block.
● Data Setting
Data setting is a type of data connection in which data is written into the connection desti-
nation from the function block’s output terminal. The value of the function block’s output
data is sent to the connection destination. Also, the data status of the connection
destination’s data is modified depending upon the data status of the output data from the
function block.
IMPORTANT
When setting data for the process output, make sure that one output terminal corresponds
to one process output.
If data is set for the same process output from output terminals of multiple function blocks,
conflict will result at the process output due to different data values set.

■ Destinations of Data Connection
In data connection, process I/O, software I/O, communication I/O, fieldbus I/O or data items
of other function blocks can be specified as the connection destination of the function
block’s I/O terminal.
Data reference and data setting can be performed with each of the connection destina-
tions.
● Data Connection with Process I/O

Data connection with process I/O is an I/O connection that connects the function block’s I/O
terminal to the process I/Os such as analog I/O and contact I/O .
Since process I/Os do not have I/O terminals, terminal connection cannot be performed.
An example of data connection with process I/O is shown below:
Data reference Data setting
PID
Process input Process output
IN OUT
Input module Output module
C020101E.EPS
Figure Data Connection with Process I/O
● Data Connection with Software I/O

Data connection with software I/O is an I/O connection that connects an internal switch and
the message outputs such as annunciator messages, messages for sequence control, etc.
to the function block’s I/O terminal.
An example of data connection with software I/O is shown below:
Data setting
PG-L13
%AN
SUB
Annunciator message
C020102E.EPS
Figure Data Connection with Software I/O

● Data Connection with Communication I/O
Data connection with communication I/O means that communication I/O word/bit data is
connected to the I/O terminal of a function block. Its example is shown below.
CALCU
IN OUT
%WW, %WB
Communication I/O data
C020103E.EPS
Figure Data Connection with Communication I/O
SEE ALSO
For the details of communication I/O, see Part J, “Subsystem Communication (Using RIO)” or Part K,
“Subsystem Communication (Using FIO).”
● Data Connection with Fieldbus I/O

Data connection with fieldbus I/O means that fieldbus block parameters are connected to
the I/O terminal of a function block. Its example is shown below.
CALCU
IN OUT
Fieldbus Communication Module
C020104E.EPS
Figure Data Connection with Fieldbus I/O
SEE ALSO
For more information about data connection with Fieldbus I/O, see A2.2, “Control Loop and Data Flow” in
Foundation Fieldbus Reference (IM 33Y05P10-01E) in regarding to KFCS2 or KFCS, or see A3.3,
“Fieldbus Block Connection” in Foundation Fieldbus Tools (IM 33S05P10-01E) in regarding to PFCS,
LFCS2, LFCS or SFCS.

● Data Connection with Other Function Blocks
Data connection with other function blocks is an I/O connection that connects data items
such as process variables (PV) and manipulated output values (MV) held in the other
function blocks, to the function block’s I/O terminals.
An example of data connection with other function blocks’ data items is shown below:
PVI LDLAG PID
PV IN OUT VN
C020105E.EPS
Figure Data Connection with Other Function Blocks’ Data Items
In data connection with other function blocks, data is directly exchanged with the data items
of the connection destination. Therefore, there is no need to specify I/O connection infor-
mation in the function blocks of the connection destination as long as the I/O connection
information is specified in the function block of the connection source.
When using calculated input values (RV, RVn) as constants in a calculation block, data can
be set for the calculated input values (RV, RVn) of that calculation block. In such a case,
however, if data reference or terminal connection (cascade input) is specified for the input
terminal corresponding to these calculated input values (RV, RVn), the input action that
uses the input terminal has precedence over the other.
An example of data setting for the calculated input value (RV) is shown below:
Data setting
CALCU
OUT
Data setting for RV is invalid when
the IN terminal is connected.
CALCU
IN RV
Data reference connection or cascade

input terminal connection
C020106E.EPS
Figure Data Setting for Calculated Input Value (RV)

■ I/O Connection Information for Data Connection ¡ £
▼ Input Connection Information, Output Connection Information, Set Value Input Connection
Information
Specify the I/O connection information to the I/O terminal of the function block as follows in
order to perform data connection.
Element symbol name.data item name

• Element symbol name:
A tag name, label name, element number or terminal number that identifies the con-
nection destination.
• Data item name: PV, RV, MV, etc.
In data connection with a process I/O, a tag name, label name or terminal number is speci-
fied for the element symbol name, and PV is specified for the data item name.
The terminal number is represented by the following symbols:
%Z01usmm
Terminal (01 to 32)
Slot (1 to 4)
Unit (1 to 5)
C020107E.EPS
Figure I/O Information Symbols ¡
%Znnusmm
Terminal (01 to 32)
Slot (1 to 4)
Unit (1 to 5)
INput module (fixed at 01) (*1)
Node number (01to 08) (*2)
C020108E.EPS
*1: £ Can only be used with SFCS.

*2: £ Can only be used with LFCS2 or LFCS.
Figure I/O Information Symbols £ : LFCS2/LFCS2/SFCS
%Znnusmm
Terminal (01 to 64) (*1)
Segment (1 to 4) (*2)
Slot (1 to 8)
Node number (01 to 10)
C020111E.EPS
*1: For fieldbus communication, terminal “mm” ranges between 01 to 48.

*2: For fieldbus communication, segment “s” ranges between 1 to 4. For process output “s” is fixed as 1. For Analog I/O
(HART Compatible) modules, when “s” is set to 2, the element is used as a HART variable channel; when “s” is set to
1, the element is used as an analog input channel.
Figure I/O Information Symbols £ : KFCS2/KFCS
In data connection with software I/O, a tag name or element symbol number is specified for
the element symbol name, and PV is specified for the data item name.
In data connection with other function blocks, a tag name is specified for the element
symbol name and a data item name that is the target of connection is specified for the data
item name.

SEE ALSO
Refer to C2.5, “I/O Connection Information” for the element numbers. Refer to the description of corre-
sponding function block in D1, “Regulatory Control,” D2, “Arithmetic Calculation, Logic Operation,” D3,
“Sequence Control” or D4, “Faceplate Blocks” for the data item names of each function block.
TIP
The I/O terminal which performs input and output of character string data cannot be connected to a
process I/O. The I/O terminals that perform input and output of the character string data are shown in the
following:
Table I/O Terminals for Character Strings

Function block Terminal
CALCU-C Q04 to 07, J02, J03
DSW-16C OUT
BDSET-1C/2C J01 to J16
BDA-C J01 to J16
C020109E.EPS
■ Data Reference with Respect to Dual-Redundant Input ¡ £

As indicated below, there are three methods of data reference with respect to dual-redun-
dant input modules, depending on the type of input module.
● Dual-Redundant Analog Input : PFCS/LFCS2/LFCS/SFCS

When reading data from dual-redundant analog input modules, a Dual-Redundant Signal
Selector Block (SS-DUAL) is used. Specify an input module for each of the connection
destinations of the two input terminals (IN1, IN2) of the SS-DUAL block, respectively.
An example of a dual-redundant input connection is illustrated below.
Data reference
Data reference
Input
SS-DUAL
module IN1 PID
PV IN
IN2
Input
module
Data reference
C020110E.EPS
Figure Dual-Redundant Input Connection : PFCS/LFCS2/LFCS/SFCS

● Dual-Redundant Multi-Point Analog Input : PFCS/LFCS2/LFCS/SFCS
To access the multi-point analog input modules in dual-redundant configuration, the follow-
ing settings are required.
• On the IOM module property sheet, check the mark “Duplicate Next Card.” The setting
is the same for either input modules or output modules.
• For the function block input terminal, specify the terminal number of the module with
slot number 1 of the two duplicate modules. The data reference method is the same
as that for a non-dual-redundant module.
Normally, the module with slot number 1 is the control side and the module with slot num-
ber 2 is the standby side. If the module on control side fails, the module that was on the
standby side will take over the control. Function blocks will read data from the new control
side module.
SEE ALSO
For more information about multi-point analog I/O module dual-redundant configuration, see a section
“■ Dual-Multipoint Analog Control I/O.” in chapter A3.3.2, “Parameters for Multipoint Analog Control
Input/Output.”
● Dual-Redundant Multi-Point Analog Input : KFCS2/KFCS £

To access the multi-point analog input modules in dual-redundant configuration, the follow-
ing settings are required.
• On the IOM module property sheet, check the mark “Duplicate Next Card.”
the smaller slot number of the two duplicate modules. The data reference method is
the same as that for a non-dual-redundant module.
Normally, the module with the smaller slot number is the control side and the module with
the larger slot number is the standby side. If the module on control side fails, the module
that was on the standby side will take over the control. Function blocks will read data from
the new control side module.
SEE ALSO
“■ Dual-FIO Analog Input/Output : KFCS2/KFCS £” in chapter A3.4.1, “Parameters for FIO Analog
Inputs/Outputs.”

● Dual-Redundant Contact Input ¡ £
When reading data from dual-redundant status input modules, it is necessary to perform
the following operations.
the smaller slot number of the two duplicate modules. The method of setting data
reference is the same as that for a non-dual-redundant module.
Normally, the module with the smaller slot number is to be the control side and the module
with the larger slot number is to be the standby side. If the module on control side faults, the
module that was on the standby side will take over the control. Function blocks read data
from the control side.
SEE ALSO
• For more information about contact I/O module dual-redundant configuration in regarding to PFCS, LFCS
2, LFCS and SFCS, see a section “■ Dual-Relay, Contact Terminal, Contact Connector” in chapter A3.3.4,
“Parameters for Relay, Contact Terminal or Contact Connector.”
• For more information about contact I/O module dual-redundant configuration in regarding to KFCS2,
KFCS, see a section “■ Dual-FIO Contact Input/Output : KFCS2/KFCS £” in chapter A3.4.2, “Param-
eters for FIO Contact Inputs/Outputs.”
■ Data Setting with Respect to Dual-Redundant Output ¡ £

As indicated below, there are three methods of data setting with respect to dual-redundant
output modules, depending on the type of output module.
● Dual-Redundant Analog Output : PFCS/LFCS2/LFCS/SFCS

To write the same output value to dual-redundant analog output modules, the following
operation is required:
• Specify “Dual” for each terminal on the IOM definition builder. For redundancy, specify
two successive output points (1-2, 3-4, ..., 15-16) to the output modules.
• For output terminal of the function block, specify the output point with the younger
number of the two output points. The method of setting data is the same as that for a
non-dual-redundant module.

● Dual-Redundant Multi-Point Analog Output : PFCS/LFCS2/LFCS/SFCS
To write data to the multi-point analog output modules in dual-redundant configuration, the
following settings are required.
• On the IOM module property sheet, check the mark “Duplicate Next Card.” The setting
is the same for either input modules or output modules.
slot number 1 of the two duplicate modules. The data reference method is the same
as that for a non-dual-redundant module.
Normally, the module with slot number 1 is the control side and the module with slot num-
ber 2 is the standby side. If the module on control side fails, the module that was on the
standby side will take over the control. Function blocks will read data from the new control
side module.
SEE ALSO
“■ Dual-Multipoint Analog Control I/O : PFCS/LFCS/SFCS in chapter A3.3.2, “Parameters for Multiple
Analog Control Input/Output.”
● Dual-Redundant Multi-Point Analog Output : KFCS2/KFCS £

To write data to the multi-point analog output modules in dual-redundant configuration, the
following settings are required.
the smaller slot number of the two duplicate modules. The data reference method is
the same as that for a non-dual-redundant module.
Normally, the module with the smaller slot number is the control side and the module with
the larger slot number is the standby side. If the module on control side fails, the module
that was on the standby side will take over the control. Function blocks will read data from
the new control side module.
SEE ALSO
“■ Dual-FIO Analog Input/Output : KFCS2/KFCS £ in chapter A3.4.1, “Parameters for FIO Analog
Inputs/Outputs.”

● Dual-Redundant Contact Output ¡ £
When writing data to dual-redundant contact output modules, it is necessary to perform the
following operations in order to write the same output value to the two output modules.
• For output terminal of the function block, specify the terminal number of the module
with the smaller slot number of the two duplicate modules. The method of setting data
is the same as that for a non-dual-redundant module.
Normally, the module with the smaller slot number is to be the control side and the module
with the larger slot number to be on the standby side. If the module on control side faults,
the module that was on the standby side will take over the control. Function blocks write
data to the modules on both sides.
SEE ALSO
• For more information about contact I/O module dual-redundant configuration in regarding to PFCS,
LFCS2, LFCS and SFCS, see a section “■ Dual-Relay, Contact Terminal, Contact Connector” in chap-
ter A3.3.4, “Parameters for Relay, Contact Terminal or Contact Connector.”
• For more information about contact I/O module dual-redundant configuration in regarding to KFCS2,
KFCS, see a section “■ Dual-FIO Contact Input/Output : KFCS2/KFCS £” in chapter A3.4.2, “Param-
eters for FIO Contact Inputs/Outputs.”

<Toc> <Ind> <C2.2 Terminal Connection> C2-13
C2.2 Terminal Connection

Terminal connection is used when performing cascade control by connecting I/O
terminal of a function block to that of another function block.
■ Terminal Connection
The terminal connection specifies the I/O terminal of a function block as the connection
destination of the other function block’s I/O terminal. Data is exchanged between the I/O
terminals of two function blocks in terminal connection. The connections between I/O
terminals of function blocks are well applied to the cascade loops where the upper stream
block’s output depends on the lower stream block’s status.
The terminal connection is mainly used in the following instances:
● Connection Between Function Blocks

The output terminal (OUT) of the upstream function block and the setting input terminal
(SET) or input terminal (IN, INn) of the downstream function block are connected under the
cascade control.
● Connection by Way of a Switch Block (SW-33, SW-91)

Terminal connection must always be used as the I/O connection method at one or the other
of the I/O terminals (input side or output side) of the SW-33 or SW-91 block. The other
terminal uses the I/O connection method such as data reference, data setting or terminal
connection that applies the case that SW-33 or SW-91 does not intervene.
■ I/O Connection Information for Terminal Connection

When the terminal connection with the I/O terminal of another function block is established,
specify the I/O connection information to the I/O terminal of the function block as follows:
Element symbol name.I/O terminal name

A tag name identifies the connection destination.
• I/O terminal name:
IN, OUT, SET, etc.
In terminal connection, I/O terminal of each other must be specified in the both of function
blocks: connection source and connection destination. This is because data is exchanged
with the I/O terminal of the function block of the connection destination.

C2.2.1 Connection between Function Blocks

This section explains the connection between the output terminal (OUT) of the
upstream function block and the setting input terminal (SET) or input terminal (IN,
INn) of the downstream function block under the cascade control.
■ Terminal Connection between the Output Terminal (OUT) and

Setting Input Terminal (SET)
The following example shows connection between output terminal (OUT) of the upstream
function block and the setting input terminal (SET) of the downstream function block under
the cascade control. In this example, two I/O terminals are connected by the terminal
connection.
Terminal connection
PID
OUT
SET
PID
CSV
C020201E.EPS
Figure Terminal Connection between the Output Terminal and SET Terminal
In this example, data is sent from the output terminal (OUT) of the upstream function block
by way of the setting input terminal (SET) of the downstream function block, then set as a
cascade setting value (CSV) of the downstream function block at the end.
■ Terminal Connection between the Output and Input Terminals

The following example shows a connection between output terminal (OUT) of the upstream
function block and the input terminal (IN, INn) of the downstream function block. In this
example, two I/O terminals are connected by the terminal connection.
Terminal connection
PID AS-H
OUT IN1 RV1
C020202E.EPS
Figure Terminal Connection between the Output and Input Terminals
In this example, data is sent from the output terminal (OUT) of the upstream function block
by way of the input terminal (IN1) of the downstream function block, then set as a calcu-
lated input value (RV1) of the downstream function block at the end.

■ Function Blocks and Their Target Terminals that Allow Terminal
Connection
The following table lists the function blocks that can be connected to the OUT terminal
using a terminal connection and the I/O terminals for which terminal connections can be
used.
Table List of Function Blocks which can be Connected by the Terminal Connection and Their
Target Terminals
Target terminal Corresponding
Block type Block model name
name input data
PID
PI-HLD
PID-BSW
ONOFF
ONOFF-G
PID-TP
PD-MR SET CSV
PI-BLEND
PID-STC
MILD-SW
VELLIM
FOUT
Regulatory SPLIT
control
RATIO IN PV
FFSUM SET CSV
IN1 RV1
SS-H/M/L
IN2 RV2
AS-H/M/L
IN3 RV3
IN1 RV1
SS-DUAL
IN2 RV2
XCPL IN PV
SQRT
EXP
LAG
INTEG
Calculation LD IN RV
LDLAG
DLAY
DLAY-C
FUNC-VAR
C020203E.EPS

C2.2.2 Connection by a Switch Block (SW-33, SW-91)

This section explains the connections between I/O terminals of the function blocks
by a switch block (SW-33, SW-91) as well as the connection to the process I/O or
software I/O by the switch block.
A terminal connection to a switch block (SW-33, SW-91) of another control station or
a sequence connection via the SW-33 or SW-91 block cannot be done.
■ Connection Between Function Blocks by a Switch Block

(SW-33, SW-91)
A switch block (SW-33, SW-91) can be placed in the middle of the cascade control loop. In
this case, the switch block and its upstream/downstream function blocks are connected by
the terminal connection, respectively.
● Connection to a Setting Input Terminal (SET) by a Switch Block (SW-33,

SW-91)
The following example shows a connection between an output terminal (OUT) of the
upstream function block and a setting input terminal (SET) of the downstream function
block by a switch block (SW-33).
Terminal connection Terminal connection
SW33
PID
S11
OUT S12 S10
S13
SET
PID
CSV
C020204E.EPS
Figure Connection to a Setting Input Terminal (SET) by Way of a Switch Block (SW-33)
● Connection to an Input Terminal by a Switch Block (SW-33, SW-91)

The following example shows a connection between an output terminal (OUT) of the
upstream function block and an input terminal (IN) of the downstream function block by a
switch block (SW-33).
SW33
PID AS-H
S11
OUT S12 S10 IN1 RV1
S13
C020205E.EPS
Figure Connection to an Input Terminal by Way of a Switch Block (SW-33)

■ Connection to a Process I/O or Software I/O by a Switch Block (SW-33,
SW-91)
An I/O terminal of the function block and a process I/O or software I/O are connected by a
switch block (SW-33, SW-91).
In the SW-33, SW-91 block, however, there is no data item to be used for data connection
from another function block. Therefore, the I/O terminal on the function block side is con-
nected by the terminal connection and that on the process I/O or software I/O side is
connected by data connection.
● Data Reference by a Switch Block (SW-33, SW-91)

In order to input data from a process I/O by a switch block (SW-33, SW-91), one I/O termi-
nal of the SW-33 or SW-91 block is connected by the terminal connection while the other is
connected by data reference.
The following example shows data reference by a SW-33 block.
Data reference Terminal connection
SW33
PVI
S11
I/O module S12 S10 IN
S13
C020206E.EPS
Figure Data Reference by a Switch Block (SW-33)
● Data Setting by a Switch Block (SW-33, SW-91)

In order to output data to a process I/O by a switch block (SW-33, SW-91), one I/O terminal
of the SW-33 or SW-91 block is connected by the terminal connection while the other is
connected by data setting.
The following example shows data setting by a SW-33 block.
Terminal connection Data setting
SW-33
PID
S11
OUT S12 S10 I/O module
S13
C020207E.EPS
Figure Data Setting by a Switch Block (SW-33)

■ Mixture of Terminal Connection and Data Connection
In the SW-33 or SW-91 block, it is possible to mix two methods; reading data by the termi-
nal connection and by data connection. These two methods can be switched depending on
the situation.
The following example shows a mixture of terminal connection and data connection by a
SW-33 block.
SW-33
PID AS-H
S11
OUT S12 S10 IN RV1
S13
Input module
Data reference
C020208E.EPS
Figure Mixture of Terminal Connection and Data Connection by a Switch Block

(SW-33)

<Toc> <Ind> <C2.3 Sequence Connection> C2-19
C2.3 Sequence Connection

Sequence connection is used when testing the conditions of input signals in the
function block or manipulating the status of the elements at the output destination.
■ Sequence Connection ¡ £
In this method, various elements that contain data are specified as the connection destina-
tion of the function block’s I/O terminal. It is necessary to specify the conditional expression
to the input terminal in order to judge the data status, as well as data for manipulating the
element status to the output terminal. The sequence connection is the I/O connection
method used by sequence controls. In addition to the sequence control block, sequence
connection can also be used in the Pulse Count Input Block (PTC) of regulatory control
blocks, the Logic Operation Blocks (*1) or the General-Purpose Calculation Blocks
(CALCU, CALCU-C) for arithmetic and logic operation functions.
*1: ¡ £ Logic Operation Block can only be used for CS 3000.
■ Condition Testing and Status Manipulation

In sequence connection, a process performed to read data from the connection destination
is called “condition testing,” and a process performed to write data to the connection desti-
nation is called “status manipulation.”
In sequence connection, data contained in the element is exchanged to test the condition,
and data for status manipulation of the element is exchanged to manipulate the status,
respectively, with the element (process I/O, software I/O, or other function blocks) specified
as a connection destination.
● Condition Testing
Condition testing is a sequence connection for reading data from the connection destina-
tion of the function block’s I/O terminal. In condition testing, the data at the connection
destination is tested by the condition expression specified to the input terminal, and a
logical value (true or false) which indicates established/unestablished of the condition
expression is obtained. That is, the condition testing replaces the data read by the function
block with a logical value that indicates the status of the connection destination.
● Status Manipulation
Status manipulation is a sequence connection to output to the connection destination from
the function block’s I/O terminal. In status manipulation, status manipulation of the connec-
tion destination specified to the output terminal is performed according to the result of
logical operation (true or false) of the function block, then the connection destination status
is modified.

■ I/O Connection Information for Sequence Connection
In sequence connection, the I/O connection information is specified to the I/O terminal of
the function block as follows. In the Sequence Table Block (ST16, ST16E), specify this
information in the condition signal setting area and operation signal setting area.
Element symbol name.data item name.condition specification

Element symbol name.data item name.manipulation specification

Tag name, label name, element number, or terminal number that identifies the con-
nection destination
• Data item name:
Differs according to the type of connection destination
SEE ALSO
For condition specification and manipulation specification, see a chapter D3.3, “Logic Chart Block
(LC64).”

■ Function Blocks that Allow Sequence Connections and Their Target
Terminals ¡ £
The following table lists function blocks that allow sequence connections as well as their
I/O terminals.
Table A List of Function Blocks and Their Target Terminals that Allow Sequence Connections
¡£
Block type Block model name Target terminal name
Regulatory control PTC OUT
ST16
Q01 to Q56, J01 to J56
ST16E
LC64 Q01 to Q32, J01 to J32 (*2)
Sequence control TM
CTS OUT
CTP
VLVM J01 to J17
AND
OUT, Q01, Q02
OR
NOT IN, OUT
SRS1-S
Q01, Q02, J01
SRS1-R
SRS2-S
Q01, Q02, J01, J02
SRS2-R
Logical operation (*1)
WOUT OUT, Q01, Q02
OND
OFFD
IN, OUT
TON
TOFF
GT
GE OUT
EQ
General-purpose CALCU IN, OUT, Q01 to Q07, J01 to J03

calculation CALCU-C IN, OUT, Q01 to Q03, J01
C020301E.EPS
*1: ¡ £ Logic Operation Block can only be used for CS 3000.

*2: Input/output connection setting areas of sequence tables and logic chart block are equivalent to terminals.
Even if the function block has a terminal that allows sequence connections, it cannot be
connected by the sequence connection via a switch block (SW-33, SW-91).
A sequence connection (condition testing and status manipulation) cannot be set to the I/O
terminals that perform input and output of character string data.
I/O terminals which perform input and output of character string data are as follows:
Table I/O Terminal for Character String
Function block Terminal
CALCU-C Q04 to 07, J02, J03
DSW-16C OUT
BDSET-1C/2C J01 to J16
BDA-C J01 to J16
C020302E.EPS

<Toc> <Ind> <C2.4 Connection between Control Stations> C2-22
C2.4 Connection between Control Stations

A data item or I/O terminal of the function block in another control station can be
connected to the I/O terminal of the function block in the present control station.
■ Connection between Control Stations ¡ £

The connection between control stations (FCS) is an I/O connection method for establish-
ing data connection or terminal connection between the function block of the present
control station and that of another control station.
The maximum I/O terminal connection points for each type of field control station (FCS) are
as follows.
• Field Control Station : Maximum 160 points (*1)
• Field Control Station (Compact Type) : Maximum 160 points (*2)
• Enhanced Field Control Unit (RIO) : Maximum 512 points (*3)
• Field Control Unit (RIO) : Maximum 512 points (*4) (*7)
• Enhanced Field Control Unit (FIO) : Maximum 512 points (*5)
• Standard Field Control Station (FIO) : Maximum 512 points (*6) (*7)
*1: ¡ The maximum number of points may be connected to PFCS. If Batch Control database type is applied, this
number becomes 64.
*2: £ The maximum number of points may be connected to SFCS
*3: £ The maximum number of points may be connected to LFCS2.
*4: £ The maximum number of points may be connected to LFCS.
*5: £ The maximum number of points may be connected to KFCS2.
*6: £ The maximum number of points may be connected to KFCS.
*7: £ The maximum number of points may be connected to CS 3000 KFCS or LFCS varies with the following database
types.
The maximum number of points for Unit control (without recipes) type is 128.
The maximum number of points for Unit control (with recipes) type is 64.
The maximum number of points for Unit control (with recipes and valve monitors) type is 64.
Even between the function blocks that belong to different control stations (FCS) , the I/O
connection can be achieved by a similar procedure to that for the connection between
function blocks belong to the same control station. The following diagram shows an ex-
ample of cascade control using the connection between control stations (FCS).
Control bus
FCS1 FCS2
ADL
Function block Function block SET
PID PID
IN OUT IN OUT
Connection block between stations
C020401E.EPS
Figure Connection between Control Stations (FCS) (Example of the Cascade Control) ¡ £

■ Cases when Connection between Control Stations is not Allowed
The connection between control stations (FCS) is not allowed under the following circum-
stances:
• Sequence connection
• Connection to a process I/O (except for the contact I/O) and word data of communica-
tion I/O.
• Terminal connection to a switch block (SW-33, SW-91)
• Connection to an I/O terminal which corresponds to the faceplate block mode or
status
• Connection to an alarm input terminal of a Representative Alarm Block (ALM-R)
• Setting to character string data (The string data can be checked.)
• Foundation Fieldbus Faceplate Block OUT terminal
■ Data Connection with Other Control Stations

The inter-station connection block (ADL) is automatically generated if the I/O connection
information with respect to a function block of another control station is specified for the I/O
terminal of the function block at the connection source by using the Function Block Detail
Builder of Control Drawing Builder. Exchanging data with the function block of another
control station is done via the ADL block.
The setting items for the I/O connection information are the same as those within the same
control station.
The I/O operation and the function block processing remain synchronized because the
function block within the same control station performs the processing continuously accord-
ing to the defined execution order. On the other hand, I/O operations are performed asyn-
chronous to the function block processing in the I/O connection between different control
stations. Therefore, communications between control stations (FCS) should be avoided in
applications which require strict timings.
Function block
FCS 1 FCS 2
Function block Function block
IN
D1 ADL Data reference
Function block Function block
OUT
Data setting ADL D2
D1: Data 1
Inter-station connection block D2: Data 2
C020402E.EPS
Figure Connection between Control Stations (Data Connection)

■ Terminal Connection with Other Control Stations
It is possible to establish a terminal connection with a function block belongs to another
control station for the cascade control. The connection is possible even if the function block
in the downstream of the cascade belongs to another control station.
However, a select switch cannot be placed in the middle of the cascade connection.
Inter-station connection block

FCS 1 FCS 2
Terminal
ADL connection
Function block Function block SET
PID PID
IN OUT IN OUT
Terminal
connection
C020403E.EPS
Figure Connection Between Control Stations (Terminal Connection)

<Toc> <Ind> <C2.5 I/O Connection Information> C2-25
C2.5 I/O Connection Information

The I/O connection information is specified in order to identify the connection desti-
nation of the function block’s I/O terminal.
■ I/O Connection Information

This information is comprised of an element symbol name and data item name, indicating
the connection destination of the I/O terminal such as a tag name, label name, element
number, etc. The I/O connection information is added to the I/O terminal of the function
block.
In addition, in the case of sequence connection, condition testing or status manipulation is
also added to the I/O connection information.
The relationship between the connection methods and I/O connection information is as
follows:
Table I/O Connection Information
Connection method I/O signal I/O connection information (*1)
Process I/O tag name/user defined label name/terminal number.data item name
Communication I/O (*2) tag name/element number.data item name
Fieldbus I/O tag name/user defined label name/terminal number.data item name
Software I/O tag name/element number.data item name
Data Same control
reference tag name.data item name
drawing
Function Different control
tag name.data item name
block drawing
Different control
Data station
connection Process I/O tag name/user defined label name/terminal number.data item name
Communication I/O (*2) tag name/element number.data item name
Fieldbus I/O tag name/user defined label name/terminal number.data item name
Software I/O tag name/element number.data item name
Data setting Same control
drawing
block drawing
Different control
station
Same control
tag name.I/O connection terminal name
drawing
Terminal connection tag name.I/O connection terminal name
block drawing
Different control
tag name.I/O connection terminal name
station
Condition Process I/O tag name/user defined label name/terminal number/element number
Sequence testing Communication I/O (*2) .data item name.condition specification
connection Status Software I/O tag name/user defined label name/terminal number/element number
manipulation Function block .data item name.operation specification
C020501E.EPS
*1: The description like A/B/... means the I/O information specification have multiple methods. However, some elements
have exceptions that certain methods may not be applied.
*2: Access to the data acquired via communication with an external device using a communication module.

On the function block detail builder, for the logical name of the I/O connection information
with respect to the function blocks of different control stations, a (>) is added before tag
name. However, when AREAOUT block is used on control drawing builder, (>) is not
needed.
■ Terminal Numbers, Element Numbers ¡

The following table shows terminal numbers and element numbers included in the I/O
connection information.
Table List of Terminal Numbers and Element Numbers ¡
Name Symbol Symbol syntax
01: (fixed)
u: unit (1 to 5)
Process I/O %Z01usmm
s: slot (1 to 4)
mm: terminal (01 to 32)
nnnn: continuous number
Word data %WWnnnn (Standard type: 0001 to 1000)
(Enhanced type: 0001 to 4000)
Communication I/O
(*1) nnnn: continuous number
(Standard type: 0001 to 1000)
Bit data %WBnnnnbb
(Enhanced type: 0001 to 4000)
bb: bit number (01 to 16)
01: (fixed)
u: unit (1 to 5)
Fieldbus I/O %Z01usmm
s: slot (1 to 2)
Common switch %SWnnnn nnnn: continuous number (0001 to 1000)
Annunciator message %ANnnnn nnnn: continuous number (0001 to 0200)
Printout message (with data) %PRnnnn nnnn: continuous number (0001 to 0100)
Operation guide message %OGnnnn nnnn: continuous number (0001 to 0100)
Software I/O
Sequence message request %RQnnnn nnnn: continuous number (0001 to 0100)
Supervisory computer message
%M3nnnn nnnn: continuous number (0001 to 0100)
output for PICOT
Signal event message %EVnnnn nnnn: continuous number (0001 to 0100)
C020502E.EPS
*1: With communication I/O, the same I/O points can be accessed as word data (%WW) or bit data (%WB).

■ Terminal Numbers, Element Numbers £
The following table shows terminal numbers and element numbers included in the I/O
connection information.
Table List of Terminal Numbers and Element Numbers £
Name Symbol Symbol syntax
nn: Node number (01 to 10)
u: slot (1 to 8)
%Znnusmm s: 1 is fixed in Process I/O
(*1) In case of HART compatible modules,
analog input: s=1; HART variable: s=2.
Process I/O mm: terminal (01 to 64)
nn: (fixed at 01) (*3)
nn: Node number (01 to 08) (*4)
%Znnusmm
u: unit (1 to 5)
(*2)
s: slot (1 to 4)
Word data %WWnnnn nnnn: continuous number (0001 to 4000)
Communication I/O
(*5) nnnn: continuous number (0001 to 4000)
Bit data %WBnnnnbb
bb : bit number (01 to 16)
nn: Node number (01 to 10)
%Znnusmm u: slot (1 to 8)
(*1) s: segment (1 to 4)
Fieldbus I/O nn: (fixed at 01) (*3)
nn: Node number (01 to 08) (*4)
%Znnusmm
u: unit (1 to 5)
(*2)
s: slot (1 to 2)
Common switch %SWnnnn nnnn: continuous number (0001 to 4000)
nnn: continuous number (001 to 256)
Global switch %GSnnnmm
mm: station number (01 to 64)
Annunciator message %ANnnnn nnnn: continuous number (0001 to 0500)
Printout message (with data) %PRnnnn nnnn: continuous number (0001 to 0200)
Software I/O
Operation guide message %OGnnnn nnnn: continuous number (0001 to 0200)
Sequence message request %RQnnnn nnnn: continuous number (0001 to 0200)
Supervisory computer message
%M3nnnn nnnn: continuous number (0001 to 0100)
output for PICOT
Signal event message %EVnnnn nnnn: continuous number (0001 to 0200)
C020503E.EPS
*1: £ A symbol for KFCS2 or KFCS

*2: £ A symbol for LFCS2, LFCS or SFCS
*3: £ Can only be used for SFCS.
*4: £ Can only be used for LFCS2, LFCS.
*5: With communication I/O, the same I/O points can be accessed as word data (%WW) or bit data (%WB).

Blank Page
<Toc> <Ind> <C3. Input Processing> C3-1
C3. Input Processing

The function blocks are provided with various types of input processing methods to
convert the input signals for the control calculation and arithmetic calculation.
In this chapter the input processing methods common to all function blocks are
explained.
■ Input Processing
Input processing is a general term used for processing for the input signal read from the
connection destination of an input terminal, executed by the function block before the
calculation processing. There are various forms of input processing corresponding to the
function block type and the input signal format.
The Regulatory Control Blocks and Calculation Blocks have the common types of input
processing, and some function blocks have the particular types of input processing.
SEE ALSO
• The input processing for the Sequence Tables is unique and differs from that of the Regulatory Control
Blocks or Calculation Blocks. For the Sequence Tables input processing, see a chapter D3.2, “Sequence
Table Block (ST16, ST16E).”
• For details on input processing of the function blocks with sequence connection, see a chapter D3.3,
“Logic Chart Block (LC64).”
■ Input Processing Common to All Regulatory Control Blocks

The Regulatory Control Blocks have the input signals processed as shown in the figure
below. After the processing, the signal becomes process variable (PV).
Input Signal Conversion

PV
Overshoot CAL
No Conversion BAD
CAL PV
Analog Input Square Digital
Input Root Extraction Filter
Module
Pulse
Input Conversion CAL
BAD
Integration SUM
Communication
Input Conversion
C030001E.EPS
Figure Block Chart of Input Processing Common to All Regulatory Control Blocks

■ Input Processing Common to Calculation Blocks
The Calculation Blocks have the input signals processed as shown in the figure below. The
calculated input value (RV), calculated output value (CPV) or integrator value (SUM) are
obtained after the input processing.
BAD1
Q01 RV1
CPV
BADn Overshoot
Qn RVn
Calculation
IN No Conversion RV
Processing
Analog Input Square BAD CAL

Root Extraction
BAD
Digital Filter CPV
Pulse Input
Conversion
CAL
Communication
Input Conversion
Integration SUM
Input Signal Conversion
C030002E.EPS
Figure Block Chart of Input Processing Common to Calculation Blocks
■ Input Processing Common to Logic Operation Blocks £

The Logic Operation Blocks have the input signals processed as shown in the figure below.
The calculated input value (RV) and calculated output value (CPV) are obtained after the
input processing.
Q01 RV1
Qn No RVn
Conversion
Calculation
IN RV
Processing
Input Signal CAL

Conversion
CPV
C030003E.EPS
Figure Block Chart of Input Processing Common to Logic Operation Blocks £

■ Outline of Input Processing Common to Regulatory Control Block and
Calculation Block
The outline of each type of input processing common to Regulatory Control Blocks and to
Calculation Blocks is explained below.
● Input Signal Conversion

The input signal read from the input module or other function blocks is converted to process
variable (PV) or calculated input value (RV) according to the signal type.
● Digital Filter
This digital filter executes the first-order lag processing. Input signal noise can be reduced
through digital filtering process in which input signal is filtered for the Regulatory Control
Blocks while value after calculation processing is filtered for the Calculation Blocks.
● Integration
The data item (SUM) is set to the integrator value. Input signal is used for the Regulatory
Control Blocks while value after calculation processing is used for the Calculation Blocks
are used.
● PV/FV/CPV Scale out

If the data status of input signal is invalid (BAD), the process variable (PV), feedback input
value (FV) or calculated output value (CPV) is coincided with the scale high limit (SH) or
scale low limit (SL) depending on the cause of invalidity (BAD).
● Calibration
For maintenance or test purposes, the process variable (PV) or calculated output value
(CPV) can be set manually by using the operation and monitoring function.
■ Input Processing During Abnormal Status

The input processing during abnormal status is different from when it is normal. It is also
different between Regulatory Control Blocks and Calculation Blocks.
■ Input Processing for Sequence Connection ¡ £

For Logic Operation Blocks (*1) and General-Purpose Calculation Blocks (CALCU,
CALCU-C), the terminal connection may be used to link the sequence. When the terminal
connection is a sequence connection, the input is processed with “condition test.”
*1: ¡ £ Logic Operation Blocks are only supported by CS 3000.
SEE ALSO
For more information about input processing for sequence connection, see a chapter C3.7, “Input
Processing for Sequence Connection.”

■ Input Processing in Different Function Blocks
The input processing supported in function blocks vary with types of function blocks.
SEE ALSO
• For more information about the input processing in regulatory control blocks, see a chapter D1.1.3, “In-
put Processing, Output Processing, and Alarm Processing Possible for Each Regulatory Control Block.”
• For more information about the input processing in calculation blocks, see a chapter D2.3.1, “Input Pro-
cessing, Output Processing, and Alarm Processing Possible for Each Calculation Block.”

<Toc> <Ind> <C3.1 Input Signal Conversion> C3-5
C3.1 Input Signal Conversion

The input signal conversion is the function that converts the input signal read from
the input module or other function blocks into process variable (PV) or calculated
input value (RV) according to the signal type.
■ Type of Input Signal Conversion ¡ £

▼ Input Signal Conversion
There are five kinds of common input signal conversion for the Regulatory Control Blocks
and Calculation Blocks.
In addition, there are input signal conversion methods specific to particular function blocks.
The input signal conversion type can be set on the Function Block Detail Builder.
• Input Signal Conversion Type:
Select from “No Conversion,” “Square Root,” “Pulse-train,” “Control Priority Type
Pulse Train Input,” “Exact Totalization Pulse Train Input” and “Communications.”
The default setting is “No Conversion.”
● Input Signal Conversion Common to Regulatory Control Blocks and

Calculation Blocks
• No Conversion
• Square Root
• Pulse-train/ Control Priority Type Pulse Train Input/ Exact Totalization Pulse Train
Input
• Communications
Input signal conversion is performed only when the signal input through the input terminal
is the data connection type, one of the I/O connection types. And only the signal transmitted
via IN terminal (main input signal) may be converted. Furthermore, the conversion behaves
differently according to the signals connected to the IN terminal.
● Input Signal Conversion of Logic Operation Blocks £

• Bitwise Logic Operation Blocks, Logic Operation Blocks other than Relational Opera-
tion Blocks
• Bitwise Logic Operation Blocks
• Relational Operation Blocks

● Input Signal Conversion of Motor Control Blocks (MC-2, MC-3)
• Feedback Input Signal Conversion
• Answerback Input Signal Conversion
• Feedback Input to Answerback Input Conversion
SEE ALSO
For details on Input Signal Conversion of Motor Control Blocks (MC-2, MC-3), see a chapter D1.17.1,
“Input Processing of Motor Control Blocks (MC-2, MC-3).”
● Input Signal Conversion of Weight-Totalizing Batch Set Block (BSETU-3)

• Weight Measurement Conversion
• SUM Conversion
• SUM Conversion
SEE ALSO
For details on Input Signal Conversion of Weight-Totalizing Batch Set Block (BSETU-3), see a chapter
D1.22.1, “Input Signal Conversion of Weight-Totalizing Batch Set Block (BSETU-3).”
● Input Signal Conversion of Pulse Count Input Block (PTC)

• Input Signal Conversion for PTC Block
SEE ALSO
For details on Input Signal Conversion of Pulse Count Input Block (PTC), see a chapter D1.32, “Pulse
Count Input Block (PTC).”

C3.1.1 Input Signal Conversions Common to Regulatory Control

Blocks and Calculation Blocks
Input signal conversions common to the Regulatory Control Blocks and Calculation
Blocks include “No Conversion,” “Square Root,” “Pulse-train,” “Control Priority
Type Pulse Train Input,” “Exact Totalization Pulse Train Input,” and “Communica-
tions.”
The following section describes the conversion methods common to Regulatory
Control Blocks and Calculation Blocks.
■ No Conversion ¡ £
“No Conversion” is selected if the input connection destination is neither the pulse-train
input module nor communication module and the square root extraction of input signal is
not needed. Also, specify “No Conversion” when the input signal is data referenced from
another function block.
When “No Conversion” is selected, the input signal conversion is not performed. However,
the raw data (0 to 100 % data) read from analog input modules (except those from thermo-
couple or RDT modules) to the IN terminal are converted into the form of specified engi-
neering unit and scale high/low limits (SH, SL) for the process variable (PV). The raw data
read from the thermocouples and resistance temperature detectors to the IN terminal are
not converted. The data read from analog input modules to the input terminals other than
the IN terminal are not converted, either.
The table below lists the input range between each input module and the raw data.
Table Input Range of Input Module and Raw Data : PFCS/LFCS2/LFCS/SFCS
IOM Model Input Type Input Range Raw Data
Electric Current Input 4 to 20 mA 0 to 100 %
AAM10
Voltage Input 1 to 5 V 0 to 100 %
Electric Current Input 4 to 20 mA 0 to 100 %
AAM11
Voltage Input 1 to 5 V 0 to 100 %
mV Input Definable between -50 and 150 mV 0 to 100 %
Thermocouple Input
Measuring Range of the Measured
Measuring Range
Thermocouple Temperature
of Corresponding
AAM21
Resistance Temperature Measured
Measuring Range of the RTD
Detector Input Temperature
Potentiometer Input Definable between 0 and 30000 ohm 0 to 100 %
AMC80 Voltage Input 1 to 5 V 0 to 100 %

AMM12T Voltage Input 1 to 5 V 0 to 100 %
AMM22M mV Input Definable between -100 and 100 mV 0 to 100 %
Measuring Range of the Measured
AMM22T Thermocouple Input
Thermocouple Temperature
Resistance Temperature Measured
AMM32T Measuring Range of the RDT
Detector Input Temperature
AMM42T Electric Current Input 4 to 20 mA 0 to 100 %
C030101E.EPS

Table Input Range and Raw Data of Input Modules (1/2) : KFCS2/KFCS £
Type IOM Model Terminal No. I/O Type Input Range Raw Data
16-Channel Current Input;
AAI141-S 1 to 16 Current Input 4 to 20 mA 0 to 100%
Non-Isolated
AAI135-S 1 to 8 Current Input 4 to 20 mA 0 to 100%
Isolated
16-Channel Voltage Input;
AAV141-S 1 to 16 Voltage Input 1 to 5 V 0 to 100%
Non-Isolated
16-Channel Voltage Input;
AAV142-S 1 to 16 Voltage Input Definable within -10 to 10 V 0 to 100%
Non-Isolated
Thermocouple Measured
Rated range
16-Channel Thermocouple/ Input Temperature
AAT141-S 1 to 16
mV Input; Isolated Definable within
mV Input 0 to 100%
-100 to 150 mV
12-Channel Thermocouple Measured
AAR181-S 12 RTD Input Rated range
Input; Isolated Temperature
Rated range
16-Channel Thermocouple/ Input Temperature
AAT145-S 1 to 16
mV Input; Isolated Definable within
mV Input 0 to 100%
-100 to 150 mV
15-Channel Thermocouple
Input; Isolated AAT145-S 1 to 15 (*1) Rated range
Input Temperature
(MX Compatible)
Measured
16-Channel Thermocouple/ RTD Input Rated range
Temperature
Potentiometer Input; AAR145-S 1 to 16
Isolated Definable within
Potentiometer 0 to 100%
0 to 10Kohms
Number of
Number of pulse 0 to 65535;
8-Channel Pulse Input AAP135-S 1to 8 Pulse Input pulse (with
Time stamp (1ms)
time stamp)
Number of
16-Channel Pulse Input Number of pulse 0 to 65535; pulse
(PM1 Compatible) AAP149-S 1 to 16 Pulse Input
Time stamp (1ms) (with time
stamp)
8-Channel Current Input 1 to 8 Current Input 4 to 20 mA 0 to 100%
and 8-Channel Current AAI841-S
Output; Non-isolated 9 to 16 (Current Output) – –
8-Channel Voltage Input 1 to 8 Voltage Input 1 to 5 V 0 to 100%
and 8-Channel Current AAB841-S
Output; Non-isolated 9 to 16 (Current Output) – –
8-Channel Voltage Input 1,3,5.. 15
and 8-Channel Current Voltage Input 1 to 5 V 0 to 100%
Odd numbers
Output; Non-isolated AAB841-S
(MAC2 Terminal 2,4,6.. 16
–
Arrangement) Even numbers (Current Output) –
and 4-Channel Current AAI835-S
Output; Isolated 5 to 8 (Current Output) – –
C030111E.EPS
*1: The 16th channel of AAT 145 is used as cold junction compensation terminal, so that only 15 channels of the tempera-
ture signals from the field can be connected.

Table Input Range and Raw Data of Input Modules (2/2) : KFCS2/KFCS £
Type IOM Model Terminal No. I/O Type Input Range Raw Data

AAI141-H
(HART) 1 to 32 Digital (*2) Engineering Unit
8-Channel Current Input; 1 to 8 Current Input 4 to 20 mA 0 to 100%

AAI135-H
Isolate channels (HART) 1 to 32 Digital (*2) Engineering Unit
1 to 8 Current Input 4 to 20 mA 0 to 100%
8-Channel Current Output AAI841-H 9 to 16 Current Output 4 to 20 mA
(HART)
1 to 32 Digital (*2) Engineering Unit
1 to 4 Current Input 4 to 20 mA 0 to 100%
4-Channel Current Output AAI835-H 5 to 8 Current Output 4 to 20 mA
(HART)
1 to 32 Digital (*2) Engineering Unit
C030112E.EPS
*2: On IOM Builder for Analog Input and Output (HART Compatible) modules, element number is indicated as
%Znnusmm. When “s” is set to 1, the element is used as an analog input or output (Current Input/Current Output)
channel. When “s” is set to 2, the element is used as a HART variable channel.
If the input terminal connected to the process I/O is not IN terminal, the data is not con-
verted into engineering unit format, and the range of input signal is fixed to the raw data
range shown in the above table. The terminals of the function blocks that do not convert
input data into engineering unit format are listed in the table below.
Table Terminals of Function Blocks that do not Convert Data into Engineering Unit Format
Terminal Function Block
PID, PI-HLD, PID-BSW, ONOFF, ONOFF-G, PID-TP, PD-MR, PI-BLEND, MLD,
BIN/TIN
MLD-PVI, MLD-SW, RATIO, FFSUM, XCPL
ADD, MUL, DIV, AVE, TPCFL (Temperature, Pressure), ASTM1(Temperature),
Q1 to Q8
ASTM2 (Temperature), CALCU
C030102E.EPS

■ Analog Input Square Root Extraction ¡ £
The square root extraction of analog input signal can be performed in the function block.
For example, if a differential pressure type flow meter is used, the square root extraction is
normally executed in order to convert the analog input signal that indicates differential
pressure (differential pressure signal) into the signal that indicates flow (flow signal).
Shown below is the image of analog input square root extraction.
Calculated Output
PV Scale High Limit Lcut

0.0
Enlarged View
PV Scale Low Limit Raw Input Data

0.0 100.0 (%)
Lcut: Square Root Low-Input Cutoff Value (%)
C030103E.EPS
Figure Analog Input Square Root Extraction
Set a square root calculation low-input cut value when performing an analog input square
root calculation.
This function changes the value after square root calculation to 0 when the input signal is
below the low-input cut value.
The setup for square root calculation low-input cut value can be executed on the Function
Block Detail Builder.
• Square root calculation low-input cut value: Set at 0.0 to 100.0 %.
The default setting is 0.5 %.
Note that the square root calculation low-input cut value can be set only when “Square
Root” is selected as the input signal conversion type.
● Regarding to Square Root Extraction in I/O Module : PFCS/LFCS2/LFCS/

SFCS
Square root calculation can be performed in the AAM11 type current/voltage input module.
Do not select “Square Root” conversion for the function blocks connected to the AAM11
current/voltage input modules where the square root conversion is already defined on the
IOM Builder.
Since AMC80 multi-point control analog I/O module and AAM10 current/voltage input
module are not provided with square root extraction function, “Square Root” conversion
need to be specified in the function blocks connected to the modules if the square root
extraction is required.
● Regarding to Square Root Extraction in I/O Module : KFCS2/KFCS £

The I/O modules for KFCS do not have Square Root Extraction function. If square root
extraction is required, the conversion can be performed in the function block connected to
the I/O module by selecting “Square Root” as the input signal conversion on function block
builder.

■ Pulse-Train Input Conversion
A process variable (PV) is calculated based on the integrated pulse count value (P) read
from the pulse-train input module and its measurement time (t).
The pulse-train input processing calculates PV engineering unit data using the integrated
pulse count value (P) stored in sequence in the pulse input buffer and its measurement
time (t).
Pulse train input conversion is provided with the following three methods
• Control priority type pulse train input conversion (PULSE)
The accurate measured process variable (PV) and the calculated input value (RV)
may be obtained.
• Exact totalization pulse train input conversion (QTPUL)
The accurate integrator value (SUM) may be obtained.
• Pulse train input conversion (BTHPUL)
Both conversion methods, i.e., control priority type pulse train input conversion and
exact totalization pulse train input conversion are applied. The accurate measured
process variables (PV) and the calculated input values (RV) are obtained by control
priority type pulse train input conversion while the accurate integrator value (SUM) is
obtained by exact totalization pulse train input conversion.
When applying the pulse train input conversion (BTHPUL) to the following function
blocks, it only functions to obtain the calculated input values (RV) same as obtained
by control priority type pulse train input conversion.
ADD, MUL, DIV, SQRT, EXP, LAG, INTEG, LD, RAMP, LDLAG, DLAY, DLAY-C, AVE-
M, AVE-C, FUNC-VAR, TPCFL, ASTM1, ASTM2
It is required to specify the conversion method to exact totalization pulse train input conver-
sion (QTPUL) when the converted process variable (PV) or calculated output value (CPV)
are used by other function blocks for totalization. Otherwise, the totalized value may result
deviation.
However, the pulse rate and size of pulse-train input buffer are the same for all the tree
methods of pulse conversion.

● Control Priority Type Pulse-Train Input Conversion
Shown below is the block chart of the pulse-train input conversion processing.
+
/ • Scale PV
-
Pulse Input Buffer

P[0] ......
P, t P[1] P[2] P[N]
1/Prate
t[1] t[2] ...... t[N]
t[0]
Pulse Input +
Module
C030104E.EPS
Figure Block Chart of Pulse-Train Input Conversion Processing
The following is the computational expression for the pulse train input conversion:
P[0]-P[N] 1
PV= • • (SH-SL)+SL
t[0]-t[N] Prate C030105E.EPS
PV: process variable (engineering unit)

P[0]: current integrated pulse count value
P[N]: integrated pulse count value before N scan period
t[0]: current integrated pulse count value measurement time
t[N]: integrated pulse count value measurement time before N scan period
Prate: pulse rate (Hz)
SH: PV scale high limit
SL: PV scale low limit (measurement value when input pulse frequency is 0 Hz)
N: size of pulse input buffer

● Exact Totalization Pulse Train Input Conversion
Shown below is the block chart of the exact totalization pulse train input conversion pro-
cessing.
+
/ • Scale PV
-
Pulse Input Buffer

P[0] ......
P, t P[1] P[2] P[N]
1/Prate
t[1] t[2] ...... t[N]
t[0]
Pulse Input +
Module
C030106E.EPS
Figure Block Chart of Exact Totalization Pulse Train Input Conversion Processing
The following is the computational expression for the exact totalization pulse train input
conversion:
P[0]-P[N] 1
PV= • • (SH-SL)+SL
N•Ts Prate C030107E.EPS
PV: process variable (engineering unit)

P[0]: current integrated pulse count value
P[N]: integrated pulse count value before N scan period
Prate: pulse rate (Hz)
SL: PV scale low limit (measurement value when input pulse frequency is 0 Hz)
N: size of pulse input buffer
Ts: scan period
With exact totalization pulse train input conversion, the process value (PV) may not stabi-
lize and oscillate during operation, particularly during high-speed scan periods. In this
situation, the oscillation of the process value (PV) can be minimized by enlarge the size of
input buffer.

● Pulse Rate (Prate)
Pulse rate refers to the input frequency measured when the process variable reaches the
scale high limit. It is indicated in the unit of Hz.
The setup for pulse rate can be executed on the Function Block Detail Builder.
• Pulse Rate: Set a value within the range between 0.10 and 10000.00 Hz.
The default value is 1 Hz.
The following is the computational expression for pulse rate:
Prate = (SH-SL) • (pulse conversion factor)
An example of pulse rate calculation is as follows:

If the range between process variable is 0 to 2 kᐉ/min and the pulse conversion factor for
the flow meter is 2.54 pulse/ᐉ, the range between process variables is converted into the
time unit (sec.) used for pulse rate as follows.
SL=0
SH=2 (kᐉ/min)= 2 (kᐉ/sec)
60 C030108E.EPS
The pulse conversion factor is converted into the flow unit (kᐉ) used for process variables.
Pulse conversion factor = 2.54 pulse/ᐉ = 2.54 • 1000 pulse/kᐉ
The pulse rate is then calculated by assigning the range between process variable and the
pulse conversion factor to the pulse rate computational expression.
2 •2.54•1000=84.67(Hz)
Prate=
60 C030109E.EPS

● Pulse Train Input Buffer (N)
▼ Number of Input Buffers
If the pulse rate (input pulse frequency) is low, the instantaneous process variable obtained
based on the integrated pulse count values in a short interval will have a large error. In the
exact totalization pulse train input conversion, the size of pulse train input buffer (N) is
automatically determined so that a suitable value can be obtained for the sample cycle (t[0]
- t[N]) according to the pulse rate.
The table below lists the relation between the pulse rate and the size of pulse train input
buffer (N) when “Auto” is selected for the pulse train input buffer (N).
Table Pulse Rate and Size of Pulse Train Input Buffer
Pulse Rate (Prate) Size of Pulse Input Buffer (N)
Prate10 Hz 10
10 Hz<Prate<1 KHz 5
Prate1 KHz 3
C030110E.EPS
The setup for pulse train input buffer (N) can be executed on the Function Block Detail
Builder.
• Pulse Train Input Buffer (N): Select from the range between 1 and 10 or “AUTO.”
The default is “AUTO.”

■ Communication Input Conversion
The communication input conversion performs “Data Conversion” and “High/Low-Limit
Check” for the input data read from the communication input modules.
● Data Conversion
With communication input, the raw input data read from the input terminal may be in the
format specific to the connection destination. Those data need to be converted into process
variables (PV) in the engineering unit.
The following is the computational expression for the communication input conversion:
Y = GAIN • X+BIAS
Y: PV (engineering unit)
X: data read from communication input module
GAIN: data conversion gain
BIAS: data conversion bias
The setup for data conversion gain and data conversion bias can be executed on the
Function Block Detail Builder.
• Data Conversion Gain:
Set a maximum of 9-digit numeric value including sign and decimal point.
The default setting is 1.000.
• Data Conversion Bias:
Set a maximum of 9-digit numeric value including sign and decimal point.

● High/Low-Limit Check
The high-low limit check is executed in order to induce the input open alarm status in the
function block.
The following conditions are the input high limit set value or the input low limit set value
trigger alarms or reset alarms.
• Condition for high limit input open (IOP)
Y > input high limit detection set value
Input high limit detection set value = 106.25 % (PV scale span)
• Condition for low-limit input open (IOP-)
Y < input low limit detection set value
Input low limit detection set value = -6.25 % (PV scale span)
• Condition of recovering from status IOP
Y < input high limit detection set value - hysteresis value
• Condition of recovering from status IOP-
Y > input high limit detection set value + hysteresis value
The input high-limit detection set value and the input low-limit detection set value can also
be changed on the Function Block Detail Builder.
They may be set between -25.0 and 125.0 %. The default settings are 106.25 % for the
input high-limit detection set value and -6.25 % for the input low-limit detection set value.
The hysteresis value is the same value used for PV high/low-limit alarm (HI, LO).

C3.1.2 Input Signal Conversion for Logic Operation Blocks

Input Signal Conversion for Logic Calculation Input includes 3 types, they are “Con-
vert to Integer”, “No Conversion (in Hex.)” and “No Conversion.”
■ Input Signal Conversion for Logic Operation Blocks (except for Bitwise
Logic Operation Blocks and Relational Operation Blocks) £
“Convert to Integer” is fixed for this type of blocks.
The input data from the input connection terminal is converted to calculated input value
(RV). If the connection of blocks are reference type, the referred data is converted to the
integer and the first digit after decimal point is round off.
■ Input Signal Conversion for Bitwise Logic Operation Blocks £

“No Conversion (in Hex.)” is fixed for this type of blocks.
Only a certain types of data are allowed to be connected to the input terminals or to be
connected via reference connection. The input processing and the integration functions are
not provided. For the data in the connected destination function blocks, only data reference
connection type may be applied.
Input signal: Binary string (Integer)
Calculated Input Value (RV) is displayed in hexadecimal in 8 digits.
■ Input Signal Conversion for Relational Operation Blocks £

“No Conversion” is fixed for this type of blocks.
Only a certain types of data are allowed to connected to the input terminals or for the
reference connection. The input processing and the integration functions are not provided.
For the data in the connected destination function blocks, only data reference connection
type may be applied.

<Toc> <Ind> <C3.2 Digital Filter> C3-19
C3.2 Digital Filter

The digital filter is a function to remove the noises from process input signals.
■ Digital Filter
▼ Input Signal Filtering
The digital filter is a function in which the input signal is processed by the first-order lag filter
in order to reduce input signal noise.
● Digital Filter for Regulatory Control Block

In the Regulatory Control Blocks, the filtering process is executed for input signal (main
input signal) read from the IN terminal only, following input signal conversion.
● Digital Filter for Calculation Block

In the Calculation Blocks, the digital filter processing is executed for the General-Purpose
Calculation Blocks and the Data set block with input indicator only. Each block uses a
different filtering method.
• In the General-Purpose Calculation Blocks, the digital filter processing is executed
following calculation processing.
• In the Data set block with input indicator, the filtering process is executed for input
signal (main input signal) read from the IN terminal only, following input signal conver-
sion.

■ Computational Expression for Digital Filter
The following is the computational expression for the digital filter:
Yn=(1-) • X + • Yn-1
: Filter coefficient
X: Input value
Yn: Current filtering data
Yn-1: Previous filtering data
Shown below is the step response of digital filtering process.
100 % Input (X) Output (Yn)
=0.5
Timing lag between input and calculation
Calculation interval
0
0 1 2 3 4 5 6 7 Time (sec)
C030201E.EPS
Figure Step Response of Digital Filtering Process
● Digital Filter Coefficient ¡ £

▼ Digital Filter Coefficient 1 to 3
There are three kinds of digital filter coefficients. These digital filter coefficients are set by
the FCS Constants Builder for each FCS.
• Digital Filter Coefficient 1: 0 to 1.00 (0.01 unit)
The defaults for these digital filter coefficients are set to the values indicated below.
• Digital Filter Coefficient 1: 0.5
(When the digital filter coefficient is 0.5 and scan period is 1 second, the time constant
is 1 second)
(When the digital filter coefficient is 0.75 and scan period is 1 second, the time con-
stant is 3 seconds)
(When the digital filter coefficient is 0.875 and scan period is 1 second, the time
constant is 7 seconds)

When high-speed scan is used, the time constant changes in accordance with the scan
period. Since the scan period is getting shorter at high-speed scan rate, the time constant
is getting smaller accordingly.
For input indicator blocks (PVI), input indicator blocks with deviation alarm (PVI-DV),
general-purpose calculation blocks (CALCU), general-purpose calculation blocks with
string I/O (CALCU-C), if scan coefficient is specified as 2 or greater on the Function Block
Detail Builder, the digital filtering coefficient should be multiplied by the specified scan
coefficient.
■ Input Filter Specification

▼ Input Signal Filtering
The digital filter may be defined for each function block in “Input Signal Filtering” on the
Input Signal Filtering: “None,” “Auto,” “1,” “2” and “3.”
The default setting is “Auto.”
Given below are the actions performed for each type of the input signal filtering.
• Auto
If the IN terminal is connected to I/O module other than communication module,
“Digital Filter Coefficient 1” is used. If the IN terminal is connected to neither communi-
cation module nor I/O module, no filtering process is performed.
• None
No filtering process is performed.
• 1
Digital Filter Coefficient 1 is used.
• 2
• 3

<Toc> <Ind> <C3.3 Integration> C3-22
C3.3 Integration
Integration refers to the function in which the input signal or the value after calcula-
tion processing is integrated.
■ Integration
The integration processing for each of the function blocks is indicated below.
● Integration for Regulatory Control Block

In the Regulatory Control Blocks, the integration process is executed for input signal (main
input signal) read from the IN terminal only, following input signal conversion.
The integration process in BSETU-2 and BSETU-3 is different from other regulatory control
blocks.
SEE ALSO
For more information about integration process in BSETU-2 and BSETU-3, see a chapter D1.20.1, “Input
Processing of Totalizing Batch Set Blocks (BSETU-2 and BSETU-3).”
● Integration for Calculation Block

In the Calculation Blocks, the integration processing is executed for the General-Purpose
Calculation Blocks and the Data set block with input indicator only. Each block uses a
different filtering method.
• In the General-Purpose Calculation Blocks, the integration processing is executed
following calculation processing.
• In the Data set block with input indicator, the integration process is executed for input
signal (main input signal) read from the IN terminal only, following input signal conver-
sion.
■ Computational Expression for Integration

▼ Totalizer
The following is the computational expression for the integration:
Ts
SUMn = X • +SUMn-1
Tk C030301E.EPS
X: Integrated input signal

Input value after input signal conversion. However, PV value if the PV data status is CAL.
SUMn: Current integrator value
SUMn-1: Previous integrator value
Ts: Scan period (sec)
Tk: Time scale conversion coefficient

● Time Scale Conversion Coefficient
▼ Totalizer Time Unit
The time scale conversion coefficient (Tk) is set corresponding to the totalizer time unit.
The table below lists the correlation between the time scale conversion coefficient and the
totalizer time unit.
Table Time Scale Conversion Coefficient and Totalizer Time Unit
Time Scale Conversion
Totalizer time unit Coefficient (Tk)
Second 1
Minute 60
Hour 3600
Day 86400
C030302E.EPS
The time scale conversion coefficient (Tk) is automatically determined when the totalizer
time unit is set on the Function Block Detail Builder. The totalizer time unit must be set in
the same unit as the measurement value (PV). For example, if the unit of PV is “m3/min,”
set the totalizer time unit to “minute”
• Number of digits for integrator value
Up to 8 digits can be used. If the integrator value exceeds 8 digits, the value returns to
0 and the integration processing continues.
• A negative integration input signal value can be integrated as a negative value. How-
ever, integration of negative values can be executed only when the low-input cutoff
value is negative.
• Unit
Engineering unit is used.
The totalizer time unit can be defined on the Function Block Detail Builder.
• Totalizer Time Unit
Select “Second,” “Minute,” “Hour,” “Day” or “None.”
The default setting is “None,” however for the BSETU-2 block the default setting is
“Hour.”
If “None” is specified as the totalizer time unit, integration will not be executed.

● Low-Input Cut
The integration operation differs by the integration low-input cut value setting as explained
below.
• If the low-input cut value is positive (including 0):
Integration is not executed for the input signal (including negative value) less than the
low-input cut value.
• If the low-input cutoff value is negative:
Integration is not executed for the input signal if the absolute value of the input signal
is less than that of the low-input cut value.
When the integration of the reverse direction flow measurement (negative value input) is
allowed, integration cannot be executed for small flow in either direct or reverse direction if
a negative value is set to the low-input cut value.
The low-input cut value can be specified on the Function Block Detail Builder.
• Totalizer Low-Input Cut Value:
Set the data in the same unit of integrator value (PV), or percentage value for the PV
scale span.
If a percentage value is used, add % after the value.
The default setting is 0 %.

<Toc> <Ind> <C3.4 PV/FV/CPV Overshoot> C3-25
C3.4 PV/FV/CPV Overshoot

The PV/FV/CPV overshoot refers to the function in which the process variable (PV/
FV) or the calculated output value (CPV) is coincided with the scale high-limit (SH) or
the scale low-limit (SL) when the status of input signal is invalid (BAD).
This section describes PV, FV and CPV overshoot.
■ PV Overshoot
▼ PV Overshoot
When the data status of input signal becomes invalid (BAD), the PV overshoot function
overshoots the process variable (PV), or upscales it to scale high-limit or downscales it to
scale low-limit. The PV overshoot is supported only for the Regulatory Control Blocks.
Since the PV overshoot is for process input signal, it is executed when the I/O connection
type is process I/O.
The following table shows the relationship between the cause for invalidity (BAD) and
process variable (PV) when the PV overshoot is used.
Table Reason for Invalidity (BAD) and Overshoot Value
Cause of invalidity (BAD) Overshoot
High-limit input open (IOP+) Upscale to high-limit (SH)
Low-limit input open (IOP-)
Downscale to low-limit (SL)
Process I/O failure or other error
C030401E.EPS
The PV overshoot can be specified on the Function Block Detail Builder.

• PV Overshoot: Select “Overshoot PV” or “Holding PV.”
The default setting is “Holding PV.”
With “Holding PV,” when the data status of process variable (PV) becomes invalid, the last
good process variable is held.
Furthermore, when the input signal is not a process input signal, the operation becomes
“Holding PV” even though “Overshoot PV” is specified.

<Toc> <Ind> <C3.4 PV/FV/CPV Overshoot> C3-26
■ FV Overshoot
▼ FV Overshoot
When the data status of input signal becomes invalid (BAD), the feedback input value (FV)
may be overshot to be the same as the scale high-limit or the scale low-limit. The FV
Overshoot is only available for motor control block.
The FV overshoot can be specified on the Function Block Detail Builder.

• FV Overshoot: Select “Holding FV Value” or “Overshoot FV Value.”
The default setting is “Holding FV Value.”
■ CPV Overshoot
▼ PV Overshoot
When the status of input signal is invalid (BAD). The CPV overshoot function overshoots
the calculated output value (CPV), or upscales it to the scale high-limit (SL) or downscales
it low-limit (SH). CPV overshoot is supported for the General-Purpose Calculation Blocks
and the Data set block with input indicator, the Analog Calculation Blocks and the Arith-
metic Calculation except Averaging Block.
Since the CPV overshoot is for process input signal, it is executed when the I/O connection
type is process I/O.
The following table shows the relationship between the cause for invalidity (BAD) and
calculated output value (CPV) when the CPV overshoot is used.
Table Reason for Invalidity (BAD) and Overshoot Value
Cause of invalidity (BAD) Overshoot
High-limit input open (IOP+) Upscale to high-limit (SH)
Low-limit input open (IOP-)
Downscale to low-limit (SL)
Process I/O failure or other error
C030402E.EPS
The CPV overshoot can be specified on the Function Block Detail Builder.
• PV Overshoot: Select either “Overshoot PV” or “Holding PV.”
The default setting is “Holding PV.”
With “Holding PV,” when the data status of calculated output value (CPV) becomes invalid,
the last good calculated output value is held.
Furthermore, when the input signal is not a process input signal, the operation becomes
“Holding PV” even though “Overshoot PV” is specified.

<Toc> <Ind> <C3.5 Calibration> C3-27
C3.5 Calibration
The calibration is a function in which the emulated signals for process variables (PV)
or calculated output values (CPV) in the function block can be set manually with the
operation and monitoring function for maintenance or test purpose. The state in
which calibration is being executed is called calibration status.
The calibration mode differs between Regulatory Control Blocks and Calculation
Blocks.
■ Calibration for Regulatory Control Block

In Regulatory Control Blocks, calibration is executed when the data status of process
variable (PV) is set to calibration (CAL) by the operating and monitoring function.
The following are the indications of Regulatory Control Blocks in calibration status:
• The color of the operation and monitoring function PV bar display turns to cyan.
• A process variable (PV) can be set manually.
• The integration is continued with the process variable (PV) entered.
• The alarm check for the process variable (PV) entered is bypassed.
• In the function block with manual mode (MAN), the block mode switches to manual
mode.
• In the case of Motor Control Blocks (MC-2, MC-3), feedback input signal processing
and answerback input signal processing are stopped. In this case, the answerback
raw signal (RAW) follows the input signal.
The following occurs when the Weight-Totalizing Batch Set Block (BSETU-3) changes to
the calibration mode.
• Absolute integrator value (SUM0) and integrator value (SUM) can be set manually.
• Block mode changes to manual (MAN) mode.

<Toc> <Ind> <C3.5 Calibration> C3-28
■ Calibration for Calculation Block
In Calculation Blocks, calibration is executed when the data status of calculated output
value (CPV) is set to calibration (CAL) by operating the operation and monitoring function.
The Calculation Blocks in calibration status behaves as follows:
• The color of the operation and monitoring function CPV bar display turns to cyan.
• The calculated output value (CPV) can be entered manually.
• The integration is continued with the calculated output value (CPV) entered.
• The alarm check for the calculated output value (CPV) entered can be bypassed.
• The calculation stops while the block is still in automatic mode (AUT).
• The output of the secondary calculated output values (CPV1 to CPVn) stops.
• The output of the primary calculated output value (CPV) is processed as usual.
There is no calibration in the Calculation Auxiliary Blocks except the Data set block with
input indicator (DSET-PVI).
The block with calculated output value (CPV1) instead of calculated output value (CPV) is
in calibration state when the data status of calculated output value (CPV) is set to calibra-
tion (CAL). In this state, the calculated output value (CPV1) can be set manually and the
output of the values greater than CPV2 stops.
IMPORTANT
When the output destination is cascade open or output fail in the function block in which the
output value tracking is set to “Yes,” the tracking function precedes even if the data status
of calculated output value (CPV) is in calibration (CAL).
● Calibration for Inter-Terminal Connected Calculation Blocks

Among various Calculation Blocks, the Analog Calculation Blocks listed below may perform
calibration only as input processing in a case where data is entered as the calculated input
value (RV) from other function blocks using terminal connection to the input terminal (IN).
• Square Root Block (SQRT)
• Exponential Block (EXP)
• First-Order Lag Block (LAG)
• Integration Block (INTEG)
• Derivative Block (LD)
• Lead/Lag Block (LDLAG)
• Dead-Time Block (DLAY)
• Dead-Time Compensation Block (DLAY-C)
• Variable Line-Segment Function Block (FUNC-VAR)

<Toc> <Ind> <C3.6 Input Processing in the Unsteady State> C3-29
C3.6 Input Processing in the Unsteady State

In the unsteady state, the function block may execute a different input processing
from that in the normal state. This section explains input processing in the unsteady
state. Input processing in the unsteady state differs between the Regulatory Control
Blocks and Calculation Blocks.
■ Unsteady State of the Regulatory Control Blocks

The following section describes the unsteady states in the Regulatory Control Blocks and
the special input processing.
● Unsteady States
The Regulatory Control Blocks suffer the following unsteady states:
• Input signal error (PV BAD)
The data status of process variable (PV) is invalid.
• Calibration (PV CAL)
The data status of process variable (PV) is calibration (CAL).
• Input connection open
The input connection destination is the selector switch which is in open state.
● Executing Special Input Processing

The special input processing is also executed in the states below, although they are not
unsteady states.
• Terminal connection
The input terminal (IN) is connected via terminal connection with an output terminal of
the other function block. This type of connection is used for the cascade loops with
blocks such as Ratio Set Block (RATIO).
• Input connection undefined
The input connection is not defined. The loop is in unconnected state.
SEE ALSO
For the input processing of Regulatory Control Blocks in the unsteady state, see a chapter C3.6.1, “Input
Processing of the Regulatory Control Block in Unsteady State.”

■ Unsteady State of the Calculation Blocks
The Calculation Blocks suffer the following unsteady states:
• Input signal error
The data status of input signal is invalid (BAD).
• Calibration (CAL)
The data status of calculated output value (CPV) is calibration (CAL).
• The abnormal calculated input value is detected
The data status of calculated input value (RV) is invalid (BAD).
SEE ALSO
For the input processing of calculation block in the unsteady state, see chapter C3.6.2, “Input Processing
of the Calculation Block in Unsteady State.”

C3.6.1 Input Processing of the Regulatory Control Block in

Unsteady State
This section explains the input processing of Regulatory Control Blocks in unsteady
and special state.
■ Input Processing at Input Signal Error (PV BAD)

The Regulatory Control Blocks executes the following operations when input signal error
(PV BAD).
• If the data reference is available, the input signal is read to update the data status
without updating the data value.
• Input signal conversion is halted. For pulse input conversion, the contents of pulse
input buffer is initialized when the processing is restarted.
• Integration is halted and the integrator value is held. The integration is continued from
the held value when the processing is restarted.
• The digital filtering is halted. The previous value is initialized when the processing is
restarted.
• The PV/FV overshoot operates when the PV/FV overshoot is specified.
■ Input Processing at Calibration (PV CAL)

The Regulatory Control Blocks executes the following operations at calibration (PV CAL).
• If the data reference is available, the input signal is read to update the data status
without updating the data value. However, the data status of the process variable (PV)
is calibration (CAL).
• The input signal conversion is halted. For the pulse input conversion, the contents of
the pulse input buffer is initialized when the processing is restarted.
• The integration is continued with process variables (PV).
• The digital filtering is halted. The previous value is initialized when the process is
restarted from the halt status.
■ Input Processing at Open Input Connection

The Regulatory Control Blocks executes the following operations at open input connection.
• The input signal conversion is halted. For the pulse input conversion, the contents of
the pulse input buffer is initialized when the processing is restarted.
• The integration is halted and the integrator value is held. The integration is continued
from the hold value when the processing is restarted.
• The digital filter processing is halted. The previous value is initialized when the pro-
cessing is restarted.

■ Input Processing at Terminal Connection
The Regulatory Control Blocks executes the following operations at terminal connection.
• The input signal conversion is halted.
• Process variables (PV) are integrated.
• The digital filtering is halted.
■ Input Processing at Input Connection Undefined

The Regulatory Control Blocks executes the following operations at input connection
undefined.
• The input signal conversion is halted.
• The integration is halted and the integrator value is held.
• The digital filtering is halted.

C3.6.2 Input Processing of the Calculation Block in Unsteady

State
This section explains the Input processing of the Calculation Blocks in the unsteady
state.
■ Input Processing at Input Signal Error

The Calculation Blocks executes the following operations when input signal error.
• When the data status of the primary input from the input terminal (IN) is invalid (BAD),
the calculated input value (RV) update, digital filter and integration processings are
halted.
The previous calculated input value (RV) is held and the data status of calculated
input value (RV) becomes invalid (BAD). The digital filter initializes the previous value
when the processing is restarted from the halt status.
While the integration is halted, the integrator value is held, and the integration is
continued from the hold value when the processing is restarted.
• When the data status of the secondary input from the input terminal (Qn) is invalid
(BAD), the previous calculated input value (RVn) is held and the data status of the
calculated input value (RVn) becomes invalid (BAD).
• When the CPV overshoot is specified, the calculated output value (CPV) is overshoot
in the specified direction if the data status of the primary input becomes invalid (BAD).
• Input open data status signals (IOP, IOP-) are not detected for the terminals that are
connected in sequence connection. If the input signal could not be obtained, the
condition will be tested using the previous input value.
■ Input Processing at Calibration

The Calculation Blocks executes the following operations at calibration (CAL).
• The input signal conversion is executed, and the calculated input value (RV, RVn) and
the data status continue to be updated.
• The digital filer is halted. The previous value is initialized when the processing is
restarted from the halt status.
• The integration is continued. However, the calculated output value (CPV) is integrated
at calibration (CAL).
• The CPV overshoot does not operate at calibration (CAL).

■ Input Processing at Calculated Input Value Error Detection
▼ Calculated Input Value Error Detected
The Calculation Blocks executes the following operations if a calculated input value error
were detected.
• When the data status of calculated input value (RV) of the primary input from the input
terminal (IN) is invalid (BAD), the calculation is not executed, the data status of the
calculated output value (CPV) becomes invalid (BAD) and the previous calculated
output value is held.
• When the data status of the calculated input value (RVn) of the secondary input is
invalid (BAD), the calculation processing is continued using the previous calculated
input value (RVn) held, and the calculated output value (CPV) is updated. However,
the data status of the calculated output value (CPV) becomes “questionable” (QST).
• The Arithmetic Calculation Blocks, the General-Purpose Calculation Blocks and the
Logic Operation Blocks used for auxiliary inputs perform the input error detection by
themselves.
The table below shows the correlation among the data statuses of the calculated input
value (RV) of the primary input and the calculated input value (RVn) of the secondary input,
and the calculated output value (CPV).
Table Correlation of the Data Statuses RV, RVn and CPV
Calculated input value (RV) Calculated input value (RVn)
Calculated output value (CPV)
of the primary input of the secondary input
BAD - BAD
NR BAD QST
NR NR NR
C030601E.EPS
BAD: Data value BAD

NR: Neither BAD nor QST
QST: Questionable
-: Ignore (don’t care)

● Input Processing at Calculated Input Value Error Detection in the
Arithmetic Calculation
For Arithmetic Calculation Blocks other than the AVE block, the conditions for detecting an
error in calculated input values and the data status setting of the calculated output value
when an error is detected are defined in the “Calculated input value error detected” of the
The method to transfer the data status (IOP, IOP-, OOp, NRDY) of the process I/O rela-
tions, which is generated with the calculated input value (RV, RV1) in connection with the
above settings, to the calculated output value is specified. The table below describes the
specified ranges 0 to 6. The default value is “1.”
Table Specification for Calculated Input Value Error Detected in the Arithmetic-Calculation
Blocks Except AVE block
Error detection conditions Data status
Calculated input value error (Data statuses of the calculated
detection specification CPV data status transmission origin
input values below are BAD.) input value
0 - - No transmission
RV BAD
1 RV
RV1 QST
RV1 BAD
2 RV1
RV QST
RV and RV1 BAD RV priority
3
RV QST No transmission
4
RV1 QST No transmission
5
RV or RV1 QST No transmission
6 RV or RV1 BAD RV priority
C030602E.EPS
-: Ignore (Don’t care)
When the calculated input value error which causes the invalid (BAD) data status of calcu-
lated output value (CPV) occurs, the calculation processing is halted, and the previous
calculated output value (CPV) is held.
When the calculated input value error which causes the questionable (QST) data status of
calculated output value (CPV) occurs, the previous calculated input value is held due to the
current calculated input value error. The calculation processing is continued using the
previous value (RV) held and the calculated output value (CPV) is updated.
If CPV overshoot is being used, when the data status of the calculated output value is an
invalid data value (BAD) because the data status of the calculated input value (RV) of the
primary input is an invalid value (BAD), the calculated output value (CPV) overshoot in the
specified operational direction.
● Input Processing at Calculated Input Value Error Detection in the Averag-

ing Block (AVE)
AVE block behaves differently from other arithmetic calculation blocks when input error is
detected.
SEE ALSO
For more information about the behavior of AVE block when input error is detected, see a chapter D2.7,
“Averaging Blocks (AVE).”

● Input Processing at Calculated Input Value Error Detection in the Auxiliary
Inputs (RVn)-Used Logic Operation Blocks £
For Logic Operation Blocks using auxiliary inputs (RVn), the conditions for detecting an
error in calculated input values and the data status setting of the calculated output value
when an error is detected are defined in the “Calculated input value error detected” of the
tions, which is generated with the calculated input value (RV1, RV2) in connection with the
above settings, to the calculated output value is specified. The table below describes the
specified ranges 0 to 6. The default value is “1.”
Table Specification for Calculated Input Value Error Detected in the Arithmetic-Calculation £
Error detection conditions Data status

Calculated input value error
(Data statuses of the calculated CPV data status transmission origin
detection specification input value
input values below are BAD.)
0 - - No transmission
RV1 BAD
1 RV1
RV2 QST
RV2 BAD
2 RV2
RV1 QST
RV1 and RV2 BAD RV1 priority
3
4
5
RV1 or RV2 QST No transmission
6 RV1 or RV2 BAD RV1 priority
C030604E.EPS
-: Ignore (Don’t care)
● Input Processing at Calculated Input Value Error Detection in the General-

Purpose Calculation Blocks (CALCU, CALCU-C)
CALCU and CALCU-C blocks behave differently from other arithmetic calculation blocks
when input error is detected.
SEE ALSO
For more information about the behavior of CALCU and CALCU-C blocks when input error is detected,
see a chapter D2.33, “General-Purpose Calculation Blocks (CALCU, CALCU-C).”

<Toc> <Ind> <C3.7 Input Processing for Sequence Connection> C3-37
C3.7 Input Processing for Sequence Connection

As a special input processing when using the sequence connection, there is “condi-
tion testing” for the input signals. When using the sequence connection, the “Cali-
bration” function partially differs.
■ Input Processing for Sequence Connection ¡ £

For the General-Purpose Calculation Blocks and Logic Operation Blocks (*1), the se-
quence connection can be used as the I/O connection method.
When using the sequence connection for the Logic Operation Blocks (*1) and for CALCU
and CALCU-C blocks, there are two types of special input processing as follows:
• “Condition testing” for input signals
• “Calibration”
*1: ¡ £ Logic Operation Blocks are only supported by CS 3000.
■ Input Processing Block Chart for the Sequence Connection

The input processing block chart for the sequence connection is shown below.
CAL
IN
Condition testing RV
CPV
Q01 CAL
Condition testing RV1 CPV1
Logic
operation
Qn CAL
Condition testing RVn CPVn
C030701E.EPS
Figure Block Chart of Input Processing for Sequence Connection

<Toc> <Ind> <C3.7 Input Processing for Sequence Connection> C3-38
■ Condition Testing ¡ £
For sequence connection, the input terminals (IN, Qn) of the Logic Operation Blocks
applicable for sequence and CALCU, CALCU-C blocks store the following I/O connection
information:
• Information to identify the connection destination, such as tag name, user defined
label name, terminal number, and element number
• Information to identify the data item
• Information to indicate the condition specification
*1: ¡ £ Logic Operation Blocks are supported by CS 3000 only.
■ Condition Specification on the I/O Connection Information ¡ £

Using the I/O connection information and the input signal read from the input terminals, the
condition testing may be performed. When the input signals satisfy the conditions, 1 is set
to the calculated input value (RV). When the conditions are not satisfied, 0 is set to the
calculated input value (RV).
SEE ALSO
For the condition specification on the I/O connection information, see a chapter D3.3, “Logic Chart Block
(LC64).”
■ Input Processing for Calibration

Condition testing is performed to continue updating the calculated input values (RV, RVn).

<Toc> <Ind> <C4. Output Processing> C4-1
C4. Output Processing

This chapter explains the output processing common to Regulatory Control Blocks
and Calculation Blocks.
■ Output Processing
Output processing is a general term, representing that all function blocks, execute certain
process to the values obtained from the control computation before output it. There are
various forms of output processing corresponding to the function block type and the output
signal format. Some forms of output processing are common to Regulatory Control Blocks
and Calculation Blocks, while others are specific to certain particular blocks.
SEE ALSO
The output processing for the sequence control block is unique and differs from that of the Regulatory
Control Blocks or Calculation Blocks. For the sequence table block output processing details, see a
chapter D3.2, “Sequence Table Block (ST16, ST16E).”
For details on the output processing of the blocks connected in sequence connection, see a chapter
D3.3, “Logic Chart Block (LC64).”

■ Output Processing Common to Regulatory Control Block
In a Regulatory Control Block, the value obtained from control computation undergoes the
output processing, then outputs as the manipulated output variable (MV), as depicted in the
figure below.
AUT/CAS/RCAS/PRD
Preset manipulated output
AUT/CAS/RCAS/ROUT/PRD
SV MAN/ MH ML
TRK MAN TRK
Control Output Output

PV + velocity +
computation limiter
limiter MV
-
+
ROUT TRK
OUT
RMV MVrb Output signal
Readback value from conversion
output destination
Auxiliary
TIN output SUB
Output
module
C040001E.EPS
Figure Block Chart of Output Processing Common to Regulatory Control Block
TIP
In the Dual-Redundant Signal Selector Block (SS-DUAL) and Signal Selector Blocks (SS-H/M/L), the
value obtained by signal selection is output as a selected signal value (PV).

● Output Operation
▼ Control Calculation Output Type
A Regulatory Control Block outputs its manipulated output value (MV) or the vicissitude of
that value (MV).
There are two types output action: positional and velocity:
• In positional output action, the output value connects to its destinations unchanged.
• In velocity output action, the amount of change for the current output (MV) is added
to the value read back from the connection destination of the output terminal.
The output operation can be specified on the Function Block Detail Builder.
• Output action: Selectable from “positional” or “velocity.”
Default is the “positional” action.
SEE ALSO
See the explanations for the respective function blocks in D1, “Regulatory Control” for information on
setting output actions in Regulatory Control Blocks.
● Output Limiter
It limits the manipulated output value (MV) to be within the high and low limit values.
● Output Velocity Limiter

It limits the amount of change between the current and previous output values to avoid
output bumps.
● Output Clamp
It prevents the manipulated output value (MV) from being varied above or below the current
output value. This state is called output clamp. In the output clamp state, the data status of
the manipulated output value (MV) will be either the clamp high (CLP+) or clamp low (CLP-).
● Preset Manipulated Output

Upon an external command, the block is forced to operate in the manual mode and output
it’s manipulated output value (MV) at a predetermined value.
● Output Tracking
It forces the output value to match the value of its output destination or the value of the
tracking input signal.
● Output Range Tracking

It forces the scale high/low limits (MSH and MSL) of the manipulated output value (MV) to
match the scale high/low limits of its output destination. When a change occurs in the scale
high/low limits (MSH and MSL) of the manipulated output value (MV), it recalculates the
values of the data related to the manipulated output value (MV).

● Manipulated Output Index
This function displays two indexes in the manipulated output value (MV) scale in the HIS
operation monitoring screen of operation and monitoring function. They are called manipu-
lated output indexes.
These indexes are set to indicate the feasible limits of the manipulated output values (MV).
They can be used as manipulation reference when operation in the manual mode, and they
can be used to verify the normal conditions when operation in the automatic mode. The
manipulated output indexes are available only in the Regulatory Control Blocks.
● Output Signal Conversion

The function converts the result of calculation process into a signal that is compatible with
the output destination, such as the output module or other function blocks.
Various types of output signal conversion are available for different types of function block
and output signal. There are also types of output signal conversion that are common to the
Regulatory Control Blocks, as well as those specific to individual function blocks.
● Auxiliary Output
The manipulated output value (MV), change in manipulated output (MV), process variable
(PV), or change in process variable (PV) is output to final control elements such as
compensation control equipment or external indicator of control stations.
● Output Processing in Unusual Cases

When in unusual cases, the Regulatory Control Blocks process the output different from in
usual cases.
● Output Processing Specific to the Motor Control Blocks (MC-2 and MC-3)
The Motor Control Blocks (MC-2 and MC-3) execute a special output processing, which is
different from other function blocks.
SEE ALSO
For more information about output processing of MC-2 and MC-3, see a chapter D1.17.3, “Output
Processing of Motor Control Blocks (MC-2 and MC-3).”
● Output Processing for the Blocks with Sequence Connection

The Pulse Count Input Block (PTC) may be connected in sequence connection, one of the
connection types. A special output processing for sequence connection with other blocks is
supported and referred as “status manipulation.”

■ Output Processing Common to All Calculation Blocks ¡ £
In a Calculation Block, the value obtained from calculation process undergoes the output
processing, then outputs as the calculated output value (CPV), as depicted in the figure
below.
Calculation OUT
CPV Output signal conversion
processing
Auxiliary output
SUB
C040002E.EPS
Figure Block Diagram of Output Processing Common to the Numerical, Analog and General-
Purpose Calculation Blocks
Output velocity OUT

limiter
C040003E.EPS
Figure Block Diagram of Output Processing Common to Data Set Blocks
Calculation OUT
processing
C040004E.EPS
Figure Block Diagram of Output Processing Common to the Logic Operation Blocks (*1) £
*1: ¡ £ Logic Operation Blocks are only available in CS 3000 System.

● Output Operation
▼ Control Calculation Output Type
A Calculation Block outputs the calculated output value (CPV) or the vicissitude of that
value (CPV).
There are two types output action: positional and velocity:
• In positional output action, the output value connects to its destinations unchanged.
• In velocity output action, the amount of change for the current output (CPV) is added
to the value read back from the connection destination of the output terminal.
The output operation can be specified on the Function Block Detail Builder.
The Calculation Blocks that can select positional output or velocity output action are Arith-
metic Calculation Blocks and Analog Calculation Blocks. Other Calculation Blocks are fixed
to the positional output action.
• Output action: Selectable from “positional” or “velocity.”
Default is the “positional” action.
● Output Velocity Limiter

It limits the amount of change between the current and previous output values to avoid
output bumps.
● Output Clamp
It prevents the manipulated output value (MV) from being varied above or below the current
output value. This state is called output clamp. In the output clamp state, the data status of
the manipulated output value (MV) will be either the clamp high (CLP+) or clamp low (CLP-).
● Output Tracking
It forces the output value to match the value of its output destination or the value of the
tracking input signal.
● Output Signal Conversion

The function converts the result of calculation process into a signal that is compatible with
the output destination, such as the output module or other function blocks.
Various types of output signal conversion are available for different types of function block
and output signal. There are also types of output signal conversion that are common to the
Calculation Blocks, as well as those specific to individual function blocks.

● Auxiliary Output
The calculated output value (CPV), or the change in calculated output (CPV) is output to
final control elements such as compensation control equipment and external indicator of
control stations.
● Output Processing in Unusual Cases

When in unusual cases, the Calculation Blocks process the output different from in usual
cases.
● CPV Pushback
In terminal connection, a function block obtains output value (CPV) by tracking to the
downstream function block at the IN terminal, and calculates the calculation input value
(RV) backward from the CPV to allow the upstream function block tracking.
● Output Processing for General-Purpose Calculation Blocks (CALCU and

CALCU-C) in Sequence Connection ¡ £
The General-Purpose Calculation Blocks (CALC, CALC-C) and Logic Operation Blocks
(*1) may be connected in sequence connection, one of the connection types. A special
output processing for sequence connection with other blocks is supported and referred as
“status manipulation.”
*1: ¡ £ Logic operation blocks are only available for CS 3000.
■ Output Processing Applicable to Each Model of Blocks

The different types of output processing may be applied to different models of function
blocks.
SEE ALSO
• For more information about output processing applicable to each model of regularly blocks, see a chapter
D1.1.3, “Input Processing, Output Processing, and Alarm Processing Possible for Each Regularly Control
Block.”
• For more information about output processing applicable to each model of calculation blocks, see a chap-
ter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation
Block.”

<Toc> <Ind> <C4.1 Output Limiter> C4-8
C4.1 Output Limiter

The output limiter limits the manipulated output value (MV) within the MV High/Low
limits (MH and ML) when running in Auto mode. An enhanced output limiter function
is provided as the extra function to the output limiter. This function may prevent the
output from abrupt action when the manipulated output value (MV) is operated in the
manual mode beyond the range of high or low limit, and then the operation mode is
switched from manual to auto.
The output limiter is only available for Regulatory Control Blocks.
■ Output Limiter
The output limiter limits the manipulated output value (MV) within the high (MH) and low
(ML) limit setpoints.
The limiter is functioning for the Regulatory Control Blocks operating in the automatic mode
(CAS, AUT, RCAS). But, it has no effect on 2-position ON/OFF type output, or 3-position
ON/OFF type output and Pulse width type output with no feedback.
When the manipulated output value (MV) reaches the limit set by the output limiter, the high
or low limit alarm is activated, and the data status of the manipulated output value (MV) will
be in the clamp high (CLP+) or clamp low (CLP-) respectively.
The high (MH) and low (ML) limit setpoints are set in the following setting parameters.
• High limit for manipulated output value (MH):
Data in an engineering unit and within the MV range.
The default is the ceiling of the MV scale.
• Low limit for manipulated output value (MH):
The default is the bottom of the MV scale.
TIP
• In the Control Signal Splitter Block (SPLIT), the MVn scale high limit is set in the manipulated output
high limit setpoint (MH) and the MVn scale low limit is set in the manipulated output low limit setpoint
(ML), for each output.
• In the 13-Zone Program Set Block (PG-L13), the output value always falls within the range between
the MV scale high (MSH) and low (MSL) limits.

■ High/Low Limit Expansion Function
When a Regulatory Control Block is in manual operation mode and a value exceeding the
manipulated output high and low limit setpoints is set from the operating and monitoring
function, a reconfirmation request message is displayed to caution the user. If the user
performs an acknowledgment operation at this time, a value exceeding the manipulated
output high and low limit setpoints can be set. The function block outputs the value set by
the user regardless of the manipulated output high and low limit setpoints (MH, ML).
If the manipulated output value (MV) that is set by manual operation exceeds the range as
determined by the manipulated output high and low limit setpoints, and if operation is
changed to an automatic mode (CAS, AUT, RCAS), the output limiter will force the manipu-
lated output value (MV) to change to the manipulated output upper limit setpoint (MH) or
the lower limit setpoint (ML) so that the manipulated output value (MV) undergoes an
abrupt change.
The high/low limit expansion function temporarily expands the manipulated output high and
low limit setpoints (MH, ML) in order to avoid such abrupt change in the manipulated output
value (MV) caused by the output limiter.
● When MV is Set in the Manual Mode

The High/Low-limit Expansion function is activated when the manipulated output value
(MV) is manually set over the high-limit (MH) or under the low-limit (ML) in manual mode.
• If the MV exceeds the MH setpoint, the value equal to that MV will be the temporarily
extended high limit setpoint (MHe) for the manipulated output.
• If the MV falls below the ML setpoint, the value equal to that MV will be the temporarily
extended low limit setpoint (MLe) for the manipulated output.

● When the Mode is Switched from Manual to Automatic
When the mode is changed from manual operation to automatic operation, the output
limiter operates using the manipulated output high limit setpoint (MHe) or the manipulated
output low limit setpoint (MLe) that has been temporarily expanded. Therefore, there will be
no abrupt change in the manipulated output value (MV).
• If the calculation process yields a value exceeding the current MHe value, then the
current MHe value will be output as the MV. Otherwise, the calculated result will be
output, and the MHe value will be replaced by the new MV value.
• If the calculation yields a value that falls below the current MLe value, then the current
MLe value will be output as the MV. Otherwise, the calculated result will be output, and
the MLe value will be replaced by the new MV value.
The following figure shows the operation of the High/Low-limit Expansion function:
MV
MV Unlimited MV
MH
The ramp up output is limited.
ML
Time
Mode
AUT MAN AUT
Alarm
NR MHI NR
C040101E.EPS
Figure Operation of High/Low-Limit Expansion Function
● Return to Normal Operation

When the manipulated output value (MV) finally returns within the high limit (MH) and low
limit (ML) setpoints, the output limiter returns to normal operation.

<Toc> <Ind> <C4.2 Output Velocity Limiter> C4-11
C4.2 Output Velocity Limiter

It is a function to limit the amount of change between the previous and current
output values, so as to prevent abrupt changes in the output value.
■ Output Velocity Limiter

▼ Output Change, Output Velocity Limiter, MAN Mode Output Velocity Limiter Bypass
The output velocity limiter limits the amount of change in the output value according to the
output velocity limit setting. The output velocity limit is a permissible amount of output
change over one scan period.
In the manual operation mode, the operation and monitoring window will display the ma-
nipulated output value (MV) as set manually, even if the output velocity limiter has acted to
limit the manipulated output value (MV). The output velocity limiter can be disabled by
setting the bypass for the MAN-mode output velocity limiter.
Also, the limiter will not function when the output signal is 2-position ON/OFF or 3-position
ON/OFF output, or when the block is in the tracking (TRK) mode.
In the PID Controller Block with Batch Switch (PID-BSW), the output velocity limiter does
not operate during the time the manipulated output value (MV) is at the manipulated output
high limit value or low limit value because the control deviation value has exceeded the
deviation alarm setpoint and lockup setpoint.
The output velocity limiter does not function in Time-Proportioning ON/OFF Controller
Block regardless the setting for MAN Mode Output Velocity Limiter Bypass.
The output velocity limiter and the bypass for MAN-mode output velocity limiter may be
defined on the Function Block Detail Builder.
• Output Velocity Limiter:
Engineering unit data or percentage within the range from 0 to the MV scale span
setting in positive values only (six significant figures).
The default setting is 100.0 %.
• MAN Mode Output Velocity Limiter Bypass:
Selectable between “Yes” and “No.”
Default is “No.”

<Toc> <Ind> <C4.3 Output Clamp> C4-12
C4.3 Output Clamp

Output clamp is a function applied to cascade-connected output terminals. It pre-
vents the manipulated output value (MV) from exceeding, or falling below the current
value, when the data status of manipulated output value (MV) is in the high-limit
(CLP+), or low-limit (CLP-) clamped state.
■ Output Clamp
The output clamp function indicates the status that the manipulated output value (MV) is
restrained at the limits of a specified range.
The output clamp function operates only when the output terminal is connected in cascade.
The data status CLP+ or CLP- is initiated by one of the following conditions:
• When the output value is limited by the output limiter.
• When the data status of cascade-connected destination is CLP+ or CLP-.
Each of these conditions is explained further in the following paragraph.
● When the Output Value is Limited by the Output Limiter

If the output is limited within the range of high-limit (MH) and low-limit (ML) setpoints of the
manipulated output value, then the data status of the function block will be CLP+ or CLP-.
The CL+ and CL- have a 2 % (initial value) hysteresis. For example, if the low-limit setpoint
is 0 %, and the manipulated output falls to 0 % and activates the output limiter. Then the
data status of the manipulated output value (MV) become CLP-. Later, when the manipu-
lated output increases from 0 % and the output limiter is no longer activated, the data
status CLP- will continue until the manipulated output value (MV) exceeds 2 %.
● When the Data Status of Cascade-connected Destination Become CLP+ or

CLP-
If the output terminal is cascade-connected to a function block whose cascade set value
(CSV) is in the status of CLP+ or CLP-, or if the data status of data item connected to the IN
terminal of the connection destination at the terminal connection is CLP+ or CLP-, then the
data status of manipulated output value at the connection source will also be CLP+ or CLP-.

■ Operation of Output Clamp
▼ Limit Output in Direction when Clamped
When the data status of the cascade connection destination is CLP+ or CLP-, the output
direction of the manipulated output value (MV) is restricted, i.e., the value cannot be
changed to exceed or falls below the present output value, so that only the manipulated
output value (MV) in the direction that cancels CLP+ or CLP- is output.
The restriction of the direction of changes in clamped output can be set with the Function
• Limit output in direction when clamped:
Selectable from “Yes” and “No.”
Default is “Yes.”
■ Release the Output Clamp

The output clamp will be released under the following conditions:
• When the block mode is switched to the manual (MAN), remote output (ROUT),
tracking (TRK) or primary direct mode (PRD).
• When the output connection destination is changed through a switch, etc.

■ Tracking of the Output Clamp Status
The data status CLP+ or CLP- of the manipulated output value (MV) will be copied to the
data status of the setpoint (SV, CSV and RSV) and of the remote manipulated output value
(RMV). This action is called the tracking of the output clamp status. The tracking function
transmits the output clamp status of a downstream function block to an upstream function
block.
If, however, the “limit output in direction when clamped” is disabled in the upstream block,
the downstream output status will not be transmitted to the upstream.
Output value may be set as desired.

MAN
Output clamp state

CAS
CSV Output high/low limiting
Legends
CAS
MAN Function block
Block mode
If a high-end limiting occurs in the downstream block due to a reverse action, the CSV will only be
allowed to ramp down.
C040301E.EPS
Figure An Example of Typical Clamping
■ Output Clamp when the High/Low Limit Expansion Function is in Effect

Note When the output High/Low-limit Expansion function is in effect, the manipulated
output value (MV) is not limited by the high-limit (MH) or the low-limit (ML) setpoints.
Whenever MVMH or MVML, the manipulated output value (MV) data status is set as
CLP+ or CLP- even if the manipulated output value (MV) is not limited by the high/low limit
expansion function.

■ An Example of Output Clamp
The following figures illustrate examples of output clamp:
● An Example of Function Blocks Connected in Parallel in Downstream

Even in a case in which multiple function blocks are connected downstream via the Cas-
cade Signal Distributor Block (FOUT), the output clamp status of the downstream function
block output is transmitted to the upstream function block via the FOUT block.
PID Output clamp state

Output
high/low limit
AUT
Output
FOUT high/low limit
CAS
CAS CAS CAS
Output clamp state

C040302E.EPS
Figure When Downstream Function Blocks are Connected in Parallel
● When Connecting to IN Terminal of a Ratio Set Block (RATIO)

When RATIO block is connected downstream in a loop, the output clamp status of the
RATIO block is transmitted to the upstream function block connected to its SET terminal.
The clamp status is not transmitted via IN terminal even though the connection to the IN
terminal is the terminal connection type.
Output clamp state
AUT
IN OUT
Not output
clamp state RATIO
Output
IN high/low limit
AUT CAS
IN OUT
Output clamp state
C040303E.EPS
Figure An Example of Connecting to the Input Terminal of a Ratio Set Block (RATIO)

● When Connecting to an Auto Selector Block (AS-H/M/L)
When an AS-H/M/L block is connected downstream and the AS-H/M/L block signal selector
switch position is 4 (auto selection), the output clamp status of the AS-H/M/L block is
transmitted to all upstream function blocks. When the signal selector switch position is 1, 2,
or 3, the output clamp status is transmitted only to the upstream function block that is
selected by the signal selector switch.
Output clamp state

Output
PID PID clamp state
Output
clamp state
AUT AUT
AS AS
Output
IN1 IN1
AUT AUT high/low limit
IN2 Output IN2
PID
Automatic high/low IN1 is
selection limit selected
AUT AUT
Output
clamp state
C040304E.EPS
Figure An Example of Connecting with Auto Selector Block (AS)
● When Connecting to a Switch Block (SW-33, SW-91)

When connected to a downstream function block via the SW-33 or SW-91 block, the output
clamp status of the downstream function block is not transmitted upstream when the switch
is OFF. It is transmitted when the switch is ON.
PID PID
AUT AUT
SW-33 SW-33
Output Output
clamp state MLD-SW clamp state MLD-SW
AUT AUT
Output Output
high/low limit high/low limit
C040305E.EPS
Figure An Example of Connecting with a Switch Block (SW-33)

■ Precautions When Connecting a Manual Loader Block with Auto/Man
SW (MLD-SW) in the Downstream of Cascade Loop
If a Manual Loader Block with Auto/Man SW (MLD-SW) is placed downstream in a cas-
cade-connected control loop, the control block connected upstream must have the “limit
output in direction when clamped” function turned off.
The following paragraph explains how to connect a MLD-SW block in the downstream of a
cascade loop.
● An Example of Connecting a Manual Loader Block with Auto/Man SW

(MLD-SW) in the Downstream of a Cascade loop
Assume the MLD-SW gain (GAIN) is 1, bias (BIAS) is 0, the low-limit alarm setpoint is 0 %,
and hysteresis for manipulated output alarm is 2 %, in the loop shown below.
PID
AUT
Output
clamp state MLD-SW
AUT
Output
high/low limit
C040306E.EPS
Figure An Example of Turning Off the Limit Output in Direction when Clamped

● Action of the “Limit Output in Direction when Clamped”
When the block status of the PID and MLD-SW blocks are AUT, set the manipulated output
value (MV) of a PID block to 0 % then the MLD-SW manipulated output (MV) become 0 %,
clamped at the low limit, thus turns the data status of the manipulated output value (MV) to
CLP-. This will also cause the PID block data status of the manipulated output value (MV)
to CLP-, and restricts the PID manipulated output value (MV) changes on the clamped
output direction. The restriction on the PID block will continue until a change in the PID
output causes the manipulated output value (MV) of the MLD-SW to exceed 2 %, thus
releasing the CLP-data status of the manipulated output value (MV).
● Precautions on “Limit Output in Direction when Clamped”

When changes on the direction of clamped output is restricted, the PID block output can
not decrease to 0 % once it increased to 1.9 % under CPL- status. The MLD-SW is re-
stricted on moving to the clamped direction kept it at 1.9 %. In other words, though a valve
requires full close when the manipulated output value (MV) becomes 0 %, the valve is not
fully closed in this case.
Turn off the “limit output in direction when clamped” at the upstream control block can avoid
this state.

<Toc> <Ind> <C4.4 Preset Manipulated Output> C4-19
C4.4 Preset Manipulated Output

The preset manipulated output is a function that, through an external command,
forces a block to the manual mode (MAN) and output a preset value as the manipu-
lated output value (MV).
The preset manipulated output function is available only for Regulatory Control
Blocks.
■ Preset Manipulated Output

The preset manipulated output is a function that, through an external command, forces a
block to the manual mode (MAN) and output a preset value as the manipulated output
value (MV).
The command for the preset manipulated output is generated only upon switching the
preset MV switch (PSW) from 0 to 1, 2 or 3. The value of the preset MV switch (PSW) will
determine the manipulated output value (MV) as follows:
• PSW = 1: MV = MSL (the low limit of MV scale)
• PSW = 2: MV = MSH (the high limit of MV scale)
• PSW = 3: MV = PMV (the preset manipulated-output value)
The preset manipulated output value (PMV) is a value set as a tuning parameter from the
operation and monitoring function, or from the General-Purpose Calculation Blocks.

<Toc> <Ind> <C4.4 Preset Manipulated Output> C4-20
■ Reset the Preset MV Switch
• The preset MV switch (PSW) value will be automatically reset to 0 when the preset
manipulated output function is activated to set the manipulated output (MV) at a preset
value. The block mode will remain manual (MAN), can not trace back the mode and
value prior to the activation of preset manipulated output function.
• If the value of the preset MV switch (PSW) is set at 1 or 2, the output velocity limiter
will not take effect on the preset manipulated output.
• If the value of the preset MV switch (PSW) is set at 3, and if MAN mode output velocity
limiter bypass is set to off, the output velocity limiter will restrict the velocity when the
MV tries to jump to the preset value.
IMPORTANT
Since the preset MV switch (PSW) is automatically reset to 0, the PSW0 state can not be
referred by other function blocks. For example, the Sequence Table Blocks (ST16, ST16E)
can not refer it as a condition for sequence control.
■ Set Parameters for the Preset Manipulated Output Function

The set parameters for the preset manipulated output function is shown below:
• Preset manipulated output value (PMV):
Default is the low limit of the MV scale.
• Preset MV switch (PSW):
Selectable among “0,” “1,” “2,” “3.”
Default is “0.”

<Toc> <Ind> <C4.5 Output Tracking> C4-21
C4.5 Output Tracking

The output tracking is a function that forces the output value to match the value of
the output destination or the value of the tracking-input signal.
■ Output Tracking
▼ Output Value Tracking
The output tracking behaves different between the Regulatory Control Blocks and Calcula-
tion Blocks.
• For the Regulatory Control Blocks, the manipulated output value (MV) is forced to
match the value of the external tracking signal (TIN) or output destination.
• In the Calculation Blocks, the calculated output value (CPV) is forced to match the
value of the output destination when the data status of the destination block is condi-
tional (CND).
■ Output Tracking in the Regulatory Control Block

The output tracking in the Regulatory Control Blocks is a function that forces the manipu-
lated output value (MV) to match the value of the external tracking-input signal (TIN) or
output destination.
However, when the tracking input signal (TIN) or the value of the output terminal connec-
tion destination falls outside the range of the manipulated output value (MV) scale, the
manipulated output value (MV) is restricted to the MV scale low limit value (MSL) or MV
scale high limit value (MSH).
In the Cascade Signal Distributor Block (FOUT), when each output point becomes cascade
open, the manipulated output value (MV) is made to conform to the output destination data.
The output tracking in the Regulatory Control Block functions under the following condi-
tions:
• In the tracking mode (TRK).
• In the initialization manual mode (IMAN)
• In a condition other than initialization manual mode where the initialization process is
required (IMAN state).
The output tracking for Manual Loader Blocks (MLD, MLD-PVI and MLD-SW) can be set
with the Function Block Detail Builder.
• Output Value Tracking: Selectable from “Yes” and “No.”
TIP
For Regulatory Control Blocks with a remote manipulated output value (RMV), the remote manipulated
value (RMV) data is made to conform to the manipulated output value (MV) when the block mode is other
than remote output (ROUT) or service off (O/S).

■ Output Tracking of Calculation Blocks
The output tracking of the Calculation Blocks is a function that forces the calculated output
value to match the value of the connected destination.
Even if calibration (CAL) is set as the data status of the calculated output value (CPV), the
output tracking have a priority over it. The output tracking of the Calculation Blocks will
operate when the data status of the output destination block status becomes conditional
(CND). The conditional (CND) status are as follows:
• When the cascade connection is disconnected.
• When the downstream function block begins the operation in non-cascade mode.
The output tracking can be defined on the Function Block Detail Builder.
• Output Value Tracking: Selectable from “Yes” or “No.”
Additionally, if the output tracking is set to “No,” and when the status of the output destina-
tion becomes CND, the previously calculated output value (CPV) will be held.

■ Output Tracking in the Tracking Mode
The Regulatory Control Blocks where the tracking (TRK) mode is valid are provided with
the tracking switch (TSW). When the tracking switch (TSW) is turned to “ON,” the Regula-
tory Control Blocks operate in the tracking (TRK) mode.
If a function block operates in the tracking (TSK) mode, the output tracking is activated and
allows the external tracking-input signal (TIN) to be its manipulated output value (MV). In
this case, no output limiter and output velocity limiter functions on the tracking-input signal
terminal (TIN).
Tracking switch (TSW) may be set either directly by an external data set action or by data
reference through the tracking-switch input terminal (TSI).
● Occurrence of Data Errors in the Tracking Mode

When a data error (BAD) occurs, from either the tracking-input signal terminal (TIN) or
tracking-switch input terminal (TSI), an output open (OOP) alarm will be issued. Since the
initialization manual condition is established at this time, the active mode switches from the
tracking (TRK) mode to initialization manual (IMAN) mode. When the function block oper-
ates in the initialization manual mode (IMAN), the output tracking is activated to match the
manipulated output value (MV) to the value of the output destination. For the Regulatory
Control Blocks whose MV is pulse width output signal, the tracking (TRK) mode will prevail,
and the previous manipulated output value (MV) will be held when above error occurs.
If the block is not in tracking (TRK) mode, the occurrence of a data error (BAD) in the signal
at the tracking-input signal terminal (TIN) or tracking-switch input terminal (TSI) does not
invoke an alarm nor change the active mode. Control will continue regardless the occur-
rence of data error.
● Pulse Width Output

When a Regulatory Control Block is defined to give pulse width output, the tracking switch
terminal (TSI) is connected to the Remote/Local Digital Input signal and the tracking input
terminal (TIN) is connected to the Valve opening feedback signal.

■ Output Tracking in the Initialization Manual Mode
When multiple Regulatory Control Blocks are in cascade connection, the manipulated
output value (MV) of the upstream control loop is used as the setpoint value (SV) for
downstream loop. If the cascade connection opens, the upstream loop enters to the initial-
ization manual (IMAN) mode.
When a function block is in the initialization manual mode (IMAN), the output tracking
function force its manipulated output value (MV) to match the value of the output destina-
tion.
In the case that the cascade connection is established via a selector switch, when the
selector switch opens the cascade connection, the upstream loop changes to the initializing
manual (IMAN) mode, when the connection restores, it tracks its MV to the destination only
once. When the switch closes the cascade connection again, the downstream loop SV will
change to bumpless cascade set value.
When the initialization manual mode is invoked from the tracking (TRK) mode, the initializa-
tion manual mode prevails.
■ Output Tracking in the IMAN Mode

In the mode other than the initialization manual mode, a situation calling for the initializing
process is referred as IMAN status. A function block under the following circumstances is
referred as in the IMAN status:
• When initialization manual condition established in a function block that has no initial-
ization manual (IMAN) mode.
• When the mode of a block returns from off-service (O/S) mode to manual (MAN),
automatic (AUT) or cascade (CAS) mode.
• On the first scan after returning from the initialization manual mode to the non-initial-
ization manual mode.
As the function block operates in the IMAN state, the output tracking is activated to match
the manipulated output value (MV) to the value of the connection destination.

<Toc> <Ind> <C4.6 Output Range Tracking> C4-25
C4.6 Output Range Tracking

Output range tracking is a function that forces the scale High/Low limits of the
manipulated output value (MV) to match those of the output destination, and the
values of data items related to the manipulated output value (MV) are recalculated
whenever there is a change in the scale High/Low limits.
■ Output Range Tracking

In a Regulatory Control Block, data are processed as engineering unit data. For this rea-
son, whenever the manipulated output value (MV) of an upstream function block is used as
the setpoint value (SV) of the downstream function block in a cascade connection, the
scale High/Low limits of the both blocks must be identical. The output range tracking
function matches these ranges automatically. Output range tracking function will force the
scale High/Low-limit setpoints of the manipulated output value (MV) to match those of the
output destination, and recalculates the values of the data items related to the manipulated
output value (MV) whenever there is a change in the scale High/Low limits.
Output range tracking operates only when the OUT terminal of an upstream Regulatory
Control Block is connected to the SET terminal of a downstream Regulatory Control Block.
The following figure shows an example of connection in cascade where output range
tracking works.
PID
MSH
OUT
MSL
SET
PID CSV
Data value
SH
Output range tracking SL
C040601E.EPS
Figure Output Range Tracking
For instance, if the output terminal’s connected destination is a PID controller block (PID)
with the PV range of 0 to 1500 m3/h, the range of manipulated output values (MV) will also
be 0 to 1500 m3/h.
If the output destination is a process output, the range will be 0.0 to 100.00 % regardless of
the output signal format. For instance, if the output destination is the analog output module,
the manipulated output value (MV) will be 0.0 to 100.0 %.

■ Recalculation
The manipulated output value (MV)’s scale High/Low limits are applied to the following data
items related to the manipulated output value (MV).
• Remote manipulated output value (RMV)
• Preset manipulated output value (PMV)
• Output High/Low limit indexes (OPHI and OPLO)
• Reset signal value (RLV1 and RLV2)
• Manipulated output High/Low limit setpoint values (MH and ML)
These data will be recalculated with the manipulated output value (MV) whenever there is a
change in the MV scale High/Low limits. The formula for recalculation is:
MSH.n-MSL.n
DATA.n = • (DATA.o-MSL.o)+MSL.n
MSH.o-MSL.o C040602E.EPS
DATA.o: Target data before change

MSH.o: High limit of MV scale before change
MSL.o: Low limit of MV scale before change
DATA.n: Target data after change
MSH.n: High limit of MV scale after change
MSL.n: Low limit of MV scale after change

IMPORTANT
• In changing the output destination of the manipulated output value by means of switch
blocks, etc., make sure that the downstream block does not have a conflict output.
The engineering unit must be identical. If the range discrepancy exist, using Cascade
Signal Distributor Block (FOUT) or Control Signal Splitter Block (SPLIT) is required.
• The output velocity limiter value is not automatically recalculated, even if there is a
change in the MV scale High/Low limits. Use a Control Signal Splitter Block (SPLIT)
for switching, if the destination of the manipulated output applied with velocity limiter in
effect. Thus, the recalculation for output velocity limit is unnecessary.
• If a function block without output range tracking function, such as a Calculation Block,
is placed in the middle of a cascade connection, it is necessary to set the MV scale
High and Low limits for the upper stream regulatory control blocks. The MV scale
High/Low limits can be defined on the Function Block Detail Builder.
PID LAG
MSH
OUT IN OUT
MSL
SET
PID CSV
Data value
SH
SL
Output range tracking
C040603E.EPS
Figure A Cascade Connection via a Calculation Block
• If multiple controllers are connected in parallel in the downstream of a cascade control

loop, use a Cascade Signal Distributor Block (FOUT). Without using FOUT block
multiple downstream control blocks cannot be chained by terminal connection.

<Toc> <Ind> <C4.7 Manipulated Output Index> C4-28
C4.7 Manipulated Output Index

This function displays indexes that show the permissible range of the manually
manipulated values at the normal operation. The manipulated output index is only
available for Regulatory Control Blocks.
■ Manipulated Output Index

▼ Index
This function displays two indexes in the manipulated output value (MV) scale on the
operation monitoring window of the operation and monitoring function. These are called the
manipulated output indexes.
By setting these indexes at the operable limits of the manipulated output values (MV), they
can be used as manipulation guides in the manual mode, or as guides for verifying normal
status in the automatic mode.
For a Regulatory Control Block with manipulated output value (MV), both the high output
limit (OPHI) and low output limit (OPLO) indexes can be set on the tuning window. These
limits are displayed in the operation and monitoring window of the operation and monitoring
function.
The indexes may be defined on the Function Block Detail Builder.

• Set Indexes: Selectable from “Yes” and “No.”
■ Setting Parameters of Manipulated Output Index

The following items are the parameters of the manipulated output index:
• High output limit index: In an engineering unit within MV scale range.
Default is the high limit of the MV scale.
• Low output limit index: In an engineering unit within MV scale range.
Default is the low limit of the MV scale.
FIC100
MAN
NR
OPN 100.0
High output limit index
Low output limit index
CLS 0.0
Prohibit
C040701E.EPS
Figure Example of Manipulated Output Index Display

<Toc> <Ind> <C4.8 Output Signal Conversion> C4-29
C4.8 Output Signal Conversion

This process converts the result of calculation process into an output format for the
output modules or other function blocks.
■ Output Signal Conversion

▼ Output Signal Conversion
The output signal conversion may be used for the processes that are common to the
Regulatory Control Blocks and the Calculation Blocks, and for the specific function blocks
which have specific output process function.
SEE ALSO
See chapter C4.8.1, “No-Conversion Output” through C4.8.4, “Output Signal Conversion of Logic
Operation Blocks” for details on each type of the output signal conversion processes.
■ Output Signal Conversion Process Common to Regulatory Control

Blocks
Here is the outline of the output signal conversion processes that are common to the
Regulatory Control Blocks:
● No-Conversion Output
The manipulated output value (MV) resulted from the control-calculation process is No-
Conversion output.
● Pulse Width Output Conversion

The changes of manipulated output value (MV) is output after converted into a pulse
width signal.
● Communication Output Conversion

The manipulated output value (MV) resulted from the control-calculation process is con-
verted into the format compatible with the destination subsystem.
■ Output Signal Conversion Process Common to Calculation Blocks

¡£
Here is the outline of the output conversion processes that are common to the Calculation
Blocks:
● No-Conversion Outputs
The calculated output value (CPV) resulted from the control-calculation process is no-
conversion output.
● Communication Output Conversion

The calculated output value (CPV) resulted from the control-calculation process is con-
verted into the format compatible with the destination subsystem.
● Output Signal Conversion of the Logic Operation Blocks £

The output is unconverted.
■ Output Signal Conversion Processes for Specific Function Blocks
Here are the outlines of the conversion processes for different types of specific function
blocks:
● Output Signal Conversion of the Motor Control Blocks (MC-2 and MC-3)
One of the following types of output may be specified:
2-position status output; 2-position pulsive output; 3-position status output or 3-position
pulsive output.
• 2-position status output
The process switches one contact point ON or OFF according to the manipulated
output value (MV).
• 3-position status output
The process switches two contact points ON or OFF according to the manipulated
output value (MV).
• 2-position pulsive output
The process switches one of the two contacts ON for one second according to the
manipulated output value (MV).
• 3-position pulsive output
The process switches one of the three contacts ON for one second according to the
SEE ALSO
For more information about output processing specific to MC-2, MC-3 blocks, see a chapter D1.17.3,
“Output Processing of Motor Control Blocks (MC-2 and MC-3).”
● Output Signal Conversion of the Two-Position ON/OFF Controller Block

(ON/OFF)
The Two-position status output is used.
SEE ALSO
For more information about output processing specific to ONOFF block, see a chapter D1.8.2, “Two-
Position ON/OFF Controller Block (ONOFF).”
● Output Signal Conversion of the Three-Position ON/OFF Controller Block

(ON/OFF-G)
The Three-position status output is used.
SEE ALSO
For more information about output processing specific to ONOFF-G block, see a chapter D1.9.2, “Three-
Position ON/OFF Controller Block (ONOFF-G).”

● Output Signal Conversion, of the Time-Proportioning ON/OFF Controller
Block (PID-TP)
This is applied for a time-proportioning ON/OFF output. Time-proportioning ON/OFF is a
type of status output which set the contact output to ON via digital output module in propor-
tional to the manipulated output value (MV) ON/OFF cycle.
SEE ALSO
For more information about output processing specific to PID-TP block, see a chapter D1.10, “Time-
Proportioning ON/OFF Controller Block (PID-TP).”
● Output Signal Conversion of Flow/Weight-Totalizing Batch Set Block

(BESTU-2 and BESTU-3)
The 2-position or 3-position status output is used.
SEE ALSO
For more information about output processing specific to BSETU-2, BSETU-3 blocks, see a chapter
D1.20.3, “Output Processing of Totalizing Batch Set Blocks (BSETU-2, BSETU-3).”
● Output Signal Conversion of the Pulse Count Input Block (PTC)

A specific output process is used in the PTC block when it is connected to sequence
blocks.
SEE ALSO
For more information about output processing specific to PTC block, see a chapter D1.32, “Pulse Count
Input Block (PTC).”

C4.8.1 No-Conversion
The No-Conversion output is the data resulted from control computation process
and given as output without signal conversion process.
This can be used in the Regulatory Control Blocks and Calculation Blocks. Regula-
tory Control Blocks and Calculation Blocks behave differently when they are defined
to use the No-Conversion output.
Here describes the behaviors of the function blocks that are defined to use No-
Conversion output:
■ No-Conversion in the Regulatory Control Block

The No-Conversion output is to be connected to another function block or an analog output
module.
Here explains the both cases.
● Output to Another Function Block

The data output is carried out by data set to the other function blocks or by terminal con-
nection to the other function blocks.
• Output by data set
The manipulated output value (MV) is given from the OUT terminal can be used for
data set, as well as the process variable (PV) from the OUT terminal of the input
indicator block (PVI) or the input indicator block with deviation alarm (PVI-DV). The
manipulated output value (MV) and process variable (PV) are no-conversion outputs,
and in forms of engineering unit.
• Output by terminal connection
The manipulated output value (MV) is set in the cascade setpoint value (CSV) of the
connection destination function block via the SET terminal of the connection destina-
tion function block and the OUT terminal.
When an inter-terminal connection is possible at the IN terminal of the connection
destination function block, the manipulated output value (MV) can be passed to the
process variable (PV) or calculated input value (RV) of the connection destination
function block via the IN terminal of the connection destination function block and the
OUT terminal.
● Output to the Analog Output Module

When connect the output to the analog output module, the tight-shut and full-open func-
tions are automatically added to the manipulated output value (MV). The direction of analog
output can also be defined.
Output to a analog output module is in term of data set output.
Manipulated output value (MV) of 0 to 100 % is given from the OUT terminal.
The analog output module converts the 0 to 100 % the manipulated output value (MV) data
into a 4 to 20 mA (or 1 to 5 V) output to drive a final control element, such as a control
valve.

● Tight-Shut Function and Full-Open Function
The Tight-shut function fully close an operation valve and the Full-open function fully open
it when a manipulated output value (MV) is 0% or 100 %. With these functions, an actual
tight-shut output value (Ms) is set to a value less than 0% or greater than 100%, fully
closing an operation valve. And an actual full-open output value (Mf) is set to a value less
than 0% or greater than 100%, fully opening the valve.
These functions are added to the Regulatory Control Blocks with a MV and the MAN mode
to manually operate the MV, excluding the PG-L13 13-Zone Program Set Block. When you
set “No” to “Tight-shut/full-open Specifications” on the Function Block Detail Builder, these
functions are not added. When data is output to a function block of fieldbus device, set
“No.”
The following figure illustrates the tight-shut function:
Actual
output
Mf
100 %
0% 100 %
MV
Ms
C040801E.EPS
Figure Tight-Shut Function
Define the Tight-shut/full-open specifications, Ms and Mf on the Function Block Detail

Builder.
• Tight-shut/full-open Specifications:
Choose “Yes” or “No.”
The default setting is “Yes.”
• Output Value for tight-shut (Ms):
The actual output value for tight-shut
Setting range is -17.19 to 117.19 % (5 significant figures).
Default is -17.19 % for direct output setting, and -6.25 % for reverse output setting.
• Output Value for full-open (Mf):
The actual output value for full-open
Setting range is -17.19 to 117.19 % (5 significant figures).
Default is 106.25 % for direct output setting, and 117.19 % for reverse output setting.

● Analog Output Direction
The analog output module outputs 4 to 20 mA (or 1 to 5 V) against the 0 to 100 % range of
manipulated output values (MV). However, it can also output in the reverse direction,
e.g.20 to 4 mA (or 5 to 1 V). The following figure shows the relationship between the ma-
nipulated output value (MV) and output current. The reverse settings are shown in a dotted
line.
(mA DC) : Positive

direction
20
: Negative
direction
Output
current
50 100 (%)
MV
C040802E.EPS
Figure Relationship between the Manipulated Output Value and Output Current

■ No-Conversion in the Calculation Block
When the No-Conversion output is specified, the connection destination will be another
function block or an analog output module.
Its use in different cases is explained below:
● Output to Another Function Block

The output is given unconverted to another function block either by data set or terminal
connection.
The calculated output value (CPV) or the change in calculated output value (CPV) is no-
conversion output from the SUB terminal by data set.
● Output to an Analog Output Module

Calculation output value (CPV) is converted to 0 to 100 % on the CPV scale and output
through the OUT or SUB terminal. The range of the output, converted in terms of 0 to 100
% will be limited to 0 to 100 %.
Output terminals other than OUT and SUB give the output value (CPVn) unconverted,
regardless of the destination type.

C4.8.2 Pulse Width Output Conversion

This conversion method converts the changes in manipulated output value (MV)
into a pulse width signal. It is used for the contact output module to open and close
the motor-operated valve through the contacts.
The conversion to pulse width output is available only in the Regulatory Control
Blocks.
■ Pulse Width Output Conversion

In this conversion method, the changes in manipulated variable (MV) are converted into a
pulse width signal. The degree of opening for the motor-operated valve can be manipulated
by outputting this pulse width signal from the contact output module as two contact outputs
(UP, DOWN) corresponding to the sign of the manipulated variable (MV).
Furthermore, the displayed manipulated output value (MV) for the pulse width output
conversion and the output action for increasing or decreasing the manipulated output value
are different depending on the feedback input signal availability.
Table Regulatory Control Blocks where Pulse width Output Conversion is Available
With feedback Without

Type of regulatory control block
input feedback input
PID Controller Block (PID)
Sampling PI Controller Block (PI-HLD)
PID Controller Block with Batch Switch (PID-BSW)
PD Controller Block with Manual Reset (PD-MR)
Blending PI Controller Block (PI-BLEND)
Self-Tuning PID Controller Block (PID-STC)
Ratio Set Block (RATIO)
Manual Loader Block (MLD, MLD-PVI and MLD-SW)
Feedforward Signal Summing Block (FFSUM)
Non-Interference Control Output Block (XCPL)
C040803E.EPS
: available
Blank: not available

● Computational Expression for Pulse Width
The pulse width of pulse signal is given by the following computational expression:
MV
Tout=Pf •
100 C040804E.EPS
Tout: Output pulse width (sec.)

Pf: Pulse width stroke value (sec.)
MV: Change in manipulated output (%)
The stroke of the pulse width is the pulse width in time that is required to operate the final
control element from full-closed to full-opened state. In the automatic operation, the output
pulse width can not be defined greater than the control period time.
The full stroke value is defined using the Function Block Detail Builder.
• Full stroke value: The setting range is 0.00 to 7200.00 (sec.).
Default is 0.00 sec.
● Minimum Output Width

The final control element may not move if the pulse width signal is below a specific value
because of the mechanical characteristics of the object. To prevent this happens, the
minimum output width is utilized that, when a pulse width smaller than the minimum output
width, this pulse is withheld to add to the next pulse, until the pulse width becomes wider
than the minimum output value. A pulse width of fractional value below the output resolution
(10 ms) will also be added to the next output.
The minimum pulse width is only valid in automatic operation.
The minimum pulse width is defined through the Function Block Detail Builder.
• The minimum pulse width: Setting range is 0.00 to 7200.00 (sec.).
● Backlash Compensation
When the output reverses from the previous direction, a compensation value is added to
the calculated output to compensate the backlash of the final control element.
The backlash compensation is set through the Function Block Detail Builder.
• Backlash compensation value: Setting range is 0.00 to 7200.00 (sec.).
● Resetting Pulse Width

If the pulse width reset switch (RSW) is turned ON from the sequence control block or
others, the pulse width signal being output is reset immediately. The pulse width reset
switch returns to OFF after resetting the pulse width signal.
In the case of automatic operation (AUT, CAS and RCAS), no pulse width signal will be
output until the next control period after reset the pulse width.

■ Output Contacts
The output contacts are the contacts that drive final control elements, such as an motor-
operated valve. There are two types of contacts: the first contact and the second contact.
The terminal number for the first contact is defined through the Function Block Detail
Builder. An odd terminal number in the digital output module should be assigned for the first
contact. The second contact is automatically assigned with the succeeding terminal num-
ber of the first contact number.
● The First Contact

The first contact is called “UP contact” and activated when the change in manipulated
output (MV) is a positive value. If the feedback input signal is defined to indicate the valve
opening, it increases when the UP contact is ON.
● The Second Contact

The second contact is called “DOWN contact” and is activated when the change in manipu-
lated output (MV) is a negative value. If the feedback input signal is defined to indicate the
valve opening, it decreases when the DOWN contact is ON.
■ Remote/Local Switch
The on-site operation panel compatible with the pulse-width output may have an operation
button for local control. If you wish to perform on-site operation, change the remote/local
switch on the on-site operation panel to local to stop output from the FCS, then output the
on-site operation button signal. When changing the switch between remote and local, the
Regulatory Control Block receives the remote/local switching contact signal in the tracking
switch input connection terminal (TSI). When this input turns ON, the tracking switch (TSW)
turns ON and the Regulatory Control Block is set to the tracking (TRK) mode.
The operation upon switching between the remote and local modes is explained below.
● Operation Upon Switching from Remote Mode to Local Mode

• The on-site operation is enabled.
• If the feedback input is provided, the feedback input value will be displayed as the
manipulated output value (MV). If no feedback defined, a 50 % (fixed) value is dis-
played as the manipulated output value (MV).
• Only the pulse width being output at the time the mode is switched continuous till the
pulse output completed.
• The block mode is switched to the tracking (TRK) mode.
● Operation Upon Switching from Local Mode to Remote Mode (Other Than
TRK Mode)
• The calculated output value of the Regulatory Control Block becomes valid.
• If the feedback input is provided, the calculated output value will be displayed as the
manipulated output value (MV) immediately after switching, and thereafter, the feed-
back input value will be displayed as the manipulated output value (MV).
• The pulse width signal being output at the time the mode is switched will be reset.

■ Feedback Input
The feedback input communicates to the Regulatory Control Block to notify the absolute
value of the manipulated output (MV), e.g. the opening of the valve connected as the final
control element.
The pulse width output is a “velocity-type” control output action, it outputs the change in
manipulated output (MV). The absolute value of the manipulated output (MV) is not
known.
The feedback signal from the final control element is connected to the tracking input signal
terminal (TIN) of the Regulatory Control Block.
The feedback signal is provided or not provided decide how the manipulated output value
(MV) display and how the manipulated output behaves to increase or decrease the output.
The pulse width output behavior is described in the following table:
Table Pulse width Output Operation
Item With feedback input Without feedback input
During UP pulse output:
Changes in +direction
AUT During DOWN pulse output:
Feedback input value
mode Changes in -direction
While pulse is stopped:
MV is held.
Remote
MV mode
display During UP pulse output:
During pulse output: Changes in +direction
MAN Manual set point value During DOWN pulse output:
mode While pulse is stopped: Changes in -direction
Feedback input value While pulse is stopped:
50 %
Local mode Feedback input value 50 %
Pulse equivalent to MV is output.
Pulse output status on Pulse equivalent to MV is However, when MV reaches 0 or 100 %, pulse
depressing INC/DEC key output continues to output until the INC/DEC operation
is ended.
C040805E.EPS

● An Example of Pulse Width Output Conversion Operation with Feedback
Signal
Output AUT LOCAL

Output Pulse width
limiter velocity output
MV OUT
limiter conversion
MAN REM
Regulatory Control Block TIN TSI
Process Digital output module

input/output section Analog Digital
input module input module
Terminal n Terminal n +1
Motor-operated
valve - remote/local
UP DOWN
Feedback
slide resistor Control output
C040806E.EPS
Figure Schematic Diagram for Pulse Width Output Signal with Feedback Input
During automatic operation, the feedback input value which indicates how far the valve is
open is displayed as the manipulated output value (MV).
When the manipulated output value (MV) from the operation and monitoring function is
changed during manual operation, the pulse width corresponding to the change is output.
The manipulated output value (MV) displays the manipulated output value (MV) set manu-
ally during pulse width output, and when output is complete it displays the feedback input
value.
The timing chart for manual operation is shown below:
Indication of
manipulated Manually set value for
output value (MV) manipulated output value
The value may be slightly off
100 % since the feedback input value
is displayed after the pulse
width output is complete.
MV
50 %
Feedback value
Feedback value
Feedback value
0% Time
Manual operation
using the keys ON
Time
ON
Pulse width output (UP)
Time
MV
TF • 100
TF: Full stroke value

C040807E.EPS
Figure Timing Chart for Manual Operation

■ An Example of Pulse Width Output Conversion Operation without
Feedback
AUT LOCAL
Output Pulse width
MV OUT
velocity output
MAN limiter conversion REM
Regulatory Control Block TSI
Contact Contact output module

input module
Terminal n Terminal n+1
Motor-operated
valve - remote/local
UP DOWN
Control output
C040808E.EPS
Figure Schematic Diagram of Pulse Width Output Signal Conversion without Feedback Input
The valve opening will not be displayed since there is no feedback signal.
The manipulated output value (MV) in the automatic operation is displayed by UP/DOWN
of the pulse width output.
When Up: manipulated output value (MV) increases.
When DOWN: manipulated output value (MV) decreases.
No output: manipulated output value (MV) stays unchanged.
The timing chart for manual operation is shown below:
100 % 100 %
Indication of manipulated Indication of manipulated
output value (MV) MV output value (MV)
50 % 50 %
Time Time
0% 0%
ON
Time ON Time
Manual operation Manual operation
using the keys using the keys
Time Time
Pulse width output Pulse width output
(UP) (DOWN)
MV TF • 0.5 Output is stopped beyond

TF • 100 this point on the instant the
manual operation is
terminated.
(a) When moving 50% or less of the full span (b) When moving 50% or above of the full span
C040809E.EPS
Figure Timing Chart for Manual Operation

C4.8.3 Communication Output Conversion

The communication output conversion converts the data resulted from control
computation into a format that can be output to the destination subsystem.
This conversion method is available for the Regulatory Control Blocks and Calcula-
tion Blocks. It behaves differently for Regulatory Control Block and Calculation
Block.
■ Communication Output Conversion

The data value to be converted to the communication output will be the calculated output
value (MV) and calculated output value (CPV) on the regulatory control and Calculation
Blocks, respectively.
The computational expression for the communication output conversion is shown below:
1
OUT= • (MV-BIAS)
GAIN C040810E.EPS
OUT: Subsystem output value

GAIN: Data conversion gain
BIAS: Data conversion bias
The data conversion gain and bias are set through the function block detail definition
builder.
• Data Conversion Gain:
Specify a floating-decimal constant, a 9-digit number including the sign and decimal
point.
Default is 1.000.
• Data Conversion Bias:
Specify a floating-decimal constant, a 9-digit number including the sign and decimal
point.
Default is 0.000.
TIP
When a function block is defined with communication output conversion, the following features will not
function:
• Velocity-type output
• Output velocity limiter
• Reverse swinging (Reverse analog output direction)

C4.8.4 Output Signal Conversion of Logic Operation Blocks

The following paragraph explains the output signal conversion of Logic Operation
Blocks.
■ Output Signal Conversion of Logic Operation Blocks £

The logic calculated value (CPV) for the output to the connection destination connected to
the OUT terminal is passed to the destination block without any output processing. The
data type of calculated value is integer type.
TIP
In bitwise logic operation blocks, CPV is displayed in 8 digits hexadecimal.

<Toc> <Ind> <C4.9 Auxiliary Output> C4-44
C4.9 Auxiliary Output

The auxiliary output is used when output a signal to a destination other than the final
control element. The signal is often used as compensation data to other function
blocks, or to the indicator outside of the FCS, etc.
The operation of auxiliary output is different between the Regulatory Control Block
and the Calculation Block.
This section explains the operation in the auxiliary output.
■ Auxiliary Output from the Regulatory Control Block

▼ Auxiliary Output
The auxiliary output is used when output a signal through the SUB terminal to a destination
other than the final control element. The signal is often used as compensation data to other
function blocks, or to the indicator outside of the FCS, etc.
In the Regulatory Control Blocks, the process variable (PV), change in process variable
(PV), manipulated output value (MV), or the change in manipulated output value (MV) is
output via the SUB terminal. The connection method is the data setting.
The connection destinations of the SUB terminal are indicated below.
• Process output
• Data item of other function block

In function blocks with the output compensation function, the change of MV before the
output compensation is considered to be the change in manipulated output value (MV).
Even if the output of the auxiliary output becomes open, the alarm status does not change
to an output open alarm (OOP).
The operation of the auxiliary output is determined by the settings for the auxiliary output
builder definition items “Output Data” and “Output Type.”
The auxiliary output builder definition items “Output Data” and “Output Type” are set with
the Function Block Detail Builder.
Table Selection List and Default Values for Output Data of Auxiliary Output
Name of the subject function block Selection list Default value
Manual Loader Block (MLD)
Manual Loader Block with Auto/Man SW (MLD-SW) [MV] [MV] [MV]
Velocity Limiter Block (VELLIM)
Input Indicator Block (PVI)
Input Indicator Block with Deviation Alarm (PVI-DV)
2-Position ON/OFF Controller Block (ONOFF) [PV] [PV] [PV]
3-Position ON/OFF Controller Block (ONOFF-G)
Non-Interference Control Output Block (XCPL)
Regulatory control blocks other than those listed [MV] [MV]
[PV]
above [PV] [PV]
C040901E.EPS
• Output Type:
Selectable from “Positional Output Action” and “Velocity Output Action.”
Default is “Positional Output Action.”
When the output action for auxiliary output is set to “Positional Output Action,” the output
values (MV, MV, PV, or PV) can be set in the connection destination as it is. Also, when
set to the “Velocity Output Action” type, the value read back from the connection destination
is added to the output value and set in the connection destination.

● When the Connection Destination is a Process I/O
The output value is converted to a percentage by the following arithmetic expression to
output.
• When the auxiliary output is process variable (PV):
PV-SL
Output value= •100.0
SH-SL C040902E.EPS
• When the auxiliary output is change in process variable (PV):
PV
SH-SL C040903E.EPS
• When the auxiliary output is manipulated output value (MV):
MV-MSL
MSH-MSL C040904E.EPS
• When the auxiliary output is change in manipulated output value (MV):
MV
MSH-MSL C040905E.EPS
● When the Connection Destination is a Data Item of the Function Block

The output value is output from the SUB terminal without any conversion.
When the output action is set to positional type, the output value (PV, PV, MV or MV) is
set to the connection destination as it is, whereas for the velocity type, the output value is
added to the readback value from the connection destination and set to the connection
destination.
Table Relationship between the I/O Connection Methods and Output Action
Output action
Output connection method Output value
Positional type Velocity type
Process output PV, PV
Data setting to the function block MV, MV
C040906E.EPS
: Allowed
Blank: Not allowed

■ Auxiliary Output from the Calculation Block
▼ Auxiliary Output
A Calculation Block outputs the calculated output variable (CPV) or change in the calcu-
lated output value (CPV) through its SUB terminal.
A batch set block with input indicator (DSET-PVI) can output the data setpoint (SV) and the
change in data setpoint (SV) as well as the calculated output variable (CPV) and the
change in calculated output variable (CPV).
The output value and output action of auxiliary output can be set with the Function Block
Detail Builder. The action of the auxiliary output is determined by the settings of the auxil-
iary output builder definition item “Output Data” and “Output Type.”
The auxiliary output builder definition items “Output Data” and “Output Type” are set with
• Output Data:
Selectable from “CPV” and “CPV.” However, in the case of the DSET-PVI block, it is
selectable from “CPV,” “CPV,” “SV” and “SV.”
Default is “CPV.”
• Output Type:
Selectable from “Positional Output Action” and “Velocity Output Action”
Default is “Positional Output Action.”
When the “Positional Output Action” is defined for output action, the output value (CPV,
CPV, SV or SV) is set to the connection destination without change, whereas the output
value is added to the readback value from the connection destination and set to the con-
nection destination when set to the “Velocity Output Action.”

<Toc> <Ind> <C4.10 Output Processing in Unsteady State> C4-48
C4.10 Output Processing in Unsteady State

In the unsteady state, the Calculation Block executes different output processing
from that in the usual status.
The unsteady state includes the calibration (CAL) status and the bad data status
(BAD) in the calculated output value (CPV).
■ Operation during Calibration (CAL)

When the data status of the calculated output value (CPV) is in calibration (CAL), output
from the secondary terminals (CPV1 to CPVn) is stopped. Manual setting of the calculated
output value (CPV) will be enabled and the calculated output value (CPV) output will be
available as usual.
■ Operation when the CPV Data Status is BAD

When the calculation input value is abnormal or when an error occurs during the calculation
processing, the data status of the calculated output value (CPV) becomes BAD (bad data
value) and the previous value is retained as the calculated output value (CPV).

<Toc> <Ind> <C4.11 CPV Pushback> C4-49
C4.11 CPV Pushback

The CPV pushback is a function to prevent from the abrupt change of the output
when a cascade loop connection switched from open to close.
■ CPV Pushback
The CPV pushback is a function that use the calculated output value (CPV) obtained from
tracking the downstream function block in cascade to calculate back the calculated input
value (RV) for the upstream function block to track.
The CPV pushback is used to prevent the process output from abrupt changes when the
Analog Calculation Block receives output signal from a Controller Block (such as a PID
block) via its IN terminal by terminal connection, and the calculated output value (CPV)
outputs to a Manual Loader Block with Aut/Man SW (MLD-SW) or etc.
The CPV pushback operates only when the output value tracking is defined to “YES.”
SEE ALSO
For the setting of the output value tracking, see a chapter C4.5, “Output Tracking.”
■ CPV Pushback Calculation

The calculations shown below are performed during a CPV pushback.
Table CPV Pushback Calculations
Type Calculation formula
CPV 2
SQRT RV= (*1)
GAIN
CPV
EXP RV=In (*2)
GAIN
LAG
INTEG CPV
LD RV= (*1)
LDLAG GAIN
DLAY
RV is the value of X axis coordinate
FUNC-VAR calculated by inputting for the Y axis the value
resulting from dividing CPV by GAIN (*1).
C041101E.EPS
*1: When GAIN is 0, the CPV pushback calculation is bypassed and the previous calculated input value (RV) is retained.
*2: When (CPV/GAIN) 0, the previous calculated input value (RV) is retained.

■ Example of CPV Pushback
CPV pushback
f-1
OUT IN OUT
MV RV f CPV
Regulatory control
block Analog calculation block
(PID)
Data status [CND]
Terminal connection
AUT
Data connection (setting) CSV SV
MAN
Regulatory control block
(MLD-SW)
C041102E.EPS
Figure Example of CPV Pushback
In the above control loop, if the Calculation Block in the middle of the loop has not the CPV
pushback, the upstream PID block can not track the downstream block MLD-SW when the
MLD-SW is switched to MAN mode. Thus when the MLD-SW block is switched to AUT
mode the bumps occurs to the cascade setting value (CSV) of the MLD-SW block.

The CPV pushback function monitors the down stream block status. When tracking is
required, it uses calculated output value (CPV) tracked from the downstream block to
calculate back the calculated input value (RV) for upstream block to track.
Examples of the CPV pushback operations are as follows:
• When the data status of the setting destination is CND, this function equalize the
calculated output value (CPV) to the data value of the setting destination (Output
tracking function).
• When tracking, a reverse calculation is carried out to calculate the calculated input
value (RV) from the calculated output value (CPV) obtained via tracking.
• As the figure shows, the CPV pushback function is activated only when a loop is
established via terminal connection between the IN terminal (such as a switch function
block placed before the destination block) and the OUT terminal of a controller block.
Table Calculation Blocks with CPV Pushback Function

Block type Model name Name
SQRT Square Root Block
EXP Exponential Block
LAG First-Order Lag Block
Analog INTEG Integration Block
calculation block LD Derivative Block
LDLAG Lead/Lag Block
DLAY Dead-Time Block
FUNC-VAR Variable Line-Segment Function Block
C041103E.EPS
• The CPV pushback function is not available in Calculation Blocks with multiple calcu-
lation input values such as the ADD (Addition) block and TPCFL (Temperature and
pressure correction) block, as well as those which cannot uniquely define a calculated
output value from a calculation input value such as the RAMP block, since reverse
calculation is impossible.

<Toc> <Ind> <C4.12 Output Processing in Sequence Connection> C4-52
C4.12 Output Processing in Sequence Connection

The pulse count block (PTC) as well as the blocks that can be connected in se-
quence connection may perform the status manipulation to the output destination
function block specified in the connected OUT terminal when the logic value re-
quired becomes true.
■ Output Processing in Sequence Connection ¡ £

The PTC block, logic operation block (*1) and CALCU, CALCU-C blocks can use sequence
connection for the I/O connection method.
The “status manipulation” function based on output signals can be used as special output
processing when the logic operation block and CALCU, CALCU-C blocks use sequence
connection.
*1: ¡ £ Logic operation block is only available for CS 3000.
■ Status Manipulation ¡ £
In the case of sequence connection, the I/O connection information indicated below is held
in the output terminal (OUT, Jn):
• Information that identifies the connection destination, such as tag name, user defini-
tion label name, terminal number, and element number
• Information that identifies data item
• Information that shows action specifications
The information based on this I/O connection information and the logical value obtained by
the PTC block, logic operation block (*1) or a CALCU, CALCU-C block, the status manipu-
lations indicated by the output connection information that is written to the OUT terminal are
performed, for the output destination function block that is also indicated by the output
connection information when the required logic value in the block becomes true.
SEE ALSO
For the condition specification on the output connection information, see a chapter D3.3, “Logic Chart
Block (LC64).”

<Toc> <Ind> <C5. Alarm Processing – FCS> C5-1
C5. Alarm Processing – FCS

The FCS alarm processing includes an alarm detection function for detecting any
abnormality in the process and an alarm notification function for giving notification
of the detection results.
■ Functional Structure of the Alarm Processing

Alarm processing is a function that detects any abnormalities in the process from values
such as the process variable (PV) and manipulated output value (MV), then reflects this in
the function block alarm status while at the same time consolidating the detection results
and giving notification of these to the operation and monitoring function as a message.
Alarm processing is found in each function block.
Alarm processing consists mainly of the following two functions.
• “Alarm detection function,” which detects any abnormality in the process
• “Alarm notification function,” which notifies the operation and monitoring function of
the detection result
Function
block
Repeated warning alarm
Alarm
setpoint values
Alarm detection Alarm Alarm

Process notification
function status Alarm
data function
message
Alarm detection Alarm

Alarm inhibition
settings acknowledgment state
Acknowledgment
operation
Alarm setpoint values: Individual data items relating to the alarm settings (PH, PL, etc.)
Alarm status: Data item that indicates the status of the function blocks (ALRM)
Alarm acknowledgment state: Data items that indicate the alarm flashing status (ALFS)
C050001E.EPS
Figure Function Structure of the Alarm Processing
The following functions act as auxiliary functions to the alarm function and alarm notifica-
tion function.
• Alarm detection stop function
• Alarm inhibition function
• Alarm operation

■ Alarm Detection Functions
This is a function that detects any abnormality in the process from values such as process
variables (PV) and manipulated output values (MV). In order to detect anomalies in the pro-
cess, the alarm detection function performs the following alarm checks.
• Input open alarm check
• Input error alarm check
• Input high-high and low-low limit alarm check
• Input high and low limit alarm check
• Input velocity alarm check
• Deviation alarm check
• Output open alarm check
• Output failure alarm check
• Output high and low limit alarm check
• Connection failure alarm check
The alarm check can be executed among the detection functions varies by the function
block.

■ Alarm Detection Functions of Certain Function Blocks
Certain function blocks perform a special alarm check that differs from other function
blocks. These particular alarm checks are indicated below.
● Blending PI Controller Block (PI-BLEND)

• Cumulative deviation alarm check
• Control error alarm check
SEE ALSO
For more information about alarm check specific to PI-Blend block, see D1.12, “Blending PI Controller
Block (PI-BLEND).”
● Flow/weight-Totalizing Batch Set Block (BSETU-2,BSETU-3)

• Pre-batch alarm check
• Batch end alarm check
• Cumulative deviation high and low limit alarm check
• Leak alarm check
• Missing pulse alarm check (BSETU-2 only)
• Flowrate alarm check (BSETU-2)
• Flowrate alarm check (BSETU-3)
• Priority order for alarm displays specific to the batch set block for flowrate measure-
ment
• Priority order for alarm displays specific to the Weight-Totalizing Batch Set Block
SEE ALSO
• For more information about alarm check of BSETU-2 and BSETU-3 blocks, see D1.20.4, “Alarm Process-
ing of Totalizing Batch Set Blocks (BSETU-2, BSETU-3).”
• For more information about alarm check of BSETU-2 block, see D1.21, “Flow-Totalizing Batch Set Block
(BSETU-2).”
• For more information about alarm check of BSETU-3 block, see D1.22.2, “ Alarm Processing of Weight-
Totalizing Batch Set Block (BSETU-3).”
● Motor Control Block (MC-2, MC-3)

• Feedback input high and low limit check
• Thermal trip alarm check
• Interlock alarm check
• Answerback inconsistency alarm
• Answerback error alarm
SEE ALSO
For more information about alarm check of MC-2 and MC-3 blocks, see D1.17.4, “ Alarm Processing of
Motor Control Blocks (MC-2 and MC-3).”

● Velocity Limiter Block (VELLIM)
• Deviation alarm check
SEE ALSO
For more information about alarm check of VELLIM block, see D1.23, “Velocity Limiter Block (VELLIM).”
● Switch Instrument Block (SIO-2, SIO-21, SIO-22, SIO-22P)

• Answerback inconsistency alarm (Same function as the motor control operation block)
• Answerback error alarm (Same function as the motor control operation block)
SEE ALSO
For more information about alarm check of Switch Instrument blocks, see D3.4, “ Switch Instrument
Block.”
● General-Purpose Calculation Block (CALCU, CALCU-C)

• Calculation error alarm
SEE ALSO
For more information about alarm check of CALCU and CALCU-C blocks, see D2.33, “General-purpose
Calculation Blocks (CALCU, CALCU-C).”

■ Alarm Notification Functions
This is a function that summarizes the detection made by the alarm detection function and
reports the summary to the operation and monitoring function as a message. The types of
messages reported to the operation and monitoring function are listed below.
• Process alarm messages
• System alarm messages
■ Alarm Detection Stop Function

This is a function that sets whether the alarm detection function for each process alarm is
“Detect enabled” or “Detect disabled.”
■ Alarm Inhibition Function

This is a function that temporarily inhibits the process alarm message operation with the
alarm detection function still operative.
■ Alarm Operation
This is a function that enables the alarm settings to be specified by engineers or operators.
The following categories can be set.
• Classification of the alarm operation based on alarm priority level
• Specification of the alarm processing level
■ Alarm Checks that are Possible for Each Function Block

The alarm checks that are possible differ for each function block.
SEE ALSO
• For more information about alarm check items of regulatory control blocks, see D1.1.3, “Input Process-
ing, Output Processing and Alarm Processing Possible for Each Regulatory Control Block.”
• For more information about alarm check items of calculation blocks, see D2.3.1, “Input Processing, Output
Processing and Alarm Processing Possible for Each Calculation Block.”
• For more information about alarm check items of sequence control blocks, see D3.1.1, “Alarm Processing
of Sequence Control Blocks.”

<Toc> <Ind> <C5.1 Input Open Alarm Check> C5-6
C5.1 Input Open Alarm Check

The input open alarm check may generate an alarm to indicate that the input signal
is in high limit or low limit input open alarming status (IOP, IOP-).
■ Operation of the Input Open Alarm Check ¡ £

▼ Input Open Alarm
The input open alarm check is a function that determines whether the input values read
from the field by the I/O module is out of the range of the high and low limit input open
detection setpoint values.
The high-limit input open alarm (IOP) is initiated when it is determined that the input value
exceeds the input open high detection setpoint value. Similarly, the low-limit input open
alarm (IOP-) is initiated when the input value is below the low-limit input open detection
setpoint value.
The high and low limit input open alarm (IOP, IOP-) indicates that a failure such as severed
wires in the detection terminal or transmitter has occurred.
The Input open alarm check is performed by the I/O module. The function blocks that are
connected directly to the I/O module receives the check results from the I/O module as a
data status, and the high and low limit input open alarm is activated or recovered.
Even in the function blocks not directly connected to the I/O module, when the data for the
cause of the high and low limit input open alarm is accessed, the high and low limit input
open alarm is activated.
For a pair of redundant modules, the high and low limit input open alarm is initiated when a
high and low limit input open alarm is detected from both modules.
When the conditions for the alarm activation are not satisfied, the system recovers from the
high and low limit input open alarm.
For the function blocks connected to an input/output module that is undergoing online
maintenance, it is possible to specify whether to show input open (IOP) status on the
function blocks or not. This may be defined for each FCS. On the property sheet of the
FCS, check the item “Make block input-side IOP” in the filed of “Action when changing
IOM” on the Constant tab strip. (*2)
TIP
• In the Motor Control Blocks (MC-2 and MC-3), an input open alarm check is conducted for the
feedback input.
• When the input terminal connection for a Logic Operation Block (*1) and General-Purpose Calcula-
tion Block is a sequence connection, no input open check is conducted.
*1: ¡ £ The logic operation blocks are only supported in CS 3000 system.
*2: ¡ May only be specified in CS 3000 system.
£ May only be specified in LFCS2, LFCS, KFCS2 and KFCS. In KFCS2 and KFCS, the setting item “IOM Online
Updating” stipulates the action of the IOM when the initial load setting item, among many other IOM setting items, is
changed online.

<Toc> <Ind> <C5.1 Input Open Alarm Check> C5-7
SEE ALSO
For more information about KFCS2 or KFCS I/O Modules’ initial loading items, see “■ Operation of the I/
O Module when Online Download to the I/O Module is Executed : KFCS2/KFCS” in B3.5, “Operation of I/
O Module when Downloading is Performed.”
■ The Operation of the Function Block during Alarm State Initiated by the
Input Open Alarm Check
The behavior of the function block when the high and low limit input open alarm (IOP, IOP-)
initiated by the Input open alarm check is described below.
• Analog input process such as square root extraction, pulse input conversion, digital
filters, and totalizer functions are disabled.
• The value before alarms occurrence is latched as a process variable (PV). However, if
the PV overshoot is defined, the process variables (PV) are overshot to the high or low
limit of the PV range.
• For regulatory control blocks that have the MAN fallback function, the MAN fallback
function is activated and the block mode is switched to manual (MAN) mode.
■ Settings for the Input Open Alarm Check

Input open alarm check types and the high and low limit input open detection setpoint
values can be set.
● Input Open Alarm Check Types

The setting of the input open alarm check type can be defined in the “input open alarm” on
the Function Block Detail Builder. The types of input open alarm checks are listed below.
The default setting is “both input open alarms enabled.”
• Both input open alarms enabled
• High limit open alarms enabled
• Low limit input open alarms enabled
• Input open alarms disabled
● High and Low Limit Input Open Detection Setpoint Values

The high and low limit input open detection setpoint values can be defined in the IOM
Builder Detail Setting.
• High-limit input open detection setpoint value:
The value shall be within the range between -25.0 to 125.0 %
The default setting is 106.3 %
• Low-limit input open detection setpoint value:
The value shall be within the range between -25.0 to 125.0 %
The default setting is -6.3 %

<Toc> <Ind> <C5.2 Input Error Alarm Check> C5-8
C5.2 Input Error Alarm Check

The input error alarm check determines whether the data status of the input value is
invalid (BAD). When the data is invalid (BAD), the high-limit input open alarm (IOP) is
activated.
■ The Actions of Input Error Alarm Check

The input error alarm check is a function that determines whether the data status of the
input value is invalid (BAD).
When it is determined that the data status of the input value is invalid (BAD), the high-limit
input open alarm (IOP) is activated. The system recovers from the alarming state when the
data status value is no longer invalid (BAD).
The possible causes of the invalid (BAD) data status of the input value are listed below.
• Input open detected
• I/O module failure
• Block mode of the block for data reference is disabled (O/S)
• Data status of the data for data reference is invalid (BAD)
• Data status of the input value fails to communicate (NCOM)
However, when the cause of the invalidity (BAD) data status is low-limit input open, the low-
limit input open alarm (IOP-) is activated and the high-limit input open alarm (IOP) is not
activated.
TIP
In the motor control blocks (MC-2 and MC-3), an input error alarm check is conducted for the feedback
input and answer-back input.

<Toc> <Ind> <C5.2 Input Error Alarm Check> C5-9
■ The Operation of the Function Block During Alarm State Initiated by the
Input Error Alarm Check
The actions of the function block during input open high alarm (IOP) state initiated by the
Input error alarm check are described below.
• Analog input process such as square root extraction, pulse input conversion, digital
filters, and totalizer functions are disabled.
• Process variables (PV) are latched at the value before the alarm occurred. However,
when the PV overshoot is defined, the process variables (PV) are overshot to the high
or low limit of the PV range.
• For regulatory control blocks that have the MAN fallback function, the MAN fallback
function is activated and the block mode is switched to manual (MAN) mode.
■ Settings for the Input Error Alarm Check

The Input error alarm check operates when both the input open alarms enabled or the input
open high alarm enabled on the input open alarm check is defined.
If neither are defined, input error alarm check will not function. In this case, even if the data
status is invalid (BAD), the alarm will not be activated.

<Toc> <Ind> <C5.3 Input High-High and Low-Low Limit Alarm Check> C5-10
C5.3 Input High-High and Low-Low Limit Alarm

Check
The input high-high limit and low-low limit alarm check may generate an alarm to
indicate that the input signal is in high-high and low-low alarming status (HH, LL).
■ The Operation of the Input High-High and Low-low Limit Alarm Check
▼ PV High-High/Low-Low Limit Alarm
The input high-high and low-low limit alarm check is a function that determines whether the
input process variable (PV) is out of the range of the high-high and low-low limit alarm
setpoint value (HH, LL).
When it is determined that the input process variable (PV) exceeds the high-high limit
alarm setpoint value, the high-high limit alarm (HH) is activated. Similarly, when the pro-
cess variable is below the low-low limit alarm setpoint value (LL), the low-low limit alarm
(LL) is activated.
When in alarming state, if the process variable (PV) becomes smaller than the value
obtained by subtracting the alarm hysteresis value (HYS) from the high-high limit alarm
setpoint value (HH), the system recovers from the high-high limit alarm. Similarly, if the
process variable (PV) becomes greater than the value obtained by adding the alarm
hysteresis value (HYS) to the low-low limit alarm setpoint value (LL), the system recovers
from the low-low limit alarm.
PV
HH
HYS
Alarm activation conditions
PV HH
PV
LL
Alarm restoration conditions

PVHHHYS
PVLLHYS
HYS
LL
Time
HH
LL C050301E.EPS
Figure Input High-High and Low-Low Limit Alarm Check

■ Settings for the Input High-High Limit and Low-Low Limit Alarm Checks
The input high-high and low-low limit alarm check types, the high-high and low-low limit
alarm setpoint values (HH, LL), and the alarm hysteresis values (HYS) can be defined.
● The Input High-High and Low-Low Limit Alarm Check Types

The input high-high and low-low limit alarm check type is defined on the “input high-high
and low-low limit alarm” item in the Function Block Detail Builder. The types of the high-high
and low-low limit alarm checks are listed below. The default is to check both the high-high
and low-low limit alarms.
• Both high-high and low-low limit alarm
• High-high limit only
• Low-low limit only
• No alarm
However, with the Flow-Totalizing Batch Set Block (BSETU-2) and weight-Totalizing Batch
Set Block (BSETU-3), only “enabled” or “disabled” can be set for the “input low-low limit
alarm check.” The default in this case is “enabled.”

● High-High / Low-Low Limit Alarm Setpoint Value (HH, LL)
Settings of the high-high limit alarm setpoint values (HH) and the low-low limit alarm
setpoint values (LL) are executed in the HIS.
• High-high limit alarm setpoint values (HH):
Engineering unit data within PV scale Range
The default setting is PV scale high limit value
• Low-low limit alarm setpoint values (LL):
Engineering unit data within PV scale Range
The default setting is PV scale low limit value
If the high-high limit alarm setpoint value (HH) is set to the same value as the PV scale high
limit value, the high-high limit alarm will not be activated. Similarly, if the same value as the
PV scale low limit value is set to the low-low limit alarm setpoint value (LL), the low-low limit
alarm will not be activated.
● Alarm Hysteresis Value (HYS)

The alarm hysteresis value is define on each function block using the Function Block Detail
Builder.
• Hysteresis:
Engineering unit data within the range of 0 to PV scale span, or percentage data for
the PV scale span
When specifying percentage data, add % after the numeric value.
The default is 2.0 %.
This alarm hysteresis value is also used for the input high and low limit alarm check.

<Toc> <Ind> <C5.4 Input High and Low Limit Alarm Check > C5-13
C5.4 Input High and Low Limit Alarm Check

The input high limit and low limit alarm check may generate an alarm to indicate that
the input signal is in high or low alarming status (HI, LO).
In the Motor Control Blocks (MC-2 and MC-3), it checks the high limit and low limit of
the feedback input signal.
■ Input High and Low Limit Alarm Check

▼ PV High/Low Limit Alarm
The input high and low limit alarm check is a function that determines whether the process
variable (PV) is within the range of the high and low limit alarm setpoint values (PH, PL).
When it is determined that the process variable (PV) exceeds the high limit setpoint value,
the high limit alarm (HI) is activated. Similarly, when the process variable (PV) is below the
low limit alarm setpoint value (PL), the low limit alarm (LO) is activated.
When in alarming state, if the process variable (PV) becomes smaller than the value
obtained by subtracting the alarm hysteresis value (HYS) from the high limit alarm setpoint
value (PH), the system recovers from the high limit alarming state. Similarly, if the process
variable (PV) becomes greater than the value obtained by adding the alarm hysteresis
value (HYS) to the low limit alarm setpoint value (PL), the system recovers from the low
limit alarming state.
PV
PH
HYS
PV PH
PV
PL

PVPHHYS
PVPLHYS
HYS
PL
Time
HI
LO C050401E.EPS
Figure Input High and Low Limit Alarm Check

■ Settings for the Input High Limit and Low Limit Alarm Check
The types of input high and low limit alarm check, the high limit / low limit alarm setpoint
values (PH, PL), and the alarm hysteresis values (HYS) can be set.
● Types of Input High and Low Limit Alarm Check

The type of the input high and low limit alarm check is defined on the “input high and low
limit alarm” item in the Function Block Detail Builder. The types of input high and low limit
alarm check are listed below. The default is set as “both high and low limit alarms”.
• Both high and low limit alarms
• High limit only
• Low limit only
• No alarm
● High Limit/Low Limit Alarm Setpoint Value (PH, PL)

Setting of the high limit alarm setpoint values (PH) and the low limit alarm setpoint values
(PL) are performed on the HIS.
• High limit alarm setpoint values (PH):
Engineering unit data within PV scale range
The default setting is PV scale high limit value
• Low limit alarm setpoint values (PL):
Engineering unit data within PV scale range
The default setting is PV scale low limit value
If the same value as the PV scale high limit value is set to the high limit alarm setpoint value
(PH), the input high limit alarm will not be activated. Similarly, if the same value as the PV
scale low limit value is set to the low limit alarm setpoint value (PL), the input low limit alarm
will not be activated.

The alarm hysteresis value is defined on each function block using the Function Block
Detail Builder.
• Hysteresis:
the PV scale span
This alarm hysteresis value is also used for the high-high limit/low-low limit alarm check.

<Toc> <Ind> <C5.5 Input Velocity Alarm Check > C5-16
C5.5 Input Velocity Alarm Check

The input velocity alarm check may generate an alarm to indicate that the velocity in
positive direction (VEL+) or velocity in negative direction (VEL-) is in alarming sta-
tus.
■ Input Velocity Alarm Check

▼ Input Velocity Limit Alarm
The input velocity alarm check is a function that determines whether the changes in the
process variable (PV) over a specified time exceed the velocity alarm setpoint value (VL).
When it is determined that the changes in the process variable (PV) over a specified time
exceed the velocity alarm setpoint value (VL), the velocity alarm in the positive direction
(VEL+) is activated if the changes are in the increasing direction. Similarly, if the changes
are in the decreasing direction, the velocity alarm in the negative direction is activated
(VEL-).
The input velocity alarm indicates abrupt changes in the process condition and abnormali-
ties in the detectors or the transmitters.
The system will recover from the alarm status if the change in the process variable (PV)
falls into the range in which the alarm hysteresis value (HYS) is subtracted from the velocity
alarm setpoint value during the alarm status.
Process variable
VL-HYS
Sampling time interval

(T=Ts•Tp)
VL

VL
Detection time interval (N•T) N: Number of samples
Velocity alarm NR VEL NR

Time
C050501E.EPS
Figure Input Velocity Alarm Check (When Sampling N=2)
The value of sampling time interval (T) is calculated using the set sampling interval (Tp)
and the scan period of the function block (Ts).
T=Ts•Tp
Once the input velocity alarm is activated, the alarm will continue to ring for at least the
sample time interval (T).
The most previously sampled process variable (PV) for input velocity alarm check in the
buffer, i.e., the data sampled right before the Velocity – Reference Sample (PVP), may be
monitored and referred to.

■ Settings for the Input Velocity Alarm
The types of input velocity alarm check, the velocity alarm setpoint values (VL), the alarm
hysteresis value (HYS), the number of samples (N), and the sampling Intervals (Tp) can be
defined.
● Types of Input Velocity Alarm Check

The type of input velocity alarm check can be set with the “input velocity alarm” item of the
Function Block Detail Builder. The following types of input velocity alarm checks are avail-
able. The default is “detection of both directions.”
• Detection of both directions:
Monitors velocity in both directions, positive and negative
• Detection of single direction:
Monitors velocity only in positive direction or negative direction
• No Detection:
Detection is not conducted
When single direction is selected for the input velocity alarm check type, only the velocity in
the positive direction is monitored when the velocity alarm setpoint (VL) has a plus sign and
only the velocity in the negative direction is monitored when the velocity alarm setpoint has
a minus sign. However, when VL=0, the velocity of both directions is monitored regardless
of the input velocity alarm check type.
Also, when “detection of both directions” is selected as the input velocity alarm check type,
the absolute value of the velocity alarm setpoint (VL) is used for monitoring.
● Velocity Alarm Setpoint Value (VL)

The velocity alarm setpoint value (VL) can be set on the operation and monitoring function.
• Velocity alarm setpoint value (VL):
Amount of change over the detection time interval (N•Tp•Ts)
Engineering unit data within PV scale span
The default setting is the PV scale Span
When single direction is set for the input velocity alarm check type, the sign (+ or -) of the
direction to be detected is added to the engineering unit data of the velocity alarm setpoint
(VL).
Also, when the same value (positive value) as the PV scale span is set to the velocity alarm
setpoint (VL), neither a positive or negative direction velocity alarm occurs regardless of the
input velocity alarm check type.

Setting of alarm hysteresis conducted for each block using the Function Block Detail
Builder.
• Hysteresis:
the PV scale span
● Number Of Samplings (N) And Sampling Interval (Tp)

The sampling intervals (Tp) and the number of samplings (N) is defined in the Function
• Number of samplings (N): 1 to 12 points
The default setting is 1 point
• Sampling interval (Tp): 1 to 10,000
Unit is scan interval
The default setting is 1

<Toc> <Ind> <C5.6 Deviation Alarm Check > C5-19
C5.6 Deviation Alarm Check

The deviation alarm check may generate an alarm to indicate that the deviation in
positive direction (DV+) or the deviation in negative direction (DV-) is in alarming
status.
■ The Operation of the Deviation Alarm Check

▼ Deviation Alarm
The deviation alarm check is a function that determines whether the absolute value of the
deviation (DV=PV-SV) between the process variable (PV) and the setpoint value (SV)
exceeds the absolute value of the deviation alarm setpoint value (DL). When it is deter-
mined that the former exceeds the latter, a deviation alarm in the positive direction (DV+) is
activated if the deviation is in the positive direction. Similarly, if the deviation is in the nega-
tive direction, a deviation alarm in negative direction (DV-) is activated.
During the alarm status, if the absolute value of the deviation (DV) falls into the range in
which the alarm hysteresis value (HYS) is subtracted from the absolute value of the devia-
tion alarm setpoint value (DL), the system will recover from the alarm status.
Further, when the same value (positive value) as the PV scale span is set to the deviation
alarm setpoint (DL), neither a positive or negative direction deviation alarm occurs regard-
less of the deviation alarm check type.
DV
DLe
HYS
DV DLe
DV
DLe
Time
0
DVDLeHYS
DVDLeHYS
HYS
DLe
DV
DV C050601E.EPS
Figure Action of Deviation Alarm Check
TIP
With the Dual-Redundant Signal Selector Block (SS-DUAL), the deviation alarm check is performed with
respect to the deviation (DV=PV-SV) between the selected signal value (PV) and the non-selected signal
value (SV).
In this case, if either the selected signal value (PV) or the non-selected signal value (SV) is a BAD value
(BAD), the deviation alarm check is bypassed.

● Characterization of the Deviation Alarm Check
To prevent occurrence of the undesired alarm caused by abrupt set value change or set
value ramp, the velocity change speed (derivative value) of the setpoint value (SV) is used
as the deviation alarm setpoint value correction factor (r) to compensate the deviation
alarm setpoint value (DL). The compensated deviation alarm setpoint value (DLe) is the
value that adding the deviation alarm setpoint value correction factor (r) to the deviation
alarm setpoint value (DL).
DL

deviation deviation
SV
check filter r check
DLe

PV DV PID
C050602E.EPS
Figure Characterization of Deviation Alarm Check
● The Operation of the Deviation Check Filter

The deviation check filter is a function that determines the deviation alarm setpoint value
correction factor (r) by performing derivative calculations of setpoint values (SV).
The computational expression for the deviation check filter is shown below.
KSV • TSVs
r(s) • SV(s)
1TSVs C050603E.EPS
KSV: deviation check filter gain. 0.000 to 10.000

TSV: deviation check filter time constant. 0 to 10000 seconds
s: Laplacian

● Effects of the Deviation Check Filter
(A)
(B)
SV DLe
DV
DL
DLe
0 t
DLe
DL
C050604E.EPS
Figure Effect of the Deviation Check Filter
The (A) and (B) shown in the above diagram assume the setpoint value operations below.
(A) Abruptly ramp to the setpoint value (SV)
(B) Gradually ramp to the setpoint value (SV)
When operation performed like this, the deviation (DV) temporarily increases to the points
indicated as (A) and (B) in the diagram if the process variable is constant. The increase of
the deviation is the result of the setpoint values’ change performed by the operator who
expected such a consequence. The deviation check filter has the effect to prevent the
temporarily increased deviation (DV) caused by setpoint value changes from being acti-
vated. In the diagram, it shows how the corrected deviation alarm setpoint values (+/- DLe)
changes according to the changes in the setpoint value (SV) under the conditions such as
(A) and (B). If the deviation check filter is not provided, the deviation alarm always occurs
whenever the deviation (DV) exceeds the limit of the deviation alarm setpoint value (+/-
DLe), because the deviation alarm setpoint value (DLe) is the same value of the deviation
alarm setpoint value (DL).

■ Settings for the Deviation Alarm Check
The types of the deviation alarm check, the deviation alarm setpoint values (DL), the alarm
hysteresis value (HYS), and the deviation check filter can be set.
● Types of Deviation Alarm Check

The type of deviation alarm check can be defined on the “deviation alarm check” item of
the Function Block Detail Builder. The types of deviation alarm checks are listed below. The
default is “detect both directions.”
Monitors deviation in both directions
Monitors deviation in only one direction, positive or negative
• No detection:
Detection is not conducted
When single direction is selected for detection, if the deviation alarm setpoint value is plus
symbol, only the deviation in the positive direction is detected and if the deviation alarm
setpoint value is negative symbol, only the deviation in the negative direction is detected.
● Deviation Alarm Setpoint Value (DL)

The deviation alarm setpoint value (DL) is set by the operation and monitoring function.
• Deviation alarm setpoint value (DL): Engineering unit data within PV scale span
Default is the PV scale span
When only one direction is selected for detection, the direction that is to be detected (+ or -)
must be added to the engineering unit data of the velocity alarm setpoint value (DL).

● Alarm Hysteresis Value
The alarm hysteresis value is defined on each function block in the Function Block Detail
Builder.
• Hysteresis:
the PV scale span
● Deviation Check Filter

The deviation check filter gain and time constant can be defined in the Function Block
Detail Builder.
• DV check filter gain: Deviation check filter gain
0.000 to 10.000
Default is 0.
• DV check filter time constant: Deviation check filter time constant
0 to 10,000 seconds
Default is 0.
For Input Indicator Blocks with Deviation Alarm (PVI-DV), if scan coefficient is specified as
2 or greater on the Function Block Detail Builder, the deviation check filter should be multi-
plied by the specified scan coefficient.
SEE ALSO
For details on the deviation check filter gain and deviation check filter time constant, refer to “● The
Operation of the Deviation Check Filter.”
TIP
The Dual-Redundant Signal Selector Block (SS-DUAL) and the velocity limiter block (VELLIM) do not
have the deviation check filter function.

<Toc> <Ind> <C5.7 Output Open Alarm Check> C5-24
C5.7 Output Open Alarm Check

The output open alarm check may generate an alarm to indicate that the output is
open (OOP).
■ The Operation of the Output Open Alarm Check

▼ Output Open Alarm
The output open alarm check is a function that determines the data status received from
the I/O module.
Based on the data status (OOP) received from the I/O module, an output open alarm
(OOP) is activated.
This alarm indicates that the control output line has been physically severed.
The output open alarm check is performed by the I/O module. The function block receives
the check results from the I/O module as a data status (OOP) and processes the activation
or the restoration of the output open alarm. The output open alarm is activated only in the
function block that is directly connected to the I/O module. The alarm will not be activated at
function blocks that sends output through data connections to other function blocks.
When I/O modules are duplicated, an output open alarm is activated if both I/O modules
are failed.
In tracking mode (TRK), the output open alarm is activated when data status of the track-
ing input terminal (TIN) or tracking switch input terminal (TSI) is bad (BAD). At this time, the
block mode changes to Initialized manual (IMAN) mode if the output signal is not pulse
width output type. If the output signal is pulse width output type, the block mode does not
change, but the value prior the abnormality occurrence is maintained as the manipulated
output value.

<Toc> <Ind> <C5.7 Output Open Alarm Check> C5-25
■ The Function Block Reaction when Output Open Detected by Output
Open Check Function
When an alarm output open alarm occurs, detected by output open alarm check function,
the function blocks react as follows:
• For the regulatory control blocks that have MAN fallback functions, the MAN fallback
action is initiated and the block mode is changed to manual (MAN) mode.
• The manipulated output value (MV) is frozen, and the current value is kept as manipu-
lated output values (MV).
The reaction is the same as described above when the output fail alarm activates.
■ Settings for the Output Open Alarm Check

Setting of the output open alarm check is performed using the Function Block Detail
Builder.
• Output open alarm check: Choose from “Enabled” or “Disabled”
Default is “Enabled.”

<Toc> <Ind> <C5.8 Output Fail Alarm Check> C5-26
C5.8 Output Fail Alarm Check

The output fail alarm check may generate an alarm to indicate that the output is open
(OOP).
■ The Operation of the Output Fail Alarm Check

The output fail alarm check is a function that determines whether the data status of the
manipulated output value (MV) is output fail (PTPF).
When it is determined that the data status of the manipulated output value (MV) is output
fail (PTPF), an output open alarm (OOP) is activated.
The system recovers from the alarming state when the data status is no longer output fail
(PTPF).
The possible causes of the data status of the manipulated output value (MV) being output
fail (PTPF) are listed below.
• Output open detected
• I/O module failure
• The mode of the destination block that data is being set is out of service (O/S).
■ The Function Block Reaction when Output Fail Alarm Detected by Out-
put Fail Alarm Check Function
When an alarm output fail alarm occurs, detected by output fail alarm check function, the
function blocks react as follows:
• For the regulatory control blocks that have MAN fallback functions, the MAN fallback
action is initiated and the block mode is changed to manual (MAN) mode.
• The manipulated output value (MV) is frozen, and the current value is kept as manipu-
lated output values (MV).
The reaction is the same as described above when the output open alarm activates.
■ Settings for the Output Fail Alarm Check

Enable or disable the output fail alarm check depends on whether the output open alarm
check is enabled or not.
When the output open alarm check is enabled, the output fail alarm check is automatically
enabled.
Vice versa, if the output open alarm check is disabled, the output fail alarm check is dis-
abled too. In this case output fail alarm will not be activated even when the data status
becomes output fail (PTPF).

<Toc> <Ind> <C5.9 Output High and Low Limit Alarm Check> C5-27
C5.9 Output High and Low Limit Alarm Check

The output high limit and low limit alarm check may generate an alarm to indicate
that the output is in high limit or low limit alarming status (MHI, MLO).
■ Operation of the Output High and Low Limit Alarm Check

▼ Output High/Low Limit Alarm
The output high and low limit alarm check is a function that determines whether the ma-
nipulated output value (MV) exceeds the range of the manipulated output variable high-
limit/low-limit setpoint (MH, ML) for the output limiter.
When it is determined that the manipulated output value (MV) exceeds the manipulated
output variable high limit setpoint (MH), an output high limit alarm (MHI) is activated. Simi-
larly, when it is lower than the manipulated variable low limit setpoint (ML), an output low
limit alarm (MLO) is activated.
The system will recover from the alarming state when manipulated output value (MV)
becomes lower than the value in which the alarm hysteresis value is subtracted from the
manipulated variable high-limit setpoint. Similarly, the system recovers from the output low-
limit alarm when the manipulated output value becomes greater than the value in which the
alarm hysteresis value is added to the manipulated variable low-limit setpoint.

<Toc> <Ind> <C5.9 Output High and Low Limit Alarm Check> C5-28
■ Settings for Output High and Low Limit Alarm Check
The types of output high and low limit alarm checks, the manipulated variable high limit/low
limit setpoints (MH, ML), and the alarm hysteresis value (HYS) can be set.
● Types of Output High and Low Limit Alarm Checks

The types of output high and low limit alarm checks can be defined on the “output high and
low limit alarm” item in the Function Block Detail Builder. The types of output high and low
limit alarm checks are listed below. The default is set as “high and low limit alarms.”
• Both high and low limit alarms: Output high and low limit alarm check enabled
• High-limit alarm only: Output high-limit alarm check enabled
• Low-limit alarm only: Output low-limit alarm check enabled
• Alarms disabled: No alarm checking
● Manipulated Variable High-Limit / Low-Limit Setpoint (MH, ML)

The manipulated variable high-limit setpoint (MH) and the manipulated variable low-limit
setpoint (ML) is set by the operation and monitoring function.
• Manipulated variable high-limit setpoint (MH):
Engineering unit data within MV scale span
Default is MV scale high-limit value
• Manipulated variable low-limit setpoint (ML):
Engineering unit data within MV scale span
Default is MV scale low-limit value
If the same value as the MV scale high-limit value is set to the manipulated variable high-
limit setpoint (MH), the output high-limit alarm will not be activated. Similarly, if the same
value as the MV scale low-limit value is set to the manipulated variable low-limit setpoint
(ML), the output low-limit alarm will not be activated.

Alarm hysteresis can be defined in each block in the Function Block Detail Builder.
• Hysteresis:
the PV scale span
Default is 2.0 %.

<Toc> <Ind> <C5.10 Bad Connection Status Alarm Check> C5-29
C5.10 Bad Connection Status Alarm Check

Bad connection status alarm check may generate an alarm to indicate that the
connection is bad (CNF).
■ Operation of the Bad Connection Alarm Check

▼ Bad Connection Alarm
The bad connection status alarm check is a function that determines whether there is a
faulty connection to the function block or data at the I/O connection destination.
When it is determined that the connection status is bad, the bad connection alarm (CNF) is
activated. When the connection is restored, the system recovers from the alarming state.
The bad connection is judged as follows.
• The connected destination function block is in out of service (O/S) mode.
• The connection information is abnormal, and the data reference or data set cannot be
performed.
• The connected destination function block’s data type is invalid (cannot be convert to
the appropriate data type).
■ Setting of the Bad Connection Alarm Check

The bad connection alarm check can be defined in the Function Block Detail Builder.
• Bad connection alarm check: Enabled” or “Disabled”
Default is “Enabled.”

<Toc> <Ind> <C5.11 Process Alarm Message> C5-30
C5.11 Process Alarm Message

The process alarm messages are the process alarms that have been detected by the
alarm detection functions and transmitted from the function block to the operation
and monitoring function.
■ Process Alarm Messages

The process alarm messages are transmitted when abnormality in the process variables
(PV) or manipulated output values (MV) is detected by the alarm detection function of the
function block, and when the abnormality returns to normal.
Alarm detection function as well as alarm check function varies from function block types.
For those alarm items that have been set to “AOF ( Alarm Off),” when alarm occurs, the
process alarm message is detected but activates no alarm message on the operation and
monitoring function.
For those alarm items that have been as “no alarm detection,” when alarm occurs, it acti-
vates no alarm message on the operation and monitoring function because the function
block does not detect the alarm.
SEE ALSO
Refer to C5.1, “Input Open Alarm Check” to C5.10, “Bad Connection Status Alarm Check” for each
process alarm detection.

<Toc> <Ind> <C5.12 System Alarm Message> C5-31
C5.12 System Alarm Message

The system alarm messages are the messages represent system abnormality oc-
curred in the FCS and in the function blocks, those have been transmitted to the
operation and monitoring function.
This section describes the messages related to the function blocks.
■ System Alarm Message

The system alarm messages are transmitted for abnormalities originating in the control
station system, such as a malfunction in the I/O module or calculational errors caused in
the user-defined computational expressions.
Regardless how the function block alarm detection defined, system alarm message will
definitely broadcasts whenever it occurs or recovers.
The abnormalities that initiate the system alarm message are shown below.
● Abnormalities of the Input Modules

Abnormalities caused by the Input module detected by the Input error alarm check.
● Abnormalities of the Output Modules

Abnormalities caused by the output module detected by the output fail alarm check.
● Abnormalities in the User-Defined Computational Expression

Computational error caused in the user-defined computational expression in the general-
purpose calculation block (CALCU).
● Abnormalities on One-Shot Initiation Exerted from the Sequence Control

Block
Abnormalities occurred in a function block which terminal connected to a sequence control
block such as sequence table, when the sequence block exerts a One-Shot initiation to the
function block. This can be caused by any of the reasons below.
• The connected destination block is in out of service (O/S) mode.
• Restriction on the one-shot initiation from the nest.
A function block that can be one-shot initiated is able to one-shot initiate another
function block. When the chain one-shot initiation on multiple function blocks exceed
the limit, an error occurs.

<Toc> <Ind> <C5.13 Deactivate Alarm Detection> C5-32
C5.13 Deactivate Alarm Detection

The alarm detection function for each process alarm can be stopped in accordance
with the alarm detection specification.
■ Alarm Detection
For each alarm detection function of the process alarms, the alarm detection status is
changed by the function that sets “Detection enabled” or “Detection disabled”.
● Deactivate Alarm Detection

The alarms that are set as “Detection disabled,” the alarm detection function itself will be
disabled.
When the alarm detection is being changed from “Detection enabled” to “Detection dis-
abled”, if the process alarm is in alarm activating status, the alarm notification process is
executed in the same manner as alarm recovery. Therefore, if there are no alarms in
progress in the function block of the process alarm, that function block will be handled as a
normal recovery (Alarm status: NR).
■ Alarm Detection Specification

The alarm detection specifications are defined in the Function Block Detail Builder to each
alarm in each function block.
The alarm detection specification (AF) for each alarm can be changed through the se-
quence table block or the sequence-connected function block.

<Toc> <Ind> <C5.14 Alarm Inhibition (Alarm OFF)> C5-33
C5.14 Alarm Inhibition (Alarm OFF)

The alarm inhibition can be used to temporarily inhibit the action of process alarm
messages while the alarm detection is still active.
■ Alarm inhibition (Alarm OFF)

The alarm inhibition is a function that temporarily inhibits the action of process alarm
messages. During this time, the alarm detection is still active.
The alarm inhibition is abbreviated to alarm OFF (AOF).
The following table indicates the alarm action during alarm inhibition and when it is not
inhibited, each alarms priority level.
Table Standard Specification of Alarm Actions
Normal alarm action Alarm action when inhibited
Alarm priority Alarm display Repeated Alarm display Repeated
flashing action warning alarm flashing action warning alarm
High-priority Locked (*1) Self acknowledge
Medium-priority Locked (*1) Self acknowledge
Low-priority Non-locked Self acknowledge
Logging Self acknowledge Self acknowledge
Reference Self acknowledge Self acknowledge
C051401E.EPS
: For repeated warning alarm

Blank: Not for repeated warning alarm
*1: Can be changed on Alarm Priority Builder.
When the alarm shifts from the normal mode to AOF mode, the active alarms will keep
previous behaviors. For example, the alarm flashing state and the repeated-warning alarm
actions will be remained. When the alarm status changes (alarm occurs or recovers in the
same tag), the initial alarm inhibition actions will take place.
Since the alarm detection is conducted even in the alarm inhibition mode, the alarm status
can be still referred from sequence control blocks as sequence condition. The conditions
are functioning the same as in normal (not in AOF) mode.
SEE ALSO
• For more information bout alarm processing during alarm inhibition, see E12.3.3, “Alarm Inhibition (AOF).”
• For more information about alarm flashing, see C5.15.1, “Alarm Display Flashing Actions.”

<Toc> <Ind> <C5.14 Alarm Inhibition (Alarm OFF)> C5-34
■ Alarm Inhibition Setting
The alarm inhibition can be set for each function block. Alarms of a block can also be
inhibited all together. Each process alarm, including the input open alarm (IOP) and the
output open alarm (OOP), can be inhibited individually.
The alarm inhibition setting can be changed manually by the operator or changed by the
sequence control blocks or the blocks in sequence connection. However, from an operation
and monitoring console, alarms of a block can only be inhibited all together.
■ Alarm Notification when Releasing Alarm Inhibition

▼ Alarm Notify Action when All AOF Released
For all alarms in a function block, how they behave when releasing Alarm Inhibition can be
specified. To notify the operation and monitoring console the existing alarms or not to notify
the operation and monitoring console can be selected.
TIP
• The setting for notifying the or not notifying the operation and monitoring console of the existing
alarms only valid for releasing the AOF, it does not function when release alarm inhibition of each
alarm items of a function block.
• For the alarms masked by Representative Alarm Block (ALM-R), when alarm mask is released by
changing the SV or SW of the ALM-R block, the existing alarms will not initiate alarm message
outputs.
■ Check Box of Alarm Notify Action when All AOF Released

On each FCS property sheet, there is a check box of Alarm Notify Action When All AOF
Released. To notify the operation and monitoring console when alarm inhibition is released
can be set by checking this item.
• Alarm Notify Action when All AOF Released
Check this option. This option is not checked by default setting.

<Toc> <Ind> <C5.15 Classification of Alarm Actions Based on Alarm Priority> C5-35
C5.15 Classification of Alarm Actions Based on

Alarm Priority
There are five levels of alarm priority. The alarm action varies by the priority level.
■ Alarm Priority
There are five levels in alarm priority. They are high-priority alarms, medium-priority alarms,
low-priority alarms, logging alarms and reference alarms. Each level of alarm priority has its
own specifications regarding to the following items:
• Enable/Disable display on windows
• Enable/Disable printouts
• Enable/Disable logging into file
Regarding to FCS, each level of alarm priority has the following different specifications:
• Alarm Action (Alarm flashing actions when alarm occurs)
• Enable/Disable repeated warning alarm
• Alarm Action when Returning to Normal (Alarm flashing when returns to normal)
The alarm actions corresponding to each level of alarm priority when alarm inhibition is
deactivated are list in the following table.
Table Alarm Actions and Levels of Alarm Priority
Alarm display Repeated

Alarm priority When returns to normal
flashing warning alarm
High-priority Locked (*1) Yes (*1) Depends on alarm type (*1)
Medium-priority Locked (*1) No No action
Low-priority Non-locked (*1) No No action
Logging Self acknowledge No No action
Reference Self acknowledge No No action
C051501E.EPS
*1: The action may be defined on Alarm Priority Builder.
SEE ALSO
For more information about the behaviour of operation and monitoring console when an alarm returns to
normal, see E12.2, “Alarm Priority.”
For more information about alarm display flashing, action when returns to normal (Alarm flashing when
returns to normal), see C5.15.1, Alarm Display Flashing Actions.”

C5.15.1 Alarm Display Flashing Actions

The alarm display flashing action is a function that changes the alarm display color
or flashing status in the operation and monitoring window when a change occurs
with respect to the alarm.
■ Alarm Display Flashing Actions

When an alarm occurs or when the system recovers from the alarm status, and when
operator acknowledges the occurrence or recovery, the alarm marks on the operation and
monitoring window change flashing status or colors.
The alarm acknowledgment action performed by the operator is transmitted to the FCS.
The FCS indicates the alarm acknowledged status (if the alarm has been acknowledged or
not) by alarm flashing status (AFLS) for each function block. Therefore, from any operation
and monitoring console in the same project can perform the alarm acknowledgment action
and monitor the alarm acknowledgment status.
■ Alarm Display Flashing Action When Alarm Occurs

The alarm display object starts to flash when the alarming activates and stops flashing
when the alarm is acknowledged. There are three types of flashing actions behaves differ-
ently when the alarm status recovers. They are lock type, non-lock type, and self-acknowl-
edge type.
● Locked Type (LK : Locked)

Even if alarm has recovered, the alarm flashing will continue until it is acknowledged.
Alarm condition
Acknowledgment Acknowledgment
Flashing status
C051502E.EPS
Figure Locked Type Alarm Display Flashing Action
● Non-Locked Type (NL : Non-Locked)

When alarm status has recovered, the flashing stops regardless whether has been ac-
knowledged or not.
Alarm condition
Acknowledgment
Flashing status
C051503E.EPS
Figure Non-Locked Type Alarm Display Flashing Action

● Self-Acknowledge Type (SA : Self-Acknowledge)
It is assumed that the alarm is acknowledged when it activates, so that the alarm display
object does not flash.
Alarm condition
Flashing status
C051504E.EPS
Figure Self-Acknowledging Type Alarm Display Flashing Action
■ Alarm Action in Normal Status (Flashing Action in NR Status)

When a function block returns to normal status with all alarms vanished, the mark for
normal (NR) will flash to notify the operator. The flashing action when normal status returns
from alarm status contains two types, Alarm Dependent and Normal Notification. Only the
alarms with high-priority can be specified with these options.
● Alarm Dependent (XL: eXception Lock)

When all alarms vanish and normal status returns, the alarm marks that have been flashing
will continue to flash. The alarm marks that have stopped flashing will not flash.
● Normal Notification (NL: Non-Lock)

When all alarms vanish and the block returns to normal, the alarm mark starts to flash even
though the alarming status flashing has been stopped. An acknowledge operation may
stop the normal notification flashing. Without the acknowledge operation, the normal
notification flashing will be kept when a new alarm occurs. When a function block returns to
normal, it notifies it to operator by this Non-Lock type notification.

C5.15.2 Repeated Warning Alarm

The repeated warning alarm retransmits a process alarm message to notify the
operator that a critical alarm status is continuing.
■ Repeated Warning Alarm

The repeated warning alarm is a function that retransmits a process alarm message after a
specified time has elapsed during the period between the alarm occurrence and recovery
from the alarm, regardless of whether the alarm is acknowledged. The purpose of the
repeated warning alarm is to notify the operator that a critical alarming state is continuing.
When multiple alarms originated from the same tag, the re-alarm requests are issued
simultaneously to the same tag. In this case, only the one has the highest-priority among
them can be reissued again.
Only the high-priority alarm can be reissued as repeated warning alarm. If the definition
item of repeated warning alarm cycle is defined as zero second, repeated warning alarm
does not effect.
■ Repeated Warning Alarm at Initial Cold Start

▼ Alarm Mask for Initial Cold Start
The repeated warning alarm has a function in which at initial cold start (include recovery
from a long period of power failure) of the FCS, only the high-priority alarms are picked up
from all the alarms and issued to the operation and monitoring consoles.
When the initial cold start for the FCS is executed, as a rule, only the alarms that were
newly activated after start are transmitted to the operation and monitoring console by the
alarm mask function. However, for the alarms that are set as repeated warning, if alarm is
in process, the process alarm message is transmitted even though it was not newly acti-
vated.
However, if it is set as “alarm mask disabled” in the FCS Constants Builder, every alarm
that is in progress will be classified as newly activated, and the process alarm messages
will be issued at initial cold start.
■ Setting of Repeated Warning Alarm Period

▼ Interval of Repeated Warning Alarms
The period of the repeated warning alarm is defined for each control station in the FCS
Constants Builder.
• Repeated warning alarm period: The setting value is between 0 to 3600 seconds.
When 0 is set, repeated warning alarm function is
disabled.
Default is 600 seconds

<Toc> <Ind> <C5.16 Alarm Processing Levels> C5-39
C5.16 Alarm Processing Levels

With the alarm processing level, the alarm priority level can be specified for each
function block or element.
■ Alarm Processing Levels

▼ Alarm Level
Designating an alarm processing level to a function block or an element, the alarms from
the function block or the element will have the designated priority and display the desig-
nated color.
There are 16 levels, 1 to 16, for alarm processing. The alarm priority and alarm colors of all
alarms occurred in a function block or an element are defined for each processing level.
The alarm priority defined for the first 4 levels of alarm processing are shown as follows.
• Level1
All alarms initiated from the function block or the element are “High-priority alarms.”
• Level2
All alarms initiated from the function block or the element are “Medium-priority
alarms.”
• Level3
All alarms initiated from the function block or the element are “Low-priority alarms.”
• Level4
All alarms initiated from the function block or the element are “Logging alarms.”
The definitions for level1 to level4 are fixed for a whole system. The alarm priorities and
colors for level5 to level16 can be defined by users.
The alarm processing levels for each function block can be defined on the Function Block
Overview Builder or function block detail builder.
SEE ALSO
For more information about the definitions of level5 to level16, see section “■ Alarm Processing” of
chapter E12.4, “Alarm Status Character String and Alarm Processing.”

Blank Page
<Toc> <Ind> <C6. Block Mode and Status> C6-1
C6. Block Mode and Status

Block mode and status are the information that represent how a function block
behaves under the current circumstances. Block mode and block status represent
the operating state of the function blocks, while alarm status represents the alarm
state of the process. Data status represents the reliability of the process data.
■ Block Mode
Block mode is the information that represents the control state and the output state of a
function block. The different type of function blocks have different kinds of operation mode.
In general there are 9 kinds of basic block mode, and some other block modes that are the
composition of those basic block modes.
■ Block Status
A block status is the information that represents the operating state of a function block.
Block status and block mode reflect the overall behavior of the function blocks. The differ-
ent type of function block have different type of block status. Some function blocks do not
have any block status.
■ Alarm Status
An alarm status is information that represents the alarm state of a process which was
detected by the function block. The different type of function block have different type of
alarm status. Some function blocks do not have any alarm status.
■ Data Status
A data status is the information that represents the reliability of data. For the data obtained
from I/O module, their status pass from one function block to another. Data status is ob-
served when various exceptional events occurred due to abnormality in the process or
calculation.
■ Block Mode and Block Status of the Faceplate Block

The block mode and block status of the faceplate block are different from the block mode
and block status of other function blocks.
SEE ALSO
For more information about block mode and block status of the faceplate blocks, see a chapter D4.3,
“Block Mode and Status of Faceplate Blocks.”
■ Block Mode and Block Status of the SFC Block

The block mode and block status of the SFC block are different from the block mode and
block status of other function blocks.
SEE ALSO
For more information about block mode and block status of the SFC block, see a chapter D5.6.13, “SFC
Block Mode & Status.”

<Toc> <Ind> <C6.1 Block Mode> C6-2
C6.1 Block Mode

▼ Block Mode
Block mode is the information that represents the control state and the output state
of a function block. The different type of function blocks have different kinds of
operation mode. In general there are 9 kinds of basic block mode, and some other
block modes that are the composition of those basic block modes.
■ Basic Block Mode

There are 9 kinds of basic block mode. These basic block modes are shared by all function
blocks.
However, the basic block mode that can be applied to the particular function block varies
from the types of the function block.
■ Compound Block Mode

Compound block mode refers to the state where multiple basic block modes are estab-
lished simultaneously. In a compound block mode, the block mode with the highest priority
among the basic block modes that are being simultaneously established will be executed.
Between any two block modes, there exists either a complementary relationship in which
the two modes can be simultaneously established as a compound block mode, or a mutu-
ally exclusive relationship in which the two modes cannot be simultaneously established.
■ Transition of Block Mode

A transition of a block mode means that a specific block mode changes into a different
block mode. A transition of block mode can be initiated by a mode change command from
outside of the function block, or it may take place automatically when a mode transition
condition is established inside.
■ Block Mode Transition Command

The block mode transition commands are the commands for switching the block mode
performed outside of the function block, such as the operations performed by operator, or
the action from the sequence control blocks and so on.
■ Block Mode Transition Condition

The block mode transition condition stand for the factors related to block mode change.
When the condition for block mode change established, the block will automatically shift to
the mode.
■ Block Mode of Function Blocks

The type of block mode applicable to the function blocks varies with type of block.
SEE ALSO
• For more information about block mode of regulatory control blocks, see D1.1.4, “Valid Block Modes for
Each Regulatory Control Block.”
• For more information about block mode of calculation blocks, see D2.3.2, “Valid Block Modes for Each
Calculation Block.”
• For more information about block mode of sequence control blocks, see D3.1.2, “Block Mode of Se-
quence Control Blocks.”

C6.1.1 Basic Block Mode

There are 9 kinds of basic block mode. These basic block modes have common
meanings when applied to all function blocks.
■ Basic Block Mode

The following table lists the basic block modes. The basic block mode that can be applied
to the particular function block varies from the types of the function block.
Table Basic Block Modes
Symbol Name Description
O/S Out of Service All functions of the function block are currently stopped.
IMAN Initialization MANual Calculation processing and output processing are currently stopped.
TRK TRacKing Calculation processing is currently stopped and the specified value is forced to be output.
Calculation processing is currently stopped and the manipulated output value, which is
MAN MANual
set manually, is output.
AUT AUTomatic Calculation processing is being executed and the calculation result is output.
Calculation processing is being executed, the set value CSV is from the cascade
CAS CAScade
connected upstream block, and the calculation result referred to this CSV is output.
Calculation processing is currently stopped, the set value CSV is from the cascade
PRD PRimary Direct
connected upstream block, this CSV is output directly.
An control and calculation processing is being executed using the remote setpoint value
RCAS Remote CAScade (RSV) which is set remotely from a supervisory system computer, and the calculation
results is output.
Calculation processing is currently stopped, and the remote manipulated output value
ROUT Remote OUTput
(RMV) which is set remotely from a supervisory system computer is output directly.
C060101E.EPS

■ Relationships among Basic Block Modes
The initialization manual (IMAN) mode and the tracking (TRK) mode of the basic block
modes cannot exist by themselves, and they represent certain operating states when they
are established together with other basic block modes.
Any two of the modes such as automatic (AUT), manual (MAN), cascade (CAS), and
primary direct (PRD) can not be established simultaneously. They have exclusive relation-
ship and repel each other. The automatic (AUT) mode and tracking (TRK) mode can exist
together. They have a complementary relationship.
The following figure shows the relationships among the basic block modes:
Priority level
O/S 4 High
Complementary IMAN 3
relationship TRK 2
MAN, AUT, CAS, PRD 1
RCAS, ROUT 0 Low
Exclusive relationship
C060102E.EPS
Figure Relationships among Basic Block Modes

C6.1.2 Compound Block Mode

The compound block mode refers to the state where the multiple basic block modes
exist simultaneously.
■ Compound Block Mode

The state where multiple basic block modes are established simultaneously is called a
compound block mode. The basic block modes that constituting a compound block mode
have complementary relationships with each other so that they can exist together.
Among basic block modes, the initialization manual (IMAN) mode and the tracking (TRK)
mode cannot exist by themselves. Only when they are combined with other basic block
mode, they represent meaningful operating state. Therefore, the initialization manual
(IMAN) mode or the tracking (TRK) mode is established only as part of a compound block
mode.
Take the relationship between the tracking (TRK) mode and the automatic (AUT) mode for
the PID controller block (PID) for example. When the tracking switch (TSW) is turned on
when the operation in the automatic (AUT) mode, the operation of the tracking (TRK) is
executed. When the tracking switch (TSW) is turned off, the operation of the original auto-
matic (AUT) mode is executed. In this example, when the tracking switch (TSW) is on, the
automatic (AUT) mode and the tracking (TRK) mode are established as the compound
block mode.
TSW The TRK and

ON AUT modes are
TRK
AUT (AUT) satisfied simultaneously
TSW
OFF
C060103E.EPS
Figure An Example of the Compound Block Mode
■ The Priority Levels of Block Mode

In a compound block mode, the basic modes that have complementary relationships each
other are distinguished by the priority levels assigned to them. The basic block modes that
have the same priority level but have exclusive relationship cannot exist together. On the
other hand, the basic block modes that have different priority levels and complementary
relationships each other can be established simultaneously.
In a compound block mode, the mode which has the highest priority level among all exist-
ing basic block modes is called the active mode of the compound block mode.
In a compound block mode, the active mode takes effect.

■ Displaying Compound Block Mode on the Operation and Monitoring
Function
Among all simultaneously established basic block modes, the block mode which has the
highest priority level and the one which has the lowest priority level are displayed on the
operation and monitoring function.
Example 1) AUT TRK
Example 2) ROUT AUT
■ References to Compound Block Mode Throughout This Document

In this chapter, a compound block mode is indicated by listing the simultaneously estab-
lished basic block modes in a descending order starting from the highest priority level, and
the block modes that have lower priority levels are in parentheses.
Example 1) TRK (AUT)
Example 2) IMAN (AUT (RCAS))

■ Combinations of Block Mode
The following figure shows the combinations of the basic block modes that constitute
compound block mode.
Low Priority level High

0 1 2 3 4
MAN, AUT, O/S
Type 1
CAS
MAN, AUT, IMAN

Type 2
CAS, PRD
Type 3 MAN, AUT, TRK

CAS, PRD
MAN, AUT, TRK IMAN

Type 4
CAS, PRD
Type 5 RCS, ROUT IMAN
Type 6 RCS, ROUT TRK
Type 7 RCS, ROUT TRK IMAN
RCS, ROUT MAN, AUT,

Type 8
CAS, PRD
Type 9 RCS, ROUT MAN, AUT, IMAN

CAS
Type 10 RCS, ROUT MAN, AUT, TRK

CAS
Type 11 RCS, ROUT MAN, AUT, TRK IMAN

CAS
C060104E.EPS
Figure Combinations of Block Modes

● When Transit from O/S to MAN, AUT or CAS Mode (Type 1)
Compound block mode that represents a course of transition state when transit a block
mode from O/S to MAN, AUT or CAS mode (over transition mode). PRD mode can not be
combined.
Example) Transit from O/S to MAN:

Display on the operation and monitoring function: MAN O/S
Block mode: O/S (MAN)
SEE ALSO
For the over transition block mode, refer to C6.1.3, “Block Mode Transition.”

● When Operate in MAN, AUT, CAS or PRD Mode
Here is the explanation on the compound block modes established when a block mode
transition condition is satisfied while the operation in MAN, AUT, CAS or PRD mode.
SEE ALSO
For the mode transition conditions, see a chapter C6.1.5, “Block Mode Transition Condition.”
• When the Initialization Manual Condition is Satisfied (Type 2)

Compound block modes established when the initialization manual condition is
satisfied while operation in MAN, AUT, CAS or PRD mode.
Example) When the initialization manual condition is satisfied while operation in AUT
mode:
Display on the operation and monitoring function: AUT IMAN
Block mode: IMAN (AUT)
• When the Tracking Condition is Satisfied (Type 3)

Compound block modes established when the tracking condition is satisfied while
operation in MAN, AUT, CAS or PRD mode.
Example) When the tracking condition is satisfied while operation in CAS mode:
Display on the operation and monitoring function: CAS TRK
Block mode: TRK (CAS)
• When the Initialization Manual Condition is Satisfied in Tracking Operation (Type 4)

Compound block modes established when the initialization manual condition is satis-
fied while tracking is effect in the operation in MAN, AUT, CAS or PRD mode.
Example)
When the initialization manual condition is satisfied while tracking is effect in the operation
in AUT mode:
Display on the operation and monitoring function: AUT IMAN
Block mode: IMAN (TRK (AUT))

● When Operation in RCAS or ROUT Mode
Here is the explanation of compound block modes established when a block mode transi-
tion condition is satisfied while operation in RCAS or ROUT mode.
SEE ALSO
For block mode transition conditions, see a chapter C6.1.5, “Block Mode Transition Condition.”
• When the Initialization Manual Condition is Satisfied (Type 5)

satisfied while the operation in RCAS or ROUT mode.
Example) When the initialization manual condition is satisfied while operation in RCAS
mode:
Display on the operation and monitoring function: RCAS IMAN
Block mode: IMAN (RCAS)
• When the Tracking Condition is Satisfied (Type 6)

Compound block modes established when the tracking condition is satisfied while
operation in RCAS or ROUT mode.
Example) When the tracking condition is satisfied while operation in ROUT mode:
Display on the operation and monitoring function: ROUT TRK
Block mode: TRK (ROUT)
• When the Initialization Manual Condition is Satisfied During the Tracking Operation
(Type 7)
satisfied during the tracking operation in RCAS or ROUT mode.
Example)
When the initialization manual condition is satisfied during the tracking operation in
RCAS mode:
Block mode: IMAN (TRK (RCAS))

• When Transit to a Computer Backup Mode (MAN, AUT or CAS) (Type 8)
When communication from the supervisory system fails while the operation is in
RCAS or ROUT mode, transition to a compound block mode e.g. computer backup
mode (MAN, AUT or CAS) takes place. A combination with the PRD mode [PRD
(RCAS) and PRD (ROUT)] is a compound block mode that represents only an over
transition state (over transition mode) during the block mode transition.
Example) When transit from ROUT to a computer backup mode (MAN):

Display on the operation and monitoring function: ROUT MAN
Block mode: MAN (ROUT)
• When Transit from a Computer Backup Mode to RCAS or ROUT Mode (Type 8)
Compound block mode that represents only an over transition state during the block
mode transition from a computer backup mode to the RCAS or ROUT mode (over
transition mode). A combination with the PRD mode [PRD (RCAS) and PRD (ROUT)]
is a compound block mode that represents an over transition state (over transition
mode) during the mode transition.
Example) When transiting from the ROUT mode to a computer backup mode (MAN):
Display on the operation and monitoring function: ROUT MAN
Block mode: MAN (ROUT)
SEE ALSO
For the over transition mode, see a chapter C6.1.3, “Block Mode Transition.”

● During Computer Backup in RCAS or ROUT Mode
Here is the explanation of the combinations of block modes that are obtained when each
block mode transition condition is satisfied during the computer backup in the RCAS or
ROUT mode.
SEE ALSO
For the block mode transition conditions, see a chapter C6.1.5, “Block Mode Transition Condition.”
• When Initialization Manual Condition is Satisfied (Type 9)

Compound block modes that are obtained when the initialization manual condition is
satisfied during computer backup operation (MAN, AUT or CAS mode) in RCAS or
ROUT mode. PRD mode cannot be combined.
Example)
When the initialization manual condition is satisfied during the operation in the com-
puter backup mode (AUT mode) and in the RCAS mode:
Block mode: IMAN (AUT (RCAS))
• When Tracking Condition is Satisfied (Type 10)

Compound block mode established when the tracking condition is satisfied while the
computer backup operation (MAN, AUT or CAS mode) is in RCAS or ROUT mode.
PRD mode cannot be combined.
Example)
When tracking condition is satisfied while the AUT backup operation in ROUT mode:
Display on the operation and monitoring function: ROUT TRK
Block mode: TRK (AUT (ROUT))
• When Initialization Manual Condition is Satisfied During Tracking Operation (Type 11)
Compound block mode established when the initialization manual condition is satis-
fied while the RCAS or ROUT mode and the computer backup mode (MAN, AUT or
CAS mode) exist together and the tracking is in operation. PRD mode cannot be
combined.
Example)
When the initialization manual condition is satisfied during tracking operation in
computer backup mode (AUT) and in RCAS or ROUT mode:
Block mode: IMAN (TRK (AUT (RCAS))

C6.1.3 Block Mode Transition

Block mode transitions means to change a specific block mode to a different block
mode. Block mode transition can be initiated by a block mode change command
from other function block, or it may take place automatically when a block mode
transition condition is satisfied inside.
When transit from a specific block mode to a different block mode, the state which
both block modes exist temporarily is called transition mode.
■ Block Mode Transition

When change a specific block mode into a different block mode, the event is called Block
Mode Transition. In principle, block mode transitions are triggered by the following two
factors:
● Block Mode Change Commands

Block mode transition can be initiated by an external operation, such as an operation
performed by the operator from the operation and monitoring function or block mode
change command from the sequence control block. Operations from the outside of the
function block are called block mode change commands.
● Block Mode Transition Conditions

Block mode transition can take place automatically corresponding to the condition inside of
the function block itself. An example is that block mode changes when abnormality from
connected I/O module is detected.
The conditions which initiates the function block transit its own mode are called block mode
transition conditions.

■ Block Mode Transition Diagram
The following figure shows an overview of block mode transitions.
Each arrow in the figure denotes a block mode change command or a block mode transi-
tion condition.
Items designated with “command” such as in “MAN command” indicate transitions ex-
ecuted by a block mode change command. The other items indicate transitions executed
by a block mode transition condition.
For example, the transition to the out-of-service (O/S) mode is executed by the O/S com-
mand. The MAN, AUT or CAS command executes transition from the out-of-service (O/S)
mode to the respective block modes.
O/S command
O/S mode Normal mode (*1)
MAN command
MAN PRD
O/S AUT command

AUT RCAS
CAS command
CAS ROUT
IMAN satisfied
TSW TSW
O/S command
ON OFF
O/S command
IMAN mode TRK mode
IMAN recovered
IMAN IMAN TRK TRK
(MAN) (PRD) (MAN) (PRD)
O/S
IMAN IMAN TRK TRK
command (AUT) (RCAS) (AUT) (RCAS)
IMAN IMAN TRK TRK

(CAS) (ROUT) (CAS) (ROUT)
IMAN satisfied
TSW TSW
ON OFF
IMAN recovered
IMAN (TRK) mode (*2)
IMAN IMAN
(TRK (MAN) ) (TRK (PRD) )
IMAN IMAN *1: The normal mode represents that O/S,

(TRK (AUT) ) (TRK (RCAS) )
IMAN or TRK is not satisfied.
*2: IMAN (TRK) represents that IMAN and
IMAN IMAN
(TRK (CAS) ) (TRK (ROUT) )
TRK are being satisfied simultaneously.
C060105E.EPS
Figure A Transition Diagram for Block Modes
SEE ALSO
For information on block mode transitions in “normal mode,” “IMAN mode,” “TRK mode” and “IMAN (TRK)
mode” shown in the above diagram, refer to the next section “■ A Diagram for Basic Block Mode Transi-
tion in the Normal Mode.”

■ A Diagram for Basic Block Mode Transition in the Normal Mode
The following figure shows the details of block mode transitions for the segment indicated
as “normal mode” in Block Mode Transition Diagram shown in the previous page.
The block modes transition is shown as follows:
• Priority level 0
RCAS, ROUT
• Priority level 1
MAN, AUT, CAS, PRD
Transition can take place from one block mode to the other if the two modes have the same
priority level. For example, transition can take place from MAN to CAS.
CMP failure CMP failure

RCAS
CMP recovered
CMP
recovered CMP CMP
recovered failure
MAN PRD AUT CAS
(RCAS) (RCAS) (RCAS) (RCAS)
MAN/AUT command
RCAS RCAS RCAS RCAS
CAS/PRD command
command command command command
MAN fallback
MAN PRD AUT CAS
MAN PRD AUT CAS

AUT AUT
fallback fallback
MAN
fallback
MAN/AUT command
ROUT ROUT ROUT ROUT
CAS/PRD command
MAN fallback
MAN PRD AUT CAS

(ROUT) (ROUT) (ROUT) (ROUT)
CMP CMP
CMP recovered failure
recovered
CMP recovered
ROUT
CMP failure CMP failure
CMP failure: A computer failure has occurred

CMP recovered: The computer failure has been recovered
C060106E.EPS
Figure A Transition Diagram for Block Modes in the Normal Mode
Even when the “IMAN mode,” “TRK mode” and “IMAN (TRK) mode” shown in “Block Mode
Transition Diagram” in the previous page exist, transition of basic block mode whose
priority level is 0 or 1 will be similar to the above figure. In these cases, IMAN or TRK, or
both IMAN and TRK will exist in addition to the block modes shown in the above figure.

■ Examples of the Block Mode Transition
Normal mode transition and compound mode transition are show as follows:
1. In Automatic (AUT) mode which is a normal mode, when the tracking switch (TSW) is
turned on, a compound mode consisting of the tracking (TRK) mode and the auto-
matic (AUT) mode is established.
“AUT TRK” is displayed as a block mode. The tracking (TRK) mode is the active
mode.
2. When the connection with the cascade connected output destination opens, the
initialization manual (IMAN) mode is established. A compound mode consisting of the
initialization manual (IMAN) mode, tracking (TRK) mode, and automatic (AUT) mode
are established together.
“AUT IMAN” is displayed as the block mode. The initialization manual (IMAN) mode is
the active mode.
3. When the tracking switch (TSW) is turned off, the tracking (TRK) mode no longer
exists. The compound block mode only consists of the initialization manual (IMAN)
mode and automatic (AUT) mode.
“AUT IMAN” is displayed as a block mode. The initialization manual (IMAN) mode
remains to be active mode.
4. When the connection with the cascade connected output destination recovers, the
automatic (AUT) mode becomes the only block mode.
“AUT” is displayed as a block mode. The automatic (AUT) mode becomes the active
mode.
TRK
(AUT)
Cascade open
TSW ON (IMAN satisfied)
AUT IMAN
(TRK (AUT))
Cascade close TSW OFF

(IMAN recovered)
IMAN
(AUT)
C060107E.EPS
Figure Examples of the Block Modes Transition

■ Rules for Block Mode Transitions
The block mode transition either by external mode change commands or by internal mode
change conditions follows the same rules as explained below.
● Transition to an Exclusively Related Block Mode

When transit to a new block mode which has exclusive relationship with the current block
mode, current block mode will be replaced by the new block mode.
The basic block modes that have exclusive relationship with each other:
• Among MAN, AUT CAS and PRD
• Between RCAS and ROUT
Example) MAN
? AUT command
AUT
Under the same above condition, when transit from one inactive mode of a compound
block mode to another inactive mode of the same compound block mode, the active mode
is not affected, the function block’s behavior remains unchanged too.
Example) IMAN (AUT)

? MAN command
IMAN (MAN)
● Transition to a Complementary Block Mode

When transit to a new block mode which has complementary relationship with the current
block mode, the new block mode will be added to the current block mode and a compound
block mode is established. At this time, the block mode which has the highest priority level
becomes the active mode.
Example) AUT
? IMAN condition establish
IMAN (AUT)
● The Invalidation of the Active Mode

When a new condition invalidates the current active mode, the block mode which has the
next highest priority level becomes the new active mode.
Example) IMAN (TRK (AUT))

? IMAN condition vanish
TRK (AUT)

■ Over Transition Mode
When a specific block mode transits to a different block mode, a state occurs in which both
of the block modes are satisfied temporarily. This state is called an over transition mode.
An over transition occurs in the following mode transitions:
• A mode transition to the RCAS or ROUT mode when a computer failure has occurred.
• A mode transition from the O/S mode.
● A Block Mode Transition to RCAS or ROUT Mode when a Computer

Failure Occurs
When a remote cascade (RCAS) or remote output (ROUT) command is received during a
computer failure (BSW=ON), the function block does not make a direct transition to the
remote cascade (RCAS) or remote output (ROUT) mode but changes first to the over
transition mode.
Subsequently, the computer failure status is determined during the scan period in that
function block, and if there has been a recovery from the computer failure there is a transi-
tion to the remote cascade (RCAS) or remote output (ROUT) mode. If the computer failure
occurrence status is unchanged, a transition is made to the backup mode for the computer.
The over transition mode refers to a compound block mode of the block mode just prior to
the mode change command and the remote cascade (RCAS) or remote output (ROUT)
mode.
Example)
The remote output (ROUT) command when the manual (MAN) mode has been specified
as a computer backup mode, and the computer failure condition is being satisfied.
AUT
? Remote output (ROUT) command
AUT (ROUT) Over transition mode
? After one scan cycle
MAN (ROUT) Computer backup mode (when BSW=ON)
Example)
The remote cascade (RCAS) command when the computer failure condition is not satisfied
AUT
? Remote cascade (RCAS) command
AUT (RCAS) Over transition mode
? After one scan cycle
RCAS Remote cascade mode (when BSW=OFF)

● A Block Mode Transition from the O/S Mode
When a block mode change command is received from the out-of-service (O/S) mode, the
function block does not make a direct transition to the specified block mode but temporarily
changes to an over transition mode such as O/S (MAN), O/S (AUT) or O/S (CAS).
In this case, when the function block which has undergone a block mode transition is a
regulatory control block, the transition to the specified block mode (MAN, AUT, CAS) is
made after initializing the output during the next scan period.
Example) O/S
? AUT command
O/S (AUT)
? After one scan period
AUT
TIP
Output initialization processing includes the following operations:
• Output tracking in the IMAN state
• Reset the pulse width output
• Reset the time-proportional output
SEE ALSO
For output tracking in the IMAN state, refer to C4.5, “Output Tracking.”
■ The Status Change Message

▼ Status Change Message Bypass
When function blocks such as sequence control blocks change block mode, the event
recording function sends the status change message from FCS to HIS to inform the opera-
tor.
To suppress this message can be defined on each function block in the Function Block
Detail Builder.
• Status Change Message Bypass:
Select “Yes” or “No.”
The default is “No.”
In case of the sequence table block (ST16), the default is “Yes.”
When status change message is set as Bypass, the message of status change is not
recorded in the historical message file in HIS.
When the status change is performed manually on HIS, the status change message will all
be recorded in the historical message file in HIS regardless the setting of bypass.

C6.1.4 Block Mode Change Command

Block mode change commands are operations outside of the function block to
transit the block mode, such as operations from the operation and monitoring
function or status change command from sequence control blocks or from general-
purpose calculation blocks (CALCU and CALCU-C).
■ Block Mode Change Commands

Operations and descriptions related to block mode change commands are shown as
follows.
Table Mode Change Commands
Command operation Description
O/S command Sets the O/S mode and resets all other modes.
MAN command Sets the MAN mode and resets modes other than the O/S, IMAN and TRK modes.
AUT command Sets the AUT mode and resets modes other than the O/S, IMAN and TRK modes.
CAS command Sets the CAS mode and resets modes other than the O/S, IMAN and TRK modes.
Sets the PRD mode and resets modes other than the O/S, IMAN and TRK modes
PRD command
(*1).
RCAS command Sets the RCAS mode (*2).
ROUT command Sets the ROUT mode (*3).
C060108E.EPS
*1: The PRD command from the O/S mode is invalid.

*2: The RCAS command from the O/S or ROUT mode is invalid.
*3: The ROUT command from the O/S or RCAS mode is invalid.
When a function block is in calibration status, it ignores the block mode change operations
performed by the operator from the operation and monitoring function.

C6.1.5 Block Mode Transition Condition

Block mode transition conditions are conditions that internally initiate the function
block to transit its mode from one to another.
■ Block Mode Transition Conditions

Block mode transition conditions are conditions that internally initiate a function block to
transit its block mode from one to the other. When a specific condition for transiting to a
certain block mode establishes, such as abnormality in I/O module, the function block itself
changes the block mode automatically by itself according to the block mode transition
conditions.
Block mode transition conditions are listed below:
• The tracking condition
• The MAN fallback condition
• The AUT fallback condition
• The initialization manual condition
• The computer failure condition
• The block mode change interlock condition
■ The Tracking Condition

For the function blocks that have tracking (TRK) function, a tracking switch (TSW) is pro-
vided. According to the status of the tracking switch (ON/OFF), the function blocks set or
reset its tracking (TRK) mode.
A function block changes to the tracking (TRK) mode only when the tracking switch is
turned on. The status of the tracking switch can be changed by the external contact input or
set from other function blocks such as from the sequence control block.
Example) AUT
? TSW=ON
TRK (AUT)
? TSW=OFF
AUT

■ The MAN Fallback Condition
When the MAN fallback condition establishes, the function block changes to the manual
(MAN) mode regardless of the current operation status. Control calculation stops and the
operation status changes to manual.
Example) AUT A MAN

IMAN (CAS) A IMAN (MAN)
The MAN fallback condition establishes when following events occur.

• When the data status of the process variable (PV) is bad value (BAD) or calibration
(CAL). However, the MAN fallback condition does not establishes when the block
mode is the primary direct (PRD) or remote output (ROUT) mode (excluding com-
pound block modes that are obtained during computer backup operation).
• When the data status of the manipulated output value (MV) is output failure (PTPF).
• When the data status of the setpoint value (SV) is bad value (BAD).
• At the regulatory control block where the manipulated output value (MV) is connected
to the process I/O, when the FCS has been started after initialization.
• When the block mode change interlock condition has been satisfied.
• At the regulatory control block where the process variable (PV) or manipulated output
value (MV) is connected to the process I/O, when the I/O module that contains the I/O
point of the connection destination has been changed due to online maintenance.
Even when the above events that constitute the MAN fallback condition have vanished, the
block mode remains manual (MAN) and does not automatically return to the original mode.

■ The AUT Fallback Condition
When the AUT fallback condition establishes, the block changes to the automatic (AUT)
mode, and then operates in automatic status. The mode transition is the same as enforced
by the external AUT command.
Example) CAS A AUT

IMAN (CAS ) A IMAN (AUT)
The AUT fallback condition establishes when the AUT fallback item (in the builder) is
specified “Yes” and the data status of the cascade setpoint value (CSV) is bad value (BAD)
or no communication (NCOM).
The AUT fallback condition establishes only in the cascade (CAS) mode or primary direct
(PRD) mode. The mode transition is the same as enforced by the external AUT command.
Even when the above events that constitute the AUT fallback condition have vanished, the
block mode remains automatic (AUT) and does not automatically return to the original
mode.
The setting of AUT fallback condition can be in the Function Block Detail Builder.
• AUT Fallback: Select “Yes” or “No.”

■ The Initialization Manual Condition
When the initialization manual condition establishes, the block mode changes to the initial-
ization manual (IMAN) mode, and control operation temporarily stops.
A regulatory control block changes to initialization manual (IMAN) mode only when the
internal condition for the block mode establishes. When the condition vanishes, the initial-
ization manual (IMAN) mode is reset and replaced by a new active mode.
Example) AUT
? IMAN condition satisfied
IMAN (AUT)
? IMAN condition recovered
AUT
The initialization manual condition establishes when any of the following events occurs:
• When the manipulated output value (MV) connected destination block changes to
conditional (CND) status (i.e. cascade loop open).
• When the manipulated output value (MV) connected destination block is in no com-
munication (NCOM) or the output failure (PTPF) alarm status.
• When the manipulated output value (MV) connected destination block is a switch
block, and the connection is switched off. (i.e., cascade loop open).
• When the manipulated output value (MV) is output to the process equipment, and the
equipment is in abnormal status or the output open occurs.
• When the output signal is not the pulse width output type, and the data status of the
input signal of the TIN or TSI terminal has changed to bad value (BAD) in the tracking
(TRK) mode.

■ The Computer Failure Condition
When the computer failure condition establishes, operation in remote cascade (RCAS) or
remote output (ROUT) mode temporarily stops, and then switches to computer backup
mode.
Example) When the automatic (AUT) mode is specified as a computer backup mode
RCAS
? Computer failure occurs
AUT (RCAS)
? Computer failure recovers
RCAS
In the remote cascade (RCAS) mode or remote output (ROUT) mode, a setpoint value or
manipulated output value is transmitted from a supervisory system computer through
remote setting communication via control bus.
If abnormality is detected in remote setting communication, the computer failure condition
establishes. Operation in the remote cascade (RCAS) or remote output (ROUT) mode
temporarily stops, switches to a computer backup mode. When the computer failure condi-
tion vanishes, the mode immediately returns to the original (RCAS or ROUT) mode.
The function blocks that have the remote cascade (RCAS) or remote output (ROUT) mode
is provided with a backup switch (BSW). According to the status of this switch (ON/OFF),
the function block determines whether the computer failure conditions exist or not.
• When BSW=ON, the computer failure conditions exist.
• When BSW=OFF, the computer failure conditions not exist
Determine as desired the status of the backup switch (BSW) in the control application such
as a sequence table and set it for the backup switch (BSW). However, in a block mode
other than remote cascade (RCAS) or remote output (ROUT), the block mode does not
change even if the backup switch (BSW) is operated.
The computer backup mode can be set with the Function Block Detail Builder.
• Computer Backup Mode:
Status setting when the computer is down.
Select from “MAN,” “AUT” and “CAS.”
Default is “MAN.”
Select from “AUT” and “CAS” in the case of a Control Signal Splitter Block (SPLIT).
Default is “AUT.”

■ The Block Mode Change Interlock Condition
When the block mode change interlock condition establishes, the block changes to manual
(MAN) mode, and the change command to automatic operation status (AUT, CAS, PRD,
RCAS or ROUT mode) become invalid.
If automatic operation cannot continue due to abnormality in the plant, etc., it is necessary
not only to stop the currently automatically operated control loops but also to prevent them
from being put into AUT again.
To prevent the function blocks change to automatic operation mode, the automatic opera-
tion interlock switch can be used. The automatic operation interlock switch can be con-
nected to the function blocks that have automatic operation mode.
When the status of the interlock switch connected to the terminal (INT) becomes ON, the
block mode change interlock establishes, then succeeded by the following actions:
• The MAN fallback condition establishes, and the block mode changes to manual
(MAN).
• Any mode change command to put the function block into an automatic operation
status (AUT, CAS, PRD, RCAS or ROUT mode) is invalidated.
Any datum that has a logical value, such as a contact I/O or internal switch, can be speci-
fied as an automatic operation interlock switch regardless the type of the element.

<Toc> <Ind> <C6.2 Block Status> C6-27
C6.2 Block Status

▼ Block Status
The operating state of a function block may be monitored via block status.
■ Block Status
Block status is the information that represents the operating state of a function block. Block
status and block mode simultaneously reflect an overall operation state of a function block.
The different type of function blocks have different kinds of block status. Some function
blocks do not have any block status.
A function block may check itself and display the result via block status.
Similar to block modes, the block status is also categorized by priority levels. A block status
with same priority level exists exclusively. It is not possible that a block can be in two
statuses with same priority level at the same time. A supplementary status can exists
together with the main status, however, in this case, only the main status is displayed on
HIS as the block status.
Table Block Status of Each Function Block
Function block name

Arithmetic-
Regulatory control block Sequence control block calculation
block
Priority
level MC-2 BSETU-1 PTC SO-1 SIO-11 TM CTS CI CO INTEG
MC-3 BSETU-2 SO-2 SIO-12 CTP AVE-C
SIO-21
SIO-22
SIO-12P
SIO-22P
3 ANCK - - - ANCK PAUS - ERR - -
OFF PAUS PALM PALM HI HI
2 LOCK - - - CTUP CTUP LO LO -
NR NR NR NR
SIM STRT CTUP SIM SIM RUN RUN RUN
NR IBCH PALM NR NR STOP STOP STOP
STUP NR
STDY
ERLY
PBCH
1 - -
END
NCNT
RSET
EMST
EEMS
RSTR
C060201E.EPS

<Toc> <Ind> <C6.3 Alarm Status> C6-28
C6.3 Alarm Status

The process alarm may be monitored and managed via alarm statuses of data items.
■ Alarm Status Common to Regulatory Control Blocks

An alarm status is information that represents the alarm state of a process which was
detected by the function block. The alarm status that can be satisfied for a particular func-
tion block varies depending on the type of the function block.
Some function blocks do not have any alarm status.
The alarm status for the operation and monitoring function is displayed in the data item
ALAM. When multiple alarms are occurring, the alarm status with the highest alarm display
priority will be displayed.
The priority for alarm display is as follows:
OOP>IOP>IOP->HH>LL>HI>LO>DV+>DV->VEL+>VEL->MHI>MLO>CNF

Table Alarm Status Common to Regulatory Control Blocks
NR Normal Indicates a state in which no alarm has occurred.
Indicates a state in which the output data status has become output failure (PTPF) as a
OOP Output OPen Alarm result of the failure or disconnection of an operation terminal or process I/O device or the
abnormality of output destination data. Normally, the output function is stopped.
Indicates a state in which the input data status has become bad value (BAD) as a result of
the failure or disconnection of a detection terminal or process I/O device or the abnormality
High Input Open
IOP of input destination data. Normally, any processing that uses input signals is stopped. If the
Alarm
input signal has been overshot due to disconnection, etc., this alarm indicates a state in
which input is overshot to the high-limit direction.
Indicates a state in which the input signal has been overshot to the low-limit direction due
IOP- Low Input Open Alarm to disconnection, etc. The input data status becomes bad value (BAD). Normally, any
processing that uses input signals is stopped.
HH High High Alarm Indicates a state in which the process variable exceeds the high high-limit alarm setpoint.
LL Low Low Alarm Indicates a state in which the process variable falls below the low low-limit alarm setpoint.
HI High Alarm Indicates a state in which the process variable exceeds the high-limit alarm setpoint.
LO Low Alarm Indicates a state in which the process variable falls below the low-limit alarm setpoint.
Indicates a state in which the deviation between the process variable and the setpoint value
DV+ Deviation Alarm +
exceeds the deviation alarm setpoint in the positive direction.
Indicates a state in which the deviation between the process variable and the setpoint value
DV- Deviation Alarm -
exceeds the deviation alarm setpoint in the negative direction.
Indicates a state in which the change amount of the input signal within a specified time
VEL+ Velocity Alarm +
exceeds the velocity limit alarm setpoint in the positive direction.
Indicates a state in which the change amount of the input signal within a specified time
VEL- Velocity Alarm -
exceeds the velocity limit alarm setpoint in the negative direction.
Indicate a state in which the output signal almost exceeded the output high-limit value.
MHI Output High Alarm
The actual output is limited to the output high-limit value.
It indicates a state in which the output signal almost fell below the output low-limit value.
MLO Output Low Alarm
The actual output is limited to the output low-limit value.
Indicates a state in which a block mode of the function block in the I/O connection
Connection Failure destination is in the out of service (O/S) mode. This alarm controls a temporary out of
CNF
Alarm service state due to maintenance, and indicates a function block which is still in operation.
Normally, IOP or OOP occurs simultaneously.
C060301E.EPS

■ Alarm Status Common to Calculation Blocks
The alarm status for the operation and monitoring function is displayed in the data item
ALAM. When multiple alarms are occurring, the alarm status with the highest alarm display
priority will be displayed.
The priority for alarm display is as follows:
IOP>IOP->HH>LL>HI>LO>VEL+>VEL->CNF
The alarm status is NR if no alarm occurs.

Table Alarm Status Common to Calculation Blocks
the failure or disconnection of a detection terminal or process I/O device or the abnormality
IOP High Input Open Alarm of input destination data. Normally, any processing that uses input signals is stopped. If the
input signal has been overshot due to disconnection, etc., this alarm indicates a state in
which input is overshot to the high-limit direction.
Indicates a state in which the input signal has been overshot to the low-limit direction due
to disconnection, etc.
IOP- Low Input Open Alarm
The input data status becomes bad value (BAD). Normally, any processing that uses input
signals is stopped.
Indicates a state in which the calculated input value exceeds the high high-limit alarm
HH High High Alarm
setpoint.
Indicates a state in which the calculated input value falls below the low low-limit alarm
LL Low Low Alarm
setpoint.
HI High Alarm Indicates a state in which the calculated input value exceeds the high-limit alarm setpoint.
LO Low Alarm Indicates a state in which the calculated input value falls below the low-limit alarm setpoint.
Indicates a state in which the change amount of the calculated input value within a
VEL+ Velocity Alarm +
specified time exceeds the velocity limit alarm setpoint in the positive direction.
Indicates a state in which the change amount of the calculated input value within a
VEL- Velocity Alarm -
specified time exceeds the velocity limit alarm setpoint in the negative direction.
Indicates a state in which the block mode of a function block in the I/O connection
Connection Failure
CNF destination is in the out of service O/S) mode. This alarm controls a temporary out of
Alarm
service state due to maintenance, and indicates a function block which is still in operation.
Computation Error Indicates a state in which a computation error has occurred during a user-defined
CERR
Alarm calculation processing. Calculation processing is stopped.
C060302E.EPS
TIP
The one-shot processing initiated by one-shot start does not update the alarm status of the function
block.

■ Alarm Status Common to Sequence Control Blocks
Table Alarm Status Common to Sequence Control Blocks
Indicates that the block is in an output open state due to the disconnection of a process I/O
OOP Output Open
device of the output destination or other failure.
IOP Input Open the failure or disconnection of a detection terminal or process I/O device or the abnormality
of input destination data.
Indicates a state in which the block mode of a function block in the I/O connection
destination is in the out of service (O/S) mode.
CNF Connection Failure
This alarm controls a temporary out of service state due to maintenance, and indicates a
function block which is still in operation.
Computation Error
Indicates a state in which an illegal input pattern has occurred, such as when the full-open
PERR Answerback Undefined
and full-close signals are inputted simultaneously.
Alarm
Indicates a state in which answerback check is being performed and the manipulated output
ANS+ Answerback Error +
value (MV) of ON operation and the answerbacked process variable (PV) do not agree.
Indicates a state in which answerback check is being performed and the manipulated output
ANS- Answerback Error -
value (MV) of OFF operation and the answerbacked process variable (PV) do not agree.
C060303E.EPS
■ Alarm Status of Each Function Block

Different model of function block supports different alarm status.
SEE ALSO
• For more information about alarm status of regulatory control blocks, see D1.1.3, “Input Processing, Out-
put processing, and Alarm Processing Possible for Each Regulatory Control Block.”
• For more information about alarm status of calculation blocks, see D2.3.1, “Input Processing, Output pro-
cessing, and Alarm Processing Possible for Each Calculation Block.”
• For more information about alarm status of sequence control blocks, see D3.1.1, “Alarm Processing of
Sequence Control Blocks.”

<Toc> <Ind> <C6.4 Data Status> C6-32
C6.4 Data Status

▼ Data Status
Data status is the information that represents the quality of data. It is used for judg-
ing the proper operations according to the reliability of the data.
■ Data Status
Data status is the information that represents the reliability of data. The data obtained from
I/O module is passed from one function block to another with its data status information.
Data status is observed when various exceptional events occurred due to abnormality in
the process and it is helpful for making a proper decision for control operation.
Table Data Status (1/2)
Indicates a state in which a normal data value cannot be obtained. The data value stored
BAD BAD value when this status occurs may be a meaningless value or the last normal value which has
been stored.
Indicates that the data value is questionable and cannot be determined whether it is normal
or bad. The data value stored when this status occurs may be a value inputted from outside
QST QueSTionable value
while it is in the QST status, a manually set value using the CAL function, or the last
normal value which has been stored.
Indicates that when data is inputted or outputted through communication, the
NCOM No COMmunication communication has been disconnected and the data has not been updated.
Used only for I/O data that is exchanged with other control stations.
Indicates that the data value is not derived from a process I/O. The data value stored when
NFP Not From Process this status occurs may be a value inputted from outside while it is in the NFP status, a
calculated value, or a manually set value using the CAL function.
Indicates a state in which output is being disabled due to the abnormality of the block itself
or the output destination.
PTPF Path To Process Failed If the output destination is a PI/O, this status occurs when output open (OOP), not ready
(NRDY) or power failure has occurred. If the output destination is a function block, this
status occurs when the output destination block is in the out of service (O/S) mode.
Indicates that output is clamped at the high-limit value.
CLP+ CLamP high This status occurs when the block itself is limited by the output high limit or when the data
status of the output destination is clamp high (CLP+).
Represents that output is clamped at the low-limit value.
CLP- CLamP low This status occurs when the block itself is limited by the output low limit or when the data
status of the output destination is clamp low (CLP-).
Indicates that cascade connection is open.
This status occurs when a downstream function block changes to the non-cascade mode or
CND CoNDitional
the cascade connection path has been disconnected due to switching, etc. Used only for
data that is the object of cascade connection (MV, CSV, etc.)
Indicates a state in which the data value can be replaced manually as an emergency
CAL CALibration This status occurs when a downstream function block changes to the non-cascade mode or
value will not be updated until it is replaced manually.
Indicates a state in which the data value is invalid.
NEFV Not EFfecTive This is a state in which no setpoint value has been set manually after the CAL status was
obtained or the value is yet to be updated after the CAL status was turned off.
C060401E.EPS

<Toc> <Ind> <C6.4 Data Status> C6-33
Table Data Status (2/2)
Indicates that the function block of the I/O destination is in O/S mode. If the operation is
O/S Out of Service
input, the data value is not updated.
Indicates that the function block of the I/O destination is undergoing online maintenance.
If the operation is input, the data value is not updated. Normally, data reference is not
MNT MaiNTenance
performed while this data status in on, since online maintenance is performed as a group
between function block executions and data access processing.
Indicates that the process I/O of the input destination is in a high limit input open state due
IOP+ Input Open high to disconnection or other failure. The data value is not updated. The PV value is forcibly
set to a special value only when the PV overshoot function is activated.
Indicates that the process I/O of the input destination is in a low limit input open state due
IOP- Input OPen low to disconnection or other failure. The data value is not updated. The PV value is forcibly
set to a special value only when the PV overshoot function is activated.
Indicates that the process I/O of the output destination is in an output open state due to
OOP Output OPen
disconnection or other failure.
Indicates that the process I/O of the I/O destination is in an operation disabled state due to
NRDY PI/O Not ReaDY power failure, maintenance or a failure. If the operation is input, the data value is not
updated.
Indicates that the process I/O of the I/O destination is not responding due to power failure
PFAL PI/O Power FAiLure or other reason and is in an operation disabled state. If the operation is input, the data
value is not updated.
Indicates that the process I/O of the I/O destination has been non-responsive for a long time
PI/O Long Power
LPFL due to power failure or other reason and is in an operation disabled state. If the operation
FaiLure
is input, the data value is not updated.
Indicates that the upstream side of the cascade connection is in a state where a balance
MINT Master INiTialize
operation should be performed.
Indicates that the downstream side of the cascade connection is in a state where a balance
SINT Slave INiTialize
due to power failure or other reason and is in an operation disabled state. If the operation
Indicates that the downstream side of the cascade connection is in a state where the CSV
SVPB SV PushBack
should be made to match SV by the SV pushback operation.
C060402E.EPS

Blank Page
<Toc> <Ind> <C7. Process Timing> C7-1
C7. Process Timing

The function block executes a process in accordance with the process timing.
This chapter describes the process timing for the regulatory control block, the
sequence control block and the calculation block.
■ Process Timing
The process timing is a timing at which a function block executes a process. An individual
function block executes an input, a calculation or an output processing in accordance with
the process timing defined in.
There are four types of the process timing.
• Periodic Execution
This is repeatedly executed per preset period. The periodic execution can be used in
the regulatory control block, sequence control block, and calculation block.
• One-Shot Execution
This is executed only once when it is invoked from other function blocks. The one-shot
Execution can be used in the sequence control block and the calculation block.
• Initial Execution/Restart Execution
This is executed when the FCS executes the cold start or restart process. The initial
execution can be used in the sequence control block.
• Restricted Initial Execution
This is executed when the FCS executes the initial cold start process. The restricted
initial execution can be used in the sequence control block.

<Toc> <Ind> <C7. Process Timing> C7-2
■ Process Timing for Regulatory Control Block
The process timing for the regulatory control block is the periodic execution.
■ Process Timing for Calculation Block

There are following two types of the process timings for the calculation block.
■ Process Timing for Sequence Control Block

The process timing for the sequence control block has following four different types of
execution timing.

<Toc> <Ind> <C7.1 Process Timing for Regulatory Control Block> C7-3
C7.1 Process Timing for Regulatory Control Block

The process timing for the regulatory control block is the periodic execution.
■ Periodic Execution for Regulatory Control Block

The regulatory control block executes process repeatedly in a predetermined period.
Normally, these periodic execution function blocks execute per scan period.
The timing that individual function blocks activate as well as control drawings are deter-
mined by following factors in the periodic execution of the regulatory control block.
● Scan Period ¡
The scan period is period at which the function block is executed periodically. The periodic
execution function block executes a process based on the scan period.
There are two types of scan periods: the basic scan and the high-speed scan; each indi-
vidual function block can select one of the two types scan period. However, some function
blocks cannot be executed in high-speed scan.
● Scan Period £
The scan period is the period at which the function block is executed periodically. The
periodic execution function block executes a process based on the scan period.
There are three types of scan periods: the basic scan, the medium-speed scan (*1) and the
high-speed scan. One of these scan periods can be selected for each individual function
block. However, the medium-speed scan (*1) and high-speed scan cannot be selected for
some function blocks.
*1: £ The medium-speed scan setting is available only for the KFCS2, KFCS, LFCS2 or LFCS.
● Order of Process Execution

The order of process execution refers to a sequence in which the control drawing and
individual function block are executed in the periodic execution. The order of process
execution determines the execution timing of the control drawing and individual function
block within a scan period.
● Timing for Process I/O

The timing for the process I/O is a timing in which data input/output is executed between
the function block and the process I/O.
The timing for the process input/output differs from the type of input/output is analog or
contact.
● Control Period of Controller Block

Among the regulatory control blocks, the controller block has a control period that is depen-
dent on process timing. The control period of the controller block is a period in which control
calculation and output processing are executed when the controller block is performing
automatic operation (AUT, CAS, RCAS). The control period of the controller block is
always an integer multiple of the scan period.
The only processing that the controller block always performs for every scan period is input
processing and alarm processing. Control calculation and output processing during auto-
matic operation (AUT, CAS, RCAS) are performed during every control period.

C7.1.1 Scan Period

The periodic execution function block performs processing based on this scan
period.
■ Scan Period ¡
▼ Scan Period, Fast-Scan Period
The scan period determines a period for the periodic execution of the function block.
There are two scan period types: basic scan and high-speed scan.
● Basic Scan ¡
The basic scan is a standard scan period which is common to function blocks.
The basic scan period is fixed to 1 second. This cannot be changed.
● High-Speed Scan ¡
The high-speed scan is a scan period suited for the process control that requires high-
speed response.
Setting value of the high-speed scan can be selected by each FCS according to its use.
Setting value of the high-speed scan can be changed on system view:

• High-Speed Scan Period: Select “200 ms” or “500 ms.”
“50 ms” or “100 ms” can also be used by direct entry
from keyboard.
The default is “200 ms.”
● Set Scan Speed of Function Blocks ¡

Scan speed of function blocks can be set on the function block detail builder. Basic scan or
high-speed scan can be selected on the builder in accordance with requirement of re-
sponse time.
• Scan Period: Select “Basic Scan” or “High-speed Scan.”
The default setting is “Basic Scan.”
Note that “Basic Scan,” not “High-speed Scan,” should be set for the following function
blocks:
PID-TP, MC-2, MC-3, PG-L13, SLCD, SLPC, SLMC, SMST-111, SMST-121, SMRT, SBSD,
SLBC, SLCC, STLD, SI-1, SI-2, SO-1, SO-2, SIO-11, SIO-12, SIO-21, SIO-22, SIO-12P,
SIO22P, VLVM

■ Scan Period £
▼ Scan Period, Fast-Scan Period, Medium-Speed Scan Period
Scan period determines a period for the periodic execution of the function block.
There are three types of scan periods: basic scan, medium-speed scan (*1) and high-
speed scan.
● Basic Scan £
The basic scan is a standard scan period which is common to function blocks.
The basic scan period is fixed to 1 second. This cannot be changed.
● Medium-Speed Scan : KFCS2/KFCS/LFCS2/LFCS £

The medium-speed scan is a scan period suited for the process control that requires
quicker response than what can be achieved with the basic scan setting. Setting value of
the medium-speed scan can be selected by each FCS according to its use.
Setting value of the medium-speed scan can be changed on System View:

• Medium-speed scan period: Select “200 ms” or “500 ms.”
● High-Speed Scan £
The high-speed scan is a scan period suited for the process control that requires high-
speed response. Setting value of the high-speed scan can be selected by each FCS
according to its use.
Setting value of the high-speed scan can be changed on System View:

• High-speed scan period: Select “50 ms,” “100 ms,” “200 ms” or “500 ms.”
● Set Scan Speed of Function Blocks

Scan speed of function blocks can be set on the Function Block Detail Builder. Basic scan,
medium-speed scan or high-speed scan can be selected on the builder in accordance with
requirement of response time.
• Scan period: Select [Basic Scan], [Medium-speed Scan] (*1) or [High-speed
Scan.]
The default setting is [Basic Scan.]
Note that [Basic Scan], not [Medium-speed Scan] (*1) or [High-speed Scan], should be set
for the following function blocks:
PID-TP, MC-2, MC-3, PG-L13, SLCD, SLPC, SLMC, SMST-111, SMST-121, SMRT, SBSD,
SLBC, SLCC, STLD, SI-1, SI-2, SO-1, SO-2, SIO-11, SIO-12, SIO-21, SIO-22, SIO-12P,
SIO22P, VLVM
With certain function blocks, processing can be executed in a scan longer than the basic
scan by specifying the [Scan Coefficient] and [Scan Phase] parameters.

● Scan Coefficient, Scan Phase £
▼ Scan Coefficient, Scan Phase
When a scan coefficient is specified in addition to the scan period in the Function Block
Detail Builder, input indicator blocks (PVI), input indicator blocks with deviation alarm (PVI-
DV) and general-purpose calculation blocks (CALCU, CALCU-C) can be executed based
on their actual scan period being calculated as follows:
Actual scan period = Scan period • Scan coefficient
Scan coefficient: 1, 2, 4, 8, 16, 32 or 64
If the scan coefficient is represented by N, the function block is executed every N x scan
period.
In addition, when a scan phase is specified in the Function Block Detail Builder, in which of
the N times of scans the function block is executed can be defined. Specify the scan phase
using a numeric value in the following range:
Scan phase: 0 to ((Scan coefficient) - 1)

C7.1.2 Order of Process Execution

The order of process execution refers to a sequence in which the control drawing
and individual function block are executed in the periodic execution. The process
timing of a periodic execution regulatory function block is determined by the orders
of execution of the control drawings and the function blocks.
The following section describes the orders in which the control drawings and indi-
vidual function blocks are executed in the periodic execution.
■ Order of Process Execution for Control Drawings/Function Blocks ¡

The figure below shows an example of control drawings’ execution timing.
In the following example, there are three control drawings represented. Processing timing
of the function blocks with high-speed scan period in each drawing is indicated as A, B or C
and the processing timing to the function blocks with basic scan period in each drawing is
indicated as a, b or c. In the following figure, the processing to the function blocks at the
timing of A, B, C is referred to as “high-speed processing” and the processing to the func-
tion blocks at the timing of a, b, c is referred to as “basic processing.”
Basic scan (1 sec.)

High-speed
scan
Time
High-speed A B C ABC ABC ABC

processing
Basic processing a b b c ...... a b ......
......
Other process
Enlarged
b b Control drawing
1 2 3 4 5 Function block
C070101E.EPS
Figure Example of Control Drawings/Function Blocks Process Execution ¡

• The high-speed processing has priority over the basic processing.
• Once all function blocks of high-speed processing are completed to execute, the basic
processing is executed.
• In case that the high-speed processing gets its timing for execution during the basic
processing is being executed, the high-speed processing interrupts the basic process-
ing by making the basic processing pause at the gap among function blocks’ basic
processing.
• Once all function blocks of high-speed processing are completed to execute, the basic
processing is resumed from where it was interrupted.
• The high-speed processing of function blocks are executed for each of the control
drawings containing the function blocks and in the order of control drawing numbers.
Function blocks having the same scan period within the same control drawing are
executed in the set execution order (order of the function block numbers defined).
The basic processing of function blocks are executed in the same order as applied to
the high-speed processing.
• Processing of each function block is executed only once per single scan period.
• Other processes are executed in the idle time after the high-speed processing and
basic processing are completed.
● Idle Time in Processing at FCS ¡

▼ SEBOL/User C Ratio
The setting of the processing executed in the idle time in FCS’s CPU is defined in “SEBOL/
User C time ratio” on the FCS Constants Builder. This time ratio is set as “100 %” as de-
fault, means the total idle time of FCS’s CPU is used by SEBOL.
TIP
Each function block is executed asynchronously among the plural FCSes.

■ Order of Process Execution for Control Drawings/Function Blocks £
The diagram below shows an example of executing control drawings each consisting of
function blocks being executed in the high-speed scan, medium-speed scan (*) and basic
scan. In this example, three control drawings are processed. The groups of high-speed
scan function blocks in the respective drawings are indicated as A, B and C. Similarly, the
groups of medium-speed scan (*1) function blocks in the respective control drawings are
indicated as A’, B’ and C’; and the groups of basic scan function blocks, a, b and c. In the
diagram below and the explanation that follows, the processing of the function blocks
belonging to A, B and C is referred to as “high-speed processing”; processing of the func-
tion blocks belonging to A’, B’ and C’, “medium-speed processing” (*2); and processing of
the function blocks belonging to a, b and c, “basic processing.” “Other processing” indicates
processing of SFC blocks.
*1: £ The medium-speed scan setting is available only for KFCS2, KFCS, LFCS2 or LFCS.
*2: £ The medium-speed processing function is available only for KFCS2, KFCS, LFCS2 or LFCS.
Basic scan (1 sec.)
Medium-speed scan
High-speed scan
Time
High-speed A B C A B C A B C A B C A B C A B C
processing
Medium-speed A' B' C' A' B' C' C' A' B' C'
processing
Basic processing a a b b b c
Other processing Enlarged

b b Control drawing
123 4 5 Function block
C070102E.EPS
Figure Example of Control Drawings/Function Blocks Process Execution £

• The high-speed processing has priority over the medium-speed processing (*2) or
basic processing. The medium-speed processing (*2) has priority over the basic
processing.
• Once processing of all high-speed function blocks have been completed, the medium-
speed processing (*2) is executed.
When execution of all high-speed and medium-speed (*2) processes of function
blocks have been completed, the basic processing is executed.
• In case that the high-speed processing gets its timing for execution during the basic
processing or medium-speed processing (*2) is being executed, the high-speed
processing interrupts the basic processing or medium-speed processing (*2) by
making the basic processing or medium-speed processing (*2) pause at the gap
among function blocks' basic processing or medium-speed processing (*2). Once all
function blocks of high-speed processing are completed to execute, the basic pro-
cessing or medium-speed processing (*2) is resumed from where it was interrupted.
• In case that the medium-speed processing (*2) its timing for execution during the
basic processing is being executed, the medium-speed processing (*2) interrupts the
basic processing by making the basic processing pause at the gap among function
blocks' basic processing. Once all function blocks of medium-speed (*2) processing
are completed to execute, the basic processing is resumed from where it was inter-
rupted.
• The high-speed processing of function blocks are executed for each of the control
drawings containing the function blocks and in the order of control drawing numbers.
Function blocks having the same scan period within the same control drawing are
executed in the set execution order (order of the function block numbers defined).
The medium-speed processing (*2) and basic processing of function blocks are
executed in the same order as applied to the high-speed processing.
• Processing of each function block is executed only once per single scan period.
• Other processes are executed in the idle time after the high-speed processing, me-
dium-speed processing (*2) and basic processing are completed.
*2: £ The medium-speed processing function is available only for KFCS2, KFCS, LFCS2 or LFCS.
● Idle Time in Processing at FCS £

▼ SEBOL/User C Ratio
The setting of the processing executed in the idle time in FCS’s CPU is defined in “SEBOL/
User C time ratio” on the FCS Constants Builder. This time ratio is set as “100 %” as de-
fault, means the total idle time of FCS’s CPU is used by SEBOL.
TIP
Each function block is executed asynchronously among the plural FCSes.

C7.1.3 Timing of Process I/O

The timing of process I/O refers to the timing at which the data input/output is ex-
ecuted between the function block and the process I/O modules.
The timing of process I/O depends upon the type of the input/output data whether it
is analog or digital.
The following section explains the timing of process I/O.
■ Data Flow in Process I/O ¡ £

The flow of data in process input/output is different for analog data and for digital data. The
following section explains the data flow of each type.
● Analog Data ¡
For analog input/output signals, the I/O module and the function block exchange data via
the process I/O image in the main memory of processor unit.
The diagram below shows an image of analog data input/output processing.
Processor Unit
Function block
Read when the function block Write to Process I/O image when
starts the processing complete the processing
Process I/O image Main Memory
Read all at once at the beginning of Write only the changes when
the high-speedand basic scans processing of each function block
is completed
Analog I/O module
C070103E.EPS
Figure Image of Analog Data Input/Output ¡

● Analog Data : KFCS2/KFCS £
For analog input/output signals, the I/O module and the function block perform input/output
of data via the process I/O image in the main memory of processor unit.
Processor Unit
Function block
Read when the function block Write to Process I/O image

starts the processing when complete the processing
• KFCS2/KFCS: Read at the • KFCS2/KFCS: Write the changes

beginning of the basic scan the to I/O modules or EB401 when
analog input from the I/O unit or processing of all highest scan(*1)
EB401 which specified to be read function blocks is completed, as
by the basic scan: or read at the well as when processing of all
beginning of the highest scan the basic scan function blocks is
analog input from the I/O unit or completed.
EB401 which specified to ready
by the highest scan of FCS(*1)
Local Node
Remote Node Interface Card

Analog I/O modules
(EB401)
Refresh Periodically(*2)
Remote Node
Analog I/O modules
C070104E.EPS
*1: The Highest Scan of FCS means that if the FCS is applied with high-speed scan, the High-Speed Scan is the highest
scan, and otherwise the Medium-Speed Scan is. If the FCS is applied with basic scan only, the Basic Scan is the
highest scan of FCS.
*2: The period of analog I/O data refresh between EB401 and remote node varies with the number of remote nodes
connected.
Figure Image of Analog Data Input/Output : KFCS2/KFCS £

The period of data refresh between EB401 and remote nodes varies with the number of
remote nodes connected. The data refresh period corresponds to the number of nodes are
shown as follows.
Table Data Refresh Period between EB401 and IOM
Number of Remote Nodes
2 4 6
Analog I/O (None HART) 50 ms 100 ms 200 ms
Analog I/O (HART) 100 ms 200 ms 400 ms
HART Variables 1 to 2 seconds
C070105E.EPS
● Analog Data : LFCS2/LFCS/SFCS £

For analog input/output signals, the I/O module and the function block perform input/output
of data via the process I/O image in the main memory of processor unit.
Processor Unit
Function blocks
Read when the function block Write to Process I/O image

starts the processing when complete the processing
• SFCS: Read all data at once at • SFCS: Write the changes

the beginning of the high-speed when processing of each function
scans. block is completed.
• LFCS2/LFCS: Read at the beginning • LFCS2/LFCS: Write the changes
of the basic scan the analog input when processing of all high-speed
from the I/O unit which specified to scan function blocks is completed
be read by the basic scan: or read (or when processing of all medium-
at the beginning of the high-speed completed if the high-speed scan is
scan (or medium-speed scan if the not used) , as well as when
high-speed scan is not used) the processing of all basic scan
analog input from the I/O unit which function blocks is completed.
specified to ready by the high-speed
scan.
Analog I/O module
C070119E.EPS
Figure Image of Analog Data Input/Output : LFCS2/LFCS/SFCS £

● Contact I/O Data ¡
For contact input, the I/O module and the function block perform data input processing via
the process I/O image in the main memory of the processor unit and the contact input
image of the corresponding scan period stored in the data buffer areas.
Since the contact input data are stored in the image area, the function blocks which are
operated in the same period use the contact input’s image read at the beginning of that
scan period.
The diagram below shows an image of contact input data processing:
Processor Unit
Each function block of Each function block Contact input image

the high-speed scan of the basic scan common to stations
(data image for HIS)
Read when the

Contact input image Contact input image basic scan starts
for high-speed scan for basic scan the processing
Read when the Read when the

high-speed basic scan starts
scan starts the the processing
processing
Process I/O Image Main memory
Read all at once at the beginning

of the high-speed scans
Contact input module
C070106E.EPS
Figure Image of Contact Input Data Processing ¡

Also, in the case of contact output, the function blocks output data via the process I/O
image, which is in the processor unit main memory, to I/O modules.
The diagram below illustrates the digital data output processing.
Processor unit
High-speed scan Basic scan

function blocks function blocks
Write when function block Write when function block

processing is completed processing is completed
Process I/O image Main memory
Write the changes when processing of all

high-speed scan function blocks or all basic
scan function blocks is completed
Contact output module
C070107E.EPS
Figure Image of Contact Output Data Processing ¡

● Contact I/O Data : KFCS2/KFCS £
operated in the same period use the contact input’s image read at the beginning of that
scan period.
The diagram below shows an image of contact input data processing:
Processor Unit
Function blocks with Function blocks with Function blocks

high-speed scan the medium-speed scan with basic scan
Contact input image
common to stations
Contact input image Contact input image Contact input image
for high-speed scan for medium-speed scan for basic scan Read when the
basic scan starts
the processing
Read when the basic scan starts basic scan starts
high-speed the processing the processing
scan starts the
processing
• KFCS2/KFCS: Read at the beginning of the basic scan

the contact input from the I/O unit which specified to be
read by the basic scan; or read at the beginning of the
highest scan the contact input from the I/O unit which
specified to be read by the highest scan of FCS(*1)
Local Node

Contact Input Modules
(EB401)
Remote Node
Contact Input Modules
C070108E.EPS
scan of FCS, and otherwise the Medium-Speed Scan is. If the FCS is applied with basic scan only, the Basic Scan is
the highest scan of FCS.
*2: The period of contact I/O data refresh between EB401 and remote node varies with the number of remote nodes
connected.
Figure Image of Contact Input Data Processing : KFCS2/KFCS £

shown as follows.
2 4 6
Status Input 50 ms 100 ms 200 ms
ST Compatible (16-Point Input) 50 ms 100 ms 200 ms
Pushbutton Input 100 ms 200 ms 400 ms
C070109E.EPS
Also, in the case of contact output, the function blocks output data via the process I/O
image, which is in the processor unit main memory to the I/O modules.
The diagram below illustrates the contact output data processing.
Processor unit
High-speed scan Medium-speed scan Basic scan

function blocks function blocks function blocks
Write when function Write when function Write when function

block processing block processing block processing
is completed is completed is completed
• KFCS2/KFCS: Write the changes when

processing of all highest-speed scan function
blocks is completed (*1)
Local Node

Contact Output Modules
(EB401)
Remote Node
Contact Output Modules
C070110E.EPS
scan of FCS, and otherwise the Medium-Speed Scan is. If the FCS is applied with basic scan only, the Basic Scan is
the highest scan of FCS.
*2: The period of contact I/O data refresh between EB401 and remote node varies with the number of remote nodes
connected.
Figure Image of Contact Output Data Processing : KFCS2/KFCS £

shown as follows.
2 4 6
Status Output 50 ms 100 ms 200 ms
Pulse-Width Output (*1) 100 ms 200 ms 400 ms
ST Compatible (64-Point Output) 200 ms 400 ms 800 ms
C070111E.EPS
*1: The pulse-width output between IOM and field devices behaves differently, the output timing is controlled in the output
module.
● Contact I/O Data : LFCS2/LFCS/SFCS £

operated in the same period use the contact input's image read at the beginning of that
scan period.
The diagram below shows an image of digital data input processing:
Processor Unit
Function blocks with

Function blocks with the medium-speed scan Function blocks
high-speed scan (applicable only with with basic scan
the LFCS)
Contact input image
common to stations
Contact input image Contact input image Contact input image
for high-speed scan for medium-speed scan for basic scan Read when the
basic scan starts
the processing
Read when the basic scan starts basic scan starts
high-speed the processing the processing
scan starts the
processing
• SFCS: Read all data at once at the beginning of the

high-speed scans.
• LFCS2/LFCS: Read at the beginning of the basic scan
the contact input from the I/O unit which specified to be
read by the basic scan; or read at the beginning of the
high-speed scan (or medium-speed scan if the high-
speed scan is not used) the contact input from the I/O
unit which specified to be read by the high-speed scan
Contact Input Module
C070120E.EPS
Figure Image of Contact Input Data Processing : LFCS2/LFCS/SFCS £

Also, in the case of contact output, the function block and I/O module output data via the
process I/O image, which is in the processor unit main memory.
The diagram below illustrates the contact output data processing.
Processor unit
Medium-speed scan
High-speed scan function blocks Basic scan
function blocks (applicable only with function blocks
the LFCS)
Write when function Write when function Write when function
block processing block processing block processing
is completed is completed is completed
• SFCS: Write the changes when processing of

all high-speed scan function blocks or all basic
scan function blocks is completed
• LFCS2/LFCS: Write only the changes when
processing of all high-speed scan function
blocks is completed (or when processing of all
medium-
speed scan function blocks is completed if the
high-speed scan is not used), as well as when
processing of all basic scan function blocks is
completed
Contact Output Module
C070121E.EPS
Figure Image of Contact Output Data Processing : LFCS2/LFCS/SFCS £

■ Timing of Process I/O ¡
The following section describes the timing of process I/O.
● Input Timing ¡
The input signals are read from the input module to the process I/O image in the processor
unit, then to the contact input image in which they are grouped according to their scan
period in the data buffer area. All the input data are accessed all together at the beginning
of each “high-speed processing” scan.
The accessed data may be applied to either high scanned function blocks or basic scanned
function blocks.
The function blocks perform their input and calculation process to the data they read from
the process I/O image.
Basic scan (1 sec.)

High-speed
scan
Time
High-speed
ABC ABC ABC AB
processing
Basic processing a b b c ...... ...... d e
Enlarged
b b Control drawing
1 2 3 4 5 Function block : High-speed scan processing start

: Basic scan processing start
C070112E.EPS
Figure Input Timing ¡

● Output Timing ¡
The function blocks write output data to the specified area in the process I/O image when
the function blocks are executed. Of the data written to the process I/O image, only the
changes are written to the output module at the following timing:
• The contact output data is written when processing of all high-speed scan function
blocks or all basic scan function blocks is completed.
• The analog output data are written at the end of each function block’s processing.
Basic scan (1 sec.)

High-speed
scan
Time
High-speed
ABC ABC ABC AB
processing
Enlarged
b b Control drawing
1 2 3 4 5 Function block : High-speed scan processing end

: Basic scan processing end
C070113E.EPS
Figure Output Timing ¡

■ Timing of Process I/O £
Timing of Process I/O is explained in the following section.
● Input Timing : KFCS2/KFCS £

The processor reads the input data from local nodes or from the remote node communica-
tion interface card (EB401) and puts the data into processor unit memory image table at the
following timings.
The input data of remote nodes are acquired periodically by EB401 card. The input data
from EB401 to memory image table are the data that EB401 periodically acquired from the
remote nodes.
KFCS2 or KFCS:
• For the I/O modules not defined with high-speed scan, data are accessed at the
beginning of basic processing scan period.
• For the I/O modules defined with high-speed scan or medium-speed scan, data are
accessed at the beginning of highest processing scan period.
The highest scan period means that if the FCS is applied with High-Speed scan, the
High-Speed scan is the highest scan of FCS, and otherwise the Medium-Speed scan
is. If the FCS is applied with basic scan only, the basic scan is the highest scan period.
Moreover, for contact I/O data, the I/O data are sent to the image tables categorized in
accordance with the scan periods. The timings of accessing these I/O data are the begin-
nings of the corresponding scan periods.
Function blocks perform input processing, calculation processing to the analog data ac-
quired from process I/O image. While the function blocks perform input processing, calcula-
tion processing to the contact input data acquired from the I/O images of various scan
periods.

● Input Timing : LFCS2/LFCS/SFCS £
The input signals are read from input module to the process I/O image in the processor
unit, then to the contact input image in which they are grouped according to their scan
period in the data buffer area, at the following timing:
LFCS2 or LFCS:
• The input from the I/O module which specified to be read by the high-speed scan is
read when the high-speed scan processing of the function block is started (or when
the medium-speed scan processing is started if the high-speed scan is not used).
• The input from the I/O module which specified to be read by the basic scan is read
when the basic scan processing of the function block is started.
SFCS:
• Access data at the beginning of each “high-speed processing” scan.
The accessed data may be applied to either high scanned function blocks or basic
scanned function blocks.
The function blocks perform their input and calculation process to the data they read from
the process I/O image.
Basic scan (1 sec.)

High-speed
scan
Time
High-speed A B C ABC ABC AB

processing
Enlarged
b b Control drawing
1 2 3 4 5 Function block : High-speed scan processing start

: Basic scan processing start
C070114E.EPS
Figure Input Timing £

● Output Timing : KFCS2/KFCS £
▼ Output Type – Output in a Lump, Output Type – Output Immediately
Function blocks send their output data to process I/O image at the time of the function
blocks performing output processing.
The output data changes in the process I/O image are written to the local nodes or remote
node interface card (EB401) at the following timings.
The output data in the EB401 sent from process I/O image are periodically written to
remote nodes.
For analog output in KFCS2 or KFCS:
• The timings for writing the output data in process I/O image to I/O modules vary with
the designated options [Output in a Lump] and [Output immediately].
When option [Output in a Lump] is designated, the output data are written from pro-
cess I/O image to I/O modules at the completion of the highest scan of function
blocks.
When option [Output Immediately] is designated, the output data are written from
process I/O image to I/O modules right after the data are outputted from the function
blocks.
For contact output in KFCS2 or KFCS:
• The contact output data are written from process I/O image to I/O modules at the
completion of the highest scan of function blocks.
The highest scan period means that if the FCS is applied with High-Speed scan, the High-
Speed scan is the highest scan of FCS, and otherwise the Medium-Speed scan is. If the
FCS is applied with basic scan only, the basic scan is the highest scan period.
IMPORTANT
When option [Output immediately] is designated, it takes 1 or 2 milliseconds of processor
unit to perform the task of writing from process I/O image to I/O modules, thus the CPU
load is added.
It is recommended to choose [Output in a Lump] option instead of choosing [Output imme-
diately] option unless it is necessary. With [Output in a Lump] option, the output data can
also be sent from process I/O image to I/O modules at high-speed scan period if the high-
speed scan is specified.
TIP
For Flow-totalizing batch set block (BSETU-2) and Weight-totalizing batch set block, if the output auto-
matic prediction is applied, the output data are written from the function block to I/O modules or EB401 at
the predicted time.
Furthermore, it may take up to 30 milliseconds more time for outputting to the I/O modules in the remote
nodes.

● Output Timing : LFCS2/LFCS/SFCS £
The function blocks write output data to the specified area in the process I/O image when
being executed. Of the data written to the process I/O image, only the changes are written
to the output module at the following timing:
LFCS2 or LFCS analog output/contact output:

• When processing of all high-speed scan function blocks (or all medium-speed scan
function blocks if the high-speed scan is not used) is completed.
• When processing of all basic scan function blocks is completed.
SFCS analog output:

• When processing of each function block is completed.
SFCS contact output:

• When processing of all high-speed scan function blocks (or all medium-speed scan
function blocks if the high-speed scan is not used) is completed.
• When processing of all basic scan function blocks is completed.
Basic scan (1 sec.)

High-speed
scan
Time
High-speed
ABC ABC ABC AB
processing
Enlarged
b b Control drawing
1 2 3 4 5 Function block : High-speed scan processing end

: Basic scan processing end
C070115E.EPS
Figure Output Timing : LFCS2/LFCS/SFCS £

C7.1.4 Control Period for Controller Block

Among the regulatory control blocks, the controller block has control period that is
dependent on process timing. The control period of the controller block is a time
period that the controller block executes control calculation and output processing
during automatic operation (AUT, CAS, RCAS). The control period of the controller
block is always an integer multiple of the scan period.
The only processing that the controller block always performs for each scan period
is input processing and alarm processing. Control calculation and output process-
ing are performed once per each control period.
■ Control Period of Controller Block

▼ Control Period
The controller block executes the input processing per scan period. However, the control
calculation and output processing are executed per each control period.
The control period of controller block is always an integer-multiple of the scan period.
There are 2 types of the control periods of controller block as shown below:
• The control period of the regulatory control action.
• The control period of the intermittent control action.
● Control Period of Regulatory Control Action

Control calculation is executed at every control period in regulatory control action.
The figure below shows the controller block’s control period in the regulatory control action.
MV
Control
period
Scan period
Time
C070116E.EPS
Figure The Control Period in the Regulatory Control Action

● Control Period in Intermittent Control Action
In intermittent control action, control calculation and output processing are executed only
once in the scan period in which the control switch (CSW) is turned ON during the auto-
matic operation (AUT, CAS, RCAS). After the execution, the control switch (CSW) is turned
OFF. The control switch (CSW) can be set to ON by other function blocks such as the
sequence control blocks.
The figure below shows the control period of the controller block in the intermittent control
action.
MV
Control
period
: Scan period in which

CSW is turned ON
Scan period : Time in which CSW is turned ON
Time
C070117E.EPS
Figure The Control Period of the Intermittent Control Action
The intermittent control action is used for the sampling control with a sampling value to be
measured at the timing determined by outside of the controller block.

■ Setting for Control Period of Controller Block
The following section describes the method of setting the control period of a controller
block, and how the function block behaves for the different settings.
● Setting for Control Period of Controller Block

Setting for control period of controller block can be defined in the Function Block Detail
Builder.
• Control period:
Select from “fixed control period,” “automatic determination” or “intermittent control
action.”
In the case of the Blending PI Controller Block (PI-BLEND) or the sampling PI control-
ler block (PI-HLD), select from “fixed control period” or “automatic determination.”
The default is “automatic determination.”
TIP
The control period for the two-position ON/OFF controller block (ONOFF), three-position ON/OFF
controller block (ONOFF-G) and the PD Controller Block with Manual Reset (PD-MR) is the same as the
scan period.
The fixed control periods is selected from the following:

1, 2, 4, 8, 16, 32 or 64 seconds.
When the automatic determination is selected, the control period is decided by the follow-
ing rules:
Table Control Period at the Automatic Determination
Control Period (Sec.)
Integral Time (Sec.)
Basic Scan High-Speed Scan
1 to 31 1
32 to 63 2
64 to 255 4
Same as the scan period
256 to 1023 8
1024 to 2047 16
2048 to 10000 32
C070118E.EPS
When the fixed control period or the automatic determination is selected, it is operated with
the control period of the regulatory control action. When the intermittent control action is
selected, it is operated with the control period of the intermittent control action.

● Action of Controller Block Based on Control Period
Based on the control period defined, the controller blocks are executed as follows:
• When a fixed control period is selected
The control calculation processing and output action during the automatic operation
(AUT, CAS, RCAS) are executed with the preset fixed control period.
• When the automatic determination is selected
If the scan period is the basic scan, the control period is determined automatically
according to the parameter of the integral time (I). If the scan period is the high-speed
scan, the control period is the same as the scan period.
• When an intermittent control action is selected
The control calculation and output processings are executed only once with the scan
period in which the control switch (CSW) is turned ON during the automatic operation
(AUT, CAS, RCAS).

<Toc> <Ind> <C7.2 Process Timing of Calculation Block> C7-30
C7.2 Process Timing of Calculation Block

The process timing for the calculation block has the following two execution types
according to execution timing.
■ Periodic Execution
▼ Start Timing
The periodic execution means that the calculation block is repeatedly executed in a preset
cycle. The function blocks for which a periodic execution is defined is referred as the
periodic-execution type function block.
Normally, the periodic-execution type function block is executed per scan period.
The timing that the control drawings and the individual function blocks are executed by the
periodic execution of calculation block is determined by following factors.
● Scan Period ¡
The scan period refers to a period at which the function block is executed periodically. The
periodic execution function block executes a process based on the scan period.
There are 2 types of scan periods: the basic period and the high-speed period; each
individual function block can select one of the 2 types scan period. However, some function
blocks cannot execute in high-speed period.
SEE ALSO
See a chapter C7.1.1, “Scan Period” for the scan period.
● Scan Period £
The scan period is a period of periodic execution for a function block. The periodic execu-
tion function block executes a process based on the scan period.
There are three types of scan periods: basic scan, medium-speed scan (*1) and high-
speed scan. Select one of these scan periods for each function block. However, the me-
dium-speed scan (*1) and high-speed scan cannot be selected for some function blocks.
SEE ALSO
*1: £ The medium-speed scan setting is available only for KFCS2, KFCS, LFCS2 and LFCS.

individual function block are executed in the periodic execution. This order of process
execution determines the execution timing within a scan period of the control drawing and
individual function block.
SEE ALSO
See a chapter C7.1.2, “Order of Process Execution” for the order of process execution.
● Timing of Process I/O

The timing of the process input/output refers to a timing at which data I/O is executed
between the function block and the process I/O.
The timing of the process I/O differs by whether the input/output data is analog or contact
type.
SEE ALSO
See a chapter C7.1.3, “Timing of Process I/O” for the process input/output timing.

■ One-Shot Execution ¡ £
In one-shot execution, the calculation block is executed only once when it is invoked by
other function blocks. The function block defined with one-shot execution is referred as the
one-shot-execution (O) type function block.
When an one-shot function block is invoked by other function blocks in the same FCS, it
starts its own process with interrupting the process from which it was invoked. When the
one-shot block’s process is completed, it hands back the process to the block from which it
was invoked. The sequence control block cannot be invoked from other control stations.
The following diagram shows the one-shot processing:
Time
The calling source Process execution

Process execution
function block
Call Process resumption
Process
Execution completion
One-shot-execution-type
Process execution
function block
C070301E.EPS
Figure One-Shot Execution Conceptual Diagram
The one-shot execution is used when a calculation block is invoked from a sequence table
block.

The following table lists the calculation blocks where one-shot start is possible.
Table Calculation Blocks in Which One-Shot Execution is Possible ¡ £
Block type Type Name
ADD Addition Block
MUL Multiplication Block
Arithmetic calculations
DIV Division Block
AVE Averaging Block
AND Logical AND Block
OR Logical OR Block
NOT Logical NOT Block
SRSI-S Set-Dominant Flip-Flop Block with 1 Output
SRSI-R Reset-Dominant Flip-Flop Block with 1 Output
SRS2-S Set-Dominant Flip-Flop Block with 2 Outputs
SRS2-R Reset-Dominant Flip-Flop Block with 2 Outputs
Logic operation (*1)
WOUT Wipeout Block
GT Comparator Block (Greater Than)
GE Comparator Block (Greater Than or Equal)
EQ Equal Operator Block
BAND Bitwise AND Block
BOR Bitwise OR Block
BNOT Bitwise NOT Block
CALCU General-Purpose Calculation Block
General-purpose
calculations General-Purpose Calculation Block (with character string data I/O
CALCU-C
terminal)
BDSET-1L One-Batch Data Set Block
BDSET-1C One-Batch String Data Set Block
BDSET-2L Two-Batch Data Set Block
Auxiliary calculations
BDSET-2C Two-Batch String Data Set Block (strings only)
BDA-L Batch Data Acquisition Block
BDA-C Batch String Data Acquisition Block
C070302E.EPS
*1: ¡ £ The logic operation blocks can be used only for the CS 3000.
TIP
When a calculation block is executed based on one-shot specification, the alarm status is not updated
during the one-shot processing.

■ Setting for Processing Timing ¡
Setting for processing timing can be defined in the Function Block Detail Builder.
• Execution timing:
Select from “0 (periodic execution)” or “1 (one-shot execution).”
The default is 0.
When the periodic execution is selected for execution timing, set a scan period in the
Function Block Detail Builder. There are two types of scan periods: the basic scan and the
high-speed scan.
■ Setting for Processing Timing £

Setting for processing timing can be defined in the Function Block Detail Builder.
• Execution timing:
Select from “0 (periodic execution)” or “1 (one-shot execution).”
The default is 0.
When the periodic execution is selected for execution timing, set a scan period in the
function block detail definition builder. There are three types of scan periods: basic scan,
medium-speed scan (*1) and high-speed scan.

<Toc> <Ind> <C7.3 Process Timing for Sequence Control Block> C7-35
C7.3 Process Timing for Sequence Control Block

This section explains the process timing of a sequence control block.
Process timing for a Sequence Table Block (ST16, ST16E) and logic chart block
(LC64) includes the execution timing, output timing subordinated to execution
timing, control period, and control phase.
■ Start Timing of Sequence Control Block

▼ Processing Timing
A sequence control block and a logic chart block have the following four types of execution
timing:
• Periodic Execution (T)
• One-Shot Execution (O)
• Initial Execution/Restart Execution (I)
• Restricted Initial Execution (B)
■ Output Timing of Sequence Control Block

The output timing of sequence control block and logic chart block indicates the conditions
to execute the output processing when the sequence table is started periodically or as a
one shot.
There are two types of output timing as below:
• Output only when conditions change (C)
• Output each time conditions are satisfied (E)
The output timing of function blocks excluding sequence control blocks is “Output each
time conditions are satisfied (E).”
■ Combining Execution Timing and Output Timing

The execution timing and the output timing can be used in combination.
■ Control Period and Control Phase of a Sequence Control Block

The control period is a period at which Periodic Execution Type (T) sequence tables and
logic charts are executed. The control phase is the timing for performing sequence table
processing during a control period.
The control period and control phase of a sequence table and a logic chart are used when
the sequence table and a logic chart are executed using a period longer than the basic
scan for periodic execution.

C7.3.1 Execution Timing for Sequence Control Blocks

The sequence control block is executed at the timing defined, then it performs data
input processing. After the input processing, it executes processes such as the
control calculation processing and output processing.
There are four types of execution timing to start the sequence control block
■ Periodic Execution (T)

▼ Scan Period
The periodic execution means that the sequence control block is repeatedly executed in a
preset cycle. The function block for which a periodic execution is defined is referred as the
periodic-execution (T) type function block.
The timing that the control drawings and individual function blocks are executed by the
periodic execution is determined by following factors.
● Scan Period ¡
The scan period is a period of periodic execution for a function block. The periodic-execu-
tion function block performs the processing based on the scan period.
There are two types of scan periods: the basic scan (S) and the high-speed scan. In the
periodic execution type sequence table block and logic chart block, basic scan (S) or high-
speed scan (H) can be selected as the scan period.
SEE ALSO
● Scan Period £
The scan period is a time period of periodic execution for a function block. The periodic
execution function block executes a process based on the scan period.
There are three types of scan periods: basic scan (S), medium-speed scan (M) (*1) and
high-speed scan (H). In the periodic-execution-type sequence table block and logic chart
block, the basic scan (S), medium-speed scan (M) (*1) or high-speed scan (H) can be
selected as the scan period.
SEE ALSO

individual function block are executed in the periodic execution. The execution timing within
a scan period of the control drawing and the individual function block is determined by the
order of the execution.
SEE ALSO
See a chapter C7.1.2, “Order of Process Execution” for the order of process execution.
● Timing of Process I/O

The timing of process input/output refers to a timing at which data input/output is executed
between the function block and the process I/O.
The timing of process I/O differs by whether the input/output data is analog or contact type.
SEE ALSO
See a chapter C7.1.3, “Timing of Process I/O” for the process input/output timing.

■ One-Shot Execution (O)
In one-shot execution, sequence block is executed only once when it is invoked by other
function blocks. The function block defined with one-shot execution is referred as the one-
shot-execution (O) type function block.
When an one-shot function block is invoked by other function blocks in the same FCS, it
starts its own process with interrupting the process from which it was invoked. When the
one-shot block’s process is completed, it hands back the process to the block from which it
was invoked. The sequence control block cannot be invoked from other control stations.
The following diagram shows the one-shot processing:
Time
The calling source Process execution

Process execution
function block
Call Process resumption
Process
Execution completion
One-shot-execution-type
Process execution
function block
C070201E.EPS
Figure One-Shot Processing Conceptual Diagram
A one-shot function block can invoke another one-shot function block. However, such
succession is limited to seven blocks.
The one-shot processing is used when a function block is executed from a sequence
control block.

■ Initial Execution/Restart Execution (I)
In initial execution/restart execution, the sequence block executes its process when the
FCS performs a cold start or a restart. The function blocks only work in such timing are
referred as the initial-cold start/restart execution (I) style function block.
■ Restricted Initial Execution (B)

In restricted initial execution (B), the sequence control block executes only when the FCS
performs a cold start, not include restart. The function blocks only work in such timing are
referred as the initial-cold start (B) style function block.
■ Setting for Execution Timing

Setting for execution timing can be defined in the Function Block Detail Builder.
• Execution Timing:
Select from the “Periodic Execution (T),” “One-Shot Execution (O),” “Initial Execution/
Restart Execution (I),” or “Restricted Initial Execution (B).”
When the periodic execution (T) is selected for execution timing, set a scan period in the

C7.3.2 Output Timing of Sequence Table Blocks (ST16, ST16E)

The output timing of a sequence table block indicates the conditions under which
output processing is performed when the sequence table is executed periodically or
as a one shot.
The two types of output timing are given below.
• Output only when conditions are changed (C)
• Output each time conditions are satisfied (E)
■ Output Only when Conditions are Changed (C)

The ST16, ST16E blocks output an operation signal only at the timing when the judged
conditions are changed from unsatisfied to satisfied. The “output only when conditions are
changed” can only be specified for ST16, ST16E blocks with periodic execution (T) or one-
shot start (O).
■ Output Each Time Conditions are Satisfied (E)

The ST16, ST16E blocks output an operation signal every scan period as long as the
judged conditions are satisfied.
■ Setting for Execution Timing

The output timing can be defined in the Function Block Detail Builder.
• Output timing:
Select from “Output only when conditions are change” or “Output each time conditions
are satisfied.”

C7.3.3 Output Timing of a LC64 Logic Chart Block

Output timing of logic chart block shows output conditions when the logic chart
block starts by Periodic/One-shot Execution. “Each Time Conditions are Satisfied
(E)” can only be selected as output timing.
■ Output Each Time Conditions are Satisfied (E)

The LC64 Logic Chart Block outputs operation signals by scan period if the specified
conditions are satisfied.
IMPORTANT
• Manipulated output is sent from the logic chart block every cycle. If the output data
(ex. Printout messages) is not necessary every cycle, change output timing to output
only when logical operators are changed.
• When the logic chart block starts by one-shot processing, do not use time data in
internal logical operation. For example, if on-delay timer were used, output is in the
initial state.
• Internal logic operators are reset upon recovery from O/S upon online maintenance.

C7.3.4 Combination of Execution Timing and Output Timing

The following section describes combinations of the execution and output timings.
■ Combination of Execution Timing and Output Timing of Sequence Table

Blocks (ST16, ST16E)
The table below shows all possible combinations of the execution timing and the output
timing of the sequence tables.
Combinations not listed here are not allowed. The default combination is TC.
Table Combination of Execution Timing and Output Timing of Sequence Tables
Execution Timing Output Timing Symbol
Conditional Output (C) TC
Periodic Execution (T)
Each time Output (E) TE
Conditional Output (C) OC
One-Shot Execution (O)
Each time Output (E) OE
Startup at Initial Cold Start/Restart (I) - I
Restricted Initial Execution (B) - B
C070202E.EPS
■ Combination of Execution Timing and Output Timing of Logic Chart

Block (LC64)
The execution timing and the output timing of the logic chart block can be used with the
following. No other combination is allowed. The default is T.
Table Combination of Execution Timing and Output Timing of Logic Chart Block
Execution Timing Output Timing Symbol
Periodic Execution (T) Each time (E) TE
One-Shot Execution (O) Each time (E) OE
Startup at Initial Cold Start/Restart - I
Restricted Initial Execution (B) - B
C070204E.EPS

C7.3.5 Control Period and Control Phase for Sequence Table

For the periodic execution (T) type ST16 and ST16E blocks, the control period and
control phase can be set by the Function Block Detail Builder. However, the control
period and control phase can only be set when the scan period is set to the basic
scan (S).
■ Control Period for Sequence Table Blocks (ST16, ST16E)

The control period for the ST16, ST16E blocks refers to the interval at which the periodic-
execution-type ST16 or ST16E block executes the sequence table.
The control period can be set in the Function Block Detail Builder.
• Control period: Set a value between 1 and 16 seconds.
Default is 1 second.
■ Control Phase for Sequence Table Blocks (ST16, ST16E)

The control phase for the ST16, ST16E blocks refers to the timing at which the sequence
table is executed in the control period. It sets the execution timing relative to the execution
timing of the phase-zero sequence table.
The control phase can be set in the Function Block Detail Builder.
• Control phase: Set a value between 0 and 15 seconds.

■ Example of Control Period and Control Phase for Sequence Table
For example, in case of that a ST16 or ST16E block’s control period is 5 sec. and control
phase is 3 sec., the ST16 or ST16E block is executed at every 5 seconds interval, 3 sec-
onds after the phase zero’s ST16 or ST16E block.
The following execution timing diagram shows the execution timing in case of the control
period and control phase are set.
Execution
Time elapsed
Control
Phase
period 0 1 2 3 4 5 6 7 8 9 10 11 sec
1 0
0
2
1
3 1
1
4
2
5 2
C070203E.EPS
Figure Control Period and Phase for Sequence Table Block (ST16, ST16E)

C7.3.6 Control Period and Control Phase for Logic Chart Block
(LC64)
The control period and control phase of periodic execution type (T) LC64 block can
be set on the Function Block Detail Builder when the scan period is set to “Basic
Scan (S).”
■ Control Period for Logic Chart Block (LC64)

A control period is defined as a period at which the LC64 periodic execution type logic chart
block executes logic charts. Define the control period on the Function Block Detail Builder.
• Control Period: Set a value between 1 to 16 seconds.
The default is 1.
■ Control Phase for Logic Chart Block (LC64)

A control phase is defined as a timing when logic charts start within control periods. Define
start timing relative to phase 0 logic chart start timing on the Function Block Detail Builder.
• Control Phase: Set a value between 1 to 15 seconds.
The default is 0.

Blank Page
<Int> <Ind> <Rev> <Document Map> <Reference Map> Toc D-1
CS 1000/CS 3000
Reference
Function Block Details
IM 33S01B30-01E 8th Edition
CONTENTS
PART-D Function Block Details
D1. Regulatory Control ............................................................................... D1-1
D1.1 Regulatory Control Blocks ........................................................................... D1-2
D1.1.1 Types of the Regulatory Control Blocks........................................... D1-4
D1.1.2 I/O Data Handled by the Regulatory Control Blocks ........................ D1-7
D1.1.3 Input Processing, Output Processing, and Alarm Processing
Possible for Each Regulatory Control Block .................................. D1-12
D1.1.4 Valid Block Modes for Each Regulatory Control Block ................... D1-19
D1.2 Input Indicator Block (PVI) ......................................................................... D1-21
D1.3 Input Indicator Block with Deviation Alarm (PVI-DV) ................................ D1-23
D1.4 Control Computation Processing Common to Controller Blocks ........... D1-27
D1.5 PID Controller Block (PID) .......................................................................... D1-59
D1.6 Sampling PI Controller Block (PI-HLD) ...................................................... D1-71
D1.7 PID Controller Block with Batch Switch (PID-BSW) ........................... D1-81
D1.8 Two-Position ON/OFF Controller Block (ONOFF) ..................................... D1-89
D1.9 Three-Position ON/OFF Controller Block (ONOFF-G) .............................. D1-95
D1.10 Time-Proportioning ON/OFF Controller Block (PID-TP) ......................... D1-103
D1.11 PD Controller Block with Manual Reset (PD-MR) .................................... D1-111
D1.12 Blending PI Controller Block (PI-BLEND) ................................................ D1-119
D1.13 Self-Tuning PID Controller Block (PID-STC) ............................................ D1-132
D1.13.1 Control Algorithm of Self-Tuning PID Controller Block (PID-STC) .... D1-139
D1.13.2 Self-Tuning Function (STC Function) .......................................... D1-140
D1.13.3 Self-Tuning Operating Modes ..................................................... D1-143
D1.13.4 Initializer Start ............................................................................. D1-148
D1.13.5 Auto-Startup ............................................................................... D1-149
D1.13.6 On-Demand Tuning .................................................................... D1-154
D1.13.7 Tuning Parameters of Self-Tuning PID Controller Block
(PID-STC) ................................................................................... D1-156
D1.13.8 Points of Using Self-Tuning PID Controller Block (PID-STC) ...... D1-169
D1.14 Manual Loader Block (MLD) ..................................................................... D1-182
D1.15 Manual Loader Block with Input Indicator (MLD-PVI) ............................. D1-184
D1.16 Manual Loader Block with Auto/Man SW (MLD-SW) ............................... D1-187

D1.17 Motor Control Blocks (MC-2, MC-3) ......................................................... D1-201
D1.17.1 Input Processing of Motor Control Block (MC-2, MC-3) .............. D1-207
D1.17.2 Control Computation Processing of Motor Control Blocks
(MC-2, MC-3) .............................................................................. D1-211
D1.17.3 Output Processing of Motor Control Blocks (MC-2 and MC-3) ..... D1-226
D1.17.4 Alarm Processing of Motor Control Blocks (MC-2, MC-3) ............ D1-244
D1.18 Ratio Set Block (RATIO) ............................................................................ D1-247
D1.19 13-Zone Program Set Block (PG-L13) ...................................................... D1-267
D1.20 Totalizing Batch Set Blocks (BSETU-2, BSETU-3) .................................. D1-279
D1.20.1 Input Processing of Totalizing Batch Set Blocks
(BSETU-2, BSETU-3) ................................................................. D1-280
D1.20.2 Control Algorithm of Totalizing Batch Set Blocks
(BSETU-2, BSETU-3) ................................................................. D1-281
D1.20.3 Output Processing of Totalizing Batch Set Blocks
(BSETU-2, BSETU-3) ................................................................. D1-297
D1.20.4 Alarm Processing of Totalizing Batch Set Blocks
(BSETU-2, BSETU-3) ................................................................. D1-302
D1.21 Flow-Totalizing Batch Set Block (BSETU-2) ............................................ D1-305
D1.22 Weight-Totalizing Batch Set Block (BSETU-3) ........................................ D1-316
D1.22.1 Input Signal Conversion of Weight-Totalizing Batch Set Block
(BSETU-3) .................................................................................. D1-322
D1.22.2 Alarm Processing of Weight-Totalizing Batch Set Block
(BSETU-3) .................................................................................. D1-327
D1.23 Velocity Limiter Block (VELLIM) ............................................................... D1-331
D1.24 Signal Selector Blocks (SS-H/M/L) ........................................................... D1-348
D1.25 Auto-Selector Blocks (AS-H/M/L) ............................................................. D1-355
D1.26 Dual-Redundant Signal Selector Block (SS-DUAL) ................................ D1-367
D1.27 Cascade Signal Distributor Block (FOUT) ............................................... D1-372
D1.28 Feedforward Signal Summing Block (FFSUM) ........................................ D1-380
D1.29 Non-Interference Control Output Block (XCPL) ...................................... D1-398
D1.30 Control Signal Splitter Block (SPLIT) ....................................................... D1-409
D1.31 Representative Alarm Block (ALM-R) ...................................................... D1-424
D1.32 Pulse Count Input Block (PTC) ................................................................ D1-432
D1.33 Control Operations of YS Blocks ............................................................. D1-439
D1.33.1 Applying YS Blocks ..................................................................... D1-440
D1.33.2 Common Specification of YS Blocks ........................................... D1-441
D1.34 YS Controller Block (SLCD) ..................................................................... D1-455
D1.35 YS Programmable Controller Block (SLPC) ............................................ D1-459
D1.36 YS Programmable Controller Block with Pulse Width Output (SLMC) .. D1-463
D1.37 YS Station Block with SV Output (SMST-111) .......................................... D1-467
D1.38 YS Station Block with MV Output Lever (SMTS-121) .............................. D1-470
D1.39 YS Ratio Set Station Block (SMRT) .......................................................... D1-473
D1.40 YS Batch Set Station Block (SBSD) ......................................................... D1-478
D1.41 YS Batch Controller Block (SLBC) ........................................................... D1-482

D1.42 YS Blending Controller Block (SLCC) ..................................................... D1-486
D1.43 YS Totalizer Block (STLD) ......................................................................... D1-490
D2. Arithmetic Calculation, Logic Operation ............................................. D2-1
D2.1 Common Functions of Calculation Blocks .................................................. D2-2
D2.2 Data Handled by Calculation Blocks ........................................................... D2-5
D2.3 Types of Calculation Blocks ......................................................................... D2-8
D2.3.1 Input Processing, Output Processing, and Alarm Processing
Possible for Each Calculation Block .............................................. D2-11
D2.3.2 Valid Block Modes for Each Calculation Block ............................... D2-19
D2.4 Addition Block (ADD) .................................................................................. D2-22
D2.5 Multiplication Block (MUL) ......................................................................... D2-26
D2.6 Division Block (DIV) .................................................................................... D2-30
D2.7 Averaging Block (AVE) ............................................................................... D2-34
D2.8 Square Root Block (SQRT) ......................................................................... D2-40
D2.9 Exponential Block (EXP) ............................................................................ D2-44
D2.10 First-Order Lag Block (LAG)....................................................................... D2-47
D2.11 Integration Block (INTEG) ........................................................................... D2-52
D2.12 Derivative Block (LD) .................................................................................. D2-58
D2.13 Ramp Block (RAMP) ................................................................................... D2-63
D2.14 Lead/Lag Block (LDLAG) ............................................................................ D2-67
D2.15 Dead-Time Block (DLAY) ............................................................................ D2-72
D2.16 Dead-Time Compensation Block (DLAY-C) ............................................... D2-77
D2.17 Moving-Average Block (AVE-M) ................................................................. D2-81
D2.18 Cumulative-Average Block (AVE-C) ........................................................... D2-86
D2.19 Variable Line-Segment Function Block (FUNC-VAR) ................................ D2-91
D2.20 Temperature and Pressure Correction Block (TPCFL) ............................. D2-96
D2.21 ASTM Correction Block : Old JIS (ASTM1) .............................................. D2-102
D2.22 ASTM Correction Block : New JIS (ASTM2) ............................................ D2-106
D2.23 Logical AND Block (AND), Logical OR Block (OR) .................................. D2-110
D2.24 Logical NOT Block (NOT) ......................................................................... D2-113
D2.25 Flip-Flop Blocks (SRS1-S, SRS1-R, SRS2-S, SRS2-R) ............................ D2-115
D2.26 Wipeout Block (WOUT) ............................................................................. D2-119
D2.27 ON-Delay Timer Block (OND) ................................................................... D2-122
D2.28 OFF-Delay Timer Block (OFFD) ................................................................ D2-126
D2.29 One-Shot Blocks Rise Trigger (TON), Fall Trigger (TOFF) ...................... D2-130
D2.30 Relational Operation Blocks (GT, GE, EQ) ............................................... D2-133
D2.31 Bitwise AND Block (BAND), Bitwise OR Block (BOR) ............................. D2-136
D2.32 Bitwise NOT Block (BNOT) ....................................................................... D2-139
D2.33 General-Purpose Calculation Blocks (CALCU, CALCU-C) ..................... D2-142
D2.34 Three-Pole Three-Position Selector Switch Block (SW-33) .................... D2-150
D2.35 One-Pole Nine-Position Selector Switch Block (SW-91) ......................... D2-153
D2.36 Selector Switch Block for 16 Data (DSW-16) ........................................... D2-156

D2.37 Selector Switch Block for 16 String Data (DSW-16C) .............................. D2-159
D2.38 Data Set Block (DSET) .............................................................................. D2-162
D2.39 Data Set Block with Input Indicator (DSET-PVI) ...................................... D2-164
D2.40 One-Batch Data Set Block (BDSET-1L) .................................................... D2-167
D2.41 One-Batch String Data Set Block (BDSET-1C) ........................................ D2-171
D2.42 Two-Batch Data Set Block (BDSET-2L) .................................................... D2-174
D2.43 Two-Batch String Data Set Block (BDSET-2C) ........................................ D2-179
D2.44 Batch Data Acquisition Block (BDA-L) .................................................... D2-184
D2.45 Batch String Data Acquisition Block (BDA-C) ......................................... D2-188
D2.46 Inter-Station Data Link Block (ADL) ......................................................... D2-191
D2.47 General-Purpose Arithmetic Expressions ............................................... D2-196
D2.47.1 Basic Items of the General-Purpose Arithmetic Expressions ....... D2-197
D2.47.2 Constants in General-Purpose Arithmetic Expressions ............... D2-202
D2.47.3 Variables ..................................................................................... D2-204
D2.47.4 Operators ................................................................................... D2-214
D2.47.5 Arithmetic Expressions ............................................................... D2-218
D2.47.6 Control Statements ..................................................................... D2-222
D2.47.7 Error Handling ............................................................................ D2-227
D2.47.8 Built-In Functions ........................................................................ D2-231
D2.47.9 Reserved Words for Numerical and Logical Arithmetic
Expressions ................................................................................ D2-239
D3. Sequence Control ................................................................................. D3-1
D3.1 Types of Sequence Control Blocks .............................................................. D3-3
D3.1.1 Alarm Processing of Sequence Control Blocks ............................... D3-5
D3.1.2 Block Mode of Sequence Control Blocks ........................................ D3-6
D3.2 Sequence Table Block (ST16, ST16E) .......................................................... D3-7
D3.2.1 Sequence Table Configuration ...................................................... D3-11
D3.2.2 Creating a Sequence Table ........................................................... D3-16
D3.2.3 Sequence Table Processing Flow ................................................. D3-19
D3.2.4 Input Processing of Sequence Table ............................................. D3-28
D3.2.5 Condition Rule Processing of Sequence Table .............................. D3-30
D3.2.6 Action Rule Processing of Sequence Table ................................... D3-31
D3.2.7 Output Processing of Sequence Table .......................................... D3-32
D3.2.8 Number of Condition Signals and Action Signals ........................... D3-33
D3.2.9 Rule Extension ............................................................................. D3-34
D3.2.10 Condition Signal Description: Referencing Other Function Blocks
and I/O Data ................................................................................. D3-36
D3.2.11 Control Signal Description: Referencing Sequence Table ............. D3-57
D3.2.12 Syntax for Condition Signal Description: Logic Chart Reference in
Sequence Table ............................................................................ D3-70
D3.2.13 Description of Action Signal: Status Manipulation for Other
Function Blocks and I/O Data ....................................................... D3-72
D3.2.14 Action Signal Description: Status Manipulation for Sequence
Table ............................................................................................. D3-91

D3.2.15 Action Signal Description: Status Manipulation for a Logic Chart
from a Sequence Table ............................................................... D3-101
D3.2.16 Data Items of the Sequence Table Block (ST16) ......................... D3-102
D3.3 Logic Chart Block (LC64) ......................................................................... D3-103
D3.3.1 Configuration of a Logic Chart ..................................................... D3-105
D3.3.2 Creating a Logic Chart Block ...................................................... D3-108
D3.3.3 Logic Chart Processing Flow ...................................................... D3-111
D3.3.4 Input Processing of Logic Chart .................................................. D3-112
D3.3.5 Logic Calculation Processing of Logic Chart ............................... D3-113
D3.3.6 Output Processing of Logic Chart ............................................... D3-120
D3.3.7 Condition Signal Description: Referencing Other Function
Blocks and I/O Data .................................................................... D3-121
D3.3.8 Syntax for Condition Signal Description: Referencing
Logic Chart ................................................................................. D3-142
Sequence Table in a Logic Chart ................................................. D3-143
D3.3.10 Action Signal Description: Status Manipulation for Other
Function Blocks and I/O Data ..................................................... D3-147
D3.3.11 Syntax for Action Signal Description: Status Manipulation of
Logic Chart ................................................................................. D3-165
D3.3.12 Syntax for Action Signal Description: Status Manipulation of
Sequence Table from Logic Chart ............................................... D3-166
D3.3.13 Behavior of Logic Chart Internal Timer ........................................ D3-169
D3.3.14 Data Items of Logic Chart Block - LC64....................................... D3-170
D3.4 Switch Instrument Block .......................................................................... D3-171
D3.5 Timer Block (TM) ....................................................................................... D3-192
D3.6 Software Counter Block (CTS) ................................................................. D3-201
D3.7 Pulse Train Input Counter Block (CTP) .................................................... D3-206
D3.8 Code Input Block (CI) ................................................................................ D3-214
D3.9 Code Output Block (CO) ........................................................................... D3-220
D3.10 Relational Expression Block (RL) ............................................................ D3-225
D3.11 Resource Scheduler Block (RS) ............................................................... D3-230
D3.12 Valve Monitoring Block (VLVM) ................................................................ D3-240
D4. Faceplate Blocks .................................................................................. D4-1
D4.1 Types of Faceplate Blocks ........................................................................... D4-2
D4.2 Push Button Operation of Faceplate Blocks ............................................... D4-5
D4.3 Block Mode and Status of Faceplate Blocks ............................................... D4-8
D4.3.1 Block Mode of Faceplate Blocks ................................................... D4-10
D4.3.2 Block Status of Faceplate Blocks .................................................. D4-13
D4.3.3 Alarm Status of Faceplate Blocks ................................................. D4-15
D4.3.4 Data Status of Faceplate Blocks ................................................... D4-17
D4.4 Dual-Pointer Indicating Station Block (INDST2) ........................................ D4-18
D4.5 Dual-Pointer Manual Station Block (INDST2S) .......................................... D4-22
D4.6 Triple-Pointer Manual Station Block (INDST3) .......................................... D4-27
D4.7 Batch Status Indicator Block (BSI) ............................................................ D4-32
D4.8 Extended 5-Push-Button Switch Block (PBS5C) ...................................... D4-41
D4.9 Extended 10-Push-Button Switch Block (PBS10C) .................................. D4-49
D4.10 Extended Hybrid Manual Station Block (HAS3C) ...................................... D4-57
D5. Sequential Function Chart ................................................................... D5-1
D5.1 SFC Elements ................................................................................................ D5-5
D5.1.1 Step ................................................................................................ D5-6
D5.1.2 Transition ...................................................................................... D5-10
D5.1.3 Links ............................................................................................. D5-12
D5.1.4 Step & Selective Sequences ......................................................... D5-15
D5.2 Action Description Using SEBOL .............................................................. D5-18
D5.2.1 Step Common Items ..................................................................... D5-19
D5.2.2 Initial Step ..................................................................................... D5-23
D5.2.3 SEBOL Steps ............................................................................... D5-25
D5.2.4 SEBOL One-Shot Steps ............................................................... D5-26
D5.3 Action Description Using Sequence Table ................................................ D5-28
D5.3.1 Step Common Item Description Using the Sequence Table .......... D5-29
D5.3.2 Sequence Table Steps .................................................................. D5-32
D5.3.3 Sequence Table One-Shot Steps .................................................. D5-33
D5.4 Action Description Using Logic Chart ....................................................... D5-34
D5.4.1 Step Common Item Description Using Logic Chart ....................... D5-35
D5.4.2 Logic Chart Steps ......................................................................... D5-38
D5.4.3 Logic Chart One-Shot Steps ......................................................... D5-39
D5.5 Transition Conditions ................................................................................. D5-40
D5.6 SFC Block Action ........................................................................................ D5-42
D5.6.1 Queue Signal Processing ............................................................. D5-47
D5.6.2 Status Change Processing ........................................................... D5-56
D5.6.3 Interrupt Signal Processing ........................................................... D5-64
D5.6.4 Error Processing ........................................................................... D5-67
D5.6.5 Terminating SFC Block Execution ................................................. D5-68
D5.6.6 Pausing SFC Block Execution ...................................................... D5-70
D5.6.7 Referencing Current Step ............................................................. D5-76
D5.6.8 Changing Current Step ................................................................. D5-77
D5.6.9 SFC Block Alarm Processing ........................................................ D5-78
D5.6.10 SFC Online Maintenance .............................................................. D5-81
D5.6.11 SFC Block Execution .................................................................... D5-83
D5.6.12 Data Items - SFC .......................................................................... D5-84
D5.6.13 SFC Block Mode & Status ............................................................. D5-94
D5.7 Manipulating Unit Instrument from SFC Block ......................................... D5-98

D6. Unit Supervision ................................................................................... D6-1
D6.1 Outline of Unit Supervision .......................................................................... D6-2
D6.1.1 What is a Unit? ............................................................................... D6-3
D6.1.2 ISA S88.01 and Unit Supervision .................................................... D6-5
D6.1.3 Batch Management and Unit Supervision ....................................... D6-9
D6.1.4 Application Capacity of Unit Supervision ....................................... D6-10
D6.2 Unit Instrument ........................................................................................... D6-13
D6.3 Unit Instrument Data Items ......................................................................... D6-18
D6.3.1 System-Specific Data Items .......................................................... D6-19
D6.3.2 Faceplate Data Items .................................................................... D6-21
D6.3.3 User-Definable Data Items ............................................................ D6-23
D6.3.4 Data Items for Process Management ............................................ D6-27
D6.3.5 Accessing Unit Data ..................................................................... D6-29
D6.4 Unit Procedure ............................................................................................ D6-32
D6.4.1 Unit Procedure SFC ...................................................................... D6-33
D6.4.2 Compound Sequence ................................................................... D6-39
D6.4.3 Transition Conditions .................................................................... D6-42
D6.4.4 Interrupt Processing of Unit Procedure ......................................... D6-45
D6.4.5 Unit Procedure Sharing ................................................................ D6-47
D6.5 Unit Mode and Unit Status .......................................................................... D6-50
D6.5.1 Unit Mode ..................................................................................... D6-51
D6.5.2 Unit Status .................................................................................... D6-52
D6.5.3 Unit Sub-Status ............................................................................ D6-53
D6.5.4 Unit Mode and Unit Status Change Command .............................. D6-54
D6.6 State Transition Matrix ................................................................................ D6-62
D6.6.1 Standard State Transition Matrix ................................................... D6-63
D6.6.2 User Defined State Transition Matrix ............................................. D6-76
D6.7 Unit Supervision Messages ........................................................................ D6-80
D6.7.1 Unit Process Alarm Messages ...................................................... D6-81
D6.7.2 Unit Mode and Unit Status Change Messages .............................. D6-84
D6.7.3 Sequence Control Messages - Unit Instrument ............................. D6-85
D6.7.4 System Alarm Messages .............................................................. D6-86
D6.8 Operations ................................................................................................... D6-87
D6.9 Data Items of Operation .............................................................................. D6-90
D6.10 SFC Operation ............................................................................................. D6-94
D6.10.1 SFC Operation.............................................................................. D6-96
D6.10.2 Compound Sequence ................................................................. D6-101
D6.10.3 Transition Conditions .................................................................. D6-102
D6.10.4 Operation Sharing ...................................................................... D6-104

D6.11 Mode and Status of an Operation ............................................................ D6-107
D6.11.1 Operation Mode .......................................................................... D6-108
D6.11.2 Operation Status ......................................................................... D6-109
D6.11.3 Operation Mode and Status Change Command .......................... D6-110
D6.11.4 Operation Block Status Transition ............................................... D6-111
D6.12 Actions of Operation ................................................................................. D6-113
D6.12.1 Action Scripts in SEBOL ............................................................. D6-114
D6.12.2 Action Description Using the Sequence Table ............................. D6-123
D6.12.3 Action Description Using Logic Charts ........................................ D6-127
D6.13 Operation Actions ..................................................................................... D6-130
D6.13.1 Start and End of An Operation .................................................... D6-131
D6.13.2 Pause an Operation .................................................................... D6-133
D6.13.3 Referencing Current Step ........................................................... D6-139
D6.13.4 Changing Current Step ............................................................... D6-140
D6.13.5 Operation Alarm Processing ....................................................... D6-141
D6.14 Interrupt Processing of Operation ........................................................... D6-144
D6.14.1 Queue Signal Processing ........................................................... D6-151
D6.14.2 Status Change Processing ......................................................... D6-158
D6.14.3 Interrupt Signal Processing ......................................................... D6-169
D6.14.4 Error Processing ......................................................................... D6-172
D6.15 Initialization Operation and Monitoring Operation.................................. D6-173
D7. Valve Pattern Monitors ......................................................................... D7-1
D7.1 Valve Pattern Monitor Type and Size ........................................................... D7-5
D7.2 System Environment .................................................................................... D7-6
D7.3 Procedure for Operating Valve Pattern Monitor .......................................... D7-7
D7.4 Data Items for Valve Pattern Monitor ........................................................... D7-8
D7.5 Block Mode of Valve Pattern Monitor ......................................................... D7-14
D7.6 Block Status of Valve Pattern Monitor ....................................................... D7-15
D7.7 Signal Transmission and Alarm of Valve Pattern Monitor ........................ D7-16
D7.8 SEBOL Statements for Valve Pattern Monitor ........................................... D7-22
D7.8.1 vpmstart Statement ...................................................................... D7-23
D7.8.2 drive vpmon Statement ................................................................. D7-25
D7.8.3 drive vpmoff Statement ................................................................. D7-30
D7.8.4 vpmon Statement ......................................................................... D7-33
D7.8.5 vpmoff Statement ......................................................................... D7-38
D7.8.6 vpmreset Statement ..................................................................... D7-41
D7.9 Inspection of Data Acquired from FCS ...................................................... D7-42
D7.10 Builder Items for Creating Application Program ....................................... D7-45
D7.11 Example for Creating Application Program ............................................... D7-46
D7.12 Specifying Processing Timing ................................................................... D7-50
D7.13 Using Simulation Programs ....................................................................... D7-51

D8. Offsite Block ......................................................................................... D8-1
D8.1 Batch Set Control Block (FSBSET) .............................................................. D8-7
D8.1.1 Operation for Batch Loader Control - FSBSET ................................ D8-8
D8.1.2 Operation for Batch Blending Control - FSBSET ........................... D8-11
D8.1.3 Operation for X% Preset MV Control - FSBSET ............................ D8-13
D8.1.4 Configuration of Batch Set Control Block (FSBSET) ..................... D8-15
D8.1.5 Input Processing of Batch Set Control Block (FSBSET) ................ D8-17
D8.1.6 Output Processing of Batch Set Control Block (FSBSET) ............. D8-25
D8.1.7 Alarm and Notification Processing of Batch Set Control Block
(FSBSET) ..................................................................................... D8-27
D8.1.8 Control Processing of Batch Set Control Block (FSBSET) ............. D8-34
D8.1.9 Block Modes of Batch Set Control Block (FSBSET) ...................... D8-57
D8.1.10 Data Items of Batch Set Control Block (FSBSET) ......................... D8-58
D8.2 Blending Master Control Block (BLEND) ................................................... D8-61
D8.2.1 Operation for Tank Blending Control ............................................. D8-62
D8.2.2 Operation for Direct Blending Shipment Control ............................ D8-65
D8.2.3 Configuration of Blending Master Control Block (BLEND) ............. D8-67
D8.2.4 Component Management ............................................................. D8-68
D8.2.5 Port Management ......................................................................... D8-71
D8.2.6 Input Processing of Blending Master Control Block (BLEND) ........ D8-73
D8.2.7 Output Processing of Blending Master Control Block (BLEND) ..... D8-75
D8.2.8 Alarm and Notification Processing of Blending Master Control
Block (BLEND) ............................................................................. D8-76
D8.2.9 Control Processing of Blending Master Control Block (BLEND) .... D8-79
D8.2.10 Block Modes of Blending Master Control Block (BLEND) .............. D8-96
D8.2.11 Data Items of Blending Master Control Block (BLEND) ................. D8-97

Blank Page
<Toc> <Ind> <D1. Regulatory Control> D1-1
D1. Regulatory Control

The regulatory control performs control computation processing using analog
process values for process monitor and process control. The function blocks that
provide the regulatory control function are referred as “regulatory control blocks.”
This chapter presents a detailed description of the function of each of the regulatory
control blocks, excluding the Foundation Fieldbus faceplate block.
SEE ALSO
For details on the Foundation Fieldbus faceplate blocks, see a chapter A2, “Overview of FF Faceplate
Blocks” in the Foundation Fieldbus Reference (IM 33Y05P10-01E).
■ Regulatory Control Positioning ¡ £

The regulatory control is one of the basic controls in the FCS and performs control compu-
tation processing to monitor and control processes. The function blocks that perform the
this regulatory control are referred as “regulatory control blocks.”
The regulatory control blocks include Input indication blocks, controller blocks, manual
loader blocks, signal set blocks, signal limiter blocks, Signal selector blocks, signal distribu-
tion blocks, pulse-count blocks, alarm blocks and YS blocks.
The figure below shows the position of the regulatory control function in the basic control
architecture:
FCS
Basic control Software I/O

Regulatory control blocks Internal switch
Arithmetic calculation blocks Annunciator message
Sequence control blocks Sequence message
Faceplate blocks
SFC blocks
Unit instrument blocks
Options
Valve pattern monitoring (1*)
Off-site blocks (1*)
FCS I/O Interfaces
Process I/O Communication I/O Fieldbus I/O
D010001E.EPS
*1: ¡ £ The valve pattern monitor and the off-site block can only be used for the CS 3000.
Figure Regulatory Control Block in the Basic Control Function Architecture ¡ £

<Toc> <Ind> <D1.1 Regulatory Control Blocks> D1-2
D1.1 Regulatory Control Blocks

The regulatory control blocks are the function blocks that perform control computa-
tion processing mainly on the analog input as input signals. The calculated results
are used for process monitor and process control.
The regulatory control blocks support the following types of processing: input
processing, control computation processing, output processing and alarm process-
ing.
■ Structure of Regulatory Control Blocks

The function blocks that provide the regulatory control function are called “regulatory
control blocks.”
The regulatory control blocks perform control computation processing mainly on analog
signals (analog values) as input values. The results of control computation processing
performed by the regulatory control blocks are output as manipulated output values (MV).
The figure below shows a function block diagram of a general regulatory control block:
SET BIN RL1 RL2 TIN TSI INT
(VN) (RLV1) (RLV2) (TSW)
Alarm
processing
CAS
CSV
AUT
SV
MAN
RSV
RCAS
MAN
CAS
Control AUT
Input Output
IN RAW PV computation MV OUT
processing processing
processing
ROUT
(PV, PV, MV, MV) RMV
SUB
D010101E.EPS
Figure Function Block Diagram of the Regulatory Control Block
IN: Input terminal RAW: Raw data input signal

SET: Setpoint value input terminal PV: Process variable
BIN: Compensation input terminal SV: Setpoint value
RLn: Reset signal input terminal CSV: Cascade setpoint value
TIN: Tracking signal input terminal RSV: Remote setpoint value
TSI: Tracking switch input terminal VN: Compensated value Input
INT: Interlock switch input terminal RMV: Remote manipulated output value
SUB: Auxiliary output terminal RLVn: Reset signal
OUT: Output terminal MV: Manipulated output value
TSW: Tracking switch
IM 33S01B30-01E 3rd Edition : Sep.01,1998-00

■ Functions of the Regulatory Control Blocks
The regulatory control blocks have the following four processing functions:
Receives a signal from the input terminal and outputs a process variable (PV).
● Control Computation Processing

Performs control computation processing by reading the process variable (PV) and outputs
a manipulated output value (MV).
Reads the manipulated output value (MV) and outputs the result of control computation
processing to the output terminal as an output signal.
Detects an abnormality in the process variable (PV) or manipulated output value (MV) and
notifies the operation and monitoring functions.
Control computation processing can be performed independently via data setting or data
reference between the function blocks, without involving input processing or output pro-
cessing.
SEE ALSO
Refer to the following sections for the input processing, output processing, and alarm processing that are
common to a multiple number of regulatory control blocks.
• For input processing, see a chapter C3, “Input Processing.”
• For output processing, see a chapter C4, “Output Processing.”
• For alarm processing, see a chapter C5, “Alarm Processing - FCS.”
The characteristics and control computation processing functions of the regulatory control
blocks are explained as control action in the sections for individual function blocks in the
chapters from D1.3.
The characteristics and control computation processing of each regulatory control block, as
well as any input processing, output processing, and alarm processing that are inherent to
particular regulatory control blocks are explained in the sections beginning with D1.2 for
each function block.

D1.1.1 Types of the Regulatory Control Blocks

The regulatory control blocks vary by the types of data handled and control compu-
tation processing functions provided. The blocks are classified into these blocks
below.
• Input Indicator Blocks
• Controller Blocks
• Manual Loader Blocks
• Signal Setter Blocks
• Signal Limiter Blocks
• Signal Selector Blocks
• Signal Distributor Blocks
• Pulse Count Input Block
• Alarm Block
• YS Blocks
■ Input Indicator Blocks

The table below shows a list of input indicator blocks:
Table Input Indicator Blocks
Block type Code Name
PVI Input Indicator Block
Input indicators
PVI-DV Input Indicator Block with Deviation Alarm
D010102E.EPS
■ Controller Blocks
The table below shows a list of controller blocks:
Table Controller Blocks
PID PID Controller Block
PI-HLD Sampling PI Controller Block
PID-BSW PID Controller Block with Batch Switch
ONOFF 2-Position ON/OFF Controller Block
Controllers ONOFF-G 3-Position ON/OFF Controller Block
PID-TP Time-Proportioning ON/OFF Controller Block
PD-MR PD Controller Block with Manual Reset
PI-BLEND Blending PI Controller Block
PID-STC Self-Tuning PID Controller Block
D010103E.EPS

■ Manual Loader Blocks
The table below shows a list of manual loader blocks:
Table Manual Loader Blocks
MLD Manual Loader Block
MLD-PVI Manual Loader Block with Input Indicator
Manual Loader MLD-SW Manual Loader Block with Auto/Man Switch
MC-2 2-Position Motor Control Block
D010104E.EPS
■ Signal Setter Blocks

The table below shows a list of signal setter blocks:
Table Signal Setter Blocks

RATIO Ratio Set Block
PG-L13 13-Zone Program Set Block
Signal Setters
BSETU-2 Flow-Totalizing Batch Set Block
BSETU-3 Weight-Totalizing Batch Set Block
D010105E.EPS
■ Signal Limiter Block

The table below shows the signal limiter block:
Table Signal Limiter Block
Signal Limiters VELLIM Velocity Limiter Block
D010106E.EPS
■ Signal Selector Blocks

The table below shows a list of Signal selector blocks:
Table Signal Selector Blocks
AS-H/M/L Autoselector Block
Signal selectors SS-H/M/L Signal Selector Block
SS-DUAL Dual-Redundant Signal Selector Block
D010107E.EPS

■ Signal Distributor Blocks
The table below shows a list of signal distributor blocks:
Table Signal Distributor Blocks
FOUT Cascade Signal Distributor Block
FFSUM Feedforward Signal Summing Block
Signal Distributors
XCPL Non-Interference Control Output Block
SPLIT Control Signal Splitter Block
D010108E.EPS
■ Alarm Block
The table below shows the alarm block:
Table Alarm Block
Alarm ALM-R Representative Alarm Block
D010109E.EPS
■ Pulse Count Input Block

The table below shows the pulse count input connection block:
Table Pulse Count Input Connection Block
Pulse Count Input
PTC Pulse Count Input Block
Connection Block
D010110E.EPS
■ YS Blocks
The table below shows the YS blocks:
Table YS Blocks

SLCD YS Instrument Indicating Controller Block
SLPC YS Instrument Programmable Indicating Controller Block
YS Instrument Programmable Indicating Controller Block with
SLMC
PW Output
YS Instrument Auto/Manual Station Block with Pushbutton
SMST-111
Setpoint Setting
YS instrument YS Instrument Auto/Manual Station Block with Manipulated
SMST-121
Output Lever
SMRT YS Instrument Ratio Set Station Block
SBSD YS Instrument Batch Set Station Block
SLCC YS Instrument Blending Controller Block
SLBC YS Instrument Batch Controller Block
STLD YS Instrument Totalizer Block
D010111E.EPS

D1.1.2 I/O Data Handled by the Regulatory Control Blocks

As a rule, the data transmitted via I/O terminals handled by the regulatory control
blocks must be the engineering unit data. Each data item consists of data value and
data status.
■ Data Value
The data value is a numeric data that is transmitted in or out of a function block. The data
values handled by the blocks include process variable (PV), cascade setpoint value (CSV)
and manipulated output value (MV).
The data values handled by the regulatory control blocks are numeric data in engineering
unit. However, the data received from the input modules (excluding the input modules for
temperature measurement as well as for pulse trains) and the setpoint data sent to ana-
logue output modules are given as percentage values in the range from 0% to 100%.
The data value read into a function block via an input terminal is called “input data,” while
the value written out of a function block via an output terminal is called “output data.”
■ Data Status
The data status is a piece of status information that indicates the value and quality of I/O
data.
The data status is conveyed as I/O data from one function block to another via I/O connec-
tion along with a data value.
The data status is used to test the existence of exceptional events, such as process failures
and computation errors occurred in the control computation processing performed by the
function blocks.
SEE ALSO
For the details of data status, see a chapter C6, “Block Mode and Status.”

■ Input Data
The input data is numeric data that the function blocks read from input terminals.
The types of input data are shown below:
• Setpoint value (SV), cascade setpoint value (CSV), remote setpoint value (RSV)
• Input signal values (RV1, RV2, RV3)
• Reset limit values (RLV1, RLV2)
• Input or Output Compensated value (VN)
• Tracking switch (TSW)
● Process Variable (PV)

▼ Process Variable Range
The engineering unit and scale range of raw input signals (RAW) input to an IN terminal
agree with the engineering unit and scale range of data at the connected destination of the
IN terminal. A raw input signal turns into a process variable (PV) after input processing.
Use the Function Block Detail Builder to set the engineering unit and scale range. However,
the process variable (PV) of Motor control blocks (MC-2, MC-3) must be an integer value
between 0 and 2.
• Engineering unit:
Consists of six or less standard-width characters or three double-width characters.
The default is “%.”
• Process variable range:
High and low limits.
Numerical values of seven digits or less, where the sign or decimal point takes one
digit each.
The default is “100.0” for the upper limit and “0.0” for the lower limit.
● Setpoint Value (SV), Cascade Setpoint Value (CSV), Remote Setpoint Value
(RSV)
The engineering unit and scale range of the setpoint value (SV), cascade setpoint value
(CSV) and remote setpoint value (RSV) agree with the engineering unit and scale range of
the process variable (PV) except in the function blocks shown below:
Ratio Set Block (RATIO) Use the Function Block Detail

Velocity Limiter Block (VELLIM) Definition Builder to set the
Control Signal Splitter Block (SPLIT) engineering unit and scale range
Cascade Signal Distributor Block (FOUT) of SV for the function blocks
Feedforward Signal Summing Block (FFSUM) shown to the left. The engineering
unit and scale range of CSV and
RSV are same as those of SV.
The FOUT and FFSUM blocks
have no RSV.
Motor Control Blocks (MC-2, MC-3) The engineering unit and scale
13-Zone Program Set Block (PG-L13) range of the function blocks shown
Representative Alarm Block (ALM-R) to the left are fixed for each block.
D010112E.EPS

● Input Signal Values (RV1, RV2, RV3)
The input signal values (RV1, RV2, RV3) are input data handled by the Signal selector
blocks.
Use the Function Block Detail Builder to set the engineering unit and scale range of input
signal values. The input signal values (RV1, RV2, RV3) are regarded as having the same
engineering unit and scale range as those of the selected signal value (PV).
● Reset Limit Values (RLV1, RLV2)

The reset limit values (RLV1, RLV2) are input data that are handled by a controller block
when the reset limit function is used.
The reset limit values (RLV1, RLV2) are regarded as having the same engineering unit and
scale range as those of the manipulated output value (MV).
● Input or Output Compensated Value (VN)

The engineering unit and scale range are not defined for input compensated values (VN)
received from the BIN terminal, as the numeric data of input compensated values (VN)
taken in from outside are used directly for input or output compensation computation.
● Tracking Switch (TSW)

The data handled by the tracking switch (TSW) for the TSI terminal must be an integer
value of “0” or “1.” “1” and “0” indicate ON and OFF, respectively.

■ Output Data
The output data is a numeric data value that is written out of a function block via an output
terminal.
The types of output data are shown below:
• Manipulated output value (MV)
• Auxiliary output values (PV, PV, MV, MV)
● Manipulated Output Value (MV)

▼ MV Display Style
Use the Function Block Detail Builder to set the display form for the manipulated output
value (MV).
• MV Display Style:
Select “Automatic Determination” or “User Define.”
The default is “Automatic Determination.”
When “Automatic Determination” is selected, the engineering unit and scale range of the
manipulated output value (MV) change according to the connected destination of the OUT
terminal.
• If the connection destination is a process I/O, the scale range and engineering unit of
the manipulated output value (MV) is fixed to “0 to 100” and “%,” respectively. How-
ever, this rule does not apply if the connection destination is a Fieldbus block.
• When outputting to a cascade setpoint value (CSV) in a case where the connection
destines to a SET terminal of another function block (cascade connection), the engi-
neering unit and scale range of the manipulated output value (MV) agree with those of
the cascade setpoint value (CSV) of the output destination.
When the connection destination is an input terminal of another function block than
SET terminal, “self determination” must be selected.
When “User Define” is selected, set the engineering unit and scale range for the manipu-
• MV Engineering Unit Symbol:
Consists of six or less standard-width characters or three double-width characters.
• MV Range:
Numerical values of seven digits or less, where the sign and decimal point occupy one
digit each.
For MV displayed on an instrument faceplate, set whether to display the engineering unit
data as is or to convert the data into a percentage-unit value first. Use the Function Block
Detail Builder to set the instrument faceplate display.
• MV Display on Faceplate:
Select “Indicate Actual Quantity” or “Indicate %.”
The default is “Indicate real amount.”

● Auxiliary Output Values (PV, PV, MV, MV)
The auxiliary output values include PV, PV, MV and MV, the types vary with the function
block. The engineering unit and scale range of the auxiliary output values change in accor-
dance with the connected destination of the SUB terminal.
• If the connected destination is a process I/O, the scale range and engineering unit of
the auxiliary output values are fixed to “0 to 100” and “%,” respectively. However, this
rule does not apply if the connection destination is a Fieldbus block.
• When the connected destination is a function block and auxiliary output is the process
variable (PV) or process variable change (PV), the engineering unit and scale range
of the output value agree with those of the process variable (PV).
• When the connected destination is a function block and auxiliary output is the manipu-
lated output value (MV) or manipulated output change (MV), the output value is
regarded as having the same engineering unit and scale range as those of the ma-
nipulated output value (MV).
● Process Variable (PV)

The process variable (PV) can be output directly from the input indicator blocks.
The engineering unit and scale information of the process variable (PV) vary with the
connected destination of the OUT terminal.
• If the connected destination is a process I/O, the scale range and engineering unit of
the output value are fixed to “0 to 100” and “%,” respectively. However, this rule does
not apply if the connection destination is a Fieldbus block.
• If the connected destination is another function block, the scale range and engineering
unit of the output value agree with those of the process variable.

D1.1.3 Input Processing, Output Processing, and Alarm

Processing Possible for Each Regulatory Control Block
A list of the types of input processing, output processing, and alarm processing that
can be performed in each regulatory control block is shown below.
■ Input Processing Possible for Each Regulatory Control Block

Table Input Processing Possible for Each Regulatory Control Block (1/3)
Input signal
Model Digital filter Totalizer PV overshoot CAL
conversion
PVI
PVI-DV
PID
PI-HLD
PID-BSW
ONOFF BARPSb
ONOFF-G
PID-TP
PD-MR
PI-BLEND
PID-STC
MLD
MLD-PVI BARPbSb
MLD-SW
MC-2
S2 S3
MC-3
D010113E.EPS
B: No conversion (function block)

A: No conversion (analog input)
R: Square root conversion (analog input)
Pb: Pulse-train input conversion
P: Control priority type pulse-train input conversion
Pq: Exact totalization pulse-train input conversion
S2: Two-position status input (for MC-2/3 only)
S3: Three-position status input (for MC-2/3 only)
C: Code input (for BSET-3 only)
Sb: Subsystem input
: Exists
Blank: Not exist

Input signal
conversion
RATIO (*1) BARPbSb
PG-L13
BSETU-2 BARPbSb
BSETU-3 BACSb
VELLIM
SS-H/M/L
AS-H/M/L
SS-DUAL (*2) BASb
FOUT
FFSUM
XCPL
SPLIT
PTC (*3) (*3)
ALM-R
D010114E.EPS

Sb: Subsystem input
: Exists
Blank: Not exist
*1: The input processing will not function when the data setting is performed to the PV by cascade connection.
*2: The input processing is performed against the input signal on the selected side.
*3: Performs a PTC block independent processing
Input signal
conversion
SLCD B/R
SLPC
SLMC
SMST-111
SMST-121
SMRT
SBSD (*1)
SLBC (*1)
SLCC (*1)
STLD (*1)
D010115E.EPS
B: No conversion
R: Square root conversion
: Exists
Blank: Not exist
*1: Display the sum of YS Instrument.

■ Output Processing Possible for Each Regulatory Control Block
Table Output Processing Possible for Each Regulatory Control Block (1/2)
Output Velocity Clamped Output Range Auxiliary Output signal

Model PMV
limit limit output track track output conversion
PVI
PPd BASb
PVI-DV
PID
PPdMMd BAPwPwfSb
PI-HLD
PID-BSW PPdMMd BAPwfSb
ONOFF PPd S2
ONOFF-G PPd S3
PID-TP (*2) PPdMMd D
PD-MR PPdMMd BAPwfSb
PI-BLEND
PPdMMd BAPwPwfSb
PID-STC
MLD (*1) MMd BAPwfSb
MLD-PVI (*1) PPdMMd BAPwfSb
MLD-SW (*1) MMd BAPwfSb
MC-2 S2P2
MC-3 S3P3
D010116E.EPS
P: PV
Pd: PV
M: MV
Md: MV
C: CPV
Cd: CPV
S: SV
Sd: SV
B: Unconverted output (function block)
A: Analog output
D: Time-proportioning ON/OFF output
Pw: Pulse width output (without FB)
Pwf: Pulse width output (with FB)
S2: 2-position status output
P2: 2-position pulsive output
S2b: 2-position status output (BSETU-2/3 only)
S2s: 2-position status output through switch instrument (BSETU-2/3 only)
Sb: Subsystem output
*1: Selectable by builder setting.
*2: The velocity limiter functions when the block is in AUT mode, but not when the block is in MAN mode regardless the
setting for [MAN Mode Velocity Limiter Bypass].

Table Output Processing Possible for Each Regulatory Control Block (2/2)

Model PMV
RATIO PPdMMd BAPwfSb
PG-L13 (*1) BASb
BSETU-2 BAS2bS3b
BSETU-3 S2sS3sb
VELLIM MMd BASb

SS-H/M/L BASb
AS-H/M/L BASb
SS-DUAL BASb
FOUT (*2) B
FFSUM PPdMMd BAPwfSb
XCPL MMd BAPwfSb
SPLIT BASb
PTC (*3)
ALM-R
YS Blocks (*4)
D010117E.EPS
P: PV
Pd: PV
M: MV
Md: MV
C: CPV
Cd: CPV
S: SV
Sd: SV
A: Analog output
*1: Always restricted by MSH/MSL
*2: Only tracking of the CLP status of the output destination is performed.
*3: Performs processing unique to PTC block.
*4: YS Blocks contain the following models:
SLCD, SLPC, SLMC, SMST-111, SMST-121, SMRT, SBSD, SLBC, SLCC, STLD.

■ Alarm Processing Possible for Each Regulatory Control
Table Alarm Processing Possible for Each Regulatory Control Block (1/3)
Process alarms
N O I I H L H L D D V V M M C
Model R O O O H L I O V V E E H L N Other alarms
P P P + - L L I O F
- + -
PVI
PVI-DV
PID

PI-HLD
PID-BSW
ONOFF
ONOFF-G
PID-TP

PD-MR
HDV
PI-BLEND
LDV
PID-STC
MLD
MLD-PVI
MLD-SW
TRIP
MC-2
PERR
ANS+
MC-3 ANS-
INT
D010118E.EPS
: Available
Blank: Not available

Process alarms
P P P + - L L I O F
- + -
RATIO Not available

PG-L13 Not available
NPLS (*1)
BSETU-2 BDV+
BDV-

LEAK
BSETU-3 BEND
BPRE
VELLIM Not available

SS-H/M/L
AS-H/M/L
SS-DUAL
FOUT (*2)
FFSUM
XCPL
SPLIT
PTC
HALM
MALM
ALM-R
LALM
RALM
D010119E.EPS
: Available
*1: The NPLS alarm is only supported in the BSETU-2 but not in the BSETU-3.
*2: FOUT does not have an alarm status. Nevertheless, the output fail check and the bad connection status alarm check
are performed and the results are transmitted to the upstream function block. An output fail of FOUT is generated when
output fail is detected at all FOUT output destinations.

Process alarms
P P P + - L L I O F
- + -
SLCD
SLPC
SLMC
SMST-111
SMST-121
SMRT
END
SBSD PRE
LERK
END
SLBC PRE
LERK
SLCC HDV
STLD
D010120E.EPS
: Available

D1.1.4 Valid Block Modes for Each Regulatory Control Block

A list of valid block modes for each regulatory control block is shown below.
■ Valid Block Modes for Each Regulatory Control Block

Table Valid Basic Block Modes for Each Regulatory Control Blocks (1/2)
Valid basic block modes
O I T M A C P R R
Model Name of function block / M R A U A R C O
S A K N T S D A U
N S T
PVI Input indicator block
- - - - - - -
PVI- DV Input indicator block with deviation alarm
PID PID controller block
PI-HLD Sampling PI controller block
PID-BSW PID controller block with batch switch
ONOFF Two-position ON/OFF controller block
ONOFF-G Three-position ON/OFF controller block - -
PID-TP Time-proportioning ON/OFF controller block
PD-MR PD controller block with manual reset
PI-BLEND Blending PI controller block -
PID-STC Self-tuning PID controller block
MLD Manual loader block
- - - - -
MLD-PVI Manual loader block with input indicator
MLD-SW Manual loader block with Auto/Man SW - - -
MC-2 Two-position motor control block

- -
MC-3 Three-position motor control block
RATIO Ratio set block -
PG-L13 13-zone program set block - - - -
D010121E.EPS
: Valid
-: Invalid
: For MLD-SW, CAS mode can be specified instead of AUT mode.

Table Valid Basic Block Modes for Each Regulatory Control Blocks (2/2)
O I T M A C P R R
S A K N T S D A U
N S T
BSETU -2 Flow-totalizing batch set block

- - - - -
BSETU -3 Weight-totalizing batch set block
VELLIM Velocity limiter block - -
SS-H/M/L Signal selector block - - - - - - -
AS-H/M/L Autoselector block - - - - -
SS-DUAL Dual-redundant signal selector block - - - - - - -
FOUT Cascade signal distributor block - - - - - - - - -
FFSUM Feedforward signal summing block - - -
XCPL Non-inteference control output block - - - -
SPLIT Control signal splitter block - - - -
PTC Pulse count input block - - - - - - -
ALM-R Representative alarm block - - - - - - -
SLCD YS controller block - -

SLPC YS programmable controller block - -
SLMC YS programmable controller block with pulse-width output - -
SMST-111 YS manual station block with SV output - - - -
SMST-121 YS manual station block with MV output lever - - - -

SMRT YS ratio set station block - -
SBCD YS batch set station block - - - - -
SLCC YS blending controller block - - -

SLBC YS batch controller block - - -
STLD YS totalizer block - - - - -
D010122E.EPS
: Valid
-: Invalid

<Toc> <Ind> <D1.2 Input Indicator Block (PVI)> D1-21
D1.2 Input Indicator Block (PVI)

This function block displays an input signal from the I/O modules or from the other
blocks as process variable (PV). It can also output the process variable (PV) from the
OUT terminal.
This block may be used only for indicating the process variable.
■ Input Indicator Block (PVI)

▼ Connection
The figure below shows a function block diagram of the Input Indicator Block (PVI):
Input
IN PV OUT
processing
(PV, PV)
SUB
D010201E.EPS
Figure Function Block Diagram of Input Indicator Block (PVI)
The table below shows the connection method and connected destination of the I/O termi-
nals of the Input Indicator Block (PVI):
Table Connection Method and Connected Destination of I/O Terminals of Input Indicator Block
(PVI)
Connection method Connection destination

I/O terminal Data Data Terminal Process Software Function
reference setting connection I/O I/O block
IN Measurement input
Process variable
OUT
output
SUB Auxiliary output
D010202E.EPS
: Connection allowed
Blank: Connection not allowed
: Connection allowed only when connecting to a switch block (SW-33, SW-91) or inter-station data link block (ADL).
■ Function of Input Indicator Block (PVI) ¡ £

The PVI block performs input processing, output processing, and alarm processing.
The only processing timing available for the PVI block is a periodic 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. Moreover, it is
possible to specify the scan coefficient and the scan phase.
*1: ¡ £ The medium-speed scan period can only be used for the KFCS2, KFCS, LFCS2 and LFCS.
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the PVI block,
see D1.1.3, “Input Processing, Output Processing, and Alarm Processing Possible for Each Regulatory
Control Block.”
• For details on the input processing, see C3, “Input Processing.”
• For details on the output processing, see C4, “Output Processing.”
• For details on the alarm processing, see C5, “Alarm Processing-FCS.”

<Toc> <Ind> <D1.2 Input Indicator Block (PVI)> D1-22
■ Data Items - PVI
Table Data Items of Input Indicator Block (PVI)
Data Entry Permitted
Data Name Range Default
Item or Not
MODE Block mode ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- 0
AF Alarm detection specification ----- 0
AOFS Alarm masking specification ----- 0
PV Process variable (*1) PV engineering unit value SL
RAW Raw input data Value in the unit at the connection destination -----
SUM Totalizer value Engineering unit value 0
HH High - high limit alarm setpoint SL to SH SH
LL Low - low limit alarm setpoint SL to SH SL
PH High - limit alarm setpoint SL to SH SH
PL Low - limit alarm setpoint SL to SH SL
VL Velocity alarm setpoint (SH - SL) SH - SL
PVP Velocity-Reference Sample Value in the same engineering unit as PV -----
OPMK Operation mark 0 to 255 0
UAID User application ID ----- 0
SH PV scale high limit Value in the same engineering unit as PV -----
SL PV scale low limit Value in the same engineering unit as PV -----
D010203E.EPS
: Entry is permitted unconditionally

Blank: Entry is not permitted
: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL
SEE ALSO
For a list of valid block modes of the PVI block, see D1.1.4, “Valid Block Modes for Each Regulatory
Control Block.”

<Toc> <Ind> <D1.3 Input Indicator Block with Deviation Alarm (PVI-DV)> D1-23
D1.3 Input Indicator Block with Deviation Alarm

(PVI-DV)
The Input Indicator Block with Deviation Alarm (PVI-DV) displays an input signal as a
process variable (PV), provides the deviation alarm function, and outputs a PV from
the OUT terminal. This block is used for PV display, and deviation alarm indicating
the difference between a PV and a setpoint value (SV).
■ Input Indicator Block with Deviation Alarm (PVI-DV)

▼ Connection
The Input Indicator Block with Deviation Alarm (PVI-DV) displays an input signal received
from an I/O module or other function block as a process variable (PV).
In addition to the function to display an input signal as a process variable (PV), Input Indica-
tor Block with Deviation Alarm (PVI-DV) provides two other functions: “deviation alarm
check” and “setpoint value limiter.”
By presetting a deviation alarm setpoint (DL), the deviation (DV) of the setpoint value (SV)
from process variable (PV) can be confirmed.
The figure below shows a function block diagram of Input Indicator Block with Deviation
Alarm (PVI-DV):
-
SV DV
+
Input
IN PV OUT
processing
(PV, PV)
SUB
D010301E.EPS
Figure Function Block Diagram of Input Indicator Block with Deviation Alarm (PVI-DV)
The table below shows the connection methods and connected destinations of the I/O
terminals of Input Indicator Block with Deviation Alarm (PVI-DV):
Table Connection Methods and Connected Destinations of I/O Terminals of Input Indicator Block
with Deviation Alarm (PVI)

Process variable
OUT
output
D010302E.EPS

■ Function of Input Indicator Block with Deviation Alarm (PVI-DV) ¡ £
The PVI-DV block performs input processing, output processing, and alarm processing.
The only processing timing available for the PVI-DV block is a periodic startup. Selections
period, the medium-speed scan period (*1), and the high-speed scan period. Moreover, it is
possible to specify the scan coefficient and the scan phase.
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the PVI-DV block,
Control Block.”
This section describes the deviation alarm check function and the setpoint value limiter
function, which constitute some of the processing performed by the PVI-DV block.
■ Deviation Alarm Check

The deviation alarm check function generates a deviation alarm when the absolute value of
deviation (DV) between the setpoint value (SV) and process variable (PV) exceeds the
absolute value of the preset deviation alarm setpoint (DL).
• When the deviation (DV) exceeds the high limit of the deviation alarm setpoint (DL):
A positive deviation alarm (DV+) is generated.
• When the deviation (DV) falls below the low limit of the deviation alarm setpoint (DL):
A negative deviation alarm (DV-) is generated.
The deviation (DV) of the process variable (PV) from the setpoint value (SV) is represented
by the following expression:
DV=PV-SV
SEE ALSO
For the details of the deviation alarm check, see C5.6, “Deviation Alarm Check.”

■ Setpoint Value Limiter
The setpoint value limiter function limits the setpoint value (SV) within a range between the
setpoint high limit (SVH) and setpoint low limit (SVL).
The actions of the setpoint value limiter are described below:
• When a value exceeding the setpoint high limit (SVH) or high alarm setpoint (PH) is
set as a setpoint value (SV):
An acknowledgment dialog box appears to prompt for the operator’s confirmation. To
check alarm operation, the operator can set a value exceed the setpoint high limit
(SVH) or high alarm setpoint (PH).
• When a value below the setpoint low limit (SVL) or low alarm setpoint (PL) is set as a
setpoint value (SV):
An acknowledgment dialog box appears to prompt for the operator’s confirmation. To
check alarm operation, the operator can set a value exceed the setpoint low limit
(SVL) or low alarm setpoint (PL).
The parameters of the setpoint value limiter:

• Setpoint high limit (SVH):
Engineering unit data within the PV scale range.
The default is the scale’s high limit.
• Setpoint low limit (SVL):
Engineering unit data within the PV scale range.
The default is the scale’s low limit.

■ Data Items – PVI-DV
Table Data Items of Input Indicator Block with Deviation Alarm (PVI-DV)
Item or Not
SV Setpoint value Value in the same engineering unit as PV SL
DV Deviation Value in the same engineering unit as PV 0
DL Deviation alarm setpoint (SH - SL) SH - SL
SVH Setpoint high limit SL to SH SH
SVL Setpoint low limit SL to SH SL
D010303E.EPS

SEE ALSO
For a list of valid block modes of the PVI-DV block, see D1.1.4, “Valid Block Modes for Each Regulatory
Control Block.”

<Toc> <Ind> <D1.4 Control Computation Processing Common to Controller Blocks> D1-27
D1.4 Control Computation Processing Common to

Controller Blocks
The various types of controller blocks, represented by PID controller, have some
common computation processing functions. This chapter explains the control
computation processing functions that are common to multiple controller blocks.
The control computation processing functions specific to each controller block are
explained in the section of the corresponding controller block.

■ Control Computation Processing Common to Controller Blocks
The table below shows the control computation processing functions that are common to
multiple controller blocks:
Table Control Computation Processing Common to Controller Blocks (1/2)
Control computation processing Description

Changes the proportional gain in accordance with the degree of deviation so that the
Non-linear gain
relationship between the deviation and control output change (MV) becomes non-linear.
Lowers the proportional gain to moderate control effects when the deviation is within the
Gap action
gap width (GW) range.
Changes the proportional gain according to the degree of deviation when the deviation is
Squared deviation action
within the gap width (GW) range.
Converts the manipulated output change (MV) during each control period to an actual
Control output action manipulated output value (MV). The control output actions include “positional type” and
“velocity type.”
Switches the direction of the output action (reverse action or direct action) in accordance
Control action direction
with the increase or decrease in deviation.
Performs correction computation using values read from the connection destinations of
Reset limit function input terminals RL1 and RL2 during PID control computation. This function prevents
reset windup.
Adjusts the manipulated output change (MV) to “0” when the deviation is within the
Deadband action
deadband range, in order to stop the manipulated output value (MV) from changing.
I/O compensation Adds the I/O compensated value (VN) received from outside to the input signal or control
output signal of PID computation when the controller block is operating automatically.
Adds the I/O compensated value (VN) received from the outside to the input signal of the
Input compensation
PID control computation.
Adds the I/O compensated value (VN) received from outside to the output signal of the
Output compensation
Process variable tracking Causes the setpoint value (SV) to agree with the process variable (PV).
Setpoint value limiter Limits the setpoint value (SV) within the setpoint high/low limits (SVH, SVL).
Setpoint value pushback Causes two of the three setpoint values (SV, CSV, RSV) to agree with the remaining one.
D010401E.EPS

Table Control Computation Processing Common to Controller Blocks (2/2)
Switches the manipulated output value (MV) without causing it to change abruptly when
Bumpless switching the block mode has been changed or when the manipulated output value (MV) has been
switched in a downstream block in cascade.
Changes the block mode to IMAN to temporarily suspend the control action. This action
Initialization manual
takes place when the initialization manual condition becomes satisfied.
Temporarily suspends the control action while maintaining the current block mode.
Control hold
During control hold, the output action is performed normally.
Changes the block mode to MAN to forcibly stop the control action. This action takes
MAN fallback
place when the MAN fallback condition becomes satisfied.
Changes the block mode to AUT when the function block is operating in the CAS or PRD
AUT fallback mode, so that the control action is continued using values set by the operator. This action
takes place when the AUT fallback condition becomes satisfied.
Temporarily suspends the control action and switches to the computer backup mode when
an error has been detected at a supervisory computer while the function block is operating
Computer failure
in the RCAS or ROUT mode. This action takes place when the computer failure condition
becomes satisfied.
Stops the control action of function blocks currently operating automatically, while
Block mode change interlock
disabling the stopped function blocks from changing to the automatic operating mode.
Outputs the cascade setpoint value (CSV) after converting it to a manipulated output value
PRD mode action
(MV) when the block mode has been changed to PRD.
D010402E.EPS
SEE ALSO
For the control computation processing functions specific to each controller block, see a the chapter or
section of the corresponding controller block in D1.5, “PID Controller Block (PID)” through D1.13, “Self-
Tuning PID Controller Block (PID-STC).”

■ Non-Linear Gain
▼ Non-Linear Gain
The non-linear gain function changes the proportional gain in accordance with the deviation
of the process variable (PV) from the setpoint value (SV) in the control computation. As a
result, a non-linear relationship is formed between the manipulated output change (MV)
and the deviation of the process variable (PV) from setpoint value (SV).
The non-linear gain function is used for pH control, in which the process gain often be-
comes too high near the target value, or for buffer tank level control, whose purpose is to
stabilize the discharge volume while maintaining the tank level within the limits.
The actions that realize the non-linear gain function include “gap actions” and “squared
deviation actions.”
● Processing Flow of Non-Linear Gain

The non-linear gain function calculates the control output change (MV), using the effective
proportional gain (Kpe) obtained through non-linear correction of proportional gain (Kp).
The figure below shows a flow of the non-linear gain.
PID
MV
computation
Kpe
Non-linear
En MV: Manipulated output change
gain computation
Kpe: Effective proportional gain
En: Deviation
GW: Gap width
GW Kp Kp: Proportional gain
D010403E.EPS
Figure Processing Flow of the Non-Linear Gain
● Setting Non-Linear Gain

Use the Function Block Detail Builder to set the non-linear gain.
• Non-linear gain:
Select “No,” “Gap Action” or “Squared Deviation Action.”

■ Gap Action
The gap action moderates control effects by lowering the proportional gain when the
deviation is within the preset gap width (GW).
● Non-Linear Gain Characteristics of Gap Action

If a non-linear gain coefficient (Knl) has been set, the effective proportional gain (Kpe) is
obtained by the following expression when the deviation is within the gap width (GW):
Kpe=Kp • Knl
Once the deviation exceeds the limits of the gap width (GW), the effective proportional gain
(Kpe) is obtained by the following expression:
GW
Kpe= 1-(1-Knl) • • Kp
| En | D010404E.EPS
The figure below shows the non-linear gain characteristics of the gap action:
Equivalent
deviation Knl=1.0
Effective proportional (En')
gain (Kpe) Knl=0.5
Knl=1.0 Knl=0.25
Kp
Knl=0.0
0
Knl=0.5 Deviation (En)

0.5
Knl=0.25
0.25
Knl=0.0 Equivalent deviation:
The deviation equivalent to a state
0 Gap width Gap width Gap width in which no non-linear gain is specified.
Deviation (En)
(GW) (GW) (GW)
D010405E.EPS
Figure Non-Linear Gain Characteristics of Gap Action

● Setting Gap Action
Use the Function Block Detail Builder to set the non-linear gain coefficient.
• Gap Gain: Select “1.0,” “0.5,” “0.25” or “0.”
The default is “1.0.”
Table Relationship between the Non-linear Gain Coefficient and Effective Proportional Gain
Gain coefficient (Knl) | En | GW | En |>GW
1.0 (linear) - -
1 Kp GW
0.5 (1 - ) Kp
4 2 | En |
1 Kp 3GW
0.25 (1- ) Kp
2 4 | En |
GW
0 0 (1 - ) Kp
| En |
D010406E.EPS
● Set Parameter of Gap Action

The parameter of the gap action:
• Gap width (GW):
Engineering unit data between 0 and the PV scale span range limit.
The default is 0.

■ Squared Deviation Action
The squared deviation action changes the proportional gain in proportion to the degree of
deviation when the deviation is within the preset gap width (GW).
● Non-Linear Gain Characteristics of Squared Deviation Action

If a gap width (GW) has been set, the effective proportional gain (Kpe) is obtained by the
following expression when the deviation is within the gap width (GW):
| En |
Kpe= • Kp
GW D010407E.EPS
Once the deviation exceeds the limits of the gap width (GW), the effective proportional gain
(Kpe) is represented by the following expression:
Kpe=Kp
The figure below shows the non-linear characteristics of the squared deviation action:
Effective proportional Equivalent

gain (Kpe) deviation
(En')
0
Kp
Deviation (En)
Equivalent deviation:
The deviation equivalent to a state
0 Gap width Gap width Gap width in which no non-linear gain is specified.
Deviation (En)
(GW) (GW) (GW)
D010408E.EPS
Figure Non-Linear Characteristics of the Squared Deviation Action
● Set Parameter of Squared Deviation Action

The parameter of the squared deviation action:
• Gap width (GW):
The default is 0.

■ Control Output Action
The control output action converts the manipulated output change (MV) during each
control period to an actual manipulated output value (MV). There are two types of control
output actions: velocity type and positional type.
● Velocity Type
Adds the current manipulated output change (MV) to the value readback from the output
destination (MVrb) and determines the manipulated output value (MVn).
The computational expression of the velocity-type control output action is shown below:
MVn=MVrb+MVn
● Positional Type
Adds the current manipulated output change (MV) to the previous output value (MVn-1)
and determines the manipulated output value (MVn).
The computational expression of the positional-type control output action is shown below:
MVn=MVn-1+MVn
● Setting Control Calculation Output Action

Use the Function Block Detail Builder to set the control calculation output action.
• Control Calculation Output Type:
Select “Velocity Output Action” or “Positional Output Action.”
The default is “Positional Output Action.”

■ Control Action Direction
▼ Control Action
The control action direction function switches between direct action and reverse action that
reflect the increase or decrease of manipulated output value.
● Direct Action and Reverse Action

The direct action and reverse action indicate the increase and decrease directions of the
manipulated output value (MV) corresponding to deviation changes.
When the setpoint value (SV) is fixed, the relationship between the process value (PV) and
the manipulated output value (MV) in direct action and the reversed action is shown as
follows.
• Direct action
The control action in which the manipulated output value (MV) increases as the
process variable (PV) increases, or decreases as the process variable decreases.
• Reverse action
The control action in which the manipulated output value (MV) decreases as the
process variable (PV) increases, or increases as the process variable decreases.
● Setting Control Action Direction

Use the Function Block Detail Builder to set the control action direction:
• Control Action: Select “Direct” or “Reverse.”
The default is “Reverse.”

■ Reset Limit Function
The reset limit function prevents the occurrence of reset windup (integral saturation) by
setting limits to the integral term in PID control computation. The reset limit function is
applied only to the positional-type control output actions.
● Reset Windup
In PID control computation, the value obtained via the integral action represents an inte-
grated value of deviation by time. Therefore, when a batch control stops, if the deviation
prolongs, the integral term in PID control computation becomes saturated due to the
integral action. This condition is called “reset windup (integral saturation).”
For example, reset windup often occurs in the following situation:
• The control computation value exceed the manipulated variable high-limit or low-limit
setpoint (MH, ML) and the output is limited by the H/L limiter.
• The output to the manipulation terminal is switched off by an Auto-selector blocks, etc.
• Manipulated output is used as the additional signal from a PID controller block (PID)
for the purpose of fine-adjust of the base load feedforward control.
When reset windup occurs, the control result tends to overshoot, and as a result the pro-
cess becomes unstable. In a control loop that reset windup may happen, you should select
positional-type control output action and use the reset limit function.

● Reset Limit Function
The reset limit function carries out the correction to the PID control computation with the
values read from the connected destinations via the RL1 and RL2 terminals.
The values read from the connected destinations via RL1 and RL2 terminals are used as
reset signals RLV1 and RLV2. The reset signals RLV1, RLV2 are used to perform the
following correction computation to the output value of PID computation (MVn0). Thus,
when the output MV is limited by the manipulated variable high-limit and low-limit setpoints
(MH, ML), the reset limit exerts directly on the integral term of the output value (MV'), the
value before MV in computation.
If the RL1 terminal is not connected, the value readback from the output destination is used
as the reset signal value RLV1. If the RL2 terminal is not connected, “0” is used in computa-
tion as reset signal RLV2.
T
MVn=MVn0+ (RLV1-RLV2-MV'n-1)
TI D010409E.EPS
MV: Manipulated output change (after correction)

MVn0: PID computed value (manipulated output change before correction)
MV'n-1: Previously computed MV value (value before output limiting)
RLV1: Reset signal from the RL1 terminal
RLV2: Reset signal from the RL2 terminal
T: Control period
TI: Integral time
The following phenomena occur during velocity-type Control Action:

• Reset windup
Normally reset windup do not happen to the velocity-type control output actions, since
the cumulative value of manipulated output changes (MV) of each scan period is
limited. However, if the values readback from the output destination are not limited by
the MV H/L scale setpoints nor by the MV H/L limiter, the manipulated output change
(MV) of each scan period is accumulated, similar to the positional-type actions.
Consequently, the reset windup happens.
• Output excess pullback phenomenon
When the manipulated output value (MV) is limited by the manipulated variable high-
limit or low-limit setpoint (MH, ML) as a result of changes caused by pulse-type distur-
bances, an output excess pullback phenomenon happens if the control output action
is velocity type.
When the manipulated output value was limited by the manipulated variable high-limit
or low-limit setpoint (MH, ML), a significant change in the process variable (PV)
caused by disturbances can pullback the manipulated output value (MV) excessively
from the original value. When the disturbance disappears, the process variable re-
turns to the original level. This is called the “output excess pullback phenomenon.”
This phenomenon happens because the manipulated output value (MV) are limited by
the manipulated variable high-limit or low-limit setpoint (MH, ML). The current MV
limited by the limiter is added with a delta MV caused by the disturbance negative to
the current MV direction.
The output excess pullback phenomenon does not happen if the control output action
is positional type since the proportional term of the manipulated output value (MV) is
not limited by the manipulated variable high-limit or low-limit setpoint (MH, ML).

● Example for Positional-Type Control Output Action
The following section explains the example that how the reset limit acts when the control
computation value of the function block with positional-type output action exceed the
manipulated variable high-limit or low-limit setpoint (MH, ML).
With a positional-type control output action, the control computation value in the current
control period (MV'n) is the sum of the manipulated output change (MVn) obtained from
the current PID computation, and the control computation value in the previous control
period (MV'n-1).
MV'n=MVn+MV'n-1
The control computation value (MV'n) in the current control period limited by the manipu-
lated variable high-limit and low-limit setpoints (MH, ML) is output as the manipulated
output value (MVn).
The figure below shows an example of the reset limit function for the positional-type control
output action:
Control computation
Output
DMVn destination data
PID +
MV'n Output limiter MVn OUT
computation
+
RLV1 RLV2
RL1 RL2
D010410E.EPS
Figure Reset Limit Function for a Positional-Type Control Output Action
When the reset limit function is not used, positive or negative values is continuously added
to the integral term of the manipulated output change (MV) so long the positive or nega-
tive deviation exists. If the situation sustains, the manipulated output change (MV) is
added to the control computation value (MV') continuously and make it reach the MV scale
high limit (MSH) or the MV scale low limit (MSL) or the manipulated variable high-limit or
low-limit setpoint (MH, ML) and continue to windup. As a result, saturation (reset windup)
happens to the integral term of the control computation value (MV'). Because the integral
term is saturated, the manipulated output value (MV) limited by the limiter does not move
back even when the sign of deviation changes to the pullback direction. The MV starts to
pullback only when the control computation value (MV') returns to the range between the
manipulated output high-limit and low-limit setpoints (MH, ML).
In the same situation, if the reset limit function is used, the integral term of the manipulated
output value (MV') will be limited to the value “RLV1 - RLV2” as a result of correction com-
putation. Even if the deviation sustains, the reset windup does not happens.

Example on the “Figure Reset Limit Function for a Positional-Type Control Output Action,”
neither the RL1 or RL2 terminal is connected. Therefore, the reset signal RLV1 is the
readback value from the output destination, while the value of reset signal RLV2 is “0.” For
example, suppose a loop is in cascade (CAS) mode, if the manipulated output (MV) is
limited by the manipulated variable high-limit setpoint (MH), the reset signal RLV1 becomes
the manipulated variable high-limit setpoint (MH). In this situation, the integral term of the
control computation value (MV') is adjusted gradually to the value obtained by subtracting
RLV2 from RLV1 (i.e., MH), even when the deviation sustains, it does not exceed the
manipulated variable high-limit setpoint (MH).
The manipulated output value (MV) will quickly move away from the limit when the sign of
the manipulated output change (MV) reverses and agrees to the pullback direction of the
value from output limiting. This is because the control computation value (MV') is limited
within the manipulated variable high-limit and low-limit setpoints (MH, ML).
● Example for a Simple Cascade Control loop

The figure below shows an application example of using the reset limit function to a simple
cascade control loop. The RL1 and RL2 terminals are not connected.
Since the RL1 or RL2 terminals are not connected the reset signal RLV1 becomes the
readback value from the output destination and the value of the reset signal RLV2 becomes
“0.”
If use the readback value of the manipulated output value (MV) output destination to
compute the difference of the two reset signals (RLV1 - RLV2), there is no need to have
terminal RL1 or RL2 connected.
RLV1
IN OUT SET OUT

PID PID
D010411E.EPS
Figure Reset Limit Function for a Simple Cascade Control loop

● Application Example to Auto-Selection via Auto-Selector Blocks (AS-H)
The figure below shows an example of the reset limit function when automatically selecting
the signals from two function blocks using an Auto-selector blocks (AS-H).
Suppose the two PID Controller Blocks (PID) on the left side of the figure are velocity-type,
even when the deviation is within the switching point, the disturbance of the process vari-
able may trigger the output excess pullback to the manipulated output value (MV). Thus
make the Auto-selector blocks (AS-H) switch temporarily to the other controller. To define
the positional-type output action using the reset limit function can avoid this happening.
RL1
IN OUT
PID
IN1
OUT SET OUT

AS-H PID
IN2 IN
IN OUT
PID
RL1
D010412E.EPS
Figure Reset Limit Function Used for Auto-Selection via Auto-Selector Blocks (AS-H)
● Application Example in Feedforward Control

The figure below shows an example of the reset limit function used in feedforward control.
This example assumes base load control that uses the feedforward signals from the OUT
terminal of the General-Purpose Calculation Block (CALCU) as the base load values. To
prevent reset windup of the upstream PID Controller Block (PID), the RL2 terminal refer-
ences the feedforward signals, while the RL1 terminal references the process variable of
the downstream PID Controller Block (PID).
IN
CALCU
OUT
RL2 SET
IN OUT IN OUT SET OUT

PID FFSUM PID
RL1 IN
D010413E.EPS
Figure Reset Limit Function Used in Feedforward Control (Base Load Control)

■ Deadband Action
▼ Deadband Action
The deadband action stops the manipulated output value (MV) from changing while the
deviation (DV) is within the preset deadband (DB) range, by causing the manipulated
output change (MV) to be “0.”
● Characteristics of Deadband Action

The deadband action causes the manipulated output change (MVn) to be “0” when the
absolute value of the deviation (DV) minus the hysteresis value becomes smaller than the
deadband width (DB). When the absolute value of deviation (DV) increases greater than
the deadband width (DB), the manipulated output change after the deadband action
(MVn) will be brought back to the manipulated output change before the deadband action
(MVn0).
The figure below shows the characteristics of the deadband action:
Output (MVn)
HYS HYS
MVn0
En
DB DB
MVn: Manipulated output change after the deadband action

MVn0: Manipulated output change before the deadband action
DB: Deadband width
En: Deviation (data of the same unit as PV)
HYS: Hysteresis (data of the same unit as PV)
D010414E.EPS
Figure Characteristics of Deadband Action
● Setting Deadband Action

Use the Function Block Detail Builder to set the deadband action.
• Deadband action: Select “Yes” or “No.”
When the deadband action is set as “Yes,” the hysteresis (HYS) must be set. Use the
Function Block Detail Builder to set the hysteresis (HYS).
• Hysteresis:
The default is the value equivalent to 1.0 % of the PV scale span.
● Set Parameter of Deadband Action

The parameter of the deadband action:
• Deadband width (DB):
The default is 0.

■ Input or Output Compensation
▼ I/O Compensation
The Input or Output Compensation function adds the compensation value (VN) received
from outside to the input signal or output signal of PID control computation, while the
controller block is operating automatically in the automatic (AUT), cascade (CAS), or
remote cascade (RCAS) mode.
The Control Action of Input or Output Compensation include the following two types:
• Input compensation
• Output compensation
The compensation value (VN) is reset to “0” automatically at the beginning of each control
period. This prevents the previous external compensation value is added to (VN) when the
external compensation data not exist.
Normally, the external data is set directly to the compensation value (VN) from other func-
tion block. However, the external data from other function block can be connected to the
compensation input terminal (BIN), then set to the compensation value (VN).
For manual operation, the manually set manipulated output value (MV) is not affected by
the Input or Output Compensation.
● Define Input or Output Compensation

Use the Function Block Detail Builder to define the Input or Output compensation.
• I/O Compensation: Select “No,” “Input Compensation” or “Output Compensation.”
For the 2-Position ON/OFF Controller Block (ONOFF), 3-Position ON/OFF Controller Block
(ONOFF-G), PD Controller Block with Manual Reset (PD-MR) and Feedforward Signal
Summing Block (FFSUM), only the input compensation can be defined.
• Input Compensation: Select “No” or “Input Compensation.”
● Set Parameters of I/O Compensation

The parameters of the I/O compensation:
• I/O compensation gain (CK): -10.000 to +10.000.
The default is 1.000.
• I/O compensation bias (CB): Arbitrary engineering unit data.
The default is 0.0.

■ Input Compensation
▼ Input Compensation
The input compensation is a control action that adds the compensation value (VN) received
from outside to the input signal of PID control computation.
● Characteristics of Input Compensation

The computational expression of the input compensation:
CVn=PVn+CK(VN+CB)
CVn: Control variable (PV after input compensation)

PVn: Process variable
CK: I/O compensation gain
CB: I/O compensation bias (internal bias)
VN: I/O compensated value (bias signal)
The figure below shows a processing flow of the input compensation:
VN
+
+
CB
CK
+
PVn CVn MV
PV PID control computation
+
D010415E.EPS
Figure Processing Flow of the Input Compensation
● Example Using Input Compensation

The input compensation is used to improve the controllability of a process with a long dead
time, by subtracting from the input signal the signal from the Dead-Time Compensation
Block (DLAY-C) to perform PID control computation (Smith Dead Time Compensation).
The figure below shows an example of dead time compensation:
PID
IN OUT
VN
DLAY-C
D010416E.EPS
Figure Example of Dead Time Compensation

■ Output Compensation
The output compensation is a control action that adds the I/O compensated value (VN)
received from the outside to the output signal of PID control computation.
● Characteristics of the Output Compensation

The computational expression of the output compensation:
MVn=MVn0+CK(VN+CB)
MVn: Manipulated output after output compensation

MVn0: manipulated output before output compensation
The figure below shows a processing flow of the output compensation:
VN
+
+
CB
CK
+
PVn PID control MVn0 MVn
PV
computation +
D010417E.EPS
Figure Processing Flow of the Output Compensation
● Example of Using the Output Compensation

The output compensation is used for feedforward control that adds the feedforward signal
to the control output signal, or for non-interacting control that adds the output signal from
the interacting loop to the control output signal.
The figure below shows an example of feedforward control:
IN OUT
CALCU
PID
IN OUT
VN
D010418E.EPS
Figure Example of Feedforward Control

■ Process Variable Tracking (Measurement Tracking)
▼ Measurement Tracking
The process variable tracking function prevent the abrupt changes in the manipulated
output value (MV) when change from the manual (MAN) mode to automatic (AUT) mode,
by forcing the setpoint value (SV) to agree with the process variable (PV).
● Characteristics of Process Variable Tracking

When switching from the manual (MAN) mode to automatic (AUT) mode, the existence of a
large deviation is harmful, since it makes the manipulated output change (MV) very large.
If force the setpoint value (SV) to agree with the process variable (PV) in manual mode
operation via process variable tracking, abrupt Control Action can be avoided when the
mode switches to automatic (AUT).
Suppose a primary loop is in cascade connection and controls in the automatic (AUT) or
cascade (CAS) mode. If the mode of the secondary loop in the cascade connection
switches from cascade (CAS) to automatic (AUT), the cascade connection becomes open
and the control action of the primary side loop can stop. In this situation, the setpoint value
(SV) of the primary loop can be forced to agree with the process variable (PV) by the
process variable tracking function.
● Define Process Variable Tracking

Use the Function Block Detail Builder to define the process variable tracking.
• Measurement tracking
MAN mode: Select “Yes” or “No.”
AUT and CND mode: Select “Yes” or “No.”
CAS and CND mode: Select “Yes” or “No.”
The default is “Yes.”
The statuses referred to as MAN, AUT and CAS include remote backup modes such
as AUT (ROUT) and AUT (RCAS).
For a 2-Position ON/OFF Controller Block (ONOFF), 3-Position ON/OFF Controller Block
(ONOFF-G) or Time - Proportioning ON/OFF Controller Block (PID-TP), the definition is
allowed for MAN mode only.

The setpoint value limiter function limits the setpoint value (SV) within a range between the
setpoint high limit (SVH) and setpoint low limit (SVL).
The action of the setpoint value limiter varies with the block mode of the function block.
● Actions in the Automatic or Manual Mode

When the function block is in automatic (AUT) or manual (MAN) mode, the user is able to
set the setpoint value (SV). The setpoint value limiter performs the following actions:
• When try to set a setpoint value (SV) exceed the setpoint high limit (SVH) or high limit
alarm setpoint (PH):
An acknowledgment dialog box appears to prompt for the operator’s confirmation.
When confirms, the operator can set a value exceed the setpoint high limit (SVH) or
high limit alarm setpoint (PH).
• When try to set a setpoint value (SV) below the setpoint low limit (SVL) or low limit
alarm setpoint (PL):
When confirms, the operator can set a value below the setpoint low limit (SVL) or low
limit alarm setpoint (PL).
● Actions in the Remote Cascade Mode

When the function block is in remote cascade (RCAS) mode and the setpoint value (SV) is
defined to automatically follow the remote setpoint value (RSV) received from the supervi-
sory system computer, the setpoint value limiter performs the following actions:
• The value exceeds the setpoint high limit (SVH) is forced to be equal to the setpoint
high limit (SVH).
• The value smaller than the setpoint low limit (SVL) is forced to be equal to the setpoint
low limit (SVL).
● Set Parameters of the Setpoint Value Limiter

• Setpoint high limit (SVH): Engineering unit data within the PV scale range.
The default is the scale high limit.
• Setpoint low limit (SVL): Engineering unit data within the PV scale range.
The default is the scale low limit.

■ Setpoint Value Pushback
The setpoint value pushback function sets the same value for the three types of setpoint
values (SV, CSV, RSV). The figure below explains the relationship among the setpoint
value (SV), cascade setpoint value (CSV) and remote setpoint value (RSV):
Set from the supervisory computer Input from the SET terminal
RSV CSV
AUT/MAN
RCAS CAS
SV
Setpoint value
Control
computation
D010419E.EPS
Figure Relationship among Setpoint Values (SV, CSV and RSV)
The action of the setpoint value pushback varies in accordance with the block mode of the
function block.
● Action in the Automatic (AUT) or Manual (MAN) Mode

Causes the cascade setpoint value (CSV) and remote setpoint value (RSV) to agree with
the setpoint value (SV). Even when a data value is set to the setpoint value (SV) from
outside the function block, the same value is automatically set to the cascade setpoint
value (CSV) and remote setpoint value (RSV).
● Action in the Cascade (CAS) Mode

Force the setpoint value (SV) and remote setpoint value (RSV) to be equal to the cascade
setpoint value (CSV).
● Action in the Remote Cascade (RCAS) Mode

Force the setpoint value (SV) and cascade setpoint value (CSV) to be equal to the remote
setpoint value (RSV).

■ Bumpless Switching
The bumpless switching function switches the block mode of the function block or manipu-
lated output value downstream in cascade without causing the manipulated output value
(MV) to change abruptly (i.e., bumpless change).
The action during bumpless switching varies with the control output action and block mode
status.
● Action for Velocity-Type Control Output Action

For a velocity-type control output action, the manipulated output change (MVn) obtained
by control computation is added to the present value readback from the connected destina-
tion. Therefore, the block mode or cascade switch can be changed without causing an
abrupt change in the manipulated output value (MV).
● Action for Positional-Type Control Output Action

For a positional-type control action, when the function block mode changes to tracking
(TRK) mode, or when the cascade connection to the downstream is open then close again,
or for the similar reason the cascade control loop regain the control, the manipulated output
value (MV) may change abruptly. To prevent this, the output value is forced to be equal (or
to track) to the value of the output destination while the control action stops. This enables
the block mode switch causes no abrupt change in the manipulated output value (MV).
● Action when a Cascade Connected Downstream Loop Changes from

Automatic (AUT) to Cascade
When a cascade connected downstream loop changes its mode from automatic (AUT) to
cascade (CAS), the tracking process described above is performed in the upstream loop if
the downstream is only connected to one loop. Therefore, the block mode switches without
causing an abrupt change in the manipulated output value (MV).

● Action when Manipulated Output of an Upstream Loop is Connected to
Multiple Downstream Loops as Setpoint Value
When multiple downstream loops are receiving the manipulated output signals of an
upstream loop as setpoint value signals via a Cascade Signal Distributor Block (FOUT),
Control Signal Splitter Block (SPLIT) or switch block (SW-33, SW-91), the setpoint value
downstream may change abruptly. In this case, control computation is not performed in
downstream loops in the first control period following the switching of modes from auto-
matic (AUT) to cascade (CAS). In other words, the block mode can be changed without
causing an abrupt change in the output as a result of a proportional or derivative action, by
resuming the control computation from the next control period in which the change in the
setpoint value caused by the block mode change will not be reflected by the change in the
deviation (En).
The figure below shows an example of a multiple downstream loop configuration:
JO1 SET
PID
OUT SET
PID FOUT
JO8
SET
PID
D010420E.EPS
Figure Example of a Multiple Downstream Loop Configuration (when a Cascade Signal

Distributor Block is Used)
SET
PID
OUT1
OUT SET
PID SPLIT OUT2
SET
PID
D010421E.EPS
Figure Example of a Multiple Downstream Loop Configuration (when a Control Signal Splitter
Block is Used)
SET
PID
S11
OUT S10 S12 SET
PID SW33 PID
S13
SET
PID
D010422E.EPS
Figure Example of a Multiple Downstream Loop Configuration (when a Switch Block is Used)

■ Initialization Manual
The initialization manual is an error processing function that suspends the control action
temporarily by changing the block mode to initialization manual (IMAN). This action takes
place when the initialization manual condition is established.
● Characteristics of the Initialization Manual

The initialization manual function suspends the control action and control output action
temporarily during the automatic (AUT) mode or other automatic control operation mode
when the initialization manual condition is established, and changes the function block to
initialization manual (IMAN) mode.
Since the initialization manual action causes the manipulated output value (MV) to track the
value of the connected destination, even when the mode changes from initialization manual
(IMAN) mode to manual (MAN) mode, the initialization manual (IMAN) mode will precede
the manual (MAN) mode. Therefore, the manual (MAN) mode does not take effect.
The block returns to the original mode as soon as the initialization manual condition van-
ishes. However, if the mode change operation is performed in the initialization manual
(IMAN) mode, the block will switch to the mode of this operation after the initialization
manual condition vanishes.
● Initialization Manual Condition

The initialization manual condition is a block mode transition condition. It suspends the
control action and control output action temporarily by changing the block mode to initializa-
tion manual (IMAN) mode.
The initialization manual (IMAN) block mode becomes active only when the initialization
manual condition is established.
The initialization manual condition is depicted as follows:
AUT
? Initialization manual condition is established
IMAN (AUT)
? Initialization manual condition vanishes
AUT
The initialization manual condition is established in the following situation:

• When the manipulated output value (MV) connected destination’s data status is
conditional (CND) (i.e., the cascade loop open).
communication error (NCOM) or output failure (PTPF).
• When the manipulated output value (MV) connected destination is a switch block
(SW-33, SW-91) and the cascade connection is switched off (i.e., the cascade loop
open).
• When the manipulated output value (MV) connected destination is a process output,
and a failure or output open alarm has occurred in the process output.
• When the data status of the input signal at the TIN or TSI terminals become invalid
(BAD) in the tracking (TRK) mode while the output signal is not a pulse-width type.

■ Control Hold
The control hold is an error processing function that suspends the control action tempo-
rarily while maintaining the current block mode. Unlike initialization manual, the control
output action is performed normally during control hold.
The control hold action takes place when the following conditions are established during
automatic operation (AUT, CAS, PRD, RCAS, ROUT):
• The connected destination of the IN terminal is open (i.e., not selected via a selector
switch, etc.) and,
• The connected destination of the IN terminal or the connected destination of the data
at the first connected destination is a process input, and the process input is tempo-
rarily in a non-response state (momentary power failure).
The control is resumed when the conditions vanish.

■ MAN Fallback
The MAN fallback is an error processing function that stops the control forcibly by changing
the block mode to manual (MAN). This action takes place when the MAN fallback condition
is established.
● Characteristics of the Man Fallback

The MAN fallback stops the control by changing the function block to manual (MAN) mode
regardless of the current operation status, and forces the function block to manual opera-
tion state.
Once the MAN fallback condition is established, the block mode remain manual (MAN)
even after the condition vanishes.
● MAN Fallback Condition

The MAN fallback condition is used to stop the control by changing the function block to
manual (MAN) mode regardless of the current operation status, and forces the function
block to enter manual operation state. When the MAN fallback condition is established, it
indicates that a fatal error has occurred and requests operator interruption.
An example of the MAN fallback condition is shown as follows:
AUTAMAN
IMAN (CAS)AIMAN (MAN)
The MAN fallback condition is established in the following situation:

• When the data status of the process variable (PV) is invalid (BAD) or calibration
(CAL). However, the MAN fallback condition will not be established when the block
mode is primary direct (PRD), or remote output (ROUT) excluding any compound
mode during computer backup.
• When the data status of the setpoint value (SV) is invalid (BAD).
• When the manipulated output value (MV) is connected to a process I/O and the FCS
is having an initial cold start.
• When the block mode change interlock condition is established.
• When the manipulated output value (MV) is connected to a process I/O, and one of
the I/O points connected to the module has been changed via maintenance.

■ AUT Fallback
▼ AUT Fallback
The AUT fallback is an error processing function that switches the block mode from cas-
cade (CAS) or primary direct (PRD) to automatic (AUT) when the AUT fallback condition is
established. Thus the set value of the control loop can be set by the operator.
● Characteristics of the AUT Fallback

Changes the block mode from cascade (CAS) or primary direct (PRD) to automatic (AUT)
to continue control using values set by the operator.
Once the AUT fallback condition is established, the block mode remain automatic (AUT)
even after the condition vanishes.
● AUT Fallback Condition

The AUT fallback condition is used to change the block mode of the function block from
cascade (CAS) or primary direct (PRD) to automatic (AUT) so that control can be continued
using the values set by the operator. When this condition is established, it indicates that
abnormality has been detected in the cascade setpoint value (CSV) for some reason.
An example of when the AUT fallback condition establishment is as follows:
CASAAUT
IMAN (CAS)AIMAN (AUT)
● Setting AUT Fallback Condition

Use the Function Block Detail Builder to enable/disable the AUT fallback function.
If the AUT fallback is defined as “Yes” via the Function Block Detail Builder, the AUT
fallback condition is established when the data status of the cascade setpoint value (CSV)
become invalid (BAD) or communication error (NCOM).

■ Computer Fail
▼ Computer Backup Mode
When the computer fail is detected, the function block suspends the action in the remote
cascade (RCAS) mode or remote output (ROUT) mode temporarily and switches to the
computer backup mode.
● Characteristics of Computer Fail

When the function block mode is remote cascade (RCAS) or remote output (ROUT), the
function block receives the setpoint value (SV) or manipulated output value (MV) from a
supervisory system computer via Control bus communication.
When the computer fails, the block changes mode to the preset computer backup mode
(MAN, AUT or CAS) which indicates that an abnormality has been detected in the supervi-
sory computer. When the computer recovers, the block returns to the mode before the
change.
The following actions will take place when a block mode change command from MAN,
AUT, CAS or PRD to RCAS or ROUT is sent while the computer fails:
1. When a block mode change command from MAN, AUT, CAS or PRD to RCAS or PRD
is sent while the computer fails (BSW=ON), the function block does not switch to the
computer backup mode directly but switches to the transient state mode first.
The transient state mode is a compound block mode consisting of the block mode
before the execution of the block mode change command (MAN, AUT, CAS, PRD)
and a remote mode (RCAS, ROUT).
2. Then the function block tests the computer condition in the first scan after the block
mode change command and switches to the computer backup mode.
The computer backup mode is a compound block mode consisting of the backup
mode set via the Function Block Detail Builder (MAN, AUT, CAS) and a remote mode
(RCAS, ROUT).
3. If the computer recovers while the function block is in the computer backup mode, the
block mode changes to remote cascade (RCAS) or remote output (ROUT).

● Computer Fail Condition
The computer fail condition is a block-mode transition condition used to suspend actions in
the remote cascade (RCAS) or remote output (ROUT) mode and switches the mode to the
A backup switch (BSW) is provided in function block to define the remote cascade (RCAS)
or remote output (ROUT) mode. The status of this switch determines whether the computer
has failed or recovered. The value of the backup switch (BSW) can be set from a sequence
table or other function blocks.
Switching to a computer backup mode does not take effect if the backup switch (BSW) is
on a block mode other than remote cascade (RCAS) or remote output (ROUT).
• When BSW=ON, computer has failed
• When BSW=OFF, computer has recovered
An example when the automatic (AUT) mode has been specified for the computer backup
mode is shown as follows:
RCAS
? Computer fails
AUT (RCAS)
? Computer recovers
RCAS
An example when the manual (MAN) mode has been specified for the computer backup
AUT
? ROUT command
AUT (ROUT) Transient state mode
MAN (ROUT) Computer backup mode (When BSW=ON)
● Define Computer Backup Mode

Use the Function Block Detail Builder to define the computer backup mode for each func-
tion block.
Select “MAN,” “AUT” or “CAS” as the mode to be switched to when the computer
becomes down. The default is “MAN.”
For a Control Signal Splitter Block (SPLIT), select “AUT” or “CAS.” The default is
“AUT.”

■ Block Mode Change Interlock
When the block mode change interlock condition is established, the block mode change
interlock function stops the control computation processing of the function block running in
auto mode, and prohibit the function block changing to automatic operation mode.
● Characteristics of the Block Mode Change Interlock

Stops the control computation processing of the function blocks that are operating auto-
matically, and disables the currently stopped function blocks from changing to an automatic
operation state. The following actions will take place:
• The block mode changes to manual (MAN).
• Any block mode change command to make the function block into automatic opera-
tion state (AUT, CAS, PRD, RCAS or ROUT mode) becomes invalid.
● Block Mode Change Interlock Condition

The Block mode change interlock condition is established when the switch at the con-
nected destination of the interlock switch input terminal (INT) is turned ON. This switch is
manipulated in the process control sequence and the switch is turned on when the se-
quence judge that the loop can not run in Auto mode, or etc.,.

■ Primary Direct (PRD) Mode Action
The primary direct (PRD) mode action enables the downstream block to output the setpoint
value received from the cascade connected upstream block (CSV) after converting it into
The conversion action from the cascade setpoint value (CSV) to the manipulated output
value (MV) varies with the control action direction, i.e., direct or reverse.
When an error such as process input signal error is detected in the cascade connected
downstream block, the block changes to primary direct (PRD) mode, to allow the upstream
block temporarily takes over control.
The output tracking function for the cascade connected upstream block is used so that an
abrupt change in the manipulated output does not occur when the block mode for the
cascade connected downstream block is changing to the primary direct (PRD) mode. The
cascade connected downstream block returns the manipulated output value (MV) to the
setpoint value (SV, CSV, RSV) in order to make the downstream block manipulated output
value (MV) track the upstream block manipulated output value (MV) when the block mode
for the downstream block changes to the primary direct (PRD) mode.
IMPORTANT
• Normally, when changing the block mode to primary direct (PRD), the set parameter
(P, I, D) of the upstream block in cascade need to be adjusted.
• Or to switch the cascade connected upstream block to manual (MAN) mode when the
downstream block changes to primary direct (PRD) mode.
SEE ALSO
For the details of data statuses, see a chapter C6, “Block Mode and Status.”

● When the Control is Direct Action
The computational expression of the primary direct (PRD) mode action when the control
action is direct:
MSH-MSL
MV=MSH- • (CSV-SL)
SH-SL D010423E.EPS
RMV=MV

SL: PV scale low limit
MSH: MV scale high limit
MSL: MV scale low limit
When the block mode changes to primary direct (PRD), the downstream block sets its the
manipulated output value (MV) to the setpoint value (SV, CSV, RSV), using the computa-
tional expression shown below:
SH-SL
SV=SH- • (MV-MSL)
MSH-MSL D010424E.EPS
CSV=RSV=SV
● When the Control is Reverse Action

The following computational expression is used as a basis of the primary direct (PRD)
mode action when the control action is reverse:
MSH-MSL
MV= • (CSV-SL)+MSL
SH-SL D010425E.EPS
RMV=MV
When the block mode changes to primary direct (PRD), the downstream block sets its the
manipulated output value (MV) to the setpoint value (SV, CSV, RSV), using the computa-
tional expression shown below:
SH-SL
SV=SH • (MV-MSL)+SL
CSV=RSV=SV

<Toc> <Ind> <D1.5 PID Controller Block (PID)> D1-59
D1.5 PID Controller Block (PID)

The PID Controller Block (PID) provides the most general control function to perform
proportional-integral-derivative control based on the deviation of the process vari-
able (PV) from the setpoint value (SV).
■ PID Controller Block (PID)

▼ Connection
The figure below shows a function block diagram of PID Controller Block (PID):
CAS (VN) (RLV1) (RLV2) (TSW)

CSV
AUT
SV
MAN
RSV
RCAS
MAN
Control CAS/AUT
Input Output
IN PV computation MV OUT
processing
ROUT
SUB
D010501E.EPS
Figure Function Block Diagram of PID Controller Block (PID)
terminals of PID Controller Block (PID):
Table Connection Methods and Connected destinations of the I/O Terminals of PID Controller
Block (PID)
SET Setting input
OUT Manipulated output
Reset signal 1
RL1
input
Reset signal 2
RL2
input
Compensation
BIN
input
Tracking signal
TIN
input
TSI Tracking SW input
INT Interlock SW input
D010502E.EPS

■ Function of PID Controller Block (PID) ¡ £
The PID block performs input processing, control computation processing, output process-
ing, and alarm processing.
The only processing timing available for the PID block is a periodic startup. Selections
period, the medium-speed scan period (*1), and the high-speed scan period.
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the PID block,
Control Block.”

● Control Computation Processing of the PID Controller Block (PID)
The table below shows the control computation processing functions of the PID Controller
Block (PID):
Table Control Computation Processing Functions of the PID Controller Block (PID) (1/2)
Calculates the manipulated output value (MV) and manipulated output change (MV)using
PID control
the PID control algorithms.
Performs the PID control actions by bypassing derivative control actions (D), proportional
Control action bypass
control actions (P) or both proportional and derivative control actions (P+D).
Non-linear gain relationship between the deviation and manipulated output change (MV) becomes non-
linear.
Gap action
reset windup.
Deadband action
Input compensation
Output compensation
D010503E.EPS

Table Control Computation Processing Functions of the PID Controller Block (PID) (2/2)
Control hold
MAN fallback
Computer failure
becomes satisfied.
PRD mode action
D010504E.EPS
SEE ALSO
For the details on control computation processing functions applied in the PID Controller Block see a
chapter D1.4, “Control Computation Processing Common to Controller Blocks.”

■ PID Control Computation
▼ PID Control Algorithm
The PID control computation is the core of the PID control computation processing, calcu-
lating a manipulated output change (MV) by using the PID control algorithms. The PID
control is the most widely used, it combines three types of actions: proportional, integral
and derivative.
The figure below shows a block diagram of PID control computation:
P0
I-PD Proportional term
computation (P)
PI-D/PID
SV
- +
PV + Integral term + Range
MV
(Note) computation (I) conversion
PID +
D0
Derivative term
I-PD/PI-D computation (D)
Note: Compensated PV, if input compensation is performed.

D010505E.EPS
Figure Block Diagram of PID Control Computation

● PID Control Computation Expression
The PID control computation expression used in a regulatory control system (analog
control system):
100 1 dE(t)
MV(t)= E(t)+ E(t)dt+TD
PB TI dt D010506E.EPS
MV(t): Manipulated output

E(t): Deviation E(t) = PV(t) - SV(t)
PV(t): Process variable
SV(t): Setpoint value
PB: Proportional band (%)
TI: Integral time
TD: Derivative time
If we use the sampling value derived at each interval of the control period for the above
expression, the differential expression of the PID control computation is transformed as
follows:
100 T TD
MVn= En+ En + (En)
PB TI T
D010507E.EPS
MVn: Manipulated output change

E n: Deviation En=PVn-SVn
SVn: Setpoint value’
En: Change in deviation En=En-En-1
T: Control period
The subscripts “n” and “n-1” represent the sample against the control period, it stands for
the nth sample or n-1th sample.
The above differential expression calculates a change in manipulated output (difference). A
new output value is obtained by adding the current change in manipulated output (MVn) to
the previous manipulated output value (MVn-1).
● Types of PID Control Computation

The PID Controller Block uses the following five PID control algorithms to perform PID
control computation. The actions vary with the characteristics of a controlled system and
the purpose of control.
• Basic type PID control (PID)
• PV proportional and derivative type PID control (I-PD)
• PV derivative type PID control (PI-D)
• Automatic determination type
• Automatic determination type 2

● Define PID Control Computation
For PID control computation, the input variables of the proportional, integral and derivative
terms are different for each PID control algorithm.
The table below shows the PID control algorithms and the input variable of each term:
Table PID Control Algorithms and the Input Variables
PID control Trinomial input variables

algorithm Proportional term Derivative term Integral term
PID En En En
I-PD PV PV En
PI-D En PV En
Automatic Same as I-PD in the AUT mode.

determination Same as PI-D in the CAS or RCAS mode.
Automatic Same as I-PD in the AUT or RCAS mode.
determination 2 Same as PI-D in the CAS mode.
D010508E.EPS
Use the Function Block Detail Builder to define the PID control algorithm.
• PID Control Algorithm:
Select one of the following algorithms:
“Basic Type”
“Proportional PV Derivative Type PID Control (I-PID)”
“PV Derivative Type PID Control (PI-D)”
“Automatic Determination”
“Automatic Determination 2”
The default is “Automatic Determination 2.”
When the block mode of the PID Controller Block is remote cascade (RCAS), the PID
control algorithm “Automatic Determination” and “Automatic Determination 2” act as fol-
lows:
• Automatic determination type: Same actions as in the cascade (CAS) mode.
• Automatic determination type 2: Same actions as in the automatic (AUT) mode.

● Basic Type PID Control Algorithm (PID)
The basic type PID control algorithm performs proportional, integral and derivative Control
Action following the changes in the setpoint value.
This algorithm is used when the process time constant is long and the control is oriented on
the prompt response to the change in the setpoint value. For example, when use a 13-
Zone Program Set Block (PG-L13) to change the setpoint value of a controller block, this
algorithm is used for the PID block.
The computational expression of the basic type PID control algorithm (PID):
T TD
MVn=Kp • Ks En+ En+ (En)
TI T D010509E.EPS
En=PVn-SVn
100
Kp=
PB D010510E.EPS
MSH-MSL
Ks=
SH-SL D010511E.EPS
T: Control period

En: Change in deviation En=En-En-1
K p: Proportional gain
TI: Integral time
TD: Derivative time
Ks: Scale conversion coefficient
PVn: Process variable (engineering unit)
SVn: Setpoint value (engineering unit)
The process variable (PV) and setpoint value (SV) used in the computation are both
engineering unit data. The manipulated output change (MV) obtained in an engineering
unit by the range conversion performed via the scale conversion coefficient (Ks).

● PV Proportional and Derivative Type PID Control Algorithm (I-PD)
The PV proportional and derivative type PID control algorithm (I-PI) differs from the basic
type that it performs only integral actions when the setpoint value changes.
This algorithm ensures stable control characteristics even when the setpoint value changes
abruptly when the SV is set via numerical value entry. At the same time, the algorithm
ensures proper control in response to the characteristic changes occurring in controlled
processes, load variations and disturbances by performing proportional, derivative and
integral Control Action accordingly.
The computational expression of the PV proportional and derivative type PID control
algorithm (I-PD):
T TD
MVn=Kp • Ks PVn+ En+ (PVn)
TI T D010512E.EPS
PVn : Process variable change PVn=PVn-PVn-1
● PV Derivative Type PID Control Algorithm (PI-D)

Compared to the basic type, the PV derivative type PID control algorithm (PI-D) only
performs proportional and integral Control Action when setpoint value changes, but not
derivative Control Action. This algorithm is used in the situations where the better follow up
to the setpoint value change is required, such a downstream control block in a cascade
control loop.
The computational expression of the PV derivative type PID control algorithm:
T TD
MVn=Kp • Ks En+ En+ (PVn)
TI T D010513E.EPS
● Automatic Determination Type

When a PID Controller Block is in cascade (CAS) or remote cascade (RCAS) mode, it uses
the PV derivative type PID control algorithm (PI-D) to perform computation so that the
follow-up the setpoint value change can be improved.
When the block is in automatic (AUT) mode, it uses the PV proportional and derivative type
PID control algorithm (I-PD) to perform computation so that stable control characteristics
can be ensured in the event that an abrupt change occurs in the setpoint value due to a
numeric value setting.
● Automatic Determination Type 2

When a PID Controller Block is in cascade (CAS) mode, it uses the PV derivative type PID
control algorithm (PI-D) to perform computation. When the block is in remote cascade
(RCAS) mode or automatic (AUT) mode, it uses the PV proportional and derivative type
PID control algorithm (I-PD) to perform computation.
In the cascade (CAS) mode, the automatic determination type 2 orients to the follow-up
capability to setpoint value (CSV) change. In the remote cascade (RCAS) mode, it orients
to prevent the abrupt change in the output due to an abrupt change in the remote setpoint
value (RSV).

● Set Parameters of the PID Control Algorithms
The set parameters of the PID control algorithms:
• Proportional band (P): 0 to 1000 %. (Note)
• Integral time (I): 0.1 to 10000 seconds.
• Derivative time (D): 0 to 10000 seconds (Note)
Note: The control action bypass function is enabled when “0” is set.
■ Control Action Bypass

The PID Controller Block can perform the following two types of control action by bypassing
proportional and/or derivative actions among the proportional, integral and derivative
actions:
Table Control Action Bypass
Control actions
Control actions bypassed after bypassing Set parameter setpoint
Derivative (D) Proportional (P)+integral (I) P&0, D=0

Proportional (P),
Integral (I) P=0
derivative (D)
D010514E.EPS
To set the control action bypass, specify “0” to the set parameter P or D, as shown in the
table above. The proportional gain (Kp) is fixed to “1” when only integral action is required.

■ Data Items - PID
Table Data Items of PID Controller Block (PID) (1/2)
Item or Not
MODE Block mode ----- O/S (MAN)
SV Setpoint value (*2) Value in the same engineering unit as PV SL
CSV Cascade setpoint value Value in the same engineering unit as PV SL
RSV Remote setpoint value Value in the same engineering unit as PV SL
DV Control deviation value Value in the same engineering unit as PV 0
VN I/O compensation value ----- 0
MV Manipulated output value (*3) MV engineering unit value MSL
RMV Remote manipulated output value Value in the same engineering unit as MV MSL
RLV1 Reset limit value 1 Value in the same engineering unit as MV MSL
D010515E.EPS

*2: Entry is permitted when the data mode is CAS or RCAS
*3: Entry is permitted when the block mode is MAN
SEE ALSO
For a list of valid block modes of the PID block, see chapter D1.1.4, “Valid Block Modes for Each Regula-
tory Control Block.”

Table Data Items of PID Controller Block (PID) (2/2)
Item or Not
MH Manipulated variable high-limit setpoint MSL to MSH MSH
ML Manipulated variable low-limit setpoint MSL to MSH MSL
P Proportional band 0 to 1000% 100%
I Integral time 0.1 to 10,000 seconds 20 seconds
D Derivative time 0 to 10,000 seconds 0 second
GW Gap width 0 to (SH - SL) 0.0
DB Deadband 0 to (SH - SL) 0.0
CK Compensation gain -10.000 to 10.000 1.000
CB Compensation bias ----- 0.000
PMV Preset manipulated output value MSL to MSH MSL
TSW Tracking switch 0, 1 0
CSW Control switch 0, 1 0
PSW Preset MV switch 0, 1, 2, 3 0
RSW Pulse width reset switch 0, 1 0
BSW Backup switch 0, 1 0
OPHI Output high-limit index MSL to MSH MSH
OPLO Output low-limit index MSL to MSH MSL
MSH MV scale high limit Value in the same engineering unit as MV -----
MSL MV scale low limit Value in the same engineering unit as MV -----
D010516E.EPS


<Toc> <Ind> <D1.6 Sampling PI Controller Block (PI-HLD)> D1-71
D1.6 Sampling PI Controller Block (PI-HLD)

Sampling PI Controller Block (PI-HLD) stops after performing each control action
and waits for the result to come out. This block may be used to control processes
with a long dead time or for the control that relies on the data from sampling unit of
analyzers.
■ Sampling PI Controller Block (PI-HLD)

▼ Connection
The figure below shows a function block diagram of Sampling PI Controller Block (PI-HLD):

CSV
AUT
SV
MAN
RSV
RCAS
MAN
Control CAS/AUT
Input Output
processing
ROUT
SUB
D010601E.EPS
Figure Function Block Diagram of Sampling PI Controller Block (PI-HLD)
terminals of the Sampling PI Controller Block (PI-HLD):
Table Connection Methods and Connected destinations of the I/O Terminals of Sampling PI
Controller Block (PI-HLD)
SET Setting input
Reset signal 1
RL1
input
Reset signal 2
RL2
input
Compensation
BIN
input
Tracking signal
TIN
input
D010602E.EPS

■ Function of Sampling PI Controller Block (PI-HLD) ¡ £
The PI-HLD block performs input processing, control computation processing, output
processing, and alarm processing.
The only processing timing available for the PI-HLD block is a periodic startup. Selections
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the PI-HLD block,
Control Block.”

● Control Computation Processing of Sampling PI Controller Block
(PI-HLD)
The table below shows the control computation processing functions of the Sampling PI
Controller Block (PI-HLD):
Table Control Computation Processing Functions of Sampling PI Controller Block (PI-HLD)
(1/2)
Performs PI control computation for each sampling period only during the specified
PI control computation with hold
control time, and holds the manipulated output value (MV) for the remainder of the period.
linear.
Gap action
reset windup.
Deadband action Adjusts the manipulated output change (MV) to “0” when the deviation is within the
Input compensation
Output compensation
Setpoint value limiter Limits the setpoint value (SV) within the setpoint high/low limits (SVH, SVL) .
D010603E.EPS

Table Control Computation Processing Functions of Sampling PI Controller Block (PI-HLD)
(2/2)
Control hold
MAN fallback
Computer failure
becomes satisfied.
PRD mode action
D010604E.EPS
SEE ALSO
For the details on control computation processing functions of Sampling PI Controller Block (PI-HLD), see
a chapter D1.4, “Control Computation Processing Common to Controller Blocks.”

■ PI Control Computation with Hold
The PI control computation with hold is a control algorithm of the Sampling PI Controller
Block. It is a control computation function that performs PI control computation to obtain a
manipulated output value (MV) and manipulated output change (MV).
● Characteristics of the PI Control Computation with Hold

The PI control computation with hold action performs PI control for each sampling period
(TC) only during the control time (TC) in an automatic operating mode (AUT, CAS or
RCAS), and holds manipulated output for the remainder of the period (TS - TC).
The figure below shows the sampling PI control action:
MV T (control period)
Output hold
PI computation
output
Time
TC TC
(control time)
TS (sampling period) TS
D010605E.EPS
Figure Sampling PI Control Action
Set the sampling period and control time in advance, in accordance with the following
principle:
Sampling period: TS=L+T • (2 to 3)

L: Dead time of the process (second)
T: Lag constant of the process (second)
TS
Control time: TC=
10 D010606E.EPS

The value of sampling period represents the time required for the process variable (PV) to
be stabilized after the manipulated output is actually output to the process and its effects
are transmitted throughout the process. When the shortest period of a major disturbance
affecting the process is Tn, if Tn is shorter than the sampling period, the control may be-
come impossible. Therefore, refer the following expression to adjust the sampling period
shorter than Tn:
Tn
TS
5 D010607E.EPS
The sampling period and control time are considered as set parameters, and their setting
can be changed during operation.
● Computational Expressions of the PI Control Algorithm with Hold

The computational expressions of the PI control algorithm:
T
MVn=Kp • Ks PVn+ • En
TI D010608E.EPS
En=PVn-SVn
100
Kp=
PB D010609E.EPS
MSH-MSL
Ks=
SH-SL D010610E.EPS
MVn: Manipulated output change

PVn: Process variable change PVn=PVn-PVn-1 (engineering unit)
E n: Deviation
T: Control period
PB: Proportional band (% unit)
TI: Integral time
The above PI control algorithm is the same as the PV proportional and derivative type PID
control algorithm (I-PD) of the PID Controller Block (PID) except that the former does not
have a derivative term.

● Set Parameters of the PI Control Algorithm with Hold
The following are set parameters for control computation processing of the PI control
algorithm with hold:
• Sampling period (TS): 0 to 10000 seconds.
The default is 1 second.
• Control time (TC): 0 to 10000 seconds.
• Proportional band (P):
0 to 1000%.
When P=0, the proportional action does not function but only the integral action is
performed.
The proportional gain Kp is “1” when only the integral action is performed.
• Integral time (I): 0 or 1 to 10000 seconds.

● Externally Started Sampling PI Control Action
When “0” is set for the sampling period (TS), the externally started sampling PI control
action will take place, as shown in the figure below.
The externally started sampling PI control action starts control when a switch signal is
received from outside the Sampling PI Controller Block.
The externally started sampling PI control action starts PI control when the control switch
(CSW) is turned ON from outside the block during automatic operation. Once started, PI
control will continue throughout the control time (TC). When the TC time has elapsed,
output is held and the control switch (CSW) is turned OFF until the next action is started.
CSW set set set

ON
OFF
T
(control period)
MV
Output hold
PI computation output
Time
TC TC TC
(control time) D010611E.EPS
Figure Externally Started Sampling PI Control Action
The control switch (CSW) is turned ON by other function block, such as a sequence control
block.
When the control switch (CSW) is turned OFF forcibly from outside the block during the
control time, output is held immediately.

■ Data Items - PI-HLD
Table Data Items of Sampling PI Controller Block (PI-HLD) (1/2)
Item or Not
D010612E.EPS

SEE ALSO
For a list of valid block modes of the PI-HLD block, see D1.1.4, “Valid Block Modes for Each Regulatory
Control Block.”

Table Data Items of Sampling PI Controller Block (PI-HLD) (2/2)
Item or Not
I Integral time 0, 1 to 10,000 seconds 20 seconds
TS Sampling period 0 to 10,000 seconds 1 second
TC Control time 1 to 10,000 seconds 1 second
CK Compesation gain -10.000 to 10.000 1.000
CB Compesation bias ----- 0.000
D010613E.EPS


<Toc> <Ind> <D1.7 PID Controller Block with Batch Switch (PID-BSW)> D1-81
D1.7 PID Controller Block with Batch Switch

(PID-BSW)
PID Controller Block with Batch Switch (PID-BSW) outputs a high limit or low limit
manipulated output signal unconditionally when control deviation becomes large.
This block may be applied to batch reactor temperature control process.
■ PID Controller Block with Batch Switch (PID-BSW)

▼ Connection
The PID Controller Block with Batch Switch (PID-BSW) prevent overshooting so that the
process variable (PV) may be brought closer to the target value sooner.
The figure below shows a function block diagram of the PID Controller Block with Batch
Switch (PID-BSW):
SET RL1 RL2 TIN TSI INT
CAS (RLV1) (RLV2) (TSW)

CSV
AUT
SV
MAN
RSV
RCAS
MAN
Control CAS/AUT
Input Output
processing
ROUT
SUB
D010701E.EPS
Figure Function Block Diagram of PID Controller Block with Batch Switch (PID-BSW)

terminals of the PID Controller Block with Batch Switch (PID-BSW):
Table Connection Methods and Connected destinations of the I/O Terminals of PID Controller
Block with Batch Switch (PID-BSW)
SET Setting input
Reset signal 1
RL1
input
Reset signal 2
RL2
input
Tracking signal
TIN
input
D010702E.EPS
■ Function of PID Controller Block with Batch Switch (PID-BSW) ¡ £

The PID-BSW block performs input processing, control computation processing, output
The only processing timing available for the PID-BSW block is a periodic startup. Selec-
tions available for the scan period used to execute a periodic startup include the basic scan
1: ¡ £ The medium-speed scan period can only be used for the KFCS2, KFCS, LFCS2 and LFCS.
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the PID-BSW
block, see D1.1.3, “Input Processing, Output Processing, and Alarm Processing Possible for Each Regu-
latory Control Block.”

● Control Computation Processing of PID Controller Block with Batch
Switch (PID-BSW)
The table below shows the control computation processing functions of PID Controller
Block with Batch Switch (PID-BSW).
Table Control Computation Processing Functions of PID Controller Block with Batch Switch
(PID-BSW)
Changes the manipulated output computational expression in accordance with the value of
PID with two-level output switching
control deviation. PID control computation is performed in a steady state.
reset windup.
Control hold
MAN fallback
Computer failure
becomes satisfied.
PRD mode action
D010703E.EPS
SEE ALSO
For the details on control computation processing functions applied in PID Controller Block with Batch
Switch (PID-BSW) see a chapter D1.4, “Control Computation Processing Common to Controller Blocks.”

■ PID Control Computation with Two-Level Output Switching
In PID control computation with two-level output switching, the computational expression
for a manipulated output value (MV) is switched in accordance with the state of control
deviation, as shown below:
• When the control deviation is negative and excessive.
• When the control deviation is positive, or negative and extremely small.
The figure below shows an example of control action performed by the PID Controller Block
with Batch Switch (PID-BSW) when the control action direction is reverse:
DL (deviation alarm setpoint)

LK (lockup setpoint)
SV
PV
BIAS (bias setpoint)

MH
MV
Time
(1) (2) (1) (2)
(1) When the control deviation is negative and excessive

(2) When the control deviation is positive, or negative and extremely small
D010704E.EPS
Figure Example of Control Action (Reverse Action) Performed by PID Controller Block with
Batch Switch (PID-BSW)
● Control Algorithms when the Deviation is Negative and Excessive

The following expressions represent the algorithms of calculating the manipulated output
value when the process variable (PV) is smaller than the setpoint value minus deviation
alarm setpoint (SV-| DL |) value:
• When the control action direction is “reverse”
Manipulated output value (MV)=Manipulated variable high-limit setpoint (MH)
• When the control action direction is “direct”
Manipulated output value (MV)=Manipulated variable low-limit setpoint (ML)
When the deviation immediately after the start of batch operation exceeds the deviation
alarm setpoint, the PID Controller Block with Batch Switch (PID-BSW) outputs a manipu-
lated output value (MV) that is the same as the manipulated variable high-limit setpoint
(MH) or manipulated variable low-limit setpoint (ML). As a result, the process variable
quickly approaches the setpoint value.

● Control Algorithms when the Control Deviation is Positive, or Negative but
Small
The following expressions represent the algorithms of calculating the control output value
when the process variable (PV) is larger than the setpoint value minus deviation alarm setpoint
(SV-| DL |) value:
• When the control action direction is “Reverse”
Manipulated output value (MV)=Manipulated variable high-limit setpoint (MH)Bias
setpoint (BIAS). PID control computation is performed by using the result obtained
from the above calculation as an initial value.
• When the control action direction is “Direct”
Manipulated output value (MV)=Manipulated variable low-limit setpoint (ML)Bias
setpoint (BIAS)
PID control computation is performed by using the result obtained from the above calcula-
tion as an initial value. When the deviation becomes smaller than the deviation limit range, the
PID Controller Block with Batch Switch (PID-BSW) assumes that the process is stabilized
and switches the control algorithm to PID control. At this time, output resumes to the ma-
nipulated variable high-limit setpoint (MH) or manipulated variable low-limit setpoint (ML)
by vanishing the bias setpoint (BIAS) value to prevent the manipulated output value (MV)
from overshooting.
Use the Function Block Detail Builder to define the PID control algorithm.
• PID Control Algorithm:
Select one of the following algorithms:
“Basic Type”
“Proportional PV Derivation Type PID Control (I-PID)”
“PV Derivative Type PID Control (PI-D)”
“Automatic Determination”
“Automatic Determination 2”
The default is “Automatic Determination 2.”
SEE ALSO
For the details of PID control algorithm, see a chapter D1.5, “PID Controller Block (PID).”
● Lockup Function
Once the PID control action resumes, even when the deviation exceeds the deviation
alarm setpoint (DL), the manipulated output value (MV) does not immediately ramp to the
manipulated variable high-limit setpoint (MH) or manipulated output low-limit setpoint (ML).
This is because of the lockup function.
When the following condition exists, the manipulated output value (MV) does not change to
the manipulated variable high-limit setpoint (MH) if the control action direction is Reverse,
nor to the manipulated variable low-limit setpoint (ML) if the control action direction is
Direct:
• Condition
PV<SV-| DL |-LK
LK: Lockup setpoint

● Set Parameters of the PID Control Computation with Two-Level Output
Switching
The set parameters of the PID control computation with two-level output switching:
0 to 1000 %.
When P = 0, the proportional action does not function but only the integral action is
performed.
• Derivative time (D): 0 to 10000 seconds.
When D=0, the derivative action does not function.
• Deviation alarm setpoint (DL):
The default is the scale span.
• Bias setpoint (BIAS): Engineering unit data within the MV scale span range.
The default is “0.”
• Lockup setpoint (LK): Engineering unit data within the PV scale span range.
• Manipulated variable high-limit setpoint (MH):
Engineering unit data within the MV scale range.
The default is the MV scale’s high limit.
• Manipulated variable low-limit setpoint (ML):
Engineering unit data within the MV scale range.
The default is the MV scale’s low limit.

■ Data Items - PID-BSW
Table Data Items of PID Controller Block with Batch Switch (PID-BSW) (1/2)
Item or Not
D010705E.EPS

SEE ALSO
For a list of valid block modes of the PI-BSW block, see D1.1.4, “Valid Block Modes for Each Regulatory
Control Block.”

Table Data Items of PID Controller Block with Batch Switch (PID-BSW) (2/2)
Item or Not
LK Lockup setpoint 0 to (SH - SL) 0.0
BIAS Bias setpoint value 0 to (MSH - MSL) 0.0
D010706E.EPS


<Toc> <Ind> <D1.8 Two-Position ON/OFF Controller Block (ONOFF)> D1-89
D1.8 Two-Position ON/OFF Controller Block (ONOFF)

The Two-Position ON/OFF Controller Block (ONOFF) performs control by ON/OFF
action via a single contact output.
■ Two-Position ON/OFF Controller Block (ONOFF)

▼ Connection
The controller turns On or Off the contact output according to the result in comparing the
process variable (PV) and setpoint value (SV).
The figure below shows a function block diagram of the Two-Position ON/OFF Controller
Block (ONOFF):
SET BIN INT
CAS (VN)
CSV
AUT
SV
MAN
RSV
RCAS
MAN
Control CAS/AUT
Input Output
processing
ROUT
(PV, PV) RMV
SUB
D010801E.EPS
Figure Function Block Diagram of Two-Position ON/OFF Controller Block (ONOFF)
terminals of the Two-Position ON/OFF Controller Block (ONOFF):
Table Connection Methods and Connected destinations of the I/O Terminals of Two-Position ON/
OFF Controller Block (ONOFF):
SET Setting input
Compensation
BIN
input
D010802E.EPS

■ Function of Two-Position ON/OFF Controller Block (ONOFF) ¡ £
The ONOFF block performs input processing, control computation processing, output
The only processing timing available for the ONOFF block is a periodic startup. Selections
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the ONOFF block,
Control Block.”

● Control Computation Processing of Two-Position ON/OFF Controller
Block (ONOFF)
The table below shows the control computation processing functions of Two-Position ON/
OFF Controller Block (ONOFF):
Table Control Computation Processing Functions of Two-Position ON/OFF Controller Block
(ONOFF)
Compares the deviation with ON/OFF hysteresis and obtains a manipulated output value
ON/OFF two-position control
(MV).
Control output action manipulated output value (MV). The available control output actions are of “positional
type” only.
Adds the I/O compensated value (VN) received from outside to the input signal or control
I/O compensation output signal of PID computation when the controller block is operating automatically.
Only “input compensation” can be used.
Input compensation
Control hold
MAN fallback
Computer failure
becomes satisfied.
D010803E.EPS
SEE ALSO
For the control computation processing functions applied in Two-Position ON/OFF Controller Block
(ONOFF) see a chapter D1.4, “Control Computation Processing Common to Controller Blocks.”
● Output Processing Specific to Two-Position ON/OFF Controller Block

(ONOFF)
The ONOFF block performs “two-position status output” as output signal conversion.

■ ON/OFF Two-Position Control Computation
▼ ON/OFF Hysteresis
The ON/OFF two-position control computation is a control algorithm of the Two-Position
ON/OFF Controller Block (ONOFF). This algorithm compares the deviation (En=PVn-SVn)
with positive or negative ON/OFF hysteresis and outputs the manipulated output value
(MV) by 0 % or 100 % based on the comparison result.
The action of the control algorithm varies with the control action directions.
● Control Algorithm in Direct Action

Performs computation that outputs the manipulated output value (MVn) by 100 % (ON)
when the deviation (En) exceeds the positive ON/OFF hysteresis value, and by 0 % (OFF)
when the deviation falls below the negative ON/OFF hysteresis value.
● Control Algorithm in Reverse Action

Performs computation that outputs the manipulated output value (MVn) by 0 % (OFF) when
the deviation (En) exceeds the positive ON/OFF hysteresis value, and by 100 % (ON) when
the deviation falls below the negative ON/OFF hysteresis value.
The figure below shows an example of the two-position ON/OFF control action:
Deviation (En)
ON/OFF hysteresis
0
Time
Direct action Contact output status OFF ON OFF
Manipulated output value 0% 100 % 0%
Reverse action Contact output status ON OFF ON
Manipulated output value 100 % 0% 100 %

D010804E.EPS
Figure Example of the Two-Position ON/OFF Control Action
Use the Function Block Detail Builder to define the ON/OFF hysteresis value.
• ON/OFF Hysteresis:
Engineering unit data within the PV scale span range.
The default is a value equivalent to 1.0 % of the PV scale span.

■ Two-Position Status Output
The ONOFF block performs two-position status output as output signal conversion.
For the 2-position status output, a contact output (1 point) or a internal switch (1 point)
designated to the OUT terminal is turned ON and OFF according to the manipulated output
value (MV).
The following table shows the relationship between the manipulated output value (MV) and
contact output status. Note that the manipulated output value (MV) is always expressed in
percentage (%).
Table Relationship between Manipulated Output Value (MV) and Contact Output
Manipulated output value 0% 0.1 to 49.9 % 50 to 99.9 % 100 %
Contact output status OFF OFF ON ON
D010807E.EPS
■ Data Items - ONOFF

Table Data Items of Two-Position ON/OFF Controller Block (ONOFF) (1/2)
Item or Not
MODE Block mode 3 ----- O/S (MAN)
SUM Totalizer value 3 Engineering unit value 0
SV Set value (*2) Value in the same engineering unit as PV SL
CSV Cascade setpoint value 3 Value in the same engineering unit as PV SL
RSV Remote setpoint value 3 Value in the same engineering unit as PV SL
VN Input compensation value 3 ----- 0

MV Manipulated output value (*3) 0 to 100% 0%
RMV Remote manipulated output value 3 0 to 100% 0%
D010805E.EPS

SEE ALSO
For a list of valid block modes of the ONOFF block, see a chapter D1.1.4, “Valid Block Modes for Each
Regulatory Control Block.”

Table Data Items of Two-Position ON/OFF Controller Block (ONOFF) (2/2)
Item or Not
PMV Preset manipulated output value 0 to 100% 0%
D010806E.EPS


<Toc> <Ind> <D1.9 Three-Position ON/OFF Controller Block (ONOFF-G)> D1-95
D1.9 Three-Position ON/OFF Controller Block

(ONOFF-G)
The Three-Position ON/OFF Controller Block (ONOFF-G) performs control by ON
and OFF actions via two contact outputs.
■ Three-Position ON/OFF Controller Block (ONOFF-G)

▼ Connection
The ONOFF-G Block changes the ON/OFF status of two contact outputs depending on
whether a process variable (PV) is in the Low/Middle/High position compared to a setpoint
value (SV). The figure below shows the ONOFF-G Block diagram.
SET BIN INT
CAS (VN)
CSV
AUT
SV
MAN
RSV
RCAS
MAN
Control CAS/AUT
Input Output
processing
ROUT
(PV, PV) RMV
SUB
D010901E.EPS
Figure Function Block Diagram of Three-Position ON/OFF Controller Block (ONOFF-G)
terminals of the Three-Position ON/OFF Controller Block (ONOFF-G):
Table Connection Methods and Connected destinations of the I/O Terminals of Three-Position
ON/OFF Controller Block (ONOFF-G):
SET Setting input
Compensation
BIN
input
D010902E.EPS

■ Function of Three-Position ON/OFF Controller Block (ONOFF-G)
¡£
The ONOFF-G block performs input processing, control computation processing, output
The only processing timing available for the ONOFF-G block is a periodic startup. Selec-
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the ONOFF-G
• For details on the input processing, see C3,“Input Processing.”
• For details on the output processing, see C4,“Output Processing.”
• For details on the alarm processing, see C5,“Alarm Processing-FCS.”

● Control Computation Processing of 3-Position ON/OFF Controller Block
(ONOFF-G)
The table below shows the control computation processing functions of the 3-Position
ON/OFF Controller Block (ONOFF-G):
Table Control Computation Processing Functions of 3-Position ON/OFF Controller Block
(ONOFF-G)
Compares the deviation with ON/OFF hysteresis and obtains a manipulated output value
ON/OFF three-position control
(MV).
type” only.
Input compensation
Control hold
MAN fallback
Computer failure
becomes satisfied.
D010903E.EPS
SEE ALSO
For the control computation processing functions applied in 3-Position ON/OFF Controller Block
(ONOFF) see a chapter D1.4, “Control Computation Processing Common to Controller Blocks.”
● Output Processing Specific to Three-Position ON/OFF Controller Block

(ONOFF-G)
The ONOFF-G block performs “three-position status output” as output signal conversion.

■ ON/OFF Three-Position Control Computation
▼ ON/OFF Hysteresis
The ON/OFF three-position control computation is a control algorithm of the 3-Position ON/
OFF Controller Block (ONOFF-G). This algorithm compares the deviation (En=PVn-SVn)
with neutral status range (DB) that includes an ON/OFF hysteresis and outputs the ma-
nipulated output value (MV) by 0 %, 50 % or 100 % based on the comparison result.
The action of the control algorithm varies with the control action directions.
Use the Function Block Detail Builder to define the ON/OFF hysteresis.
• ON/OFF Hysteresis:
Engineering unit data within the PV scale span range.
The default is the value equivalent to 2.0 % of the PV scale span.
● Control Algorithm in Direct Action

The figure below shows the ON/OFF hysteresis when the control action direction is direct:
Neutral status range (DB) ON/OFF hysteresis (HYS)
(3)
+ (4)
(2) (5)
0
Time
Deviation (En)
- (1)
(6)
Direct action Contact 1 output status OFF ON OFF
Contact 2 output status ON OFF ON
Manipulated output value 0% 50 % 100 % 50 % 0%
Manipulated output value (MV) when the deviation (En) is increasing

(1) MV=0 %: En<-(| DB |-HYS)
(2) MV=50 %: -(| DB |-HYS))En<| DB |
(3) MV=100 %: | DB |)En
Manipulated output value (MV) when the deviation (En) is decreasing

(1) MV=100 %: | DB |-HYS<En
(2) MV=50 %: -| DB |<En)| DB |-HYS
(3) MV=0 %: En)-| DB |
D010904E.EPS
Figure ON/OFF Hysteresis in Direct Action

● Control Algorithm in Reverse Action
The figure below shows the ON/OFF hysteresis when the control action direction is re-
verse:
Neutral status range (DB) ON/OFF hysteresis (HYS)
(3)
+ (4)
(2) (5)
0
Time
Deviation (En)
- (1)
(6)
Reverse action Contact 1 output status ON OFF ON
Contact 2 output status OFF ON OFF
Manipulated output value 100 % 50 % 0% 50 % 100 %
Manipulated output value (MV) when the deviation (En) is increasing

(1) MV=100 %: En<-(| DB |-HYS)
(2) MV=50 %: -(| DB |-HYS))En<| DB |
(3) MV=0 %: | DB |)En
Manipulated output value (MV) when the deviation (En) is decreasing

(1) MV=0 %: | DB |-HYS<En
(2) MV=50 %: -| DB |<En)| DB |-HYS
(3) MV=100 %: En)-| DB |
D010905E.EPS
Figure ON/OFF Hysteresis in Reverse Action
● Set Parameter of ON/OFF Three-Position Control Computation

The parameter of the Three-Position ON/OFF Controller Block:
• Neutral status range (DB): Engineering unit data within the PV scale range.
The default is 0.

■ Three-Position Status Output
The ONOFF-G block performs three-position status output as output signal conversion.
In the 3-position status output, the contact output (2 points) or the internal switch (2 points)
are turned ON or OFF according to the manipulated output value (MV).
The following table shows the contact output status in relationship to the manipulated
output value (MV) at 0 %, 50 %, 100 % and other instances. Note that the manipulated
output value (MV) is always expressed in percentage (%).
Table Relationship of the Manipulated Output Value (MV) and Contact Output Status (At 0 %, 50 %
and 100 %)
Manipulated output value 0% 50 % 100 %
Contact 1 output status OFF OFF ON
Contact 2 output status ON OFF OFF
D010908E.EPS
Table Relationship of the Manipulated Output Value (MV) and Contact Output Status (Not at the 0 %,
50 % and 100 %)
Manipulated output value 0 to 24.9 % 25 to 74.9 % 75 to 100 %
Contact 1 output status OFF OFF ON
Contact 2 output status ON OFF OFF
D010909E.EPS
When connect process I/O contacts to the three-position output, only one contact number
need to be defined to the OUT terminal of the ONOFF-G block. This number will become
the first contact output of the ONOFF-G block. Its succeeding number contact will be
automatically assigned to be the second contact output of the ONOFF-G block. When
define the first contact point, make sure the succeeding contact should not be assigned for
other contact output module.

■ Data Items - ONOFF-G
Table Data Items of Three-Position ON/OFF Controller Block (ONOFF-G) (1/2)
Item or Not
VN Input compensation value ----- 0
MV Manipulated output value (*3) 0 to 100% 0%
RMV Remote manipulated output value 0 to 100% 0%
D010906E.EPS

SEE ALSO
For a list of valid block modes of the ONOFF-G block, see a chapter D1.1.4, “Valid Block Modes for Each

Table Data Items of Three-Position ON/OFF Controller Block (ONOFF-G) (2/2)
Item or Not
SVH Setpoint high-limit SL to SH SH
SVL Setpoint low-limit SL to SH SL
DB Neutral status range 0 to (SH - SL) 0.0
D010907E.EPS


<Toc> <Ind> <D1.10 Time-Proportioning ON/OFF Controller Block (PID-TP)> D1-103
D1.10 Time-Proportioning ON/OFF Controller Block

(PID-TP)
The Time-Proportioning ON/OFF Controller Block (PID-TP) changes ON time of
contact output proportional to the result of the PID control computation. This block
is used for temperature control of an electric furnace.
■ Time-Proportioning ON/OFF Controller Block (PID-TP)

▼ Connection
Time-Proportioning ON/OFF Controller Block (PID-TP) changes ON/OFF time ratio in
proportion to the manipulated output value (MV) obtained by PID control computation to the
overall ON/OFF period. Only the basic scan-cycle can be applied to PID-TP.
The figure below shows the function block diagram of Time-Proportioning ON/OFF Control-
ler Block (PID-TP):
SET BIN RL1 RL2 INT
CAS (VN) (RLV1) (RLV2)

CSV
AUT
SV
MAN
RSV
RCAS
MAN
Control CAS/AUT
Input Output
processing
ROUT
SUB
D011001E.EPS
Figure Function Block Diagram of Time-Proportioning ON/OFF Controller Block (PID-TP)

terminals of the Time-Proportioning ON/OFF Controller Block (PID-TP):
Table Connection Methods and Connected destinations of the I/O Terminals of Time-
Proportioning ON/OFF Controller Block (PID-TP):
SET Setting input
Reset signal 1
RL1
input
Reset signal 2
RL2
input
Compensation
BIN
input
D011002E.EPS

■ Function of Time-Proportioning ON/OFF Controller Block (PID-TP)
The PID-TP block performs input processing, control computation processing, output
The only processing timing available for the PID-TP block is a periodic startup. Moreover,
only the basic scan period can be selected as the scan period to execute the periodic
startup.
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the PID-TP block,
see a chapter D1.1.3, “Input Processing, Output Processing, and Alarm Processing Possible for Each
• For details on the input processing, see a chapter C3, “Input Processing.”
• For details on the output processing, see a chapter C4, “Output Processing.”
• For details on the alarm processing, see a chapter C5, “Alarm Processing-FCS.”
● Control Computation Processing of Time-Proportioning ON/OFF

Controller Block (PID-TP)
The table below shows the control computation processing functions of the Time-Propor-
tioning ON/OFF Controller Block (PID-TP):
Table Control Computation Processing Functions of Time-Proportioning ON/OFF Controller
Block (PID-TP) (1/2)
PV proportional and derivative PID Performs integral actions in accordance with changes in the setpoint value (SV). This
control ensures stable control characteristics even when the setpoint value changes abruptly.
linear.
Gap action
reset windup.
Deadband action
Input compensation
Output compensation
D011003E.EPS

Table Control Computation Processing Functions of Time-Proportioning ON/OFF Controller
Block (PID-TP) (2/2)
takes place when the initialization manual condition is established.
Control hold
MAN fallback
place when the MAN fallback condition is established.
takes place when the AUT fallback condition is established.
an error is detected by supervisory computer while the function block is operating in the
Computer failure
RCAS or ROUT mode. This action takes place when the computer failure condition is
established.
Stops the automatic control action of function blocks. And prevents the function blocks
Interlock on block mode change
currently operating in manual mode from changing to automatic mode.
D011004E.EPS
SEE ALSO
For the details on control computation processing functions applied in the Time-Proportioning ON/OFF
Controller Block (PID-TP), see a chapter D1.4, “Control Computation Processing Common to Controller
Blocks.”
● Output Processing Specific to Time-Proportioning ON/OFF Controller

Block (PID-TP)
The PID-TP block performs “time-proportioning ON/OFF output” as output signal conver-
sion.

■ PV Proportional and Derivative Type PID Control (I-PD)
The PV proportional and derivative type PID control algorithm (I-PI) is a control algorithm of
the Time-Proportioning ON/OFF Controller Block (PID-TP).
This algorithm performs only integral actions when the setpoint value changes, and en-
sures stable control characteristics even when the setpoint value changes abruptly by a
numerical value entry.
At the same time, the algorithm ensures proper control in response to the characteristic
changes occurring in the controlled process, load variations and disturbances by perform-
ing proportional, derivative and integral Control Action accordingly.
● Computational Expression of the PV Proportional and Derivative Type of

PID Control
The computational expression of the PV proportional and derivative type of PID control:
T TD
MVn=Kp • Ks PVn+ En+ (PVn)
TI T
D011005E.EPS
PVn: Process variable change PVn=PVn-PVn-1
● Set Parameters of the PV Proportional and Derivative Type of PID Control

The parameters the PV proportional and derivative type of PID control (I-PID):
• Proportional band (P): 0 to 1000 %
When P=0, only the integral action is performed.
When P=0, the proportional gain Kp=1.
• Integral time (I): 0.1 to 10000 seconds
• Derivative time (D): 0 to 10000 seconds
No derivative action is performed when D=0.

■ Time-Proportioning ON/OFF Output ¡ £
▼ Time-Proportioning ON/OFF Period
The PID-TP block performs time-proportioning ON/OFF output as output signal conversion.
In the time-proportioning ON/OFF output, a contact output (1 point) defined to the OUT
terminal is turned ON for the period of time proportioning to the manipulated output value
(MV) within the ON/OFF period.
Proportional to manipulated output value (MV)
ON
OFF
Time
ON/OFF period (constant)
Output value (MV value) (%)

On time (sec.) = ON/OFF period (sec.) •
100 (%)
D011008E.EPS
Figure Operation of Time-Proportioning ON/OFF Output
The time-proportioning ON/OFF output is always off against 0 % and on against 100 % of
the manipulated output value (MV) respectively. For instance, if the ON/OFF period is 10
seconds and manipulated output value (MV) is 80 %, the ON time will be 8 seconds.
The time-proportioning ON/OFF period is set through the Function Block Detail Builder.
• Time-proportioning ON/OFF Period: 1.00 to 256.00 seconds
Default is 1.00 second.
If there are multiple PID-TP blocks, their simultaneous turning on at the beginning of the
ON/OFF period will cause a large fluctuation in the load of power supply for the final control
element (such as heaters). To reduce such load fluctuation, the phases of PID-TP blocks’
ON/OFF outputs are automatically shifted.
• Phasing the ON/OFF period of the function blocks
The phasing is performed according to the internal block numbers so as to prevent the
multiple blocks ON/OFF in the same phase (*1).
• Phasing the ON/OFF period of the I/O modules. For the “time-proportioning ON/OFF
pulse period” in the Details Setting dialogue box of IOM Builder, set the same value as
the “time-proportioning ON/OFF period” specified with Function Block Detail Builder.
In addition, specify “Operation start offset” in the Details Setting dialogue box of IOM
Builder so as to prevent a heavy load caused by multiple outputs ON/OFF in the same
period (*2).
*1: ¡ The function is supported in PFCS

£ The function is supported in SFCS
*2: ¡ The function is supported only in CS 3000 system.
£ The function is supported in KFCS2, KFCS, LFCS2 or LFCS

■ Data Items - PID-TP
Table Data Items of Time-Proportioning ON/OFF Controller Block (PID-TP) (1/2)
Item or Not
MV Manipulated output value (*3) 0 to 100 % 0%
RMV Remote manipulated output value 0 to 100 % 0%
RLV1 Reset limit value1 0 to 100 % 0%
RLV2 Reset limit value 2 0 to 100 % 0%
D011006E.EPS

SEE ALSO
For a list of valid block modes of the PID-TP block, see chapter D1.1.4, “Valid Block Modes for Each

Table Data Items of Time-Proportioning ON/OFF Controller Block (PID-TP) (2/2)
Item or Not
MH Manipulated variable high-limit setpoint 0 to 100% 100 %
ML Manipulated variable low-limit setpoint 0 to 100% 0%
OPHI Output high-limit index 0 to 100% 100 %
OPLO Output low-limit index 0 to 100% 0%
D011007E.EPS


<Toc> <Ind> <D1.11 PD Controller Block with Manual Reset (PD-MR)> D1-111
D1.11 PD Controller Block with Manual Reset

(PD-MR)
PD Controller Block with Manual Reset (PD-MR) performs proportional-derivative
(PD) control function. This block may be applied to programmed temperature con-
trol process.
■ PD Controller Block with Manual Reset (PD-MR)

▼ Connection
The PD Controller Block with Manual Reset (PD-MR) performs proportional (P) and deriva-
tive (D) control, while the integral (I) may be manually set to be applied to the control
function.
In programmed temperature control process, operating conditions do not remain the same
throughout the process time. For example, a chemical process is accompanied by momen-
tary generations of intense heat. In this case, among all PID actions of the controller block
the integral (I) actions may be weakened for a specific period of time during operation so
that control is performed only by proportional and derivative (PD) actions. In this type of
process, it is necessary to set a wide proportional band, as a long dead time or large
process time constant tends to cause hunting if an integral (I) action is performed.
By performing only proportional-derivative (PD) actions, the proportional band (P) can be
narrowed. In addition, overshooting can be inhibited by shift the control phase by derivative
(D) actions to achieve the better control result.
The figure below shows the function block diagram of PD Controller Block with Manual
Reset (PD-MR):
SET BIN TIN TSI INT
CAS (VN) (TSW)

CSV
AUT
SV
MAN
RSV
RCAS
MAN
Control CAS/AUT
Input Output
processing
ROUT
SUB
D011101E.EPS
Figure Function Block Diagram of PD Controller Block with Manual Reset (PD-MR)

terminals of the PD Controller Block with Manual Reset (PD-MR):
Table Connection Methods and Connected destinations of the I/O Terminals of PD Controller
Block with Manual Reset (PD-MR)
SET Setting input
Compensation
BIN
input
Tracking signal
TIN
input
D011102E.EPS
■ Function of PD Controller Block with Manual Reset (PD-MR) ¡ £
The PD-MR block performs input processing, control computation processing, output
The only processing timing available for the PD-MR block is a periodic startup. Selections
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the PD-MR block,
Control Block.”

● Control Computation Processing of PD Controller Block with Manual
Reset (PD-MR)
The table below shows the control computation processing functions of the PD Controller
Block with Manual Reset (PD-MR):
Table Control Computation Processing Functions of PD Controller Block with Manual Reset
(PD-MR)
PD control with manual reset Performs PD actions. The reset value (MR) is set manually.
type” only.
Input compensation
Prevents abrupt changes in the manipulated output value (MV) by initializing the balance
Balance action
term in the manipulated output computational expression.
Control hold
MAN fallback
Computer failure
becomes satisfied.
PRD mode action
D011103E.EPS
SEE ALSO
For the control computation processing available with the PD Controller Block with Manual Reset (PD-
MR) see D1.4, “Control Computation Processing Common to Controller Blocks.”

■ PD Control with Manual Reset
The PD control with manual reset performs proportional and derivative (PD) actions. The
reset value (MR) must be set manually.
● Computational Expression of the PD Control with Manual Reset

The computational expression of the PD control with manual reset:
TD
CALCn=Kp • Ks • En+ PVn +MR+BLn
T D011104E.EPS
En=PVn-SVn
100
Kp=
PB D011105E.EPS
MSH-MSL
Ks=
SH-SL D011106E.EPS
T
BLn= 1- • BLn-1
Tbl D011107E.EPS
CALCn: Calculated output value

E n: Deviation
PVn: Process variable change PVn=PVn-PVn-1
MR: Manual reset value
BLn: Balance term. A correction variable used for bumpless switching from MAN to AUT.
TD: Derivative time
T: Control period
Tbl: Balance rate time
In an automatic mode (AUT, CAS or RCAS), the calculated output value (CALCn) is con-
verted into a manipulated output value (MV) through output processing.

● Set Parameters of the PD Control with Manual Reset
The parameters of the PD control with manual reset:
• Proportional band (P): 1 to 1000 %
• Integral time (D): 0 to 1000 seconds
When D=0, the proportional action does not function.
• Manual reset value (MR): Engineering unit data within the MV scale range
• Balance rate time (I): 0.1 to 10000 seconds
The balance rate time (Tbl) is set to the parameter I on
operation and monitoring functions.

The bumpless switching function switches the function block mode or switches the cascade
connected downstream block’s manipulated output value (MV) without causing its own
manipulated output value (MV) to change abruptly (i.e., bumpless switch).
The PD Controller Block with Manual Reset performs bumpless switching based on “bal-
ance action.”
The PD Controller Block with Manual Reset performs bumpless switching of the block
mode from manual (MAN) to automatic (AUT), by using a value obtained by the following
expression as the initial value of the balance term (BLn0):
TD
BLn0=MV-Kp • Ks • En+ PVn -MR
T D011108E.EPS
MV: Output in the manual mode
The figure below shows the balance action of the PD Controller Block with Manual Reset:
MV
BLn0
MR
Time
MAN AUT
D011109E.EPS
Figure Bumpless Switching by PD Controller Block with Manual Reset (Balance Action)
When the block mode is not remote output (ROUT) or out of service (O/S), the remote
manipulated output value (RMV) tracks the manipulated output value (MV).

■ Data Items - PD-MR
Table Data Items of PD Controller Block with Manual Reset (PD-MR) (1/2)
Item or Not
CALC Calculated output value Value in the same engineering unit as MV MSL
D011110E.EPS

SEE ALSO
For a list of valid block modes of the PD-MR block, see chapter D1.1.4, “Valid Block Modes for Each

Table Data Items of PD Controller Block with Manual Reset (PD-MR) (2/2)
Item or Not
I Balancing rate time 0.1 to 10,000 seconds 10 seconds
MR Manual reset value MSL to MSH MSL
D011111E.EPS


<Toc> <Ind> <D1.12 Blending PI Controller Block (PI-BLEND)> D1-119
D1.12 Blending PI Controller Block (PI-BLEND)

Blending PI Controller Block (PI-BLEND) may be applied to the multiple elements
flow control (blending control) to maintain the totalized flow value of each blending
component at a constant ratio (blending ratio).
■ Blending PI Controller Block (PI-BLEND)

▼ Connection
The figure below shows a function block diagram of Blending PI Controller Block (PI-
BLEND):
SET TIN TSI INT
CAS (TSW)
CSV
AUT
SV
MAN
RSV
RCAS
MAN
Control CAS/AUT
Input Output
processing
ROUT
SUB
D011201E.EPS
Figure Function Block Diagram of Blending PI controller Block (PI-BLEND)
terminals of Blending PI Controller Block (PI-BLEND):
Table Connection Methods and Connected Destinations of the I/O Terminals of Blending PI
Controller Block (PI-BLEND)
reference reference connection I/O I/O block
SET Setting input
Tracking signal
TIN
input
D011202E.EPS

■ Function of Blending PI Controller Block (PI-BLEND) ¡ £
The PI-BLEND block performs input processing, control computation processing, output
The only processing timing available for the PI-BLEND block is a periodic startup. Selec-
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the PI-BLEND

● Control Computation Processing of Blending PI Controller Block
(PI-BLEND)
The table below shows the control computation processing functions of Blending PI Con-
troller Block (PI-BLEND):
Table Control Computation Processing Functions of Blending PI controller Block (PI-BLEND)
PI control based on cumulative Performs proportional (P) control and integral (I) actions based on cumulative deviation,
deviation and obtains a manipulated output value (MV) and manipulated output change (MV).
Balance action
Control hold
MAN fallback
Computer failure
becomes satisfied.
D011203E.EPS
SEE ALSO
For the control computation processing functions applied in Blending PI Controller Block (PI-BLEND) see
D1.4, “Control Computation Processing Common to Controller Blocks.”
● Alarm Processing Specific to Blending PI Controller Block (PI-BLEND)

The “cumulative deviation alarm check” and “control error alarm check,” which are two of
the alarm checks performed by the PI-BLEND block, are specific to this function block.

■ PI Control Based on Cumulative Deviation
The Blending PI Controller Block (PI-BLEND) performs proportional and integral actions
based on cumulative deviation. The cumulative deviation value (DVn) is obtained by totaliz-
ing deviations of the process variable (PVn) from setpoint value (SVn) for each scan period
and performing time scale-conversion on the totalized deviation.
● Computational Expression of the PI Control Algorithm Based on

Cumulative Deviation
DVRn=DVRn-1+(PVn-SVn)
DVRn
DVn= • TS
TK D011204E.EPS
DVRn: Raw cumulative deviation value

DVRn-1: Previous raw cumulative deviation value
DVn: Cumulative deviation value
TS: Scan period
TK: Time scale conversion coefficient
The time scale conversion is to convert the raw cumulative deviation value that represents
a totalized deviation value, from a value of flowrate unit (e.g., m3/h) to that in a weight or
volume unit (e.g., m3). The time scale conversion coefficient (TK) used in the above compu-
tational expression is a value in seconds representing the unit time of the flowrate unit. For
example, if the unit of the process variable (PV) is m3/h, set “3600” as a time scale conver-
sion coefficient (TK).

The computational expression of the control algorithm used by the Blending PI Controller
Block.
K p • Ks T
MVn = T • En + ESn +BLn
8 TI D011205E.EPS
En= PVn-SVn
100
Kp=
PB D011206E.EPS
MSH-MSL
Ks=
SH-SL D011207E.EPS
Kp: Proportional gain

ESn: Control cumulative deviation (A DV value limited by DL)
BLn: Balance term. A correction variable used for bumpless switching from MAN to AUT.
T: Control period
TI: Integral time

● Control Cumulative Deviation Value (ESn) Used in the PI Control Algorithm
Based on Cumulative Deviation
The control cumulative deviation value (ESn) used for PI control computation is equivalent
to the cumulative deviation value (DVn) limited by the deviation alarm setpoint (DL).
• When DVn| DL |
ESn=+| DL | • TK
• When-| DL |<DVn<| DL |
ESn=DVRn • TS
• When DVn-| DL |
ESn=-| DL | • TK
The cumulative deviation value (DVn) is reset to “0” in the following cases:
• When the cumulative deviation reset switch (RST) is set to “1.”
• When “Yes” is specified for process variable tracking and the block mode changes
from manual (MAN) to automatic (AUT).
When the cumulative deviation reset switch (RST) is set to “1,” it returns to “0” automati-
cally when resetting is complete.
● Set Parameters of the PI Control Algorithm Based on Cumulative Deviation

The parameters of the PI control algorithm based on cumulative deviation:
• Time scale conversion coefficient (TK): 1 to 100,000
1 to 1000 %
When P = 0, only the integral action is performed.
• Ramp constant (RP):
Set engineering unit data within the scale span range of the manipulated output value
(MV).
The default is the MV scale span.

The bumpless switching function switches the function block mode or switches the down-
stream block’s manipulated output value (MV) without causing its own manipulated output
value (MV) to change abruptly (i.e., bumpless change).
The Blending PI Controller Block performs bumpless switching based on “balance action.”
The Blending PI Controller Block performs bumpless switching of the block mode from
manual (MAN) to automatic (AUT), by using a value obtained by the following expression
as the initial value of the balance term (BLn0):
Kp • Ks T
BLn0=- T • En + ESn
8 TI D011208E.EPS
MV: Output in the manual mode
When the mode switches to automatic (AUT), the balance term (BLn) approaches “0” with
each control period for the increment of ramp constant, until it finally reaches “0.”
The figure below shows the balance action of Blending PI Controller Block:
BLn Control period

BLn0
Ramp constant (RP)
Time
0
MAN AUT
D011209E.EPS
Figure Bumpless Switching by Blending PI Controller Block (PI-BLEND) (Balance Action)

■ Cumulative Deviation Alarm Check
▼ Accumulated Deviation Alarm
The cumulative deviation alarm check is a function that determines whether the absolute
value of the cumulative deviation (DV) exceeds the absolute value of the cumulative
deviation alarm setpoint value (DL).
When it is determined that the absolute value of the cumulative deviation (DV) exceeds the
absolute value of the cumulative deviation alarm setpoint value (DL) in the positive direc-
tion, a positive direction cumulative deviation alarm (DV+) is activated. Similarly, when it
exceeds the setpoint in the negative direction, a negative direction cumulative deviation
alarm (DV-) is activated.
When an alarm has occurred, if the cumulative deviation (DV) absolute value drops lower
than the cumulative deviation alarm setpoint (DL) absolute value minus the alarm hyster-
esis value (HYS), the alarm is returned to normal state.
DV
| DL |
HYS
Conditions causing an alarm
DV | DL |
Time DV
| DL |
Conditions causing recovery from an alarm
0
DV | DL | HYS
DV | DL | HYS
HYS
| DL |
DV
D011212E.EPS
Figure Actions of Cumulative Deviation Alarm Check

The cumulative deviation alarm check type, cumulative deviation alarm setpoint (DL),
cumulative deviation range (DV) and the alarm hysteresis value can be set.
● Cumulative Deviation Alarm Check Types

The cumulative deviation alarm check type is set with the Function Block Detail Builder.
The default is “detection of both directions.”
Monitors the deviation of both the positive and negative directions.
Monitors the deviation of either the positive or negative direction only.
• No alarm:
Detection is not performed.
When single direction is selected for the cumulative deviation alarm check type, only the
deviation in the positive direction is monitored when the cumulative deviation alarm
setpoint (DL) has a plus sign, and only the deviation in the negative direction is monitored
when the cumulative deviation alarm setpoint has a minus sign.
● Cumulative Deviation Alarm Setpoint (DL)

The cumulative deviation alarm setpoint is set by the operation and monitoring function.
• Cumulative deviation alarm setpoint:
Engineering unit data within the DV scale span range
Default is DV scale span
● Cumulative Deviation Range

▼ DV Range
The cumulative deviation range can be set with the Function Block Detail Builder.
• Cumulative deviation range:
Set engineering unit data (absolute value)
5 significant figures

The alarm hysteresis value can be set with the Function Block Detail Builder.
• Hysteresis:
Engineering unit data within the range of 0 to DV scale span, or percentage data for
the DV scale span
Default is 1.0 %.

■ Control Error Alarm Check
▼ Alarm for Control Error
In the control error alarm check it is determined whether or not the absolute value of the
cumulative deviation (DV), which may continue to increase even after the activation of the
cumulative deviation alarm, exceeds the absolute value of the control error alarm setpoint
value (VL).
If it is determined that the absolute value of the cumulative deviation (DV) exceeds the
absolute value of the control error alarm setpoint value (VL), a positive direction control
error alarm (HDV) is activated if the deviation is in the positive direction. And, when the
deviation is in the negative direction, a negative direction control error alarm (LDV) occurs.
When an alarm has occurred, if the cumulative deviation (DV) absolute value drops lower
than the control error alarm setpoint (VL) absolute value minus the hysteresis value, the
alarm is returned to normal state.
Cumulative deviation (DV)

Control error alarm setpoint
| VL |
| DL |
Cumulative deviation alarm
setpoint
SV
0
Deviation PV
| VL |
| DL |
D011213E.EPS
Figure Actions of Control Error Alarm Check

The control error alarm check type, control error alarm setpoint (VL) and the alarm hyster-
esis value can be set.
● Control Error Alarm Check Types

The control error alarm check type is set with the Function Block Detail Builder. The default
is “detection of both directions.”
Monitors the deviation of both the positive and negative directions.
Monitors the deviation of either the positive or negative direction only.
• No alarm:
Detection is not performed.
When single direction is selected for the control error alarm check type, only the deviation
in the positive direction is monitored when the control error alarm setpoint (DL) has a plus
sign, and only the deviation in the negative direction is monitored when the control error
alarm setpoint has a minus sign.
● Control Error Alarm Setpoint (VL)

The control error alarm setpoint is set by the operation and monitoring function.
• Control error alarm setpoint:
Engineering unit data within the DV scale span range
Default is DV scale span

The alarm hysteresis value can be set with the Function Block Detail Builder.
• Hysteresis:
Engineering unit data within the range of 0 to DV scale span, or percentage data for
the DV scale span
Default is 1.0 %.

■ Data Items - PI-BLEND
Table Data Items of Blending PI Controller Block (PI-BLEND) (1/2)
Item or Not
DV Cumulative deviation value DV engineering unit value 0
VL Control error alarm setpoint (DSH - DSL) DSH - DSL
DL Cumulative deviation alarm setpoint (DSH - DSL) DSH - DSL
D011210E.EPS

DSH: DV scale high limit
DSL: DV scale low limit
SEE ALSO
For a list of valid block modes of the PI-BLEND block, see D1.1.4, “Valid Block Modes for Each Regula-

Table Data Items of Blending PI Controller Block (PI-BLEND) (2/2)
Item or Not
TK Time scale conversion coefficient 1 to 100,000 1
RP Ramp constant 0 to (MSH - MSL) MSH to MSL
RST Cumulative deviation reset switch 0, 1 0
SH PV scale high limit Value in the same engineering unit as PV O/S (MAN)
DSH DV scale high limit Value in the same engineering unit as DV -----
DSL DV scale low limit Value in the same engineering unit as DV -----
D011211E.EPS

DSH: DV scale high limit
DSL: DV scale low limit

<Toc> <Ind> <D1.13 Self-Tuning PID Controller Block (PID-STC)> D1-132
D1.13 Self-Tuning PID Controller Block (PID-STC)

The Self-Tuning PID Controller Block (PID-STC) has both the PID control function
and self-tuning function (STC function). This function block is used to automatically
adjust PID parameters (P, I, D).
■ Self-Tuning PID Controller Block - (PID-STC)

▼ Connection
The Self-Tuning PID Controller Block (PID-STC) has both the PID control function and self-
tuning function (STC function). The STC function automatically sets PID parameters (P, I,
D).
The STC function provides the following two merits:
• Maintains optimum controllability in spite of the static and dynamic process character-
istics variation
• Reduces the work load of tuning operation at process startup
The figure below shows a function block diagram of Self-Tuning PID Controller Block (PID-
STC):

CSV
AUT
SV
MAN
RSV
RCAS
MAN
Self-tuning control CAS/AUT
Input Output
processing
ROUT
SUB
D011301E.EPS
Figure Function Block Diagram of Self-Tuning PID Controller Block (PID-STC)

The figure below shows a block diagram of the self-tuning control computation processing
area of the Self-Tuning PID Controller Block (PID-STC):
Estimated
process
model
PID Process
parameter characteristic
calculation estimation
P I D Response
monitoring
SV - PID PV
Process
controller MV
D011302E.EPS
Figure Block Diagram of the Self-Tuning Control Computation Processing Area
The Self-Tuning PID Controller Block (PID-STC) estimates process characteristics while
monitoring process variables (PV) and manipulated output values (MV) to create an esti-
mated process model. Optimum PID parameters (P, I, D) are calculated based on the
estimated process model.
terminals of the Self-Tuning PID Controller Block (PID-STC):
Table Connection Methods and Connected Destinations of the I/O Terminals of Self-Tuning PID
Controller Block (PID-STC)
SET Setting input
Reset signal 1
RL1
input
Reset signal 2
RL2
input
Compensation
BIN
input
Tracking signal
TIN
input
D011303E.EPS

■ Function of Self-Tuning PID Controller Block (PID-STC) ¡ £
The PID-STC block performs input processing, control computation processing, output
The only processing timing available for the PID-STC block is a periodic startup. Selections
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the PID-STC
● Control Computation Processing of Self-Tuning PID Controller Block (PID-

STC)
The function of the PID-STC block related to control computation processing includes the
“PID control function” and the “self-tuning function (STC function).”
SEE ALSO
• For the PID control function, see D1.13.1, “Control Algorithm of Self-Tuning PID Controller Block (PID-
STC).”
• For details on the self-tuning function (STC function), see sections from D1.13.2, “Self-Tuning Function
(STC Function)” through D1.13.8, “Points of Using Self-Tuning PID Controller Block (PID-STC).”

■ Data Items - PID-STC
Table Data Items of Self-Tuning PID Controller Block (PID-STC) (1/4)
Item or Not
BSTS Block status ----- RUN, OFF
D011304E.EPS

SEE ALSO
For a list of valid block modes of the PID-STC block, see a chapter D1.1.4, “Valid Block Modes for Each

Item or Not
MH Manipulated variable high - limit setpoint MSL to MSH MSH
ML Manipulated variable low - limit setpoint MSL to MSH MSL
P Proportional band 0.0 to 1000.0 % 100.0 %
I Integral time 1.0 to 10,000.0 seconds 20.0 seconds
D011305E.EPS


Item or Not
D011306E.EPS


Entry Permitted
Data Item Data Name Range Default
or Not
STC STC operation mode selection switch (*1) -1, 0, 1, 2, 3 0 (*1)
TR Process 95% response time 1 to 10,000 seconds 40 seconds
NB Noise band 1.0 % to 20.0 % of PV 1.0 % of PV
OS Control target type 0, 1, 2, 3 2
MI MV impulse amplitude 0.0 % to 20.0 % of MV 5.0 % of MV
PMAX Proportional band high limit 0.0 to 1000.0 % 1000.0 %
PMIN Proportional band low limit 0.1 to 1000.0 % 0.1 %
IMAX Integral time high limit 0.1 to 1000.0 seconds 10000.0 seconds
IMIN Integral time low limit 0.1 to 1000.0 seconds 0.1 seconds
DMAX Derivative time high limit 0.0 to 1000.0 seconds 2000.0 seconds
PIDC PID update ratio coefficient 0.00 to 1.00 1.00
CR Estimation accuracy error 0.000 to 100.000 -----
LM Estimated equivalent dead time 0.0 to 10,000.0 seconds -----
Estimated equivalent first-order lag
TM 0.0 to 10,000.0 seconds -----
constant
GM Estimated equivalent process gain 0.000 to 100.000 -----
PA Proportional band calculation value 0.0 to 1000.0 % -----
IA Integral time calculation value 0.1 to 10000.0 seconds -----
DA Derivative time calculation value 0.0 to 10000.0 seconds -----
D011307E.EPS

*1: ¡ For CS 1000, if there are more than 5 PID-STC in one FCS, the default value will be -1 for the blocks from the 6th
PID-STC.
£ For CS 3000, if there are more than 10 PID-STC in one FCS, the default value will be -1 for the blocks from the
11th PID-STC.

D1.13.1 Control Algorithm of Self-Tuning PID Controller Block

(PID-STC)
Self-Tuning PID Controller Block (PID-STC) obtains manipulated output value (MV)
and manipulated output change (MV) based on PID algorithm.
■ PID Control Algorithm

The Self-Tuning PID Controller Block (PID-STC) uses the same PID control algorithm as
the PID controller block (PID).
SEE ALSO
For the details of PID control algorithm, see a section “■ PID Control Computation” in D1.5, “PID Control-
ler Block (PID).”
■ Control Action Bypass

When 0 is set for the PID parameter (P) or (D) of the Self-Tuning PID Controller Block (PID-
STC), parts of the control action can be bypassed.
The figure below shows the partially bypassed control action and setpoint values of PID
parameters (P, I, D):
Table Partially Bypassed Control Action and Setpoint Values of PID Parameters (P, I, D)
Control action PID parameter setpoint value
Proportional (P) +integral (I) P0, D=0
Integral (I) P=0
D011308E.EPS
If you want to run the PID controller in proportional-integral (PI) action, you may set a value
other than 0 to parameter (P) and set to parameter (D). If run the controller in integral (I)
actions only, you may set 0 for parameter (P). In this case, even set a value for parameter
(D), the derivative (D) action does not work. When execute integral (I) action only, the
proportional gain (Kp) becomes 1.
IMPORTANT
The Self - Tuning PID Controller Block (PID-STC) is unable to control astatic processes by
using integral (I) actions only. If the process type is set as “astatic system (integral system)”
and only integral (I) action defined, the block changes to STC function invalid (INVL) status,
and stops the STC function.

D1.13.2 Self-Tuning Function (STC Function)

The self-tuning function (STC function) determines a tuning index based on the
estimated process model, PID control algorithm, process type and control target
type, to calculate optimum PID parameters (P, I, D) in accordance with the obtained
tuning index.
■ Self-Tuning Function (STC Function)

The self-tuning function (STC function) estimates process characteristics while monitoring
process variables (PV) and manipulated output values (MV) to create an estimated pro-
cess model. It then determines a tuning index based on the estimated process model, PID
control algorithm, process type and control target type, and calculates optimum PID param-
eters (P, I, D) in accordance with the obtained tuning index.
The STC function can be started by the following three methods:
• Initialize start
• Auto-startup
• On-demand tuning
SEE ALSO
• For the details of initialize start, see a chapter D1.13.4, “Initializer Start.”
• For the details of auto-startup, see a chapter D1.13.5, “Auto-Startup.”
• For the details of on-demand tuning, see a chapter D1.13.6, “On-Demand Tuning.”

■ Tuning Index
Generally, in a normal PID controller block (PID), optimum PID parameters (P, I, D) vary
with the purpose of control: to follow up the setpoint value or to prevent from disturbances.
Therefore, it is difficult to tune parameters in a single set of PID parameters (P, I, D) to
obtain the optimum responses for the prompt follow-up of set point value change as well as
to restrain from external disturbances. The Self-Tuning PID Controller Block (PID-STC)
changes the index (tuning index) according to the control target and the PID control func-
tion algorithm and block mode, so that optimum responses can be obtained based on each
tuning index.
The table below shows the tuning indexes of the Self-tuning function (STC function):
Table Tuning Indexes
Tuning index
Control algorithm
Block mode AUT Block mode CAS Block mode RCAS
Setpoint value follow-up Setpoint value follow-up Setpoint value follow-up
PID
response response response
Disturbance suppression Disturbance suppression Disturbance suppression
I-PD
Setpoint value follow-up Setpoint value follow-up Setpoint value follow-up
PI-D
Automatic determination Disturbance suppression Setpoint value follow-up Setpoint value follow-up
Automatic determination 2 response response response
D011309E.EPS
The Self-Tuning PID Controller Block (PID-STC) calculates PID parameters (P, I, D) of the
setpoint value follow-up type when the PV derivative type (PI-D) control algorithm is used,
and calculates those of the disturbance suppression type when the PV proportional and
derivative type (I-PD) control algorithm is used.
When the STC function calculates PID parameters based on the result of process estima-
tion, the following processing are performed:
• When the block detects that response is tending to hunt, the tuning stops when such
hunting occurs only for one cycle to ensure safety.
• When the gain of the controller block is increased, the change is limited to ensure
safety.
• When the deviation remains large for a prolonged period of time, the gain of the
controller block increases.

■ Number of Simultaneously Executable Blocks ¡ £
There is no limit to the number of Self-tuning PID controller blocks (PID-STC) that can be
used in one FCS. However, the number of Self-tuning PID controller blocks (PID-STC)
executing self-tuning function (STC function) at the same time is limited to 5 (*1) or 10 (*2)
blocks per FCS.
If more than 5(*1) or 10 (*2) Self-tuning PID controller blocks (PID-STC) are defined by the
Function Block Detail Builder, the first 5 blocks (*1) or 10 blocks (*2) with the smaller block
numbers are set in the PID parameter display mode (STC=0), while the remaining Self-tuning
PID controller blocks (PID-STC) are set in the STC operation stop mode (STC=-1).
If 5 (*1) or 10 (*2) Self-tuning PID controller blocks (PID-STC) are currently executing the
STC function, the STC function of a new Self-Tuning PID Controller Block cannot be
started. Only after one of the currently executing Self-Tuning PID Controller Blocks (PID-
STC) stops the STC function i.e., changes its STC operation mode (STC=-1), the new Self-
Tuning PID Controller Block can start the STC function.
*1: ¡ Restriction for CS 1000.
*2: £ Restriction for CS 3000.

D1.13.3 Self-Tuning Operating Modes

The self-tuning operating mode (STC operating mode) determines the action of the
Self-tuning function (STC function). The Self-Tuning PID Controller Block (PID-STC)
uses five types of STC operating modes.
■ Self-Tuning Operating Mode (STC Operating Mode)

Switching between the STC operating modes is done via an STC operating mode selection
switch (STC).
● STC Stop Mode (STC=-1)

The STC function is not executed in this mode.
Neither process characteristic estimation nor PID parameter (P, I, D) calculation are per-
formed.
The block acts in the same way as a PID Controller Block (PID).
● PID Parameter Display Mode (STC=0)

In this mode, process characteristic estimation and PID parameter (P, I, D) calculation are
performed, but the calculated PID parameters (P, I, D) are only displayed and not used for
control.
In the PID parameter display mode, process characteristic estimation is performed when
the process variable (PV) moves out of the noise band (NB), and PID parameter (P, I, D)
calculation is performed if the estimation accuracy is high. The calculated PID parameters
(P, I, D) are only displayed and not used for control.
● PID Parameter Automatic Updating Mode (STC=1)

In this mode, process characteristic estimation and PID parameter (P, I, D) calculation are
performed, and the calculated PID parameters (P, I, D) are used for control. In the PID
parameter automatic updating mode, process characteristic estimation is performed when
the process variable (PV) moves out of the noise band (NB), and PID parameter (P, I, D)
calculation is performed if the estimation accuracy is high. The calculated PID parameters
(P, I, D) are used for control.

● Auto-Startup Mode (STC=2)
Auto-startup is executed in this mode.
The process 95 % response time, noise band and PID parameters (P, I, D) are calculated
automatically. This mode is used when initial setpoint values are not known, such as during
plant startup.
● On-Demand Mode (STC=3)

On-demand tuning is executed in this mode.
Step test signals are added to the manipulated output value (MV), and PID parameters (P,
I, D) are calculated based on the response waveform of the corresponding process vari-
able (PV).
SEE ALSO
• For the details of auto-startup, see a chapter D1.13.5, “Auto-Startup.”
• For the details of on-demand tuning, see a chapter D1.13.6, “On-Demand Tuning.”

■ Flow of Self-Tuning Actions
During each control period, the Self-Tuning PID Controller Block (PID-STC) performs
actions in accordance with the Self-tuning operating mode (STC operating mode).
STC function
STC operating
STC=-1 mode
STC=2 STC=3
STC=0, 1
PV and MV data
Manual mode Manual mode Manual mode

Block mode
Block mode Block mode
(*1)
Automatic mode Automatic Automatic
mode mode
No
Change in PV
Yes
Estimation of
Auto-startup On-demand
process
characteristics
No High estimation
accuracy
Yes
Operating mode
Calculation of
recovery
PID parameters
STC=0
Operating mode
STC=1
Setting of PID
parameters
(*1) Go to the step below if “disable” is set for the STC

Return function bypass specification during the MAN mode.
D011310E.EPS
Figure Flow of Self-Tuning Actions

■ Actions in Self-Tuning Operating Modes (STC Operating Modes)
Table Table of Actions in Self-Tuning Operating Modes (STC Operating Modes) (1/2)
STC operating mode
selection switch Block mode Action
Previous Current
MAN Remains in the initialization processing state (*1).
0
AUT Starts normal processing after initialization processing (*1).
MAN Remains in the initialization processing state (*1).
1
AUT Starts normal processing after initialization processing (*1).
-1
Remains in the initialization processing state.
MAN
2 Startup mode waiting state (*1).
AUT Operation disabled. Returns to STC=-1.
3 All Operation disabled. Returns to STC=-1.
-1 All Stops STC actions. The block mode remains the same.
1 All No special processing. The block mode remains the same.
MAN Remains in the startup mode waiting state.
0 2
AUT Operation disabled. Returns to STC=0.
MAN Operation disabled. Returns to STC=0.
3
AUT On-demand mode. Returns to STC=0 after applying signals to MV.
D011311E.EPS
All: All normal modes (MAN, PRD, ROUT, AUT, CAS, RCAS)
*1: ¡ For CS 1000, only up to 5 PID-STC blocks are allowed to run self-tuning at the same time per one FCS. The STC
setting will be forced to -1 for the blocks from the 6th PID-STC.
£ For CS 3000, only up to 10 PID-STC blocks are allowed to run self-tuning at the same time per one FCS. The STC
setting will be forced to -1 for the blocks from the 11th PID-STC.
MAN: All manual modes (MAN, PRD, ROUT)
All: All automatic modes (AUT, CAS, RCAS)
All normal modes, if “No” is selected for the STC bypass specification during the MAN mode.

Table Table of Actions in Self-Tuning Operating Modes (STC Operating Modes) (2/2)
STC operating mode
selection switch Block mode Action
Previous Current
-1 All Stops STC actions. The block mode remains the same.
0 All No special processing. The block mode remains the same.
MAN Remains in the startup mode waiting state.
1 2
AUT Operation disabled. Returns to STC=1.
MAN Operation disabled. Returns to STC=1.
3
AUT On-demand mode. Returns to STC=1 after applying signals to MV.
MAN Stops STC actions. The block mode remains the same.
-1 Suspends the startup action. Stops STC actions. The block mode
AUT
changes to MAN.
2 Stops the startup action. The block mode and block status change
0 All
to MAN and PVER, respectively.
Stops the startup action and returns to STC=0. The block mode and
1 All
block status change to MAN and PVER, respectively.
3 All Operation disabled. Returns to STC=2.
The operating mode of STC=3 returns to the original operating
mode in the next control period. In the previous operating mode
3 All All
transition, actions will continue assuming that the STC=3 mode has
never existed.
D011312E.EPS
All: All normal modes (MAN, PRD, ROUT, AUT, CAS, RCAS)
MAN: All manual modes (MAN, PRD, ROUT)
AUT: All automatic modes (AUT, CAS, RCAS)
All normal modes, if “disable” is selected for the STC bypass specification during the MAN mode.
SEE ALSO
For the details of self-tuning operating mode selection switch (STC), see a chapter D1.13.7, “Tuning
Parameters of Self-Tuning PID Controller Block (PID-STC).”

D1.13.4 Initializer Start

Initializer start can be executed in the situation that allows to use the estimated
initial values of PID parameters (P, I, D).
The initializer start function uses estimated PID parameters (P, I, D) to start control.
■ Execution of Initializer Start

The methods used to start initialization are shown below. To execute initializer start, the
following conditions must be satisfied:
• The self-tuning operating mode (STC operating mode) is STC stop.
• The block mode is manual (MAN).
• The following parameters are set:
PID parameters (P, I, D)
Process 95 % response time (TR)
Noise band (NB)
Control target type (OS)
PID data set high/low limits (PMAX, PMIN, IMAX, IMIN, DMAX)
PID update ratio coefficient (PIDC)
IMPORTANT
Before changing the block mode to any of the automatic modes (AUT/CAS/RCAS), confirm
that measured signals are within the safety range where step changes (MI) can be added
to manipulated output signals, and the measured process signals are sufficiently stable.
When the following operations are performed with the above parameters set, initializer start
will be executed after the time set as the process 95 % response time (TR) has elapsed:
1. Change the STC operating mode to the PID parameter display or PID automatic
updating mode.
2. Change the block mode to any of the automatic modes (AUT/CAS/RCAS).
Upon executing initializer start, PID control and self-tuning starts using the values set for
PID parameters (P, I, D) as initial values.

D1.13.5 Auto-Startup
In the process where step response can be obtained, use auto-startup if initial
setpoint values of PID parameters (P, I, D) cannot be estimated, such as when the
plant is first started.
The auto-startup function starts control by automatically calculating the process 95
% response time (TR), noise band (NB) and PID parameters (P, I, D) based on data
obtained via step responses.
■ Execution of Auto-Startup
The methods of auto-startup are shown below. To execute auto-startup, the following
conditions must be satisfied:
• The self-tuning operating mode (STC operating mode) is STC stop.
• The block mode is manual (MAN).
• The following parameters are set:
Control target type (OS)
MV Impulse amplitude (MI)
PID parameter (P)
PID parameter (D)
When the following operations are performed after the above conditions established, auto-
startup can be executed.
1. Change the STC operating mode to auto-startup.
2. Change the block mode to any of the automatic modes (AUT/CAS/RCAS).
Upon auto-startup, the following actions take place:

1. The block status changes to STUP (during auto-startup), and the current manipulated
output value (MV) is held for 30 seconds.
2. Step signal set as the MV Impulse amplitude (MI) is added to the manipulated output
value (MV) in the direction of increasing deviation.
3. Observation of the response waveform of measured signals relative to the step
change is started. If, during the observation, the measured signal change (PV)
becomes equivalent to or larger than 1.5 times of the MV Impulse amplitude (MI), the
manipulated output value (MV) returns to the original value to ensure safety.

4. If the target process is a static system (IP=0), the manipulated output value (MV)
returns to the original value after the response waveform is observed for a specified
period of time. If the process is an astatic system (IP=1), the step changes equivalent
to the MV Impulse amplitude (MI) is added to the manipulated variable in the reverse
direction, then the manipulated output (MV) returns to the original value.
5. Process characteristics is estimated based on the data obtained by the step response
observation.
6. The process 95 % response time (TR) and PID parameters (P, I, D) are calculated
based on the estimated model.
7. The following computations on the PID parameters (P, I, D) of the estimated model are
performed, and the computed results are set as PID parameters’ high/low limits
(PMAX, PMIN, IMAX, IMIN, DMAX).
PMAX=4 • PB
PMIN= PB
4
IMAX=4 • TI
IMIN= TI
4
DMAX=4 • TD D011313E.EPS
Some of these values may be fixed to “0” depending upon the control method.
8. Measured noise is observed for a specified period of time (2TR; minimum 2 min-
utes, maximum 5 minutes), and the noise band (NB) is calculated based on the peak
value.
9. The STC operating mode automatically changes to the PID parameter automatic
updating mode (STC=1), then PID control and self-tuning start to run.

● Example of the Auto-Startup Action in Static Process
Auto-startup begin
(STC=2,MANAAUT) Auto-startup end
MI signal
application Tuning end
MI
MV
PV
Time
Waiting for settling Waveform Noise
(30 seconds) observation observation Operation after switching to
Block status "STUP" the PID automatic
updating mode (STC=1)
D011314E.EPS
Figure Example of the Auto-Startup Action in Static (Non-Integral) System
● Example of the Auto-Startup Action in Astatic Process

Auto-startup begin
(STC=2,MANAAUT) Auto-startup end
MI signal
application Tuning end
MI
MV
MI
PV
Time
Waiting for settling Waveform Noise
(30 seconds) observation observation Operation after switching to
Block status “STUP” the PID automatic
updating mode (STC=1)
D011315E.EPS
Figure Example of the Auto-Startup Action in Astatic (Integral) System

■ Abnormal Termination of Auto-Startup
The following section explains the abnormal termination of auto-startup.
● Causes of the Abnormal Termination of Auto-Startup

The auto-startup action is terminated abnormally if the following events occur:
• Power failure
• Change in the self-tuning operating mode (STC operating mode)
• Change to a block mode other than automatic modes (AUT, CAS, RCAS).
• Failure to create an estimated process model
• The measured signal change (PV) remains under 0.5 % of the MV Impulse ampli-
tude (MI) after the maximum observation time (90 minutes) elapsed.
• Insufficient information from step response.
• The data status of the manipulated output value (MV) changes to CLP or CND.
• The alarm status changes to IOP+, IOP-, OOP or CNF.
● Self-Tuning PID Controller Block (PID-STC) upon Abnormal Termination of

Auto-Startup
When the auto-startup action is stopped, the following changes take place inside the Self-
tuning PID controller block (PID-STC):
• The block changes to automatic (AUT) mode.
• The STC operating mode changes to PID parameter display (STC=0).
• The block status changes to auto-startup abnormal termination (PVER).
The block status changes or set the STC operating mode operation stop (STC=-1) cancels
the auto-startup abnormal termination status.
IMPORTANT
Do not use auto-startup for systems whose process dead-time is short. This is because an
abnormal termination processing of the auto-startup may not be carried out if the process
dead-time is 4 seconds or less. If an abnormal termination processing could not be carried
out, the block status remains as STUP.
If an auto-startup has been used by mistake, change the block mode to MAN mode and
interrupt the auto-startup.

■ Setup Items for Auto-Startup
The following items must be set in the auto-startup mode:
• Control target type (OS):
Specify the type of response waveform to be targeted by the self-tuning function (STC
function)
Select a target suitable for the controlled plant
• MV Impulse amplitude (MI):
Set a value that may trigger the process variable (PV)’s impulse response around 5
%.
• Control method (P, I, D):
Specify a desired control method
Specify one of the following three types of control methods:
I control: P=0
PI control: P0, D=0
PID control: P0, D0
Within the range allowed by the process, the bigger the impulse response from the process
variable (PV) the more accurate estimation can be provided by the model.
When a control algorithm that uses derivative (D) action is selected, it may change to the
control method that does not use derivative (D) action if it is judged appropriate by the STC
function.

D1.13.6 On-Demand Tuning

On-demand tuning is applied to tune PID parameters (P, I, D) when tuning request is
given from the operator. On-demand tuning may be applied to the loops where the
change of setpoint values need to be avoided.
■ Execution of On-Demand Tuning

For on-demand tuning, when a tuning demand is given from the operator, a step test signal
is added to the manipulated output value (MV) in a closed loop. Then the self-tuning is
performed based on the response waveform of the corresponding process variable (PV).
The method of on-demand tuning is shown below. To execute on-demand tuning, the
following conditions must be satisfied:
• The self-tuning operating mode (STC operating mode) is the PID parameter display or
PID automatic updating mode
• The block mode is one of the automatic modes
IMPORTANT
Before changing to the on-demand tuning mode, confirm that the value of the MV Impulse
amplitude (MI) is well within the safe range.
When the STC operating mode is changed to on-demand tuning in the above state, on-
demand tuning may be executed.
During on-demand tuning, the following actions take place:
1. Step signal equivalent to the MV Impulse amplitude (MI) is added to the manipulated
output (MV) in the direction of decreasing deviation.
If the process type is “astatic system (IP=1),” the pulse of TR/5 in time span will be
added.
2. After the step signals is added, the STC operating mode returns to “0” or “1” in the
next control period.
3. The response waveform of a measured signal that corresponds to the step change is
monitored.
4. PID control and self-tuning are started.
MV
PV
Time
Tuning
Set as “STC=3”
(on-demand command)
D011316E.EPS
Figure Responses in the On-Demand Mode
If responses from the process are extremely monotonous, an estimated model may not be
created. In this case, increase the MV Impulse amplitude (MI) and retry the self-tuning.

■ Setup Item for On-Demand Tuning
The following item must be set in order to execute on-demand tuning:
%.
Within the range allowed by the process, the bigger the impulse response from the process
variable (PV) the more accurate estimation can be provided by the model.

D1.13.7 Tuning Parameters of Self-Tuning PID Controller Block

(PID-STC)
This tuning parameters of PID-STC block consist of three types; Setting parameters
that may be set on the tuning window; Parameters for indication and the parameters
defined on the function block detail definition window.
■ Tuning Parameters
The tuning parameters of the Self-Tuning PID Controller Block (PID-STC) include the
following types:
• Parameters may be set on tuning window
These tuning parameters can be set on the tuning window during operation.
• Parameters for indication
These parameters are displayed in the tuning window to indicate the operating status
of the STC function. The values of the parameters are calculated automatically by the
Self-tuning PID Controller Block (PID-STC).
• Parameters defined on the Function Block Detail Builder
These parameters are defined on the Function Block Detail Builder.

● Parameters Set from the Tuning Window
The table below shows the parameters that are set from the tuning window:
Table Parameters Set from the Tuning Window
Entry Setup items in each

Symbol Name enable/ Range Default operating mode
disable -1 0 1 2 3
STC operating mode
STC -1, 0, 1, 2, 3 0 (*1) (*4)
selection switch
TR Process 95 % response time 1 to 10000 seconds 40 seconds -
1.0 to 20.0 % of the PV

NB Noise band 1.0 % (*2) -
value (*2)
OS Control target type 0, 1, 2, 3 2 -
0.0 to 20.0 % of the MV
MI MV Impulse amplitude 5.0 % (*3) - - -
value (*3)
P Proportional band 0.0 to 1000.0 % 100.0 %
I Integral time 0.1 to 10000.0 seconds 20.0 seconds
D Derivative time 0.0 to 10000.0 seconds 0.0 second
PMAX Proportional band high limit 0.0 to 1000.0 % 1000.0 % -
PMIN Proportional band low limit 0.1 to 1000.0 % 0.1 % -
IMAX Integral time high limit 0.1 to 10000.0 seconds 10000.0 seconds -
IMIN Integral time low limit 0.1 to 10000.0 seconds 0.1 second -
DMAX Derivative time high limit 0.0 to 10000.0 seconds 2000.0 seconds -
PIDC PID update ratio coefficient 0.00 to 1.00 1.00 - - - -
D011317E.EPS
: Can be entered from the tuning windows at any time.

: Setting required.
-: Setting not required.
: Setting is done automatically, but can be entered from the tuning window, as well.
*1: The default values of the 11th and subsequent PID-STC controller blocks within the same control station will be -1.
*2: A percentage value converted from the PV engineering unit data.
*3: A percentage value converted from the MV engineering unit data.
*4: A determining factor of the operating mode.

● Display Parameters
The table below shows display parameters. These parameters are displayed in the tuning
window to indicate the operating status of the STC function.
Table Display Parameters

Symbol Name enable/ Range operating mode
disable -1 0 1 2 3
CR Estimation accuracy error 0.000 to 100.000
LM Estimated equivalent dead time 0.0 to 10000.00 seconds
Estimated equivalent first-order lag
TM 0.1 to 10000.0 seconds
constant
GM Estimated equivalent process gain 0.000 to 100.000
PA Proportional band calculation value 0.0 to 1000.0 %
IA Integral time calculation value 1.0 to 10000.0 seconds
DA Derivative time calculation value 0.0 to 10000.0 seconds
D011318E.EPS
: Cannot be entered from the tuning window.

: Items for automatic calculation and display only.
● Items Defined in the Function Block Detail Builder

The table below shows the tuning parameters of the Self-Tuning PID Controller Block (PID-
STC) defined in the Function Block Detail Builder:
Table Items defined in the Function Block Detail Builder

Symbol Name enable/ Range Default operating mode
disable -1 0 1 2 3
IP Process type 0, 1 0 (non-integral)
- Manual mode STC function bypass ON, OFF ON
D011319E.EPS
: Item defined in the Function Block Detail Builder.

■ STC Operating Mode Selection Switch (STC)
Set the operating mode of the Self-Tuning PID Controller Block (PID-STC) to the STC
operating mode selection switch.
• STC: Specify the operating mode using a numeric value.
The following operating modes can be selected:
-1: STC operation stop mode
0: STC parameter display mode
1: STC parameter automatic updating mode
2: Auto-startup mode
3: On-demand mode

■ Process 95 % Response Time (TR)
Set the rise time for 95 % of process step response in an open-loop.
● Process 95 % Response Time Setting Methods

The Self-Tuning PID Controller Block (PID-STC) calculates the time for measured signal
waveform observation as well as sampling time for process characteristic estimation,
based on the process 95 % response time (TR). To operate the STC function in a good
condition, an optimum value for the process 95 % response time (TR) is required.
• Process 95 % response time
Set the rising time for 95 % of process step response in an open-loop.
The procedure to set an optimum TR value is shown below:

• When step responses from the process are known
Set the time required for the process variable change (PV) to reach 95 % of the
settling value.
• When the process can be approximated based on the first-order lag system
Obtain TR that satisfied TR=L+3T, from the dead time (L) and first-order lag constant
(T) of the process, and set the obtained value as the process 95 % response time
(TR).
• When the process is an astatic system (integral system)
The time required for the process variable change (PV) reach 95 % peak can be set
as the response rising time (TR) after an impulse is applied to the process.
• When the past operating process behavior is known
Obtain the specific oscillation cycle (Tp) of the process from the past operation data,
and set this value as the process 95 % response time.
• When the response time is expected to change
Set a value in accordance with the particular response waveform to be controlled. As
in the case of furnace temperature, if the response rising time of the process variable
(PV) is different from the falling time, use the longer response time. In this way, esti-
mated process characteristic values will have less error than that the shorter response
time is used.

● Examples of Process 95 % Response Time (TR) Estimation
The figures below are examples of process response estimation when step responses from
the process are known (estimated from the step response waveform) and when the past
operation conditions are known (estimated from damped oscillatory waveform):
Estimation from the step response waveform
MV
PV
settling value
PV
95 %
Time
TR
Estimation from the damped oscillatory waveform
TR=TP
PV
TP
Specific
oscillation cycle
Time
D011320E.EPS
Figure TR Estimation Methods
■ Noise Band (NB)

Set the noise band (NB) to prevent process characteristic estimation from being disturbed
by noise. For the noise band, set a value that is twice of the peak value of random noise
being superimposed over measured signals (maximum width of noise).
When a noise band (NB) is set, process characteristic estimation will be started when the
process variable (PV) changes beyond the limits of noise band (NB) during a single sam-
pling period.
NB
Time
D011321E.EPS
Figure Noise Band
• Noise Band (NB):

Set a value that is twice of the peak value of random noise being superimposed over
measured signals (maximum width of noise).

■ Control Target Type (OS)
The desirable control target response waveform varies depending upon the process type
and operating method. Set a control target type (OS) from the tuning window according to
the controlled system.
• Control target type (OS):
Select a control target type and specify a numeric value indicating the type.
The table below shows the control target types (OS) that can be set for the Self-Tuning PID
Controller Block (PID-STC):
Table Control Target Types
OS Target overshoot Characteristics Evaluation expression
0 0% Overshoot: zero Overshoot zero
Minimum time-load control area
Overshoot: small
1 5%
Settling time: short Min | e | tdt
0
Minimum control area

Overshoot: medium
2 10 %
Rise time: slightly quick Min | e | dt
0
Minimum squared control area

Overshoot: large
3 15 % Rise time: quick Min e 2 tdt
0
D011322E.EPS
• 0
No overshoot exists.
• 1
Minimizes the product of the evaluation expression that multiplies the deviation area
by elapsed time. The overshoot is smaller and setting time is shorter.
• 2
Minimizes the control area (deviation). This is the default setting.
• 3
Minimizes the squared area of deviation. The overshoot is larger and rise time is
quicker.
Control area
SV
PV response
Time
D011323E.EPS
Figure Control Areas and PV Responses

■ MV Impulse Amplitude (MI)
The MV Impulse amplitude (MI) is the size of the test signal that is applied to the manipu-
lated output value (MV) during the auto-startup or on-demand mode. The value is set from
the tuning window.
%.
As the auto-startup mode is a MAN state, the current control deviation is assumed to be on
the safe side and the test signal is added in the direction of increasing control deviation. In
the on-demand mode, which is an AUT state, the test signal is added in the direction of
decreasing control deviation.
The table below shows the directions of MV step changes:
Table Directions of MV Step Changes
Action mode
Operating mode Deviation
Direct action Reverse action
SVPV +MI % -MI %
Auto-startup
SV<PV -MI % +MI %
SVPV -MI % +MI %
On-demand
SV<PV +MI % -MI %
D011324E.EPS
■ PID Parameters (P, I, D)

The PID parameters (P, I, D) are used in control computation. The values of respective
parameters are shown below:
• P: Proportional band
• I: Integral time
• D: Derivative time
During operation in the PID parameter automatic updating mode, the values set for PID
parameters (P, I, D) are used as initial values and updated automatically when the self-
tuning function (STC function) is activated.
Set initial values for PID parameters (P, I, D) using the following methods:
● New Process
• When estimation or calculation is possible based on the statistical data of other
processes
Use values estimated or calculated based on the statistical data of other processes.
• When using estimated or calculated values is difficult
Use auto-startup. If auto-startup cannot be used, perform self-tuning in the PID pa-
rameter display mode, and use the values displayed as new calculated values of PID
parameter (PA, IA, DA).
● Existing Control System Replacement

Use the PID values before the replacement.

■ PID Data Set High/Low Limits (PMAX, PMIN, IMAX, IMIN, DMAX)
If the process is likely to receive negative impacts when PID parameters (P, I, D) exceed
their specified limit, set PID data set high/low limits in advance.
The PID data set high/low limits indicate control ranges that are used to limit PID param-
eters (P, I, D) when they are changed by the STC function.
• PMAX: Proportional band high limit
• PMIN: Proportional band low limit
• IMAX: Integral time high limit
• IMIN: Integral time low limit
• DMAX: Derivative time high limit
The PID parameters (P, I, D) are limited within the range of the corresponding high/low
limits:
PMIN P PMAX (Same for PA when the STC value is “1”)

IMIN I IMAX (Same for IA when the STC value is “1”)
0 D PMAX (Same for DA when the STC value is “1”)
If the set high limit is smaller than low limit, the corresponding PID parameter (P, I or D) will
be fixed to the high limit value. If the DMAX value is 0, the value of the PID parameter (D)
becomes 0. If the PMAX value is 0, the value of the PID parameter (P or D) becomes 0.
If, due to the STC function any PID parameter (P, I, or D) exceeds the control range during
operation in the PID parameter automatic updating mode, the block status changes to PID
parameter limiting (PLMT) and the PID parameter (P, I or D) obtained by the STC function
will be limited within the range of the corresponding PID data set high/low limits (PMAX,
PMIN, IMAX, IMIN or DMAX).
The PID parameter limiting (PLMT) status is canceled when the applicable PID parameter
(P, I or D) has changed to a value inside the control range or when the STC actions have
stopped (STC=-1).

■ PID Update Ratio Coefficient (PIDC)
The PID update ratio coefficient (PIDC) represents a ratio at which the current PID param-
eters (P, I, D) are updated by the corresponding PID parameter values calculated by the
STC function (PA, IA, DA).
• PID update ratio coefficient (PIDC): A value between 0.00 and 1.00.
The parameters are not updated if PIDC is 0.00. If PIDC is 1.00, the PID parameter values
calculated by the STC function (PA, IA, DA) will be set directly as PID parameters (P, I, D).
If the estimated model remains unstable due to disturbances and the PID parameters (P, I,
D) tend to change although slightly with every tuning, set a smaller PIDC value to stabilize
the PID parameters (P, I, D).
This coefficient is effective only in the PID parameter automatic updating mode.
PBnew = (1.0-PIDC) • PB +PIDC • PA

TInew = (1.0-PIDC) • TI +PIDC • IA
TDnew = (1.0-PIDC) • TD +PIDC • DA
Pbnew: New effective proportional band value

PB: Current effective proportional band value
PA: PB calculated value
Tinew: New effective integral time value
TI: Current effective integral time value
IA: TI calculated value
Tdnew: New effective derivative time value
TD: Current effective derivative time value
DA: TD calculated value
PIDC: Update ratio coefficient (0.00 to 1.00)
IMPORTANT
When exceptional tuning is performed at slow response or hunting response processing,
the PID update ratio coefficient (PIDC) is ignored and the PID parameter values (PA, IA,
DA) calculated by the STC function will be set directly as PID parameters (P, I, D).

■ Estimation Error (CR)
Whenever an estimated process model is created, the STC function simulates the output of
the model and calculates a squared error based on the actual process response. The
estimation error is a value obtained from the best parameter set which has the smallest
estimation error.
If the estimated model matches perfectly with the actual process, the estimation error (CR)
becomes 0.000. However, as the actual process is affected by measurement noise and
various disturbances, deviations exist between the estimated model and actual process
and the value of the estimation error (CR) varies accordingly.
When the value of the estimation error (CR) exceeds 5.000, the Self-Tuning PID Controller
Block (PID-STC) assumes that the current estimated model is not effective and starts
creating a new estimated model using new data without updating the PID parameters (P, I,
D).
■ Estimated Models (LM, TM, GM)

The Self-Tuning PID Controller Block (PID-STC) creates estimated models by approximat-
ing the target process based on the dead time and first-order lag system. The estimated
models, LM, TM and GM, represent the equivalent dead time, equivalent first-order lag
constant and equivalent process gain, respectively.
The estimated models (LM, TM, GM) hold the latest values as long as the estimation error
(CR) is under 5.000.
The estimation error (CR) is updated every time a process characteristic estimation is
performed, but the estimated models (LM, TM, GM) are updated if the estimation error
(CR) is 5.000 or greater.
■ New Calculated Values of PID Parameters (PA, IA, DA)

The new calculated values of PID parameters obtained by the self-tuning function (STC
function). If the value of the Self-tuning operating mode (STC) is “1,” the new calculated
values of PID parameters (PA, IA, DA) are set as the corresponding PID parameters (P, I,
D) after receiving computation processing based on the PID update ratio coefficient
(PIDC).

■ Process Type (IP)
▼ Process Type
The process type indicates whether the target process is a static system (non-integral
system) or astatic system (integral system). The process type is specified in the Function
• Process Type: Select “Static system” or “Astatic.”
The default is “Static system.”
The static system is a process whose process variable (PV) changes gradually toward a
settling value when step change is added to the manipulated output value (MV), until an
equilibrium state is finally reached. The astatic system is a process whose process variable
(PV) rises or falls infinitely with time when step change is added to the manipulated output
value (MV). An example of astatic system is a constant-flow pump whose flowrate is
maintained at constant levels via level control.
The figures below show examples of step responses from static system and astatic system
processes:
Static system (non-integral system) process
MV
PV settling value
PV
Time
Astatic system (integral system) process
MV
PV
Time
D011325E.EPS
Figure Examples of Step Responses from Static System and Astatic System Processes

■ MAN Mode STC Function Bypass
▼ STC Function Bypass Designation for MAN Mode
Specify whether to use or bypass the self-tuning function (STC function) when the block is
in a manual operating mode (MAN, PRD or ROUT).
Use the Function Block Detail Builder to set the MAN mode STC function bypass specifica-
tion.
• STC function bypass designation for MAN mode: Select “Yes” or “No.”
In general, it is not desirable that PID parameters (P, I, D) change when PID computation is
not performed. Therefore, set “Yes” as the default bypass specification.
In the bypass mode, the STC function does become active. However, as I/O data is con-
stantly observed, the STC function becomes active as soon as the block changes to an
automatic operating mode (AUT, CAS or RCAS).
If “No” is set as the bypass specification, the STC function becomes active even in a
manual operating mode (MAN, PRD or ROUT). Setting “No” as the bypass specification is
effective in the PID parameter display mode or PID parameter automatic updating mode.

D1.13.8 Points of Using Self-Tuning PID Controller Block

(PID-STC)
This section explains the points to be noted when using the self-tuning function
(STC function) in various controlled systems and loops as well as applicability of the
function.
■ Applicable Conditions of Self-Tuning PID Controller Block (PID-STC)

The self-tuning function can be used only when the process satisfies the following condi-
tions:
• PID control is allowed.
• The cycle of factors that can cause changes in the control deviation (changes in
process characteristics and setpoint values, etc.) is longer than the specific oscillation
cycle of the control loop.
• Responses between the manipulated variable (MV) and process variable (PV) can be
approximated by the dead time and first-order lag system or integral system.
In general, many processes can be approximated with a combination of higher-order lag

element, dead time, and process gain, by the following expression:
Ke-LS
Gp(s)=
(1+T1S) • (1+T2S) ....... (1+TnS) D011326E.EPS
In estimated models created by the STC function, even the higher-order system used in the
above expression is approximated by the dead time and first-order lag system. The Self-
Tuning PID Controller Block (PID-STC) performs appropriate tuning after changes have
occurred in the process variable (PV) as a result of changes in the setpoint value or ma-
nipulated variable. Appropriate control is ensured if the ratio of dead time to lag time (L/T) is
3 or smaller.

■ Stable Control Loops (Regulatory Control)
When using a Self-Tuning PID Controller Block (PID-STC) in a stable control loop in which
the setpoint value does not change frequently and process characteristics undergo little
fluctuation, it is recommended that the control be performed with the self-tuning function
(STC function) turned OFF once optimum PID parameters (P, I, D) are calculated. The
procedure is shown below:
1. First, obtain optimum PID parameters (P, I, D) using the STC function.
2. Change the PID data set high/low limits to reduce the range of PID parameters (P, I,
D) or turn the STC function OFF (STC=-1).
■ Controlling a Process with a Longer Dead Time

The following section shows the points to be noted when using a Self-Tuning PID Controller
Block (PID-STC) in a process with a longer dead time:
When a Self-Tuning PID Controller Block (PID-STC) is used to control a process in which
the dead time element is dominant, determine whether or not appropriate control is feasible
using the Self-Tuning PID Controller Block (PID-STC), based on the value of the dead time/
lag time ratio (L/T).
• When the dead time/lag time ratio (L/T) of the process is smaller than 3
Appropriate actions can be obtained by combining basic PID functions and the STC
function.
• When the dead time/lag time ratio (L/T) of the process is larger than 3
It is difficult to perform control by combining basic PID functions and the STC function.
In this case, consider using the Smith’s Dead Time Compensation Control or sampled
value PI control. Note that the STC function cannot be used with either of these
control methods.

■ Cascade Control with Quicker Downstream Responses
The following section shows the points to be noted when using Self-Tuning PID Controller
Blocks (PID-STC) in a process with quick responses coming from downstream, by using an
example of a cascade loop consisting of temperature control and flowrate control as the
upstream and downstream processes, respectively.
Distillation
column Temperature TIC
FIC
Flowrate
Steam
D011327E.EPS
Figure Cascade Control loop with Quicker Downstream Responses
Unless frequent changes occur in the process of the downstream Self-Tuning PID Control-
ler Block (PID-STC), it is recommended to use the Self-tuning function (STC function) of
the upstream Self-Tuning PID Controller Block (PID-STC) only. The procedure is shown
below:
1. Change the downstream block to AUT mode to open the cascade connection.
2. Set an optimal PID value using the STC function of the downstream Self-Tuning PID
Controller Block (PID-STC).
3. Turn off the STC function of the downstream Self-Tuning PID Controller Block (PID-
STC).
4. Establish the cascade connection.
5. Turn on the STC function of the upstream Self-Tuning PID Controller Block (PID-
STC).

■ Cascade Control with Slower Downstream Responses
Block (PID-STC) in a process with slower responses coming from downstream, by using an
example of a cascade loop consisting of two temperature control processes in upstream
and downstream.
TC 1
Raw material
TC 2
Cooling
jacket
Water
Reactor
Steam
Split range control valve

D011328E.EPS
Figure Cascade Control with Slower Downstream Responses
The procedure to control this cascade loop is shown below:

1. Change the downstream block to AUT mode to open the cascade connection.
2. Set an optimal PID value using the STC function of the downstream Self-Tuning PID
Controller Block (PID-STC).
3. Turn off the STC function of the downstream Self-Tuning PID Controller Block (PID-
STC).
4. Establish the cascade connection.
5. Turn on the STC function of the upstream Self-Tuning PID Controller Block (PID-
STC).
In this type of cascade loop, it is generally recommended that the Self-tuning function (STC
function) be executed only in the upstream controller, which is the main target of control, in
order to avoid interaction between the two STC functions in upstream and downstream.

■ Controlling a Process with Changing Target Control Characteristics
Block (PID-STC) in a process where target control characteristics, such as gain, lag time
and dead time, fluctuate.
Intermediate
outflow volume
Inflow volume Pump F0
F1 Outflow volume
F
LIC FIC
Level
Tank
Re-circulated
D011329E.EPS
Figure Process with Changing Gain
The above example shows a process where the flowrate F is control target. Since the
flowrate F1, inflow of the tank, fluctuate periodically, the level control is activated to change
the intermediate outflow volume F0. The changes in F0 correspond to those in gain that
occur in the target control process of FIC.
If the change cycle of the target control characteristic is longer than the specific oscillation
cycle of the control loop, the self-tuning function (STC function) is activated to follow up the
change. If changes in the process variable response are detected as a result of the
changes in the target control characteristic, the STC function will be activated.

■ Neutralization Control
Block (PID-STC) for neutralization control.
14
Neutralizing
agent 12
pHC
10
Controlled fluid
pH 8
7
6
pH transmitter
4
0
MV (neutralizing agent)
D011330E.EPS
Figure Neutralization Control
In the neutralization control shown above, the pH process shows non-linear characteristics;
i.e., the gain increases significantly near the neutralizing point (pH=7) and becomes small
on both sides.
The pH controller is controlled by calculating optimum PID parameter values (P, I, D) near
the neutralizing point. Therefore, the proportional band converges by several hundred
percent, making it impossible to obtain appropriate control away from the neutralizing point.
In this case, specify non-linear gain processing for the controller and use the STC function
after obtaining linear characteristics.

■ Tank Level Control with Integral Characteristics
Block (PID-STC) in a process with integral characteristics, by using a level control process
as an example:
LIC
Q1
Q1 inflow volume
Level Fluid level H

gauge
Constant flowrate
Constant-flow pump t
D011331E.EPS
Figure Control with Integral Characteristics
The level control shown above is a process that maintains a constant outflow volume via a
constant-flow pump, regardless of the fluid level. In this process, the fluid level (H) contin-
ues to rise linearly as the inflow volume (Q1) increases. In other words, this is an integral
process that does not have a self-regulation function. When controlling an integral process,
use proportional and derivative (PD) control by setting a longer integral time, as the pro-
cess becomes unstable if the integral time is short.
In this type of integral process, use the self-tuning function (STC function) by setting “1” for
the process type (IP). When the process type (IP) is “1,” proportional and derivative (PD)
control is executed by setting a longer integral time.

■ Controlling a Process with Phases of Varying Response Speeds
Block (PID-STC) in a process where the response speed varies depending on the phase,
by using an example of temperature control.
MV Step input
Time
PV
Temperature
Time
Heating phase Cooling

phase
D011332.EPS
Figure Example of Step Responses in a Process with Phases of Varying Response Speeds
In a heating furnace or heat exchanger process that requires temperature control, the
process response time may vary with the heating phase and cooling phase. When using a
Self-Tuning PID Controller Block (PID-STC) to control these processes, set the
process 95 % response time (TR) based on the phase with a longer response time.
PID parameters changes between the optimum PID parameters (P, I, D) of the two
phases in accordance with the direction of process variable response actions.

■ Controlling a Process with Slower Actions at the Final Control Element
Block (PID-STC) in a process whose final control element exhibits slower actions, by using
an example of flowrate control with a motor-operated valve.
Flow gauge FIC
Motor-operated
M
valve
D011333E.EPS
Figure Motor-Operated Valve Flowrate Control
SV + + MV
PID
- -
PV
aTds
1+Tds
a: First-order lead computation gain
Td: First-order lead constant
D011334E.EPS
Figure Controlling a Process with Slower Actions at the Final Control Element
When performing flowrate control using a motor-operated valve, the speed of response
time control for the motor-operated valve may be affected, as the response time of the
motor-operated value is slower than that of the flow gauge. As the self-tuning function (STC
function) estimates process characteristics by taking into account delays at the final control
element, set a larger proportional band than when there is no delay at the final con-
trol element.
If controllability needs to be further improved, consider using phase compensation
by first-order lead computation, in order to compensate for the derivative actions.

■ Program Pattern Control
The following shows points to be noted when applying a Self-Tuning PID Controller Block
(PID-STC) to program control, by using an example of a program controlling process where
the setpoint value of the temperature controller is changed in accordance with a specific
temperature rise and fall pattern:
Temperature
Temperature pattern
Time
TPG Temperature pattern generator
TIC
Heat treatment
furnace
Fuel
D011335E.EPS
Figure Program Control
When applying a Self-Tuning PID Controller Block (PID-STC) to a program controlling

process where the setpoint value of the temperature controller is changed in accordance
with a specific temperature rise and fall pattern, note the following points:
• Select the PI-D type (PV derivative type) control algorithm. The I-PD type (PV propor-
tional and derivative type) algorithm provides poor follow-up capability relative to
changes in SV.
• If it requires that overshoot of the rising temperature must be minimized, set “0” for the
control target type (OS) of the Self-Tuning PID Controller Block (PID-STC).
In general, when the setpoint value changes along a ramp pattern, as in the case of rising
or falling temperature, the Self-Tuning PID Controller Block (PID-STC) generates an
offset. If on-demand tuning is executed at this time, the MV Impulse amplitude
(MI) is applied to the manipulated output value (MV) in the direction of decreasing
control deviation, then PID parameters (P, I, D) are calculated and set automatically
based on the response obtained. As a result, the offset is reduced.

■ Batch Control Combining a Self-Tuning PID Controller Block (PID-STC)
Block (PID-STC) for batch control:
Additional
Temperature raw material
input Batch end
SV
PV
Time
STC stop STC stop
D011336E.EPS
Figure Batch Control
During PID control, simple batch processes are subject to large disturbances beyond the
correctable range through feedback control, as a result of additional charging of raw materi-
als or discharging of products in large quantities. In such cases, use the STC start and stop
functions to build a sequence control process where STC actions stop temporarily when
disturbances occur.
If the process is left unattended after batch end, with the setpoint value (SV) maintained at
a constant level in the automatic (AUT) mode, stop the STC function to prevent any unnec-
essary action of the self-tuning function (STC function).
■ Controlling Interacting Loops Whose Interaction cannot be Eliminated

The following section shows the points to be noted when using Self-tuning PID controller
blocks (PID-STC) to control interacting loops whose interaction cannot be eliminated, by
using an example of pressure control and flowrate control interacting with each other:
PC FC
Pressure Flowrate
D011337E.EPS
Figure Controlling Interacting Loops Whose Interaction cannot be Eliminated
If interaction exists between pressure control and flowrate control, as shown in the figure
above, using the self-tuning function (STC function) in both control loops causes interacting
oscillation when their PID parameters (P, I, D) approach optimum values. In this case, turn
off the STC function of one Self-Tuning PID Controller Block (PID-STC) whose process
variable (PV) is allowed to change, and set larger values for the current effective propor-
tional band (PB) and current effective integral time (TI). (e.g.: PB=100 to 200 %, TI=30 to
80 seconds)
After this, use the STC function of the other Self-Tuning PID Controller Block (PID-STC)
only.

■ Controlling Interacting Loops whose Interaction can be Eliminated
Blocks (PID-STC) to control interacting loops whose interaction can be eliminated, by using
an example of temperature control in a distillation column:
T1
Distillation
column +
m1
TC
LL - 1
1
g21
-
g22
g12
-
g11
TC m2 LL - 2
2
+
T2
TC 1
PID controller
TC 2
D011338E.EPS
Figure Controlling Interacting Loops whose Interaction Can Be Eliminated
If interaction exists between the column top temperature and column bottom temperature
control segments of a distillation column process, first execute non-interacting control.
The method of non-interacting control is shown below:
In the figure, when the transmission function between the output mi and temperature Tj of
the controller TCi is gij. T1 and T2 will be represented as follows after non-interacting ele-
ments LL-1 and LL-2 are applied:
T1 = (g11-g12 • g21/g22) m1
T2 = (g22-g12 • g21/g11) m2
As a result, the process is divided into two control loops that are regulated based on T1 and
T2, respectively.
Configure STC after confirming the result of this non-interacting control.

■ Controlling a Loop Subject to Impulse Noise
When a Self-Tuning PID Controller Block (PID-STC) is used to control a loop subject to
impulse noise, the Self-Tuning PID Controller Block (PID-STC) estimates process charac-
teristics after removing the impulse noise. When noise generates frequently, set a noise
band (NB).
If impulse noise is generated frequently at intervals of TR/10 or shorter, consider using
filters to remove the noise.

<Toc> <Ind> <D1.14 Manual Loader Block (MLD)> D1-182
D1.14 Manual Loader Block (MLD)

Manual Loader Block (MLD) may be applied to output manipulated output value (MV)
to manually operate final control elements, such as control valves.
■ Manual Loader Block (MLD)

▼ Connection
Manual Loader Block (MLD) outputs manipulated output value (MV) set from operation and
monitoring function. When in tracking (TRK) mode, the tracking input signal received from
the TIN terminal is output as manipulated output value (MV).
The figure below shows a function block diagram of the Manual Loader Block (MLD):
TIN TSI
(TSW)
Output
MV OUT
processing
(MV, MV)
SUB
D011401E.EPS
Figure Function Block Diagram of Manual Loader Block (MLD)
terminals of the Manual Loader Block (MLD):
Table Connection Methods and Connected destinations of the I/O Terminals of Manual Loader
Block (MLD)
Tracking signal
TIN
input
D011402E.EPS

<Toc> <Ind> <D1.14 Manual Loader Block (MLD)> D1-183
■ Function of Manual Loader Block (MLD) ¡ £
The MLD block performs output processing and alarm processing.
The only processing timing available for the MLD block is a periodic startup. Selections
SEE ALSO
• For the types of output processing and alarm processing possible for the MLD block, see D1.1.3, “Input
Processing, Output Processing, and Alarm Processing Possible for Each Regulatory Control Block.”
■ Data Items - MLD

Table Data Items of Manual Loader Block (MLD)
Entry Permitted
or Not
D011403E.EPS

SEE ALSO
For a list of valid block modes of the MLD block, see D1.1.4, “Valid Block Modes for Each Regulatory
Control Block.”

<Toc> <Ind> <D1.15 Manual Loader Block with Input Indicator (MLD-PVI)> D1-184
D1.15 Manual Loader Block with Input Indicator

(MLD-PVI)
Manual Loader Block with Input Indicator (MLD-PVI) may output manipulated output
value while displaying the process variable (PV). It may be applied to manually
operate final control elements and observing the process variable (PV) at the same
time.
■ Manual Loader Block with Input Indicator (MLD-PVI)

▼ Connection
Manual Loader Block with Input Indicator (MLD-PVI) displays the value input from the IN
terminal as process variable (PV). It also outputs the value set from operation and monitor-
ing function as manipulated output value (MV). In tracking (TRK) mode, the block outputs
the tracking input signal received from the TIN terminal as manipulated output value (MV).
The figure below shows a function block diagram of the Manual Loader Block with Input
Indicator (MLD-PVI):
TIN TSI
(TSW)
Input Output
IN PV MV OUT
(PV, PV, MV, MV)
SUB
D011501E.EPS
Figure Function Block Diagram of Manual Loader Block with Input Indicator (MLD-PVI)
terminals of the Manual Loader Block with Input Indicator (MLD-PVI):
Block with Input Indicator (MLD-PVI)
Tracking signal
TIN
input
D011502E.EPS

■ Function of Manual Loader Block with Input Indicator (MLD-PVI) ¡ £
The MLD-PVI block performs input processing, output processing, and alarm processing.
The only processing timing available for the MLD-PVI block is a periodic startup. Selections
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the MLD-PVI

■ Data Items - MLD-PVI
Table Data Items of Manual Loader Block with Input Indicator (MLD-PVI)
Item or Not
MODE Block mode ----- O/S(MAN)
D011503E.EPS

SEE ALSO
For a list of valid block modes of the MLD block, see D1.1.4, “Valid Block Modes for Each Regulatory
Control Block.”

<Toc> <Ind> <D1.16 Manual Loader Block with Auto/Man SW (MLD-SW)> D1-187
D1.16 Manual Loader Block with Auto/Man SW

(MLD-SW)
Manual Loader Block with Auto/Man SW (MLD-SW) may be applied as the lowest
downstream block in the control loops that consist of multiple function blocks.
■ Manual Loader Block with Auto/Man SW (MLD-SW)

▼ MLD-SW AUT/CAS, Connection
The Manual Loader Block with Auto/Man SW (MLD-SW) selects the manipulated output
signals to be sent to final control elements, by switching between the output signal received
from a controller and its own manually manipulated output signal.
In the manual (MAN) mode, the Manual Loader Block with Auto/Man SW (MLD-SW)
outputs the value set from operation and monitoring function as manipulated output value
(MV) to operate the final control element. In the automatic (AUT) mode or cascade (CAS)
mode, it performs control computation processing to the value input from other function
block (CSV), and outputs the result as a manipulated output value (MV) while in the manual
mode (MAN) it outputs the MV set from the operation and monitoring function.
Whether to set the cascade (CAS) mode or automatic (AUT) block mode for outputting the
result obtained by control computation processing of the value input from other function
block, may be selected for each control station on the property setting box of the FCS:
• MLD-SW AUT/CAS: Check “CAS” or “AUT.”
The default is “AUT.”
The figure below shows the function block diagram of Manual Loader Block with Auto/Man
SW (MLD-SW)
SET TIN TSI INT
(TSW)
CSV
GAI • CSV+BIAS
SV
Range AUT (CAS) Output

MV OUT
adjustment processing
Control computation
MAN
processing
(MV, MV)
SUB D011601E.EPS
Figure Function Block Diagram of Manual Loader Block with Auto/Man SW (MLD-SW)

terminals of the Manual Loader Block with Auto/Man SW (MLD-SW):
Block with Auto/Man SW (MLD-SW)
SET Setting input
Tracking signal
TIN
input
D011602E.EPS

■ Function of Manual Loader Block with Auto/Man SW (MLD-SW) ¡ £
The MLD-SW block performs control computation processing, output processing, and
alarm processing.
The only processing timing available for the MLD-SW block is a periodic startup. Selections
SEE ALSO
• For the types of output processing and alarm processing possible for the MLD-SW block, see D1.1.3,
“Input Processing, Output Processing, and Alarm Processing Possible for Each Regulatory Control
Block.”
● Control Computation Processing of Manual Loader Block with Auto/Man

SW (MLD-SW)
The table below shows the control computation processing functions of the Manual Loader
Block with Auto/Man SW (MLD-SW):
Table Control Computation Processing Functions of Manual Loader Block with Auto/Man SW
(MLD-SW)
Performs computation processing to the cascade setpoint value (CSV) and obtains a
Automatic control output
setpoint value (SV). Then, performs range conversion to this SV and obtains a
computation
manipulated output value.
Control output action manipulated output value (MV). The control output actions available with this function
block are of “positional type” only.
Set the setpoint value (SV) which was converted to the cascade setpoint value (CSV)to the
Setpoint value pushback
CSU.
Performs inverse operation on the manipulated output value to obtain SV and CSV and
uses them as a setpoint value (SV) and cascade setpoint value (CSV), respectively.
Output pushback
Combining this function with output tracking prevents the manipulated output value (MV)
from changing abruptly when the mode is changed to automatic.
Obtains a BIAS value to balance the manipulated output value and cascade setpoint value,
and resets the bias term. Combining this function with output tracking prevents the
Bias tracking
manipulated output value (MV) from changing abruptly when the mode is changed to
automatic.
Causes the current manipulated output value (MV) to gradually approach the MV value
Setpoint value ramp
converted from the setpoint value. This prevents the manipulated output value (MV) from
action
changing abruptly when the mode is changed to automatic.
MAN fallback
D011603E.EPS

■ Automatic Control Output Computation
The automatic control output computation function converts the value set from other func-
tion blocks as a cascade setpoint value (CSV) to a manipulated output value (MV).
● Characteristics of Automatic Control Output Computation

The following computational expression is used in automatic control output:
The computation processing shown below is performed to the cascade setpoint value
(CSV) to obtain a setpoint value (SV):
SV=GAIN • CSV+BIAS
When the block mode is automatic (AUT) or cascade (CAS), a manipulated output value
(MV) is obtained by performing range conversion to the setpoint value (SV).
MSH-MSL
MV= • (SV-SSL)+MSL
SSH-SSL D011604E.EPS

SSH: SV scale high limit
SSL: SV scale low limit
● Set Parameters of Automatic Control Output Computation

The parameters of automatic control output computation:
• Gain (GAIN): Arbitrary data.
• Bias value (BIAS): Engineering unit data within the SV scale span range.
The default is 0.0.
● Setpoint range (SV)

▼ SV Range
Numerical values of seven digits or less, where the sign and decimal point occupy one digit
each.

The control output action converts the manipulated output change ( MV) of each control
period to an actual manipulated output value (MV).
The control output actions applied in Manual loader with Aut/Man SW (MLD-SW) is “posi-
tional type.” The manipulated output value (MV) is the value obtained from automatic
control output computation.

When output is clamped, the setpoint value (SV) is converted to and set as a cascade
setpoint value (CSV), using the following computational expression:
SV-BIAS
CSV=
GAIN D011605E.EPS
The setpoint value pushback action does not take place if GAIN is 0.

status.
The bumpless switching performed by the Manual Loader Block with Auto/Man SW (MLD-
SW) include the following types:
• Output pushback
• Bias tracking
• Setpoint value ramp action

● Output Pushback
The output pushback function calculates a setpoint value (SV) and cascade setpoint value
(CSV) from the manipulated output value (MV) when the block is in the manual (MAN) or
initialization manual (IMAN) mode, and put it to the setpoint value (SV) and cascade
setpoint value (CSV), respectively. Output pushback is used when an upstream block is
cascade connected to the Manual Loader Block with Auto/Man SW (MLD-SW), and the
upstream block is tracking to the MLD-SW. With the combination of the output pushback
and the output tracking function of the cascade connected upstream control block, the
manipulated output value (MV) of the cascade connected upstream block changes in
accordance with the manipulated output value (MV) of the Manual Loader Block with Auto/
Man SW (MLD-SW) when the cascade connection is open. This action allows to change
the block mode for the Manual Loader Block with Auto/Man SW (MLD-SW) from manual
(MAN) to automatic (AUT) bumplessly and without balancing.
The computational expressions of output pushback:
SSH-SSL
SV= • (MV-MSL)+SSL
SV-BIAS
CSV=
GAIN D011607E.EPS
The output pushback action takes place when the following settings are performed:
• “No” is set for bias tracking.
• A value other than “0” is set for GAIN.

The following figure shows an action example of output pushback:
A Manual Loader Block with output switch is cascade connected in the middle of this loop,
when the cascade connection is open the manipulated output value (MV) of the upstream
block is forced to be equal to the setpoint value (SV) of the downstream block in the same
cascade loop:
PV MV
CAS
PID (AUT) MAN
Output pushback
Output value tracking SV

MV
CAS
MLD-SW AUT/MAN
Output value tracking

SV
PV MV
PID
D011608E.EPS
Figure Output Pushback and Output Value Tracking when Cascade is Open
In the above action example, bumpless switching is realized by the following three func-
tions:
• Output value tracked by the upstream block in the cascade loop
• Output pushback by the Manual Loader Block with Auto/Man SW (MLD-SW)
• Output value tracks the downstream by the Manual Loader Block with Auto/Man SW
(MLD-SW)

● Bias Tracking
▼ Bias Tracking
The bias tracking function calculates a bias value (BIAS) that allows the manipulated output
value (MV) to agree with the MV value converted from the cascade setpoint value (CSV),
and replaces the current bias value (BIAS) with the calculated value. Bias tracking is used
when an upstream block cascade connected to the Manual Loader Block with Auto/Man
SW (MLD-SW) performances the output value tracking function. When cascade connection
is open, the upstream block’s MV does not only follow the changes of MV of the Manual
Loader Block with Auto/Man SW (MLD-SW) but also adds the bias of the Manual Loader
Block with Auto/Man SW (MLD-SW), so that the bump can be avoided when connection
switches back to cascade.
By using the bias tracking function, switching of the block mode from manual (MAN) to
automatic (AUT) can be performed bumplessly.
The computational expressions of bias tracking:
SSH-SSL
SV= • (MV-MSL)+SSL
MSH-MSL
D011609E.EPS
BIAS=SV-GAIN • CSV
Use the Function Block Detail Builder to define bias tracking.

• Bias Tracking: Select “Yes” or “No.”
If “Yes” is defined for bias tracking, the output pushback and setpoint value ramp actions
will not be performed. If “No” is defined for bias tracking, these two actions will take place.
However, the setpoint value ramp action is not performed if the ramp constant (RP) set
parameter remains at its default value.
When the upstream function block in cascade connection is a Cascade Signal Distributor
Block (FOUT), define “Yes” for bias tracking. This activates the bias tracking action even
when the Cascade Signal Distributor Block (FOUT) has multiple output connected destina-
tions and the Manual Loader Block with Auto/Man SW (MLD-SW) in cascade is closed
when connected to the second output destination or thereafter.

● Setpoint Value Ramp Action
The setpoint value ramp action causes the current manipulated output value (MV) to
gradually approach the manipulated output value (MV) converted from the setpoint value
(SV). This function is used when a upstream block cascade connected to the Manual
Loader Block with Auto/Man SW (MLD-SW) is not defined the output tracking function.
The setpoint value ramp action takes place when the following two block mode changes
are performed:
• The block mode changes from manual (MAN) to an automatic (AUT or CAS) mode.
• The initialization manual (IMAN) mode is canceled while the block is still in an auto-
matic (AUT or CAS) mode.
The setpoint value ramp action causes the current manipulated output value (MV) to
approach the manipulated output value (MV) converted from the setpoint value (SV), by
limiting the change per-scan period in the setpoint value (SV) that is used to calculate a
manipulated output value (MV) (effective setpoint value) to equivalent to or less than the
ramp constant (RP), when the setpoint value (SV) changes as a result of the above two
block mode changes.
The following example shows the action of the setpoint value ramp:
Ramp constant (RP)

SV
Effective setpoint value
Scan period
Time
D011610.EPS
Figure Action Example of the Setpoint Value Ramp
The setpoint value ramp action takes place only when “No” is defined for the bias tracking.
The parameter of the setpoint value ramp action:
Engineering unit data between 0 and the SV scale span range limit.
The default is the SV scale span.
The setpoint value ramp action enables bumpless switching of the cascade status from
open to close, even when the upstream block in cascade connection does not have the
output tracking function and the bias tracking action of the Manual Loader Block with output
switch is disabled.


when the initialization manual condition is established, and changes the block mode of the
function block to initialization manual (IMAN).
When output value tracking is set to “Yes” with the Function Block Detail Builder, the ma-
nipulated output value (MV) is tracked to the value of the connection destination when
initialization manual goes into effect. Because of this, even if the mode is changed to the
manual (MAN) mode during initialization manual (IMAN) mode, the initialization manual
(IMAN) mode takes priority and the operation to change to the manual (MAN) mode be-
comes invalid.
The block returns to the original mode when the initialization manual condition vanishes.
However, if try to change block mode in the initialization manual (IMAN) mode, the block
only change to that mode when the initialization condition vanishes.

The initialization manual condition is a block mode transition condition that suspends the
tion manual (IMAN). The initialization manual (IMAN) block mode becomes active only
when the initialization manual condition is established.
The following example shows when the initialization manual condition establishes and
vanishes:
AUT
? Initialization manual condition establishes
IMAN (AUT)
AUT

conditional (CND) (i.e., the cascade loop open).
(SW-33, SW-91) and the cascade connection is switched off (i.e., the cascade loop
open).
• When the manipulated output value (MV) connected destination is a process output-,
and a failure or output open alarm has occurred in the module.
• When the data status of the input signal at the TIN or TSI terminals becomes invalid

■ MAN Fallback
The MAN fallback is an error processing function that stops the control and forces the
function block to enter manual operation state. This action takes place when the MAN
fallback condition is established.
● Characteristics of the MAN Fallback

regardless of the current operation status, and forces the function block to enter manual
operation state.
Once the MAN fallback condition is established, the block mode remains manual (MAN)
even when the condition later vanishes.

The following example shows when the MAN fallback condition is established:
AUTAMAN
IMAN (AUT)AIMAN (MAN)

• When the manipulated output value (MV) is connected to a process I/O module and
the FCS is having an initial cold start.
• When the manipulated output value (MV) is connected to a process I/O module, and
one of the I/O points connected to the module is undergoing maintenance load.


• Any block mode change command to make the function block into automatic opera-
tion state (AUT or CAS mode) become invalid.


■ Data Items - MLD-SW
Table Data Items of Manual Loader Block with Auto/Man SW (MLD-SW)
Item or Not
AF Alarm detection specificaton ----- 0
SV Setpoint value SV engineering unit value SSL
CSV Cascade setpoint value Value in the same engineering unit as SV SSL
ML Mnipulated variable low - limit setpoint MSL to MSH MSL
GAIN Gain ----- 1.000
BIAS Bias (SSH - SSL) 0.0
RP Ramp consistant 0 to (SSH - SSL) SSH to SSL
PSW Preset MV swich 0, 1, 2, 3 0
D011611E.EPS

SEE ALSO
For a list of valid block modes of the MLD-SW block, see D1.1.4, “Valid Block Modes for Each Regulatory
Control Block.”

<Toc> <Ind> <D1.17 Motor Control Blocks (MC-2, MC-3)> D1-201
D1.17 Motor Control Blocks (MC-2, MC-3)

The Motor Control Blocks MC-2 and MC-3 are applied to operate motor-driven
pumps and motor-operated valves. These blocks may be used to start or stop mo-
tors from operation and monitoring functions or to control them automatically.
There are two models of Motor Control Block (MC-2, MC-3), which behaves in differ-
ent output manner.
• Two-Position Motor Control Block (MC-2)
• Three-Position Motor Control Block (MC-3)
■ Motor Control Blocks (MC-2, MC-3)

▼ Connection
The motor control blocks MC-2 and MC-3 are provided with function to operate motor-
driven pumps and motor-operated valves.
The motor control blocks (MC-2, MC-3) enable starting and stopping of motors from opera-
tion and monitoring functions. Also, combining the motor control blocks (MC-2, MC-3) with
the sequence control function to realize the automatic control on motors.
The figure below shows the function block diagram of the motor control blocks (MC-2, MC-
3):
SV CSV RMV
TT FV
Input Answerback Output

IN PV MV OUT
processing check function processing
FB
(BPSW)
SWI INT IL TSI

D011701E.EPS
Figure Function Block Diagram of the Motor Control Blocks (MC-2, MC-3)

terminals of the Motor Control Blocks (MC-2, MC-3):
Table Connection Methods and Connected destinations of the I/O Terminals of Motor Control
Blocks (MC-2, MC-3)
IN Answerback input
Feedback signal
FB
input
Thermal trip signal
TT
input
Operation interlock
IL
input
Bypass command
SWI
SW input
D011702E.EPS

■ Functions of Motor Control Blocks (MC-2, MC-3)
The MC-2 and MC-3 blocks perform input processing, control computation processing,
output processing, and alarm processing.
The only processing timing available for the MC-2 and MC-3 blocks is a periodic startup.
Moreover, only the basic scan period can be selected as the scan period to execute the
periodic startup.
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the MC-2 and
MC-3 blocks, see a chapter D1.1.3, “Input Processing, Output Processing, and Alarm Processing Pos-
sible for Each Regulatory Control Block.”
• For details on the input processing, see a chapter C3, “Input Processing.”
● Input Processing Specific to Motor Control Blocks (MC-2, MC-3)

The MC-2 and MC-3 blocks perform special input signal conversions.
● Control Computation Processing of the Motor Control Blocks

(MC-2, MC-3)
The table below shows the control computation processing functions of the Motor Control
Blocks (MC-2, MC-3):
Table Control Computation Processing Functions of the Motor Control Blocks (MC-2, MC-3)
Compares the answerback input value (PV) with manipulated output value (MV) and
Answerback check checks if the final control element is operating in accordance with the output signals from
the motor control block.
MAN fallback
Computer failure
in the ROUT mode. This action takes place when the computer failure condition becomes
satisfied.
Starts sequentially and at specific intervals the multiple motor control blocks (MC-2, MC-
Serial start 3) belonging to the same group within the same control station , when start requests are
issued to these blocks simultaneously.
Counts the number of times the manipulated output value (MV) has changed from “0” to
Start count
“2” or from “1” to “2,” and uses the obtained value as the number of starts (OCNT).
Totalizes the periods of time during which the manipulated output value (MV) remains at
Operating time
“1” or “2,” and uses the obtained value as the operating time (ONTM).
Outputs a status change message when block mode is changed or when a specific block
Status change message
status is changed.
Simulation function Simulates the internal processing actions of the motor control blocks (MC-2, MC-3) .
Bypasses actions in accordance with the condition specified by the bypass command
Bypass command switch
switch.
D011703E.EPS

● Output Processing Specific to Motor Control Blocks (MC-2, MC-3)
The MC-2 and MC-3 blocks perform output processing that is different from the output
processing performed by other function blocks. The following lists the output processing
items specific to the MC-2 and MC-3 blocks.
• Setting method of manipulated output value (MV)
• Output signal conversion
• Inching output
• Remote/local input function
• Answerback tracking function
• Interlock check function
• Off-service function
● Alarm Processing Specific to Motor Control Blocks (MC-2, MC-3)

The following lists the alarm checks performed by the MC-2 and MC-3 blocks which are
specific to these two function blocks.
• Feedback input high and low limit alarm check
• Answerback unset alarm check
• Answerback error alarm check

■ Data Items - MC-2, MC-3
Table Data Items of Motor Control Blocks (MC-2, MC-3) (1/2)
Entry Permitted
or Not
BSTS Block status ----- NR
PV Answerback input value (*1) 0 to 2 0
FV Feedback input value FV engineering unit value SL
SV Inching output setpoint value 0 to 100 % 0%
CSV Sequence setpoint value 0, 1, 2 0
MV Manipulated output value (*2) 0, 1, 2 0
RMV Remote manipulated output value 0, 1, 2 0
RAW Answerback raw signal 0, 1, 2 0
ONCT Number of starts 0 to 99999999 0
ONTM Operating time count 0 to 99999999 seconds 0 second
ONTH Operating time hour unit 0 to 99999999 hours 0 hour
ONTS Operating time second unit 0 to 3599 seconds 0 second
D011707E.EPS

SEE ALSO
For a list of valid block modes of the MC-2 and MC-3 blocks, see a chapter D1.1.4, “Valid Block Modes for

Table Data Items of Motor Control Blocks (MC-2, MC-3) (2/2)
Item or Not
PH Feedback input high - limit alarm setpoint SL to SH SH
PL Feedback input low - limit alarm setpoint SL to SH SL
ANSP Answerback setpoint SL to SH SL
MTM Answerback check masking time 0 to 10,000 seconds 0 seconds
SVH Setpoint high limit 0 to 100 % 100 %
SVL Setpoint low limit 0 to 100 % 0%
BPSW Bypass command switch 0, 1, 2, 3, 4 0
SIMM Simulation switch 0, 1 0
SH FV scale high limit Value in the same engineering unit as FV -----
SL FV scale low limit Value in the same engineering unit as FV -----
D011708E.EPS

FV: Feedback input value
■ Block Status of Motor Control Blocks (MC-2, MC-3)

Table Block Status of Motor Control Blocks (MC-2, MC-3)
Block Status
Level Description
Symbol Name
3 ANCK Answer - Back Check Inhibition Answer - Back Check is inhibited
OFF Off Service Output is stopped
2
LOCK Interlock Forced to output a preset value.
SIM Simulation Stops output but simulates the output actions.
1
NR Normal Normal status
D011709E.EPS

D1.17.1 Input Processing of Motor Control Block (MC-2, MC-3)

Input signals specific to the Motor Control Blocks (MC-2, MC-3) include feedback
input signal and answerback input signal. “Input Signal Conversion of Feedback
Input,” “Input Signal Conversion of Answerback Input” and “Input Signal Conver-
sion of Feedback Input Value into Answerback Input Value” are provided for conver-
sion of these signals. “FV Overshoot” is an input processing of motor control blocks
(MC-2, MC-3).
SEE ALSO
For the FV overshoot, see a chapter C3.4, “PV/FV/CPV Overshoot.”
■ Input Signal of Motor Control Block (MC-2, MC-3)

Input signals specific to the Motor Control Blocks (MC-2, MC-3) are shown as follows.
● Feedback Input Signal

Feedback input signal is used when the feedback terminal (FB) in the MC-2 or MC-3 block
is connected to analog input modules or other function blocks. The feedback signal often
indicates the connected filed equipment status such as the openness of a motor-operated
valve.
● Answerback Input Signal

Answerback input signal is used when the IN terminal in the MC-2 or MC-3 block is con-
nected to a contact input or other internal status switch. The answerback signal often
indicate the state of onsite equipment such as the open/close status of motor-operated
valve or the start/stop status of pump operation.
● Input Signal Conversion Specific to Motor Control Block (MC-2, MC-3)

The MC-2 or MC-3 block uses a special input signal conversion corresponding to the
feedback input signal and answerback input signal.
• Input Signal Conversion of Feedback Input
• Input Signal Conversion of Answerback Input
• Input Signal Conversion of Feedback Input Value into Answerback Input Value

■ Input Signal Conversion of Feedback Input
▼ Feedback Low-Input Cutoff
Feedback value (FV) is the signal that the feedback terminal FB received from its connec-
tion destination without conversion. However, if the value from FB is equal to or less than
the low-input cutoff value, the feedback value (FV) is set to 0.
Input signal conversion setting parameters for the feedback input signal are given below.
• FV scale high limit (SH): Set FV engineering unit data.
• FV scale low limit (SL): Set FV engineering unit data.
Also, the setup for feedback low-input cutoff can be executed on the Function Block Detail
Builder.
• Feedback Low-input Cutoff: Set FV engineering unit data.
■ Input Signal Conversion of Answerback Input

The answerback input value (PV) is the answerback input signal read from the IN terminal’s
connection destination, such as a connected contact input or other internal status switch
then converted into the code value.
● Number of Answerback Input Points

There are two kinds of answerback input signal conversion methods. The number of
answerback input points is determined depending on the type of conversion.
• 2-Status Input (answerback=1 point)
• 3-Status Input (answerback=2 points)
The selection of input signal conversion type may be performed on the Function Block
Detail Builder.
• Input signal conversion type: Set “2-Status Input” or “3-Status Input.”
The default setting is “2-Status Input.”
● Direction of Answerback
Direction of answerback specify the meaning of ON/OFF, status of answerback input
signal, which reflect the final control element status if it operates properly according to the
manipulated output value (MV) from the MC-2 or MC-3 block.
The setup for direction of answerback may be performed on the Function Block Detail
Builder.
• Direction of Answerback:
Select “Direct,” “Reverse,” “Inverted connect direct action” or “Reversed connection
reverse action.”
The default setting is “Direct.”

● Conversion of Answerback Input Signal into Answerback Input Value (PV)
Either 0, 1 or 2 is set for the answerback input value in the function block depending on the
direction and contact status of answerback input signal. Connect the input n to the
answerback input signal indicating “open” and the input n+1 to the answerback input signal
indicating “close,” and vice versa for reversed connection.
The table below shows the correlation between the answerback input value (PV) and
contact status.
Table Determination of Answerback Input Signal
Number of Action of Contact status

answerback points answerback PV Alarm
n (*1) n+1 (*2)
ON - 2 -
Direct
OFF - 0 -
1
ON - 0 -
Reverse
OFF - 2 -
ON OFF 2 -
OFF OFF 1 -
Direct
OFF ON 0 -
ON ON Hold previous value (*3) PERR
ON OFF 0 -
OFF OFF Hold previous value (*3) PERR
Reverse
OFF ON 2 -
ON ON 1 -
2
OFF ON 2 -
Reversed OFF OFF 1 -
connection
direct action ON OFF 0 -
ON ON Hold previous value (*3) PERR
OFF ON 0 -
Reversed OFF OFF Hold previous value (*3) PERR
connection
reversed action ON OFF 2 -
ON ON 1 -
D011710E.EPS
*1: The n in the table indicates the element connected to the IN terminal (contact input or other internal switch). The
answerback input signal read from the element n represents the status of “open;” vise versa, when the connection is
reversed, the answerback input signal read from the element n represents the status of “close.”
*2: The n+1 in the table indicates the next element connected to the IN terminal. The answerback input signal read from
the element n+1 represents the status of “close;” vise versa, when the connection is reversed, the answerback input
signal read from the element n+1 represents the status of “open.”
*3: When both “open” and “close” answerback signals are true, an error will be initiated.
The data status of answerback input value (PV) becomes invalid (BAD) if both “open” and
“close” answerback input signals are true at the same time, or one of the connection
destinations to read answerback input signal is abnormal.
The input open alarm is activated if the status of answerback input value (PV) is invalid
(BAD) due to abnormal status at the connection destination. If the data value is invalid
(BAD) because both “open” and “close” answerback input signals are true at the same
time, the answerback undefined alarm (PERR) is activated.

■ Input Signal Conversion of Feedback Input Value into Answerback Input
Value
If the answerback input terminal has no connection while the feedback input terminal is in
connection, the answerback input value (PV) is set to one of the following values after
comparing the feedback input value (FV) with the answerback setpoint (ANSP).
• If FVANSP, PV=2
• If FV<ANSP, PV=0
The answerback setpoint (ANSP) is a data in the engineering unit that indicates the scale
range between feedback input value (FV), and can be updated as a setting parameter
while the system is running.
If the data status of feedback input value (FV) is invalid (BAD), the status of answerback
input value (PV) is set invalid (BAD) with the previous answerback input value (PV) latched.
If both the answerback input terminal and the feedback input terminal are in connection, the
answerback input precedes. The answerback input is converted into the answerback input
value (PV) through input signal conversion.
If neither the answerback input terminal nor the feedback input terminal are in connection,
the previous answerback input value (PV) is latched.
IMPORTANT
The answerback input signal conversion is not executed in the following states:
• When the block status is simulation (SIM).
• When the data status of answerback input value (PV) is calibration (CAL).
• When the answerback check bypass is activated.
(answerback check bypass command switch BPSW=1 or 3)
Even if the answerback input signal at the IN terminal connection destination is not properly
converted due to one of the above conditions, the data converted through the same
answerback input signal conversion (2- or 3-status conversion) as the answerback input
value (PV) are stored in the answerback raw signal input value.

D1.17.2 Control Computation Processing of Motor Control

Blocks (MC-2, MC-3)
This section describes the control computation processing functions of the MC-2
and MC-3 blocks, which are listed below.
• Answerback check
• Initialization manual
• MAN fallback
• Computer fail
• Block mode change interlock
• Serial start
• Start count
• Operating time
• Status change message
• Simulation function
• Bypass command switch (BPSW)

■ Answerback Check
The answerback check function checks if the final control elements are operating normally
in accordance with the output signals from the Motor control blocks (MC-2, MC-3). Unless
the manipulated output value (MV) is changed, the answerback input value (PV) and
manipulated output values (MV) are constantly compared. If the two do not agree with each
other, an alarm is generated.
The following types of alarms are generated:
• Positive answerback error alarm (ANS+)
Generated when the manipulated output value (MV) is “2” and the answerback input
value (PV) is not “2”.
• Negative answerback error alarm (ANS-)
Generated when the manipulated output value (MV) is “0” and the answerback input
value (PV) is not “0”.
While the answerback error alarm exists, if the answerback input value (PV) and manipu-
lated output value (MV) becomes equal or the manipulated output value (MV) changes
back, the answerback error alarm (ANS+ or ANS-) vanishes.
After the manipulated output value (MV) changes, it takes some time for the final control
elements to complete action. Therefore, the answerback check masking time (MTM) is
introduced after the manipulated output value (MV) changes. During this mask time, even
when the answerback input value (PV) and manipulated output value (MV) do not agree,
the answerback check does not initiate alarm.
When the manipulated output value (MV) changes, the block status changes to
answerback (ANCK), indicating that the answerback check is in progress. The answerback
check (ANCK) block status is canceled when the answerback input value (PV) comes to
meet the manipulated output value (MV). When the answerback input value (PV) does not
come to meet the manipulated output value (MV) within the answerback check masking
time (MTM), the answerback check (ANCK) block status is canceled too.
The answerback check function stops in the following conditions:

• When the block status is simulation (SIM).
• When the block mode is tracking (TRK).
• When answerback bypass is specified (BPSW=1 or 3).
• When the manipulated output value (MV) is “1.”
• When the data status of the answerback input value (PV) is calibration (CAL).
• When out of service (BPSW=4) is specified.
In the initialization manual (IMAN) mode, the answerback check masking timer behaves as
if the masking time has already elapsed, and the Motor control blocks (MC-2, MC-3) main-
tain their alarm status.

● Define the Answerback Check
▼ Answerback Check
Select the answerback check monitoring action from the following three types:
• Positive monitoring
Starts the answerback check masking timer at the start of output (OFFAON). If the
answerback input value (PV) still disagrees with manipulated output value (MV) after
the answerback check masking time has elapsed, an alarm is generated. If output is
OFF, no alarm will be generated even when the answerback input value (PV) does not
agree with manipulated output value (MV).
• Negative monitoring
Starts the answerback check masking timer at the end of output (ONAOFF). If the
the answerback check masking time has elapsed, an alarm is generated. If output is
ON, no alarm will be generated even when the answerback input value (PV) does not
agree with manipulated output value (MV).
• Both-side monitoring
Starts the answerback check masking timer at the start and end of output. If the
the answerback check masking time elapsed, an alarm is generated.
Use the Function Block Detail Builder to define the answerback check.
• Answerback Check: Select “No,” “Both Sides,” “Open,”
“Close.”

● Answerback Bypass
The answerback bypass function forces the answerback input value (PV) to be equal to the
manipulated output value (MV) and stops the answerback check. The answerback bypass
function is activated when the bypass command switch (BPSW) is 1 or 3.
● Set Parameters of the Answerback Check

The parameters of the answerback check:
• Answerback checks masking time (MTM):0 to 10000 seconds.
The default is 4 seconds.
• Bypass command switch (BPSW): Select 0, 1, 3 or 4. The default is 0.
SEE ALSO
For the bypass command switch (BPSW), see a section “■ Bypass Command Switch (BPSW).”
TIP
Even when the serial start is specified, changing the manipulated output value (MV) triggers a transition
to the answerback check (ANCK) status.


The initialization manual function suspends the control output action temporarily during
operation when the initialization manual condition is established, and changes the block
mode of the function block to initialization manual (IMAN).

tion manual (IMAN).
The following example shows when the initialization manual condition establishes or
vanishes:
AUT
IMAN (AUT)
AUT
The initialization manual condition establishes in the following situation:

(SW-33, SW-91) and the connection is switched off.
• When the manipulated output value (MV) connected destination is a process output
module, and a failure or output open alarm has occurred in the module.

■ MAN Fallback

operation state.

AUTAMAN

• When the data status of the answerback input value (PV) is calibration (CAL).
• When the answerback abnormality designated on the builder item [Fallback operation
on the abnormal answerback] occurs.
• When the manipulated output data status becomes PTPF.
• When the switch connected to INT terminal is turned ON (i.e., the interlock condition is
established for changing the block into interlock mode).

■ Computer Fail
output (ROUT) mode temporarily and switches to the computer backup mode.

When the function block mode is remote output (ROUT), the function block receives the
manipulated output value (MV) from a supervisory system computer via control bus com-
munication.
change.
The following section is an action flow of the function block from the time the computer fail
condition establishes till it vanishes.
1. When a block mode change command from MAN, AUT or CAS to ROUT is sent while
the computer fails (BSW=ON), the function block does not switch to the computer
backup mode directly but switches to the transient state mode first.
before the execution of the block mode change command (MAN, AUT, CAS) and a
remote mode (ROUT).
(ROUT).
block mode changes to remote output (ROUT).

the remote output (ROUT) mode and switches the mode to the computer backup mode.
A backup switch (BSW) is provided in function block to define the remote output (ROUT)
mode. The status of this switch determines whether the computer has failed or recovered.
The value of the backup switch (BSW) can be set from a sequence table or other function
blocks.
on a block mode other than remote output (ROUT).
• When the backup switch BSW=ON, computer has failed
• When the backup switch BSW=OFF, computer has recovered
An example when the automatic (AUT) mode has been specified for the computer backup
ROUT
? Computer fails
AUT (ROUT)
? Computer recovers
ROUT
AUT
? ROUT command
● Define Computer Backup Mode

Use the Function Block Detail Builder to set the computer backup mode for each function
block.
becomes down.
The default is “MAN.”


• Any block mode change command to obtain an automatic operation state (AUT, CAS,
or ROUT mode) becomes invalid.

The block mode change interlock condition is established when the switch at the connected
destination of the interlock switch input terminal (INT) is turned ON as a result of continued
automatic operation becoming impossible due to an abnormality in the plant, etc.
■ Serial Start
▼ Serial Startup Group, MC Block – Serial Startup Interval
The serial start function put the Motor control blocks (MC-2, MC-3) in the same control
station into groups and starts multiple Motor control blocks (MC-2, MC-3) in the same
group sequentially at a specified interval when start requests are issued to these blocks
simultaneously.
Serial start is executed when the manipulated output value (MV) changes to execute the
positive action. For example, serial start takes place if the manipulated output value (MV)
changes from 0 to 2 but not when it changes from 2 to 0.
After start requests have been issued, the Motor control blocks (MC-2, MC-3) that are
waiting for serial start will remain in the state of “not performing output although the manipu-
lated output value is changing.” When this occurs, the answerback check masking time is
extended by the time for which the blocks waiting for serial start.
Use the Function Block Detail Builder and system view to define serial start.
• Serial Startup Group:
Specify a value between 0 and 7.
The default is 0.
Set the value in the Function Block Detail Builder.
Serial start is executed to the group whose group number is 0.
• Serial start interval:
Specify a value between 0 and 9999 seconds.
The default is 0.
Specification defined in the system view valid for whole control station.

■ Start Count
Counts the number of times the manipulated output value (MV) has changed from 0 or 1 to
2, and uses the obtained value as the number of starts (ONCT).
The ONCT count increases from 0 to 99999999 and upon reaching 99999999, returns to 0
with the next count. The number of starts (ONCT) will not be initialized automatically, even
during initial cold start. However, the number of starts (ONCT) is initialized when an arbi-
trary ONCT value is set. The number of starts (ONCT) can be initialized at any time as
necessary.
The number of starts (ONCT) is not counted in the simulation mode (SIM) or during inching
output operation.
■ Operating Time
Totalizes the periods of time during which the manipulated output value remained at 1 or 2,
and stores the obtained value in the operating time (ONTM). The operating time (ONTM) is
indicated in seconds.
The operating time (ONTM) value is totalized from 0 to 99999999, and upon reaching
99999999, returns to 0 with the next count.
The values representing the hour and second digits of the operating time are stored in the
operating time hour unit (ONTH) and operating time second unit (ONTS), respectively. The
operating time hour unit (ONTH) and operating time second unit (ONTS) are constantly
updated in accordance with changes in the operating time (ONTM).
The operating time (ONTM) will not be initialized automatically, even during initial cold start.
However, if an arbitrary value is set for the operating time (ONTM), the operating time
(ONTM) is initialized by that value. The operating time (ONTM) can be initialized at any
time as necessary.
The operating time (ONTM) is not updated in the simulation mode (SIM) or during inching
output operation.
■ Status Change Message

The Motor control blocks (MC-2, MC-3) issue a status change message when changes
occur in the block mode or status. The statuses for which a status change message is
issued are “OFF” and “LOCK.”
When the block status changes from “OFF” or “LOCK,” a status change message is issued.

■ Simulation Function
The simulation function simulates the internal processing actions of the Motor control
blocks (MC-2, MC-3). This function is used when testing the operation of devices using
Motor control blocks (MC-2, MC-3).
● Setting and Canceling the Simulation Mode

The following section explains how to set and cancel the simulation mode:
• Setting the simulation mode
When the simulation switch (SIMM) is set to ON (=1), the simulation mode becomes
active. The simulation mode is indicated by the block status, “SIM.”
• Canceling the simulation mode
When the simulation switch (SIMM) is set to OFF (=1), the simulation mode is can-
celed and the block returns to a normal state.

The table below shows actions of the motor control block (MC-2, MC-3) functions in the
simulation mode:
Table Actions of Motor Control Block (MC-2, MC-3) Functions in the Simulation Mode
Function Action
Block mode Same as in a normal state, except IMAN.
Block status SIM
Alarm status No alarm is generated.
Answerback input Only takes in values for RAW.
Feedback input Only takes in values.
Thermal trip check No action.
• The check and alarm actions do not stop.
• When the answerback check specification is set to “enable,” the MV value is set
Answerback check as the PV value after the answerback check masking time elapses (*1).
• When the answerback check specification is “disabled,” the MV value is set as
the PV value immediately.
Calibration function
Same as in a normal state.
Remote/local input
Answerback tracking
No action.
Interlock check
• The output action stops, but the MV action continues as normal.
Output signal conversion • In the status type output, the current status of the output destinations is retained.
• In the pulsive type output, the status of all output destinations changes to OFF.
Inching output The output action stops, but the MV and SV actions continue as normal.
Serial start
Start count No action.
Operating time
Status change message Same as in a normal state.
D011704E.EPS
*1: If turns ON the simulation mode when the answerback alarm is present, the manipulated output value (MV) is set to be
equal to the answerback input value (PV) immediately.
SEE ALSO
For the thermal trip check, see a chapter D1.17.4, “Alarm Processing of Motor Control Blocks (MC-2 and
MC-3).”

● Actions after Cancellation of the Simulation Mode
The following actions take place in the first scan period after the simulation mode is can-
celed:
• Status output type
The contact status of the output destination is read back and set as the manipulated
output value (MV).
• Pulsive output type
When “Yes” is set for the answerback tracking function, the answerback input value
(PV) is set as the manipulated output value (MV). This processing is not performed
while the answerback bypass function is active.
The above actions take place commonly when the output status changes from stop to start,
regardless the cancellation of simulation mode.

■ Bypass Command Switch (BPSW)
The bypass command switch is used to stop the answerback check function, interlock
check functions, or output actions.
The table below shows the commands and actions of the bypass command switch (BPSW)
corresponding to different switch positions (0 to 4):
Table Commands and Actions of the Bypass Command Switch (BPSW) Corresponding to
Different Switch Positions (0 to 4)
BPSW Command Action
0 No bypass Normal actions.
1 Answerback bypass The answerback bypass action is executed.
2 Interlock bypass The interlock action is stopped.
Answerback The answerback bypass action is executed.
3
+interlock bypasses The interlock action is stopped.
Block mode=MAN
4 Out of service Block status=OFF
The answerback tracking action is executed.
D011705E.EPS
The “out of service” corresponding the switch position 4 instructs the Motor control block
(MC-2, MC-3) to stop the output action.
The value of the bypass command switch (BPSW) is set by the input signal from the
bypass command switch input terminal (SWI). If the SWI terminal is not connected, the
value is set directly from operation and monitoring functions or other function block.

The table below summarizes various types of bypasses that are explained in the sections
of corresponding functions:
Table Table of Function Bypasses
Mode Block status PBSW
Function PV.CAL
TRK IMAN OFF LOCK SIM =1.3
Feedback input
Answerback input
Thermal trip check
Answerback check
Answerback bypass action (MVAPV) - - - -
Answerback tracking action (*1)
- - - -
(PVAMV)
Interlock check (*4)
Signal output (*2) (*3)
D011706E.EPS
: Bypass unless other condition denoted by “X” exist

Blank: Not Bypass
-: Irrelevant
*1: The answerback tracking is not active when the “answerback tracking specification” is “No.”
*2: If the signal output status changes from “enable” to “disable” while pulsive output is in progress, the output action will
not stop after specified pulse-width signals are outputted. If the change occurs during inching processing, the output
action does not continue to finish the inching processing. However, no further inching operation request is accepted.
*3: Same as during status output while the answerback tracking action is active.
*4: If BPSW=3, the interlock check is not active.

D1.17.3 Output Processing of Motor Control Blocks (MC-2 and

MC-3)
The Motor Control Block (MC-2 and MC-3) executes special output processing
different from other function blocks.
This section describes the output processing specific to Motor Control Blocks (MC-
2 and MC-3).
• Set manipulated output value MV
• Output Signal Conversion
• Inching Output
• Remote/Local Input
• Answerback Tracking
• Interlock Check
• Off-service

■ Set the Manipulated Output Value (MV) of Motor Control Blocks
(MC-2 and MC-3)
The setting method of the manipulated output value (MV), which is the target of the output
processing, varies depending on the block mode in the Motor Control Blocks (MC-2, MC-
3).
● In the Manual Mode (CRT Manual)

When the block mode is manual (MAN) mode (CRT manual), the manipulated output value
(MV) is set by the following method.
• The manipulated output value (MV) is set by the operator’s operation on the operation
and monitoring function.
• For the inching output, the manipulated output value (MV) is automatically set based
on the setpoint value (SV) set by the operator on the operation and monitoring func-
tion.
● In the Automatic Mode (Sequence Automatic 1) or Cascade Mode

(Sequence Automatic 2)
When the block mode is in the automatic (AUT) mode (sequence automatic 1) or cascade
(CAS) mode (sequence automatic 2), the sequence setpoint value (CSV) set by another
function block such as a Sequence Control Block or Calculation Block is set as the manipu-
● In the Remote Output Mode (Computer Remote)

When the block mode is in the remote output (ROUT) mode (computer remote), a remote
manipulated output value (RSV) set by an upper-level computer is set as the manipulated
output value (MV).
When the block mode is neither remote output (ROUT) or out of service (O/S) , a tracking is
executed so that the remote setpoint value (RSV) becomes the manipulated output value
(MV).
● In the Tracking Mode (On-Site Manual)

When the block mode is in the tracking (TRK) mode (on-site manual), the manipulated
output value (MV) is set by the following method:
• When the answer back tracking is set to “YES,” the answer back input value (PV) is
set as the manipulated output value (MV).
• When the answer back tracking is “NO,” if the output signal conversion is “2-position
status output” or “3-position status output,” the status of the output destination (contact
output or internal switch) is read back and the value after the reverse-conversion of
the output signal is set as the manipulated output value (MV).
If the output signal conversion is “2-position pulsive output” or “3-position pulsive
output,” the previous value is retained as the manipulated output value (MV).

■ Output Signal Conversion of Motor Control Blocks (MC-2 and MC-3)
The motor control block (MC-2 and MC-3) executes the following output processing.
Table Output Processing of the Motor Control Block (MC-2 and MC-3)
Output signal conversion Number of output Output action direction
specification contacts specification
2-position status output 1 Yes
3-position status output 2 Yes
2-position pulsive output 2 No
3-position pulsive output 3 No
D011710E.EPS
The output signal conversion types and output action directions are described.
● Output Signal Conversion Types

The type of output signal conversion can be set with the Function Block Detail Builder.
• Output Signal Conversion:
For a 2-Position Motor Control Block (MC-2), select from “2-position Status Output”
and
“2-position Pulsive Output.”
Default is “2-position Status Output.”
For a 3-Position Motor Control Block (MC-3), select from “3-position Status Output”
and “3-position Pulsive Output.”
Default is “3-position Status Output.”
● Output Action Directions

When “2-position Status Output” or “3-position Status Output” is specified, the “Output
Action Direction” can be defined too.
The output action direction can be set with the Function Block Detail Builder.
• Output Action Direction:
Select from “Direct,” “Reverse” “Reversed connection direct action” and “Reversed
connection reversed action.”
Default is “Direct.”
SEE ALSO
See sections “■ Output Signal Conversion of 2-position Status Output” and “■ Output Signal Conversion
of 3-position Status Output” for information on the output action direction for the MC-2 and MC-3 blocks.

● Pulse Width Time
▼ MC Block - Pulse Width
The time of ON for contact output for the converted signal of “2-position Pulsive Output” or
“3-position Pulsive Output” may be defined in each FCS.
Pulse width may be defined in the property box of the FCS folder.
• Pulse Width: 1 to 100 Sec.
Default is 1 Sec.
SEE ALSO
For details on pulsive width of MC2 or MC3 blocks see a section “■ Output Signal Conversion of 2-
position Pulsive Output” or “■ Output Signal Conversion of 3-position Pulsive Output.”

■ Output Signal Conversion of 2-Position Status Output
The relationship between the manipulated output value (MV) and the ON/OFF status in the
2-position status output is as follows:
Table The Manipulated Output Value and the Contact Output Status of the 2-Position Status
Output
Output signal Output action Contact output status

MV
conversion specification direction n (*1) n+1 (*1) n+2 (*1)
2 ON
Direct action
2-position status 0 OFF
output 0 ON
Reverse action
2 OFF
D011711E.EPS
*1: “n” in the table indicates the element number specified to connect to OUT terminal. “n+1” and “n+2” indicates the
element number succeeding the element number “n” that is specified to connect to OUT terminal.
The action of 2-position status output is shown as follows:
0 2 0
MV
ON
Direct action Contact output status OFF OFF
(n)
ON ON
Reverse action Contact output status OFF
(n)
D011712E.EPS
Figure Action of the 2-Position Status Output
In the 2-position status output, the state of MV=1 is the same as the state of MV=2.

■ Output Signal Conversion of 3-Position Status Output
3-position status output is as follows:
Table The Manipulated Output Value and the Contact Output Status of the 3-Position Status
Output
Output signal Contact output status

Output action MV
conversion specification n (*1) n+1 (*1) n+2 (*1)
2 ON OFF _
Direct action 1 OFF OFF _
0 OFF ON _
2 OFF ON _
Reverse action 1 ON ON _
0 ON OFF _
3-position status
output 2 OFF ON _
Reversed
connection 1 OFF OFF _
Direct action _
0 ON OFF
2 ON OFF _
Reversed
connection 1 ON ON _
Reversed action _
0 OFF ON
D011713E.EPS
The action of 3-position status output is shown as follows:
0 1 2
MV
ON
Output status of contact 1 OFF
(n)
Direct ON
action
(n+1)
ON
(n)
Reversed ON
action
(n+1)
ON
Reversed
(n)
connection ON
Direct Action
(n+1)
ON
Reversed
(n)
connection ON
Reversed Action
(n+1)
D011714E.EPS
Figure Action of the 3-Position Status Output

■ Output Signal Conversion of the 2-Position Pulsive Output
2-position pulsive output is as follows:
Table The Manipulated Output Value and the Contact Output Status of the 2-Position Pulsive
Output

MV
2-position pulsive 2 ON OFF

output 0 OFF ON
D011715E.EPS
The action of an 2-position pulsive output is shown as follows:
0 2
MV
ON
Output status of contact 1 OFF OFF
(n)
ON
(n+1)
D011716E.EPS
Figure Action of the 2-Position Pulsive Output
For pulsive output signal, the time of ON is set in the column of “MC block pulse width” on
FCS folder. The default is 1 sec.

■ Output Signal Conversion of the 3-Position Pulsive Output
3-position pulsive output is as follows:
Table The Manipulated Output Value and the Contact Output Status of the 3-Position Pulsive
Output

MV
2 ON OFF OFF
3-position pulsive
1 OFF OFF ON
output
0 OFF ON OFF
D011717E.EPS
The action of an 3-position pulsive output is shown as follows:
0 1 2
MV
ON
(n)
ON
(n+1)
ON
(n+2)
D011718E.EPS
Figure Action of the 3-Position Pulsive Output
For pulsive output signal, the time of ON is set in the column of “MC block pulse width” on
FCS folder. The default is 1 sec.

■ Inching Output
▼ Inching/Full-Stroke Time Width
Inching output is a function which drives or stops the motor for a specified duration accord-
ing to the manual operation of the operator using the operation and monitoring function.
The inching output is initiated when change the inching output setpoint value (SV). The final
control element is manipulated for a duration (Tout) proportional to the change in SV (SV)
from 0, 50 or 100 % shown below.
After Tout has elapsed, the inching output setpoint value (SV) follows the manipulated
output value (MV) prior to the modification. The inching operation is available only in
manual (MAN) mode.
When the inching operation is not executed, the inching output setpoint value (SV) follows
the manipulated output value (MV).
Table The Relationship Between the Manipulated Output Value (MV) and the Inching Output
Setpoint Value (SV)
MV 0 1 2
SV 0% 50 % 100 %
D011719E.EPS
Tout can be obtained by the following expression:
| SV |
Tout=Tf •
100 D011720E.EPS
Tout: Inching output action time (second)

Tf: Inching full stroke time width (second)
SV: Change in SV (%) = SV value after change - SV value before change
The “Inching/Full-stroke Time Width” indicates the time span for the operation of the final
control element when the inching output setpoint value (SV) is changed by 100 %.
The inching/full-stroke time width is set by the Function Block Detail Builder.
• Inching/Full-stroke Time Width:
0 to 10000.0 seconds. For the pulsive output, however, the output within one second
is invalid.

■ Action of the Inching Output
The action of the inching output is explained for each type of the output signal conversion.
In the explanation, the full stroke time width is assumed to be 100 seconds.
In each output signal conversion, the inching operation is aborted when the setting of the
manipulated output value (MV) is modified during the operation.
● Inching Output of a 2-Position Status Output

The output reverses from ON to OFF, or from OFF to ON only during Tout time.
The inching output only reverses the contact output to the OUT terminal connection desti-
nation; the manipulated output value (MV) remains unchanged.
0 2
MV
0 10 0 100 90 100
SV %
ON 10 seconds
Contact 1 (direct action) Tout
OFF Tout
10 seconds
ON
Contact 1 (reverse action)
OFF
D011721E.EPS
Figure Inching Output of a 2-Position Status Output (When the Full Stroke Time Width is 100
Seconds)

● Inching Output of a 3-Position Status Output
• When MV=2, the output of the contact 1 is reversed for duration of Tout.
• When MV=0, the output of the contact 2 is reversed for duration of Tout.
• When MV=1, the output of the contact 1 is reversed for duration of Tout if the change
in inching output setpoint value (SV) is positive. The output of the contact 2 is re-
versed for duration of Tout if the inching output setpoint value (SV) is negative.
The inching output only reverses the contact output, the manipulated output value (MV)
remains unchanged.
0 1 2
MV
0 10 0 50 40 50 60 50 100 90 100
SV %
ON
Contact 1
OFF
Direct 10 seconds 10 seconds
action ON (Tout) (Tout)
Contact 2
OFF
10 seconds 10 seconds
(Tout) (Tout)
ON
Contact 1
OFF
Reverse
action ON
Contact 2
OFF
ON
Contact 1
Reversed OFF
Connection
Direct action ON
Contact 2
OFF
ON
Contact 1
Reversed OFF
Connection
Reversed action ON
Contact 2
OFF
D011722E.EPS
Figure Inching Output of a 3-Position Status Output (When the Full Stroke Time Width is 100
Seconds)

● Inching Output of a 2-Position Pulsive Output
• When MV=2, performs pulsive output from the contact 2, then performs again from
contact 1 after Tout has elapsed.
The inching output only executes the pulsive output from the contact and the manipulated
output value (MV) is not changed.
0 2
MV
0 10 0 100 90 100
SV %
ON
Contact 1 10 seconds 10 seconds
OFF
ON (Tout) (Tout)
Contact 2
OFF
D011723E.EPS
Figure Inching Output of a 2-Position Pulsive Output (When the Full Stroke Time Width is 100
Seconds)
● Inching Output of a 3-Position Pulsive Output

• When MV=1, if the sign for the change in inching output setpoint (SV) is positive,
pulsive output is performed from contact 1, then again from contact 3 after Tout has
elapsed.
If the sign for the change in inching output setpoint (SV) is negative, pulsive output is
performed from contact 2, then again from contact 3 after Tout has elapsed.
The inching output only executes the pulsive output from the contact and the manipulated
output value (MV) is not changed.
0 1 2
MV
0 10 0 50 40 50 60 50 100 90 100
SV %
Contact 1
10 10
seconds seconds
Contact 2
10
10 seconds
seconds
Contact 3
D011724E.EPS
Figure Inching Output of a 3-Position Pulsive Output (When the Full Stroke Time Width is 100
Seconds)

■ Remote/Local Input Function
The remote/local input function reads the status of on-site push button switches installed
near the equipment such as valves and pumps, and to prevent the output from the MC-2
and MC-3 block since the on-site operation is given higher priority when the system is in
the local mode.
The remote/local input signal is fed through the TSI terminal of the MC-2 and MC-3 block.
In addition to the contact input, internal switches can be used as signal input too. The
remote/local input signal is stored in the tracking switch (TSW).
Table Relationship Between the Remote/Local Input Signal and the Tracking Switch
Input signal (*1) Remote/Local TSW Mode
OFF (0) Remote 0 Mode except for TRK
ON (1) Local 1 TRK
D011725E.EPS
*1: Input signal in () indicates the signal from an internal switch.
When the TSI terminal is not connected, the data can be set directly to the tracking switch
(TSW) from other function blocks. When TSW is 1, the block mode is set to the on-site
manual mode (TRK). When TSW becomes 0, the mode returns to the normal mode (MAN,
AUT, CAS or ROUT) from the on-site manual (TRK) mode.
● Remote/Local Input Function in On-Site Manual (TRK) Mode

The action of the remote/local input function in the on-site manual (TRK) mode is as fol-
lows:
• The output action (output signal conversion) is not executed. But the output action is
carried out when the answer back tracking is defined in the status output.
• The interlock check is not performed.
• The answer back check is not performed because the answer back error alarm
(ANS+, ANS-) is reset.
■ Answerback Tracking Function

▼ Answerback Tracking
The answerback tracking function is a function to force the manipulated output value (MV)
to match the answerback input value (PV), when the block is in Filed-Manual (TRK) mode
or when the bypass command switch (BPSW) is 4 (out-of-service command).
The answerback tracking function is defined in the function block detail definition builder.
• Answerback Tracking: Select either “Yes” or “No.”

■ Answerback Error Triggered Fallback
▼ Fallback Operation on the Abnormal Answerback
Answerback Error Triggered Fallback is a function that forces the block into MAN mode and
forces the block's manipulated output (MV) into a designated value whenever answerback
signals indicate an error.
Triggers of Fallback may be selected from one of the three errors shown as below.
• Answerback error occurred due to abnormality of ON (ANS+) signal
• Answerback error occurred due to abnormality of OFF (ANS-) signal
• Answerback error occurred due to abnormality of either ON (ANS+) or OFF (ANS-)
signal.
When fallback is activated, the manipulated output (MV) will be forced to the output position
designated in the builder item [Output when interlock status is true]. At the same time, the
interlock alarm (INT) will be initiated right after the output (MV) changed to the designated
position.
Once the manipulated output (MV) is manually changed, the interlock alarm (INT) will be
deactivated.
SEE ALSO
• For details on interlock check functions, see later section “■ Interlock Check Function.”
• For details on interlock alarm (INT), see D1.17.4, “Alarm Processing of Motor Control Blocks (MC-2, MC-
3).”
If answerback check is not activated, the fallback will not be triggered by answerback error.
The interlock alarm (INT) subsequent to the fallback can be dissolved when any of the
following conditions establishes.
• When block mode changes to Tracking (TRK) mode.
• When answerback bypass is activated (BPSW=1 or 3).
• When the answerback input signal (PV) is switched to calibration (CAL) mode.
• When off service is activated (BPSW=4).
If the block is in simulation (SIM) status, the fallback will not be triggered by answerback
error. The interlock alarm (INT) subsequent to the fallback will be dissolved right after the
block changes simulation (SIM) status.

When a 2-position status output encounters the answerback error triggered fallback, its
behavior is shown in the following illustrate.
MAN fallback starts according

to the setting for fallback triggered
by the answerback error.
ANS+ initiated when MV is forced to the designated
answerback detects value for interlock and the
an error. interlock alarm (INT) occurs. When MV is manipulated,
the INT alarm will be dissolved.
2
MV
0
2
PV
0
Block
AUT MAN
mode
A
Block N
NR ANCK NR C NR
status
K
Alarm
NR INT NR
status
ANS+ When PV answers the corresponding MV,

the ANS+ alarm will be dissolved.
D011726E.EPS
Figure Answerback Error Triggered Fallback (2-Position Status Output)
When a 3-position status output encounters the answerback error triggered fallback, its
behavior is shown in the following illustrate.
MAN fallback starts according

to the setting for fallback triggered
by the answerback error.
ANS+ initiated when MV is forced to the designated
answerback detects value for interlock and the
an error. interlock alarm (INT) occurs. When MV is manipulated,
the INT alarm will be dissolved.
2
MV 1
0
MV=0, answerback becomes
2
normal, INT alarm continues.
PV 1
0
Block
AUT MAN
mode
A A
Block N N N N
ANCK C NR C NR
status R R
K K
Alarm
NR INT NR
status
ANS+ Since MV is manipulated,

the ANS+ alarm will be dissolved. D011727E.EPS
Figure Answerback Error Triggered Fallback (3-Position Status Output)

● Settings Answerback Triggers for Fallback
Setting the answerback triggers for fallback may be performed on the Function Block Detail
Builder.
• Fallback operation on the abnormal answerback:
Select from “NONE,” “ANS+,” “ANS-” and “BOTH.” The default setting is “NONE.”

■ Interlock Check Function
▼ Interlock Input Signal Direction, Output when Interlock Status is True, Modify Pulsive Output
when Interlock Status True
The interlock check function is used to place the MC-2 or MC-3 block in the interlock state
according to the operation interlock input signal that is input to the IL terminal of the MC-2
or MC-3 block.
In the interlock state, the predefined output action for MV=0, MV=1 or MV=2 can be ex-
ecuted.
• An internal switch or contact output can be used as the operation interlock input signal
in addition to the contact input.
• The “Interlock Input Signal Direction” determines whether the interlock state is acti-
vated by ON or OFF of the operation interlock input signal. The “Interlock Input Signal
Direction” may be defined on the Function Block Detail Builder. The default is “Direct.”
Direct: Interlock status is activated when the interlock signal = ON.
Reverse: Interlock status is activated when the interlock signal = OFF.
• The “Output When Interlock Status True” may be defined on the Function Block Detail
Builder. For a 2-position motor control block (MC-2), the selections are “Open” and
“Close.” The default is “Open.”
For a 3-position motor control block (MC-3), the selections are “Open,” “Close” and
“Stop.” The default is “Close.”
• In the interlock state, the output is switched to the status output even if it is pulsive
output. However, when “Direct Output” is specified in “Modify Pulsive Output When
Interlock Status True” in the Function Block Detail Builder, the pulsive output is re-
tained. The default is “Status Output.”
• When the interlock state is activated, the change of the output is monitored and the
interlock alarm (INT) will be activated at the occurrence of output change by the output
action of predefined interlock state. When the interlock is released, the interlock alarm
is deactivated at the same time.
IMPORTANT
The interlock check function does not operate under the following conditions:
• Simulation status (SIM)
• On-site manual mode (TRK)
• When the interlock check bypass command is issued (when BPSW=2 or 3)
• When the off-service command is issued. (when BPSW=4)
The action and interlock alarm (INT) initiated by establishment of interlock conditions will be
activated when answerback error triggered fallback takes place.
SEE ALSO
For details on the behavior of the fallback triggered by answerback errors, see previous section
“■ Answerback Error Triggered Fallback.”

■ Off-Service Function
The off-service function is used to stop the output from the MC-2 or MC-3 block via a
command from the bypass command switch (BPSW).
Off-service function supports the following processes.
• The off-service function is activated by putting the bypass command switch (BPSW) to
4. When the off-service command is issued, the block mode is changed to the manual
(MAN) mode and the block status becomes OFF.
• No output action (output signal conversion) is executed in the off-service state.
• The answerback tracking operates in the off-service state.

D1.17.4 Alarm Processing of Motor Control Blocks (MC-2, MC-3)

The following lists the alarm checks performed by the MC-2 and MC-3 blocks which
are specific to these two function blocks.
• Feedback input high and low limit alarm check
• Answerback unset alarm check
• Answerback error alarm check
■ Feedback Input High Limit/Low Limit Alarm Check

▼ Input High/Low Limit Alarm
The input high limit and low limit alarm check in the MC-2 and MC-3 blocks is used for
checking the feedback input.
By means of this feedback input high limit and low limit alarm check, when the feedback
input value (FV) exceeds the feedback input high limit alarm setpoint (PH), a feedback
input high limit alarm (HI) is generated. Also, when the feedback input value (FV) drops
below the feedback input low limit alarm setpoint (PL), a feedback input low limit alarm (LO)
is generated.
When an alarm has occurred, if the feedback input value (FV) drops lower than the value of
the feedback input high limit alarm setpoint (PH) minus the input high and low limit alarm
hysteresis (HYS), the feedback input high limit alarm (HI) is returned to normal state. Also,
if the feedback input value (FV) exceeds the feedback input low limit alarm setpoint (PL)
plus the input high and low limit alarm hysteresis (HYS), the feedback input low limit alarm
(LO) is returned to normal state.
FV
PH
HYS
Conditions generating an alarm
FV PH
FV
PL
Conditions for recovery from alarm

FVPHHYS
FVPLHYS
HYS
PL
Time
HI
LO
D011728E.EPS
Figure Actions of the Feedback Input High and Low Limit Alarm Check

● Feedback Input High Limit/Low Limit Alarm Settings
Setting of the feedback input high limit/low limit alarm setpoint (PH, PL) is done using the
following setting parameters:
• Feedback input high limit alarm setpoint (PH):
Engineering unit data within the FV scale range
The default is the FV scale high limit value.
• Feedback input low limit alarm setpoint (PL):
Engineering unit data within the FV scale range
The default is the FV scale low limit value.
The hysteresis is set with the Function Block Detail Builder.

• Hysteresis:
Engineering unit data within the range of 0 to FV scale span, or percentage data for
the FV scale span
■ Thermal Trip Alarm Check

The thermal trip alarm check is a function that determines whether a thermal trip signal
indicating a motor overload condition was input to the MC-2 or MC-3 block.
If it is determined that when the signal for the thermal trip signal input terminal (TT) turns on
in the MC-2 or MC-3 block, a thermal trip alarm is generated. If the signal from the thermal
trip signal input terminal (TT) turns off while the alarm is being generated, the alarm is
returned to normal state.
The output action of the MC-2 and MC-3 blocks when there is a thermal trip alarm is the
same as when the block is showing an interlock (LOCK) state.
SEE ALSO
See section “■ Interlock Check Function” in chapter D1.17.3, “Output Processing of Motor Control Blocks
(MC-2 and MC-3)” for information on the interlock status of the MC-2 and MC-3 blocks.

■ Interlock Alarm Check
For MC-2 or MC-3 Motor Controller blocks, when the Interlock Alarm Check function
detects the establishment of interlock condition, or fallback action is activated by
answerback errors, the manipulated output (MV) will be forced to the designated value
predefined in the builder item [Output when interlock status is true]. At the same time the
Interlock Alarm (INT) will be initiated.
When the Interlock Alarm Check detects that the interlock condition is no longer existing,
the Interlock Alarm (INT) will be dissolved.
The interlock check triggered interlock alarm (INT) will be deactivated whenever the inter-
lock condition is dissolved.
The interlock alarm (INT) initiated by Answerback Error Triggered Fallback will become
deactivated once the manipulated output value (MV) is manually changed.
SEE ALSO
For more information about the answerback error triggered fallback, see section “■ Answerback Error
Triggered Fallback” in chapter D1.17.3, “Output Processing of Motor Control Blocks (MC-2, MC-3).”
■ Answer-Back Inconsistency Alarm Check

The answerback inconsistency alarm check is a function that determines whether two
answerback input signals indicate full-open and full-close simultaneously.
If it is determined that two answerback input signals indicated full-open and full-close
simultaneously, an answerback inconsistency alarm (PERR) occurs.
If the two answer-back input signals stop indicating full-open and full-close simultaneously
while the alarm is being generated, the alarm is returned to normal state.
■ Answer Back Error Alarm Check

The answerback error alarm check is a function that determines if the manipulated output
value and the answerback input value do not match.
If it is determined that the manipulated output value and the answerback input value do not
match when the manipulated output value (MV) is 2, the ON side answerback error alarm
(ANS+) occurs. If the manipulated output value and the answerback input value do not
match when the manipulated output value (MV) is 1, the OFF side answerback error alarm
(ANS-) occurs.
If the manipulated output value and the answer-back input value match while the alarm is
being generated, the alarm is returned to normal state.

<Toc> <Ind> <D1.18 Ratio Set Block (RATIO)> D1-247
D1.18 Ratio Set Block (RATIO)

The Ratio Set Block (RATIO) outputs its manipulated output value (MV) follows the
change of process variable (PV) times the ratio set value. This block is used to set a
specific ratio at which two controlled variables are maintained.
■ Ratio Set Block (RATIO)

▼ Connection
The RATIO Block defines a ratio for control of two control amounts. The figure below shows
the RATIO Block diagram.
The figure below shows the function block diagram of Ratio Set Block (RATIO):
SET TIN TSI INT
CAS (TSW)
CSV
AUT
SV
MAN
RSV
RCAS
Input Control computation CAS/AUT Output

IN PV MV OUT
processing (ratio computation) processing
ROUT
SUB D011801E.EPS
Figure Function Block Diagram of Ratio Set Block (RATIO)

The figure below shows the internal control computation processing of the Ratio Set Block
(RATIO):
Control computation
Setpoint value Setpoint

CSV RSV
pushback value limiter
Ratio
SV
tracking
Setpoint value
ramp action
MAN
Ratio computation Output

PV CALC MV
KR • SVe • PV+BIAS AUT processing
CAS
RCAS ROUT D011802E.EPS
Figure Control Computation Processing of Ratio Set Block (RATIO)
The figure below shows an example of using the Ratio Set Block (RATIO):
IN OUT rF1
RATIO
SET
F1
IN OUT
PID
F2
D011803E.EPS
Figure Example of Using Ratio Set Block (RATIO)

In this control loop, the flowrates F1 and F2 are maintained in a specific ratio r, by setting
the value of F1 multiplied by r, or rF1, as the setpoint value of F2.
terminals of the Ratio Set Block (RATIO):
Table Connection Methods and Connected destinations of the I/O Terminals of Ratio Set Block
(RATIO)
SET Setting input
Tracking signal
TIN
input
D011804E.EPS

■ Function of Ratio Set Block (RATIO) ¡ £
The RATIO block performs input processing, control computation processing, output
The only processing timing available for the RATIO block is a periodic startup. Selections
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the RATIO block,
see chapter D1.1.3, “Input Processing, Output Processing, and Alarm Processing Possible for Each
• For details on the input processing, see chapter C3, “Input Processing.”
• For details on the output processing, see chapter C4, “Output Processing.”
• For details on the alarm processing, see chapter C5, “Alarm Processing-FCS.”
● Control Computation Processing of Ratio Set Block (RATIO)

The table below shows the control computation processing functions of the Ratio Set Block
(RATIO):
Table Control Computation Processing Functions of Ratio Set Block (RATIO)
Obtains a calculated output value (CALCn) by multiplying the process variable (PV) by
Ratio computation
the effective ratio setpoint value (SVe).
type” only.
Constantly updates the ratio setpoint value (SV) with a value calculated backwards from
Ratio tracking the current manipulated output value (MV), when ratio computation is stopped. This
prevents the manipulated output value from changing abruptly.
Causes the change in the effective ratio setpoint value (SVe) to gradually approach the
Ratio setpoint value
newratio setpoint value, when the ratio setpoint value (SV) has changed abruptly. This
ramp action
prevents the manipulated output value from changing abruptly.
Control hold
MAN fallback
Changes the block mode to AUT when the function block is operating in the CAS mode,
AUT fallback so that the control action is continued using values set by the operator. This action takes
place when the AUT fallback condition becomes satisfied.
Temporarily suspends actions in the RCAS or ROUT mode and switches to the computer
Computer failure
backup mode.
D011805E.EPS

■ Ratio Computation
In ratio computation, the following computation processing is performed to obtain a calcu-
lated output value (CALC) by multiplying the process variable (PV) by the effective ratio
setpoint value (SVe):
CALCn=KR • SVe • PVn+BIAS (1)
CALCn: Current calculated output value

PVn: Current process variable
SVe: Effective ratio setpoint value
KR: Ratio gain
BIAS: Bias value
The effective ratio setpoint value (SVe) is a ratio setpoint value (SV) that has been pro-
cessed via the setpoint value ramp action to be used for bumpless switching of block
modes.
In any automatic operating mode (AUT, CAS or RCAS), the calculated output value (CALC)
receives output signal processing and is set as the manipulated output value (MV).
● Setpoint Value (SV) Range

▼ SV Range
Use the Function Block Detail Builder to set the ratio setpoint value (SV) range:
• SV range high limit:
Specify a numeric value of 7 digits or less, where the sign and decimal point occupy
one digit each.
The default is 4.0.
• SV range low limit:
one digit each.
The default is 0.0.
● Ratio Gain
▼ Ratio Gain
Use the Function Block Detail Builder to set the ratio gain:
• Ratio Gain:
one digit each.
The default is 1.0.

The expressions to obtain the ratio gain are shown below:
• Example 1
The figure below shows an example of operating a flow ratio control system where the
flowrates F1 and F2 range from 0 to 100 m3/h and from 0 to 30 m3/h, respectively, by
maintaining the ratio r between 0.0 and 0.3:
r=0 to 0.3
F1=0 to 100 m3/h

RATIO
F2=0 to 30 m3/h
PID
D011806E.EPS
Figure Example of Flow Ratio Control
When the above conditions are applied to the computational expression (1), the
flowrate F1, target flowrate value of F2, and ratio r are represented by the process
variable (PV), calculated output value (CALC) and ratio setpoint value (SV), respec-
tively.
When F1 is 0, the target of F2 is also 0. Thus, set the bias setpoint value (BIAS) of the
computational expression to 0. As a result, the following computational expressions
are satisfied:
CALCn=KR • SVe • PV (2)
CALCn
KR= (3)
SVe • PV D011807E.EPS
When r is 0.1 and F1 is 100 m3/h, the target value of F2 is the product of 100 and 0.1,
or 10 m3/h. If this condition is applied to the computational expression (3), the follow-
ing computational expression is obtained:
CALCn=10, PV=100, SVe=0.1 (SVe=SV)
10
KR=
0.1 • 100
=1.0 D011808E.EPS
As values of the process variable (PV), calculated output value (CALCn) and effective
ratio setpoint value (SVe) are all engineering unit data, this computational expression
indicates that the ratio gain (KR) becomes 1.0, if the process variable (PV) and calcu-
lated output value (CALCn) are in the same unit and the effective ratio setpoint value
(SVe) has no unit.

• Example 2
In the figure “Example of Flow Ratio Control,” assume that the flow ratio control
system provides the flowrates F1 and F2 that range from 0 to 300 m3/h and from 0 to
100 ᐉ/min., respectively, and is operated at the ratio r of between 0.0 and 2.0 %.
When F1 is 0, the target value of F2 is 0. Thus, set the bias setpoint value (BIAS) to 0
and apply the expression (3) in Example 1.
When the assumed setting of r is 1.0 % and F1 is 300 m3/h, the target value of F2 is
the product of 300 and 1.0/100, or 3 m3/h, which is then converted to 50 ᐉ/min.
When this is applied to the expression (3), the following computational expression is
obtained:
CALCn=50, PV=300, SVe=1.0 (SVe=SV)
50
KR=
1.0 • 300
=0.1667 D011809E.EPS
As values of the process variable (PV) and calculated output value (CALCn) are engineer-
ing unit data, the ratio gain (KR) does change even when the scale high/low limits of the
process variable (PV) and calculated output value (CALCn) are changed.
However, the ratio gain (KR) must be changed when the engineering unit of the process
variable (PV) and calculated output value (CALCn) or that of ratio setpoint value (SV) is
changed, as the ratio gain (KR) is calculated based on the unit conversion coefficients of
these values. The engineering unit of the calculated output value (CALCn) is the same as
that of the manipulated output value (MV).
● Bias Value
Set the bias value.
Set a data value in the same engineering unit as the manipulated output value (MV) and
within the range of - (MSH - MSL) to (MSH - MSL). The bias value can be set or changed
from operation and monitoring functions during operation. The default is the MV scale low
limit (MSL).

control period to an actual manipulated output value (MV).
The control output actions available with the Ratio Set Block (RATIO) are of “positional
type” only.
The calculated output value (CAL) is set as the manipulated output value (MV).

The setpoint value limiter function limits the setpoint value (SV) within the range between
the setpoint high limit (SVH) and setpoint low limit (SVL), recognizing values only inside this
range as valid.
The action of the setpoint value limiter varies in accordance with the block mode of the
function block.
● Actions in the Automatic (AUT) or Manual (MAN) Mode

When the block mode of the function block is automatic (AUT) or manual (MAN), in which
the user is able to set the setpoint value, the setpoint value limiter performs the following
actions in accordance with the situation:
• When a value exceeding the setpoint high limit (SVH) is set as the setpoint value (SV)
When confirms, the operator can set a value exceeding the setpoint high limit (SVH).
• When a value below the setpoint low limit (SVL) is set as the setpoint value (SV)
When confirms, the operator can set a value below the setpoint low limit (SVL).
● Actions in the Remote Cascade (RCAS) Mode

When the block mode of the function block is remote cascade (RCAS) and the setpoint
value (SV) is set to automatically agree with the remote setpoint value (RSV) received from
the supervisory system computer, the setpoint value limiter performs the following actions:
• Limits a value exceeding the setpoint high limit (SVH) to the setpoint high limit (SVH).
• Limits a value below the setpoint low limit (SVL) to the setpoint low limit (SVL).

• Setpoint high limit (SVH): Engineering unit data within the SV scale range
• Setpoint low limit (SVL): Engineering unit data within the SV scale range

values (SV, CSV, RSV). The figure below explains the relationships among the setpoint
RSV CSV
AUT/MAN
RCAS CAS
SV
Setpoint value
Control
computation
D011810E.EPS
function block.


Causes the setpoint value (SV) and remote setpoint value (RSV) to agree with the cascade

Causes the setpoint value (SV) and cascade setpoint value (CSV) to agree with the remote

lated output value (MV) downstream in cascade without causing the manipulated output
value (MV) to change abruptly (i.e., bumpless change).
status.
The functions of bumpless switching available with the Ratio Set Block (RATIO) include the
following:
• Ratio tracking
• Ratio setpoint value ramp action
● Ratio Tracking
▼ Ratio Tracking
The ratio tracking function sets as a ratio setpoint value (SV) the value calculated back-
wards from the manipulated output value (MV), when ratio computation is stopped.
Ratio tracking enables bumpless switching of block modes from manual (MAN) to auto-
matic (AUT).
1
SV=(MV-BIAS) •
PV • KR D011811E.EPS
Ratio tracking is executed in the following conditions:

• In the manual (MAN) mode
• In the initialization manual (IMAN) mode (e.g., when cascade connection to a down-
stream loop becomes open)
Use the Function Block Detail Builder to set ratio tracking.

• Ratio tracking:
Set “Yes” or “No” for each condition of MAN, AUT plus CND or CAS plus CND.
The table below shows the default settings of ratio tracking:
Table Default Settings of Ratio Tracking

Specification condition (status) Default
MAN Ratio tracking disable.
AUT plus CND Ratio tracking disable.
CAS plus CND Ratio tracking disable.
D011812E.EPS
Note: The statuses of MAN, AUT and CAS include remote backup modes, such as AUT (ROUT) and AUT (RCAS).

● Ratio Setpoint Value Ramp Action
The ratio setpoint value tracking action executes bumpless switching in place of ratio
tracking, when “No” is specified for ratio tracking.
The ratio setpoint value ramp action limits the change in the effective ratio setpoint value
(SVe) during each scan period to be equal to or less than the ramp constant (RP), when
changes occur in the ratio setpoint value (SV).
When the block mode changes from manual (MAN) to automatic (AUT), an effective ratio
setpoint value (SVe) is calculated backwards from the manipulated output value (MV), and
the obtained value is set as the initial effective ratio setpoint value (SVe). Therefore, the
same actions take place when the ratio setpoint value (SV) changes, thus prevent the
manipulated output value (MV) from changing abruptly when the block mode changes.
The figure below shows an example of the ratio setpoint value ramp action.
SV
Ramp constant (RP)

Effective ratio setpoint value
Scan period
D011813E.EPS
Figure Example of the Ratio Setpoint Value Ramp Action
Set the ramp constant from operation and monitoring functions as a set parameter.
• Ramp constant (RP): Engineering unit data within the SV scale span range.
When “Yes” is specified for ratio tracking, the ratio setpoint value ramp action will not be
executed even when the block mode is changed from manual (MAN) to automatic (AUT).


Because the initialization manual action causes the manipulated output value (MV) to track
the value at the connected destination, even when the initialization manual (IMAN) mode
changes to manual (MAN), the initialization manual (IMAN) mode will override the manual
(MAN) mode. Therefore, no actions in the manual (MAN) mode will take place.
changes to that mode only when the initialization condition vanishes.

vanishes:
AUT
IMAN (AUT)
AUT
The initialization manual condition establishes in the following situation:

• When the data status at the connected destination of the manipulated output value
(MV) is conditional (CND) (i.e., the cascade connection is open).
(SW-33, SW-91) and the connection is switched off. (i.e., the cascade connection is
open).
• When the manipulated output value (MV) connected destination is a process output,
and a failure or output open alarm has occurred in the module.

■ Control Hold
The control hold action takes place when the following conditions are established during
automatic operation (AUT, CAS, RCAS or ROUT):
switch, etc.).
rarily in a non-response state (momentary power failure).
The control is resumed when the conditions vanish.

■ MAN Fallback

operation state.

AUTAMAN

(CAL). However, the MAN fallback condition will not be established when the block
mode is remote output (ROUT) excluding any of the compound modes during com-
puter backup.

■ AUT Fallback
cade (CAS) to automatic (AUT) when the AUT fallback condition is established, and
switches the control action to the one that uses values set by the operator.

Changes the block mode from cascade (CAS) to automatic (AUT) to continue control using
values set by the operator.
Once the AUT fallback condition establishes, the block mode remains automatic (AUT)
even when the condition vanishes.

The AUT fallback condition is used to change the function block mode from cascade (CAS)
to automatic (AUT) so that control can be continued using values set by the operator. When
this condition is established, it indicates that abnormality has been detected in the cascade
setpoint value (CSV) for some reason.
The following example shows when the AUT fallback condition establishes:
CASAAUT
Use the Function Block Detail Builder to enable or disable the AUT fallback function.
The AUT fallback condition establishes when the AUT fallback is defined as “Yes” via the
Function Block Detail Builder and the data status of the cascade setpoint value (CSV)
becomes invalid (BAD) or communication error (NCOM).

■ Computer Fail

supervisory system computer via control bus communication.
change.
The following actions take place while the computer fail condition exists, the block mode
change command from MAN, AUT or CAS to remote cascade (RCAS) or remote output
(ROUT) is sent:
1. When a block mode change command from MAN, AUT or CAS to RCAS or ROUT is
sent while the computer fails (BSW=ON), the function block does not switch to the
before the execution of the block mode change command (MAN, AUT, CAS and a
remote mode (RCAS, ROUT).
(RCAS, ROUT).

A backup switch (BSW) is provided in function blocks to define the remote cascade (RCAS)
The following example shows when the automatic (AUT) mode has been specified for the
computer backup mode:
RCAS
? Computer fails
AUT (RCAS)
? Computer recovers
RCAS
AUT
? ROUT command
● Setting Computer Backup Mode

Use the Function Block Detail Builder to set the computer backup mode for each function
block.
becomes down.

auto mode, and prohibit the function block changing to automatic operation mode

RCAS or ROUT mode) becomes invalid.

The block mode change interlock condition is established when the switch at the connected
destination of the interlock switch input terminal (INT) is turned ON as a result of continued
automatic operation becoming impossible due to an abnormality in the plant, etc.

■ Data Items - RATIO
Table Data Items of Ratio Set Block (RATIO) (1/2)
Item or Not
SV Ratio setpoint value (*2) SV engineering unit value SSL
CSV Cascade ratio setpoint value Value in the same engineering unit as SV SSL
RSV Remote ratio setpoint value Value in the same engineering unit as SV SSL
D011814E.EPS

SEE ALSO
For a list of valid block modes of the RATIO block, see chapter D1.1.4, “Valid Block Modes for Each

Table Data Items of Ratio Set Block (RATIO) (2/2)
Item or Not
BIAS Bias value MSL to MSH MSL
RP Ramp constant 0 to (SSH - SSL) SSH - SSL
KR Ratio gain ----- 1.000
D011815E.EPS


<Toc> <Ind> <D1.19 13-Zone Program Set Block (PG-L13) > D1-267
D1.19 13-Zone Program Set Block (PG-L13)

The 13-Zone Program Set Block (PG-L13) outputs the time function signals accord-
ing to the specified line segment graph against time-axis.
Using the 13-Zone Program Set Block (PG-L13) in combination with controller
blocks enables program control of processes.
■ 13-Zone Program Set Block (PG-L13)

▼ Connection
Specify the time function signal output of the 13-Zone Program Set Block (PG-L13) indi-
cated in a line-segment pattern. A program pattern of up to 166 hours or 166 minutes long
can be set when the time-axis setting unit is minute or second, respectively.
The figure below shows a function block diagram of 13-Zone Program Set Block (PG-L13):
INT
SV
Control computation
(program setting)
CAS
AUT Output
CALC MV OUT
processing
MAN
(Annunciator output)
SUB D011901E.EPS
Figure Function Block Diagram of 13-Zone Program Set Block (PG-L13)
terminals of the 13-Zone Program Set Block (PG-L13):
Table Connection Methods and Connected destinations of the I/O Terminals of 13-Zone Program
Set Block (PG-L13)
SUB Annunciator output
D011902E.EPS

■ Function of 13-Zone Program Set Block (PG-L13)
The PG-L13 block performs control computation processing, output processing, and alarm
processing.
The only processing timing available for the PG-L13 block is a periodic startup. Moreover,
startup.
SEE ALSO
• For the types of output processing and alarm processing possible for the PG-L13 block, see a chapter
D1.1.3, “Input Processing, Output Processing, and Alarm Processing Possible for Each Regulatory
Control Block.”
● Control Computation Processing of 13-Zone Program Set Block

(PG-L13)
The table below shows the control computation processing functions of the 13-Zone
Program Set Block (PG-L13):
Table Control Computation Processing Functions of the 13-Zone Program Set Block (PG-L13)
Expresses a line-segment pattern of the program with line segments connecting up to 14
Line-segment pattern signal
coordinates on a plane of time (X axis) and output (Y axis) including starting and end
generation
points.
Calculates output values during each base period in accordance with the program set
Program set action
pattern, to obtain a calculated output value (CALC).
Saves or changes the calculated output value (CALC) and elapsed time (SV) at the end of
Program end action
the program.
Movement along the time axis Moves along the time axis in accordance with the setting of set parameters (SV, ZONE).
Annunciator output Turns the annunciator message ON at the end of the program set action.
type” only.
the block mode has been changed or when the manipulated output value (MV) has been
Bumpless switching
switched in a downstream block in cascade. The types of bumpless switching include
“bumpless start action.”
MAN fallback
D011903E.EPS

■ Line-Segment Pattern Signal Generation
▼ Total Elapsed Time, Time Unit
The 13-Zone Program Set Block (PG-L13) performs control computation based on line-
segment pattern signal generation. The line-segment pattern used to set programs is
expressed by line segments that connect coordinate points of time and output including the
starting and end points.
● Line-Segment Pattern
The line-segment pattern used to set programs is expressed by line segments that connect
up to 14 coordinate points on a plane of time (X axis) and output (Y axis) including the
starting and end points (maximum 13 line segments). The specifications of program-setting
line-segment patterns are shown below:
● Number of Line-Segments: 1 to 13
Arbitrary line segments can be set on a coordinate plane of time (X axis) and output (Y
axis).
● Zone Number (ZONE): 1 to 13

The space between the time-axis coordinates Xn and Xn+1 is called “Zone n.”
● Setting Ranges
Line-segment patterns are set from operation and monitoring functions.
• Time-axis breakpoint coordinate (X01 to X14):
0 to 9999 minutes, or 0 to 9999 seconds.
• Output-axis breakpoint coordinate (Y01 to Y14):
Engineering unit MV data.
Use the Function Block Detail Builder to set the time unit of time-axis breakpoint coordi-
nates or total running time of the program.
• Time Unit: Select “seconds” or “minutes”
The default is “second.”
• Total Elapsed Time: 0 to 10000
The default is 10000.

■ Program Set Action
In the automatic (AUT) or cascade (CAS) mode, the program set action calculates output
values set by the program set pattern during each basic scan period (1 second), and uses
the obtained result as a calculated output value (CALC). In the cascade (CAS) mode, the
current position returns to the start of the program set pattern when its end is reached, and
output is repeated along the program set pattern.
CALC
PH
PL
2
3
Present value
MH
ML
SV
D011904E.EPS
Elapsed time (SV)
Calculated output value (CALC)
Intra-zone time high limit (PH): End time of the zone number corresponding to the current elapsed time
Intra-zone time low limit (PL): Start time of the zone number corresponding to the current elapsed time
Remaining intra-zone output high limit (MH): Maximum output value between the current elapsed time and intra-zone time
high limit (PH)
Remaining intra-zone output low limit (ML): Minimum output value between the current elapsed time and intra-zone time
low limit (PL)
Figure Program Set Pattern

In the automatic (AUT) or cascade (CAS) mode, output processing is performed to the
calculated output value (CALC) and the result is output as a manipulated output value
(MV).
When the automatic (AUT) or cascade (CAS) mode is changed to manual (MAN) or initial-
ization manual (IMAN), the set action will stop. However, computation data, such as time
and calculated output values, will be stored.
If the block mode is changed back to automatic (AUT) or cascade (CAS), the program set
action resumes from the stored time.
If breakpoints are partially set in a reverse direction on the time axis (e.g., X01 > X02), the
reversed portion will be ignored. The figure below shows an example of the reversed
portion on the time axis being ignored:
D011905E.EPS
In this example, the original line-segment pattern is represented by a dotted line. However,
the 13-Zone Program Set Block (PG-L13) only recognizes the pattern represented by the
solid line.
■ Program End Action

▼ When Program Exits
The actions performed in the automatic (AUT) mode at the end of the program include the
following two types:
In each action, the manipulated output value (MV) is caused to agree with the calculated
output value (CALC). Use the Function Block Detail Builder to set the program end action.
• When program exits: Select “Holding PV” or “Quick Return.”
The default is “Holding PV.”
● Final Value Holding Type

The calculated output value (CALC) and elapsed time (SV) at the end of the program are
held and the operating mode is switched to manual.
● Quick Return Type

The current position returns to the beginning of the program pattern (time value=0), and the
operating mode is switched to manual after the calculated output value (CALC) and
elapsed time (SV) are changed to the values at the starting point.

■ Movement Precedence Along the Time Axis
The 13-Zone Program Set Block (PG-L13) moves along the time axis not only as time
elapses but also when data is set from operation and monitoring functions to the SV or
ZONE set parameter or when bumpless start is executed.
The three methods to force the block to move along the time axis have the following move-
ment precedence:
Movement precedence
1: Bumpless start action
2: Setting the zone number (ZONE)
3: Setting the elapsed time (SV)
● Setting the Zone Number

When a value between 1 and 13 is set for the zone number (ZONE), actions will be contin-
ued from the beginning of the zone that has been set. The zone number (ZONE) can be set
in any block mode.
● Setting the Elapsed Time (SV)

When any of the time data between the starting point and end point is set for the elapsed
time (SV), actions will continue from the point on time axis that has been set. The elapsed
time (SV) can be set in any block mode.
SEE ALSO
For the bumpless start action, see a section “■ Bumpless Switching.”
■ Annunciator Output
When the software annunciator message (%AN) is specified for the output destination of
the annunciator output terminal (SUB), the annunciator message function will be turned ON
at the end of the program set action. However, the program set block only turns the function
ON but does not reset it. Use a sequence control block, or etc. to reset the alarm.

The control output action converts the manipulated output change (MV) of each control
The control output action applied in the 13-Zone Program Set Block (PG-L13) is of “posi-
tional type” only.
The calculated output value (CALC) is set as the manipulated output value (MV).

▼ Bumpless Start
lated output value of the downstream block in the cascade loop without causing the ma-
nipulated output value (MV) to change abruptly (i.e., bumpless change).
The type of bumpless switching action varies with the control output action and block mode
status.
The type of bumpless switching performed by the 13-Zone Program Set Block (PG-L13) is
“bumpless start action.”
The bumpless start action prevents the value of the output destination from changing
abruptly when the program set action is started from zero elapsed time (SV) by changing
the block mode from manual (MAN) to automatic (AUT) or cascade (CAS).
When the program set action is started from zero elapsed time (SV), the position on time
axis is fast-forwarded until the calculated output value (CALC) agrees with the setpoint
value of the output destination. The range of program pattern in which this agreement point
is searched is specified by the bumpless start zone (ZSTR) and bumpless end zone
(ZEND).
If no matching pattern is found in the search range, the program set action is started from
the end point of the last zone that exists inside the search range.

Use the Function Block Detail Builder to define the bumpless start action.
• Bumpless Start: Select “Yes” or “No.”
The bumpless start zone (ZSTR) and bumpless end zone (ZEND) are set from operation
and monitoring functions as set parameters.
• Bumpless start zone (ZSTR): Select a value between 1 and 13.
• Bumpless end zone (ZEND): Select a value between 1 and 13.
Bumpless start zone
Present value of
output destination ZEND
ZSTR
0 Fast-forwarding
along the time axis SV
D011906E.EPS
Figure Bumpless Start Action
If two successive mode change commands, one to the manual (MAN) mode and the other
to the automatic (AUT) or cascade (CAS) mode, are issued from a sequence control block,
etc. within a single scan period, bumpless start is not executed. Instead, the program set
action is started from the starting point of the program pattern.
If a mode change command to the automatic (AUT) mode is issued by itself, bumpless start
is executed.


However, if try to change the block mode in the initialization manual (IMAN) mode, the
block will switch to that mode only when the initialization condition vanishes.

tion manual (IMAN).
vanishes:
AUT
IMAN (AUT)
AUT

(MV) is a communication error (NCOM) or output failure (PTPF).
• When the connected destination of the manipulated output value (MV) is a switch
block (SW-33, SW-91) and the switch off the cascade connection (i.e., the cascade
connection is open).
• When the connected destination of the manipulated output value (MV) is a process
output and a failure or output open alarm is detected in module.

■ MAN Fallback

The MAN fallback stops the control by changing the block to manual (MAN) mode regard-
less of the current operation status, and forces the function block to enter manual operation
state.

Example) AUTAMAN

the I/O points connected to the I/O module has been changed via maintenance.


operation state. The following actions take place:
• Any block mode change command to obtain an automatic operation state (AUT or
CAS mode) becomes invalid.


■ Data Items - PG-L13
Table Data Items of 13-Zone Program Set Block (PG-L13)
Item or Not
SV Elapsed time Value in seconds or minutes 0
PH Intra - zone time high limit Value in seconds or minutes 0
PL Intra - zone time low limit Value in seconds or minutes 0
MH Output high-limit for remainder of zone MSL to MSH MSL
ML Output low-limit for remainder of zone MSL to MSH MSL
ZONE Zone number (*2) 1 to 13 1
ZSTR Bumpless start zone 1 to 13 1
ZEND Bumpless end zone 1 to 13 1
X01 to X14 Time - axis breakpoint coordinate (*3) Value in seconds or minutes 0
Y01 to Y14 Output - axis breakpoint coordinate MSL to MSH MSL
OPLO Output high-limit index MSL to MSH MSL
SH Time-axis scale high limit Value in seconds or minutes -----
SL Time-axis scale low limit Value in seconds or minutes -----
MSH MV scale high limit MV engineering unit value -----
MSL MV scale low limit MV engineering unit value -----
D011907E.EPS

*2: Data for ZONE can be set through an I/O connection with another function block, such as a calculation block, but not
externally as from the operation and monitoring functions.
*3: X01 cannot be set because it is a time-axis origin and fixed at 0.
SEE ALSO
For a list of valid block modes of the PG-L13 block, see a chapter D1.1.4, “Valid Block Modes for Each

<Toc> <Ind> <D1.20 Totalizing Batch Set Blocks (BSETU-2, BSETU-3)> D1-279
D1.20 Totalizing Batch Set Blocks (BSETU-2,

BSETU-3)
The term “totalizing batch set block” is a generic name for the flow-totalizing batch
set block (BSETU-2) and the weight-totalizing batch set block (BSETU-3).
This section describes the functions common to these two function blocks.
■ Common Functions of Totalizing Batch Set Blocks

The following explains the functions common to the BSETU-2 and BSETU-3 blocks.
SEE ALSO
• For the functions specific to the BSETU-2 block, see a chapter D1.21, “Flow-Totalizing Batch Set Block
(BSETU-2).”
• For the functions specific to the BSETU-3 block, see a chapter D1.22, “Weight-Totalizing Batch Set Block
(BSETU-3).”
● Input Processing Common to Totalizing Batch Set Blocks

The BSETU-2 and BSETU-3 blocks perform a special integration.
● Control Computation Processing Common to Totalizing Batch Set Blocks

The control computation processing functions of the BSETU-2 and BSETU-3 blocks are
the same. The control computation processing functions possessed by these two function
blocks are as follows:
• Batch operation
• MAN fallback
● Output Processing Common to Totalizing Batch Set Blocks

The BSET-2 and BSETU-3 blocks perform a special output signal conversion.
● Alarm Processing Common to Totalizing Batch Set Blocks

The alarm checks commonly performed by and specific to the BSETU-2 and BSETU-3
blocks are as follows:
• Cumulative deviation high and low limit check

D1.20.1 Input Processing of Totalizing Batch Set Blocks

(BSETU-2, BSETU-3)
The BSETU-2 and BSETU-3 blocks perform a special integration.
■ Integration in the Totalizing Batch Set Blocks

In the BSETU-2 and BSETU-3 blocks, the following two types of integration are available:
• Integrator value (SUM):
The integration specification is the same as for other Regulatory Control Blocks, but
when batch begins the integrator value is cleared to 0.
• Total integrator value (SUM1):
The total integrator value (SUM1) accumulates the integrator value (SUM) for each
batch completion.
Total integrator value (SUM1)=(Total integrator value up to the previous
batch)+Integrator value (SUM)
SEE ALSO
For details on the integration, see a chapter C3.3, “Integration.”

D1.20.2 Control Algorithm of Totalizing Batch Set Blocks

(BSETU-2, BSETU-3)
The following functions are common to the control computation processing per-
formed by the BSETU-2 and BSETU-3 blocks.
• Batch operation
• MAN fallback
■ Batch Operation (Analog Output)

The batch operation performed by the Totalizing Batch Set Blocks varies depending upon
the type of output (analog output, 2-position ON/OFF output or 3-position ON/OFF output).
The figure below shows an example of batch operation in the case of analog output or data
setting output to other function block:
TU TD TU TD
MV
MH
Pre-batch
flowratesetpoint TW
PRE
ML
0
NCNT STRT RSTR STUP ERLY
Block
IBCH STUP STDY EMST EEMS STDY PBCH END NCNT
status
ZONE 0 10 1 2 3 8 9 11 2 3 4 5 7 0
Totalized 0 <
ILST
value ILST BSET - PLST BSET - LPV
Block
MAN AUT MAN
mode
Pre-batch BPRE
batch end
alarm BEND
MH: High flowrate setpoint BSET: Batch setpoint

ML: Low flowrate setpoint ILST: Initial forecast value
PRE: Pre-batch flowrate setpoint PLST: Pre-batch setpoint
TU: Rise time LPV: Leakage predictive value
TD: Fall time BPRE: Pre-batch alarm (early notification)
TW: Batch end wait time BEND: Batch end alarm (end notification)
D012001E.EPS
Figure Batch Operation (Analog Output)

The operating status is indicated by the block status and control step. The operating status
is switched via the command switch (SW), emergency stop switch (EMSW) or control step
(ZONE). The commands issued by the command switch (SW) and emergency stop switch
(EMSW) are shown below:
• Command switch (SW)
1: Start
2: Restart
3: Abort
4: Emergency stop
0: Changes to “0” automatically when the command (1 to 4) is acknowledged.
• Emergency stop switch (EMSW)
1: Emergency stop
0: After the executes command (1), it changes to “0” automatically.
● Basic Batch Operation

The following section explains the basic operation of the Totalizing Batch Set Blocks at
each control step (ZONE):
1. ZONE10: Batch start (Block status: STRT)

Sets data to the set parameters including batch setpoint (BSET) prior to batch start. If
the command switch is set to start (SW=1) while in the automatic (AUT) block mode,
the current control step moves to ZONE10 and the block starts batch operation after
resetting the totalized value (SUM) to 0.
Once batch starts, the control step moves to ZONE1.
2. ZONE1: Initial batch (Block status: IBCH)

After batch start, outputs the low flowrate setpoint (ML) as the manipulated output
value (MV) until the totalized value (SUM) reaches the initial forecast value (ILST).
The output velocity limiter does not operate. When the totalized value (SUM) exceeds
ILST, the control step moves to ZONE2.
The “low flowrate setpoint (ML)” and “initial forecast value (ILST)” are set from the
operation and monitoring functions as set parameters.
• Low flowrate setpoint (ML):
Set engineering unit data within the manipulated output value (MV) scale range.
The default is the manipulated output value (MV) scale’s low limit.
• Initial forecast value (ILST):
Set data in the same unit as the totalized value (SUM).
The default is 0.
The set value consist of 8 digits or less.

3. ZONE2: Setup (Block status: STUP)
Changes the manipulated output value (MV) to the high flowrate setpoint (MH) value
during the Ramp Up time (TU). The high flowrate setpoint (MH) is an output value in a
steady state.
When the set TU time elapses in the setup mode, the control step moves to ZONE3.
The “high flowrate setpoint (MH)” and “Ramp Up time (TU)” are set from the operation
and monitoring functions as set parameters.
• High flowrate setpoint (MH):
Set engineering unit data within the manipulated output value (MV) scale range.
• Ramp Up time (TU):
Set a value between 0 and 10000 seconds.
4. ZONE3: Steady (Block status: STDY)

Outputs the high flowrate setpoint (MH) as the manipulated output value (MV). When
the totalized value (SUM) reaches the value of batch setpoint (BSET) less pre-batch
setpoint (PLST), the control step moves to ZONE4.
The “batch setpoint (BSET)” and “pre-batch setpoint (PLST)” are set from the opera-
tion and monitoring functions as set parameters.
• Batch setpoint (BSET): Set data in the same unit as the totalized value (SUM).
The default is 0.
Specify a numeric value consisting of 8 digits or less.
• Pre-batch setpoint (PLST): Set data in the same unit as the totalized value (SUM).
The default is 0.
Specify a numeric value consisting of 8 digits or less.
5. ZONE4: Early (Block status: ERLY)

The alarm status changes to pre-batch alarm (BPRE). In the course of Ramp Down
time (TD), the manipulated output value (MV) is changed to PRE (pre-batch flowrate
setpoint) on the gradient that leads to the low-flowrate setpoint (ML). When the ma-
nipulated output value (MV) becomes the same value as the pre-batch flowrate
setpoint (PRE), the control step moves to ZONE5.
The “pre-batch flowrate setpoint (PRE)” and “Ramp Down time (TD)” are set from the
operation and monitoring functions as set parameters.
• Pre-batch flowrate setpoint (PRE):
Set engineering unit data within the MV scale range.
• Ramp Down time (TD):
Set a value between 0 and 10000 seconds.

6. ZONE5: Pre-batch (Block status: PBCH)
Outputs the pre-batch flowrate setpoint (PRE) as the manipulated output value (MV).
When the totalized value (SUM) reaches the value of batch setpoint (BSET) less
leakage predictive value (LPV), the control step moves to ZONE7.
The “leakage predictive value (LPV)” is set from the operation and monitoring func-
tions as a set parameter.
• Leakage predictive value (LPV):
Set data in the same unit as the totalized value (SUM).
The default is 0.
Specify a numeric value of 4 digits or less.
7. ZONE7: Batch end (Block status: END)

The alarm status changes to batch end alarm (BEND), and batch operation ends after
the manipulated output value (MV) is reset to “0.” When the batch end wait time (TW)
elapses in the batch end mode, the block mode changes to manual (MAN) and the
control step moves to ZONE0. At this time, the totalized value (SUM) is added to the
cumulative totalized value (SUM1). However, this addition will not take place in the
manual (MAN) mode.
The “batch end wait time (TW)” is set from the operation and monitoring functions as a
set parameter.
• Batch end wait time (TW): Set a value between 0 and 10000 seconds.
8. ZONE0: Batch operation stop (Block status: NCNT)

In this mode, batch Control Action stops and a manually manipulated variable can be
output.
9. ZONE6: Reset (Block status: RSET)

When the command switch is set to Abort (SW=3) during batch operation, the control
step moves to ZONE6 and the manipulated output value (MV) is brought down to 0 %
at a speed of changing it from the high flowrate setpoint (MH) to low flowrate setpoint
(ML) over the Ramp Down time (TD).
When the manipulated output value reaches 0 %, the control step moves to ZONE7.
When the totalized value exceeds the value of batch setpoint (BSET) less leakage
predictive value (LPV), the status changes to batch end and generates an alarm
(BEND). The batch ends other than this way does not generate batch end alarm
(BEND).
10. ZONE8: Emergency stop (Block status: EMST)

When the emergency command switch is set to emergency stop (EMSW=1), or when
the command switch is set to emergency stop (SW=4), the control step moves to
ZONE8, and the manipulated output value (MV) is brought down to 0 % at a speed of
changing it from the high flowrate setpoint (MH) to low flowrate setpoint (ML) over TD
(Ramp Down time). When the manipulated output value (MV) reaches 0 %, the control
step moves to ZONE9.

11. ZONE9: Emergency stop complete (Block status: EEMS)
When the totalized value (SUM) reaches the value of batch setpoint (BSET) less
leakage predictive value (LPV) during emergency stop, the control step moves to
ZONE7.
12. ZONE11: Restart (Block status: RSTR)

When the command switch is set to restart (SW=2) during the emergency stop com-
plete mode (ZONE9), the control stop moves to ZONE1 via ZONE11.
■ Actions Triggered by Command Switch

The figure below shows the actions of batch operation triggered by the command switch
(SW):
Command switch (SW) 1 4 2 3

Action Start EM-ST Restart Reset
Block mode AUT AUT AUT AUT
MV
MH
TW
ML
0
NCNT STRT RSTR STUP RSET
Block
IBCH STUP STDY EMST EEMS STDY END NCNT
status
ZONE 0 10 1 2 3 8 9 11 2 3 6 7 0
Totalized 0 <
ILST
value ILST
Block
MAN AUT MAN
mode
D012002E.EPS
Figure Actions of Batch Operation Triggered by Command Switch
Other than by the emergency stop command (SW=4), emergency stop can also be trig-
gered via the emergency stop switch (EMSW=1).

■ Transition of Control Step Status
The figure below shows a status transition diagram of control steps:
(M)
(F)
(D)
6
RSET (N)
1 (B) 2 (C) 3 (D) 4 (E) 5 (F) 7
IBCH STUP STDY ERLY PBCH END
(H)
(J)
11 9 8
(L) (I) (F)
RSTR EEMS EMST
(B)
(A) 10 (K) 0 (G)
STRT NCNT
Legend
ZONE
Block status
D012003E.EPS
(A) Batch start complete

(B) End of initial batch
(C) End of setup
(D) Early point detection (SUM>BET-PLST)
(E) End of pre-batch processing (MV=PRE)
(F) Batch end detection (SUM>BSET-LPV)
(G) End of batch end processing
(H) Emergency stop command (EMSW=1 or SW=4)
(I) Emergency stop complete
(J) Restart complete
(K) Start command (SW=1)
(L) Restart command (SW=2)
(M) Abort (SW=3)
(N) Abort completed (MV=0 %)
Figure Transition of Control Step Status
Status transition can also be induced by changing the control step. The control step
(ZONE) can be changed from a sequence table or calculation block, but not from the
operation and monitoring functions. Note that change commands issued by the command
switch (SW) precede any operation to change the control step (ZONE).
The totalized value (SUM) is added to the cumulative totalized value (SUM1) when batch
end processing is completed.

■ Manual Operation
When the block mode changes to manual (MAN), automatic control processing is sus-
pended and manual operation is enabled. The control step changes even during the
manual (MAN) mode. When the block mode is changed from manual (MAN) to automatic
(AUT) during manual operation, automatic control is started.
■ Automatic Prediction
When batch end is detected during each scan period, a flowrate error equivalent to a
maximum of one scan period may generate. The Totalizing Batch Set Blocks automatically
predicts batch end in order to minimize this error.
When the alarm status changes to pre-batch alarm (BPRE), the totalized value during the
next scan is predicted based on the totalized value increase during the current scan period
(totalized value during the current scan-totalized value during the previous scan). If the
predicted value exceeds the batch setpoint (BSET), a duration of time to keep the valve
fully open is calculated in 25 msec. units, based on the totalized value (SUM). The valve is
fully opened when the time calculated using this formula elapses.
The automatic prediction function is executed only in ZONE5. This function is also acti-
vated for outputs via a switch instrument block.
■ Batch Operation (2-Position ON/OFF Output)

Simple batch control based on the two-position ON/OFF output method can be performed
by connecting the output terminal (OUT) of the Totalizing Batch Set Blocks to a contact
output or switch instrument block. Valve closure processing can also be performed via
automatic prediction when the block is connected to a switch instrument.
The table below shows the relationship between the manipulated output values (MV)
during manual operation and those of a contact output or switch instrument block.
Table Relationship between Manipulated Output Values (MV) during Manual Operation and Those
of a Contact Output or Switch Instrument Block
MV value 0 % to 49.9 % 50 % to 100 %
Contact output OFF ON
Switch instrument MV=0 MV=2
D012004E.EPS

● Actions when Switch Instrument is in Cascade (CAS) Mode
When the connected switch instrument is in the cascade (CAS) mode, the BSETU-2 and
BSETU-3 blocks output the manipulated output value (MV) to the sequence setpoint value
(CSV) of the switch instrument, and the switch instrument outputs the received sequence
setpoint value (CSV) as its own manipulated output value (MV). In the case of emergency
stop, the manipulated output value (MV) drops to 0 % immediately.
The figure below shows an example of simple batch operation based on the 2-position ON/
OFF output method, when the switch instrument is in the cascade (CAS) mode.
In this example, the parameters are set as follows:
• Output velocity limiter: 100 %
• Ramp Up time (TU): 0 second
• Ramp Down (TD): 0 second
• High flowrate setpoint (MH): 100 %
• Low flowrate setpoint (ML): 100 %
• Pre-batch flowrate setpoint (PRE): 100 %
MV
100
2-position TW
ON/OFF
Block
NCNT STRT IBCH STDY EEMS RSTR STDY PBCH END NCNT
status
ZONE 0 10 1 3 9 11 3 5 7 0
Totalized 0
<ILST ILST BSET - LPV
value BSET - PLST
Block
MAN AUT MAN
mode
Pre-batch BPRE
batch end
alarm BEND
D012005E.EPS
Figure Example of Simple Batch Operation Using 2-Position ON/OFF Output Method when the
Both Switch Instruments are in Cascade (CAS) Mode
SEE ALSO
For the switch instrument block, see a chapter D3.4, “Switch Instrument Block.”

● Actions when Switch Instrument is not in Cascade (CAS) Mode
When the connected switch instrument is not in the cascade (CAS) mode, the Flow/
Weight-Totalizing Batch Set Block (BSETU-2, BSETU-3) changes to the initialization
manual (IMAN) mode. In this mode, the MV value of the switch instrument is set as the MV
of the Flow/Weight-Totalizing Batch Set Block (BSETU-2, BSETU-3) after having been
converted via the output value tracking function.
■ Batch Operation (3-Position ON/OFF Output)

Simple batch control using the 3-position ON/OFF output method can be performed by
connecting the output terminals (OUT, OUT2) of the Flow-Totalizing Batch Set Block
(BSETU-2) to contact outputs or switch instruments.
When connecting to contact outputs, use two contact outputs with successive terminal
numbers. Register the contact output with the smaller terminal number as I/O connection
information of the OUT terminal. The contact output with the smaller terminal number
becomes output contact 1. When connecting to switch instruments, the switch instrument
connected to the OUT terminal becomes switch instrument 1, and the one connected to the
OUT2 terminal becomes switch instrument 2.
The table below shows the relationship between the manipulated output values (MV)
during manual operation and those of contact outputs or switch instruments:
Table Relationship between Manipulated Output Values (MV) during Manual Operation and
Contact Outputs or Switch Instrument Blocks
MV value 0 % to 24.9 % 25 % to 74.9 % 75 % to 100 %
Contact output 1 OFF OFF ON
Contact output 2 OFF ON ON
Switch instrument 1 MV=0 MV=0 MV=2
Switch instrument 2 MV=0 MV=2 MV=2
D012006E.EPS

● Actions when Both Switch Instruments are in Cascade (CAS) Mode
When both of the connected switch instruments are in the cascade (CAS) mode, the
BSETU-2 or BSETU-3 blocks output two manipulated output values (MV) to the corre-
sponding sequence setpoint values (CSV) of switch instruments 1 and 2, and each switch
instrument outputs the received sequence setpoint value (CSV) as its own manipulated
output value (MV). In the case of emergency stop, the manipulated output value (MV)
drops to 0 % immediately.
The figure below shows an example of simple batch operation based on the three-position
ON/OFF output method, when the switch instruments are in the cascade (CAS) mode.
In this example, the parameters are set as follows:
• Output velocity limiter: 100 %
• Ramp Up time (TU): 0 second
• Ramp Down time (TD): 0 second
• High flowrate setpoint (MH): 100 %
• Low flowrate setpoint (ML): 50 %
• Pre-batch flowrate setpoint (PRE): 50 %
MV
100
3-position TW
ON/OFF
Block
NCNT STRT IBCH STDY EEMS RSTR STDY PBCH END NCNT
status
ZONE 0 10 1 3 9 11 3 5 7 0
Totalized 0
<ILST ILST BSET-LPV
value BSET-PLST
Block
MAN AUT MAN
mode
Pre-batch BPRE
batch end
alarm BEND
D012007E.EPS
Figure Example of Simple Batch Operation Based on 3-Position ON/OFF Output Method when
Both Switch Instruments are in the Cascade (CAS) Mode

● Actions when Only Switch Instrument 2 is in Cascade (CAS) Mode
When only switch instrument 2 is in the cascade mode, the Flow/Weight-Totalizing Batch
Set Block (BSETU-2, BSETU-3) outputs only to switch instrument 2.
ON/OFF output method, when only switch instrument 2 is in the cascade (CAS) mode:
MV
100 %
50 %
0 %
BSETU-2/ ZONE 0 1 3 9 3 5 7
BSETU-3
Switch instrument MODE CAS Other than CAS

1 MV 0 0/2 (No output from the BSETU-2/BSETU-3)
Switch instrument MODE CAS

2 MV 0 2 0 2 0
Switch instrument 1 changes to a non-CAS mode D012008E.EPS
Figure Example of Batch Operation when Only Switch Instrument 2 is in Cascade (CAS) Mode

● Actions when Only Switch Instrument 1 is in Cascade Mode
In batch operation where only switch instrument 1 is in the cascade (CAS) mode, the
manipulated output value (MV) of switch instrument 1 becomes 0 in the initial batch
(ZONE1) and pre-batch (ZONE5) modes. Therefore, if the manipulated output value (MV)
of switch instrument 2 is 0, the emergency stop mode (ZONE9) becomes active.
To perform output in this state, set either of the following:
• ILST (initial forecast value)=0
• PLST (pre-batch setpoint)=0
This eliminates the mode of ZONE1 or 5 and sets the command switch (SW) to “2” (restart
specification). As a result, the control step changes to ZONE3 and batch operation re-
sumes.
ON/OFF output method, when only switch instrument 1 is in the cascade (CAS) mode:
MV
100 %
50 %
0%
BSETU-2/ ZONE 0 1 9 3 9 3 7
BSETU-3
Switch instrument MODE CAS

1 MV 0 2 0 2 0
Switch instrument MODE CAS Other than CAS

2 MV 0 2 0/2 (No output from the BSETU-2/BSETU-3)
LIST=PLST=0. Set SW=2.
Switch instrument 2 changes to a non-CAS mode

D012009E.EPS
Figure Example of Batch Operation when Only Switch Instrument 1 is in Cascade (CAS) Mode
● Actions when Neither Switch Instrument is in Cascade (CAS) Mode

When neither switch instrument is in the cascade (CAS) mode, the Flow/Weight-Totalizing
Batch Set Block (BSETU-2, BSETU-3) enters the initialization manual (IMAN) mode. In this
mode, the MV value of the switch instrument is set as the MV of the Flow/Weight-Totalizing
Batch Set Block (BSETU-2, BSETU-3) after having been converted via the output value
tracking function.

■ Emergency Stop when an Alarm Occurs
▼ Emergency Stop when Input Open, Emergency Stop when Low-Low Alarm, Emergency Stop
when High Alarm, Emergency Stop when Low Alarm, Emergency Stop when Missing Pulse
The batch operation can be set to the emergency stop state when an alarm occurs. Emer-
gency stop execution can be specified for the alarms indicated below:
• Input open alarm (IOP, IOP-)
• Input low-low limit alarm (LL)
• Input high limit alarm (HI)
• Input low limit alarm (LO)
• Missing pulse alarm (NPLS) (*1)
The setting for whether the batch operation comes to an emergency stop or continues
when an alarm occurs is performed for each alarm using the Function Block Detail Builder.
The setting selections are “Yes” or “No.” When “Yes” is selected, the operation performs an
emergency stop when an alarm occurs. When “No” is selected, there is no emergency stop
and the batch operation continues. Default settings are given below:
• Emergency Stop When Input Open: The default is “Yes”
• Emergency Stop When Low-Low Alarm: The default is “No.”
• Emergency Stop When High Alarm: The default is “No.”
• Emergency Stop When Low Alarm: The default is “No.”
• Emergency Stop When Missing Pulse: The default is “Yes.” (*2)
*1: The missing pulse alarm (NPLS) is available only for BSETU-2, but not for BSETU-3.
*2: Emergency Stop When Missing Pulse is available only for BSETU-2, but not for BSETU-3.
SEE ALSO
• See chapter C5, “Alarm Processing - FCS” for more details on the input open, input low-low limit, input
high limit and input low limit alarms.
• See chapter D1.21, “Flow-Totalizing Batch Set Block (BSETU-2)” for the details of the missing pulse
alarm.


the value at the connected destination, even when the initialization manual (IMAN) mode is
changed to manual (MAN), the initialization manual (IMAN) mode will precede the manual
(MAN) mode and any operation to change to the manual (MAN) mode will become invalid.
However, if try to change a block mode in the initialization manual (IMAN) mode, the block
will switch to that mode only when the initialization condition vanishes.

vanishes:
AUT
IMAN (AUT)
AUT

block (SW-33, SW-91) and the switches off the cascade connection.
output and a failure or output open alarm is detected in the process output.

■ MAN Fallback
fallback condition is established. In the Flow-Totalizing Batch Set Block (BSETU-2), the
emergency stop action triggered by an input open alarm will override the MAN fallback
action only when input open emergency stop is defined “Yes” in the function block builder.
When an input open alarm occurs, the emergency stop (EMST) mode becomes active and
the manipulated output value (MV) drops to the manipulated output scale low limit (MSL).
Once the emergency stop action is completed, the MAN fallback action is executed and the
block mode changes to manual (MAN) mode.
● Characteristics of MAN Fallback

state.

AUTAMAN
The MAN fallback condition is established in the following situations:

(CAL).

The block mode change interlock function stops the control computation processing of
function blocks that are operating automatically, while disabling the currently stopped
function blocks from changing to an automatic operation state. This action takes place
when the block mode change interlock condition is established.

• Any block mode change command to obtain an automatic operation state (AUT mode)
becomes invalid.


D1.20.3 Output Processing of Totalizing Batch Set Blocks

(BSETU-2, BSETU-3)
The BSET-2 and BSETU-3 blocks perform a special output signal conversion.
This section describes the output signal conversion, using the BSETU-2 block as an
example.
■ Output Signal Conversion of the Flow/Weight-Totalizing Batch Set Block

(BSETU-2 and BSETU-3)
The types of output signal processing available in the BSETU-2 and BSETU-3 blocks are
analog output, data set output for other function block, subsystem output, and 2-position/3-
position ON/OFF output. Pulse width output is not available.
Not only the process I/O contact output but also Switch Instrument blocks can be used as
the destination of 2-position/3-position ON/OFF output.
The following list shows the Switch Instrument block that may be connected to BSETU-2
and BSETU-3. Switch Instrument block with two status output can not be connected.
• SIO-11
• SIO-21
• SO-1
• SIO-12P
• SIO-22P

● Connecting a 2-Position ON/OFF Output to a Contact Output
The following figure illustrates the connection of an I/O contact output to the output terminal
(OUT) of the BSETU-2 block:
IN BSETU-2 OUT
D012010E.EPS
Figure An Example of 2-Position ON/OFF Output
The following table shows the relationship between the manipulated output value (MV) in
the manual operating mode and the contact output status:
Table Relationship between the MV and the Contact Output Status in Manual Mode
MV value 0 to 49.9 % 50 to 100 %
Contact output OFF ON
D012011E.EPS
MV
100
2-position
ON/OFF
0
D012012E.EPS
Figure Simplified Batch Operation of the 2-Position ON/OFF Output System

● Connecting a 3-Position ON/OFF Output to Contact Outputs
The following figure illustrates the connection of the I/O contact outputs to the output
terminals (OUT and OUT2) of the BSETU-2 block:
IN BSETU-2 OUT
OUT2
D012013E.EPS
the manual operating mode and the contact outputs status:
Table Relationship between the MV and the Contact Output Status in Manual Mode
MV value 0 to 24.9 % 25 to 74.9 % 75 to 100 %
Contact output 1 OFF OFF ON
Contact output 2 OFF ON ON
D012014E.EPS
MV
100
3-position
ON/OFF
0
D012015E.EPS
Figure 3-Position ON/OFF Output

● 2-Position ON/OFF Output Connected to a Switch Instrument in
Cascade
The following figure illustrates the connection of a 2-position ON/OFF output to a switch
instrument in cascade. In this example, the switch instrument CSV is connected to the
output terminal (OUT) of the Flow-Totalizing Batch Set Block (BSETU-2) in cascade.
IN OUT
BSETU-2
IN CSV OUT
SIO-11
D012016E.EPS
the manual operating mode and the switch instrument status:
Table Relationship between the MV of 2-Position ON/OFF Block and the MV of the Switch
Instrument Block
MV value 0 to 49.9 % 50 to 100 %
Switching instrument MV=0 MV=2
D012017E.EPS
When the connected switch instrument is in the cascade (CAS) mode, the BSETU-2 block
outputs a manipulated output value (MV) to the sequence setpoint value (CSV) of the
switch instrument, and the instrument will output the sequence setpoint value (CSV) as its
own manipulated output value (MV). If the switch instrument is not in the cascade (CAS)
mode, the BSETU-2 block will be in the initialization manual mode (IMAN). Then, the switch
instrument manipulated output value (MV) converted to the manipulated output value (MV)
data of the BSETU-2 block will be set as the manipulated output value (MV) of the BSETU-
2 by the output tracking function. Even when connected to a switch instrument block, the
automatic prediction is still functioning to close the valve.

● 3-Position ON/OFF Output Connected to a Switch instrument in Cascade
The following figure illustrates the connection of the 3-position ON/OFF output to a switch
instrument in cascade. In this example, the switch instrument CSV is connected to the
output terminals (OUT or OUT2) of the Flow-Totalizing Batch Set Block (BSETU-2) in
cascade. In the case of 3-position ON/OFF output, Switch Instrument Block with 1 Output
(SO-1) and Switch Instrument Block with 1 Output (SO-1) are connected to the OUT and
OUT2 terminals, respectively.
OUT
IN
BSETU-2 OUT2
CSV OUT CSV OUT

SO-1 SO-1
D012018E.EPS
the manual operating mode and the switch instrument status:
Table Relationship between the MV of 3-Position ON/OFF Block and the MV of the Switch
Instrument Block
MV value 0 to 24.9 % 25 to 74.9 % 75 to 100 %
Switching instrument 1 MV=0 MV=0 MV=2
Switching instrument 2 MV=0 MV=2 MV=2
D012019E.EPS
When both of the connected switch instruments are in the cascade (CAS) mode, the
BSETU-2 block outputs two manipulated output values (MV) to the sequence setpoint
values (CSV) of the switch instrument 1 and 2, respectively, and the individual instruments
will output their sequence setpoint value (CSV)’s as their own manipulated output value
(MV)’s, respectively. If neither of the switch instruments is in the cascade (CAS) mode, the
BSETU-2 block will be in the initialization manual mode (IMAN). Then, the switch instru-
ment manipulated output value (MV) converted to the manipulated output value (MV) data
of the BSETU-2 block will be set as the manipulated output value (MV) of the BSETU-2 by
the output tracking function.

D1.20.4 Alarm Processing of Totalizing Batch Set Blocks

(BSETU-2, BSETU-3)
The alarm checks commonly performed by and specific to the BSETU-2 and BSETU-
3 blocks are as follows:
• Cumulative deviation high and low limit check
■ Pre-Batch Alarm Check

▼ Pre-Batch Alarm
The pre-batch alarm check is a function that determines if the integral value (SUM) has
reached a value (BSET-PLST) obtained by subtracting the pre-batch setpoint value (PLST)
from the batch setpoint value (BSET).
If it is determined that the integral value (SUM) has reached a value (BSET-PLST) obtained
by subtracting the pre-batch setpoint value (PLST) from the batch setpoint value (BSET), a
pre-batch alarm (BPRE) is activated.
To enable the pre-batch alarm function, set the alarm detect as “enabled” in the Function
The pre-batch alarm can be set with the Function Block Detail Builder.
• Pre-batch alarm: Select from “enabled” and “disabled”
Default is “disabled.”
■ Batch End Alarm Check

▼ Batch End Alarm
The batch end alarm check is a function that determines if the integral value (SUM) has
reached a value (BSET-LPV) obtained by subtracting the leakage predictive value (LPV)
from the batch setpoint value (BSET).
If it is determined that the integral value (SUM) has reached a value (BSET-LPV) obtained
by subtracting the leakage predictive value (LPV) from the batch setpoint value (BSET), a
batch end alarm (BEND) is generated.
To enable the batch end alarm check, set the alarm detect as “enabled” in the Function
The batch end alarm can be set with the Function Block Detail Builder.
• Batch end alarm: Select from “enabled” and “disabled”

■ Cumulative Deviation High and Low Limit Check
▼ Accumulated Deviation High/Low Limit Alarm
The cumulative deviation high and low limit check is a function that determines whether the
deviation (SUM-BSET) between the integral value (SUM) and batch setpoint value (BSET)
falls outside the range of the absolute value of the cumulative deviation alarm setpoint
value (DL).
If it is determined that the deviation exceeds the cumulative deviation alarm setpoint value
(DL) in the positive direction, a cumulative deviation high limit alarm (BDV+) occurs. Simi-
larly, if it exceeds the DL in the negative direction, a cumulative deviation low limit alarm
(BDV-) occurs. These alarms are checked upon batch completion (transits from ZONE7 to
ZONE0) and are maintained as long as the control step is ZONE0 (batch stopped status).
However, when a reset (SW=3) is done, the alarm check is not performed.
To activate the cumulative deviation high and low limit alarm check, set the type of cumula-
tive deviation high and low limit alarm check and the cumulative deviation high and low limit
alarm check setpoint value (DL).
● Cumulative Deviation High and Low Limit Alarm Check Type

The type of cumulative deviation high and low limit alarm is set by the “cumulative deviation
high and low limit alarm” item in the Function Block Detail Builder. The types of cumulative
deviation high and low limit alarms are given below. The default is “high and low limit
alarm.”
• High and low limit alarm: Monitors the deviation for both the high and low limits
• High limit only: Monitors the deviation for the high limit only
• Low limit only: Monitors the deviation for the low limit only
• No alarm: No detection is performed
When single direction is specified for the cumulative deviation high and low limit alarm type,
only the cumulative deviation high limit alarm is monitored when the cumulative deviation
alarm setpoint (DL) has a plus sign, and only the low limit alarm is monitored when the
setpoint has a minus sign.
● Cumulative Deviation Alarm Setpoint (DL)

The cumulative deviation alarm setpoint (DL) is set by the operation and monitoring func-
tion. The cumulative deviation alarm setpoint (DL) can changed as setting parameters.
• Cumulative deviation alarm setpoint (DL): Same unit data as SUM
• Number of digits for the setting: Maximum 4 digits
Default is 1000.

■ Leak Alarm Check
▼ Leak Check
The leak alarm check is a function that compares the integral value and the previous
integral value at the time of batch completion (saved when batch is completed) and deter-
mines whether the difference exceeds the leak setpoint value (LK).
If it is determined that the difference exceeds the leak setpoint value (LK), a leak alarm
(LEAK) occurs. Flowrate accumulation is being performed from the time the batch is
completed until the next batch starts.
• Flow-Totalizing Batch Set Block (BSETU-2)
For the BSETU-2 block, the leak alarm check is performed only for an increase (the
difference is a positive number).
• Weight-Totalizing Batch Set Block (BSETU-3)
For the BSETU-3 block, the leak alarm check is performed for both an increase (the
difference is a positive number) and decrease (the difference is a minus number).
However, the alarm status will be leak alarm (LEAK) whether the leak is an increase or
a decrease.
To activate the leak alarm check, set whether the leak alarm check is enabled or disabled
and the leak setpoint value (LEAK).
● Leak Alarm Enabled/Disabled

The leak alarm can be set with the Function Block Detail Builder.
• Leak alarm: Select from “enabled” and “disabled”
● Leak Setpoint (LK)

The leak setpoint is set by the operation and monitoring function.
• Leak setpoint (LK): Same unit data as SUM
Maximum 4 digits
Default is 100.

<Toc> <Ind> <D1.21 Flow-Totalizing Batch Set Block (BSETU-2)> D1-305
D1.21 Flow-Totalizing Batch Set Block (BSETU-2)

The Flow-Totalizing Batch Set Block (BSETU-2) totalizes flowrate signals and out-
puts the manipulated output value in accordance with the totalized value. This block
is used for batch control, such as batch shipment control of products and batch
charge control of raw materials.
■ Flow-Totalizing Batch Set Block (BSETU-2)

▼ Connection
The Flow-Totalizing Batch Set Block (BSETU-2) totalizes flowrate signals and outputs the
manipulated output value (MV) in accordance with the totalized value.
The Flow-Totalizing Batch Set Block (BSETU-2) changes the output to 0 % when the
totalized value reaches the batch setpoint.
The Flow-Totalizing Batch Set Block (BSETU-2) enables batch control, such as batch
shipment control of products and batch charge control of raw materials.
The figure below shows a function block diagram of Flow-Totalizing Batch Set Block
(BSETU-2):
ZONE SW EMSW
Input AUT Output

IN PV Batch MV OUT
set pattern
MAN OUT2
SUM
INT D012101E.EPS
Figure Function Block Diagram of Flow-Totalizing Batch Set Block (BSETU-2)

The figure below shows an example of simple batch shipment control:
IN BSETU-2 OUT
D012102E.EPS
Figure Example of Simple Batch Shipment Control
The figure below shows an example of batch shipment control where flow velocity is PID
controlled in combination with other function blocks:
IN BSETU-2 OUT
SET
IN PID OUT
D012103E.EPS
Figure Example of Batch Shipment Control
The figure below shows an example of batch blend control:
J01 FOUT BSETU-2

SET OUT IN
J02
IN RATIO OUT IN RATIO OUT
SET SET
IN PI-BLEND OUT IN PI-BLEND OUT
D012104E.EPS
Figure Example of Batch Blend Control

terminals of the Flow-Totalizing Batch Set Block (BSETU-2):
Table Connection Methods and Connected destinations of the I/O Terminals of Flow-Totalizing
Batch Set Block (BSETU-2)
Manipulated output
OUT2
(*1)
INT Interlock SW output
D012105E.EPS
*1: The OUT2 terminal is used when connecting a 3-position ON/OFF output to switch instruments 1 and 2, for connection
to switch instrument 2.
● OUT Terminal Manipulated Output

The OUT terminal outputs the manipulated output signals indicated below:
• Analog output
• Output to other function blocks
• Contact outputs for 2-position ON/OFF output and 3-position ON/OFF output
• Data setting to the 2-position ON/OFF output switch instrument
• Data setting to switch instrument 1 when the 3-position ON/OFF output is connected
to switch instruments 1 and 2.
● OUT2 Terminal Manipulated Output

The OUT2 terminal outputs the data set to switch instrument 2 when the 3-position ON/
OFF output is connected to switch instruments 1 and 2.

■ Function of Flow-Totalizing Batch Set Block (BSETU-2) ¡ £
The BSETU-2 block performs input processing, control computation processing, output
The only processing timing available for the BSETU-2 block is a periodic startup. Selec-
SEE ALSO
• For the functions common to the BSETU-2 and BSETU-3 blocks, see a chapter D1.20, “Totalizing Batch
Set Blocks (BSETU-2, BSETU-3).”
• For the types of input processing, output processing, and alarm processing possible for the BSETU-2
block, see a chapter D1.1.3, “Input Processing, Output Processing, and Alarm Processing Possible for
● Control Computation Processing of Flow-Totalizing Batch Set Block

(BSETU-2)
The table below shows the control computation processing functions of the Flow-Totalizing
Batch Set Block (BSETU-2).
Table Control Computation Processing Functions of Flow-Totalizing Batch Set Block (BSETU-2)
Performs batch operation in accordance with the type of output (analog output, two-
Batch operation
position ON/OFF output or three-position ON/OFF output).
MAN fallback place when the MAN fallback condition becomes satisfied. However, the emergency stop
action precedes when an input open alarm has occurred.
D012106E.EPS
SEE ALSO
For details on the control computation processing of the BSETU-2 block, see chapter D1.20.2, “Control
Algorithm of Totalizing Batch Set Blocks (BSETU-2, BSETU-3).”
● Alarm Processing Specific to Flow-Totalizing Batch Set Block (BSETU-2)

The “missing pulse alarm check” and “flowrate alarm check,” which are two of the alarm
checks performed by the BSETU-2 block, are specific to this function block.
In addition, the BSETU-2 block uses a unique alarm display priority order, which is different
from that of other function blocks.

■ Missing Pulse Alarm Check
▼ Missing Pulse
The missing pulse alarm check is a function that determines whether a pulse input for a set
duration is detected during pulse input detection.
If it is determined that when a pulse input is not detected for the set duration during pulse
input detection, a missing pulse alarm (NPLS) is generated. This check is performed during
each missing pulse check time (t3) after the missing pulse check mask interval (t2) has
elapsed and only when the control step is 1, 2, 3, 4 or 5.
The figure below illustrates the timing of the BSETU-2 block alarm check.
MV
MH
PRE
ML
Block
NCNT IBCH STUP STDY EMST EEMS STUP STDY ERLY PBCH END
status
ZONE 0 1 2 3 8 9 2 3 4 5 7
LO t1 t1
HI/LL t1 t1
NPLS t2 t2
t3
: Alarm check period LO : Low limit alarm

t1 : Flowrate check mask interval HI : High limit alarm
t2 : Missing pulse check mask interval LL : Low-low limit alarm
t3 : Missing pulse check time NPLS : Missing pulse warning
: Missing pulse check timing
D012107E.EPS
Figure Alarm Check Timing

To activate the missing pulse alarm, set whether the missing pulse alarm check is enabled
or disabled, the missing pulse check mask interval, and the missing pulse check time.
● Missing Pulse Alarm Check Enabled/Disabled

The missing pulse alarm can be set with the Function Block Detail Builder.
• Missing pulse alarm: Select from “enabled” and “disabled”
● Missing Pulse Check Mask Interval

The missing pulse check mask interval can be set with the Function Block Detail Builder.
• Missing pulse check mask interval: 0 to 10000
Unit is the scan period
Default is 5.
● Missing Pulse Check Time

The missing pulse check time can be set with the Function Block Detail Builder.
• Missing pulse check time: 0 to 10000
Unit is the scan period
Default is 1.

■ Flowrate Alarm Check
▼ Flow Check Mask Interval
The flowrate checks take place upon expiration of the flowrate check masking interval (t1),
as shown in Figure below. Specify the masking interval with the Function Block Detail
Builder.
• Flowrate check masking interval: 0 to 10000
(in the scan period unit)
The default is 10.
The flowrate alarm check processing timing of BSETU-2 block is shown below.
MV
MH
PRE
ML
Block
status
ZONE 0 1 2 3 8 9 2 3 4 5 7
LO t1 t1
HI/LL t1 t1
: Alarm check period LO : Low-limit alarm

t1 : Flowrate check masking interval HI : High-limit alarm
LL : Low-low limit alarm
D012108E.EPS
Figure Flowrate Check Processing Timing

The flowrate alarm check in the BSETU-2 block consists of the low-low limit check and the
high-low limit check.
● Low-Low Limit Alarm

A low-low limit alarm (LL) is generated if the flowrate (PV) falls below the low-low limit alarm
setpoint (LL). This check operates in control steps 1, 2, 3, 4, and 5.
● Low-Limit Alarm
A low-limit alarm (LO) is generated if the flowrate (PV) falls below the low-limit alarm
setpoint (PL). This check operates only in control step 3.
● High-Limit Alarm
A high-limit alarm (HI) is generated if the flowrate (PV) exceeds the high-limit alarm setpoint
(PH). This check operates in control steps 1, 2, 3, 4, and 5.

■ Alarm Display Priority of the Flow-Totalizing Batch Set Block (BSETU-2)
The following is the order for the alarm display priority specific to the BSETU-2 block:
OOP>IOP>IOP->NPLS>LL>HI>LO>LEAK>BDV+>BDV->BEND>BPRE>CNF
When there are absolutely no alarms generated, the alarm status is NR.
Table Alarm Check for the Control Steps (ZONE) of the Flow-Totalizing Batch Set Block
ZONE
Alarm
0 1 2 3 4 5 6 7 8 9 10 11
IOP
IOP-
OOP
CNF
LL - - - - - - -
HI - - - - - - -
LO - - - - - - - - - - -
BDV + - - - - - - - - - - -
BDV- - - - - - - - - - - -
LEAK - - - - - - - - - - -
NPLS - - - - - - -
BPRE
BEND
D012109E.EPS
: Alarm check is executed for the ZONE.

: Alarm check is executed only once when ZONE=7 changes to ZONE=0.
-: Alarm check is not executed for the ZONE.
The alarm is set to normal state (NR).
: Alarm check is not executed and the status prior to ZONE=0 is retained.
SEE ALSO
Refer to section “■ Batch Operation (Analog Output)” in chapter D1.20.2, “Control Algorithm of Totalizing
Batch Set Block (BSETU-2, BSETU-3)” for information on operation of the control steps for the BSETU-2
block.

■ Data Items - BSETU-2
Table Data Items of Flow-Totalizing Batch Set Block (BSETU-2) (1/2)
Item or Not
BSTS Block status ----- NCNT
PV Flowrate process variable (*1) PV engineering unit value SL
SUM Totalizer value SUM engineering unit value 0
SUM1 Cumulative totalized value Value in the same engineering unit as SUM 0
SW Command switch 0, 1, 2, 3, 4 0
DL Cumulative deviation alarm setpoint Value in the same engineering unit as SUM 1000
D012110E.EPS

SEE ALSO
For a list of valid block modes of the BSETU-2 block, see a chapter D1.1.4, “Valid Block Modes for Each

Table Data Items of Flow-Totalizing Batch Set Block (BSETU-2) (2/2)
Item or Not
MH High flowrate setpoint MSL to MSH MSH
ML Low flowrate setpoint MSL to MSH MSL
PRE Pre-batch flowrate setpoint MSL to MSH MSL
LPV Leakage predictive value Value in the same engineering unit as SUM 0
ILST Initial forecast value Value in the same engineering unit as SUM 0
PLST Pre-batch setpoint Value in the same engineering unit as SUM 0
BSET Batch setpoint Value in the same engineering unit as SUM 0
LK Leak setpoint Value in the same engineering unit as SUM 100
TU Up time 0 to 10,000 seconds 0 second
TD Down time 0 to 10,000 seconds 0 second
TW Batch end wait time 0 to 10,000 seconds 0 second
ZONE Control step 0 to 11 0
EMSW Emergency stop switch 0, 1 0
D012111E.EPS

SUM: Totalizer value
■ Block Status of Flow-Totalizing Batch Set Block (BSETU-2)

Table Block Status of Flow-Totalizing Batch Set Block (BSETU-2)
Block Status
Level
Symbol Name
STRT Batch Start
IBCH Batch Initialization
STUP Batch Setup
STDY Ready
ERLY Early
PBCH Pre-Batch
1
END Batch End
NCNT Batch Stopped
RSET Reset
EMST Emergency Shutdown
EEMS Emergency Shutdown Completed
RSTR Restart
D012113E.EPS

<Toc> <Ind> <D1.22 Weight-Totalizing Batch Set Block (BSETU-3)> D1-316
D1.22 Weight-Totalizing Batch Set Block (BSETU-3)

The Weight-Totalizing Batch Set Block (BSETU-3) calculates a totalized value of
changes in weight signals sent from a scale, and outputs the manipulated output
value in accordance with the totalized value. This block is used for batch control,
such as batch shipment control of products and batch charge control of raw materi-
als.
■ Weight-Totalizing Batch Set Block (BSETU-3)

▼ Connection
The Weight-Totalizing Batch Set Block (BSETU-3) calculates a totalized value of changes
in weight signals sent from the scale, and outputs the specified manipulated output value in
accordance with the totalized value.
The Weight-Totalizing Batch Set Block (BSETU-3) changes the output to 0 % when the
totalized value reaches the batch setpoint.
The Weight-Totalizing Batch Set Block (BSETU-3) enables batch control, such as batch
shipment control of products and batch charge control of raw materials.
The figure below shows a function block diagram of Weight-Totalizing Batch Set Block
(BSETU-3):
ZONE SW EMSW
IN
IN2 AUT
Input Output
PV Batch MV OUT
IN3 set pattern
MAN OUT2
IN4
SUM0
SUM
INT D012201E.EPS
Figure Function Block Diagram of Weight-Totalizing Batch Set Block (BSETU-3)

terminals of the Weight-Totalizing Batch Set Block (BSETU-3):
Table Connection Methods and Connected destinations of the I/O Terminals of Weight-Totalizing
Batch Set Block (BSETU-3)
IN Analog input
IN2 Digital input
IN3 Sign bit input
IN4 Ready bit input
Manipulated output
OUT2
(*1)
D012202E.EPS
*1: The OUT2 terminal is used when connecting a 3-position ON/OFF output to switch instruments 1 and 2, for connection
to switch instrument 2.
● IN Terminal Analog Input

If the weight signal from a scale is a analog signal, connect the weight signal to the IN
terminal via an analog process I/O module of process I/O. When reading weight data from
other function blocks, also connect the weight signal to the IN terminal.
● IN2 Terminal Digital Input

If the weight signal from the scale is a digital datum that satisfy the following conditions,
connect it to the IN2 terminal via a contact module of process I/O.
Also use the IN2 terminal when inputting digital data of weight signals that satisfy the above
condition, from a software I/O.
Number of bits: 32 bits or less
Code: Binary or BCD
● IN3 Terminal Sign Bit Input

Connect the sign bit of weight signal digital data to the IN3 terminal.
The sign bit indicates the sign of data. The length of this bit is 1 bit. “0” and “1” indicate
positive and negative, respectively.

● IN4 Terminal Ready Bit Input
The ready bit transmits the timing of when the weight signals sent as digital data can be
read. The length of this bit is 1 bit.
Connect the ready bit to the IN4 terminal.
Use the Function Block Detail Builder to define the control action direction of the ready bit.
• Ready-bit Action Direction: Select “Direct” or “Reverse.”
The default is “Direct.”
The table below shows actions of the IN4 terminal ready bit input:
Action
Ready bit Status
specification
0 Preparing data
Direct action
1 Read ready
0 Read ready
Reverse action
1 Preparing data
D012203E.EPS
● OUT Terminal Manipulated Output

The OUT terminal outputs the following manipulated output signals:
• Analog output
• Output to other function blocks
• Contact output of a 2-position or 3-position ON/OFF output
• Data setting of a 2-position ON/OFF output to the switch instrument
• Data setting to switch instrument 1, when a 3-position ON/OFF output is connected to
switch instruments 1 and 2.
● OUT2 Terminal Manipulated Output

The OUT2 terminal transmits data setting output to switch instrument 2, when a 3-position
ON/OFF output is connected to switch instruments 1 and 2.

■ Function of Weight-Totalizing Batch Set Block (BSETU-3) ¡ £
The BSETU-3 block performs input processing, control computation processing, output
The only processing timing available for the BSETU-3 block is a periodic startup. Selec-
SEE ALSO
• For the functions common to the BSETU-2 and BSETU-3 blocks, see chapter D1.20, “Totalizing Batch
Set Blocks (BSETU-2, BSETU-3).”
• For the types of input processing, output processing, and alarm processing possible for the BSETU-3
block, see chapter D1.1.3, “Input Processing, Output Processing, and Alarm Processing Possible for Each
● Input Processing Specific to Weight-Totalizing Batch Set Block (BSETU-3)

The BSETU-3 block performs special input signal conversions.
● Control Computation Processing of Weight-Totalizing Batch Set Block

(BSETU-3)
The table below shows the control computation processing functions of the Weight-Totaliz-
ing Batch Set Block (BSETU-3).
Table Control Computation Processing of Weight-Totalizing Batch Set Block (BSETU-3)
Performs batch operation in accordance with the type of output (analog output, two-
Batch operation
position ON/OFF output or three-position ON/OFF output).
MAN fallback place when the MAN fallback condition becomes satisfied. However, the emergency stop
action precedes when an input open alarm has occurred.
D012204E.EPS
SEE ALSO
For details on the control computation processing of the weight-totalizing batch set block (BSETU-3), see
chapter D1.20.2, “Control Algorithm of Totalizing Batch Set Blocks (BSETU-2, BSETU-3).”

● Alarm Processing Specific to Weight-Totalizing Batch Set Block (BSETU-3)
The “flowrate alarm check,” which is one of the alarm checks performed by the BSETU-3
block, is specific to this function block.
In addition, the BSETU-3 block uses a unique alarm display priority order, which is different
from that of other function blocks.
■ Data Items - BSETU-3

Table Data Items of Weight-Totalizing Batch Set Block (BSETU-3) (1/2)
Item or Not
BSTS Block status ----- NCNT
AF Alarm detection specificaton ----- 0
PV Flowrate process variable PV engineering unit value SL
SUM Totalizer value SUM engineering unit value 0
SUM0 Absolute totalized value Value in the same engineering unit as SUM 0
SUM1 Cumulative totalized value Value in the same engineering unit as SUM 0
SW Command switch 0, 1, 2, 3, 4 0
DL Cumulative deviation alarm setpoint Value in the same engineering unit as SUM 1000
D012205E.EPS

SEE ALSO
For a list of valid block modes of the BSETU-3 block, see a chapter D1.1.4, “Valid Block Modes for Each

Table Data Items of Weight-Totalizing Batch Set Block (BSETU-3) (2/2)
Item or Not
MH High flowrate setpoint MSL to MSH MSH
ML Low flowrate setpoint MSL to MSH MSL
PRE Pre-batch flowrate setpoint MSL to MSH MSL
LPV Leakage predictive value Value in the same engineering unit as SUM 0
ILST Initial forecast value Value in the same engineering unit as SUM 0
PLST Pre-batch setpoint Value in the same engineering unit as SUM 0
BSET Batch setpoint Value in the same engineering unit as SUM 0
LK Leak setpoint Value in the same engineering unit as SUM 100
TU Up time 0 to 10,000 seconds 0 second
TD Down time 0 to 10,000 seconds 0 second
TW Batch end wait time 0 to 10,000 seconds 0 second
ZONE Control step 0 to 11 0
EMSW Emergency stop switch 0, 1 0
D012206E.EPS

SUM: Totalizer value
■ Block Status of Weight-Totalizing Batch Set Block (BSETU-3)

Table Block Status of Weight-Totalizing Batch Set Block (BSETU-3)
Block Status
Level
Symbol Name
STRT Batch Start
IBCH Batch Initialization
STUP Batch Setup
STDY Ready
ERLY Early
PBCH Pre-Batch
1
END Batch End
NCNT Batch Stopped
RSET Reset
EMST Emergency Shutdown
EEMS Emergency Shutdown Completed
RSTR Restart
D012207E.EPS

D1.22.1 Input Signal Conversion of Weight-Totalizing Batch Set

Block (BSETU-3)
The input signal conversion specific to the Weight-Totalizing Batch Set Block
(BSETU-3) includes three types of methods: “Weight Measurement Conversion,”
“SUM Conversion” and “SUM Conversion.”
■ Input Signal Conversion of Weight-Totalizing Batch Set Block (BSETU-3)

Shown below is the block chart for the input signal conversion of the Weight-Totalizing
Batch Set Block (BSETU-3).
Weight SUM conversion

IN measurement Measurement in the
CAL CAL incremental direction SUM
conversion
SUM = conversion
IN2 Digital
SUM0= SUM0 SUM0 - (zero point) SUM SUM PV
filter
volume unit calculation
IN3 conversion factor Measurement in the
decremental direction
x input data SUM = SUM1
IN4 (zero point) - SUM0
SUM0: absolute integrator value SUM: integrator value SUM1: cumulative integrator value
D012208E.EPS
Figure Block Chart for Input Signal Conversion of Weight-Totalizing Batch Set Block (BSETU-3)
As shown in above figure, the combination of input signal conversion includes the following
three types
• Weight Measurement Conversion
• SUM Conversion
• SUM Conversion

■ Weight-Totalizing Conversion
Weight-Totalizing Conversion refers to the processing in which the weight input data read
from a weighing machine are converted into the data in the same unit as the integrator
value (SUM) to obtain the absolute integrator value (SUM0).
The following is the computational expression for the absolute integrator value (SUM0):
SUM0 = quantity unit scale factor • input data
● Quantity Unit Scale Factor

The quantity unit scale factor is the factor used to convert the input data into the data in the
same unit as integrator value (SUM). For example, if the unit of input data is “g” and that of
integrator value (SUM) is “kg,” the quantity unit scale factor is 0.001.
The setup for quantity unit scale factor can be executed with the Function Block Detail
Builder.
• Quantity unit scale factor: Within the range between 0.001 to 100000
The default setting is 1.
In the weight measurement conversion, the input data differs by the type of weight signal.
• If the weight signal is an analog signal, the input data is the 0 to 100 % data read from
the connection destination.
• If the weight signal is data read from the communication input, the input data is the
data after communication input conversion.
• If the weight signal is a digital signal, the input data can be obtained as follows:
When the ready bit is “Ready to Read,” the digital data and its sign bit are read for
each scan period and converted into the same format (double-precision floating-point)
as the absolute integrator value (SUM0) to obtain the input data.
If the ready bit is “Not Ready to Read,” the data setting for absolute integrator value
(SUM0) is bypassed while the previous value is latched.
SEE ALSO
For more information about communication input conversion of the weight-totalizing signals, see “■
Communication Input Conversion” in C3.1.1“Input Signal Conversions Common to Regulatory Control
Blocks and Calculation Blocks.”

● Code Conversion
Code conversion is a function that converts the weight signal digital data read from IN
terminal 2 to binary code data. The weight signal digital data that can be read by the
BSETU-3 block includes binary codes and binary coded decimal (BCD) codes. Specify
“No” when the weight signal is a binary code and “BCD” in the case of BCD code using the
Function Block Detail Builder, together with the number of code contacts.
• Number of Code Contacts:
Set by the unit of one bit within the range between 1 to 32 bits.
The default setting is 16 bits.
• Code Conversion:
Set “BCD” if the input signal is a binary-coded decimal code (BCD) or “No” if it is a
binary.
The default setting is “No conversion.”
● Weight-Totalizing Conversion Bypass

Under the following circumstances, the weight-totalizing conversion is bypassed.
• The input signal is digital type and the ready bit is in the status of “Not Ready to Read.”
• The data status of the absolute integrator value (SUM0) is not good (BAD or IOP).
When the weight-totalizing conversion is bypassed, the absolute integrator value (SUM0) is
not to be updated, the previous good value is kept.

■ SUM Conversion
▼ Input Change Protrusion Bypass
SUM conversion refers to the processing in which the integrator value (SUM) is obtained by
totalizing the increment or decrement of the absolute integrator value (SUM0) from the
batch start.
The following is the totalization formula for measurement in the incremental or decremental
direction:
• Measurement in the incremental direction: SUM=SUM0-zero point
• Measurement in the decremental direction: SUM=zero point-SUM0
The zero point refers to the absolute integrator value (SUM0) when the control step is 10
(initialization processing at batch start).
If the input change exceeds the input velocity limit setting value, it is considered as an
abnormal input signal so that the integrator value data setting is not executed and the
previous value is held. The data status, however, is not invalid in this case. The input
velocity alarm bypass setting is a value indicated by the process variable change in one
scan period. The basic scan period is 1 scan per 1 second.
The weight measurement direction specification, input velocity alarm bypass specification,
and the setting value for input velocity limit can be defined on the Function Block Detail
Builder.
• Weighing Direction:
Select “Increase” or “Decrease.”
The default setting is “Increase.”
• Input Velocity Alarm Bypass:
Select “Yes” or “No.”
The default setting is “No.”
• Setting value:
Set the value between 0 and 1000 in the same unit as SUM.
The cumulative integrator value (SUM1) is the accumulation of integrator values at the end
of batch. The cumulative integrator value (SUM1) is obtained at the end of each batch as
follows:
SUM1=SUM1 (cumulative integrator value kept at the end of the previous batch) +SUM
Under the following circumstances, the SUM conversion is bypassed.

When the SUM conversion is bypassed, the integrator value (SUM) is not to be updated,
the previous good value is kept.

■ SUM Conversion
▼ Flow Time Unit
SUM conversion refers to the function in which the integrator value variation in the speci-
fied time unit is passed to the digital filter. The value variation after digital filter processing is
the flow rate (PV). The following is the computational expression for the SUM.
(PV time unit)

SUM = (process variable change of SUM in one scan period) •
(scan period)
D012209E.EPS
The PV time unit and scan period in the above formula are in the unit of second.
The flow measurement time unit can be defined on the Function Block Detail Builder.
• Flow Time Unit: Select “Second,” “Minute,” “Hour” or “Day.”
The default setting is “Second.”
e.g. Select “Hour” for ton/h and “Minute” for kg/min.
Under the following circumstances, the input signal processing is bypassed.

In these cases, the flow rate value (PV) is not to be updated, the previous good value is
kept.

D1.22.2 Alarm Processing of Weight-Totalizing Batch Set Block

(BSETU-3)
This section describes the “flowrate alarm check,” which is one of the alarm checks
performed by the BSETU-3 block and is specific to this function block.
In addition, the BSETU-3 block uses a unique alarm display priority order, which is
different from that of other function blocks.
■ Flowrate Alarm Check

▼ Flow Check Mask Interval, Flow Check Time Interval, Input Low-Low Limit Alarm, PV High/Low
Limit Alarm
Low-low limit and high and low-limit checks are made upon expiration of a specified period
of time, as shown in Figure below. The specified period of time is called the flowrate check
masking interval. The checks are made by comparing the SUM change (SUM) for the
flowrate check time interval with an alarm setpoint.
Specify the flowrate check masking interval and the flowrate check time interval with the
• Flowrate check masking interval: 0 to 10000
10 is assumed by default.
• Flowrate check time interval: 0 to 10000
1 is assumed by default.

The flowrate alarm check processing timing of BSETU-3 block is shown below.
MV
MH
PRE
ML
Block
status
ZONE 0 1 2 3 8 9 2 3 4 5 7
LO t1 t1
HI/LL t1 t1
t2
: Alarm check period LO : Low-limit alarm

t1 : Flowrate check masking interval HI : High-limit alarm
t2 : Flowrate check time interval LL : Low-low limit alarm
: Check timing D012210E.EPS
Figure Flowrate Check Processing Timing

The flowrate alarm check in the BSETU-3 block consists of the low-low limit check and the
high-low limit check.
● Low-Low Limit Check

A low-low limit check (LL) is generated if the value of SUM in the flow check masking
interval converted to a flow measurement falls below the low-low limit alarm setpoint (LL).
This check is operable in control steps 1, 2, 3, 4, and 5.
SUM (PV time unit)

< LL A LL alarm
(Flowrate check time interval) (Scan period) D012211E.EPS
● Low-Limit Check
A low-limit alarm (LO) is generated if the value of SUM in the flow check masking interval
converted to a flow measurement falls below the low-limit alarm setpoint (PL). This check is
operable only in control step 3.
SUM (PV time unit)

< PL A LO alarm
● High-Limit Check
A high-limit alarm (HI) is generated if the value of SUM in the flow check masking interval
converted to a flow measurement exceeds the high-limit alarm setpoint (PH). This check is
operable in control steps 1, 2, 3, 4, and 5.
SUM (PV time unit)

> PH A HI alarm

■ Alarm Display Priority Specific to Weight-Totalizing Batch Set Block
(BSETU-3)
The following is the order for the alarm display priority specific to the BSETU-3 block:
OOP>IOP>IOP-> LL>HI>LO>LEAK>BDV+>BDV->BEND>BPRE>CNF
When there are absolutely no alarms generated, the alarm status is NR.
Table Alarm Check for the Control Steps (ZONE) of the Weight-Totalizing Batch Set Block
ZONE
Alarm
0 1 2 3 4 5 6 7 8 9 10 11
IOP
IOP-
OOP
CNF
LL - - - - - - -
HI - - - - - - -
LO - - - - - - - - - - -
BDV + - - - - - - - - - - -
BDV- - - - - - - - - - - -
LEAK - - - - - - - - - - -
BPRE
BEND
D012215E.EPS
: Alarm check is executed for the ZONE.

: Alarm check is executed only once when ZONE=7 changes to ZONE=0.
-: Alarm check is not executed for the ZONE.
The alarm is set to normal state (NR).
: Alarm check is not executed and the status prior to ZONE=0 is retained.
SEE ALSO
For the operation of each control step in the BSETU-3 block, see a section “■ Batch Operation (Analogue
Output)” in D1.20.2, “Control Algorithm of Totalizing Batch Set Blocks (BSETU-2, BSETU-3).”

<Toc> <Ind> <D1.23 Velocity Limiter Block (VELLIM)> D1-331
D1.23 Velocity Limiter Block (VELLIM)

The Velocity Limiter Block (VELLIM) outputs a change per unit time by limiting it
within the velocity limits. The Velocity Limiter Block may be applied to the control
process that the abrupt change need to be avoided.
■ Velocity Limiter Block (VELLIM)

▼ Connection
The Velocity Limiter Block (VELLIM) performs control computation processing to the
setpoint signals from other function blocks or setpoint values set by the operator, and
outputs a change per unit time by limiting it within the velocity limits. The velocity limiting
processing is executed in the cascade (CAS) or automatic (AUT) mode.
The Velocity Limiter Block (VELLIM) reads the abruptly changing manipulated output value
(MV) of other function blocks as a cascade setpoint signal, and outputs its change per scan
period as a manipulated output value (MV) by limiting it within the velocity limits. In the
automatic (AUT) mode, the block outputs a change per scan period in the setpoint value
(SV) received from outside, such as operation and monitoring functions, as a manipulated
output value (MV) by limiting it within the velocity limits. Separate velocity limits may be set
for upward and downward directions.
The figure below shows the function block diagram of Velocity Limiter Block (VELLIM):
SET INT
CAS
CSV
AUT
SV
MAN
RSV
RCAS
MAN
Velocity limiting AUT/CAS Output

BPSW MV OUT
computation processing
ROUT
(MV, MV) RMV
SUB
D012301E.EPS
Figure Function Block Diagram of Velocity Limiter Block (VELLIM)
terminals of the Velocity Limiter Block (VELLIM):
Table Connection Methods and Connected Destinations of I/O Terminals of Velocity Limiter Block
(VELLIM):
SET Setting input
D012302E.EPS

■ Function of Velocity Limiter Block (VELLIM) ¡ £
The VELLIM block performs control computation processing, output processing, and alarm
processing.
The only processing timing available for the VELLIM block is a periodic startup. Selections
SEE ALSO
• For the types of output processing and alarm processing possible for the VELLIM block, see chapter
D1.1.3, “Input Processing, Output Processing, and Alarm Processing Possible for Each Regulatory Con-
trol Block.”
● Control Computation Processing of Velocity Limiter Block (VELLIM)

The table below shows the control computation processing functions of the Velocity Limiter
Block (VELLIM):
Table Control Computation Processing Functions of Velocity Limiter Block (VELLIM)
Performs velocity limiting to the setpoint value (SV) and obtains a manipulated output
Velocity limiting computation
value (MV).
Performs range conversion to the manipulated output value (MV) based on the setpoint
Output pushback value range, and obtains a new setpoint value. This prevents the manipulated output value
from changing abruptly.
MAN fallback
Computer failure
becomes satisfied.
D012303E.EPS
● Alarm Processing Specific to Velocity Limiter Block (VELLIM)

The “deviation alarm check,” which is one of the alarm checks performed by the VELLIM
block, is specific to this function block.

■ Velocity Limiting Computation
This function executes velocity limiting computation to the setpoint value when the block
mode is automatic (AUT), cascade (CAS) or remote cascade (RCAS), and uses the com-
puted result as a manipulated output value (MV).
The velocity limiting computation action varies depending upon whether the rate of SV
change is below or on/over the velocity limits.
The figure below shows an action example of velocity limiting computation:
SV Converted upward velocity limit value (Dmp)

SV
MV
Converted downward velocity limit value (Dmm)

MV
Scan period Scan period Time
D012304E.EPS
Figure Action Example of Velocity Limiting Computation

▼ SV Range
Use the Function Block Detail Builder to set the setpoint value (SV) range:
• SV Range High Limit Value:
one digit each
The default is 100.0
• SV Range Low Limit Value:
one digit each
The default is 0.0.
● When the Rate of Setpoint Value Change Is BELOW the Velocity Limits
If the rate of SV change is below the velocity limits, the SV value receives velocity limiting
processing and is converted to an MV-range value to be used as an MV.
The computational expression of this velocity limiting computation is shown below:
MSH-MSL
MVc= • (SV-SSL)+MSL
MVn = MVc
MVc: Manipulated output computed value

MVn: Manipulated output current value

● When the Rate of Setpoint Value Change Is ON or OVER the Velocity
Limits
If the rate of SV change is on or over the velocity limits, the SV value receives velocity
limiting processing and is converted to an MV-range value to be used as a manipulated
output value. The computational expressions of this velocity limiting computation are
shown below:
MVn=MVn-1+Dmp (When MVDmp)
MVn=MVn-1+Dmp (When MV-Dmm)
MV=MVc-MVn-1
Dmp:
A per-scan rate-of-change value in the MV range, converted from the upward velocity limit
value (DMVP).
Dmp:
A per-scan rate-of-change value in the MV range, converted from the downward velocity
limit value (DMVM).
● Set Parameters of Velocity Limiting Computation

The parameters of velocity limiting computation:
When 1 is set for the velocity limiting bypass switch (BPSW), the velocity limiting bypass
function is enabled. If 0 is set for the BPSW, the velocity limiting bypass function is dis-
abled.
• Upward velocity limit value (DMVP) :
Set engineering unit data between 0 and the SV scale span range limit.
• Downward velocity limit value (DMVM):
Set engineering unit data between 0 and the SV scale span range limit.
• Velocity limiting time unit (TU):
Select “0 (1 second)” or “1 (1 minute).”
• Bypass switch (BPSW):
Select “0 (limited)” or “1 (not limited).” The default is “0.”

The control output action of Velocity limiter block is “positional type.” The result of velocity
limiting computation is output as the current manipulated output value (MV).

the setpoint high limit (SVH) and setpoint low limit (SVL), and recognizes setpoint values
(SV) within this range as a valid one.
function block.
● Setpoint Value Limiter in the Automatic (AUT) or Manual (MAN) Mode

• When a value exceeding the setpoint high limit (SVH) is set as the setpoint value (SV):
• When a value below the setpoint low limit (SVL) is set as the setpoint value (SV):
● Setpoint Value Limiter in the Remote Cascade (RCAS) Mode

When the block mode of the function block is remote cascade (RCAS) and the setpoint
value (SV) is set to automatically agree with the remote setpoint value (RSV) received from
the supervisory system computer, the setpoint value limiter performs the following actions:
• Limits a value exceeding the setpoint high limit (SVH) to the setpoint high limit (SVH).
• Limits a value below the setpoint low limit (SVL) to the setpoint low limit (SVL).

• Setpoint high limit (SVH): Engineering unit data within the SV scale range.
• Setpoint low limit (SVL): Engineering unit data within the SV scale range.

RSV CSV
AUT/MAN
RCAS CAS
SV
Setpoint value
Control
computation
D012306E.EPS
Figure Relationship Among Setpoint Values (SV, CSV and RSV)
function block.




▼ Output Pushback
The bumpless switching function switches the function block mode or switches the cascade
connected downstream block’s manipulated output value (MV) without causing its own
manipulated output value (MV) to change abruptly (i.e., bumpless switch).
status.
The type of bumpless switching performed by the Velocity Limiter Block (VELLIM) is “out-
put pushback.”
In the manual (MAN) or initialization manual (IMAN) mode, the output pushback function
sets as a setpoint value (SV), a SV-range value converted from the manipulated output
value (MV). Also, when the block mode is not remote output (ROUT) or off-service (O/S),
the remote manipulated output value (RMV) is caused to track the manipulated output
value (MV). The figure below shows the action of output pushback:
Output pushback
CAS
CSV
AUT
SV
MAN
RSV
RCAS
MAN
Velocity AUT/CAS Output

BPSW MV OUT
limiting processing
ROUT
RMV
D012307E.EPS
Figure Output Pushback
Use the Function Block Detail Builder to set the output pushback.
• Output pushback: Select “Yes” or “No.”

Using the output pushback function enables a balanceless bumpless switching of block
modes from manual (MAN) to automatic (AUT).
The following figure shows an example of bumpless cascade closing in a control loop:
PV MV
PID MAN
Output pushback
Output tracking
SV
MV
CAS
VELLIM AUT/MAN
Output tracking
SV
PV MV
PID
D012308E.EPS
Figure Output Pushback and Output Tracking When Cascade Is Open
1. When cascade connection is open, the output tracking function causes the manipu-
lated output value (MV) to track data of the output destination.
2. When cascade connection is closed, the output pushback function performs range
conversion to the manipulated output value (MV) and sets the result as the setpoint
value (SV).
3. The output value tracking function of the upstream block causes the output value of
the upstream function block to track the setpoint value (SV).
In this control loop, when cascade is closed the input value from the upstream function
block will agree with the data value at the output destination of the Velocity limiter block.
Therefore, output will not bump when cascade connection is closed.


changed to manual (MAN), the initialization manual (IMAN) mode will override the manual
(MAN) mode. In other words, any operation to change to the manual (MAN) mode be-
comes invalid.
The block returns to the original mode as soon as the initialization manual condition van-
ishes. However, if try to change block mode in the initialization manual (IMAN) mode, the
block only change to that mode when the initialization condition vanishes.

vanishes:
AUT
IMAN (AUT)
AUT

block (SW-33, SW-91) and cascade connection is switched is off (i.e., the cascade

■ MAN Fallback

state.

The following example shows when the MAN fallback condition is established and van-
ished:
AUTAMAN


■ AUT Fallback


cascade (CAS) to automatic (AUT) so that control can be continued using values set by the
operator. When this condition is established, it indicates that abnormality has been de-
tected in the cascade setpoint value for some reason.
vanishes:
CASAAUT
Use the Function Block Detail Builder to set whether or not to use the AUT fallback.
The AUT fallback condition is established when the AUT fallback is set as “Yes” via the
Function Block Detail Builder and the data status of the cascade setpoint value (CSV) has

■ Computer Fail

supervisory system computer via control bus communication.
change.
The following actions take place while the computer fail condition exists, the block mode
change command from MAN, AUT or CAS to RCAS or ROUT is sent:
1. When a block mode change command from MAN, AUT or PRD to RCAS or ROUT is
sent while the computer fails (BSW=ON), the function block does not switch to the
before the execution of the block mode change command (MAN, AUT, CAS) and a
remote mode (RCAS, ROUT).
(RCAS, ROUT).

RCAS
? Computer fails
AUT (RCAS)
? Computer recovers
RCAS
AUT
? ROUT command

tion block.
becomes down.


RCAS or ROUT mode) becomes invalid.


■ Deviation Alarm Check
▼ Deviation Alarm
The deviation alarm check in the VELLIM block is applicable to the deviation (DV) between
the manipulated output value (MV) converted to a value in the setpoint (SV) range and the
setpoint value (SV).
When the absolute value of the deviation (DV) exceeds the absolute value of the deviation
alarm setpoint (DL), either a positive direction deviation alarm (DV+) or a negative direction
deviation alarm (DV-) is generated. When an alarm has occurred, if the deviation (DV)
absolute value drops lower than the absolute value of the deviation alarm setpoint (DL)
minus the hysteresis value (HYS), the alarm is returned to normal state.
There is no deviation check filter function in the VELLIM block deviation alarm check.
The deviation (DV) that is subject to the deviation alarm check of the VELLIM block is
expressed in the following format.
DV=MVs-SV
SSHSSL
MVS = • (MVMSL)SSL
MSHMSL D012309E.EPS
MVs: Manipulated output value (MV) after conversion to the SV range

When the deviation (DV) absolute value exceeds the absolute value of the deviation alarm
setpoint (DL) and the deviation is for the positive direction, a positive direction deviation
alarm (DV+) occurs. If the deviation is for the minus direction, a negative direction deviation
alarm (DV-) occurs. When an alarm has occurred, if the deviation (DV) absolute value
drops lower than the absolute value of the deviation alarm setpoint (DL) minus the hyster-
esis value (HYS), there is a recovery from the alarm.
Further, when the same value as for the SV scale span (positive value) is set in the devia-
tion alarm setpoint (DL), neither a positive direction nor negative direction deviation alarm
occurs regardless of the deviation alarm check.
DV
DL
HYS
Conditions causing an alarm
DV DL
DV
DL
Time
Conditions causing recovery from alarm
0
DVDLHYS
DVDLHYS
HYS
DL
DV+
DV-
D012310E.EPS
Figure Actions of Deviation Alarm Check in the Velocity Limiter Block (VELLIM)

● Deviation Alarm Check Settings
The type of deviation alarm check, deviation alarm setpoint (DL), and alarm hysteresis
value can be set.
The type of deviation alarm check is defined by the “deviation alarm check” item in the
Function Block Detail Builder. The types of deviation alarm checks are given below. The
default is “detection of both directions.”
Monitors the deviation of both the positive and negative directions
Monitors the deviation of either the positive or negative direction only
• No alarm:
No detection is performed
When single direction is selected for the deviation alarm check type, only the deviation in
the positive direction is monitored when the deviation alarm setpoint (DL) has a plus sign,
and only the deviation in the negative direction is monitored when the deviation alarm
setpoint has a minus sign.
Setting of the deviation alarm check type can be performed in the sequence control block
or CALCU, CALCU-C blocks in addition to the Function Block Detail Builder.
The deviation alarm setpoint (DL) is set by the operation and monitoring function.
• Deviation alarm setpoint (DL):
Engineering unit data within the SV scale span range
Default is SV scale span.
When single direction is selected for the deviation alarm check type, add the sign (+ or -) for
the direction to be detected to the deviation alarm setpoint (DL) engineering unit data.
Setting for the alarm hysteresis value is done by the Function Block Detail Builder for each
regulatory control block.
• Hysteresis:
Engineering unit data within the range of 0 to SV scale span, or percentage data for
the SV scale span

■ Data Items - VELLIM
Table Data Items of Velocity Limiter Block (VELLIM)
Item or Not
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
SV Setpoint value (*1) SV engineering unit value -----
CSV Cascade setpoint value Value in the same engineering unit as SV -----
RSV Remote setpoint value Value in the same engineering unit as SV -----
DV Deviation Value in the same engineering unit as SV -----
MV Manipulated output value (*2) MV engineering unit value -----
RMV Remote manipulated output value Value in the same engineering unit as MV -----
DL Deviaton alarm setpoint (SSH - SSL) SSH-SSL
SVH Setpoint high limit SSL to SSH SSH
SVL Setpoint low limit SSL to SSH SSL
DMVP Upward velocity limit value 0 to (MSH - MSL) MSH-MSL
DMVM Downward velocity limit value 0 to (MSH - MSL) MSH-MSL
TU Velocity limit timer unit 0 (second) or 1 (minute) 0
BPSW Velocity limit bypass switch 0, 1 0
OPMK Operation mark 0 ~ 255 0
D012311E.EPS

SEE ALSO
For a list of valid block modes of the VELLIM block, see D1.1.4, “Valid Block Modes for Each Regulatory
Control Block.”

<Toc> <Ind> <D1.24 Signal Selector Blocks (SS-H/M/L)> D1-348
D1.24 Signal Selector Blocks (SS-H/M/L)

The Signal Selector Blocks (SS-H/M/L) compares the value of the signals from
multiple inputs, then selects 1 signal (PV) as output. This block may be applied to
the signal selection loop.
■ Signal Selector Blocks (SS-H/M/L)

▼ Connection, Constant Input
The Signal Selector Blocks (SS-H/M/L) compare the signals from 2-position input or 3-
position input, then selects the maximum, minimum or medium value signal (PV) as output.
The selection may be operated manually.
The figure below shows the function block diagram of Signal Selector Blocks (SS-H/M/L):
0
1
2
IN1 RV1 PV OUT
3
Automatic 4
IN2 RV2 signal
selection
SW SEL
IN3 RV3
Selected
number
D012401E.EPS
Figure Function Block Diagram of Signal Selector Blocks (SS-H/M/L)
The Signal Selector Blocks (SS-H/M/L) are classified into three types according to the
automatic selection rule used:
Table Types of Signal Selector Blocks (SS-H/M/L)
Code Automatic selection rule
SS-H Selects the maximum value (high selector)
SS-M Selects the medium value
SS-L Selects the minimum value (low selector)
D012402E.EPS

terminals of the Signal Selector Blocks (SS-H/M/L):
Table Connection Methods and Connected destinations of the I/O Terminals of Signal Selector
Blocks (SS-H/M/L)
IN1 Signal input 1
IN2 Signal input 2
IN3 Signal input 3
D012403E.EPS
The methods used by the Signal Selector Blocks (SS-H/M/L) to obtain input signals (RV1 to
RV3) include two “connection input” types and one “constant input” type.
The terminal connection input methods include:
• Data reference to other function block via data reference connection from the input
connection terminals.
• Data setting from other function block via terminal connection to the input connection
terminals.
The constant input method does not involve connection to the input connection terminals.
Instead, the signal input value (RVn) set from operation and monitoring functions is used as
a constant.
Use the Function Block Detail Builder to define whether “connection input” or “constant
input” is used for each input signal. The input signals (RVn) for which “connection input” is
specified but no connection has been made, will not be regarded as signal selection targets
of the Signal selector blocks.
• Input Signal n: Select “Constant Input” or “Connection Input.”
The default is “Connection Input.”

■ Functions of Signal Selector Blocks (SS-H/M/L) ¡ £
The SS-H/M/L blocks perform control computation processing, output processing, and
alarm processing.
The only processing timing available for the SS-H/M/L blocks is a periodic startup. Selec-
SEE ALSO
• For the types of output processing and alarm processing possible for the SS-H/M/L blocks, see D1.1.3,
Block.”
● Control Computation Processing of Signal Selector Blocks

(SS-H/M/L)
The table below shows the control computation processing functions of the Signal selector
blocks (SS-H/M/L):
Table Control Computation Processing Functions of Signal Selector Blocks (SS-H/M/L)
Compares the sizes of three input signal values (RV1, RV2, RV3) and selects the one that
Signal selection
satisfies the condition set by the signal selection switch.
PV pushback Causes the non-selected input signal values to agree with the selected signal value (PV).
D012404E.EPS

■ Signal Selection
The signal selection function selects one signal from multiple input signals. The signal to be
selected varies depending upon the type of the Signal Selector Blocks (SS-H/M/L) and
value of the signal selection switch (SW).
● Function of the Signal Selection Switch (SW)

The table below shows the signal selection switch positions and corresponding actions:
Table Signal Selection Switch Positions and Corresponding Actions
Switch position (SW) Action
0 Holds the selected signal value (PV).
1 Selects input signal 1
4 Selects the result of signal-size comparison (automatic selection).
D012405E.EPS
• When the signal selection switch (SW) is set to automatic selection (SW=4)
The values of input signals (RV1 to RV3) are compared. The SS-H, SS-L and SS-M
blocks select the maximum, minimum or medium value, respectively as a selected
signal value (PV).
• When the SW is set to 1 to 3
The input signal (RV [SV]) that corresponds to each SW value is selected uncondition-
ally.
• When the SW is set to 0
Signal selection is not performed, but the previously selected signal value (PV) is held
and output.
The automatic selection rule to be used is determined by the code of the function block.
If automatic selection is performed and one of the input signals has an invalid (BAD) data
status, the maximum or minimum value will be selected from the data excluding the invalid
signal. If two input signals are invalid (BAD), the remaining non-invalid input signal (RVn) is
selected.
The table below shows invalid input signals and corresponding actions when selecting the
medium value:
Table Invalid Input Signals and Corresponding Actions When Selecting the Medium Value
Input signal with BAD data status Action
RV1 RV2 is selected.
Any two signals RVn that is not BAD is selected.
All signals BAD The previously selected value is stored and the SW is set to “0.”
D012406E.EPS

The rules of determining the data status of the selected signal value (PV) are shown below:
• When SW=0
The status of the previous value is stored.
• When SW=1 to 3
The status of the selected signal value (PV) is determined based on the status of the
currently selected input signal.
• When SW=4
currently selected input signal. If all input signals have invalid (BAD) data status, the
data status of the previous value is stored.
● Display of Selected Number (SEL)

Whether it is performed automatically or manually, the signal selection action displays the
number of the currently selected input signal (1, 2 or 3) as a selected number (SEL). If the
signal selection switch position is “0” and no signal is selected, SEL becomes 0.
● Change in Selected Signal Value (PV)

When the signal selection switch position is 0, the selected signal value (PV) can be set
from operation and monitoring functions or other function block.
● Set Parameters of Signal Selection

The parameters of signal selection:
If the signal selection switch position is set above the switch high limit setpoint (SWH) or
below the switch low limit setpoint (SWL) via operation from operation and monitoring
functions, an acknowledgment dialog box appears to prompt for the operator’s confirma-
tion. When confirms, the switch position can be set outside the high/low limit setpoint
range.
• Switch high limit setpoint (SWH): Select “0,” “1,” “2,” “3” or “4.”
• Switch low limit setpoint (SWL): Select “0,” “1,” “2,” “3” or “4.”

■ PV Pushback
The PV pushback function causes the non-selected input signal values (RV1 to RV3) to
agree with the selected signal value (PV).
The PV pushback action targets the input signal values that are obtained via terminal
connection to the input terminals. The PV pushback action is not performed to the input
signal values which are received via data reference or for which “constant input” is speci-
fied.
The figure below shows the action of PV pushback:
0
1
2
IN1 RV1 PV OUT
3
Automatic 4
IN2 RV2 signal
selection
SW SEL
IN3 RV3
Selected
number
PV pushback
D012407E.EPS
Figure PV Pushback
An abrupt change in the selected signal value (PV) upon switching of the selection switch,
may have a negative impact on the process. Preventing this abrupt change in the selected
signal value (PV) is called, “bumpless switching.”
Combining the PV pushback function with the output tracking function of the input con-
nected destination function block enables the signal selection switch position to be
changed bumplessly. The following example shows a control loop where the signal selec-
tion switch position is changed bumplessly.
Output tracking
PV MV PV pushback
RATIO
PV
SS-H
D012408E.EPS
Figure PV Pushback and Output Tracking
1. The PV pushback function sets the selected signal value (PV) to the non-selected
input signals (RV1 to RV3).
2. The output value tracking functions of the upstream function blocks connected to the
IN1 to IN3 terminals cause the output values of the upstream function blocks to track
the values of input signals (RV1 to RV3).

■ Data Items
Table Data Items of Signal Selector Blocks (SS-H/M/L)
Item or Not
MODE Block mode ----- O/S(AUT)
PV Selected signal value (*1) PV engineering unit value SL
SW Signal selection switch 0, 1, 2, 3, 4 0
SEL Selected number 0, 1, 2, 3 0
RV1 Input signal value 1 (*2) Value in the same engineering unit as PV SL
SWH Switch high limit setpoint 0 to 4 4
SWL Switch low limit setpoint 0 to 4 0
D012409E.EPS

*2: Entry is permitted if “Constant input” is specified
SEE ALSO
For a list of valid block modes of the SS-H/M/L blocks, see chapter D1.1.4, “Valid Block Modes for Each

<Toc> <Ind> <D1.25 Auto-Selector Blocks (AS-H/M/L)> D1-355
D1.25 Auto-Selector Blocks (AS-H/M/L)

The Auto-Selector Blocks (AS-H/M/L) compare signals from 2-position or 3-position
input from 2 or 3 controller blocks and automatically select one signal as manipu-
lated output value (MV). Auto-selector blocks may be applied to the override control
loops for signal selection.
■ Auto-Selector Blocks (AS-H/M/L)

▼ Connection, Constant Input
The Signal Selector Blocks (SS-H/M/L) compare the signals from 2-position input or 3-position
input, then selects the maximum, minimum or medium value signal (PV) as output. The selec-
tion may be operated manually.
The figure below shows the function block diagram of Signal Selector Blocks (SS-H/M/L):
An auto-selector control system can be configured by combining an Auto-Selector Blocks (AS-
H/M/L) and 2 to 3 controller blocks. In other words, final control elements of a single loop
can be controlled in such a way that 2 to 3 variables are monitored and maintained on the
safe side of their presetpoint values using a signal selector unit; whereas, in a normal case
the final elements are controlled based on a single variable.
The figure below shows a function block diagram of the Auto-Selector Blocks (AS-H/M/L):
INT
0
1
2 AUT Output
IN1 RV1 PV MV OUT
processing
3
Automatic 4 MAN
IN2 RV2 signal
selection
SW SEL
IN3 RV3
Selected
number
D012501E.EPS
Figure Function Block Diagram of Auto-Selector Blocks (AS-H/M/L)
The Auto-Selector Blocks (AS-H/M/L) are classified into three types according to the
automatic selection rule used:
Table Types of Auto-Selector Blocks (AS-H/M/L)
Code Automatic selection rule
AS-H Selects the maximum value (high selector)
AS-M Selects the medium value
AS-L Selects the minimum value (low selector)
D012502E.EPS

terminals of the Auto-Selector Blocks (AS-H/M/L):
Table Connection Methods and Connected destinations of the I/O Terminals of Auto-Selector
Blocks (AS-H/M/L)
IN1 Signal input 1
IN2 Signal input 2
IN3 Signal input 3
D012503E.EPS
: Connection allowed only when connecting to a switch block (SW-33, SW-91) or an inter-station data link block (ADL).
The methods used by the Auto-Selector Blocks (AS-H/M/L) to obtain input signals 1 to 3
(RV1 to RV3) include two “connection input” types and one “constant input” type.
The connection input methods include the following:
• Data reference to other function block via data reference connection from the input
connection terminals
• Data setting from other function block via terminal connection to the input connection
terminals
The constant input method does not involve connection to the input connection terminals.
Instead, the signal input value (RVn) set from operation and monitoring functions is used as
a constant.
Use the Function Block Detail Builder to define whether “connection input” or “constant
input” is used for each input signal. The input signals (RVn) for which “connection input” is
specified but no connection has been made, will not be regarded as signal selection targets
of the Auto-selector blocks.
• Input Signal: Select “Constant Input” or “Connection Input.”
The default is “Connection Input.”
IMPORTANT
When a controller block is terminal connected to the INx terminal of an Auto-selector blocks
(AS-H/M/L), be sure to specify “positional type” for the control output action of the controller
block.

■ Functions of Auto-Selector Blocks (AS-H/M/L)
The AS-H/M/L blocks perform control computation processing, output processing, and
alarm processing.
The only processing timing available for the AS-H/M/L blocks is a periodic startup. Selec-
SEE ALSO
• For the types of output processing and alarm processing possible for the AS-H/M/L blocks, see D1.1.3,
Block.”
● Control Computation Processing of Auto-Selector Blocks (AS-H/M/L)

The table below shows the control computation processing functions of the Auto-Selector
blocks (AS-H/M/L):
Table Control Computation Processing Functions of Auto-Selector Blocks (AS-H/M/L)
Compares the sizes of three input signal values (RV1, RV2, RV3) and selects one input
Signal selection
signal that satisfies the condition set by the signal selection switch.
Automatic control output Performs range conversion to the selected signal value (PV) to obtain a manipulate output
computation value (MV).
Causes the input signal values (RV1, RV2, RV3) to agree with the manipulated output
Output pushback
value (MV) to prevent the manipulated output value (MV) from changing abruptly.
MAN fallback
D012504E.EPS

The signal selection function selects one signal from multiple input signals. The signal to be
selected varies depending upon the type of the Auto-Selector Blocks (AS-H/M/L) and value
of the signal selection switch (SW).
The Auto-Selector Blocks (AS-H/M/L) do not output the selected signal value (PV) if the
block mode is manual (MAN) or initialization manual (IMAN). However, as the signal
selection function remains active, the selected number (SEL) and selected signal value
(PV) are updated constantly.
● Function of the Signal Selection Switch (SW)

0 Holds the selected signal value (PV).
4 Selects the result of signal-size comparison (automatic selection).
D012505E.EPS
• When the signal selection switch (SW) is set to automatic selection (SW=4)
The values of input signals (RV1 to RV3) are compared. The SS-H, SS-L and SS-M
blocks select the maximum, minimum or medium values, respectively as the selected
signal value (PV).
• When the SW is set to 1 to 3
The input signal (RV [SV]) that corresponds to each SW value is selected uncondition-
ally.
• When the SW is set to 0
Signal selection is not performed, but the previously selected signal value (PV) is held
and output.
The automatic selection rule to be used is determined by the code of the function block.
If automatic selection is performed and one of the input signals has an invalid (BAD) data
status, the maximum or minimum value will be selected from the data excluding the invalid
signal. If two input signals have invalid (BAD) data value, the remaining non-invalid input
signal (RVn) is selected.
The table below shows invalid input signals and corresponding actions when selecting the
medium value:
Table Invalid Input Signals and Corresponding Actions When Selecting the Medium Value
Input signal with BAD data status Action
Any two signals RVn that is not BAD is selected.
All signals BAD The previously selected value is stored and the SW is set to “0.”
D012506E.EPS

The rules of determining the data status of the selected signal value (PV) are shown below:
• When SW=0
The previous status is stored.
• When SW=1 to 3
currently selected input signal.
• When SW=4
currently selected input signal. If all input signals are invalid (BAD), the data status of
the previous value is stored.
● Display of Selected Number (SEL)

Whether it is performed automatically or manually, the signal selection action displays the
number of the currently selected input signal (1, 2 or 3) as a selected number (SEL). If the
signal selection switch position is “0” and no signal is selected, SEL becomes “0.”
● Set Parameters of Signal Selection

The parameters of signal selection.
If the signal selection switch position is set above the switch high limit setpoint (SWH) or
below the switch low limit setpoint (SWL) from operation and monitoring functions, an
acknowledgment dialog box appears to prompt for the operator’s confirmation. When
confirms, the switch position can be set outside the high/low limit setpoint range.
• Switch high limit setpoint (SWH): Select “0,” “1,” “2,” “3” or “4.”
• Switch low limit setpoint (SWL): Select “0,” “1,” “2,” “3” or “4.”

■ Automatic Control Output Computation
The automatic control output computation function determines the manipulated output
value (MV) by performing range conversion to the selected signal value (PV). This action
takes place in the automatic (AUT) mode.
The computational expression of range conversion:
MV= MSH-MSL • (PV-SL)+MSL

SH-SL D012507E.EPS


period to an actual manipulated output value (MV). The action that converts the manipu-
lated output change to an actual manipulated output value (MV) is called, “control/calcula-
tion output action.”
The control action applied in the Auto-Selector Blocks (AS-H/M/L) are of “positional type”
only. The result of automatic control output computation is output as a manipulated output
value (MV).

lated output value of the downstream block in cascade loop without causing the manipu-
lated output value (MV) to change abruptly (i.e., bumpless change).
The action during bumpless switching varies in accordance with the control output action
and block mode status.
The type of bumpless switching performed by the Auto-Selector Blocks (AS-H/M/L) is
“output pushback.”
The output pushback function causes the input signal values (RV1 to RV3) to agree with
the manipulated output value (MV).
INT
0
1
2 AUT Output
IN1 RV1 PV MV OUT
processing
3
Automatic 4 MAN
IN2 RV2 signal
selection
SW SEL
IN3 RV3
Selected
number
D012508E.EPS
Figure Output Pushback
In any block mode, the output pushback function of the Auto-Selector Blocks (AS-H/M/L)
sets as the input signal values (RV1 to RV3), the range-converted values based on MV.
SH-SL
RVn= • (MV-MSL)+SL
Output pushback operates in coordination with the output tracking function of the output
processing targets, and causes the input signal values (RV1 to RV3) to agree with the
values at the output destination blocks cascade connected downstream.
By using the output pushback function in a cascade control loop built around an Auto-
Selector Blocks (AS-H/M/L), the cascade status can be switched without causing an output
bump.
Output pushback is performed only to the input signal values received from the input
terminals used for cascade connection. Output pushback is not performed to the input
signal values that are extracted via data reference or used as constants during “constant
input.”

The following example shows a control loop where the signal selection switch position is
changed bumplessly.
Output tracking
PV MV PV pushback
PID
PV
SS-H D012510E.EPS
Figure PV Pushback and Output Tracking
1. The output tracking function causes the selected signal value (PV) to track data at the
output destination.
2. The output pushback function sets the tracked data as input signals (RV1 to RV3).
3. The output value tracking functions of the upstream function blocks connected to the
IN1 to IN3 terminals cause the output values of the upstream function blocks to track
the values of input signals (RV1 to RV3).


(MAN) mode. Therefore, no actions in the manual (MAN) mode take place.

vanishes:
AUT
IMAN (AUT)
AUT

• When the data status at the connected destination of manipulated output value (MV)
is conditional (CND) (i.e., the cascade connection is open).
• When the data status at the connected destination of manipulated output value (MV)
is a communication error (NCOM) or output failure (PTPF) (i.e., the cascade connec-
tion is open).
• When the connected destination of manipulated output value (MV) is a switch block
(SW-33, SW-91) and the cascade connection is switched off.
• When the connected destination of manipulated output value (MV) is a process output
and a failure or output open alarm is detected in the process output.

■ MAN Fallback

state.

AUTAMAN

(CAL).


becomes invalid.


■ Data Items - AS-H/M/L
Table Data Items of Auto-Selector Blocks (AS-H/M/L)
Item or Not
SW Signal selection switch 0, 1, 2, 3, 4 0
SEL Selected number 0, 1, 2, 3 0
RV2 Input signal value 2 (*3) Value in the same engineering unit as PV -----
RV3 Input signal value 3 (*3) Value in the same engineering unit as PV -----
SWH Switch high limit setpoint 0 to 4 4
SWL Switch low limit setpoint 0 to 4 0
D012511E.EPS

*3: Entry is permitted if “Constant input” is specified
SEE ALSO
For a list of valid block modes of the AS-H/M/L blocks, see a chapter D1.1.4, “Valid Block Modes for Each

<Toc> <Ind> <D1.26 Dual-Redundant Signal Selector Block (SS-DUAL)> D1-367
D1.26 Dual-Redundant Signal Selector Block

(SS-DUAL)
Dual-Redundant Signal Selector Block (SS-DUAL) may be applied in a redundant
configuration to automatically select one of the two input signals from the same
process signal source but received separately via two signal paths.
■ Dual-Redundant Signal Selector Block (SS-DUAL)

▼ Connection
The Dual-Redundant Signal Selector Block (SS-DUAL) automatically selects one of the
two input signals. The selected signal is output as process variable (PV).
With the Dual-Redundant Signal Selector Block (SS-DUAL), the redundant configuration
become possible. Similar to the dual-redundant transmitter configuration, the dual-redun-
dant analog I/O modules are provided in the process input and output configuration.
The figure below shows the function block diagram of Dual-Redundant Signal Selector
Block (SS-DUAL):
Deviation
check
1
IN1 RV1
Automatic
2 Input
signal PV OUT
processing
selection 3
IN2 RV2
SW SEL
Selected
number
D012601E.EPS
Figure Function Block Diagram of Dual-Redundant Signal Selector Block (SS-DUAL)
terminals of the Dual-Redundant Signal Selector Block (SS-DUAL):
Table Connection Methods and Connected Destinations of I/O Terminals of Dual-Redundant
Signal Selector Block (SS-DUAL):
IN1 Input signal 1
IN2 Input signal 2
D012602E.EPS

■ Function of Dual-Redundant Signal Selector Block (SS-DUAL)
The SS-DUAL block performs input processing, control computation processing, output
The only processing timing available for the SS-DUAL block is a periodic startup. Selec-
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the SS-DUAL
● Control Computation Processing of Dual-Redundant Signal Selector Block

(SS-DUAL)
The table below shows the control computation processing functions of the Dual-Redun-
dant Signal Selector Block (SS-DUAL):
Table Control Computation Processings of Dual-Redundant Signal Selector Block
(SS-DUAL)
Tests the data status of two input signal values (RV1, RV2) and selects
Signal selection
the one that satisfies the condition set by the signal selection switch.
Changes the data status of the selected signal (PV) to BAD when two
Selected signal error input signals have an invalid (BAD) data status or when a deviation
alarm is present.
D012603E.EPS
● Alarm Processing Specific to Dual-Redundant Signal Selector Block

(SS-DUAL)
The SS-DUAL block performs a special operation triggered by the presence of a deviation
alarm in its alarm processing.

The signal selection function selects one of multiple input signals.
● Signal Selection Switch (SW)

1 Selects input signal 1.
2 Selects input signal 2.
3 Selects input signal 1 or 2, whichever is in normal state.
D012604E.EPS
If the signal selection switch is set to “3” (automatic selection), the data statuses of input
signals RV1 and RV2 are tested, and the signal whose data status is other than invalid
(BAD) is selected as the selected signal value (PV). If both input signals are normal or
abnormal, the previously selected input signal remains selected. If the signal selection
switch is set to “1” or “2,” the specified input signal is selected unconditionally.
● Selected Number (SEL)

The currently selected input signal number (1 or 2) is stored as the selected number (SEL)
and displayed.
● Non-Selected Signal Value (SV)

The input signal value of the signal not selected is stored as the non-selected signal value
(SV) and displayed.

■ Selected Signal Error
The selected signal error function changes the data status to invalid (BAD) when the
selected signal error conditions are satisfied.
Table Selected Signal Error Conditions
Switch position (SW) Error condition
1 Input signal 1 is BAD.
2 Input signal 2 is BAD.
3 Both input signals 1 and 2 are BAD, or a deviation alarm is present.
D012605E.EPS
In a control loop where the selected signal value (PV) that received this selected signal
error processing is input as a process variable, the block mode changes to manual (MAN).
■ Operations during Deviation Alarm

▼ Deviation Alarm, Update PV value during SS-DUAL Deviation Alarm
If the signal selection switch is set to 3, when the difference between the selected signal
value (PV) and non-selected signal value (SV) exceeds the deviation alarm settings value
(DL), a deviation alarm will be generated and the PV data status will become invalid (BAD).
While the deviation alarm is being generated, the PV data value immediately prior to the
alarm generation is maintained. However, if “Update PV value during SS-DUAL deviation
alarm generation” is selected in the Properties of the FCS folder, the data value will be
updated to the selected input value even if the PV data status is BAD due to a deviation
alarm.
The table below shows the difference in operations between when “Update PV value
during deviation alarm generation” is selected and when “Maintain PV value” is selected.
Table Operations during Deviation Alarm Generation when SW=3
Item Maintain PV Value (Default) Update PV Value
PV data status BAD (Data value invalid) BAD (Data value invalid)
Maintains value immediately prior to
PV data value Updates value
deviation alarm generation
Digital filter No operation Operates
Totalizer No operation No operation
High-limit, low-limit alarm
Performs check Performs check
High-high limit, low-low limit alarm
Velocity alarm Does not perform check Does not perform check
Output from OUT terminal Maintained value is output Updated value is output
Performs MAN fallback since the PV data Performs MAN fallback since the PV data
Operation of connected
status is BAD. The destination data value is status is BAD. The destination data value is
function block
not updated. not updated.
D012606E.EPS

■ Specifying Operation during Deviation Alarm
The operation during deviation alarm generation is specified for each FCS station using the
FCS Properties.
The operation cannot be specified for individual SS-DUAL blocks. The specification can
only be changed off-line.
• Update PV Value during SS-DUAL Deviation Alarm Generation:
Select this specification by placing a check in the checkbox. By default, the PV value
immediately prior to the generation of a deviation alarm is maintained during the alarm
generation (the checkbox is left blank)
■ Data Items - SS-DUAL

Table Data Items of Dual-Redundant Signal Selector Block (SS-DUAL)
Entry Permitted
or Not
SV Non-selected signal value Value in the same engineering unit as PV SL
DV Deviation Value in the same engineering unit as PV 0
RV1 Input signal value 1 Value in the same engineering unit as PV SL
RV2 Input signal value 2 Value in the same engineering unit as PV SL
SW Signal selection switch 1, 2, 3 3
SEL Selected number 1, 2 1
D012607E.EPS

SEE ALSO
For a list of valid block modes of the SS-DUAL block, see chapter D1.1.4, “Valid Block Modes for Each

<Toc> <Ind> <D1.27 Cascade Signal Distributor Block (FOUT)> D1-372
D1.27 Cascade Signal Distributor Block (FOUT)

The Cascade Signal Distributor Block (FOUT) distributes cascade setpoint signals
input from controller blocks to multiple down-stream controller blocks. This block
may be applied in a cascade control loop with multiple function blocks in parallel
downstream connected.
■ Cascade Signal Distributor Block (FOUT)

▼ Connection
The Cascade Signal Distributor Block (FOUT) can distribute cascade signals to as many as
8 function blocks.
Using the Cascade Signal Distributor Block (FOUT) enables the creation of a cascade
control loop where multiple controller blocks are connected in parallel downstream. The
system does not support to simply link the downstream controller blocks in a chain connec-
tion.
The Cascade Signal Distributor Block transmits the cascade open or clamp status of the
downstream controller blocks to the upstream controller block.
The figure below shows the function block diagram of the Cascade Signal Distributor Block
(FOUT):
MV1 J01
MV2 J02
SET CSV SV Output
computation
MV8 J08
D012701E.EPS
Figure Function Block Diagram of Cascade Signal Distributor Block
The setpoint value (SV) of the Cascade Signal Distributor Block (FOUT) can be used for
data reference but not for data setting.

The figure below shows an application example of the Cascade Signal Distributor Block
(FOUT):
IN OUT
PV MV
PID
SET
SV MV1
J01
MV2
J02
FOUT
SET SET
IN SV OUT IN SV OUT
PV MV PV MV
PID PID
D012702E.EPS
Figure Application Example of Cascade Signal Distributor Block (FOUT)
Considering the range of each output destination, the cascade setpoint signals to be
distributed undergo range matching. Assume that the SV range of the Cascade Signal Dis-
tributor Block (FOUT) is 0 to 100 %, while the PV ranges of the two downstream controller
blocks are 0 to 8000 NM3/H and 0 to 10.00 KG/H, respectively. If the manipulated output of
the upstream controller block is 50 %, the output values of the Cascade Signal Distributor
Block (FOUT) become 400 NM3/H and 5.00 KG/H, respectively.
The function blocks that can be used upstream of the Cascade Signal Distributor Block are
limited to those that satisfy the following conditions:
• A regulatory control block with a manipulated output value (MV), capable of forming
cascade connection
• An analog calculation block capable of forming cascade connection
When Cascade Signal Distributor Block (FOUT) are connected in cascade in multiple
levels, the maximum number of Cascade Signal Distributor Block (FOUT) that can be
connected serially between the top block and bottom block is 6. Switch blocks (SW-33,
SW-91) inserted in between are not counted. If FOUT blocks used exceed the limit, the
manipulated output value (MV) of the top function block becomes output failure (PTPF).

terminals of the Cascade Signal Distributor Block (FOUT):
Table Connection Methods and Connected Destinations of I/O Terminals of Cascade Signal
Distributor Block (FPIT):
SET Setting input
Manipulated
J01
output 1
Manipulated
J02
output 2
Manipulated
J03
output 3
Manipulated
J04
output 4
Manipulated
J05
output 5
Manipulated
J06
output 6
Manipulated
J07
output 7
Manipulated
J08
output 8
D012703E.EPS
SET terminal can not be connected to the terminals of other station’s function block.

■ Function of Cascade Signal Distributor Block (FOUT)
The FOUT block performs control computation processing and output processing.
The only processing timing available for the FOUT block is a periodic startup. Selections
SEE ALSO
• For the types of output processing possible for the FOUT block, see chapter D1.1.3, “Input Processing,
Output Processing, and Alarm Processing Possible for Each Regulatory Control Block.”
● Control Computation Processing of Cascade Signal Distributor Block

(FOUT)
The table below shows the control computation processing functions of the Cascade Signal
Distributor Block (FOUT):
Table Control Computation Processing Functions of Cascade Signal Distributor Block (FOUT)
Performs range matching to the cascade setpoint value (CSV) based on the range of the
Range conversion output distribution output destination, and uses the result as a manipulated output value (MV). Range
matching is performed for each output destination.
Obtains a cascade setpoint value (CSV) from the Cascade Signal Distributor Block’s
Output pushback (FOUT) manipulated output value (MVn) via range conversion. Prevents abrupt changes
in the manipulated output by utilizing output tracking.
D012704E.EPS
● Output Processing Specific to Cascade Signal Distributor Block (FOUT)

As part of its output processing, the FOUT block employs a special “output clamp.”

■ Range Conversion Output Distribution
The control algorithm used by the Cascade Signal Distributor Block (FOUT) is based on
range conversion output distribution.
The range conversion output distribution function performs range matching to the cascade
setpoint value (CSV) set from the upstream function block, for each connected destination
based on the destination range. During range conversion output distribution, range match-
ing is performed using output range tracking.
Range matching is based on the following expression:
MSHn-MSLn
MVn= • (SV-SSL)+MSLn
MVn: nth manipulated output value (MV1 to MV8)

SLS: SV scale low limit
MSHn: MVn scale high limit
MSLn: MVn scale low limit
MSHn and MSLn are caused to automatically agree with the scale high limit and low limit of
the output destination via the output range tracking function.

▼ SV Range
one digit each.
one digit each.
The default is 0.0.

The type of bumpless switching performed by the Cascade Signal Distributor Block (FOUT)
is “output pushback.”
The output pushback function sets as the setpoint value (SV) and cascade setpoint value
(CSV), the SV-range values converted from the manipulated output value (MVn) via range
conversion.
Combining the output pushback and output tracking functions enables the creation of a
control loop where a balanceless bumpless transfer can be performed.
The computational expression of range conversion:
SV= SSH-SSL • (MVn-MSLn)+SSL

MSHn-MSLn
CSV=SV D012706E.EPS

Output pushback is executed when the following occur:
• When the cascade status of one output destination of the Cascade Signal Distributor
Block (FOUT) has changed to close, while the cascade statuses of all other output
destinations remain open.
• In a configuration where a selector switch exists between the Cascade Signal Dis-
tributor Block (FOUT) and the upstream function block in cascade connected to the
FOUT, the switch status has changed from open to close.
• When cascade is open and tracking is enabled at the J01 terminal.
1. When cascade is open, the output tracking function causes the manipulated output
value (MVn) to track data at the output destination.
2. When cascade is closed, the manipulated output value (MVn) is pushed back to the
level of SV. However, this occurs only when one of the above output pushback execu-
tion conditions is satisfied.
3. The output value tracking function of the upstream function block causes the output
value of the upstream function block to track the setpoint value (SV).
In a control loop where these actions take place, the output value of the upstream function
block agrees with data at the output destination of the Cascade Signal Distributor Block
(FOUT) when the cascade status is switched to close. Therefore, no output bump occurs
as a result of the cascade status switching to close.
Output pushback can handle only one input signal (RVn) at one time. In other words,
balanceless bumpless transfer of a cascade loop is possible only in the first loop.
Bumpless switching based on the output pushback function will not be executed to the
second and subsequent output destinations to close cascade. However, abrupt changes in
output as a result of changes in the setpoint value can be prevented if the downstream
controller blocks are PID type controller blocks (PID), as they bypass control computation
during the first control period after the cascade connection establishes.
If the upstream function block is a calculation block, neither output pushback action nor
output tracking action take place.
■ Output Clamp
The output clamp is a function that limits the manipulated output value (MV) in such a way
that it cannot be changed to a value greater than or less than the current output value. The
status where the manipulated output value (MV) is limited in this way is called the output
clamp status.
In the FOUT block, if the output value at each output destination is subject to a limitation,
the output clamp status is indicated by the MVn data status “high limit clamp (CLP+)” or
“low limit clamp (CLP-).”
The cascade setpoint value (CSV) data status will be data status (CLP+ or CLP-) if the data
statuses for all output points that are in the cascade close status are CLP+ or CLP-, re-
spectively.
SEE ALSO
For details on the output clamp, see a chapter C4.3, “Output Clamp.”

■ Data Items - FOUT
Table Data Items of Cascade Signal Distributor Block (FOUT)
Item or Not
MV1 Manipulated output value 1 Value in the same unit as connection destination JO1 MSL1
D012707E.EPS


<Toc> <Ind> <D1.28 Feedforward Signal Summing Block (FFSUM)> D1-380
D1.28 Feedforward Signal Summing Block (FFSUM)

Feedforward Signal Summing Block (FFSUM) adds the feedforward signal to the
feedback control signal then outputs the result. This block may be applied to the
control loop that performs feedforward compensation control or base load control.
■ Feedforward Signal Summing Block (FFSUM)

▼ Connection
Feedforward Signal Summing Block (FFSUM) adds up the feedback signal (manipulated
output value) input to the IN terminal from an up-stream controller block via cascade
connection and the feedforward signal input to the SET terminal via cascade connection,
and outputs the result.
The figure below shows the function block diagram of Feedforward Signal Summing Block
(FFSUM):
SET BIN TIN TSI INT
CAS (VN) (TSW)

CSV
AUT
SV
MAN
Signal CAS/AUT Output

IN PV MV OUT
addition processing
MAN
FSW
(PV, PV, MV, MV)
SUB
D012801E.EPS
Figure Function Block Diagram of Feedforward Signal Summing Block (FFSUM)
terminals of the Feedforward Signal Summing Block (FFSUM):
Table Connection Methods and Connected Destinations of I/O Terminals of Feedforward Signal
Summing Block (FFSUM)
IN FB signal input
SET FF setting input
Compensation
BIN
input
Tracking signal
TIN
input
D012802E.EPS
: Connection allowed only when connecting to a switch block (SW-33, SW-91) or an inter-station data link block (ADL).

■ Function of Feedforward Signal Summing Block (FFSUM) ¡ £
The FFSUM block performs control computation processing, output processing, and alarm
processing.
The only processing timing available for the FFSUM block is a periodic startup. Selections
SEE ALSO
• For the types of output processing and alarm processing possible for the FFSUM block, see chapter
D1.1.3, “Input Processing, Output Processing, and Alarm Processing Possible for Each Regulatory
Control Block.”
● Control Computation Processing of Feedforward Signal Summing Block

(FFSUM)
The table below shows the control computation processing functions of the Feedforward
Signal Summing Block (FFSUM):
Table Control Computation Processings of Feedforward Signal Summing Block (FFSUM)
Obtains a manipulated output value (MV) by adding to the feedforward setpoint value
Feedforward control signal addition
(SV) the feedback input value (PV) corrected by the input corrected value (VN).
Only “input compensation” is available.
Input compensation
Setpoint value limiter Limits the setpoint value (SV) within the setpoint high/low limits.
Forcibly sets as the feedback input value, the PV value calculated back from the MV
Output pushback output destination readback value (MVrb). This prevents the manipulated output value
(MV) from changing abruptly.
Balance action
Control hold
MAN fallback
D012803E.EPS

■ Feedforward Signal Summing
The feedforward signal summing function adds the feedforward setpoint value (SV) to the
feedback input value (PV), after correcting the latter by the input compensated value (VN),
to obtain a manipulated output value (MV) when the block mode is automatic (AUT) or
cascade (CAS).
Input
VN compensation
AUT/MAN CAS
CSV
+
+
CB
CK SV FSW
+
CV Signal MV
PV
+ addition
D012804E.EPS
Figure Feedforward Signal Summing Action
● Signal Addition
The following computational expressions are used to add up the PV value (CV) after input
compensation and feedforward setpoint value (SV) via range conversion to obtain a ma-
nipulated output value (MV).
MV=CVm+SVm+BLn
MSH-MSL
CVm= • (CV-SL)+MSL
SH-SL D012805E.EPS
MSH-MSL
SVm= • (SV-SSL)+MSL
MV: Manipulated output value

SV: Feedforward setpoint value
SVm: SV after range conversion
CV: PV after input compensation
CVm: CV after range conversion
BLn: Balance term

● Feedforward Signal Cut
Depending upon the operating condition of the plant, it is sometimes desirable that
Feedforward Signal Summing be disabled completely. When the feedforward control signal
cut switch (FSW) is turned ON, the feedback input value after input compensation directly
receives range conversion and is output as a manipulated output value (MV) in the auto-
matic (AUT) or cascade (CAS) mode.
MV=CVm+BLn
During the automatic (AUT) or cascade (CAS) mode, the following balance operation is
performed to prevent an output bump as a result of switching the feedforward control signal
cut switch.
When the feedforward signal cut switch (FSW) is turned ON, BLn changes to the value
shown below:
BLn=MVrb-CVm
MVrb: MV output destination readback value
When the feedforward switch (FSW) is turned OFF, the following computation is performed
to determine the BLn value.
BLn=MVrb-SVm-CVm’

▼ SV Range
one digit each
one digit each
The default is 0.0.

■ I/O Compensation
The I/O compensation function adds the I/O compensated value (VN) received from out-
side to the input signal or output signal of PID control computation, while the controller
block is operating automatically in the automatic (AUT) or cascade (CAS) mode.
Only input compensation is available with the Feedforward Signal Summing Block
(FFSUM).
● Characteristics of Input Compensation

The following is a computational expression of input compensation:
CVn=PVn+CK (VN+CB)
CVn: Control variable (PV after input compensation)

The figure below shows a processing flow of input compensation:
VN
+
+
CB
CK
+
PVn CVn PID control MV
PV
+ computation
D012807E.EPS
Figure Processing Flow of Input Compensation
When creating a base load control system, set the median value of feedforward signals in a
normal operating state as the input compensated value (VN). Also, preset CK and CV to
-1.0 and 0.0, respectively. As a result, the feedback control signal (PV) is compensated by
its deviation from the median value of feedforward signals (SV) and obtained as a final

● Set Parameters of Input Compensation
The parameters of input compensation:
• Compensation gain (CK): -10.000 to 10.000
• Compensation bias (CB): Arbitrary engineering unit data
The default is 0.
The input compensated value (VN) can not only be set from other function block via data
setting, but also be entered via data reference from the compensation input terminal (BIN).

The control output actions available with the Feedforward Signal Summing Block (FFSUM)
are of “positional type” only. The result of signal summing computation is output as a

the setpoint high limit (SVH) and setpoint low limit (SVL), and recognizes the setpoint
values (SV) only within this range as valid.
function block.
● Actions in Automatic (AUT) or Manual (MAN) Mode

• When a value exceeding the setpoint high limit (SVH) is set as the setpoint value (SV):
• When a value below the setpoint low limit (SVL) is set as the setpoint value (SV):
● Set Parameters of Setpoint Value Limiter


The setpoint value pushback function sets the same value for the two types of setpoint
values (SV, CSV). The figure below explains the relationship between the setpoint value
(SV) and cascade setpoint value (CSV):
Input from the SET terminal
CSV
AUT/MAN
CAS
SV
Setpoint value
Control
computation
D012808E.EPS
Figure Relationship between Setpoint Values (SV and CSV)
function block.
● Action in Automatic (AUT) or Manual (MAN) Mode

Causes the cascade setpoint value (CSV) to agree with the setpoint value (SV). Even when
a data value is set to the setpoint value (SV) from outside the function block, the same
value is automatically set to the cascade setpoint value.
● Action in Cascade (CAS) Mode

Causes the setpoint value (SV) to agree with the cascade setpoint value (CSV).

The bumpless switching functions available with the Feedforward Signal Summing Block
(FFSUM) include:
• Output pushback
• Balance action
● Output Pushback
The output pushback function sets as the feedback input value (PV), the value calculated
back from the MV output destination readback value (MVrb).
The following computational expressions are used to calculate PV back from MVrb:
PV=CV-CK • (VN+CB)
SH-SL
CV= • (CVm-MSL)+SL
CVm=MVrb-SVm-BLn
MSH-MSL
BLn: Balance term

In the manual (MAN) or initialization manual (IMAN) mode
BLn=0.0
When output is clamped in the automatic (AUT) or cascade (CAS) mode
BLn=BLn-1
If no input compensation is performed, the feedback input value (PV) in the above compu-
tational expression is the same as CV.
If the calculated value exceeds the feedback input value (PV) range, it is limited to the SH
or SL value.
An abrupt change in the manipulated output value (MV) upon changing of block modes
from manual (MAN) to automatic (MAN), may have a negative impact on the process.
Preventing this abrupt change in the manipulated output value (MV) is called, “bumpless
switching.”

Using the output pushback function in combination with the output tracking function en-
ables balanceless bumpless transfer of a cascade loop.
AUT/MAN
SV
PV MV PV MV
PID FFSUM
CAS AUT/MAN
Output tracking
Output tracking SV
Output pushback PV MV
PID
D012811E.EPS
Figure Output Pushback and Output Tracking when Cascade is Open
1. When cascade is open, the output tracking function causes MVrb to track data at the
output destination.
2. When cascade is closed, the output pushback function calculates the feedback input
value (PV) from MVrb, and sets the obtained value as PV.
3. The output value tracking function of the upstream block in cascade causes the output
value of the upstream function block to track the feedback input value (PV).

● Balance Action
The balance action function adjusts the balance term value when the feedback input value
(PV) changes abruptly during automatic operation in the auto (AUT) or cascade (CAS)
mode, in order to prevent the manipulated output value (MV) from changing abruptly.
An abrupt change in the manipulated output value (MV) during automatic operation may
have a negative impact on the process. Preventing this abrupt change in the manipulated
output value (MV) is called, “bumpless switching.”
The balance action prevents the manipulated output value from changing abruptly when
the feedback input value undergoes an abrupt change.
The balance term is adjusted based on the following computational expressions:
BLn=MVrb-CVm-SVm
MSH-MSL
CVm= • (CV-SL)+MSL
SH-SL D012812E.EPS
MSH-MSL
CV=PV+CK • (VN+CB)
If no input compensation is performed, CV in the above computational expressions is the

same as PV.
The Feedforward Signal Summing Block (FFSUM) executes this balance action when the
feedback control function block connected upstream in cascade issues a warning that the
setpoint value will be bumped.
The execution conditions of the balance action:
• When a Cascade Signal Distributor Block (FOUT) is connected upstream and the
conditional (CND) status of the upstream output value is canceled.
• A calculation block that does not provide a balance function is connected upstream.
• The initialization manual (MAN) mode is canceled while the output pushback value is
being limited to the MSH or MSL value.
When the balance action is executed, BLn is moved toward 0 by the ramp constant (RP)
during each of the subsequent scan periods, until it finally reaches 0.
Engineering unit data between 0 and the MV scale span range limit
The setting can be changed from operation and monitoring functions during operation.

● Characteristics of Initialization Manual

changed to manual (MAN), the initialization manual (IMAN) mode will precede the manual
(MAN) mode.
In other words, any operation to change to the manual (MAN) mode becomes invalid.
only change to that mode when initialization condition vanishes.

vanishes:
AUT
IMAN (AUT)
AUT

block (SW-33, SW-91) and the switch is disconnected (i.e., the cascade connection is
open).
output and a failure or output open alarm has occurred in the process output.
• The output signal is not a pulse-width output and the data status of the input signal at
the TIN or TSI terminal has become invalid (BAD) during the tracking (TRK) mode.

● Control Hold
The control hold action takes place when the following conditions are establishes during
automatic operation (AUT, CAS):
switch, etc.)
rarily in a non-response state (momentary power failure)
The control is resumed when the conditions become unsatisfied.

■ MAN Fallback
● Characteristics of Man Fallback

state.

AUTAMAN

• When the data status of the process variable (PV) is invalid (BAD).
• When the block mode change interlock condition establishes.

■ AUT Fallback
● Characteristics of AUT Fallback


tected in the cascade setpoint value (CSV) for some reason.
The following examples shows when the AUT fallback condition is established:
CASAAUT
Use the Function Block Detail Builder to define whether or not to use the AUT fallback.

● Characteristics of Block Mode Change Interlock

• Any block mode change command to obtain an automatic operation state (AUT or
CAS mode) becomes invalid.


■ Data Items - FFSUM
Table Data Items of Feedforward Signal Summing Block (FFSUM) (1/2)
Item or Not
PV Fedback input signal value PV engineering unit value SL
SV Fedforward setpoint value SV engineering unit value SSL
CSV Fedforward control signal cascade setpoint Value in the same engineering unit as PV SSL
D012814E.EPS

SEE ALSO
For a list of valid block modes of the FFSUM block, see a chapter D1.1.4, “Valid Block Modes for Each

Table Data Items of Feedforward Signal Summing Block (FFSUM) (2/2)
Item or Not
VN Input compensation value ----- 0.0
RP Ramp constant 0 to (MSH - MSL) MSH - MSL
FSW Fedforward control signal cut switch 0, 1 0
D012815E.EPS


<Toc> <Ind> <D1.29 Non-Interference Control Output Block (XCPL)> D1-398
D1.29 Non-Interference Control Output Block

(XCPL)
Non-Interference Control Output Block (XCPL) adds output compensation signals to
the feedback control signal the outputs the result.
This block may be applied to add non-interference compensation signals to two
mutually non-interference control loops.
■ Non-Interference Control Output Block (XCPL)

▼ Connection
Non-Interference Control Output Block (XCPL) adds output compensation signals to the
feedback control signal (manipulated output value) that are received by the IN terminal
from an upstream control loop via cascade connection.
The figure below shows the function block diagram of Non-Interference Control Output
Block (XCPL):
BIN TIN TSI INT
(TSW)
VN
Signal AUT Output

IN PV MV OUT
addition processing
MAN
(MV, MV)
SUB
D012901E.EPS
Figure Function Block Diagram of Non-Interference Control Output Block (XCPL)
The figure below shows an example of mutually non-interacting control using Non-interfer-
ence Control Output Blocks (XCPL):
PID XCPL A
MV MV
VN
CALC
CALC
PID VN B
MP MV
XCPL
D012902E.EPS
Figure Example of Mutually Non-Interference Control Using Non-Interference Control Output

Block (XCPL):

terminals of the Non-Interference Control Output Block (XCPL):
Table Connection Methods and Connected destinations of the I/O Terminals of Non-Interference
Control Output Block (XCPL):
IN FB signal input
Compensation
BIN
input
Tracking signal
TIN
input
D012903E.EPS

■ Function of Non-Interference Control Output Block (XCPL) ¡ £
The XCPL block performs control computation processing, output processing, and alarm
processing.
The only processing timing available for the XCPL block is a periodic 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.
SEE ALSO
• For the types of output processing and alarm processing possible for the XCPL block, see chapter D1.1.3,
Block.”
● Control Computation Processing of Non-Interference Control Output

Block (XCPL)
The table below shows the control computation processing functions of the Non-Interfer-
ence Control Output Block (XCPL):
Table Control Computation Processings of Non-Interference Control Output Block (XCPL)
Adjusts the noninteracting compensated value (VN) using the compensation gain (CK) and
Non-interference compensation
compensation bias (CB). The adjusted value is added to the feedback input signal value
signal addition
(PV) to obtain a manipulated output value (MV).
Switches the increasing/decreasing direction of the manipulated output value (MV) in
Control action direction accordance with the increase or decrease in the feedback input signal (PB). The control
action direction of this function block is always “direct.”
Forcibly sets as the feedback input value (PV) the value calculated back from the
Output pushback manipulated output value (MV). This prevents the manipulated output value (MV) from
change abruptly.
Balance action
MAN fallback
D012904E.EPS

■ Non-Interference Compensation Signal Addition
The non-interference compensation signal addition function adds the non-interference
compensated value (VN) to the feedback input signal value (PV) to obtain a manipulated
output value (MV) during the automatic (AUT) mode.
VN
+
+
CB
CK
+
MV
PV
+
D012905E.EPS
Figure Non-Interference Compensation Signal Addition Action
The following expression is used to add the non-interference compensated value (VN) to
the feedback input signal value (PV):
MV=PV+CK • (VN+CB)+BLn
MV: Manipulated output value

PV: Feedback input signal value
VN: Non-interacting compensated value
CK: Compensation gain
CB: Compensation bias
BLn: Balance term
• Input compensation gain (CK): -10.000 to +10.000

The setting can be changed during operation.
• Input compensation bias (CB): Arbitrary engineering unit data
The default is 0.
The setting can be changed during operation.
The non-interference compensation value (VN) can be set from other function block via
data setting and also can be input via data reference from the compensation input terminal
BIN. If the compensation input terminal (BIN) is not connected, this value is considered to
the handled via data setting.
For the Non-Interference Control Output Block (XCPL), only the MV scale may be defined.
The process variable (PV) uses the same scale as the manipulated output value (MV).

The control output action applied in the Non-Interference Control Output Block (XCPL) is
“positional type” only. The computed result of non-interacting compensation signal addition
is output as a manipulated output value (MV).

The control action direction function switches the increasing/decreasing direction of the
manipulated output value (MV) in accordance with the increase or decrease in the feed-
back input signal value (PV).
The manipulated output value (MV) changes in the same direction as the change in the
process variable (PV) in “direct action,” while the manipulated output value (MV) changes
in the opposite direction to the change in the process variable (PV) in “reversed action.”
The control output action of the Non-Interference Control Output Block (XCPL) is always
“direct action.”

The bumpless switching functions available with the Non-Interference Control Output Block
(XCPL) include:
• Output pushback
• Balance action
● Output Pushback
The output pushback function sets as the feedback input value (PV), the value calculated
back from the manipulated output value (MV).
The following computational expression is used to calculate the manipulated output value
(MV):
PV=MVrb-CK • (VN+CB)-BLn
MVrb: MV output destination readback value

BLn: Balance term
In the manual (MAN) or initialization manual (IMAN) mode
BLn=0.0
When output is clamped in the automatic (AUT)
BLn=BLn-1
Output pushback is executed in the following conditions:

• In the manual (MAN) mode
• When the mode status is initialization manual (IMAN)
• When output is clamped in the automatic (AUT) mode
If the calculated value exceeds the PV range, it is limited to the MSH or MSL value.
Using the output pushback function in combination with the output tracking function en-
ables balanceless bumpless transfer of cascade loop.
1. When cascade is open, the output tracking function causes the manipulated output
value (MV) to track data at the output destination.
2. When cascade is closed, the output pushback function back calculates the manipu-
lated output value (MV), and sets the obtained value as the feedback input value (PV).
3. The output value tracking function of the upstream block in cascade causes the output
value of the upstream function block to track the feedback input value (PV).

● Balance Action
The balance action function adjusts the balance term value when the feedback input value
(PV) changes abruptly during automatic operation in the auto (AUT) or cascade (CAS)
mode, in order to prevent the manipulated output value (MV) from changing abruptly.
The BLn is adjusted by the following computational expression. Using the balance action
prevents the manipulated output value from changing abruptly when the feedback input
value undergoes an abrupt change.
BLn=MVrb-PV-CK • (VN+CB)
The Non-Interference Control Output Block (XCPL) executes this balance action when the
feedback control function block connected upstream in cascade issues a warning that the
setpoint value will be bumped.
The following are execution conditions of the balance action:
• When a Cascade Signal Distributor Block (FOUT) is connected upstream and the
conditional (CND) status of the upstream output value is canceled
• A calculation block that does not provide a balance function is connected upstream
• The initialization manual (MAN) mode is canceled while the output pushback value is
being limited to the MSH or MSL value
When the balance action is executed, BLn is moved toward “0” by the ramp constant (RP)
during each of the subsequent scan periods, until it finally reaches “0.”
• Ramp constant (RP)
Engineering unit data between 0 and the MV scale span range limit.
IMPORTANT
Observe the following rules when creating a control system that includes a Non-Interfer-
ence Control Output Block (XCPL):
• Always specify “velocity type” for the control output action of the upstream controller
blocks in cascade.
• Specify “output limiters” or “output velocity limiters” for the upstream controller blocks
in cascade in such a way that no limiting action will actually take place.
• Specify “No” for the “output compensation” specification of the upstream controller
blocks in cascade.
• To manually control the loop, change the block mode of the Non-Interference Control
Output Block (XCPL) to manual (MAN).

● Characteristics of Initialization Manual

(MAN) mode. In other words, any operation to change to the manual (MAN) mode be-
comes invalid.

vanishes:
AUT
IMAN (AUT)
AUT

(MV) is communication error (NCOM) or output failure (PTPF).
block (SW-33, SW-91) and the connection is switched off (i.e., the cascade connec-
tion is open).
• The output signal is not a pulse-width output and the data status of the input signal at
the TIN or TSI terminal has become invalid (BAD) during the tracking (TRK) mode.

■ MAN Fallback
● Characteristics of Man Fallback

state.

AUTAMAN

• When the data status of the feedback input signal (PV) is invalid (BAD).

● Characteristics of Block Mode Change Interlock

operation state. The following actions take place:
becomes invalid.


■ Data Items - XCPL
Table Data Items of Non-Interference Control Output Block (XCPL)
Item or Not
PV Feedback input signal value Value in the same engineering unit as MV MSL
VN Input compensation value ----- 0.0
RP Ramp constant 0 to (MSH - MSL) MSH - MSL
D012906E.EPS

SEE ALSO
For a list of valid block modes of the XCPL block, see a chapter D1.1.4, “Valid Block Modes for Each

<Toc> <Ind> <D1.30 Control Signal Splitter Block (SPLIT)> D1-409
D1.30 Control Signal Splitter Block (SPLIT)

Control Signal Splitter Block (SPLIT) is capable of distributing the manipulated
output signals from the upstream control loop to two output destinations via a
signal distribution switch. This block may be applied to the loops when split the
upstream signal to multiple downstream control loops with different operation
ranges.
■ Control Signal Splitter Block (SPLIT)

▼ Connection
Control Signal Splitter Blocks (SPLIT) may be applied to the multiple downstream control
loops with different operation ranges.
The figure below shows the function block diagram of Control Signal Splitter Block (SPLIT):
0
1
Range
MV1 OUT1
CAS conversion
SET CSV
3
AUT SV
RSV
RCAS 2 Range
SW MV2 OUT2
conversion
Signal distribution switch
D013001E.EPS
Figure Function Block Diagram of Control Signal Splitter Block (SPLIT)
Data setting cannot be performed to the manipulated output values (MV1, MV2) of the
Control Signal Splitter Block (SPLIT).
terminals of the Control Signal Splitter Block (SPLIT):
Table Connection Methods and Connected Destinations of I/O Terminals of Control Signal
Splitter Block (SPLIT)
I/O terminal
Data Data Terminal Process Software Function
SET Setting input
Manipulated
OUT1
output 1
Manipulated
OUT2
output 2
D013002E.EPS

■ Function of Control Signal Splitter Block (SPLIT) ¡ £
The SPLIT block performs control computation processing, output processing, and alarm
processing.
The only processing timing available for the SPLIT block is a periodic startup. Selections
SEE ALSO
• For the types of output processing and alarm processing possible for the SPLIT block, see chapter D1.1.3,
Block.”
● Control Computation Processing of Control Signal Splitter Block (SPLIT)

The table below shows the control computation processing functions of the Control Signal
Splitter Block (SPLIT):
Table Control Computation Processing Functions of Control Signal Splitter Block (SPLIT)
Signal distribution with output
Obtains two manipulated output values (MV1, MV2) based on the process variable (PV).
destination switching
Switches the increasing/decreasing direction of the manipulated output value (MVn) in
MV output action direction accordance with the increase or decrease in the setpoint value (SV). The control action
direction of this function block is set for each output destination.
Balance action
Computer failure
in the RCAS mode. This action takes place when the computer failure condition becomes
satisfied.
D013003E.EPS
● Output Processing Specific to Control Signal Splitter Block (SPLIT)

As part of its output processing, the SPLIT block employs a special “output clamp.”

■ Signal Distribution with Output Destination Switching
The figure below shows the control signal splitter action:
0
1 Range conversion
(manipulated output MV1
value computation)
3
SV
Range conversion
Signal 2 (manipulated output MV2
distribution value computation)
switch
SW
D013004E.EPS
Figure Control Signal Splitter Action

▼ SV Range
• SV Range high Limit Value:
one digit each
one digit each
The default is 0.0.
● Manipulated Output Value Computation

▼ MVn Operation Range
The Control Signal Splitter Block (SPLIT) gives two manipulated output values (MV1, MV2)
calculated from the process variable (SV). The computational expressions are shown in the
later paragraphs.
In the Function Block Detail Builder, user can preset the SV-based action range for two
manipulated outputs (SRH1, SRL1, SRH2, SRL2), the values defined should be within the
SV range. The figure below shows an example of action ranges:
MV1 MV2
MSH1 MSH2
MSL1 MSL2
SSL SV SSH
SRL1 SRL2 SRH1 SRH2

D013005E.EPS
Figure Control Signal Splitter

Use the Function Block Detail Builder to define the manipulated output value computation:
• MVn Operation Range:
Specify “SRH1,” “SRL1,” “SRH2” and “SRL2” values within the SV range.
The default for “SRH1” and “SRH2” is the SV scale high limit (SSH).
The default for “SRL1” and “SRL2” is the SV scale low limit (SSL).
The two manipulated output values (MV1, MV2) can be obtained by the following expres-
sions when the SV is meaningful:
MVi=CALCi+BLi (n)
When the MV output action direction is “direct”
MSHi-MSLi
CALCi=MSLi+ (SV-SRLi)
SRHi-SRLi D013006E.EPS
When the MV output action direction is “reverse”
MSHi-MSLi
CALCi=MSHi- (SV-SRLi)
SRHi-SRLi D013007E.EPS
MVi: Manipulated output (i=1 or 2)

CALCi: Manipulated output computed value
BLi (n): Balance term
SV: Setpoint value
MSHi MVi scale high limit
MSLi MV i scale low limit
SRHi MV i action range high limit
SRLi MVi action range low limit

● Signal Distribution Switch
The normal actions of the Control Signal Splitter Block (SPLIT) consist of computing a
manipulated output value for each output point based on the setpoint value and distributing
signals to both output destinations. However, the signal distribution action can be limited to
a specific output point by operating the signal distribution switch (SW).
The table below shows the signal distribution switch positions and corresponding actions:
Table Signal Distribution Switch Positions and Corresponding Actions:
0 Stops signal distribution.
1 Distributes signals to MV1 only.
2 Distributes signals to MV2 only.
3 Distributes signals to both output points.
D013008E.EPS
The value at the manipulated output point that has not been selected by the signal distribu-
tion switch is always caused to agree with the value at the output destination via output
tracking.

period to an actual manipulated output value (MV). The action to convert a change of the
manipulated output to an actual manipulated output value (MV) is called “control output
action.” The control output actions available with Control Signal Splitter Block (SPLIT) are
of “positional type.” The result of manipulated output computation corresponding to the
signal distribution switch position, is output as the manipulated output value (MV).

▼ MVn Output Direction
The control action direction function switches the increasing/decreasing direction of a
manipulated output value (MVn) corresponding to the increase or decrease in the setpoint
value (SV).
The manipulated output value (MV) changes in the same direction as the change of the
setpoint variable (PV) is called “direct action,” while the MV value changing to the reverse
direction to the change of PV is called “reverse action.”
Use the Function Block Detail Builder as define the control action direction:
• MV1 Output Direction/MV2 Output Direction: Select “Direct” or “Reverse”
The default is “Direct.”

the setpoint high limit (SVH) and setpoint low limit (SVL), and recognizes the setpoint
values (SV) only within this range as valid.
function block.
● Actions in Automatic (AUT) Mode

When the block mode of the function block is automatic (AUT) and user is to set the
setpoint value, the setpoint value limiter performs the following actions in accordance with
the situation:
• When a value exceeding the setpoint high limit (SVH) is set as the setpoint value (SV)
• When a value below the setpoint low limit (SVL) is set as the setpoint value (SV)
● Actions in Remote Cascade (CAS) Mode

When the function block is in the remote cascade (RCAS) mode and the remote setpoint
value (RSV) from a supervisory system computer is automatically set as the setpoint value
(SV), the setpoint value limiter performs the following actions:
• A value exceeding the setpoint high limit (SVH) is limited to the setpoint high limit
(SVH).
• A value below the setpoint low limit (SVL) is limited to the setpoint low limit (SVL).
● Set Parameters of Setpoint Value Limiter


RSV CSV
AUT
RCAS CAS
SV
Setpoint value
Control
computation
D013009E.EPS
function block.
● Action in Automatic (AUT) Mode

● Action in Cascade (CAS) Mode

● Action in Remote Cascade (RCAS) Mode


status.
The type of bumpless switching performed by the Control Signal Splitter Block (SPLIT) is
“balance action.”
The balance action adjusts the balance term value when the feedback input value (PV)
changes abruptly during automatic operation in the auto (AUT) or cascade (CAS) mode, in
order to prevent the manipulated output value (MV) from changing abruptly.
Using the balance action enables bumpless switching of block modes from automatic
(AUT) to cascade (CAS).
The balance action prevents the manipulated output value from changing abruptly when
the operating condition of the plant has changed.
The following computational expression is used to adjust BLi:
BLi (n)=MVRBi-CALCi
BLi (n): Balance term (i=1 or 2)

MVRBi: Manipulated output readback value
CALCi: Manipulated output computed value
The execution conditions of the balance action (switching of operating conditions):

• When signal distribution is started after the setting of the signal distribution switch
(SW) has been changed
• When the initialization manual condition is canceled during signal distribution
• When an initialization request is issued from an upstream block in cascade during
signal distribution
• When an initialization request is issued from an output destination function block
during signal distribution
When the balance action is executed, BLi is moved toward “0” by the specified value of
ramp constant (RP) during each of the subsequent scan periods, until it finally reaches “0.”
• MV1 ramp constant (RP1):
Set engineering unit data between 0 and the MV1 scale span range limit.
The default is the MV1 scale span.
• MV2 ramp constant (RP1):
Set engineering unit data between 0 and the MV2 scale span range limit.
The default is the MV2 scale span.
TIP
Initialization requests from upstream blocks are issued automatically.



vanishes:
AUT
IMAN (AUT)
AUT
The initialization manual condition for the Control Signal Splitter Block (SPLIT) is satisfied
in the following cases:
• When SW=1 and the initialization manual condition is established at the connected
destination of the OUT1 terminal.
• When SW=2 and the initialization manual condition is established at the connected
destination of the OUT2 terminal.
• When SW=3 and the initialization manual condition (same as above) is satisfied at the
connected destinations of the OUT1 and OUT2 terminals.

block (SW-33, SW-91) and the cascade connection is switched off (i.e., the cascade

■ AUT Fallback

Once the AUT fallback condition establishes, the block mode will remain automatic (AUT)
even after the condition later vanishes.

tected in the cascade setpoint value (CSV) for some reason.
The following example shows when the AUT fallback condition is established:
CASAAUT
Use the Function Block Detail Builder to define whether or not to use the AUT fallback.

■ Computer Fail
cascade (RCAS) mode temporarily and switches to the computer backup mode.

When the function block mode is remote cascade (RCAS), the function block receives the
setpoint value (SV) or manipulated output value (MV) from a supervisory system computer
via control bus communication.
(AUT or CAS) which indicates that an abnormality has been detected in the supervisory
computer. When the computer recovers, the block returns to the mode before the change.
The following actions take place when the computer failure condition exist and a block
mode change command from AUT or CAS to RCAS is sent:
1. When a block mode change command from AUT or CAS to RCAS is sent while the
computer fails (BSW=ON), the function block does not switch to the computer backup
mode directly but switches to the transient state mode first.
before the execution of the block mode change command (AUT, CAS) and a remote
mode (RCAS).
mode set via the Function Block Detail Builder (AUT, CAS) and a remote mode
(RCAS).
block mode changes to remote cascade (RCAS).

the remote cascade (RCAS) mode and switches the mode to the computer backup mode.
mode. The status of this switch determines whether the computer has failed or recovered.
The value of the backup switch (BSW) can be set from a sequence table or other function
blocks.
on a block mode other than remote cascade (RCAS)
RCAS
? Computer fails
AUT (RCAS)
? Computer recovers
RCAS

tion block.
Select “AUT” or “CAS” as the mode to be switched to when the computer becomes
down.
The default is “AUT.”

■ Output Clamp
The output clamp is a function that limits the manipulated output value (MV) in such a way
that it cannot be changed to a value greater than or less than the current output value. The
status where the manipulated output value (MV) is limited in this way is called the output
clamp status.
In the SPLIT block, the output clamp statuses for manipulated output values MV1 and MV2
respectively are indicated as data status high limit clamp (CLP+) and low limit clamp (CLP-).
The clamp status of the cascade setpoint value (CSV) is as follows:
• When SW=0
There is no clamp data status.
• When SW=1
When the MV1 output operation is direct, the clamp status is the same as for MV1. For
reverse operation, if MV1 is CLP+ status, then the status is CLP-, if MV1 is CLP-
status, then the status is CLP+.
• When SW=2
When the MV2 output operation is direct, the clamp status is the same as for MV2. For
reverse operation, if MV2 is CLP+ status, then the status is CLP-, if MV2 is CLP-
status, then the status is CLP+.
• When SW=3
If output operation is direct and both MV1 and MV2 are CLP+ status, or if output
operation is reverse and MV1, MV2 are CLP- status, then the status becomes CLP+.
Or, if the output operation is direct and both MV1 and MV2 are CLP- status, or if the
output operation is reverse and MV1, MV2 are CLP+, then the status becomes CLP-.
SEE ALSO
For details on the output clamp, see a chapter C4.3, “Output Clamp.”

■ Data Items - SPLIT
Table Data Items of Control Signal Splitter Block (SPLIT)
Entry Permitted
or Not
RSV Remote setpoint value Value in the same engineering unit as SV SSL
MV1 Manipulated output value 1 MV1 engineering unit value MSL1
MV2 Manipulated output value 2 MV2 engineering unit value MSL2
RP1 MV1 ramp constant 0 to (MSH1 - MSL1) MSH1 - MSL1
RP2 MV2 ramp constant 0 to (MSH2 - MSL2) MSH2 - MSL2
SW Signal distributor switch 0, 1, 2, 3 0
D013010E.EPS

MSHn:MVn scale high limit
SEE ALSO
For a list of valid block modes of the SPLIT block, see a chapter D1.1.4, “Valid Block Modes for Each

<Toc> <Ind> <D1.31 Representative Alarm Block (ALM-R)> D1-424
D1.31 Representative Alarm Block (ALM-R)

Representative Alarm Block (ALM-R) manages the alarms initiated from up to 16
function blocks. This block may be applied to inhibit the unnecessary alarm notifica-
tions from the function blocks.
■ Representative Alarm Block (ALM-R)

▼ Representative Alarm
The Representative Alarm Block (ALM-R) controls alarms initiated from up to 16 function
blocks. The block has function to activate or inhibit the alarms sent from other function
blocks.
The figure below shows the function block diagram of Representative Alarm Block (ALM-
R):
Representative alarm
ALRM Alarm
priority SW
masking
Input masking SV
Q01 Q02 Q16
Function Function Function

block 1 block 2 block 16
Alarm masking command

D013101E.EPS
Figure Function Block Diagram of Representative Alarm Block (ALM-R)
terminals of the Representative Alarm Block (ALM-R):
Table Connection Methods and Connected destinations of the I/O Terminals of Representative
Alarm Block (ALM-R):
Q01 to Q16 Alarm input (*1)
D013102E.EPS
*1: Connection allowed to any input terminal only when specifying an annunciator message to a software I/O.

■ Function of Representative Alarm Block (ALM-R) ¡ £
The ALM-R block performs only alarm processing.
The only processing timing available for the ALM-R block is a periodic startup. Selections
SEE ALSO
• For the types of alarm processing possible for the ALM-R block, see chapter D1.1.3, “Input Processing,
Output Processing, and Alarm Processing Possible for Each Regulatory Control Block.”
■ Alarm Input Specification

The targets of a maximum of 16 alarm inputs that can be controlled by a Representative
Alarm Block (ALM-R):
• Alarm status of function blocks
• Annunciator messages
To specify an alarm input controlled by the representative alarm, use the Function Block
Detail Builder to specify a tag name for the corresponding function block or annunciator
message.
Each function block has a number of alarm items. The alarm processing range, i.e.,
whether all alarm items of a function block are regarded as input targets or only some of
them are regarded, can be specified for each input terminal. The alarm processing range
specification is determined by the priority level of the alarm.
Specify one of the following four types of alarm processing ranges for each input terminal:
Range setting Target alarms

Full alarm All alarms
Medium-priority alarm or lower Alarms excluding high-priority alarms
Low-priority alarm or lower Alarms excluding high- and medium-priority alarms
Logging alarm or lower Alarms excluding high-, medium- and low-priority alarms
D013103E.EPS
Those alarms excluded from the alarm processing range cannot be controlled collectively
by the Representative Alarm Block (ALM-R). Individual alarms of the annunciator mes-
sages or function blocks that are specified as input targets of the Representative Alarm
Block (ALM-R) are notified via the block. Alarm notifications issued directly to operation and
monitoring functions are masked. However, the target of this alarm masking is limited by
priority masking

■ Representative Alarm Processing
The Representative Alarm Block (ALM-R) checks the status of all alarm inputs and deter-
mines its own alarm status (representative alarm) based on the alarm of the highest priority.
The table below shows the alarm statuses of the Representative Alarm Block (ALM-R):
Table Table of Alarm Statuses of Representative Alarm Block (ALM-R)
Alarm status Name
NR Normal
HALM High-priority alarm present
MALM Medium-priority alarm present
LALM Low-priority alarm present
RALM Logging alarm present
CNF Connection failure alarm
D013104E.EPS
For example, if the most important alarm among all alarms present is a medium-priority
alarm, the alarm status becomes “medium-priority alarm present (MALM).”
When the status of this representative alarm changes, a process alarm message is initiated
for output.
The alarm masking function is also effective on representative alarms. For example, if a
Representative Alarm Block (ALM-R) is specified as an input source of another Represen-
tative Alarm Block (ALM-R), the representative alarm of the input source can be masked.
Using this method, a nested alarm filtering system can be configured.
The alarm detection specification of the Representative Alarm Block (ALM-R) is always
fixed to detection “Yes” for all alarms shown in the “Table of Alarms of Representative Alarm
Block (ALM-R)” except connection failure alarms.
By the input masking function explained in the following page, certain alarm inputs of the
Representative Alarm Block (ALM-R) may be excluded from the targets of above represen-
tative alarm processing.

■ Input Masking
The input masking function specifies by the setpoint value (SV), which input points are and
are not regarded as a target of representative alarm processing among the 16 alarm input
points connected to the input terminals.
Input masking is performed by setting as setpoint value (SV), an input masking pattern
represented by a numeric value between 0 and 15. The setpoint value (SV) can be
changed via setting from operation and monitoring functions or other function block.
The table below shows the setpoint values (input masking patterns) and corresponding
targets of representative alarm processing:
Table Setpoint Values and Corresponding Targets of Representative Alarm Processing
SV Target of representative alarm processing
0 No input is regarded as a target of representative alarm processing
1 All inputs are regarded as targets of representative alarm processing
2 to 15 Defined by the user
D013105E.EPS
When the setpoint value (SV) is 2 through 15, the targets of representative alarm process-
ing can be defined using the Function Block Detail Builder. Define the targets for each of
the Representative alarm blocks (ALM-R) used, by the following methods:
Table Table of Input Masking Patterns
SV
Input point
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
1 . Y
2 . Y
3 . Y
4 . Y Defined by the user
‘Y’ or ‘N’ or ‘.’
···
16 . Y
D013106E.EPS
Specify “Y,” “N” or “.” for each entry column in the table of input masking patterns, where the
X axis and Y axis represent the setpoint value (SV) and input point, respectively. “Y,” “N”
and “.” have the following meanings:
“Y”: Regarded as a target of representative alarm processing.
“N”: Not regarded as a target of representative alarm processing.
Alarm of the input source are unmasked.
“.” : Not regarded as a target of representative alarm processing.
The alarm masking status of alarms at the input source is not manipulated at all.
Note that when the specification changes from “Y” to “.” following a change in the setpoint
value (SV), the current alarm masking status is held as is.
After the specification of an input point is changed from “Y” to “.,” alarm notifications will no
longer be transmitted from the function block corresponding to the input point or from the
Representative Alarm Block (ALM-R).
When the alarm masking status at the connected destination of an input terminal is
changed from unmasked to masked, the first alarm that occurs at this connected destina-
tion after the change will not be masked. Therefore, caution should be exercised when
changing the input masking pattern from “N” to “Y,” from “N” to “.,” or from “.” to “Y.”

■ Priority Masking
The priority masking function specifies the range of alarm masking via the priority masking
switch (SW) for each alarm of the annunciator message and function block that is con-
nected to a terminal of the Representative Alarm Block (ALM-R).
Priority masking targets the alarms included in the alarm processing range.
● Specification of Priority Masking

Priority masking is specified by setting a numeric value between 0 and 5 for the priority
masking switch. The table below shows the priority masking switch (SW) values and
corresponding alarm masking actions:
Table Priority Masking Switch Values and Alarm Masking Actions
SW Name Action
0 No masking Does not manipulate the alarm masking status at all.
1 Full alarm masking Performs alarm masking (AOF) to all alarms at once.
Masks medium-priority alarms and alarms of lower priorities.
2 Medium-priority alarm masking
Only high-priority alarms are not masked.
Masks low-priority alarms and alarms of lower priorities.
3 Low-priority alarm masking
High- and medium-priority alarms are not masked.
Masks logging alarms and alarms of lower priorities.
4 Logging alarm masking
High-, medium- and low-priority alarms are not masked.
Masks the alarms whose priority is lower than that of the
highest-priority alarm currently occurred in the connected function block.
5 Dynamic masking
Only the alarm of the highest priority at the moment is not
masked.
D013107E.EPS
Among all alarms at the alarm inputs of the Representative Alarm Block (ALM-R), those of
the priority (priority level) specified by the value of the priority masking switch (SW) or lower
will be masked. In case of priority mask, all the alarms of the connected function block with
lower level than the alarm of the highest priority level occurred so far will be masked.
The priority masking switch (SW) can be changed by the operator or via setting operation
from other function block.

When the setting of the priority masking switch (SW) is changed, any changes in the alarm
masking status will be limited by the priorities that are included in the alarm processing
range specified by the builder. The table below shows alarm masking ranges for different
combinations of the alarm processing range specification and SW setting:
Table Alarm Masking Ranges
“Alarm processing range” specification by the builder
SW
Medium-priority alarm
Full alarm Low-priority alarm or lower Logging alarm or lower
or lower
0 Alarm masking status is not manipulated at all.
1 Full alarm
Medium-priority alarm or
Medium-priority alarm or lower
2 Low-priority alarm or lower
lower Logging alarm or lower
3 Low-priority alarm or lower Low-priority alarm or lower
4 Logging alarm or lower Logging alarm or lower Logging alarm or lower
5 (*1) (*2) (*3) (*4)
D013108E.EPS
*1: The alarm masking range covers those alarms occurred in the connected function block whose priority is lower than
that of the most important alarm currently present.
that of the most important alarm currently present among medium-priority alarms and alarms of lower priorities.
that of the most important alarm currently present among low-priority alarms and alarms of lower priorities.
that of the most important alarm currently present among logging alarms and alarms of lower priorities.

● Action Example of Priority Masking
The figure below shows an example of how the alarm masking status changes during
priority masking when dynamic masking (SW=5) is specified:
HH (high-priority alarm)
HI (medium-priority alarm)
DEV (low-priority alarm)

Legend
Alarm masking status
D013109E.EPS
Figure Action of Dynamic Masking (SW=5)
In this example, the builder-specified alarm range is assumed to be “All alarms.” The figure
is based on a scenario in which a high-priority alarm, medium-priority alarm and low-priority
alarm have occurred simultaneously at a function block controlled by the Representative
Alarm Block (ALM-R), to depict how the alarm masking status changes, or how the alarm
status is recovered in the order of higher to lower priority alarms.
Among all alarms present, only the alarm of the highest priority is not subject to masking.
Dynamic masking checks the priority level of alarms in each function block. For an ex-
ample, if a function block is sending an alarm with high priority level, the new alarms with
lower levels will be masked. While if another function block connected in the same ALM-R
is in normal status, an new alarm with medium level sent from this block will not be masked.
So that it is useful to used dynamic masking for handling alarms with multiple priority levels.
● Inhibiting Alarm of Connected Function Block

The alarms of a function block that connected to ALM-R can be inhibited by changing the
state of the priority level switch (SW) on ALM-R block.
• No masking (SW=0)
The current alarm masking status of the input source is held.
This also applies to the action of specifying “N” by switching the setpoint value (SV).
Although the alarms for which “N” is specified are normally unmasked, they are not
unmasked if the SW value is 0.
• Dynamic masking (SW=5)
The alarm masking status of the input source is set every period in accordance with
the alarm occurrence status.
• Other masking (SW=1, 2, 3, 4)
The alarm masking status of the input source is set only when the setting of the priority
masking switch (SW) or SV has been changed.
In some cases the alarm masking status of a function block controlled by the Representa-
tive Alarm Block (ALM-R) may not be changed directly from operation and monitoring
functions or via other means.

IMPORTANT
During on-line maintenance, merely changing the alarm processing level of the tag as-
signed to a connected destination of the Representative Alarm Block (ALM-R) does not
make the Representative Alarm Block (ALM-R) a target of on-line loading. In this case,
discrepancies may occur between the Representative Alarm Block (ALM-R) and the
connected destination block, causing actions to become unstable. Specify the representa-
tive alarm itself as a target of on-line loading, as well.
■ Data Items - ALM-R

Table Data Items of Representative Alarm Block (ALM-R)
Entry Permitted
or Not
SV Setpoint value SV engineering unit value 1
SW Priority masking switch 0 to 15 0
D013110E.EPS

SEE ALSO
For a list of valid block modes of the ALM-R block, see D1.1.4, “Valid Block Modes for Each Regulatory
Control Block.”

<Toc> <Ind> <D1.32 Pulse Count Input Block (PTC)> D1-432
D1.32 Pulse Count Input Block (PTC)

Pulse Count Input Block (PTC) counts process values that are products of pulse
signals multiplied by the pulse conversion coefficient. This block may be applied to
count process values obtained by multiplying the input pulse signals by pulse
conversion coefficient.
■ Pulse Count Input Block (PTC)

▼ Connection
Pulse Count Input Block (PTC) counts process values that are products of pulse signals
multiplied by the pulse conversion coefficient. In addition, the Pulse Count Input Block
(PTC) has a preset counter function.
Counting operations of the counter, such as issuing of reset and hold commands, are
performed from a sequence control block, calculation block or other function blocks. The
block status that indicates the action status can be referenced from other function blocks.
The figure below shows the function block diagram of Pulse Count Input Block (PTC):
CTUP
PH
DL - PALM
Input Count
IN PV OUT
RMV HSW
D013201E.EPS
Figure Function Block Diagram of Pulse Count Input Block (PTC)
terminals of the Pulse Count Input Block (PTC):
Table Connection Methods and Connected Destinations of I/O Terminals of Pulse Count Input
Block (PTC):
I/O terminal Data Data Condition Status Terminal Process Software Function
reference setting testing manipulation connection I/O I/O block
Measurement
IN
input
Manipulated
OUT
output
D013202E.EPS

■ Function of Pulse Count Input Block (PTC) ¡ £
The PTC block performs input processing, control computation processing (count process-
ing), output processing, and alarm processing.
The only processing timing available for the PTC block is a periodic startup. Selections
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the PTC block,
see chapter D1.1.3, “Input Processing, Output Processing, and Alarm Processing Possible for Each
● Input Processing Specific to Pulse Count Block (PTC)

The PTC block performs special input signal conversions.
● Control Computation Processing of Pulse Count Block (PTC)

The PTC block performs count processing as its control computation processing. The
count processing contains the following functions.
• Counter update operation
• Preset counter function
• Pause operation
• Restart operation
● Output Processing Specific to Pulse Count Block (PTC)

The PTC block performs special output signal conversions.

■ Input Signal Conversion of Pulse Count Input Block (PTC)
▼ Pulse Conversion Factor
The input signal conversion for the Pulse Count Input Block (PTC) counts the increments of
integrated pulse count values (P) read from the input connection terminal then multiply it by
the pulse conversion factor to convert it into count value (PV).
The following is the computational expression for the count value (PV):
PVn = Pfactor • (Pn - Pn-1)+PVn-1
P: Integrated pulse count value

Pfactor: Pulse conversion factor
PV: Count value, decimal-point notation is valid, the value returns to 0 when exceeding 8 digits.
The subscripts “n” and “n-1” indicate the number of sampling scan periods.
The setup for the pulse conversion factor can be executed on the Function Block Detail
Builder.
• Pulse Conversion Factor: Within the range between 0.001 to 1000

■ Counter Updating Operation
When a counter reset command is received, counting is started after the counter value
(PV) is reset to “0.” Counter reset command is issued by setting the reset command switch
(data item: RST) to “1” from operation and monitoring functions or a sequence control
block. The reset command switch (RST) automatically returns to “0” when the reset com-
mand is executed.
When a counter reset command is received, the block status changes to normal (NR).
When counting, PV is updated every scan period.
PV
PH
DL
Block
NR PALM NR PALM CTUP
status
Reset Reset
command command D013203E.EPS
Figure Basic Pulse Counting Action

■ Preset Counter Function
The preset counter function notifies when the count value (PV) has reached the preset
number.
Besides this count-up completed notification function based on the presetpoint (PH), the
Pulse Count Input Block (PTC) also has the pre-alarm function by which a warning is
issued before the presetpoint is reached.
When the block mode is automatic (AUT), the block status changes to pre-alarm (PALM) or
count-up completed (CTUP) when the following conditions are satisfied:
• Pre-alarm (PALM) status
0DVDL
DV=PH-PV
DV: Remaining count value

DL: Pre-alarm setpoint (8 digits)
PH: Presetpoint (8 digits)
PV: Count value
• Count-up completed (CTUP) status
PH-PV0
PH: Presetpoint (8 digits)

PV: Count value
The pre-alarm (PALM) status and count-up completed (CTUP) status are mutually exclu-
sive. When DV=0, the pre-alarm (PALM) status is canceled and changes to count-up
completed (CTUP).
When the setting is DL=0, the status will never become pre-alarm (PALM).
The setting of PH and DL can be changed during operation as set parameters.
The count value continues to be updated even after the count-up completed (CTUP) status
is obtained. When the count value exceeds 8 digits, PV changes to “0” and the block status
returns to normal (NR) before counting is continued.

■ Pause Operation
A pause command is issued by setting the hold command switch (data item: HSW) to “1”
from operation and monitoring functions or via other function blocks such as a sequence
control block or calculation block. When a pause command is received, the counter action
stops temporarily. The counter value and other data are held during the pause. The current
block status of normal (NR), pre-alarm (PAL) or count-up completed is held, while a new
pause (PAUS) status is added. The block status display on the operation and monitoring
functions shows only the pause (PAUS) status that has a higher priority.
When a counter reset command is received in a pause (PAUS) state, the count value is
reset to “0” and the currently held block status (NR, PALM or CTUP) is changed to NR.
The figure below shows an example of pause/restart actions of the pulse-count block:
PH
DL
DV
PV
Block status NR PALM CTUP NR

PAUS PAUS
Operation command Pause Pause Pause Reset Pause

command canceled command command canceled
D013204E.EPS
Figure Example of Pause/Restart Actions of the Pulse-Count Block
■ Restart Operation
The pause command is canceled by setting 0 for the hold command switch (data item:
HSW). When the pause command is canceled, the count action currently in pause (PAUS)
is resumed. The pause (PAUS) status is removed from the block status, and the original
status that has been saved is recovered. Updating of the count value resumes from the
value that has been held.
■ Output Signal Conversion of the Pulse Count Input Block (PTC)

In the Pulse Count Input Block (PTC), a processing specific to the PTC Block takes place
when it is connected in sequence connection.
If the output terminal is defined to the manipulation of sequence connection status, then its
status can be manipulated according to the block status of the PTC Block.
Table Description of Manipulation for Each Block Status
Block status Description of manipulation
CTUP plus NOT PAUS Status manipulation for the logical value “true” is executed.
(NR or PALM) plus NOT PAUS Status manipulation for the logical value “false” is executed.
PAUS Not valid
D013206E.EPS

■ Data Items - PTC
Table Data Items of Pulse Count Input Block (PTC)
Entry Permitted
or Not
PV Count value ----- SL
PH Presetpoint ----- SH
DV Remaining count value ----- -----
DL Pre-alarm setpoint Value in the same engineering unit as PV 0
PL PV initial value 0 0
RST Reset command switch 0, 1 0
HSW Hold command switch 0, 1 0
D013205E.EPS

SEE ALSO
For a list of valid block modes of the PTC block, see chapter D1.1.4, “Valid Block Modes for Each Regula-
■ Block Status of Pulse Count Input Block (PTC)

Table Block Status of Pulse Count Input Block (PTC)
Block Status
Level Description
Symbol Name
2 PAUS Pause Pauses pulse counter
CTP Count Up Counter reaches a preset value
1 PALM Pre-Alarm Counter reaches Pre Count Up.
NR Normal Counting or CTUP, PALM not active.
D013207E.EPS

<Toc> <Ind> <D1.33 Control Operations of YS Blocks> D1-439
D1.33 Control Operations of YS Blocks

The YS80/YS100 communication blocks (hereinafter referred to as YS blocks) are
function blocks designated to act as gateways for displaying the faceplate of the
YS100 SERIES/YEWSERIES 80/YEWSERIES BCS electronic control systems (herein-
after referred to as YS instruments) via the operation and monitoring function of the
HIS. The YS instruments are connected via the ALR121 modules of the KFCS2/
KFCS, via the ACM12 modules of the PFCS/LFCS2/LFCS/SFCS (RS-422/RS-485
communication modules) or the LCS (loop communication card) of the migrated
FCS (RFCS5, RFCS2). Function block models, such as SLCD and SLPC, are avail-
able for respective YS instruments.
■ YS Block Functions
The YS block offers the following functions:
• Operation and monitoring of YS instruments from the HIS
Operates and monitors YS instruments via the YS block.
• Cascade control of YS instruments and FCS function blocks
By using the SET terminal of the YS block, a cascade loop can be created for the FCS
of the function block and the YS instruments, which are used as a slave loop.
Similar to the faceplate block, the YS block has no special control algorithm. This function
block simply sends and receives data to/from the YS instruments connected to it.
The YS block is used to operate and monitor YS instruments from the HIS, or to control
them from an FCS or supervisory computer.
■ Correspondence between Function Block Models and YS Instruments

See the table below to select the applicable YS block according to the YS instrument to be
connected.
Table YS Block Model List
Function Block Corresponding Corresponding Corresponding
Model YS80 Instrument YS BCS Instrument YS100 Instrument
SLCD SLCD
SLPC SLPC YS170, YS150
SLMC SLMC
SMST-111 SMST-111 YS135
SMST-121 SMST-121 YS136
SMRT SMRT
SBSD SBSD
SLBC SLBC
SLCC SLCC
STLD STLD
D013301E.EPS

D1.33.1 Applying YS Blocks

The YS block is a function block operating on the FCS. YS instruments can be oper-
ated and monitored from the HIS via the YS block on the FCS.
■ Positioning of the YS Block within the System

Similarly to other function blocks, the YS block is generated with a tag name via the Engi-
neering function and is executed periodically on the FCS. It can also be connected with
other function blocks. The HIS displays the YS block’s process data or parameters, such as
PV, SV, and MV. This allows for indirect operation and monitoring of YS instruments via the
YS block.
The figure below shows the positioning of the YS block within the system.
MODE = AUT ALRM = NR HIS Operation and Monitoring Window

PV : 55.0 PH = 100.0
SV = 60.0 PL = 0.0
MV = 59.0
z FCS
YS instrument OUT
PID
SET
IN
YS block
D013302E.EPS
Figure YS Block Positioning
IMPORTANT
The YS block and YS instruments are connected via the ALR121/ACM12 on the PFCS/
KFCS2/KFCS/LFCS2/LFCS/SFCS. In such cases, do not use the YS block in ROUT mode
or RCAS mode since high-speed communications cannot be achieved. If the YS block and
YS instruments are connected via the LCS in the migrated FCS (RFCS5, RFCS2), to use
the YS block in ROUT mode and send a manipulated output value from a controller block
(such as PID) to a YS instrument via the YS block, select “execute YS block before control-
ler block.”
SEE ALSO
For more information on communication time, see J7, “YS Instrument Communication.”

D1.33.2 Common Specification of YS Blocks

The YS block provides the following common specification of function block mod-
els.
• Block Mode Tracking Function
• Data Tracking Function
• Input Processing
• Fully-open/Tightly-shut
• Alarm Processing
• Others
• Processing Timing
■ Overview of Common Specification of YS Blocks

The following describes common specifications of YS block. Some YS block models may
not have block modes or data items that correspond to the functions described below.
● Block Mode Tracking Function

This function synchronizes the YS block mode and the operation mode of the YS instru-
ment. It notifies the YS instruments of a change made from the HIS or Sequence Control
functions to the YS block mode as an operation change. This function also detects changes
in the operation mode of the YS instruments and changes the YS block mode accordingly.
● Data Tracking Function

This function synchronizes process data and various control parameters between the YS
block and YS instruments.
Among process data of the YS block, PVs are processed via the standard input signal
processing function.
● Fully-Open/Tightly-Shut
When the YS block is in either MAN or ROUT mode and attempts to set an MV to the YS
instruments, the Fully-open or Tightly-shut function will be executed according to the
setting corresponding to that particular value. When the Fully-open/Tightly-shut function is
executed, the manipulated value of the YS instrument will be -6.3 % or +106.3 %.
The YS block performs the following two types of alarm processing:
• The YS block references the alarm function of the YS block and sends a message as
a process alarm.
• The YS block independently checks an alarm and sends a message as a process
alarm.

■ Block Mode Tracking Function
This function synchronizes the YS block mode and the operation mode of the YS instru-
ment. It notifies the YS instruments of a change made from the HIS or Sequence Control
functions to the YS block mode as an operation change. This function also detects changes
in the operation mode of the YS instruments and changes the YS block mode accordingly.
The operation of a YS instrument, while in cascade mode, is either Analog CAS or Commu-
nication CAS.
• Analog CAS
Acquires an SV from the analog cascade setting input terminal of the YS instrument.
• Communication CAS
Sets an SV from the FCS (when the SPC/DDC flag of the YS instrument is SPC), or
sets an MV from the FCS (when the SPC/DDC flag of the YS instrument is DDC).
The setting made on the YS instrument determines whether Analog CAS or Communica-
tion CAS is used.
The block mode change operation will differ between Analog CAS and Communication
CAS.
IMPORTANT
In Communication CAS, do not use the YS block in RCAS or ROUT mode for the PFCS/
KFCS2/KFCS/LFCS2/LFCS/SFCS that communicate with YS instruments via the ALR121/
ACM12, since high-speed communications cannot be achieved. The YS block can be used
in CAS mode.
● Mode Changes for Analog CAS

In Analog CAS, set points are entered from other YS instruments.
FCS
YS block
IN
CIN
IN IN MV
MV
D013303E.EPS
Figure Connection Example for Analog CAS

When using the YS instrument in Analog CAS, the mode changes will be as shown below.
Circles
CAS Upper row: YS Block Mode
CAS Lower row: YS Instrument Operation Mode
Arrows
C: Mode change to CAS on DCS or YS
A: Mode change to AUT on DCS or YS
M: Mode change to MAN on DCS or YS
A M
C
A
AUT MAN
AUT MAN
M
D013304E.EPS
Figure Mode Changes for Analog CAS
In Analog CAS, the YS instrument’s mode changes are handled in the same way as the YS
block’s mode changes made from the HIS or sequence table. When in MAN mode, neither
YS block mode nor YS instrument’s operation mode can be switched to CAS mode.
In Analog CAS, the cascade setting input value on the YS instrument will be used as an SV
in CAS mode. The YS block matches its SV value to the SV value on the YS instrument
side. If the SET terminal of the YS block is connected, the IMAN status of the master loop
will not be changed even when the mode is switched to CAS. In RCAS or ROUT mode, no
controls can be performed from the supervisory computer.

● Mode Changes when Using the Set Terminal in Communication CAS
In Communication CAS, the mode changes differ depending on whether the SET terminal
of the YS block is used.
If the SET terminal of the YS block is used in Communication CAS, a value entered from
the SET terminal is set in the YS instrument in CAS mode. RCAS and ROUT modes are
not available.
FCS
OUT
PID
SET
YS block
IN
PV MV
D013305E.EPS
Figure Connection when Using the Set Terminal in Communication CAS

When using the SET terminal in Communication CAS, the mode changes will be as shown
below.
******
BUAorBUM
FCS
Fail FCS Circles
Recover Upper row: YS Block Mode
Lower row: YS Instrument Operation Mode
CAS BU: AUT or MAN
SPC
Arrows
M C: Mode change to CAS on either DCS or YS
A: Mode change to AUT on either DCS or YS
A M: Mode change to MAN on either DCS or YS
C
A
AUT MAN
AUT MAN
M
D013306E.EPS
Figure Mode Changes when Using the SET Terminal in Communication CAS
When mode is changed from AUT to CAS, the YS block will enter CAS mode and the YS
instrument will enter SPC mode.
When changing from MAN mode to CAS mode, it is necessary to change from MAN to AUT
first, then to CAS.
A YS instrument will enter the backup mode when the FCS fails while its YS block is in CAS
mode. A setting on the YS instrument can be set to determine whether the backup mode
will be MAN or AUT.

● Mode Changes when the SET Terminal is not Used in Communication CAS
IMPORTANT
Do not use the PFCS/KFCS2/KFCS/LFCS2/LFCS/SFCS, which communicate with YS
instruments via the ALR121/ACM12, by setting the YS instrument to Communication CAS
but without using the SET terminal of the YS block.
If the SET terminal is not used in Communication CAS, the YS block will not enter CAS
mode. Any attempt on the YS instrument to set the mode to CAS will switch the mode to
RCAS or ROUT.
To control the YS instruments through DDC via PID block and use them as a backup of the
FCS, connect the PID and YS block as shown below. The PID output is enabled when the
YS block is in ROUT mode. In other modes, the PID enters IMAN mode and tracks the MV
of the YS block.
FCS
IN OUT
PID
YS block
PV RMV
PV MV
D013307E.EPS
Figure Connection Example when the SET Terminal is not Used in Communication CAS

Circles
Upper row: YS Block Mode
Lower row: YS Instrument Operation Mode
****** ******
BUAorBUM BUAorBUM Arrows
C: Mode change to CAS
A: Mode change to AUT
M: Mode change to MAN
FCS FCS FCS FCS RCAS: Mode change to RCAS
Recover Fail Recover Fail ROUT: Mode change to ROUT
: Mode change on the DCS
: Mode change on the YS instrument
Other symbols indicate mode changes
RCAS ROUT
from one or the other.
SPC DDC
A M
C RCAS ROUT C
A
AUT MAN
AUT MAN
M
D013308E.EPS
Figure Mode Changes when the SET Terminal is not Used in Communication CAS
During MAN mode, if an attempt is made on the YS instrument to change the mode to
CAS, that operation will be disabled if the SPC/DDC flag of the YS Instrument Internal
Status is SPC. If the SPC/DDC flag is DDC, the YS instrument enters DDC mode, and the
YS block enters ROUT mode. The SPC/DDC flag status is determined by the previous
remote mode.
Only AUT mode can be changed to RCAS mode, while only MAN mode can be changed to
ROUT mode.

● Mode Changes Specific to the SMST Block
IMPORTANT
In Communication CAS, do not use the YS block in RCAS or ROUT mode for the PFCS/
KFCS2/KFCS/LFCS2/LFCS/SFCS that communicate with YS instruments via the ALR121/
ACM12, since high-speed communications cannot be achieved. The YS block can be used
in CAS mode.
The figure below shows the mode changes of the SMST-111 and SMST-121 blocks.
Set terminal is connected Set terminal is not connected

Analog CAS for Communication CAS for Communication CAS
FCS FCS
CAS CAS Fail Fail RCAS
CAS DDC DDC
FCS FCS
Recover Recover C
C C
M M RCAS M
******
MAN MAN BUM MAN
MAN MAN MAN
FCS
SMST-111 FCS Fail
SMST-121 Recover
Analog CAS Communication CAS Circles

Upper row: YS Block Mode
CAS ROUT Lower row: YS Instrument Operation Mode
CAS DDC
Arrows
C: Mode change to CAS
C A: Mode change to AUT
C
M: Mode change to MAN
M ROUT M RCAS: Mode change to RCAS
ROUT: Mode change to ROUT
: Mode change on the DCS
MAN MAN : Mode change on the YS instrument
MAN MAN Other symbols indicate mode changes
from one or the other.
D013309E.EPS
Figure Mode Changes of the SMST Blocks
When Analog CAS is applied in the SMST-111 block, the mode will either be MAN or CAS.
When Communication CAS is connected to set terminal of SMST-111 block, the mode will
be MAN, CAS, otherwise the mode will be RCAS. (When the mode is CAS or RCAS, the
YS instrument will perform DDC operation.)
If Analog CAS is applied in the SMST-121 block, the mode will either be MAN or CAS.
While, if communication CAS is applied in the SMST-121 block, the mode will be either
MAN or ROUT.

● Mode Changes Specific to the SBSD and STLD Blocks
The SBSD and STLD instruments can only operate in AUT mode. AUT or CAS can be
selected for the display, depending on the YS instrument setting. From the YS block side,
the mode can be changed to out of service (O/S), and from O/S to AUT or CAS. The mode
may change from O/S to something other than specified in the YS instrument. This is
because the mode first changes to the one specified in the YS block before switching to the
mode specified in the YS instrument.
● Fixing to MAN Mode using the Mode Change Interlock Function

The mode can be fixed to MAN via the value of the connection destination of the YS block’s
INT terminal. When the mode change is interlocked, sending a command to the YS block to
change the mode to other than MAN will generate an error. Any attempt to change the
mode on the YS instrument side will be canceled since the mode is forcibly fixed to MAN
from the YS block.
● Mode Changes in the Event of a Communication Error

When an error occurs in communication with the YS instrument, the YS block enters IMAN
mode (combined mode with the previous modes).
If communication between the YS instrument and FCS is interrupted during the CAS
operation (Communication CAS), the YS instrument enters the backup mode automatically.
If the YS instrument is still in the backup mode after communication has resumed, the YS
block issues a command to the YS instrument to cancel the backup mode.

■ Data Tracking Function
The Data Tracking Function synchronizes process data and various control parameters
between the YS block and YS instruments.
This function collects control parameters and process data such as PV, SV, and MV from
the YS instruments and sets them as YS block data. If any data is set for the YS block from
the HIS, that data will also be set in the YS instruments via this function.
Each YS instrument model has different process data and control parameters. Accordingly,
each YS block has different process data and control parameters, depending on the corre-
sponding YS instrument. Some data only exists in the YS block but not in the YS instru-
ment.
Process data and parameters of the YS block can be handled in one of the following
manners:
• Only tracks YS instrument data but cannot be changed from the YS block side
Example: PV
• Exchanges data between the YS instrument and YS block
Examples: SV, MV, MH, ML, P, I, D
• Maintains value in the YS block, independent of the YS instrument
Examples: SUM, PH, PL
In certain types of YS instruments, parameters cannot be changed via communication.

Such data can only reference the YS instrument data.
Data relating to the Input Processing and Alarm Processing, such as SUM, PH, and PL,
which will be discussed later, are handled independently from the YS instrument.
Details on which data relates to which function will be explained with the functions of
respective function block models.
IMPORTANT
Be sure to set batch setpoints (BSET) to the SBSD and SLBC from the HIS prior to a batch
start. Changing a BSET after a batch start may result in an immediate batch end.

■ Input Processing
The YS block can perform the following Common Input Processing.
Digital Filter and Calibration functions are not available.
● Input Signal Conversion

▼ IOP Detection Value
There are two options for YS block input signal conversions: non-conversion and square
root conversion. Square root conversion can be selected when the connected YS instru-
ment uses the square-law scale. The YS blocks other than SLCD have only one option that
is non-conversion.
An YS block can have its own PV input open high limit and low limit for IOP+/IOP- detec-
tion. When a PV is greater than the value for IOP+ detection limit, the data will be in IOP+
status, vice versa, when the PV is smaller than the IOP- detection limit, the data will be in
IOP- status. IOP detection value can be specified on Function Block Detail Builder.
IOP Detection Value
• IOP+ Detection Set Value: Can be set between 100 % to 125 %.
• IOP- Detection Set Value: Can be set between -25 % to 0 %.
The default setting is -5.50.
● Totalizer
In the YS80 Block (SLCD, SLPC, SLMC, SMST-111, SMST-121, SMRT), the PVs are
totalized and the SUM is created.
The YS BCS Block (SBSD, SLBC, SLCC, STLD) displays the YS instrument SUM without
any changes. To display the correct totalized value, set the SH and SL according to the
decimal places on the YS instruments.
IMPORTANT
The decimal point positions of PV and SUM can be set independently of the YS instru-
ments. On the other hand, the YS BCS block sets the same decimal point positions for
SUM and PV. Therefore, when the decimal point positions are different between PV and
SUM on the YS instrument, the decimal point position of SUM displayed on the YS BCS
block differs from that of the YS instrument.
● PV Overshoot
PV is set to an SH value when the IOP+ is detected via the Alarm Processing function. PV
is also set to an SL value when IOP- is detected or when there is an error in communication
with the YS instruments.

■ Output Signal Processing
When the MV is set to 0 % or 100 % from the YS block, the YS instrument outputs Fully-
open/Tightly-shut values. When the Operation Low Limit Setpoint (ML) and the Manipu-
lated Variable High Limit Setpoint (MH) are set to 0 % and 100 %, respectively, from the YS
block, the ML and MH on the YS instrument will be -6.3 % and +106.3 %, respectively.
● Tight-Shut and Full-Open

An YS instrument can continuously output an MV ranging from -6.3 % and +106.3 %. In
MAN mode, an YS instrument can output an MV less than 0 % and greater than 100 %, as
long as the value is within the above range.
A YS block can output an MV ranging from 0 % to 100 %. When the YS block passes a 0 %
MV or a 100 % MV to YS instrument, the YS instrument will output a -6.3 % MV or a 106.3 %
MV as Tight-Shut or Full-Open signals of the YS instrument. When the YS block passes an
output signal to YS instrument between the value of 0 % and 100 %, the YS instrument will
output the same output without change. If a YS block’s ML is set as 0 % and MH is set as
100 %, the ML and MH in the corresponding YS instrument will be -6.3 % for ML and 106.3
% for MH respectively. This is caused by the Tight-Shut and Full-Open functionality of the
YS instrument. So that if the ML or the MH needs to be set as 0 % and 100 %, the setting
should be performed on YS instrument but not on YS block. A YS instrument MV can be
manipulated on YS block when the YS instrument is in MAN mode and the YS block is in
ROUT mode.
When a YS block is in ROUT mode, it always tracks the values in YS instrument unless the
YS block is being manipulated for passing an MV to the YS instrument. When the MV in the
YS instrument is less than 0 %, the YS block will take it as a 0 % value, while if the MV in
the YS instrument is greater than 100 %, the YS block will take it as a 100 % value.
● Manipulated Variable High Limit Setpoint (MH) / Manipulated Variable Low

Limit Setpoint (ML)
The Manipulated Variable High Limit Setpoint (MH) and the Manipulated Variable Low Limit
Setpoint (ML) are specified within the range between -6.3 % and +106.3 % when set from
the YS instrument, and between 0 % and 100 % when set from the YS block. However, if
the ML is set to 0 % from the YS block, the ML on the YS instrument will be -6.3 %. Simi-
larly, if the MH is set to 100 % from the YS block, the ML on the YS instrument will be
+106.3 %. If you wish to set the ML to 0 % or MH to 100 %, set these values on the YS
instrument.

■ Alarm Processing
▼ Leak Check, Pre-Batch Alarm, Batch End Alarm, Integral Deviation Alarm Level-One, Integral
Deviation Alarm Level-Two
The YS block handles alarms generated on the YS block and some alarms generated on
the YS instruments.
● Processing of Alarms Detected by YS Instrument

The YS instrument checks for OOP, IOP, HI, LO, DV+, and DV-. The YS block only acquires
the OOP and reflects it in the alarm status.
The SBSD and SLBC blocks not only acquire the OOP but also the END (Batch End), PRE
(Pre-batch), LEAK (Leak) alarms from the YS instrument and reflects them in the alarm
status. The SLCC block not only acquires the OOP but also DV+ (Level-1 Totalization
Deviation Alarm) and HDV (Level-2 Totalization Deviation Alarm) alarms from the YS
instrument and reflects them in the alarm status.
Enable or disable the END, PRE, LEAK alarm statuses on SBSD, SLBC blocks, enable or
disable the DV+, HDV alarm statuses on SLCC blocks can be set on Function Block Detail
Builder.
• Leak Check: Choose [Yes] or [No].
The default setting is [No].
• Pre-Batch Alarm: Choose [Yes] or [No].
• Batch End Alarm: Choose [Yes] or [No].
• Integral Deviation Alarm Level-One:Choose [Yes] or [No].
The default setting is [Yes].
• Integral Deviation Alarm Level-Two:Choose [Yes] or [No].
The default setting is [Yes].
● Processing of Alarms Detected by YS Block

All YS blocks detect IOP/IOP- independently of the YS instrument. When the PV exceeds
the IOP+ detection set value, it is considered an IOP. When the PV falls below the IOP-
detection set value, it is considered an IOP-. The detection of IOP or IOP- will not change
the block mode.
The YS80 blocks independently check HI, LO, DV+, and DV- as part of the Input Signal
Conversion functions. Alarm setpoints such as PH, PL, and DL are set independently from
the YS instrument parameters.
All YS blocks will generate both an OOP and IOP in the event of an error in communication
with the YS instrument. Thus, the OOP and IOP each contains two meanings, one being
the alarm detected by the YS instruments mentioned previously.
An invalid terminal definition will cause all YS blocks to generate a CNF. Causes of invalid
definitions include when the terminal is not connected to the applicable YS instrument
model and when it is not connected via an ACM12 or an LCS.
SEE ALSO
For details on YS block’s alarm checks, see chapter C5, “Alarm Processing - FCS.”

■ Others
The YS block has the following functions according to the standard PID blocks.
● Setpoint Push-Back
This function equalizes SV, CSV, and RSV according to the mode of the function block.
Table Block Modes and Equalization
Block Mode Equalization Operation
AUT, MAN, ROUT, CAS (analog CAS) SVACSV, RSV
CAS (Communication CAS) CSVASV, RSV
RCAS RSVASV, CSV
D013310E.EPS
● Setpoint Limiter
This function regulates data set to the RSV from the supervisory computer within the
setpoint high and low limits while in RCAS mode (SPC mode).
SEE ALSO
For more details on Setpoint Push-back and Setpoint Limiter, see D1.4, “Control Computation Processing
Common to Controller Blocks.”
■ Processing Timing
The only processing timing available for the YS blocks is a periodic startup. Moreover, only
the basic scan period can be selected as the scan period to execute the periodic startup. It
is not possible to specify the medium-speed scan period (*1) or the high-speed scan
period.
*1: ¡ £ The medium-speed scan period can only be used for the KFCS2, KFCS, LFCS2 or LFCS.

<Toc> <Ind> <D1.34 YS Controller Block (SLCD)> D1-455
D1.34 YS Controller Block (SLCD)

By connecting the SLCD block to the SLCD Indicating Controller, the SLCD Indicat-
ing Controller can be operated and monitored from the HIS.
■ YS Controller Block (SLCD)

▼ Connection
The connection of the SLCD block and the SLCD Indicating Controller allows the HIS to
operate and monitor the controller.
The figure below shows the function block diagram of the SLCD block.
SET INT
CAS RCAS
CSV RSV
AUT/MAN
SV
SLCD IN SLCD instrument image
PV MV
D013401E.EPS
Figure Function Block Diagram of the YS Controller Block (SLCD)
The table below shows the connection methods and the connection destinations of SLCD
block I/O terminals.
Table I/O Terminal Connection Methods and Connection Destinations of YS Controller Block
(SLCD)
Connection Method Connection Destination
I/O Terminal Data Data Terminal Process Soft Function
Reference Setting Connection I/O I/O Block
IN YS Instrument - - (*1) - -
SET Set Value Input - - - -
INT Interlock Switch Input -
D013402E.EPS
: Connection is possible
-: Connection is not possible
: Connection is possible only when integrating with a Switch Block (SW-33, SW-91) or Inter-Station Connection Block
(ADL)
*1: Connection is possible only when integrating with YS instruments

■ Function of YS Instrument Indicating Controller Block (SLCD)
The SLCD block performs input processing, control computation processing, output pro-
cessing, and alarm processing.
The only processing timing available for the SLCD block is a periodic startup. Moreover,
startup.
SEE ALSO
• For the common functions of the YS blocks, see D1.33, “Control Operations of YS Blocks.”
• For the types of input processing, output processing, and alarm processing possible for the SLCD block,
Control Block.”
■ Control Computation Processing of the YS Controller Block (SLCD)
● Setpoint Push-Back Function

This function equalizes the setpoints (SV), cascade setpoints (CSV), and remote setpoints
(RSV) in respect to the YS block mode.
SEE ALSO
For details on the setpoint pushback function, see D1.33.2, “Common Specification of YS Blocks” and
● Setpoint Limiter Function

setpoint high and low limits when the YS block is in RCAS mode (SPC mode).
SEE ALSO
For details on the setpoint limiter function, see D1.33.2, “Common Specification of YS Blocks” and D1.4,
“Control Computation Processing Common to Controller Blocks.”
● Mode Change Interlock Function

This function locks the YS block mode to MAN depending on the connection destination of
the YS block’s INT terminal.
SEE ALSO
For details on the mode change interlock function, see D1.33.2, “Common Specification of YS Blocks.”

■ Data Items of YS Controller Block (SLCD)
Table Data Items of YS Controller Block (SLCD) (1/2)
Item or Not
MODE Block mode - O/S (MAN)
ALRM Alarm status - - NR
AFLS Alarm flashing status - - 0
AF Alarm detection specification - - 0
AOFS Alarm masking specification - - 0
PV Process variable - PV engineering unit value SL
SV Setpoint Value in the same engineering unit as PV SL
CSV Cascade setpoint - Value in the same engineering unit as PV SL
RSV Remote setpoint - Value in the same engineering unit as PV SL
DV Control deviation value - Value in the same engineering unit as PV 0
MV Manipulated output value 0.0 to 100.0 % 0
RMV Remote manipulated output value - 0.0 to 100.0 % 0
PH High-limit alarm setpoint SL to SH SH
PL Low-limit alarm setpoint SL to SH SL
DL Deviation alarm setpoint (SH-SL) 0
MH Manipulated variable high setpoint (*1) 0.0 to 100.0 % 100
ML Manipulated variable low setpoint (*1) 0.0 to 100.0 % 0
SVH Set high setpoint SL to SH SH
SVL Set low setpoint SL to SH SL
P Proportional band (*1) 6.3 to 999.9 % 100
I Integral time (*1) 1 to 9999 sec 20
D Derivative time (*1) 0 to 9999 sec 0
OPHI Output high-limit index 0.0 to 100.0 % 100
OPLO Output low-limit index 0.0 to 100.0 % 0
UAID User application ID - 0
D013403E.EPS
: Entry is permitted from both the YS instrument and HIS

: Entry is permitted from the HIS only
: Data for the YS block can be entered from the HIS, the data for the YS instrument can be entered from the YS
instrument
-: Entry is not permitted
*1: MH, ML, P, I, D parameters can be entered from the HIS with SLCD Style E only.
SEE ALSO
For a list of valid block modes of the SLCD block, see D1.1.4, “Valid Block Modes for Each Regulatory
Control Block.”

Table Data Items of YS Controller Block (SLCD) (2/2)
Item or Not
SH PV scale high limit - Value in the same engineering unit as PV -
SL PV scale low limit - Value in the same engineering unit as PV -
MSH MV scale high limit - Fixed to 100 % 100 %
MSL MV scale low limit - Fixed to 0 % 0%
RAW Raw input data - 0.0 to 100.0 % -
D013404E.EPS

<Toc> <Ind> <D1.35 YS Programmable Controller Block (SLPC)> D1-459
D1.35 YS Programmable Controller Block (SLPC)

By connecting the SLPC block to the SLPC programmable controller, the SLPC
programmable controller can be operated and monitored from the HIS.
■ YS Programmable Controller Block (SLPC)

▼Connection
The connection of the SLPC block and the SLPC programmable controller allows the HIS
to operate and monitor the controller.
The figure below shows the function block diagram of the SLPC block.
SET INT
CAS RCAS
CSV RSV
AUT/MAN
SV
SLPC IN SLPC instrument image
PV MV
D013501E.EPS
Figure Function Block Diagram of the YS Programmable Controller Block (SLPC)
The table below shows the connection methods and the connection destinations of SLPC
Table I/O Terminal Connection Methods and Connection Destinations of YS Programmable
Controller Block (SLPC)

I/O Terminal Data Data Terminal Process Software Function
D013502E.EPS
(ADL)

■ Function of YS Instrument Programmable Indicating Controller Block
(SLPC)
The SLPC block performs input processing, control computation processing, output pro-
The only processing timing available for the SLPC block is a periodic startup. Moreover,
startup.
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the SLPC block,
Control Block.”
■ Control Computation Processing of the YS Programmable Controller

Block (SLPC)

SEE ALSO

SEE ALSO

SEE ALSO

■ Data Items of YS Programmable Controller Block (SLPC)
Table Data Items of YS Programmable Controller Block (SLPC) (1/2)
Item or Not
MH Manipulated variable high setpoint 0.0 to 100.0 % 100
ML Manipulated variable low setpoint 0.0 to 100.0 % 0
P Proportional band 6.3 to 999.9 % 100
I Integral time 1 to 9999 sec 20
D Derivative time 0 to 9999 sec 0
BS (*1) Computation parameter 1 -8.000 to 8.000 0.0
CS (*1) Computation parameter 2 -8.000 to 8.000 1.000
AUX1 (*1) Auxiliary input 1 - 0.0 to 100.0 % -
D013503E.EPS

instrument
*1: BS and CS correspond to P01 and P02 of the SLPC instrument. AUX1 to AUX3 correspond to analog output registers
Y4 to Y6 of the SLPC instrument.
SEE ALSO
For a list of valid block modes of the SLPC block, see D1.1.4, “Valid Block Modes for Each Regulatory
Control Block.”

Table Data Items of YS Programmable Controller Block (SLPC) (2/2)
Item or Not
D013504E.EPS


<Toc> <Ind> <D1.36 YS Programmable Controller Block with ...> D1-463
D1.36 YS Programmable Controller Block with

Pulse Width Output (SLMC)
By connecting the SLMC block to the SLMC Programmable Indicating Controller
with Pulse Width Output, the SLMC Programmable Indicating Controller with Pulse
Width Output can be operated and monitored from the HIS.
■ YS Programmable Controller Block with Pulse Width Output (SLMC)

▼ Connection
The connection of the SLMC block and the SLMC Programmable Controller Block with
Pulse Width Output allows the HIS to operate and monitor the controller.
The figure below shows the function block diagram of the SLMC block.
SET INT
CAS RCAS
CSV RSV
AUT/MAN
SV
SLMC IN SLMC instrument image
PV MV
D013601E.EPS
Figure Function Block Diagram of the YS Programmable Controller Block with Pulse Width
Output (SLMC)
The table below shows the connection methods and the connection destinations of SLMC
Table I/O Terminal Connection Methods and Connection Destinations of YS Programmable
Controller Block with Pulse Width Output (SLMC)

D013602E.EPS
(ADL)

■ Function of YS Instrument Programmable Indicating Controller Block
with PW Output (SLMC)
The SLMC block performs input processing, control computation processing, output pro-
The only processing timing available for the SLMC block is a periodic startup. Moreover,
startup.
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the SLMC block,
Control Block.”
■ Control Computation Processing of the YS Programmable Controller

Block with Pulse Width Output (SLMC)

SEE ALSO

SEE ALSO

SEE ALSO

■ Data Items of YS Programmable Controller Block with Pulse Width
Output (SLMC)
Table Data Items of YS Programmable Controller Block with Pulse Width Output (SLMC) (1/2)
Item or Not
P Proportional band 6.3 to 999.9 % 100
I Integral time 1 to 9999 sec 20
BS (*1) Computation parameter 1 -8.000 to 8.000 0.0
CS (*1) Computation parameter 2 -8.000 to 8.000 1.000
D013603E.EPS

instrument
*1: BS and CS correspond to P01 and P02 of the SLMC instrument. AUX1 to AUX3 correspond to analog output registers
Y4 to Y6 of the SLMC instrument.
SEE ALSO
For a list of valid block modes of the SLMC block, see D1.1.4, “Valid Block Modes for Each Regulatory
Control Block.”

Table Data Items of YS Programmable Controller Block with Pulse Width Output (SLMC) (2/2)
Item or Not
D013604E.EPS


<Toc> <Ind> <D1.37 YS Station Block with SV Output (SMST-111)> D1-467
D1.37 YS Station Block with SV Output (SMST-111)

By connecting the SMST-111 block to the SMST-111 Station Block with SV Output,
the SMST-111 Station Block with SV Output can be operated and monitored from the
HIS.
■ YS Station Block with SV Output (SMST-111)

▼ Connection
The connection of the SMST-111 block and the SMST-111 Station Block with SV Output
allows the HIS to operate and monitor the station.
The figure below shows the function block diagram of the SMST-111 block.
SET INT
CAS RCAS
CSV RSV
AUT/MAN
SV
SMST-111 IN SMST-111 instrument image
PV
D013701E.EPS
Figure Function Block Diagram of the YS Station Block with SV Output (SMST-111)
The table below shows the connection methods and the connection destinations of the
SMST-111 block I/O terminals.
Table I/O Terminal Connection Methods and Connection Destinations of YS Station Block with SV
Output (SMST-111)
D013702E.EPS
(ADL)

■ Function of YS Instrument Auto/Manual Station Block with Pushbutton
Setpoint Setting (SMST-111)
The SMST-111 block performs input processing, control computation processing, and
alarm processing.
The only processing timing available for the SMST-111 block is a periodic startup. More-
over, only the basic scan period can be selected as the scan period to execute the periodic
startup.
SEE ALSO
• For the types of input processing and alarm processing possible for the SMST-111 block, see D1.1.3,
Block.”
■ Control Computation Processing of the YS Station Block with SV Output

(SMST-111)

SEE ALSO

SEE ALSO

SEE ALSO

■ Data Items of YS Station Block with SV Output (SMST-111)
Table Data Items of YS Station Block with SV Output (SMST-111)
Item or Not
D013703E.EPS

instrument
SEE ALSO
For a list of valid block modes of the SMST-111 block, see D1.1.4, “Valid Block Modes for Each Regula-

<Toc> <Ind> <D1.38 YS Station Block with MV Output Lever (SMTS-121)> D1-470
D1.38 YS Station Block with MV Output Lever

(SMTS-121)
By connecting the SMST-121 block to the SMST-121 Station Block with MV Output
Lever, the SMST-121 Station Block with MV Output Lever can be operated and
monitored from the HIS.
■ YS Station Block with MV Output Lever (SMST-121)

▼ Connection
The connection of the SMST-121 block and the SMST-121 Station Block with MV Output
Lever (SMST-121) allows the HIS to operate and monitor the station.
The figure below shows the function block diagram of the SMST-121 block.
INT
SMST-121 IN SMST-121 instrument image
PV MV
D013801E.EPS
Figure Function Block Diagram of the YS Station Block with MV Output Lever (SMST-121)
The table below shows the connection methods and the connection destinations of the
SMST-121 block I/O terminals.
Table I/O Terminal Connection Methods and Connection Destinations of YS Station Block with
MV Output Lever (SMST-121)

D013802E.EPS
(ADL)

■ Function of YS Instrument Auto/Manual Station Block with Manipulated
Output Lever (SMST-121)
The SMST-121 block performs input processing, control computation processing, output
The only processing timing available for the SMST-121 block is a periodic startup. More-
over, only the basic scan period can be selected as the scan period to execute the periodic
startup.
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the SMST-121
■ Control Computation Processing of the YS Station Block with MV Output

Lever (SMST-121)

SEE ALSO

■ Data Items of YS Station Block with MV Output Lever (SMST-121)
Table Data Items of YS Station Block with MV Output Lever (SMST-121)
Item or Not
D013803E.EPS

instrument
SEE ALSO
For a list of valid block modes of the SMST-121 block, see D1.1.4, “Valid Block Modes for Each Regula-

<Toc> <Ind> <D1.39 YS Ratio Set Station Block (SMRT)> D1-473
D1.39 YS Ratio Set Station Block (SMRT)

By connecting the SMRT block to the Ratio Set Station (SMRT), the SMRT Ratio Set
Station can be operated and monitored from the HIS.
■ YS Ratio Set Station Block (SMRT)

▼ Connection
The connection of the SMRT block and the SMART Ratio Set Station allows the HIS to
operate and monitor the station.
The figure below shows the function block diagram of the SMRT block.
SET INT
CAS RCAS
CSV RSV
AUT/MAN
SV
SMRT IN SMRT instrument image
PV MV
D013901E.EPS
Figure Function Block Diagram of the YS Ratio Set Station Block (SMRT)
The table below shows the connection methods and the connection destinations of SMRT
Table I/O Terminal Connection Methods and Connection Destinations of YS Ratio Set Station
Block (SMRT)
D013902E.EPS
(ADL)

■ Function of YS Instrument Ratio Set Station Block (SMRT)
The SMRT block performs input processing, control computation processing, output pro-
The only processing timing available for the SMRT block is a periodic startup. Moreover,
startup.
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the SMRT block,
Control Block.”
■ Control Computation Processing of the YS Ratio Set Station Block

(SMRT)

SEE ALSO

SEE ALSO

SEE ALSO

■ Data Items of YS Ratio Set Station Block (SMRT)
Table Data Items of YS Ratio Set Station Block (SMRT) (1/2)
Item or Not
SV Ratio setpoint SSL to SSH SL
CSV Cascade ratio setpoint - SSL to SSH SL
RSV Remote ratio setpoint - SSL to SSH SL
DL Lamp constant (SSH-SSL) 100.0
SVH Ratio setting high setpoint SSL to SSH SSH
SVL Ratio setting low setpoint SSL to SSH SSL
EB External bias - 0.0 to 100.0 % 0
P1 Computation parameter 1 -800.0 to 800.0 0
CALC Computed value - 0.0 to 100.0 % 0.0 %
D013903E.EPS

instrument
SEE ALSO
For a list of valid block modes of the SMRT block, see D1.1.4, “Valid Block Modes for Each Regulatory
Control Block.”

Table Data Items of YS Ratio Set Station Block (SMRT) (2/2)
Item or Not
SSH SV scale high limit - Fixed to 8.000 8.000
SSL SV scale low limit - Fixed to 0.000 0.000
D013904E.EPS


<Toc> <Ind> <D1.40 YS Batch Set Station Block (SBSD)> D1-478
D1.40 YS Batch Set Station Block (SBSD)

By connecting the SBSD block to the Batch Set Station (SBSD), the SBSD Batch Set
■ YS Batch Set Station Block (SBSD)

▼ Connection
The connection of the SBSD block and the SBSD Batch Set Station allows the HIS to
operate and monitor the station.
The figure below shows the function block diagram of the SBSD block.
RCAS
RSV
AUT
SV
SBSD IN SBSD instrument image
PV MV
D014001E.EPS
Figure Function Block Diagram of the YS Batch Set Station Block (SBSD)
IMPORTANT
Be sure to set batch setpoints (BSET) to the YS Batch Set Station Block (SBSD) from the
HIS prior to a batch start. Changing a BSET after a batch start may result in an immediate
batch end.
The table below shows the connection methods and the connection destinations of SBSD
Table I/O Terminal Connection Methods and Connection Destinations of YS Batch Set Station
Block (SBSD)
D014002E.EPS
(ADL)

■ Function of YS Instrument Batch Set Station Block (SBSD)
The SBSD block performs input processing and alarm processing.
The only processing timing available for the SBSD block is a periodic startup. Moreover,
startup.
SEE ALSO
• For the types of input processing and alarm processing possible for the SBSD block, see D1.1.3, “In-
put Processing, Output Processing, and Alarm Processing Possible for Each Regulatory Control Block.”
■ Control Computation Processing of YS Batch Set Station Block (SBSD)

There are no items subject to the SBSD block’s control computation processing.

■ Data Items of YS Batch Set Station Block (SBSD)
Table Data Items of YS Batch Set Station Block (SBSD) (1/2)
Item or Not
MODE Block mode - O/S (AUT)
PV Instantaneous flow - PV engineering unit value SL
SV Command switch 0 to 8 0
RSV Remote command switch - 0 to 8 0
MV Demand output value 0.0 to 100.0 % 0
PH High-limit flow setpoint SL to SH SH
PL Initial flow setpoint SL to SH SL
VL Initial flow totalizer limit value SL to SH SL
BSET Batch setpoint Engineering unit value 0
Instrumental error compensation
CC1 -1.0000 to 1.0000 0.0000
coefficient (*3)
First-order compensation
CC2 -1.0000 to 1.0000 0.0000
coefficient (*1) (*3)
Second-order compensation
CC3 -1.0000 to 1.0000 0.0000
CC4 Density (*2) 0.5000 to 1.2000 1.0000
D014003E.EPS

instrument
*1: Valid only when the general secondary expression is selected for the correction computation. Setting a new value for
CC2 will change the CC4 data.
*2: Valid only when the ASTM method is selected for the correction computation. Setting a new value for CC4 will change
the CC2 data.
*3: The decimal point position for the coefficient can be specified on the YS instrument, while that is fixed to 4 decimal
places on the YS BCS block. Therefore, the decimal point position of the YS BCS block will not match that of the YS
instrument unless the coefficient on the YS instrument also has 4 decimal places. For example, if the YS BCS block
shows the coefficient to 3 decimal places, e.g. 1.000, the YS BCS block will display 0.1000.
SEE ALSO
For a list of valid block modes of the SBSD block, see D1.1.4, “Valid Block Modes for Each Regulatory
Control Block.”

Table Data Items of YS Batch Set Station Block (SBSD) (2/2)
Item or Not
D014004E.EPS

<Toc> <Ind> <D1.41 YS Batch Controller Block (SLBC)> D1-482
D1.41 YS Batch Controller Block (SLBC)

By connecting the SLBC block to the Batch Controller (SLBC), the SLBC Batch Set
■ YS Batch Controller Block (SLBC)

▼ Connection
The connection of the SLBC block and the SLBC Batch Controller allows the HIS to oper-
ate and monitor the controller.
The figure below shows the function block diagram of the SLBC block.
INT
RCAS
RSV
AUT/MAN
SV
SLBC IN SLBC instrument image
PV MV
D014101E.EPS
Figure Function Block Diagram of the YS Batch Controller Block (SLBC)
IMPORTANT
Be sure to set batch setpoints (BSET) to the SLBC from the HIS prior to a batch start.
Changing a BSET after a batch start may result in an immediate batch end.
The table below shows the connection methods and the connection destinations of SLBC
Table I/O Terminal Connection Methods and Connection Destinations of YS Batch Controller
Block (SLBC)
D014102E.EPS
(ADL)

■ Function of YS Instrument Batch Controller Block (SLBC)
The SLBC block performs input processing, control computation processing, output pro-
The only processing timing available for the SLBC block is a periodic startup. Moreover,
startup.
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the SLBC block,
Control Block.”
■ Control Computation Processing of the YS Batch Controller Block

(SLBC)

SEE ALSO

■ Data Items of YS Batch Controller Block (SLBC)
Table Data Items of YS Batch Controller Block (SLBC) (1/2)
Item or Not
SV Ratio setpoint 0 to 8 0
RSV Remote command switch - 0 to 8 0
PH High-limit flow setpoint SL to SH SH
PL Initial flow setpoint SL to SH SL
VL Initial flow totalizer limit value SL to SH SL
BSET Batch setpoint Engineering unit value 0
CC1 -1.0000 to 1.0000 0.0000
coefficient (*3)
CC2 -1.0000 to 1.0000 0.0000
CC3 -1.0000 to 1.0000 0.0000
CC4 Density (*2) 0.5000 to 1.2000 1.0000
D014103E.EPS

instrument
the CC2 data.
SEE ALSO
For a list of valid block modes of the SLBC block, see D1.1.4, “Valid Block Modes for Each Regulatory
Control Block.”

Table Data Items of YS Batch Controller Block (SLBC) (2/2)
Item or Not
D014104E.EPS

<Toc> <Ind> <D1.42 YS Blending Controller Block (SLCC)> D1-486
D1.42 YS Blending Controller Block (SLCC)

By connecting the SLCC block to the SLCC Blending Controller, the SLCC Blending
Controller can be operated and monitored from the HIS.
■ YS Blending Controller Block (SLCC)

▼ Connection
The connection of the SLCC Blending Controller allows the HIS to operate and monitor the controller.
The figure below shows the function block diagram of the SLCC block.
INT
RCAS
RSV
AUT
SV
SLCC IN SLCC instrument image
PV MV
D014201E.EPS
Figure Function Block Diagram of the YS Blending Controller Block (SLCC)
The table below shows the connection methods and the connection destinations of SLCC
Table I/O Terminal Connection Methods and Connection Destinations of YS Blending Controller
Block (SLCC)
D014202E.EPS
(ADL)

■ Function of YS Instrument Blending Controller Block (SLCC)
The SLCC block performs input processing, control computation processing, output pro-
The only processing timing available for the SLCC block is a periodic startup. Moreover,
startup.
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the SLCC block,
Control Block.”
■ Control Computation Processing of the YS Blending Controller Block

(SLCC)

SEE ALSO
■ SV Range Display Format of YS Blending Controller Block (SLCC)

▼ SV Range Display Format
This sets the SV Range Display Format so the decimal point of the ratio setting value (SV)
of the SLCC block will match that of the SLCC Blending Controller Block.
● Setting the SV Range Display Format

The SV Range Display Format is setting using the Function Block Detail Builder.
• SV Range Display Format: Select one from [0] to [4].
[0]: 10000
[1]: 1000.0
[2]: 100.00
[3]: 10.000
[4]: 1.0000
Default is [2].

■ Data Items of YS Blending Controller Block (SLCC)
Table Data Items of YS Blending Controller Block (SLCC) (1/2)
Item or Not
SV Ratio setpoint SSL to SSH 0
RSV Remote ratio setpoint - SSL to SSH 0
DV Totalized deviation value - Engineering unit value 0
CC1 -1.0000 to 1.0000 0.0000
coefficient (*3)
CC2 -1.0000 to 1.0000 0.0000
CC3 -1.0000 to 1.0000 0.0000
CC4 Density (*2) 0.5000 to 1.2000 1.0000
D014203E.EPS

instrument
the CC2 data.
SEE ALSO
For a list of valid block modes of the SLCC block, see D1.1.4, “Valid Block Modes for Each Regulatory
Control Block.”

Table Data Items of YS Blending Controller Block (SLCC) (2/2)
Item or Not
10000, 1000.0, 100.00, 10.000,
SSH SV scale high limit - 100.00 %
or 1.0000 % (*4)
SSL SV scale low limit - 0, 0.0, 0.00, 0.000, or 0.0000 % (*4) 0.000
D014204E.EPS

*4: The High and low limit of SV scale varies with the setting in [SV Range Display Format] on the builder. For an YS
instrument (SLCC), the SV range can be set between 0 to 299.99, but for a SLCC block, the setting will be limited to 0
to 99.99 % when the option 2 is selected for the setting of [SV Range Display Format]. When changing this setting, the
decimal point position will be changed accordingly.

<Toc> <Ind> <D1.43 YS Totalizer Block (STLD)> D1-490
D1.43 YS Totalizer Block (STLD)

By connecting the STLD block to the Totalizer (STLD), the STLD Totalizer can be
operated and monitored from the HIS.
■ YS Totalizer Block (STLD)

▼ Connection
The connection of the STLD block and the STLD Totalizer allows the HIS to operate and
monitor the totalizer.
The figure below shows the function block diagram of the STLD block.
STLD IN STLD instrument image
PV
D014301E.EPS
Figure Function Block Diagram of the YS Instrument Totalizer Block (STLD)
The table below shows the connection methods and the connection destinations of STLD
Table I/O Terminal Connection Methods and Connection Destinations of YS Totalizer Block
(STLD)
D014302E.EPS
(ADL)

■ Function of YS Instrument Totalizer Block (STLD)
The STLD block performs input processing and alarm processing.
The only processing timing available for the STLD block is a periodic startup. Moreover,
startup.
SEE ALSO
• For the types of input processing and alarm processing possible for the STLD block, see D1.1.3, “Input
Processing, Output Processing, and Alarm Processing Possible for Each Regulatory Control Block.”
■ Control Computation Processing of YS Totalizer Block (STLD)

There are no items subject to the STLD block’s control computation processing.

■ Data Items of YS Totalizer Block (STLD)
Table Data Items of YS Totalizer Block (STLD)
Item or Not
MODE Block mode - O/S (AUT)
CC1 -1.0000 to 1.0000 0.0000
coefficient (*3)
CC2 -1.0000 to 1.0000 0.0000
CC3 -1.0000 to 1.0000 0.0000
CC4 Density (*2) 0.5000 to 1.2000 1.0000
D014303E.EPS

instrument
the CC2 data.
SEE ALSO
For a list of valid block modes of the STLD block, see D1.1.4, “Valid Block Modes for Each Regulatory
Control Block.”

<Toc> <Ind> <D2. Arithmetic Calculation, Logic Operation> D2-1
D2. Arithmetic Calculation, Logic Operation

The arithmetic calculation and logic operation function blocks perform general-
purpose calculation processing, such as arithmetic calculation, analog calculation
and logic operation.
The arithmetic calculation and logic operation blocks include numeric calculation
blocks, analog calculation blocks, general-purpose calculation blocks, calculation
auxiliary blocks and logic operation blocks.
This chapter explains each model of calculation and logic operation function blocks.
■ Arithmetic Calculation and Logic Operation ¡ £

The general-purpose calculation processing such as arithmetic calculation, analog calcula-
tion and logic operation (*1) are performed to input signals to improve the regulatory control
and sequence control. The function block that executes arithmetic calculation is referred as
the calculation block.
The following figure shows the calculation blocks in basic control architecture.
*1: ¡ £ The logic operation blocks are only supported in CS 3000 system.
FCS
Basic control
Software I/O
Calculation blocks Annunciator message
Sequence control blocks

Sequence control message
Faceplate blocks
SFC blocks
Options
FCS I/O Interfaces
D020001E.EPS
Figure Calculation Blocks in Basic Control Architecture ¡ £

<Toc> <Ind> <D2.1 Common Functions of Calculation Blocks> D2-2
D2.1 Common Functions of Calculation Blocks

Calculation blocks provide calculation functions for analog signals and contact signals.
Calculation blocks convert the calculation results into the signals that can be used
by other function blocks.
■ Calculation Blocks
Calculation blocks receive analog signals (analog values) or contact signals (digital values)
as input values, and perform calculation according to the set parameters. The result of
calculation is outputted as the calculated output value (CPV).
Following diagram shows the architecture of calculation blocks.
P1 Pn
Input Output
IN RV CPV OUT
Q01 RV1 CPV1 J01

Calculation
processing
Qn RVn CPVn Jn
(CPV, CPV)
SUB
D020101E.EPS
IN: Input terminal (main input) OUT: Output terminal (main output)
Qn: Input terminal (subsidiary input) Jn: Output terminal (subsidiary output)
RV: Calculated input value CPV: Calculated output value
RVn: Calculated input value CPVn: Calculated output value
Pn: Set parameter SUB: Auxiliary output
Figure Architecture of Calculation Blocks
All calculation blocks are provided with the following three processing functions.
• Input processing:
Receive the signal from the input terminal and convert the signal into the calculation
input value (RV).
• Calculation processing:
Read the calculation input value (RV) and perform calculation processing then output
the result as calculated output value (CPV).
• Output processing:
Read the calculated output value (CPV) and output the calculation result as an output
signal to the connected destination of the output terminal.
Furthermore, to perform calculation with data of other function blocks via data setting or
data reference functions may bypass the input processing and output processing.
SEE ALSO
• For details on input processing common to calculation blocks, refer to C3, “Input Processing.”
• For details on output processing common to calculation blocks, refer to C4, “Output Processing.”

■ Logic Operation Blocks £
Logic operation blocks (*1) receive analog signals (analog values) or contact signals (digital
values) as input values, and perform calculation according to the set parameters. The
result of calculation is outputted as the calculated output value (CPV).
*1: £ Logic Operation blocks are only supported in CS 3000.
The following diagram shows the architecture of the Logic Operation block.
IN RV CPV OUT
Q01 RV1 CPV1 J01

Input Calculation Output
processing processing processing
Qn RVn CPVn Jn
Logic calculation blocks (*1)

D020102E.EPS
IN: Input terminal (main input) OUT: Output terminal (main output)
Qn: Input terminal (subsidiary input) Jn: Output terminal (subsidiary output)
RV: Calculated input value CPV: Calculated output value
RVn: Calculated input value CPVn: Calculated output value
Pn: Set parameter SUB: Auxiliary output
Figure Architecture of Logic Operation Blocks £
All calculation blocks are provided with the following three processing functions.
• Input processing:
Receive the signal from the input terminal and convert the signal into the calculation
input value (RV).
• Calculation processing:
Read the calculation input value (RV) and perform calculation processing then output
the result as calculated output value (CPV).
• Output processing:
Read the calculated output value (CPV) and output the calculation result as an output
signal to the connected destination of the output terminal.
Furthermore, to perform calculation with data of other function blocks via data setting or
data reference functions may bypass the input processing and output processing.
SEE ALSO
• For details on input processing common to calculation blocks, refer to C3, “Input Processing.”
• For details on output processing common to calculation blocks, refer to C4, “Output Processing.”

■ Calculation Output Operation
The calculation output operation is a function that converts the operation results of a
calculation block into actual calculated output values (CPV). There are two types of calcu-
lation output operations: velocity type and positional type.
● Positional type
Changes the calculated output value (CPVn) for the present calculation result to the actual
calculated output value (CPVn).
● Velocity type
Adds the difference (CPVn) between the calculated output value for the present calculation
result (CPVn) and that for the previous calculation result (CPVn-1) to the value read back
(CPVrb) from the output destination, and determines the actual calculated output value
(CPVn).
The arithmetic calculation block and analog calculation block are the only calculation
blocks that can use the velocity type.
● Setting the Calculation Output Operation

In the case of an arithmetic calculation block or an analog calculation block, the calculation
output operation is set using the Function Block Detail Builder. Calculation blocks that are
neither an arithmetic calculation block nor an analog calculation block only have the “Posi-
tional Output Action” calculation output operation, so no setting is necessary.
• Output Type:
Select from either “Velocity Output Action” or “Positional Output Action”
The default is “Positional Output Action.”

<Toc> <Ind> <D2.2 Data Handled by Calculation Blocks> D2-5
D2.2 Data Handled by Calculation Blocks

The calculation blocks can handle both the external data related to outside and the
internal data related only to inside calculation processing.
■ I/O Data Handled by Calculation Blocks ¡ £

The I/O data handled by calculation blocks consists of data values and data statuses.
● Data Value ¡ £
The calculation blocks can handle the following types of data: floating-point, double-preci-
sion floating-point, integer and character string.
When exchange data with other function blocks, if the data are in different type, the calcula-
tion block executes the following processing.
• When refer data from a function block
The calculation block converts the data into the type suitable itself.
• When set data to a function block
The calculation block converts the data suitable to the objective function block.
Because of the above processing, the engineer need not worry about the data type differ-
ence when generate and connect calculation blocks in the Function Block Detail Builder.
The I/O data types and set parameters applied to each type of calculation block are shown
below.
Table I/O data types and set parameters ¡ £
Block type Input data Output data Set parameter
Arithmetic calculation Double-precision floating-point Double-precision floating-point Not specified
Single-precision floating-point,
Analog calculation Single-precision floating-point Single-precision floating-point
integer
Logic operation (*1) integer (logical value) integer (logical value) Not specified
Double-precision floating-point,
Relational operation integer (logical value) Not specified
character string
Bitwise logic operation integer integer Not specified
General-purpose Double-precision floating-point, Double-precision floating-point, Double-precision floating-point,
calculation character string character string character string
Double-precision floating-point,
Calculation auxiliary Double-precision floating-point Double-precision floating-point
integer
Calculation auxiliary
Character string Character string Character string, integer
(for character strings only)
D020201E.EPS
Note: The analog calculation blocks handle data in engineering unit so that the internal data is floating type.
The general-purpose calculation blocks and calculation auxiliary blocks can pre-determine each individual data item
type in each function block.

● Data Status
The calculated output value (CPV) data status varies depending on whether the builder-
specified item “Output Value Tracking,” is enabled or disabled.
• When output value tracking is “No”
The calculated output value (CPV) is the result of calculation. It does not track to the
data of the output connected destination. Therefore, data statuses for the calculated
output value (CPV) are BAD (invalid), QST (questionable data value) and CAL (cali-
bration).
• When output value tracking is “Yes”
The calculated output value (CPV) is the result of calculation. It tracks to the output
connected destination’s data under the certain status. Therefore, the data status,
those often used for other function blocks but seldom for calculation blocks such as
CND (conditional) or NFP (non process origin), may occur to the calculated output
value (CPV).
The status of output value tracking can be indicated from the data status of the calculated
output value (CPV).
When CPV data status is BAD, QST, CAL, NEFV (IOP+, IOP-, OOP, NRDY), the CPV
Output value tracking is disabled.
When CPV data status is BAD, QST, CAL, NEFV, CND, NFP (IOP+, IOP-, OOP, NRDY),
the CPV Output value tracking is enabled.
Note: The data status in parentheses is only for CPV of the addition, multiplication, division, analog calculation or general-
purpose calculation blocks.
When a process I/O-related data status (IOP+, IOP-, OOP, NRDY) occurs to the calculated
input value (RV), the analog calculation blocks pass the data status to the calculated output
value (CPV), regardless of whether output tracking is enabled or disabled. Thus, the data
status occurred on the input side, such as IOP+ (input open high), is passed to the function
block connected to it.
The calculation block will set the status of calculated data as a bad data (BAD) when an
error occurs in the course of calculation.
Calculation error may be generated in the following cases.
• When the calculation result overflows.
• When the divisor of the calculation is zero, the calculation is zero divided.
• When calculate the square root of a negative number in the calculation.
SEE ALSO
For the details of data status, refer to C6.4, “Data Status.”

■ Calculation Precision
In a calculation block, all numeric values are calculated as double-precision floating-point
numbers. Numeric value data other than double-precision floating-point data are converted
to double-precision floating-point data inside the calculation block prior to the execution of
calculation processing. Therefore, calculation precision up to the double-precision floating
point is ensured.

<Toc> <Ind> <D2.3 Types of Calculation Blocks> D2-8
D2.3 Types of Calculation Blocks

According to the data type and calculation processing capability, the calculation
function blocks are classified into arithmetic calculation blocks, analog calculation
blocks, general-purpose calculation blocks and calculation auxiliary blocks.
■ Arithmetic Calculation Blocks

Table Arithmetic Calculation Blocks
Input Output
terminals terminals
ADD Addition Block
Arithmetic calculation MUL Multiplication Block 2 2

blocks DIV Division Block
AVE Averaging Block 8 2
D020301E.EPS
Note: The SUB terminal is counted as one of the output terminals.
■ Analog Calculation Blocks

Table Analog Calculation Blocks
Input Output
terminals terminals
SQRT Square Root Block
EXP Exponential Block
LAG First-Order Lag Block
INTEG Integration Block
LD Derivative Block
RAMP Ramp Block
LDLAG Lead/Lag Block 1 2
Analog calculation blocks DLAY Dead-Time Block

DLAY-C Dead-Time Compensation Block
AVE-M Moving-Average Block
AVE-C Cumulative-Average Block
FUNC-VAR Variable Line-Segment Function Block
TPCFL Temperature and Pressure Correction Block 3 2
ASTM1 ASTM Correction Block: Old JIS
2 2
ASTM2 ASTM Correction Block: New JIS
D020302E.EPS

■ Logic Operation Blocks £
Table Logic Operation Blocks £
Input Output
terminals terminals
2 1
OR Logical OR Block
NOT Logical NOT Block 1 1
SRS1-S Set-Dominant Flip-Flop Block with 1 Output
2 1
SRS1-R Reset-Dominant Flip-Flop Block with 1 Output
2 2
WOUT Wipeout Block 2 1
OND ON-Delay Timer Block
Logic Operation (*1)
OFFD OFF-Delay Timer Block
1 1
TON One-Shot Block (Rising-Edge Trigger)
TOFF One-Shot Block (Falling-Edge Trigger)
EQ Equal Operator Block 2 1
BNOT Bitwise NOT Block 1 1
D020303E.EPS

*1 : £ Logic Operation Blocks are only available for CS 3000.
■ General-Purpose Calculation Blocks

Table General-Purpose Calculation Blocks
Input Output
terminals terminals
CALCU General-Purpose Calculation Block
General-purpose
General-Purpose Calculation Block with 32 17
calculation blocks CALCU-C
String I/O
D020304E.EPS

■ Calculation Auxiliary Blocks
Table Calculation Auxiliary Blocks
Input Output
terminals terminals
Three-Pole Three-Position Selector
SW-33 9 (3) (*1) 3 (9) (*1)
Switch Block
One-Pole Nine-Position Selector
SW-91 9 (1) (*2) 1 (9) (*2)
Switch Block
DSW-16 Selector Switch Block for 16 Data
DSW-16C Selector Switch Block for 16 String Data 0 1
DSET Data Set Block
Calculation auxiliary DSET-PVI Data Set Block with Input Indicator 1 1
blocks
0 16
0 16
BDSET-2C Two-Batch String Data Set Block
16 0
ADL Inter-Station Data Link Block 0 0
D020306E.EPS

*1: 3 input terminals and 9 output terminals can be used.
*2: One input terminal and 9 output terminals can be used.

D2.3.1 Input Processing, Output Processing, and Alarm

Processing Possible for Each Calculation Block
A list of the types of input processing, output processing, and alarm processing that
can be performed for each calculation block is shown below.
■ Input Processing Possible in Each Calculation Block ¡ £

Table Input Processing Possible in Each Calculation Block (1/3)
Input signal
conversion
ADD BARPPqSb
MUL BARPPqSb
DIV BARPPqSb
AVE B
SQRT BARPPqSb (*1) (*1)
EXP BARPPqSb (*1) (*1)
LAG BARPPqSb (*1) (*1)
INTEG BARPPqSb (*1) (*1)
LD BARPPqSb (*1) (*1)
RAMP BARPPqSb
LDLAG BARPPqSb (*1) (*1)
DLAY BARPPqSb (*1) (*1)
DLAY-C BARPPqSb (*1) (*1)
AVE-M BARPPqSb
AVE-C BARPPqSb
FUNC-VAR BARPPqSb (*1) (*1)
TPCFL BARPPqSb
ASTM1 BARPPqSb
ASTM2 BARPPqSb
D020307E.EPS

Sb: Subsystem input
: Exists
Blank: Not exist
*1: The input processing other than the calibration function will not function when data setting is performed to the PV by
cascade connection.

Table Input Processing Possible in Each Calculation Block (2/3) £
Input signal
conversion
AND
OR
NOT
SRS1-S
SRS1-R
SRS2-S
SRS2-R
WOUT
OND
OFFD
TON
TOFF
GT
GE
EQ
BAND
BOR
BNOT
D020308E.EPS
: Exists
Blank: Not exist

Table Input Processing Possible in Each Calculation Block (3/3)
Input signal
conversion
CALCU BARPPqSb
CALCU-C BARPPqSb
SW-33
SW-91
DSW-16
DSW-16C
DSET
DSET-PVI BARPSb
BDSET-1L
BDSET-1C
BDSET-2L
BDSET-2C
BDA-L
BDA-C
ADL
D020309E.EPS

Pq: Exact totalization type pulse-train input conversion
Sb: Subsystem input
: Exists
Blank: Not exist

■ Output Processing Possible in Each Calculation Block ¡ £
Table Output Processing Possible in Each Calculation Block (1/2) ¡ £
Type PMV
ADD (*2) CCd BASb
MUL (*2) CCd BASb
DIV (*2) CCd BASb
AVE (*2) CCd BASb
AQRT (*1) (*2) CCd BASb
EXP (*1) (*2) CCd BASb
LAG (*1) (*2) CCd BASb
INTEG (*1) (*2) CCd BASb
LD (*1) (*2) CCd BASb
RAMP (*2) CCd BASb
LDLAG (*1) (*2) CCd BASb
DLAY (*1) (*2) CCd BASb
DLAY-C (*1) (*2) CCd BASb
AVE-M (*2) CCd BASb
AVE-C (*2) CCd BASb
FUNC-VAR (*1) (*2) CCd BASb
TPCFL (*2) CCd BASb
ASTM1 (*2) CCd BASb
ASTM2 (*2) CCd BASb
Logical
Calculation (*2) CCd BASb
Blocks (*3)
D020310E.EPS
P: PV
Pd: PV
M: MV
Md: MV
C: CPV
Cd: CPV
S: SV
Sd: SV
A: Analog output
S3: 3-position pulsive output
P3: 3-position status output
*1: Only tracking of the CLP status of the output destination is performed.
*2: Selectable by builder setting.
*3: ¡ £ The logical calculation blocks contain the following models. The logical calculation blocks are available only in
CS 3000 system. If the connection method of an output terminal is "status manipulation," the operation specification
defined for the output terminal is executed.
AND, OR, NOT, SRSI-S, SRS1-R, SRS2-S, SRS2-R, WOUT, OND, OFFD, TON, TOFF, GT, GE, EQ, BAND, BOR,
BNOT

Table Output Processing Possible in Each Calculation Block (2/2)
Type PMV
CALCU (*1) CCd BASb
CALCU-C (*1) CCd BASb
SW-33
SW-91
DSW-16 BASb
DSW-16C
DSET BASb
DSET-PVI CCdSSd BASb
DSET-1L
DSET-1C
DSET-2L
DSET-2C
BDA-L
BDA-C
D020311E.EPS
P: PV
Pd: PV
M: MV
Md: MV
C: CPV
Cd: CPV
S: SV
Sd: SV
A: Analog output
*1: Possible if explicitly input using computational expression

■ Alarm Processing Possible in Each Calculation Block ¡ £
Table Alarm Processing Possible in Each Calculation Block (1/3)
Common process alarms
Code R O O O H L I O V V E E H L N Other alarms
P P P + - L L I O F
- + -
ADD
MUL
DIV
AVE
SQRT
EXP
LAG
INTEG
LD
RAMP

LDLAG
DLAY
DLAY-C
AVE-M
AVE-C
FUNC
FUNC-VAR
TPCFL
ASTM1
ASTM2
D020312E.EPS
: Available

Table Alarm Processing Possible in Each Calculation Block (2/3) £
P P P + - L L I O F
- + -
AND
OR
NOT
SRS1-S
SRS1-R
SRS2-S
SRS2-R
WOUT
OND

OFFD
TON
TOFF
GT
GE
EQ
BAND
BOR
BNOT
D020313E.EPS
: Available

Table Alarm Processing Possible in Each Calculation Block (3/3)
P P P + - L L I O F
- + -
CALCU
CERR
CALCU-C
SW-33
SW-91
DSW-16
DSW-16C
DSET
DSET-PV1
BDSET-1L
BDSET-1C
BDSET-2L
BDSET-2C
BDA-L
BDA-C
D020314E.EPS
: Available

D2.3.2 Valid Block Modes for Each Calculation Block

A list of valid block modes for each calculation block is shown below.
■ Valid Block Modes for Each Calculation Block ¡ £

Table Valid Basic Block Modes for Calculation Blocks (1/3)

O I T M A C P R R
Type Name of function block / M R A U A R C O
S A K N T S D A U
N S T
ADD Addition block

MUL Multiplication block
DIV Division block
AVE Average block
SQRT Square root block
EXP Exponential block
LAG First-order lag block
INTEG Integration block
LD Derivative block
RAMP Ramp block - - - - - - -
LDLAG Lead/lag block
DLAY Dead time block
DLAY-C Dead time compensation block
AVE-M Moving average block
AVE-C Cumulative average block
FUNC-VAR Variable line-segment function block
TPCFL Temperature and pressure correction block
ASTM1 ASTM correction block:Old JIS
ASTM2 ASTM correction block:New JIS
D020315E.EPS
: Valid
-: Invalid

Table Valid Basic Block Modes for Calculation Blocks (2/3) ¡ £

O I T M A C P R R
S A K N T S D A U
N S T
AND (*1) Logic product block

OR (*1) Logic sum block
NOT (*1) Negation block
SRS1-S (*1) Set-dominant flip-flop block with 1 output
SRS1-R (*1) Reset-dominant flip-flop block with 1 output
SRS2-S (*1) Set-dominant flip-flop block with 2 outputs
SRS2-R (*1) Reset-dominant flip-flop block with 2 outputs
WOUT (*1) Wipeout block
OND (*1) On-delay timer block
OFFD (*1) Off-delay timer block
- - - - - - -
TON (*1) Rise trigger block
TOFF (*1) Fall trigger block
GT (*1) Greater than operator block
GE (*1) Greater than or equal to operator block
EQ (*1) Equal operator block
BAND (*1) Bitwise AND block
BOR (*1) Bitwise OR block
BNOT (*1) Bitwise NOT block
CALCU General-purpose calculation block
CALCU-C General-purpose calculation block with string I/O
D020316E.EPS
: Valid
-: Invalid
*1: ¡ £ Logic Operation blocks are only available for CS 3000.

Table Valid Basic Block Modes for Calculation Blocks (3/3)
O I T M A C P R R
S A K N T S D A U
N S T
SW-33 Three-pole three-position selector switch block

- - - - - - - - -
SW-91 One-pole nine-position selector switch block
DSW-16 Selector switch block for 16 data
DSW-16C Selector switch block for 16 string data
DSET Data set block
DSET-PVI Data set block with input indicator
BDSET-1L One-batch data set block
- - - - - - -
BDSET-1C One-batch string data set block
BDSET-2L Two-batch data set block
BDSET-2C Two-batch string data set block
BDA-L Batch data acquisition block
BDA-C Batch string data acquisition block
D020317E.EPS
: Valid
-: Invalid

<Toc> <Ind> <D2.4 Addition Block (ADD)> D2-22
D2.4 Addition Block (ADD)

The Addition Block (ADD) is used when performing addition processing or subtrac-
tion processing.
■ Addition Block (ADD)

▼ Connection
The Addition Block (ADD) is a function block that executes addition or subtraction of input
data.
Here is the diagram of the Addition Block (ADD).
Input
IN RV
processing
Gain
(GAIN),
Addition CPV OUT
bias
(BIAS)
RV1 gain
(GN1),
Q01 RV1
RV1 bias
(BS1)
(CPV, CPV) SUB

D020401E.EPS
Figure Function Block Diagram of Addition Block (ADD)
The following table shows the connection types and connection destinations of the I/O
terminals of the Addition Block (ADD).
Table Connection Types and Connection Destinations of the I/O Terminals of Addition Block
(ADD)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
IN Main input
Q01 Sub input
Calculation
OUT
output
Auxiliary
SUB
output
D020402E.EPS
: 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).

■ Function of Addition Block (ADD) ¡ £
The ADD block performs input processing, calculation processing, output processing, and
alarm processing.
The processing timings available for the ADD block 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.
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the ADD block,
see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Cal-
culation Block.”
● Input Processing of Addition Block (ADD) When a Calculation Input Value

Error is Detected
The ADD block performs special input processing when an abnormal calculation input
value is detected.
SEE ALSO
For the input processing when an abnormal calculation input value is detected, see chapter C3.6.2, “Input
Processing of the Calculation Block in Unsteady State.”
● Calculation Processing of Addition Block (ADD)

The ADD block performs addition and subtraction using its calculation algorithm and setup
parameters.

■ Calculation Algorithm
The Addition Block (ADD) executes the following calculation processing for addition or
subtraction of the input data.
CPV=GAIN • (RV+ ( (GN1 • RV1) +BS1) +BIAS
To perform addition processing of input data, set a positive numeric value for the RV1 gain.
To perform subtraction processing of input data, set a negative numeric value for the RV1
gain.
■ Set Parameters
The set parameters of the Addition Block (ADD) are shown as follows.
• Gain (GAIN):
A numeric value of 7 digits or less including the sign and decimal point.
The default is 1.00
• Bias (BIAS):
An engineering unit data value of 7 digits or less including the sign and decimal point.
The default is 0.00
• RV1 gain (GN1):
The default is 1.00
• RV1 bias (BS1):
An engineering unit data of 7 digits or less including the sign and decimal point.
The default is 0.00

■ Data Items – ADD
Table Data Items of Addition Block (ADD)
Item or Not
RV Calculated input value ----- 0
RV1 Calculated input value ----- 0
RAW1 Raw input data Value in the unit at the connection destination -----
CPV Calculated output value (*1) CPV engineering unit value SL
GAIN Gain 7 - digit real number including sign and decimal point 1.00
BIAS Bias 7 - digit real number including sign and decimal point 0.00
GN1 RV1 gain 7 - digit real number including sign and decimal point 1.00
BS1 RV1 bias 7 - digit real number including sign and decimal point 0.00
SH CPV scale high limit Value in the same engineering unit as CPV -----
SL CPV scale low limit Value in the same engineering unit as CPV -----
D020403E.EPS

SEE ALSO
For the information about valid block mode for ADD block, see chapter D2.3.2, “Valid Block Modes for
Each Calculation Blocck.”

<Toc> <Ind> <D2.5 Multiplication Block (MUL)> D2-26
D2.5 Multiplication Block (MUL)

The Multiplication Block (MUL) is used when performing multiplication processing.
■ Multiplication Block (MUL)

▼ Connection
The Multiplication Block (MUL) is a function block that performs multiplication of input data.
Here is a function block diagram of the Multiplication Block (MUL).
Input
IN RV
processing
Gain
(GAIN),
Multiplication CPV OUT
bias
(BIAS)
RV1 gain
(GN1),
Q01 RV1
RV1 bias
(BS1)
(CPV, CPV) SUB

D020501E.EPS
Figure Function Block Diagram of Multiplication Block (MUL)
terminals of the Multiplication Block (MUL).
Table Connection Types and Connection Destinations of the I/O Terminals of Multiplication Block
(MUL)
Data setting
IN Main input
Q01 Sub input
Calculation
OUT
output
Auxiliary
SUB
output
D020502E.EPS

■ Function of Multiplication Block (MUL) ¡ £
The MUL block performs input processing, calculation processing, output processing, and
alarm processing.
The processing timings available for the MUL block are a periodic startup and a one-shot
period.
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the MUL block,
culation Block.”
● Input Processing of Multiplication Block (MUL) When a Calculation Input

Value Error is Detected
The MUL block performs special input processing when an abnormal calculation input
value is detected.
SEE ALSO
● Calculation Processing of Multiplication Block (MUL)

The MUL block performs multiplication using its calculation algorithm and setup param-
eters.

The Multiplication Block (MUL) executes the following calculation processing to perform
multiplication of input data.
CPV=GAIN • (RV • ( (GN1 • RV1) + BS1) ) +BIAS
■ Set Parameters
The set parameters of the Multiplication Block (MUL) are shown as follows.
• Gain (GAIN):
The default is 1.00
• Bias (BIAS):
The default is 0.00
• RV1 gain (GN1):
The default is 1.00
• RV1 bias (BS1):
The default is 0.00

■ Data Items – MUL
Table Data Items of Multiplication Block (MUL)
Item or Not
D020503E.EPS

SEE ALSO
For a list of valid block modes for MUL block, see chapter D2.3.2, “Valid Block Modes for Each Calcula-
tion Block.”

<Toc> <Ind> <D2.6 Division Block (DIV)> D2-30
D2.6 Division Block (DIV)

The Division Block (DIV) is used when performing division processing.
■ Division Block (DIV)

▼ Connection
The Division Block (DIV) is a function block that performs division of input data.
Here is a function block diagram of the Division Block (DIV).
Input
IN RV
processing
Gain
(GAIN),
Division CPV OUT
bias
(BIAS)
RV1 gain
(GN1),
Q01 RV1
RV1 bias
(BS1)
(CPV, CPV) SUB

D020601E.EPS
Figure Function Block Diagram of Division Block (DIV)
terminals of the Division Block (DIV).
Table Connection Types and Connection Destinations of the I/O Terminals of Division Block (DIV)
Data setting
IN Main input
Q01 Sub input
Calculation
OUT
output
Auxiliary
SUB
output
D020602E.EPS

■ Function of Division Block (DIV) ¡ £
The DIV block performs input processing, calculation processing, output processing, and
alarm processing.
The processing timings available for the DIV block are a periodic startup and a one-shot
period.
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the DIV block,
culation Block.”
● Input Processing of Division Block (DIV) When a Calculation Input Value

Error is Detected
The DIV block performs special input processing when an abnormal calculation input value
is detected.
SEE ALSO
● Calculation Processing of Division Block (DIV)

The DIV block performs division using its calculation algorithm and setup parameters.

The Division Block (DIV) executes the following calculation processing for performing
division of input data.
CPV=GAIN • (RV/ ( (GN1 • RV1) +BS1) ) +BIAS
■ Set Parameters
The set parameters of the Division Block (DIV) are shown as follows.
• Gain (GAIN):
The default is 1.00
• Bias (BIAS):
The default is 0.00
• RV1 gain (GN1):
The default is 1.00
• RV1 bias (BS1):
The default is 0.00

■ Data Items – DIV
Table Data Items of Division Block (DIV)
Item or Not
D020603E.EPS

SEE ALSO
For a list of valid block modes for DIV block, see chapter D2.3.2, “Valid Block Modes for Each Calculation
Block.”

<Toc> <Ind> <D2.7 Averaging Block (AVE)> D2-34
D2.7 Averaging Block (AVE)

The Averaging Block (AVE) is used when calculate the average value of input data.
■ Averaging Block (AVE)

▼ Connection
The Averaging Block (AVE) is a function block that obtains the average value of input data.
Here is a function block diagram of the Averaging Block (AVE).
Q01 RV1
Q02 RV2
Q03 RV3
Q04 RV4
Averaging
CPV OUT
processing
Q05 RV5
Q06 RV6
Q07 RV7
Q08 RV8
(CPV, CPV)
SUB
D020701E.EPS
Figure Function Block Diagram of Averaging Block (AVE)

terminals of the Averaging Block (AVE).
Table Connection Types and Connection Destinations of the I/O Terminals of Averaging Block
(AVE)
Data setting
First
Q01 calculation
input
Second
Q02 calculation
input
Third
Q03 calculation
input
Fourth
Q04 calculation
input
Fifth
Q05 calculation
input
Sixth
Q06 calculation
input
Seventh
Q07 calculation
input
Eighth
Q08 calculation
input
Calculation
OUT
output
Auxiliary
SUB
output
D020702E.EPS

■ Function of Average Block (AVE) ¡ £
The AVE block performs input processing, calculation processing, output processing, and
alarm processing.
The processing timings available for the AVE block are a periodic startup and a one-shot
period.
*1: ¡ £ The medium-speed scan period can only be used for the KFCS2, KFCS, LFCS2 and LFCS
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the AVE block,
culation Block.”
● Input Processing of Average Block (AVE) When a Calculation Input Value

Error is Detected
The AVE block performs special input processing when an abnormal calculation input value
is detected.
● Calculation Processing of Average Block (AVE)

The AVE block returns the average value of input data using its calculation algorithm and
setup parameters.

■ Input Processing at Calculated Input Value Error Detection
In the Average block (AVE), the detection of calculated input value error is executed for
every input terminal. For each input terminal, when the data status of the connection
destination is invalid (BAD), that of corresponding calculated input value (RVn) becomes
invalid (BAD), and the previous calculated input value is held.
The data status of the calculated output value (CPV) becomes invalid (BAD) or question-
able (QST) at calculated input value error detection.
The settings of the detection conditions for calculated input value error detection in the
Average block (AVE) and the data status of the calculated output value (CPV) at calculated
input value error detection are executed with “Calculated input value error detected” on the
tions, which is generated with the calculated input value (RVn) in connection with the above
settings, to the calculated output value (CPV) is specified.
The table below lists the ranges of the calculated input value error detection. The default
value is “1.”
Table Processing at Calculated Input Value Error Detection in the Average Block (AVE)
Calculated input value Error detection conditions Data status
error detection (Data status of the CPV data status transmission
specification calculated input value) origin input value
0 - NR (*1)
RV1 to RVn (n is an average number)
NR (*1)
are all NR (*1). No transmission
At least one of RV1 to RVn
1 QST
(n is an average number) is BAD.
BAD RV1 to RVn (*2)
are all BAD.
NR (*1) No transmission
are all NR (*1).
2
At least one of RV1 to RVn
BAD RV1 to RVn (*2)
(n is an average number) is BAD.
D020703E.EPS
*1: NR in the table indicates the state in which the data status is neither BAD nor QST.
*2: The priority of input values is in the order of RV1 to RVn. IOP and IOP- precede in the transfer status. IOP is trans-
ferred when NRDY is generated in the input values of higher priority and IOP is generated in the input values of lower
priority.

▼ Number of Averaged, Sampling Candidate Specification
The Averaging Block (AVE) performs the following calculation processing for obtaining the
average value of input data.
RV1+RV2+RV3+...+RVN
CPV=GAIN •
N
D020704E.EPS
“Number of averaged” and “sampling candidate specification” is set using the Function
• Number of Averaged (N):
Any integer between 1 and 8.
The default is 1.
Set the number of data to be averaged.
• Sampling Candidate Specification:
Select from “Regardless of data status,” “other than BAD” or “other than BAD or QST.”
If the data status of the calculated input value (RVn) changes to the status indicating the
data is not good, this data can be excluded from the averaging calculation. The conditions
to include or exclude the data for the averaging calculation can be defined on the builder
under the following conditions.
• Regardless of data status
All input data (RVn) regardless of data status
• Other than BAD
All input data (RVn) except for BAD data
• Other than BAD and QST
All input data (RVn) except for BAD and QST data
The calculation block’s behavior is restricted by the input error detection function. When the
calculation input error detection is specified to “2,” only “Regardless of data status” is valid
as averaging calculation condition. Or else, any input detected BAD makes the calculated
output value (CPV) become BAD (invalid) and the averaging calculation stops.
While, when the condition is specified as “other than BAD” or “other than BAD or QST,” the
above described phenomena occur, i.e. the BAD input data stops the averaging calcula-
tion.

■ Set Parameter
The parameters of the Averaging Block(AVE) are shown as follows.
• Gain (GAIN):
The default is 1.00
■ Data Items – AVE

Table Data Items of Averaging Block (AVE)
Entry Permitted
or Not
RV1 to RV8 Calculated input value 1to 8 ----- 0
RAW1 to RAW8 Raw input data 1to 8 Value in the unit at the connection destination -----
7 - digit real number including sign and

GAIN Gain 1.00
decimal point
D020705E.EPS

SEE ALSO
For a list of valid block modes for AVE block, see chapter D2.3.2, “Valid Block Modes for Each Calculation
Block.”

<Toc> <Ind> <D2.8 Square Root Block (SQRT)> D2-40
D2.8 Square Root Block (SQRT)

The Square Root Block (SQRT) is used when obtaining the square root of input data.
■ Square Root Block (SQRT)

▼ Connection
The Square Root Block (SQRT) is a function block that obtains the square root of input
data.
Here is a function block diagram of the Square Root Block (SQRT).
Input
IN RV GAIN • RV CPV OUT
processing
(CPV, CPV)
SUB
D020801E.EPS
Figure Function Block Diagram of Square Root Block (SQRT)
terminals of the Square Root Block (SQRT).
Table Connection Types and Connection Destinations of the I/O Terminals of Square Root Block
(SQRT)
Data setting
Calculation
IN
input
Calculation
OUT
output
Auxiliary
SUB
output
D020802E.EPS

■ Function of Square Root Block (SQRT) ¡ £
The SQRT block performs input processing, calculation processing, output processing, and
alarm processing.
The only processing timing available for the SQRT block is a periodic startup. Selections
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the SQRT block,
culation Block.”
● Calculation Processing of Square Root Block (SQRT)

The SQRT block calculates the square root of input data using its calculation algorithm and
setup parameters.
● Output Processing Specific to Square Root Block (SQRT)

In the output processing of the SQRT block, it is possible to perform “CPV pushback.”
The Square Root Block (SQRT) executes the following calculation processing to obtain the
square root of input data.
CPV=GAIN • RV
D020803E.EPS
■ Set Parameter
The parameters of the Square Root Block (SQRT) are shown as follows.
• Gain (GAIN):
The default is 1.00

■ CPV Pushback
The CPV pushback is a function used to prevent a sudden change in an output value to the
process control output when the status of a cascade connection is changed from open to
close.
If the SQRT block is connected by means of cascade connection and the cascade connec-
tion is opened, the calculation input value (RV) is calculated back based on a calculation
output value (CPV) obtained from a downstream function block via tracking, thereby mak-
ing the upstream function block track the value.
The CPV pushback operates only when the output value tracking is set to “enabled.”
The following calculation formula is used in the CPV pushback of the SQRT block.
CPV 2
RV=
GAIN
D020804E.EPS
If GAIN is 0, the CPV pushback calculation is bypassed and the calculation input value
(RV) retains the previous value.
SEE ALSO
For details on the CPV pushback, see chapter C4.11, “CPV Pushback.”

■ Data Items – SQRT
Table Data Items of Square Root Block (SQRT)
Item or Not
D020805E.EPS

SEE ALSO
For a list of valid block modes for SQRT block, see chapter D2.3.2, “Valid Block Modes for Each Calcula-
tion Block.”

<Toc> <Ind> <D2.9 Exponential Block (EXP)> D2-44
D2.9 Exponential Block (EXP)

The Exponential Block (EXP) is used when obtaining the result of exponential value
of the base of natural logarithms with the input data.
■ Exponential Block (EXP)

▼ Connection
The Exponential Block (EXP) is a function block that obtains the result of exponential value
of the base of natural logarithms with the input data.
Here is a function block diagram of the Exponential Block (EXP).
Input
IN RV GAIN • eRV CPV OUT
processing
(CPV, CPV)
SUB
D020901E.EPS
Figure Function Block Diagram of Exponential Block (EXP)
terminals of the Exponential Block (EXP).
Table Connection Types and Connection Destinations of the I/O Terminals of Exponential Block
(EXP)
I/O terminal
Data Condition Status Terminal Process Software Function
Data setting
Calculation
IN
input
Calculation
OUT
output
Auxiliary
SUB
output
D020902E.EPS

■ Function of Exponential Block (EXP)
The EXP block performs input processing, calculation processing, output processing, and
alarm processing.
The only processing timing available for the EXP block is a periodic startup. Selections
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the EXP block,
culation Block.”
● Calculation Processing of Exponential Block (EXP)

The EXP block calculates the value where the base of the natural logarithm is raised to a
power given by the input data using its calculation algorithm and setup parameters.
● Output Processing Specific to Exponential Block (EXP)

In the output processing of the EXP block, it is possible to perform "CPV pushback."
The Exponential Block (EXP) executes the following calculation processing to the input
data.
CPV=GAIN • eRV
e: Base of a natural logarithm
■ Set Parameter
The parameters of the Exponential Block (EXP) are shown as follows.
• Gain (GAIN):

■ CPV Pushback
close.
If the EXP block is connected by means of cascade connection and the cascade connec-
The CPV pushback operates only when the output value tracking is set to [Yes].
The following calculation formula is used in the CPV pushback of the EXP block.
CPV
RV=ln
GAIN
D020903E.EPS
If (CPV/GAIN) 0, the calculation input value (RV) retains the previous value.
SEE ALSO
■ Data Items – EXP

Table Data Items of Exponential Block (EXP)
Item or Not
D020904E.EPS

SEE ALSO
For a list of valid block modes for EXP block, see chapter D2.3.2, “Valid Block Modes for Each Calculation
Block.”

<Toc> <Ind> <D2.10 First-Order Lag Block (LAG)> D2-47
D2.10 First-Order Lag Block (LAG)

The First-Order Lag Block (LAG) is used when performing filtering processing to the
input signals or simulating process characteristics.
■ First-Order Lag Block (LAG)

▼ Connection
The First-Order Lag Block (LAG) is a function block that outputs the first-order lag of input
signals.
The First-Order Lag Block (LAG) enables filtering processing of input signals as well as
simulation of process characteristics.
Here is a function block diagram of the First-Order Lag Block (LAG).
Input GAIN
IN RV CPV OUT
processing 1+Tis
(CPV, CPV)
SUB
D021001E.EPS
Figure Function Block Diagram of First-Order Lag Block (LAG)
terminals of the First-Order Lag Block (LAG).
Table Connection Types and Connection Destinations of the I/O Terminals of First-Order Lag
Block (LAG)
Data setting
Calculation
IN
input
Calculation
OUT
output
Auxiliary
SUB
output
D021002E.EPS

■ Function of First-Order Lag Block (LAG) ¡ £
The LAG block performs input processing, calculation processing, output processing, and
alarm processing.
The only processing timing available for the LAG block is a periodic startup. Selections
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the LAG block,
culation Block.”
● Calculation Processing of First-Order Lag Block (LAG)

The LAG block performs a first-order lag calculation using its calculation algorithm and
setup parameters.
● Output Processing Specific to First-Order Lag Block (LAG)

In the output processing of the LAG block, it is possible to perform "CPV pushback."

The First-Order Lag Block (LAG) executes the following calculation processing to the input
data.
GAIN
CPV= • RV
1+Tis
D021003E.EPS
Ti: First-order lag time (Ti = I - Scan period)

I: First-order lag time setpoint
s: Laplace transform operator
When the block mode is switched from O/S (out of service) to AUT (automatic), or when the
data status of the calculated output value (CPV) has returned to normal from CAL (calibration)
or BAD (invalid), first-order lag calculation is initialized with the calculated input value (RV).
■ Set Parameters
The parameters of the First-Order Lag Block (LAG) are shown as follows.
• Gain (GAIN):
• First-order lag time setpoint (I):
A numeric value between 0.1 and 1000.0. Unit: sec.
The default is 1.
If a time shorter than the scan period is set as the first-order lag time (I), calculation pro-
cessing is performed assuming that the first-order lag time setpoint (I) is the same as the
scan period.
■ Action Example
The following figure shows an example of step response action of the First-Order Lag Block
(LAG).
Input signal
Output signal (When GAIN = 1.000)
Time t
Ti

D021004E.EPS
Figure Example of the Step Response Action of First-Order Lag Block (LAG)

■ CPV Pushback
close.
If the LAG block is connected by means of cascade connection and the cascade connec-
The following calculation formula is used in the CPV pushback of the LAG block.
CPV
RV=
GAIN
D021005E.EPS
SEE ALSO
For details on the CPV pushback, see chapter C4.11, "CPV Pushback."

■ Data Items – LAG
Table Data Items of First-Order Lag Block (LAG)
Item or Not
I First - order lag time 0.1 to 10,000.0 seconds 1
D021006E.EPS

SEE ALSO
For a list of valid block modes for LAG block, see chapter D2.3.2, “Valid Block Modes for Each Calculation
Block.”

<Toc> <Ind> <D2.11 Integration Block (INTEG)> D2-52
D2.11 Integration Block (INTEG)

The Integration Block (INTEG) is used when obtaining the integral value of input
data.
■ Integration Block (INTEG)

▼ Connection
The Integration Block (INTEG) is a function block that integrates input data.
Here is a function block diagram of the Integration Block (INTEG).
Input GAIN
IN RV CPV OUT
processing Tis
(CPV, CPV)
SUB
D021101E.EPS
Figure Function Block Diagram of Integration Block (INTEG)
terminals of the Integration Block (INTEG).
Table Connection Types and Connection Destinations of the I/O Terminals of Integration Block
(INTEG)
Data setting
Calculation
IN
input
Calculation
OUT
output
Auxiliary
SUB
output
D021102E.EPS

■ Function of Integration Block (INTEG) ¡ £
The INTEG block performs input processing, calculation processing, output processing,
and alarm processing.
The only processing timing available for the INTEG block is a periodic startup. Selections
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the INTEG block,
culation Block.”
● Calculation Processing of Integration Block (INTEG)

The INTEG block calculates the integrated value of input data using its calculation algo-
rithm and setup parameters.
● Output Processing Specific to Integration Block (INTEG)

In the output processing of the INTEG block, it is possible to perform “CPV pushback.”

The Integration Block (INTEG) executes the following calculation processing for integrating
input data.
GAIN
CPV= • RV
Tis
D021103E.EPS
Ti: Integral time (Ti = I)

The Integration Block (INTEG) starts calculation actions in accordance with the values of
the manipulation switch (SW).
If the integral value overflows, the previous maximum value used as the calculation result.
When the integral value overflows, BAD (invalid) is set as the data status of the calculated
output value (CPV).
The following figure shows the manipulation switch values and the corresponding calcula-
tion actions as well as block status transitions.
• When Manipulation switch (SW) is 0
Starts to initialize calculation block status, then the manipulation switch (SW) changes
to 1 when initialization is completed. Block status is RUN.
Starts the integration calculation. The calculated output value (CPV) is updated by
each scan period. Block status is RUN.
Holds the current calculated output value (CPV), the calculation stops. Block status is
STOP.
■ Set Parameters
The parameters of the Integration Block (INTEG) are shown as follows.
• Gain (GAIN):
• Integral time setpoint (I):
A numeric number between 0.1 and 10000.0. Unit: sec.

■ Action Example
The following figure shows an action example of the Integration Block (INTEG).
Input signal
Ts
GAIN RV
I
Output signal
Time t
Scan period (Ts)
Hold Integration calculation Hold
Initialize Calculation stop
2 1 2
SW
SW(2A0A1) SW(1A2)
D021104E.EPS
Figure Action Example of Integration Block (INTEG)

■ CPV Pushback
close.
If the INTEG block is connected by means of cascade connection and the cascade connec-
The following calculation formula is used in the CPV pushback of the INTEG block.
CPV
RV=
GAIN
D021105E.EPS
SEE ALSO

■ Data Items – INTEG
Table Data Items of Integration Block (INTEG)
Item or Not
BSTS Block status ----- RUN
SW Manipulation switch 0, 1, 2 -----
I Integral time 0.1 to 10,000.0 seconds 1
D021106E.EPS

SEE ALSO
For a list of valid block modes for INTEG block, see chapter D2.3.2, “Valid Block Modes for Each Calcula-
tion Block.”
■ Block Status of Integration Block (INTEG)

Table Block Status of Integration Block (INTEG)
Block Status
Level Description
Symbol Name
RUN Integration Starts Initialization or integration starts.
1
STOP Integration Stops Integration stopped, the output is held.
D021107E.EPS

<Toc> <Ind> <D2.12 Derivative Block (LD)> D2-58
D2.12 Derivative Block (LD)

The Derivative Block (LD) is used when obtaining the derivative value of input data.
■ Derivative Block (LD)

▼ Connection
The Derivative Block (LD) is a function block that differentiates input data.
Here is a function block diagram of the Derivative Block (LD).
Input GAIN • Tds

IN RV CPV OUT
processing 1+Tds
(CPV, CPV)
SUB
D021201E.EPS
Figure Function Block Diagram of Derivative Block (LD)
terminals of the Derivative Block (LD).
Table Connection Types and Connection Destinations of the I/O Terminals of Derivative Block
(LD)
Data setting
Calculation
IN
input
Calculation
OUT
output
Auxiliary
SUB
output
D021202E.EPS

■ Function of Derivative Block (LD) ¡ £
The LD block performs input processing, calculation processing, output processing, and
alarm processing.
The only processing timing available for the LD block is a periodic startup. Selections
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the LD block, see
chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calcu-
lation Block.”
● Calculation Processing of Derivative Block (LD)

The LD block calculates the derivative value of input data using its calculation algorithm
and setup parameters.
● Output Processing Specific to Derivative Block (LD)

In the output processing of the LD block, it is possible to perform “CPV pushback.”

The Derivative Block (LD) executes the following calculation processing to differentiate
input data.
Tds
CPV=GAIN • • RV
1+Tds
D021203E.EPS
Td: Derivative time (Td = D)

When the block mode is switched from O/S (out of service) to AUT (automatic), or when the
data status of the calculated input value (CPV) returns to normal from CAL (calibration) or
BAD (invalid), derivation calculation is initialized with the calculated input value (RV).
■ Set Parameters
The parameters of the Derivative Block (LD) are shown as follows.
• Gain (GAIN):
• Derivative time setpoint (D):
If a time shorter than the scan period is set as the derivative time setpoint (D), calculation
processing is performed assuming that the derivative time setpoint (D) is same as the scan
period.
■ Action Example
The following figure shows an action example of the Derivative Block (LD).
Input signal
Time t
Td
Td: Derivative time (D) 0.0 to 10000.0 seconds

D021204E.EPS
Figure Step Response of Derivative Block (LD)

■ CPV Pushback
close.
If the LD block is connected by means of cascade connection and the cascade connection
is opened, the calculation input value (RV) is calculated back based on a calculation output
value (CPV) obtained from a downstream function block via tracking, thereby making the
upstream function block track the value.
The following calculation formula is used in the CPV pushback of the LD block.
CPV
RV=
GAIN
D021205E.EPS
SEE ALSO

■ Data Items – LD
Table Data Items of Derivative Block (LD)
Item or Not
D Derivative time 0.0 to 10,000.0 seconds 0
D021206E.EPS

SEE ALSO
For a list of valid block modes for LD block, see chapter D2.3.2, “Valid Block Modes for Each Calculation
Block.”

<Toc> <Ind> <D2.13 Ramp Block (RAMP)> D2-63
D2.13 Ramp Block (RAMP)

The Ramp Block (RAMP) is used to generate an output data to follow the step
changes of the input data with the ramp characteristic (constant velocity).
■ Ramp Block (RAMP)

▼ Connection
The Ramp Block (RAMP) is a function block that generates an output data to follow the
step changes of the input data with the ramp characteristic (constant velocity).
Here is a function block diagram of the Ramp Block (RAMP).
Input
IN RV GAIN • (Ramp characteristic) CPV OUT
processing
(CPV, CPV)
SUB
D021301E.EPS
Figure Function Block Diagram of Ramp Block (RAMP)
terminals of the Ramp Block (RAMP).
Table Connection Types and Connection Destinations of the I/O Terminals of Ramp Block
(RAMP)
Data setting
Calculation
IN
input
Calculation
OUT
output
Auxiliary
SUB
output
D021302E.EPS

■ Function of Ramp Block (RAMP) ¡ £
The RAMP block performs input processing, calculation processing, output processing,
The only processing timing available for the RAMP block is a periodic startup. Selections
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the RAMP block,
culation Block.”
● Calculation Processing of Ramp Block (RAMP)

The RAMP block performs computation using its calculation algorithm and setup param-
eters.

The Ramp Block (RAMP) executes the calculation processing that generates an output
data to follow the step changes of the input data with the ramp characteristic (constant
velocity).
The calculated output value (CPV) is the Ramp characteristic output signal multiplied by
the gain (GAIN).
CPV = GAIN • (Ramp characteristic)
The ramp characteristic is shown below.
Input signal
(CPV span)
• Scan period (sec.)
STEP
Scan period
D021303E.EPS
Figure Ramp Characteristic
The rate of the output data change is determined by the value of the step (STEP) param-
eter, scan period and span of the calculated output value (CPV).
CPV span
Output data change per second =
STEP
D021304E.EPS
CPV span
Output data change per scan = • Scan period (seconds)
STEP
D021305E.EPS
■ Set Parameters
The parameters of the Ramp Block (RAMP) are shown as follows.
• Gain (GAIN):
• Step (STEP):
A numeric number between 0.1 and 10000.0.
The step (STEP) defines in how many scans that the calculated output value (CPV) follows
up the full-span of the input change, in one second scan period. When the scan period is
not one second, the number of scans needed for the full-span input change can be calcu-
lated by dividing the step (STEP) by the scan period (second).

■ Data Items – RAMP
Table Data Items of Ramp Block (RAMP)
Item or Not
AF Alarm detection specificaton ----- -----
STEP Step 0.1 to 10,000.0 seconds 1
D021306E.EPS

SEE ALSO
For a list of valid block modes for RAMP block, see chapter D2.3.2, “Valid Block Modes for Each Calcula-
tion Block.”

<Toc> <Ind> <D2.14 Lead/Lag Block (LDLAG)> D2-67
D2.14 Lead/Lag Block (LDLAG)

The Lead/Lag Block (LDLAG) is used for dynamic compensation in feedforward
control.
■ Lead/Lag Block (LDLAG)

▼ Connection
The Lead/Lag Block (LDLAG) is a function block that performs dynamic compensation in
feedforward control. Normally, this block is used in combination with the controller block or
Feedforward Signal Summing Block (FFSUM).
Here is a function block diagram of the Lead/Lag Block (LDLAG).
Input GAIN • (1+Tds)

IN RV CPV OUT
processing 1+Tis
(CPV, CPV)
SUB
D021401E.EPS
Figure Function Block Diagram of Lead/Lag Block (LDLAG)
terminals of the Lead/Lag Block (LDLAG).
Table Connection Types and Connection Destinations of I/O Terminals of Lead/Lag Block
(LDLAG)
I/O terminal
Data setting
Calculation
IN
input
Calculation
OUT
output
Auxiliary
SUB
output
D021402E.EPS

■ Function of Lead/Lag Block (LDLAG) ¡ £
The LDLAG block performs input processing, calculation processing, output processing,
The only processing timing available for the LDLAG block is a periodic startup. Selections
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the LDLAG block,
culation Block.”
● Calculation Processing of Lead/Lag Block (LDLAG)

The LDLAG block performs computation using its calculation algorithm and setup param-
eters.
● Output Processing Specific to Lead/Lag Block (LDLAG)

In the output processing of the LDLAG block, it is possible to perform “CPV pushback.”

The Lead/Lag Block (LDLAG) executes the following calculation processing to perform
dynamic compensation of the lead/lag element.
GAIN • (1+Tds)
CPV= • RV
1+Tis
D021403E.EPS
Td: Lead time (Td = D)

Ti: Lag time (Ti = I - Scan period)
■ Set Parameters
The parameters of the Lead/Lag Block (LDLAG) are shown as follows.
• Gain (GAIN):
• Lead time setpoint (D):
• Lag time setpoint (I):
If a time shorter than the scan period is set as the lag time setpoint (I), calculation process-
ing is performed assuming that the lag time (I) is same as the scan period.
■ Action Example
The following figure shows the action of the Lead/Lag Block (LDLAG).
D/I>1
Input signal
Output signal (GAIN = 1.000)
D/I<1
Time t D021404E.EPS
Figure Action of Lead/Lag Block (LDLAG)

■ CPV Pushback
close.
If the LDLAG block is connected by means of cascade connection and the cascade con-
nection is opened, the calculation input value (RV) is calculated back based on a calcula-
tion output value (CPV) obtained from a downstream function block via tracking, thereby
making the upstream function block track the value.
The following calculation formula is used in the CPV pushback of the LDLAG block.
CPV
RV=
GAIN
D021405E.EPS
SEE ALSO

■ Data Items – LDLAG
Table Data Items of Lead/Lag Block (LDLAG)
Item or Not
D Lead time 0.0 to 10,000.0 seconds 0
I Lag time 0.1 to 10,000.0 seconds 1
D021406E.EPS

SEE ALSO
For a list of valid block modes for LDLAG block, see chapter D2.3.2, “Valid Block Modes for Each Calcula-
tion Block.”

<Toc> <Ind> <D2.15 Dead-Time Block (DLAY)> D2-72
D2.15 Dead-Time Block (DLAY)

The Dead-Time Block (DLAY) is used when simulating the dynamic process charac-
teristics.
■ Dead-Time Block (DLAY)

▼ Connection
The Dead-Time Block (DLAY) is a function block that simulates the dynamic process
characteristics using dead time and first-order lag.
Here is a function block diagram of the Dead-Time Block (DLAY).
Input GAIN -LS

IN RV e CPV OUT
processing 1+Tis
(CPV, CPV)
SUB
D021501E.EPS
Figure Function Block Diagram of Dead Block (DLAY)
terminals of the Dead-Time Block (DLAY).
Table Connection Types and Connection Destinations of the I/O Terminals of Dead-Time Block
(DLAY)
Data setting block
reference testing manipulation connection I/O I/O
IN Main input
Calculation
OUT
output
Auxiliary
SUB
output
D021502E.EPS

■ Function of Dead-Time Block (DLAY) ¡ £
The DLAY block performs input processing, calculation processing, output processing, and
alarm processing. The only processing timing available for the DLAY block is a periodic
period.
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the DLAY block,
culation Block.”
● Calculation Processing of Dead-Time Block (DLAY)

The DLAY block performs computation using its calculation algorithm and setup param-
eters.
● Output Processing Specific to Dead-Time Block (DLAY)

In the output processing of the DLAY block, it is possible to perform “CPV pushback.”

▼ Number of Sample Points
The Dead-Time Block (DLAY) realizes the dead time characteristic through sampling. For
this reason, the following calculation processing that uses dead time and first-order lag is
performed to simulate the dynamic process characteristics.
GAIN
CPV= e-LS • RV
1+Tis D021503E.EPS
L: Dead time L = Sampling interval (SMPL) • (m - I)

m: Number of sample points
Ti: First-order lag time (Ti = I - scan period)
e: Base number of natural logarithm
In order to smoothen the calculated output value (CPV), the Dead-Time Block (DLAY)
performs complementary calculation to values between sampled values when obtaining
the calculated output value (CPV).
Initialization of all sampled data (dead time buffer) is done by the reset switch (RST). When
the reset switch (RST) is set to “1,” the dead time buffer is initialized with the calculated
input value (RV). When the initialization is complete, the reset switch (RST) returns to “0”
(normal state). When the data status of the calculated output value (CPV) returns to normal
from IOP+ (input open high) or CAL (calibration), the reset switch (RST) changes to “1”
automatically and the dead time buffer is initialized.
The number of sample points is set on the Function Block Detail Builder.
• Number of Sample Points: A numeric value between 1 and 60
■ Set Parameters
The parameters of the Dead-Time Block (DLAY) are shown as follows.
• Gain (GAIN):
• Sampling interval (SMPL):
Set a value which is a multiple of the scan period.
• First-order lag time (I):
cessing is performed assuming that the first-order lag time (I) is same as the scan period.

■ Action Example
The following figure shows an action example of the Dead-Time Block (DLAY).
Input signal
Time t
L Ti
L Dead time
Ti First-order lag time (Ti = I - Scan period)
D021504E.EPS
Figure Action Example of Dead Time Block (DLAY)
■ CPV Pushback
close.
If the DLAY block is connected by means of cascade connection and the cascade connec-
The following calculation formula is used in the CPV pushback of the DLAY block.
CPV
RV=
GAIN
D021505E.EPS
SEE ALSO

■ Data Items – DLAY
Table Data Items of Dead-Time Block (DLAY)
Item or Not
RST Reset switch 0, 1 0
SMPL Sampling interval 0.1 to 10,000.0 seconds 1
D021506E.EPS

SEE ALSO
For a list of valid block modes for DLAY block, see chapter D2.3.2, “Valid Block Modes for Each Calcula-
tion Block.”

<Toc> <Ind> <D2.16 Dead-Time Compensation Block (DLAY-C)> D2-77
D2.16 Dead-Time Compensation Block (DLAY-C)

The Dead-Time Compensation Block (DLAY-C) is used for dead time compensation
control.
■ Dead-Time Compensation Block (DLAY-C)

▼ Connection
The Dead-Time Compensation Block (DLAY-C) is a function block that is used in combina-
tion with the controller block when performing dead time compensation control.
Here is a function block diagram of the Dead-Time Compensation Block (DLAY-C).
Input GAIN
IN RV (e-LS-1) CPV OUT
processing 1+Tis
(CPV, CPV)
SUB
D021601E.EPS
Figure Function Block Diagram of Dead-Time Compensation Block (DLAY-C)
The following figure shows an example of dead time compensation control using the Dead-
Time Compensation Block (DLAY-C).
PID controller block (PID)
- PID
Set point value
calculation
+
Input compensated value (VN)
Measured value
Dead-Time
Output Compensation Input
Block
(DLAY-C)
Process
D021602E.EPS
Figure Example of Dead Time Compensation Control Using Dead-Time Compensation Block
(DLAY-C)
terminals of the Dead-Time Compensation Block (DLAY-C).
Table Connection Types and Connection Destinations of the I/O Terminals of Dead Time
Compensation Block (DLAY-C)
Data setting
Calculation
IN
input
Calculation
OUT
output
Auxiliary
SUB
output
D021603E.EPS

■ Function of Dead-Time Compensation Block (DLAY-C) ¡ £
The DLAY-C block performs input processing, calculation processing, output processing,
The only processing timing available for the DLAY-C block is a periodic startup. Selections
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the DLAY-C block,
culation Block.”
● Calculation Processing of Dead-Time Compensation Block (DLAY-C)

The DLAY-C block performs computation using its calculation algorithm and setup param-
eters.
▼ Number of Sample Points
The Dead-Time Compensation Block (DLAY-C) performs the following calculation process-
ing. The dead time characteristic is realized through sampling.
GAIN
CPV= (e-LS -1) • RV
1+Tis
D021604E.EPS
L: Dead time L = Sampling interval (SMPL) • (m - I)

m: Number of sample points
e: Base number of natural logarithm
In order to smoothen the calculated output value (CPV), the Dead-Time Compensation
Block (DLAY-C) performs complementary calculation to the values between the sampled
values.
Initialization of all sampled data (dead time buffer) is done by the reset switch (RST). When
the reset switch (RST) is turned to “1,” the dead time buffer is initialized by the calculated
input value (RV). When the initialization is complete, the reset switch (RST) returns to “0”
(normal state). When the data status of the calculated output value (CPV) returns to normal
from IOP+ (input open high) or CAL (calibration), the reset switch (RST) changes to “1”
automatically and the dead time buffer is initialized.
The number of sample points is set on the Function Block Detail Builder.
• Number of Sample Points: A numeric value between 1 and 60

■ Set Parameters
The parameters of the Dead-Time Compensation Block (DLAY-C) are shown as follows.
• Gain (GAIN):
Set a multiple of the scan period as the value.
• First-order lag time (I):
cessing is performed assuming that the first-order lag time (I) is same as the scan period.
■ Action Example
The following figure shows an action example of the Dead-Time Compensation Block
(DLAY-C).
Input signal
Time t
L Dead time
Ti Ti First-order lag time (Ti = I - Scan period)
L
D021605E.EPS
Figure Action Example of Dead-Time Compensation Block (DLAY-C)

■ Data Items – DLAY-C
Table Data Items of Dead-Time Compensation Block (DLAY-C)
Item or Not
AF Alarm detection specificaton ----- -----
D021606E.EPS

SEE ALSO
For a list of valid block modes for DLAY-C block, see chapter D2.3.2, “Valid Block Modes for Each

<Toc> <Ind> <D2.17 Moving-Average Block (AVE-M)> D2-81
D2.17 Moving-Average Block (AVE-M)

The Moving-Average Block (AVE-M) is used when obtaining the moving average of
the input signals that have been received between the present and a certain time in
the past.
■ Moving-Average Block (AVE-M)

▼ Connection
The Moving-Average Block (AVE-M) is a function block that obtains the moving average of
the input signals that have been received between the present and a certain time in the
past.
Here is a function block diagram of the Moving-Average Block (AVE-M).
Input Xr+Xr-1+...+Xr-m+1
IN RV GAIN CPV OUT
processing m
(CPV, CPV)
SUB
D021701E.EPS
Figure Function Block Diagram of Moving-Average Block (AVE-M)
terminals of the Moving-Average Block (AVE-M).
Table Connection Types and Connection Destinations of the I/O Terminals of Moving-Average
Block (AVE-M)
Data setting
Calculation
IN
input
Calculation
OUT
output
Auxiliary
SUB
output
D021702E.EPS

■ Function of Moving Average Block (AVE-M) ¡ £
The AVE-M block performs input processing, calculation processing, output processing,
The only processing timing available for the AVE-M block is a periodic startup. Selections
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the AVE-M block,
culation Block.”
● Calculation Processing of Moving Average Block (AVE-M)

The AVE-M block calculates the moving average of an input signal using its calculation
algorithm and setup parameters.

The Moving-Average Block (AVE-M) performs the following calculation processing to
obtain the moving average of input data.
Xr+Xr-1+...+Xr-m+1
CPV=GAIN •
m D021703E.EPS
The Moving-Average Block (AVE-M) calculates the average value of past data that have
been sampled at a specified interval. The target input signals of this calculation are the
specified number of latest sampled data.
The following shows an action example of the Moving-Average Block (AVE-M) when the
specified number of samples is “6.”
Xr+Xr-1+...+Xr-m+1 Specified time interval (SMPL)

m CPV
X
RV GAIN
PREV
Xr
Xr-1 Xr-m+1
Moving average buffer r-8 r-7 r-6 r-5 r-4 r-3 r-2 r-1 r
Number of moving average samples at time r (6 points)

m Number of sample points: 1 to 60
SMPL Sampling interval: 0.1 to 10000.0 seconds
PREV Earliest sampled data: Number of moving average samples at time r-1 (6 points)
(Calculation input value of m • SMPL seconds before) • GAIN
Moving average measuring time = SMPL • m (second)
Number of moving average samples at time r-2 (6 points)
D021704E.EPS
Figure Action of Moving-Average Block (AVE-M)
Initialization of the moving average is done by the reset switch (RST). When the reset
switch (RST) is turned to “1,” the buffer is initialized with the calculated input value (RV).
When the initialization is complete, the reset switch (RST) returns to “0” (normal state).
When the data status of the calculated output value (CPV) returns to normal from IOP+
(input open high) or CAL (calibration), the reset switch (RST) changes to “1” automatically
and the moving average is initialized.
The earliest sampled data is stored in the earliest calculation input value (PREV) and is
available for reference.

■ Set Parameters
The parameters of the Moving-Average Block (AVE-M) are shown as follows.
• Gain (GAIN):
• Number of Sample Point (NUM):
A numeric value between 1 and 60.
For the sampling interval (SMPL), set a multiple of the scan period. If any other value is set,
sampling is performed at an interval rounded up to the next larger multiple of the scan
period.
How the sampling interval (SMPL) value is rounded up is shown as follows:
Scan period = 1 second SMPL = 0.5 A Action occurs assuming SMPL = 1
Scan period = 1 second SMPL = 1.1 A Action occurs assuming SMPL = 2
Scan period = 1 second SMPL = 2 A Action at SMPL = 2
Scan period = 0.1 second SMPL = 0.5 A Action at SMPL = 0.5

■ Data Items – AVE-M
Table Data Items of Moving-Average Block (AVE-M)
Item or Not
PREV Earliest calculation input value Value in the same engineering unit as CPV 0
NUM Number of samples 0 to 60 1
D021705E.EPS

SEE ALSO
For a list of valid block modes for AVE-M block, see a chapter D2.3.2, “Valid Block Modes for Each

<Toc> <Ind> <D2.18 Cumulative-Average Block (AVE-C)> D2-86
D2.18 Cumulative-Average Block (AVE-C)

The Cumulative-Average Block (AVE-C) is used when obtaining the average value
(integrated average value) of the input data received after a specified point in time.
■ Cumulative-Average Block (AVE-C)

▼ Connection
The Cumulative-Average Block (AVE-C) is a function block that calculates the average
value (integrated average value) of the input data received after a specified point in time.
Here is a function block diagram of the Cumulative-Average Block (AVE-C).
Manipulation SW
switch
Input
IN
processing
RV GAIN • Average CPV OUT
value
(CPV, CPV)
SUB
D021801E.EPS
Figure Function Block Diagram of Cumulative-Average Block (AVE-C)
terminals of the Cumulative-Average Block (AVE-C).
Table Connection Types and Connection Destinations of the I/O Terminals of Cumulative-
Average Block (AVE-C)
Data setting
Calculation
IN
input
Calculation
OUT
output
Auxiliary
SUB
output
D021802E.EPS

■ Function of Cumulative Average Block (AVE-C) ¡ £
The AVE-C block performs input processing, calculation processing, output processing,
The only processing timing available for the AVE-C block is a periodic startup. Selections
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the AVE-C block,
culation Block.”
● Calculation Processing of Cumulative Average Block (AVE-C)

The AVE-C block calculates the cumulative average (integral average value) of input data
using its calculation algorithm and setup parameters.

The Cumulative-Average Block (AVE-C) performs the processing that calculates the
average value (integrated average value) of input data.
The Cumulative-Average Block (AVE-C) starts calculation actions in accordance with the
values of the manipulation switch (SW).
When the manipulation switch is turned to “0,” the current calculated output value (CPV) is
saved as the previous average value (PREV), then average calculation is started again.
This is called initialization of integration calculation.
After that point, the integrated average value of input data for each scan period to the
current time cumulates until the manipulation switch (SW) turns to “0” again.
The calculated output value(CPV) is the cumulated integrated average value multiplied by
gain (GAIN).
CPV=GAIN • Cumulated Integrated average value
The status of calculation action is indicated by the block status.

The following figure shows the manipulation switch values (SW), corresponding actions
and block status transitions.
Starts to initialize calculation block status, then the manipulation switch (SW) changes
to 1 when initialization is completed. Block status is RUN.
Starts the average calculation. The calculated output value (CPV) is updated by each
scan period. Block status is RUN.
Holds the current calculated output value (CPV), the calculation stops. Block status is
STOP.
Start and end of integrated average calculation are set by the manipulation switch (SW).
The manipulation switch can be operated from operation and monitoring functions or other
function blocks.
Even when the block mode or alarm status has changed, the Cumulative-Average Block
(AVE-C) will not initialize the average value calculation automatically.
There is an integration number counter inside the Cumulative-Average Block (AVE-C).
When the manipulation switch (SW) is set to “1,” the value of this counter increases by one
for each scan period. When the counter value becomes 2,147,483,647, calculation will
stops and set the manipulation switch (SW) to “0,” then the calculation restarts.

■ Set Parameters
The parameters of the Cumulative-Average Block (AVE-C) are shown as follows.
• Manipulation switch:
Specify a numeric value from 0, 1 and 2.
• Gain (GAIN):
■ Action Example
The following figure shows an action example of the Cumulative-Average Block (AVE-C).
Calculated
output value
(CPV)
Calculated
input value
(RV)
Average value Average value

Hold calculation Hold calculation
Initialize Initialize
2 1 2 1
SW
(2A1) (1A2) (2A1) D021803E.EPS
Figure Action Example of Cumulative-Average Block (AVE-C)

■ Data Items – AVE-C
Table Data Items of Cumulative-Average Block (AVE-C)
Item or Not
BSTS Block status ----- RUN
SW Manipulation switch 0, 1, 2 0
PREV Previous average value Value in the same engineering unit as CPV SL
D021804E.EPS

SEE ALSO
For a list of valid block modes for AVE-C block, see chapter D2.3.2, “Valid Block Modes for Each Calcula-
tion Block.”
■ Block Status of Cumulative-Average Block (AVE-C)

Table Block Status of Block Status of Cumulative-Average Block (AVE-C)
Block Status
Level Description
Symbol Name
RUN Averaging Starts Initialization or averaging starts.
1
STOP Averaging Stops Averaging stopped, the output is held.
D021805E.EPS

<Toc> <Ind> <D2.19 Variable Line-Segment Function Block (FUNC-VAR)> D2-91
D2.19 Variable Line-Segment Function Block

(FUNC-VAR)
The Variable Line-Segment Function Block (FUNC-VAR) converts the input signal
into a function by using arbitrary unequal line segments.
The line segment characteristics can be changed from the Variable Line-Segment
Function Block (FUNC-VAR) on operation and monitoring functions.
■ Variable Line-Segment Function Block (FUNC-VAR)

▼ Connection
The Variable Line-Segment Function Block (FUNC-VAR) is a function block that converts
input signals in accordance with an arbitrary line-segment function.
Here is a function block diagram of the Variable Line-Segment Function Block (FUNC-
VAR).
Input Variable
IN RV GAIN • CPV OUT
processing line-segment function
(CPV, CPV)
SUB
D021901E.EPS
Figure Function Block Diagram of Variable Line-Segment Function Block (FUNC-VAR)
terminals of the Variable Line-Segment Function Block (FUNC-VAR).
Table Connection Types and Connection Destinations of the I/O Terminals of Variable Line-
Segment Function Block (FUNC-VAR)
Data setting
Calculation
IN
input
Calculation
OUT
output
Auxiliary
SUB
output
D021902E.EPS

■ Function of Variable Line-Segment Function Block (FUNC-VAR) ¡ £
The FUNC-VAR block performs input processing, calculation processing, output process-
The only processing timing available for the FUNC-VAR block is a periodic startup. Selec-
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the FUNC-VAR
● Calculation Processing of Variable Line-Segment Function Block

(FUNC-VAR)
The FUNC-VAR block converts the value of an input signal using its calculation algorithm
(line-segment function) and setup parameters.
● Output Processing Specific to Variable Line-Segment Function Block

(FUNC-VAR)
In the output processing of the FUNC-VAR block, it is possible to perform “CPV pushback.”

The Variable Line-Segment Function Block (FUNC-VAR) performs the calculation process-
ing that converts the input signal corresponding to the X coordinate of the set line segment,
to the Y coordinate value of the line segment.
The calculated output value (CPV) is the converted value multiplied by the gain (GAIN).
CPV=GAIN • Variable line-segment function output
■ Set Parameters
The parameters of the Variable Line-Segment Function Block (FUNC-VAR) are shown as
follows.
• Number of segments (SECT):
• X_axis coordinate (input):
Set the engineering unit input signal after input signal conversion.
X01 to X15 (1 to Number of line-segment divisions + 1)
• Y_axis coordinate (output):
Set the engineering unit calculated output value (CPV).
Y01 to Y15 (1 to Number of line-segment divisions + 1)
Line-segment coordinates can be set from operation and monitoring functions or other
function blocks.
Set the X_axis coordinate line-segment function in the continues increasing direction.
When the setting does not allow the X coordinate to increase strictly, the function assumes
that the function is represented by the solid line shown in the figure below.
Y
Set line segment
(error)
Action line segment
X
D021903E.EPS
Figure Action When Line-Segment Function Setting Error Occurs

■ Action Example
The following figure shows an example of the variable line-segment function with six
segments.
Y (Output value: Engineering unit data of CPV)
6
5
4
X (Input value: Engineering unit data)
D021904E.EPS
Figure Example of a Variable Line-Segment Function with Six segments
■ CPV Pushback
close.
If the FUNC-VAR block is connected by means of cascade connection and the cascade
connection is opened, the calculation input value (RV) is calculated back based on a
calculation output value (CPV) obtained from a downstream function block via tracking,
thereby making the upstream function block track the value.
In the CPV pushback of the FUNC-VAR block, the value RV is obtained by calculating the
x-axis coordinate while using the value obtained by dividing CPV by GAIN as the input on
the y-axis.
SEE ALSO

■ Data Items – FUNC-VAR
Table Data Items of Variable Line-Segment Function Block (FUNK-VAR)
Item or Not
7 - digit real number including sign and decimal
GAIN Gain 1.00
point
SECT Number of segments 1 to 14 1
X01 to X15 X-axis line-segment breakpont ----- -----
Y01 to Y15 Y-axis line-segment breakpont ----- -----
D021905E.EPS

SEE ALSO
For a list of valid block modes for FUNC-VAR block, see chapter D2.3.2, “Valid Block Modes for Each

<Toc> <Ind> <D2.20 Temperature and Pressure Correction Block (TPCFL)> D2-96
D2.20 Temperature and Pressure Correction Block

(TPCFL)
The Temperature and Pressure Correction Block (TPCFL) are used to correct the
flowrate measured by a differential pressure flowmeter on the basis of temperature
and pressure.
■ Temperature and Pressure Correction Block (TPCFL)

▼ Connection
The Temperature and Pressure Correction Block (TPCFL) are used to correct the flowrate,
that measured by a differential pressure flowmeter, of a gas relative to the ideal gas on the
basis of temperature and pressure.
Here is a function block diagram of the Temperature and Pressure Correction Block
(TPCFL).
Input
IN processing RV
Correction
Q01 TMP CPV OUT
computation
Q02 PRS
(CPV, CPV)
SUB
D022001E.EPS
Figure Function Block Diagram of Temperature and Pressure Correction Block (TPCFL)
terminals of the Temperature and Pressure Correction Block (TPCFL).
Table Connection Types and Connection Destinations of the I/O Terminals of Temperature and
Pressure Correction Block (TPCFL).
I/O terminal
Data setting
Measured
IN
flowrate
Measured
Q01
temperature
Measured
Q02
pressure
Calculation
OUT
output
Auxiliary
SUB
output
D022002E.EPS

■ Function of Temperature and Pressure Correction Block (TPCFL)
¡£
The TPCFL block performs input processing, calculation processing, output processing,
The only processing timing available for the TPCFL block is a periodic startup. Selections
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the TPCFL block,
culation Block.”
● Calculation Processing of Temperature and Pressure Correction Block

(TPCFL)
The TPCFL block performs computation using its calculation algorithm and setup param-
eters.

▼ Corrective Computation
The Temperature and Pressure Correction Block (TPCFL) correct the flowrate of a gas
relative to an ideal gas on the basis of temperature and pressure.
The following three types of correction computation algorithms are available:
• Temperature and pressure correction computations
• Temperature correction computation
• Pressure correction computation
Both the input and the output of the correction computation are floating-point data.
The calculated output value (CPV) is the corrected flowrate (F0) multiplied by the gain
(GAIN).
CPV = GAIN • F0
● Temperature and Pressure Computation

In a temperature and pressure computation, correction computations of both temperature
and pressure are performed. The following is a correction computation expression with the
measured flowrate of Fi, reference pressure of Pb, reference temperature of Tb, measured
pressure of P, and when the pressure unit of the measured temperature T is [kPa].
P+1.01325 • 102 Tb+273.15 Pressure: kPa

F0 = • • Fi
Pb+1.01325 • 10 2
T+273.15 Temperature: C
D022003E.EPS
Fi: Measured flowrate
F0: Corrected flowrate
P: Measured pressure [kPa]
P b: Reference pressure [kPa]
T: Measured temperature (C)
Tb: Reference temperature (C)
With the pressure unit of kgf/cm2 and the temperature unit of F, the expression is given
below.
P+1.0332 T'b+273.15 Pressure: kgf/cm2

F0= • Fi
Pb+1.0332 T'+273.15 Temperature: F
5 5
T'= (T -32) T'b= (Tb-32)
9 9
D022004E.EPS

P: Measured pressure [kgf/cm2]
T: Measured temperature (F)
P b: Reference pressure [kgf/cm2]
Tb: Reference temperature (F)

● Temperature Correction Computation
In temperature correction computation, only a correction computation of temperature is
performed with the measured flowrate of Fi, reference temperature of Tb, and measured
temperature of T. A correction computation expression is shown below.
Tb+273.15
F0= • Fi [Temperature: C]
T+273.15
D022005E.EPS

The formula for corrective calculation at the temperature unit F is given below.
T'b+273.15
F0= Fi
T'+273.15
D022006E.EPS
● Pressure Correction Computation

In pressure correction computation, only a correction computation of pressure is performed
with the measured flowrate of Fi, reference pressure of Pb, and measured pressure of P.
The correction computation expression is as follows when the pressure unit is [kPa].
P+1.01325 • 102
F0= • Fi [Pressure: kPa]
Pb+1.01325 • 102
D022007E.EPS

P: Measured pressure [kPa]
Pb: Reference pressure [kPa]
The expression for corrective calculation at the pressure unit kgf/cm2 is given below.
P+1.0332
F0= Fi
Pb+1.0332
D022008E.EPS

■ Set Parameters
▼ Pressure Unit, Temperature Unit
The parameters of the Temperature and Pressure Correction Block (TPCFL) are shown as
follows.
• Reference temperature (TB):
Depends on the temperature unit specified in the builder. Degree C or F.
• Reference pressure (PB): Depends on the unit specified in the builder.
• Gain (GAIN):
“Correction computation,” “temperature unit” and “pressure unit” are set in the
• Corrective Computation:
Select from “Temperature and Pressure Correction,” “Pressure Correction,” and
“Temperature Correction.”
The default is “Temperature Correction.”
• Temperature Units:
Only Deg. C may be selected from the list. If use Fahrenheit degree, F may be manu-
ally entered in the entry box.
• Pressure Units: Select from “Pa,” “kPa,” and “MPa.”
The default is “kPa.”
If use kgf/cm2, KGF/CM2 may be manually entered in the entry box.
TIP
Only F can be manually entered in the temperature’s entry box, and only KGF/CM2 can be entered in the
pressure entry box. Entering other unit or strings may generated entry error.
Pjt:MYPJT Stn:FCS0101 Drow:DR0001 File:TPCFL1.edf-...

Pressure Alarm Control Calculation Output
Unit
3: kPa
2: Pa Pressure Unit KGF/CM2
4: MPa
Temperature Unit F
D022009E.EPS
Figure Example of Manually Entry of F and KGF/CM2

■ Data Items – TPCFL
Table Data Items of Temperature and Pressure Correction Block (TPCFL)
Item or Not
RV Measured flowrate ----- 0
TMP Measured temperature ----- 0
PRS Measured pressure ----- 0
TB Reference temperature ----- 0
PB Reference pressure ----- 0
D022010E.EPS

SEE ALSO
For a list of valid block modes for TPCFL block, see chapter D2.3.2, “Valid Block Modes for Each Calcula-
tion Block.”

<Toc> <Ind> <D2.21 ASTM Correction Block : Old JIS (ASTM1)> D2-102
D2.21 ASTM Correction Block : Old JIS (ASTM1)

The ASTM Correction Block: Old JIS (ASTM1) is used when performing correction
computation based on the ASTM correction (old JIS).
■ ASTM Correction Block : Old JIS (ASTM1)

▼ Connection
The ASTM Correction Block: Old JIS (ASTM1) performs correction computation on the
flowrate of crude oil and petroleum products based on the ASTM correction (Old JIS) based
on the measured temperature and specific gravity.
Here is a function block diagram of the ASTM Correction Block: Old JIS (ASTM1).
Input
IN RV
processing
Correction
CPV OUT
computation
Q01 TMP
(CPV, CPV)
SUB
D022101E.EPS
Figure Function Block Diagram of ASTM Correction Block : Old JIS (ASTM1)
terminals of the ASTM Correction Block: Old JIS (ASTM1).
Table Connection Types and Connection Destinations of the I/O Terminals of ASTM Correction
Block : Old JIS (ASTM1)
Data setting
Measured
IN
flowrate
Measured
Q01
temperature
Calculation
OUT
output
Auxiliary
SUB
output
D022102E.EPS

■ Function of ASTM Correction Block : Old JIS (ASTM1) ¡ £
The ASTM1 block performs input processing, calculation processing, output processing,
The only processing timing available for the ASTM1 block is a periodic startup. Selections
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the ASTM1 block,
culation Block.”
● Calculation Processing of ASTM Correction Block : Old JIS (ASTM1)

The ASTM1 block performs computation using its calculation algorithm and setup param-
eters.

▼ Temperature Unit
The ASTM Correction Block: Old JIS (ASTM1) performs temperature correction computa-
tion of flowrates at the measured temperature of t and specific gravity of c, based on the
ASTM correction computation (Old JIS).
In a specific gravity range not shown in the ASTM table for the ASTM correction computa-
tion (Old JIS), the same computation can be performed by extending the applicability to
Table II of JIS K2249.
The specific gravity ranges and temperature range of the ASTM and Table II of JIS K2249
are shown below.
-25 C 1.100
1.1
Old JIS
1
125 C 0.960
0.9
100 C 0.870
75 C 0.840
Specific gravity 0.8 Old JIS & ASTM
at 15/4 C (C1)
0.7
-46 C 60 C
0.6 0.600
Old JIS
55 C 0.510
0.5
-50 0 50 100 150 200
Temperature (C) D022103E.EPS
Figure Specific Gravity Ranges and Temperature Ranges of the ASTM Correction Computation
(Old JIS) and Table II of JIS K2249 (Old JIS)
ASTM correction computation under the old JIS is shown below.
F0 = Cf • Fi
Cf = 1 + (TMP-15) + (TMP-15)2
-P2 (TMP) -P3 (TMP)

= + P2 (TMP) , = + P4 (TMP)
C1 C1
D022104E.EPS
TMP: Measured temperature (C)
C1: Specific gravity (15/4 C)
P1 (TPM) to P4 (TPM): Parameters determined by temperature
(GAIN).
CPV = GAIN • F0
The temperature unit is specified in the Function Block Detail Builder.

• Temperature Units: Deg. C
■ Set Parameters
The parameters of the ASTM Correction Block: Old JIS (ASTM1) are shown as follows.
• Specific gravity at 15/4 C (DEN):
Set within the specific gravity range shown in Table II of JIS K2249.
• Gain (GAIN):
■ Data Items – ASTM1

Table Data Items of ASTM Correction Block : Old JIS (ASTM1)
Item or Not
DEN Specific gravity ----- 0
D022105E.EPS

SEE ALSO
For a list of valid block modes for ASTM1 block, see chapter D2.3.2, “Valid Block Modes for Each Calcula-
tion Block.”

<Toc> <Ind> <D2.22 ASTM Correction Block : New JIS (ASTM2)> D2-106
D2.22 ASTM Correction Block : New JIS (ASTM2)

The ASTM Correction Block: New JIS (ASTM2) is used when performing correction
computation based on the ASTM correction (new JIS).
■ ASTM Correction Block : New JIS (ASTM2)

▼ Connection
The ASTM Correction Block: New JIS (ASTM2) performs correction computation on the
flowrate of crude oil and petroleum products based on the ASTM correction (New JIS)
based on the measured temperature and specific gravity.
Here is a function block diagram of the ASTM Correction Block: New JIS (ASTM2).
Input
IN RV
processing
Correction
CPV OUT
computation
Q01 TMP
(CPV, CPV)
SUB
D022201E.EPS
Figure Function Block Diagram of ASTM Correction Block: New JIS (ASTM2)
terminals of the ASTM Correction Block: New JIS (ASTM2).
Table Connection Types and Connection Destinations of the I/O Terminals of ASTM Correction
Block: NEW JIS (ASTM2)
Data setting
Measured
IN
flowrate
Measured
Q01
temperature
Calculation
OUT
output
Auxiliary
SUB
output
D022202E.EPS

■ Function of ASTM Correction Block : New JIS (ASTM2) ¡ £
The ASTM2 block performs input processing, calculation processing, output processing,
The only processing timing available for the ASTM2 block is a periodic startup. Selections
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the ASTM2 block,
culation Block.”
● Calculation Processing of ASTM Correction Block : New JIS (ASTM2)

The ASTM2 block performs computation using its calculation algorithm and setup param-
eters.

▼ Type of Oil, Temperature Unit
The ASTM Correction Block: New JIS (ASTM2) calculates the corrected flowrate of the
flowrate F at the measured temperature of t and density of p, based on the ASTM correc-
tion computation (Old JIS).
ASTM correction computation based on the new JIS is shown below.
F0 = Cf • Fi
Cf = exp {- (TMP - 15) - 0.82 (TMP - 15)2}
K0 K1 B
= + or = A +
2
2
D022203E.EPS

TMP: Measured temperature (C)
: Density at 15 C (kg/m3)
K0, K1, A, B: Oil dependent constants
The specific correction computation under the ASTM correction (New JIS) varies depend-
ing upon the type of oil used. Select appropriate constants from the table below.
Table Types of Oil and Oil Dependent Constants
Constants
Type of oil Density range at 15kg/m3
K0 K1 A B
Crude oil 610.5 1075.0 613.9723 0.0
653.0 < 770.25 346.4228 0.4388
770.25 < 787.75 -0.00336312 2680.3206
Fuel oil
787.75 < 838.75 594.5418 0.0
838.75 1075.0 186.9696 0.4862
Lubricating oil 800.0 1164.0 0.0 0.6278
D022204E.EPS
(GAIN).
CPV = GAIN • F0
The “type of oil” and “temperature unit” are set on the Function Block Detail Builder.
• Type of Oil: Select from “Crude,” “Fuel Oil” and “Lubricant.”
• Temperature Units: Deg. C

■ Set Parameters
The parameters of the ASTM Correction Block: New JIS (ASTM2) are shown as follows.
• Density at 15 C (DEN):
Data with the unit of kg/m3.
• Gain (GAIN):
An actual quantity value of 7 digits or less including the sign and decimal point.
■ Data Items – ASTM2

Table Data Items of ASTM Correction Block : New JIS (ASTM2)
Item or Not
DEN Density ----- 0
D022205E.EPS

SEE ALSO
For a list of valid block modes for ASTM2 block, see chapter D2.3.2, “Valid Block Modes for Each Calcula-
tion Block.”

<Toc> <Ind> <D2.23 Logical AND Block (AND), Logical OR Block (OR)> D2-110
D2.23 Logical AND Block (AND), Logical OR Block

(OR)
AND block is used to calculated the product of RV1 and RV2. OR block is used to
calculate the sum of RV1 and RV2.
■ Logical AND Block (AND), Logical OR Block (OR) £

▼ Connection
AND is the function block to be used to calculate the product of RV1 and RV2 and OR is
the function block to be used to calculate the sum of RV1 and RV2.
Here is a function block diagram of Logical AND Block (AND) and Logical OR Block (OR).
Input
Q01 RV1
Processing
Calculation Output
CPV OUT
Processing Processing
Input
Q02 RV2
Processing
D022301E.EPS
Figure Function Block Diagram of Logical AND Block (AND) and Logical OR Block (OR) £
terminals of Logical AND Block (AND) and Logical OR Block (OR).
Table Connection Types and Connection Destinations of I/O Terminals of Logical AND Block
(AND) and Logical OR Block (OR) £
Data setting
Calculation
Q01
input 1
Calculation
Q02
input 2
Calculation
OUT
output
D022302E.EPS

■ Functions of Logical AND Block (AND) and Logical OR Block (OR) £
The AND and OR blocks perform input processing, calculation processing, output process-
The processing timings available for the AND and OR 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 KFCS2, KFCS, LFCS2 and LFCS.
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the AND and OR
blocks, see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for
Each Calculation Block.”
● Calculation Processing of Logical AND Block (AND) and Logical OR Block

(OR) £
The AND block calculates the logic product of the calculation input values (RV1, RV2) using
its calculation algorithm. The OR block calculates the logic sum of the calculation input
values (RV1, RV2) using its calculation algorithm.
■ Calculation Algorithm £
The calculated output value (CPV) and the calculated input value (RV1, RV2) have the
following relationship.
Table Relationship of Input and Output of Logical AND Block (AND) £
RV1 0 0 0 0
RV2 0 0 0 0
CPV 0 0 0 1
D022303E.EPS
Table Relationship of Input and Output of Logical OR Block (OR) £

RV1 0 0 0 0
RV2 0 0 0 0
CPV 0 1 1 1
D022304E.EPS

■ Data Items – AND and OR £
Table Data Items of Logical AND Block (AND), Logical OR Block (OR) £
Entry
Data Data Name Range Default
Permission
RV1 Calculation input value 1 0
CPV Calculated output value (*1) 0, 1 0
D022305E.EPS

SEE ALSO
For a list of valid block modes for AND and OR blocks, see chapter D2.3.2, “Valid Block Modes for Each

<Toc> <Ind> <D2.24 Logical NOT Block (NOT)> D2-113
D2.24 Logical NOT Block (NOT)

NOT block is used to perform the negation calculation.
■ Logical NOT Block (NOT) £

▼ Connection
NOT is the function block to be used to calculate the negation of the calculated input value
(RV).
Here is a function block diagram of Logical NOT Block (NOT).

IN RV CPV OUT
Processing Processing Processing
D022401E.EPS
Figure Function Block Diagram of Logical NOT Block (NOT) £
terminals of Logical NOT Block (NOT).
Table Connection Types and Connection Destinations of I/O Terminals of Logical NOT Block
(NOT) £
Data setting
Calculation
IN
input
Calculation
OUT
output
D022402E.EPS
■ Function of Logical NOT Block (NOT) £

The NOT block performs input processing, calculation processing, output processing, and
alarm processing.
The processing timings available for the NOT block are a periodic startup and a one-shot
period.
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the NOT block,
see D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation
Block.”

<Toc> <Ind> <D2.24 Logical NOT Block (NOT)> D2-114
● Calculation Processing of Negative Block (NOT) £
The NOT block performs a negative operation on the calculation input value (RV) using its
calculation algorithm.
The calculated output value (CPV) and the calculated input value (RV) have the following
relationship.
Table Relationship of Input and Output of Logical NOT Block (NOT) £
RV 0 0
CPV 1 0
D022403E.EPS
■ Data Items – NOT £

Table Data Items of Logical NOT Block (NOT) £
Entry
Permission
RV Calculation input value 0
CPV Calculated output value (*1) 0, 1 SL
D022404E.EPS

SEE ALSO
For a list of valid block modes for NOT block, see chapter D2.3.2, “Valid Block Modes for Each Calcula-
tion Block.”

<Toc> <Ind> <D2.25 Flip-Flop Blocks (SRS1-S, SRS1-R, SRS2-S, SRS2-R)> D2-115
D2.25 Flip-Flop Blocks (SRS1-S, SRS1-R, SRS2-S,

SRS2-R)
SRS1-S, SRS1-R, SRS2-S and SRS2-R blocks are the function blocks used for flip-
flop operations.
■ Flip-Flop Blocks (SRS1-S, SRS1-R, SRS2-S, SRS2-R) £

▼ Connection
SRS1-S, SRS1-R, SRS2-S and SRS2-R blocks are the function blocks give the flip-flop
operation output CPV according the calculated input value of RV1 and RV2. SRS1-S,
SRS1-R, SRS2-S and SRS2-R blocks are classified as follows.
• Set-Dominant Flip-Flop Block with 1 Output (SRS1-S)
• Reset-Dominant Flip-Flop Block with 1 Output (SRS1-R)
• Set-Dominant Flip-Flop Block with 2 Outputs (SRS2-S)
• Reset-Dominant Flip-Flop Block with 2 Outputs (SRS2-R)
Input Output
Q01 RV1 CPV1 J01
Calculation
Processing
Input
Q02 RV2
Processing
SRS1-S and SRS1-R
Input
Q01 RV1 CPV1 J01
Processing
Calculation Output
Input
Q02 RV2 CPV2 J02
Processing
SRS2-S and SRS2-R

D022501E.EPS
Figure Function Block Diagram of SRS1-S, SRS1-R, SRS2-S and SRS2-R Blocks £

terminals of SRS1-S, SRS1-R, SRS2-S and SRS2-R blocks.
Table Connection Types and Connection Destinations of the I/O Terminals of SRS1-S, SRS1-R,
SRS2-S and SRS2-R Blocks £
Data setting
Calculation
Q01
input 1
Calculation
Q02
input 2
Calculation
J01
output 1
Calculation
J02
output 2
D022502E.EPS
■ Functions of Flip-Flop Blocks (SRS1-S, SRS1-R, SRS2-S, SRS2-R) £

The SRS1-S, SRS1-R, SRS2-S, and SRS2-R blocks perform input processing, calculation
processing, output processing, and alarm processing.
The processing timings available for the SRS1-S, SRS1-R, SRS2-S, and SRS2-R 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.
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the SRS1-S,
SRS1-R, SRS2-S, and SRS2-R blocks, see chapter D2.3.1, “Input Processing, Output Processing, and
Alarm Processing Possible for Each Calculation Block.”
● Calculation Processing of Flip-Flop Blocks (SRS1-S, SRS1-R, SRS2-S,

SRS2-R) £
The SRS1-S, SRS1-R, SRS2-S, and SRS2-R blocks perform a flip-flop operation using
their calculation algorithms.

The calculated output value (CPV) and the calculated input value (RV1, RV2) have the
Table Relationship of Input and Output of Set-Dominant Flip-Flop Block with 1 Output (SRS1-S)
£
RV1 0 0 0 0
Input
RV2 0 0 0 0
CPV1 Hold 1 0 1
Output
- - - - -
D022503E.EPS
Table Relationship of Input and Output of Reset-Dominant Flip-Flop Block with 1 Output (SRS1-
R) £
RV1 0 0 0 0
Input
RV2 0 0 0 0
CPV1 Hold 1 0 0
Output
- - - - -
D022504E.EPS
Table Relationship of Input and Output of Set-Dominant Flip-Flop Block with 2 Outputs (SRS2-S)
£
RV1 0 0 0 0
Input
RV2 0 0 0 0
CPV1 Hold 1 0 1
Output
CPV2 Hold 0 1 0
D022505E.EPS
Table Relationship of Input and Output of Reset-Dominant Flip-Flop Block with 2 Outputs
(SRS2-R) £
RV1 0 0 0 0
Input
RV2 0 0 0 0
CPV1 Hold 1 0 0
Output
CPV2 Hold 0 1 1
D022506E.EPS

■ Data Items – SRS1-S, SRS1-R, SRS2-S, SRS2-R £
Table Data Items of SRS1-S, SRS1-R, SRS2-S, SRS2-R flip-flop blocks £
Entry
Permission
RV1 Calculation input value1 0

CPV1 Calculated output value1 (*1) 0, 1 0
CPV2 Calculated output value2 0, 1 0
D022507E.EPS

SEE ALSO
For a list of valid block modes for SRS1-S, SRS1-R, SRS2-S and SRS2-R blocks, see chapter D2.3.2,
“Valid Block Modes for Each Calculation Block.”

<Toc> <Ind> <D2.26 Wipeout Block (WOUT)> D2-119
D2.26 Wipeout Block (WOUT)

The WOUT block is used for the logical operation to output the AND of the calcula-
tion input value1 (RV1) and the NOT of the calculation input value2 (RV2).
■ Wipeout Block (WOUT) £

▼ Connection
The WOUT block is the function block to be used for the logical operation to output the AND
of the calculation input value1 (RV1) and the NOT of the calculation input value2 (RV2).
Here is a function block diagram of Wipeout Block (WOUT).
Input
Q01 RV1
Processing
Calculation Output
CPV OUT
Input
Q02 RV2
Processing
D022601E.EPS
Figure Function Block Diagram of Wipeout Block (WOUT) £
terminals of Wipeout Block (WOUT).
Table Connection Types and Connection Destinations of the I/O Terminals of Wipeout Block
(WOUT) £
Data setting
Calculation
Q01
input 1
Calculation
Q02
input 2
Calculation
OUT
output
D022602E.EPS

■ Function of Wipeout Block (WOUT) £
The WOUT block performs input processing, calculation processing, output processing,
The processing timings available for the WOUT block are a periodic startup and a one-shot
period.
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the WOUT block,
culation Block.”
● Calculation Processing of Wipeout Block (WOUT) £

The WOUT block performs computation using its calculation algorithm.
The calculated output value (CPV) and the calculation input value (RV1, RV2) have the
Table Relationship of Input and Output of Wipeout Block (WOUT) £
RV1 0 0 0 0
Input
RV2 0 0 0 0
Output CPV 0 1 0 0
D022603E.EPS

■ Data Items – WOUT £
Table Data Items of Wipeout Block (WOUT) £
Entry
Permission
D022604E.EPS

SEE ALSO
For a list of valid block modes for WOUT block, see chapter D2.3.2, “Valid Block Modes for Each Calcula-
tion Block.”

<Toc> <Ind> <D2.27 ON-Delay Timer Block (OND)> D2-122
D2.27 ON-Delay Timer Block (OND)

OND block is used for the operation to output the logic value 1 as calculated output
value (CPV) when the pre-defined time elapsed after the calculation input value (RV)
is changed to a value other than 0.
■ ON-Delay Timer Block (OND) £

▼ Connection
OND block is used for the operation to output the logic value 1 when the pre-defined time
elapsed after the calculation input RV is changed to a value other than 0.
The calculated output value (CPV) is 0 when the calculation input value (RV) is 0.
Here is a function block diagram of ON-Delay Timer Block (OND).
IN Input RV Calculation CPV Output OUT

D022701E.EPS
Figure Function Block Diagram of ON-Delay Timer Block (OND) £
terminals of ON-Delay Timer Block (OND).
Table Connection Types and Connection Destinations of the I/O Terminals of ON-Delay Timer
Block (OND) £
Data setting
Calculation
IN
input
Calculation
OUT
output
D022702E.EPS

■ Function of ON-Delay Timer Block (OND) £
The OND block performs input processing, calculation processing, output processing, and
alarm processing.
The only processing timing available for the OND block is a periodic startup. Selections
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the OND block,
culation Block.”
● Calculation Processing of ON-Delay Timer Block (OND) £

The OND block sets the calculation output value (CPV) to 1 after the pre-defined time
(STM) has elapsed using its calculation algorithm and setup parameters.

▼ Time Unit
The calculation algorithm of ON-Delay Timer Block may be illustrated as follows.
• The timer is initiated when the calculation input value (RV) is changed to a value other
than 0.
• When timer is running, the current elapsed time (PTM) displays.
• When pre-defined time (STM) elapsed, the calculated output value (CPV) changes
from 0 to 1.
• When the calculation input value (RV) changes to 0, the calculated output value (CPV)
is reset to 0.
0
RV
0
t
STM Timer start Timer reset
t<STM
1
CPV
D022703E.EPS
Figure ON-Delay Timer Block (OND) Calculation Algorithm £
The time unit of the timer block may be set on the Function Block Detail Builder.
• Time Unit: Select between “Second” and “Minute.”
The default is “Second.”
■ Setting Parameter £
OND block has the following setting parameters.
• Set Time (STM): 1 to 10000

■ Data Items – OND £
Table Data Items of ON-Delay Timer Block (OND) £
Entry
Permission
STM Pre-defined time 1 to 10000 1
PTM Elapsed time 0 to 10000 0
D022704E.EPS

SEE ALSO
For a list of valid block modes for OND block, see chapter D2.3.2, “Valid Block Modes for Each Calcula-
tion Block.”

<Toc> <Ind> <D2.28 OFF-Delay Timer Block (OFFD)> D2-126
D2.28 OFF-Delay Timer Block (OFFD)

OFFD block is used for the operation to output the logic value 0 as calculated output
value (CPV) when the pre-defined time elapsed after the calculation input value (RV)
is changed to 0.
■ OFF-Delay Timer Block (OFFD) £

▼ Connection
OFFD block is used for the operation to output the logic value 0 when the pre-defined time
(STM) elapsed after the calculation input RV is changed from 1 to 0.
Here is a function block diagram of OFF-Delay Timer Block (OFFD).

IN RV CPV OUT
D022801E.EPS
Figure Function Block Diagram of OFF-Delay Timer Block (OFFD) £
terminals of OFF-Delay Timer Block (OFFD).
Table Connection Types and Connection Destinations of the I/O Terminals of OFF-Delay Timer
Block (OFFD) £
Data setting
Calculation
IN
input
Calculation
OUT
output
D022802E.EPS

■ Function of Off-Delay Timer Block (OFFD) £
The OFFD block performs input processing, calculation processing, output processing, and
alarm processing.
The only processing timing available for the OFFD block is a periodic startup. Selections
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the OFFD block,
culation Block.”
● Calculation Processing of Off-Delay Timer Block (OFFD) £

The OFFD block sets the calculation output value (CPV) to 0 after the pre-defined time
(STM) has elapsed using its calculation algorithm and setup parameters.

▼ Time Unit
The calculation algorithm of OFF-Delay Timer Block may be illustrated as follows.
• The timer is initiated when the calculation input value (RV) is changed to 0.
• When timer is running, the current elapsed time (PTM) displays.
• When pre-defined time (STM) elapsed, the calculated output value (CPV) changes
from 1 to 0.
• When the calculation input value (RV) changes to a value other than 0, the calculated
output value (CPV) is reset to 1.
0
RV
0
t
STM
Timer start Timer reset
t<STM
1
CPV
D022803E.EPS
Figure OFF-Delay Timer Block (OFFD) Calculation Algorithm £
The time unit of the timer block may be set on the Function Block Detail Builder.
• Time Unit: Select between “Second” and “Minute.”
The default is “Second.”
■ Setting Parameter £
OFFD timer block has the following setting parameters.
• Set Time (STM): 1 to 10000

■ Data Items – OFFD £
Table Data Items of OFF-Delay Timer Block (OFFD) £
Entry
Permission
STM Pre-defined time 1 to 10000 1
PTM Elapsed time 0 to 10000 0
D022804E.EPS

SEE ALSO
For a list of valid block modes for OFFD block, see chapter D2.3.2, “Valid Block Modes for Each Calcula-
tion Block.”

<Toc> <Ind> <D2.29 One-Shot Blocks Rise Trigger (TON), Fall Trigger (TOFF)> D2-130
D2.29 One-Shot Blocks Rise Trigger (TON), Fall

Trigger (TOFF)
TON block is used for the operation to output the logic value 1 as calculated output
value (CPV) for one scan period when the calculation input value (RV) is changed to
a value other than 0.
TOFF block is used for the operation to output the logic value 1 for one scan period
when the calculation input value (RV) is changed to 0.
■ One-Shot Blocks Rise Trigger (TON), Fall Trigger (TOFF) £

▼ Connection
TON block and TOFF block are used for the operation to output the logic value 1 as calcu-
lated output value (CPV) for one scan period when the calculation input value (RV) of TON
block is changed to a value other than 0, or the calculation input value (RV) of TOFF is
changed to 0. Otherwise, the calculated output value (CPV) is kept as 0.
Here is a function block diagram of One-shot blocks TON and TOFF.

D022901E.EPS
Figure Function Block Diagram of One-shot Blocks TON and TOFF £
terminals of One-shot blocks TON and TOFF.
Table Connection Types and Connection Destinations of the I/O Terminals of One-shot Blocks
TON and TOFF £
Data setting
Calculation
IN
input
Calculation
OUT
output
D022902E.EPS
: Connection is available only when connecting to a switch block (SW-33, SW-91) or an inter-station data link block
(ADL).

■ Functions of One-Shot Block Rising-Edge Trigger (TON) and Falling-
Edge Trigger (TOFF) £
The TON and TOFF blocks perform input processing, calculation processing, output
The only processing timing available for the TON and TOFF blocks is a periodic 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.
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the TON and
TOFF blocks, see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible
for Each Calculation Block.”
● Calculation Processing of One-Shot Block Rising-Edge Trigger (TON) and

Falling-Edge Trigger (TOFF) £
The TON and TOFF blocks set the calculation output value (CPV) to 1 for the duration of
one scan using their calculation algorithms.
The calculation algorithm of One-shot blocks TON and TOFF may be illustrated as follows.
● One-Shot Block (Rising-Edge Trigger) (TON) £

When the calculation input value (RV) is changed to a value other than 0, the logic value 1
is output as calculated output value (CPV) for one scan period.
0
IN
OUT
1 Scan
One-shot
Rise trigger
D022903E.EPS
Figure One-Shot Block (Rising-Edge Trigger) (TON) £

● One-Shot Block (Falling-Edge Trigger) (TOFF) £
When the calculation input RV is changed from 1 to 0, the logic value 1 is output for one
scan period.
0
IN
OUT
1 Scan
One-shot
Fall trigger
D022904E.EPS
Figure One-Shot Block (Falling-Edge Trigger) (TOFF) £
■ Data Items – TON and TOFF £

Table Data Items of One-shot Blocks Rise Trigger (TON), Fall Trigger( TOFF) £
Entry
Permission
D022905E.EPS

SEE ALSO
For a list of valid block modes for TON and TOFF blocks, see chapter D2.3.2, “Valid Block Modes for

<Toc> <Ind> <D2.30 Relational Operation Blocks (GT, GE, EQ)> D2-133
D2.30 Relational Operation Blocks (GT, GE, EQ)

GT, GE and EQ blocks are used to compare the two calculation input values RV1 and
RV2.
■ Relational Operation Blocks (GT, GE, EQ) £

▼ Connection
GT, GE and EQ blocks are used to compare the two inputs (RV1, RV2). When the compari-
son result is True, the calculated output value (CPV) becomes 1, otherwise the output
value (CPV) is 0.
Here is a function block diagram of GT, GE and EQ.
Input
Q01 RV1
Processing
Calculation Output
CPV OUT
Input
Q02 RV2
Processing
D023001E.EPS
Figure Function Block Diagram of Relational Operation Blocks (GT, GE, EQ) £
terminals of Relational Operation Blocks (GT, GE, EQ).
Table Connection Types and Connection Destinations of the I/O Terminals of Relational
Operation Blocks (GT, GE, EQ) £
Data setting
Calculation
Q01
input 1
Calculation
Q02
input 2
Calculation
OUT
output
D023002E.EPS

■ Functions of Relational Operation Blocks (GT, GE, EQ) £
The GT, GE, and EQ blocks perform input processing, calculation processing, output
The processing timings available for the GT, GE, and EQ blocks are a periodic startup and
a one-shot startup. Selections available for the scan period used to execute a periodic
speed scan period.
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the GT, GE, and
EQ blocks, see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible
• For details on the alarm processing, see chapter C5, “Alarm Processing-FCS.“
● Calculation Processing of Relational Operation Blocks (GT, GE, EQ) £

The GT, GE, and EQ blocks compare the calculation input values (RV1, RV2) using their
calculation algorithms.
The calculation algorithm of GT, GE, EQ may be described as follows.
● Comparator Block (Greater Than) (GT) £

The calculation input values (RV1, RV2) are the floating-point numeric data, while the
calculated output value (CPV) is integer.
When RV1 > RV2, the calculated output value (CPV) becomes 1, otherwise, it is 0.
● Comparator Block (Greater Than or Equal) (GE) £

When RV1 RV2, the calculated output value (CPV) becomes 1, otherwise, it is 0.
● Equal Operator Block (EQ) £

When RV1 = RV2, the calculated output value (CPV) becomes 1, otherwise, it is 0.
When the connection destination is engineering unit data, the comparison is carried out by
floating-point numeric values.

■ Data Items – GT, GE, EQ £
Table Data Items of Relational Operation Blocks (GT, GE, EQ) £
Entry
Permission
D023003E.EPS

SEE ALSO
For a list of valid block modes for GT, GE and EQ blocks, see chapter D2.3.2, “Valid Block Modes for

<Toc> <Ind> <D2.31 Bitwise AND Block (BAND), Bitwise OR Block (BOR)> D2-136
D2.31 Bitwise AND Block (BAND), Bitwise OR Block

(BOR)
BAND block is used when the product of the calculation input values (RV1, RV2) is
calculated in bitwise.
BOR block is used when the sum of the calculation input values (RV1, RV2) is calcu-
lated in bitwise.
■ Bitwise AND Block (BAND), Bitwise OR Block (BOR) £

▼ Connection
Based on the calculation input values (RV1, RV2), BAND Block calculates the bitwise
product of the two inputs while BOR block the bitwise sum of the two inputs.
Here is a function block diagram of Bitwise AND Block (BAND) and Bitwise OR Block
(BOR).
Input
Q01 RV1
Processing
Calculation Output
CPV OUT
Input
Q02 RV2
Processing
D023101E.EPS
Figure Function Block Diagram of Bitwise AND Block (BAND) and Bitwise OR Block (BOR) £
terminals of Bitwise AND Block (BAND) and Bitwise OR Block (BOR).
Table Connection Types and Connection Destinations of the I/O Terminals of Bitwise AND Block
(BAND) and Bitwise OR Block (BOR) £
Data setting
Calculation
Q01
input 1
Calculation
Q02
input 2
Calculation
OUT
output
D023102E.EPS

■ Functions of Bitwise AND Block (BAND) and Bitwise OR Block (BOR)
£
The BAND and BOR blocks perform input processing, calculation processing, output
The processing timings available for the BAND and BOR blocks are a periodic startup and
a one-shot startup. Selections available for the scan period used to execute a periodic
speed scan period.
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the BAND and
BOR blocks, see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible
● Calculation Processing of Bitwise AND Block (BAND) and Bitwise OR

Block (BOR) £
The BAND and BOR blocks perform computation using their calculation algorithms.
The I/O data of BAND and BOR blocks are integer type.
The calculation algorithm of BAND and BOR may be described as follows.
● Bitwise AND Block (BAND) £

The bitwise product of calculation input values (RV1, RV2) is calculated.
Example
RV1 = 0xFFFF FF00, RV2 = 0x0000 0FFF

CPV = 0x0000 0F00
● Bitwise OR Block (BOR) £

The bitwise sum of calculation input values (RV1, RV2) is calculated.
Example
RV1 = 0xFFFF FF00, RV2 = 0x0000 000F

CPV = 0xFFFF FF0F

■ Data Items – BAND, BOR £
Table Data Items of Bitwise AND Block (BAND) and Bitwise OR Block (BOR) £
Entry
Permission
RV1 Calculation input value 1 8 digits, hex 0
RV2 Calculation input value 2 8 digits, hex 0
CPV Calculated output value (*1) 8 digits, hex 0
D023103E.EPS

SEE ALSO
For a list of valid block modes for BAND and BOR blocks, see chapter D2.3.2, “Valid Block Modes for

<Toc> <Ind> <D2.32 Bitwise NOT Block (BNOT)> D2-139
D2.32 Bitwise NOT Block (BNOT)

BNOT block is used when the negation of the calculation input values (RV1, RV2) is
calculated in bitwise.
■ Bitwise NOT Block (BNOT) £

▼ Connection
Based on the calculation inputs (RV), BNOT block calculates the bitwise negation of the
inputs.
Here is a function block diagram of Bitwise NOT Block (BNOT).

D023201E.EPS
Figure Function Block Diagram of Bitwise NOT Block (BNOT) £
terminals of Bitwise NOT Block (BNOT).
Table Connection Types and Connection Destinations of the I/O Terminals of Bitwise NOT Block
(BNOT) £
Data setting
Calculation
IN
input
Calculation
OUT
output
D023202E.EPS

■ Function of Bitwise NOT Block (BNOT) £
The BNOT block performs input processing, calculation processing, output processing, and
alarm processing.
The processing timings available for the BNOT block are a periodic startup and a one-shot
period.
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the BNOT block,
culation Block.”
● Calculation Processing of Bitwise NOT Block (BNOT) £

The BNOT block performs computation using its calculation algorithm.
The calculation input values (RV, CPV) of BNOT blocks is integer type.
The BNOT calculates its CPV according to the bitwise value of calculation input value (RV).
Example
RV = 0xFFFF FF00
CPV = 0x0000 00FF

■ Data Items – BNOT £
Table Data Items of Bitwise NOT Block (BNOT) £
Entry
Permission
RV Calculation input value 8 digits, hex 0
CPV Calculated output value (*1) 8 digits, hex 0
D023203E.EPS

SEE ALSO
For a list of valid block modes for BNOT block, see chapter D2.3.2, “Valid Block Modes for Each Calcula-
tion Block.”

<Toc> <Ind> <D2.33 General-Purpose Calculation Blocks (CALCU, CALCU-C)> D2-142
D2.33 General-Purpose Calculation Blocks (CALCU,

CALCU-C)
The General-Purpose Calculation Blocks (CALCU, CALCU-C) are used when defin-
ing 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).
P01 P08
IN RV CPV OUT
User-defined
Q01 RV1 CPV1 Output J01
Input arithmetic/logic
processing calculation processing
processing
Q07 RV7 CPV3 J03
(CPV, CPV)
SUB
D023301E.EPS
Figure 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 Connection Types and Connection Destinations of the I/O Terminals of
General-Purpose Calculation Block (CALCU)
I/O terminal
Data setting
Calculation
IN
input
Q01 nth
to calculation
Q07 input
Calculation
OUT
output
J01 nth
to calculation
J03 output
Auxiliary
SUB
output
D023302E.EPS
Table Connection Types and Connection Destinations of the I/O Terminals of

General-Purpose Calculation Block with String I/O (CALCU-C)
Data setting
Calculation
IN
input
Q01 nth
to calculation
Q03 input
Q04 nth
to calculation
Q07 input
Calculation
OUT
output
nth
J01 calculation
output
J02 nth
to calculation
J03 output
Auxiliary
SUB
output
D023303E.EPS

■ Functions of General-Purpose Calculation Blocks (CALCU, CALCU-C)
¡£
The CALCU and CALCU-C blocks perform input processing, calculation processing, output
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.
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the CALCU and
CALCU-C blocks, see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing
Possible for Each Calculation Block.”
● 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.
● 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.
● 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.

■ Input Processing when a Calculation Input Value Error is 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
“Calculation input value error detection” 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 [Calculation Input Value Error Detection] item.
Table Specification of Calculation Input Value Error Detection of General-Purpose Calculation

Blocks (CALCU, CALCU-C)
Error detection condition
CPV data Input value of data status
Specification RV1 to RV7 Calculation
RV status communication source
(*2) processing
BAD – – BAD RV
Correction
NR (*1) BAD Normal QST
calculation type Do not communicate.
NR (*1) NR (*1) Normal NR (*1)
BAD – – BAD The priority order is from
Detect all type – BAD – BAD RV to RVn (*3).
NR (*1) NR (*1) Normal NR (*1) Do not communicate.

Non-detection type – – Normal NR (*1) Do not communicate.
D023304E.EPS
-: Ignore (don’t care)

*1: An “NR” entry in the table indicates a condition where the data status is neither BAD nor QST.
*2: “RV1 to RV7” means the logic sum of the data statuses from RV1 to RV7.
*3: 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 and the value immediately before the error
generation is output as a calculation output value (CPV).
However, the calculation output value (CPV) is overshot at the specified value (the
CPV is set to the specified value) if CPV overshoot is used and the data status of the
calculation output value (CPV) has become a bad data value because the data status
of the calculation input value of the main input (RV) became a bad data value (BAD).
• 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.

The General-Purpose Calculation Blocks (CALCU, CALCU-C) execute algorithms that are
defined using the general-purpose calculation expression description language.
SEE ALSO
For the general-purpose calculation expression description language, refer to D2.47, “General-Purpose
Arithmetic Expressions.”
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 descrip-
tion 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
The input signals that are directly specified in the calculation expression description be-
come the target of calculation input error detection.
● 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.
• 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.
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 computa-
tion error alarm (CERR) returns to normal. The value at the error occurrence is held in
ERRL.
SEE ALSO
For details on the description of calculation errors and the calculation error handling, see chapter
D2.47.7, “Error Handling.”

■ Data Items – CALCU, CALCU-C
The table below shows the data items of the General-Purpose Calculation Block (CALCU):
Table Data Items of General-Purpose Calculation Block (CALCU)
Entry Permitted
or Not
RV1 to RV7 Calculated input value 1 to 7 ----- 0
RAW1 to RAW7 Raw input data 1 to 7 Value in the unit at the connection destination -----
SUM Totalizer value Value in the same engineering unit as CPV 0
CPV1 to CPV3 Calculated output value 1 to 3 ----- 0
P01 to P08 Calculation parameters 1 to 8 ----- 0
EERL Error statement number ----- 0
ERRC (* 2) Error code ----- 0
D023305E.EPS

*2: ERRC denotes a detailed error code and a class error code
SEE ALSO
For a list of valid block modes for CALCU block, see chapter D2.3.2, “Valid Block Modes for Each

The table below shows the data items of the General-Purpose Calculation Block with String
I/O (CALCU-C):
Table Data Items of General-Purpose Calculation Block with String I/O (CALCU-C)
Entry Permitted
or Not
RV1 to RV3 Calculated input value 1 to 3 ----- 0
RAW1 to RAW3 Raw input data 1 to 3 Value in the unit at the connection destination -----
RV4 to RV7 Calculated input value 4 to 7 16B NULL
CPV1 Calculated output value 1 16B NULL
CPV2 to CPV3 Calculated output value 2 and 3 ----- 0
P01 to P04 Calculation parameters 1 to 4 ----- 0
P05 to P08 Calculation parameters 5 to 8 16B NULL
EERL Error statement number ----- 0
ERRC (* 2) Error code ----- 0
D023306E.EPS

*2: ERRC denotes a detailed error code and a class error code
SEE ALSO
For a list of valid block modes for CALCU-C block, see chapter D2.3.2, “Valid Block Modes for Each

<Toc> <Ind> <D2.34 Three-Pole Three-Position Selector Switch Block (SW-33)> D2-150
D2.34 Three-Pole Three-Position Selector Switch

Block (SW-33)
The Three-Pole Three-Position Selector Switch Block (SW-33) is used when chang-
ing three-position signal paths.
■ Three-Pole Three-Position Selector Switch Block (SW-33)

▼ Connection
The Three-Pole Three-Position Selector Switch Block (SW-33) is a function block that
changes signal paths in accordance with the switch command sent from the operation and
monitoring functions or other function blocks. Up to three three-position switches can be
handled simultaneously by one Three-Pole Three-Position Selector Switch Block (SW-33).
Here is a function block diagram of the Three-Pole Three-Position Selector Switch Block
(SW-33).
Switch position
SW
OFF 0
S11 1
S12 2 S10
S13 3
OFF 0
S21 1
S22 2 S20
S23 3
OFF 0
S31 1
S32 2 S30
S33 3
D023501E.EPS
Figure Function Block Diagram of Three-Pole Three-Position Selector Switch Block (SW-33)

terminals of the Three-Pole Three-Position Selector Switch Block (SW-33).
Table Connection Types and Connection Destinations of the I/O Terminals of Three-Pole Three-
Position Selector Switch Block (SW-33)
Data setting
S10 I/O terminal
S11 I/O terminal
S12 I/O terminal
S13 I/O terminal
S20 I/O terminal
S21 I/O terminal
S22 I/O terminal
S23 I/O terminal
S30 I/O terminal
S31 I/O terminal
S32 I/O terminal
S33 I/O terminal
D023502E.EPS
Note: Condition check and status manipulation signals of sequence connection cannot be handled by the Three-Pole Three-
Position Selector Switch Block (SW-33). Inter-station data link cannot be performed via the block, either.
■ Function of 3-Pole 3-Position Selector Switch Block (SW-33) ¡ £

The SW-33 block performs input processing and calculation processing.
The SW-33 block does not have its own processing timing. The SW-33 block is never
subject to scans. The signal path of the SW-33 block is used at the timing when a function
block at the connection destination is executed.
SEE ALSO
• For the types of input processing possible for the SW-33 block, see chapter D2.3.1, “Input Processing,
Output Processing, and Alarm Processing Possible for Each Calculation Block.”
● Calculation Processing of 3-Pole 3-Position Selector Switch Block (SW-33)

The SW-33 block changes the 3-pole signal path via the operation and monitoring function
or other function blocks.

The Three-Pole Three-Position Selector Switch Block (SW-33) changes signal paths in
accordance with the switch command sent from the operation and monitoring functions or
other function blocks.
There is no restriction on the I/O direction of signals. S10, S20 and S30 terminals as well as
the remaining terminals can be used for input. However, as the three three-position
switches are linked with one another, each three-position switch is always connected to a
terminal at the same switch position.
■ Set Parameters
The parameters of the Three-Pole Three-Position Selector Switch Block (SW-33) are
shown as follows.
• Selector switch (SW): A numeric value between 0 and 3
• Switch high limit (SWH): A numeric value between 0 and 3
• Switch low limit (SWL): A numeric value between 0 and 3
When setting the selector switch (SW) from the operation and monitoring functions, if the
set selector switch (SW) exceeds the switch high limit (SWH) or the switch low limit (SWL),
a confirmation message appears. When the operator performs confirmation operation, the
content of the setting becomes effective.
■ Data Items – SW-33

Table Data Items of Three-Pole Three-Position Selector Switch Block (SW-33)
Entry Permitted
or Not
SW Selector switch 0 to 3 0
SWH Switch high limit 0 to 3 3
SWL Switch low limit 0 to 3 0
D023503E.EPS

<Toc> <Ind> <D2.35 One-Pole Nine-Position Selector Switch Block (SW-91)> D2-153
D2.35 One-Pole Nine-Position Selector Switch

Block (SW-91)
The 1-Pole 9-Position Selector Switch Block (SW-91) is used when changing nine-
position signal paths.
■ One-Pole Nine-Position Selector Switch Block (SW-91)

▼ Connection
The One-Pole Nine-Position Selector Switch Block (SW-91) is a function block that
changes signal paths in accordance with the switch command sent from the operation and
monitoring functions or other function blocks. Only one nine-position switch can be handled
by the One-Pole Nine-Position Selector Switch Block (SW-91).
Here is a function block diagram of the One-Pole Nine-Position Selector Switch Block (SW-
91).
OFF 0
S11 1 SW
S12 2
S13 3
S14 4
S15 5 S10
S16 6
S17 7
S18 8
S19 9
D023601E.EPS
Figure Function Block Diagram of One-Pole Nine-Position Selector Switch Block (SW-91)

terminals of the One-Pole Nine-Position Selector Switch Block (SW-91).
Table Connection Types and Connection Destinations of the I/O Terminals of One-Pole Nine-
Position Selector Switch Block (SW-91)
Data setting
S10 I/O terminal
S11 I/O terminal
S12 I/O terminal
S13 I/O terminal
S14 I/O terminal
S16 I/O terminal
S17 I/O terminal
S18 I/O terminal
S19 I/O terminal
D023602E.EPS
Note: Condition check and status manipulation signals of sequence connection cannot be handled. Inter-station data link
cannot be performed, either.
■ Function of 1-Pole 9-Position Selector Switch Block (SW-91) ¡ £

The SW-91 block performs input processing and calculation processing.
The SW-91 block does not have its own processing timing. The SW-91 block is never
subject to scans. The signal path of the SW-91 block is used at the timing when a function
block at the connection destination is executed.
SEE ALSO
• For the types of input processing possible for the SW-91 block, see chapter D2.3.1, “Input Processing,
● Calculation Processing of 1-Pole 9-Position Selector Switch Block (SW-91)

The SW-91 block changes the 9-pole signal path via the operation and monitoring function
or other function blocks.

The One-Pole Nine-Position Selector Switch Block (SW-91) changes signal paths in
accordance with the switch command sent from the operation and monitoring functions or
other function block.
There is no restriction on the I/O direction of signals for the One-Pole Nine-Position Selec-
tor Switch Block (SW-91). Terminals S10 through S19 can be used for input.
■ Set Parameters
The parameters of the One-Pole Nine-Position Selector Switch Block (SW-91) are shown
as follows.
• Switch high limit (SWH): A numeric value between 0 and 9
• Switch low limit (SWL): A numeric value between 0 and 9
When setting the selector switch (SW) from the operation and monitoring functions, if the
set selector switch (SW) exceeds the switch high limit (SWH) or the switch low limit (SWL),
a confirmation message appears. When the operator performs confirmation operation, the
content of the setting becomes effective.
■ Data Items – SW-91

Table Data Items of One-Pole Nine-Position Selector Switch Block (SW-91)
Entry Permitted
or Not
SWH Switch high limit 0 to 9 9
SWL Switch low limit 0 to 9 0
D023603E.EPS

<Toc> <Ind> <D2.36 Selector Switch Block for 16 Data (DSW-16)> D2-156
D2.36 Selector Switch Block for 16 Data (DSW-16)

The Selector Switch Block for 16 Data (DSW-16) is used when switching output
constants (numeric data) from one to the other is required.
■ Selector Switch Block for 16 Data (DSW-16)

▼ Connection
The Selector Switch Block for 16 Data (DSW-16) is a function block that outputs a constant
(numeric value data) in accordance with the switch command sent from the operation and
monitoring functions or other function blocks.
Here is a function block diagram of the Selector Switch Block for 16 Data (DSW-16).
Switch position
OFF 0
SW
Constant 1 1
Constant 2 2
CPV OUT
Constant 16 16
D023701E.EPS
Figure Function Block Diagram of Selector Switch Block for 16 Data (DSW-16)
terminals of the Selector Switch Block for 16 Data (DSW-16).
Table Connection Types and Connection Destinations of the I/O Terminals of Selector Switch
Block for 16 Data (DSW-16)
Data setting
Calculation
OUT
output
D023702E.EPS

■ Functions of Selector Switch Block for 16 Data (DSW-16) ¡ £
The DSW-16 block performs input processing, calculation processing, output processing,
The only processing timing available for the DSW-16 block is a periodic startup. Selections
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the DSW-16
● Calculation Processing of Selector Switch Block for 16 Data (DSW-16)

The DSW-16 block performs computation using its calculation algorithm and setup param-
eters.
▼ Output Velocity Limiter
The Selector Switch Block for 16 Data (DSW-16) outputs one of the values of the constants
1 through 16 in accordance with the switch command sent from the operation and monitor-
ing functions or other function blocks. The value of the constant to be output can be limited
by the output velocity limiter function.
When the selector switch (SW) is turned OFF (0), the previous value is held as the calcu-
lated output value (CPV).
The output velocity limiter value can be defined in the Function Block Detail Builder.
An allowed change per scan in the calculated output value (CPV).
The default is the scale span value.
■ Set Parameters
The parameters of the Selector Switch Block for 16 Data (DSW-16) are shown as follows.
• Constants 1 to 16 (SD01 to SD16): Engineering unit data values

■ Data Items – DSW-16
Table Data Items of Selector Switch Block for 16 Data (DSW-16)
Entry Permitted
or Not
SD01 to SD16 Constants 1 to 16 Value in the same engineering unit as CPV 0
D023703E.EPS

SEE ALSO
For a list of valid block modes for DSW-16 block, see chapter D2.3.2, “Valid Block Modes for Each

<Toc> <Ind> <D2.37 Selector Switch Block for 16 String Data (DSW-16)> D2-159
D2.37 Selector Switch Block for 16 String Data

(DSW-16C)
Selector Switch Block for 16 String Data (DSW-16C) is used when switching output-
ting constants (text string data) from one to the other.
■ Selector Switch Block for 16 String Data (DSW-16C)

▼ Connection
The Selector Switch Block for 16 String Data (DSW-16C) is a function block that outputs a
constant (string data) in accordance with the switch command sent from the operation and
monitoring functions or other function blocks.
Here is a function block diagram of the Selector Switch Block for 16 String Data (DSW-
16C).
Switch position
OFF 0
SW
Constant 1 1
Constant 2 2
CPV OUT
Constant 16 16
D023801E.EPS
Figure Function Block Diagram of Selector Switch Block for 16 String Data (DSW-16C)
terminals of the Selector Switch Block for 16 String Data (DSW-16C).
Table Connection Types and Connection Destinations of the I/O Terminals of Selector Switch
Block for 16 String Data (DSW-16C)
Data setting
Calculation
OUT
output
D023802E.EPS

■ Functions of Selector Switch Block for 16 String Data (DSW-16C) ¡ £
The DSW-16C block performs input processing, calculation processing, and alarm pro-
cessing.
The only processing timing available for the DSW-16C block is a periodic startup. Selec-
SEE ALSO
• For the types of input processing and alarm processing possible for the DSW-16C block, see chapter
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation
Block.”
● Calculation Processing of Selector Switch Block for 16 String Data

(DSW-16C)
The DSW-16C block performs computation using its calculation algorithm and setup
parameters.
The Selector Switch Block for 16 String Data (DSW-16C) executes the processing that
outputs one of the constants from data 1 to data 16 in accordance with the switch com-
mand sent from the operation and monitoring functions or other function blocks.
When the selector switch (SW) is turned OFF (0), the previous value is held in the calcu-
lated output value (CPV).
■ Set Parameters
The parameters of the Selector Switch Block for 16 String Data (DSW-16C) are shown as
follows.
• Constants 1 to 16 (SD01 to SD16):
Set string data of up to 16 standard-width characters or 8 double-width characters.

■ Data Items – DSW-16C
Table Data Items of Selector Switch Block for 16 String Data (DSW-16C)
Entry Permitted
or Not
CPV Calculated output value (*1) 16B NULL
SD01 to SD16 Constants 1 to 16 16B NULL
D023803E.EPS

SEE ALSO
For a list of valid block modes for DSW-16C block, see chapter D2.3.2, “Valid Block Modes for Each

<Toc> <Ind> <D2.38 Data Set Block (DSET)> D2-162
D2.38 Data Set Block (DSET)

The Data Set Block (DSET) is used as buffers for engineering unit data entered from
the operation and monitoring functions.
■ Data Set Block (DSET)

▼ Connection
The Data Set Block (DSET) is a function block that outputs the engineering unit data
entered from the operation and monitoring functions.
Here is a function block diagram of Data Set Block (DSET).
SV Velocity limiter OUT
D023901E.EPS
Figure Function Block Diagram of Data Set Block (DSET)
terminals of Data Set Block (DSET).
Table Connection Types and Connection Destinations of the I/O Terminals of Data Set Block
(DSET)
Data setting
Setting
OUT
output
D023902E.EPS
■ Functions of Data Set Block (DSET) ¡ £

The DSET block performs input processing, calculation processing, output processing, and
alarm processing.
The only processing timing available for the DSET block is a periodic startup. Selections
*1: ¡ £The medium-speed scan period can only be used for the KFCS2, KFCS, LFCS2 and LFCS.
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the DSET block, see
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block.”
● Calculation Processing of Data Set Block (DSET)

The DSET block outputs arbitrary engineering unit data that is input via the operation and
monitoring function using its calculation algorithm and setup parameters.

<Toc> <Ind> <D2.38 Data Set Block (DSET)> D2-163
The Data Set Block (DSET) outputs the data setpoint (SV) entered via key operation from
the operation and monitoring functions. The output is restricted by velocity limiting process-
ing.
The output velocity limiter value is set on the Function Block Detail Builder.
The allowed change per scan in the calculated output value (CPV).
The default is the scale span value.
■ Set Parameters
The parameters of Data Set Block (DSET) are shown as follows.
• Data setpoint (SV): An engineering unit data value
• Data setpoint high limit (SVH): An engineering unit data value
• Data setpoint low limit (SVL): An engineering unit data value
When setting the data setpoint (SV) from the operation and monitoring functions, if the set
data setpoint (SV) exceeds the data setpoint high or low limit (SVH, SVL), a confirmation
message appears, the content of the setting becomes effective when the operator performs
confirmation operation.
■ Data Items – DSET

Table Data Items of Data Set Block (DSET)
Entry Permitted
or Not
SV Data setpoint SV engineering unit value SL
SVH Data high - limit setpoint Value in the same engineering unit as SV SH
SVL Data high - low setpoint Value in the same engineering unit as SV SL
SH CPV scale high limit Value in the same engineering unit as SV -----
SL CPV scale low limit Value in the same engineering unit as SV -----
D023903E.EPS

SEE ALSO
For a list of valid block modes for DSET block, see chapter D2.3.2, “Valid Block Modes for Each Calcula-
tion Block.”

<Toc> <Ind> <D2.39 Data Set Block with Input Indicator (DSET-PVI)> D2-164
D2.39 Data Set Block with Input Indicator

(DSET-PVI)
Data Set Block with Input Indicator (DSET-PVI) is used when the function of the data
set block (DSET) and Input Indicator Block (PVI) applied to regulatory control are
required simultaneously.
■ Data Set Block with Input Indicator (DSET-PVI)

▼ Connection
The Data Set Block with Input Indicator (DSET-PVI) is a function block that has the function
of the Data Set Block (DSET) as well as that of the Input Indicator Block (PVI) used for
regulatory control.
This block performs the following two different processing simultaneously:
• Outputs arbitrary engineering unit data entered from the operation and monitoring
functions.
• Indicate input signals sent from Process I/O and other function blocks.
Here is a function block diagram of the Data Set Block with Input Indicator (DSET-PVI).
Input Velocity
IN CPV SV OUT
processing limiter
(CPV, CPV, SV, SV)
SUB
D024001E.EPS
Figure Function Block Diagram of Data Set Block with Input Indicator (DSET-PVI)
terminals of Data Set Block with Input Indicator (DSET-PVI).
Table Connection Types and Connection Destinations of the I/O Terminals of Data Set Block with
Input Indicator (DSET-PVI)
Data setting
Calculation
IN
input
Calculation
OUT
output
Auxiliary
SUB
output
D024002E.EPS

■ Functions of Data Set Block with Input Indicator (DSET-PVI) ¡ £
The DSET-PVI block performs input processing, calculation processing, output processing,
The only processing timing available for the DSET-PVI block is a periodic startup. Selec-
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the DSET-PVI
● Calculation Processing of Data Set Block with Input Indicator (DSET-PVI)

The DSET-PVI block performs computation using its calculation algorithm and setup
parameters.
The data setpoint (SV) set by the operation and monitoring functions is output under the
restriction of velocity limiting processing.
The value input from the IN terminal is converted to the calculated output value (CPV) and
displayed.
The output velocity limiter value is defined in the Function Block Detail Builder.
The allowed change per scan in the calculated output value (CPV).
The default is the scale span value
■ Set Parameters
The parameters of the Data Set Block with Input Indicator (DSET-PVI) are shown as follows.
• High-high limit alarm setpoint (HH): An engineering unit data value.
• Low-low limit alarm setpoint (LL): An engineering unit data value.
• High-limit alarm setpoint (PH): An engineering unit data value.
• Low-limit alarm setpoint (PL): An engineering unit data value.
• Velocity limit alarm setpoint (VL):
An engineering unit data value within the span of 0 to CPV.
• Data setpoint (SV): An engineering unit data value.
• Data setpoint high limit (SVH): An engineering unit data value.
• Data setpoint low limit (SVL): An engineering unit data value.

When setting the data setpoint (SV) from the operation and monitoring functions, if the set
data setpoint (SV) exceeds the data setpoint high or low limit (SVH, SVL), a confirmation
message appears, the content of the setting becomes effective when the operator performs
confirmation operation.
■ Data Items – DSET-PVI

Table Data Items of Data Set Block with Input Indicator (DSET-PVI)
Entry Permitted
or Not
CPV Calculated input value (*1) Value in the same engineering unit as CPV SL
SV Data setpoint Real quantity SL
SVH Data high - limit setpoint Real quantity SH
SVL Data low - limit setpoint Real quantity SL
HH High - high limit alarm setpoint Value in the same engineering unit as CPV SH
LL Low - low limit alarm setpoint Value in the same engineering unit as CPV SL
PH High - limit alarm setpoint Value in the same engineering unit as CPV SH
PL Low - limit alarm setpoint Value in the same engineering unit as CPV SL
VL Velocity limit alarm setpoint 0 to CPV span (SH - SL)
D024003E.EPS

SEE ALSO
For a list of valid block modes for DSET-PVI block, see chapter D2.3.2, “Valid Block Modes for Each

<Toc> <Ind> <D2.40 One-Batch Data Set Block (BDSET-1L)> D2-167
D2.40 One-Batch Data Set Block (BDSET-1L)

The One-Batch Data Set Block (BDSET-1L) is used to set numeric batch set data for
a single batch in a group or by selecting items.
■ One-Batch Data Set Block (BDSET-1L)

▼ Connection
The One-Batch Data Set Block (BDSET-1L) is a function block that selects and outputs
arbitrary numeric batch set data using a command switch (SW).
By using the command switch (SW), various setpoint values and control parameters for the
feedback control loop in the batch control loop, as well as setpoint values of the timer and
counter used for sequence control can be set.
In the One-Batch Data Set Block (BDSET-1L), the batch data including numeric data only
can be stored up to 16 batch data.
Here is a function block diagram of the One-Batch Data Set Block (BDSET-1L).
Batch data 1 J01
Batch data 2 J02
Batch data 3 J03
Batch data 16 J16
Command switch SW
D024101E.EPS
Figure Function Block Diagram of One-Batch Data Set Block (BDSET-1L)
The following table shows the connection types and connection destinations of the One-
Batch Data Set Block (BDSET-1L).
Table Connection Types and Connection Destinations of the I/O Terminals of One-Batch Data Set
Block (BDSET-1L)
Calculation
J01 to J16
output
D024102E.EPS

■ Functions of 1-Batch Data Set Block (BDSET-1L) ¡ £
The BDSET-1L block performs calculation processing and alarm processing.
The processing timings available for the BDSET-1L block 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.
SEE ALSO
• For the types of alarm processing possible for the BDSET-1L block, see chapter D2.3.1, “Input Process-
ing, Output Processing, and Alarm Processing Possible for Each Calculation Block.”
● Calculation Processing of 1-Batch Data Set Block (BDSET-1L)

The BDSET-1L block performs calculation processing based on the action of the command
switch (SW). In addition, it has the "setpoint value limiter function," which is related to the
calculation processing.
■ Action of the Command Switch (SW)

The One-Batch Data Set Block (BDSET-1L) performs the following processing in accor-
dance with the value of the command switch (SW).
Table Processing Contents of One-Batch Data Set Block (BDSET-1L)
Operation example
SW Status
Processing content Operation source
(1) Sets batch data. Operation and monitoring
0 Setting up data
(2) Switches the SW from “0” to “1.” functions
(1) Waits for the completion of setup.
1 Waiting for the batch sequence Sequence control block
(2) Switches the SW from “1” to “2.”
(1) Distributes data to the output destinations.
2 Distributing data to the output destinations BDSET-1L block
(2) Switches the SW from “2” to “3.” (*1)
(1) Waits for the completion of batch operation.
3 Operating the batch sequence Sequence control block
D024103E.EPS
*1: Switching of the switch position from “2” to “3” is performed automatically by the BDSET-1L block.

■ Action during Status Manipulation via Sequence Connection
When a status manipulation signal is received from other function block connected via
sequence connection, data setting is performed. However, the value of the manipulation
switch (SW) will not change.
The formats of the status manipulation command sent from other function block and the
content of the corresponding processing performed by the One-Batch Data Set Block
(BDSET-1L) are shown below.
Element symbol.ACT.n
n = 0: All batch data (DT01 to DT16) are changed to “0.”

n = 1 to 16: The specified data (DTnn) is set to the output destination.
n = 17: All batch data (DT01 to DT16) are set to all output destinations.
■ Set Limit Function

The set limit function is a function that limits the value of the batch data (DTnn) set from
outside to values within a specified range (between high/low limits).
If the set value is outside the high/low limit range, a setting error occurs.
The high limit value (DHnn) and low limit value (DLnn) represent the high limit and low limit of
Set data, respectively. The high limit value (DHnn) and low limit value (DLnn) must be consis-
tent with the range of the output destination.
The set limit function only checks the data set via the operation and monitoring functions.
Data set from other function blocks are not checked.
Setting to the output destination is performed even when batch data (DTnn) exceed the
specified limits.
■ Set Parameters
The parameters of the One-Batch Data Set Block (BDSET-1L) are shown as follows.
• Batch data (DT01 to DT16):
Engineering unit data values at output destinations
• Command switch (SW):
A value between 0 and 3
• Set limit high limit (DH01 to DH16):
• Set limit low limit (DL01 to DL16):

■ Data Items – BDSET-1L
Table Data Items of One-Batch Data Set Block (BDSET-1L)
Entry Permitted
or Not
SW Command switch 0 to 3 0
DT01 to DT16 Batch data DLnn to DHnn 0
DH01 to DH16 Set limit high limit Value in the unit at the connection destination 10000
DL01 to DL16 Set limit low limit Value in the unit at the connection destination 0
D024104E.EPS

SEE ALSO
For a list of valid block modes for BDSET-1L block, see chapter D2.3.2, “Valid Block Modes for Each

<Toc> <Ind> <D2.41 One-Batch String Data Set Block (BDSET-1C)> D2-171
D2.41 One-Batch String Data Set Block (BDSET-1C)

The One-Batch String Data Set Block (BDSET-1C) is used to set string-type batch set
data for a single batch are set in a group or by selecting items.
■ One-Batch String Data Set Block (BDSET-1C)

▼ Connection
The One-Batch String Data Set Block (BDSET-1C) is a function block that selects and
outputs arbitrary string-type batch set data using a command switch (SW).
The One-Batch String Data Set Block (BDSET-1C) can store up to 16 batch data, each
containing only string data.
Here is a function block diagram of One-Batch String Data Set Block (BDSET-1C).
Batch data 1 J01
Batch data 2 J02
Batch data 3 J03
Batch data 16 J16
Command switch SW
D024201E.EPS
Figure Function Block Diagram of One-Batch String Data Set Block (BDSET-1C)
The following table shows the connection types and connection destinations of the One-
Batch String Data Set Block (BDSET-1C).
Table Connection Types and Connection Destinations of the I/O Terminals of One-Batch String
Data Set Block (BDSET-1C)
Calculation
J01 to J16
output
D024202E.EPS

■ Functions of One-Batch String Data Set Block (BDSET-1C) ¡ £
The BDSET-1C block performs calculation processing and alarm processing.
The processing timings available for the BDSET-1C block are a periodic startup and a one-
scan period.
SEE ALSO
• For the types of alarm processing possible for the BDSET-1C block, see chapter D2.3.1, “Input Process-
● Calculation Processing of One-Batch String Data Set Block (BDSET-1C)

The BDSET-1C block performs calculation processing based on the action of the command
switch (SW).

The One-Batch String Data Set Block (BDSET-1C) performs the following processing in
accordance with the value of the command switch (SW).
Table Processing Contents of One-Batch String Data Set Block (BDSET-1C)
Operation example
SW Status
(1) Sets batch data. Operation and monitoring
0 Setting up data
(2) Switches the SW from “0” to “1.” functions
(1) Waits for the completion of setup.
1 Waiting for the batch sequence Sequence control block
(1) Distributes data to the output destinations.
2 Distributing data to the output destinations BDSET-1C
(2) Switches the SW from “2” to “3.” (*1)
(1) Waits for the completion of batch.
3 Operating the batch sequence Sequence control block
D024203E.EPS
*1: Switching of the switch position from “2” to “3” is performed automatically by the One-Batch String Data Set Block
(BDSET-1C).

Data setting is performed when a status manipulation signal is received from other function
block connected via sequence connection. However, the value of the command switch
(SW) will not change.
The format of the status manipulation command sent from other function block and the
content of the processing performed by the One-Batch String Data Set Block (BDSET-1C)
are shown below.
n = 0: All batch data (DT01 to DT16) are replaced with null.

n = 1 to 16: The specified data (DTnn) is set to the output destination.
n = 17: All batch data (DT01 to DT16) are set to all output destinations.
■ Set Parameters
The parameters of the One-Batch String Data Set Block (BDSET-1C) are shown as follows.
• Batch data (DT01 to DT16):
• Command switch (SW): A numeric value between 0 and 3.
■ Data Items – BDSET-1C

Table Data Items of One-Batch String Data Set Block (BDSET-1C)
Entry Permitted
or Not
DT01 to DT16 Batch data 16B -----
D024204E.EPS

SEE ALSO
For a list of valid block modes for BDSET-1C block, see chapter D2.3.2, “Valid Block Modes for Each

<Toc> <Ind> <D2.42 Two-Batch Data Set Block (BDSET-2L)> D2-174
D2.42 Two-Batch Data Set Block (BDSET-2L)

The Two-Batch Data Set Block (BDSET-2L) is used to set numeric-type batch data for
two batches in a group or by selecting specific items.
■ Two-Batch Data Set Block (BDSET-2L)

▼ Connection
The Two-Batch Data Set Block (BDSET-2L) is a function block that selects and outputs
arbitrary batch set data using a command switch (SW).
Various setpoint values and control parameters of the feedback control loop, as well as
setpoint values of the time and counter used for sequence control can be set.
Up to 16 current batch data and up to 16 next batch data can be stored. By switching the
value of the command switch (SW), the stored next batch data can be moved to the current
batch data, or the current batch data can be set to the output destination. The Two-Batch
Data Set Block (BDSET-2L) can only set numeric data.
Here is a function block diagram of the Two-Batch Data Set Block (BDSET-2L).
Next batch data 1 Current batch data 1 J01
SW Command switch
D024301E.EPS
Figure Function Block Diagram of Two-Batch Data Set Block (BDSET-2L)
The following table shows the connection types and connection destinations of the Two-
Batch Data Set Block (BDSET-2L).
Table Connection Types and Connection Destinations of I/O Terminals of Two-Batch Data Set
Block (BDSET-2L)
Calculation
J01 to J16
output
D024302E.EPS

■ Functions of Two-Batch Data Set Block (BDSET-2L) ¡ £
The BDSET-2L block performs calculation processing and alarm processing.
The processing timings available for the BDSET-2L block are a periodic startup and a one-
scan period.
SEE ALSO
• For the types of alarm processing possible for the BDSET-2L block, see chapter D2.3.1, “Input Process-
● Calculation Processing of Two-Batch Data Set Block (BDSET-2L)

The BDSET-2L block performs calculation processing based on the action of the command
switch (SW) and batch status (NXBS). In addition, it has the “setpoint value limiter func-
tion,” which is related to the calculation processing.

■ Action of the Command Switch (SW) and Batch Status (NXBS)
The Two-Batch Data Set Block (BDSET-2L) performs the processing shown in the table
below, in accordance with the value of the command switch (SW).
The batch status (NXBS) indicates the status of the next batch data. When the value of the
batch status (NXBS) is other than “0,” it indicates that the setting of the next batch data
(NX01 to NX16) has been completed and the current batch data is ready for transfer. If the
value of the batch status (NXBS) is “0,” it indicates that the next batch data is not yet ready
to be transferred to the current batch data.
If the batch status (NXBS) is left at “0,” the Two-Batch Data Set Block (BDSET-2L) ignores
the next batch data. While the batch status (NXBS) remains “0,” the Two-Batch Data Set
Block (BDSET-2L) can be used temporarily as the One-Batch Data Set Block (BDSET-1L).
Table Processing Contents of Two-Batch Data Set Block (BDSET-2L)
Operation example
SW Status Operation from HIS
Transferring the (1) Moves the next data to the current data.
0 next data to the (2) Switches the SW from “0” to “1.” BDSET-2L (*1)
current data (3) Sets NXBS to “0.”
Waiting for the (1) Waits for the setup to be completed. Sequence control
1 (2) Switches the SW from “1” to “2.”
batch sequence block (1) Set the next batch data from
an operation and monitoring
(1) Distributes the current data to the output
Distributing the functions, when SW is “1,” “2,”
2 destinations. BDSET-2C
current data or “3.”
(2) Switches SW from “2” to “3.”
(2) Set a value other than “0” to
Operating the batch (1) Waits for the completion of batch. Sequence control NXBS.
3
sequence (2) Switches SW from “3” to “0.” block
D024303E.EPS
*1: The Two-Batch Data Set Block (BDSET-2L) transfers the next data to the current data when the command switch (SW)
becomes “0” and the value of the batch status (NXBS) becomes other than “0.” If the command switch (SW) changes
to “0” when the next batch data is yet to be set at the operation and monitoring functions, the Two-Batch Data Set Block
(BDSET-2L) waits for the value of the batch status (NXBS) to become other than “0.” When a value other than “0” is set
to the batch status (NXBS) after the next data has been set at the operation and monitoring functions, the Two-Batch
Data Set Block (BDSET-2L) moves the next data to the current data, then sets the value of the command switch (SW)
to “1” to wait for the batch sequence.

block connected via sequence connection. However, the value of the command switch
The format of the status manipulation command outputted from other function block and
the content of the processing performed by the Two-Batch Data Set Block (BDSET-2L) are
shown below.
n = 0: All current set data are changed to “0.”

n = 1 to 16: Only the specified current data (DTnn) is set.
n = 17: All current set data are set.

The set limit function is a function that limits the value of the current batch data (DTnn) and
next batch data (NXnn), both of which are set from outside, within a specified range (be-
tween high/low limits).
If the set value is outside the high/low limit range, a setting error occurs.
The high and low limit values (DHnn, DLnn) represent the high limit and low limit of set data,
respectively. The high and low limit values (DHnn, DLnn) must be consistent with the range of
the output destination.
Setting to the output destination is even allowed with the batch data (DTnn) exceeding the
specified limits.
■ Set Parameters
The parameters of the Two-Batch Data Set Block (BDSET-2L) are shown as follows.
• Current batch data (DT01 to DT16): Engineering unit data values of output destina-
tions.
Arbitrary values can be selected and set as long as they can be indicated in the
double-precision floating format. Whether the value is within the range of the output
destination is not checked during setting.
• Next batch data (NX01 to NX16): Engineering unit data values of output destinations.
Arbitrary values can be selected and set as long as they can be indicated in the
double-precision floating format. Whether the value is within the range of the output
destination is not checked during setting.
• Command switch (SW): A numeric value between 0 and 3.
• Batch status (NXBS):
An integer value other than “0” set from the operation and monitoring functions.
Automatically changes to “0” when batch data setting action is performed.
• Set limit high (DH01 to DH16): Engineering unit data values of output destinations.
• Set limit low (DL01 to DL16): Engineering unit data values of output destinations.

■ Data Items – BDSET-2L
Table Data Items of Two-Batch Data Set Block (BDSET-2L)
Entry Permitted
or Not
NXBS Batch status Integer of 0 or higher 0
DT01 to DT16 Current batch data DLnn to DHnn 0
NX01 to NX16 Next batch data DLnn to DHnn 0
D024304E.EPS

SEE ALSO
For a list of valid block modes for BDSET-2L block, see chapter D2.3.2, “Valid Block Modes for Each

<Toc> <Ind> <D2.43 Two-Batch String Data Set Block (BDSET-2C)> D2-179
D2.43 Two-Batch String Data Set Block (BDSET-2C)

The Two-Batch String Data Set Block (BDSET-2C) is used to set string batch data for
two batches in a group or by selecting items.
■ Two-Batch String Data Set Block (BDSET-2C)

▼ Connection
The Two-Batch String Data Set Block (BDSET-2C) is a function block that selects and
outputs arbitrary batch set data using a command switch (SW).
Up to 16 batch data can be stored for current output and for next output, respectively.
By changing the value of the command switch (SW), the stored next batch data can be
moved to the current batch data, or the current batch data can be set to the output destina-
tion. The Two-Batch String Data Set Block (BDSET-2C) can only set string data.
Here is a function block diagram of the Two-Batch String Data Set Block (BDSET-2C).
SW Command switch
D024401E.EPS
Figure Function Block Diagram of Two-Batch String Data Set Block (BDSET-2C)
The following table shows the connection types and connection destinations of the Two-
Batch String Data Set Block (BDSET-2C).
Table Connection Types and Connection Destinations of I/O Terminals of Two-Batch String Data
Set Block (BDSET-2C)
Calculation
J01 to J16
output
D024402E.EPS

■ Functions of Two-Batch Data Set Block: Strings (BDSET-2C) ¡ £
The BDSET-2C block performs calculation processing and alarm processing.
The processing timings available for the BDSET-2C block are a periodic startup and a one-
scan period.
SEE ALSO
• For the types of alarm processing possible for the BDSET-2C block, see chapter D2.3.1, “Input Process-
● Calculation Processing of Two-Batch Data Set Block: Strings (BDSET-2C)

The BDSET-2C block performs calculation processing based on the action of the command
switch (SW) and batch status (NXBS).

■ Action of the Command Switch (SW) and Batch Status (NXBS)
The Two-Batch String Data Set Block (BDSET-2C) performs the processing shown in the
table below, in accordance with the value of the command switch (SW).
The batch status (NXBS) indicates the status of the next batch data. When the value of the
batch status (NXBS) is other than “0, “ it indicates that the setting of the next batch data
(NX01 to NX16) has been completed and the current batch data is ready for transfer. If the
value of the batch status (NXBS) is “0,” it indicates that the next batch data is not yet ready
to be transferred to the current batch data.
If the batch status (NXBS) is left at “0,” the Two-Batch String Data Set Block (BDSET-2C)
ignores the next batch data. While the batch status (NXBS) remains “0,” the Two-Batch
String Data Set Block (BDSET-2C) can be used temporarily as the One-Batch String Data
Set Block (BDSET-1C).
Table Processing Contents of Two-Batch String Data Set Block (BDSET-2C)
Operation example
SW Status Operation from HIS
Transferring the (1) Moves the next data to the current data.
BDSET-2L
0 next data to the (2) Switches the SW from “0” to “1.” (*1)
block
current data (3) Sets NXBS to “0.”
Waiting for the (1) Waits for the setup to be completed. Sequence control
1
batch sequence (2) Switches the SW from “1” to “2.” block (1) Set the next batch data from
an operation and monitoring
(1) Distributes the current data to the output
Distributing the BDSET-2C functions, when SW is “1,” “2,”
2 destinations.
current data block or “3.”
(2) Switches SW from “2” to “3.”
(2) Set a value other than “0” to
Operating the batch (1) Waits for the completion of batch. Sequence control NXBS.
3
sequence (2) Switches SW from “3” to “0.” block
D034403E.EPS
*1: The Two-Batch String Data Set Block (BDSET-2C) transfers the next data to the current data when the command
switch (SW) becomes “0” and the value of the batch status (NXBS) becomes other than “0.” If the command switch
(SW) changes to “0” when the next batch data has yet to be set at the operation and monitoring functions, the Two-
Batch String Data Set Block (BDSET-2C) waits for the value of the batch status (NXBS) to become anything other than
“0.” When a value other than “0” is set to the batch status (NXBS) after the next data has been set at the operation and
monitoring functions, the Two-Batch String Data Set Block (BDSET-2C) moves the next data to the current data, then
sets the value of the command switch (SW) to “1” to resume the batch sequence.

block connected via sequence connection. However, the value of the manipulation switch
The format of the status manipulation command outputted from other function blocks and
the content of the processing performed by the Two-Batch String Data Set Block (BDSET-
2C) are shown below.
n = 0: All current set data are replaced with a null.

n = 1 to 16: Only the specified current data (DTnn) is set.
n = 17: All current set data are set.
■ Set Parameters
The parameters of the Two-Batch String Data Set Block (BDSET-2C) are shown as follows.
• Current batch data (DT01 to DT16):
• Next batch data (NX01 to NX16):
• Command switch (SW):
• Batch status (NXBS):
An integer value other than “0” set from the operation and monitoring functions.
Automatically changes to “0” when batch data setting action has been performed.

■ Data Items – BDSET-2C
Table Data Items of Two-Batch String Data Set Block (BDSET-2C)
Entry Permitted
or Not
NXBS Batch status Integer of 0 or higher 0
DT01 to DT16 Current batch data 16B -----
NX01 to NX16 Next batch data 16B -----
D024404E.EPS

SEE ALSO
For a list of valid block modes for BDSET-2C block, see chapter D2.3.2, “Valid Block Modes for Each

<Toc> <Ind> <D2.44 Batch Data Acquisition Block (BDA-L)> D2-184
D2.44 Batch Data Acquisition Block (BDA-L)

The Batch Data Acquisition Block (BDA-L) is used to acquire numeric batch data.
■ Batch Data Acquisition Block (BDA-L)

▼ Connection
The Batch Data Acquisition Block (BDA-L) is a function block that acquires various control
parameters of the feedback control loop as well as data of the timer and counter used for
sequence control, as batch data. The Batch Data Acquisition Block (BDA-L) only acquires
numeric batch data.
Here is a function block diagram of the Batch Data Acquisition Block (BDA-L).
Acquired data 1 J01
Acquired data 2 J02
Acquired data 3 J03
Acquired data 16 J16
Command switch SW
D024501E.EPS
Figure Function Block Diagram of Batch Data Acquisition Block (BDA-L)
The following table shows the connection types and connection destinations of the Batch
Data Acquisition Block (BDA-L).
Table Connection Types and Connection Destinations of I/O Terminals of Batch Data Acquisition
Block (BDA-L)
Calculation
J01 to J16
output
D024502E.EPS

■ Functions of Batch Data Acquisition Block (BDA-L) ¡ £
The BDA-L block performs calculation processing and alarm processing.
The processing timings available for the BDA-L block are a periodic startup and a one-shot
period.
SEE ALSO
• For the types of alarm processing possible for the BDA-L block, see chapter D2.3.1, “Input Processing,
● Calculation Processing of Batch Data Acquisition Block (BDA-L)

The BDA-L block performs calculation processing based on the action of the command
switch (SW). In addition, it has the “setpoint value limiter function,” which is related to the
calculation processing.

The Batch Data Acquisition Block (BDA-L) acquires engineering unit data from the connec-
tion destinations of I/O terminals, when a value is set to the command switch (SW).
Data acquisition processing actions are shown below:
• When a value between 1 and 16 is set to the command switch (SW)
Acquire data from the I/O terminal (J01 to J16) which corresponds to the value of the
manipulation switch (SW), and changes the value of the command switch (SW) to “0.”
• When “17” is set to the command switch (SW)
Acquire data from all input terminals, and changes the value of the command switch
(SW) to “0.”
Data acquisition is not performed.
■ Set Parameter
The parameters of the Batch Data Acquisition Block (BDA-L) are shown as follows.
• Command switch (SW): An integer value between 0 and 17

Data acquisition is performed when a status manipulation signal is received from other
function block connected via sequence connection. However, the value of the command
The format of the status manipulation command output from other function block and the
content of the processing performed by the Batch Data Acquisition Block (BDA-L) are
shown below.
n = 0: All acquired data are changed to “0.”

n = 1 to 16: Only the specified data (DTnn) is acquired.
n = 17: All data are acquired.

The set limit function is a function that limits the value of the batch data (DTnn), which is set
from outside of the Batch Data Acquisition Block (BDA-L), within a specified range between
high and low limits.
If the set data value is outside the high/low limit range, a setting error occurs.
The high limit value (DHnn) and low limit value (DLnn) represent the high limit and low limit of
set data, respectively.
Therefore, as long as the data acquired by the Batch Data Acquisition Block (BDA-L) has
been received from the input source through normal batch data acquisition, each value is
stored in the batch data (DTnn) as is even if the limits are exceeded.

■ Data Items – BDA-L
Table Data Items of Batch Data Acquisition Block (BDA-L)
Entry Permitted
or Not
DT01 to DT16 Acquired data DLnn to DHnn 0
D024503E.EPS

SEE ALSO
For a list of valid block modes for BDA-L block, see chapter D2.3.2, “Valid Block Modes for Each Calcula-
tion Block.”

<Toc> <Ind> <D2.45 Batch String Data Acquisition Block (BDA-C)> D2-188
D2.45 Batch String Data Acquisition Block

(BDA-C)
The Batch String Data Acquisition Block (BDA-C) is to acquire string-type batch
data.
■ Batch String Data Acquisition Block (BDA-C)

▼ Connection
The Batch String Data Acquisition Block (BDA-C) is a function block that acquires string-
type batch data. The Batch String Data Acquisition Block (BDA-C) only acquires string-type
batch data.
Here is a function block diagram of the Batch String Data Acquisition Block (BDA-C).
Acquired data 1 J01
Acquired data 2 J02
Acquired data 3 J03
Acquired data 16 J16
Command switch SW
D024601E.EPS
Figure Function Block Diagram of Batch String Data Acquisition Block (BDA-C)
The following table shows the connection types and connection destinations of the Batch
String Data Acquisition Block (BDA-C).
Table Connection Types and Connection Destinations of I/O Terminals of Batch String Data
Acquisition Block (BDA-C)
Calculation
J01 to J16
output
D024602E.EPS

■ Functions of Batch String Data Acquisition Block (BDA-C) ¡ £
The BDA-C block performs calculation processing and alarm processing.
The processing timings available for the BDA-C block 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.
SEE ALSO
• For the types of alarm processing possible for the BDA-C block, see chapter D2.3.1, “Input Processing,
● Calculation Processing of Batch String Data Acquisition Block (BDA-C)

The BDA-C block performs calculation processing based on the action of the command
switch (SW).

The Batch String Data Acquisition Block (BDA-C) acquires string data from the connection
destinations of I/O terminals, when a value is set to the command switch (SW).
Data acquisition processing actions are shown below:
• When a value between 1 and 16 is set to the command switch (SW)
Acquire data from the I/O terminal (J01 to J16) which corresponds to the value of the
manipulation switch (SW), and changes the value of the command switch (SW) to “0.”
Acquire data from all input terminals, and changes the value of the command switch
(SW) to “0.”
Data acquisition is not performed.
■ Action by Other Function Block Connected via Sequence Connection

Data acquisition is performed when a status manipulation signal is received from other
function block connected by sequence connection. However, the value of the command
The format of the status manipulation command outputted from other function blocks and
the content of the processing performed by the Batch String Data Acquisition Block (BDA-
C) are shown below.
n = 0: All acquired data are replaced with null.

n = 1 to 16: Only the specified data (DTnn) is acquired.
n = 17: All data are acquired.

■ Set Parameter
The set parameters of the Batch String Data Acquisition Block (BDA-C) are shown as
follows.
• Command switch (SW): An integer value between 0 and 17.
■ Data Items – Batch String Data Acquisition Block (BDA-C)

Table Data Items of Batch String Data Acquisition Block (BDA-C)
Entry Permitted
or Not
DT01 to DT16 Acquired data 16B -----
D024603E.EPS

SEE ALSO
For a list of valid block modes for BDA-C block, see chapter D2.3.2, “Valid Block Modes for Each Calcula-
tion Block.”

<Toc> <Ind> <D2.46 Inter-Station Data Link Block (ADL)> D2-191
D2.46 Inter-Station Data Link Block (ADL)

The Inter-Station Data Link Block (ADL) is used for referencing data or relaying set
data between function blocks that belong to different FCS. This function block is
automatically created when inter-station data link is specified.
■ Inter-Station Data Link Block (ADL)

The Inter-Station Data Link (ADL) is a function block that relays reference data or set data
between function blocks that belong to different FCS.
In addition to simple data reference and data setting, this block can be used for cascade
connection between controller function blocks.
Here is a function block diagram of the Inter-Station Data Link Block (ADL).
Reference data 1
SET1
Set data 1
Reference data 2
SET2
Function block
Set data 2
of other control station
Reference data 8
SET8
Set data 8
D024701E.EPS
Figure Function Block Diagram of Inter-Station Data Link Block (ADL)

Even in the case of connection between function blocks that belong to different FCS, if a
connection is specified using the same method for connecting function blocks belonging to
the same FCS, the Inter-Station Data Link Block (ADL) is automatically created and in-
serted between the function blocks specified for the connection. The Inter-Station Data Link
Block (ADL) is created on the FCS with the function block that is the source of reference or
setting.
However, the Inter-Station Data Link Block (ADL) will not be created if any of the following
connection methods is used:
• Sequence connection (condition testing, status manipulation)
• Referencing from or setting to a process I/O and word data of a communication I/O
other than contact I/Os
• Terminal connection to a switch block (SW-33, SW-91)
• Data link from the connection terminal which corresponds to the block mode or status
of a faceplate block
• Connection to an alarm input terminal of a Representative Alarm Block (ALM-R)
• Setting character string data (Character string data may be referenced.)
• Connecting with OUT terminal of Foundation Fieldbus Faceplate Block.
TIP
After downloading the engineering data in which portions not relating to the Inter-Station Data Link Block
(ADL) have been modified by a builder, a difference may be detected, indicating that some changes have
occurred to the Inter-Station Data Link Block (ADL). This difference is generated because the inter-station
data link is recreated dynamically.
Function blocks in the control stations belonging to different projects can be connected in
the same way as for inter-station connection in the same project by using a multiple-project
tag name for the tag name of that function block. However, the HIS must be installed with
the Multiple-Project connection packages.
Multiple-project tag names are specified in the following format:
tag name@project ID
Project ID can be defined on the Multiple-Project Connection builder for the upper level
project. The project ID can not be more than two alphanumeric characters. The maximum
number of characters that can be used for the entire multiple-project tag name is 16,
including the @ mark and the project ID.
An example of inter-station connection using Multiple-Project tags is illustrated as follows.
Project ID = P1 Project ID = P2
TIC101 OUT
FIC001@P2.SET TIC101@P1.OUT
PID
SET
FIC001
PID
TI102 IN TI002
TI102@P1.PV
PVI PVI
D024702E.EPS
Figure Example of Inter-Station Connection Using Multiple-Project Tag Names

■ Control Action
Three types of processing are available with the Inter-Station Data Link Block (ADL): “data
reference only,” “data setting only” and “data reference and setting.”
Which processing is performed is determined automatically in accordance with the data
that has been linked when I/O connection was specified in the Function Block Detail
Builder. The processing types and corresponding I/O connections are shown below.
Processing type: I/O connection
Data reference: Data reference connection
Data reference and setting: Data setting connection, cascade connection
Data setting: Data setting connection from a specific function block
The cycle of periodic communication processing (processing timing) performed by the

Inter-Station Data Link Block (ADL) is specified by the FCS Constants Builder for each FCS
to which the Inter-Station Data Link Block (ADL) belongs.
When the communication error occurs, NCOM (communication failure) is transmitted as
the data status to the function blocks or the data buffers connect to it.
Communication failure alarm is initiated only when the communication error occurred for a
specified number of times. So far, this specified number is fixed as 1, i.e., the alarm occurs
whenever the error is detected.
● Data Reference
When processing type is “reference” or “reference and setting,” data is referred from the
specified reference destination. An example of data reference action is shown below.
Referencing function block ADL Other Referenced function block

control station
PV IN SETn Reference data n DATA
D024703E.EPS
Figure Data Reference Action of Inter-Station Data Link Block (ADL)

● Data Setting
When processing type is “setting” or “reference and setting,” data is set to the specified
setting destination. When data with data status is set, its data status is transmitted just like
the connection between function blocks that both belong to the same FCS.
Before setting data, function blocks read back the set data. This readback action is also
performed when data is set between different FCS. Therefore, data reference (readback) is
performed to every data specified for “reference and setting” prior to setting. The refer-
enced value in this readback action is returned when a readback request is received from
the setting source function block.
The data set examples in the case of data setting connection are shown as follows.
Data setting source ADL Other Data setting destination

function block control station function block
Reference data n
MV OUT SETn DATA
Set data n
D024704E.EPS
Figure Data Setting Action
Upstream block ADL Other Downstream block

in cascade control station in cascade
Reference data n
MV OUT SETn SET CSV
Set data n
D024705E.EPS
Figure Cascade Connection
IMPORTANT
When the cascade connection between controller function blocks involves different FCS,
use the Inter-Station Data Link Block (ADL) in accordance with the following conditions.
• Set the control output action type of the upstream function block in cascade to “posi-
tional.”
• The control period of the upstream function block in cascade should be set longer
than the inter-station communication period.

● Inter-Station Communication Period
▼ Inter-Station Data Link Communication Period
The inter-station communication period is a time required to complete all inter-station data
link processing within a FCS. It is specified in the FCS Constants Builder as a FCS-specific
constant. The default is one second.
During inter-station data link processing, inter-station data link processing at all points is
completed within the time in seconds corresponding to the “inter-station communication
period.” The number of inter-station communications points executed in one second is
shown below.
Points obtained by rounding up the result of the following equation to the nearest multiple of
8.
(Effective inter-station data link points)

(round up by every 8 points)
(Inter-station communication period)
D024706E.EPS
The effective inter-station data link points are the points of the inter-station data link actually
wired in Control Drawing Builder or in Function Block Detail Builder or in Function Block
Overview Builder within each FCS. When the definition (wire connection) of the inter-
station data link is changed, the inter-station data link points to be processed in one second
will be set again based on the set inter-station data link points.
TIP
When the inter-station communication period is changed, offline downloading will be required.
● Re-Transmission Skip when Communication Error Detected

▼ Re-Transmission Skip when Inter-Station Data Link Error
When a communication error is detected during inter-station data link processing, inter-
station communication transmission skips for a period of time then retry the transmission in
the interval of this skip period. This re-transmission skip period is expressed as follows:
Re-transmission skip period =

(Inter-station communication period) • (re-transmission skip times)
The re-transmission skip times can be defined in the FCS Constants Builder as a FCS
constant. The default is 60.
If the inter-station communication period extends, the re-transmission skip period extends
accordingly.

<Toc> <Ind> <D2.47 General-Purpose Arithmetic Expressions> D2-196
D2.47 General-Purpose Arithmetic Expressions

The general-purpose arithmetic expression description language is a programming
language to describe the arithmetic algorithm of the general-purpose calculation
blocks (CALCU, CALCU-C).
■ General-Purpose Arithmetic Expressions

The general-purpose arithmetic expressions are used in order to define the calculation
algorithm of the general-purpose calculation blocks (CALCU, CALCU-C).
The following section describes the features of the general-purpose arithmetic expressions.
• Data items of an arbitrary function block can be referred to or set through the I/O
terminal of the general-purpose calculation blocks (CALCU, CALCU-C).
• Arithmetic expressions which handle character strings such as messages and block
mode can be described.
• Processing such as conditional jumps can be described by using control statements.
• Built-in functions which execute calculations for the temperature correction or pres-
sure correction, etc., can be used.

D2.47.1 Basic Items of the General-Purpose Arithmetic

Expressions
This section explains the basic items of the general-purpose arithmetic expressions.
■ Identifiers in the General-Purpose Arithmetic Expressions

▼ Basic of Arithmetic Calculation Description
The identifiers in the general-purpose arithmetic expressions are the character strings that
represent the arithmetic expressions and variables and labels used by arithmetic expres-
sions.
Various variables used by the labels of the arithmetic expressions or in the arithmetic
expressions require identifiers. They cannot become the object of calculation without
identifiers.
The names of the identifiers have the following restrictions:
• Only the following characters are allowed to use; alphabet (A to Z and a to z), num-
bers (0 to 9), “_” (underscore), “$”, and “%.”
• Use an alphabet or “%” for the first character of the identifier name.
• Even though there is no limit to the length of the identifier, only the first eight charac-
ters are valid for identification. Identifiers that have the same first eight-characters are
treated as the same identifier.
• Upper case and lower case of the alphabets are not distinguished.
• The identifiers which are defined as reserved words for the numerical calculation
expressions cannot be used other than the reserved purposes.
SEE ALSO
For the reserved words of the general-purpose arithmetic expression, see chapter D2.47.9, “Reserved
Words for Numerical and Logical Arithmetic Expressions.”

■ Configuration of the General-Purpose Arithmetic Expression
The general-purpose arithmetic expression consists of a program statement, which indi-
cates the start of an arithmetic expression; declaration statement, which declares variables;
executable statements, which execute calculations; and an end statement, which indicates
the end of an arithmetic expression.
The program statement and end statement can be omitted.
The following lines give the example of the order that each statement in the arithmetic
expression:
program
declaration statement
executable statement
end
● Express in Multiple Lines

When one statement is too long and does not fit in one line, use “\” or “//” in the end of the
line. One statement can be written in multiple lines if “\” or “//” is followed by a line break.
The following example shows a statement in multiple lines:
program
{PIC100.MODE.MAN)=//
{TIC100.ALRM.HI}
{SW100.SV.3}=\
{TIC100.MODE.AUT}
end
● Comment
When a line is headed by a “*” mark, the contents of the entire line are treated as a com-
ment.
When “!” mark appears in the middle of a line, the texts from the right-hand side of “!” mark
till the end of the line are treated as a comment.
The following examples show a comment and a comment statement:
program !This portion is comment.
*This line is for comment.
if ({SW100.SW.3})then

● Label
A label can be attached to a statement as a mark. A label can be used as a branch destina-
tion of a goto statement.
The labels are written in the following format:
<identifier>:<statement>
An example of label is shown below:

program
label: if({SW100.SW.3})then
If there is no statement to the right-hand side of a label, it means that the label is for the
next statement. An example when no statement is written to the right-hand side of the label
is shown below:
program
label:
if({SW100.SW.3})then
● Maximum Number of Lines for an Arithmetic Expression

A maximum number of lines for an arithmetic expression are 250 including comment and
empty lines. Among them, only 20 lines can be used for the statement descriptions. The
lines listed below, however, are excluded from the statement description lines:
• Program, end, else, end if, case, otherwise, end switch, labels, comments, and lines
that consist of declaration statements only.
• The second line and thereafter of a statements where ended with “\” or “//” mark.
• Empty lines
When a “case” statement and another statement are written in the same line, such as “case
1:i=1,” the line is treated as a statement line.
● Engineering Index
Even if the statement is written in 20 lines or less, a capacity overflow error may occur
during the compilation. This phenomenon occurs due to the limitation on the used vari-
ables, constants and the number of operators.
The possibility of a capacity overflow error is lowered if approximately 20 lines of assign-
ment statements with four terms, as shown below, are written:
A = A1 + A2 + A3 + A4

■ Data Types of the General-Purpose Arithmetic Expression
The variables used in the general-purpose arithmetic expression have the same data types
as other programming languages.
The data types of variables are as follows:
Data type Character string type (char*n)
Numerical value type Integer type Integer (integer)
Long integer (long)
Real type Single-precision floating point (float)
Double-precision floating point (double)

D024801E.EPS
Figure Data Types
Range of values for each data type is shown below.

Table Data Type
Data type Bits Minimum value Maximum value
Character string (*1) 8•n Not applicable Not Applicable
Integer 16 -32768 32767
Long integer 32 -2147483648 2147483647
Single-precision floating point (*2) 32 -3.402823 • 10 38 3.402823 • 10 6
Double-precision Floating point (*3) 64 -1.79769313486231 • 10 308 1.79769313486231 • 10 6
D024802E.EPS
*1: 16 bytes maximum for a character string

*2: The number of digits may be displayed for a single-precision floating point is seven.
*3: The number of digits may be displayed for a double-precision floating point is fifteen.

The bit format of data for each data type is shown below. Integers and the mantissa part of
real numbers are two’s complement representation.
char*n
1st byte nth byte
integer
Integer 15 bits
Sign bit (1 bit) 0: Positive 1: Negative
long
Integer 31 bits
Sign bit (1 bit) 0: Positive 1: Negative
float
Exponent field Mantissa field
(E) 8 bits (M) 23 bits
Sign bit (S) 1 bit

The value is given by the following formula:
(-1) S • 2e-127•1.M
double
Exponent field Mantissa field
(E) 11 bits (M) 52 bits
Continuation of the mantissa field (M)
Sign bit (S) 1 bit

The value is given by the following formula:
(-1) S • 2e-1023•1.M
D024803E.EPS
Figure Data Format of Each Data Type

D2.47.2 Constants in General-Purpose Arithmetic Expressions

Constants in general-purpose arithmetic expressions are character strings which
represent values themselves. Three kinds of constants can be used, as follows:
Integer constant (10, 20, etc.)
Floating-point constant (1.5, 100.0, 1.5E10, etc.)
Character string constant (“ABC”, “character string”, etc.)
■ Integer Constants in General-Purpose Arithmetic Expressions

▼ Constant
The integer constants are the constants represented by integers.
The data type of integer constant is the long type. An integer constant can be represented
by a decimal number or a hex number. It is normally represented by a decimal number.
When the hex notation is used, add “$” at the beginning of a constant.
A decimal integer constant is represented by characters “0” through “9”. In addition to the
numbers, alphabets between “A” and “F” as well as between “a” and “f” are used for the
hex notation.
Examples of constants are as follows:
• Decimal integer constants: 5 10 65535
• Hex integer constants: $5 $A $FFFF
■ Floating-Point Constants in the General-Purpose Arithmetic

Expressions
The floating-point constants are the constants represented by the mantissa field and
exponent field.
The data type of floating-point constants is the double type. Only the decimal notation is
allowed for the floating point.
The following shows the expression methods of the floating point:
• Describe a decimal number with a decimal point.
• Describe in the <mantissa field>E<exponent field> format or <mantissa
field>e<exponent field> format.
<Mantissa field>: A decimal number with or without decimal point.
<Exponent field>: A decimal number without or with a sign.
When the <mantissa field> is x and the <exponent field> is y, the value of the constant
is
x • 10y.
The following shows examples of floating-point constants:

• Description of a decimal number with decimal point:
1.0, 15.8, 0.05
• Description in the <mantissa field>E<exponent field> format or <mantissafield>
e<exponent field> format.
1.0E5, 1.0e-5, 123E3

■ Character String Constants in General-Purpose Arithmetic Expressions
The character string constant is a constant that can represent a character string. A charac-
ter string constant can use both single-byte characters and double-byte characters.
A character string constant is represented by a character string enclosed by double quotes
(“”). The double quotations, line break, horizontal tab and back slash have to be replaced
by the following character strings:
Table Notations of Special Characters
Special character Symbol Notation
Line break NL \n
Horizontal tab HT \t
Back slash \ \\
Double quote ” \”
D024804E.EPS
Examples of the character string constants are as follows:

“abc”, “This is a character string”
“character string”, “1-st line\n2-nd line\n3-rd line”

D2.47.3 Variables
A variable is a data which has a name and data type. A value can be referred to and
set by a variable.
There are two kinds of variables: I/O variables and local variables.
■ I/O Variables of the General-Purpose Arithmetic Expressions

▼ Variables
The I/O variables are data items of the General-Purpose Calculation Block (CALCU,
CALCU-C), such as the calculated input value (RVn), calculation output value (CPVn),
parameter (Pn), etc.
The data type of the calculated input value (RVn) and calculation output value (CPVn) is
automatically determined by the data item of the connection destination. In addition, the
data type of the parameter (Pn) is automatically determined by the type of the general-
purpose calculation block and the data item. It is not necessary to declare the parameter
(Pn), which is used as the I/O variable, in the arithmetic expression.
TIP
• The block mode and alarm status are integer data.
• The size of the character string I/O variable is 16 bytes.
● Usage of I/O Variables

The I/O variables are used for referring to or setting data of the connection destination of
the I/O terminal.

● When Referencing by Wiring the I/O Terminals
If the I/O terminals are connected to other function blocks using the Function Block Detail
Builder, the data of other function blocks can be referred or set by way of I/O variables.
In order to refer or to set an I/O variable, use the data item name that corresponds to the
connected I/O terminal.
A maximum of eight input variables and four output variables can be declared by wiring the
I/O terminal.
CALCU
IN
RV
PVI 01
IN OUT
PV RV1 CPV=RV+RV1+RV2 CPV
02
PVI RV2
IN
PV
D024805E.EPS
Figure Example of I/O Variables and Arithmetic Expression when Wired by the Builder
TIP
• When the same data is connected to the input connection terminal and output connection terminal,
separate input variable and output variable are allocated.
• The I/O variables can be used in an expression. However, input variables (RV, RV1, RV2, ...) cannot
be used on the left-hand side of the assignment statement.

● When the Data of Other Function Block is Specified by an Element Symbol
Data of other function block can be specified by an element symbol and data item name.
A maximum of 24 input variables and 12 output variables can be declared as element
symbol and data item name.
There are three kinds of formats for handling the data of other function block (connection
information) in arithmetic expressions, as follows:
• Data connection (Data reference and setting)
<element symbol>.<data item name>
• Sequence connection (Data value reference and data value modification)
{<element symbol>.<data item name>.<condition specification|operation specifica-
tion>}
• Sequence connection (Data status reference)
{<element symbol>.<data item name>=<condition specification>}
When a tag name is used as the element symbol, if a tag name starts with a number or “-”
sign, the computation may not be correct. Define an alias to use the tag.
The element symbols and data item names represent the data from other blocks can be
assigned to variables by compiler. The data items assigned to variables according to the
following conditions:
• If the data of other function block is written on the left-hand side of an assignment
statement, it is assigned to an output variable.
• If the data of other function block is written both on the left-hand side of an assignment
statement, it is assigned to an input variable.
• If the same data as other function block is written both on the left-hand side of an
assignment statement and another place in the data connection format, it is assigned
to an output variable.
• If the same data as other function block is written both on the left-hand side of an
assignment statement and another place in the sequence connection format, it is
assigned to a separate input variable and output variable.
• If the data of another function block is written at a place other than the left-hand side of
an assignment statement in the sequence connection format, the condition testing of
the sequence connection is always executed even if the statement is not executed.

● Data Connection Using the Element Symbol (Data Reference and Setting)
The following example shows an arithmetic expression by which the data reference and
setting of other function block are executed, using the element symbol.
program
TIC100.VN=FIC100.CPV*0.1
end
The second line is a statement which sets the calculation output value (CPV) of FIC100
multiplied by 0.1 to the I/O compensation value (VN).
When data reference and setting of other function block are executed by using the element
symbol instead of terminal connected by the Function Block Detail Builder, the following
restrictions apply:
• Connection between terminals and connection between stations cannot be specified
because the connection is not established by the builder.
• The I/O variable that the element symbol is assigned to is unknown, because the
compiler automatically assigns the element symbol to the I/O variable other than RV,
RV1 through RV7, CPV, CPV1 through CPV3.
● Sequence Connection Using the Element Symbol (Data Value Reference

and Data Value Modification)
The following example shows an arithmetic expression which executes the sequence
connection with other function block using the element symbol.
program
{PIC100.MODE.MAN}={TIC100.ALM.HI}
{SW100.SV.3}={TIC100.MODE.AUT}
end
The second line is a statement which changes the block mode of PIC100 to MAN when the
alarm status of TIC100 is HI.
The third line is a statement which modifies the signal path by changing SV of the selector
switch to 3 when the block mode of TIC100 is in the automatic (AUT) mode.

● Sequence Connection by Using the Element Symbol
(Data Status Reference)
The following example shows an arithmetic expression for a sequence connection by using
the element symbol.
program
if({SW100.SW.3})then
{PIC100.MODE.AUT}={CAL100.ACT.ON}
end if
end
The second line is an “if” statement which tests whether SV of the selector switch is 3 or
not. The third line is a statement executed when the if statement in the second line is true.
In this statement, the block mode of PIC100 is switched to the automatic (AUT) mode when
the CAL100 block is started by a one-shot command.
The one-shot command to start the CAL100 might be triggered by any other blocks or
occurs at the time even before this block starts. It is irrelevant to this calculation block. In
the other word, the CAL100 started by the one-shot command have no relation with state-
ment in the second line in this calculation block.
On the contrary, the statement on the left-hand side which changes PIC100 to AUT is not
executed unless the result of the if statement in the second line is true and the third line
condition written at right-hand side is true at the same time.

■ Local Variables in General-Purpose Arithmetic Expressions
The local variables in a general-purpose arithmetic expression are the variables declared in
the function block. They can be used only in the general-purpose calculation block where
they were declared. In order to use local variables, use them as intermediate variables after
declaring the type. The local variables do not retain values from the previous execution of
the arithmetic expression. In addition, the initial value is undefined. A maximum of ten local
variables can be used in one general-purpose arithmetic expression.
● Declaration of Local Variables

The local variables are declared as follows:
<type specifier><variable name>[,<variable name> .. ]
• <type specifier>: Specify the variable type.

The type specifiers include char *n, integer, long, float, and double. Use char *n as the
type specifier to declare a character string. By using this description, it is possible to
use a character string variable which is capable of expressing a character string of a
maximum of n bytes.
• <variable name>: Specify a variable name as the identifier.
When multiple variable names are listed and separated by commas, more than one
variable of the same data type can be declared at once.
TIP
• Specify the number of bytes, n, of the character string when a character string variable is declared.
When a character string variable where characters which require two bytes per character, such as
the Japanese character code, are stored, specify a value n by taking characters that require two
bytes into account.
• The maximum size of local variable of the character string type is sixteen bytes.

● Implicit Declaration of Local Variables
When an undeclared variable is encountered, the data type of the variable is automatically
decided based on the first character of the variable name, and the variable is treated as a
local variable. This is called implicit declaration.
The relationship between the first character of the local variable name and the data type is
as follows:
• I: Integer
• L: Long integer
• F: Single-precision floating point
• C: Character string
• Others: Double-precision floating point
If the compiler control command, #implicit none is given, the implicit declaration of the local
variable is disabled. Then a compiler error occurs if a variable not declared is used.
Use the “#implicit none” instruction between the program statement and the end statement.
■ Tag Name of the General-Purpose Arithmetic Expressions

When an undeclared variable name is followed by “.” (period), the variable is treated as a
tag name.
When an arithmetic expression is compiled, whether or not the tag name has been defined
by the builder before is checked. A compiler error occurs if the tag name has not been
defined.
In addition, the arithmetic expression cannot be compiled correctly if a tag name that starts
with a number or includes “-” (hyphen) even if the tag name has been registered. To define
an alias or replace the tag name with the one does not start with a number and does not
include “-.”

■ Alias Definition of the General-purpose Arithmetic Expressions
Alias definition is to substitute the name of an I/O variable with another character string.
When an alias of input variable is defined, I/O variables and data of other function block
can be handled by different name in the arithmetic expression. Write alias definitions at the
beginning of arithmetic expression.
The format of the alias definition is as follows:
alias <alias><word list>
How to write the word list is shown below.

Table Word List of Alias Definition
Type of word list Format of word list Description example
Input variable RV, RV1 to RV7 alias FLOW RV1
Output variable CPV, CPV1 to CPV3 alias HOSEI CPV
Data connection <element symbol>.<data item> alias PRESS FIC001.PV
冦<element symbol>.<data
alias SEQ1 冦TAG001.MODE.AUT冧
item>.<condition specification>冧
冦<element symbol>.<data
alias SEQ2 冦TAG002.MODE.AUT冧
item>.<operation specification>冧
Sequence connection
冦<element symbol>.<data item>
alias SEQ3 冦TAG003.PV=BAD冧
=<condition specification>冧
冦<element symbol>.<data item>
alias SEQ4 冦TAG004.PV=CAL冧
=<operation specification>冧
D024806E.EPS
An example of arithmetic expression which includes alias definitions is shown below:

program
alias FLOW RV1
alias HOSEI CPV1
HOSEI=FLOW*0.1
end
An example of arithmetic expression which uses aliases for data reference and data setting
of other function block is shown blow:
program
alias FLOW FIC100.CPV
alias HOSEI TIC100.VN
HOSEI=FLOW*0.1
end

■ Character String Substitution
The character string substitution is to assign a specific character string to an identifier.
Character string substitution is executed by using the compiler control instruction, “#de-
fine.”
The format of the character string substitution is shown below:
#define<identifier><character string>
Conditions of a range which is recognized as a <character string> is as follows:

• Character string up to a line break. Continuous spaces immediately before the line
break and comment part are excluded.
• When “\” or “//” is used, the contents in the following line are recognized as a substitut-
ing character string as well.
When the arithmetic expression is compiled, the identifier defined by the compiler control
instruction “#define” is replaced by assigned character string prior to compilation. Even if
the identifier appears in the character string, however, substitution is not performed.
An example of character string substitution is shown below:
program
#define OPEN 2
......
SI0100.MV=OPEN
SI0200.MV=OPEN
end
The “OPEN” identifier in this arithmetic expression is the substitution of “2”.

In order to define a character string which includes an arithmetic expression using the
“#define” compiler control instruction, enclose the arithmetic expression by “( )”. It might be
necessary to enclose the corresponding arithmetic expression by “( )” to obtain the desired
arithmetic expression, because the “#define” compiler control instruction is a substitution of
the character string. The following example shows an improper substitution of arithmetic
expression:
program
#define MAXLEN 256
#define GOOD (MAXLEN-1)! Good example
#define BAD MAXLEN-1! Bad example
......
i1=GOOD*5!(MAXLEN-1)*5Calculated like this
i2=BAD*5!Calculated as MAXLEN-1*5, i.e., calculated as MAXLEN-(1*5)
......
end
In this example, (256-1) • 5=1275 is expected as the result of the calculation.

But, i2 is resulted in 251 incorrectly while i1 is resulted in 1275 correctly because of differ-
ent calculation priorities.

D2.47.4 Operators
The following operators can be used in the general-purpose arithmetic expressions:
• Binomial operator
• Unary arithmetic operator
• Relational operator
• Equality operator
• Binary logical operator
• Unary logical operator
• Bitwise logical operator
• Bitwise shift operator
■ Binomial Arithmetic Operator

▼ Operators
Calculation with a binomial arithmetic operator can be executed to any numerical data.
Usable binomial arithmetic operators are as follows:
• +: Addition
• -: Subtraction
• *: Multiplication
• /: Division
• mod: Remainder
When an integer is divided by another integer, the digits to the right of the decimal point are
truncated for the quotient.
If the operand of a mod calculation is a real number, the fractional part of the operand is
rounded off and the operand is converted to a long integer (long) type prior to the calcula-
tion.
Insert a space before and after “mod.”
■ Unary Arithmetic Operator

Calculation with an unary arithmetic operator can be executed to any numerical data.
Usable unary arithmetic operators are as follows:
• +: Positive
• -: Negative
+ retain the sign of the operand.

- switch the sign of the operand from positive to negative or negative to positive.

■ Relational Operators
Calculation with a relational operator can be executed to any numerical data and any
character string data.
Usable unary relational operators are as follows:
• <: Smaller than
• >: Greater than
• <=: Equal to or smaller than
• >=: Equal to or larger than
The result of the calculation by a relational operator is the integer type. The value of the
calculation result becomes true (1) if the relationship between the two sides connected by
the relational operator is satisfied, or becomes false (0) if it is not satisfied.
■ Equality Operators
Calculation with an equality operator can be executed to any numerical data and any
character string data.
Usable equality operators are as follows:
• ==: Equals
• <>: Not equals
The result of the calculation with the equality operator is the integer data. The value of the
calculation result becomes 1 if the relationship between the two sides connected by the
equality operator is satisfied, or becomes 0 if it is not satisfied. When both the equality
operator and relational operator are used in the same arithmetic expression, the relational
operator is evaluated first.
When a comparison of real numbers is executed by the equality operator, it is determined
to be different even if the values of both sides differ slightly. Use relational operators (>=,
<=, >, <) to compare real numbers.
■ Binary Logical Operators

Calculation with a binary logical operator can be executed to any numerical data.
Usable binary logical operators are as follows:
• and: AND
• or: OR
• eor: Exclusive OR
The logical values of both sides become true if any value other than 0, and false if 0. The
value of the calculation result becomes 1 if the logical calculation result is true and 0 if false.
The calculation result is the integer type.
Insert a space before and after a binary logical operator.

■ Unary Logical Operator
Calculation with the unary logical operator can be executed to any numerical data.
Usable unary logical operator is as follows:
• not: Negation
The logical value of the operand becomes true if the value is anything other than 0, and
false if 0. The value of the calculation result becomes 1 if the result of the logical calculation
is true, and 0 if false.
The calculation result is the integer type.
Insert a space before and after the unary logical operator.
■ Bitwise Logical Operators

Calculation with a bitwise logical operator can be executed to any numerical data.
Usable bitwise logical operators are as follows:
• &: Bitwise AND
• |: Bitwise OR
• ^: Bitwise exclusive OR
• –: One’s complement (unary operator)
If the operand of a bitwise binary logical calculation is a real number, the fractional part of
the operand is rounded off and the operand is converted to the long integer (long) type prior
to calculation.
The logical calculation is executed bit-by-bit to the values on both sides.

■ Bitwise Shift Operators
Calculation by a bitwise shift operator can be executed to any numerical data.
Usable bitwise shift operators are as follows:
• <<: Leftward bit shift
• >>: Rightward bit shift
• <@: Leftward cyclic shift
• >@: Rightward cyclic shift
An example of the calculation operation when described as <expression 1><shift

operation><expression 2> is as follows:
• <expression 1> is shifted by bit or cyclic-shifted for the number of times specified by
the value of <expression 2>. Arithmetic shift is executed for the bit shift. When the bits
are shifted rightward, the original most significant bit is duplicated as the new most
significant bit. 0 is always entered to the least significant bit when the bits are shifted
leftward.
• When <expression 1> or <expression 2> is the floating point type, the fractional part of
the operand is rounded off and the operand is converted to the long integer (long) type
prior to calculation.
• When <expression 1> is the integer type, the remainder of <expression 2> divided by
16 is used as the number of shift applied to <expression 1>.
• When <expression 1> is the long type or real type, the remainder of <expression 2>
divided by 32 is used as the number of shift applied to <expression 1>.

D2.47.5 Arithmetic Expressions

An arithmetic expression refers to a statement which satisfies one of the following
conditions:
• It is a function, constant, or variable.
• It is a statement which connects functions, constants and variables by an
operator.
• It is a statement which connects arithmetic expressions by an operator.
■ Arithmetic Expressions
▼ Arithmetic Expressions
An arithmetic expression can be described using the following format in general-purpose
arithmetic expressions:
• <function>
• <constant>
• <variable>
• (<expression>)
• <expression><binomial operator><expression>
• <unary operator><expression>
• <expression><equality operator><expression>
• <expression><relational operator><expression>
• <expression><binary logical operator><expression>
• <unary logical operator><expression>
• <expression><bitwise binary logical operator><expression>
• <bitwise unary logical operator><expression>
• <expression><bitwise shift operator><expression>

■ Priority Order
The priority order of the calculations is shown in the following table:
Table Priority Order of the Calculations
Calculation Symbol (Operator) Association rule Priority
Parenthesis () Left to right Highest priority
Function Function Left to right B
Unary operator — (not) - (negative) + (positive) Right to left
Multiplication and division * / MOD Left to right
Addition and subtraction +- Left to right
Shift operation << >> <@>@ Left to right
Relational operator < <= > >= Left to right
Equality operator == <> Left to right
Logical operator & Left to right
Logical operator ^ Left to right
Logical operator | Left to right
Logical operator and Left to right
Logical operator eor Left to right ?
Logical operator or Left to right Lowest priority
D024807E.EPS
■ Data Type Conversion

When the operands on both sides of the operator that requires two operands have different
data types, the data type of one operand is automatically converted to match the other data
type which can handle larger data. The rules of data type conversion are shown in the
following table. The table shows the data types of the operands and calculation results.
Table Data Type Conversion Rules
Right-hand side
Left-hand side integer long float double
integer I•IAI L•LAL D•DAD D•DAD

long L•LAL L•LAL D•DAD D•DAD
float D•DAD D•DAD D•DAD D•DAD
double D•DAD D•DAD D•DAD D•DAD
D024808E.EPS
I: integer type
L: long type
D: double type
Note: Calculation is not allowed if the character string data and numerical data are mixed. Also, no data type conversion is
executed between the character string type and numerical type.
Note: The float type is converted to the double type unconditionally.
TIP
• If either operand is the double type, the other operand will also be converted to the double type.
Accordingly, the calculation result becomes the double type.
• If either operand is the long type and the other is integer, the other operand is converted to the long
type. The calculation result becomes the long type.
• If both operands are integer type, the calculation result remains integer type.

■ Comparison of Character Strings
Character strings can be compared as a character string operation. The relational operator
and equality operator can be used for character comparison. Character strings cannot be
processed by the general-purpose arithmetic expression description.
● Character String Comparison Method

The character string comparison method follows the rules below:
• The comparison of characters is executed by comparing the internal codes of the
characters. The internal codes are compared as unsigned 8-bit values.
• Spaces is subject to comparison.
• Comparison of character strings is executed character-by-character from the first
character of the left-hand side and right-hand side.
● Test Conditions of the Character String Comparison

Testing of large and small between character strings follows the rules below:
• When both sides are exactly the same character strings, the two sides are evaluated
as equal.
• When at least one character is different, the comparison starts from the character
closest to the beginning among the different characters. The character string with a
character which has a larger internal code as a result of comparison is evaluated as
the larger one.
• When the lengths of the character strings are different, the longer character string is
evaluated as the larger one.

■ Assignment Statement
An assignment statement refers to a statement which has a variable on the left-hand side
and an expression on the right-hand side, and they are connected by the “=” symbol. An
assignment statement substitutes the left-hand side variable by the calculation result of the
right-hand side expression.
It is necessary in the assignment statement for both of the right side and left side to be the
numerical type or character string type.
The format of the assignment statement is as follows:
<variable> = <expression>
• <variable>:
Variable to which the value of <expression> calculation should be assigned.
• <expression>:
Expression that calculates the substituting value for the <variable>.
● Numerical Value Substitution

Two variables put on each side of “=” symbol forms a substitution formula.
If the data types on each side of expression are different, the data type of the right-hand
side expression is converted to the data type of the left-hand side variable.
Combinations of the left hand and right hand which may cause an overflow or loss of digits
are shown in the following table:
Table Combinations of the Left-hand Side and Right-hand Side which may Cause an Overflow or
Loss of Digits
Right-hand side
Left-hand side integer long float double
integer A A A
long A A
float B A, B
double
D024809E.EPS
Blank: No problem
A: An overflow may occur.
B: Loss of digits may occur.
Note: Extend the sign of the value before assigning a value of the integer type to a long-type variable.
Note: An overflow error occurs when the substituting value exceeds the handling range for the integer type.
Note: When a variable of the integer type is substituted by a value of the real type, round off the substituting value at the first
digit after the decimal point prior to substitution. Use the “int” built-in function to truncate after the decimal point.
● Character String Substitution

When the entered character string longer than the allowed size of the character string
variable, the characters for the character string size are inserted from the beginning of the
character string. Characters which cannot fit are discarded.
When a character string shorter than the size of the character string variable is entered to a
character string variable, a terminator is added to the end of the character string. The size
of the substituted character string variable becomes the size of the character string before
the terminator.

D2.47.6 Control Statements

The control statement is a statement for controlling the execution order of arithmetic
expressions. There are four kinds of control statements for testing conditions and
selections as follows:
• if statement:
Condition testing
• switch statement:
Multiple-branches processing
• goto statement:
Unconditional jump
However, jump cannot be specified if the execution of the arithmetic expression
goes backwards.
• exit statement:
Jumps to the “end” statement unconditionally.
■ if
▼ Control Statements
The “if” statement is used to control the execution of arithmetic expressions by the
condition(s) of the expression.
The format of the “if” statement is shown below:
● Format 1
if (<expression>)<statement>
• <expression>: Give the expression to be evaluated in the numerical or character

string format.
• <statement>: A statement which will be executed when the expression is true.
When the “if” statement above is executed, <expression> is calculated. <statement> is

executed only when the result of the <expression> is true (<>0).

● Format 2
if (<statement>)then
....
[else
....
]
....
end if
....
When the “if” statement above is executed, <expression> is evaluated first. Further pro-
cessing will be determined depending on the evaluation result.
• When the result of <expression> is true (<>0), after executing the statements from the
one after “then” to the one before “else”, the execution jumps to the statement after
the “end if” statement. When the “else” statement does not exist, the statements after
“then” will be executed.
• When the result of <expression> is false (==0), if the “else” statement exists, the
statements after “else” will be executed. When the “else” statement does not exist, the
statements after “end if” statement will be executed.

● Format 3
if (<expression>)then
....
else if (<expression>)then
....
[else
....
]
....
end if
....
When the “if” statement above is executed, the <expression> is evaluated first. Further
processing will be determined depending on the evaluation result.
• When the result of the <expression> in the “if” statement is true (<>0), after executing
the statements starting from the statement after “then” which corresponds to <expres-
sion>, to the statement before the “else if” statement, the execution jumps to the
statement after the “end if” statement.
• When the result of the <expression> in the “if” statement is false (==0), the conditional
expression in the next “else if” statement is evaluated.
• When the result of the <expression> in the “if” statement is false (==0) and the result
of the <expression> in the “else if” statement is true (<>0), if there is an “else if” state-
ment after the “then” statement, the statements starting from the one after “then”
statement to the one before “else if” statement will be executed, and the execution
jumps to the statement after the “end if” statement.
If there is no “else if” statement after “then” statement and an “else” statement exists,
the statements starting from the one after the “then” statement to the one before the
“else” statement will be executed, and the execution jumps to the statement after the
“end if” statement.
If there is no “else if” statement nor “else” statement after the “then” statement, the
statements following the “then” statement will be executed.
• When the result of the <expression> in the “if” statement is false (==0) and the result
of the <expression> in the “else if” statement is false (==0), if an “else if” statement
exists after the “then” statement, the “else if” statement will be executed in the same
way as in the case described above.
If there is no “else if” statement exists after the “then” statement but the “else” state-
ment exists, the statements following the “else” statement will be executed.
If there is no “else if” statement or “else” statement, the statements following the “end
if” statement will be executed.
While the processing can jump out of the “if” to “end if” statement range by a “goto” state-
ment, the execution cannot jump to inside the “if” to “end if” statement range from outside of
the “if” statement.

■ switch
The switch statement is used to branch depending on the matching condition of expression
with any of the multiple constant values.
switch (<expression>)
case <constant>[,<constant>]...:
....
[case <constant>[,<constant>...]:
....
[otherwise:
....
]]
end switch
• <expression>
Give the expression to be evaluated in the integer or character string format.
• <constant>
A constant to be compared with the <expression>. Specify a value of the same data
type as that of the <expression> in the “switch” statement. Multiple constants can be
listed.
When the switch statement above is executed, the value of the <expression> is calculated
first. The processing will be branched depending on the result of the comparison be-
tween the <expression> value and the <constant>. The branch algorithm is shown below:
• When a <constant> of the same value as that of the <expression> exists, the process-
ing branches to the statement after the “case” statement which includes the <con-
stant> of the same <expression> value. After executing to the statement before the
next “case” statement, the processing jumps to the statement after the “end switch”
statement.
• When there is no <constant> that is the same as the <expression> value and there is
an “otherwise” statement, the processing branches to the statement after the “other-
wise” statement.
• When there is no <constant> that is the same as the <expression> value and there
are no “otherwise” statement, the processing branches to the statement after the “end
switch” statement.
While the processing can jump out of the “switch” to “end switch” statement range by a
“goto” statement, the execution cannot jump to inside the “switch” to “end switch” statement
range from outside of the “switch” statement.
The statement following the “case” statement can be written in the same line as the “case”
statement. Even though a line which only has a “case” statement is not counted as an
execution statement, it will be counted as an execution statement if a statement is written in
the same line as the “case” statement.

■ goto
The “goto” statement unconditionally jumps to the line with the specified label.
The “goto” statement, however, cannot specify a label before the “goto” statement itself.
goto <label>
A compiler error will occur if the label specified by the “goto” statement is located prior to
the “goto” statement, or if the specified label does not exist in the arithmetic expression.
■ exit
The “exit” statement unconditionally jumps to the “end” statement. The “exit” statement can
be placed anywhere in the arithmetic expression.

D2.47.7 Error Handling

This section describes the causes of errors occurred during the execution of gen-
eral-purpose arithmetic expression and how to handle the errors as well as the
details of error codes.
■ Error in the Arithmetic Processing

▼ Error Handling
The cause of errors occurred during the execution of the assignment processing and
calculation processing, as well as how to handle the errors will be explained.
● Causes of Computation Errors

Causes of the computation errors are as follows:
• When the computation result overflows.
• When division by 0 is executed.
• When a calculation is executed to an imaginary number.
• When X 0 in log (X).
• When X < 0 and Y is a decimal fraction in power (X, Y).
● Computation Error Handling

The handling when a computation error occurs is as follows:
• The calculation processing and the assignment processing are immediately stopped.
The value in the variable does not change.
• The following maintenance information is saved in the General-Purpose Calculation
Block (CALCU, CALCU-C).
Statement number where the error occurred. (ERR)
Error code
All local variables
■ Error in Conditional Expression

If an error occurs during the calculation of a conditional expression, the calculation is
stopped due to a calculation error.

■ Arithmetic Expression Interpreter Error Code
The arithmetic expression interpreter error codes, which occur when statements are
executed, are as follows:
• Category error code
This error code indicates the cause of the error.
• Detailed error code
The contents are different depending on the category error code.
The category error code and the detailed error code are output to the operation and moni-
toring functions output as a system alarm message. The output format of the error code is
shown below.
tag_name tag_comment CALCULATION ERROR LINE=nnnnnn CODE=xxxxxx-yyyy
nnnnnn: Line number

xxxxxx: Category error code (decimal)
yyyy: Detailed error code (hex)
The category error codes include the calculation error, errors specific to the arithmetic
expression, execution control error, general error of the built-in function, and other errors.
The details of the category error and detailed error codes are shown below.
● Calculation Error Codes

Table Calculation Error Codes
Code Description Remark
1 Overflow caused by calculation
2 Overflow caused by data type conversion
3 Division by 0
4 Underflow (reserved)
5 Invalid calculation occurred. Including a division by 0 for a real number.
10 Array index is out of range.
11 Attempted to set a value to a constant.
The character string type is specified to a part where only the numerical
12
type is allowed.
The numerical type is specified to a part where only the character string
13
type is allowed.
14 The numerical type and the character string type are mixed.
20020 Calculation stack overflow.
20021 Exceeded the range of character string area to be used by calculation.
D024810E.EPS

● Error Codes Specific to the Arithmetic Expression
The following table shows the error codes specific to the arithmetic expression.
Table List of Error Code Specific to the Arithmetic Expression
Detailed error
Code Description
code
70 Exceeded the maximum number of executable lines.
71 Attempted to execute a program which does not follow the grammar.
80 to 82 Reserved
83 Attempted to access the input variable whose number is out of range.
84 Attempted to access the output variable whose number is out of range.
85 Attempted to access the parameter variable whose number is out of range.
86 Attempted to set to the input variable.
87 Attempted to set to the pulse count value.
D024811E.EPS
: Detailed error code exists

Blank: Detailed error code does not exist
The detailed error code is a code that indicates the serial number of the data item name
where the error occurred.
The following table is a list of detailed error codes:
Table List of Detailed Error Codes
Code Data item name
0 CALCU or RV of CALCU-C, CPV
1 to 31 RVn, CPVn
0 to 7 P01 to P08
D024812E.EPS
● Execution Control Error Codes

Table List of Execution Control Error Codes
Code Description
20430 Attempted to execute an unsupported statement.
20431 Attempted to execute an unsupported built-in function.
20432 Attempted to access an unsupported variable.
20433 Attempted to use an unsupported operator.
D024813E.EPS

● Built-In Function Generic Error Codes
Table List of Built-In Function Generic Error Codes
Code Description
800 Overflow was detected in the built-in function calculation.
801 Division by zero was detected in the built-in function calculation.
802 The square root of a negative value was calculated by a built-in function.
803 Error in the argument of power() or log().
804 The absolute value of an argument to a trigonometric function is too large to calculate.
805 An error occurred by the mathematical built-in function.
807 The low-limit value is larger than the high-limit value.
810 The number of arguments for a built-in function is incorrect.
811 The type of the argument for a built-in function is incorrect.
895 The first argument of stpvcalc is not between “00” and “99.”
896 The result of stpvcalc is out of the range “00” to “99.”
D024814E.EPS
● Other Errors
Table List of Other Error Codes
Code Description
-1 to 32767 Internal error
D024815E.EPS

D2.47.8 Built-In Functions

The built-in functions of the general-purpose arithmetic expression execute calcula-
tions according to the given arguments and return calculation results.
The details of the built-in functions that can be used in the general-purpose arith-
metic expression description language are described in this section.
■ Built-In Functions
▼ Built-In Functions
The built-in functions are the applicable functions already built in the system. The built-in
functions include general arithmetic functions, bit operation functions, trigonometric func-
tions, natural logarithm, temperature and pressure correction functions and so on.
Specify one variable or constant to the built-in function as a parameter. Expressions such
as i+1 and d/10.0, or built-in function calls may not be specified as an argument.
■ Arithmetic Functions
These functions execute arithmetic calculations.
The details of the arithmetic functions are as follows.
● Absolute Value – labs(arg)

“labs” is a function that returns the absolute value of the argument. Both the argument and
result are the long type.
● Absolute Value – dabs(arg)

“dabs” is a function that returns the absolute value of the argument. Both the argument and
result are the double type.
● Maximum Value – lmax(arg1,arg2,...)

“lmax” is a function that returns the maximum value in an argument list. The maximum
number of arguments is 32. The argument and result are both the long types.
● Maximum Value – dmax(arg1,arg2,...)

“dmax” is a function that returns the maximum value in an argument list. The maximum
number of arguments is 32. The argument and result are both the double types.
● Minimum Value – lmin(arg1,arg2,...)

“lmin” is a function that returns the minimum value in an argument list. The maximum
number of arguments is 32. Both the argument and result are the long type.
● Minimum Value – dmin(arg1,arg2,...)

“dmin” is a function that returns the minimum value in an argument list. The maximum
number of arguments is 32. Both the argument and result are the double type.
● Power – power(arg1, arg2)

“power(arg1, arg2)” is a function that returns a value after multiplying arg1 for arg2 times.
Both the argument and result are the double type.

● Truncation After Decimal Point – int(arg)
“int” is a function that truncates after the decimal point. Both the argument and result are
the double type.
■ Bit Operation Function

These functions execute bit operations.
The details of bit operation functions are listed below.
● Bit Position Search Function – bitpstn(arg1,arg2)

“bitpstn(arg1,arg2)” is a function that searches the bit position. The position of the bit whose
value is 1 is searched in the integer variable specified by arg1. The result is the long type.
“bitpstn” returns -1 as the return value when two or more bits are 1 in arg1.
● Bit Position Search Function – bitsrch(arg1,arg2)

“bitsrch(arg1,arg2)” is a function that searches the bit position. The position of the bit whose
value is 1 is searched in the integer variable specified by arg1. The result is the long type.
“bitsrch” searches the value of each bit, starting start from the most significant bit. The
search stops when a bit with a value of 1 is found, and the position of the bit whose value is
1 is returned.
The return value of the normal end will be the bit position. The return value will be 0 when
all bits are 0, and -1 when an error occurs.
The “arg2,” an argument for “bitpstn” and “bitsrch,” is a variable prepared for the functional
extension in the future. “arg2” is ignored even if it is specified.
■ Trigonometric Functions
These functions execute calculations related to the trigonometric functions.
The details of the trigonometric functions are as follows:
● Sine – sin(arg)
“sin” is a function that calculates the sine of the argument. The unit of the argument is in
radian. Both the argument and result are the double type.
● Cosine – cos(arg)
“cos” is a function that calculates the cosine of the argument. The unit of the argument is in
radian. Both the argument and result are both double types.
● Tangent – tan(arg)
“tan” is a function that calculates the tangent of the argument. The unit of the argument is in
radian. Both the argument and result are the double type.
● Arctangent – atan(arg)
“atan” is a function that calculates the arctangent of the argument. The unit of the argument
is in radian. Both the argument and result are the double type.

■ Square Root – sqrt(arg)
“sqrt” is a function that calculates the square root of the argument. Both the argument and
■ Exponent – exp(arg)
“exp(arg)” is a function that calculates the result of the exponential function (the value after
multiplying e for arg times). Both the argument and result are the double type.
■ Natural Logarithm – log(arg)

“log” is a function that calculates the natural logarithm (logarithm of base e) of the argu-
ment. Both the argument and result are the double type.

■ Temperature and Pressure Correction Function
This function executes the correction calculation to the measured flowrate by the differen-
tial-pressure type flow gauge which employs the orifice. The correction calculation to the
ideal gas is executed. The details of the temperature and pressure correction function are
shown blow.
● Temperature Correction – TC(Fi,T,Tb)

TC(Fi,T,Tb) is a function that only executes temperature correction to the measured flowrate
Fi, measured temperature T and reference temperature Tb. Each input data and calculation
The correction arithmetic formula is as follows:
Tb+273.15
TC (Fi, T, Tb) = • Fi
T+273.15
D024816E.EPS

Instead of TC (C), TCF (F) maybe used in the above formula.
● Pressure Correction – PCKP(Fi, P, Pb)

PCKP(Fi,P,Pb) is a function that only executes the pressure correction to the measured
flowrate Fi, measured pressure P and reference pressure Pb. Each input data and the
calculation result are the double type.
The correction arithmetic formula is as follows:
P+1.01325 • 102
PCKP (Fi, P, Pb) = • Fi
Pb+1.01325 • 102 D024817E.EPS

P: Measured pressure (kPa)
P b: Reference pressure (kPa)
Even though PCKP (pressure unit: kPa) is used in the description above, PCP (pressure unit:
Pa) , PCMP (pressure unit: MPa) and PC (pressure unit:kgf/cm2) can alternatively be used.
When Pa or MPa is used, the constant of the pressure correction term is 1.01325 • 105 and
1.01325 • 10-1 respectively.
When PC is used, the constant of pressure term becomes 1.0332 • 102.

● Temperature and Pressure Correction – TPKP(Fi,T,P,Tb,Pb)
TPCKP(Fi,T,P,Tb,Pb) is a function that executes the correction of both temperature and
pressure for the measured flowrate Fi, measured temperature T, measured pressure P,
reference temperature Tb and reference pressure Pb. Each input data and the calculation
results are the double type.
The correction arithmetic expression is as follows:
P+1.01325 • 102 Tb+273.15

TPCKP (Fi, T, P, Tb, Pb) = • • Fi
Pb+1.01325 • 102 T+273.15
D024818E.EPS
P: Measured pressure (kPa)
Pb: Reference pressure (kPa)
Even though the TPCKP(pressure unit: kPa) is used in the description above,
TPCP(pressure unit: Pa), TPCMP(pressure unit: MPa) and PC (pressure unit :kgf/cm2) can
alternatively be used. When Pa or MPa is used as the pressure unit, the constant of the
pressure correction term is 1.01325 • 105 and 1.01325 • 10-1 respectively.
When PC is used, the constant of pressure term becomes 1.0332 • 102.

■ ASTM Correction Function
This function executes the correction calculation of the liquid flow.
The details of the ASTM correction function are as follows:
● ASTM Correction (Old JIS) – ASTM1(t,F,C1)

ASM1(t,F,C1) calculates the correction flowrate of flowrate F based on the ASTM correction
(old JIS) for the measured temperature t (C) and the specific gravity (15/4 C specific
gravity) C1. The argument and result are both the double types.
The correction arithmetic expression is shown below:
F0 = Cf • Fi
Cf = 1 + (t - 15) + (t - 15)2
-P1(t) -P3(t)
= +P2(t) = +P4(t)
C1 C1 D024819E.EPS
t: Measured temperature
C1: 15/4 C specific gravity
F0: Corrected flow
P1(t) to P4(t): Temperature-dependent parameters
● ASTM Correction (New JIS) – ASTM2, ASTM3, ASTM4

ASMn(t,F,) calculates the correction flowrate of flowrate F based on the ASTM correction
(new JIS) for the measure temperature t(C) and the density (kg/m3).
“n” of ASTMn can be 2, 3 or 4. ASTM2 is used for the crude oil, ASTM3 for the fuel oil, and
ASTM4 for the lubricating oil. The argument and result are both the double types.
The correction arithmetic expression is shown below:
F0 = Cf • F1
Cf=exp - (t-15) - 0.8 2 (t-15)2

D024820E.EPS
K0 K1
= +
2
D024823E.EPS

t: Measured temperature
: Density at 15 C (kg/m3)
K0, K1: Oil type specific constants

■ High and Low Limit – llimit, dlimit
This function is used to limit the input data value within the limit value range.
The details of the high and low limit function are shown below.
● High and Low Limit

llimit(arg1,arg2,arg3) and dlimit(arg1,arg2,arg3) are used to limit data within the specified
high limit and low limit range. Specify data to arg1, high limit to arg2, and low limit to arg3.
When data, min, and max are used as the arguments, the return value of the
llimit(data,min,max) or dlimit(data,min,max) is shown as follows:
min (when data < min)

Return value of the function = data (when min data max)
max (when data > max)
D024821E.EPS
Because the arguments of “llmit” are converted to the long type, the result will be the long
type.
Because the arguments of “dlmit” are converted to the double type, the result will be the
double type.
An error occurs when arg2 (low limit value) is larger than arg3 (high limit value). In this
case, the return value of the function will be the data value.

■ Step Name Calculation – stpvcalc(arg1,arg2)
stpvcalc(arg1,arg2) is a function that calculates the step name of the sequence table.
“arg1” is converted to a numerical value and the increment of arg2 is added, then the value
is returned after converting to a character string (“00” to “99”).
• arg1: Current step name (char*2 type)
Specify a 2-digit decimal number between “00” and “99” by a character string constant
or a character string variable. If the value is between 0 and 9, add a 0 to make it a two-
digit number.
• arg2: increment (integer type)
Specify the increment by a numeric variable or constant.
The result of “stpvcalc” is always 2-digit decimal number between “00” and “99” (char*2
type). If the value is between 0 and 9, 0 is added. An error occurs if the result of the addition
becomes negative or exceeds 99.
An example of changing PV (step name) of the sequence table SEQ001 is shown below:
program
.....
Assume !SEQ001.PV as “03”.
SEQ001.PV=stpvcalc(SEQ001.PV,1)
* SEQ001.PV becomes “04” after applying +1 to “03.”
......
SEQ001.PV=stpvcalc(SEQ001.PV,2)
* SEQ001.PV becomes “06” after applying +2 to “04.”
......
SEQ001.PV=stpvcalc(SEQ001.PV,-4)
* SEQ001.PV becomes “02” after applying -4 to “06.”
......
end
If “00” is specified to arg1, a character string value converted from the arg2 number can be
obtained.
An example of setting a step name to PV of the sequence table SE002 is shown below:
program
......
SEQ002.PV=stpvcalc(“00”,8)
* SEQ002.PV becomes “08.”
......
SEQ002.PV=stpvcalc(“00”,12)
* SEQ002.PV becomes “12.”
......
end

D2.47.9 Reserved Words for Numerical and Logical Arithmetic

Expressions
The reserved words for the numerical and logical arithmetic expression are the
identifiers that are used as reserved words by the numerical and logical arithmetic
expression compliers.
■ Reserved Words for Numerical and Logical Arithmetic Expressions

▼ Reserved Words
The following table shows the list of reserved words for numerical and logical arithmetic expression:
Table Reserved Word List
ALIAS (D) DMAX (B) P04 (V) RV02 (V)
AND (O) DMIN (B) P05 (V) RV03 (V)
ASTM1 (B) DOUBLE (D) P05C (R) RV04 (V)
ASTM2 (B) ELSE (S) P06 (V) RV05 (V)
ASTM3 (B) ELSE IF (S) P06C (R) RV06 (V)
ASTM4 (B) END (S) P07 (V) RV07 (V)
ATAN (B) ENDIF (S) P07C (R) RV1 (V)
BITPSTN (B) END SWITCH (S) P08 (V) RV2 (V)
BITSRCH (B) EOR (O) P08C (R) RV3 (V)
CASE (S) EXIT (S) P1 (V) RV4 (V)
CHAR (D) EXP (B) P2 (V) RV5 (V)
COS (B) FLOAT (D) P3 (V) RV6 (V)
CPV (V) GOTO (S) P4 (V) RV7 (V)
CPV01 (V) IF (S) P5 (V) SIN (B)
CPV02 (V) INT (B) P5C (R) SQRT (B)
CPV03 (V) INTEGER (D) P6 (V) STPVCALC (B)
CPV04 (V) LABS (B) P6C (R) SWITCH (S)
CPV05 (V) LLIMIT (B) P7 (V) TAN (B)
CPV06 (V) LMAX (B) P7C (R) TC (B)
CPV07 (V) LMIN (B) P8 (V) TCF (B)
CPV1 (V) LOG (B) P8C (R) THEN (S)
CPV2 (V) LONG (D) PC (B) TPC (B)
CPV3 (V) MOD (O) PCKP (B) TPCF (B)
CPV4 (V) NOT (O) PCMP (B) TPCFP (B)
CPV5 (V) OR (O) PCP (B) TPCKP (B)
CPV6 (V) OTHERWISE (S) POWER (B) TPCMP (B)
CPV7 (V) P01 (V) PROGRAM (S) TPCP (B)
DABS (B) P02 (V) RV (V)
DLIMIT (B) P03 (V) RV01 (V)
D024822E.EPS
Note: The letter in parentheses ( ) indicates in which part of the program the reserved word is used.
(D): Declaration statement (S): Statement (B): Built-in function
(O): Operator (V): Variable name (R): Reserved
Even though the data item name such as PV and MV are not included in reserved words by
the compiler, it takes greater program resource to find out when a data item name is used
in the place beyond data item names. It is advised not to use the same character string of
data item names in the program scripts.

Blank Page
<Toc> <Ind> <D3. Sequence Control> D3-1
D3. Sequence Control

Sequence Control Blocks which execute the sequence control include Sequence
Table Blocks, Logic Chart Blocks, SFC Blocks, Switch Instrument Blocks, Sequence
Element Blocks, and Valve Monitoring Block.
This chapter explains details of each type of sequence control block except SFC
Blocks.
SEE ALSO
For details of SFC functions, refer to D5, “Sequencial Function Chart.”
■ Sequence Control ¡ £
The sequence control follows each control step in sequence according to predefined
conditions and order. The function block that executes sequence control function is referred
to as the sequence control block.
The figure below describes the positioning of the sequence control in the basic control.
FCS
Basic control
Software I/O
Regulatory control blocks Common switch
Sequence control blocks Annunciator message
Calculation blocks Sequence control message
Faceplate blocks
Unit instruments
Options
Valve pattern monitoring (*1)
Off-site blocks (*1)
FCS I/O Interfaces
D030001E.EPS
*1: ¡ £ Valve pattern monitorring and off-site blocks are available in CS 3000.
Figure Positioning of Sequence Control in Basic Control ¡ £

<Toc> <Ind> <D3. Sequence Control> D3-2
With sequence control function blocks, the following types of sequence control can be
applied.
• Condition control (monitoring)
Monitors process status and controls it according to pre-defined conditions.
• Program control (phase steps)
Controls according to pre-defined programs (phases).
■ Sequence Control Description Method

The description of the sequence control may be applied to the following function blocks.
● Sequence Table Block

The conditions and operations are arranged in the table format and specifies which opera-
tion is performed by the combination of conditions. This is suitable for the description of all
sequences such as the parallel operation, interlock operation and sequence operation.
● Logic Chart Block

In a logic chart block, the conditions and operations are listed, and the combination of
conditions with the logic operators corresponding to the logic requirement may manipulate
the operation signals. This block can be used as the description of an interlock sequence
control or a logic chart.
● SFC Block
SFC (Sequential Function Chart) block is a function block using SFC for sequence control.
The SFC (Sequential Function Chart) block is a graphical flow diagram suitable for describ-
ing a process control sequence. It is standardized by the international standard, IEC
SC65A/WG6.
The SFC block is used for relatively large-scaled sequence controls and for controlling
devices. The flow of the entire sequence is defined by the SFC block. Each step in the SFC
is described by the sequence table and SEBOL (SEquence and Batch Orientated Lan-
guage).

<Toc> <Ind> <D3.1 Types of Sequence Control Blocks> D3-3
D3.1 Types of Sequence Control Blocks

Sequence Control Blocks include Sequence Table Blocks, Logic Chart Blocks, SFC
Blocks, Switch Instrument Blocks, Sequence Element Blocks and Valve Monitoring
Block.
■ Types of Sequence Control Blocks ¡ £

The table below lists various sequence control blocks.
● Sequence Table Block ¡

This function block realizes sequence control by operating other function blocks and/or
process I/O or software I/O.
The following two models of blocks are categorized as Sequence Table Block.
• Sequence Table Block (ST16)
• Rule Extension Block (ST16E)
● Sequence Table Block £

This function block realizes sequence control by operating other function blocks and/or
process I/O or software I/O.
The following two models of blocks are categorized as Sequence Table Block.
• Sequence Table Block (ST16)
• Rule Extension Block (ST16E)
TIP
In KFCS2, KFCS, LFCS2, LFCS, RFCS5 and RFCS2, the following types of sequence table blocks are
also available other than the above mentioned sequence table blocks.
• Sequence Table Block (M_ST16)
Capacity: Condition Signals: 32 to 64 / Action Signals: 32 to 64 / Total: 96
• Rule- Extension Sequence Table Block (M_ST16E)
• Sequence Table Block (L_ST16)
Capacity: Condition Signals: 64 / Action Signals: 64 / Total: 128
• Rule-Extension Sequence Table Block (L_ST16E)
● Logic Chart Block

This function block performs interlock sequence control programmed in the expression of a
logic chart diagram.
The following model of block is categorized as Logic Chart Block.
• Logic chart with 32 inputs, 32 outputs and 64 logic elements (LC64)

● SFC Block
This function block realizes sequence control by the program described in sequential
function chart.
The following three models of blocks are categorized as SFC Block.
• Three-Position Switch SFC Block (_SFCSW)
• Pushbutton SFC Block (_SFCPB)
• Analog SFC Block (_SFCAS)
● Switch Instrument Block

This function block monitors and operates devices such as opening/closing valves, start/stop
motors or pumps, and final control elements for contacts. 10 types of blocks are available
with various I/O points and output methods, usually used in combination with a sequence
table.
The following ten models of blocks are categorized as Switch Instrument Block.
• Switch Instrument Block with 1 Input (SI-1)
• Switch Instrument Block with 2 Inputs (SI-2)
• Switch Instrument Block with 1 Output (SO-1)
• Switch Instrument Block with 2 Outputs (SO-2)
• Switch Instrument Block with 1 Input, 1 Output (SIO-11)
• Switch Instrument Block with 1 Input , 2 Outputs (SIO-12)
• Switch Instrument Block with 2 Inputs, 1 Output (SIO-21)
• Switch Instrument Block with 2 Inputs , 2 Outputs (SIO-22)
• Switch Instrument Block with 1 Input , 2 One-Shot Outputs (SIO-12P)
• Switch Instrument Block with 2 Inputs , 2 One-Shot Outputs (SIO-22P)
● Sequence Element Blocks

This function block assists with sequence control. It is activated by the sequence table.
The following seven models of blocks are categorized as Sequence Element Block.
• Timer Block (TM)
• Software Counter Block (CTS)
• Pulse Train Input Counter Block (CTP)
• Code Input Block (CI)
• Code Output Clock (CO)
• Relational Expression Block (RL)
• Resource Scheduler Block (RS)
● Valve Monitoring Block (VLVM)

This function block monitors valve opening and closing, and starts an alarm when abnor-
mal conditions are detected.

D3.1.1 Alarm Processing of Sequence Control Blocks

Various alarm processing type of sequence control blocks are listed in the following
table.
■ Alarm Processing of Sequence Control Blocks

Table Alarm Processing of Sequence Control Blocks
Process alarms
N O I I H L H L D D V V M M C Other
Model R O O O H L I O V V E E H L N alarms
P P P + – L L I O F
– + –
ST16
ST16E
LC64
SI -1

SI-2
SO-1

SO-2
SIO-11
SIO-12
SIO-21 PERR
ANS+
SIO-22 ANS-
SIO-12P
SIO-22P
TM
CTS
CTP
CI
CO
RL
RS
VLVM
D030002J.EPS
: available
The alarm status of ST16, LC64, TM and VLVM blocks are always indicated as NR (stands
for Normal status).

D3.1.2 Block Mode of Sequence Control Blocks

Various modes of sequence control blocks are listed in the following table.
■ Block Mode of Sequence Control Blocks

Table Block Mode of Sequence Control Blocks
O I T M A C P R R
S A K N T S D A U
N S T
ST16 Sequence table (basic section) block

ST16E Rule extension block
LC64 Logic chart block
SI-1 Switch instrument block with 1 input

SI-2 Switch instrument block with 2 inputs
SO-1 Switch instrument block with 1 output
SO-2 Switch instrument block with 2 outputs
SIO-11 Switch instrument block with 1 input and 1 output
SIO-12 Switch instrument block with 1 input and 2 outputs

SIO-21 Switch instrument block with 2 inputs and 1 output
SIO-22 Switch instrument block with 2 inputs and 2 outputs
SIO-12P Pulse type switch instrument block with 1 input and 2 outputs
SIO-22P Pulse type switch instrument block with 2 inputs and 2 outputs
TM Timer block
CTS Software counter block
CTP Pulse train input counter block
CI Code input block

CO Code output block
RL Relational expression block
RS Resource scheduler block
VLVM 16-valve monitor block
D030003E.EPS
: valid
Blank: Invalid

<Toc> <Ind> <D3.2 Sequence Table Block (ST16, ST16E)> D3-7
D3.2 Sequence Table Block (ST16, ST16E)

Sequence Table Blocks (ST16, ST16E) controls the monitoring of processing and the
phase step sequences by connecting with other function blocks, process I/O, and
software I/O.
■ Sequence Table Block (ST16, ST16E)

Sequence Table Block (ST16, ST16E) is a decision table type function block that describes
the relationship between input signal and output signal in a Y/N (yes/no) fashion. By mak-
ing sequence connection with other function blocks, they control the monitoring of process-
ing and phase step sequences. Sequence Table Blocks include the basic ST16, and
ST16E that is only used for rule extension.
The figure below shows the function block diagram of Sequence Table Blocks (ST16,
ST16E).
Q01 Rule 1 ...... 32 J01

Y N
Q02 J02
YN
Q03 Input Output J03
processing Y processing
NY
Q64 Logic operation J64
D030201E.EPS
Figure Function Block Diagram of Sequence Table Block (ST16, ST16E)
The table below lists connection methods and destinations for Sequence Table Blocks
(ST16, ST16E) I/O terminals.
Table Connection Methods and Destinations for Sequence Table Block (ST16, ST16E) I/O
Terminals
I/O Status Terminal
terminal Data Data Condition Process Software Function
manipula- connecti-
reference setting testing I/O I/O block
tion on
Q01 to Q56
J01 to J56
D030202E.EPS

I/O connection is set by describing connection information and data in the input connection
information setting area, condition specification setting area, output connection information
setting area, and operation specification setting area of the sequence table displayed in the
sequence table edit window of the Function Block Detail Builder.
Rule number 01 02 03 04 05 06 07 08 32
No. Tag name Data Step label
Data item
Comment
Input Condition
connection specification Condition rule setting area
information setting area
setting area
Output Operation
connection specification
information setting area
setting area
Action rule setting area
D030203E.EPS
Figure Conceptual Diagram of Sequence Table
Two types of blocks are available in the Sequence Table Block (ST16, ST16E).
• ST16: Sequence Table Block
• ST16E: Rule Extension Block

● Sequence Table Block (ST16)
The Sequence Table Block (ST16) has a sequence control function that handles a total of
64 I/O signals, 32 rules. It can also change distribution of the 64 I/O signals and output
signals in the 8-signal unit. The total number of I/O signals is fixed to 64. Thus, a sequence
table with only eight inputs and eight outputs cannot be created.
● Rule Extension Block (ST16E)

This function block is used for rule extensions of the Sequence Table Block (ST16). It
connects to an extending Sequence Table Block (ST16) as an extended sequence table to
form a sequence table group.
Because the Rule Extension Block (ST16E) is managed by the Sequence Table Block
(ST16) that is an extending sequence table, it cannot be activated independently.
The Rule Extension Block (ST16E) only allows connection to a step-type extending Se-
quence Table Block (ST16) on which step labels is described. Nonstep-type Sequence
Table Blocks (ST16) cannot be connected.

■ Rule Expansion
When the phase step sequence table is used, the number of processes (number of steps)
may be insufficient depending on the process that is being performed. At this time, use the
rule expansion format Sequence Table Block (ST16E) which enables the number of rules
to be expanded.
The following figure shows when the rule expansion of sequence tables.
ST16 ST16E
Rule 01 ... ... ... ... ... ... 32 Rule 01 ... ... ... ... ... 3132
Symbol Step 01 ... ... ... ... ... ... 15 Symbol Step 16 ... ... ... ... ... ... 35
C01 C01
• •
• E1 G1 • E1 G2
• •
C32 C32
A01 A01
• •
• H1 J1 • H1 J2
• •
A32 A32
THEN THEN
ELSE ELSE
NEXT Expansion destination sequence table name
Expansion source sequence table Expansion destination sequence table
D030204E.EPS
Figure Example of Sequence Table Expansion

D3.2.1 Sequence Table Configuration

Sequence tables consist of condition signals, action signals, rule numbers, condi-
tion rules, action rules and step labels.
■ Complete Sequence Table Configuration

▼ Sequence Table Configuration
The figure below shows the complete sequence table.
Processing timing Scan period
Rule number 01 02 03 04 05 06 07 08 32
Tag name
No. Data Step label
Data item
Condition signal Comment
C01 TM14.BSTS RUN
Condition rule
C02 FC001.ALRM HI
C03 %SW0201.PV ON
C03
C04
Action signal
A01 ST90.MODE AUT

A02 %AN0010.PV H
Action rule
A03
A04
A05
Extension rule tag name THEN label

NEXT ELSE label
Next step label
D030205E.EPS
Figure Conceptual Diagram of Complete Sequence Table

■ Outline of Sequence Table Elements ¡ £
The following describes various sequence table elements.
● Condition Signal
Enter the element symbol and data item into the Tag name. Data item column as the input
connection information, then enter the condition specification to Data column.
● Action Signal
Enter the element symbol and data item into the Tag name. Data item column as the input
connection information then enter the action specification to Data column.
● Rule Number
Up to 32 rules per block may be used. The output is based on each rule condition and
condition testing result.
● Condition Rule
Describe the Y/N (Y: true, N: false) pattern (combination) to condition rule. If the testing
result of condition signal corresponds with the Y/N pattern, the condition of the rule is
satisfied.
● Action Rule
Describe the Y/N ( Y: Positive action; N: Negative action) pattern (combinations) to action
rule. Perform manipulated output according to the Y/N pattern of the action rule for the rule
number whose condition is satisfied.
● Step Label
▼ Step
These labels are attached for phase identification purposes when performing step se-
quence control using a sequence table. Step labels are character strings that combine two
or less alphanumeric characters (A to Z, 0 to 9).
If two characters are combined while one is not alphanumeric and the other is alphanu-
meric, the label is managed as the same step name, even if the order of characters is
reversed (e.g., “_A” and “A_”).
Up to 100 steps can be described in one sequence table group. However, same step labels
cannot be described at multiple locations inside the sequence table group.
The step labeled 00 is activated every scan cycle.

● Next Step Label
▼ THEN, ELSE
Describe the step label that is to be executed in the next scan.
Next step labels include THEN and ELSE labels according to case conditions being true or
false. If both labels are blank, the step does not transfer.
• THEN label
Describe the next step label when the corresponding rule condition status is true.
Transition to the step described in the THEN label is executed after the manipulated
output is completed.
• ELSE labels
Describe the next step label when the corresponding rule status is false.
The described step labels must exist in the same sequence table group. To execute a step
from another sequence table group at the next scan, it must be described as an action
signal.
● Tag Name.Data Item

Describe the input connection information of the condition signal or the output connection
information of the action signal.
● Data
Describe the condition specification of the condition signal or the operation specification of
the action signal.
● Comment
Comments are defined by users for the condition and action signals. The meaning of
symbols and the contents of status manipulation may be put in these texts, by using up to
24 single-byte alphanumeric characters, or 12 double-byte characters.
By clicking the task [Referencing Signal Comment] from the [Tool] menu, the user-defined
comment text may be displayed at the right area of signals. By this Referencing Signal
Comment operation, the comment texts defined by users for the condition signals and
action signals and the tag comments are all displayed. The comment text for the refer-
enced signals can not be edited on the sequence table editing window.
IMPORTANT
Specify an element number with the number of digits specified for each element to a
condition or action signal. If the number without the highest digit’s “0” is specified to a
condition or action signal, a reference signal comment is not displayed.
TIP
A referenced signal comment is not stored in a builder file. To reference a comment, select [Referencing
Signal Comment] from the [Tool] menu.

● Processing Timing
The processing timing of a sequence table consists of start timing and output timing.
Start timing refers to the timing at which control algorithms of the sequence table are
executed upon receipt of input signals. Output timing indicates the conditions under which
action signals are output at the time a periodic start type or one-shot start type sequence
table is executed.
“Start Timing” and “Output Timing” are set for each sequence table.
• Start Timing:
Select either “Periodic Execution Type (T),” “One-shot Processing Type (O),” “Startup
at Initial Cold Start/Restart (I)” or “Restricted Initial Execution Type (B).”
• Output Timing:
Select either “Output Only When Conditions Change (C)” or “Output Each Time
Conditions are Satisfied (E).”
● Scan Period ¡
Periodic start sequence tables are activated at defined scan period. Among the periodic
started sequence tables, the sequence tables activated in the basic period have the items
“Control Period” and “Control Phase” to be defined in addition to scan period.
“Scan Period,” “Control Period,” and “Control phase” can be defined for each sequence
table.
• Scan Period: Select from “Basic Scan” or “High-speed Scan.”
• Control Period: 1 to 16 seconds.
• Control Phase: 0 to 15 seconds.
● Scan Period £
Periodic start sequence tables are activated at defined scan period. Among the periodic
started sequence tables, the sequence tables activated in the basic period have the items
“Scan Period,” “Control Period,” and “Control phase” can be defined for each sequence
table.
• Scan Period:
Select from “Basic Scan”, “Medium-speed Scan” (*1) or “High-speed Scan.”
• Control Period: 1 to 16 seconds.
• Control Phase: 0 to 15 seconds.
*1: £ “Medium-speed Scan” is only supported by KFCS2, KFCS, LFCS2 and LFCS.

● Extension Rule Tag Name
▼ NEXT
Described by 16 or less alphanumeric characters.
SEE ALSO
• For sequence block processing timing, refer to C7.3, “Process Timing for Sequence Control Block.”
• For details on scan period, refer to C7.1.1, “Scan Period.”
• For details on control period and control phase, refer to C7.3.5, “Control Period and Control Phase for
Sequence Table Blocks (ST16, ST16E).”
■ Sequence Description Example

The basic logical circuit figure for the AND and OR commands is described in the sequence
table as shown in the following figure.
01 02 03
No Tag Name and Data Item Data

C01 %SW0200.PV ON Y N
%SW0200 Condition C02 %SW0201.PV ON Y N
ON %Z011101 C03
ON
%SW0201 A01 %Z011101.PV H Y N N
ON AND Action A02
A03
D030206E.EPS
Figure AND Circuit Example
In the example in this figure, for AND operator, only when two condition signals are satis-
fied, the operation may be performed.
01 02 03
No Tag Name and Data Item Data

C01 %SW0200.PV ON Y N
%SW0200 Condition C02 %SW0201.PV ON Y N
ON %Z011101 C03
ON
%SW0201 A01 %Z011101.PV H Y Y N
ON OR Action A02
A03
D030207E.EPS
Figure OR Circuit Example
In the example in this figure, for OR operator, any one of the two conditions is established,
the operation may be performed.

D3.2.2 Creating a Sequence Table

To create a sequence table, enter the input information for sequence control in each
setting area of the sequence table edit window of the Function Block Detail Builder.
■ Configuration of Sequence Table Edit Window

The figure below shows the configuration of the sequence table edit window.
Process timing setting area Step label setting area

Signal setting column heading Rule number display area STEP
Condition signal
number
display area Condition signal setting area Condition rule setting area
Action signal
number
display area Action signal setting area Action rule setting area
Next step label setting area THEN
NEXT Extension table setting area

Next step label setting area ELSE
D030208E.EPS
Figure Configuration of Sequence Table Edit Window
To create a sequence table, the information (condition signals, action signals, condition rule
and action rules) for sequence connection and the information (condition rule and action
rules) for logic calculation should be entered to each setting area of the sequence table edit
window.
The setting area are listed below.
• Processing timing setting area
• Step label setting area
• Condition signal setting and action signal setting area
• Condition rule setting and action rule setting area
• Extension table setting area
• Next step label setting area (THEN, ELSE)

■ Processing Timing Setting Area
Processing timing and scan period are displayed in the processing timing setting area.
Processing timing and scan period may be defined on the processing timing setting dialog
box.
A display example of processing timing setting dialog is shown below.
Processing timing
Processing timing
Execution timing Periodic execution

Output timing Output only at condition change
Scan period
Scan period Basic scan

Control period
Control phase
OK Cancel
D030209E.EPS
Figure Processing Timing Setting Dialog
SEE ALSO
For details of processing timing, refer to C7.3, “Process Timing for Sequence Control Block.”

■ Step Label Setting Area
Enter the step label in the step label setting area using 2 or less alphanumeric characters.
■ Condition Signal Setting Area and Action Signal Setting Area

Enter the condition signal and action signal into each line that displays the signal number in
the condition signal setting area and action signal setting area.
■ Condition Rule Setting Area and Action Rule Setting Area

Enter Y/N pattern condition rule and action rule respectively, in the condition rule setting
area and the action rule setting area.
To enter the condition rule and action rule, click on the input location. The display alternates
between “Y,” “N” and “.” as it is clicked. When a “.” is displayed, it means that no Y/N pattern
has been entered yet.
SEE ALSO
• For details of condition rules, refer to D3.2.5, “Condition Rule Processing of Sequence Table.”
• For details of action rules, refer to D3.2.6, “Action Rule Processing of Sequence Table.”
■ Extension Table Setting Area

Enter the tag name of the extended sequence table in the extended sequence table setting
area.
The rules of the extending and extended sequence tables are connected and the rule
numbers that can be used in the sequence table are then extended, if the tag name of the
extended sequence table is entered.
SEE ALSO
For details of rule extension, refer to D3.2.9, “Rule Extension.”
■ Next Step Label Setting Area (THEN, ELSE)

Enter a 2 digits alphanumeric number directly to the next step label setting area.

D3.2.3 Sequence Table Processing Flow

In the sequence table, condition rule processing and action rule processing are
performed based on the results of input processing. Output processing is then
performed for the action target.
■ Sequence Table Processing Flow

▼ Sequence Table Processing Flow
The figure below shows the sequence table processing flow.
Input processing
(condition testing)
Condition rule processing
....... Y
....... Y
....... N
....... Y
Action rule processing
Output processing
(status manipulation)
D030210E.EPS
Figure Sequence Table Processing Flow
The true/false status of the condition signal is determined by performing condition testing
based on the input signal.
● Condition Rule Processing

The true/false status of the rule condition is determined by comparing the true/false status
of the condition signal with the Y/N pattern of the condition rule described in the sequence
table.
● Action Rule Processing

The action signal output is determined by the Y/N pattern of the action rule when the status
of condition is true.
Status manipulation of the action target is performed based on the description of the action
signal. The status manipulation, start command transmission, data setting, and status
change can be performed to the contact outputs and other function blocks.
There are two types of sequence tables: step and nonstep. Rule processing differs by the
type of sequence table.

■ Operations of Non-Step Sequence
In a non-step sequence table, all 32 rules are subject to condition testing, and the operation
is performed according to the conditions. The following shows the operation of a non-step
sequence table.
Rule 01 … … … … … … 32
Step
C01 All rule numbers are
. subject to condition testing.
.
. Condition signal
C32
A01 Only the rules whose conditions
. are satisfied are executed.
. Operation signal
.
A32
THEN
ELSE
D030211E.EPS
Figure Operation of NonStep Sequence Table
• As for condition testing, a condition is satisfied when all conditions (Y or N) for the
same rule number are true. A sequence table whose rule columns are all blank is
considered true unconditionally.
• Operations are executed according to the operation contents of Y or N described for
the rule number whose conditions are satisfied.
• When the output timing is specified as “Output Only When Conditions Change,” the
operation is executed only once when the condition is switched from false to true.
However, if non-latched output is specified for the operation signal, the operation
changes when the condition is switched from true to false.
• When the output timing is specified as “Output Each Time Conditions are Satisfied,”
the operation is executed during each period as long as the condition remains true.
• When the conditions of multiple rules are satisfied simultaneously with respect to the
same operation signal, if requests for both Y and N are detected as the resultant
operations, the request for Y takes precedence, and the operation for N will not be
executed.
01 02 03
No Tag Name.Data Item Data

C01 %SW0100.PV ON Y When %SW0100 and %SW0101 turn on simultaneously,
Conditions C02 %SW0101.PV ON Y %SW0200 turns on.
C03 The Y operation takes precedence.
A01 %SW0200.PV H Y N
Operations A02
A03
D030212E.EPS
Figure Example of Operation for Simultaneous Requests

■ Example of the Non-Step Format Sequence Using the Sequence Table
An example of the sequence that normally monitors operations to prevent the buffer tank in
the processing piping system from overflow is shown in the following figure. In this se-
quence, LI100 (indication block) alarm status is used.
VALVE-A open command

FCS
Limit switch (LS-A, Open)
HH
LI H
Inflow valve 100 L
VALVE-A LL
PVI
Differential Pressure
transmitter
LT100
Limit switch (LS-B, open)

Outflow valve
VALVE-B VALVE-B open command
Next process
D030213E.EPS
Figure Example of Process Flow Figure
Flow inflow valve - Open Outflow valve - Open

Inflow valve - Closed
Level High - High limit alarm %AN0001
AND
Level - High limit alarm %AN0002
Level - Low limit alarm %AN0003
Level Low - Low limit alarm Outflow valve - Open

Inflow valve - Closed
Outflow valve - Open %AN0004
AND D030214E.EPS
Figure Example of Condition Logic Diagram

The condition logic diagram of the previous page is described as below used the sequence
table.
Processing Timing TC .... Scan Period Basic Scan

Rule Number
No Tag Name - Data Item Data Comment 01 02 03 04
C01 LS-A.PV ON Inflow valve limit switch Y

C02 LS-B.PV ON Outflow valve limit switch Y
C03 LI100.ALRM HH Y
C04 LI100.ALRM HI Y
C05 LI100.ALRM LO Y
C06 LI100.ALRM LL Y
A01 VALVE-A.PV H Inflow valve open command N Y

A02 VALVE-B.PV H Outflow valve open command Y N
A03 %AN0001 L Upper level, high-limit alarm Y
A04 %AN0002 L Level, high-limit alarm Y
A05 %AN0003 L Level, low-limit alarm Y
A06 %AN0004 L Lower level, low-limit alarm Y
D030215E.EPS
Figure Non-step Sequence Table Example
The sequence table in the figure shown above monitors the conditions in rule numbers 01
to 04 simultaneously. Any condition in one of the 4 rules becomes true, the operation in the
same rule will be executed again. The monitoring continues after the execution.

■ Action of Step Sequence
In a step sequence table, the process control sequence of a phase-step process is divided
into the smallest phase units (steps) of the condition monitoring and operation, then these
steps are executed one by one.
In a step sequence table, only step label 00 and the rule corresponding to the current step
number are subject to condition testing and operation. The following shows the action of a
step sequence table.
Rule 01 … … … … … … 32
Step 01 02 03 04
C01 Only the step currently being executed is
. subject to condition testing.
.
. Condition signal
C32
A01 Only the operations for the rules whose conditions are
. satisfied in the step currently being executed, are executed.
. Operation signal
.
A32
THEN
ELSE
D030216E.EPS
Figure Action of Step Sequence Table
• Step label 00 is executed during each period. Step 00 may only be described at the
head of a sequence table group. Step 00 cannot be described as a next step label.
• For step sequences, the next execution step label must be described in THEN/ELSE
in order to advance the steps. The step will not be advanced if both next step labels in
THEN/ELSE are blank. If there is no description for the next step label, the same step
is executed each time, the sequence does not move step.
• The next step specified in THEN is the step to advance when the condition test result
in positive. When all operations for the corresponding rules are completed, the step
proceeds to the next step.
• The next step specified in ELSE is the step to advance when the condition test result
in negative. When conditions for the corresponding rules are established, the step
proceeds to the next step without executing the operation rules.
• If there are multiple requests for step transition in the same step, the step advances to
the next step label that is described for the smallest rule number.
• When a step is advanced, the conditions for the rules are initialized once. In other
words, all the conditions become false with respect to the previous execution.
• The timing in which the next step is actually executed after a step is advanced, is the
next scan period.

• The same step label can be assigned to multiple rules. In this case, branched opera-
tions can be performed according to the condition.
01 02 03 04 05
A A A
No Tag Name.Data Item Data 1 2 3
C01 %SW0100.PV ON Y N If %SW0100 is on at step label A1,
Condition C02 it turns on %SW0200 and advances the step.
C03 If %SW0100 is off,
Y N it turns off %SW0200 and advances the step.
A01 %SW0200.PV H
Operation A02
A03
A A
THEN
2 3
ELSE
D030217E.EPS
Figure Example of Conditional Branch

■ Example of a Step Sequence that Uses the Sequence Table
This figure shows an example of the phase step sequence that combines the water injec-
tion processing and drain processing.
Sequence Specifications
Push the start button, valve A opens to fill water to the tank. When the tank is full, switch A
becomes ON, the valve is closed.
Push the start button again when the tank is full, then the valve B opens.
When the drain process ends, switch B becomes ON, the valve B closes.
FCS
Start button
(PB001)
Valve A
(VLVA)
Switch A
(SWA)
Switch B
(SWB)
Valve B
(VLVB)
To the next process

D030218E.EPS
Figure Example of Process Flow

Sequence start
Start button No
(PB001)
Yes
Valve A: Open (VLVA)
Water injection processing (Step label A1)
Switch A level Hi No
(SWA)
Yes
Valve A: Open (VLVA)
Start button No
PB001
Yes
Valve B: Open (VLVS)
Water drain processing (Step label A2)
Switch B level Lo No
(SWB)
Yes
Valve B: Close (VLVS)
D030219E.EPS
Figure Example of Sequence Flow Chart

The sequence flow chart of the previous page is described as below used the sequence
table.
Rule Number 01 02 03 04 05 06
Process Timing TC .... Scan Period Basic Scan A A
STEP
No Tag Name - Data Item Data Comment 1 2
C01 PB001.PV ON Start Button Y Y

C02 SWA.PV ON Switch A (Level HI) N Y Y
C03 SWB.PV ON Switch A (Level LO) N
C04
C05
C06
A01 VLVA.PV H Valve A Y N

A02 VLVB.PV H Valve B Y N
A03
A04
A05
A06
A A
THEN
2 1
Destination Step Label
ELSE
D030220E.EPS
Figure Example of Step Sequence Table
In the above sequence table, rule numbers 01 and 02 are step A1. Rule numbers 03 and
up are step A2. Rule numbers 05 and beyond do not have any description for the condition
rule, operation rule or move-destination step label, so they are not subject to condition
testing nor operation.
Step A1 monitors the conditions for rule numbers 01 and 02 simultaneously. Of rule num-
bers 01 and 02, whichever the condition is satisfied will be executed. Executing the opera-
tion of rule 01 does not advance the step, since there is no designation in the move-desti-
nation step label. After executing the operation, A1 resumes monitoring rule numbers 01
and 02 again. On the other hand, if the condition for rule number 02 becomes true, the
operation of rule 02 will be executed, and the step advances to A2 because the move-
destination step label has a designation.

D3.2.4 Input Processing of Sequence Table

In input processing, the true/false status of a condition signal is determined by
performing condition testing on each of the multiple input terminals.
■ Input Processing of Sequence Table

In input processing, condition testing is performed on the condition signal of the rules
subject to execution, in order to retain the true/false status of the condition signal in the
form of a logical value. The label of a step that is to be executed is described on the rule
subject to execution. When the step label is not described in the step column of the se-
quence table, all rules are subject to the execution rule.
For all rule conditions except those subject to execution, the status of the condition signal is
considered “false” regardless of the status of the connection destination.
The table below lists the results of condition testing when error occurs during input pro-
cessing.
Table Descriptions of Input Processing Errors and Condition Testing Results
Input processing results and

Error Descriptions
effect on condition signal processing
• When the condition signal is not described • The status of the condition signal is set “true”
• When there is an error in the testing condition • The result of the condition signal processing is set
of the condition signal unconditionally “true” regardless of the Y/N pattern
• When the necessary input signal for condition • Maintain the state of previous input processing
testing was unavailable (*1) • Condition signal processing is performed based on the
• When one-shot execution was not available previous test result
D030221E.EPS
*1: The following describes factors that do not allow input signals.
• When the database of the connection destination or element is abnormal.
• When the connection destination or process I/O is undergoing online maintenance.
A system alarm occurs when referencing the result of one-shot execution at the connection
destination fails due to the following:
• When the nest referring from a referenced sequence table to other sequence
table exceeds seven levels including the referencing sequence table;
• When the connection destination block mode is out of service (O/S); or
• When the connection destination is undergoing maintenance.

IMPORTANT
When a function block of the connection destination and/or a process I/O is undergoing
maintenance, input signals cannot be obtained. When performing maintenance, and before
performing online loading, be sure to set related function blocks to manual (MAN) mode or
perform any processing that stops executions in order to execute an online load.
The true/false status of the condition signal is maintained as the previous input value within
the sequence table. However, when the necessary input signal for condition testing is
unavailable, or when one-shot execution of the connection destination function block is
unavailable, the previous input value used in condition testing as in the case shown below
will not be the expected value.
• When the sequence table itself is a one-shot execution type, or when the function
block of the connection destination is a one-shot execution type while the block mode
is out of service (O/S), it might have been long since the previous input value was
obtained. If so, the value obtained from the previous one-shot execution remains to be
the previous input value.
• When the sequence table itself is a one-shot execution type, or when the function
block of the connection destination is a one-shot execution type while the block mode
is out of service (O/S), if no one-shot execution was performed, the previous input
value is 0.
• Immediately after a step is changed in the step-type sequence table, always set the
previous input value to 0 (false) before performing the condition testing.

D3.2.5 Condition Rule Processing of Sequence Table

In the condition rule processing, the true/false status of each rule condition is deter-
mined by comparing for each rule the true/false status of condition signals and the
condition rules.
■ Condition Rule Processing of Sequence Table

An example of condition rule processing is shown below.
Rule number True/false status True/false status of condition signal...condition testing result:
01 02 03 04 true (1). false (0)
of condition signal
True/false status of condition.....True/false status of conditionsignal
Condition signal 1 1 Y Y in one rule corresponds with the Y/N
Condition signal 2 0 Y Y pattern in the same rule.
Condition signal 3 1 Y N
True/false condition status 0 0 1 0 As shown in the figure left, the true/false status of the condition
signal corresponds with the Y/N pattern in Rule 03 only.
Action signal 1 Y N The Y operation in action signal 2 is, therefore, performed.
Action signal 2 Y
Action signal 3 N
D030222E.EPS
Figure Example of Condition Rule Processing
● Comparing the True/False Status of Condition Signals and Condition

Rules
The comparison content differs by the Y/N pattern of the condition signal described in the
condition rule.
• When Y is described in the condition signal.
If the status of the condition signal obtained by input processing is true (1), the condi-
tion is satisfied.
• When N is described in the condition signal.
If the status of the condition signal obtained by input processing is false (0), the
condition is satisfied.
● Determining the True/False Status of Conditions

Only rules with satisfied conditions are subject to action rule processing. When all Y/Ns of a
condition described in the rule of the same number are satisfied, the status of the rule
condition is true (1). If even one of them is not satisfied, the status is false (0).

D3.2.6 Action Rule Processing of Sequence Table

For each rule number for which the condition part is true (satisfied), the correspond-
ing output signals are decided by the Y/N pattern in the action part of the rule.
■ Action Rule Processing of Sequence Table - ST16, ST16E

The output action signal based on the Y/N pattern is determined in the action rule process-
ing.
Rule number True/false status True/false status of condition signal...condition testing result:
01 02 03 04 true (1). false (0)
of condition signal
True/false status of condition.....True/false status of conditionsignal
Condition signal 1 1 Y Y in one rule corresponds with the Y/N
Condition signal 2 0 Y Y pattern in the same rule.
Condition signal 3 1 Y N
True/false condition status 0 0 1 0 As shown in the figure left, the true/false status of the condition
signal corresponds with the Y/N pattern in Rule 03 only.
Action signal 1 Y N The Y operation in action signal 2 is, therefore, performed.
Action signal 2 Y
Action signal 3 N
D030223E.EPS
Figure Example of Condition Rule Processing
Of the rules with true status of condition, only action signals described with Y or N in action
rules will be output targets.
When “Output Only when Conditions Change” is specified for output timing, rules whose
true/false status of condition is changed can be action targets.
The content of status manipulation in the sequence table is decided by the Y/N pattern,
while those of status manipulation in other sequence control blocks differ by the true/false
logical calculation result.

D3.2.7 Output Processing of Sequence Table

In output processing, the action target is manipulated by outputting the action
signal obtained by action rule processing.
■ Output Processing of Sequence Table

In output processing, by outputting action signals, the action target is manipulated based
on the action target and action specifications described in the action signal column. The
manipulation for the action target is called status manipulation.
When errors occur in output processing while performing operations such as changing the
block mode of a function block for which a block mode change interlock is specified, status
manipulations to the target blocks are not performed.
If one action signal is tested by multiple rules, and both Y and N actions are requested, Y
has higher priority. In this case, Y is executed but N is ignored.
Also, a system alarm occurs when one-shot execution fails due to the reasons indicated
below:
• When the nest executing from an executed sequence table to other sequence table
exceeds seven levels including the executing sequence table;
• When the connection destination block mode is out of service (O/S); or
• When the connection destination is undergoing maintenance.

D3.2.8 Number of Condition Signals and Action Signals

Up to 32 condition signals and 32 action signals for a total of 64 signals can be
described in one Sequence Table Block (ST16).
When more than 32 condition signals or 32 action signals must be described, the
allocation of the number of condition signals and action signals totaling 64 can be
changed in units of eight signals.
■ Number of Condition Signals and Action Signals

▼ Number of Signals
There are 32 action signals and 32 condition signals in each Sequence Table Block (ST16).
However, allocation of the number of signals can be changed in the 8-signal unit using the
signal selection dialog which is called from the Function Block Detail Builder.
• Select Number of Signals: Sets allocation of the number of I/O signals in the 8-signal
unit.
Table Combination of Condition Signal and Action Signal Counts

Condition signal count Action signal count
8 56
16 48
24 40
32 (default) 32 (default)
40 24
48 16
56 8
D030224E.EPS
The signal count selection dialog box is displayed by selecting [Change Number of Signal
Lines] from the [View] menu in the Function Block Detail Builder.
A display example of the signal line selection dialog box is shown below.
Select Number of Signal Lines
Condition signal = 32, Operation signal = 32
OK Cancel
D030225E.EPS
Figure Example of Signal Line Selection Dialog Box
IMPORTANT
Condition signal and action signal information may be lost if the signal count is decreased
by changing signal count allocation.
The message shown below is displayed when information may be lost.
• Type: warning
• Description:
“Some of the existing definition information will be lost by changing this setting. Is it
OK to change?”

D3.2.9 Rule Extension

In the sequence table, up to 32 rules can be set to test condition signals and action
signals.
When describing information in the sequence table, if more than 32 rules are re-
quired in one phase of a sequence control that is being described in the sequence
table, the number of rules can be extended.
■ Rule Extension
The number of rules in one sequence table is fixed at 32 and cannot be modified. However,
if the number of rules in a sequence table is not enough to describe one phase unit, it can
be extended in the 32-rule unit by connecting to another sequence table. The number of
rules can be extended for a step-type sequence table.
● Method of Rule Extension

To extend the number of rules, specify a tag name for the rule extension block (ST16E) in
the sequence table setting area of the extending sequence table (ST16). It does not matter
if the number of signals and signal contents are different between the extending sequence
table (ST16) and extended sequence table (ST16E).
The number of rules can be extended in the 32-rule unit per block.
An example of the number of rules extended to 64 is shown below.
Extending table Extending table Extended table
ST16 ST16 ST16E

condition side condition side condition side
ST16 ST16 ST16E
operation side operation side operation side
D030226E.EPS
Figure Examples of Rule Extension
● Sequence Table Group

Multiple sequence tables connected for rule extension are referred to as a sequence table
group.
Up to 100 steps can be described in one sequence table group. The number of rules
cannot be extended over 100 steps. A step name cannot be described more than once in a
sequence table group (not in both extending table and extended table).
● Editing an Extended Sequence Table

An extended sequence table (ST16E) can be opened by selecting [Open the next exten-
sion table] from the [display] menu in the Function Block Detail Builder. To enter information
for sequence connection, the method used in an extended sequence table (ST16E) can
also be used in the extending sequence table (ST16).

■ Restrictions on Rule Extension
This section explains the restrictions on rule extension.
● Restrictions on the Number of Steps

Rule extension is required in the step-type sequence tables. Up to 100 steps can be de-
scribed in the step-type sequence table. Even when the step-type sequence table is ex-
tended for rule extension, the maximum number of describable steps is limited to 100
within a sequence table group.
If it is necessary to describe over 100 steps in a step-type sequence table, create another
step-type sequence table to allow execution of the second table continued from the first
table.
There are no restrictions on the number of tables. However, in consideration of the perfor-
mance of sequence table execution, the number of connected tables in the sequence table
group should be as small as possible.
● Restrictions on Step Label

The same step label cannot be described in more than one step label setting area within a
sequence table group. The step executed over two sequence tables or more cannot be
described, either.
If a step cannot be described within one sequence table, decrease processing to be ex-
ecuted in a step and describe a step label indicating that the next step starts from a newly
extended sequence table.
● Restrictions on Rule Extension Table

The rule extension sequence table block should be created in the same control drawing
with the original sequence table block. If the rule extension sequence block is created in a
drawing different from the original sequence block, on HIS, the status display of the original
sequence block can not be extended to the rule extension sequence block.
SEE ALSO
For more information about control drawings, see F3. “Control Drawing Builder.”

D3.2.10 Condition Signal Description: Referencing Other

Function Blocks and I/O Data
In the condition testing in which other function blocks are referenced, various data,
block mode and status can be referenced. I/O data such as process I/O, software I/O,
communication I/O can also be referenced.
■ Function Blocks and I/O Data that can be Referenced from a Sequence
Table
▼ Conditional Signal Description
Function blocks that can be referenced from a sequence table are shown below.
• Switch Instrument Blocks
• Code Output Block (CO)
• Valve Monitoring Block (VLVM)
• Regulatory Control Blocks
• Calculation Blocks
• Faceplate Blocks
• SFC Blocks
• Unit Instrument Blocks
• Sequence Table Blocks
• Logic Chart Blocks
In addition, the following I/O data can be referenced from the sequence table.
• Processing I/O (contact I/O)
• Software I/O (internal switch, annunciator message)
• Communication I/O
The following should be taken into account when referencing a sequence table block
mode.
• When O/S is specified in the condition specification for block mode reference, the test
result will be unsatisfied in the compound block mode in which O/S and another basic
block mode are satisfied simultaneously.
• When MAN or AUT is specified in the condition specification for block mode reference,
the test result is satisfied even in the compound block mode as long as the specified
basic block mode is established.

■ Switch Instrument Block Reference
The table below lists the condition signal symbolic convention for referencing various data
and status of switch instrument block as well as the conditions for true Y/N described in the
condition rule.
Table Condition Signal Symbolic Convention and Conditions for True Y/N Described in Condition
Rule (1/2)
Condition signal description column Condition
Condition rule Conditions for true status
Input signal column
specification
Y Answerback value coincides with specification.
Element symbol.PV 0, 1, 2
N Answerback value does not coincide with specification.
Y Data status coincides with specification.
Element symbol.PV =Data status
N Data status does not coincide with specification.
Y Output value coincides with specification.
Element symbol.MV 0, 1, 2
N Output value does not coincide with specification.
Element symbol.MV =Data status
Y Tracking switch is in specified state.
Element symbol.TSW 0, 1
N Tracking switch is not in specified state.
Element symbol.TSW =Data status
Y Backup switch is in specified state.
Element symbol.BSW 0, 1
N Backup switch is not in specified state.
AUT, MAN, CAS, Y Block mode coincides with specification.

Element symbol.MODE
ROUT, TRK, O/S N Block mode does not coincide with specification.
Y Block is in ROUT (MAN) mode.
BUM
N Block is not in ROUT (MAN) mode.
Y Block is in ROUT (AUT) mode.
Element symbol.XMODE BUA
N Block is not in ROUT (AUT) mode.
Y Block is in ROUT (CAS) mode.
BUC
N Block is not in ROUT (CAS) mode.
Y Block status coincides with specification.
Element symbol.BSTS NR, SIM, ANCK
N Block status does not coincide with specification.
D030227E.EPS

Rule (2/2)
Input signal specification Condition
NR, IOP, OOP, ANS+, Y Specified alarm is activated.

Element symbol.ALRM
ANS-, PERR, CNF N Specified alarm is not activated.
Y Alarm is in IOP or IOP- status.
Element symbol.XALRM IOP
N Alarm is in neither IOP nor IOP- status.
PERR, AFL (*1), NR, Y Specified alarm is flashing.
Element symbol.AFLS IOP, OOP, ANS+,
ANS-, CNF N Specified alarm is not flashing.
NR, IOP, OOP, ANS+, Y Specified alarm detection is off.

Element symbol.AF
ANS-, PERR, CNF N Specified alarm detection is on.
Y IOP or IOP- detection is disabled.
Element symbol.XAF IOP
N IOP or IOP- detection is enabled.
NR, IOP, OOP, ANS+, Y Specified alarm is masked.
Element symbol.AOFS CNF, ANS-, PERR,
AOF (*2) N Specified alarm is unmasked.
Y Sequence setting value coincides with specification.
Element symbol.CSV 0, 1, 2
N Sequence setting value does not coincides with specification.
Element symbol.CSV =Data status
N Data status does not coincides with specification.
Y Remote manipulated output value coincides with specification.
Element symbol.RMV 0, 1, 2 Remote manipulated output value does not coincides with
N specification.
Element symbol.RMV =Data status
Y Bypass switch is in specified state.
Element symbol.BPSW 0, 1
N Bypass switch is not in specified state.
Element symbol.BPSW =Data status
D030228E.EPS
*1: Condition Specification AFL references the group flashing status.

*2: Condition Specification AOF references the alarm group mask status.

■ Timer Block Reference (TM)
and status of the Timer Block (TM) and the conditions for true Y/N described in the condi-
tion rule.
Rule

rule Conditions for true status
Input signal Condition specification column
Y Block mode coincides with specification.
Element symbol.MODE AUT, O/S
N Block mode does not coincide with specification.
STOP, RUN, PAUS, Y Block status is in specified state.

Element symbol.BSTS
NR, PALM, CTUP
N Block status is not in specified state.
Y Alarm status is in specified state.
Element symbol.ALRM NR
N Alarm status is not in specified state.
Y Specified alarm is flashing.
Element symbol.AFLS AFL (*1), NR
N Specified alarm is not flashing.
Y Specified alarm detection is off.
Element symbol.AF NR
N Specified alarm detection is on.
Y Specified alarm is masked.
Element symbol.AOFS NR,AOF (*2)
N Specified alarm is unmasked.
D030229E.EPS

■ Software Counter Block Reference (CTS)

and status of the Software Counter Block (CTS) as well as the conditions for true Y/N
described in the condition rule is shown below.
Rule

Y Block status is in specified state.
STOP, RUN, NR,
Element symbol.BSTS
PALM, CTUP N Block status is not in specified state.
D030230E.EPS

■ Pulse Train Input Counter Block Reference (CTP)
and status of the Pulse Train Input Counter Block (CTP) as well as the conditions for true Y/
N described in the condition rule.
Rule
STOP, RUN, PAUS, Y Block status is in specified state.

Element symbol.BSTS
NR, PALM, CTUP
Element symbol.ALRM CNF, NR, IOP
Element symbol.XALRM IOP
AFL (*1), CNF, NR, Y Specified alarm is flashing.

Element symbol.AFLS
IOP N Specified alarm is not flashing.
Element symbol.AF CNF, NR, IOP
N IOP and IOP- detection is enabled.
CNF, NR, IOP, Y Specified alarm is masked.

Element symbol.AOFS
AOF (*2) N Specified alarm is unmasked.
D030231E.EPS


■ Code Input Block Reference (CI)
and status of the Code Input Block (CI) as well as the conditions for true Y/N described in
the condition rule.
Rule

Element symbol.BSTS NR, LO, HI, ERR
D030232E.EPS
■ Code Output Block Reference (CO)

and status of the Code Output Block (CO) as well as the conditions for true Y/N described
in the condition rule.
Rule

Element symbol.BSTS NR, LO, HI
D030233E.EPS

■ Relational Expression Block Reference (RL)
and status of the Relational Expression Block (RL) as well as the conditions for true Y/N
described in the condition rule.
Rule

EQ, GT, GE, LT, LE, Y Relationship between two data is in specified state.
Element symbol.X01 to 16 AND N Relationship between two data is not in specified state.
D030234E.EPS
The table below lists the description of condition specifications.

Table Description of Condition Specifications
EQ equal data 1=data 2
GT greater than data 1>data 2
GE great than or equal to data 1*data 2
LT less than data 1<data 2
LE less than or equal to data 1)data 2
AND logical product bitwise logical product of data 1 and 2
D030235E.EPS
■ Resource Scheduler Block Reference (RS)

and status of the Resource Scheduler Block (RS) as well as the conditions for true Y/N
Rule

Usage request status coincides with specification.

Y
Element symbol.RQ01 to 32 0, 1 (0: Not requested, 1: Requesting)
N Usage request status does not coincide with specification.
Permission status coincides with specification.
Y
Element symbol.PM01 to 32 0, 1 (0: Not permitted, 1: Permitted)
N Permission status does not coincide with specification.
Maximum permissible number coincides with
Y
specification.
Element symbol.RMH 0 to 32
Maximum permissible number does not coincide with
N
specification.
D030236E.EPS

■ Valve Monitoring Block Reference (VLVM)
and status of the Valve Monitoring Block (VLVM) as well as the conditions for true Y/N
Rule

Y Specified alarm is activated.
N Specified alarm is not activated.
Y Alarm is flashing.
Element symbol.AFLS NR, AFL (*1)
N Alarm is not flashing.
Element symbol.AOFS NR, AOF (*2)
Valve normal/abnormal state coincides with specification.
Y
(0: Normal, 1: Abnormal)
Element symbol.PV01 to 16 0, 1
Valve normal/abnormal state does not coincide with
N
specification.
Representative valve normal/abnormal state coincides
with specification.
Y
(0: All valves are normal, 1: At least one of the alarms is
Element symbol.PVR 0, 1 abnormal)
Representative valve normal/abnormal state does not
N
coincide with specification.
Message suppression coincides with specification.
Y
Element symbol.MCSW 0, 1 (0: Not suppressed, 1:Suppressed)
N Message suppression does not coincide with specification.
D030237E.EPS


■ Regulatory Control Block Reference
The table below lists the condition signal symbolic convention for referencing the block
mode, block status, alarm status, and data status of the regulatory control block as well as
the conditions for true Y/N described in the condition rule.
Rule

Y Block mode is in specified state.
Element symbol.MODE Block mode
N Block mode is not in specified state.
Y Block is in ROUT (MAN) or RCAS (MAN) mode
BUM
N Block is not in ROUT (MAN) or RCAS (MAN) mode
Y Block is in ROUT (AUT) or RCAS (AUT) mode
N Block is not in ROUT (AUT) or RCAS (AUT) mode
Y Block is in ROUT (CAS) or RCAS (CAS) mode
BUC
N Block is not in ROUT (CAS) or RCAS (CAS) mode
Y Block status is in specified state.
Element symbol.BSTS Block status
Element symbol.ALRM Alarm status
IOP
Element symbol.XALRM
Y Alarm is in VEL or VEL- status.
VEL
N Alarm is in neither VEL nor VEL- status.
Element symbol.AFLS Alarm status, AFL (*1)
Element symbol.AF Alarm status
Element symbol.AOFS Alarm status, AOF (*2)
Y Data value coincides with specification.
Element symbol.Data item Data value
N Data value does not coincide with specification.
Element symbol.Data item =Data status
D030238E.EPS


● Regulatory Control Block that can Describe Data Values in Condition
Specifications
The table below lists the regulatory control blocks that can describe data values in condi-
tion specifications and the setting ranges of data items.
Table Regulatory Control Blocks that can Describe Data Values in Condition Specifications and
the Setting Ranges of Data Items (1/3)
Block code Name Data item Setting range

TSW 0, 1
CSW 0, 1
PID PID Controller Block PSW 0 to 3
RSW 0, 1
BSW 0, 1
TSW 0, 1
CSW 0, 1
PID-HLD Sampling PI Controller Block PSW 0 to 3
RSW 0, 1
BSW 0, 1
TSW 0, 1
CSW 0, 1
PID-BSW PID Controller Block with Batch Switch PSW 0 to 3
RSW 0, 1
BSW 0, 1
CSW 0, 1
PID-TP Time-Proportioning ON/OFF Controller Block PSW 0 to 3
BSW 0, 1
PSW 0 to 3
BSW 0, 1
PSW 0 to 3
ONOFF-G 3-Position ON/OFF Controller Block
BSW 0, 1
TSW 0, 1
PSW 0 to 3
RSW 0, 1
BSW 0, 1
TSW 0, 1
PSW 0 to 3
PI-BLEND Blending PI Controller Block RSW 0, 1
BSW 0, 1
RST 0, 1
TSW 0, 1
CSW 0, 1
PSW 0 to 3
RSW 0, 1
BSW 0, 1
STC -1 to 3
D030239E.EPS


TSW 0, 1
RSW 0, 1
TSW 0, 1
RSW 0, 1
TSW 0, 1
MLD-SW Manual Loader Block with Auto/Man SW PSW 0 to 3
RSW 0, 1
TSW 0, 1
BSW 0, 1
BPSW 0 to 4
MC- 2 2-Position Motor Control Block SIMM 0 to 1
CSV 0 to 2
PV 0 to 2
MV 0 to 2
TSW 0, 1
BSW 0, 1
BPSW 0 to 4
MC-3 3-Position Motor Control Block SIMM 0 to 1
CSV 0 to 2
PV 0 to 2
MV 0 to 2
TSW 0, 1
PSW 0 to 3
RSW 0, 1
BSW 0, 1
ZONE 1 to 13
PG-L13 13-Zone Program Set Block ZSTR 1 to 13
ZEND 1 to 13
D030240E.EPS

SW 0 to 4
BSETU-2 Flow-Totalizing Batch Set Block EMSW 0, 1
ZONE 0 to 11
SW 0 to 4
BSETU-3 Weight-Totalizing Batch Set Block EMSW 0, 1
ZONE 0 to 11
PSW 0 to 3
VELLIM Velocity Limiter Block BSW 0, 1
BPSW 0, 1
SW 0 to 4
SS-H/M/L Signal Selectors
SEL 0 to 3
PSW 0 to 3
AS-H/M/L Auto Selectors SW 0 to 4
SEL 0 to 3
SW 1 to 3
SEL 1 to 2
TSW 0, 1
PSW 0 to 3
FSW 0, 1
RSW 0, 1
TSW 0, 1
XCPL Non-Interference Control Output Block PSW 0 to 3
RSW 0, 1
BSW 0, 1
SW 0 to 3
SW 0 to 5
ALM-R Representative Alarm Block
SV 0 to 15
D030241E.EPS

■ Calculation Block Reference ¡ £
The table below lists the condition signal symbolic convention for referencing the block
mode of calculation block, block status, alarm status, and data status, as well as the condi-
tions for true Y/N described in the condition rule is shown below.
Rule


Element symbol.BSTS RUN, STOP
IOP
VEL
Element symbol.AOFS Alarm status, AOFS (*2)
Y Calculation result is not 0.
Element symbol.ACT ON
N Calculation result is 0.
Element symbol.data item Data value (*3)
Y Data status coincides with the status of specified data.
Element symbol.data item =Data status Data status does not coincide with the status of specified
N
data.
D030242E.EPS

*3: Only integers can be a data value. If the data item is a floating decimal point, the value is rounded off for comparison.

● Calculation Blocks that can Describe Data Values in Condition
Specifications ¡ £
The table below lists the data items of Calculation Blocks that can describe data values in
condition specifications and their setting ranges.
Table Calculation Blocks that can Describe Data Values in Condition Specifications and Setting
Range of Data Items (1/2) ¡ £
DLAY-C Dead-Time Compensation Block RST 0, 1
SW 0, 1, 2
SW-33 Three-Pole Three-Position Selector Switch Block SW 0 to 3
SW 0 to 3
SW-91 One-Pole Nine-Position Selector Switch Block SW 0 to 9
SW 0 to 16
DSW-16C Selector Switch Block for 16 String Data
SW 0 to 17
D030243E.EPS

Table Calculation Blocks that can Describe Data Values in Condition Specifications and Setting
Range of Data Items (2/2) £
AND (*1) Logical AND Block RV1 0, 1
RV2 0, 1
CPV 0, 1
OR (*1) Logical OR Block RV1 0, 1
RV2 0, 1
CPV 0, 1
NOT (*1) Logical NOT Block RV 0, 1
CPV 0, 1
SRS1-S (*1) Set-Dominant Flip-Flop Block with 1 Output RV1 0, 1
RV2 0, 1
CPV1 0, 1
SRS1-R (*1) Reset-Dominant Flip-Flop Block with 1 Output RV1 0, 1
RV2 0, 1
CPV1 0, 1
SRS2-S (*1) Set-Dominant Flip-Flop Block with 2 Outputs RV1 0, 1
RV2 0, 1
CPV1 0, 1
CPV2 0, 1
SRS2-R (*1) Reset-Dominant Flip-Flop Block with 2 Outputs RV1 0, 1
RV2 0, 1
CPV1 0, 1
CPV2 0, 1
WOUT (*1) Wipeout Block RV1 0, 1
RV2 0, 1
CPV 0, 1
OND (*1) ON-Delay Timer Block RV 0, 1
CPV 0, 1
OFFD (*1) OFF-Delay Timer Block RV 0, 1
CPV 0, 1
TON (*1) One-Shot Block (Rising-Edge Trigger ) RV 0, 1
CPV 0, 1
TOFF (*1) One-Shot Block (Falling-Edge Trigger ) RV 0, 1
CPV 0, 1
GT (*1) Comparator Block (Greater Than) CPV 0, 1
GE (*1) Comparator Block (Greater Than or Equal) CPV 0, 1
EQ (*1) Equal Operator Block CPV 0, 1
D030244E.EPS
*1: £ The Logic Operation Blocks are only applicable to CS 3000.

● Calculation Blocks that can Reference Calculation Results by One-Shot
Execution ¡ £
The table below lists Calculation Blocks that can reference calculation results by one-shot
execution of the condition signal, “element symbol. ACT.ON.”
Table One-Shot Executable Blocks for Condition Testing ¡ £
ADD Addition Block
Arithmetic calculation
DIV Division Block
AVE Averaging Block
OR Logical OR Block
SRS1-S Set-Dominant Flip-Flop with 1 Output
SRS1-R Reset-Dominant Flip-Flop 1 Output
SRS2-S Set-Dominant Flip-Flop with 2 Outputs
Logic Calculation (*1) SRS2-R Reset-Dominant Flip-Flop 2 Outputs

WOUT Wipeout Block
General-Purpose CALCU General-Purpose Calculation Block

Calculations CALCU-C General-Purpose Calculation Block with String I/O
D030245E.EPS
*1: ¡ £ The Logic Operation Blocks are only applicable to CS 3000.

■ Faceplate Block Reference
and status of the faceplate block, as well as the conditions for true Y/N described in the
condition rule.
Rule

Y Block is in ROUT (MAN) or RCAS (MAN) mode.
BUM
N Block is not in ROUT (MAN) or RCAS (MAN) mode.
Y Block is in ROUT (AUT) or RCAS (AUT) mode.
N Block is not in ROUT (AUT) or RCAS (AUT) mode.
Y Block is in ROUT (CAS) or RCAS (CAS) mode.
BUC
N Block is not in ROUT (CAS) or RCAS (CAS) mode.
Y Specified alarm is on.
N Specified alarm is not on.
IOP
VEL
1 to 99 Y Phase step number coincides with specification.

Element symbol.SV
(Only BSI block is valid) N Phase step number does not coincide with specification.
Y Operation command coincides with specification.
Element symbol.PV01 to 10 0, 1
N Operation command does not coincide with specification.
Element symbol. Y Switch display color coincides with specification.

0 to 15
SWCR[n] (*3) N Switch display color does not coincide with specification.
Element symbol. Y Switch flashing status coincides with specification.

0, 1
SWST[n] (*3) N Switch flashing status does not coincide with specification.
Y Switch operation disabled status coincides with specification.
Element symbol.
-15 to 15 Switch operation disabled status does not coincide with
SWOP[n] (*3) N
specification.
D030246E.EPS

*3: n is the subscript of the 1 dimensional array. This subscript is the number of the push button switches on a faceplate
block. This number varies with the type of faceplate block.

■ SFC Block Reference
and status of the SFC block as well as the conditions for true Y/N described in the condition
rule.
Rule

Y Block mode is in specified state.
Element symbol.MODE MAN, SEMI, AUT, O/S
N Block mode is not in specified state.
RUN, PAUS, STOP, Y Block status is in specified state.
Element symbol.BSTS ABRT
Element symbol.Data item Data value

D030247E.EPS

● Setting Range of Data Item When Describing Data Value in Condition

Specification
The table below lists the data items of SFC block that can describe data values in condition
specifications and their setting ranges.
• STEPNO: 1 to 99
• SWCR[5]: 0 to 15
• SWST[5]: 0, 1
• SWOP[5]: -15 to 15

■ Unit Supervision Reference
and status of the unit instrument block as well as the conditions for true Y/N described in
the condition rule.
Rule

Y Unit mode is in specified state.
Element symbol.MODE MAN, SEMI, AUT, O/S
N Unit mode is not in specified state.
Y Unit status is in specified state.
Element symbol.BSTS Unit status
N Unit status is not in specified state.
Element symbol.AOFS Alarm status, AOFS (*2)
Y SFC step number coincides with specification.
Element symbol.STEPNO 1 to 99
N SFC step number does not coincide with specification.
D030248E.EPS


■ Processing I/O Reference
and status of the processing I/O block as well as the conditions for true Y/N described in
the condition rule.
Rule

ON/OFF status of contact I/O coincides with
Y
specification.
Element symbol.PV ON, OFF
ON/OFF status of contact I/O does not coincide with
N
specification.
Y Data status of contact I/O coincides with specification.
Element symbol.PV =Data status Data status of contact I/O does not coincide with
N
specification.
D030249E.EPS
■ Global Switch Reference £

The syntax for applying the various types of data and data status of a global switch as
condition test reference signal in a sequence table and the True/False representation of Y/
N in the condition rule columns of the sequence table are shown as follows.
Table Syntax for condition signal description and True/False representation of Y/N in condition
rule columns

Y Specified global switch status is True.
N Specified global switch status is False.
Y Data status of global switch is BAD.
Element symbol.PV =BAD
N Data status of global switch is not BAD.
D030250E.EPS
■ Common Switch Reference

and status of the common switch as well as the conditions for true Y/N described in the
condition rule.
Rule

ON/OFF status of common switch coincides with
Y
specification.
N ON/OFF status of common switch does not coincide with
specification.
D030251E.EPS

■ Annunciator Message Reference
and status of the annunciator message as well as the conditions for true Y/N described in
the condition rule.
Rule

Annunciator occurrence status coincides with
Y specification.
Element symbol.PV ON, OFF (ON: Occurred, OFF: Not occurred)
Annunciator occurrence status does not coincide with
N
specification.
Y Flashing status
element symbol.AFLS AFL
N Normal status (not flashing)
Y Alarm masking status
element symbol.AOFS AOF
N Normal status (no alarm masking status)
Repeated warning status coincides with specification.
Y
(ON: Waiting for repeated warning, OFF: NR)
element symbol.RP ON, OFF
Repeated warning status does not coincide with
N
specification.
D030252E.EPS
■ Communication I/O Reference

and status of communication I/O as well as the conditions for true Y/N described in the
condition rule.
Rule

Y All relevant bits are in the same ON/OFF status.
Element symbol.PV (*1) ON, OFF
N Relevant bits are not in the same ON/OFF status.
Y All relevant bits are in the same data status.
N Relevant bits are not in the same data status.
D030253E.EPS
*1: Only discrete type element may be referred.

D3.2.11 Control Signal Description: Referencing Sequence Table

In a condition testing referencing a sequence table, in addition to the sequence table
block mode and status, the true/false status of condition can also be referenced by
performing one-shot execution of the referenced sequence table.
To reference a sequence table whose number of rules is extended over multiple
sequence tables, specify a tag name for the extending sequence table.
■ Referencing an Entire Sequence Table

▼ Conditional Signal Description - Sequence Table
The true/false status of condition for the entire sequence table specified is referenced.
The table below lists the condition signal symbolic convention for referencing the entire
sequence table and the conditions for true Y/N described in the condition rule.
Rule

Y At least one target condition rule is satisfied.
Element symbol. SD R
N None of the target condition rules is satisfied.
D030254E.EPS
The condition rule subject to referencing varies by the type of sequence tables at reference
source and destination (step type/nonstep type) as shown below.
Table Reference Target Rules by Sequence Table Type
Reference source Reference destination Reference target rule
Nonstep type All rules
Nonstep type
Step type Rule of Step 00
Step type Rule of Step 00 and that of the same step
Step type
name as reference source
D030255E.EPS

The following should be taken into account when referencing the entire sequence table.
• When referencing the entire sequence table, only condition signal descriptions of the
referenced sequence table are valid. Ignore any action signal description.
• If no Y/N pattern exists in the condition rule of referenced sequence table, the status of
rule condition is false. If the Y/N pattern of such condition rule is unspecified, the
status becomes unconditionally true in the periodic processing of the above sequence
table.
• When there exist no steps to be executed in the referenced sequence table, the
previous true/false status of condition is maintained as a current reference result.
• When Step 00 exists in the reference destination, rules that belong to Step 00 will also
be executed. However, when no steps exist as an execution target, the reference
result of Step 00 is ignored.
• Other sequence tables can be referenced in the referenced sequence table condition
column. In this case, up to seven levels of nests (including the first sequence table)
are possible.

● When the Referenced Sequence Table is a Nonstep Type
A description example of the nonstep-type referenced sequence table is shown below.
ST 003 ST 010
Rule number 01 02 03 04 05 Rule number 01 02 03 04 05

Tag name Tag name
Data
Data item Data Step label Data item Step label
Comment Comment
DI0010.PV ON ................................ Y Y Y N DI0030.PV ON ............................. Y Y N
DI0015.PV ON ................................ Y N DI0031.PV ON ............................. Y Y N
ST010.SD R ................................ Y N DI0036.PV ON ............................. Y N N Y
DI0018.PV ON ................................ N Y Y %SW0201.PV ON ............................. Y N Y
DO0001.PV H ................................ Y N
DO0011.PV H ................................ Y N
D030256E.EPS
Figure Description Example of Referencing the Entire Nonstep-Type Sequence Table
The following describes the condition testing processing for the above example.
• When “Y” is described in the condition rule of the condition signal ST010.SD.R.
In the description of the condition signal of the referenced sequence table, if there
exists at least one rule with a true status, the status of condition signal is true. If no
such rules exist, the condition of the referencing sequence table is false.
As for Rule 01 in Table ST003 listed above, the output signal of DO0001 is ON if the
condition signal DI0010.PV.ON is true, DI0015.PV.ON is true, DI0018.PV.ON is false,
and one of the conditions at rules 01 to 32 of Table ST010 is true.
• When “N” is described in the condition rule of the condition signal ST010.SD.R.
In the description of the condition signal of the referenced sequence table, if there
exists no rule with a true status, the status of condition signal is true. If there exists at
least one rule with a true status, the condition of the referencing sequence table is
false.
As for Rule 03 in Table ST003 listed above, the output signal of DO0001 is OFF if the
condition signal DI0010.PV.ON is true, DI0015.PV.ON is false, and none of the condi-
tions at rules 01 to 32 of Table ST010 is true.
• The condition of rules that has no Y/N patterns in Table ST010 is false.

● When the Referenced Sequence Table is a Step Type
A description example of the step-type referenced sequence table is shown below.
When both sequence tables at reference source and destination are a step type, the true/false
status of Step 00 rule condition and that of the rule with the same step name as the refer-
ence source is referenced.
ST 003 ST 010

Tag name Tag name
Data
Data item Data Step label 1 2 3 4 Data item Step label 1 1 2 3
Comment Comment
ST010.SD R ................................ Y N DI0036.PV ON ............................. Y N N Y
DO0001.PV H ................................ Y N
DO0011.PV H ................................ Y N
D030257E.EPS
Figure Description Example of Referencing the Entire Nonstep-Type Sequence Table
• As for Rule 01 in Table ST003, the output signal of DO0001 is ON if the condition
signal DI0010.PV.ON is true, DI0015.PV.ON is true, DI0018.PV.ON is false, and one
of the conditions at Rule 01 or 02 of Table ST010 is true.
• As for Rule 03 in Table ST003, the output signal of DO0001 is OFF if the condition
signal DI0010.PV.ON is true, DI0015.PV.ON is false, and the condition at Rule 04,
Step 3 of Table ST010 is false.

● When Step 00 and Step n Exist in a Referenced Sequence Table
A description example of when Step 00 and Step n exist in a referenced sequence table is
shown below.
ST 003 ST 010

Tag name Tag name
Data Data item Data
Data item Step label 1 Step label 0 0
2 3 4 1 2 3
Comment 0 0
Comment
DI0010.PV ON ................................ Y Y Y N DI0030.PV.ON ON ............................. Y Y N N
DI0015.PV ON ................................ Y N DI0031.PV.ON ON ............................. Y Y N N
ST010.SD R ................................ Y N DI0036.PV.ON ON ............................. Y N N Y N
DI0018.PV ON ................................ N Y Y %SW0201.PV ON ............................. Y N Y N
DO0001.PV H ................................ Y N
DO0011.PV H ................................ Y N
D030258E.EPS
Figure Description Example of Referencing the Entire Step-Type Sequence Table
• The reference range of the referenced table at Rule 01, Table ST003 is steps 00 and 1
of Table ST010.
As for Rule 01 in Table ST003 listed above, the output signal of DO0001 is ON if the
condition signal DI0010.PV.ON is true, DI0015.PV.ON is true, DI0018.PV.ON is false,
and one of the conditions at Step 00 Rule 01/02 or Step 1 Rule 03 of Table ST010 are
true.
• The reference range of the referenced table at Rule 03 of Table ST003 are steps 00
and 3 of Table ST010.
As for Rule 03 in Table ST003 listed above, the output signal of DO0001 is OFF if the
condition signal DI0010.PV.ON is true, DI0015.PV.ON is false, and the condition at
Step 00 Rule 01/02 or Step 3 Rule 05 of Table ST010 are false.

■ Referencing Sequence Table Corresponding Rule Number
The true/false status of condition for the same rule number as the current rule number in
the referencing sequence table is referenced. Use this to extend the number of condition
signals beyond 64 in a nonstep-type sequence table.
The table below lists the condition signal symbolic convention for referencing the true/false
status of the conditions for the corresponding rule number and the conditions for true Y/N
status described in the condition rule.
Rule

Y Condition for the same rule number is satisfied.
Element symbol. SD C
N Condition for the same rule number is not satisfied.
D030259E.EPS
• When the referenced sequence table is a nonstep type and the referencing sequence
table is a step type.
Although referencing a corresponding rule number is meaningless, condition refer-
ence to the corresponding rule is executed.
• When the referenced sequence table is a step type.
Referencing the same rule is meaningless and therefore causes an error. However,
the status of condition signal is true.
The following should be taken into account when referencing a corresponding rule number.
referenced sequence table are valid. Ignore any action signal description.
rule condition is false. If the Y/N pattern of such a condition rule is unspecified, the
table.
are possible.

A description example of when referencing the true/false status of conditions for a corre-
sponding rule number is shown below.
ST 003 ST 010

Tag name Tag name
Data item Data Step label 1 Data item
Data
Step label
2 3 4
Comment Comment
ST010.SD C ................................ Y N DI0036.PV ON ............................. Y N N Y
DO0001.PV H ................................ Y N
DO0011.PV H ................................ Y N
D030260E.EPS
Figure Description Example of Referencing the Corresponding Rule Number
signal DI0010.PV.ON is true, DI0015.PV.ON is true, DI0018.PV.ON is false, and the
conditions at Rule 01 of Table ST010 are true.
signal DI0010.PV.ON is true, DI0015.PV.ON is false, and the conditions at Rule 03 of
Table ST010 are false.
IMPORTANT
When referencing a corresponding rule number, do not describe the step number on the
step label of the referenced sequence table.
When referencing a corresponding rule number, referencing cannot be properly performed
if the step number is described on the step label of the referenced sequence table.

■ Referencing a Particular Step in a Sequence Table
The true/false status of conditions for a particular step of a specified sequence table is
referenced.
The table below lists the condition signal symbolic convention for referencing the true/false
status of conditions for a particular step, and the conditions for true Y/N described in the
condition rule. The step label is specified in the condition specification.
Rule

At least one of the conditions for steps 00 and xx is
Y
Element symbol. SA XX satisfied.
N None of the conditions for steps 00 and xx is satisfied.
D030261E.EPS
xx: Specify a step label using 2 or less alphanumeric characters.
The condition rule subject to referencing varies by the type of sequence table at reference
source and destination (step-type/nonstep type) as shown below.
Table Reference Target Rules by Sequence Table Type
Reference source Reference destination Reference target condition rule
Nonstep type
Step type Rules of a specified step
Step type
Step type Rules of a specified step
D030262E.EPS
• When the specified step does not exist in the referenced sequence table, the refer-
ence result will be the previous true/false condition status that has been latched.
• When Step 00 exists in the reference destination, the rules belonging to Step 00 will
also be executed. However, when the specified step does not exist in the referenced
sequence table, the reference result of Step 00 is ignored.
The following should be taken into account when referencing a particular step.
• When referencing a particular step in the sequence table, only condition signal de-
scriptions of the referenced sequence table are valid. Ignore any action signal descrip-
tion.
table.
are possible.

A description example of referencing the true/false status of conditions for a particular step
number is shown below.
ST 003 ST 010

Tag name Tag name
Data item Data Data item Data
Step label 1 2 3 4 Step label 1 1 2 3
Comment Comment
DI0010.PV ON ................................ Y Y Y N DI0030.PV ON .............................. Y Y N
DI0015.PV ON ................................ Y N DI0031.PV ON .............................. Y Y N
ST010.SA 2 ................................ Y N DI0036.PV ON .............................. Y N N Y
DI0018.PV ON ................................ N Y Y %SW0201.PV ON .............................. Y N N Y
DO0001.PV H ................................ Y N
DO0011.PV H ................................ Y N
D030263E.EPS
Figure Description Example of Referencing a Particular Step Number
signal DI0010.PV.ON is true, DI0015.PV.ON is true, DI0018.PV.ON is false, and the
conditions for Step 2, or Rule 03 of Table ST010 are true.
signal DI0010.PV.ON is true, DI0015.PV.ON is false, and the conditions for Step 2, or
Rule 03 of Table ST010 are false.

● When Steps 00 and n Exist in the Referenced Sequence Table
A description example of the sequence table when steps 00 and n exist in the referenced
sequence table are shown below.
ST 003 ST 010

Tag name Data Tag name Data
Data item Step label 1 2 3 4 Data item Step label 0 0
1 2 3
Comment Comment 0 0
DI0010.PV ON ................................ Y Y Y N DI0030.PV ON ............................... Y Y N N

DI0015.PV ON ................................ Y N DI0031.PV ON ............................... Y Y N N
ST010.SA 2 ................................ Y N DI0036.PV ON ............................... Y N N Y N
DI0018.PV ON ................................ N Y Y %SW0201.PV ON ............................... Y N Y N
DO0001.PV H ................................ Y N
DO0011.PV H ................................ Y N
D030264E.EPS
Figure Description Example of Referencing a Particular Step Number
The table reference range for the rule number 01 of Table ST003 are steps 00 and 2 of
Table ST010 in the above example.

■ Sequence Table Step Label Reference
The progress status of a sequence phase can be confirmed by referencing the sequence
table step label. However, such confirmation does not involve the true/false status of step
conditions since it only determines whether or not a specified step processing is being
performed in the referenced sequence table.
The table below lists the condition signal symbolic convention for referencing the step label
and the conditions for true Y/N described in the condition rule.
Rule

Y Current execution step label is xx.
Element symbol.PV xx
N Current execution step label is other than xx.
D030265E.EPS
A description example of referencing the execution status of Step 1 processing in Table

ST010 is shown below.
ST 003
Rule number 01 02 03 04 05 06 07
Tag name
Data Step label
Data item
Comment
SW0110.PV ON ................................ Y Y
Condition
ST010.PV 1 ................................ Y N
ST010.SA 1 ................................ Y
Operation
SW0110 H ................................ N
D030266E.EPS
Figure Description Example of Step Label Reference

■ Sequence Table Block Mode Reference
The table below lists the condition signal symbolic convention for referencing the sequence
table block mode, and the conditions for true Y/N described in the condition rule.
Rule

Y Block mode is in the specified state.
Element symbol.MODE O/S, MAN, AUT
N Block mode is not in the specified state.
D030267E.EPS
A description example of restarting Table ST005 from the stop status is shown below.
Rule number 01 02 03 04 05 06 07
Tag name
Data Step label
Data item
Comment
ST005.MODE MAN .............................. Y
%SW0201.PV ON .............................. Y Condition
ST005.MODE AUT .............................. Y

Operation
D030268E.EPS
Figure Description Example of Block Mode Reference
The following should be taken into account when referencing a sequence table block
mode.
• When O/S is specified in the condition specification for block mode reference, the test
result will be unsatisfied in the compound block mode in which O/S and another basic
block mode are satisfied simultaneously.
• When MAN or AUT is specified in the condition specification for block mode reference,
the test result is satisfied even in the compound block mode as long as the specified
basic block mode is satisfied.

■ Sequence Table Alarm Status Reference
The table below lists the condition signal symbolic convention for referencing the sequence
table alarm status and the conditions for true Y/N described in the condition rule.
Rule

Y Alarm status is in the specified state.
N Alarm status is not in the specified state.
Y Specified alarm detection is canceled.
N Specified alarm is being detected.
D030269E.EPS


D3.2.12 Syntax for Condition Signal Description: Logic Chart

Reference in Sequence Table
When using logic chart for condition test, a block mode of a logic chart and an alarm
status of a logic chart can be used as a reference signal in a sequence table.
■ Logic Chart Block Mode Reference

▼ Conditional Signal Description - Logic Chart
The specified logic chart block mode can be used as reference signal in a sequence table.
The syntax for applying the logic chart block mode as condition test reference signal in a
sequence table and the True/False representation of Y/N in the condition rule columns of
the sequence table are shown as follows.
Table Syntax for Condition Signal Description and True/False Representation of Y/N in Condition
Rule Columns

Y Specified Block mode is True.
N Specified Block mode is False.
D030270E.EPS
The following points should be taken into consideration when referencing a logic chart
block mode.
• When O/S is specified as the condition specification for block mode reference, the test
result will be False when the block is in the compound block mode, i.e., O/S and
another basic block mode exist simultaneously.
• When MAN or AUT is specified as the condition specification for block mode refer-
ence, the test result will be True even in the compound block mode as long as the
specified basic block mode exists.

■ Logic Chart Alarm Status Reference
The specified alarm status of logic chart can be used as reference signal in a sequence
table.
The syntax for applying the alarm status of logic chart as condition test reference signal in a
sequence table and the True/False representation of Y/N in the condition rule columns of
Rule Columns

Y Specified Alarm Status is True.
Element symbol.ALM NR
N Specified Alarm Status is False.
Y Specified Alarm symbol is flashing.
N Specified Alarm symbol is not flashing.
Y Alarm Detection Disabled is True.
N Alarm Detection Disabled is False.
Y Alarm Inhibition is True.
N Alarm Inhibition is False.
D030271E.EPS
*1: The condition test for Alarm Symbol Flashing can only test the flashing status of each block or symbol, can not test the
flashing status of each alarming item.
*2: The condition test for Alarm Inhibition can only test the inhibition status of each block or symbol, can not test the
inhibition status of each alarming item.

D3.2.13 Description of Action Signal: Status Manipulation for

Other Function Blocks and I/O Data
Sequence Table Block may manipulate the mode or status change of other function
blocks. In addition, it can also manipulate the status change of process I/O, software
I/O and communication I/O.
■ Function Blocks and I/O Data for Which Status Manipulation can be
Performed from Sequence Table
▼ Action Signal Description
Function blocks for which status manipulation can be performed from the sequence table
are:
• Switch Instrument Blocks
• SFC Blocks
I/O data for which status manipulation can be performed from the sequence table are:
• Process I/O
• Software I/O (internal switch, annunciator message, sequence message output)

■ Status Manipulation of Switch Instrument Block
The table below lists the symbolic convention of action signal and action description for
executing status manipulation on various switch instrument block functions.
Table Symbolic Convention of Action Signal and Action Description
Action signal description column Action rule
column Action description
Output signal Action specification (Y/N)
MAN, AUT, CAS, Y Block mode change command

Element symbol.MODE
ROUT, O/S N –
ANS+, ANS-, IOP, Y Cancel specified alarm detection

Element symbol.A.F
PERR, OOP, CNF N Execute specified alarm detection
Y Disables IOP and IOP- detection
N Enables IOP and IOP- detection
ANS+, ANS-, PERR, Y Mask specified alarm
Element symbol.AOFS CNF, IOP, AOF (*1),
OOP N Unmask specified alarm
Y Perform alarm group confirmation
Element symbol.AFLS AFL
N –
Y Set the sequence setpoint (CSV) (*2)
0, 1, 2
N –
Y Set CSV to 0
P0
N Set CSV to 2
Element symbol.CSV
Y Set CSV to 1
P1
N –
Y Set CSV to 2
P2
N Set CSV to 0
Y Tracking switch (0: OFF, 1: ON)
Element symbol.TSW 0, 1
N –
Y Bypass switch (0: OFF, 1: ON)
Element symbol.BPSW 0, 1
N –
Y Backup switch (0: OFF, 1: ON)
Element symbol.BSW 0, 1
N –
Y Switch to CAL or release CAL
Element symbol.PV =XCAL (*3)
N –
D030272E.EPS
*1: AOF specification is only effective for changing the alarm masking specification. This action performs alarm masking
on all alarms except NR.
*2: To set a manipulated output value for the switch instrument from other function block, write data to the sequence
setpoint (CSV). If the switch instrument block is either in AUT or CAS state, the output will be performed after the value
of CSV is written to the manipulated output value (MV).
*3: The Output Timing of the sequence table that =XCAL is applied should be set to [Output Only When Condition
Changes (C)].

■ Status Manipulation of Timer Block
The table below lists the symbolic convention and action description of the action signal to
manipulate the status of various functions of the Timer Block (TM).

Y Timer stop command
STOP
N –
Y Timer start command
START
N Timer stop command
Element symbol.OP
Y Restart command
RSTR
N –
Y Pause command
WAIT
N Restart command
D030273E.EPS
■ Status Manipulation of Software Counter Block (CTS)

manipulate the status of various functions of the Software Counter Block (CTS).

Y Software counter operation command
ON
N –
Element symbol.ACT
Y Software counter stop command
OFF
N –
Y Trigger software counter (One Count)
Element symbol.XACT ON
N Stop software counter
D030274E.EPS

■ Status Manipulation of Pulse Train Input Counter Block (CTP)
manipulate the status of various functions of the Pulse Train Input Counter Block (CTP).

Y Pulse input counter stop command

STOP
N –
Y Pulse input counter start command
START
N Pulse input counter stop command
Element symbol.OP
Y Restart command
RSTR
N –
Y Pause command
WAIT
N Restart command
Y Cancel specified alarm detection

Element symbol.AF IOP, CNF
N Execute specified alarm detection
Y Mask specified alarm
Element symbol.AOFS IP, CNF, AOF (*1)
N Unmask specified alarm
N –
D030275E.EPS
*1: AOF specification is only effective for changing the alarm masking specification. This action operates alarm masking
■ Status Manipulation of Code Input Block (CI)

manipulate the status of various functions of the Code Input Block (CI).

Y Code input read command
N –
D030276E.EPS

■ Status Manipulation of Code Output Block (CO)
manipulate the status of various functions of the Code Output Block (CO).

Code output command to contact output signal or internal
Y
Element symbol.ACT ON status switch
N Disable
D030277E.EPS
■ Status Manipulation of Resource Scheduler Block (RS)

manipulate the status of various functions of the Resource Scheduler Block (RS).
Specified number usage cancel/request command
Y
Element symbol.RQ01 to 32 0, 1 (1: Request, 0: Cancel)
N Disable
Y Set the maximum allowable number (m32)
Element symbol.PMH 0 to 32
N Disable
Entire resource group request/cancel
Y
Element symbol.ACT ON, OFF (ON: Request, OFF: Cancel)
N Disable
D030278E.EPS
■ Status Manipulation of Valve Monitoring Block (VLVM)

manipulate the status of various functions of the Valve Monitoring Block (VLVM).

Y Message suppression (1: Suppress, 0: Cancel)
Element symbol.MCSW 0, 1
N Disable
D030279E.EPS

■ Status Manipulation of Regulatory Control Block
manipulate the status of various functions of the regulatory control block.

MAN, AUT, CAS, Y Block mode change command
Element symbol.MODE RCAS, ROUT, PRD,
O/S N Disable
Element symbol.AF Alarm status except NR
Alarm status except NR, Y Mask specified alarm

Element symbol.AOFS
AOF (*1) N Unmask specified alarm
N Disable
Y Set data
Element symbol.data item Data value
N Disable
Y Switch PV to CAL status
Element symbol.PV =CAL
N Release PV from CAL status
N –
Element symbol.SUM0 =XCAL (*2)
N –
D030280E.EPS
*1: AOF specification is only effective for changing the alarm masking specification. This action performs alarm masking
Changes (C)].

● Regulatory Control Block that can Describe Data Values in Action
Specifications
The table below lists the regulatory control blocks that can describe data values in action
specifications and the setting ranges of data items.
Table Regulatory Control Blocks that can Describe Data Values in Action Specifications and the
Setting Ranges of Data Items (1/3)

TSW 0, 1
CSW 0, 1
BSW 0, 1
RSW 0, 1
TSW 0, 1
CSW 0, 1
PI-HLD Sampling PI Controller Block PSW 0 to 3
BSW 0, 1
RSW 0, 1
TSW 0, 1
CSW 0, 1
BSW 0, 1
RSW 0, 1
CSW 0, 1
BSW 0, 1
PSW 0 to 3
BSW 0, 1
PSW 0 to 3
BSW 0, 1
TSW 0, 1
PSW 0 to 3
BSW 0, 1
RSW 0, 1
TSW 0, 1
PSW 0 to 3
PI-BLEND Blending PI Controller Block BSW 0, 1
RSW 0, 1
RST 0, 1
TSW 0, 1
CSW 0, 1
PSW 0 to 3
BSW 0, 1
RSW 0, 1
STC -1 to 3
D030281E.EPS


TSW 0, 1
RSW 0, 1
TSW 0, 1
RSW 0, 1
TSW 0, 1
RSW 0, 1
TSW 0, 1
BSW 0, 1
BPSW 0 to 4
SIMM 0 to 1
0, 1, 2, P0, P1,
CSV P2 (*1)
TSW 0, 1
BSW 0, 1
BPSW 0 to 4
MC- 3 3-Position Motor Control Block
SIMM 0 to 1
0, 1, 2, P0, P1,
CSV P2 (*1)
TSW 0, 1
PSW 0 to 3
BSW 0, 1
RSW 0, 1
ZONE 0 to 13
ZEND 0 to 13
D030282E.EPS
*1: The value set for the CSV varies depending on the values of action rules and setting range.
0: CSV = 0 when the action rule is [Y], Disable when [N]
P0: CSV = 0 when the action rule is [Y], CSV = 2 when [N]
P1: CSV = 1 when the action rule is [Y], Disable when [N]
P2: CSV = 2 when the action rule is [Y], CSV = 0 when [N]


SW 0 to 4
ZONE 0 to 11
SW 0 to 4
ZONE 0 to 11
PSW 0 to 3
BPSW 0, 1
SS-H/M/L Signal Selectors SW 0 to 4
PSW 0 to 3
AS-H/M/L Auto Selectors
SW 0 to 4
SS-DUAL Dual-Redundant Signal Selector Block SW 1 to 3
TSW 0, 1
PSW 0 to 3
FSW 0, 1
RSW 0, 1
TSW 0, 1
RSW 0, 1
BSW 0, 1
SW 0 to 3
RST 0, 1
HSW 0, 1
SW 0 to 5
SV 0 to 15
D030283E.EPS

■ Status Manipulation of Calculation Block ¡ £
manipulate the status of various functions of the calculation block.

Y One-shot execution (with parameter)
mm (*1)
N Disable
Element symbol.ACT
Y One-shot execution (without parameter)
ON
N Disable
Alarm status except NR, Y Mask specified alarm

Element symbol.AOFS
N Disable
Element symbol. Y Set data

Data value
DATA ITEM N Disable
Y Change CPV's data status to CAL
Element symbol.CPV =CAL
N Cancel CPV's CAL data status
Element symbol.CPV =XCAL (*3)
N –
Element symbol.CPV1 =XCAL (*3)
N –
Element symbol.CPV2 =XCAL (*3)
N –
D030284E.EPS
*1: mm is a parameter required for one-shot execution of the batch data setting block and the batch data acquisition block.
The data set at the one-shot execution varies depending on the mm value.
mm=0: Set 0 to all data.
mm=1 to 16: Set specified data only (DTn).
mm=17: Set all data.
*2: AOF specification is only effective for changing the alarm masking specification. This operation performs alarm
masking on all alarms except NR.
Changes (C)].

● Calculation Blocks That Can Describe Data Values In Condition
Specifications
The table below lists the data items of regulatory control blocks that can describe data
values in condition specifications and their setting ranges.
Table Calculation Blocks that can Describe Data Values in Action Specifications and Setting
Range of Data Items

AVE-C Cumulative average block
SW 0, 1, 2
SW-33 Three-Pole Three-Position Selector Switch SW 0 to 3
SW-91 One-Pole Nine-Position Selector Switch SW 0 to 9
SW 0 to 16
BDSET-1L One Batch Data Set Block
SW 0 to 3
BDSET-2L Two Batch Data Set Block
SW 0 to 17
ADL Inter-Station Data Link Block SIMM 0, 1
D030285E.EPS

● Executable Calculation Block for One-Shot Execution ¡ £
The table below lists the calculation blocks that can specify one-shot execution as an
action specification.
Table One-Shot Executable Calculation Block ¡ £
ADD Addition Block
DIV Division Block
AVE Averaging Block
OR Logical OR Block
Logic Calculation (*1)
WOUT Wipeout Block

Calculations CALCU-C General-Purpose Calculation Block with String I/O
Calculation auxiliary
D030286E.EPS
*1: ¡ £ The Logic Operation Blocks are only applicable to CS 3000.

● Calculation Block that Requires mm Parameter for One-Shot Execution
The table below lists the calculation blocks that are required to specify one-shot execution
parameter mm as an action specification.
Table Calculation Blocks That is Required to Specify Parameter mm in the Action Specification
Parameter setting
Block code Name Remarks
range (mm)
BDSET-1C One-Batch String Data Set Block Set individual
0 to 17
BDSET-2L Two-Batch Data Set Block data

BDA-L Batch Data Acquisition Block Acquire
0 to 17
BDA-C Batch String Data Acquisition Block individual data
D030287E.EPS
Note: Parameter mm is defined as follows.

mm=0: Set 0 to all data.
mm=1 to 16: Set specified data only (DTn).
mm=17: Set all data.

■ Status Manipulation of Faceplate Block
manipulate the status of various functions of the faceplate block.

Y Change block mode
N Disable
Y Change block status
N Cancel block status
Y Change alarm status
Element symbol.ALRM Alarm status except NR
N Cancel alarm status
Y Cancel the specified alarm detection.
N Execute the specified alarm detection.
Alarm status except NR, Y Mask the specified alarm.

Element symbol.AOFS
AOF (*1) N Unmask the specified alarm.
Y Perform alarm group confirmation.
N Disable
Y Set batch step number (Effective only for BSI block)
Element symbol.SV 1 to 99
N Disable
Element symbol. Y Set action command

0, 1
PV01 to 10 N Disable
Y Change switch display color
Element symbol.SWCR[n] (*2) 0 to 15
N Disable
Y Switch flashing status ON/OFF
Element symbol.SWST[n] (*2) 0, 1
N Disable
Y Change the switch operation disable status
Element symbol.SWOP[n] (*2) -15 to 15
N Disable
D030288E.EPS
*2: n is the subscript of the 1 dimensional array. This subscript is the number of the push button switches on a faceplate
block. This number varies with the type of faceplate block.

■ Status Manipulation of Sequential Function Chart (SFC) Block
manipulate the status of various functions of the sequential function chart (SFC) block.

Y Block mode change command
Element symbol.MODE MAN, AUT
N Disable
RUN, PAUS, STOP, Y Block status change command
Element symbol.BSTS
ABRT
N Disable
Y Cancel the specified alarm detection
N Execute the specified alarm detection
Alarm status except NR, Y Mask the specified alarm

Element symbol.AOFS
N Disable
Y Set data
Element symbol.data item Data value
N Disable
Y Change PV's data status to CAL
Element symbol.PV =CAL
N Cancel PV's CAL data status
N –
D030289E.EPS
Changes (C)].
● Sequential Function Chart Block Data Item that can be Described as a Data
Value in the Action Specification
The following table lists the sequential function chart block data item which can be de-
scribed as a data value in the action specification, and their setting ranges.
• STEPNO: 1 to 99
• SWCR[5]: 0 to 15
• SWST[5]: 0, 1
• SWOP[5]: -15 to 15

■ Status Manipulation of Unit Instrument
manipulate the status of various functions of the unit instrument.

Y Unit mode change command
Element symbol.MODE MAN, SEMI, AUT
N Disable
Unit status change Y Unit status change command
Element symbol.UBSC
command name
N Disable
Y Cancel the specified alarm detection.
N Execute the specified alarm detection.
Alarm status except NR, Y Mask the specified alarm.

Element symbol.AOFS
AOF (*1) N Unmask specified alarm.
N Disable
Y Change SFC step number.
Element symbol.STEPNO 1 to 99
N Disable
D030290E.EPS
■ Status Manipulation of Process I/O ¡ £

manipulate the status of various functions of the process I/O.

Y Contact output ON (Latched output)
H
N Contact output OFF (Latched output)
Y Contact output ON (Unlatched output)
L
N Disable
Element symbol.PV
Y Cause flashing state.
F
N Stop the flashing state (*1)
Y Output one-second pulse to the relevant bit (*2)
P
N Disable
D030291E.EPS
*1: Even though the flashing state stops, the contact output itself remains ON. Turn off the contact output using a different
action signal with a latched contact output.
*2: £ Not available in LFCS2 or LFCS. For LFCS2 or LFCS to give a pulse output, first to set the point mode of the
output terminal on IOM into Pulse Output (PO), then put a latched type symbol (H) or none latched type symbol (L) in
the action columns of sequence table.
SEE ALSO
For more information about pulse output, see paragraphs “● Pulse Contact Output : PFCS/KFCS2/
KFCS/SFCS” and “● Pulse Contact Output : LFCS2/LFCS” in section “■ Manipulating Status Output of I/
O Module” of chapter A3.2.2, “Contact Output.”

■ Status Manipulation of Global Switch £
The syntax in action signal description for manipulating the global switch to perform its
various functions and the output actions corresponding to Y/N in the action rule columns of
Table Syntax in Action Signal Description and Output Actions Corresponding to Y/N in Action
Rule Columns £

Y Turn the global switch ON (Latched).
H
N Turn the global switch OFF (Latched).
Element symbol.PV
Y Turn the global switch ON (Nonlatched).
L
N Disable
D030292E.EPS
■ Status Manipulation of Common Switch

manipulate the status of various functions of the common switch.

Y Common switch output ON (Latched output)
H
N Common switch output OFF (Latched output)
Element symbol.PV
Y Internal status switch output ON (Unlatched output)
L
N Disable
D030293E.EPS
■ Status Manipulation of Annunciator Message

manipulate the status of various functions of the annunciator message.

Y Annunciator output (Latched output)
H
N Cancel the annunciator output (Latched output)
Element symbol.PV
Y Annunciator output (Unlatched output)
L
N Disable
Repeated warning specification
Y
Element symbol.RP ON, OFF (ON: Repeated warning, OFF: Cancel)
N Disable
Y Mask the specified alarm.
Element symbol.AOFS AOF
N Unmask the specified alarm.
N Disable
D030294E.EPS

■ Status Manipulation of Sequence Message Output
The manipulation contents and description symbolic convention of the action signals when
performing status manipulation for the various message functions for sequence control are
indicated below.
The messages used in sequence controls include the messages attached with parameters
(constants) and the messages without parameters. Usage of the sequence control mes-
sages for manipulating sequence signals varies with the messages with or without param-
eters.
The sequence control messages without parameters consist of the following types of
messages:
• Print message output (%PR)
• Operator guide message output (%OG)
• Multimedia function message outputV (%VM)
• Sequence message request (%RQ)
• Event message output for supervisory computer (%CP)
• PICOT supervisory computer event message output (%M3)
The sequence control messages attached with parameters consist of the following types of
messages:
• Print message attached with parameters (%PR)
• Signal event message output (%EV)
• SFC/SEBOL return event message output (%RE)

Y Sequence message output without parameter
NON
N Disable
Element symbol.PV
Y Sequence message output with parameter
mm (*1)
N Disabl
D030295E.EPS
*1 Integer type data (2-byte unsigned integer type data) can be specified for mm.
Range: Integer from 0 to 65535

■ Status Manipulation of Communication I/O
manipulate the status of various functions of the communication I/O.

Y Relevant bit ON (Latched output)
H
N Relevant bit OFF (Latched output)
Element symbol.PV
Y Relevant bit ON (Unlatched output)
L
N Disable
D030296E.EPS

D3.2.14 Action Signal Description: Status Manipulation for

Sequence Table
In the status manipulation for sequence table, in addition to data setting and status
change, a series of processing from condition testing to status manipulation can be
performed by one-shot execution of the sequence table.
For status manipulation of a sequence table with rules extended to multiple se-
quence tables, a tag name for the extending sequence table must be specified.
There exist several types of status manipulations for sequence table as shown
below.
• Execution of the entire sequence table
• Execution of the corresponding rule number in sequence table
• Execution of a particular step(s)
• Setting of a sequence table execution step label
• Change of the sequence table block mode
■ Execution of the Entire Sequence Table

▼ Action Signal Description - Sequence Table
The sequence table indicated by an element symbol of the action signal from the referenc-
ing sequence table (branched sequence table) is activated to perform one-shot execution.
If the branched sequence table is a nonstep type, the entire table is subject to execution.
If the branched sequence table is a step type, the relevant steps according to the step
processing in the branched sequence table are subject to execution.
It is possible to further branch from a branched sequence table to other sequence table to
perform condition testing and actions for the first branched sequence table. Nesting is
available up to seven levels including the first sequence table.
● When the Branched Sequence Table is a Nonstep Type

The entire branched sequence table is executed.
The table below lists the symbolic convention and action description for the action signal
used to execute the entire branched sequence table.
Table Symbolic Convention and Action Description for Action Signal
Action signal description

Action rule Action description
Output signal Action specification
Y Execute the specified table
N Disable
D030297E.EPS
When the conditions described in the condition rule are satisfied, the sequence table
number listed in the action signal symbol column will be one-shot executed to branch to the
activated sequence table. After executing all condition testing and actions, it returns to the
action rule processing in the branching sequence table.

● When the Branched Sequence Table is a Nonstep Type
Description examples for the nonstep-type branched sequence tables are shown below.
Assume that “Output Only when Conditions Change” is specified for the output timing.
ST 005 ST 015

Tag name Tag name
Data item Data Step label Data item Data Step label
Comment Comment
DI0010.PV ON ................................ Y Y N DI0030.PV ON ................................ Y Y N
DI0015.PV ON ................................ Y N N DI0031.PV ON ................................ Y Y N
DI0016.PV ON ................................ Y Y Y Y DI0036.PV ON ................................ Y N N
DI0018.PV ON ................................ N N Y DI0038.PV ON ................................ Y N Y
DI0020.PV ON ................................ Y Y DI0125.PV ON Y Y Y Y
DI0021.PV ON ................................
DO0001.PV H Y Y N DO0050.PV H ................................ Y N Y

DO0011.PV H ................................ Y DO0052.PV H ................................ Y N
ST015.ACT ON ................................ Y Y DO0053.PV H ................................ Y N Y
DO0014.PV H ................................ Y Y DO0054.PV H ................................ N Y Y
D030298E.EPS
Figure Description Examples of Nonstep-Type Sequence Table Execution
The following explains the details of action rule processing in the description examples
shown above.
• If the conditions in Rule 01 of Table ST005 are satisfied, the DO001.PV.H=Y operation
will be executed and all the conditions from rules 01 to 32 will then be tested after
branching to Table ST015. If conditions are satisfied at Table ST015, operations will be
executed for the rules whose conditions have been satisfied. It will then return to Table
ST005 action rule processing to execute the DO0014.PV.H=Y operation.
• Neither Rule 02 nor 03 on table ST005 is associated with the action rule processing
because no action descriptions for Table ST015 are listed in either rule.
• If the conditions in Rule 04 of Table ST005 are satisfied, the DO001.PV.H=N operation
will be executed and all the conditions from rules 01 to 32 will then be tested after
branching to Table ST015. If conditions are satisfied at Table ST015, operations will be
executed for the rules whose conditions have been satisfied. It will then return to Table
ST005 action rule processing to execute the DO0014.PV.H=Y and DO0035.PV.H=Y
operations.
• If the periodic execution is specified for the processing timing of Table ST015, in
addition to one-shot execution caused by status manipulation, periodic execution will
also be performed at Table ST015.

● When the Branched Sequence Table is a Step Type
Description examples for the step-type branched sequence table is shown below. Assume
that “Output Only when Conditions Change” is specified for the output timing.
If the branched sequence table is a step type, steps will be executed under the step man-
agement of the branched sequence table.
ST 005 ST 015

Tag name Tag name
Data item Data Data
Step label 1 2 3 4 Data item Step label 1 2 2 3
Comment Comment
DI0021.PV ON ................................
DO0001.PV H Y Y N DO0050.PV H ................................ Y N

DO0011.PV H ................................ Y N DO0052.PV H ................................ Y N
DO0035.PV H ................................ Y Y DO0061.PV H ................................ N Y
THEN 2 3 1
ELSE
D030299E.EPS
Figure Description Examples of Step-Type Sequence Table Execution
The following explains the details of action rule processing in the description examples
shown above.
will be executed to branch to Table ST015. If the execution step label (PV) is Step 2,
the condition testing for rules 02 and 03 of Step 2 will be performed. If conditions are
satisfied, operations for the rules whose conditions have been satisfied will be ex-
ecuted. It will then return to Table ST005 to execute the DO0014.PV.H=Y operation.
• If the step label is described on the branched sequence table, a processing will be
executed according to the step management of the branched sequence table, regard-
less of the step label on the branching sequence table.

● When There Exist Steps 00 and n in the Branched Sequence Table
Description examples of the branched sequence table with steps 00 and n are shown
below. Assume that “Output Only when Conditions Change” is specified for the output
timing.
ST 005 ST 015

Tag name Tag name
Data Data
Data item Step label 1 2 3 4 Data item Step label 0 1 1 2
Comment Comment
DI0021.PV ON ................................
DO0001.PV H Y Y N DO0050.PV H ................................ Y N

DO0011.PV H ................................ Y N DO0052.PV H ................................ Y
THEN 2 1
ELSE
D0302A0E.EPS
Figure Description Examples of Step-Type Sequence Table Execution
The following explains the details of the action rule processing in the description examples
shown above.
If the conditions in Rule 01 of Table ST005 are satisfied, the D000001.PV.H=Y operation
will be executed to branch to Table ST015. If the execution step label (PV) at Table ST015
is Step 2 at the time, the condition testing for Rule 01 of Step 00 and Rule 04 of Step 2 will
be performed. If conditions are satisfied at Table ST015, operations for the rules whose
conditions are satisfied, will be executed. It will then return to Table ST005 to execute the
DO0014.PV.H=Y operation.

■ Execution of the Corresponding Rule Number in the Sequence Table
One-shot execution of the sequence table is performed, with the same rule number as the
current rule at the branch source as an execution target. This is used to expand the condi-
tion signal and action signal over 64 signals in the nonstep type sequence table.
The table below lists the symbolic convention and description of action signal to execute
the corresponding rule numbers.
Action signal description column Action
rule Action description
Output signal Action specification column
Y Execute the same table
Element symbol.SD C
N Disable
D0302A1E.EPS
• When the branch source is a step type and the branch destination is a nonstep type:
Although execution of the corresponding rule number is meaningless, the correspond-
ing rules will be executed.
• When the branched table is a step type:
Because execution of the same rules will be meaningless, the system will halt without
executing any actions.
It is possible to branch further from the branched sequence table to other sequence table,
and perform condition testing and operation for the first branched sequence table. Nesting
is available up to seven levels, including the first sequence table.

Description examples of the status manipulation of corresponding rule numbers are shown
below. Assume that “Output Only when Conditions Change” is specified for the output
timing.
ST 005 ST 015

Tag name Tag name
Data Data
Data item Step label Data item Step label
Comment Comment
DI0020.PV ON ................................ Y Y DI0125.PV ON Y Y N Y
DI0021.PV ON ................................
DO0001.PV H ................................ Y Y N DO0050.PV H ................................ Y N Y

DO0011.PV H ................................ Y N DO0052.PV H ................................ Y N
ST015.SD C ................................ Y Y DO0053.PV H ................................ Y N Y
DO0035.PV H ................................ Y Y DO0061.PV H ................................ N Y
D0302A2E.EPS
Figure Description Examples of Corresponding Rule Number Execution
The following explains the details of the action rule processing in the description examples
shown above.
will be executed, and the condition testing of Rule 01 will be conducted after branch-
ing to Table ST015. If conditions are satisfied, DO0050.PV.H=Y, DO0052.PV.H=Y, and
DO0054.PV.H=N operations will be executed. It will then return to Table ST005 to
execute the DO0014.PV.H=Y operation.
• Neither rule 02 nor 03 of Table ST005 is associated with Table ST015.
• If the conditions in Rule 04 of Table ST005 are satisfied, the DO0001.PV.H=N and
DO0011.PV.H=N operations will be executed to branch to Table ST015. Condition
testing will then be performed for Rule 04. If conditions are satisfied, operations for the
rules whose conditions have been satisfied will be executed. DO0053.PV.H=Y,
DO0054.PV.H=Y, and DO0061.PV.H=Y operations will be executed. It will then return
to Table ST005 to execute the DO0014.PV.H=Y and DO0035.PV.H=Y operations.

■ Executing a Particular Step in the Sequence Table
The following describes the action signal’s symbolic convention and the action description
for executing a particular step in the specified sequence table.

Y Execute steps xx and 00
Element symbol.SA xx
N Disable
D0302A3E.EPS
xx: Specify the step label using 2 or less alphanumeric characters.
It is possible to further branch from the branched sequence table to other sequence table,
and perform condition testing and operation for that branched sequence table. Up to seven
levels of nesting are possible including the first sequence table.
The action rule subject to execution varies by the type of sequence table (nonstep, step) at
the execution source and execution destination.
Table Execution Target Rules by Sequence Table Type
Branch source Branch destination Action rule subject to execution
Nonstep type
Step type Rules in specified step and step 00
Step type
Step type Rules in specified step and step 00
D0302A4E.EPS
When the conditions described in the condition rule are satisfied, the sequence table
number listed in the action signal symbol column will be one-shot executed to branch to the
destination sequence table. After executing condition testing and actions for rules in Step
00 and steps specified by the branched sequence table, it returns to the action rule pro-
cessing in the branching sequence table.
If the specified step does not exist in the branched sequence table, an error will occur and
the step will not be executed. However, in spite of the error, if Step 00 exists in the
branched sequence table, only that step will be executed.
If “execution of a particular step” is performed for the nonstep-type sequence table, all rules
will be subject to execution.

A description example of executing a particular step is shown below.
ST 005 ST 015

Tag name Tag name
Data Data
Data item Step label A1 A2 A3 A4 Data item Step label A1 A2 A2 A3
Comment Comment
DI0021.PV ON ................................
DO0001.PV H Y Y N DO0050.PV H ................................ Y N Y

DO0011.PV H ................................ Y N DO0052.PV H ................................ Y N
ST015.SA. A2 ................................ Y Y DO0053.PV H ................................ Y N Y
THEN
Description is
ELSE
not required.
D0302A5E.EPS
Figure Description Example of Executing Action Rule Processing
The following describes the action rule processing for the above example.
• If the conditions in Rule 01 of Table ST005 are newly satisfied, the DO001.PV.H=Y
operation will be performed to branch to Table ST015. Following the condition testing
conducted for rules 02 and 03 of Step A2 in the branched sequence table, if the
conditions are newly satisfied, relevant operations will be performed. It will then return
to Table ST005 to execute the DO0014.PV.H=Y operation.
• Neither Rule 02 nor 03 in Table ST005 is associated with Table ST015.
• If the conditions in Rule 04 of Table ST005 are satisfied, the DO0001.PV.H=N and
DO0011.PV.H=N operations will be performed to branch to Table ST015. Following
the condition testing for rules 02 and 03 of Step A2 in the branched sequence table, if
the conditions are newly satisfied, relevant operations will be performed. It will then
return to table ST005 to execute the DO0014.PV.H=Y and DO0035.PV.H=Y opera-
tions.

■ Setting Execution Step Label in the Sequence Table
Execution step label (PV) of the sequence table is set. Unlike “executing a particular step,”
this operation merely sets a step label for the execution step label (PV) of a specified
sequence table. This setup operation alone will not execute the step. It is not until the
execution step label (PV) is activated after the setup that the step is executed.
The table below lists the symbolic convention and action description of the action signal for
setting the execution step label.
Table Symbolic Convention and Action Description of the Action Signal

Y Set the step name xx
Element symbol.PV xx
N Disable
D0302A6E.EPS
xx: Specify the step label using 2 or less alphanumeric characters.
A description example of specifying the execution step label of a specified sequence table
is shown below.
ST 005
Rule number 01 02 03 04 05 06 07
Tag name Data
Data item Step label
Comment
DI0013.PV ON Auto/manual N Y
Condition
ST010.PV A1 Y
ST011.PV A1 Y
ST012.PV A1 Y Operation
ST013.PV A1 Y
D0302A7E.EPS
Figure Description Example of Setting Execution Step Label
The following describes the action rule processing for the above description example.
• When DI0013 becomes “OFF,” “A1” will be set on the execution step label in se-
quence tables ST010, ST011 and ST012.
• When DI0013 becomes “ON,” “A1” will be set on the execution step label in the ST013
sequence table.

■ Block Mode Change in Sequence Table
By describing the block mode change of the other sequence table in the sequence table
action signal, halt (change to MAN mode)/restart (change to AUT mode) of the other
specified sequence table is manipulated.
The sequence table changed to the manual (MAN) mode will retain the status at the time of
block mode change. When “changed output” is specified for the output timing, the states of
halt and restart are compared upon restarting the processing to execute the status manipu-
lation for the changed condition rules.
The table below lists the symbolic convention of the action signal and action description for
changing the block mode.

Y Table mode change command
Element symbol.MODE AUT, MAN, O/S
N Disable
D0302A8E.EPS
■ Pause and Restart a Sequence Table

Some sequence tables are running in a fixed scan cycle while some others are staring,
pausing or restarting in accordance with process procedures. To pause a running se-
quence table, and to restart a paused sequence table is possible. The scripts may be
described in a sequence table for a sequence table’s Pause and Restart are shown as
follows.
Table Syntax for Output Signal Scripts and Action Description

Y Starts or restarts sequence table
Element symbol.XS ON
N Pause Sequence table
D0302B2E.EPS
When Y is scripted in an action rule, if the condition of that rule establishes, the sequence
table scripted in the Element symbol column will be started or restarted. When the restarted
sequence table is running in the [Output Only When Condition Changes (C)] timing, the
restarted will compare the current conditions with the conditions before it was paused, only
the rules that the conditions have been changed will perform the output actions. If the
sequence table is a [Periodic Execution Type], the sequence table will continue to run until
it receives another pause command.
When N is scripted in an action rule, if the condition of that rule establishes, the sequence
table scripted in the Element symbol column will be paused.

D3.2.15 Action Signal Description: Status Manipulation for a

Logic Chart from a Sequence Table
In the status manipulation for a logic chart, a logic chart block mode can be
changed. In addition, the specified logic chart can be one-shot executed.
■ One-Shot Execution of a Logic Chart from a Sequence Table

▼ Action Signal Description - Logic Chart
The syntax in action signal description for one-shot executing a logic chart and the output
actions corresponding to Y/N in the action rule columns of the sequence table are shown
as follows.
Rule Columns

Y Execute a logic chart
N Disable
D0302A9E.EPS
• The output of an executed logic chart can execute another logic chart. The output
signal can be nested up to seven times, including the branching sequence table.
• If one-shot execution of a logic chart fails for one of the following reasons, a system
alarm will be triggered.
• The output of an executed logic chart to execute another logic chart is nested over
seven times, including the branching sequence table.
• The function block connected to the input terminal is in O/S mode.
• The function block connected to the input terminal is udder online maintenance.
■ Changing the Block Mode of a Logic Chart from a Sequence Table

The block mode of the specified logic chart may be changed. Changing the block mode
allows the logic chart to be paused (with the MAN mode specified) or resumed (with the
AUT mode specified).
The syntax in action signal description for changing a block mode and the output actions
corresponding to Y/N in the action rule columns of the sequence table are shown as fol-
lows.
Rule Columns

Y Change a block mode
N Disable
D0302B0E.EPS

D3.2.16 Data Items of the Sequence Table Block (ST16)

The data items of the ST16 block is shown below.
■ Data Item
Table Data Items of the Sequence Table Block (ST16)
Entry Permitted
Symbol Data Name Range Default
or Not
PV Executing step name 100 steps Start step name
MODE Mode ---- O/S (MAN)
ALRM Alarm status ---- NR
AFLS Alarm flashing status ---- 0
AF Alarm detection ---- 0
AOFS Alarm in hibition ---- 0
UAID User application ID ---- 0
D0302B1E.EPS
: Entry is permitted unconditionally.

Blank: Entry is not permitted.
SEE ALSO
For a list of valid block mode of the ST16, see D3.1.2 “Block Mode of Sequence Control Blocks.”

<Toc> <Ind> <D3.3 Logic Chart Block (LC64)> D3-103
D3.3 Logic Chart Block (LC64)

Logic Chart Block (LC64) may combine or arrange the signals of other function
blocks, process I/O and software I/O into an application for interlock sequence
control.
■ Logic Chart Block (LC64)

▼ Logic Chart
Logic Chart Block is the function block that describes the relations of the input signals, the
output signals and the logic calculation operators in the interlock diagram form, so that it
can perform its main function, the interlock sequence control using the same expressions
as those used on the logic chart blue prints.
An architecture of LC64 Logic Chart Block is shown as follows.
Q01 J01
Q02 J02
Q03 Input Output J03

Logic operation
Q56 J56
D030301E.EPS
Figure Function Block Diagram of Logic Chart Block (LC64)
The connection methods and destinations for I/O terminals of Logic Chart Block (LC64) are
shown below.
Table Connection Methods and Destinations for I/O Terminals of Logic Chart Block (LC64)
I/O Status Terminal
terminal Data Data Condition Process Software Function
manipula- connecti-
tion on
Q01 to Q56
J01 to J56
D030302E.EPS

The input and output connections can be set by entering the connection information and
data description on the client area of the logic chart editing window.
Mooving into
WO %SW0200.PV.L cooling phase
StopACool %SW0500.PV.ON
%SW0001.ON Cooling printout
Level 1 %SW0100.PV.ON TM100
TCV full
Level 2 %SW0150.PV.ON %SW0160.PV.L
close command
CoolAStop %SW0120.PV.ON
Shutoff valve 1
Auto %SW0001.PV.ON TV100.CSV.2
open output
TM100 Shutoff valve 2
TV101.CSV.2
open output
Open shutoff valve 1 TV100.PV.2 Open shutoff valve %SW0201.PV.L Cool command
Open shutoff valve 2 TV101.PV.2
Comment
No.1 temperature
RL001.X01.LT Cooling and
<- 70 C DO0100.PV.L voice message
No.2 temperature
RL002.X02.LT
<- 70 C
Comment Condition signal Logic element Action signal Comment

D030303E.EPS
Figure Outline of the Logic Chart
A logic chart with 32 inputs, 32 outputs and 64 logic elements (LC64) is provided.
● Logic Chart with 32 Inputs, 32 Outputs and 64 Logic Elements (LC64)

LC64 block is a sequence control function block with 32 input and 32 output signal chan-
nels and it can handle 64 logic operators. Since the input and output signal channels are
fixed, the small logic chart with only 8 input and 8 output signal channels can not be cre-
ated.

D3.3.1 Configuration of a Logic Chart

A logic chart consists of condition signals, action signals and logic operators.
■ General Outlook of a Logic Chart

A general outlook of a logic chart is shown as follows.
Process timing Scan period Order of execution

A B C D E F G H I J K L M N O P Q R S T U V W
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20 Comment Condition Logic chart area Action Comment
21 signals signals
22
23
24
25
26
27
28
29
30
31
32
Client area
D030304E.EPS
Figure Configuration of the Entire Logic Chart

■ Outline of Logic Chart Elements ¡ £
The logic chart elements are shown as follows.
● Processing Timing
The processing timing of a logic chart consists of start timing and output timing.
Start timing refers to the timing at which control algorithm of the logic chart is executed
upon receipt of input signal. Output timing indicates the conditions under which action
signals are output at the time a periodic start type or one-shot start type logic chart is
executed.
The output timing of logic charts is fixed to “output each time.” If the logical value acquired
by logic operation is true, output signals are output whenever started.
“Start timing” can be set on each logic chart block.
• Start timing:
Select from “Periodic Execution Type (T),” “One-shot Processing Type (O),” “Startup
at Initial Cold Start/Restart (I)” or “Restricted Initial Execution Type (B).”
• Output timing:
“Output Each Time Conditions are Satisfied”
● Scan Period ¡
Periodic start logic charts are activated at each defined scan period. Among the periodic
started logic charts, the logic charts activated in the basic period have the items “Control
Period” and “Control Phase” to be defined in addition to scan period.
“Scan period,” “control period,” and “control phase” can be defined for each logic chart.
• Scan period: Select from “Basic Scan” or “High-speed Scan.”
• Control period: 1 to 16 seconds.
• Control phase: 0 to 15 seconds.
● Scan Period £
Periodic start logic charts are activated in each scan period as defined here. Among the
periodic started logic charts, the logic charts activated in the basic period have the items
“Scan period,” “control period,” and “control phase” can be defined for each logic chart.
• Scan period:
Select from “Basic Scan”, “Medium-speed Scan” (*1) or “High-speed Scan.”
• Control period: 1 to 16 seconds.
• Control phase: 0 to 15 seconds.
*1: £ “Medium-speed Scan” is only supported by KFCS2, KFCS, LFCS2 and LFCS.
SEE ALSO
• For details on processing timing, refer to C7.3, “Process Timing for Sequence Control Block.”
• For details on scan period, refer to C7.1.1, “ Scan Period.”
• For details on control period and control phase, refer to C7.3.6, “Control Period and Control Phase for
Logic Chart Block (LC64).”

● Order of Logic Calculation
For the execution order of logic calculation, the matrix expansion or manual expansion can
be selected.
● Condition Signals
The input information such as tag names and data items or other specific condition scripts
should be entered for condition signals.
● Comment
For the input signals or output signals, their service comments can be described using up
to 24 alphanumeric characters or 12 double-byte characters. A comment corresponding to
a condition or action signal can be automatically entered.
SEE ALSO
For the details of comment entry, refer to F4, “Editing Logic Chart.”
● Logic Chart Area

The logic calculation process can be expressed in logic chart diagram form.
● Action Signals
The output information such as tag names and data items or other specific manipulation
scripts should be entered for action signals.

D3.3.2 Creating a Logic Chart Block

To create a logic chart block, the settings related to the sequence control informa-
tion should be entered in each setting area of the logic chart edit window.
■ Configuration of Logic Chart Edit Window

The figure below shows the configuration of the logic chart edit window.
Processing timing setting area Execution order of logic calculation setting area
Client area
D030305E.EPS
Figure Configuration of Logic Chart Edit Window
To create a logic chart, the information for sequence connection (condition signals, action
signals, logic operators, parameters of the applied logic operators) needs to be entered in
each setting area of the logic chart edit window.
The setting areas are listed below.
• Processing timing setting area
• Execution order of logic calculation setting area
• Client area

■ Processing Timing Setting Area
In processing timing area, the existing settings for the processing timing and scan period
are displayed. Data can be specified and changed at the Processing Timing and Scan
Period on the Processing Timing setup area. The processing timing, scan/control periods
and control phase can also be specified at the Set Start Timing dialog box.
An example of processing timing setting dialog box is shown as below.
Processing timing
Processing timing
Execution timing Periodic execution

Output timing Output only at condition change
Scan period
Scan period Basic scan

Control period
Control phase
OK Cancel
D030306E.EPS
Figure Processing Timing Setting Dialog Box
SEE ALSO
For details of processing timing, refer to C7.3, “Process Timing for Sequence Control Block.”

■ Execution Order of Logic Calculation Setting Area
For the execution order, either matrix expansion or manual expansion can be selected in
this setting area.
TIP
Clicking [Execution Order] on [View] menu may display execution order of the logic elements on the client
area of the logic chart edit window.
Moreover, this setting is also valid for the status display window and for the self-documentation of the
window.
■ Client Area
The client area is used to put the logic operators symbols on the matrix for describing the
logic calculation processing in logic chart format.
SEE ALSO
For details on logic calculation processing, refer to D3.3.5, “Logic Calculation Processing of Logic Chart.”

D3.3.3 Logic Chart Processing Flow

In the logic chart, the logic calculation is performed based on the result of input
processing. Output processing is then performed for the output action to the opera-
tion target.
■ Logic Chart Processing Flow

The figure below shows the logic chart processing flow.
Logic calculation processing
Input processing Output processing

(condition test) (status manipulation)
D030307E.EPS
Figure Logic Chart Processing Flow
The true or false status of a condition signal is determined by the condition test performed
on the input signal.
● Logic Calculation Processing

The logic calculation is based on the result of condition test of the input signal (true = 1,
false = 0). The logic calculation algorithm is expressed by combinations of logic operators.
Status manipulation output is determined based on the result of logic calculation process-
ing.
The status manipulation will be output as the output signals to the operation target. The
status manipulation can send commands such as starting, data setting, and status change
to the contact output terminals or to other function blocks.

D3.3.4 Input Processing of Logic Chart

The input processing gives a true or false status signal based on the result of condi-
tion test performed on each of the multiple input signals.
■ Input Processing of Logic Chart ¡ £

Logic chart function block samples input signals via its input terminals from the connected
destinations. Then the condition test is performed based on these signals.
The result of the condition test is referred to as condition signal status. The condition signal
status True or False will be passed to the logic calculation function in the block.
If the function block connected to the input terminal is a one-shot started block, the result of
the calculation performed in the one-shot started function block can also be used as the
signal for condition test.
When referencing the signal from the one-shot started function block fails, and the failure is
caused by one of the following reasons, a system alarm will be triggered.
• In the condition column of the referenced sequence table, the reference target is
another sequence table, the sub-reference is nested more than 7 times.
• The function block connected to the input terminal is in O/S mode.
• The function block connected to the input terminal is udder online maintenance.
If an input terminal is not connected or a condition element is not defined, the condition test
result will give a True status unconditionally.
When the condition test can not access the current signal status, or can not trigger the one-
shot started block to start, it will use the previously used signal status for the condition test.
This result will be further used in the logic calculation processing.
A block or an element database connected is abnormal, the connected function block,
process I/O or global switch (*1) is under online maintenance are the main obstacles for
accessing the input signal.
*1: ¡ £ The global switch is only supported in CS 3000 system.
IMPORTANT
Online maintenance is one of the main obstacles for accessing the input signal and starting
the one-shot started block. The duration of an online maintenance varies with the size and
type of the modified contents for the online maintenance. When the modified contents are
in large size, the online maintenance may last for tens of seconds.
When the condition test can not access the current signal status, or can not trigger the one-
shot started block to start, the condition test uses the previously used signal status. Since
this status is kept in the logic chart, cautions should be taken in the following case.
• When the logic chart block itself is one-shot execution type or the connected function
block is one-shot start type, and the access failure is caused by O/S mode, the previ-
ous signal status might be a signal kept for a long time. If the one-shot has not been
started for at least one time, the status signal kept might be a 0 (False).
With consideration of the online maintenance in above mentioned case, when designing a
sequence control, especially the sequence control loop related to the hazardous process
controls, it is required to add an error process subroutine, or to set the related blocks into
MAN mode on the builder for online downloading.

D3.3.5 Logic Calculation Processing of Logic Chart

The logic calculation processing performs the logic calculation described in logic
chart. The logic calculation is based on the input signal status and the calculated
result is output as an action signal.
■ Logic Calculation Processing

The logic calculation based on the signal status (True = 1, False = 0) is performed at each
scan cycle when the block is periodic type or at each time the block starts when the block is
one-shot started type. The result of the calculation will be output to other logic elements in
the logic chart or sent out as an action signal. In most of cases, a logic element gives an
action signal only when the calculation result is True.
■ Logic Operation Elements

The logic chart is described with combinations of logic elements in the logic chart block.
The detailed specifications of the logic operation elements will be explained in the following
sections. The logic operation element shares the same specification with corresponding
logic operation block.
TIP
• When an input is directly wired to an output, it is still counted as one logic operation element.
• SRS, WOUT or CMP is counted as 2 logic operation elements.
● AND: Logic Product

It gives one output based on multiple inputs. When all the inputs are True, the output
becomes True. The maximum number of inputs is 21.
, , ,
D030308E.EPS
Figure AND symbols
● OR: Logic Sum

It gives one output based on multiple inputs. When any of inputs is True, the output be-
comes True. The maximum number of inputs is 21.
, , ,
D030309E.EPS
Figure OR symbols
● NOT: Negation
It gives the inverse of the input as an output.
D030310E.EPS
Figure NOT symbol

● SRS1-R (1 output), SRS2-R (2 outputs): Flip-Flop (Reset-Dominant)
It gives one output or two outputs shown in the following truth table based on the set and
reset input signals.
One flip-flop operation is counted as two logic operation elements.
S S OUT1 S S OUT1
R R R R OUT2
Without reset output With reset output

D030311E.EPS
Figure SRS1-R and SRS2-R symbols
Table Reset-Dominant Truth Table
S 0 1 0 1
Input
R 0 0 1 1
OUT1 Latched 1 0 0
Output
OUT2 Latched 0 1 1
D030312E.EPS
Latched: The previous state is maintained.
● SRS1-S (1 output), SRS2-S (2 outputs): Flip-Flop (Set-Dominant)

It gives one output or two outputs shown in the following truth table based on the set and
reset input signals.
One flip-flop operation is counted as two logic operation elements.
S S OUT1 S S OUT1
R R R R OUT2
Without reset output With reset output

D030313E.EPS
Figure SRS1-S and SRS2-S symbols
Table Set-Dominant Truth Table
S 0 1 0 1
Input
R 0 0 1 1
OUT1 Latched 1 0 1
Output
OUT2 Latched 0 1 0
D030314E.EPS
Latched: The previous state is maintained.

● WOUT: Wipeout
It gives an output which is an inverse of reset signal when reset signal is true, otherwise, it
gives the set signal as output, shown in the following truth table based on the set and reset
input signals.
One wipeout operation is counted as two logic operation elements.
Its symbol is shown below.
(W. O)
Table WOUT Truth Table
S 0 1 0 1
Input
R 0 0 1 1
Output OUT 0 1 0 0
D030315E.EPS

● OND: On-Delay Timer
When the input status changes from 0 to 1, the internal timer starts. When the set time t
elapsed, its output changes from 0 to 1. When the input status changes to 0, the output will
be reset to 0 immediately.
D030316E.EPS
Figure On-Delay Timer symbol
IN
OUT
D030317E.EPS
Figure Behavior of On-Delay Timer
● OFFD: Off-Delay Timer

When the input status changes from 1 to 0, the internal timer starts. When the set time t
elapsed, its output changes from 1 to 0. When the input status changes to 1, the output will
be reset to 1 immediately.
D030318E.EPS
Figure Off-Delay Timer symbol
IN
OUT
D030319E.EPS
Figure Behavior of Off-Delay Timer

● TON: One-Shot (Rise Trigger)
When the input status changes from 0 to 1, it gives an output 1 for a one scan cycle. The
output is always 0 except for that 1 scan cycle.
D030320E.EPS
Figure One-Shot (Rise Trigger) symbol
1
IN
0
1
OUT
0
One scan cycle

D030321E.EPS
Figure Behavior of One-Shot (Rise Trigger)
● TOFF: One-Shot (Fall Trigger)

When the input status changes from 1 to 0, it gives an output 1 for a one scan cycle. The
output is always 0 except for that 1 scan cycle.
D030322E.EPS
Figure One-Shot (Fall Trigger) symbol
1
IN
0
1
OUT
0
One scan cycle

D030323E.EPS
Figure Behavior of One-Shot (Fall Trigger)

● CMP-GE: Comparator
It compares the logic values of input 1 and input 2. It gives an output 1 when input 1 is
greater than or equal to input 2, otherwise it gives an output 0.
One Comparator operation is counted as two logic operation elements.
D030324E.EPS
Figure CMP-GE symbol
Table CMP-GE Truth Table

IN1 0 0 1 1
Input
IN2 0 1 0 1
Output OUT 1 0 1 1
D030325E.EPS
● CMP-GT: Comparator
greater than input 2, otherwise it gives an output 0.
D030326E.EPS
Figure CMP-GT symbol
Table CMP-GT Truth Table

IN1 0 0 1 1
Input
IN2 0 1 0 1
Output OUT 0 0 1 0
D030327E.EPS
● CMP-EQ: Comparator
equal to input 2, otherwise it gives an output 0.
D030328E.EPS
Figure CMP-GT symbol
Table CMP-EQ Truth Table

IN1 0 0 1 1
Input
IN2 0 1 0 1
Output OUT 1 0 0 1
D030329E.EPS

■ Execution Order of Logic Calculation
The Execution Order indicates in which order logic elements in logic charts are executed,
which includes Matrix Expansion and Manual Expansion.
• Matrix expansion
Logic operators in logic charts are executed from the left column to the right, and from
the upper element to the lower in the same column.
• Manual expansion
The execution order automatically assigned to the logic operation elements according
to their position can be manually changed.
The execution order of logic operation elements can be specified on the logic chart edit
window. The default setting for the execution order is matrix expansion.

D3.3.6 Output Processing of Logic Chart

The output processing of the logic chart gives an action signal to the operation
target. The action signal is the result availed from the logic calculation processing.
■ Output Processing of Logic Chart

The output processing of the logic chart performs status manipulation to the specified
output terminal in accordance with the action signal. The action signal is availed from the
True or False result of the logic calculation in the logic chart function block.
When the action signal is specified to a function block to be one-shot started, the block will
be one-shot started when the action signal is output to it.
When output to the one-shot function block fails, and the failure is caused by one of the
following reasons, a system alarm will be triggered.
• In the action column of the destination sequence table, the output signal is output to
another logic chart. Moreover, the output is redirected to another logic chart. The
output is nested more than 7 times.
• The function block connected to the output terminal is in O/S mode.
• The function block connected to the output terminal is udder online maintenance.
When the output action is to set a datum or to change status, if the connected destination, a
block or an element, is under online maintenance, the output will be skipped then the
processing continues.
When the output action is to change the block mode of the connected destination block, if
the output processing has an error, the status change of the connected destination block
will not be performed.
For the logic chart that has multiple output terminals, each terminal outputs the action
signal in accordance with logic calculation True or False result related to the terminal.

D3.3.7 Condition Signal Description: Referencing Other Function

Blocks and I/O Data
Various types of data, block mode and status can be referenced for condition test
performed in logic chart. I/O data including the process I/O, software I/O, and com-
munication I/O can also be referenced.
■ Function Blocks and I/O Data that can be Referenced from Logic Chart
Function blocks that can be referenced from logic chart are shown below.
• Switch instrument blocks
• SFC Blocks
The following I/O data can also be referenced from logic chart.
• Processing I/O (contact I/O)
• Software I/O (internal switch, annunciator message)
block mode.
ence, the test result is True even in the compound block mode as long as the specified
basic block mode exists.

■ Referencing Switch Instrument Block
The syntax for applying the various types of data and data status of a switch instrument
block as condition test reference signal in a logic chart and the True/False representation in
the logic chart are shown as follows.
Table Syntax for Condition Signal Description and True/False Representation (1/2)
Condition signal description column
True/false Satisfiable condition
Input signal Condition specification
True Answerback value matches specification
Element symbol.PV. 0, 1, 2
False Answerback value does not match specification
True Data status matches specification
Element symbol.PV= Data status
False Data status does not match specification
True Output value matches specification
Element symbol.MV. 0, 1, 2
False Output value does not match specification
Element symbol.MV= Data status
True Tracking switch in specified state
Element symbol.TSW. 0,1
False Tracking switch not in specified state
True Tracking switch in specified state
Element symbol.TSW= Data status
False Tracking switch not in specified state
True Backup switch in specified state
Element symbol.BSW. 0, 1
False Backup switch not in specified state
AUT, MAN, CAS, True Block mode matches specification

Element symbol.MODE.
ROUT, TRK, O/S False Block mode does not match specification
True Block is in ROUT (MAN) mode
BUM
False Block is not in ROUT (MAN) mode
True Block is in ROUT (AUT) mode
Element symbol.XMODE. BUA
False Block is not in ROUT (AUT) mode
True Block is in ROUT (CAS) mode
BUC
False Block is not in ROUT (CAS) mode
True Block status matches specification
Element symbol.BSTS. NR, SIM, ANCK
False Block status does not match specification
D030330E.EPS

Condition signal description column True/ Satisfiable condition
Input signal Condition specification false
NR, IOP, OOP, ANS+ True Specified alarm occurring

Element symbol.ALRM.
ANS-, PERR, CNF False No occurrence of specified alarm
True Alarm is in IOP or IOP- status.
Element symbol.XALRM. IOP
False Alarm is in neither IOP nor IOP- status.
PERR, AFL (*1), NR, True Specified alarm in flashing state
Element symbol.AFLS. IOP, OOP, ANS+, ANS-,
CNF False Specified alarm in non-flashing state
NR, IOP, OOP, ANS+ True Canceling the specified alarm detection
Element symbol.AF.
ANS-, PERR, CNF False Detecting the specified alarm
True IOP or IOP- detection is disabled
Element symbol.XAF. IOP
False IOP and IOP- detection is enabled
NR, IOP, OOP, ANS+ True Suppressing the specified alarm
Element symbol.AOFS. CNF, ANS-, PERR,
AOF (*2) False Canceling the specified alarm in suppression
True Sequence setpoint value matches specification
Element symbol.CSV 0, 1, 2
False Sequence setpoint value does not match specification
Element symbol.CSV= Data status
True Remote manipulated output value matches specification
Element symbol.RMV 0, 1, 2
False Remote manipulated output value does not match specification
Element symbol.RMV= Data status
True Bypass switch in specified state
Element symbol.BPSW. 0, 1
False Bypass switch not in specified state
Element symbol.BPSW= Data status
D030331E.EPS
*1: The condition specification of the AFL is the reference in all flashing state.
*2: The condition specification of the AOF is the reference in all suppressing alarm state.

■ Referencing Timer Block (TM)
The syntax for applying the various types of data and data status of a timer (TM) block as
condition test reference signal in a logic chart and the True/False representation in the logic
chart are shown as follows.
Table Syntax for Condition Signal Description and True/False Representation
True Block mode matches specification
Element symbol.MODE. AUT, O/S
False Block mode does not match specification
STOP, RUN, PAUS, True Block status in specified state
Element symbol.BSTS. NR, PALM, CTUP False Block status not in specified state
True Alarm status in specified state
Element symbol.ALRM. NR
False Alarm status not in specified state
True Specified alarm in flashing state
Element symbol.AFLS. AFL (*1), NR
False Specified alarm in non-flashing state
True Canceling the specified alarm detection
Element symbol.AF. NR
False Detecting the specified alarm
True Suppressing the specified alarm
Element symbol.AOFS. NR, AOF (*2)
False Canceling the specified alarm in suppression
D030332E.EPS
■ Referencing Software Counter Block (CTS)

The syntax for applying the various types of data and data status of a software counter
(CTS) block as condition test reference signal in a logic chart and the True/False represen-
tation in the logic chart are shown as follows.
STOP, RUN, NR, True Block status in specified state

Element symbol.BSTS.
PALM, CTUP False Block status not in specified state
D030333E.EPS

■ Referencing Pulse Train Input Counter Block (CTP)
The syntax for applying the various types of data and data status of a pulse train input
counter (CTP) block as condition test reference signal in a logic chart and the True/False
representation in the logic chart are shown as follows.
Condition True/false Satisfiable condition
Input signal
specification
STOP, RUN, PAUS, True Block status in specified state

NR, PALM, CTUP False Block status not in specified state
Element symbol.ALRM. CNF, NR, IOP
Element symbol.XALRM. IOP
AFL (*1), CNF, NR, True Specified alarm in flashing state

Element symbol.AFLS.
IOP False Specified alarm in non-flashing state
Element symbol.AF. CNF, NR, IOP
True IOP or IOP- detection is disabled.
False IOP and IOP- detection is enabled.
CNF, NR, IOP, True Suppressing the specified alarm

Element symbol.AOFS.
D030334E.EPS

■ Referencing Code Input Block (CI)
The syntax for applying the various types of data and data status of a code input (CI) block
as condition test reference signal in a logic chart and the True/False representation in the
logic chart are shown as follows.
Element symbol.BSTS. NR, LO, HI, ERR
D030335E.EPS
■ Referencing Code Output Block (CO)

The syntax for applying the various types of data and data status of a code output (CO)
block as condition test reference signal in a logic chart and the True/False representation in
Element symbol.BSTS. NR, LO, HL
D030336E.EPS

■ Referencing Relational Expression Block (RL)
The syntax for applying the various types of data and data status of a relational expression
(RL) block as condition test reference signal in a logic chart and the True/False representa-
tion in the logic chart are shown as follows.
Input signal
specification
EQ, GT, GE, True Relationship of two data in specified state

Element symbol.X01 to 16.
LT, LE, AND False Relationship of two data not in specified state
D030337E.EPS
The Meanings of the condition specifications are as follows:

Table Meanings of the Condition Specifications
Symbol Name Meanings
EQ Equal to Data 1 = data 2
GT Greater than Data 1 > data 2
GE Great than or equal to Data 1 * data 2
LT Less than Data 1 < data 2
LE Less than or equal to Data 1 ) data 2
AND Logical product The logic product of each pair of bits in data 1 and data 2
D030338E.EPS
■ Referencing Resource Scheduler Block (RS)

The syntax for applying the various types of data and data status of a resource scheduler
(RS) block as condition test reference signal in a logic chart and the True/False representa-
tion in the logic chart are shown as follows.
Input signal
specification
Usage request state matches specification
True
Element symbol.RQ01 to 32. 0, 1 (0: No request 1: Requesting)
False Usage state does not match specification
Permission state matches specification
True
(0: No permission 1: Permitted)
Element symbol.PM01 to 32 0, 1
Permission state does not match
False
specification
Maximum allowable number matches
True
specification
Element symbol.PMH. 0 to 32
Maximum allowable number does not match
False
specification
D030339E.EPS

■ Referencing Valve Monitoring Block (VLVM)
The syntax for applying the various types of data and data status of a Valve Monitoring
(VLVM) Block as condition test reference signal in a logic chart and the True/False repre-
sentation in the logic chart are shown as follows.
Input signal
specification
AUT, True Block mode matches specification

O/S False Block mode does not match specification
True Specified alarm occurring
Element symbol.ALRM. NR
False No occurrence of specified alarm
NR, True Specified alarm in flashing state
AFL (*1) False Specified alarm in non-flashing state
Element symbol.AF. NR
NR, True Suppressing the specified alarm
Valve abnormal matches specification
True
Element symbol.PV01 to 16. 0, 1 (0: Normal 1: Error)
False Valve abnormal does not match specification
Representative valve abnormal matches
specification
True
(0: All valves normal 1: At least one error
Element symbol.PVR. 0, 1 occurred)
Representative valve abnormal does not match
False
specification
Message suppression matches specification
True
Element symbol.MCSW. 0, 1 (0: Not suppressed 1: Suppressed)
False Message suppression does not match specification
D030340E.EPS

■ Referencing Regulatory Control Block
The syntax for applying the block mode, block status, alarm status and data status of a
regulatory control block as condition test reference signal in a logic chart and the True/
False representation in the logic chart are shown as follows.
True Block mode in specified state
Element symbol.MODE. Block mode
False Block mode not in specified state
True Block is in ROUT (MAN) or RCAS (MAN) mode.
BUM
False Block is not in ROUT (MAN) or RCAS (MAN) mode.
True Block is in ROUT (AUT) or RCAS (AUT) mode.
False Block is not in ROUT (AUT) or RCAS (AUT) mode.
True Block is in ROUT (CAS) or RCAS (CAS) mode.
BUC
False Block is not in ROUT (CAS) or RCAS (CAS) mode.
True Block status in specified state
Element symbol.BSTS. Block status
False Block status not in specified state
Element symbol.ALRM. Alarm status
IOP
Element symbol.XALRM.
True Alarm is in VEL or VEL- status.
VEL
False Alarm is in neither VEL nor VEL- status.
Alarm status, True Specified alarm in flashing state
Element symbol.AF. Alarm status
Alarm status, True Suppressing the specified alarm
True Data value matches specification
Element symbol, Data item. Data value
False Data value does not match specification
Element symbol, Data item= Data status
D030341E.EPS

● Data Items of Regulatory Control Blocks for Condition Test
The data items of the regulatory control blocks and the range of the data values that can be
put in the condition column for condition test are listed as follows.
Table Data Items of Regulatory Control Blocks and Range of Data Values for Condition Test (1/3)
TSW 0, 1
CSW 0, 1
RSW 0, 1
BSW 0, 1
TSW 0, 1
CSW 0, 1
RSW 0, 1
BSW 0, 1
TSW 0, 1
CSW 0, 1
RSW 0, 1
BSW 0, 1
CSW 0, 1
BSW 0, 1
PSW 0 to 3
BSW 0, 1
PSW 0 to 3
BSW 0, 1
TSW 0, 1
PSW 0 to 3
RSW 0, 1
BSW 0, 1
TSW 0, 1
PSW 0 to 3
PI-BLEND Blending PI Controller Block RSW 0, 1
BSW 0, 1
RST 0, 1
TSW 0, 1
CSW 0, 1
PSW 0 to 3
RSW 0, 1
BSW 0, 1
STC -1 to 3
D030342E.EPS

TSW 0, 1
RSW 0, 1
TSW 0, 1
RSW 0, 1
TSW 0, 1
RSW 0, 1
TSW 0, 1
BSW 0, 1
BPSW 0 to 4
CSV 0 to 2
PV 0 to 2
MV 0 to 2
TSW 0, 1
BSW 0, 1
BPSW 0 to 4
CSV 0 to 2
PV 0 to 2
MV 0 to 2
TSW 0, 1
PSW 0 to 3
RSW 0, 1
BSW 0, 1
ZONE 1 to 13
ZEND 1 to 13
D030343E.EPS

SW 0 to 4
ZONE 0 to 11
SW 0 to 4
ZONE 0 to 11
PSW 0 to 3
BPSW 0, 1
SW 0 to 4
SS-H/M/L Signal Selector Block
SEL 0 to 3
PSW 0 to 3
AS-H/M/L Autoselector Block SW 0 to 4
SEL 0 to 3
SW 1 to 3
SEL 1 to 2
TSW 0, 1
PSW 0 to 3
FSW 0, 1
RSW 0, 1
TSW 0, 1
RSW 0, 1
BSW 0, 1
SW 0 to 2
SW 0 to 5
SV 0 to 15
D030344E.EPS

■ Referencing Calculation Block ¡ £
The syntax for applying the block mode, block status, alarm status and data status of a
calculation block as condition test reference signal in a logic chart and the True/False
representation in the logic chart are shown as follows.

Input signal
specification
Element symbol.ALRM. CNF, NR
IOP
VEL

AFL (*1)
False Specified alarm in non-flashing state
Element symbol.AF. CNF, NR
CNF, NR, True Suppressing the specified alarm

True Calculation execution result is not 0
Element symbol.ACT. ON
False Calculation execution result is 0
Element symbol.Data item. Data value (*3)
True Data status of specified data matches
Element symbol.Data item= Data status
False Data status of specified data does not match
D030345E.EPS
*3: Only integers can be handled as data values, When the data type of the data item is a floating-point type, the compari-
son is made by rounding off the value.

● Data Items of Calculation Blocks for Condition Test ¡ £
The data items of the calculation blocks and the range of the data values that can be put in
the condition column for condition test are listed as follows.
Table Data Items of Calculation Blocks and Range of Data Values for Condition Test (1/2)
SW 0, 1, 2
Three-Pole Three-Position Selector
SW-33 SW 0 to 3
Switch Block
SW 0 to 3
SW 0 to 16
SW 0 to 17
D030346E.EPS

Table Data Items of Calculation Blocks and Range of Data Values for Condition Test (2/2) £
AND Logical AND Block RV1 0, 1
RV2 0, 1
CPV 0, 1
OR Logical OR Block RV1 0, 1
RV2 0, 1
CPV 0, 1
NOT Logical NOT Block RV 0, 1
CPV 0, 1
SRS1-S Set-Dominant Flip-Flop Block with 1 Output RV1 0, 1
RV2 0, 1
CPV 0, 1
SRS1-R Reset-Dominant Flip-Flop Block with 1 Output RV1 0, 1
RV2 0, 1
CPV 0, 1
SRS2-S Set-Dominant Flip-Flop Block with 2 Outputs RV1 0, 1
RV2 0, 1
CPV1 0, 1
CPV2 0, 1
SRS2-R Reset-Dominant Flip-Flop Block with 2 Outputs RV1 0, 1
RV2 0, 1
CPV1 0, 1
CPV2 0, 1
WOUT Wipeout Block RV1 0, 1
RV2 0, 1
CPV 0, 1
OND ON-Delay Timer Block RV 0, 1
CPV 0, 1
OFFD OFF-Delay Timer Block RV 0, 1
CPV 0, 1
TON One-Shot Block (Rising-Edge Trigger) RV 0, 1
CPV 0, 1
TOFF One-Shot Block (Falling-Edge Trigger) RV 0, 1
CPV 0, 1
GT Comparator Block (Greater Than) CPV 0, 1
GE Comparator Block (Greater Than or Equal) CPV 0, 1
EQ Equal Operator Block CPV 0, 1
D030347E.EPS
*1: ¡ £ Only applicable to CS 3000.

● Calculation Blocks whose Results can be Referenced by One-Shot
Execution ¡ £
The one-shot executable calculation blocks whose calculation results can be referenced for
condition test with “element symbol. ACT.ON” script are shown as follows.
Table One-Shot Executable Blocks for Condition Test ¡ £
Block type Block code Name
ADD Addition Block
DIV Division Block
AVE Averaging Block
OR Logical OR Block
Logic Operation SRS2-R Reset-Dominant Flip-Flop Block with 2 Outputs

Blocks (*1) WOUT Wipeout Block

Calculation CALCU-C General-Purpose Calculation Block with String I/O
D030348E.EPS
*1: ¡ £ Only applicable to CS 3000.

■ Referencing Faceplate Block
The syntax for applying the various types of data and data status of a faceplate block as
Condition signal description column True/
Satisfiable condition
Input signal Condition specification false
True Block mode in specified state

False Block mode not in specified state
True Block is in ROUT (MAN) or RCAS (MAN) mode.
BUM
False Block is not in ROUT (MAN) or RCAS (MAN) mode.
True Block is in ROUT (AUT) or RCAS (AUT) mode.
False Block is not in ROUT (AUT) or RCAS (AUT) mode.
True Block is in ROUT (CAS) or RCAS (CAS) mode.
BUC
False Block is not in ROUT (CAS) or RCAS (CAS) mode.
True Block status in specified state
False Block status not in specified state
IOP
VEL


1 to 99 True Batch step number matches specification
Element symbol.SV. (Valid only for
BSI blocks) False Batch step number does not match specification
True Operation command matches specification
Element symbol.PV01 to 10. 0, 1
False Operation command does not match specification
Element symbol.Data item= Data status
D030349E.EPS

Condition signal description column True/
Satisfiable condition
Input signal (*1) Condition specification false
True Switch display color matches specification

Element symbol.SWCR[1 to n]. 0 to 15
False Switch display color does not match specification
True Switch flashing status matches specification
Element symbol.SWST[1 to n]. 0, 1
False Switch flashing status does not match specification
True Switch operation prohibited status matches specification
Element symbol.SWOP[1 to n]. -15 to 15
False Switch operation prohibited status does not match specification
D0303A0E.EPS
*1: n indicates the number of elements in a one-dimensional array. This is the number of push-button switches in a
faceplate block, and varies with the type of each faceplate block.
■ Referencing SFC Block

The syntax for applying the various types of data and data status of a SFC block as condi-
tion test reference signal in a logic chart and the True/False representation in the logic chart
are shown as follows.
Input signal
specification
MAN, SWMI, True Block mode in specified state

AUT, O/S False Block mode not in specified state
RUN, PAUS, True Block status in specified state

STOP, ABRT False Block status not in specified state


Element symbol.AOFS. AOF (*2) False Canceling the specified alarm in suppression
Element symbol.Dataitem. Data value
Element symbol.Dataitem= Data status
D030350E.EPS
● Range of Data Value When Referencing the Data Items for Condition Test
The ranges of data values when referencing SFC data items in a logic chart for condition
test are shown as follows.
• STEPNO: 1 to 99
• SWCR[5]: 0 to 15
• SWST[5]: 0, 1
• SWOP[5]: -15 to 15

■ Referencing Unit Instrument
The syntax for applying the various types of data and data status of a unit instrument block
Input signal
specification
MAN,SEMI, True Unit mode in specified state

AUT,O/S False Unit mode not in specified state
True Unit status in specified state
Element symbol.BSTS. Unit status
False Unit status not in specified state


True SFC step number matches specification
Element symbol.STEPNO. 1 to 99 SFC step number does not match
False
specification
D030351E.EPS
■ Referencing Process I/O

The syntax for applying the various types of data and data status of a process I/O as
Input signal specification
Contact I/O ON/OFF state matches
True
specification
Element symbol.PV. ON, OFF
Contact I/O ON/OFF state does not match
False
specification
True Contact I/O data status matches specification
Element symbol.PV= Data status Contact I/O data status does not match
False
specification
D030352E.EPS

■ Referencing Global Switch £
The syntax for applying the various types of data and data status of a global switch as
Table Syntax for Condition Signal Description and True/False Representation £
Input signal specification
True Specified global switch status is True.

False Specified global switch status is False.
True Data status of global switch is BAD.
Element symbol.PV= BAD
False Data status of global switch is not BAD.
D030353E.EPS
■ Referencing Common Switch

The syntax for applying the data of a common switch as condition test reference signal in a
logic chart and the True/False representation in the logic chart are shown as follows.
Input signal
specification
Specified internal status switch ON/OFF state
True
matches specification
Specified internal status switch ON/OFF state
False
does not match specification
D030354E.EPS

■ Referencing Annunciator Message
The syntax for applying the various types of data and data status of an annunciator mes-
sage as condition test reference signal in a logic chart and the True/False representation in
Input signal
specification
Annunciator occurrence state matches
True specification
Element symbol.PV. ON, OFF (On: Occurred OFF: No occurrence)
Annunciator occurrence state does not match
False
specification
True Flashing state
Element symbol.AFLS. AFL
False Steady state (non-flashing state)
True Alarm suppressing state
Element symbol.AOFS. AOF
False Steady state (non-alarm suppressing state)
Repeated warning status is consistent with
True specification
Element symbol.RP ON, OFF (ON: Wait for repeated warning OFF: NR)
Repeated warning state is not consistent with
False
specification
D030355E.EPS
■ Referencing Communication I/O

The syntax for applying the various types of data and data status of a Communication I/O
Input signal
specification
Specified bit ON/OFF state matches
True
specification
Specified bit ON/OFF state does not match
False
specification
Specified bit data status matches
True
specification
Specified bit data status does not match
False
specification
D030356E.EPS


Logic Chart
When referencing a logic chart for condition test, a block mode and an alarm status
of a logic chart can be used as a reference signal in other logic charts.
■ Referencing Logic Chart Block Mode

The specified logic chart block mode can be used as reference signal in logic charts. The
syntax for applying the logic chart block mode as condition test reference signal and the
True/False representation are shown as follows.
Input signal
specification
True Specified Block mode is True.
False Specified Block mode is False.
D030357E.EPS
block mode.
■ Referencing Logic Chart Alarm Status

The specified alarm status of a logic chart can be used as reference signal in logic charts.
The syntax for applying the alarm status of logic chart as condition test reference signal
and the True/False representation are shown as follows.
Input signal
specification
True Specified Alarm Status is True.
Element symbol.ALM NR
False Specified Alarm Status is False.
True Specified Alarm symbol is flashing.
False Specified Alarm symbol is not flashing.
True Alarm Detection Disabled is True.
False Alarm Detection Disabled is False.
True Alarm Inhibition is True.
False Alarm Inhibition is False.
D030358E.EPS
*1: The condition test for Alarm Symbol Flashing can only test the flashing status of each block or symbol, can not test the
flashing status of each alarming item.
*2: The condition test for Alarm Inhibition can only test the inhibition status of each block or symbol, can not test the


Sequence Table in a Logic Chart
When referencing a sequence table for condition test, the true or false status of the
condition for one-shot execution of the referenced sequence table as well as the
block mode and status of the sequence table can be applied.
To reference a sequence table whose number of rules is extended over multiple
sequence tables, the tag name of the base sequence table needs to be specified.
■ Referencing the Entire Sequence Table

A specified sequence table can be one-shot started and the True/False status of the entire
sequence table’s condition can be referenced by a logic chart.
The syntax for referencing an entire sequence table condition as the condition test signal in
a logic chart and the True/False representation are shown as follows.
Input signal column
specification
Y At least one target condition rule is satisfied.
Element symbol.SD R
N None of the target condition rules is satisfied.
D030359E.EPS
The following should be taken into account when referencing the entire sequence table.
referenced sequence table are valid. Ignore any signal description.
rule condition is false. If the Y/N pattern of such condition rule is unspecified, the
table.
• When there exist no steps to be executed in the referenced sequence table, the
previous true/false status of condition is maintained as a current reference result.
• When Step 00 exists in the reference destination, rules that belong to Step 00 will also
be executed. However, when no steps exist as an execution target, the reference
result of Step 00 is ignored.
are possible.

■ Referencing a Particular Step in a Sequence Table
A specified sequence table can be one-shot started and a particular step of the sequence
table can be referenced by a logic chart.
The syntax for a particular sequence table step reference as the condition test signal in a
logic chart and the True/False representation are shown as follows.
Input signal column
specification
At least one of the conditions for steps 00
Y
and xx is satisfied.
None of the conditions for steps 00 and xx is
N
satisfied.
D030360E.EPS
The following should be taken into account when referencing a corresponding rule number.
• When referencing a particular step in a sequence table, only condition signal descrip-
tions of the referenced sequence table are valid. Ignore any action signal description.
table.
are possible.

■ Referencing Sequence Table Step Label
A sequence progress state can be confirmed by referencing the related sequence table
step labels. However, it only check if the sequence step corresponding to the specified
sequence step label is being processed or not, it does not involve the conditions test of the
step’s True/False status.
The syntax for a Sequence Table Step Label Reference as the condition test signal in a
logic chart and the True/False representation are shown as follows.
Input signal column
specification
Y Current execution step label is xx.
N Current execution step label is other than xx.
D030361E.EPS
■ Referencing Sequence Table Block Mode

The specified sequence table block mode can be used as reference signal in a logic chart.
The syntax for applying the sequence table block mode as condition test reference signal in
a logic chart and the True/False representation are shown as follows.
Input signal
specification
True Specified Block mode is True.
False Specified Block mode is False.
D030362E.EPS
The following points should be taken into consideration when referencing a sequence table
block mode.

■ Referencing Sequence Table Alarm Status
The specified alarm status of a sequence table can be used as reference signal in a logic
chart.
The syntax for applying the alarm status of sequence table as condition test reference
signal in a logic chart and the True/False representation are shown as follows.
Rule Columns
Input signal
specification
True Specified Alarm Status is True.
False Specified Alarm Status is False.
True Specified Alarm symbol is flashing.
False Specified Alarm symbol is not flashing.
True Alarm Detection Disabled is True.
False Alarm Detection Disabled is False.
True Alarm Inhibition is True.
False Alarm Inhibition is False.
D030363E.EPS
*1: The condition test for Alarm Symbol Flashing can only test the flashing status of each block or symbol; it can not test
the flashing status of each alarming item.
*2: The condition test for Alarm Inhibition can only test the inhibition status of each block or symbol; it can not test the

D3.3.10 Action Signal Description: Status Manipulation for Other

Function Blocks and I/O Data
Logic chart block can be used to manipulate the execution, the mode or status
change of other function blocks as well as the status change of process I/O, soft-
ware I/O and communication I/O.
■ Function Blocks and I/O Data that can be Manipulated from Logic Chart
Function blocks for which status manipulation that can be performed from the sequence
table
are:
• Switch instrument blocks
• SFC Blocks
• Unit instrument Blocks
In addition, the following I/O data can be manipulated from logic chart:
• Process I/O
• Software I/O (internal switch, annunciator message, message output for sequence
control)

■ Status Manipulation of Switch Instrument Block
The syntax for applying the various functions of a switch instrument block as status ma-
nipulation signal in a logic chart and the actions corresponding to True/False are shown as
follows.
Table Syntax for Action Signal Description and Actions Corresponding to True/False
Manipulation signal description
True/False Manipulation description
Output signal Action Specifications
MAN, AUT, CAS, True Block mode change command

ROUT, O/S False Disable
ANS+, ANS-, IOP, True Release detection of specified alarm

Element symbol.AF.
PERR, OOP, CNF False Perform detection of specified alarm
True Disables IOP and IOP- detection
False Enables IOP and IOP- detection
ANS+, ANS-, PERR, True Perform suppression of specified alarm

CNF, IOP, AOF (*1), OOP False Release suppression of specified alarm
True Perform group verification of alarms
False Disable
True Setting of sequence setpoint value (CSV) (*2)
0, 1, 2
False Disable
True Set CSV to 0
P0
False Set CSV to 2
Element symbol.CSV.
True Set CSV to 1
P1
False Disable
True Set CSV to 2
P2
False Set CSV to 0
True Tracking switch (0; OFF, 1; ON)
Element symbol.TSW. 0, 1
False Disable
True Bypass switch (0; OFF, 1; ON)
Element symbol.BPSW. 0, 1
False Disable
True Backup switch (0; OFF, 1; ON)
Element symbol.BSW. 0, 1
False Disable
True Switch to CAL or release CAL
Element symbol.PV. =XCAL (*3)
False –
D030364E.EPS
*1: The AOF specification is valid only with respect to the change in the alarm suppression specification. This operation
performs alarm suppression for all alarms with the exception of the NR alarm.
*2: Sequence setpoint value (CSV) data is written when the switch instrument manipulated output value (MV) is set from
another function block. If the switch instrument block is in AUT or CAS state, output is executed after the sequence
setpoint value (CSV) is written in the manipulated output value (MV).
*3: The type of logic chart that =XCAL is applied should be set to [One-Shot Processing Type (O)].

■ Status Manipulation of Timer Block (TM)
The syntax for applying the various functions of a Timer Block (TM) as status manipulation
signal in a logic chart and the actions corresponding to True/False are shown as follows.
True Timer stop command
STOP
False Disable
True Timer startup command
START
False Timer stop command (*1)
Element symbol.OP.
True Restart command
RSTR
False Disable
True Pause command
WAIT
False Restart command (*1)
D030365E.EPS
*1: When connected to the function blocks other than logic chart and sequence table blocks via sequence connection, the
true actions are valid while the false actions are invalid.
■ Status Manipulation of Software Counter Block (CTS)

The syntax for applying the various functions of a software counter (CTS) block as status
manipulation signal in a logic chart and the actions corresponding to True/False are shown
as follows.
True Operation manipulation of software counter
ON
False Disable
Element symbol.ACT.
True Software counter stop command
OFF
False Disable
D030366E.EPS

■ Status Manipulation of Pulse Train Input Counter Block (CTP)
The syntax for applying the various functions of a Pulse Train Input Counter (CTP) block as
status manipulation signal in a logic chart and the actions corresponding to True/False are
shown as follows.
True Pulse-input counter stop command
STOP
False Disable
True Pulse-input counter start command
START
False Disable
Element symbol.OP.
True Restart command
RSTR
False Disable
True Pause command
WAIT
False Disable
True Release detection of specified alarm
Element symbol.AF. IOP, CNF
False Perform detection of specified alarm
True Perform suppression of specified alarm
Element symbol.AOFS. IOP, CNF, AOF (*1)
False Release suppression of specified alarm
False Disable
D030367E.EPS
■ Status Manipulation of Code Input Block (CI)

The syntax for applying the various functions of a Code Input (CI) block as status manipula-
tion signal in a logic chart and the actions corresponding to True/False are shown as
follows.
True Code-input read command
False Disable
D030368E.EPS

■ Status Manipulation of Code Output Block (CO)
The syntax for applying the various functions of a Code Output (CO) Block as status
as follows.
True Code output command
False Disable
D030369E.EPS
■ Status Manipulation of Resource Scheduler Block (RS)

The syntax for applying the various functions of a Resource Scheduler (RS) Block as status
as follows.
Usage cancel/request command for specified number
True
Element symbol.RQ01 to 32. 0, 1 (1; request, 0; cancel)
False Disable
True Setting of maximum allowed number (m32)
Element symbol.PMH. 0 to 32
False Disable
Group resources all request/cancel
True
Element symbol.ACT. ON, OFF (ON; request, OFF; cancel)
False Disable
D030370E.EPS
■ Status Manipulation of Valve Monitoring Block (VLVM)

The syntax for applying the various functions of a Valve Monitoring (VLVM) Block as status
as follows.
True Message suppression (1; suppress 0; do not suppress)
Element symbol.MCSW. 0, 1
False Disable
D030371E.EPS

■ Status Manipulation of Regulatory Control Block
The syntax for applying the various functions of a regulatory control block as status ma-
nipulation signal in a logic chart and the actions corresponding to True/False are shown as
follows.
MAN, CAS, RCAS, True Block mode change command

AUT, ROUT, PRD, O/S False Disable
Alarm status excluding True Release detection of specified alarm

Element symbol.AF.
NR False Perform detection of specified alarm
Alarm status excluding True Perform suppression of specified alarm

NR, AOF (*1) False Release suppression of specified alarm
False Disable
True Data setting
Element symbol.Data Item Data value
False Disable
True Switch PV to CAL status
Element symbol.PV= CAL
False Release PV from CAL status
False –
Element symbol.SUM0. =XCAL (*2)
False –
D030372E.EPS

● Data Items of Regulatory Control Blocks for Status Manipulation
The data items of the regulatory control blocks and the range of the data values that can be
applied for status manipulation are listed as follows.
Table Data Items of Regulatory Control Blocks and Range of Data Values for Status Manipulation
(1/3)
TSW 0, 1
CSW 0, 1
BSW 0, 1
RSW 0, 1
TSW 0, 1
CSW 0, 1
BSW 0, 1
RSW 0, 1
TSW 0, 1
CSW 0, 1
BSW 0, 1
RSW 0, 1
CSW 0, 1
BSW 0, 1
PSW 0 to 3
BSW 0, 1
PSW 0 to 3
BSW 0, 1
TSW 0, 1
PSW 0 to 3
BSW 0, 1
RSW 0, 1
TSW 0, 1
PSW 0 to 3
PI-BLEND Blending PI Controller Block BSW 0, 1
RSW 0, 1
RST 0, 1
TSW 0, 1
CSW 0, 1
PSW 0 to 3
BSW 0, 1
RSW 0, 1
STC -1 to 3
D030373E.EPS

(2/3)
TSW 0, 1
RSW 0, 1
TSW 0, 1
RSW 0, 1
TSW 0, 1
RSW 0, 1
TSW 0, 1
BSW 0, 1
BPSW 0 to 4
SIMM 0 to 1
0, 1, 2, P0, P1,
CSV P2 (*1)
TSW 0, 1
BSW 0, 1
BPSW 0 to 4
SIMM 0 to 1
0, 1, 2, P0, P1,
CSV P2 (*1)
TSW 0, 1
PSW 0 to 3
BSW 0, 1
RSW 0, 1
ZONE 1 to 13
ZEND 1 to 13
D030374E.EPS
*1: The values set to the CSV varied according to the data in the manipulation rule column and setting range as shown
below.
0: CSV=0 when the manipulation rule column is “TRUE,” disabled when “FALSE.”
P0: CSV=0 when manipulation rule column is “TRUE,” CSV=2 when “FALSE.”
P1: CSV=1 when manipulation rule column is “TRUE,” disabled when “FALSE.”
P2: CSV=2 when manipulation rule column is “TRUE,” CSV=0 when “FALSE.”

(3/3)
SW 0 to 4
ZONE 0 to 11
SW 0 to 4
ZONE 0 to 11
PSW 0 to 3
BPSW 0, 1
SS-H/M/L Signal Selector Block SW 0 to 4
PSW 0 to 3
AS-H/M/L Auto-Selector Block
SW 0 to 4
SS-DUAL Dual-Redundant Signal Selector Block SW 1 to 3
TSW 0, 1
PSW 0 to 3
FSW 0, 1
RSW 0, 1
TSW 0, 1
RSW 0, 1
BSW 0, 1
SW 0 to 2
RST 0, 1
HSW 0, 1
SW 0 to 5
SV 0 to 15
D030375E.EPS

■ Status Manipulation of Calculation Block ¡ £
The syntax for applying the various functions of a calculation block as status manipulation
True One-shot startup (with parameter)
mm (*1)
False Disable
Element symbol.ACT.
True One-shot startup (without parameter)
ON
False Disable

Element symbol.AF.

False Disable
True Data setting
Element symbol.data item. Data value
False Disable
True Set PV data status to CAL
Element symbol.CPV= CAL
False Release the CAL data status of CPV
Element symbol.CPV. =XCAL (*3)
False –
Element symbol.CPV1. =XCAL (*3)
False –
Element symbol.CPV2. =XCAL (*3)
False –
D030376E.EPS
*1: mm is required parameter for one-shot execution of the batch data setting block and batch data collection block. Data
that will be set during a one-shot execution according to the mm value.
mm=0: All setting data are set to 0.
mm=1 to 16: Only the specified data (DTn) is set.
mm=17: All data will be set.

● Data Items of Calculation Blocks for Status Manipulation
The data items of the calculation blocks and the range of the data values that can be
applied for status manipulation are listed as follows.
Table Data Items of Calculation Blocks and Range of Data Values for Status Manipulation
SW 0, 1, 2
SW-33 Three-Pole Three-Position Selector Switch Block SW 0 to 3
SW 0 to 3
ADL Interstation Connection Block SIMM 0, 1
SW 0 to 16
SW 0 to 17
D030377E.EPS

● One-Shot Executable Calculation Blocks ¡ £
The one-shot executable calculation blocks can be applied for status manipulation are
shown as follows.
Table One-Shot Executable Calculation Blocks for Status Manipulation ¡ £
Block Type Model Name Description
ADD Addition Block
Arithmetic MUL Multiplication Block

Calculation DIV Division Block
AVE Averaging Block
OR Logical OR Block
Logic Operation (*1)
WOUT Wipeout Block
General-purpose CALCU General-Purpose Calculation Block

Calculation CALCU-C General-Purpose Calculation Block with String I/O
Calculation BDSET-2L Two-Batch Data Set Block

Auxiliary-2 BDSET-2C Two-Batch String Data Set Block
D030378E.EPS
*1: ¡ £ Logic operation blocks are only available for CS 3000.

● Calculation Blocks Requiring One-Shot Parameter mm
The calculation blocks that require mm parameter for one-shot execution when applied for
status manipulation are shown as follows.
Table One-Shot Parameter Required Calculation Blocks for Status Manipulation
Parameter setting
Block code Name Comments
Range (mm)
BDSET-1C One-Batch String Data Set Block Individual data
0 to 17
BDSET-2L Two-Batch Data Set Block setting

BDA-L Batch Data Acquisition Block Individual data
0 to 17
BDA-C Batch String Data Acquisition Block acquisition
D030379E.EPS
Note: mm is required parameter for one-shot execution of the batch data setting block and batch data collection block. Data
that will be set during a one-shot execution according to the mm value.
mm=0: All setting data are set to 0.
mm=1 to 16: Only the specified data (DTn) is set.
mm=17: All data will be set.

■ Status Manipulation of Faceplate Block
The syntax for applying the various functions of a faceplate block as status manipulation
True Change block mode
False Disable
True Change block status
Element symbol.BSTS. Block Status
False Release block status
Alarm Status excluding True Change alarm status

Element symbol.ALRM.
NR False Release alarm status
Alarm Status excluding True Release detection of specified alarm

Element symbol.AF.
Alarm Status excluding True Perform suppression of specified alarm

False Disable
True Process number setting

Element symbol.SV. 1 to 99 (Only Valid with BSI Block)
False Disable
True Control command setting
Element symbol.PV01 to 10. 0,1
False Disable
Element symbol.SWCR [1 to n]. True Change color of switch display

0 to 15
(*2) False Disable
Element symbol.SWST [1 to n]. True ON/OFF of switch flashing status

0,1
(*2) False Disable
Element symbol.SWOP [1 to n]. True Changing of switch control disable status

-15 to 15
(*2) False Disable
D030380E.EPS
*2: n indicates the number of elements in a one-dimensional array. This is the number of push-button switches in a
faceplate block, and varies with the type of each faceplate block.

■ Status Manipulation of SFC Block
The syntax for applying the various functions of an SFC block as status manipulation signal
in a logic chart and the actions corresponding to True/False are shown as follows.
True Block mode change command
Element symbol.MODE. MAN, AUT
False Disable
RUN, PAUS True Block status change command

ATOP, ABRT False Disable
Alarm Status excluding True Release detection of specified alarm

Element symbol.AF.
Alarm Status excluding True Perform suppression of specified alarm

False Disable
True Data setting
Element symbol.Data Item Data Value
False Disable
True Set PV data status to CAL
Element symbol.PV= CAL
False release the CAL data status of PV
False –
D030381E.EPS
● Range of Data Value When Manipulating the Data Items

The ranges of data values when manipulating the SFC data items in a logic chart for status
manipulation are shown as follows.
• STEPNO: 1 to 99
• SWCR[5]: 0 to 15
• SWST[5]: 0, 1
• SWOP[5]: -15 to 15

■ Status Manipulation of Unit Instrument
The syntax for applying the various functions of a unit instrument block as status manipula-
follows.
True Unit mode change command
Element symbol.MODE. MAN, SEMI, AUT
False Disable
Unit status change True Unit status change command

Element symbol.UBSC.
command name False Disable

Element symbol.AF.

False Disable
True Change SFC step number
Element symbol.STEPNO. 1 to 99
False Disable
D030382E.EPS
■ Status Manipulation of Process I/O ¡ £

The syntax for applying the various functions of a process I/O as status manipulation signal
in a logic chart and the actions corresponding to True/False are shown as follows.
True Contact output ON (nonlatched)
L
False Contact output OFF
Element symbol.PV.
True Begin flashing output
F
False End flashing output (*1)
D030383E.EPS
*1: When the flashing stops, the contact output itself is in the ON state.
SEE ALSO
For more information about pulse output, see paragraphs “● Pulse Contact Output : PFCS/KFCS2/
KFCS/SFCS” and “● Pulse Contact Output : LFCS2/LFCS” in section “■ Manipulating Status Output of I/
O Module” of chapter A3.2.2, “Contact Output.”

■ Status Manipulation of Global Switch £
The syntax for applying the various functions of a global switch as status manipulation
The status manipulation can be only applied to the global switches assigned in the same
control station of the logic chart.
Table Syntax for Action Signal Description and Actions Corresponding to True/False £
True Turn ON specified global switch. (Nonlatched)
Element symbol.PV. L
False Turn OFF specified global switch.
D030384E.EPS
■ Status Manipulation of Common Switch

The syntax for applying the various functions of a common switch as status manipulation
True Common switch output ON (nonlatched)
False Common switch output OFF
D030385E.EPS
■ Status Manipulation of Annunciator Message

The syntax for applying the various functions of an annunciator message as status manipu-
lation signal in a logic chart and the actions corresponding to True/False are shown as
follows.
True Annunciator output ON (nonlatched)
False Annunciator output OFF
Repeated warning specification
True
Element symbol.RP. ON, OFF (ON: Repeated warning, OFF: Release)
False Disable
True Perform suppression of specified alarm
Element symbol.AOFS. AOF
False Release suppression of specified alarm
False Disable
D030386E.EPS

■ Status Manipulation of Sequence Message Output
The syntax for applying the various functions of a Sequence Message Output as status
as follows.
The following types of sequence message output are supported:
• Print message output
• Operator guide message output
• Multimedia function message output
• Sequence message request
• PICOT supervisory computer event message output
• Event message output for supervisory computer
• Signal event message output
• SFC/SEBOL return event message output
True Message output without parameter
NON
False Disable
Element symbol.PV.
True Message output with parameter
mm (*1)
False Disable
D030387E.EPS
*1: mm can specify integer data (2-byte long integer data).

Range: -32768 to 32767
■ Status Manipulation of Communication I/O

The syntax for applying the various functions of a communication I/O as status manipula-
follows.
Manipulation signal Manipulation specification
True The bit turns ON (nonlatched)
False The bit turns OFF
D030388E.EPS

D3.3.11 Syntax for Action Signal Description: Status

Manipulation of Logic Chart
Logic chart status manipulation can change the block mode of a logic chart, it can
also start a logic chart for one-shot execution.
■ Logic Chart One-Shot Execution

The following scripts can be used to define an output signal element to start a logic chart
one-shot execution.
True/False Action
True Execute logic chart
False Disable
D030389E.EPS
• When action signal specified to start an one-shot execution of a function block, the
target block can start another block for one-shot execution. The chain start can be
nested seven times.
• When output to the one-shot function block fails, and the failure is caused by one of
the following reasons, a system alarm will be triggered.
• The destination logic chart is used to start another logic chart, and the chain start is
nested more than seven times.
• The function block connected to the output terminal is in O/S mode.
• The function block connected to the output terminal is udder online maintenance.
■ Logic Chart Block Mode Change

The block mode of a logic chart can be changed. Changing the block mode of the logic
chart can manipulate the logic block to pause the execution (MAN mode) or to restart the
execution (AUT mode).
The following scripts can be used to define an output signal element to change block mode
of a logic chart block.
True Change the block’s mode
False Disable
D030390E.EPS

D3.3.12 Syntax for Action Signal Description: Status

Manipulation of Sequence Table from Logic Chart
The status manipulation to sequence table blocks can not only change the data or
data status in the sequence table, but also can start a sequence table and control the
whole processing of the sequence table from the condition test to status manipula-
tion output.
When manipulating or referencing a sequence table whose number of rules is ex-
tended over multiple sequence tables, the tag name of the base sequence table
needs to be specified.
The following types of status manipulation may be applied to sequence tables.
• Referencing an entire sequence table
• Executing a particular sequence table step
• Setting a execution label to a sequence table step
• Changing a sequence table block mode
■ Executing an Entire Sequence Table

A sequence table defined to an output operation element in a logic chart (transition destina-
tion sequence table) can be started for a one-shot execution.
When the transition destination sequence table is not a step type sequence table, the entire
sequence table will be executed.
When the transition destination sequence table is a step type sequence table, the step
corresponding to the transition process in the sequence table will be executed.
From the transition sequence table, another sequence table can be started as a transition
table for condition test or status manipulation. The chain start can be nested for 7 times
including the first sequence table.
True Execute the specified table
False Disable
D030391E.EPS

■ Executing a Particular Step in a Sequence Table
The syntax for executing a particular sequence table step in a logic chart and the actions
corresponding to True/False are shown as follows.
Manipulation signal description column
Action True/False Manipulation description
Output signal
specification
Branch to step xx in the specified table and
True
Element symbol.SA. xx execute steps xx and 00.
False Disable
D030392E.EPS
xx: Specify a step label with up to two alphanumeric characters.
From the transition sequence table, another sequence table can be started as a transition
table for condition test or status manipulation. The chain start can be nested for 7 times
including the first sequence table.
The action rule of the sequence table behaves as follows according to the types (step type
or nonstep type) of the execution origin and the execution destination sequence tables.
Table Execution Target Action Rule in Accordance with Types of Sequence Table
Branching source Branching destination Execution target action rule

Nonstep type Rules for a specified step and step 00
Nonstep type
Step type All rules
Nonstep type Rules for a specified step and step 00
Step type
Step type All rules
D030393E.EPS
When a logic chart starts a sequence table specified in the output operation element, the
started sequence table run its transition to start the transition destination sequence table.
The transition destination sequence table will run its step 00 and the transition specified
step for condition test and the status manipulation.
If the specified transition step of the transition sequence table can not be found, an error
will be generated, the step can not be executed. However, if the transition sequence table
has step 00, the step 00 will be executed.
When execute an entire sequence table to a non step type sequence table, all rules will be
executed.

■ Setting an Execution Label to a Step in a Sequence Table
An execution label can be set to a sequence table step, this action is different from the
executing a particular sequence table step, it only set the execution label to a specified
sequence table step but does not execute the step. The set step will be executed first when
the sequence table is started the next time.
The syntax for setting an execution label to a sequence table step as the action signal in a
logic chart and the actions corresponding to True/False are shown as follows.
Action signal description column
Output signal
specification
True Set execution label to step xx
Element symbol.PV. xx
False Disable
D030394E.EPS
xx: Specify a step label with up to two alphanumeric characters.
■ Changing Sequence Table Block Mode

The block mode of a sequence can be changed from a logic chart. Changing the block
mode of a sequence table block can manipulate the sequence table to pause the execution
(MAN mode) or to restart the execution (AUT mode).
When a sequence table is paused by changing to MAN mode, the state of the sequence
table will be kept.
The syntax for changing a sequence table block mode as an action signal in a logic chart
and the actions corresponding to True/False are shown as follows.
Output signal
specification
True Change the block’s mode
Element symbol.MODE. AUT, MAN, O/S
False Disable
D030395E.EPS
■ Pause and Restart a Sequence Table

Some sequence tables are running in a fixed scan cycle while some others are staring,
pausing or restarting in accordance with process procedures. To pause a running se-
quence table, and to restart a paused sequence table is possible. The scripts may be
described in a sequence table for a sequence table’s Pause and Restart are shown as
follows.
Table Syntax for Output Signal Scripts and Action Description
Output signal
specification
True Starts or restarts sequence table
Element symbol.XS. ON
False Pause Sequence table
D030399E.EPS

D3.3.13 Behavior of Logic Chart Internal Timer

Logic chart block has an internal timer to control the processes of itself.
■ Behavior of Internal Timer

The process timer of a logic chart is used to execute the on-delay timer and the off-delay
timer. The timer starts when the logic chart itself changes to AUT mode.
Setting range: 0 - 10,000 (sec.)

Table Timer Specification
Number of timers Total number of logic operators (64)
Mode and status The timer itself has neither a mode nor status.
Pause Not supported
When PT = 0 or the input signal changes
Start condition
(on-delay timer 0->1; off-delay timer 1 ->0)
Start action 0 start
1. The input signal inverses from the start status
Stop condition 2. Block changes to MAN mode
3. Timer count up (PT _ ST)
Stopped by stop condition 1, the elapsed time reset.
Stop Action
Stopped by stop condition 2 or 3, the elapsed time is kept.
Timer set value (ST) Set on HIS ( 0 - 10,000 sec.)
D030396E.EPS
On-delay timer behaves as illustrated below.
ST
PT
MODE AUT MAN AUT

IN 0 1 0 1 0 1
OUT 0 1 0
PT: Elapsed time of internal timer ( 0 to 10,000 sec.)

ST: Set time of internal timer ( 0 to 10,000 sec.)
D030397E.EPS
Figure Behavior of on-delay timer

D3.3.14 Data Items of Logic Chart Block - LC64

The table below shows the data items of the Logic Chart Block (LC64):
■ Data Items
Table Data Items of the logic Chart Block (ST-16)
Entry parnitted
or Not
MODE Block mode O/S (AUT)
ALRM Alarm status NR
Alarm flashing status
AFLS 0
AF Alarm detection 0
AOFS Alarm inhibition 0
UAID User application ID 0
ST01 - 64 Set time of internal timer 0 to10000 (sec.) 0 (sec.)
PT01 - 64 Elapsed time of internal timer 0 to10000 (sec.) 0 (sec.)
D030398E.EPS

SEE ALSO
For a list of valid block mode of the LC64, see D3.1.2 “Block Mode of Sequence Control Blocks.”

<Toc> <Ind> <D3.4 Switch Instrument Block> D3-171
D3.4 Switch Instrument Block

The switch instrument blocks are used to start, stop, monitor and manipulate the
status of various types of instruments.
■ Switch Instrument Block

▼ Connection
The switch instrument block (ST16, ST16E) is a function block which is often used to start/
stop motors and pumps and monitor or manipulate open-close state of the motor-operated
valves. In most cases, this type of blocks is used in combination with the sequence table
block (ST16, ST16E) and the Logic Chart Block (LC64).
A function block chart of the switch instrument block is shown below.
Answerback Remote Sequence

SWI output value setpoint
bypass function
BPSW=0
RMV CSV
INT BPSW=1
Answerback MAN
PV
check function
ROUT CAS, AUT
CAL MV
BPSW=0 BPSW=1
Answerback
input function
Remote/local Output signal
input function conversion function
RAW
IN TSI OUT
D030401E.EPS
Figure Function Block Chart of the Switch Instrument Block

There exist 10 different types of switch instrument blocks according to the difference
between the answerback input points and output points.
The table below lists the switch instrument blocks.
A list of switch instrument blocks is shown as follows.
• SI-1: Switch instrument block with 1 input
• SI-2: Switch Instrument Block with 2 Inputs
• SO-1: Switch Instrument Block with 1 Output
• SO-2: Switch instrument block with 2 outputs
• SIO-11: Switch Instrument Block with 1 Input, 1 Output
• SIO-12: Switch Instrument Block with 1 Input, 2 Outputs
• SIO-21: Switch Instrument Block with 2 Inputs, 1 Output
• SIO-22: Switch Instrument Block with 2 Inputs, 2 Outputs
• SIO-12P: Switch Instrument Block with 1 Input, 2 One-Shot Outputs
• SIO-22P: Switch Instrument Block with 2 Inputs, 2 One-Shot Outputs
The table below shows the connection methods and connection destinations of the switch
instrument block I/O terminals.
Table Connection Method and Connection Destination of Switch Instrument Block I/O Terminals
Code I/O terminal Status Terminal

Data Data Condition Process Software Function
manipul- connecti-
ation on
SI-1 Answerback
IN
SI-2 I/O terminal
Remote/local
TSI
I/O terminal
Output
SO-1 OUT
terminal
SO-2
Interlock
INT switch input
terminal
Answerback
IN
input terminal
Remote/local
TSI
I/O terminal
SIO-11
SIO-12 Answerback
SIO-21 SWI bypass input
SIO-22 terminal
SIO-12P
Output
SIO-22P OUT
terminal
Interlock
INT switch input
terminal
D030402E.EPS
: Connection is available only when connecting to a switch block (SW-33, SW-91).

■ Example of Using Switch Instrument Block
An outline of the function manipulating the motor-operated valve is explained in the switch
instrument block (SIO-22P) faceplate shown below.
TAG NO.
AUT
Push OPEN
Push
CLOSE
SEQTYPE1
*VALVE*
1 to 2 sec
Open-
output 1 to 2 sec
OPEN
Output
Close-output CLOSE
Valve
limit
switch
Motor-operated valve
D030403E.EPS
Figure Functional Schematic Diagram of Switch Instrument Block (SIO-22P)

■ Process Timing
The process timing of switch instrument block is only based on periodical start period. The
periodic start period is based on basic scan period.
■ List of Switch Instrument Block Functions

The switch instrument block function varies by the type of the block. The table below lists
major functions of switch instrument blocks.
Table List of Switch Instrument Block Functions by Block Type (1/2)
Code
SI-1 SI-2 SO-1 SO-2 SIO-11
Function
Number of answerback points 1 2 1
Number of output points 1 2 1
Block mode
Block status
Alarm status
Answerback input
Illegal Answerback Alarm Detection
Remote/local input
Answerback check
Output signal conversion
Answerback bypass
Answerback tracking
Calibration function
Mode change interlock
Initialization manual mode
Manual mode fallback
Simulation
D030404E.EPS
: Yes
Blank: No

Table List of Switch Instrument Block Functions by Block Type (2/2)
Code
SIO-12 SIO-21 SIO-22 SIO-12P SIO-22P
Function
Number of answerback points 1 2 2 1 2
Number of output points 2 1 2 2 2
Block mode
Block status
Alarm status
Answerback input
Remote/local input
Answerback check
Output signal conversion
Answerback bypass
Answerback tracking
Calibration
Mode change interlock
Initialization manual mode
Manual mode fallback
Simulation
D030405E.EPS
: Yes
Blank: No
SEE ALSO
• For the types of alarm processing possible for the switch instrument blocks, see D3.1.1 “Alarm Processing
of Sequence Control Blocks.”
• For more information about alarm processing, see C5 “Alarm Processing - FCS.”

■ Answerback Input
▼ Direction of Answerback
In answerback input function, the limit switch signal indicating the valve’s open/close status
is entered from the answerback input terminal (IN) to generate the answerback input value
(PV). Contact input and internal status switch can be specified for the answerback signal
input destination. The answerback input signal is converted into the answerback input
value (PV) inside the switch instrument. This answerback input value varies depending
upon the answerback input direction and the input status of the valve limit switch. The table
below lists the answerback input values.
Table List of Answerback Input Value
Number of Valve limit (*1)

Action of switch status
answerback Answerback input value (PV)
answerback
point n n+1
ON - 2
Direct
OFF - 0
1
ON - 0
Reverse
OFF - 2
ON OFF 2
OFF OFF 1
Direct
OFF ON 0
ON ON Retain the previous PV value (*2)
ON OFF 0
OFF OFF Retain the previous PV value (*2)
Reverse
OFF ON 2
ON ON 1
2
OFF ON 2
Reversed connection OFF OFF 1

direct action ON OFF 0
ON ON Hold previous value (*2)
OFF ON 0
Reversed connection OFF OFF Hold previous value (*2)

reversed action ON OFF 2
ON ON 1
D030406E.EPS
*1: n in the table indicates the connection destination element of the open answerback signal specified to the answerback
input terminal. n+1 is the connection destination element of the close answerback signal, indicating the next element
that follows the element specified to n.
*2: This is an abnormal event in which input from full-open signal and full-close signal occurs simultaneously. The
answerback undefined alarm (PERR) occurs.
The answerback input direction is specified in the Function Block Detail Builder.
• Direction of Answerback:
Select from [Direct], [Reverse], [Reversed connection direct action] or [Reversed
connection direction direct action].
Default is [Direct].

● Data Status Accompanied by Alarms
If a full-open signal and a full-close signal are input simultaneously, or at least one of the
input destinations of the input target element is abnormal, the data status of the
answerback input value (PV) becomes invalid (BAD).
If the data status of the answerback input value becomes invalid (BAD), the input open
alarm (IOP) will occur.
If the invalid data value is caused by the simultaneous input of full-open and full-close
signals, the answerback undefined alarm (PERR) will occur.
The status of answerback signal will be stored in the answerback raw signal (RAW), be-
sides the answerback input value (PV). Even if the answerback input function fails, the
answerback raw data (RAW) will follow the actual answerback signal.
● Conditions under Which Answerback Input Function Fails

The answerback input function fails under the following conditions:
• Simulation state (SIMM=1)
• Calibrating (PV.CAL=1)
• During answerback bypass (BPSW=1)
■ Actions of Answer-Back Inconsistency Alarm Check

The answerback inconsistency alarm check is a function that determines whether two
answerback input signals indicate full-open and full-close simultaneously in the switch
instrument blocks (SI-2, SIO-21, SIO-22, or SIO-22P).
If it is determined that two answerback input signals indicated full-open and full-close
simultaneously, an answerback inconsistency alarm (PERR) occurs.
If the two answer-back input signals stop indicating full-open and full-close simultaneously
while the alarm is being generated, the alarm is returned to normal state.

■ Remote/Local Input
The remote/local input function switches the block mode depending on the status of the on-
site operation push-button (remote/local input signal) input from the remote/local input
terminal (TSI). For remote/local signals, the contact input and common switch can be
specified. The state of remote/local input signal is stored in the tracking switch (TSW). The
block mode will be changed depending on the state of tracking switch (TSW).
Table Remote/Local Input Function of the Switch Instrument
On-site operation remote/ Input signal to TSI Tracking switch
Block mode
local switching input terminal (TSW)
Remote OFF 0 Cancel TRK
Local ON 1 TRK
D030407E.EPS
If there exists no connection for the remote/local input terminal (TSI), the block mode
external to the block function can set the tracking switch (TSW) directly.
The following is an example of description to the sequence table action signal column for
setting the switch instrument (Tag name=SU0100) tracking switch (TSW) to 1.
Tag name/Data item Data Action rule

SU0100.TSW 1 Y D030408E.EPS
The cprresponding logic chart is shown below:
Data connection
SU0100.TSW.1
OR
SIO-21
DI010 Q01 DI010.PV.ON
SU0100.TSW.1 OUT TSW
DI011 Q02 DI011.PV.ON
Switch instrument
(Tag No.=SU0100)
D030418E.EPS
Figure Example of a Logic Chart

■ Answerback Check
▼ Answerback Check, Answerback Abnormal Alarm
The answerback check function checks if final control elements such as a valve is working
as specified by the output from the switch instrument block.
If there exists answerback check specification, operations are checked by comparing the
answerback input value (PV) and manipulated output value (MV) regularly, except for a
certain period after a change in the output. If there is any inconsistency between the
answerback input value (PV) and the manipulated output value (MV), the answerback error
alarm (ANS+ or ANS-) will occur.
● Conditions for Answerback Error Alarm Occurrence

Answerback error alarm occurs under the following conditions:
• Open-side answerback error alarm (ANS+): MV=2 and PV2
• Close-side answerback error alarm (ANS-): MV=0 and PV0
Presence/absence of the answerback error alarm can be specified in the Function Block
Detail Builder.
• Answerback Abnormal Alarm
Select from “Close,” “OFF Direction,” “Both” or “No.”
The default is “Both.”
● Conditions for Recovery from Answerback Error Alarm

Recovery from the answerback error alarm is possible under the following conditions.
• Open-side answerback error alarm (ANS+)
When PV changes to PV=2, or MV changes to MV2
• Close-side answerback error alarm (ANS-)
When PV changes to PV=0, or MV changes to MV0

● Answerback Check Suppression Timer
It takes a certain length of time from changing the manipulated output value (MV) to com-
pleting the final control element operation. Consequently, when there is a change in ma-
nipulated output value, even if there is any inconsistency between the answerback input
value (PV) and the manipulated output value (MV), the alarm will not be activated for a
certain length of time (answerback check suppression time: MTM) after the change. If the
manipulated output value (MV) is changed, the block status will become answerback check
status (ANCK), starting the answerback check suppression timer.
If there is any inconsistency between the answerback input value (PV) and the manipulated
output value during the period between the time-up of answerback check suppression
timer and the next change in the manipulated output value (MV), the answerback error
alarm (ANS ) will be activated.
The answerback check status (ANCK) will be canceled when there is an inconsistency
between the answerback input value (PV) and the manipulated output value (MV), or when
the answerback check suppression timer expires.
Elapsed time of the answerback check suppression timer (PTM) indicates the time elapsed
after activating the answerback check suppression timer. When there is an inconsistency
between the answerback input value (PV) and the manipulated output value (MV) or when
the answerback check suppression timer expires, the answerback check suppression timer
will stop counting, retaining the count value.
The operation range of the answerback check suppression time (MTM) is from 0 to 10,000
seconds.
● Answerback Check Monitoring

The answerback check monitoring is specified in the Function Block Detail Builder.
• Answerback Check
Select from “Both sides”, “Open”, “Close”, or “No.”
The default is “Both sides.”
When either “Open” or “Close” is specified, answerback check will not be performed even if
there is any inconsistency on the side not specified. On the other hand, if monitoring both
sides is specified, the alarm will be activated when an inconsistency is detected on either
side. The alarm will be canceled when both sides satisfy their recovery conditions.

● Monitoring Both Sides
The answerback check time will be activated upon rising and falling of the output. If there
exists any inconsistency between the answerback input value (PV) and the manipulated
output value during the period between the time-up of answerback check suppression
timer and the next change in the manipulated output value (MV), the answerback error
alarm (ANS+) or close-side answerback error alarm (ANS-) will be activated.
MV=2
Manipulated output
MV=0
PV=2
Answerback input
PV=0
MTM
Answerback check
suppression timer
0
Alarm status NR ANS+ NR ANS- NR

AN AN
Block status NR CK NR CK NR ANCK NR ANCK NR
D030409E.EPS
Figure Operation Diagram of Both-Side Monitoring
● Monitoring Open-Side
The answerback check time will be activated upon rising (OFF➝ON) (MV=0➝2) of the
manipulated output. If there exists any inconsistency between the answerback input value
(PV) and the manipulated output value during the period between the time-up of
answerback check suppression timer and the next change of the manipulated output value
(MV) to 0, the open-side answerback error alarm (ANS+) will be activated.
MV=2
Manipulated output
MV=0
PV=2
Answerback input
PV=0
MTM
Answerback check
suppression timer
0
Alarm status NR ANS+ NR

Block status NR ANCK NR ANCK NR
D030410E.EPS
Figure Operation Diagram of Open-Side Monitoring

● Monitoring Close-Side
The answerback check time will be activated upon falling (ON➝OFF) (MV=2➝0) of the
manipulated output. If there exists any inconsistency between the answerback input value
(PV) and the manipulated output value during the period between the time-up of
answerback check suppression timer and the next change of the manipulated output value
(MV) to 2, the close-side answerback error alarm (ANS-) will be activated.
MV=2
Manipulated output
MV=0
PV=2
Answerback input
PV=0
MTM
Answerback check
suppression timer
0
Alarm status NR ANS- NR

Block status NR ANCK NR ANCK NR
D030411E.EPS
Figure Operation Diagram of Close-Side Monitoring
● Conditions under Which Answerback Check Function Fails

Answerback check function fails under the following conditions:
• Simulation state (SIMM): SIMM=1
• On-site manual operation mode (TRK): TSW=1
• During answerback bypass: BPSW=1
• MV=1
• Calibrating (PV.CAL=1)
• Input data error
• Initialization manual mode (IMAN)

■ Answerback Bypass
The answerback bypass function stops the answerback input function and answerback
check function, forcing the answerback input value (PV) and the manipulated output value
(MV) to match. The status of the answerback bypass switch will be input via the
answerback bypass input terminal (SWI). The contact input and internal status switch can
be specified to the input terminal. If there is no connection to the SWI input terminal, the
answerback bypass switch (BPSW) can be specified directly from outside the function
block.
The answerback bypass function is available only when the answerback bypass switch
(BPSW) is set to 1.
The table below shows the relationship between the answerback bypass input terminal and
the answerback bypass switch.
Table Relationship between Answerback Bypass Input Terminal and Answerback Bypass Switch
Item SWI input terminal ON SWI input terminal OFF
Answerback bypass switch (BPSW) 1 0
Answerback bypass function Execute Stop
D030412E.EPS

■ Output Signal Conversion
▼ Output Action Direction
The output signal conversion function outputs a contact signal to the output destination
specified by the output terminal depending on the manipulated output value (MV). The
manipulated output value (MV) from the switch instrument block varies by the block mode.
• When in CRT manual (MAN) mode
The output value is the values set on HIS.
• When in Sequence automatic 1 (AUT) or Sequence automatic 2 (CAS) mode
The output value is the value set by other blocks such as sequence control block
(CSV).
• When in Computer remote (ROUT) mode
The output value is the value remotely set from a supervisory computer (RMV).
• When in On-site manual (Local tracking) (TRK) mode
The output value is the value of the answerback input value (PV) if it is not in simula-
tion status and answerback tracking is specified.
The output contact signal varies with the direction of output action. Output action direction
can be set on the Function Block Detail Builder.
• Output action direction:
Select from [Direct], [Reverse], [Reversed connection Direct action] or [Reversed
connection Reversed action].
The default is [Direct].

Table Manipulated Output Value (MV) and Output Status
Output status (*1)
Number of output point Output action direction MV
n n+1
2 ON -
Direct action
1 0 OFF -
(Two-position type) 0 ON -
Reverse action
2 OFF -
2 ON OFF
Direct action 1 OFF OFF
0 OFF ON
2 OFF ON
Reverse action 1 ON ON
2 0 ON OFF
(Three-position type) 2 OFF ON
Reversed connection
1 OFF OFF
Direct action
0 ON OFF
2 ON OFF
Reversed connection
1 ON ON
Reversed action
0 OFF ON
2 2 ON OFF
Direct action
(Pulse type) 0 OFF ON
D030413E.EPS
*1: n in the table indicates the element at the output destination of the manipulated output value (MV) specified by the
output terminal (OUT).
n + 1 indicates the element after the n terminal.
Number of output points 1 ON

(two-position type) n
OFF
MV=0 MV=2 MV=0
ON
n
Number of output points 2 OFF
(three-position type)
ON
n+1
OFF
MV=1 MV=2 MV=1 MV=0 MV=1
ON
n
Number of output points 2 OFF 1 to 2 sec
(Pulse type)
ON
n+1
OFF 1 to 2 sec
MV=2 MV=0
D030414E.EPS
Figure Examples of Output Action (Action Direction = Direct Action)

■ Answerback Tracking
▼ Answerback Tracking
The answerback tracking function forces the manipulated output value (MV) to coincide
with the answerback input value (PV) (MV=PV) during the on-site manual operation mode
(TRK). The presence/absence of the answerback tracking function can be specified in the
• Answerback Tracking: Select from “Yes’’ or “No.’’
■ Calibration
The calibration function allows manual setting of the input signal. The calibration function is
activated when the data status of the answerback input value (PV) becomes calibration
(CAL). This state is called the calibration status. Change to the calibration status can be
executed from the human-machine interface station (operation and monitoring functions).
The following describes the switch instrument block actions during the calibration status.
• Answerback input value (PV) can be set manually.
• The manual fall back condition is satisfied and the block mode becomes manual
(MAN). The output function is performed.
• Bypass the alarm process for the answerback input value (PV).
• Bypass the answerback input and answerback check function.

■ Simulation
The simulation function simulates only the internal processing of the switch instrument
block in order to test the operation of devices using the switch instrument block. There
exists two main status in the switch instrument block: normal status and simulation status.
The status shifts to simulation when the switch instrument block simulation switch (SIMM)
is set to ON (=1).
● Setting the Simulation Status

Upon setting the switch instrument block simulation switch (SIMM) to ON (=1), the status
shifts to simulation (Block status: SM). The status can be set in the tuning widow of opera-
tion and monitoring functions.
● Canceling the Simulation Status

Upon setting the switch instrument block simulation switch (SIMM) to ON (=0), the simula-
tion status will be canceled (block status: NR). The status can be canceled in the tuning
widow of operation and monitoring functions.
● Actions under Simulation Status

The table below lists the actions of the switch instrument block functions during simulation
status.
• Block mode: Same as the normal state except IMAN
• Block status: SIM
• Alarm status: Always NR (Normal)
• Answerback input: No action except for including raw input data value.
• Answerback check:
Checking and alarming action is stopped. After the answerback check suppression
time is elapsed, MV value is set to PV value. When the answerback check is “absent,”
MV value is immediately set to PV value.
• Answerback bypass: No action except for including data from SWI.
• Output signal conversion: Output action is stopped.
• Answerback tracking: No action
• Alarm function: No action
• Calibration function: Same as the normal state.
The following describes the switch instrument block action in the first scan period after
canceling the simulation status.
• For a status-output type, the contact state of the output destination (element con-
nected to output terminal) is read back as the manipulated output value (MV).
• For a pulse-output type (SIO-12P, SIO-22P), if the answerback tracking function is
“Yes,” the manipulated output value (MV) is matched to the answerback input value
(PV).

■ Mode Change Interlock
This function prevents the automatic operation of the switch instrument block. When the
internal status switch of the interlock switch input terminal connection destination is turned
ON, the block mode change command to the automatic operation status (AUT, CAS,
ROUT) is disabled. At the same time, the manual fall back condition becomes satisfied, and
the block mode is changed to manual mode (MAN).
Any data containing a logical value such as the connection I/O and the internal switch can
be specified to the connection destination of the interlock switch input terminal regardless
of the element type.
The initialization manual function is an error processing functions. It suspends the control
action by changing the block mode to the initialization manual mode (IMAN). The initializa-
tion manual][ function will be activated when a temporary abnormal state occurred at the
output destination of manipulated output value can be restarted automatically upon recov-
ery from the abnormal state, for instance, during on-line maintenance.
• When the initialization manual function is activated, the control action is stopped when
the block mode is in the status that allows automatic controls as in the automatic
mode (AUT). The previous manipulated output value (MV) is retained. However, the
manual operation will not be available if the initialization manual mode is enabled,
even if the mode is changed from IMAN (AUT) to IMAN (MAN). Upon returning from
the initialization manual (IMAN) mode, the manipulated output value (MV) will track
the PV value of the output destination.
• The initialization manual mode (IMAN) is reset upon recovery of the occurrence
conditions, returning to the previous block mode. If the block mode change is ex-
ecuted during the initialization manual mode (IMAN), the block mode will be the mode
specified upon recovery of IMAN conditions.
SEE ALSO
For initialization manual conditions, refer to C6.1.5, “Block Mode Transition Condition.”
■ Manual Mode Fallback

The manual fallback function is one of the error processing functions. It forces the control to
stop by changing the block mode to the manual mode (MAN) regardless of the current
operation status. If the manual mode is activated (MAN) by the manual fallback function,
the block mode of the switch instrument block remains manual (MAN) even after the
recovery of an error.
The following describes manual fallback conditions for the switch instrument block.
• When the switch connected to INT terminal is turned ON (i.e., the interlock condition is
established for changing the block into interlock mode).
• When the data status of the answerback input value (PV) changes to calibration (CAL)
• When the data status of the manipulated output value becomes output failure (PTPF)
• When the FCS is undergoing a restart process, and the manipulated output is used for
a process control via a process control I/O module.

■ Data Items - Switch Instrument Block
SEE ALSO
For a list of valid block modes for the switch instrument blocks, see D3.1.2 “Block Mode of Sequence
Control Blocks.”
Table Data Items of the Switch Instrument Blocks (SI-1, SI-2)

Entry Permitted
or Not
AF Alarm detection ----- 0
AOFS Alarm inhibition ----- 0
RAW Raw input data 0 to 3 -----
D030415E.EPS


Table Data Items of the Switch Instrument Blocks (SO-1, SO-2)
Entry Permitted
or Not
MV Manipulated output value (*1) 0 to 2 0
RMV Remote manipulated output value 0 to 2 0
CSV Sequence setpoint value 0 to 2 0
TSW Tracking switch (*2) 0, 1 0
D030416E.EPS

*2: Entry is permitted when no data is specified to the input connection terminal

Table Data Items of the Switch Instrument Blocks (SIO-11, SIO-12, SIO-21, SIO-22, SIO-12P,
SIO-22P)
Entry Permitted
or Not
RAW Answerback raw signal 0 to 3 -----
MV Manipulated output value (*2) 0 to 2 0
RMV Remote manipulated output value 0 to 2 0
CSV Sequence setpoint value 0 to 2 0
Answerback check masking time
MTM 0 to 10000 4
(seconds)
PTM Elapsed time (seconds) 0 to 10000 0
BPSW Answerback bypass switch (*3) 0, 1 0
TSW Tracking switch (*3) 0, 1 0
D030417E.EPS

*3: Entry is permitted when no data is specified to the input connection terminal
■ Block Status of Switch Instrument Block

Table Block Status of Timer Block (TM)
Block Status
Level Description
Symbol Name
3 ANCK (*1) Answerback Check Inhibition Answerback check is inhibited
SIM Simulation Simulation state, output is invalidated
1
NR Normal Normal state
D030419E.EPS
*1: ANCK status is not available in SI-1, SI-2, SO-1 and SO-2.

<Toc> <Ind> <D3.5 Timer Block (TM)> D3-192
D3.5 Timer Block (TM)

The Timer Block (TM) is used to measure time in the unit of seconds or minutes.
■ Timer Block (TM)

▼ Connection
The Timer Block (TM) is a function block which measures time in the unit of seconds or
minutes. In addition to the basic elapsed time measuring function, the block includes the
preset timer function which notifies the time-up after a specified amount of time has
elapsed, the function which performs the periodic action, and the function which manipu-
lates the status based on the action signals specified in the output terminals.
The figure below is a function block diagram of the Timer Block (TM).
Counting
PV01 OUT
process
(CTUP) CTUP: Time-up
D030501E.EPS
Figure Function Block Diagram of the Timer Block (TM)
The table below lists the connection methods and connection destinations of the I/O termi-
nals of the Timer Block (TM).
Table Connection Methods and Connection Destinations of the I/O Terminals of the Timer Block
(TM)
I/O terminal Status Terminal

manipula- connecti-
tion on
Output
OUT
terminal
D030502E.EPS
Operations such as the timer start or stop can be performed from the sequence control
block, calculation block, and operation and monitoring functions. The block status which
indicates an operating status can also be referenced from other function blocks.
Status manipulation is the only connection method from the OUT terminal of the Timer
Block (TM). Thus, the Timer Block (TM) manipulates the status according to the action
signals specified in the OUT terminals. The logical value of the Timer Block (TM) becomes
true when the preset timer function is in time-up status (block status: CTUP).

The figure below shows an example of connection between the Timer Block (TM) and other
sequence control block.
TM Sequence connection CTS

OUT
(TM001) (COUNT01)
Specify COUNT01.ACT.ON
D030503E.EPS
Figure Connection Example of Timer Block (TM) and Other Sequence Control Block
Every time the Timer Block (TM) with the tag name TM001 expires, the Software Counter
Block (CTS) with the tag name COUNT01 is increased by one count.
■ Process Timing ¡ £
The process timing of Timer block is only based on periodical start period. The periodic
start period is based on high-speed scan period, medium-speed scan period (*1) and basic
scan period.
*1: ¡ £ Medium-speed scan period is supported in KFCS2, KFCS, LFCS2 and LFCS only.
■ Set Parameter
▼ Timer Property
The following describes the set parameters of the Timer Block (TM).
• Preset time setpoint value (PH): 0 to 100000 (second or minute)
• Pre-alarm setpoint value (DL): PL to PH
The PL is the low-limit value (fixed at 0) of the timer elapsed time (PV).
Use the Function Block Detail Builder to set the unit for the preset time setpoint.
• Timer Property: Select from “Second timer” or “Minute timer.”
Default is “Second timer.”

■ Action Commands for the Timer Block (TM)
Action commands can be given to the Timer Block (TM) from the operation and monitoring
functions, other sequence control blocks, or calculation block.
● Action Commands from the Operation and Monitoring Functions

Action commands can be given to the Timer Block (TM) by pressing the softkeys listed
below.
• STOP: Timer stop command
• START: Timer start command
• CONTINUE: Restart command
• PAUS: Pause command
● Action Commands from Sequence Control Blocks and Calculation Blocks

(CALCU, CALCU-C)
The table below describes the specified format of action signals and action description
when giving action commands to the Timer Block (TM) from sequence control blocks and
the calculation block.
Table Specified Format of Action Signals and Action Description
Action signal description column Y/N
Action description
Output signal Action specification True/False
Y/True Timer stop command

STOP
N/False Disable
Y/True Timer start command
START
N/False Timer stop command (*1)
Element symbol.OP
Y/True Restart command
RSTR
N/False Disable
Y/True Pause command
WAIT
N/False Restart command (*1)
D030504E.EPS
*1: An action for “N” is enabled only with the sequence table.
An action for “False” is enabled only with the logic chart.

■ Action of the Timer Block
When the Timer Block receives an action command from the operation and monitoring
functions or other function blocks, the block status changes according to the given com-
mand. There exist four types of basic actions for the Timer Block: Start, Stop, Pause, and
Restart.
The figure below shows the relationship between the timer elapsed time (PV) and the block
status, and each basic action.
PV Value
PH
DL
DV
PV
Time
Block RUN STOP RUN STOP

Status NR NR NR PALM CTUP NR
Action Start Stop Start Stop

Command Command Command Command Command
D030505E.EPS
Figure Basic Actions of the Timer Block (TM)
● Timer Start Action

When the Timer Block (TM) receives the timer start command, it starts the counting action
upon resetting (PV=0) the timer elapsed time (PV). The block status of the Timer Block
(TM) changes to “counting” (RUN-NR). The DV indicates the timer’s remaining time (DV=PH-
PV).
The figure below shows the changes in the timer elapsed time (PV) by the timer start
command.
Start command
PV value Scan period
PV=0 Time
Block status RUN

D030506E.EPS
Figure Timer Elapsed Time (PV) by Timer Start Command
The following describes an example of the timer start specified in the action signal column
of the sequence table.

TM0002.OP START Y D030507E.EPS

● Timer Stop Action
When the Timer Block (TM) receives the timer stop command, it stops the counting action
while holding the timer elapsed time (PV). The block status of the Timer Block (TM)
changes to stop status (STOP).
The figure below shows the changes in the timer elapsed time (PV) by the timer stop
command.
PV
Stop command
Scan period
PV=0 Time
Block
RUN STOP
Status
D030508E.EPS
Figure Timer Elapsed Time (PV) by Timer Stop Command
The following describes an example of specifying the timer stop in the action signal column
of the sequence table.

TM0002.OP STOP Y D030509E.EPS
● Timer Pause Action

When the Timer Block (TM) receives the pause command, the counting action is halted.
During the pause, the Timer Block (TM) holds the timer elapsed time (PV) or other data. As
for the block status, the pause status (PAUS) is newly added while the statuses such as
counting (RUN), pre-alarm status (PALM), time-up status (CTUP), or stop status (STOP)
are held. However, the status will be changed if the preset time setpoint value (PH), pre-
alarm setpoint value (DL), or the timer elapsed time (PV) is changed during the pause.
The following describes an example of specifying the timer pause in the action signal
column of the sequence table.

TM0002.OP WAIT Y D030510E.EPS

● Timer Restart Action
When the Timer Block (TM) in pause status receives the restart command, the counting
action is restarted. The Timer Block (TM) is released from the pause status (PAUS), and
returns to the previous block status that has been held.
The pause status (PAUS) is released when it receives the restart command. However, the
elapsed time (PV) is updated every scan period of the Timer Block (TM) itself.
PH
DL
DV
PV
RUN STOP
Block
NR PALM CTUP
Status
PAUS PAUS
Action Pause Restart Stop Pause Restart Start

Command Command Command Command Command Command Command
D030511E.EPS
Figure Pause/Restart Action of Timer
The following describes an example of specifying the timer restart in the action signal
column of the sequence table.

TM0002.OP RSTR Y D030512E.EPS

■ Preset Timer
▼ Periodic Action
The preset timer function notifies that the specified amount of time has elapsed. The
content of the notification includes the time-up status (TUP) based on the preset time
setpoint (PH) and the pre-alarm status (PALM) which gives prior notices before reaching
the preset time.
If one of the following conditions is satisfied for the timer’s remaining time (DV=PH-PV)
when the block status is counting (RUN), the pre-alarm status (PALM) or time-up status
becomes true.
• 0<DVDL: Pre-alarm status (PALM)
• DV=0: Time-up status (CTUP)
Use the Function Block Detail Builder to set the presence/absence of the periodic action.
• Periodic Action: Select from “Yes” or “No.”
The action of the preset timer function differs depending on the presence/absence of the
periodic action specification and the value of timer’s remaining time (DV).

● When Periodic Action Specification is “No”
Since the pre-alarm status (PALM) and the time-up status (CTUP) can not be true simulta-
neously, if DV0, the pre-alarm status (PALM) is canceled, shifting to the time-up status
(CTUP). When the time-up status becomes true, the elapsed time update is stopped. The
PV=PH and DV=0 status is therefore retained.
When the time-up status (CTUP) is true, the block status and the timer elapsed time (PV)
will be held even if the preset time setpoint (PH) is changed. A stop command or start
command must be given remotely in order to cancel the time-up status.
● When Periodic Action Specification is “Yes”

The time-up status (CTUP) becomes true if PVPH and DV0. However, when the timing
increment is in “seconds,” the timer elapsed time (PV) is set to 1 second (when the scan
period is 1 second) at the next scanning to restart the counting action. The block status will
be the status caused when PV=1. The figure below shows the changes in the timer
elapsed time (PV) when the periodic action specification is “Yes.”
PV
PH 8
4 PV=1
PV
2
0 Time
Scan period
Block RUN
status NR CTUP NR
D030513E.EPS
Figure Change in Timer Elapsed Time (PV) When Preset Time Setpoint (PH) is 8 Seconds
● When the Pre-Alarm Setpoint Value (DL) is Set to 0

The pre-alarm status (PALM) will not occur.
■ Status Manipulation from the Timer Block (TM)

When the action signal by sequence connection is specified to the OUT terminal of the time
block, the Timer Block (TM) executes the status manipulation corresponding to the existing
block status.
• CTUP and NOT PAUS:
Executes status manipulation for the logical value True.
• NR and NOT PAUS, or PALM and NOT PAUS:
Executes status manipulation for the logical value False.
• STOP or PAUS: Disable

■ Data Items - TM
The table below shows the data items of the Timer Block (TM):
Table Data Items of the Timer Block (TM)
Entry Permitted
or Not
BSTS Block status ----- STOP
PV Elapsed time PL to PH 0
PH Preset time setpoint value 0 to 100000 100000
DV Remaining time -PL to PH PH
DL Pre-alarm setpoint value PL to PH PL
PL PV scale low limit Fixed at 0. 0
D030514E.EPS

SEE ALSO
For a list of valid block modes of the timer block, see D3.1.2 “Block Mode of Sequence Control Blocks.”
■ Block Status of Timer Block (TM)

Table Block Status of Timer Block (TM)
Block Status
Level Description
Symbol Name
3 PAUS Pause Timer is paused
PALM Pre-Alarm Timer is running and 0<DV<=DL
2 CTUP Time Up Timer is running and DV = 0
NR Normal Timer is running and DV > DL
RUN Run Timer is running after a Start command
1
STOP Normal Timer is stopped after a Stop command
D030515E.EPS

<Toc> <Ind> <D3.6 Software Counter Block (CTS)> D3-201
D3.6 Software Counter Block (CTS)

The Software Counter Block (CTS) is used to calculate the number of events oc-
curred.
■ Software Counter Block (CTS)

▼ Connection
In addition to the basic calculating function, the CTS block includes the preset counter
function which notifies of the count-up upon calculating the specified numeric value, and
the function which manipulates the status based on the action signal specified to the output
terminal.
The figure below is a function block diagram for the Software Counter Clock (CTS).
Count
PV OUT
process
D030601E.EPS
Figure Function Block Diagram for the Software Counter Block (CTS)
The table below lists the connection methods and connection destinations of the I/O termi-
nal of the Software Counter Block (CTS).
Table Connection Methods and Connection Destinations of the I/O Terminals of the Software
Counter Block (CTS)

manipula- connecti-
tion on
Output
OUT
terminal
D030602E.EPS

The calculating operation of the software counter can be performed from other function
blocks such as the sequence control block or the calculation block.
The figure below shows a connection example of Software Counter Block (CTS). In this
example, the CALCU block sends a one-shot start command to CTS for counting.
Sequence connection
DI010 Q01 CTS001.ACT.ON
CALCU OUT
DI011 Q02
Process input General-purpose

calculation block CTS
OUT
(CTS001)
Software counter block
D030603E.EPS
Figure Example of Using General-Purpose Calculation Block (CALCU)
■ Process Timing
The process timing of CTS block is only based on one-shot start.
■ Set Parameter
The set parameters of the Software Counter Block (CTS) are:
• Preset setpoint (PH): 0 to 100000
• Pre-alarm setpoint (DL): PL to PH
PL: The scale low limit (fixed at 0) of the count value (PV).

■ Operation of the Software Counter Block (CTS)
The Software Counter Block (CTS) updates the count value (PV) upon receiving the
counter operation command. It also changes the block status.
The figure below shows the basic operation of the Software Counter Block (CTS).
7 Hold PV value
6
PH
(=6) DL=2 5
DV=4
4
3
2
PV=1 PV
Time
Block STOP RUN STOP

status NR PALM CTUP
Counter operation
command
Operation Stop
command command
D030604E.EPS
Figure Basic Operation of the Software Counter Block (CTS)
● Software Counter Update Action

Every time the Software Counter Block (CTS) receives the counter operation command,
the count value (PV) is added by 1. If the block status is in stop status (STOP) when the
counter operation command is received, the block status of the Software Counter Block
(CTS) changes to “counting” (RUN-NR). The count value (PV) is also reset (PV=1).
The following describes an example of specifying the operation of the software counter in
the action signal column of the sequence table.

CTS001.ACT ON Y D030605E.EPS
● Software Counter Stop Action

When the Software Counter Block (CTS) receives the counter stop command, it stops its
calculating action while holding the count value (PV). The block status of the Software
Counter Block (CTS) changes to the stop status (STOP).
The following describes an example of specifying the software counter stop in the action
signal column of the sequence table.

CTS001.ACT OFF Y D030606E.EPS

■ Preset Counter Function
The preset counter function notifies that the count value (PV) has reached the specified
count number. The content of notification includes the count-up status (CTUP) based on
the preset setpoint (PH), and the pre-alarm status (PALM) which gives prior notices before
reaching the preset setpoint (PH).
When the remaining count value (DV=PH-PV) satisfies one of the following conditions
while the block status is in counting (RUN), the pre-alarm status (PALM) or the count-up
status (CTUP) becomes true.
• When 0<DVDL: Pre-alarm status (PALM)
• When DV0: Count-up status (CTUP)
Since the pre-alarm status (PALM) and the count-up status (CTUP) can not become true
simultaneously, the pre-alarm status (PALM) is canceled when DV=0, shifting to the count-
up status (CTUP). Although the count value (PV) continues to be updated even after the
status shifts to the count-up, the count value (PV) is reset when it reaches 100000. How-
ever, the block status at count-up is held as count-up status (CTUP).
In order to cancel the count-up status (CTUP), the count value (PV) must be set remotely
or a stop command must be given. Also, when the pre-alarm setpoint (DL) is set to 0, the
pre-alarm status (PALM) will not occur.
■ Status Manipulation from the Software Counter Block (CTS)

When the action signal by sequence connection is specified to the output terminal of the
Software Counter Block (CTS), the status manipulation is performed based on the block
status.
• CTUP: Executes status manipulation for the logical value True.
• NR or PALM: Executes status manipulation for the logical value False.
• STOP: Disable

■ Data Items - CTS
Table Data Items of the Software Counter Block (CTS)
Entry Permitted
or Not
BSTS Block status ----- STOP
PV Count value 0 to 100000 0
PH Preset setpoint 0 to 100000 100000
DV Remaining count value -PL to PH PH
DL Pre-alarm setpoint PL to PH PL
D030607E.EPS

SEE ALSO
For a list of valid block modes of the CTS block, see D3.1.2 “Block Mode of Sequence Control Blocks.”
■ Block Status of Software Counter Block (CTS)

Table Block Status of Software Counter Block (CTS)
Block Status
Level Description
Symbol Name
PALM Normal Counter is running and DV > DL
2 CTUP Pre-Alarm Counter is running and 0<DV<=DL
NR Count Up Counter is running and DV <= 0
RUN Run Counter is running after a Start command
1
STOP Normal Counter is stopped after a Stop command
D030608E.EPS

<Toc> <Ind> <D3.7 Pulse Train Input Counter Block (CTP)> D3-206
D3.7 Pulse Train Input Counter Block (CTP)

The Pulse Train Input Counter Block (CTP) is used to count the number of pro-
cesses, which are expressed in the form of pulse signals.
■ Pulse Train Input Counter Block (CTP)

▼ Connection
The Pulse Train Input Counter Block (CTP) is a function block that counts the number of
processes, which are expressed in the form of pulse signals. In addition to the basic count-
ing function, it also includes the preset counter function, which indicates the count-up state
when the specified number has been counted, and a function that manipulates the status
based on the action signal specified at the output terminal.
The following is a function block diagram of the Pulse Train Input Counter Block (CTP).
Count
IN PV OUT
Process
D030701E.EPS
Figure Function Block Diagram of the Pulse Train Input Counter Block (CTP)
SEE ALSO
• For the types of alarm processing possible for the CTP block, see D3.1.1 “Alarm Processing of Sequence
Control Blocks.”
• For more information about alarm processing, see C5 “Alarm Processing-FCS.”
The table below lists connection methods and destinations for the Pulse Train Input
Counter Block (CTP).
Table Connection Methods and Destinations for the Pulse Train Input Counter Block (CTP) I/O
Terminals

manipula- connecti-
tion on
Input
IN
terminal
Output
OUT
terminal
D030702E.EPS
Operations such as start or stop of the pulse counter can be performed from other function
blocks such as the sequence control block or the calculation block, as well as from the
operation and monitoring functions. The block status that indicates the operating status can
be referenced from other function blocks.

The figure below shows a signal connection example from the pulse input module.
CTP
(CTP001)
IN
%Znnusmm
D030703E.EPS
Figure Example of the Signal Connection from the Pulse Input Module
■ Process Timing ¡ £
The process timing of Timer block is only based on periodical start period. The periodic
start period is based on high-speed scan period, medium-speed scan period (*1) and basic
scan period.
*1: ¡ £ Medium-speed scan period is supported in KFCS2, KFCS, LFCS2 and LFCS only.
■ Set Parameters - CTP

The following are the set parameters of the Pulse Train Input Counter Block (CTS).
• Preset setpoint (PH): 0 to 100000
• Pre-alarm setpoint (DL): PL to PH
PL: The scale low limit (PV) of the count value (fixed to 0).

■ Action Command of the Pulse Train Input Counter Block (CTP) - CTP
The action command can be issued to the Pulse Train Input Counter Block (CTP) from the
operation and monitoring functions, other sequence control block or calculation block.
● Action Command from the Operation and Monitoring Functions

Pressing a button listed below can issue an action command to the Pulse Train Input
Counter Block (CTP).
• STOP: Counter stop command
• START: Counter start command
• CONTINUE: Restart command
• PAUS: Pause command
● Action Command from Other Sequence Control Block or Calculation

Block
The table below lists the description format and action description of the action signals
when issuing the action command to the Pulse Train Input Counter Block (CTP) from other
sequence control block or calculation block.
Table Description Format and Action Description of Action Signals
Action signal description column Y/N Action description
Action/Output signal Action specification True/False
Y/True Pulse input counter stop command

STOP
N/False Invalid
Y/True Pulse input counter start command
START
N/False Pulse input counter stop command (*1)
Element symbol.OP
Y/True Restart command
RSTR
N/False Invalid
Y/True Pause command
WAIT
N/False Restart command (*1)
D030704E.EPS
*1: Actions for “N” are valid only for the sequence table.
Actions for “False” are valid only for the logic chart.

■ Action of the Pulse Train Input Counter Block (CTP)
The Pulse Train Input Counter Block (CTP) is provided with an action command from the
operation and monitoring functions or other function block, and holds block status corre-
sponding to the command. The basic actions of the Pulse Train Input Counter Block (CTP)
include four actions: the update action, stop action, pause action and restart action.
The following describes the relationship between the count value (PV) and the block status
along with the basic action.
● Pulse Train Counter Update Action

When the Pulse Train Input Counter Block (CTP) receives the counter start command, it
begins counting after resetting the count value (PV=0). When the counter start command is
received, the block status becomes the during counting status (RUN-NR). While counting,
it reads the pulse input from the input terminal during each scan period, and updates the
count value (PV) by adding the pulse count that is increased from the previous period.
When the data status of input signals is “invalid (BAD)” or “I/O not ready (NRDY),” the
status is recognized as faulty and the count value (PV) is not updated.
The following shows an example of specifying the start of the Pulse Train Input Counter
Block (CTP) in the action signal column of the sequence table.

CTP001.OP START Y D030705E.EPS

● Pulse Train Counter Stop Action
When the Pulse Train Input Counter Block (CTP) receives the stop command for the
counter, it stops the counting operation while holding the count value (PV). The block status
becomes the stop status (STOP).
The following shows an example of specifying the stop of the Pulse Train Input Counter

CTP001.OP STOP Y D030706E.EPS
PH
DL
DV
PV
5
2
4
4
Time
1 scan
Block STOP RUN STOP

status NR PALM NR CTUP
PALM
Action Start Start command Stop
commands command command
4 4 2 5
Time
Scan Scan Scan Scan Scan
D030707E.EPS
Figure Basic Actions of the Pulse Train Counter
● Pulse Train Counter Pause Action

When the Pulse Train Input Counter Block (CTP) receives the pause command, it pauses
the counting operation. At this time, the data when the pause was issued is held as the
count value (PV). The pause status (PAUS) is added in addition to the currently held block
status, which is one of the counting (RUN), pre-alarm (PALM), normal (NR), time-up
(CTUP) and stop (STOP) statuses.
The following shows an example of specifying the pause of the Pulse Train Input Counter

CTP001.OP WAIT Y D030708E.EPS

● Pulse Train Counter Restart Action
When the pausing Pulse Train Input Counter Block (CTP) receives the restart command, it
resumes the counter operation. The Pulse Train Input Counter Block (CTP) is released
from the pause status (PAUS) and returns to the block status that was originally held. If the
original block status was the counting status (RUN), count updating resumes from the
counter value that was held then.
The pause status (PAUS) is released at the timing when it accepts a restart command.
However, the count value (PV) update timing differs, depending on the scan period of the
Pulse Train Input Counter Block (CTP) itself.
The following shows an example of specifying the restart of the Pulse Train Input Counter

CTP001.OP RSTR Y D030709E.EPS
PH
DL
DV
PV
Time
RUN STOP
Block
NR PALM CTUP
status
PAUS PAUS
Action Pause Restart Stop Pause Restart Start

commands command command command command command command
D030710E.EPS
Figure Pause and Restart Actions

■ Preset Counter Function of Pulse Counter
The preset counter function indicates that the count value (PV) has reached the specified
count. The content of the notification could be the count-up status (CTUP) based on the
preset setpoint (PH) or the pre-alarm status (PALM), which indicates prior to reaching the
preset setpoint (PH).
When the remaining count value (DV=PH-PV) satisfies one of the following conditions
while the block status is the counting status (RUN), the pre-alarm status (PALM) or the
count-up status (CTUP) becomes true.
• 0<DVDL: Pre-alarm status (PALM)
• DV0: Count-up status (CTUP)
Since the pre-alarm status (PALM) and count-up status (CTUP) can not become true
simultaneously, the pre-alarm status (PALM) is canceled when DV=0, and the status shifts
to the count-up (CTUP) status. Although updating of the count value (PV) continue even
after the status shifts to count-up status, the count value (PV) is reset when it reaches
100,000 and counting continues. However, the block status is held at the count-up status
(CTUP) when it is counted.
In order to cancel the count-up status, it is necessary to set the count value (PV) externally
or to issue a stop command. Also, when the pre-alarm setpoint (DL) is set to 0, the pre-
alarm status (PALM) will not occur.
■ Status Manipulation from the Pulse Train Input Counter Block (CTP)
When the action signal is specified via sequence connection to the OUT terminal of the
Pulse Train Input Counter Block (CTP), the status is manipulated based on the block
status.
• CTUP and NOT PAUS:
Execute status manipulation for true logical value.
• NR and NOT PAUS, or PALM and NOT PAUS:
Execute status manipulation for false logical value.
• STOP or PAUS: Invalid
If an error occurs during status manipulation, the alarm status of the Pulse Train Input
Counter Block (CTP) becomes the connection failure status (CNF). This is recovered when
either the cause of alarm is removed during the status manipulation, or the pulse counter is
stopped or paused.

■ Data Items - CTP
Table Data Items of the Pulse Counter Block (CTP)
Entry Permitted
or Not
PV Count value 0 to 100000 0
PH Preset setpoint 0 to 100000 100000
DV Remaining count value -PL to PH PH
DL Pre-alarm setpoint PL to PH PL
D030711E.EPS

SEE ALSO
For a list of valid block modes of the CTP block, see D3.1.2 “Block Mode of Sequence Control Blocks.”
■ Block Status of Pulse train Input Counter Block (CTP)

Table Block Status of Pulse train Input Counter Block (CTP)
Block Status
Level Description
Symbol Name
3 PAUS Pause Counter is paused
CTUP Count Up Counter is running and DV <= 0
2
PALM Pre-Alarm Counter is running and 0<DV<=DL
RUN Run Counter is running after a Start command
1
STOP Normal Counter is stopped after a Stop command
D030712E.EPS

<Toc> <Ind> <D3.8 Code Input Block (CI)> D3-214
D3.8 Code Input Block (CI)

The CI block is used to read the contact input or internal switch as a binary code or
binary coded decimal and display the integer value indicated by the code as the
input code value.
■ Code Input Block (CI)

▼ Connection
The CI block is a function block that convert the digital input signal into code value (PV).
The conversion of digital input signals to input code values (PV) includes “No-conversion”
in which the signal pattern is interpreted as is as a binary number, and “BCD conversion” in
which it is interpreted as a BCD (binary coded decimal) code.
The following is a function block diagram of the Code Input Block (CI).
IN Bit Encoding PV
Inversion
D030801E.EPS
Figure Function Block Diagram of Code Input Block (CI)
The table below lists connection methods and destinations for the Code Input Block (CI).
Table Connection Methods and Destinations for Code Input Block (CI) I/O terminals

manipula- connecti-
tion on
Input
IN
terminal
D030802E.EPS
The CI block input processing and code conversion are performed as one-shot execution
from other function blocks such as a sequence control block.
The following describes an example of specifying the code input block one-shot execution
in the action signal column of the sequence table.

CI001.ACT ON Y D030803E.EPS

■ Process Timing
The process timing of CI block is only based on one-shot start.
■ Number of Input Signals

▼ Number of Bits Input
The Code Input Block (CI) inputs the contact signals that continue for the number of input
signal points from the element of the input destination specified in the IN terminal. The first
element corresponds to the most significant digit. If there is a data error even at one point in
the input signal, the input code value (PV) is handled as faulty data. When an input error
occurs, the previous value is held for the input code value (PV).
The input signal points are set by the Function Block Detail Builder.
• Number of Bits Input: 0 to 18 points
Up to 16 points in the case of “no conversion”
Default is 0.
■ Bit Inversion
▼ Bit Inversion
The bit inversion of the Code Input Block (CI) inverses the ON/OFF status of the input
digital signals. If the bit inversion is specified as ‘’Non-reversed,’’ the ON/OFF status will not
be inversed.
The bit inversion is set by the Function Block Detail Builder.
• Bit Inversion: Select from “No” or “Yes.”
■ Encoding
▼ Code Conversion
The encoding of the Code Input Block (CI) interprets the input digital signal as a code and
converts it into an integer value. The converted integer value becomes the input code value
(PV). The input code value (PV) is held until the Code Input Block (CI) starts for the next
time via the code input read command.
There exist two methods for encoding the digital signals:
• “No conversion,” which interprets the contact signal patterns as binary numbers.
• “BCD conversion,” which interprets the contact digital patterns as binary coded deci-
mal (BCD) codes.

The figure below shows examples of encoding when “no conversion” and “BCD conver-
sion” are specified.
No conversion BCD conversion

%Z011101 %Z011101
%Z011102 %Z011102
%Z011103 %Z011103
%Z011104 %Z011104
%Z011105 %Z011105
%Z011106 %Z011106
O O O O O O O O O O O O
F N F N F N F N F N F N
F F F F F F
101 100
Code input data Code input data
0 1 0 1 0 1 0 1 0 1 0 1 (15)
(binary input) (BCD input)
Encoding Encoding
0 1 0 1 0 1 0 0 1 1 1 1
(no conversion) (BCD to binary)
(no inversion) (no inversion)
Conversion at Conversion at
operation and Convert binary operation and Convert binary
monitoring functions to decimal monitoring functions to decimal
(for display) (for display)
Display (PV) 21 Display (PV) 15
D030804E.EPS
Figure Encoding When “No Conversion” and “BCD Conversion” are Specified
When 6 points from %Z011101 are specified for CI001, %Z011101 to%Z011106 become
the code input data and %Z011101 is always the most significant bit.
Assuming that current ON/OFF statuses of %Z011101 to %Z011106 are as shown in the
figure above, PV (CI001) =15 when the BCD conversion is specified, and PV (CI001) =21
when the non conversion is specified. In the above examples, when the BCD conversion is
specified, the upper 2 bits (%Z011101, 011102) represent the ones places of 10, and the
lower 4 bits (%Z011103 to 6) does the zeros places of 10.

For the BCD conversion, when the input signal patterns are meaningless as BCD code, the
block status is set to the input code error (ERR). This “meaningless pattern as BCD code”
refers to the input signal pattern indicating a value other than 0 to 9.
The figure below shows examples of when the block status is in the normal status (NR),
and when it is meaningless.
Upper digit Lower digit Upper digit Lower digit
0101 0010 0101 1011

BCD handles
values
5 2 5 B 0 to 9 only
52 Meaningless
Block status = NR Block status = ERR

D030805E.EPS
Figure BCD Code Examples
The encoding function is set by the Function Block Detail Builder.

• Code conversion: Select from “No” and “BCD.”
“No” is binary input, “BCD” is binary coded decimal input.

■ Input Data Status Testing Function
The input data status testing function investigates the conditions listed below for the en-
coded input code value (PV), and determines the block status.
The following lists the conditions for the input code value (PV) for determining the block
status.
• 0PV<PH-DL: Normal status (NR)
• PH-DLPV<PH: Low limit alarm status (LO)
• PVPH: High limit alarm status (HI)
PH: Input high limit setpoint
DL: Low limit alarm status setting range
The figure below shows the graphed conditions of the input code value (PV).
PV
PH
DL
NR LO HI
D030806E.EPS
Figure Relationship Between Input Code Value (PV) and Block Status
The input data status testing is not performed if an input code error has occurred.

■ Data Items - CI
Table Data Items of Code Input Block (CI)
Entry Permitted
or Not
PV Input code value 0 to 65535 PL
RAW Raw input data ----- -----
PH High - limit alarm setpoint 0 to 65535 65535
DV PH – PV -PL to PH PH
DL LO width 0 to 65535 0
D030807E.EPS

SEE ALSO
For a list of valid block modes of the CI block, see D3.1.2 “Block Mode of Sequence Control Blocks.”
■ Block Status of Code Input Block (CI)

Table Block Status of Code Input Block (CI)
Block Status
Level Description
Symbol Name
3 ERR Code Error Invalid BCD code pattern
NR Normal 0 < PV < PH-DL
2 LO Low PH-DL =< PV < PH
HI High PV >= PH
D030808E.EPS

<Toc> <Ind> <D3.9 Code Output Block (CO)> D3-220
D3.9 Code Output Block (CO)

The Code Output Block (CO) is used to convert the integer value which is set as the
setting code value (PV) from the operation and monitoring functions or other func-
tion block into the code pattern for output to the contact output or internal switch,
etc.
■ Code Output Block (CO)

▼ Connection
The Code Output Block (CO) is a function block that converts the integer value which is set
as the setting code value (PV). Converting of the setting code value (PV) has “no conver-
sion,” which outputs the integer value in binary, and “BCD conversion,” which outputs after
converting into binary coded decimal (BCD) options.
The following is a function block diagram of the Code Output Block (CO).
Bit
PV Encoding OUT
Inversion
D030901E.EPS
Figure Function Block Diagram of the Code Output Block (CO)
The table below lists connection methods and destinations for the Code Output Block (CO)
I/O terminals.
Table Connection Methods and Destinations for the Code Output Block (CO) I/O Terminals

manipula- connecti-
tion on
Output
OUT
terminal
D030902E.EPS
: Connection available only when connecting to switch blocks (SW-33, SW-91)
The conversion of a CO block setting code value (PV) to a code are performed as one-shot
execution from other function blocks such as the sequence control block.
The following describes an example of specifying the code output block one-shot execution
in the action signal column of the sequence table.

CO001.ACT ON Y D030903E.EPS

■ Number of Output Signal
▼ Number of Bits Output
The output signal points of the Code Output Block (CO) are set by the Function Block
Detail Builder.
• Number of Bits Output: 0 to 18 points
Up to 16 points in the case of “no conversion.”
Default is 0.
■ Encoding
▼ Code Conversion
The encoding function of the Code Output Block (CO) converts the integer value set as the
setting code value (PV) into bit patterns.
There exist two methods for converting an integer value into bit patterns:
• “No conversion,” converts to binary patterns.
• “BCD conversion,” converts the value into binary coded decimal (BCD) patterns.
The figure below shows examples of encoding when “no conversion” and “BCD conver-
sion” are specified.
No conversion BCD conversion

%SW0100 %SW0100
%SW0101 %SW0101
%SW0102 %SW0102
%SW0103 %SW0103
%SW0104 %SW0104
%SW0105 %SW0105
O O O O O O O O O O O O
F N F N F N N F F F F N
F F F F F F F
D030904E.EPS
Figure Encoding When “Non Conversion” and “BCD Conversion” are Specified
When six points from %SW0100 are specified for CI001, %SW0100 to %SW0105 will be
subject to the code output. If the bit inversion is specified as “Non-reversed” and code
output is performed with the settings of CO0001 and PV=21, the ON/OFF statuses of the
%SW0100 to %SW0105 are as shown in the figure above.
The encoding function is set by the Function Block Detail Builder.
• Code Conversion:
Select from “No” and “BCD.”
“No” yields binary output, “BCD” yields binary coded decimal output.

■ Bit Inversion
▼ Bit Inversion
The bit inversion of the Code Output Block (CO) inverses the ON/OFF status of the signals
to be output. If the bit inversion is specified as “No,” the ON/OFF status will not be inversed.
The bit inversion is set by the Function Block Detail Builder.
• Bit Inversion: Select from “No” or “Yes.”
■ Set Data Status Testing Function

The set data status testing function investigates the conditions listed below for the set code
value (PV), and determines the block status.
The following lists the conditions for the set code value (PV) for determining the block
status.
• 0PV<PH-DL: Normal status (NR)
• PH-DLPV<PH: Low limit alarm status (LO)
• PVPH: High limit alarm status (HI)
PH: Alarm high limit value
DL: Low limit alarm status (LO) setting range
The figure below shows the graphed conditions of the set code value (PV).
PV
PH
DL
NR LO HI
D030905E.EPS
Figure Relationship between Set Code Value (PV) and Block Status

■ Signal Output Function
The signal output function outputs bit patterns to the continuous elements of the output
destination for the number of output signal points, starting with the element specified in the
OUT terminal.
When the output destination is the contact output, if there exists even one output with a
hardware failure, the entire signal will not be output. When the hardware failure occurs, the
data status of the set code value (PV) becomes the output fail status (PTPF), and the
previous set code value is held as the set code value (PV).
When a value that is too large to express with the specified output signal points is set for
the set code value (PV), only the code patterns of the available output signal points are
output. This is not handled specifically as an error.
The figures below show an example of insufficient output signal points.
Input data PV=175
Non conversion, no inversion
Reverse code conversion

1 0 1 0 1 1 1 1
(Decimal to binary)
Significant digits
Four output signal points
Output 1 1 1 1
D030906E.EPS
Figure Encoding Example for Four Output Signal Points

■ Data Items - CO
Table Data Items of Code Output Block (CO)
Entry Permitted
or Not
MODE Block mode ----- AUT
PV Setting code value 0 to 65535 0
PH High - limit alarm setpoint 0 to 65535 65535
DV PH – PV -PL to PH PH
DL LO width 0 to 65535 0
D030907E.EPS

SEE ALSO
For a list of valid block modes of the CO block, see D3.1.2 “Block Mode of Sequence Control Blocks.”
■ Block Status of Code Output Block (CO)

Table Block Status of Code Output Block (CO)
Block Status
Level Description
Symbol Name
NR Normal 0 =< PV < PH-DL
2 LO Low PH-DL =< PV < PH
HI High PV >= PH
D030908E.EPS

<Toc> <Ind> <D3.10 Relational Expression Block (RL)> D3-225
D3.10 Relational Expression Block (RL)

The Relational Expression Block (RL) is used to judge the numerical relationship or the
logical product of two data.
■ Relational Expression Block (RL)

▼ Relational Expression
The Relational Expression Block (RL) is executed during the condition testing process for a
sequence control block such as a sequence table, or during the condition testing process
for the calculation block. It tests for the numerical relationship or the logical product of two
data, according to the relational expression within the Relational Expression Block (RL),
and returns the result of whether or not it matches the conditions to the calling function
block.
The following is a function block diagram of the Relational Expression Block (RL).
Q01 RV01
(X01)
Q02 RV02
Q31 RV31
(X16)
Q32 RV32
D031001E.EPS
Figure Function Block Diagram of Relational Expression Block (RL)
The table below lists connection methods and destinations for the Relational Expression
Block (RL) I/O terminals.
Table Connection Methods and Destinations for Relational Expression Block (RL) I/O Terminals

manipula- connecti-
tion on
Data input
Q01 to Q32
terminal
D031002E.EPS

The test objects are either two process data, or one process data and one constant data.
One Relational Expression Block (RL) can handle 16 sets of relational expressions, thus it
can handle 32 individual data.
The figure below shows a connection example to another function block.
Process I/O
%Znnusmm Q01 RV01=%Znnusmm
(X01)
Q02 RV02=CALCU1.CPV1
Q01 Calculation J01

block
CALCU1 OUT
Q31 RV31
(X16)
%SW0100 Q32 RV32
Software I/O
Relational Expression Block
D031003E.EPS
Figure Connection with Another Function Block
■ Process Timing
The process timing of RL block is only based on one-shot start.

■ Relational Expression Data
With a single set of relational expressions, either two process data or one process data
and one constant data can be judged. Other referable data such as process I/O, software
I/O and function block data can be specified as the process data. Always specify the
process data on the left-hand side of the relational expression. For the right-hand side of
the relational expression, process data or constant data can be specified. Special data
such as character strings, connection data and pulse input cannot be used for the calcula-
tion.
Constants for the constant data are set by the Function Block Detail Builder.
The following shows the relationship expression between process data and process data.
FIC101.PV: FIC102.PV
FIC101. PV (RV01)
X01
FIC102. PV (RV02)
D031004E.EPS
Figure Relationship Expression between Process Data and Process Data
The following shows the relationship expression between process data and constant data.
FIC101.PV: 123.4
FIC101. PV (RV03)
X02
123.4 (RV04)
D031005E.EPS
Figure Relationship Expression of Process Data and Constant Data
The following shows an entry example to the condition signal column in the sequence
table when testing for RV01 > RV02 shown in the first example above.
%BL0100.X01.GT -------- Y
The function block indicated by %BL0100 represents the Relational Expression Block
(RL).
Use the Function Block Detail Builder to pre-define the data expressed by relational
expression data RV01 and RV02 as X (the first data) and Y (the second data).
• X, Y: Character string of up to 34 standard width characters.
Describe the process data or a real number.
Default is blank.

■ Relational Expression Type
When the Relational Expression Block (RL) is referenced from other function blocks for
condition testing, relational operation for the relational expression specified in X01 through
X16 is performed as a one-shot operation. There exist two types of relational expressions:
the numerical comparison operation between two data, and the logical product operation of
two data. For the relational expression type, delimit the two data with an operator and
preset by each relational expression using the Function Block Detail Builder.
• Operator: Select from “CMP” and “AND”
The table below lists the operators and description of each operation.
• CMP
Numerical comparison:
Performs the numerical comparison of two data. It tests if the relationship matches the
relational expression and returns a logical value.
• AND
Logical product:
Computes logical products of two data by bit. It returns true if at least one bit satisfies
the relational expression.
The following describes an example of performing the logical product operation against two
data.
%CI0100.PV & %CI0101.PV.
CI0100 and CI0101 represent the Code Input Block (CI). The above example computes the
logical product of each corresponding bit of the two input code values (PV). If both corre-
sponding bits include 1, it returns true (1) to the calling function block.
The two data types are converted into floating point, if the relation operation type is numeri-
cal comparison, or are converted to the unsigned integer type if the relational operation
type is the logical product.
In the following cases, relational operation is performed using the data of previous rela-
tional expression:
• When failed to obtain data from the connection destination
For example, the connection destination is under on-line maintenance.
• When the input data has the data value error status (BAD)
For example, a negative value is input for the logical product relational operation.
Up to 24 alphanumeric character can be added to the 16 sets of relational expressions as

comments so that the operation is being performed by each relational expression can be
indicated in text.

■ Range of Operation
The Relational Expression Block (RL) performs the operation only for the specified rela-
tional expression during each one-shot execution from other function blocks. When it is not
called as one-shot, the previous values remain for the relational expressions that have not
been performed.
■ Data Items - RL
Table Data Items of Relational Expression Block (RL)
Entry Permitted
or Not
RV01 to RV32 Relational expression data ----- 0
AV01 to AV32 AND data ----- 0
D031006E.EPS


<Toc> <Ind> <D3.11 Resource Scheduler Block (RS)> D3-230
D3.11 Resource Scheduler Block (RS)

The Resource Scheduler Block (RS) is used to manage the utilization of limited plant
resources.
■ Resource Scheduler Block (RS)

When the resource usage requests exceed the number of usage limit for the Resource
Scheduler Block (RS), the usage requests are added to the queue and placed in usage
request waiting status. After that, it issues permission in sequence as the resource be-
comes available.
Although there are no I/O terminals for the Resource Scheduler Block (RS), data inside the
block may be referenced and set.
The following is a function block diagram of the Resource Scheduler Block (RS).
Permission (PM) Maximum

permissible
......... number
1 32
PMH
Usage request (RQ)
......... (0 to 32)
1 32
D031101E.EPS
Figure Function Block Diagram of Resource Scheduler Block (RS)
Issuing the usage request command and the usage request cancel command, referencing
and setting the maximum permissible number and referencing the permission status of the
Resource Scheduler Block (RS) may be performed from the sequence control blocks or
calculation block.

The figure below shows an example of the lorry shipping system with a built-in pump count
control.
Spot
P (Lorry shipping alarm)
Maximum
Pump count permissible number Request
Resource
control setting scheduler Spot control
Permission
D031102E.EPS
Figure Example of Lorry Shipping
In the above system example, the number of spots that can be used simultaneously for
product shipment is restricted by the total flow rate of the products that flow into the spots.
In such cases, the Resource Scheduler Block (RS) is used to control the usage status of
each spot for shipping control. By receiving a shipping request (usage request) from each
spot, the Resource Scheduler Block (RS) issues a sequential shipping permission (usage
permission) to the first entry in the FIFO (First In First Out) queue.
In the above system example, the product total flow rate that restricts the number of spots
(the maximum permissible number) that can be used simultaneously is determined by the
number of operating pumps. Therefore, the maximum permissible number (PMH) for the
Resource Scheduler Block (RS) is set via the function block that controls the pump count.
■ Process Timing
The process timing of RS block is only based on one-shot start.

■ Usage Request Control Function
The usage request control function controls the request queue, usage request status
(RQ01 to RQ32) and permission (PM01 to PM32) upon receiving the usage request com-
mand or the usage request cancel command. In order to use the Resource Scheduler
Block (RS) from the sequence control block or the general-purpose calculation block, it is
necessary to predefine the identification number for each of the requesters for the re-
sources. The requesters are identified by this number when referencing the usage request
command, usage request cancel command, usage request (RQnn) and permission
(PMnn). The numeric portion (noted as nn in this document) of the data item name for the
usage request (RQnn) and permission (PMnn) is used as the identification number.
● Usage Request Command

The usage requester sends a usage request command to the Resource Scheduler Block
(RS). Only a single request at a time can be accepted from the same requester. The re-
quester which has already been given permission or is waiting in the usage request queue
cannot send additional requests. Two or more simultaneous requests are ignored.
When the entire resource group usage request command is received, the Resource
Scheduler Block (RS) processes the usage requests in the ascending order of request
numbers. Since the permission is restricted by the maximum permissible number (PMH),
the remaining usage requests are placed in the queue for permission.
The following describes operations when the number of usage requests is equal to or
greater than the maximum permissible number (PMH), or when less than the maximum
permissible number (PMH).
• When usage request number Maximum permissible number
It gives permission for the request by setting 1 to the corresponding usage request
(RQnn) and permission (PMnn).
• When usage request number > Maximum permissible number
Although the corresponding usage request (RQnn) is set to 1, it cannot give permis-
sion because there are not enough resources for requests. It adds the identification
number of the requester to the queue, while the corresponding permission (PMnn) is
kept at 0.

● Usage Request Cancel Command
It is necessary for the requester to issue the usage request cancel command when it has
used all the resources, or when canceling the usage request. The Resource Scheduler
Block (RS) resets the corresponding usage request (RQnn) and permission (PMnn) to 0
upon receiving a usage request cancel command. If there is an entry for the corresponding
usage request in the queue, it is deleted from the queue.
For a cancel command for a permitted usage request, if there is a request for permission in
the queue, the request is deleted after setting the permission (PMnn) of the usage request
that is stored at the head of the queue. If the requester sends an entire resource group
usage request cancel command, the current usage requests are all reset to 0.
● Monitoring of the Resource Usage Request Status

The requester of the resource usage monitors the resource usage availability by referenc-
ing the permission (PMnn) of the Resource Scheduler Block (RS). By referencing the
usage requests of the Resource Scheduler Block (RS), the status of resource usage
requests can be grasped.
■ Maximum Permissible Number Control Function

The number of resources that can be used simultaneously is set to the maximum permis-
sible number (PMH) from other function blocks. When the maximum permissible number
setting is changed, the maximum permissible number control function manipulates the
permission status of the resources by responding to an increase/decrease in the maximum
permissible number (PMH), as described below.
● When the Maximum Permissible Number is Increased.

It increases the number of permissions that can be provided simultaneously for the in-
creased maximum permissible number.
● When the Maximum Permissible Number is Decreased.

It will not give out new permissions until the number of current resource usage becomes
less than the maximum permissible number. For usage requests currently permitted, it
holds the permission status until the usage request cancel command is received.

■ Control Example with the Resource Scheduler Block (RS)
The figure below shows a tank level control example using the Resource Scheduler Block
(RS) RS001 and Sequence Table Block (ST16).
Source tank
Valve 1 2 3 4 5 Valve 10
Tank 1 2 3 4 5 Tank 10
LO LO LO LO LO LO
D031103E.EPS
Figure Tank Level Control Example
This control includes ten processes that open and close the valves. These processes
open valve nn if level LO of the tank n becomes ON, and then close valve nn if the level
LO is released after waiting for the level being recovered. However, no more than three
valves can be opened at a time. Also, the valves are opened in the order in which the
level LO is reached.
The identification numbers of these processes are defined as in the table below.
Table Detecting Input and Identification Number
Identification
Contact input to detect the tank level LO
number
DI0001 1
DI0002 2
DI0003 3
: :
DI00010 10
D031104E.EPS
Call the usage requester, usage request and permission by the corresponding number (1
to 10) of each process identification number.
• Usage Requester 1 (DI001 : Tank 1’s level is LO)
• Usage Request 1
(Usage request 1 that has been submitted by usage requester 1 : Wants to open
valve 1.)
• Permission 1 (Permission for usage request 1 : OK to open valve 1.)

Assume that DI003, DI005, DI002 and DI006 become ON, in this respective order, when
the maximum permissible number is 3. The rules 4, 6, 3 and 7 of sequence table block 1
are satisfied, and usage requests 3, 5, 2 and 6 are entered into the resource schedule
block (RS) RS001 in this order. Because the maximum permissible number is 3, the re-
source schedule block (RS) RS001 issues permissions to usage requests 3, 5 and 2 only,
within the same scan.
Tag name. Rule number
Data item Name. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Data Comment
DI0001.PV.ON Usage requester 1 Y Y N
RS0001.ACT.OFF Entire resource group usage Y
request cancel command
RS0001.ACT.ON Entire resource group Y
usage request command
RS0001.RQ01.1 Usage request command 1 Y
RS0001.RQ01.0 Usage request cancel command 1 Y
D031105E.EPS
Figure Sequence Table Block (ST16) used for Tank Level Control (1/2)

Tag name. Rule number
Data item name. 1 2 3 4 5 6 7 8 9 10
Data Comment
RS0001.PM01.1 Usage request permission 1 permitted Y

DO0001.PV.L Valve 1 open command Y

D031106E.EPS
Figure Sequence Table Block (ST16) used for Tank Level Control (2/2)
Usage request
Waiting for Permission

Usage request 6
Usage request 5 Permission 2

Maximum permissible number: 3

D031107E.EPS
Figure Resource Scheduler Block (RS) Process
The sequence table block 2 indicates which usage request a permission is issued to.
The following describes an example of specifying the reference of permission status for
usage request 3 into the condition symbol column of the sequence table.

RS0001.PM03 1 Y D031108E.EPS

“During condition signal (PM03)” corresponds to the usage request (RQ03). In this ex-
ample, since permissions 3, 5 and 2 received permissions, the rules 3, 5 and 2 of Table 2
are satisfied and the contact outputs are outputted (valve open) according to the descrip-
tions in the action signal column.
In order to issue permission for usage request 6 that is waiting in the queue, it is necessary
for the condition signal status of any one of the usage requests 3, 5 and 2 to be unsatisfied,
and the usage request of the same identification number that became false must be reset.
IMPORTANT
It is always necessary to issue the usage request cancel command, because the usage
request is not reset automatically, even after permission is given for the usage request.
When the usage request signal is an internal switch, turn off the internal switch (when the
ON status means the usage request state) for the next request after permission is sent,
then issue the usage request cancel command.
If the usage request that has been permitted is reset, there will be one vacancy for permis-
sion, and permission is given to usage request 6. The following describes an example of
setting permission 2 to be reset in the condition signal column of the sequence table.

RS0001.RQ02 0 Y D031109E.EPS

● When Issuing the Entire Resource Group Usage Request Command after
Issuing the Entire Resource Group Usage Request Cancel Command
When the entire resource group usage request cancel command and the entire resource
group usage request command are sent, based on rule 1 of sequence table block 1, the
currently issued permissions are all reset, then all the usage requests are sent. Usage
requests 1 to 10 are stored in ascending order in the resource scheduler. At this time,
usage requests 1, 2 and 3 will be given permission within the same scan, and usage
requests 4, 5, 6, 7, 8, 9 and 10 will be placed in the queue for permission.
The figure below shows the status of usage request storage.
Usage request
Usage request 10
Usage request 9
Waiting for permission

Usage request 4


D031110E.EPS
Figure Storage Status of Usage Request
● When Issuing the Entire Resource Group Usage Request Command

Without the Entire Usage Request Cancel Command
When the entire resource group usage request command is issued without the entire
resource group usage request cancel command, the current usage requests that have
been permitted remain as they are, and the other usage requests are stored in the ascend-
ing order.
The figure below shows the storage status of the usage requests.
Usage request
Usage request 10
Usage request 9
Ascending order
Usage request 4
Usage request 1
Waiting for permission
Usage request 6

Usage request 5 Permission 5 No change

D031111E.EPS
Figure Storage Status of Usage Request

● Canceling the Usage Request
The following shows an example of specifying the cancellation of usage request 2. This is
the same specification as that for resetting the usage request.

RS0001.RQ02 0 Y D031112E.EPS
● Changing the Maximum Permissible Number

The following are the methods to change the maximum permissible number to 4.
• When changing on the operation and monitoring functions
Input 4 for the data type PMH in the tuning window.
• When changing from the Sequence Table Block (ST16, ST16E)
Enter as below in the action signal column of the sequence table block.

RS0001.PMH. 4 Y D031113E.EPS
■ Data Items - RS
Table Data Items of Resource Scheduler Block (RS)
Entry Permitted
or Not
RQ01 to RQ32 Usage request 0/1 0
PM01 to PM32 Usage permission 0/1 0
PMH Maximum permission number 0 to 32 32
D031114E.EPS

SEE ALSO
For a list of valid block modes of the RS block, see D3.1.2 “Block Mode of Sequence Control Blocks.”

<Toc> <Ind> <D3.12 Valve Monitoring Block (VLVM)> D3-240
D3.12 Valve Monitoring Block (VLVM)

The Valve Monitoring Block (VLVM) is used to monitor whether the final control
element (valve) is operating properly.
■ Valve Monitoring Block (VLVM)

▼ Valve Monitor
The Valve Monitoring Block (VLVM) handles 16 sets of input signals independently, per-
forming valve operation monitoring and message output for each input signal. A set of input
signals is comprised of a combination of one point of valve contact output and one point (or
two points) of limit switch. Also, when an error occurs in any set of the 16 sets, the mes-
sage output can be extracted from the representative message output terminal (J17).
The figure below shows the function block of the Valve Monitoring Block (VLVM).
Q01 PV01 J01

Action
Q02 verification timer J02
Valve output monitoring
Q31 PV16 J16

Action
Q32 verification timer J17
PVR Representative message
output terminal
D031201E.EPS
Figure Function Block Diagram of the Valve Monitoring Block (VLVM)

The table below lists connection methods and destinations for the Valve Monitoring Block
(VLVM) I/O terminals.
Table Connection Methods and Destinations for Valve Monitoring Block (VLVM) I/O Terminals

manipula- connecti-
tion on
Q01, Input terminal for
Q03, ..., valve contact
Q31 output
Q02,
Limit switch input
Q04, ...,
terminal
Q32
J01 Individual message

to J16 output terminal
Representative
J17 message output
terminal
D031202E.EPS
Connect input terminals (Q01, Q03, ..., Q31) with the contact output leading to the valve.
Connect input terminals (Q02, Q04, ..., Q32) with the contact input (signals from the limit
switch) that indicates the open/close status of the valve. These two types of inputs (for
example, Q01 and Q02) are compared and any mismatch present is detected. If a mis-
match is detected as a result of comparison, the valve abnormal state (PVnn) is set to 1,
and messages specified in the output terminal such as the annunciator message (%AN)
and print message with data (%PR) are output.
The figure below shows an example of monitoring the valve that has one point of contact
output (open signal) and one point of limit switch input (open answer-back) using the Valve
Monitoring Block (VLVM).
Valve monitor block
Contact output monitor DO 0001 Q01 Action

monitoring PV01 J01 %AN,
DI 0001 timer %PR etc.
Limit switch input Q02
(open answerback)
Q03 Action
monitoring PV02 J02
Q04 timer
On/off valve
(with a limit switch)
D031203E.EPS
Figure Connection of Valve Monitoring Block (VLVM)
■ Process Timing
The process timing of VLVM block is only based on periodical start period. The periodic
start period is based on basic scan period only.

■ Valve Monitor Limit Switch Action
There are three types of limit switch actions, which are the input signals of the Valve Moni-
toring Block (VLVM). The type needs to be selected from the three types for each valve
using the Function Block Detail Builder.
• Triggers: Select from “Direct,” “Reverse,” and “Both.”
The default is “Both.”
The following lists the three types of actions:

• Direct Direction
The polarities of the valve contact output and limit switch status are matched.
• Reverse Direction
The polarities of the valve contact output and limit switch status are reversed.
• Both Direction
Two points of limit switches correspond to the valve contact output. One limit switch is
for direct direction and the other is for reverse direction.
ON
Valve manipulated output
OFF
OPEN
Valve action
CLOSE
ON
Limit switch 1
OFF
ON
Limit switch 2
OFF
Positive Negative Bidirectional
action(P) action(N) action(B)
D031204E.EPS
Figure Limit Switch Actions
To set the limit switch to correspond at two points for the both direction specification, assign
limit switch 1 (direct direction) to the input point specified at the input terminal, and limit
switch 2 (reverse direction) to the subsequent point of the specified point.

■ Valve Output Monitor Function
This function inputs the values of contact output (valve contact output) to the contact
operation type final control element and the contact input (limit switch) that represents the
open/close status, then compares the values to detect a mismatch.
The following describes the order of operations for the valve output monitoring.
1. When a change in the valve contact output is detected, the action verification timer
inside the Valve Monitoring Block (VLVM) is started (PT = action confirmation elapsed
time).
2. While the action confirmation timer is being started, the ON/OFF statuses of the valve
contact output and limit switch are compared. If the statuses match, the action confir-
mation timer expires and the system proceeds to step 4.
3. If the statuses do not match after a certain period of time (action confirmation setting
time = MT) has elapsed, data value 1 indicating an error status is stored in the valve
abnormal state (PV01 to PV16).
4. After that, monitoring continues until a change occurs in the valve contact output for
the next time (i.e. until the next valve operation), and the valve abnormal state (PV01
to PV16) is updated.
The monitor action can be specified according to the timing of comparison between the
limit switch and valve contact output. The monitor action is set using the Function Block
Detail Builder.
• Monitor action
Select from “Monitoring the ON side only,” “Monitoring the OFF side only” and
“Monitoring both-side.”
The default is “Monitoring both-side.”

The following describes each monitor action.
• Monitoring the ON Side only
This starts the action verification timer at the rise of valve contact output (OFF➝ON),
and compares the statuses only while the valve contact output is ON.
• Monitoring the OFF Side only
This starts the action verification timer at the fall of the valve contact output
(ON➝OFF), and compares the statuses only while the valve contact output is OFF.
• Monitoring Both Sides
This starts the action verification timer at both the rise and fall of valve contact output,
and compares the statuses while the valve contact output is either ON or OFF.
ON
Output to valve
OFF
OPEN
Valve action
CLOSE
ON
Limit switch
OFF
Difference between valve output 1

and limit switch
0
Action confirmation Action confirmation Action confirmation

setting time setting time setting time
(MT)
ON Abnormality detected message Abnormality recovered
Valve status message
(PV01 to PV16)
OFF
Normal operation Abnormal operation

D031205E.EPS
Figure Valve Output Monitoring (Monitoring Both Sides)

The table below shows the limit switch action specifications and corresponding valve
output monitor actions.
Table List of Valve Output Monitor Action
Valve output monitoring

Limit switch Single-side Single-side
Contact
action Both-side monitoring monitoring monitoring
ON-side OFF-side
Valve
manipulated
output
Positive
Limit switch
action
(P)
Valve abnormal
state
Valve
manipulated
output
Negative
Limit switch
action
(N)
Valve abnormal
state
Valve
manipulated
output
BIdirectional
Limit 1
action
Limit 2
(B)
Valve abnormal
state
Action verification time

D031206E.EPS
• When the action specification for the limit switch is “Operate in Both Direction,” set the
valve abnormal state (PVnn) to 1 if either of the two points of limit switches is a mis-
match to the valve contact output.
Also, the valve abnormal state (PVnn) becomes 0 when both of the two points match
the valve contact output.
• If the valve operation output is changed while the valve status is abnormal (PVnn=1),
the valve abnormal state (PVnn) to reset to 0.
• Upon comparing the valve output contact with the limit switch, if either of the input
destinations has a device error or the data status of input data is faulty (BAD), the
valve abnormal states (PV01 to PV16) hold the current value.

■ Representative Valve Abnormal State Detection Function
The representative abnormal state (PVR) is an information item that represents the abnor-
mal statuses for a maximum of 16 points of valves monitored by the Valve Monitoring Block
(VLVM). The representative abnormal state (PVR) is determined by the logical OR of
individual valve abnormal statuses (PV01 to PV16).
PV01
PV02
OR PVR=1
PV16
D031207E.EPS
Figure Logical OR of Valve Abnormal States
When there is no connection to the limit switch input terminal, the limit switch input terminal
is recognized as unused, so the valve abnormal state (PVnn) is always 0.
■ Message Output
VLVM block may generate an alarm message when an error occurs or recovers to notify
the operator. The message output may be specified.
● Message Output to the Individual Message Output Terminal

At the Valve Monitoring Block (VLVM), the operator can be notified of error occurrences
and recoveries of individual valves by specifying the message output to the output terminal
via the Function Block Detail Builder.
• Individual message output terminal
Specify connection with the “annunciator message,” “print message with data,” “op-
erator guide message” or “internal switch.” Set one point or two points for each valve.
The following describes the output timing of messages.

• Abnormality detected message
Sends the message at the timing in which the valve abnormal state (PVnn) changes
from normal to abnormal (0➝1).
• Abnormality recovered message
Sends the message at the timing in which the valve abnormal state (PVnn) changes
from abnormal to normal (1➝0).

● Message Output to the Representative Message Output Terminal
▼ Representative Message Output
At the Valve Monitoring Block (VLVM), the operator can be notified of error occurrence and
recovery of one of the 16 valves by specifying the message output to the output terminal
via the Function Block Detail Builder.
• Representative message output terminal
Specify connection with the “annunciator message,” “print message with data,” “op-
erator guide message” or “internal switch.” Set one point or two points for each valve.
Be careful that the abnormality recovered message is not output until all the valves return
to their normal state.
• Abnormality detected message
Sends the message at the timing in which the representative valve abnormal state
(PVR) changes from normal to abnormal (0➝1).
• Abnormality recovered message
Sends the message at the timing in which the representative valve abnormal state
(PVR) changes from abnormal to normal (1➝0).
● Specifying the Message Output

For the message output as a connection destination of the output terminal, the abnormality
recovered message may not be output, depending on the types of messages. The table
below shows the presence/absence status of the abnormality recovered message output.
Table Presence/Absence of Abnormality Recovered Message Output
Abnormality Abnormality
Message type
detected recovered
Annunciator message (%AN)
Print message with data (%PR)
Operator guide message (%OG)
D031208E.EPS
: Present
Blank: Absent
: Depends on the builder specification

● Annunciator Message Output
When the annunciator message is specified as the connection destination of the message
output, the abnormality detected message and the abnormality recovered message is sent
with the same number. The abnormality recovered message sent as an annunciator mes-
sage is suffixed with “” at the end.
● Output of the Print Message with Data

▼ Printout Message at Representative Recovery
When the print message with data is specified as the connection destination of the mes-
sage output, the abnormality detected message is sent with the specified message num-
ber. Furthermore, only when “Yes” is specified for the “print message at representative
recovery” or “print message at recovery” using the Function Block Detail Builder, it will send
the abnormality recovered message with the subsequent number of the specified message
number.
• Printout Message at Recovery: Select from “Yes” and “No.”
• Printout Message at Representative Recovery: Select from “Yes” and “No.”
Specify “No” for the “Printout Message at Representative Recovery” or the “Printout Mes-
sage at Recovery” when the connection destination of the message output is other than a
print message with data.
● Message Output to the Internal Switch

The internal switch (%SW) can be specified as the connection destination of the message
output. In this case, the valve abnormal state is set as the ON/OFF status of the internal
switch.
● Message Suppressing
When the message suppression control switch (MCSW) is set to ON (=1), sending of all
messages specified in the output terminal is suppressed. When the message suppression
status is on, setting of the ON/OFF status for the internal switch at the output destination is
not performed. The status of the message suppressing switch (MCSW) can be changed by
the operation and monitoring functions or other function block.

■ Data Items - VLVM
Table Data Items of Valve Monitoring Block (VLVM)
Entry Permitted
or Not
MODE Block mode ----- AUT
PV01 to PV16 Valve abnormal state 0, 1 0
PVR Representative abnormal state 0, 1 0
MCSW Message suppression control switch 0, 1 0
MT01 to
Action confirmation setting time (seconds) 0 to 10000 4
MT16
PT01 to PT16 Action confirmation elapsed time (seconds) 0 to 10000 0
D031209E.EPS

SEE ALSO
For a list of valid block modes of the RS block, see D3.1.2 “Block Mode of Sequence Control Blocks.”

Blank Page
<Toc> <Ind> <D4. Faceplate Blocks> D4-1
D4. Faceplate Blocks

This chapter explains the faceplate blocks and their basic control functions.
The faceplate blocks consist of analog faceplate blocks, sequence faceplate blocks
and hybrid faceplate blocks.
This chapter explains the function details of each type of faceplate blocks.
■ Faceplate Blocks
A faceplate block enables multiple function blocks to be recognized as one function block.
The function blocks that execute the faceplate function are called faceplate blocks. The
following diagram shows positioning of the faceplate function in basic control functions.
FCS
Basic control
Software I/O
Regulatory control blocks Common switch
Arithmetic calculation blocks Sequence control message
Faceplate blocks
SFC blocks
Options
Valve pattern monitoring (*1)
Off-site blocks (*1)
FCS I/O Interface
D040001E.EPS
*1: ¡ £ Valve pattern monitoring and off-site blocks are available in CS 3000.
Figure Faceplate Blocks in Basic Control Architecture
Faceplate blocks are capable of indicating and manipulating the data of multiple function
blocks that comprise a control loop. These indications and operation functions are per-
formed on the instrument faceplate of the operation and monitoring window. Faceplate
blocks are classified into analog faceplate blocks, sequence faceplate blocks and hybrid
faceplate blocks.

<Toc> <Ind> <D4.1 Types of Faceplate Blocks> D4-2
D4.1 Types of Faceplate Blocks

Depending upon the content of indication and manipulation, faceplate blocks are
classified into three types; analog faceplate blocks, sequence faceplate blocks and
hybrid faceplate blocks.
■ Analog Faceplate Blocks

Analog faceplate blocks include the following function blocks that indicate and manipulate
analog data on the instrument faceplate of the monitoring and operation window.
• Dual-Pointer Indicating Station Block (INDST2)
Used for the indication of measured values and the setting of setpoint values.
• Dual-Pointer Manual Station Block (INDST2S)
Used for the setting of setpoint values and manipulated output values.
• Triple-Pointer Manual Station Block (INDST3)
Used for the indication of measured values and the setting of setpoint values as well
as manipulated output.
■ Sequence Faceplate Blocks ¡ £

Sequence faceplate blocks include the following function blocks that indicate sequence
phases and manipulate switch statuses on the instrument faceplate of the operation and
monitoring window. These faceplate blocks can be used as man-machine interfaces of the
sequence control function.
• Batch Status Indicator Block (BSI)
Used for the indication of sequence phases.
• Extended 5-Push-Button Switch Block (PBS5C)
Used for the lamp indication and operation of five push buttons.
• Extended 10-Push-Button Switch Block (PBS10C) (*1)
Used for the lamp indication and operation of ten push buttons.
*1: £ Extended 10-push-button switch block (PBS10C) is only available in CS 3000 system.
■ Hybrid Faceplate Blocks

A hybrid faceplate block has the functions of an analog faceplate block and those of a
sequence faceplate block.
The function blocks that are classified as hybrid faceplate blocks include the Extended
Hybrid Manual Station Block (HAS3C). The Extended Hybrid Manual Station Block
(HAS3C) has the functions of Triple-Pointer Manual Station Block (INDST3) and those of
the Extended 5-Push-Button Switch Block (PBS5C).
IM 33S01B30-01E 4th Edition : Jan.11,1999-00

■ Example of Using the Faceplate Block
The following example shows how to use an analog faceplate block.
ST16
PID PV
TIC102 T1 IN TC 100
INDST3
TC100
IN1
AUT
CALCU IN2 NR
X103 F1 IN 100.0
SV
IN1 CALCU PID

F2 IN FIA100 FIC101 V OUT
PV
0.0
IN2 IN3
MV T1 IN
P2 IN T2 IN V OUT
D040101E.EPS
Figure Example of Using the Faceplate Block
In the above example, the data items of TC100 (INDST3 block), TIC102 (PID controller
block) and FIC101 (PID controller block) are connected. The connected data items are
shown below.
• PV of TC100 and PV of TIC102
• SV of TC100 and SV of TIC102
• MV of TC100 and MV of FIC101
• MODE of TC100 and MODE of FIC101.

By connecting these data items, the following functions can be realized.
● Indication of Data Items

The values of TC100 data items are changed to the values of the connected data items.
• The value of the data item PV of TC100 is changed to that of TIC102’s PV.
• The value of SV is changed to that of TIC102' SV, and the value of MV is changed to
that of FIC101’s MV.
• The block mode of MODE is changed to that of FIC101’s MODE. However, the mode
will not change to O/S.
● Setting Operation
When a value is set to any data item of TC100 from the instrument faceplate or other
setting source, the value of the connected data item will be changed.
• When SV of TC100 is changed, SV of TIC102 will change to the same value.
• When MV of TC100 is changed, MV of FIC101 will change to the same value.
• When the block mode of TC100 is changed, MODE of FC101will change to the same
block mode. However, the mode will not change to O/S.

<Toc> <Ind> <D4.2 Push Button Operation of Faceplate Blocks> D4-5
D4.2 Push Button Operation of Faceplate Blocks

There are three types of push buttons common to Sequence faceplate blocks and
Hybrid faceplate blocks: momentary button, alternate button and radio button.
■ Momentary Button Action

When button operation is performed by the operator, the manipulated command value
(MVnn) changes to “1 (ON)” for a period specified as the output time span in the unit of scan
cycle. When the specified period is elapsed, the value returns to “0 (OFF)” automatically.
The following figure shows the relationship between the manipulated command value
(MVnn) and the output value when button operation is performed.
Block processing
timing Button operation
ON
MVnn OFF
ON
Output OFF
Time
t 2t 3t 4t 5t
t = Scan period
Output time span
D040201E.EPS
Figure Action When the Momentary Button is Specified
The manipulated command value (MVnn) remains ON for a period of time equivalent to a
multiple of the scan period.
If button operation is performed while the manipulated command value (MVnn) is ON, the
value will remain ON through the specified scan periods from the time when the last button
operation was performed.
The following figure shows the action of the momentary button when button operation is
performed while the manipulated command status is ON.
Block processing
timing Button operation Button operation
ON
MVnn OFF
ON
Output OFF
Time
t 2t 3t 4t 5t
t = Scan period
Output time span
D040202E.EPS
Figure When Button Operation is Performed While the Manipulated Command Status is ON

■ Alternate Button Action
When button operation is performed by the operator, the manipulated command value
(MVnn) changes to OFF if it was ON, and to ON if it was OFF. The following figure shows the
relationship between the manipulated command value (MVnn) and the output value when
button operation is performed.
Block processing
ON
MVnn OFF
ON
Output OFF
Time
t 2t 3t 4t 5t
t = Scan period
D040203E.EPS
Figure Action When the Alternate Button is Specified
When multiple button operations are performed in a single scan period, the manipulated
command value (MVnn) changes with each button operation. The change in the manipu-
lated command value (MVnn) will be executed immediately after the operation, while the
output of the manipulated command value (MVnn) will be executed during block processing.
It must be noted that the change in manipulated command value (MVnn) will not be trans-
mitted to the storage destination, even when multiple button operations are performed in a
single scan period.
The following figure shows the relationship between the manipulated command value
(MVnn) and the output value when multiple button operations are performed in one scan
period.
Block processing
ON
MVnn OFF
ON
Output OFF
Time
t 2t 3t 4t 5t
t = Scan period
D040204E.EPS
Figure When Multiple Button Operations are Performed in One Scan Period

■ Radio Button Action
When the operator pushes one button (MVnn) ON, all other manipulated command values
(MVnn) will be turned OFF forcibly.
Switches that are turned OFF forcibly while the “radio button” is in use are limited to those
that support the button operation function.
When the “radio button” is in use, even a switch whose operation disable status is ON will
be turned OFF forcibly once other switches are turned ON.
Depending upon the operation timing, multiple switch statuses may turn ON simulta-
neously. In this case, only the switch with the smallest number of manipulated command
values (MVnn) that are ON will remain so. All other switch statuses will be turned OFF
forcibly.

<Toc> <Ind> <D4.3 Block Mode and Status of Faceplate Blocks> D4-8
D4.3 Block Mode and Status of Faceplate Blocks

The block mode and status of the faceplate block are different from the block mode
and status of other function blocks. In this section, the block mode and status that
are specific to the faceplate block are explained.
SEE ALSO
For more information about block mode and status, see a chapter C6 “Block Mode and Status.”
■ The Block Mode of the Faceplate Block

The block mode of a faceplate block agrees with the connected destination function block,
except for the out of service (O/S) mode.
The faceplate block periodically refers to the connected destination function block to keep
the mode agree with each other. On the other hand, if the block mode of the faceplate block
changes, the connected destination function block changes too.
■ The Block Status of the Faceplate Block

The block status of a faceplate block agrees with the connected destination function block.
the status agree with each other.
■ The Alarm Status of the Faceplate Block

The alarm status of a faceplate block agrees with the connected destination function block,
except for the connection failure alarm (CNF) or normal (NR) status.
the alarm status agree with each other.

■ The Data Status of the Faceplate Block
In the faceplate block, the three types of analog data, namely, the process variable (PV),
setpoint value (SV), and manipulated output value (MV), are treated as “data with data
status.” The data status of the faceplate block agrees with the data status of the connected
destination function block. If there is no block connected, the data status is determined by
the status of its own data.
■ The Status Change Message

In the faceplate block, a status change message is sent when a change has occurred to the
block mode or block status.
Also, the status change message bypass function is provided to suppress the status
change message. The status change message bypass action is determined by the value
which is specified in the builder of the block itself, regardless of the existence or absence of
a block mode connection or block status connection.
However, in the absence of a block status connection, a status change message is sent
even when the block status does not change if the same status as the current one has
been specified as the block status.

D4.3.1 Block Mode of Faceplate Blocks

The block mode of a faceplate block agrees with the block mode of connected
destination function block, except for the off-service (O/S) mode.
Depending on the existence of the block mode connection, the faceplate block takes
different action when the block mode is changed.
■ Behavior of Faceplate with Block Mode Connection

the block mode agree with each other. The faceplate block periodically refers to the con-
nected destination function block to keep the block mode agree with each other. On the
other hand, if the block mode of the faceplate block is changed, the block mode of the
connected destination function block changes too.
When connect with other blocks, the data item MODE is specified of the destination tag to
the terminal (JMOD). If a data item other than MODE is specified, it may not work properly.
A faceplate block cannot be connected to another faceplate block.
● The Block Mode that can be Established

The types of the block mode (AUT, MAN, etc.) that can be established for the faceplate
block depend on the types of the block mode that can be connected as destination block.
Whether or not a mode change is possible also depends on whether the mode change is
enabled or not of the connected destination block.
● Off-Service (O/S) Mode Related Actions when Block Mode Change

When link the block mode change of the faceplate block to the out of service (O/S) mode of
connected destination block, the faceplate takes different action. The out of service (O/S)
mode related actions are specified as follows:
Table Block Mode Change Action Specifications Regarding O/S (1/2)
Change operation Action of the connection
at the faceplate block destination block
O/SAMAN O/SAMAN
O/SAMAN AUTAMAN
O/S(MAN)AMAN O/SAMAN
O/S(MAN)AO/S No change
MANAO/S No change
D040301E.EPS
Note: MAN indicates a mode other than O/S. Actions are the same for all mode other than O/S.

Table Block Mode Change Action Specifications Regarding O/S (2/2)
Change operation at the
Action of the faceplate block
connection destination block
O/SAMAN O/SAO/S
O/SAMAN O/S(MAN)AMAN
MANAO/S O/SAO/S
MANAO/S MANAO/S(MAN)
D040302E.EPS
Note: MAN indicates a mode other than O/S. Actions are the same for all mode other than O/S.
• When the block mode of the faceplate block changes to out of service (O/S), only the
mode of the faceplate block becomes out of service (O/S), the mode of the connected
destination function block does not change.
• When the block mode of the connected destination block is changed to out of service
(O/S), the block mode of the faceplate block does not become out of service (O/S) but
becomes O/S (MODE) which is a compound block mode. “MODE” of O/S (MODE)
indicates either the MAN, AUT or CAS mode. If the block mode of the faceplate block
is displayed as “MAN O/S” on the operation and monitoring function or described as
“O/S (MAN)” in this chapter, it means that the connected destination is in the out of
service (O/S) mode and the faceplate block is in the manual (MAN) mode.
• Actions that take place when a mode change is performed against the faceplate block
while the faceplate block is in the out of service (O/S) mode or O/S (MAN):
When a block mode change is performed directly against the faceplate block, the
same block mode change command is sent simultaneously to the connected destina-
tion function block of the faceplate block.
• When a mode change is performed to the connected destination function block while
the faceplate block is in the out of service (O/S) mode:
The faceplate block remains in the out of service (O/S) mode.

■ Behavior of Faceplate without Block Mode Connection
When there is no block mode connection, the block modes that are unique to the faceplate
block are used, as shown in the table below. Block mode can be changed only by external
operations outside the faceplate block, unless the block is returning from an O/S over
transition state.
Table Behavior of Faceplate Mode without Block Mode Connection
Block mode
Description
Symbol Name
O/S Out of service Indicates a state in which all functions are stopped.
MAN Manual
SEMI Semi-automatic
AUT Automatic Specific meanings of each mode can be defined freely using the
CAS Cascade application.
RCAS Remote cascade

ROUT Remote output
D040303E.EPS
Note: SEMI (semi-automatic) has the same priority as AUT and MAN, and is mutually exclusive with the two.
■ Interlock Condition for Faceplate Block Mode Change

Like other function blocks, the faceplate block has an interlock switch input terminal (INT)
which activates the block mode change interlock function. The block mode change inter-
lock function takes effect according to the status of the switch connected to the terminal
(INT) of the faceplate block itself. Whether the faceplate block is connected to other func-
tion block or not is irrelevant.
However, if the connected destination block and the faceplate block use the different signal
for block mode change interlock, the faceplate block will follow the block mode change of
the connected destination function block.
Thus, when the block mode is restricted under the faceplate block’s interlock condition , the
connected destination block can not change block mode again.

D4.3.2 Block Status of Faceplate Blocks

The block status of the faceplate block agrees with the block status of the connected
destination function block. If there is no destination connection, a unique block
status is used.
■ Behavior of Faceplate with Block Status Connection

The faceplate block periodically refers to the connected destination block status to keep
their block status agree with each other.
To establish block status connection, connect the data item BSTS (block status) of the
destination tag to the terminal (JBST) of faceplate block. When a data item other than
BSTS is specified, the faceplate block does not operate properly. A faceplate block cannot
be connected to another faceplate block.
When block status connection establishes, the connected destination function block’s is
read via JBST terminal, status change can be performed only from the faceplate block.
The types of the block status (STOP, RUN, etc.) for the faceplate block depend on the
types of the block status available for the connected destination block.

■ Behavior of Faceplate without Block Status Connection
▼ USER1(Faceplate Block)
When there is no block status connection, the block status strings defined on the user-
defined Status Character String Builder unique to the faceplate block can be used. The
default status strings for faceplate blocks are shown in the table below.
Table Behavior of Faceplate Status without Block Status Connection
Block status
Priority States
Symbol Name
FAIL Fail
ABRT Abort
3
IDLE Idle
SIML Simulation
RUN Run
STOP Stop
Specific meanings of each status can be defined freely
STUP Startup
1 using the application.
HOLD Hold
WAIT Wait
END End
SDWN Shutdown
0 ESD Emergency shutdown
RSTR Restart
D040304E.EPS
The character strings for faceplate block status are the user-defined status character string
defined in column USER1 on the Status Character String Builder.
In the table, the position 33 is system reserved, can not be used.
A block status string can be defined with up to 8 alphanumeric characters including under-
score (_).

D4.3.3 Alarm Status of Faceplate Blocks

The alarm status of a faceplate block agrees with the connected destination function
block’s alarm status, except for the connection failure (CNF) or normal (NR) status. If
there is no connection destination, a unique alarm status is used.
The alarm-related functions such as alarm acknowledgment, alarm detection specifi-
cation and alarm inhibition functions are available.
■ Behavior of Faceplate with Alarm Status Connection

The faceplate block periodically refers to the connected destination block’s alarm status to
keep their alarm status agree with each other.
To establish the alarm status connection, connect the data item ALRM of the destination
tag to the terminal (JALM) of the faceplate block. If a data item other than ALRM is used, it
does not work properly. A faceplate block cannot be connected to another faceplate block.
If alarm status connection establishes, any alarm status change operation on the faceplate
block becomes invalid.
The types of the alarm status (IOP, HI, etc.) for the faceplate block depend on the types of
alarm status available for the connected destination block.
When the connected destination block changes to connection failure (CNF) alarm status,
the faceplate block does not change to connection failure (CNF).

■ Behavior of Faceplate without Alarm Status Connection
When there is no alarm status connection, the alarm strings defined on the user-defined
Status Character String Builder unique to the faceplate block can be used. The default
alarm strings for faceplate blocks are shown in the table below.
The alarm status of the faceplate block can be changed by the alarm status change opera-
tion.
Table Behavior of Faceplate Alarm Status without Alarm Status Connection
Alarm status
Description
Symbol Name
NR Normal status Indicates a state in which no alarm has occurred.
OOP Output open alarm
IOP High input open alarm
IOP- Low input open alarm
ESTP Emergency stop alarm
HIHI High-High alarm
LOLO Low-Low alarm
HI High alarm
LO Low alarm Specific meanings of each alarm can be defined freely using the
DV+ Positive deviation alarm application.
DV- Negative deviation alarm

TRP Trip alarm
SCBL Scramble alarm
INT Interlock alarm
ERR Error alarm
DISC Discrete alarm
BLCK Block alarm
CNF Connection failure alarm Displays a state defined in common specification.
D040305E.EPS
SEE ALSO
Faceplate alarm status characters strings are defined in column USER9 on user-defined character string
builder. For more information, see “■ User-Defined Alarm Status Character String” in E12.4, “Alarm
Status Character String and Alarm Processing.”
■ Alarm-Related Functions
The alarm-related functions such as alarm acknowledgment, alarm detection specification
and alarm inhibition functions are available for a faceplate block. They can be set on the
data items named alarm flashing status (AFLS), alarm detection specification (AF), and
alarm inhibition specification (AOFS), respectively.
The settings on the faceplate block itself determines the alarm-related functions. Whether
the faceplate is connected with other function block is irrelevant.

D4.3.4 Data Status of Faceplate Blocks

A faceplate block has three types of analog data, the process variable (PV), setpoint
value (SV), and manipulated output value (MV). They are referred as “data with data
status.” The data status of the process variable (PV), setpoint value (SV), and ma-
nipulated output value (MV) agree with the data status of the connected destination
block. If there is no block connected, the data status is determined by the status of
the data setting block.
■ Faceplate with Data Connection

The data status agrees with the data status of the connected destination function block.
When data from the terminal connected function block have bad value (BAD) status, the
data set to the faceplate as it is anyway.
The faceplate blocks, except for batch status block (BSI), only read process variable (PV)
from the connected destination blocks. The PV can not be changed from the faceplate.
Therefore, to set the process variable (PV) of the faceplate block to CAL will result in a
setting error. If you really want to change the PV to calibration state you can do it directly on
the connected destination block.
■ Faceplate without Data Connection

When there is no data connection, the data status depends on the data status of its own
data.
For the faceplate blocks that have no connection with other blocks, data can be set exter-
nally such as from the operation and monitoring function. In this case, the bad value (BAD)
data status is reset.

<Toc> <Ind> <D4.4 Dual-Pointer Indicating Station Block (INDST2)> D4-18
D4.4 Dual-Pointer Indicating Station Block (INDST2)

The Dual-Pointer Indicating Station Block (INDST2) is a faceplate block used for
indication.
■ Dual-Pointer Indicating Station Block (INDST2)

▼ Connection Information
The Dual-Pointer Indicating Station Block (INDST2) is a faceplate block used for indication.
Here is a function block diagram of the Dual-Pointer Indicating Station Block (INDST2).
JMOD MODE
JBST BSTS
JALM ALRM
JPV PV
JSV SV
J01 SVH
J02 SVL
INT
D040401E.EPS
Figure Function Block Diagram of Dual-Pointer Indicating Station Block (INDST2)

The figure below shows an example of the instrument faceplate of the Dual-Pointer Indicat-
ing Station Block (INDST2) displayed in the operation and monitoring window.
AIC100
System A
Concentration
AUT
NR
100.0
80.0
60.0
40.0
20.0
0.0
D040402E.EPS
Figure Display Example of Dual-Pointer Indicating Station Block (INDST2)
The table below shows the connection types and connection destinations of the I/O termi-
nals of the Dual-Pointer Indicating Station Block (INDST2).
Table Connection Types and Connection Destinations of the I/O Terminals of Dual-Pointer
Indicating Station Block (INDST2)
Block mode
JMOD
connection
Block status
JBST
connection
Alarm status
JALM
connection
PV
JPV
connection
SV
JSV
connection
SVH
J01
connection
SVL
J02
connection
Interlock
INT
switch input
D040403E.EPS
: Connection is available only when connecting to a selector switch block (SW-33, SW-91).

■ Analog Data Display Function
The Dual-Pointer Indicating Station Block (INDST2) references the analog data at the
connection destination of the I/O terminals shown below during each scan period, and
stores data values and data statuses as data items.
If no I/O connection terminal is connected, the values currently stored in the data items are
held.
Table Target I/O Terminals of the Analog Data Display and Corresponding Data Items
I/O terminal Data item
JPV Process variable (PV)
JSV Setpoint value (SV)
J01 Setpoint high limit (SVH)
J02 Setpoint low limit (SVL)
D040404E.EPS
■ Analog Data Operation Function

When setting operation is performed to any data items of the Dual-Pointer Indicating
Station Block (INDST2), the set data item values will be set to the connection destination of
the corresponding I/O terminals shown below:
Table Target I/O Terminals of the Analog Data Operation Function and Corresponding Data Items
D040405E.EPS
The setting of analog data to the connection destination is performed during the periodic
scan that immediately follows the setting operation to the data item of the Dual-Pointer
Indicating Station Block (INDST2).

■ Data Items - INDST2
Table Data Items of Dual-Pointer Indicating Station Block (INDST2)
Entry Permitted
or Not
BSTS Block status ----- 0
PV Process variable PV engineering unit value SL
SH Scale high limit Value in the same engineering unit as PV -----
SL Scale low limit Value in the same engineering unit as PV -----
D040406E.EPS


<Toc> <Ind> <D4.5 Dual-Pointer Manual Station Block (INDST2S)> D4-22
D4.5 Dual-Pointer Manual Station Block (INDST2S)

The Dual-Pointer Manual Station Block (INDST2S) is a faceplate block used for
operation.
■ Dual-Pointer Manual Station Block (INDST2S)

Here is a function block diagram of the Dual-Pointer Manual Station Block (INDST2S).
JMOD MODE
JBST BSTS
JALM ALRM
JSV SV
JMV MV
J01 SVH
J02 SVL
J03 MH
J04 ML
INT
D040501E.EPS
Figure Function Block Diagram of Dual-Pointer Manual Station Block (INDST2S)

The figure below shows an example of the instrument faceplate of the Dual-Pointer Manual
Station Block (INDST2S) displayed in the operation and monitoring window.
AIC200
System B
Concentration
AUT
NR
100.0
80.0
60.0
40.0
20.0
0.0
D040502E.EPS
Figure Display Example of Dual-Pointer Manual Station Block (INDST2S)
nals of the Dual-Pointer Manual Station Block (INDST2S).
Table Connection Types and Connection Destinations of the I/O Terminals of Dual-Pointer
Manual Station Block (INDST2S)
Block mode
JMOD
connection
Block status
JBST
connection
Alarm status
JALM
connection
SV
JSV
connection
MV
JMV
connection
SVH
J01
connection
SVL
J02
connection
MH
J03
connection
ML
J04
connection
Interlock
INT
switch input
D040503E.EPS

The Dual-Pointer Manual Station Block (INDST2S) references the analog data at the
held.
Table Target I/O Terminals of Analog Data Display and Corresponding Data Items
JMV Manipulated output value (MV)
J03 Manipulated variable high-limit setpoint (MH)
J04 Manipulated variable low-limit setpoint (ML)
D040504E.EPS
The display form of the manipulated output value (MV) is set in the Function Block Detail
Builder.
• MV Display Style: Select from “Auto determination” or “User Define.”
The default setting is “Auto determination.”
When “User Define” is selected, set the engineering unit and scale range of the manipu-
lated output value (MV). The engineering unit and scale range of the manipulated output
value (MV) are set in the Function Block Detail Builder.
• MV Engineering Unit Symbol: MV engineering unit.
The default setting is “%.”
• MV Range:
The high limit and low limit values of the maximum range of the manipulated output
value.
The default setting is “100.0” for the high limit value and “0.0” for the low limit value.

When setting operation is performed to any data items of the Dual-Pointer Manual Station
Block (INDST2S), the set data item values will be set to the connection destination of the
corresponding I/O terminals shown below:
Table Target I/O Terminals of Analog Data Operation and Corresponding Data Items
D040505E.EPS
scan that immediately follows the setting operation to the data item of the Dual-Pointer
Manual Station Block (INDST2S).

■ Data Items - INDST2S
Table Data Items of Dual-Pointer Manual Station Block (INDST2S)
Item or Not
MV Manipulated output value MV engineering unit value MSL
D040506E.EPS


<Toc> <Ind> <D4.6 Triple-Pointer Manual Station Block (INDST3)> D4-27
D4.6 Triple-Pointer Manual Station Block (INDST3)

The Triple-Pointer Manual Station Block (INDST3) is a faceplate block used for
indication operation.
■ Triple-Pointer Manual Station Block (INDST3)

Here is a function block diagram of the Triple-Pointer Manual Station Block (INDST3).
JMOD MODE
JBST BSTS
JALM ALRM
JPV PV
JSV SV
JMV MV
J01 SVH
J02 SVL
J03 MH
J04 ML
INT
D040601E.EPS
Figure Function Block Diagram of Triple-Pointer Manual Station Block (INDST3)

The figure below shows an example of the instrument faceplate of the Triple-Pointer
Manual Station Block (INDST3) displayed in the operation and monitoring window.
AIC300
System C
Concentration
AUT
NR
100.0
80.0
60.0
40.0
20.0
0.0
D040602E.EPS
Figure Display Example of Triple-Pointer Manual Station Block (INDST3)
nals of the Triple-Pointer Manual Station Block (INDST3).
Table Connection Types and Connection Destinations of I/O Terminals of Triple-Pointer Manual
Station Block (INDST3)
Block mode
JMOD
connection
Block status
JBST
connection
Alarm status
JALM
connection
JPV PV connection
JSV SV connection
JMV MV connection
J01 SVH connection
J02 SVL connection
J03 MH connection
J04 ML connection
Interlock
INT
switch input
D040603E.EPS

The Triple-Pointer Manual Station Block (INDST3) references the analog data at the
held.
D040604E.EPS
Builder.
• MV Display Style: Select from “Auto determination” or “User Define.”
The default setting is “Auto determination.”
• MV Range:
value.

When setting operation is performed to any data items of the Triple-Pointer Manual Station
Block (INDST3), the set data item values will be set to the connection destination of the
corresponding I/O terminals shown below:
D040605E.EPS
scan that immediately follows the setting operation to the data item of the Triple-Pointer
Manual Station Block (INDST3).

■ Data Items - INDST3
Table Data Items of Triple-Pointer Manual Station Block (INDST3)
Item or Not
MH Manipulated variable high -limit setpoint MSL to MSH MSH
ML Manipulated variable low -limit setpoint MSL to MSH MSL
D040606E.EPS


<Toc> <Ind> <D4.7 Batch Status Indicator Block (BSI)> D4-32
D4.7 Batch Status Indicator Block (BSI)

The Batch Status Indicator Block (BSI) is a sequence faceplate block that has inter-
nal functions to display sequence phase signals and to operate three push button
switches.
■ Batch Status Indicator Block (BSI)

Here is a function block diagram of the Batch Status Indicator Block (BSI).
JMOD MODE
JBST BSTS
JALM ALRM
SET SV PV
SWOP[1]
INT
SWST[1]
SWCR[1]
SVLMH
Q01 PV01 SWLB[1]
SVLMH
Q02 PV02 SWLB[2]

MH
Q03 PV03 SWLB[3]
D040701E.EPS
Figure Function Block Diagram of Batch Status Indicator Block (BSI)

The figure below shows an example of the instrument faceplate of the Batch Status Indica-
tor Block (BSI) displayed in the operation and monitoring window.
BS100
Phase in
System A
MAN
NR
Cooling
16
START
HALT
STOP
1
D040702E.EPS
Figure Display Example of Batch Status Indicator Block (BSI)
nals of the Batch Status Indicator Block (BSI).
Table Connection Types and Connection Destinations of I/O Terminals of Batch Status Indicator
Block (BSI)
Block mode
JMOD
connection
Block status
JBST
connection
Alarm status
JALM
connection
SV
SET
connection
PV01
Q01
connection
PV02
Q02
connection
PV03
Q03
connection
Interlock
INT
switch input
D040703E.EPS

■ Phase Signal Display Function
▼ Process Name 1 to 16
The phase signal display function is a function that displays the name of the phase being
executed at the plant, on the instrument faceplate of the operation and monitoring window.
The Batch Status Indicator Block (BSI) performs processing in the following order.
• References the data at the connection destination of the SV connection terminal
(SET), and stores the referenced value as the current phase step number (SV).
• Select the current phase signal (PHAS[SV]) from process signals (PHAS[n]) based on
the value stored as the current phase step number (SV), and sets it as the current
phase signal (PV).
• If no data is linked to the SET terminal, PHAS[SV] is selected by using the value held
as SV.
• If the value of the current phase step number (SV) is 17 or larger, the value of the
current phase signal (PV) is held as is.
• If the value of the current phase step number (SV) is 17 or larger, the current phase
signal (PV) will be changed when character string data is set to the signal.
Up to 16 phase signals can be defined in the Function Block Detail Builder. Phase signals
are defined as one-dimensional array data (PHAS[n]) whose elements are character
strings containing 16 alphanumeric characters.

■ Switch Status Input Function
The switch status input function of the Batch Status Indicator Block (BSI) determines
whether the switch statuses (PV01 to PV03) are ON or OFF in accordance with the status
data value of the connection destination.
● Action of the Switch Status Input Function

The Batch Status Indicator Block (BSI) references the status information at the connection
destination of input connection terminals (Q01 to Q03) during each scan period. If the value
of the referenced status information is “0,” then the switch status becomes OFF. If the value
is other than “0,” then the switch status becomes ON.
When the switch status is OFF, the values of PV01 to PV03 are “0.” When the switch status
is ON, the values of PV01 to PV03 are “1.”
● Operating Conditions of the Switch Status Input Function

Depending upon the connection status of the I/O terminal and the switch type setting, data
reference and the switch status (PVnn) determination may or may not be performed.
Table Operating Conditions of the Switch Status Input Function
I/O connection Switch type Data reference Switch status determination
No connection ------
Not used
Lamp
Connection
Button
Button with lamp
D040704E.EPS
: Performed
Blank: Not performed

■ Lamp Indication Function
▼ Label for OFF, Label for ON, Display Color for OFF, Display Color for ON
The lamp indication function of the Batch Status Indicator Block (BSI) changes the indica-
tion color of the push button switch and the indication content of its switch label when the
value of each switch status (PV01 to PV03) is changed.
● Action of the Lamp Indication Function

When the ON/OFF status of each switch (PV01 to PV03) changes, the values of the corre-
sponding switch indication color (SWCR1 to SWCR3) and switch label (SWLB1 to
SWLB3), which are data items, will change. Accordingly, the indication color and switch
label of the push button switch, which is located on the instrument faceplate of the Batch
Status Indicator Block (BSI), will change.
The setting of the indication color and switch label of the push button switch can be
changed by using the Function Block Detail Builder.
The following are the default set values of each switch indication color and label.
• Display color at ON: Red
• Display color at OFF: White
• Label at ON: ON
• Label at OFF: OFF
● Operating Conditions of the Lamp Indication Function

Depending upon the connection status of the I/O terminal and the switch type setting,
indication color determination and switch label determination may or may not be per-
formed.
Table Operating Conditions of the Lamp Indication Function
Indication color
I/O connection Switch type Switch label determination
determination
Not used
Lamp
Connection
Button
Button with lamp
D040705E.EPS
: Performed

■ Button Operation Function
The button operation function of the Batch Status Indicator Block (BSI) sets the value of
each switch status (PV01 to PV03) to the connection destination when button operation is
performed by the operator.
● Action of the Button Operation Function

When button operation is performed by the operator on the instrument faceplate, or when
data is set to PV01 to PV03 from outside the block, the corresponding switch status (PV01
to PV03) will change. How the switch status changes depends on the setting of the button
action.
When the value of PV01, PV02, or PV03 has been changed, that value (PV01 to PV03) is
set to the connection destination of the corresponding I/O terminal (Q01 to Q03). This
setting is executed during the first periodic scan following the setting operation to the data
item of the Batch Status Indicator Block (BSI).
● Operating Conditions of the Button Operation Function

switch status (PVnn) determination and data output may or may not be performed.
Table Operating Statuses of the Button Operation Function
Switch status
I/O connection Switch type Data output
determination
Not used
Lamp
Connection
Button
Button with lamp
D040706E.EPS
: Performed

● Button Action
▼ Button Action
The button action references the ways in which the switch status changes when button
operation is performed by the operator.
The button action of the Batch Status Indicator Block (BSI) is defined in the Function Block
Detail Builder. Two types of button actions are available for selection: “check button” and
“radio button.”
• Check button action
When button operation is performed by the operator, the switch status changes. The
status changes to OFF (0) if it was ON (1), and to ON (1) if it was OFF (0). Multiple
switches can be turned ON simultaneously.
• Radio button action
When button operation is performed by the operator, all switches other than the one
that has been turned ON (1) by the operation will be turned OFF (0) forcibly.
• Switches that are turned OFF forcibly while the “radio button” is in use are limited to
those that support the button operation function.
• When the “radio button” is in use, even a switch whose operation disable status is ON
will be turned OFF forcibly once other switches have been turned ON.
• In some circumstances, such as when switch statuses are referenced by the lamp
indication function, multiple switch statuses may become ON simultaneously. In this
case, only the switch with the smallest number among the switches that are ON will
remain so. All other switch statuses will be turned OFF forcibly. When any switch
status is turned OFF forcibly, its PVnn value will be set to the connection destination of
the corresponding I/O terminal, as is the case with the button operation function.

■ Switch Flashing Function
The switch flashing function flashes the lamp of each switch on the instrument faceplate.
When the switch flashing status (SWST[n]) is set to “1” through data setting, the lamp
indication on the instrument faceplate starts flashing. When the switch flashing status
(SWST[n]) is set to “0,” the lamp indication returns to a normal state.
■ Switch Operation Disable Function

The switch operation disable function is a function that disables switch operation from the
instrument faceplate. This function can enable or disable operation of the status (PVnn) and
flashing status (SWST[n]) of each switch.
When a numeric value of 0 or less is set as the switch operation disable status (SWOP[n]),
operation is enabled.
When a numeric value of 1 or more is set as the switch operation disable status
(SWOP[n]), operation is disabled.
Note that this function disables only the operations performed on the instrument faceplate.
Even when switch operation is disabled by this setting, other switch operations, such as the
setting of data between function blocks and data entry operation from the tuning window of
the specified tag and data item names, can be performed freely.

■ Data Items - Batch Status Indicator Block (BSI)
Table Data Items of Batch Status Indicator Block (BSI)
Entry Permitted
or Not
Equivalent to a string of 16 alphanumeric

PV Current phase step name -----
characters
SV Current phase step number 1 to 99 1
PV01 to PV03 Switch status 1 to 3 0/1 0
SWCR[1] to [3] Switch indication color 0 to 15 7

SWLB[1] to [3] Switch label -----
characters
SWST[1] to [3] Switch flashing status 0/1 0
SWOP[1] to [3] Switch operation disable status -15 to 15 0

PHAS[1] to [16] Phase step name -----
characters
D040707E.EPS


<Toc> <Ind> <D4.8 Extended 5-Push-Button Switch Block (PBS5C)> D4-41
D4.8 Extended 5-Push-Button Switch Block (PBS5C)

The Extended 5-Push-Button Switch Block (PBS5C) is a sequence faceplate block
that holds status data of five push button switches.
■ Extended 5-Push-Button Switch Block (PBS5C)

The Extended 5-Push-Button Switch Block (PBS5C) is a sequence faceplate block that
holds status data of five push button switches, and changes the indication on the instru-
ment faceplate in accordance with the status of each push button switch.
Here is a function block diagram of the Extended 5-Push-Button Switch Block (PBS5C).
JMOD MODE
AKLB[1]
JBST BSTS SWOP[1]
JALM ALRM SWST[1]MV
SWCR[1]MV
SVH
Q01 PV01 SWLB[1]
MVSVH MV01 B01
SVL
Q02 PV02 SWLB[2]
SVHSVL MV02 B02
MH
Q03 PV03 SWLB[3]
SVLMH MV03 B03
Q04 PV04 SWLB[4]

MH MV04 B04
Q05 PV05 SWLB[5] MV05 B05
INT
D040801E.EPS
Figure Function Block Diagram of Extended 5-Push-Button Switch Block (PBS5C)

The figure below shows an example of the instrument faceplate of the Extended 5-push-
button switch block (PBS5C) displayed in the operation and monitoring window.
SC100
System A
MAN NR
NR
SW1 OFF
V1
CLOSE
P1 STOP
SW2 OFF
V2
CLOSE
D040802E.EPS
Figure Display Example of Extended 5-Push-Button Switch Block (PBS5C)

nals of the Extended 5-Push-Button Switch Block (PBS5C).
Table Connection Types and Connection Destinations of I/O Terminals of Extended 5-Push-
Button Switch Block (PBS5C)
Block mode
JMOD
connection
Block status
JBST
connection
Alarm status
JALM
connection
PV01
Q01
connection
PV02
Q02
connection
PV03
Q03
connection
PV04
Q04
connection
PV05
Q05
connection
MV01
B01
connection
MV02
B02
connection
MV03
B03
connection
MV04
B04
connection
MV05
B05
connection
Interlock
INT
switch input
D040803E.EPS

The switch status input function of the Extended 5-Push-Button Switch Block (PBS5C)
determines whether the switch statuses (PV01 to PV05) are ON or OFF in accordance with
the status data value of the connection destination.
● Action of the Switch Status Input Function

The PBS5C Block references status of terminals connected to input terminals Q01 to Q05
at established scan periods. When the referenced status is 0, a switch turns OFF and the
values of PV01 and PV05 are 0. When it is other than 0, a switch turns ON and the values
are 1.
● Operating Conditions of the Switch Status Input Function

Depending upon the connection status of the I/O terminal and the switch type, data refer-
ence and the switch status (PVnn) determination may or may not be performed.
Table Operating Conditions of the Switch Status Input Function
Not used
Lamp
Connection
Button
Button with lamp
D040804E.EPS
: Performed

The lamp indication function of the Extended 5-Push-Button Switch Block (PBS5C)
changes the indication color of the push button switch and the indication content of its
switch label when the value of each switch status (PV01 to PV05) is changed.
● Action of the Lamp Indication Function

label of the push button switch, which is located on the instrument faceplate of the Ex-
tended 5-Push-Button Switch Block (PBS5C), will change.
The following shows the default set values of each switch indication color and label.
• Label at ON: ON
● Operating Conditions of the Lamp Indication Function

formed.
Table Operating Conditions of the Lamp Indication Function
Indication color
determination
Not used
Lamp
Connection
Button
Button with lamp
D040805E.EPS
: Performed

The button operation function of the Extended 5-Push-Button Switch Block (PBS5C)
changes manipulated command values (MV01 to MV05) when button operation is per-
formed by the operator.
● Action of the Button Operation Function

data is set to manipulated command values (MV01 to MV05) from outside the block, the
manipulated command values (MV01 to MV05) will change. How each value changes
varies depending upon the button operation setting.
When the value of any manipulated command value (MV01 to MV05) is changed, that
manipulated command value (MV01 to MV05) will be set to the connection destination of
the corresponding output connection terminal (B01 to B05). This setting of data to the
connection destination is executed during the first periodic scan following the setting
operation to the data item of the Extended 5-Push-Button Switch Block (PBS5C).
● Operating Conditions of the Button Operation Function

manipulated command value (MVnn) determination and data output may or may not be
performed.
Table Operating Conditions of the Button Operation Function
Manipulated command
value determination
Not used
Lamp
Connection
Button
Button with lamp
D040806E.EPS
: Performed
● Button Action
▼ Button Action
The button action of the Extended 5-Push-Button Switch Block (PBS5C) is set in the
Function Block Detail Builder. Three types of button action are available for selection;
“momentary button,” “alternate button,” and “radio button.” The default is “momentary
button.”
When the “momentary button” is selected, output time span must be set. The output time
span is set in the Function Block Detail Builder.


When a numeric value of 0 or smaller is set as the switch operation disable status
(SWOP[n]), operation is enabled.
When a numeric value of 1 or greater is set as the switch operation disable status
■ Reconfirmation Operation
A dialog box for reconfirming the switch operation is displayed.
In the dialog, an OFF switch label is displayed when the current switch status (PVnn) is ON
and an ON switch label is displayed when the switch status is OFF.

■ Data Items - PBS5C
Table Data Items of Extended 5-Push-Button Switch Block (PBS5C)
Entry Permitted
or Not

characters

AKLB[1] to [5] Reconfirmation label -----
characters
MV01 to MV05 Manipulated command 1 to 5 0/1 0
D040807E.EPS


D4.9 Extended 10-Push-Button Switch Block

(PBS10C)
The Extended 10-Push-Button Switch Block (PBS10C) is a sequence faceplate block
that holds status data of ten push button switches.
■ Extended 10-Push-Button Switch Block (PBS10C) £

Here is a function block diagram of the Extended 10-Push-Button Switch Block (PBS10C).
JMOD MODE
AKLB[1]
JBST BSTS SWOP[1]
JALM ALRM SWST[1]MV
SWCR[1]MV
SVH
Q01 PV01 SWLB[1]
MVSVH MV01 B01
SVL
Q02 PV02 SWLB[2]
SVHSVL MV02 B02
MH
SVLMH
MH
Q10 PV10 SWLB[10] MV10 B10
INT
D040901E.EPS
Figure Function Block Diagram of Extended 10-Push-Button Switch Block (PBS10C) £

The figure below shows an example of the instrument faceplate of the Extended 10-Push-
Button Switch Block (PBS10C) displayed in the operation and monitoring window.
SC200
System B
MAN NR
NR
SW1 OFF P2 STOP
V1 CLOSE SW3 OFF
P1 STOP V3 CLOSE
SW2 OFF P3 STOP
V2 CLOSE SW4 OFF
D040902E.EPS
Figure Display Example of Extended 10-Push-Button Switch Block (PBS10C) £

nals of the Extended 10-Push-Button Switch Block (PBS10C).
Button Switch Block (PBS10C) (1/2) £
Block mode
JMOD
connection
Block status
JBST
connection
Alarm status
JALM
connection
PV01
Q01
connection
PV02
Q02
connection
PV03
Q03
connection
PV04
Q04
connection
PV05
Q05
connection
PV06
Q06
connection
PV07
Q07
connection
PV08
Q08
connection
PV09
Q09
connection
PV10
Q10
connection
Interlock
INT
SW input
D040903E.EPS

Button Switch Block (PBS10C) (2/2) £
MV01
B01
connection
MV02
B02
connection
MV03
B03 connection
MV04
B04
connection
MV05
B05
connection
MV06
B06
connection
MV07
B07
connection
MV08
B08
connection
MV09
B09
connection
MV10
B10
connection
D040904E.EPS
■ Switch Status Input Function £

The switch status input function of the Extended 10-Push-Button Switch Block (PBS10C)
● Action of the Switch Status Input Function £

The PBS10C Block references status of terminals connected to input terminals Q01 to Q10
are 1.

● Operating Conditions of the Switch Status Input Function £
Depending upon the connection status of the I/O terminal and the switch type, data refer-
ence and the switch status (PVnn) determination may or may not be performed.
Table Operating Conditions of Switch Status Input Function £
Switch status
I/O connection Switch type Data reference
determination
No connection —
Not used
Lamp
Connection
Button
Button with lamp
D040905E.EPS
: Performed
■ Lamp Indication Function £

The lamp indication function of the the Extended 10-Push-Button Switch Block (PBS10C)
● Action of Lamp Indication Function £

tended 10-Push-Button Switch Block (PBS10C), will change.
The following shows the default set values of each switch indication color and label.
• Label at ON: ON

● Operating Conditions of Lamp Indication Function £
formed.
Table Operating Conditions of Lamp Indication Function £
Indication color Switch label
I/O connection Switch type
determination determination
No connection —
Not used
Lamp
Connection
Button
Button with lamp
D040906E.EPS
: Performed
■ Button Operation Function £

The button operation function of the Extended 10-Push-Button Switch Block (PBS10C)
● Action of the Button Operation Function £

manipulated command values (MV01 to MV10) will change. How each value changes
varies depending upon the button operation setting.
When the value of any manipulated command value (MV01 to MV10) is changed, that
manipulate command value (MV01 to MV10) will be set to the connection destination of the
corresponding output connection terminal (B01 to B10). This setting of data to the connec-
tion destination is executed during the first periodic scan following the setting operation to
the data item of the Extended 10-Push-Button Switch Block (PBS10C).
● Operating Conditions of the Button Operation Function £

performed.
Table Operating Conditions of the Button Operation Function £
Manipulated
I/O connection Switch type command value Data output
determination
No connection —
Not used
Lamp
Connection
Button
Button with lamp
D040907E.EPS
: Performed

● Button Action £
▼ Button Action
The button action of the Extended 10-Push-Button Switch Block (PBS10C) is set in the
button.”
■ Switch Flashing Function £

■ Switch Operation Disable Function £

When a numeric value 0 or smaller is set as the switch operation disable status (SWOP[n]),
When a numeric value 1 or greater is set as the switch operation disable status (SWOP[n]),
operation is disabled.
■ Reconfirmation Operation £
A dialog box for reconfirming the switch operation is displayed.

■ Data Items - PBS10C £
Table Data Items of Extended 10-Push-Button Switch Block (PBS10C)
Entry Permitted
or Not
MODE Block mode O/S (MAN)
BSTS Block status 0
ALRM Alarm status NR
AFLS Alarm flashing status 0
Alarm detection
AF 0
specification
Alarm masking
AOFS 0
specification
SWCR[10] Switch indication color 0 to 15 7
Equivalent to a string of 8
SWLB[10] Switch label
alphanumeric characters
SWST[10] Switch flashing status 0/1 0
Switch operation disable
SWOP[10] -15 to 15 0
status
Equivalent to a string of 8
AKLB[10] Reconfirmation label
alphanumeric characters
Manipulated command
MV01 to MV10 0/1 0
1 to 10
UAID User application ID 0
D040908E.EPS


<Toc> <Ind> <D4.10 Extended Hybrid Manual Station Block (HAS3C)> D4-57
D4.10 Extended Hybrid Manual Station Block

(HAS3C)
The Extended Hybrid Manual Station Block (HAS3C) is a faceplate block that has a
faceplate block for indication operation and status data for five push button
switches.
■ Extended Hybrid Manual Station Block (HAS3C)

Here is a function block diagram of the Extended Hybrid Manual Station Block (HAS3C).
JMOD MODE
AKLB[1]
JBST BSTS SWOP[1]
JALM ALRM SWST[1]MV
SWCR[1]MV
SVH
Q01 PV01 SWLB[1]
MVSVH MV01 B01
SVL
Q02 PV02 SWLB[2]
SVHSVL MV02 B02
MH
Q03 PV03 SWLB[3]
SVLMH MV03 B03
Q04 PV04 SWLB[4]

MH MV04 B04
Q05 PV05 SWLB[5] MV05 B05
JPV PV
JSV SV
JMV MV
J01 SVH
J02 SVL
J03 MH
J04 ML
INT
D041001E.EPS
Figure Function Block Diagram of Extended Hybrid Manual Station Block (HAS3C)

The figure below shows an example of the instrument faceplate of the Extended Hybrid
Manual Station Block (HAS3C) displayed in the operation and monitoring window.
HA100
System 1
AUT
NR
100.0
SW1A
OFF
80.0
SW1B
OFF
60.0
V1A
CLOSE
40.0
V1B
20.0 CLOSE
P1A
0.0 STOP
D041002E.EPS
Figure Display Example of Extended Hybrid Manual Station Block (HAS3C)

nals of Extended Hybrid Manual Station Block (HAS3C).
Table Connection Types and Connection Destinations of I/O Terminals of Extended Hybrid
Manual Station Block (HAS3C)
Block mode
JMOD
connection
Block status
JBST
connection
Alarm status
JALM
connection
PV01
Q01
connection
PV02
Q02
connection
PV03
Q03
connection
PV04
Q04
connection
PV05
Q05
connection
MV01
B01
connection
MV02
B02
connection
MV03
B03
connection
MV04
B04
connection
MV05
B05
connection
PV
JPV
connection
SV
JSV
connection
MV
JMV
connection
SVH
J01
connection
SVL
J02
connection
MH
J03
connection
ML
J04
connection
Interlock
INT
switch input
D041003E.EPS

▼ MV Display Style, MV Engineering Unit Symbol, MV Range
The Extended Hybrid Manual Station Block (HAS3C) references the analog data at the
held.
D041004E.EPS
Builder.
• MV Display Style: Select from “Automatic determination” or “User Define.”
The default setting is “Automatic determination.”
• MV Range:
value.

When setting operation is performed to any data items of the Extended Hybrid Manual
Station Block (HAS3C), the set data item values will be set to the connection destination of
the corresponding I/O terminals shown below:
J03 Manipulated variable high-limit setpoint (ML)
D041005E.EPS
scan that immediately follows the setting operation to the data item of the Extended Hybrid
Manual Station Block (HAS3C).

The switch status input function of the Extended Hybrid Manual Station Block (HAS3C)
● Action of Switch Status Input

The HAS3C Block references status of terminals connected to input terminals Q01 to Q05
are 1.
● Operating Conditions of Switch Status Input

▼ Switch type
Depending upon the connection status of the I/O terminal and the switch type setting, data
reference and the switch status (PVnn) determination may or may not be performed.
Table Operating Conditions of the Switch Status Input
Not used
Lamp
Connection
Button
Button with lamp
D041006E.EPS
: Performed

The lamp indication function of the Extended Hybrid Manual Station Block (HAS3C)
● Action of Lamp Indication

tended Hybrid Manual Station Block (HAS3C), will change.
The default set values of each switch indication color and label are shown as follows.
• Label at ON: ON
● Operating Conditions of Lamp Indication

formed.
Table Operating Conditions of Switch Indication
Indication color
determination
Not used
Lamp
Connection
Button
Button with lamp
D041007E.EPS
: Performed

The button operation function of the Extended Hybrid Manual Station Block (HAS3C)
● Action of Button Operation

manipulated command values (MV01 to MV05) will change. The value to be set varies
depending upon the button operation setting.
When a value is set to any manipulated command value (MV01 to MV05), the manipulated
command value (MV01 to MV05) is set to the connection destination of the output terminal
(B01 to B05). This setting is executed during the first periodic scan after the switch status
setting.
● Operating Conditions of Button Operation

performed.
Table Operating Conditions of Button Operation
Manipulated command
value determination
Not used
Lamp
Connection
Button
Button with lamp
D041008E.EPS
: Performed
● Button Action
▼ Button Action
The button action of the Extended Hybrid Manual Station Block (HAS3C) is set in the
button.”

The switch flashing function flashes each switch on the instrument faceplate.
When 1 is set to the switch flashing state (SWST[n]), the lamp of the faceplate flashes;
When 0 is set, the lamp turns to the normal state.

When a numeric value of 0 or less is set as the switch operation disable status (SWOP[n]),
When a numeric value of 1 or more is set as the switch operation disable status
■ Reconfirmation Operation
A dialog box for reconfirming the switch is displayed.

■ Data Items - HAS3C
Table Data Items of Extended Hybrid Manual Station Block (HAS3C)
Entry Permitted
or Not
Manipulated variable high-limit
MH MSL to MSH MSH
setpoint
Manipulated variable low-limit
ML MSL to MSH MSL
setpoint

characters

AKLB[1] to [5] Reconfirmation label -----
characters
MV01 to MV05 Manipulated command 1 to 5 0/1 0
D041009E.EPS


<Toc> <Ind> <D5. Sequential Function Chart> D5-1
D5. Sequential Function Chart

The sequential function chart (SFC) is a graphical programming language used to
define control sequences.
SFC can be written using the SFC block, which is a function block included in the
sequence control function.
■ SFC
▼ SFC Block
The SFC language describes a program defining sequential control steps for every group
of processes.
An example of SFC involving three steps, which are initialization, water feed, and heating,
is shown below:
Step
Transition 01 Initialization
Link 02 Water feed
03 Heating
D050001E.EPS
Figure Example of SFC
TIP
SFC is also used in functions other than the SFC block as indicated below, but the SFC specifications for
each of these will vary somewhat.
• Unit instrument
• Operation
SEE ALSO
For more information about unit instruments and operations, see chapter D6, “Unit Supervision.”

● Elements
SFC uses the following three elements to define a sequence:
• Step: Defines the action of a step.
• Transition:Defines the condition of transition to next step.
• Link: Defines connections from step to transition and transition to step.
The flow of SFC processing is in accordance with a step sequence in which the action
defined for each step is sequentially executed from the top. Upon completion of one step,
further processing is determined by the defined transition condition.
SFC can define a selective sequence as well, in which steps are defined in parallel to have
them branched for execution. Interrupt steps, which interrupt a normal process for their
execution, can also be described.
● Architecture of SFC Block

SFC block may be applied to execute the program written in SFC which is one of the FCS
functions.
SFC blocks are usually applied for the comparatively large scale sequence control or
device control system. With the application of SFC, the process management (status
display) becomes convenient.
The following figure gives a draft image of the SFC architecture.
Function block data

SFC
System fixed data item
Mode
Status SEBOL or
Sequence table
User defined data item
D050002E.EPS
Figure Image of SFC Block Architecture

● Describing Step Actions
SEBOL, a sequence table or a logic chart can be used to describe step actions.
An example of SEBOL-written step actions is shown below:
global integer i1, i2, i3

......
V001.MV = CLOSE
01 Initialization ......
......
V001.MV = OPEN
02 Water feed wait until (L001.PV >= 10)
V001.MV = CLOSE
......
03 Heating ......
H001.MV = ON
wait until (T001.PV >= 20)
H001.MV = OFF
......
D050003E.EPS
Figure SFC Block Control Algorithm
Although all step actions are written in SEBOL in the above example, a different manner of
description can be used for each step action according to the disposition of the involved
process.
SEE ALSO
• For the details of SEBOL, see chapter H1, “SEBOL Details.”
• For the details of the sequence table and the logic chart, see chapter D3, “Sequence Control.”

■ SFC Block
SFC-written programs are classified according to their processing types as follows:
• Queue-signal processing:
Processing executed according to the contents of a queue signal in an SFC main
program designed for normal processing.
• Status-change processing:
Interrupt processing executed due to a status change of the SFC block. Different
processing may be executed before and after the status change.
• Interrupt-signal processing:
Interrupt processing executed according the contents of an interrupt signal in an SFC
main program designed for normal processing.
• Error processing:
Interrupt processing executed when error is caused during the execution of the SFC
block.
With the SFC block, a process step which is being executed can be stopped temporarily,
referenced for its step number, or changed.
● Data Items
The SFC block has data items to identify SFC status.
These items are either system-specific predetermined data or user-defined data.
● Block Modes and Status

The SFC block uses the block mode to identify its control status and the block status to
identify the state of operation as follows:
• Block modes: AUT (automatic), SEMI (semi-automatic), O/S (out-of-service).
• Block status: STOP (stopped), RUN (running), PAUS (paused), ABRT (aborted).

<Toc> <Ind> <D5.1 SFC Elements> D5-5
D5.1 SFC Elements

SFC uses “step,” “transition,” and “link” elements in combinations to define a
sequence.
■ Description of SFC Elements

The step and link elements use varied symbols according to their actions. Their details are
shown below:
Table SFC Block Elements
Element Name Symbol
Step
Initial step
Double-Width Step
Step
Initial Double-Width
Step
Interrupt step
Transition Transition
Selective Sequence
Split
Selective Sequence
Join
Loop-Branch
Link Loop-Join
Jump Down Jnn
Jump Up Jnn
Jump To Jnn
Link
D050101E.EPS
SFC defines processes to be executed using these three basic elements in combinations.
Both step and selective sequences can be defined according to the flow of SFC process-
ing. Interrupt steps can also be described to interrupt the normal flow of process.

D5.1.1 Step
There are five elements as step elements. Each step needs to be defined with at-
tributes and action.
■ Step
“Step” is the most basic element for defining SFC processings.
The following five step elements are used:
• Step
• Initial step
• Step with expanded comment
• Initial step with expanded comment
• Interrupt step
Up to 99 steps can be described in one SFC, with attributes and action defined for each
step.
● Step
This is an ordinary step. In an example shown below, the step number is indicated in the
square on the left and a comment identifying the action defined for the step is shown in the
rectangle on the right:
02 Water feed
D050102E.EPS
Figure Example of Step
● Initial Step
This is the step to be executed first. The step number is indicated in the square on the left
and a comment identifying the action defined for the step is shown in the rectangle on the
right. The use of the square and rectangle is the same as the ordinary “step” described
above except that a double square is used instead:
01 Initialization
D050103E.EPS
Figure Example of Initial Step

● Double-Height Step
This element is also for an ordinary step except that a larger rectangle permits to enter
three-times the normal volume of action comment:
02
D050104E.EPS
Figure Example of Double-Height Step
● Initial Double-Height Step

This element is also for an initial step except that a larger rectangle permits to enter three-
times the normal volume of action comment:
01
D050105E.EPS
Figure Example of Initial Double-Height Step
● Interrupt Step
An interrupt step is used to interrupt the execution of the main program and execute an
interrupt program. The interrupt step in the main program specified the destination for the
expansion to an interrupt program.
An example of interrupt steps is shown below:
01
Interrupt step
02 RUN
03 STOP
04 PAUS
D050106E.EPS
Figure Example of Interrupt Step

■ Step Attributes
Attributes such as step type and step number need to be defined for each step.
Each step needs to be defined with attributes such as step type and step number.
The table below lists the step attributes.
Table Step Attributes
Attribute Description
Select one of the following:
• SEBOL step
• SEBOL one-shot execution step (SEBOL one-shot)
Action-describing • Sequence table step (sequence table step)
methods • Sequence table one-shot execution step
(sequence table one-shot)
• Logic chart step (logic chart)
• Logic chart one-shot execution step (logic chart one-shot)
Step number Integer 1 through 99 (*1)
Step comment Character string of up to 16 bytes.
Phase name Character string of up to 16 bytes.
D050107E.EPS
*1: Duplicate numbers must not be assigned.
■ Step Action
Each step is described as an action to execute a processing.
The types of action and the description of each step are shown below:
• Initial step
in SEBOL
• SEBOL step
in SEBOL
• SEBOL one-shot
in SEBOL
• Sequence table one-shot execution step (sequence table step)
in Sequence table
• Sequence table one-shot execution step (sequence table one-shot step)
in Sequence table
• Logic chart step (logic chart) in Logic chart
• Logic chart one-shot execution step (logic chart one-shot) in Logic chart
SEE ALSO
See D5.2, “Action Description Using SEBOL,” D5.3, “Action Description Using Sequence Table,” and
D5.4, “Action Description Using Logic Chart” for the details of action description.

Some steps require the use of parameters to define action as described below:
Table Action Parameters
Step Parameter Action when unspecified
Initial step None -
SEBOL step &
None -
SEBOL oneshot
Sequence table Parameter-storing variable in action column. Ignored (*1)
one-shot
execution step Name of step executed. -
Sequence table Condition testing result-storing variable. Ignored (*2)
one-shot
execution Name of step executed. -
Logic chart step Parameter-storing variable in action column Ignored (*1)
Logic chart
None -
one-shot
D050108E.EPS
*1: The operation & monitoring parameter is ignored.

*2: The condition testing result is ignored.
SEE ALSO
• See D5.3.1, “Step Common Item Description Using the Sequence Table,” for the details of the action sig-
nal parameter and condition testing result for sequence table and sequence table one-shot steps.
• See D5.4.1, “Step Common Item Description Using Logic Chart,” for the details of the action signal pa-
rameter for logic chart steps.
■ Step Status
A step is “active” when it is being executed or “inactive” when it is not yet executed or its
execution is completed.
When step status changes to active, the step action is executed.
Ending of the step action, step status changes to inactive and the step advances to the
next precessing.

D5.1.2 Transition
The transition is an element to evaluate the transition condition to the next step.
■ Transition
The transition is an element used for evaluating the transition condition between steps. The
transition condition must defined with a single logical expression.
The condition is evaluated when the current step is completed and the next step is acti-
vated if the condition is determined to be true.
The transition is denoted by a short horizontal line crossing the vertical link line between
steps.
SFC can describe step sequence transition and selective sequence transition.
● Step Sequence Transition

In step sequence, steps are executed in the programmed order from top to bottom.
When the transition condition of the current step is satisfied, the next step is activated and
the action is executed. If no condition is defined for the transition, the next step is activated
and the step action is executed.
Step sequence is SFC basic action.
06
Transition
07
D050109E.EPS
Figure Example of Step Sequence Transition
SEE ALSO
For details on transition conditions, refer to D5.5, “Transition Conditions.”

● Selective Sequence Transition
In case of a selective sequence with a number of steps defined in parallel, the transition
condition is evaluated for every step from left to right. When the transition condition of the
current step is satisfied, the next step is activated. If no transition condition is defined for
the transition, the next step is activated and the action is executed.
At the moment the action is executed, the selective sequence transition is already com-
pleted.
No other transition conditions are evaluated within the selective sequence during execution
of one step.
05
Transition
06 07 08
D050110E.EPS
Figure Example of Selective Sequence Transition
The transition condition is evaluated once every basic cycle, or once in a few cycles unless
time is allocated to the SFC block specifically for once-per-cycle evaluation.
SEE ALSO
Refer to D5.1.4, “Step & Selective Sequences,” for more information.

D5.1.3 Links
The Links define the order of step execution. The following eight links are available:
• Selective Sequence Split
• Selective Sequence Join
• Loop-Branch
• Loop-Join
• Jump Down
• Jump Up
• Jump To
• Link
These links, except for ordinary “Link,” must be used in the following combinations:
• Selective Sequence Split and Selective Sequence Join
• Loop-Branch and Loop-Join
• Jump Down and Jump To
• Jump Up and Jump To
■ Selective Sequence Split and Selective Sequence Join

These links are used in a selective sequence as shown below:
Selective Sequence Split
Selective Sequence Join

D050111E.EPS
Figure Selective Sequence Split and Selective Sequence Join
Up to a maximum of eight horizontal rows of steps can be defined within a selective se-
quence. The transition of steps in a selective sequence is determined as the steps are
evaluated from left to right. The step located under the transition element is activated if the
transition condition is true.
SEE ALSO
See “■ Selective Sequence” in D5.1.4, “Step & Selective Sequences,” for more information.

■ Loop-Branch and Loop-Join
These links are used to define a loop as shown below.
The step or steps located between Loop-Branch and Loop-Join are repeatedly executed as
long as the transition condition for the loop is true.
Loop-Join
Loop-Branch
D050112E.EPS
Figure Example of Loop-Branch and Loop-Join
■ Jump Down, Jump Up and Jump To

These links are used when the process sequence must forcibly be skipped.
The Jump Down element defines downward skipping and the Jump Up element defines
upward skipping. The Jump To element, which must be used in combination with either one
of the skipping elements, defines the destination of skipping.
The Jump To is executed when the transition condition defined proceeding the Jump Down
or succeeding the Jump Up is true.
Examples of skipping are shown below:
Jump To
J2
Jump Down
J1
J2
Jump Up
Jump To
J1
Example of Jump Down Example of Jump Up
D050113E.EPS
Figure Examples of Jumping
When a new skip label is created, it is automatically numbered adding 1 to the number of
the most recent skip label.

■ Link
The “link” used to connect steps as shown below.
The vertical links for a step with a step, a transition with a step are shown in the following
example.
02
Links
03
D050114E.EPS
Figure Example of Link

D5.1.4 Step & Selective Sequences

SFC can describe step-sequence and selective-sequence as well as interrupt pro-
grams which thrust into those processing steps.
■ Step Sequence
In a step sequence, steps are executed in the programmed order from the top and only one
transition is defined between steps.
An example is shown below:
06 Step
Transition
07 Step
D050115E.EPS
Figure Example of Step Sequence
The defined action is executed when the step is activated. As soon as the action is com-
pleted, the transition condition is evaluated and the successive step is activated when the
condition is true. The successive step will be activated immediately upon completion of the
current step if no transition condition is defined.

■ Selective Sequence
In a selective sequence, one of two to eight steps defined in parallel is executed selectively.
05
Transition
06 07 08
D050116E.EPS
Figure Example of Selective Sequence
The transition condition is evaluated from left to right for every step; and the step for which
the condition is true will be activated, which is defined preceding the step. If no transition
condition is defined, the step will be activated unconditionally.
No other transition conditions are evaluated within the selective sequence during execution
of one step.

■ Interrupt Program
The interrupt program is an SFC program designed to interrupt the main SFC program for
the execution of a non-sequential event. The interrupt program needs to be written for each
non-sequential event and is developed from an interrupt step defined for the event in the
main program.
An example of the interrupt program for pausing (PAUS) developed from an SFC block
containing three interrupt steps is shown below:
Main program
01
Interrupt steps
02 RUN
03 STOP
04 PAUS
Developed
PAUS interrupt program
01
02
D050117E.EPS
Figure Example of Interrupt Program Developed from Interrupt Step

<Toc> <Ind> <D5.2 Action Description Using SEBOL> D5-18
D5.2 Action Description Using SEBOL

The following methods of describing step actions using SEBOL are explained in this
section:
• Step common items
• Initial steps
• SEBOL steps
• SEBOL one-shot steps
■ Using SEBOL
Global and local variables can be used to define steps in the SFC block using SEBOL.
Enabling access to a function block from a SEBOL-written step requires global or local
function-block declaration.
TIP
Parameters cannot be specified when describing action using SEBOL. They can be specified when
describing action using a sequence table, however.

D5.2.1 Step Common Items

Items common to all steps for which SEBOL is used to write actions are as follows:
• SEBOL variables
• Function-block declaration
• Branching range
• “quit” statement
• #define
■ SEBOL Variables
Global and local SEBOL variables can be used in the SFC block when a step is described
using SEBOL. The global variable can be accessed from all the SEBOL-written steps in the
SFC block, while the local variable can be accessed from only one step.
Areas are allocated to both variables and they are initialized to zero when the SFC block is
started.
The areas are released when the SFC block has been executed.
TIP
In the case of a character-string variable, the global or local variable is initialized to a null-length character
string when the SFC block is started.
● Global Variables
Global variables can be accessed from any SEBOL-written step in the SFC block. To use
global variables, they should be specified in the initial step as shown below:
global integer <variable name>[, <variable name>...]

global long <variable name>[, <variable name>...]
global float <variable name>[, <variable name>...]
global double <variable name>[, <variable name>...]
global char*n <variable name>[, <variable name>...]
“n” in “char*n”: 1 through 255.
D050201E.EPS
TIP
Global variables cannot be accessed from any sequence table or logic chart described step.

● Local Variables
Local variables can be accessed only from the steps for which the use of local variables is
declared. To use local variables, they should be specified in the initial step as shown below:
integer <variable name> [, <variable name>...]

long <variable name> [, <variable name>...]
float <variable name> [, <variable name>...]
double <variable name> [, <variable name>...]
char*n <variable name> [, <variable name>...]

D050202E.EPS
The same local variable can be used in different steps under the same variable name, in
which case area is allocated independently for each variable.
If a step is repeatedly executed in a loop, the local variable remains unchanged throughout
the repeated execution.
● Note Points
The same name cannot be assigned to global and local variables. An error is caused if the
two has the same name.

■ Function Block Declaration
The use of a function block can be declared globally or locally. The global declaration
permits access from all SEBOL-written steps, while the local declaration permits access
only from the declared step.
● Global Declaration
A function block can be accessed from any SEBOL-written step when the use of that
function block is globally declared in the initial step as shown below:
• Tag name declaration

global block <block code> <tag name>[, <tag name>...]
• Global generic name

global genname <block code> <global generic name>[, <global generic name>...]
D050203E.EPS
● Local Declaration
A function block can be accessed from just one step when the use of the function block is
locally declared in that step as shown below:

block <block code> <tag name>[, <tag name>...]
• Local generic name

genname <block code> <local generic name>[, <local generic name>...]
D050204E.EPS
● Note Points
• No error occurs when the tag name specified in global declaration is used also in local
declaration; however, an error will occur if different block codes are specified. An error
also occurs if specified global and local generic names are identical.

• Using multiple-project-tag name, the function block data of other projects can be
accessed. Since a multiple-project-tag has an @ mark in its name, it is necessary to
declare an alias for the multiple-project-tag.
Multiple-project-tag is named in the following format
TagName@ProjectID
Up to 16 alphanumeric characters can be used for naming a Multiple-project-tag
including @ mark.
An example of declaring an alias for function block with a multiple-project-tag.
block PID FIC100
block PID TAG001 alias TIC100@P1
FIC100.CSV = TAG001.MV
SEE ALSO
For the details about calling up multiple-project tag name, see “■ Ideatical Tag Names” in M9.2.1,
“Operation and Motoring Multiple Projects”.
■ Branching Range
The destination for branching is restricted to be within the step in which branching is speci-
fied using a “goto” statement, for example. Processing cannot be branched to other steps
using “error” and “errorsub” specifications, “goto” statements, etc.
SEE ALSO
For the details about “error” and “errorsub” specifications, see H1.13, “Error Handling”. For the details
about “goto” statement, see H1.8.7, “goto”.
■ “quit” Statement
The “quit” statement terminates the action being executed.
When this statement is executed as a step action, the transition condition defined succeed-
ing the step will then be evaluated.
■ #define
A name can be defined using “#define” only in the initial step. The defined name can then
be used in all SEBOL-written steps.
SEE ALSO
For the details about “#define”, see “■ #define statement” in H1.1.8,“Substifution of Character String”.

D5.2.2 Initial Step

The following methods of describing the initial step are described in this section:
• Order of description
• Example of description
• Use of “#define”
• Use of “#include”
• Use of “#IMPLICIT”
■ Order of Description
The initial step action should be described in order of global variables, local variables, and
execution statements as shown below; an error will be caused otherwise.
<global variable/global function-block declaration>

<local variable/local function-block declaration>
<action execution statement>
D050205E.EPS
The initial step action can be described using up to 2000 lines. No parameters are used in
describing the action.
The initial step is completed when the last described execution statement or a “quit” state-
ment has been executed.
■ Example of Description
The following is an example of initial-step description:
!global variable declaration
global block TM TM301, TM302
global block SIO-11 VL301, VL302
global integer loop
global char*16 name
!local variable declaration

integer i, j, k
!action execution statement

[ VL301.MODE.MV = "MAN", 0]
.......
quit

■ Use of “#define”
Names can be defined using “#define” anywhere within the initial step.
The defined names can then be used in any SEBOL-written step and transition condition.
SEE ALSO
For the details of “#define”, see “■ #define statement” in H1.1.8, “Substitution of Character String.”
■ Use of “#include”
“#include” can be specified for file-inclusion anywhere within the initial step.
The order of all statements in the included file, however, must be in conformity with that of
the initial step. Otherwise, an error is caused for the statements in the included file.
SEE ALSO
For the details of “#include”, see “■ #include” in H1.1.9, “Include File.”
■ Use of “#IMPLICIT”
A “#IMPLICIT” command can be used in the initial step. The command is then valid within
the entire SFC block.
(This command cannot be entered in any other steps.)
SEE ALSO
For the details of “#IMPLICIT”, see “■ #IMPLICIT Instruction” in H1.1.7, “Implicit Declarations of Vari-
ables.”

D5.2.3 SEBOL Steps

The following items as to describing SEBOL steps are explained in this section:
• Restrictions
The SEBOL step action should be described in order of variables and execution statements
as shown below; an error will be caused otherwise.

D050206E.EPS
The SEBOL step action can be described using up to 2000 lines. No parameters are used
in describing the action.
The step is completed when the last described execution statement or a “quit” statement
has been executed.
The following is an example of SEBOL-step description:
block PVI LI303
integer ierr

wait until (LI303.PV >= 10.0) ; ierr
.......
■ Note Points
#define, #include, and #IMPLICIT command cannot be used with SEBOL steps. These
commands can be used only by the initial step. However, the name defined by means of
“#define” in the initial step can be used.

D5.2.4 SEBOL One-Shot Steps

The following items as to describing SEBOL oneshot steps are explained in this
section:
• Execution
• Restrictions
The SEBOL oneshot-step action should be described in order of variables and execution
statements as shown below; an error will be caused otherwise.

D050207E.EPS
No parameters are used in describing the action. The step is completed when the last
described execution statement or a “quit” statement has been executed.
The following is an example of SEBOL oneshot-step description:
block %SW SW301, SW302

SW301.PV = 1
SW302.PV = 1
quit
■ Execution
The SEBOL oneshot-step action will be executed without any break once it is activated. Its
processing time will not be shared by any other SFC program. No interrupt signals nor
status change instructions are allowed to interrupt the execution until it is completed.

■ Note Points
The SEBOL oneshot-step action can be continuously executed up to 20 lines. If a “for”
statement is used, for example, and one line is repeatedly executed, each repetition is
counted as one line. If execution is attempted exceeding 20 lines, an execution error is
caused and the successive action will be executed not as oneshot but normal step action.
The following statements should not be used in order to avoid any execution error:
• Statement for accessing function-block data at another control station.
• “signal” statement for sending signals to another control station.
• “qsigcancel” and “qsigmove” statements for manipulating an SFC block at another
control station.
Also the following statements should not be used in order to avoid any error:
• “drive” statement, “seqstable” and “logicchart” statements with “drivewait” specifica-
tion.
• “wend,” “until,” and “next” statements without “@.”
• “wait until,” “delay,” and “delaycycle” statements.
• “dialogue” statement.
• “nopreempt begin” and “nopreempt end” statements.
• “semlock wait” statement.
• “wait for qsignal” statement.
• “ssdtwrite” and “ssdtwritebit” statements.
#define, #include, and #IMPLICIT command cannot be used with SEBOL oneshot steps.
These commands can be used only by the initial step. However, the name defined by
means of “#define” in the initial step can be used.

<Toc> <Ind> <D5.3 Action Description Using Sequence Table> D5-28
D5.3 Action Description Using Sequence Table

The following items as to describing step actions using a sequence table are ex-
plained in this section.
• Step common items using the sequence table
• Sequence table (ST) steps
• Sequence table (ST) one-shot steps
■ Using the Sequence Table

When using a sequence table to describe a step, the sequence table block needs to be
assigned with a tag name.
The sequence table needs a step name as the action parameter and the name of a vari-
able to store the action-signal column parameter.
The sequence table one-shot step needs a step name as the action parameter and the
name of a variable to store condition testing result.

D5.3.1 Step Common Item Description Using the Sequence Table

Items common to all sequence table steps are as follows:
• Tag name
• Step name
• Variable to store action-signal column parameter or sequence table-condition
testing result
■ Tag Name
The sequence table needs to be tagged so that its tangle can be used as the step name.
The specified sequence table can be shared by different steps.
The tag names that can be specified for the step execution name are only the sequence
tables in the same control station.
■ Step Name
The step name can be specified for the sequence table step as described below:
Table Step Name Specification
Specification Action
No specification (default) The first step is executed.
An execution step name
The specified step is executed.
specified using up to 2 characters.
Continuation is specified. The current step is executed (*1)
D050301E.EPS
*1: The current step is retained in sequence table data item PV.
In the case of sequence table one-shot steps, the specified step and step 00 are oneshot-
executed.
In the case of sequence table steps, the sequence table is periodically executed at its own
timing after the specified step and step 00 have been oneshot-executed. Step 00 is ex-
ecuted in every scan period. Specifying a step name for a non-step sequence table is
ignored.
SEE ALSO
See D3.2, “Sequence Table Block (ST16, ST16E),” for the details of sequence tables.

■ Specified Variable to Store Action-signal Column Parameter or
Condition Testing Result
In the case of sequence table step or sequence table one-shot step, a variable to store the
parameter for the action signal of SFC/SEBOL return event message (%RE) or condition
testing result may be specified in the action signal column. When sequence table step or
sequence table one-shot step is executed, the “parameter in action signal column” and the
“condition testing result” will be stored in the specified variable. Both “parameter in action
signal column” and the “condition testing result” are Long type data.
Which one will be stored in the variable depends on the step types, shown as below.
Table Representation of the Variable
Step Parameter in Action-signal column Condition testing result
Sequence table step
Sequence table

one-shot step
D050302E.EPS
: Stored.
Blank: Not stored.
These variables will be ignored if their names are not specified in step action.
● Action-Signal Column Parameter

This parameter for the SFC/SEBOL return even message (%RE), which is an output of
software I/O messages, is stored in the specified variable using 0 through 65535 defined in
the action-signal column of the sequence table.
● Sequence Table Condition Testing Result

This is a result of condition testing the sequence table, which is either true (1) or false (0).
• In the case of a non-step sequence table, the result is true if at least one of 32 rules is
satisfied and false if none is satisfied.
• In the case of a step sequence table, all the rules for the specified step and step 00
are evaluated. Then the result is true if at least one rule is satisfied and false if none is
satisfied.

● Variable Name
The names of both variables can be specified in one of the following four different manners:
• Present SFC-block data item
When storing data as a data item in the present SFC block, specify the variable name
as follows:
%.<data item>
• Global variable
When storing data in a global variable, specify the name of the simple variable de-
clared using “global long” in the initial step.
• Tag name-specified function-block data item
When storing data as a data item in the tag name-specified function block, specify the
variable name as follows:
<tag name>.<data item>
In this case, the tag name should have been declared using “global long” in the initial
step. When storing the condition testing result for an ST oneshot step, the tag name
must be present within the same control station as the SFC block; specifying a tag
name from another control station causes error when the SFC block is executed.
• Global generic name-specified function-block data item
When storing data as a data item in the global generic name-specified function block,
specify the variable name as follows:
<global variable>.<data item>
The global generic name, which must be a simple variable, should be declared using
“global block” in the initial step. When storing the condition testing result for an se-
quence table oneshot step, the tag name present within the same control station as
the SFC block must be assigned to the global generic name using the “assign” state-
ment.
SEE ALSO
See D3.2, “Sequence Table Block (ST16, ST16E),” for the details of sequence tables.

D5.3.2 Sequence Table Steps

The following items as to describing sequence table steps are explained in this
section.
• Step action description
• Step execution
■ Step Action Description

The sequence table step action is described using a periodic start sequence table (TE or
TC).
■ Step Execution
The sequence table step is oneshot-executed when its action is activated, and the se-
quence table block mode changes to AUT at the same time. The sequence table will then
be periodically executed according to its own action timing.
The sequence table step action is terminated when an SFC/SEBOL return event message
(%RE) is received from the sequence table. The sequence table block mode then changes
from AUT to MAN.

D5.3.3 Sequence Table One-Shot Steps

The following methods of describing sequence table one-shot steps is explained in
this section.
• Step execution

The sequence table one-shot step is described using a non-step sequence table (OE or
OC).
■ Step Execution
The sequence table one-shot step is oneshot-executed when its action is activated. The
sequence table block mode remains unchanged.

<Toc> <Ind> <D5.4 Action Description Using Logic Chart> D5-34
D5.4 Action Description Using Logic Chart

The following methods of describing step actions using logic chart are explained in
this section.
• Step common items using logic chart
• Logic chart steps
• Logic chart one-shot execution steps
■ Using Logic Chart

To describe steps using logic charts, tag names of logic chart blocks must be specified. At
logic chart steps, variable names to store action signal column parameters can be specified
as parameters for action.

D5.4.1 Step Common Item Description Using Logic Chart

Items common to all logic chart steps are as follows:
• Tag name
• Variable to store action signal column parameters
■ Tag Name
The logic chart needs to be tagged so that its tangle can be used as the step name.
The specified logic chart can be shared by different steps.
The tag names that can be specified for the step execution name are only the logic chart in
the same control station.

■ Specified Variable to Store Action-Signal Column
In the case of logic chart step, a variable to store the parameter for the action signal of
SFC/SEBOL return event message (%RE) may be specified in the action signal column.
When logic chart step is executed, the “parameter in action signal column” will be stored in
the specified variable. “Parameter in action signal column” is Long type data.
The variable will be ignored if the name is not specified in step action.
● Action-Signal Column Parameter

This parameter for the SFC/SEBOL return even message (%RE), which is an output of
software I/O messages, is stored in the specified variable using 0 through 65535 defined in
the action-signal column of the sequence table.

● Variable Name
• Present SFC-block data item
When storing data as a data item in the present SFC block, specify the variable name
as follows:
%.<data item>
• Global variable
<global variable>
step.
“global block” in the initial step.
SEE ALSO
See D3.3, “Logic Chart Block (LC64),” for the details of logic chart.

D5.4.2 Logic Chart Steps

The following items as to describing logic chart steps are explained in this section.
• Step execution

The logic chart step action is described using a periodic start logic chart (TE or TC).
■ Step Execution
The logic chart step is one-shot-executed when its step is activated, and the logic chart
block mode changes to AUT at the same time. The sequence table will then be periodically
executed according to its own action timing.
The logic chart step action is terminated when an SFC/SEBOL return event message is
received from the logic chart. The logic chart block mode then changes from AUT to MAN.

D5.4.3 Logic Chart One-Shot Steps

The following method of describing logic chart one-shot steps is explained in this
section.
• Step execution
■ Step Execution
The logic chart one-shot step is one-shot-executed when the step is activated. The logic
chart block mode remains unchanged.

<Toc> <Ind> <D5.5 Transition Conditions> D5-40
D5.5 Transition Conditions

The following methods as to describing transition conditions are explained in this
section:
• Description of transition conditions
• Variables applicable to transition conditions
■ Description
Conditional expressions is SEBOL statement are used to define conditions for the transi-
tion of steps.
The same manner of describing the transition condition applies to all types of steps.
The condition is satisfied when the result of the conditional expression is not zero and not
satisfied when it is zero. When equivalence operators (==, <>) or relational operators (>=,
<=, >, <) are used, the condition is satisfied when the relation is true (1) and not satisfied
when it is false (0).
For a selective sequence, up to eight transition conditions can be defined. It is not neces-
sary to describe transition condition if step transition is unconditional.

<Toc> <Ind> <D5.5 Transition Conditions> D5-41
■ Variables
The following variables can be used in the conditional expressions for transition:
Table Variables Applicable to Conditional Expressions
Variable Remarks
Constant -
Global variable -
Local variable Declared in step action.
Global tag name Tag name declared using “global block.”
Tag name declared using “block” in SEBOL-step action.
Tag name Sequence table tag name in sequence table step action.
Logic chart tag name in logic chart step action.
Global generic name Generic name declared using “global genname.”
Local generic name Declared using “genname” in step action.
Declared using “global unit genname,” or declared using
Unit generic name
“unit genname” in step action.
Replaced by tag name of action-written sequence
%$
table/logic chart.
D050501E.EPS
• Global variables, step local variables, and constants can be used in array subscript
expressions for array-element variables.
• SEBOL built-in functions can be used in conditional expressions.
• “%$” entered in transition condition is replaced by the tag name of the sequence table/
logic chart which defines action. The conditional expression %$.MODE=“AUT” will be
changed to ST0101.MODE=“AUT” if the sequence table tag name is ST0101, for
example.
• If the sequence table/logic chart is specified using a unit generic name, “%$” cannot
be replaced by the generic name. The generic name must be written in the conditional
expression in this case.

<Toc> <Ind> <D5.6 SFC Block Action> D5-42
D5.6 SFC Block Action

The SFC block is designed to execute SFC-written programs.
■ SFC Programs
An SFC program that executes normal processing is the main program and an SFC pro-
gram that interrupts the main program for execution is the interrupt program.
SFC-written programs are classified according to their function and behavior.
● Main Programs
• Queue signal processing
This process is executed according to the queue signal contents in the SFC main
program, which executes normal processing.
• Exit of the SFC block
• Pause of the SFC block
• Reference of the current step.
• Change of the step to be executed
• Alarm processing of the SFC block
● Interrupt Programs
• Status change
This program is run together with SFC block status change. Separated programs
before/after status changes may be implemented.
• Interrupt signal
Interrupt signal interrupts the SFC main program to run the programs requested by
the interrupt signal.
• Error processing
Error occurrence when SFC block is running may trigger an interrupt program for error
processing.

■ SFC Block Online Maintenance
When part of system is added or modified while the system is running, online maintenance
is required so as to update the database.
■ SFC Block Execution Timing

When all the basic control functions are executed, the SFC block is executed using the idle
time left.
■ SFC Block Data Items

SFC blocks have fixed data items as well as user-definable data items.
■ SFC Block Status

SFC block running state can be indicated by block mode and block status.

■ Interrupt Programs
Interrupt programs must be described separately for every different purpose.
When the block status has been changed and if it is necessary to pause or terminate the
process, an interrupt program or programs can be executed as required. For example, the
heater needs to be stopped if the process is to be terminated during heating, or the valve
needs to be closed if the process is to be paused during tank charging.
An example of executing an interrupt program for pausing from the main program, which
contains SIGNAL 1, RUN, STOP, and PAUS interrupt steps is shown below:
Main program
Interrupt steps
01 SIGNAL 1
02 RUN
03 STOP
04 PAUS
Developed
PAUS interrupt program
01
02
D050601E.EPS
Figure Example of Interrupt Program Execution
Although the first step of the interrupt program is shown in a double square in the above
example, it does not mean that the step is the initial step.
Global variables cannot be declared using “global integer” nor “global block” for the first
step of an interrupt program. They can be read or written, however.

■ Interrupt Program Types of Processing
Interrupt programs can be used for the following processing:
• Status change pre-processing
• Status change post-processing
• Interrupt signal processing
The following steps can be used in these interrupt programs as well as the main program:
Table Steps Applicable to SFC Programs
Program
Step Main Status change Status change Interrupt signal Error
program pre-processing post-processing processing processing
Initial step
SEBOL step
SEBOL one-shot step
Sequence table step
Sequence table

one-shot step
Logic chart step
Logic chart

one-shot step
Interrupt step
D050602E.EPS
Note: Transition can be defined for programs other than the status change pre-processing program.
: Applicable
Blank: Not applicable

■ Interrupt Program Parameters
Parameters must be specified according to the type of interrupt processing.
● For Status Change Pre-processing & Post-processing

One of the following parameters needs to be specified according to which status change
instruction is to be executed:
• RUN
Starts the SFC block or restarts the paused SFC block.
• STOP
Terminates the SFC block being executed.
• PAUS
Pauses the SFC block being executed.
SEE ALSO
See D5.6.2, “Status Change Processing,” for more information.
● For Interrupt Signal Processing

The name of the signal needs to be specified to execute the interrupt program.
SEE ALSO
See D5.6.3, “Interrupt Signal Processing,” for more information.
● For Error Processing

No parameter can be specified for error processing.
SEE ALSO
See D5.6.4, “Error Processing,” for more information.

D5.6.1 Queue Signal Processing

Queue signals are processed in the SFC main program.
■ Signal Declaration
Queue signals to be sent to the SFC block must be so declared in the initial step using the
“queue signal” statement.
queue signal<signal name>[,<signal name>…]

<signal name> a character string constant using up to 8 bytes.
D050603E.EPS
• The signal is ignored and error is returned to the source if an undeclared signal or any
non-defined interrupt signal is received.
• The “queue signal” statement can be used wherever declaration is allowed in the
initial step (global and local variable declarations).
• The “queue signal” statement cannot be used in steps other than the initial step.
• An error is caused if the same signal name is declared in duplication.
• An error is also caused if the same signal name as an interrupt signal name is de-
clared.
The following is an example of queue signal declaration:

queue signal "SG1,""SG2"

■ Signal Processing
The SFC block fetches the first signal in the queue to process the signal in the main pro-
gram.
When the SFC block in the RUN or PAUS status receives a queue signal, it is stored in the
signal queue. If the block is in a status other than RUN and PAUS, the received signal is
ignored and error is returned to the signal source.
The SFC block signal queue may be cancelled as required.
Queue signals are transmitted using the “signal” statement and pending signals can be
manipulated using “qsigcancel” and “qsigmove” statements.
SEE ALSO
• For the details about queue signal transmission, see H1.12.1, “Signal Transmission Processing.”
• For the details about pending signal manipulation, see H1.12.2, “Processing of Queue Signal.”

■ Fetching Queue Signals
▼ Maximum Number of Queue Signal Parameters, Maximum Number of Acceptable Queue Signal
Parameters
The first signal in the queue is fetched for processing when the “wait for qsignal” statement
(see below) is executed in the SFC block.
• Format used to wait for signal-receiving only:

wait for qsignal<signal name-storing variable>
• Format used to wait for signal-receiving or until the expressed condition is satisfied:
wait for qsignal<signal name-storing variable>(<expression>)
[;<error variable>][; error <label>[,<error identifier>]]
errorsub
<signal name-storing variable>: Character-string local variable to store received
signal names.
<error variable>: Local variable for code-setting when error is caused
(0 when no error is caused).
<label>: Branching destination when error is caused.

<error identifier>: Local variable or constant to identify error-caused
location in the error handling phase.
D050604E.EPS
The maximum number of received signal parameters can be specified in a range of 2 to 8

(2 at default) for the parameter attached to a queue signal on the Function Block Detail
Builder. Any signal received exceeding the specified number will be ignored, causing an
error.
The maximum number of signals received in the queue can be specified in a range of 0 to
99 (5 at default) on the Function Block Detail Builder. No additional signals can be received
exceeding the specified number. Any signal transmitted when the queue is full, an error will
be returned to the signal source.
The signal fetched used “wait for qsignal” statement from the queue and being processed
is included in the count of the specified maximum number of signals. The processed signal
will be dequeued when the next signal is fetched used wait for “qsignal” statement.

● Format-1 “wait for qsignal” Statement
This format is used to wait until a queue signal is received. If no signal is in the queue when
the “wait for qsignal” statement in this format is executed, the SFC block waits until a signal
is received while the queue is checked for any received signal once every scan period of
the block at most.
As soon as a signal is received and fetched from the queue for processing, the name of the
signal is stored in the specified variable.
TIP
• Status change pre-processing or post-processing, or interrupt signal processing will be executed
while the waiting for the receiving of queue signals.
• If time cannot be shared sufficiently for the once-every-scan-period check for received signals, the
check will be made no more than once every few scan periods.
● Format-2 “wait for qsignal” Statement

This format is used to wait until a queue signal is received or the condition specified by the
expression is satisfied.
The expression is first calculated when the “wait for qsignal” statement in this format is
executed. If the result is true (other than 0), the condition is satisfied and the statement is
closed. If the result is false (0), the presence of signals in the queue is checked.
When the statement is closed with the condition satisfied, a null-length character string (“”)
is stored in the signal name-storing variable. When a signal has been fetched from the
queue, the name of the signal is stored in the variable. When the result of the expression is
false and no signal is in the queue, both the expression and the queue will be checked
once every scan period of the block at most.
<label> can be used to specify the destination for branching when error is caused. If “error”
or “errorsub” is not used, execution is resumed from the next statement when error is
detected.
Specifying <error identifier> permits to identify the error-caused location in the error han-
dling phase, which provides the identifier value using a built-in function.
TIP
It is recommended to use just one “wait for qsignal” statement, in either one of the two formats, in the SFC
block, and program so that execution returns to the statement for successive signal processing upon
completion of the current signal processing.
SEE ALSO
See H1.13, “Error Handling,” for the details of error processing.

■ Fetching Signal Parameters
Upon completion of the “wait for qsignal” statement with a signal fetched from the queue,
the parameter and name of that signal can be read.
Built-in function “creadpara,” “lreadpara,” or “dreadpara” is used to read the signal param-
eter; and built-in function “creadpara” is used to read the signal name.
creadpara(<parameter number>)
lreadpara(<parameter number>)
dreadpara(<parameter number>)
<parameter number> : 1 to 8(integer constant or variable),

0 for “dreadpara” reads the signal name.
D050605E.EPS
“creadpara” is a character-string function, “lreadpara” is a long integer function, and

“dreadpara” is a long double-precision floating-point real-number function, and they are
used to read character-string, integer, and real-number signal parameters respectively.
Using any of these built-in functions after the expressed condition is the format-2 “wait for
qsignal” statement has been satisfied will cause error when executed.

■ Examples of Queue Signal Processing
Examples of queue signal processing using the two formats of the “wait for qsignal” state-
ment are shown below.
● Waiting for Signal-Receiving Only

An example of executing the format-1 “wait for qsignal” statement:
......
01 Initial step queue signal "SG1" "SG2"
......
char*16 signame
J01
wait for qsignal signame
02 Waiting for signal
! Signal name set at signame.
......
signame == "SG1" signame == "SG2"
03 "SG1" process 1 05 "SG2" process 1
J01 J01
D050606E.EPS
Figure Example of Queue Signal Processing Using Format-1 Statement
The “wait for qsignal” statement is executed in step 2 and a signal is fetched from the
queue. The signal name is then evaluated according to the transition condition defined
following step 2, selecting either SG1 or SG2 for processing.

● Waiting for Signal-Receiving or Satisfied Condition
An example of executing the format-2 “wait for qsignal” statement:
......
......
char*16 signame
J01
wait for qsignal signame (<expression>)
......
signame == "" signame == "SG1" signame == "SG2"

Process when
03 <expression> is 04 "SG1" process 1 06 "SG2" process 1
satisfied
J01 J01 J01

D050607E.EPS
Figure Example of Queue Signal Processing Using Format-2 Statement
The “wait for qsignal” statement is executed in step 2, determining to wait for a signal or to
calculate the expression. The result of the expression is checked for the first transition
condition defined following Step 2. Either SG1 or SG2 is selected for processing according
to the other two transition conditions.

■ Referencing
▼ Reference Signal Parameter Numbers
User-defined data item QUEUE is used to reference the queue of signals. QUEUE is
defined as a one-dimensional CHR16 character-string array and each of its elements can
be accessed as a char*16 character string in SEBOL. The name of the signal stored in the
queue or one of signal parameters is set at a QUEUE element. The data of signals pending
to be processed are set in the QUEUE array but the data of the signal being processed is
not.
● QUEUE Definition
Data item QUEUE can be defined for the purpose of referencing the queue of signals as
follows:
• Define a CHR16 one-dimensional array named QUEUE. No data type other than
character strings nor simple variables cannot be used.
• Specify 1 to 32 array elements. Any elements specified exceeding 32 are ignored.
• Do not define QUEUE if there is no need for referencing the queue of signals.
Use the Function Block Detail Builder to specify the use of signal names and parameter
numbers for QUEUE array elements. The parameter numbers specified are then used as
reference signal parameter numbers. The signal name is set if the reference signal param-
eter number is 0; if the number is 1 to 8, the signal parameter of that number is set at the
QUEUE element. When numeric signal parameters are used, they are converted to char-
acter strings and set at QUEUE elements starting from the first element.

● Example of Referencing
When the queue has four signals, for example, referencing can be made as described
below:
SG1 SG2 SG2 SG1
SUMMER AUTUMN WINTER SPRING

*1 *1 *1 *1
*1: The first parameter

D050608E.EPS
Figure Queue Holding Four Signals
If the reference signal parameter number is 1, the contents of QUEUE array elements are
as follows:
Queue[1] = "SUMMER"
Queue[2] = "AUTUMN"
Queue[3] = "WINTER"
Queue[4] = "SPRING"
Queue[5] = " "
.....
Queue[10] = " "
QUEUE[5] to QUEUE[10] are null-length character strings since there are no signals.

D5.6.2 Status Change Processing

There are following two types of the interrupt processes executed with a block
status change command:
• Status-change pre-processing
• Status-change post-processing
■ Processing Flow - SFC

The flow of processing when the SFC block receives a status change command is shown
below:
Status change command received
No
Is the command viable?
Yes
Executed as the
Status-change pre-process command is received.
No
Is the change feasible?
Yes
Status change executed
Status-change post-process
End
D050609E.EPS
Figure Flow of Status Change Process
As the SFC block receives a status change command, the feasibility of the commanded
change and the interrupt processes are checked in relation to the current status. The
conditions for block status changes are shown below:
Table Feasibility of Block Status Change
Status commanded for change
Current status
STOP RUN PAUS RSET ABRT
STOP (*1)
RUN (*1)
PAUS (*1)
ABRT (*1)
D050610E.EPS
: Status change feasible. Both pre- & post-processes executable.

: Status change feasible, but pre- & post-processes not executable.
Blank: Status change not feasible.
*1: Command ignored.

● Feasibility Checking
The command to change the current block status of STOP to RUN or PAUS is executed,
interrupting the main program to start the pre-process; a change to RSET, ABRT, or STOP
causes error. A change to RSET is accepted only when the current status is ABRT.
A change to ABRT is accepted when the current status is RUN or PAUS. When the com-
mand to change the current status to ABRT is received, the SFC block is forcibly termi-
nated and the status is changed to ABRT; the pre-process is executed when feasible.
IMPORTANT
The command to change the status to ABRT is a command to forcibly terminate the SFC
block and should not be used during normal operation. It may be used if the SFC block is
locked due to application error causing infinite looping during status-change post-process-
ing, and so forth.
The change-to-ABRT command is different from other status change commands as fol-
lows:
• Pre- and post-processing cannot be defined for the command.
• The command can be received even while another status change command is being
post-processed.
● Pre-Processing
The feasibility of status change is determined in the pre-process. If the change is denied,
the source of the command is notified of the error. The status is changed as commanded if
the pre-process is not defined.
● Status Changing
The status of the SFC block is changed as commanded when the change is justified both in
the initial check in relation to the current status and the check performed in pre-processing.
● Post-Processing
Status-change post-processing is executed in accordance with the execution of the SFC
block itself, not with the receiving of the status change command.
Any additional status change command is prohibited until the current post-process is
completed; the command will be ignored if received, causing error.

■ Status-Change Pre-Process - SFC
The status-change pre-process is one-shot-executed upon receipt of the status change
command before changing the block status. There are three steps to describe status-
change pre-process.
• Sequence table one-shot execution step (Sequence table one-shot)
• Logic chart one-shot execution step (Logic chart one-shot)
Since the status-change pre-process is one-shot-executed, it must be completed as quickly

as possible. Do not access data of another control station and delay the process. Only one
step can be executed as pre-process, where no transition condition can be defined.
STOP
01 Pre-process
D050611E.EPS
Figure Status-Change Pre-Process
At the SEBOL and sequence table one-shot steps, the feasibility of status change can be
determined. With the logic chart one-shot step, the status can be changed. If the pre-
process is not defined, the status can also be changed. At the pre-process, the status and
mode of the pre-process-described SFC block or other SFC blocks cannot be changed.

● Pre-Processing Using SEBOL Oneshot Step
The SEBOL oneshot step is completed when the last line, or “return” or “quit” statement
has been executed.
If the last line or “quit” statement has been executed, the feasibility of status change is
justified. If the “return” statement has been executed, the feasibility of status change is
determined according to the returned value as follows:
return[<status change feasibility>]
<status change feasibility>: Integer constant or numerical expression.

==0: Change denied.
<>0: Change justified.
Omitted: Change justified.
D050612E.EPS
The SEBOL oneshot step in which the pre-process is defined has the following additional
restrictions over the normal steps:
• “exit” statement cannot be used. Error is caused if used.
• “signal” statement cannot be used. Error is caused if used.
• “qsigcancel” and “qsigmove” statements cannot be used. Error is caused if used.
• “isigmask” and “isigunmask” statements cannot be used. Error is caused if used.
• “semlock”: and “semunlock” statements cannot be used. Error is caused if used.
• In the case of fatal error, only a SEBOL error message is output and the SFC block is
not terminated. Any status change will be denied.
• When an execution error is detected, no branching is made to common error process-
ing and a SEBOL error message is output. Any status change will be denied.
• The block status and mode of the present SFC block or any other SFC block cannot
be changed.

● Pre-Processing Using Sequence Table One-Shot Step
In the sequence table one-shot step, the feasibility of status change is determined accord-
ing to the result of sequence-table evaluation. The status change is justified when the result
is true (1) and denied if false (0).
• Non-step sequence table:
The condition testing result is true (1) when at least one of 32 rules is satisfied and
false (0) if none of them is satisfied.
• Step sequence table:
All rules of the oneshot-executed step and step 00 are evaluated and the result is true
(1) when at least one of the rules is satisfied and false (0) if none of them is satisfied.
In the pre-process, no variable can be specified to receive the condition testing result, any
specified variable is ignored. The block status and mode cannot be changed in pre-pro-
cessing for the SFC block in which the pre-process is defined or for any other SFC block.
● Pre-Processing Using Logic Chart One-Shot Step

With the logic chart one-shot step, the status can be changed. At the pre-processing, the
status of the pre-process-described SFC block or other SFC blocks cannot be changed.

■ Status-Change Post-Process - SFC
The status-change post-process is executed after the status has been changed. The
process is executed as an interrupt signal processing, interrupting the main program in
accordance with the basic scan period of the SFC block.
Both step and selective sequences can be used in the post-process. Any additional status
change command is prohibited until the current post-process is completed; the command
will be ignored if received, causing error.
IMPORTANT
The post-process should not be kept suspended by means of a selective sequence transi-
tion condition, or a “wait until,” “compare,” or “dialogue” statement. If the process is sus-
pended, the block status cannot then be changed unless the program is forcibly terminated
using a command to change to ABRT.
The execution of the post-process defined in a SEBOL step can be controlled using “quit”
and “return” statements:
• Using “quit” statement
Executing this statement in a step sequence terminates the current action and ex-
ecutes the next step. Executing it in a selective sequence starts evaluation of transi-
tion conditions. Executing the statement in the last post-process step terminates the
process.
• Using “return” statement
Executing this statement terminates the post-process without executing the remaining
steps. Any operand specified in this statement will be ignored.

■ Referencing Block Status - SFC
Data item PREBSTS (previous block status) is used in the post-process to permit referenc-
ing the block status before the change. When the status is changed, data item BSTS (block
status) which contains information on the status before the change is copied to PREBSTS.
These two data items are operated as follows:
1. The BSTS data is copied to PREBSTS.
2. BSTS is changed to the new block status.
The BSTS data is referenced to justify the change of block status for the pre-process. The
PREBSTS data is referenced to justify the status change for the post-process. Two cases
of referencing BSTS and PREBSTS are shown below:
• In the first case, the current status of RUN is changed to STOP as commanded.
• In the second case, the current status of PAUS is changed to STOP as commanded.
Table BSTS & PREBSTS

RUN ➝ STOP PAUS ➝ STOP
Process being executed
BSTS PREBSTS BSTS PREBSTS
Status-change pre-process RUN (*1) PAUS (*1)
Status-change
STOP RUN STOP PAUS
post-process
D050613E.EPS
*1: Status before changing to the commanded status.

● Block Status Referencing in Pre-Process
An example of referencing the block status in the pre-process using the two cases de-
scribed above:
switch (%.BSTS)
case "RUN":
!Process changing from RUN to STOP.
case "PAUS"
!Process changing from PAUS to STOP.
end switch
● Block Status Referencing in Post-Process

An example of referencing the block status in the post-process using the two cases de-
scribed above:
switch (%.PREBSTS)
case "RUN"
!Process when changed from RUN to STOP.
case "PAUS"
!Process when changed from PAUS to STOP.
end switch

D5.6.3 Interrupt Signal Processing

Interrupt signal processing is executed interrupting the main program when an
interrupt signal is received.
■ Interrupt Signals - SFC

Interrupt signals are sent from the SFC block, sequence table and logic chart. Every inter-
rupt signal can be named using a character string of up to 8 bytes and attached with up to 8
parameters.
Whether a signal is taken as a queue signal or an interrupt signal depends on the definition
in the SFC block which receives the signal and cannot be specified at the signal source.
Queue and interrupt signals are distinguished as follows:
• Signals defined in the initial step using the “queue signal” statement are handled as
queue signals.
• Signals having their names written at the entrance of interrupt signal processing are
handled as interrupt signals.
If the same name is used both in the initial-step definition and at the interrupt-signal en-
trance, an error is caused.
Interrupt signals can be received only when the SFC block is in the RUN or PAUS status,
any signal transmitted is ignored otherwise and an error is returned to the source.
Interrupt signals received during the course of the PAUS status are stored in a queue and
will be processed when the status is changed to RUN restarting the block.

■ Interrupt Signal Processing - SFC
▼ Maximum Number of Receive Interrupt Signals
Interrupt signals are processed interrupting the main program, which resumes execution as
soon as the signal has been processed.
Main program Interrupt signal processing
Interrupt signal received
D050616E.EPS
Figure Interrupt Signal Processing
Interrupt signals can be processed only when the SFC block is in the RUN status. The
signal processing is canceled if the status is changed to PAUS during the processing and
will not be resumed when the status is returned to RUN.
If another interrupt signal is received while one is being processed, the received signal is
queued and will be processed as soon as the current processing is completed. The maxi-
mum number of interrupt signals which can be queued can be defined for each SFC block
using the Function Block Detail Builder. The number is 5 at default and can be defined up to
99. The defined capacity includes the signal currently being processed. If a signal is re-
ceived when the queue is full, the signal is ignored causing an error.
The execution of the interrupt signal process defined in a SEBOL step can be controlled
using “quit” and “return” statements:
Executing this statement terminates the current step action and executes the next
step. Executing it in a selective sequence starts evaluation of transition conditions.
Executing the statement in the last step of interrupt signal processing terminates the
process.
Executing this statement terminates the process without executing the remaining

■ Fetching Interrupt Signal Parameters
▼ Maximum Number of Interrupt Signal Parameters
Queue signal parameters can be fetched using built-in functions during interrupt signal
processing.

D050617E.EPS

used to fetch character-string, integer, and real-number signal parameters respectively.
The maximum number of signals can be defined in a range of 2 to 8 (2 at default) for the
parameter attached to an interrupt signal. If the SFC block receives an interrupt signal
exceeding its parameter setting, the signal is ignored causing an error.

D5.6.4 Error Processing

Error processing needs to be defined in an SFC block separately from the SFC block
of the main program. Only one set of processing can be described in one SFC block.
■ Error Processing Description

Similar to other interrupt processes, error processing needs to be defined in an SFC block
separately from the SFC block of the main program. Only one set of processing can be
described in one SFC block.
Both step and selective sequences can be used in error processing. It is necessary for a
selective sequence, however, that the transition conditions are so defined that they can be
easily satisfied; the process being executed when error is caused will not be resumed
otherwise.
SEE ALSO
See H1.13, “Error Handling,” for the details of common error processing.
The execution of the error processing defined in a SEBOL step can be controlled using
“quit” and “return” statements:
Executing this statement in a step sequence terminates the current step action and
executes the next step. Executing it in a selective sequence starts evaluation of
transition conditions. Executing the statement in the last error processing step termi-
nates the process.
Executing this statement terminates error processing without executing the remaining

D5.6.5 Terminating SFC Block Execution

The execution of the SFC block can be terminated as described below:
■ Programs Permitted of Terminating Execution

The execution of the SFC block can be terminated in one of the following manners:
• Executing an “exit” statement.
• Changing block data item BSTS to STOP.
The programs which permit terminating the block execution are as follows:
Table Programs Permitted of Terminating Block Execution
Program “exit” statement BSTS change
Main program
Status-change pre-process - -
Status-change post-process -
Interrupt signal processing
Common error processing (*1)
D050618E.EPS
: Definable.
–: Not definable.
*1: The feasibility of block status change during error processing is determined by the location where the error involved
has been caused. If the error is in the main program, the status can be changed. If the error is in the status-change
post-process, the status cannot be changed.
■ Termination Using “exit” Statement

Use the “exit” statement to terminate the block execution unconditionally, which can be
written as follows:
exit[<expression>]
D050619E.EPS
The block is terminated when the statement is executed and the block status changes to
STOP. The status change pre-/post-processes are not executed.

■ Termination by Changing Block Status
Set the command to change the status to STOP in data item BSTS as in the example
shown below:
EXAMPLE:
.......
.......
%.BSTS = "STOP"
.......
Status-change pre- and post-processes can be executed when changing the block status
to STOP.

D5.6.6 Pausing SFC Block Execution

The execution of the SFC block is paused in one of the following conditions, which
are further described below:
• When the block mode is SEMI.
• When the block being executed receives the command to change the status to
PAUS.
• When the block standing-by for execution receives the command to change the
status to PAUS.
• When the block standing-by for execution in the SEMI mode receives the com-
mand to change the status to RUN.
When the block is paused while a program line is being executed, how the inter-
rupted action is affected varies according to the contents of that line.
The restarting of the paused block is determined by the built-in function “ckstep”
and action when the block is restarted varies according to the condition of the block
at the time of pause.
■ Pausing
The four conditions in which the SFC block is paused are described below, the paused
block can be restarted by commanding a status change to RUN in any of these conditions:
● Block in SEMI Mode

When the block is in the SEMI mode and executed to the start of a main program step, the
block status changes from RUN to PAUS and the block pauses at the start of action.
• No status-change processing takes place at this time.
• Execution is not paused at the start of an interrupt processing step.
● PAUS Command to Block in Execution

When the block being executed receives a PAUS command, the block status is changed
from RUN to PAUS and the block is paused.
• Status-change processing takes place.
• If the block is paused during a SEBOL-described action, the builder-defined PAUS
position will be applied to the restarting of the block.
• If the block is paused during a sequence table or logic chart described action, the
sequence table or logic chart block mode changes from AUT to MAN. The block will
be restarted from the start of the step at all times even if the PAUS position is defined
as the current line.

● PAUS Command to Block at Stand-by for Execution
When the block standing-by for execution receives a PAUS command, the block status
changes from STOP to PAUS and the block is paused at the start of the initial step.
● RUN Command to Block at Stand-by in SEMI Mode

When the block standing-by for execution in the SEMI mode receives a RUN command,
the block status changes from STOP to RUN and then to PAUS and the block is paused at
the start of the initial step.
• Status-change processing takes place for the STOP-RUN status change but does not
for the RUN-PAUS change.
• If post-processing is executed for the STOP-to-RUN change, the RUN-to-PAUS
changes takes place after the post-processing is completed.
• If an interrupt signal is received during the post-processing for the STOP-to-RUN
change, the signal is processed first when the post-processing is completed and then
the RUN-to-PAUS change takes place upon completion of the signal processing.

■ Pause-Interrupted Actions
Actions when the SFC block, for which the PAUS position is defined as the current line, is
paused during execution of a SEBOL step are described.
● “dialogue” Statement Used

When the block has been paused while waiting for input from the operation and monitoring
function after executing a “dialogue” statement, the block is restarted from the line following
the “dialogue” statement unless the operator has not input anything. Since the “time”
specified wait time advanced even while the block is paused, a time-out error is caused if
the wait time has been counted up during the pause.
● “delaycycle” and “delay” Statements Used

The time specified to “delaycycle” and “delay” statements advances even while the block is
paused.
● “wait until” and “compare” Statements Used

The time specified to “wait until” and “compare” statements advances even while the block
is paused. Comparison or condition evaluation is executed at lease once after the block is
restarted, however, even if the specified time has elapsed.
● “semlock wait” Statement Used

When the block has been paused while waiting for the unlocking of semaphore, the block is
restarted from the line following the “semlock wait” statement if the semaphore has been
unlocked by another SFC block during the pause. If the semaphore has not been unlocked
and is secured, the state of waiting for the unlocking will be maintained.
● “seqtable drivewait” Statement Used

When the block has been paused while waiting for the output of an SFC/SEBOL return
event message (%RE) from the sequence table after starting the sequence table using a
“seqtable drivewait” statement, the sequence table block mode remains AUT. The block is
restarted from the line following the “seqtable drivewait” statement if %RE is output from
the sequence table during the pause. If not, the state of waiting for the output will be main-
tained.
● “logicchart drivewait” Statement Used

event message (%RE) from the logic chart after starting the logic chart using a “logicchart
drivewait” statement, the logic chart block mode remains AUT. The block is restarted from
the line following the “logicchart drivewait” statement if %RE is output from the logic chart
during the pause. If not, the state of waiting for the output will be maintained.

■ Identification of Restart Condition
The data returned when the built-in function “ckstep” is executed identifies the condition in
which the SFC block has been restarted.
“ckstep” return values are as follows:
• Data returned 1:
When SFC block is restarted after changing STEPNO in the PAUS mode.
When SFC block is restarted without changing STEPNO in the PAUS mode.
In cases other than listed above.
● “ckstep” Returns “2”

“ckstep” returns “2” when the SFC block, for which the PAUS position defined as the start of
the step, was paused by a PAUS command and restarted without changing STEPNO.
TIP
For the SFC block with the PAUS position defined as the current line, “ckstep” returns the same data
when the block was paused by a PAUS command and restarted without changing STEPNO. Even after
the block has been restarted, “ckstep” returns the same data as that returned before the pause.

• “ckstep” returns “1” when the SFC block was paused, STEPNO has been changed,
and then restarted.

● Cases of “0” Returned by “ckstep”
• When the block is being executed without being paused.
• When the block was paused at the start of a step in the SEMI mode and has been
restarted without changing STEPNO.
• For interrupt signal processing, “0” is returned at all times.
• For status-change pre-processing, “0” is returned at all times.
• For status-change post-processing, “0” is returned at all times.
• For error processing, “0” is returned at all times.
• When the built-in function “ckstepcl” is executed to clear the status following a pause.
• When the action of the restarted step has been completed.
SEE ALSO
D5.6.8, “Changing Current Step,” for the changing of data item STEPNO.

■ Restarting Actions
Actions when the SFC block is restarted with its status changed to RUN are described:
● Restarting after Paused during SEBOL-Defined Action

The block restarts execution from the PAUS position defined on Function Block Detail
Builder. Execution is restarted from the start of the action when the start of the step is
builder-defined, or resumed from where the action was interrupted when the current line is
builder-defined.
● Restarting after Paused during Sequence Table or Logic Chart-Defined

Action
The block restarts execution from the start of the step regardless of the PAUS position
defined on Function Block Detail Builder.
● Restarting after Paused during Transition Evaluation

Evaluation is restarted from the leftmost transition condition.
● Restarting after Paused during Interrupt Signal Processing

The interrupt signal process is canceled and not resumed when the block is restarted.
● Handling of Queued Signals when Restarted

Any signals already queued when the block was paused remain in the queue when the
block is restarted.
● Handling of Signal Received during Pause

Any signals received during the pause are queued and available when the block is re-
started.
● Restarting After Paused during Error Processing

Restarting action varies depending on whether post-processing is executed or not when
PAUS was commanded.
• When post-processing is not executed:
The block is restarted first resuming the interrupted error processing and then resum-
ing the main program from the builder-defined PAUS position.
• When post-processing is executed:
The ongoing error processing is completed first and then the block status is changed
and post-processed when PAUS is commanded. The block resumes execution of the
main program from the builder-defined PAUS position when restarted.

D5.6.7 Referencing Current Step

The step number of the step being executed in the SFC block main program can be
referenced.
■ Procedure
Data item STEPNO is used to reference the step number of the step being executed. As
the execution of the main program advances, the step number of the current step is sent to
STEPNO.
TIP
Data item PHASE is used to hold the name of the current process, which can also be referenced to check
the progress of the block execution. When using PHASE, however, every phase in program steps should
be uniquely named.

D5.6.8 Changing Current Step

The following items as to changing the current step are explained in this section.
• Procedure
• Restrictions
• Actions after STEPNO change
■ Procedure
The number of the current step can be changed by changing the step number set in main
program data item STEPNO when the block is the PAUS status. The use of STEPNO,
however, is only applicable to main program steps but not to interrupt program steps.
■ Note Points
The number of the current step cannot be changed in the following cases:
• When status-change pre- or post-processing is being executed, even if the block is in
the PAUS status.
• Step numbers in the present SFC block cannot be changed, doing so causes error
when executed.
■ Actions after STEPNO Change

Actions following a step number change are as follows:
• No user-defined application program can be executed following a step number
change.
• When the block with the PAUS position defined as the current line is paused, the
restarting position may be changed to the start of step action by setting the current
step number in STEPNO.
• When the block is paused during transition condition evaluation, the restarting position
may be changed to the start of step action by setting the current step number in
STEPNO.
• The current STEPNO data is retained when the block status is changed to STOP.
• The block is restarted from the start of step action when a change to the RUN status is
commanded after STEPNO has been changed.
• The condition in which the block has been restarted can be identified using built-in
function “ckstep.”

D5.6.9 SFC Block Alarm Processing

The SFC block alarm processing and alarm status indication can be scripted using
SEBOL when required.
■ SFC Block Alarm Processing Scripts

Unlike regulatory control function blocks, SFC blocks do not have built-in alarm processing
functions. Thus alarm processing and alarm status indication must be programmed using
SEBOL, if required.
There are four process alarm related data items of the SFC block shown as follows:
• ALRM (Alarm Status)
• AF (Alarm Detection)
• AOFS (Alarm Inhibition)
• AFLS (Alarm Flashing Status)
ALRM (Alarm Status)

The alarm status strings for indicating SFC alarm status contains 23 user-defined strings
and a NR string (string for normal status), which can be specified for all SFC blocks.
If there is no alarm status is in active state, the data item ALRM will be in NR status.
When using a “prcsalarm” statement in a SEBOL step, an alarm status string and a process
alarm can be output together. Using “prcsalarm recover” statement can recover from the
alarm status.
SEE ALSO
• See C5.13, “Deactive Alarm Detection”, C5.14, “Alarm Inhibition (Alarm OFF)” or C5.15.1, “Alarm Dis-
play Flashing Actions” for more information about AF, AOFS and AFLS.
• For more information about changing and referencing alarm data items, see H1.5.10, “Referencing Alarm
Status” and H1. 5.12, “Referencing Alarm Status Individually.”
• See section “■ User-Defined Alarm Status Character String” in Chapter E12.4, “Alarm Status Charac-
ter String and Alarm Processing” for more information about alarm status character strings.

■ Changing Alarm Status for Present SFC Block
Data items AF, AOFS, and AFLS of the present SFC block can be changed so that the
block’s alarm status can all be group-controlled. The following alarm status-change com-
mands are used:
Table Alarm Status Change Commands
Status-change command
Data item
AOF AON ACK
AF Alarm detection group-bypassing. Alarm group-suppression. -
AOFS Undo group-bypassing. Undo group-suppression. -
AFLS - - Alarm group-acknowledging.
D050620E.EPS
■ Changing Alarms of Other SFC Blocks

Process alarms of other SFC blocks can be controlled changing data items AF and AOFS.
The SFC block with its data item AF externally specified for the group-bypassing of alarm
detection, for example, will not output any process alarm and the alarm status will not be
changed even when the “prcsalarm” statement is executed by the present block. Also,
changing data item AFLS permits alarm acknowledging while disabling flashing.

■ Alarm Data Items
The alarm data items are initialized as follows:
Table Data Item Initialization
When initialization When SFC block
Data item Name Builder default
started executed
ALRM Alarm status NR NR
AF Alarm detection specification Previous status
maintained Previous status Despecified
AOFS Alarm suppression specification maintained status
AFLS Alarm flashing status
D050621E.EPS
The alarm status is initialized to the normal status (NR) when the SFC block is executed.
When the execution of the block is terminated with any process alarm caused, the normal
state is recovered when the block is executed again. This is the same when the block mode
is changed from O/S to AUT.
■ Alarm Repeating - SFC Block

If an alarm state is not normalized for a predetermined period of time, repeating alarm
defined on FCS Constants Builder will be caused as long as the SFC block is being ex-
ecuted or paused. The repeating alarm is not caused for the SFC block not being executed
or paused, nor if the execution of the block has been terminated with a process alarm
caused.
Actions related to repeating alarms are otherwise the same as other function blocks.
SEE ALSO
See C5.15.2, “Repeated Warning Alarm,” for more information.

D5.6.10 SFC Online Maintenance

In online maintenance operation, SFC block databases can be manipulated for
system retrofitting, modification, and so forth.
■ Characteristic of SFC Block Online Maintenance

Only the SFC block requiring maintenance is stopped and only the part to be manipulated
is downloaded to FCS for online maintenance so that other control functions will remain
unaffected.
The online SFC block maintenance is different as described below from the normal mainte-
nance of regulatory control block, sequence control block, calculation block, and faceplate
block functions:
• Online maintenance operation cannot be performed on the SFC block if it is in the
RUN or PAUS status but can be performed only in the STOP or ABRT status.
• The SFC block mode changes to O/S during online maintenance operation. The block
status changes to STOP and the mode returns to the previous mode.
• After the downloading for online maintenance, the execution of the SFC block is
resumed when the status is changed to RUN from the operation and monitoring
function or user-defined application program.

■ Block Code Definition
SFC block codes cannot be changed, deleted, nor added. The block’s user-defined data
items can be changed, deleted, or added, however.
■ Block Manipulation
SFC blocks can be changed, deleted, or added in the following cases:
• SFC blocks can be changed or deleted when they are stopped.
• SFC blocks can be added as long as additions are within the maximum number of
function blocks defined for each control station.

D5.6.11 SFC Block Execution

SFC blocks are executed in the idle time of one control period after the execution of
all other basic control functions.
■ Order of Execution
SFC blocks are repeatedly executed in the basic scan period according to the following
rules:
• SFC blocks are executed in the idle time available after the execution of all other basic
control functions has been completed, which include regulatory control, sequence
control, calculation, and faceplate blocks. The rule also applies when both basic
control functions and SFC blocks reside in the same control drawing.
• SFC blocks are infinitely executed within one scan period during the time available
after the execution of other basic control functions. In the next scan period, execution
is resumed from where it was interrupted last.
• SFC blocks are not executed and terminated if sufficient time is not available after the
execution of other basic control functions. In the next scan period, execution is re-
sumed from where it was interrupted last.
An example of two control drawings each defined with three SFC blocks is shown below.
SFC blocks are assigned with time for execution in the numbered order:
Control drawing 1
SFC block SFC block SFC block
1 2 3
Control drawing 2
SFC block SFC block SFC block
4 5 6
D050622E.EPS
Figure The Order of Execution Time Allocation
After the last SFC block 6 in control drawing 2 was allocated with execution time, the order
returns to the top SFC block 1 in control drawing 1 and execution time is reallocated.
Execution time is not allocated to any SFC blocks which are not being executed.

D5.6.12 Data Items - SFC

SFC blocks use system-specific and user-defined data items.
Every different SFC block using a different group of data items needs to be differ-
ently coded. If a group of same data items is used by a number of blocks, the blocks
can be identically coded and they can share the same group of data items.
■ SFC Block Models

It is necessary to define SFC block model as follows:
1. Select one of the three available models of system-specific data sets (see below).
2. Specify the name and data type for the user-defined data item to be used. Different
SFC block codes are needed for different models as well as different user-defined
data items.
The following three SFC block models are available:
• _SFCSW: 3-position switch
• _SFCPB: Pushbutton
• _SFCAS: Analog
The following are their details:
Table Details of Models
Model
_SFCSW _SFCPB _SFCAS
Item
User-defined data No. of items 32 32 32
item high limit Max. area size 8180 bytes 8180 bytes 8180 bytes
Data item comment Availability Not available Available Available
3-position-switch type - -
Instrument faceplate 5-pushbutton type - -
Basic type - -
None -
Trend
PV, SV, MV - -
D050623E.EPS

The instrument faceplates of the three block models are shown below:
AUT STOP AUT STOP AUT STOP

NR NR NR
100.0
RUN RUN RUN
80.0
60.0
PAUSE PAUSE PAUSE
40.0
20.0
STOP STOP STOP

0.0

D050624E.EPS
Figure SFC Block Instrument Faceplates

■ System-Specific Data Items
▼ System Definition Data Items
SFC block system-specific data items and their availability in block models are listed below:
Table System-Specific Data Items & Block Models (1/2)
SFC block model
Data item Data name
MODE Block mode
OMOD Block mode (lowest priority)
CMOD Block mode (highest priority)
BSTS Block status
PREBSTS Previous block status
ALRM Alarm
AFLS Alarm flashing
AF Alarm detection
AOFS Alarm suppression
ERRC Classified error code
ERRE Detailed error code
ERRP Error-caused plane number
ERRS Error-caused step number
ERRL Error-caused line number
ERRF Error-caused program unit
STEPNO Current-step number
PHASE Phase name
IPHASE Interrupt-phase name
D050625E.EPS
: Available

Table System-Specific Data Items & Block Models (2/2)
SFC block model
Data item Data name
OPMK Operation mark
SAID System user ID
UAID User application ID
DILG Dialog acknowledgement
SEMA Semaphore name
SWLB[5] Switch label -
SWCR[5] Switch display color -
SWST[5] Switch flashing status -
SWOP[5] Switch operation disable status -
PV Process variable - -
SV Setpoint value - -
MV Manipulated output value - -
SH Scale high-limit value - -
SL Scale low-limit value - -
SVH Setpoint high limit - -
SVL Setpoint low limit - -
MH Manipulated variable high-limit setpoint - -
ML Manipulated variable low-limit setpoint - -
MSH MV scale high limit - -
MSL MV scale low limit - -
D050626E.EPS
: Available
–: Not available

The accessibility of the system-specific data items is shown below:
Table System-Specific Data Item Accessibility (1/2)
General-purpose
SEBOL Sequence table
Data item calculation block
Read Write Read Write Condition Manipulation
MODE (*1) (*1)
OMOD - - - - -
CMOD - - - - -
BSTS (*1) (*1)
PREBSTS - - - -
ALRM - (*1) - -
AFLS (*1) (*1)
AF (*1) (*1)
AOFS (*1) (*1)
ERRC - - - -
ERRE - - - -
ERRP - - - -
ERRS - - - -
ERRL - - - -
ERRF - - - -
STEPNO (*2)
PHASE - - - -
IPHASE - - - -
D050627E.EPS
: Accessible
–: Not available
*1: Accessible by connecting sequences.
*2: See D5.6.8, “Changing Current Step,” for restrictions.
SEE ALSO
For details on setting step numbers, refer to D5.6.8, “Changing Current Step.”

Table System-Specific Data Item Accessibility (2/2)
General-purpose
SEBOL Sequence table
Data item calculation block
Read Write Read Write Condition Manipulation
OPMK - -
UAID - -
DILG - -
SEMA - - - -
SWLB[5] - -
SWCR[5]
SWST[5]
SWOP[5]
PV - -
SV - -
MV - -
SH - - - -
SL - - - -
SVH - -
SVL - -
MH - -
ML - -
MSH - - - -
MSL - - - -
D050628E.EPS
: Accessible
–: Not available

● Step-Number & Phase-Name Data Items
Step numbers and phase names are set in the following data items:
• Main program
Step No.: STEPNO
Phase name: PHASE
• Interrupt programs
Step No.: None
Phase name: IPHASE
The main program current step number is set at STEPNO and current phase name at
PHASE. The interrupt program current phase name is set at IPHASE. During the execution
of an interrupt program, the step number and the phase name of the main program when
the interrupt program was invoked are retained at STEPNO and PHASE respectively.
TIP
One exception with interrupt programs is that the phase name of status-change pre-processing is not set
at IPHASE.
When interrupt programs of different levels are being executed simultaneously, only the
phase name of the highest-level interrupt program is set at IPHASE. A null-length character
string (“”) is set at IPHASE for a regular-level interrupt program.
Default STEPNO, PHASE, and IPHASE are as follows:
Table Default STEPNO, PHASE, & IPHASE
Data item Name Builder default At initialization At SFC block start
STEPNO Current step number 0 Step number of initial step
Previous state
PHASE Phase name “” (*1) retained Phase name of initial step
IPHASE Interrupt program phase name “” (*1) “” (*1)
D050629E.EPS
*1: Null-length character string.

● Alarm Data Items
ALRM, AFLS, AF, and AOFS are process alarm data items.
SEE ALSO
See D5.6.9, “SFC Block Alarm Processing,” for details.
● Error Data Items

When an error is caused, the classified error code is set at ERRC and the detailed error
code at ERRE. The error-caused plane number is set at ERRP and the error-caused step
number at ERRS, making it easy to identify the location of the error caused.
• When an error is detected in a SEBOL-described action, ERRL identifies the error-
caused line number and ERRF identifies the error-caused function name. A null-length
character string is set at ERRF if the detected error is in the main program.
• When an error is detected in a sequence table-described action, 0 is set at ERRL and
a null-length character string at ERRF.
• When an error is detected in a transitional condition, the negative transition condition
number (-1 through -8) is set at ERRL and a null-length character string at ERRF.

■ User-Defined Data Items
▼ User Definition Data Items
Up to 32 data items can be optionally user-defined, using up to 8180 bytes in total.
● Date Types Available

The following data types can be used for user-defined data items:
Table Data Types of User-Defined Data Items
Data type Symbol No. of bits Min. data Max. data
Character string CHRn 8*n bits n=2 n=16
Integer I16 16 bits -32768 32767
Long integer I32 32 bits -2147483648 2147483647
38 38
Single-precision floating point F32 32 bits -3.402823*10 3.402823*10
308 308
Double-precision floating point F64 64 bits -1.79769313486231*10 1.79769313486231*10
D050630E.EPS
Simple variables and one- and two-dimensional arrays can be used with every type. Up to
999 array elements can be used and up to 10000 elements can be used for arrays 1 and 2
in total. The data status-attached data type is not available.
Mainly, the following settings may be defined for a user defined data item of SFC block.
• Data item name
• Data type
• Array element 1
• Array element 2
• Data item comment

● Accessing User-Defined Data Items
Accessing user-defined data items from function blocks and some restrictions are as
follows:
• Data as well as sequences can be connected for user-defined data items.
• User-defined data items cannot be described in the condition and action signal col-
umns of a sequence table.
• In the case of general-purpose calculation blocks (CALCU, CALCU-C), user-defined
data items cannot be accessed even if “<tag name>.<data item name>” is directly
specified in the block.
• User-defined data items can be accessed from SEBOL programs in SFC blocks.
• SFC block queue signals can be referenced when a CHR16 one-dimensional array
named QUEUE is defined as a user-defined data item.
SEBOL data-type specifiers for data-type symbols are listed below:

• CHR2 to CHR16: char *2 to char*16
• I16: integer
• I32: long
• F32: float
• F64: double
SEE ALSO
See D5.6.1, “Queue Signal Processing,” for the details of queue signals.

D5.6.13 SFC Block Mode & Status

The modes, status, and status transition of SFC blocks are described.
■ Block Modes - SFC

▼ SEMI Mode Operation
The SFC block has three control modes.
● Description of Modes - SFC

The control status in each block mode is described below:
• O/S: Out-of-service
• SEMI: Semi automatic
• AUT: Automatic
The actions of SFC block in each block mode are shown below:
• AUT (automatic) mode:
Every step is successively executed.
• SEMI (semi-automatic) mode:
The block stops at the start of each step, and the step is executed at a command from
the operation and monitoring function, etc. The mode can be enabled or disabled for
each block.
• O/S (out-of-service) mode:
The block cannot be executed. Online maintenance operation is performed in this
mode.

● Rules for Changing Block Modes - SFC
The following rules are applied to the changing of block modes:
• The mode cannot be changed to O/S when the block status is RUN or PAUS.
• The block status remains unchanged when the block mode is changed to O/S.
• The block status changes to STOP when the block mode is changed from AUT to O/S,
or from O/S to SEMI.
• The block status cannot be changed when the block mode is O/S.
• The block mode can be changed from AUT to SEMI or vice versa without any restric-
tion, except that the mode cannot be change to SEMI if its use is prohibited by the
builder.
• No user applications can be executed following a block mode change.
An example of changing the mode of the SFC block tag-named SFC001 using a SEBOL
program is shown below:
......
SFC001.MODE = "SEMI"
......
SFC001.MODE = "AUT"
......

■ SFC Block Status
The SFC block status shows the SFC block operation status as executing, paused,
stopped, and aborted.
The SFC block has four status as described below:
Table SFC Block Status
Name Status Description
STOP Stopped The block is stopped and standing-by for a start command.
RUN Executing Step actions are being executed or transition conditions are being evaluated.
PAUS Paused Execution is suspended.
ABRT Aborted Execution has been aborted due to fatal or internal error or insufficient memory.
D050631E.EPS
The following commands are used to change the block status:

• RUN:
Changes status to RUN, starting execution of the block or restarting the paused block.
• STOP:
Changes status to STOP, stopping execution of the block.
• PAUS:
Changes status to PAUS, suspending execution of the block.
• RSET:
Resets status of the aborted block to STOP.
• ABRT:
Changes status to ABRT, forcibly terminating execution of the block.

■ Transition of SFC Block Status
▼ PAUS Stop Position
The transition of block status when the SFC block is in the AUT or SEMI mode is described.
PAUS
PAUS
PAUS ABRT
(*3) (*1)
STOP RUN
RUN ABRT
STOP RUN ABRT
STOP (*1)
(*2)
RSET
*1: Status changes also in case of fatal or internal error, or insufficient memory.
*2: Status changes also when execution is terminated by the “exit” or “end” statement.
*3: Status changes at the start of a step when the block mode is SEMI.
D050632E.EPS
Figure Transition of Block Status
• The RUN command starts execution of the SFC block in the STOP status, which then
changes to RUN when started.
• The PAUS command suspends execution of the SFC block in the STOP status at the
start of the initial step, the status then changes to PAUS.
• The stopping position when the status is changed to PAUS during execution of a
SEBOL step action can be specified either at the start of the step or the current pro-
gram line.
• In the SEMI mode, the block status changes from RUN to PAUS at the start of every
step. The step can then be executed upon receiving the RUN command from the
operation and monitoring function, etc.
An example of changing the status of the SFC block tag-named SFC001 using a SEBOL
program is shown below, in which a status change command character string is entered on
the right-hand side of each assignment statement :
.....
SFC001.BSTS = "RUN"
......
SFC001.BSTS = "PAUS"
......
SFC001.BSTS = "STOP"
......

<Toc> <Ind> <D5.7 Manipulating Unit Instrument from SFC Block> D5-98
D5.7 Manipulating Unit Instrument from SFC Block

Accessing unit data and transmitting signal to units from the SFC block are de-
scribed.
■ Accessing Unit Data

Unit data can be accessed from the SFC block as described below.
Use one of the following manners to access unit data:
• Declare the unit tag name using the “block” or “global block” statement. Or assign the
unit tag name using the “assign” statement to the local generic name in the “genname”
statement or the global generic name in the “global genname” statement.
• Define the unit data name in place of the function block data item name.
An example of accessing unit data from a SEBOL step is shown below:

!_UTSW is the unit model name.
block _UTSW UNIT001
char*8 umode, ustat
!Acquire the mode.
umode = UNIT001.MODE
!Acquire the status.
ustat = UNIT001.BSTS
.....
The <block model> referred by “block” statement, or etc., are the model name of unit
function blocks displayed in the Function Block Detail Builder.
The following three models of unit are supported.
• _UTSW: Non-Resident Unit Instrument with Three-Position Switch
• _UTPB: Non-Resident Unit Instrument with Five-Pushbutton Switch
• _UTAS: Analog Non-Resident Unit Instrument
SEE ALSO
For the details of unit instruments, see chapter D6.2, “Unit Instrument.”

■ Transmitting Signals to Units
Signals can be transmitted to units from the SFC block using the “signal” statement. Upon
receiving a signal, the unit sends the same signal to every unit operation being executed.
signal<signal name>[,<signal parameter>…]to<tagname>
[;<error variable>>][; error <label>[,<error identifier>]]

errorsub
<signal name>: A character string constant or variable using up to 8 bytes.
<signal parameter>: An integer, long, float, or double-type numeric expression, or a
character string (effective up to the leading 16 bytes). Up to 8
parameters can be specified.
<tag name>: The tag name of the destination unit for signal transmission. The
“block” statement-declared tag name, “gene” statement-declared local
generic name, or “argblock” statement-declared formal-argument
function block can be used. Specify “%%” for the present unit.
<label>: A branching destination for error processing.
<error identifier>: A constant or local variable to identify the error-caused location in
error processing.
D050633E.EPS

It is required to designate a <tag name> when unit instrument transmitting a signal. If the
unit tag name is not specified, the signal is transmitted to the present unit.
The “signal” statement is normally terminated when the signal has been received by opera-
tions of the destination unit. Error is caused if none of unit operations receive the signal.
TIP
The “signal” statement is used for transmitting both queue and interrupt signals.
SEE ALSO
For the details of operations, see chapter D6.8, “Operations.”

<Toc> <Ind> <D6. Unit Supervision> D6-1
D6. Unit Supervision

Unit Supervision is an operating and monitoring activity for controlling the devices
grouped as a unit, of batch process or continuous process. Unit Supervision may
define a group of processing devices as a “unit,” each “unit” may be assigned with
a “unit instrument,” so that the operation on the grouped devices may be carried out
as a unit.
Usually, the devices of a process are operated and monitored individually, when
applying Unit Supervision, a plant may be operated in a much-simplified manner.

<Toc> <Ind> <D6.1 Outline of Unit Supervision> D6-2
D6.1 Outline of Unit Supervision

In this section, Unit Supervision of CS 1000/CS 3000 is explained.

D6.1.1 What is a Unit?

A unit is a group of device modules for controlling main process procedures in a
plant, such as the modules, assigned with tag names, for distillation columns or
reactors. So that the operation may be carried out by groups instead of individual
devices. Control and management for devices can be performed cooperatively as a
grouped unit.
■ A Continuous Process Unit

When a complicated application for process control and management is applied to a
continuous process, many sequence tables may be used. Using the Unit Supervision, the
process management may be controlled by a single unit instrument, and the detailed
process steps may be controlled by the operations related to the unit instrument.
Raw material
Cracked gas
Steam
Fuel
D060101E.EPS
Figure A Continuous Process (Cracking Furnace) Unit
Raw material stop
System disconnection
Cooling
Steam introduction
Heating
Raw material feed
D060102E.EPS
Figure Decaulking Work Flow

■ A Batch Process Unit
In batch processing for a chemical plant, devices used for control operations are grouped
into several equipment entities for different processes, such as reaction process and
crystallization process. By assigning a unit instrument to each group, operation can be
performed by equipment entities.
Material A
Material B
Unit A Unit B
TIC TIC
M M
TIC TIC
STM STM
Discharge Discharge
Intermediate
product C
Material D
Unit C
TIC
M
TIC
STM
Discharge
D060103E.EPS
Figure A Batch Process Unit

D6.1.2 ISA S88.01 and Unit Supervision

ISA-SP88 is a specification worked out by a group of users and vendors gathered
together for setting a standard for American ISA (Instrument Society of America)
standardization. Part of it, Batch Control Part1: Models and Terminology has com-
pleted and was published as IEC 61512-1 in 1997.
In this section, the ISA S88.01 and Unit Supervision will be explained.
■ Physical Model
ISA S88.01 stipulates a seven-level Physical Model (physical assets based model). Unit
Supervision applies the Unit Instruments, Operations and Regulatory Control Blocks (PID
etc.) to represent the Units (devices), Equipment Modules and Control Modules. Thus, the
control modules, in a hierarchy, for whole plant may be constructed except for the field
devices in the physical layer.
ISA S88.01 Physical Model Unit Supervision
Enterprise
Site
Area
Process Cell
Unit Unit Instrument
Equipment Module Operation (SFC)
Regulatory Control Block

SEBOL
Control Module
Sequence Table
Logic Chart
D060201E.EPS
Figure ISA S88.01 Physical Model and CS 1000/CS 3000 Unit Supervision

■ Control Activity Model
In ISA S88.01, the Control Activity Model consists of seven control activities for batch
manufacturing control is defined as follows. Unit Supervision is positioned at the supervi-
sory level of process control (Function Block) activity.
Furthermore, Unit Supervision is not only limited for batch process but can also be applied
to continuous process. Thus, Unit Supervision may be configured to execute independently
without applying the Process Management.
Production Planning Production Information

Recipe Management
and Scheduling Management
Process Management
Unit Supervision
Process Control
(Function Block)
Personnel and Scope of Unit Supervision

Environmental Protection
D060202E.EPS
Figure ISA S88.01 Control Activity Model and CS 1000/CS 3000 Unit Supervision

■ Procedural Control Model
For a batch process, the products produced in the process requires proper procedural
control for operation and manufacture. This procedural control is in a hierarchical manner
and is stipulated in S88.01 as Procedural Control Model. Unit Supervision conforms to the
ISA S88.01 model and controls the Sequence Table, Logic Chart assigned under the
hierarchy of Phase when running the operations in SFC. The operations executed in unit
instruments are under the supervisory control of the unit procedure.
ISA S88.01
Procedural Control Model
Procedure
Procedure 01 Blending
02 Reaction
Scope of Unit Supervision
Unit instrument
Unit procedure
01 Charging A
Unit Procedure 02 Heating 03 Charging B
04 Reaction
Operation
Operation 01 Initialization
02 Catalyst charging
03 Curing
Phase
Phase SEBOL
Sequence
table
Logic
chart
D060203E.EPS
Figure ISA S88.01 Procedural Control Model and CS 1000/CS 3000 Unit Supervision

● Procedure
The procedure defines the processing strategy in a unit for product manufacture.
● Unit Procedure
A unit procedure is a procedure running in a unit instrument. The unit instrument is defined
with the procedure for the corresponding control entity and physical equipment, and it
displays each manufacturing stage when the production carried out in that physical equip-
ment. A unit procedure consists of one or more operations and is configured in one unit
instrument.
● Operation
An operation is a sub-procedure of the unit procedure; it consists of a set of phases.
Normally, one operation is running in one unit instrument as the operating sequence for
controlling a continuous processing unit. For a batch processing unit, multiple operations
are normally running in one unit instrument as the operating sequence.
The operations for batch process may not only be assigned to a specific product, but may
also be applied as a common operations shared by others.
However, the operations, the unit instrument for calling the operations must be placed in
the same FCS.
● Phase
Phase is the smallest element of procedural control for the corresponding process actions.
For the production process divided in many parallel production lines with many stages, a
phase may also represent each process stage.
According to CS 1000/CS 3000 Unit Supervision, the SEBOL program, the sequence table
and the logic chart called out by the operations are conforming to the phases.

D6.1.3 Batch Management and Unit Supervision

This chapter explains how to apply Unit Supervision together with Batch Manage-
ment.
■ Unit Supervision
When Batch Management is applied at the upper level of Unit Supervision, the nonresident
type unit instruments should be used.
For a nonresident unit instrument, the unit procedure can not be defined on the function
block. A unit recipe procedure created by Batch Management may be assigned as a unit
procedure to the unit instrument when running the recipe. Thus, if there is no unit recipe is
running, the unit instrument does not have any unit procedure.
The followings will describe the behavior of Unit Supervision built-in Process Management.
● Nonresident Unit
Nonresident Unit is a unit instrument may be applied to execute a unit recipe procedure
assigned to it. When the unit recipe is not running, the unit procedure does not reside.
● Common Block Data Access

When a common block applied in a recipe, its data may be accessed by operations.
● Data Items for Process Management

On the unit instrument system fixed data items, the data for process management are set.
SEE ALSO
For details on recipe management and process management, refer to Part G, “Batch Management.”

D6.1.4 Application Capacity of Unit Supervision

Application capacity for Unit Supervision is described below.
■ Application Capacity of Unit Supervision ¡

Table Application Capacity For PFCS ¡
Item Max. capacity
No. of units 2 per FCS, 10 per FCS, 15 per FCS(*1)
No. of operation 30 per FCS, 100 per FCS, 120 per FCS(*1)
No. of generic tag names (arrays) 256 per unit
No. of generic tag names (array elements) 512 per unit
Resident unit 64 per unit
No. of operation generic names
Nonresident unit 99 per unit
No. of user-defined data items 256 per unit
User-defined data memory size 32768 byte per unit
No. of unit procedure steps 99 steps
No. of SFC operation steps 99 steps
No. of Transitional Matrixes 16 per project
D060401E.EPS
*1: The maximum number varies with the FCS database types.
SEE ALSO
For details on FCS database type of PFCS, refer to “● FCS Database Types Selectable in the Standard
Type PFCS ¡ ”or “● FCS Database Type Selectable in the Enhanced Type PFCS ¡ ” in “ ■ Define
Database Type ¡ ” in F1.4.1, “Creating a New FCS.”
■ Application Capacity of Unit Supervision £

Table Application Capacity SFCS £
Item Max. capacity
No. of unit instruments 20 per FCS (*1)
No. of operations 150 per FCS (*1)
No. of generic operation names 99 per unit
D060402E.EPS
SEE ALSO
For details on FCS database type of SFCS, refer to “● FCS Database Types Selectable in the SFCS :
SFCS £ ” in “■ Define Database Type £” in F1.4.1, “Creating a New FCS.”

Table Application Capacity LFCS £
Item Max. capacity
No. of unit instruments 5 per FCS, 35 per FCS, 30 per FCS (*1)
No. of operation 20 per FCS, 250 per FCS, 200 per FCS (*1)
D060403E.EPS
SEE ALSO
For details on FCS database type of LFCS, refer to “● FCS Database Types Selectable in the LFCS :
LFCS £ ” in “■ Define Database Type £ ” in F1.4.1, “Creating a New FCS.”
Table Application Capacity LFCS2 £
Item Max. capacity

No. of operation 400 per FCS (*1)
D060405E.EPS
SEE ALSO
For details on FCS database type of LFCS2, refer to “● FCS Database Types Selectable in the LFCS2 :
LFCS2 £ ” in “■ Define Database Type £ ” in F1.4.1, “Creating a New FCS.”

Table Application Capacity KFCS £
Item Max. capacity
No. of unit instruments 5 per FCS, 30 per FCS (*1)
No. of operation 20 per FCS, 250 per FCS, 200 per FCS (*1)
D060404E.EPS
SEE ALSO
For details on FCS database type of KFCS, refer to “● FCS Database Types Selectable in the KFCS :
KFCS £ ” in “■ Define Database Type £” in F1.4.1, “Creating a New FCS.”
Table Application Capacity KFCS2 £
Item Max. capacity

No. of operation 400 per FCS (*1)
D060406E.EPS
SEE ALSO
For details on FCS database type of KFCS2, refer to “● FCS Database Types Selectable in the KFCS2 :
KFCS2 £ ” in “■ Define Database Type £” in F1.4.1, “Creating a New FCS.”

<Toc> <Ind> <D6.2 Unit Instrument> D6-13
D6.2 Unit Instrument

Unit Instrument is a part of Unit Supervision application. Unit Instruments can be
applied for controlling and operating a series of processes, such as heating, agita-
tion, reaction and distillation.
The process control can be carried out with the operations called from unit proce-
dures, while the unit procedures are called from the unit instrument.

■ Type of Unit Instruments
A unit instrument consists of unit instrument data items and unit procedures.
A unit procedure is an ordered set of operations for controlling the process of product
manufacture.
An operation is an ordered set of the control sequences, the operations consist of the
following types.
• The operation may be started by a unit procedure
• The operation for real-time monitoring
• The operation for process initialization to the unit instrument execution.
• The operation for interrupt processing which interrupts to the sequentially started
control sequences.
The data items of a unit instrument are mainly for tuning parameters and monitoring the
process. Some data items on the unit instrument are user definable.
There are two types of unit instruments, resident type and non-resident type.
● Resident Unit
A resident unit means that a unit instrument is assigned with fixed unit procedure (SFC).
When the manufacturing procedure for production is always the same, the resident unit
may be applied.
Unit Instrument
Unit instrument data items Unit procedure (Fixed)
System-fixed data items Initialization
User-definable data items

Charging 1
Agitation
Charging 2
D060201E.EPS
Figure Resident Unit Instrument

● Non-Resident Unit
A non-resident unit means that a unit instrument is not assigned with fixed unit procedure.
So that a non-resident unit may use the unit recipe procedure created by Batch Manage-
ment for application. The unit recipe procedure may be downloaded to the specified non-
resident unit when setting up the recipe.
The non-resident unit may be applied together with Batch Management.
Batch Management
Unit recipe procedure
Initialization
Charging 1
Agitation
Charging 2
Download
Unit Instrument (Nonresident)
Unit instrument data items Unit procedure (editable)
System-fixed data items
User-definable data items
D060202E.EPS
Figure Non-Resident Unit Instrument
■ Unit Instrument Block Models

They are categorized into two types, resident type and nonresident type. Each type con-
sists of three models.
● Resident Unit Models

Resident unit instruments consist of the following three block models.
• _UTAS Analog Unit Instrument
• _UTPB Unit Instrument with Five-Pushbutton Switch
• _UTSW Unit Instrument with Three-Position Switch
● Nonresident Unit Models

Nonresident unit instruments consist of the following three block models.
• _UTAS-N Analog Non-Resident Unit Instrument
• _UTPB-N Non-Resident Unit Instrument with Five-Pushbutton Switch
• _UTSW-N Non-Resident Unit Instrument with Three-Position Switch

■ Unit Instrument Elements
A unit instrument is constructed with the following elements.
● Unit Instrument Data Items

The process data, the data controlled by the unit instrument such as the internal tempera-
ture and pressure of a reactor can be assigned to the unit instrument data items for control
and monitoring.
The information related to the process flow such as the load factor and the operating rate,
or the quality, the name and the information related to the products being manufactured
may be displayed via instrument data items.
There are 4 types of data items for unit instrument, shown as follows.
• System fixed data items
• User definable data items
• Data items for faceplate (Fixed by each model of unit instrument)
• Data items for process management (Fixed by each model of unit instrument)
● Unit Procedure
A unit procedure controls an ordered set of operations. An operation is a set of control
sequences corresponds to the physical equipment.
The unit procedure may be formed in an SFC (Sequential Function Chart), by registering
the names of operations to the step action columns of SFC.
A unit instrument may not only execute the operations started by the unit procedure but may also
execute the operation for initialization and the operation for monitoring.
Furthermore, the unit recipe procedure created by Batch Management can be used for a
nonresident unit procedure.
● Operation
There are two types of operations are available, the operations programmed in SEBOL and
operations programmed in SFC. The data items of operations are not user definable.
In the operations programmed in SEBOL, the main process, status change process and
signal conditioning process are all written in SEBOL.
While in the operations programmed in SFC, the main process and status change process
are described by SFC, but the sequences in each step are described in SEBOL, sequence
table, or logic chart. There are 6 models of operations programmed in SFC are available,
they are classified according to their available data items.
• OPSFC SFC Operation
• OPSFCP1 SFC operation with floating-data parameters
• OPSFCP2 SFC operation with character-data parameters
• OPSFCP3 SFC operation with floating/character-data parameters
• OPSFCP4 SFC operation with integer/character-data parameters
• OPSFCP5 SFC operation with floating/integer-data parameters

● Unit Mode and Unit Status
A unit instrument likes other function blocks also has mode and status.
The mode and status of a unit instrument are referred to as unit mode and unit status
respectively.
The unit mode includes AUT, SEMI etc. may indicate the control mode of the unit instrument.
The unit status includes END, ABORTED etc. may indicate the operation state of the unit
instrument.
● State Transition Matrix

State transition matrix determines the states to transit corresponding to a unit mode change
or a unit status change.
When a unit mode change or a unit status change command is given, the unit instrument
may change its unit mode or unit status according to the state transition matrix to control
the programs and operations in the unit instrument.
● Interrupt Processing
The interrupt processing is available when an operation started from a unit procedure is
interrupted. The interrupt processing to an operation may have the following activities.
• Processing prior to status change
An interrupt processing triggered by an one-shot command for unit mode or unit
status change.
This processing allows SEBOL or other programs to check and give the permission for
the block status change.
• Processing after status change
An interrupt processing after a unit mode or a unit status change.
• Processing upon an interruption signal
Upon a designated signal, the specified interrupt processing may be executed.
● Alarm Status
A unit instrument may display its alarm status just like other function blocks. With a SEBOL
statement (unit prcsalarm) scripted in an operation, the unit instrument may generate
messages for occurrence and recovery of an alarming status. The alarm messages gener-
ated by a unit instrument, just like other function blocks, may be displayed on the process
alarm window. Moreover, the alarm priority, alarm detection, alarm inhibition and so on may
be defined for the unit instrument alarms.
● Message
There are following types of messages related to the unit instrument. Just like other func-
tion blocks, the unit instrument related messages are also stored in the historical message
save file in HIS.
• Unit process alarm occurrence/recovery message
• Unit mode/status change message
• Sequence message
• System alarm message
• Operation record message

<Toc> <Ind> <D6.3 Unit Instrument Data Items> D6-18
D6.3 Unit Instrument Data Items

Unit instrument data items are used to indicate the process data of unit-controlled
equipment modules. And the temperature and pressure of reactors and other pro-
cess data such as material feed quantities can be set on the data items.
■ Data Types of Unit Instrument

The data can be used on the unit instrument data items are shown below. Different from the
data of function blocks, the data of unit instruments are not attached with data status
information.
Table Unit Instrument Data Types
Type Description Remarks
I16 16-bit signed integer -32768 to 32767
U32 32-bit unsigned integer 0 to 4294967295
F32 Single-precision floating-point (32 bits) -3.402823 • 1038 to 3.402823 • 1038
F64 Double-precision floating-point (64 bits) -1.79769313486231 • 10308 to 1.79769313486231 • 10308
CHR*n Character-string (2)n)16)
D060301E.EPS
■ Data Items of Unit Instrument

A unit instrument has the following groups of data items:
• System-fixed data items
• Faceplate data items
• User-defined data items
• Data items for process management (nonresident unit instrument)

D6.3.1 System-Specific Data Items

System-fixed data items are a group of preset unit data items, such as data item
names, data names and data types. These system-fixed data items cannot be
changed by the user.

■ System-Fixed Unit Instrument Data Items
▼ System Definition Data Items
The specifications of system-fixed data item names, data names and data types are shown
below:
Table System-Fixed Data Items
Data item name Data name Data type Entry Default Remark
MODE Unit mode CHAR*8 AUT
BSTS Unit status CHAR*8 END
SUBS Unit substatus CHAR*8
RUNS Unit control status CHAR*8
ALRM Alarm CHAR*8 NR
AFLS Alarm flashing U32
AOFS Alarm suppression specification U32
AF Alarm detection specification U32
ERRC Classified error code U32 0
ERRE Detailed error code U32 0x0000
ERRL Error-caused step number U32 0
STEPNO SFC step number I16 0
OPMK Operation mark I16 0
SAID System APID I16 0
UAID User APID I16
SUAID Self-user reserve I16 0
OMOD Unit mode (lowest priority) CHAR*4
CMOD Unit mode (highest priority) CHAR*4
DILG Dialog acknowledgement U32
PREMODE Previous unit mode U32 AUT
PREBSTS Previous unit status U32 END
STARTIME Execution start date & time U32
ENDTIME Execution end date & time U32
BATCHID Batch ID CHAR*16 For Process Management
USER1 User code 1 CHAR*16 For Process Management
USER2 User cord 2 CHAR*16 For Process Management
RECIPEGR Recipe group number I16 0 For Process Management
RECIPE Recipe name CHAR*16 For Process Management
PARTNO Unit recipe number I16 0 For Process Management
D060302E.EPS
: Entry allowed at all times.

Blank: Entry not allowed.

D6.3.2 Faceplate Data Items

These data items are used for displaying data of unit faceplates. Different sets of
data items are applied to different faceplates.
■ Data Items for Analog Unit Instrument Faceplate

The specifications of faceplate data items for analog unit instrument faceplates, which are
in accordance with the _UTAS or _UTA-N unit model, are shown below:
Table Analog Type Faceplate Data Items
Data item name Data name Data type Entry Range Default
PV Process variable F32 PV engineering-unit data SL
SV Setpoint value F32 PV engineering- unit data SL
MV Manipulated output value F32 MV engineering-unit data MSL
SH Scale high limit F32 PV engineering-unit data 100.0
SL Scale low limit F32 PV engineering-unit data 0.0
MH MV high-limit setpoint F32 MSL to MSH MSH
ML MV low-limit setpoint F32 MSL to MSH MSL
SVH Setpoint high limit F32 SL to SH SH
SVL Setpoint low limit F32 SL to SH SL
MSH MV-scale high limit F32 MV engineering-unit data 100.0
MSL MV-scale low limit F32 MV engineering-unit data 0.0
SWCR[5] Switch display color I16 0 to 15 7 (*1)
SWLB[5] Switch label CHAR*8 None null (*2)
SWST[5] Switch flashing status I16 0,1 0 (*1)
SWOP[5] Switch disabled status I16 -15 to 15 0 (*1)
D060303E.EPS

*1: Array [1] to array [5] are the same.
*2: The default settings for SWLB[1] to SWLB[5] are as follows.
SWLB[1]: START, SWLB[2]: PAUSE, SWLB[3]: RESTART, SWLB[4]: SUSPEND, SWLB[5]: END
TIP
For the data display on [PV], [SV], [MV], it is required to define them in the monitoring operations or etc..

■ Data Items for 5-Pushbutton Switch Faceplate
The specifications of faceplate data items for 5-pushbutton switch faceplates, which are in
accordance with the _UTPB or _UTPB-N unit model, are shown below:
Table 5-Pushbutton Faceplate Data Items
Data item name Data name Data type Entry Range Default
SWCR[5] Switch display color I16 0 to 15 7: White (*1)
SWLB[5] Switch label CHAR*8 None (*2)
SWST[5] Switch flashing status I16 0,1 0: Stop (*1)
SWOP[5] Switch disabled status I16 -15 to 15 0: None (*1)
D060304E.EPS

*1: Array [1] to array [5] are the same.
*2: The default settings for SWLB[1] to SWLB[5] are as follows.
SWLB[1]: START, SWLB[2]: PAUSE, SWLB[3]: RESTART, SWLB[4]: SUSPEND, SWLB[5]: END
■ Data Items for 3-Position Switch Faceplate

There are no data items for 3-position switch faceplates, which are in accordance with the
_UTSW or _UTSW-N unit model.

D6.3.3 User-Definable Data Items

User-definable data items refer to a data item group defined by the user for unit
instrument data.
■ Number of Unit Instrument Data Items that can be Defined by User ¡

A maximum of 256 data items can be defined by user for a unit instrument. However, the
total memory sizes for the unit instrument data defined by user must be smaller than 32K
byte.
■ Number of Unit Instrument Data Items that can be Defined by User £

A maximum of 256 data items can be defined by user for a unit instrument. However, the
total memory sizes for the unit instrument data defined by user must be smaller than 8K
byte.
■ Definition of User Definable Data Item

▼ User Definition Data Items
The definitions on a user definable data item of a unit instrument are as follows.
● Data Item
Data item name may be defined with up to 8 alphanumeric character including underscore
( _ ) , but the underscore can not be used as the first character of the data item name.
● Data Type
The data type may be specified. Unit instruments support the following data types.
• I16 16-bit signed integer
• I32 32-bit signed integer
• F32 32-bit floating point
• F64 64-bit floating point
• CHR2 to 16 character string
● Array 1, Array 2
When the array is not specified, the default settings will be applied. The default settings
only use one array, array 2 will be specified as 0.
When array is required, the number of array element 1 and the number of array element 2
need to be specified. The value set for array1 is the number of array element for array1 and
the value set for array2 is the number of array element for array2. If only array1 is required,
the array1 may be specified from 1 to 999 and the array2 may be specified as 0.
The total number of data may be arrayed is 10000 or less. The area for the specified data
size varies with FCS database types.

● Comment
The comment may be defined with up to 16 alphanumeric characters or 8 double-byte
characters. Comment can be omitted.
When comment is defined, the comment will be displayed on the tuning window for the
data item instead of the data item name.
● Engineering Unit Symbol

The engineering unit may be defined with up to 6 alphanumeric characters or 3 double-byte
characters.
● Security Level
The data item may be specified with a security level from 1 to 8.
SEE ALSO
For details on data item’s security level, refer to “■ Security Levels” in F9.4, “Function Block Security.”
● Display Format
The number of digits to be displayed on the tuning window may be specified. The actual
display varies with data types.
For I16 and I32 data type, the integer part digits may be specified.
For F32 and F64 data type, the number of digits for integer part and fraction part may be
specified. For example 7.1 means 7 digits for the whole string and 1 digit for the fraction
after decimal point.
CHR* means the data is a character string with a number of * characters.

● Entry Method
Data entry method may be specified. There are 4 types of data entry methods.
When setting menu label, menu data and menu number, the labels for displaying on menu
need to be defined on Menu Data Definition dialog box.
TIP
Menu Data Definition dialog box can be opened from [Tools] menu on Function Block Detail Builder.
• Direct Input
A datum may directly be entered on the tuning window to the data item.
• Menu Label
The label for the menu display may be entered as a datum. A menu label must be a
datum with CHR2 to CHR16 data type.
The selected menu label can be input as a datum.

Menu dialog
UT100.DT01 Tuning window
TANK A Temperature = 240 C

TANK B
TANK C
TANK D
Destination = TANK C
OK Cancel
D060305E.EPS
Figure Using Menu Label for Data Entry
• Menu Data
A datum displayed to the corresponding data item on the menu may be entered.
Label Data
A1 12.5
The selected menu data can be input as a datum. A2 25.0
Menu dialog A3 37.5
Tuning window A4 50.0
UT100.DT01
A1 Temperature = 240 C
A2
A3
A4
Level = 37.5
OK Cancel
D060306E.EPS
Figure Using Menu Data for Data Entry

• Menu Number
The relative number (1 to 64) displayed for the menu label on the menu dialog box
may be entered as a datum. A menu number must be a datum with I16 or I32 data
type.
The selected menu number can be input as a datum.

Menu dialog
UT100.DT01 Tuning window
10 Temperature = 240 C
20
30
40
Lot number = 30
OK Cancel
D060307E.EPS
Figure Using Menu Number for Data Entry
● Display Position
The display position of the data item on the tuning window may be specified. It may be
selected from AUTO, NONE, Column1 and Column2.
When choosing AUTO, the data item will be automatically placed to an idle position start
from the column 1.
When Column1 or Column2 is selected, the Line (horizontal position) needs to be speci-
fied.
● Line
When Column1 or Column2 is selected as display position, the line position (from 3 to 150)
may be specified.
● Check
The method to check the entered data may be specified. There are methods provided by
the system and the methods that may be specified by users. When using the user specified
methods, the high and low limits need to be defined.
Moreover, the user specified method, I.e., when the [Check] column is specified with [User
Definition], profiler only allow the I16 and I32 data types for data entry.
● High Limit, Low Limit

The range (High limit, Low Limit) for entered data may be specified.
In the [Check] column, only when “User definition” or “User definition with Acknowledg-
ment” is specified, this range is valid.

D6.3.4 Data Items for Process Management

Data items for Process Management refer to a data item group in which data for
Process Management can be set when a unit instrument operates under the control
of Process Management.
■ System Fixed Data Items for Process Management

Listed in the table below are the unit instrument data items may be used by Process Man-
agement.
When the nonresident unit instrument operates under the control of Process Management,
the Process Management data can be set in the unit instrument data items shown in the
table below at the time the unit instrument starts (when the unit recipe procedure starts).
After the unit instrument is started, USER 1 through USER 4 are overwritten as formula
data for the recipe, but even if these values are changed, they are not reflected in the unit
instrument data.
The data set in the unit instrument when the unit instrument started will be cleared after the
unit instrument is ended (status of the unit instrument becomes END).
Table Data Items for Process Management
Data item name Data name Data type Entry Default
BATCHID Batch ID CHR*16 - null
USER1 User code 1 CHR*16 - null
RECIPEGR Recipe group number I16 - 0
RECIPE Recipe name CHR*16 - null
PARTNO Unit recipe number I16 - 0
D060308E.EPS
-: Entry not possible

■ User Definable Data Items may be Applied to Process Management
Among the user definable data items, the following items are provided with unique func-
tions.
● RESERVED Batch ID (RP_QUEUE[ ])

For the RESERVED Batch ID, the reserved recipe’s batch ID and the first queued unit
name are stored. The RESERVED Batch ID may be used when using SEBOL to download
a recipe or start a recipe.
When using Batch ID, it is required to define the array data item for the unit instrument, and
to specify the destination tag name to be set to the RESERVED Batch ID, on the Process
Management Configuration Builder for each recipe group, or to define the destination tag
name to be set to the RESERVED Batch ID.
After loading the recipe, the status of the recipe will change from RESERVED to READY.
The Batch ID and the Unit name will be removed from the QUEUE. The RESERVED Batch
IDs are stored in the order of the time they were reserved. When the number of RESERVED
Batch ID queued is more than array elements after recipe setup, the new batch ID and unit
name can not be stored as RESERVED Batch ID. However, after deleting a batch ID from
the array and load the recipe, a new batch ID can be added to the end of the array.
The RESERVED batch ID may be defined on the unit instrument user definable data items
as follows.
Data Item Name: RP_QUEUE (may be modified)
Data Type: CHR16
Array1: 10
Array2: 2
Display Format: 16
● To be Executed Batch ID (BIDQUEUE[ ])

For the To be Executed Batch ID (BIDQUEUE), the unit recipe whose status changed to
READY is stored.
When using the To be Executed Batch ID, it is required to define the array data item for the
unit instrument.
When the number of batch ID reguired is greater than number of array element, the old
batch ID will be deserted in FIFO manner. Furthermore, when a unit starts running, the
active Batch ID will be deleted from the queue of BIDQUEUE.
The To be Executed Batch ID may be defined on the unit instrument user definable data
items as follows.
Data Item Name: BIDQUEUE
Data Type: CHR16
Array1: 10
Array2: 0
Display Format: 16

D6.3.5 Accessing Unit Data

Unit instrument data items can be accessed from other function blocks or faceplate
blocks for referencing or setting.
■ Accessing Unit Instrument Data Items from Other Function Blocks

The operations started from unit instrument can access all data items of the unit
instrument’s data items.
When accessing unit instrument data items from the function blocks which are not con-
trolled by the unit subject to the following restrictions:
● Accessing from Function Blocks Other Than SFC Blocks

Among all unit instrument data items, only the system-fixed data items can be connected to
the function blocks with data connection or sequence connection.
● Accessing from Sequence Table Blocks

the sequence table blocks with sequence connection by entering the item into the condition
or operation column of the sequence table.
● Accessing from Logic Chart Blocks

the logic chart blocks with sequence connection by entering item as a condition or an
operation symbol in the logic chart.
● Accessing from General-Purpose Calculation Blocks (CALCU, CALCU-C)

Among all unit instrument data items, only the system-fixed data items can be used in
CALCU, CALCU-C calculation blocks in the format of [<TagName>.<DataItem>] as a
variable in the calculation.
● Accessing from SFC Blocks

All unit instrument data items are accessible from SEBOL programs in SFC blocks.

■ Accessing Unit Instrument Data Items from Faceplates
There are one analog type faceplates and two switch types faceplates may be applied for
unit instruments.
These faceplates may be applied to 6 kinds of unit instruments. Using the push buttons or
switches on the faceplate may send status manipulation commands to the unit instruments.
When sending a status change command to a nonresident unit instrument, if the unit
procedure does not exist, an error will occur.
The example of the faceplate displays for unit instruments are shown as follows.
UT0101 UT0102 UT0103

REACTOR-1 REACTOR-2 REACTOR-3
AUT END AUT END AUT END

NR NR NR
PV
0.0
SV
0.0
MV %
0.0
100.0
START START START
80.0
PAUSE PAUSE
60.0
RESTART RESTART PAUSE

40.0
SUSPEND SUSPEND
20.0
END END RESTART

0.0
_UTAS _UTPB _UTSW

_UTAS - N _UTPB - N _UTSW - N
D060309E.EPS
Figure Unit Instrument Faceplates
SEE ALSO
For details on status change commands, refer to D6.5.4, “Unit Mode and Unit Status Change Command.”

● Analog Unit Instrument Faceplate
This type of faceplate may be applied to the unit instrument with _UTAS or _UTAS-N model
name. The default status change commands assigned to the pushbuttons of the faceplate
are as follows. The status change commands in the State Transition Matrix can be user-
defined to the pushbuttons.
SWLB[1] (START): PSTART
SWLB[2] (PAUSE): PAUSE
SWLB[3] (RESTART): RESTART
SWLB[4] (SUSPEND): SUSPEND
SWLB[5] (END): END
● Five-Pushbutton type Unit Instrument Faceplate

This type of faceplate may be applied to the unit instrument with _UTPB or _UTPB-N
model name. The default status change commands assigned to the pushbuttons of the
faceplate are as follows. The status change commands in the State Transition Matrix can
be user-defined to the pushbuttons.
SWLB[1] (START): PSTART
SWLB[2] (PAUSE): PAUSE
SWLB[3] (RESTART): RESTART
SWLB[4] (SUSPEND): SUSPEND
SWLB[5] (END): END
● Three-Position Switch Type Unit Instrument Faceplate

This type of faceplate may be applied to the unit instrument with _UTSW or _UTSW-N
model name. The default status change commands assigned to the push buttons of the
faceplate are as follows. The status change commands in the State Transition Matrix can
be user-defined to the pushbuttons.
Label position 1 (START): PSTART
Label position 2 (PAUSE): PAUSE
Label position 3 (RESTART): RESTART

<Toc> <Ind> <D6.4 Unit Procedure> D6-32
D6.4 Unit Procedure

The unit procedure controls the modules grouped in a unit for the production pro-
cess assigned to the unit.
■ Positioning of Unit Procedure

▼ Unit Procedure
A unit procedure consists of more than one operations executed according to the unit
procedure defined for a unit. Execution time is automatically shared when more than one
operations required to be executed in parallel.
A unit procedure can be described using the sequential function chart (SFC) designed for
the purpose. The positioning of a unit procedure is shown below:
Operation SEBOL
(SFC Type)
Unit
Initialization
Unit procedure (SFC)
Sequence table
Charging
Y
Initial step Termination N
Charging 1
Logic chart
Agitation
Charging 2
Heating
Operation
(SEBOL Type)
SEBOL
D060401E.EPS
Figure Positioning of Unit Procedure

D6.4.1 Unit Procedure SFC

A sequential function chart (SFC) for describing unit procedures represent the
running orders of operating procedures and multiple operations in a unit instrument.
The name or generic name of an operation can be registered as a step action of in
the unit procedure SFC.
■ Composition of Unit Procedure

Operation names or operation generic names may be described in the action column of
each SFC step. The operations are executed according to the step sequence.
An example of unit-procedure composition is shown below:
Unit procedure Operation
01 Initial step
02 Charging Operation (OPSBL)
Step
03 Heating 04 Agitation
Action
or
05 Analyzing
Operation (OPSFC)
06 Discharging 1 07 Discharging 2
08 Washing
09 Termination
D060402E.EPS
Figure Composition of Unit Procedure SFC
In the above example, the steps are executed successively as described. The heating and
agitation steps are executed simultaneously.

■ Basic Unit Procedure Elements
The unit procedure SFC uses the following basic elements:
• Step: Describes action.
• Transition: Describes transition condition.
• Connection: Connects a step to transition, and transition to a step.
Table Unit Procedure SFC Basic Elements

Element Name Symbol Remarks
Double height initialization step is also
Initial Step
available.
Step Step Double height step is also available.
Wait Step Only available with unit procedure SFC
Selective Seq.-Split
Selective Seq.-Join
Parallel-Start Only available with unit procedure SFC
Parallel-End Only available with unit procedure SFC
Loop-Branch
Link
Loop-Join
Jump Down Jnn nn: numerals
Jump Up Jnn nn: numerals
Jump To Jnn nn: numerals
Link
D060403E.EPS
These elements are applicable to all SFC blocks, however the three elements below are
only applicable to the unit procedures.
• Wait Step
• Parallel-Start
• Parallel-End

■ Unit Procedure SFC Steps
The square in the step is for placing the step number (01 to 99).
The unit-procedure SFC step is scripted with its step number indicated in a square and its
action in a rectangle shown to the right of the step number square. When the step is acti-
vated, the operation identified by its tagname in the action box is started. The operation tag
name or the operation generic name may be put into the action column.
When using the operation generic name, it is necessary to define tag names to the corre-
sponding operation generic names on the function block detail builder.
Step number Action box
10
D060404E.EPS
Figure SFC Step
Every step is either in the active state, in which the step is being executed, or the inactive
state, in which the step has been completed or is yet to be executed.
TIP
A maximum number of steps can be described in one column is 50. With parallel, transition, and jump
sequences, up to 99 steps can be described in one SFC.
● Step Action
The step action is the process executed when the step is active. For a unit-procedure SFC
step, the process is the operation defined in the action box. When execution of the action or
operation is completed, the step is inactivated and processing is shifted to the next step
according to the connection of the step.
TIP
When a comment is entered when defining the steps properties, the comment may be displayed in the
action column of the SFC window displayed on a HIS.

● Initial Step
The initial step is the first step to be executed in a unit procedure. The step number in this
case is shown in a double square, however, the basic function of this step is the same as
other steps.
01 Initialization
D060405E.EPS
Figure Initial Step
● Wait Step
The wait step is a step which is not defined for any action in a unit procedure. It is used
when synchronization with another step is required, for example. When this step is acti-
vated, it is completed without executing any action and then inactivated.
05
D060406E.EPS
Figure Wait Step
■ SFC Transition
Transition is shown with a short horizontal line crossing the step-connecting link. Transition
defines the condition of transition using a logical expression. Execution advances to the
linked step when the result of the expression is true. If the transition condition is not estab-
lished, the check for the condition will continue at each basic cycle.
The transition condition will be parsed as soon as the previous step operation is completed.
Transition
06
07
D060407E.EPS
Figure SFC Transition

■ SFC Links
Link elements, which are vertical or horizontal lines connecting unit-procedure steps and
transitions, indicating the execution order or path of steps. Examples of their use are shown
below:
Link

Ordinary link Selective Sequence
Split & Join
Parallel Start
Loop Join
Loop Branch
Parallel-Join
Loop Branch & Loop Join Parallel Start & End
Jump To
J2 Jump Down
J1
J2
Jump Up
Jump To
J1
Jump Up Jump Down

D060408E.EPS
Figure Connection Elements

■ SFC Execution Order
An SFC-described unit procedure is executed in the following order:
1. As soon as the execution of a unit procedure is started, the initial step is activated.
2. The operation described in the action box is started when the step is activated.
3. The step is deactivated when the execution of the operation is completed.
4. One of the following processes starts when the step has been inactivated:
• When the linked destination is a step
The step will be activated.
• When the linked destination is a transition
The transition condition is evaluated, when the result of the evaluation is true, the
linked step will be activated.
If the transition condition is not established, the check for the conditions will continue
at each basic cycle.

D6.4.2 Compound Sequence

A compound sequence is composed of a number of laterally described sequences.
A selective sequence and a simultaneous sequence are compound sequences.
In the selective sequence, a step is selected for execution according to the defined
transition conditions. In the simultaneous sequence, more than one operation are
executed simultaneously.
In the case of executing a step by switching among the multiple choices according to
transition condition, the selective sequence may be applied. For one selective sequence,
eight choices may be set in parallel.
An example of selective sequence is shown as follows.
05
06 07 08
Selective sequence
09
10
D060409E.EPS
Figure A Selective Sequence
In the above example, the three laterally linked transition conditions are evaluated from the
left when step 05 has been completed and inactivated. If one of the conditions is true, the
step linked to that transition is activated. If there are two or more true conditions, the one on
the left has priority over the others.
If none of the conditions is true, the evaluation will be repeated at every basic scan period
until one of the conditions becomes true.

■ Parallel Sequence
A Parallel sequence is used when it is required to execute multiple sequences simulta-
neously. The parallel sequence is indicated with a double-line. The steps described below
and in parallel with the double-line are activated for simultaneous execution. The sequence
returns to the original sequence upon completion of the execution, which is indicated again
with a double-line.
05
06 07 08
Simultaneous
sequence
09
10
D060410E.EPS
Figure A Parallel Sequence
The transition condition for the parallel sequence will not be evaluated until all the steps in
the sequence are completed.
A slash (/) can be used as a special processing to end parallel sequences. When it is
described in the transition condition, if any one of the parallel operations finishes executing,
a STOP change instruction is sent to the other operation being simultaneously executed
and the control moves to the next step.
TIP
Parallel sequence is only available in unit procedure SFC.

● Notice on Using Parallel Sequence
The Parallel sequence has the following conditions for its use:
• Up to eight steps can be described in one Parallel sequence.
• Up to 32 steps can be executed simultaneously including nested Parallel sequences.
• Up to three Parallel sequences can be nested in one parallel sequence. System alarm
will be invoked if the sequence is nested to four levels.
An example of nested Parallel sequences is shown below:
05
06 07
Nested parallel
08 09 10 sequences
11
12
D060411E.EPS
Figure Nested Parallel Sequences

D6.4.3 Transition Conditions

The logical expressions which can be described as transition conditions are ex-
plained.
■ Logical Expression
The logical expression can be described in one line composed of the left-hand side data,
an operator, and the right-hand side data.
%SW1000.PV == 1
Left Operator Right

D060412E.EPS
Figure Transition Conditional Expression
■ Left-Hand Side Data

One of the following data items can be used on the left-hand side:
• Unit instrument data
• Function block data
• Common block data
The unit instrument data and the function block data running in other control stations can
not be used as the transition condition.
However, the common block data may be used as the transition condition in the recipe unit
procedure applied as a nonresident unit instrument procedure.
SEE ALSO
For details on unit recipe procedure, refer to “■ Recipe Unit Procedure” in G2.1.2, “Procedure.”
■ Operators
One of the following operators can be used:
Table Logical Expression Operators
Operator Description
== True if left and right side are equal. False if not equal.
<> True if left and right side are not equal. False if equal.
< True if right side is larger than left side. False if not.
<= True if right side is larger than or equal to left side. False if not.
> True if right side is smaller than left side. False if not.
>= True if right side is smaller than or equal to left side. False if not.
D060413E.EPS

■ Right-Hand Side Data
One of the following data items or constants can be used on the right-hand side:
• Unit instrument data
• Function block data
• Common block data
• Constants
The unit instrument data and the function block data running in other control stations can
not be used as the transition condition.
However, the common block data may be used as the transition condition in the recipe unit
procedure applied as a nonresident unit instrument procedure.
SEE ALSO
For details on unit recipe procedure, refer to “■ Recipe Unit Procedure” in G2.1.2, “Procedure.”
■ Left- & Right-Hand Side Scripts

Table Left- & Right-Hand Side Scripts
Data Format Remarks
<unit name>.<data item>
%%.<data item> Present-unit data
Unit instrument data
$<generic name>.<data item>
<generic name array>[constant].<data item>
<tagname>.<data item> Operations included.
Function block data $<generic name>.<data item>
$<generic name array>[constant].<data item>
Common block data #<common block name>.<data item>
Numeric data nnnn.nn or nnnn Constant cannot be
Constants
Character-string data "cccc" used at left side.
D060414E.EPS
● Special Processing Specification

A slash (/) is used in the transition condition for a parallel sequence join.
No character string can be scripted following the slash.
When the condition contains a slash, the STOP command is sent to the other operations
being executed in the parallel sequence as soon as one of the parallel operations is com-
pleted, and execution advances to the next step when the operation status changes to
STOP. In the normal parallel sequence join, for which the slash is not used, the transition
condition is not evaluated until all parallel operations are completed.
If the operation status cannot be changed because it is determined not permissible in the
pre-processing for the status change command, the command will be sent at every basic
scan period until the change is permitted.

■ Examples of Transition Condition
Examples of describing transition conditions are shown below:
● Example 1
In this example, the condition is true if unit data STEPNO of the present unit is smaller than
or equal to 10:
%%.STEPNO<=10
● Example 2
In this example, the condition is true if unit data MODE of the present unit is equal to
character-string AUT:
%%.MODE=="AUT"
■ Comparison of Data in Transition Condition

The following should be noted regarding the comparison of data performed in transition
conditions:
● Comparison of Numeric & Character-String Data

An error message will be generated by transition condition check if comparing a character
string to a numeric value in transition condition.
● Comparison of Floating-Point Data

Floating-point data contain very small errors because of calculation accuracy, and they
could actually be different internally even if two units of floating-point data are apparently
the same. So their comparison could be determined false when they are compared using
(==) or (<>).
It is recommended to use (>=) or (<=) for comparing floating-point data instead of (==) or
(<>).

D6.4.4 Interrupt Processing of Unit Procedure

The interrupt processing of a unit instrument may start upon a mode change or
status change or an event signal. When an interruption event occurs, the normal
process procedure is interrupted, and the interrupt processing will be executed.
An interrupt processing of unit instrument may be created by defining it as an event
signal processing in an operation or a monitoring operation.
■ Interrupt Processing for Unit Mode/Status Changes

The interrupt processing can not be programmed in the unit procedure scripts but can be
put in the operations started by the unit procedure as for unit instrument mode and status
change interrupt processing.
When the interrupt processing for the mode and status change gives an error return, the
mode and status change command may end with an error.
Table Interrupt Processing for Mode/status Changes
Execution status Operation Monitoring operation
Step activated Interrupt processing executed. Interrupt processing executed.
Evaluation of transition condition Interrupt processing not executed. Interrupt processing executed.
Stopped at start of step Interrupt processing not executed. Interrupt processing executed.
D060415E.EPS
For a unit procedure-started operation, interrupt processing can be executed only when the
operation is being executed. It is thus necessary to describe interrupt processing according
to the action of the operation involved.
For a monitoring operation, interrupt processing can be executed anytime. It is thus neces-
sary to describe interrupt processing according to the action of the unit instrument.
SEE ALSO
For details on state transition matrix, refer to D6.6, “State Transition Matrix.”

■ Interrupt Processing upon a Signal
When sending a signal to a unit instrument, the unit instrument passes the signal to the
operation started from the unit procedure of the unit instrument.
An operation started from unit procedure accepts signals only when it is being executed.
However, a monitoring operation accepts signals at all times.
If more than one operations are being executed, the signal will be sent to all of them. Since
the unit instrument has no signal queue, it cannot keep the received signals for waiting. An
operation can hold the signal sent to it in QUEUE [5] data item.
SEE ALSO
See D6.14.1, “Queue Signal Processing” for the details on the interrupt processing upon a signal.

D6.4.5 Unit Procedure Sharing

Normally, one unit procedure is assigned to one unit instrument.
When multiple unit instruments corresponding to the same type of equipment entity
which have the same control sequence, unit procedures may be shared.
■ What is Unit Procedure Sharing

▼ Sharing a Unit Procedure
One unit procedure can be shared by multiple unit instruments.
Unit procedure sharing means to allow multiple unit instruments with the same control
algorithm to share the same unit procedure.
For an example, if one unit procedure is shared by 3 unit instruments, only one unit proce-
dure will be prepared for three unit instruments on the FCS, so that it reduces the unit
procedure process memory use to 1/3 of the original. When modifying one unit procedure,
all the unit instruments’ procedures will be changed together.
However, the shared unit procedure can be modified only when the procedure is no used
by any of the unit instruments.

■ Sharing a Unit Procedure
The shared unit procedure may be created on FCS sequence library builder. The name of
the created unit procedure may be defined on the Function Block Detail Builder.
In the action column of the shared unit procedure, the tag name of the operation or the
generic name of the operation may be specified.
When the generic name of the operation is used, the generic name of the operation used
by unit instrument corresponds the tag name of the actually used operation. For one unit
instrument, up to 99 generic names for operations may be specified.
Moreover, the transition condition for unit instrument or the tag generic names in the unit
instrument may be used. When using the tag generic names, the tag generic names in the
unit instrument corresponding to the actually used tag names may be defined.
SEE ALSO
For details on FCS sequence library, refer to F8, “FCS Sequence Library.”
■ Operation Generic Name Definition Items

▼ Operation Generic Name
The definition items for operation generic names are shown as follows.
● Operation Generic Name

The operation generic name may be specified in the action column of the unit procedure in
the FCS sequence library. An operation generic name may be defined with up to 8 alphanu-
meric characters.
● Tag Name
Corresponding to the operation’s generic name, the actually used tag name for the opera-
tion may be specified.

■ Example of Sharing a Unit Procedure
The sharing of a unit procedure is explained using the following diagram as an example. In
the example, unit instruments A and B share unit procedure X. In unit procedure X, the
generic operation names “OP001” and “OP002” are described as the startup operation
names. Unit instrument A has a correspondence table between the generic operation
names and tag names for unit instrument A, and unit instrument B has a correspondence
table between the generic operation names and tag names for unit instrument B. When unit
procedure X operates as a unit procedure for unit instrument A, generic operation names
“OP001” and “OP002” reference the correspondence table and are converted to tag names
“ABC1” and “XYZ1,” then operations ABC1 and XYZ1 will start in succession. When unit
procedure X operates as a unit procedure for unit instrument B, generic operation names
“OP001” and “OP002” use the correspondence table to convert themselves to tag numbers
“ABC2” and “XYZ2,” then operations ABC2 and XYZ2 will start in succession.
Unit instrument A
Operation generic name Tag name

OP001 ABC1
OP002 XYZ1
FCS Sequence library

Unit procedure X Operation
Unit procedure X ABC1
3 OP001
3 OP001 Sharing
4 OP002
4 OP002 Operation
XYZ1
Unit instrument B
Operation generic name Tag name

OP001 ABC2
OP002 XYZ2
Unit procedure X Operation

ABC2
3 OP001
Sharing
4 OP002
Operation
XYZ2
D060416E.EPS
Figure Sharing a Unit Procedure

<Toc> <Ind> <D6.5 Unit Mode and Unit Status> D6-50
D6.5 Unit Mode and Unit Status

The block mode of units is called unit mode, and the block status of units is called
unit status.
The block mode change or status change command may change the control state or
running state of a unit instrument.

D6.5.1 Unit Mode

Unit mode indicates the control status in the unit instrument’s running state. When a
command for changing the unit instrument mode is given, the behaviors of the unit
procedure and operation may be changed.
■ Available Modes
▼ Unit Mode
Available unit modes, which are system-specific, are shown below:
● Out-of-Service (O/S) Mode

The execution of the unit, including initialization and monitoring operations, is completely
stopped in this mode for the purpose of maintenance, etc.
Transition to O/S mode is possible only when the unit is in the completed (END) or aborted
(ABRT) status. The other statuses may cause errors. Transition to the O/S mode is completely
stopped the unit for the purpose of the maintenance, etc.
● Manual (MAN) Mode

The unit procedure cannot be run in this mode.
● Semi-Automatic (SEMI) Mode

The operation of each unit-procedure step is automatically executed in this mode but
stopped for manual transition to the next step.
● Automatic (AUT) Mode

The operations of all unit-procedure steps are automatically transited in this mode. It
indicating the unit is in automatic unit execution.

D6.5.2 Unit Status

The unit status indicates the running state of a unit instrument (running state of a
unit procedure).
■ Default Unit Status

▼ Default Unit Status
There are following types of system-fixed unit status.
User-defined status character strings in column USER2 of block status file are applied as
the default character strings for unit status display.
● END
Execution of unit procedure completed.
● ABORTED
Unit procedure execution aborted.
● RUNNING
Unit procedure being executed.
● SUSPEND
Unit procedure execution suspended at the start of a step.
● PAUSED
Execution of operation paused at the start of a phase.
■ User-Defined Unit Status

▼ User-Defined Unit Status, USER 2 to 8 (Unit Instrument)
The character strings for user-defined unit status can be specified in tables of USER2 to
USER8 in the Block Status Character String builder.
The user-defined status character strings (USER2 to USER8) can be used only when they
are designated in State Transition Matrix builder. In this State Transition Matrix builder, the
character strings defined in the table at the position 4 to 17 and 23 can be used.
The character string [ABORTED] at the table position 4 and the character string [END] at
the table position 23 can not be changed. User can define the character strings for the table
position 5 to 17.
A character string for the status can be defined using up to 8 alphanumeric characters
including underscore ( _ ) started with an alphabet letter.
IMPORTANT
When character string table USER2 is modified, the default State Transition Matrix (Ma-
trix1) will change its action accordingly.

D6.5.3 Unit Sub-Status

Unit sub-status is provided to indicate more detailed running state under each unit
status.
■ Type of Sub-Status
Unit sub-status is an auxiliary information to indicate more detailed running state under a
unit status.
The unit substatus and the unit status have the following relationship.
Table Unit Status and Unit Sub-Status
Unit Status Substatus Description
CNCT Waiting for starting of unit procedure execution.
NOCNCT No unit procedure available.
END
INIT Initialization being executed.
INIR Interrupt processing being executed.
USER User-aborted state.
ABORTED
SYSTEM System-aborted state.
RUNNING INTR Interrupt processing being executed.
INTR Interrupt processing being executed.
SUSPEND
CKTR Transition condition being evaluated.
PAUSED INTR Interrupt processing being executed.
D060501E.EPS

D6.5.4 Unit Mode and Unit Status Change Command

The unit instrument can receive operation commands from the operation and moni-
toring consoles, sequence table or logic chart, other units and actions such as
emergency stop caused by equipment failure, as a unit mode change command or
unit status change command.
Unit Mode/Unit Status change commands

Operation & monitoring console
Sequence table Unit instrument

Logic chart
Another unit instrument
D060502E.EPS
Figure Unit Mode/Unit Status Change Commands Sent to Unit
■ Unit Mode Change Commands

▼ Mode Change Commands
Available unit-mode change commands, which are also system-fixed, are described below:
● AUT
Transition to the automatic mode.
● SEMI
Transition to the semi-automatic mode.
● MAN
Transition to the manual mode.
● O/S
Transition to the out-of-service mode.

■ System-Fixed Unit Status Change Commands
▼ System-Fixed Unit Status Change Commands, Status Change Commands, Directives to Change
the Status
Available unit status change commands are described below:
Table Unit Status Change Commands
Execution
Symbol Command Description
level
PSTART Start command Starts unit procedure. Low
RESTART Restart command Restarts suspended/paused unit procedure. Low
END End command Terminates unit-procedure execution. Low
Forcibly terminates unit execution.
ABORT Abort command High
(Unit Status interrupt processing cannot be described).
SUSPEND Suspend command Suspends execution of unit-procedure step. Low
PAUSE Pause command Pauses execution of unit-procedure operation phase. Low
RESET Reset command Resets aborted status. Low
MSTART Monitoring-start command Restarts monitoring operation. High
Stops execution at the start of next step in SEMI mode.
SCOMP (*1) Step end command Low
Changes steps when the unit is stopped.
STEP (*1) Step change command Low
EXECERR Stops execution at the start of step when error is caused during
Execution error command High
(*1) operation.
D060503E.EPS
*1: SCOMP, STEP, and EXECERR commands are system-initiated (see below), user cannot issue the commands.

The MSTART command and system-initiated SCOMP, STEP, and EXECERR commands
are described below:
● MSTART Change Command

This command restarts the monitoring operation when it has been stopped for some
reason. The monitoring operation is normally kept being executed regardless of unit status.
When the monitoring operation stops, MSTART command may be issued to restart it.
● SCOMP Change Command

This is a status change command issued by the system. The users are not allowed to issue
this command.
The SCOMP change command is a change command that creates a pause between steps
when the mode is semi-automatic (SEMI).
When the block mode is in semi-automatic (SEMI), the system issues an SCOMP change
command each time an SFC step of the unit procedure and the transition in connection
with that step have been executed. When an SCOMP change command is issued, the unit
suspends execution at the start of the next step according to the status transition matrix.
● STEP Change Command

When performing batch stepping of unit procedure SFC, a step change is executed by
setting the step number of the stepping target in the STEPNO data item and instructing a
STEP change. When a STEP change command is received, the unit executes the process
stepping according to the status transition matrix.
● EXECERR Change Command

This is a status change command issued by the system. The users are not allowed to issue
this command.
When the unit procedure starts an operation, there are times when the operation is in the
middle of maintenance or being started by another unit procedure. In this case, the
EXECERR change command is issued. When the EXECERR change command is re-
ceived, the unit enters the pause state according to the status transition matrix.

■ User-Defined Status Change Commands
▼ User-Defined Status Change Commands, CUSER1 to CUSER8
The character strings for user-defined status change commands can be specified in tables
of CUSER1 to CUSER8 in Status Change Command Character String builder.
The user-defined status change command character strings (CUSER1 to CUSER8) can be
used only when they are designated in State Transition Matrix builder.
A character string for a status change command can be defined using up to 8 alphanumeric
characters including underscore ( _ ) started with an alphabet letter. The identical character
strings can not defined in the same table. The reserved strings [RUN], [STOP] and [PAUS]
can not be defined.
The following default character strings for status changes commands can not be changed
by user.
String Number 1 PSTART
String Number 2 STEP
String Number 3 SCOMP
String Number 4 EXECERR
String Number 21 MSTART
String Number 22 ABORT
IMPORTANT
When character string table CUSER1 is modified, the default State Transition Matrix
(Matrix1) will change its action accordingly.
■ Start Action
▼ Start Action
The action for FCS initialization start or unit stop (Unit mode changes to END) may be
defined. The start action of a unit include 3 types, they are “Manual Start,” “Auto Start” or
“Auto Start when FCS initialization start.”
• Auto Start
When Auto Start is defined, the unit is automatically start the PSTART command when
the unit status changes to END.
• Manual Start
When Manual Start is defined, the unit does not send PSTART command when the
unit status changes to END. The PSTART command has to be manually send to start
the unit.
• Auto Start when FCS initialization start
When Auto Start when FCS initialization start is defined, the PSTART command is
sent when the FCS initialization start.

■ Unit Procedure Step Jump
When a unit procedure’s unit is in SUSPEND status, it is possible to jump its sequence to a
designated step. Step jump means a unit procedure to transit to a desired step for execu-
tion, either forward or backward is allowed. There two ways to set the unit into SUSPEND
status, by setting the unit into Semi-automatic (SEMI) mode or by sending a command for
changing to SUSPEND status methods.
To perform step jump, first to set the unit into SUSPEND status, then perform a step jump
on the SFC window, then send a RESTART command to the unit. After the above opera-
tions, the unit starts its execution from the jumped step.
In a unit procedure, multiple steps may be executed in parallel. It is possible to jump to a
step which is one of the parallel steps but only the jumped step is activated. If there two
steps running in parallel, after the step jump, only one step starts running, the other step is
not. In the case like this, it is required to jump to another step again.

■ Receiving Status Change Command
When unit instrument receives a mode/status change command, the feasibility of changing
to the mode or status is checked by the unit instrument according to the status transition
matrix.
It will give an error return when the check result is negative.
If the change is permitted, all the running operations under the management of the unit will
execute the mode change or status change commands following the unit mode and status
change.
For operations, the interrupt processing programs should be prepared in advance, so that
when an operation is interrupted by a mode change or status change command, the
prepared processing can be executed accordingly.
Mode/status change
command processing starts.
Has any previous change No

command been completed?
Yes
Yes Is execution-level high?
No
No
Is the change feasible according
to status transition matrix?
Yes
No
The command is notified to Is the change feasible according
unit's operations. to status transition matrix?
Yes
Is change-command No
pre-processing normal?
1
1 Yes
The change is made. Error signal is returned.
Normal termination
signal is returned.
Command processing
completed.
D060504E.EPS
Figure Receiving Processing of Mode/Status Change Command
SEE ALSO
Refer to D6.6, “State Transition Matrix,” for the details of the state transition matrix.

■ Errors Caused by Change Commands
The errors caused when a unit mode/status change command is denied are described
below.
● Transition Error
Error is caused if the change command is not defined in the status transition matrix.
● Previous Change Command being Processed

Error may be caused if a new change command is received while a previously received
change command is still being processed.
The change commands classified as high execution-level commands have priority over the
low execution-level commands. Error is caused if the previously received command has
not been completed when its level is the same as the newly received command. When a
high-level change command is received during processing of a low-level command, the
newly received command is accepted for processing.
Table Processing According to Command Levels
State Low-level command received High-level command received
Previous command completed Accepted. Accepted.
Low-level command being processed Error caused. Accepted.
High-level command being processed Error caused. Error caused.
D060505E.EPS

■ Completion of Change Command Processing
The completion of the mode or status change command means the running operation has
completed its mode and status change processing including the processing prior mode and
status change and the processing after the mode and status change.
● Completion of Pre-Processing
The pre-processing for a mode/status change command is a user-written interrupt pro-
gram. The feasibility of the change can be determined by this interrupt program. When no
interrupt program is described for pre-processing, it will be assumed that pre-processing
has been normally executed justifying the change.
● Completion of Post-Processing
The post-processing for a mode/status change command is also a user-created interrupt
program. It is executed after the change is made and any new mode/status change com-
mand is denied until the post-processing is completed. Error is caused if a new mode/
status change command is issued prior to the completion.
SEE ALSO
For details on the Status Change Pre-Process, or the details on the Status Change Post-Process, see
D6.14.2, “Status Change Processing.”

<Toc> <Ind> <D6.6 State Transition Matrix> D6-62
D6.6 State Transition Matrix

The status transition matrix determines transition action for unit mode/status
change commands and the actions. The unit instrument changes its mode and
status in accordance with the state transition matrix. A default standard transition
matrix and a user-defined transition matrix are available.
■ State Transition
The control status of a unit instrument is indicated by the unit mode. The running state of
the unit instrument is indicated by the unit status. The unit state transition means the unit
instrument transfers its mode or status to another mode or status.
The transition of the unit mode or unit status is initiated by the unit mode or unit status
change command. When the transition command is given, the unit instrument refers to the
state transition matrix to check if it is allowed to transit from the current mode or status to
the required mode or status.
■ Designation of State Transition Matrix

▼ State Transition Matrix
The table number of state transition matrix for the unit instrument should be designated.
The tables of Matrix1 to Matrix16 are available. Matrix1 is designated as the default setting.
The standard state transition should use Matrix1.

D6.6.1 Standard State Transition Matrix

How the standard state transition matrix, set as default, behaves will be explained in
this section.
■ Standard State Transition

How a unit instrument transit its state when it receives a mode change or a status change
command is decided in the State Transition Matrix. The state to be transited will be decided
according to the current unit status, unit mode and the command received.
When a unit instrument receives a transition command, it will follow the transition rules in
the State Transition Matrix to change to a new mode and new status. At the same time, the
unit instrument transmits the actions to running operations so as to control the running
state and controlling state of the operations and the unit instrument itself.
IMPORTANT
When using the standard state transition matrix, the contents defined in USER2 on State
Transition Matrix builder and the contents in CUSER1 on Status Change Command Char-
acter String builder can not be modified.

● Transition Feasibility when Unit Instrument in AUT Mode
END
RUNNING END
PSTART
ABORT
PAUSE
SUSPEND
RESTART RESTART END
SUSPEND
PAUSED SUSPEND
ABORT ABORT
RESET
ABORTED
D060601E.EPS
Figure Transition Feasibility when Unit Instrument in AUT Mode
● Transition Feasibility when Unit Instrument in SEMI Mode

END
RUNNING END
PSTART
ABORT
PAUSE
At start of
step execution
or SUSPEND
RESTART RESTART END
SUSPEND
PAUSED SUSPEND
ABORT ABORT
RESET
ABORTED
D060602E.EPS
Figure Transition Feasibility when Unit Instrument in SEMI Mode

● Transition Matrix for Mode Change Commands
The status transition matrix for mode change commands is shown below:
Table Transition Matrix for Mode Change Commands
Current Current Mode Change command

status mode AUT SEMI MAN
ABORTED AUT ABORTED, A, CONTN ABORTED, S, CONT ABORTED, M, CONT

SEMI ABORTED, A, CONT ABORTED, S,CONTN ABORTED, M, CONT
MAN ABORTED, A, CONT ABORTED, S,CONT ABORTED, M, CONTN
RUNNING AUT RUNNIN, A, CONTN RUNNING, S, CONT

SEMI RUNNIN, A, CONT RUNNING, S, CONTN
MAN
SUSPEND AUT SUSPEND, A,CONTN SUSPEND, S,CONT

SEMI SUSPEND, A,CONT SUSPEND, S,CONTN
MAN
PAUSED AUT PAUSED, A, CONTN PAUSED, S, CONT

SEMI PAUSED, A, CONT PAUSED, S, CONTN
MAN
END AUT END, A, CONTN END, S, CONT END, M, CONT

SEMI END, A, CONT END, S, CONTN END, M, CONT
MAN END, A, CONT END, S, CONT END, M, CONTN
D060603E.EPS
Data in the “mode change command” columns in the above table are from the left: “unit
status changed to,” “unit mode changed to,” and “action instruction for unit or operation” (A,
S, and M indicate AUT, SEMI, and MAN modes respectively). Blank cells indicate that
transition is not allowed.
● Note Points Regarding Mode Change Commands

The following points need to be noted in regarding unit instrument mode change com-
mands.
• The mode can be changed to MAN from any mode in the END or ABORTED status.
No unit procedure can be executed in the MAN mode and error is caused at any
attempt to change status.
• The mode can be changed to O/S from any mode in the END or ABORTED status. No
mode/status change commands are allowed in the O/S mode and error is caused at
any attempt while the END or ABORTED status is retained.

● Transition Matrix for Unit Status Change Commands
The status transition matrix for unit status change commands is shown below:
Table Transition Matrix for Unit Status Change Commands (1/3)
Current Current Status Change command

status mode PSTART STEP SCOMP
ABORTED AUT
SEMI
MAN
RUNNING AUT
SEMI SUSPEND, S, SUSP+
MAN
SUSPEND AUT SUSPEND, A, STEP

SEMI SUSPEND, S, STEP
MAN
PAUSE AUT
SEMI
MAN
END AUT RUNNING, A, STRA

SEMI RUNNING, A, STRA
MAN
D060604E.EPS
Data in the “status change command” columns in the above table are from the left: “unit


status mode EXECERR RESTART END
ABORTED AUT
SEMI
MAN
RUNNING AUT SUSPEND, A, SUSPA END, A, END

SEMI SUSPEND, S, SUSPA END, S, END
MAN
SUSPEND AUT SUSPEND, A, SUSPA RUNNING, A, RSMA END, A, END

SEMI SUSPEND, S, SUSPA RUNNING, S, RSMA END, S, END
MAN
PAUSED AUT SUSPEND, A, SUSPA RUNNING, A, RSMA END, A, END

SEMI SUSPEND, S, SUSPA RUNNING, S, RSMA END, S, END
MAN
END AUT
SEMI
MAN
D060605E.EPS


status mode SUSPEND PAUSE RESET
ABORTED AUT END, A, END

SEMI END, S, END
MAN END, M, END
RUNNING AUT SUSPEND, A, SUSPA PAUSED, A, PAUSA

SEMI SUSPEND, S, SUSPA PAUSED, S, PAUSA
MAN
SUSPEND AUT
SEMI
MAN
PAUSED AUT SUSPEND, A, SUSPA

SEMI SUSPEND, S, SUSPA
MAN
END AUT
SEMI
MAN
D060606E.EPS

■ Action Instructions for Unit Instrument or Operation
The action instructions for the unit instrument or operation following the unit mode or status
change commands are described as follows:
Table Action Instruction for Unit/Operation (1/2)
Symbol Action Operation
STRA Start Initial-step operation started (operation mode: AUT).
STRS Start Initial-step operation started (operation mode: SEMI).
STR Start Initial-step operation started.
Current-step operation started (operation mode: AUT).
RSMA Restart
RUN command sent to the operation.
Current-step operation started (operation mode: SEMI).
RSMS Restart
RUN command sent to the operation.
RSM Restart Current-step operation started. RUN command sent to the operation.
Processing started from current-step transition condition (operation mode: AUT).
RSMA+ Restart STOP command sent to current-step operation and processing started from current-step transition
condition.
RSMS+ Restart Processing started from current-step transition condition (operation mode: AUT).
RSM+ Restart Processing started from current-step transition condition.
Current-step operation restarted from start (operation mode: AUT).
RSMA- Restart STOP command sent to current-step operation and START command sent again after completion of the
operation.
RSMS- Restart Current-step operation restarted from start (operation mode: SEMI).
RSM- Restart Current-step operation restarted from start.
END End STOP command sent to all current operations.
ABRT Abort ABRT command sent to all current operations.
STOP command sent to all current operations (operation mode: AUT).
SUSPA Suspend
Stop position shifted to start of current step after completion of operation.
STOP command sent to all current operations (operation mode: SEMI).
SUSPS Suspend
Stop position shifted to start of current step after completion of operation.
STOP command sent to all current operations. Stop position shifted to start of current step after
SUSP Suspend
completion of operation.
STOP command sent to all current operations (operation mode: AUT).
SUSPA+ Suspend Step transition condition evaluated for current operation upon its completion and then execution stopped
at start of the next step when the condition is satisfied.
STOP command sent to all current operations (operation mode: SEMI).
SUSPS+ Suspend
Step transition condition evaluated for current operation upon its completion and then execution stopped.
STOP command sent to all current operations.
SUSP+ Suspend
Step transition condition evaluated for current operation upon its completion and then execution stopped.
D060607E.EPS

Table Action Instruction for Unit/Operation (2/2)
Phase PAUS command sent to all current operations.
PAUSA
pause Execution stopped at start of the current phase of operation (operation mode: AUT).
PAUSS
pause Execution stopped at start of the current phase of operation (operation mode: SEMI).
PAUS
pause Execution stopped at start of the current phase of operation.
CONTA Continue Current conditions and action continued (operation mode: AUT).
CONTS Continue Current conditions and action continued (operation mode: SEMI).
CONT Continue Current conditions and action continued.
CONTN Continue Current conditions and action continued (no interrupt processing).
Phase
STEP Step advanced to STEPNO-specified step.
advance
D060608E.EPS
IMPORTANT
If an action instruction suffixed with a (+) plus, such as SUSP+ and RSM+, is given and the
current-step transition condition is not satisfied, the condition will be maintained until the
condition is satisfied. Be sure to define a transition condition which never fails when de-
scribing it for a selective sequence.

■ Actions Invoked by Action Instructions
The actions of the unit or operation after having been instructed following mode/status
change commands are described below:
Table Actions Invoked by Action Instructions
Instruction Unit action Change-command interrupt processing Operation status Operation mode
STRA AUT
Only monitoring operation permitted as RUN-
STRS Execution started. RUN SEMI
command interrupt processing.
STR (None)
RSMA+
RSMA- AUT
RSMA
RSMA+
Suspended execution Only monitoring operation permitted as RUN-
RSMA- RUN SEMI
restarted. command interrupt processing.
RSMS
RSM+
RSM- (None)
RSM
RSMA AUT
RSMS RUN-command interrupt processing executed. RUN SEMI
RSM (None)
RSMA+ Phase-paused AUT
RSMA- execution restarted.
RSMS+
STOP-command interrupt processing executed. RUN SEMI
RSMS-
RSM+
(None)
RSM-
END Execution ended. STOP-command interrupt processing executed. STOP (None)
ABRT Execution aborted. No interrupt processing allowed. ABRT (None)
SUSPA[+] AUT
SUSPS{+} Execution suspended. STOP-command interrupt processing executed. STOP SEMI
SUSP{+} (None)
PAUSA AUT
Phase execution
PAUSS PAUS-command interrupt processing executed. PAUS SEMI
paused.
PAUS (None)
CONTA AUT
RUN-command interrupt processing allowed
CONTS RUN SEMI
Execution continued. during execution.
CONT (None)
CONTN No interrupt processing allowed. (Continued) (None)
STEP Step feed. No interrupt processing allowed. (Continued) (None)
Instruction Unit action Change-command interrupt processing Operation status Operation mode
D060609E.EPS

■ Details of Action Instruction for Unit Instruments
The details of action instruction for unit instruments are described below.
● STRA, STRS, STR (starting)

These action instructions start the operation of the unit-procedure initial step. They are
effective only when the unit is stopped or its execution has been aborted. They do not
execute any interrupt processing when the operation is started except for the monitoring
operation, for which RUN-command interrupt processing can be described.
● RSMA, RSMS, RSM (restarting)

When a unit is in PAUSE status (including the phase’s PAUSE status), these instructions
may be applied.
RSMA, RSMS, RSM instructions may restart the operation where the unit procedure
paused at the beginning of the step. However, the interrupt processing do not function
when the restarting is running.
There is one exception, i.e. the RUN instruction may used for interruption in a monitoring
operation.
When restarting a paused phase, RSMA, RSMS and RSM instructions send the RUN
command to the current operation. If the operation has any RUN-command interrupt
processing, it will be first executed. If error is caused during status-change pre-processing,
the status will not be changed.
After the restarting, the SFC step of current operation is executed.

● RSMA+, RSMS+, RSM+ (restarting)
When a unit instrument is in PAUSE status (including the phase’s PAUSE status), these
instructions may be applied.
RSMA+, RSMS+, RSM+ instructions may restart the condition check for transition at that
step. However, the interrupt processing can not be used in the operation.
There is one exception, i.e. the STOP instruction may used for interruption in a monitoring
operation.
When restarting a paused phase, RSMA+, RSMS+ and RSM+ instructions send the STOP
command to the current operation. If the operation has any STOP-command interrupt
the status will not be changed.
After the execution of operation is completed, the transition-condition evaluation for the
current step is restarted.
● RSMA-, RSMS-, RSM- (restarting)

When a unit instrument is in PAUSE status (including the phase’s PAUSE status), these
instructions may be applied.
RSMA-, RSMS-, RSM- instructions may restart the operation where the unit procedure
paused at the beginning of the step. However, the interrupt processing of an operation do
not function when the restarting is running.
There is one exception, i.e. the STOP instruction may used for interruption in a monitoring
operation.
When restarting a paused phase, RSMA-, RSMS- and RSM- instructions send the STOP
command to the current operation. If the operation has any STOP-command interrupt
the status will not be changed. The operation will be restarted upon completion of its
execution.
● END (ending)
It is effective only when the unit is being executed or suspended, including a paused phase.
This action instruction ends the execution of the unit procedure.
If the current operation has any STOP-command interrupt processing, it will be first ex-
ecuted. If error is caused during status-change pre-processing, the status will not be
changed. When any interrupt processing is executed, the unit execution ends when status-
change post-processing for all current operations is completed.

● ABRT (aborting)
It is effective only when the unit is being executed or suspended, including a paused phase.
This action instruction sends the ABRT command to all current operations and forcibly
terminates the execution of the unit procedure SFC.
No interrupt processing can be executed, including the monitoring operation.
● SUSPA, SUSPS, SUSP (suspending)

It is effective only when the unit is being executed or a phase is paused.
These action instructions send the STOP command to all current operations and then stop
the execution of the unit procedure at the start of the current step.
changed. The current step will be retained after execution has been suspended.
● SUSPA+, SUSPS+, SUSP+ (suspending)

They are effective only when the unit is being executed or a phase is paused.
These action instructions send the STOP command to all current operations, start transi-
tion-condition evaluation for the step upon completion of the operation, and then stop the
execution of the unit procedure at the start of the next step when the transition condition is
satisfied.
changed. The next step will be executed when execution is restarted, but the suspension
will be maintained if the transition condition for the current step is not satisfied.
● PAUSA, PAUSS, PAUS (phase pause)

They are effective only when the unit is being executed or is suspended.
These action instructions send the PAUS command to all current operations and stop the
execution of the unit procedure at the start of the current operation phase, or at the start of
the current operation if in a suspended status.
If the current operation has any PAUS-command interrupt processing, it will be first ex-
changed.

● CONTA, CONTS, CONT (continuation)
They are effective in any unit status.
These action instructions continue execution retaining the current conditions.
If the current operation has any RUN-command interrupt processing, it will be first ex-
changed. When a phase is paused and the operation has any RUN-command interrupt
processing, its pre-processing will be executed.
● CONTN (continuation)
It is effective in any unit status.
This action instruction also continues execution retaining the current conditions.
Interrupt processing is not executed, however, for the current operation.
● STEP (step change)

It is effective when the unit is suspended.
This action instruction jumps execution to a step specified by unit data item STEPNO. Any
step number can be entered to STEPNO as long as it exists.
No interrupt processing can be executed, including the monitoring operation.

D6.6.2 User Defined State Transition Matrix

When creating a user-defined state transition matrix, the corresponding unit status
character strings and the unit status change command character strings need to be
defined first.
■ Setting the State Transition Matrix Table

Choose the COMMON folder on the directory tree of System View. Then choose [Create
New] -- [State Transition Matrix] from [File] menu. A Create New dialog box will display. On
this dialog box, the State Transition Matrix, the Status Label, the Status Change Command
and the Comment can be set. A dialog box is display as follows.
Create New
State Transition Matrix Matrix2
Status label USER2
Status Change Command CUSER1
Comment Matrix Table 2
OK Cancel
D060610E.EPS
Figure State Transition Matrix Create New Dialog Box

● State Transition Matrix
▼ State Transition Matrix Name
A matrix (Matrix1 to Matrix16) can be designated as the State Transition Matrix. Then the
status character strings and status change command strings corresponding to the desig-
nated matrix should be set.
The name of the defined State Transition Matrix can be designated on the Unit Instrument
Function Block Detail Builder as State Transition Matrix.
● Status Label
▼ Status Character String Table Name
The table of character strings (USER2 to USER8) corresponding to the designated State
Transition Matrix should be specified. The labels in the specified character string table can
be used as the state transition destination.
● Status Change Command

▼ Status Change Command Character
The table of character strings (CUSER1 to CUSER8) corresponding to the designated
State Transition Matrix should be specified. The strings in the specified character string
table can be used as the status change commands.
● Comment
▼ Comment
Up to 24 alphanumeric characters or 12 double-byte characters can be used for comment.
TIP
After setting the State Transition Matrix, when the designated table for status label and status change
command character strings are changed, the settings for the matrix will not be changed. The State
Transition Matrix settings can be changed if required.

■ Configuring State Transition Matrix
The state transition matrix can be configured on the State Transition Matrix builder. The
state transition consists of unit mode transition and unit status transition.
Mode change command
State Transition Matrix Builder - [Pjt:MYPJT File:Matrix1.edf ( USER2, CUSER1 )]

File Edit View Tool Window Help
1 : AUT Block Mode Block Status
ABORTED 1 : AUT 2 : SEMI 3:

RUNNING 1-1 ABORTED AUT ABORTED A CONTN ABORTED S CONT ABO
SUSPEND 1-2 SEMI ABORTED A CONT ABORTED S CONTN ABO
PAUSED 1-3 MAN ABORTED A CONT ABORTED S CONT AB
END
2-1 RUNNING AUT RUNNING A CONTN RUNNING S CONT
2-2 SEMI RUNNING A CONT RUNNING S CONTN
2-3 MAN
3-1 SUSPEND AUT SUSPEND A CONTN SUSPEND S CONT
3-2 SEMI SUSPEND A CONT SUSPEND S CONTN
3-3 MAN
4-1 PAUSED AUT PAUSED A CONTN PAUSED S CONT
4-2 SEMI PAUSED A CONT PAUSED S CONTN
4-3 MAN
5-1
5-2
5-3
6-1
Ready
Current unit status Current unit mode Unit mode for transition
Unit status for transition Action after transition

D060611E.EPS
Figure State Transition Matrix Builder
In the State Transition Matrix builder, the following three items need to be configured:
• Unit status for transition
• Unit mode for transition
• Action after transition
The blank in the matrix means the transition can not be set.

● Unit Status for Transition
Under the current unit mode and unit status, when receiving a change command, the unit
may transit to a designated status. This designated status can be defined here.
The status character strings to be displayed will be the strings in the table whose number is
configured for the matrix.
● Unit Mode for Transition

may transit to a designated mode. This designated mode can be defined here. O/S can not
be configured as a mode for transition and blank means no transition.
The mode for transition can be selected from the followings:
• Blank
• AUT
• SEMI
• MAN
When defining AUT, SEMI and MAN as the mode for transition, use A, S, M, the signs
representing the modes.
● Action After Transition

may perform a designated action. This designated action can be defined here.
SEE ALSO
For more information about action after transition, see section “■ Action Instructions for Unit Instrument
or Operation” in chapter D6.6.1, “Standard State Transition Matrix.”

<Toc> <Ind> <D6.7 Unit Supervision Messages> D6-80
D6.7 Unit Supervision Messages

The following messages are used with the unit supervision. They will be stored in
the historical message file of the HIS:
• Unit process alarm messages
• Unit mode and unit status change messages
• Sequence control messages
• System alarm messages

D6.7.1 Unit Process Alarm Messages

Unit instrument is provided with the process alarm message handling function same
as other function blocks. This chapter explains the process alarm handling function
of the unit instrument.
■ Unit Process Alarms

The process alarm of unit control is referred to as unit process alarm. These alarms can be
described in the operation written in SEBOL programs. Their generation and recovery can
be optionally defined. Their priority, detection, suppression, and repetition requirements
can also be specified. Process alarms caused in a unit can be shown in process-alarm and
other windows.
■ Unit Alarm Status

▼ Alarm Status
The alarm status of a unit is called the unit alarm status.
A priority is assigned to each unit alarm status. When more than one unit alarm status
occur at the same time, the unit alarm status with the higher priority will take place in the
ALRM, a unit data item.
Alarm status character strings defined in the user-defined alarm status character string
builder (USER11 to USER16) can be used for indicating unit instrument’s alarm status.
SEE ALSO
For more information about user-defined alarm status character string, see “■ User-Defined Alarm
Status Character String” in E12.4, “Alarm Status Character String and Alarm Processing.”

■ Alarm Generation and Recovery
“unit prcsalarm” and “unit prcsalarm recover” SEBOL statements used in the operations in
unit instrument can define unit process-alarm generation and recovery.
An alarm may occur or recover either in a unit interment or in an operation. These alarms
can be applied to either a unit or an operation by specifying it in the SEBOL program. The
flows of process-alarm generation and recovery are shown below:
Flow of generation Flow of recovery
Processing starts. Processing starts.
Alarm generation Alarm recovery
Is alarm-detection YES Is alarm-detection YES

group-by-pass enabled? group-by-pass enabled?
NO NO
Is alarm-detection NO Is alarm-detection NO
group-suppression enabled? group-suppression enabled?
YES YES
Alarm-flashing suppressed. Alarm-flashing suppressed.
YES NO
Subject alarm has already Subject alarm has already
been generated. been generated.
NO YES
Alarm generated. Process alarm normalized.
NO
Processing ends. All alarms normalized.
YES
Recovery message output.
Processing ends.
D060701E.EPS
Figure Flows of Unit Process-alarm Generation & Recovery

■ Unit Process Alarm Initialization
Unit process alarms are initialized when the unit starts to run. If a unit process alarm al-
ready exists, that alarm will also be forcibly initialized and the recovery message will be
output.
■ Unit Process Alarm Repetition

If a unit is kept running for a predetermined period of time without resetting the existing unit-
process alarms, the alarms can be repeatedly output as long as the unit is in the RUN-
NING, PAUSED, or SUSPEND status. Alarm repetition can be specified using the function
block detail builder.
■ Unit Process Alarm Detection & Suppression

The detection and suppression of unit process alarms can be specified at unit data items
AF and AOFS respectively. Unit process alarms are output by the specification of these two
data items.
■ Unit Process Alarm Flashing

The flashing of unit process alarms can be specified for the operation and monitoring
function using unit data item AFLS. The flashing action is same as other function blocks.
■ Unit Process Alarm Messages

The messages to notify the occurrence of a unit process alarm and the recovery of the
alarm status can be output in the same manner as other function blocks. The message is
displayed in the process alarm window, while the unit name appears in place of the normal
tag name and the unit comment in place of the tag comment.
■ Unit Alarms of Unit Instrument

Levels of priority can be specified for unit instrument and alarms. The level of tag priority
determines the tag mark, and the level of alarm priority determines the window display,
alarm sound, acknowledgment action, etc.

D6.7.2 Unit Mode and Unit Status Change Messages

The unit has unit mode change messages and status change messages.
■ Unit Mode Change Message

A message is output when unit mode is changed.
■ Unit Status Change Message

A message is output when unit status is changed.

D6.7.3 Sequence Control Messages - Unit Instrument

Five types of messages can be output from operations of the unit instruments.
Outputting the messages can be programed in the operations written in SEBOL.
SEE ALSO
Refer to H1.9, “SEBOL Message Statements” for the details of SEBOL message statements.
■ Operator Guide Message

This message can be written using an optional character string or a character string speci-
fied by the element number of an operator guide message. The output of the message can
be programed using the “opeguide” statement in the operations written in SEBOL.
■ Dialog Message
fied by the element number of an operator guide message. The output of the message can
be programed using the “dialogue” statement in the operations written in SEBOL. The use
of this message permits exchanging data between the operator and the operation and
monitoring console by dialog message window.
■ Printout Message
A message written using an optional character string or a character string specified by the
element number of a printout message can be output to the printer. The output of this
message can be programed using the “message” statement in the operations written in
SEBOL. The message will be saved in the historical message file.
■ Historical Message
fied by the element number of a historical message. The output of the message can be
programed using the “history” statement in the operations written in SEBOL. The message
will be saved in the historical message file.
■ Request Sequence Message

fied by the element number of a request message. The output of the message can be
programed using the “request” statement in the operations written in SEBOL.

D6.7.4 System Alarm Messages

System alarm messages include system-fixed and user-defined alarm messages.
■ System-Fixed Alarm Messages

System-fixed alarms are output when error is caused in the action of the unit, such as
follows:
• Errors caused during execution of the unit.
• Errors caused during execution of operations.
• Errors caused during execution of commands from Process Management.
SEE ALSO
See Operating Messages (IM 33S02H10-01E) for the details of message output formats.
■ User-Defined Alarm Messages

User-defined alarms can be output from operations. Alarm generation and recovery mes-
sages can be written using optional character strings and their output can be programed
using the “sysalarm” statement in the operations written in SEBOL.
SEE ALSO
Refer to H1.9.6, “sysalarm” for the details of SEBOL sysalarm statement.

<Toc> <Ind> <D6.8 Operations> D6-87
D6.8 Operations
An operation is an independent phase in an ordered set of production phases as-
signed to a unit instrument and executes a sequence of control steps within the unit
procedure.

■ Positioning of Operations
▼ Operation
Each step in a unit procedure represents an operation. When a unit procedure of a unit
instrument starts, the operation will be executed while the step is activated in the se-
quence.
Execution time is automatically shared when more than one operation are executed in
parallel.
Operation (SFC Type) SEBOL
Unit
Initialization
Unit procedure (SFC)
Sequence table
Charging
Y
Initial step Termination N
Charging 1
Logic chart
Agitation
Charging 2
Heating
Operation (SEBOL Type)
SEBOL
D060801E.EPS
Figure Positioning of Operations

■ Types of Operations
There are two types of operations are available, the operations are programmed in SEBOL
or in SFC, so that they are distinguished as SEBOL type and SFC type operations.
● SEBOL Type Operations

Operations and phases are programmed in SEBOL
The model of the SEBOL operation block is OPSBL.
● SFC Type Operations

Operations are programmed in SFC but the phases are programmed in SEBOL, logic
charts or sequence tables. Moreover, the SFC type operations categorized into 6 block
models according to their available data items.
• OPSFC (SFC Operation)
• OPSFCP1 (SFC operation with floating-data parameters)
• OPSFCP2 (SFC operation with character-data parameters)
• OPSFCP3 (SFC operation with floating/character-data parameters)
• OPSFCP4 (SFC operation with integer/character-data parameters)
• OPSFCP5 (SFC operation with floating/integer-data parameters)
■ Special Operations
In addition to ordinary unit procedure-started operations, there are two types of special
operations:
• Initialization operation:
An operation to initialize the process before execution.
• Monitoring operation:
An operation to permit execution according to the process status which is monitored at
all times.

<Toc> <Ind> <D6.9 Data Items of Operation> D6-90
D6.9 Data Items of Operation

Only system-fixed data items are available in an operation. There is no user-defined
data items. If user defined data items are required, a unit instrument for starting
operations should be created.
■ Data Types of Operation

The data types of an operation are shown as follows. The data of other function blocks are
attached with data status signals but the data of operation cannot be attached with data
status signals.
Table Data Types of Operation
Type Description Remarks
U32 32-bit unsigned integer 0 to 4294967295
F32 Single-precision floating-point (32 bits) -3.402823 • 1038 to 3.402823 • 1038
F64 Double-precision floating-point (64 bits) -1.79769313486231 • 10308 to 1.79769313486231 • 10308
CHR*n Character-string (2n16) –
D060901E.EPS

■ Operation Data Items Available
The following data items can be applied to the operations of all models.
Table Operation Data Items
MODE Block mode CHAR*8 AUT
OMOD Block mode( lowest priority) CHAR*4 AUT
CMOD Block mode( highest priority) CHAR*4
BSTS Block status CHAR*8 STOP
PREBSTS Previous block status CHAR*8
ALRM Alarm CHAR*8 NR
AFLS Alarm flashing CHAR*8
AF Alarm detection specification CHAR*8
AOFS Alarm suppression specification CHAR*8
ERRC Classified error code U32 0
ERRE Detailed error code U32 0x0000
ERRP Error-caused plane number U32 0
ERRS Error-caused step number U32 0
ERRL Error-caused line U32 0
ERRF Error-caused program unit CHAR*8
STEPNO Current step number U32 0
PHASE Phase name CHAR*16
IHASE Interrupt processing phase name CHAR*16
OPMK Operation mark I16 0
UAID User application ID I16 0
SAID System application ID I16 0
DILG Dialog acknowledgement U32
SEMA Semaphore name CHAR*8
BATCHID Batch ID CHAR*16 For Process Management
UNITNAME Unit name CHAR*16
RECIPEGR Recipe group number I16 0 For Process Management
OPID Operation ID I16 0
QUEUE[5] Signal queue display CHAR*16
D060902E.EPS


● Data Items of SFC Operation with Floating-Data Parameters
Data items may be applied to the SFC operation with floating-data parameters (OPSFCP1)
are as follows.
Table Data Items of SFC Operation with Floating-Data Parameters
Data Item Data Type Entry Security Level Input Check
DT01 to DT14 F64 Yes 3 None
D060903E.EPS
● Data Items of SFC Operation with Character-Data Parameters

Data items may be applied to the SFC operation with character-data parameters
(OPSFCP2) are as follows.
Table Data Items of SFC Operation with Character-Data Parameters

CH01 to CH07 CHR16 Yes 3 None
D060904E.EPS
● Data Items of SFC Operation with Floating/Character-Data Parameters

Data items may be applied to the SFC operation with floating/character-data parameters
Table Data Items of SFC Operation with Floating/Character-Data Parameters

D060905E.EPS

● Data Items of SFC Operation with Integer/Character-Data Parameters
Data items may be applied to the SFC operation with integer/character-data parameters
Table Data Items of SFC Operation with Integer/Character-Data Parameters
INT01 to INT08 I16 Yes 3 None
D060906E.EPS
● Data Items of SFC Operation with Floating/Integer-Data Parameters

Data items may be applied to the SFC operation with floating/integer-data parameters
Table Data Items of SFC Operation with Floating/Integer-Data Parameters
INT01 to INT08 I16 Yes 3 None
D060907E.EPS

<Toc> <Ind> <D6.10 SFC Operation> D6-94
D6.10 SFC Operation

The functions of an SFC operation is the same as a normal SFC block.
■ Composition of An SFC Operation

The composition of an SFC operation is shown below, in which steps are regarded as
phases:
01 Initialization
Phase
02 Charging SEBOL program

block PID TIC301
Step .
.
.
03 Low-temperature heating 05 High-temperature heating .
04 Low-speed agitation 06 High-speed agitation

Sequence table
Action
YNN
07 Discharging NYN
08 Termination Logic chart
D061001E.EPS
Figure Composition of an SFC Operation

■ Differences between Operation and Unit Procedure
The SFC (Sequential Function Chart) in an operation and the SFC in a unit procedure have
the following differences:
• The SFC cannot handle parallel sequences and wait steps.
• The SFC in an operation describes transition conditions using SEBOL expressions.
The SFC in a unit-procedure uses logical expressions, which are used exclusively for
unit instruments.
• The actions of SFC in an operation may be redirected to a program written in SEBOL,
sequence table or logic chart for execution. The actions of SFC in a unit procedure
may be redirected to an operation name or an operation generic name for executing
the operations.
■ Differences between Operation and SFC Block

The SFC in an operation and the SFC in an SFC block have similar functions. An operation
started from a unit instrument can be considered as an SFC block. Also an SEBOL type
operation is about the same as an SFC block which only has an initial step.
The following are the differences between the SFC in an operation and the SFC in an SFC
block:
● Accessing Unit Instrument Data

An operation may access the unit instrument data in the format of
<TagName.DataItemName>. If the unit instrument is where the operation is started, the unit
instrument data may be accessed in the format of <%%.DataItemName>. While, an SFC
block may access the unit instrument data only with the format of
<TagName.DataItemName>.
● Starting an Operation
An operation can be started only from a unit instrument. An operation can not be started
separately.
● Accessing Common Block Data

When Batch Management is applied, common block data for the recipe can be accessed
from the SFC in a operation. However, it cannot be accessed from an SFC block.
● Start and End of Recipe Unit Procedure

When Batch Management is applied, the SFC in an operation can start and end the recipe
unit procedure operated by other unit instruments in the same recipe.
• A download of the recipe unit procedure operated by other unit instruments in the
same recipe can be requested.
• A unit instrument to be executed by the recipe unit procedure operated by a unit
instrument in the same recipe can be assigned (dynamic assignment of unit).

D6.10.1 SFC Operation

The SFC (Sequential Function Chart) in an operation runs an ordered set of running
procedures i.e., an ordered set of phases. In one word, the steps of the SFC in the
operation may be assigned with the functions by entering the designated tag names
of the phases.
■ Basic SFC Elements of Operation

The SFC in an operation uses the following basic elements:
• Step: Describes action.
• Transition: Describes transition condition.
• Connection: Connects a step to transition, and transition to a step.
Table Unit Procedure SFC Basic Elements

Element Name Symbol Remarks
Double height initialization step is also
Initial Step
available.
Step Step Double height step is also available.
Interrupting Step
Selective Seq.-Split
Selective Seq.-Join
Loop-Branch
Loop-Join
Connection
Jump Down Jnn nn: numerals
Jump Up Jnn nn: numerals
Jump To Jnn nn: numerals
Link
D061002E.EPS

■ Operation SFC Steps
The square in the step is for placing the step number (01 to 99).
The action of the SFC step is scripted in a rectangle shown to the right of the step. When
the step is activated, the phase in the action box will be started. In the phase, a SEBOL,
sequence table or logic chart program may be redirected.
Step number Action box
10
D061003E.EPS
Figure SFC Step
Every step is either in the active state, in which the step is being executed, or the inactive
state, in which the step has been completed or is yet to be executed.
TIP
A maximum number of steps can be described in one column is 50. With parallel, transition, and jump
sequences, up to 99 steps can be described in one SFC.
● Operation Step Action

The step action is the process executed when the step is active. For an operation SFC
step, the process is the phase defined in the action box. When execution of the phase is
completed, the step is inactivated and processing is shifted according to the connection of
the step.
TIP
When a comment is defined entered when defining he steps properties, the comment may be displayed
in the action column of the SFC window displayed on a HIS.
● Operation Initial Step

The initial step is the first step to be executed in an operation. The step number in this case
is shown in a double square, however, the basic function of this step is the same as other
steps.
01 Initialization
D061004E.EPS
Figure Initial Step

● Interrupting Steps in an Operation
The program for normal processing is referred to as main program, the programs for
interrupt the main program invoked by certain events are referred to as interrupting SFC
programs. The interrupting programs are extended from interrupting steps.
01
Interrupting steps
02 RUN
03 STOP
04 PAUS
D061005E.EPS
Figure Interrupting Steps
● Step Actions
The steps other than interrupting steps are scripted as actions for execution.
When using SEBOL, clicking the step may open the editing window for editing SEBOL
scripts. When using sequence table or logic chart, the tag name or the generic name of the
sequence table or the logic chart shall be assigned to the step. When assigning a generic
name, the tag name of the unit instrument where the generic name belongs to needs be
designated.
There are following types of step actions
• SEBOL
• SEBOL one-shot
• Sequence table
• Sequence table one-shot
• Logic chart
• Logic chart one-shot
SEE ALSO
For more information about scripting an action, see D6.12 “Actions of Operation.”

■ Operation SFC Transition
Transition is shown with a short horizontal line crossing the step-connecting link. Transition
defines the condition of transition using a logical expression. Execution advances to the
linked step when the result of the expression is true. If the transition condition is not estab-
lished, the check for the conditions will continue at each basic cycle.
The transition condition will be parsed as soon as the current step operation is completed.
Transition
06
07
D061006E.EPS
Figure SFC Transition

■ Operation SFC Connections
Link elements, which are vertical or horizontal lines connecting unit-procedure steps and
transitions, indicating the execution order or path of steps. Examples of their use are shown
below:
Link

Ordinary link Selective Sequence Split Join
Loop Join
Loop Branch
Loop Branch and Loop Join
Jump To
J2 Jump Down
J1
J2
Jump Up
Jump To
J1
Jump Up Jump Down

D061007E.EPS
Figure Link Elements

D6.10.2 Compound Sequence

A compound sequence is composed of a number of laterally described sequences.
A selective sequence is a compound sequences.
In the case of executing a step by switching among the multiple choices according to
transition condition, the selective sequence may be applied. For one selective sequence,
eight choices may be set in parallel.
An example of selective sequence is shown as follows.
05
06 07 08
Selective sequence
09
10
D061008E.EPS
Figure A Selective Sequence
In the above example, the three laterally linked transition conditions are evaluated from the
left when step 05 has been completed and inactivated. If one of the conditions is true, the
step linked to that transition is activated. If there are two or more true conditions, the one on
the left has priority over the others.
If none of the conditions is true, the evaluation will be repeated at every basic scan period
until one of the conditions becomes true.

D6.10.3 Transition Conditions

The transition conditions in the operation SFC are explained.
■ Scripts of Conditional Transition

The conditional transition expression may be scripted in SEBOL. When the result of the
condition expression for the transition is not 0, the transition will be committed while when
the result is 0, the transition will not. When an arithmetic expression is used, transition will
be committed when the result is 1, transition will not committed when the result is 0.
If the condition expression is omitted, the transition will be committed unconditionally.
■ Operators in Condition Expression

The following operators can be applied in the expressions for conditional transition.
Table Operators in Condition Expression
Operator Description
== True if left and right side are equal. False if not equal.
<> True if left and right side are not equal. False if equal.
< True if right side is larger than left side. False if not.
<= True if right side is larger than or equal to left side. False if not.
> True if right side is smaller than right side. False if not.
>= True if right side is smaller than or equal to left side. False if not.
D061009E.EPS

■ Variables in Condition Expression
The following variables can be used in the condition expressions for conditional transition:
Table Variables in Condition Expressions
Variable Remarks
Constant -
Global variable -
Local variable Need to be declared in step action.
Global tag name Tag name declared by “global block.”
Tag name declared by “block” in SEBOL-step action.
Tag name Sequence table tag name in sequence table step action.
Logic chart tag name in logic chart step action.
Global generic name Generic name declared by “global genname.”
Local generic name Declared by “genname” in step action.
Declared by “global unit genname,” or declared by
Unit generic name
“unit genname” in step action.
Replaced by tag name of sequence table or logic chart
%$
used in action step.
D061010E.EPS
• Global variables, step local variables, and constants can be used in array subscript
expressions for array-element variables.
• SEBOL built-in functions can be used in condition expressions.
• “%$” entered in transition condition is replaced by the tag name of the sequence table/
logic chart which defines action. The condition expression %$.MODE=“AUT” will be
changed to ST0101.MODE=“AUT” if the sequence table tag name is ST0101, for
example.
• If the sequence table/logic chart is specified using a unit generic name, “%$” cannot
be replaced by the generic name. The generic name must be written in the condition
expression in this case.
■ Comparison of Data in Transition Condition

The following should be noted regarding the comparison of data performed in transition
conditions:
● Comparison of Numeric & Character-String Data

An error message will be generated (by transition condition check) if comparing a character
string to a numeric value in transition condition.
● Comparison of Floating-point Data

Floating-point data contain very small errors because of calculation accuracy, and they
could actually be different internally even if two units of floating-point data are apparently
the same. So their comparison could be determined false when they are compared using
(==) or (<>).
It is thus necessary to use (>=) or (<=) in comparing floating-point data instead of (==) or
(<>).

D6.10.4 Operation Sharing

Normally, one operation is assigned in one unit instrument. When multiple unit
instruments corresponding to the same type of equipment entity which have the
same control sequence, the operation may be shared.
■ What is Operation Sharing

▼ Sharing an Operation
One SFC may be shared by multiple operations. the shared SFC may be created on FCS
Sequence Library Builder. The SFC sequence name of the created SFC may be defined on
In the shared SFC program, the tag name or the tag generic name may be specified.
When a program in an operation access a function block or another unit instrument, the tag
generic name is used instead of using the tag name. Using the tag generic name, the
program may created independently from the tag name assignment, thus enables the
sharing of the SFC program. The table corresponding the generic tag names in the opera-
tion and the actually used tag names is held in the unit instrument. The tag generic name is
defined on unit instrument when the operation is started. One unit instrument may define
up to 512 tag generic names.
SEE ALSO
For details on FCS sequence library, refer to F8, “FCS Sequence Library.”
■ Operation Generic Name Definition

▼ Tag Generic Name
Tag generic name is an ID of an operation, it can be used even when the operation is not
shared. The items to be defined for an operation are shown as follows.
● Tag Generic Name

The tag generic name may be defined by a SEBOL statement in the operation. A tag
generic name may be defined with up to 8 alphanumeric characters.
● Array Element Number

The array element for the tag generic name may be defined from 0 to 99. When array is not
used, the default setting is 0.
● Tag Name
Corresponding to the tag generic name, the actually used tag name may be specified.

■ Example of Sharing an Operation
For an example, if an operation may be called from unit instrument A or unit instrument B,
when called from unit instrument A, the table corresponding tag generic name and tag
name in the unit instrument A is referred, while when called from called from unit instrument
B, the table corresponding tag generic name and tag name in the unit instrument B is
referred.
When using the tag generic name of the operation’s program like this, the table corre-
sponding the generic tag names and the tag names in the unit instrument may be referred,
thus the logic in the operation may be shared. The sharing is only ranged within the same
station. When beyond one station, they should be created separately.
The data area of the operation (function block data) can not be shared.
FCS sequence library

SFC sequence
SEBOL
Sharing
VALVE1.MV=1
Unit instrument A Operation sequence OP101

SEBOL
7
SI100.MV=1
8 OP101
Substitute VALVE1 for SI100

Tag generic
Tag name
name
VALVE1 SI100
VALVE2 SI101
Unit instrument B Operation sequence OP201

SEBOL
7
SI200.MV=1
8 OP201
Substitute VALVE1 for SI200

Tag generic
Tag name
name
VALVE1 SI200
VALVE2 SI201
D061011E.EPS
Figure Sharing an Operation

■ Operation ID
In a unit-procedure SFC, the same operations described in the same control algorithm are
often repeatedly invoked from a number of steps. It then becomes necessary to identify the
round of the repetition in order to change operation processing accordingly. For this pur-
pose, every step needs an operation ID. In the case like this, each step of the procedure
will assign the operation with an operation ID. When the operation is started, the operation
ID assigned will be attached to the operation.
01 Initialization
02 Charging 1
Charging operation
03 Charging 2
Assign an operation ID
04 Termination
D061012E.EPS
Figure Operation ID
When creating an unit procedure SFC, the operation to be called from a step may be
defined with a name and an arbitrary ID number. If the user does not define the ID for the
operation, a system default ID number will be assigned to the operation. Actually, there is
no need for a user to worry about the operation’s ID.
For an example, in the case that the operation of step 2 (Charging 1) is assigned with an ID
number 1, and the operation for step 3 (Charging 2) is assigned with an ID number 2, when
unit instrument starts execution, the operation ID will be used as the arguments for calling
the operation. An operation’s SEBOL program can read the argument to determine the step
where it is called, so that the operation may switch it processing accordingly.

<Toc> <Ind> <D6.11 Mode and Status of an Operation> D6-107
D6.11 Mode and Status of an Operation

Like a function block, mode and status are also provided to an operation. The block
mode of an operation is referred to as operation mode, while the block status of an
operation is referred to as operation status. This chapter will give explanations on
the operation mode, operation status and the operation state transition.

D6.11.1 Operation Mode

Operation mode indicates the operation’s control state. Normally, an operation is
defined as apart of a unit instrument, the operation mode and operation status
changes are controlled from the unit instrument.
■ Operation Mode
An operation may have the following modes. The modes of operation are system-fixed.
● O/S (Out Service) Mode

The operation is not running
● SEMI (Semi-Automatic) Mode

▼ SEMI Mode Operation
The block stops at the start step of each operation, and the step is executed upon a exter-
nal command such as a command from the operation and monitoring console.
The mode can be “enabled” or “disabled” for each operation.
When it is “disabled”, the operation will not have the SEMI mode.
● AUT (Automatic) mode:

The operation continuously runs from one step to another.

D6.11.2 Operation Status

An operation’s status may indicate the operation’s running state.
■ Operation Status
The running state of an operation such as PAUSE is indicated by the operation’s status.
The statuses of the operation are system-fixed.
The statuses of an operation are shown as follows.
● STOP
The operation is stopped and ready for starting
● RUN
The operation is running by executing its actions while checking transition conditions.
● PAUS
The operation is temporarily suspended.
● ABRT
The operation is terminated abnormally.

D6.11.3 Operation Mode and Status Change Command

Just like other function blocks, an operation’s mode and status may be changed by
an operation mode change or status change command.
■ Mode Change - Operation

To change an operation block mode, the block mode change command can be used. The
block mode of an operation may be changed by a mode change command or a status
change command from unit instrument. An operation may change its mode without desig-
nation. The modes of an operation are system-fixed.
● AUT
Command for changing the operation to automatic mode
● SEMI
Command for changing the operation to semi-automatic mode
● O/S
Command for changing the operation to out-service mode
■ Status Change - Operation

An operation may be started by a command from a unit instrument. A status change com-
mand from the unit instrument may also change the operation’s block status. An operation
can not start by the command from itself.
Table Block Status Change Commands
Symbol Service Description
RUN Run Starts operation or restarts paused operation.
STOP Stop Stops current operation.
PAUS Pause Pauses current operation.
RSET Reset Changes ABRT status to STOP.
ABRT Abort Forcibly terminates current operation.
D061101E.EPS

D6.11.4 Operation Block Status Transition

Operation block status transition will be committed accordingly when a mode
change or a status change command is given.
■ Operation Block Status Transition

▼ PAUS Stop Position
The status transition scheme of the operation block is shown below:
PAUS
ABRT (*1)
PAUS
PAUS RUN
(*3)
STOP
RUN ABRT (*1)

STOP RUN ABRT
STOP (*2)
RSET D061102E.EPS
*1: Transition is made even in the case of fatal or internal error or memory insufficiency.
*2: Transition is made even when execution is terminated using the “exit” or “end” statement.
*3: Transition is made from RUN to PAUS at the start of a step when the block is in the SEMI mode.
Figure Transition of Operation Block Status
• The RUN command starts execution of the SFC block in the STOP status, which then
changes to RUN when started. When an operation is started, the operation’s status
changes to RUN.
• The PAUS command suspends execution of the SFC block in the STOP status at the
start of the initial step, the status then changes to PAUS.
• When the operation block status is changed to PAUS during execution of a SEBOL
step action, the stopping position can be specified either at the start of the step or the
current program line.
• When an operation is in SEMI mode, the operation status changes from RUN to
PAUS at the start of every step. The step can then be executed upon receiving the
RUN command from the operator consoles.

■ Operation Step Jump
When an operation SFC is in SUSPEND status, it is possible to jump its sequence to a
designated step. Step jump enables an operation SFC to transit to a desired step for
execution, either forward or backward is allowed. There are two ways to set the unit into
SUSPEND status, by setting the unit into Semi-automatic (SEMI) mode or by sending a
command for changing to PAUS status.
● Changing the Operation to SEMI Mode

This method changes the running operation started from a unit instrument into the semi-
automatic (SEMI) mode first.
When the operation changes to SEMI mode, the operation temporarily stops at the begin-
ning of a step (phase), the sequence status becomes PAUS.
Under this situation, on the SFC window, the step may jump forward or backward. Then
sending a RUN command to the operation may start the execution from the jumped step.
● Changing the Operation to PAUS Status

Sending a PAUS status change command may change an operation to a temporary stop
(PAUS) status.
Under this situation, on the SFC window, the step may jump forward or backward. Then
sending a RUN command to the operation may start the execution from the jumped step.

<Toc> <Ind> <D6.12 Actions of Operation> D6-113
D6.12 Actions of Operation

This section explains the SEBOL, sequence table and logic chart related to setting
the actions in an operation.

D6.12.1 Action Scripts in SEBOL

The following three types of steps can be scripted in SEBOL.
• Initial step
• SEBOL step
• SEBOL one-shot step
■ SEBOL Variables
Global and local SEBOL variables can be used in the operation when a step is scripted
using SEBOL. The global variable can be accessed from all the SEBOL steps in the opera-
tion, while the local variable can be accessed from only one step.
Areas are allocated to both types of variables and they are initialized to zero when the
operation is started.
The reserved areas will be released when the operation is completed.
TIP
In the case of a character-string variable, the global or local variable is initialized to a zero-length charac-
ter string when the operation is started.
● Global Variables
Global variables can be accessed from any SEBOL step in the operation. To use global
variables, they should be specified in the initial step as shown below:
global integer <variable name>[, <variable name>...]

global long <variable name>[, <variable name>...]
global float <variable name>[, <variable name>...]
global double <variable name>[, <variable name>...]
global char*n <variable name>[, <variable name>...]
D061201E.EPS
TIP
Global variables cannot be accessed from the steps described in sequence table or logic chart.

● Local Variables
Local variables can be accessed only from the steps for which the use of local variables is
declared. To use local variables, they should be specified in the step as shown below:
integer <variable name> [, <variable name>...]

long <variable name> [, <variable name>...]
float <variable name> [, <variable name>...]
double <variable name> [, <variable name>...]
char*n <variable name> [, <variable name>...]

D061202E.EPS
The same local variable name can be used in different steps, in this case, each variable will
be allocated with a separate area.
If a step is repeatedly executed in a loop, the local variable remains unchanged throughout
the repeated execution.
● Restrictions
The same name cannot be assigned to global and local variables. An error will occur if the
two has the same name.

■ Function Block Declaration
The use of a function block can be declared globally or locally. The global declaration
permits access from all SEBOL steps, while the local declaration permits access only from
the declared step.
SEE ALSO
See a chapter H1.5.1, “Usage of Function Block Data,” how to access function block data.
● Global Declaration
A function block can be accessed from all SEBOL steps when the use of that function block
is globally declared in the initial step as shown below:

global block <block code> <tag name>[, <tag name>...]
• Global generic name

global genname <block code> <global generic name>[, <global generic name>...]
D061203E.EPS
● Local Declaration
A function block can be accessed from just one step when the use of the function block is
locally declared in that step as shown below:

block <block code> <tag name>[, <tag name>...]
• Local generic name

genname <block code> <local generic name>[, <local generic name>...]
D061204E.EPS
● Restrictions
No error will occur when the tag name specified in global declaration is used also in local
declaration; however, an error will occur if different block codes are specified. An error will
also occur if specified global and local generic names are identical.

■ Branching
The destination for branching is restricted to be within the step in which branching is speci-
fied using a “goto” statement, for example. Processing cannot be branched to other steps
using “error” and “errorsub” specifications, “goto” statements, etc.
SEE ALSO
• For the details on “error” and “errorsub” specifications, please see a chapter “■ Setting Branching Des-
tination for Error Occurrence” in H1.13.1, “Error Handling for Statements with I/O or Communication.”
• For the details on “goto” statements, please see a chapter H1.8.7, “goto.”
■ “quit” Statement
The “quit” statement terminates the action being executed.
When this statement is executed as a step action, the transition condition defined succeed-
ing the step will then be evaluated.

■ Initial Step
The scripts for initial step are described in this section:
● Order of Scripts
The initial step action should be described in the order of global variables, local variables,
and execution statements as shown below; an error will be caused otherwise.
<global variable/global function-block declaration>

<action statement>
D061205E.EPS
The initial step action can be described using up to 2000 lines. No parameters are used in
the action scripts.
The initial step will be ended when the last statement or a “quit” statement is executed.
● Example of Scripts
The following is an example of initial-step scripts.
!global variable declaration

global block TM TM301, TM302
global block SIO-11 VL301, VL302
global integer loop
global char*16 name

integer i, j, k
!action statement
.......
■ Use of “#define”
Names can be defined using “#define” anywhere within the initial step.
The defined names can then be used in all SEBOL steps or in transition condition.
SEE ALSO
For the details of “#define” statement, see a chapter H1.1.8, “Substitution of Character String.”

■ Use of “#include”
“#include” can be specified for file-inclusion anywhere within the initial step.
The order of all statements in the included file, however, must be in conformity with that of
the initial step. Otherwise, an error is caused for the statements in the included file.
SEE ALSO
See a chapter H1.1.9, “Include File,” for the details of “#include.”
■ Use of “#IMPLICIT”
A “#IMPLICIT” command can be used in the initial step. The command is then valid within
the entire operation.
(This command cannot be scripted in any other steps.)
SEE ALSO
See a chapter H1.1.7, “Implicit Declarations of Variables” for the details of “#IMPLICIT.”

■ SEBOL Steps
The SEBOL step action should be scripted in the order of variables and execution state-
ments as shown below; otherwise an error will occur.
The SEBOL step action can be scripted using up to 2000 lines. No parameters are used in
the action.
The step will be ended when the last statement or a “quit” statement is executed.

<action statement>
D061206E.EPS
The following is an example of SEBOL step scripts:
block PVI LI303
integer ierr
!action statement
wait until (LI303.PV >= 10.0) ; ierr
.......
● Restrictions
#define, #include, and #IMPLICIT command cannot be used with SEBOL steps. These
commands can be used only by the initial step. However, the name defined by means of
“#define” in the initial step can be used.

■ SEBOL One-Shot Steps
The SEBOL oneshot steps are explained in this section:
● Order of Scripts
The SEBOL oneshot-step action should be scripted in the order of variables and execution
statements as shown below; otherwise an error will occur.
No parameters are used in the action. The step will be ended when the last statement or a
“quit” statement is executed.

<action statement>
D061207E.EPS
The following is an example of SEBOL oneshot-step scripts. In the following example, the
common switches SW301 and SW302 should be defined on the common switched builder
before they are used in the scripts.

block %SW SW301, SW302
!action statement
SW301.PV = 1
SW302.PV = 1
● Execution
The SEBOL oneshot-step action will be executed without any break once it is activated. Its
processing time will not be shared by any other SFC program. No interrupt signals nor
status change instructions are allowed to interrupt the execution until it is completed.

● Restrictions
The SEBOL oneshot-step action can be continuously executed up to 20 lines. If a “for”
statement is used, for example, and one line is repeatedly executed, each repetition is
counted as one line. If execution is attempted exceeding 20 lines, an execution error is
caused and the successive action will be executed not as oneshot but normal step action.
The following statements should not be used in order to avoid any execution error:
• Statement for accessing function-block data at another control station.
• “signal” statement for sending signals to another control station.
• “qsigcancel” and “qsigmove” statements for manipulating function block at another
control station.
Also the following statements should not be used in order to avoid any error:
• “drive” statement, “seqstable” and “logicchart” statements with “drivewait” specifica-
tion.
• “wend,” “until,” and “next” statements without “@.”
• “wait until,” “delay,” and “delaycycle” statements.
• “dialogue” statement.
• “nopreempt begin” and “nopreempt end” statements.
• “semlock wait” statement.
• “wait for qsignal” statement.
• “ssdtwrite” and “ssdtwritebit” statements.
#define, #include, and #IMPLICIT command cannot be used with SEBOL oneshot steps.
These commands can be used only by the initial step. However, the name defined by
means of “#define” in the initial step can be used.

D6.12.2 Action Description Using the Sequence Table

The following two types of step actions can be described by sequence table.
• Sequence table (ST) step
• Sequence table (ST) one-shot step
SEE ALSO
See a chapter D3.2, “Sequence Table Block (ST16, ST16E)” for the details of Sequence Table.
■ Tag Name
The tag name or the generic name of the sequence table for the step needs to be desig-
nated. The same sequence table can be shared by different steps.
An operation or a sequence table in the same control station may be designated as the
step. When using a generic name, the link between the generic name and the tag name
should be defined in the unit instrument that running the operation.
■ Step Designation
When using a step of step type sequence table as a step action, the step name of the step
type sequence table can be designated.
In the case that the sequence table step is an one-shot step, the specified step and step 00
will be executed for a one-shot.
In the case that the sequence table is an periodic sequence table, the specified step and
step 00 will be executed for a one-shot, then the sequence table will continue in its own
pace of execution periodically. Step 00 will also be executed in every scan period. If a step
name designated for a non-step sequence table, the designation will be ignored.
The step can be configured with following options.
● Head
The sequence starts from the beginning of the sequence table when the it is invoked.
● Continue
The sequence starts its execution from the current running step. The running step number
is stored in the data item PV of the sequence table.
● Specification
The sequence starts its execution from the specified step. The specified step name should
be entered for this type execution.

■ Variable Designation
Vary with the types of action, the variables designated for the step are different.
● Sequence Tables
When [Sequence Tables] is designated, the variable will be kept in the SFC/SEBOL return
even message (%RE) as a parameter.
The value 0 through 65535 defined in the action-signal column of the sequence table is
stored as a variable.
● Sequence Table One-Shot

When [Sequence Table One-Shot] is designated, the result of condition test of the se-
quence table is stored as the variable, which is either true (1) or false (0).
• In the case of a non-step sequence table, the result is true if at least one of 32 rules is
satisfied and false if none is satisfied.
• In the case of a step sequence table, all the rules for the specified step and step 00
are evaluated. Then the result is true if at least one rule is satisfied and false if none is
satisfied.

● Variable Name
The variable names for SFC/SEBOL return event message parameters and the condition
test results are as following 4 types.
• Operation data item
When storing data as a data item in the operation, specify the variable name as
follows:
%.<data item>
• Global variable
step. When storing the condition testing result for an ST oneshot step, the tag name
must be present within the same control station as the SFC block; specifying a tag
name from another control station causes error when the operation is executed.
“global genname” in the initial step. When storing the condition testing result for an
sequence table oneshot step, the tag name present within the same control station as
the operation block must be assigned to the global generic name using the “assign”
statement.

■ Sequence Table Steps
When sequence table step is designated, the sequence table action is a periodic start (T)
sequence table.
The sequence table step is oneshot-executed when its action is activated, and the se-
quence table block mode changes to AUT at the same time. The sequence table will then
be periodically executed according to its own action timing.
The sequence table step action is terminated when an SFC/SEBOL return event message
(%RE) is received. The sequence table block mode then changes from AUT to MAN.
■ Sequence Table One-Shot Step

When sequence table one-shot step is designated, the sequence table action is an one-
shot start (O) sequence table.
The sequence table one-shot step is oneshot-executed when its action is activated. The
sequence table block mode remains unchanged after the execution.

D6.12.3 Action Description Using Logic Charts

The following two types of step actions can be described by logic chart.
• Logic chart step
• Logic chart one-shot step
SEE ALSO
For the details of logic chart, see D3.3, “Logic Chart Block (LC64).”
■ Tag Name
The Tag name or generic name of the logic chart for the step needs to be designated.
One logic chart can be shared by different steps.
The tag names that can be specified for the step execution name are limited to the logic
chart in the same control station.
An operation or a sequence table in the same control station may be designated as the
step. When using a generic name, the link between the generic name and the tag name
should be defined in the unit instrument that running the operation.

■ Variable Designation
When [Logic Chart] is designated, the variable will be kept in the SFC/SEBOL return even
message (%RE) as a parameter.
The value 0 through 65535 defined in the action-signal column of the sequence table is
stored as a variable.
When [Logic Chart One-Shot] is designated, the variable can not be used.
● Variable Name
The variable names for SFC/SEBOL return event message parameters are as following 4
types.
• Operation data item
When storing data as a data item in the operation, specify the variable name as
follows:
%.<data item>
• Global variable
<global variable>
step.
“global genname” in the initial step.

■ Logic Chart Step
When logic chart step is designated, the logic chart action is a periodic start (T) logic chart.
The logic chart step is oneshot-executed when its action is activated, and the logic chart
block mode changes to AUT at the same time. The logic chart will then be periodically
executed according to its own action timing.
The logic chart step action is terminated when an SFC/SEBOL return event message
(%RE) is received. The logic chart block mode then changes from AUT to MAN.
■ Logic Chart One-Shot Step

When logic chart one-shot step is designated, the logic chart action is an one-shot start (O)
logic chart.
The logic chart one-shot step is oneshot-executed when its action is activated. The logic
chart block mode remains unchanged after the execution.

<Toc> <Ind> <D6.13 Operation Actions> D6-130
D6.13 Operation Actions

Operation internal processing and actions are explained in this section.

D6.13.1 Start and End of An Operation

This section explains how to start and how to end an operation.
■ Start an Operation
An operation can be started from a unit instrument. An operation can not start by itself.
■ End an Operation
One of the following methods may end an operation.
• By exit statement
• Change block status (BSTS) to STOP
• By a command from a unit instrument
SEE ALSO
For more information about commands from unit instruments, see D6.6 “State Transition Matrix.”
The programs in which the exit statement and the status change scripts are allowed are
shown as follows.
Table Programs Allow exit Statement and Status Change Scripts
Program “exit” statement BSTS change
Main program Yes Yes
Status-change pre-process No No
Status-change post-process Yes No
Interrupt signal processing Yes Yes
Common error processing Yes (*1)
D061301E.EPS
*1: The feasibility of block status change during error processing is determined by the location where the error involved
has been caused. If the error is in the main program, the status can be changed. If the error is in the status-change
post-process, the status cannot be changed.

● End an Operation by “exit” Statement
Use the “exit” statement may terminate an operation unconditionally, which can be written
as follows:
exit[<expression>]
D061302E.EPS
The operation block will be terminated when the exit statement is executed and the block
status changes to STOP. The status change pre-/post-processes will not be executed.
● End an Operation by Changing Block Status

In a SEBOL program, by changing an operation block’s status BSTS into STOP may end
the operation.
EXAMPLE:
.......
.......
%.BSTS = "STOP"
.......
Status-change pre- and post-processes can be executed when changing the block status
to STOP.

D6.13.2 Pause an Operation

The execution of an operation can be paused in one of the following conditions.
• When the operation block mode is SEMI.
• When the operation block being executed receives a command to change the
status to PAUS.
• When the operation block ready for execution receives a command to change
the status to PAUS.
• When the operation block ready for execution in the SEMI mode receives a
command to change the status to RUN.
When the block is paused while a program line is being executed, how the inter-
rupted action is affected varies according to the contents of that line.
The restarting of the paused block is determined by the built-in function “ckstep”
and action when the block is restarted varies according to the condition of the block
at the time of pause.
■ Pausing
The four conditions in which an operation may be paused are described below, the paused
operation block can be restarted by commanding a status change to RUN in any of these
conditions:
● When the Operation Block in SEMI Mode

When the block is in SEMI mode and executed to the start of a main program step, the
block status changes from RUN to PAUS and the block pauses at the start action of the
operation.
• No status-change processing takes place at this time.
• Execution is not paused at the start of an interrupt processing step.
● When the Operation Block Receives a PAUS Command

When the block being executed receives a PAUS command, the block status is changed
from RUN to PAUS and the block will be paused.
• If the block is paused during a SEBOL-described action, the builder-defined PAUS
position will be applied to the restarting of the block.
• If the block is paused during a sequence table or logic chart described action, the
sequence table or logic chart block mode changes from AUT to MAN. The block will
be restarted from the start of the step at all times even if the PAUS position is defined
as the current line.

● When a Ready for Execution Block Receives a PAUS Command
When the block standing-by for execution receives a PAUS command, the block status
changes from STOP to PAUS and the block is paused at the start of the initial step.
● When a Ready for Execution Block in SEMI Mode Receives a RUN Com-
mand
When the block ready for execution in SEMI mode receives a RUN command, the opera-
tion block status changes from STOP to RUN and then to PAUS and the operation block is
paused at the start of the initial step.
• Status-change processing takes place for the STOP-RUN status change but does not
for the RUN-PAUS change.
• If post-processing is executed for the STOP-to-RUN change, the RUN-to-PAUS
changes takes place after the post-processing is completed.
• If an interrupt signal is received during the post-processing for the STOP-to-RUN
change, the signal is processed first when the post-processing is completed and then
the RUN-to-PAUS change takes place upon completion of the signal processing.

■ Pause-Position Actions
When an operation has been designated an execution script as the PAUS position, the
action of the SEBOL step is explained as follows.
● “dialogue” Statement Used

When the block has been paused while waiting for input from the operation and monitoring
function after executing a “dialogue” statement, the block is restarted from the line following
the “dialogue” statement unless the operator has not input anything. Since the “time”
specified wait time advanced even while the block is paused, a time-out error is caused if
the wait time has been counted up during the pause.
● “delaycycle” and “delay” Statements Used

The time specified to “delaycycle” and “delay” statements advances even while the block is
paused.
● “wait until” and “compare” Statements Used

The time specified to “wait until” and “compare” statements advances even while the block
is paused. Comparison or condition evaluation is executed at lease once after the block is
restarted, however, even if the specified time has elapsed.
● “semlock wait” Statement Used

When the block has been paused while waiting for the unlocking of semaphore, the block is
restarted from the line following the “semlock wait” statement if the semaphore has been
unlocked by another SFC block during the pause. If the semaphore has not been unlocked
and is secured, the state of waiting for the unlocking will be maintained.
● “seqtable drivewait” Statement Used

event message (%RE) from the sequence table after starting the sequence table using a
“seqtable drivewait” statement, the sequence table block mode remains AUT. The block is
restarted from the line following the “seqtable drivewait” statement if %RE is output from
the sequence table during the pause. If not, the state of waiting for the output will be main-
tained.
● “logicchart drivewait” Statement Used

event message (%RE) from the logic chart after starting the logic chart using a “logicchart
drivewait” statement, the logic chart block mode remains AUT. The block is restarted from
the line following the “logicchart drivewait” statement if %RE is output from the logic chart
during the pause. If not, the state of waiting for the output will be maintained.

■ Identification of Restart Condition
The data returned when the built-in function “ckstep” is executed identifies the condition in
which the operation block has been restarted.
“ckstep” return values are as follows:
When operation block is restarted after changing STEPNO in the PAUS mode.
When operation block is restarted without changing STEPNO in the PAUS mode.
When unit instrument is restarted after changing STEPNO in the PAUSED mode.
When unit instrument is restarted without changing STEPNO in the PAUSED mode.
When unit instrument is restarted without changing STEPNO in the SUSPEND mode.
In cases other than listed above.

“ckstep” returns “2” when the SFC block, for which the PAUS position defined as the start of
the step, was paused by a PAUS command and restarted without changing STEPNO.
TIP
For the operation block with the PAUS position defined as the stop line, “ckstep” returns the same data
when the block was paused by a PAUS command and restarted without changing STEPNO. Even after
the block has been restarted, “ckstep” returns the same data as that returned before the pause.

“ckstep” returns “1” when the SFC block was paused, STEPNO has been changed, and
then restarted.

● Cases of “0” Returned by “ckstep”
• When the operation is being executed without being paused.
• When the block was paused at the start of a step in the SEMI mode and has been
restarted without changing STEPNO.
• For interrupt signal processing, “0” is returned at all times.
• For status-change pre-processing, “0” is returned at all times.
• For status-change post-processing, “0” is returned at all times.
• For error processing, “0” is returned at all times.
• When the built-in function “ckstepcl” is executed to clear the status following a pause.
• When the action of the restarted step has been completed.
SEE ALSO
See D6.13.4, “Changing Current Step,” for the changing of data item STEPNO.
● Values Returned by ckstep for an Unit Instrument

When the operation is executed as an operation from the unit, “ckstep” additionally returns
the following values:
• When the unit instrument restarts execution and the operation begins executing after
the unit instrument has been paused and the unit instrument data STEPNO has been
changed, “ckstep” returns “101”.
• When the unit restarts execution and the operation resumes executing after the
operation BSTS had changed to PAUS because the unit status changed to the
PAUSED, “ckstep” returns “102” if the PAUS position defined as the start of the step.
If the PAUS stop position defined as the current line, “ckstep” returns the same value
when the execution restarts as the one returned prior to the pause.
• When the unit restarts execution and the operation resumes executing after the
operation BSTS had changed to STOP because the unit status changed to the SUS-
PEND, “ckstep” returns “103”.
• When the unit pauses at the top of the steps (of the unit) because the unit is in the
SEMI mode, and the unit restarts execution and the operation resumes executing
without changing the unit instrument data STEPNO, “ckstep” returns “0”.

■ Restarting Actions of an Operation
Actions when an operation block is restarted with its status changed to RUN are described:
● Restarting after Paused by SEBOL Scripted Action

The block restarts execution from the PAUS position defined on Function Block Detail
Builder. Execution is restarted from the start of the action when the start of the step is
builder-defined, or resumed from where the action was interrupted when the current line is
builder-defined.
● Restarting after Paused during Sequence Table or Logic Chart-defined

Action
The block restarts execution from the start of the step regardless of the PAUS position
defined on Function Block Detail Builder.
● Restarting after Paused during Transition Evaluation

Evaluation is restarted from the leftmost transition condition.
● Restarting after Paused during Interrupt Signal Processing

The interrupt signal process is canceled and not resumed when the block is restarted.
● Handling of Queued Signals when Restarted

Any signals already queued when the block was paused remain in the queue when the
block is restarted.
● Handling of Signal Received during Pause-

Any signals received during the pause are queued and available when the block is re-
started.
● Restarting After Paused during Error Processing

Restarting action varies depending on whether post-processing is executed or not when
PAUS was commanded.
• When post-processing is not executed:
The block is restarted first resuming the interrupted error processing and then resum-
ing the main program from the builder-defined PAUS position.
• When post-processing is executed:
The ongoing error processing is completed first and then the block status is changed
and post-processed when PAUS is commanded. The block resumes execution of the
main program from the builder-defined PAUS position when restarted.

D6.13.3 Referencing Current Step

The step number of the step being executed in the operation main program can be
referenced.
■ Procedure
Data item STEPNO can be used to reference the step number of the step being executed
in an operation. As the execution of the main program advances, the step number of the
current step is sent to STEPNO.
TIP
Data item PHASE is used to hold the name of the current process in the operation, which can also be
referenced to check the progress of the block execution. When using PHASE, however, every phase in
program steps should be uniquely named.

D6.13.4 Changing Current Step

The following items as to changing the current step are explained in this section.
• Procedure
• Restrictions
• Actions after STEPNO change
■ Procedure
The number of the current step can be changed by changing the step number set in main
program data item STEPNO when the operation block is PAUS status. The use of
STEPNO, however, is only applicable to main program steps but not to interrupt program
steps.
■ Restrictions
The number of the current step cannot be changed in the following cases:
• When status-change pre- or post-processing is being executed, even if the operation
block is in the PAUS status.
• Step numbers in the operation block cannot be changed, doing so causes error when
executed.
■ Actions after STEPNO Change

Actions following a step number change are as follows:
• No user-defined application program can be executed following a step number
change.
• When the block with the PAUS position defined as the current line is paused, the
restarting position may be changed to the start of step action by setting the current
step number in STEPNO.
• When the block is paused during transition condition evaluation, the restarting position
may be changed to the start of step action by setting the current step number in
STEPNO.
• The current STEPNO data is retained when the block status is changed to STOP.
• The block is restarted from the start of step action when a change to the RUN status is
commanded after STEPNO has been changed.
• The condition in which the block has been restarted can be identified using built-in
function “ckstep.”

D6.13.5 Operation Alarm Processing

In an operation, if required, the alarm processing and alarm status-indicating pro-
gram must be scripted in SEBOL.
■ Scripts of Operation Alarm Processing

Unlike regulatory control blocks, an operation block does not have built-in alarm-processing
functions. Thus the alarm processing and alarm status-indicating program must be scripted
in SEBOL when required.
The 4 data items of process alarms applicable to operations are as follows.
• ALRM (alarm status)
• AF (alarm detection specification)
• AOFS (alarm suppression specification)
• AFLS (alarm flashing status)
Data item ALRM identifies the state of occurrence and recovery (normal state) for each
alarm. It indicates NR when there is no alarm or the normal state has been restored. An
alarm status character string can be output using the “prcsalarm” statement when a pro-
cess alarm occurs in SEBOL steps. The “prcsalarm recover” statement is used to recover
from an alarm state.
SEE ALSO
• See C5, “Alarm Processing - FCS,” for the functions of AF, AOFS, and AFLS, which are the same as other
function blocks.
• See H1.5, “Function Block Data,” for the manner of changing and referencing alarm data items.

■ Changing Alarm Status of Operation Block
Data items AF, AOFS, and AFLS of operation block can be changed so that the block’s
alarm status can all be controlled. The following alarm status-change commands can be
used:
Table Alarm Status Change Commands
Status-change command
Data item
AOF AON ACK
AF Alarm detection group-bypassing. Alarm group-suppression. -
AOFS Undo group-bypassing. Undo group-suppression. -
AFLS - - Alarm group-acknowledging.
D061303E.EPS
■ Changing Alarms of Other Operation Blocks

Process alarms of other operation blocks can be controlled by changing data items AF and
AOFS.
The operation block with its data item AF externally specified for the group-bypassing of
alarm detection, for example, will not output any process alarm and the alarm status will not
be changed even when the “prcsalarm” statement is executed by the operation block. Also,
changing data item AFLS permits alarm acknowledging while disabling flashing.

■ Alarm Data Items
The alarm data items are initialized as follows:
Table Data Item Initialization
When initialization When Operation
Data item Name Default setting
started block is running
ALRM Alarm status NR NR
AF Alarm detection specification Previous status
maintained Previous status
AOFS Alarm suppression specification maintained Released status
D061304E.EPS
The alarm status is initialized to the normal status (NR) when the operation block is ex-
ecuted. When the execution of the block is terminated with any process alarm, the normal
state will be recovered when the block is executed again. This is the same when the block
mode is changed from O/S to AUT.
■ Operation Block Alarm Repeating

If an alarm state is not normalized for a predetermined period of time, repeating alarm
defined on FCS constants builder will be invoked as long as the operation block is being
executed or paused. The repeating alarm will not be initiated for the operation block not
being executed or paused, nor if the execution of the block has been terminated with a
process alarm.
Actions related to repeating alarms are the same as other function blocks.
SEE ALSO
See C5.15.2, “Repeated Warning Alarm,” for more information.

<Toc> <Ind> <D6.14 Interrupt Processing of Operation> D6-144
D6.14 Interrupt Processing of Operation

Operation interrupting processes are explained, in general, below.
■ Interrupting Processing of Operation

When an operation block status is changed for a pause or abort action, a program may be
required for the processing of the status change. For example, the heater needs to be
stopped when aborting the heating operation, or the valve needs to be closed when paus-
ing a tank charging operation.
The main programs for the ordinary processing can be scripted in the main planes, the
interrupting processes can be put into other planes according to the types of event.
● A SEBOL Operation Interrupt Program

An example of the SEBOL operation interrupt program is shown below:
Operation
Main program
SEBOL
Interrupt programs
SEBOL
D061401E.EPS
Figure A SEBOL Operation Interrupt Program

● An SFC Operation Interrupt Program
[STOP Processing] and [Emergency Shutdown] are two interrupt programs in an operation,
the extension of the [Emergency Shutdown] interrupt program is shown as follows.
Operation
Main program
Interrupt program
invoking
STOP processing
Emergency shutdown
Interrupt program
Emergency shutdown
Start of interrupt step
D061402E.EPS
Figure An SFC Operation Interrupt Program
Although the first step of the interrupt program is shown in a double square in the above
example, it does not mean that the step is the initial step.
Global variables cannot be declared using “global integer” or “global block” for the first step
of an interrupt program. They can be read or written, however.

■ Interrupt Program Types of Processing
Interrupt programs can be used for the following processing:
• Status change pre-processing
• Status change post-processing
• Interrupt signal processing
The following steps can be used in these interrupt programs as well as the main program:
Table Steps Applicable to SFC Programs
Program
Step Main Status change Status change Interrupt signal Error
program pre-processing post-processing processing processing
Initial step
SEBOL step
SEBOL one-shot step
Sequence table step
Sequence table

one-shot step
Logic chart step
Logic chart

one-shot step
Interrupt step
D061403E.EPS
Note: Transition can be defined for programs other than the status change pre-processing program.
: Applicable
Blank: Not applicable

■ Interrupt Program Parameters
Parameters must be specified according to the type of interrupt processing.
● For Status Change Pre-Processing & Post-Processing

One of the following parameters needs to be specified according to which status change
instruction is to be executed:
• RUN
Starts the operation block or restarts the paused operation.
• STOP
Terminates the operation block being executed.
• PAUS
Pauses the operation block being executed.
SEE ALSO
See D6.14.2, “Status Change Processing,” for more information.
● For Interrupt Signal Processing

The name of the signal needs to be specified to execute the interrupt program.
SEE ALSO
See D6.14.3, “Interrupt Signal Processing,” for more information.
● For Error Processing

No parameter can be specified for error processing.
SEE ALSO
See D6.14.4, “Error Processing,” for more information.

■ Interrupt Processing for Mode or Status Change
The following points should be noted regarding the operation interrupt processing executed
for mode or status changes.
• When unit instrument is given a mode change or a status change command, the
operation starts the interrupt process corresponds to the RUN, STOP or PAUS status.
• When a unit instrument changes its mode or status, for instance, the pre-processes of
RUN an operation will interrupt the unit instrument for mode change from RESTART,
AUT to SEMI. In the case like this, to change more than one mode or status of a unit,
the operation only interrupt once.
• To execute interrupt processing separately for each mode/status change command,
the built-in (SEBOL) function “creadpara(0)” can be used in the interrupting program.
With this creadpara(0) command, the mode change and status change command to
the unit will be returned
• When a unit is in SUSPEND status, only the operations in STOP state accept status
change command, the operations in RUN or in PAUSE state do not accept status
change command. Nevertheless, a Monitoring Operation will accept status change
command even in RUN or PAUSE state.

● Operation Interrupt Processes
Operation interrupt processings are shown as follows.
Table Overview of Operation Interrupt Processes
Interrupt Processing CREADPARA-read data Description
"RESTART" Restarting of operation from PAUS.
"" Restarting command from operation SFC window.
RUN pre-processing
"AUT" AUT command received during RUN.
"SEMI" SEMI command received during RUN.
"" Restarting command from operation SFC window.
RUN post-processing "AUT" AUT command received during RUN.
"RUN" When operation started (*1).
"PAUSE" PAUS command received.
"" PAUS command from operation SFC window.
PAUS pre-processing
"AUT" AUT command received during PAUS (*2).
"SEMI" SEMI command received during PAUS (*2).
"PAUSE" PAUS command received.
PAUS post-processing
"" PAUS command received from operation SFC window.
"END" Unit ending command received.
STOP pre-processing "" STOP command received from operation SFC window.
"SUSPEND" Unit procedure suspending command received.
STOP post-processing "" STOP command received from operation SFC window.
D061404E.EPS
*1: Post-processing is executed when operation is started at the start of a step during execution of a unit procedure. No
pre-processing is executed.
*2: Only pre-processing is executed for block mode (AUT, SEMI or stc.) change commands in the PAUS status. No post-
processing is executed.

● Monitoring Operation Interrupt Processes
Monitoring operation interrupt processings are shown as follows.
Table Overview of Monitoring Operation Interrupt Processes
Interrupt Processing CREADPARA-read data Description
"PSTART" Unit started
RUN pre-processing
"AUT" AUT command received during RUN.
"PSTART" Unit started
RUN post-processing "AUT" AUT command received during RUN.
"MSTART" When monitoring-operation started (*1).
"PAUSE" Operation PAUS command received.
"" PAUS command from operation SFC window.
PAUS pre-processing
"AUT" AUT command received during PAUS.
"SEMI" SEMI command received during PAUS.
"PAUSE" Operation PAUS command received.
PAUS post-processing
"" PAUS command received from operation SFC window.
STOP pre-processing "" STOP command received from operation SFC window.
STOP post-processing "" STOP command received from operation SFC window.
D061405E.EPS
*1: Post-processing is executed when monitoring operation is started. No pre-processing is executed.

D6.14.1 Queue Signal Processing

Queue signals are processed in the SFC main program.
■ Signal Declaration
Queue signals to be sent to the operation must be so declared in the initial step using the
“queue signal” statement.
queue signal<signal name>[,<signal name>…]

<signal name> a character string constant using up to 8 bytes.
D061406E.EPS
• The signal is ignored and error is returned to the source if an undeclared signal or any
non-defined interrupt signal is received.
• The “queue signal” statement can be used wherever declaration is allowed in the
initial step (global and local variable declarations).
• The “queue signal” statement cannot be used in steps other than the initial step.
• An error is caused if the same signal name is declared in duplication.
• An error is also caused if the same signal name as an interrupt signal name is de-
clared.
The following is an example of queue signal declaration:

queue signal "SG1,""SG2"
■ Signal Processing
The operation block fetches the first signal in the queue to process the signal in the main
program.
When the operation block in the RUN or PAUS status receives a queue signal, it is stored in
the signal queue. If the block is in a status other than RUN or PAUS, the received signal will
be ignored and an error will be returned to the signal source.
The operation block signal queue may be cancelled as required.
Queue signals are transmitted using the “signal” statement and pending signals can be
manipulated using “qsigcancel” and “qsigmove” statements.
SEE ALSO
See H1.12, “Signal Processing,” for the details of queue signal transmission and pending signal manipu-
lation.

■ Fetching Queue Signals
▼ Maximum Number of Queue Signal Parameters, Maximum Number of Acceptable Queue Signal
Parameters
The first signal in the queue is fetched for processing when the “wait for qsignal” statement
(see below) is executed in an operation block.
• Syntax for waiting for signal-receiving only:

wait for qsignal<signal name-storing variable>
• Syntax for waiting for signal-receiving or the expressed condition is satisfied:

wait for qsignal<signal name-storing variable>(<expression>)
errorsub
<signal name-storing variable>: Character-string local variable to store received
signal names.
<error variable>: Local variable for code-setting when error is caused
(0 when no error is caused).
<label>: Branching destination when error is caused.

<error identifier>: Local variable or constant to identify error-caused
locationin the error handling phase.
D061407E.EPS
The maximum number of received signal parameters can be specified in a range of 2 to 8

(2 at default) for the parameter attached to a queue signal on the Function Block Detail
Builder. Any signal received exceeding the specified number will be ignored, and initiate an
error.
The maximum number of signals received in the queue can be specified in a range of 0 to
99 (5 at default) on the Function Block Detail Builder. No additional signals can be received
exceeding the specified number. Any signal transmitted when the queue is full, an error will
be returned to the signal source.
The signal fetched used “wait for qsignal” statement from the queue and being processed
is included in the count of the specified maximum number of signals. The processed signal
will be dequeued when the next signal is fetched used wait for “qsignal” statement.

● Syntax of “wait for qsignal” Statement - Waiting only
This syntax is used to wait until a queue signal is received. If no signal is in the queue when
the “wait for qsignal” statement in this format is executed, the operation waits until a signal
is received while the queue is checked for any received signal once every scan period of
the block at most.
As soon as a signal is received and fetched from the queue for processing, the name of the
signal is stored in the specified variable.
TIP
• Status change pre-processing or post-processing, or interrupt signal processing will be executed
while the waiting for the receiving of queue signals.
• If time cannot be shared sufficiently for the once-every-scan-period check for received signals, the
check will be made no more than once every few scan periods.
● Syntax of “wait for qsignal” Statement - Waiting and Testing Conditions

This syntax is used to wait until a queue signal is received or the condition specified by the
expression is satisfied.
The expression is first calculated when the “wait for qsignal” statement in this format is
executed. If the result is true (other than 0), the condition is satisfied and the statement is
closed. If the result is false (0), the presence of signals in the queue is checked.
When the statement is closed with the condition satisfied, a null-length character string (“”)
is stored in the signal name-storing variable. When a signal has been fetched from the
queue, the name of the signal is stored in the variable. When the result of the expression is
false and no signal is in the queue, both the expression and the queue will be checked
once every scan period of the block at most.
<label> can be used to specify the destination for branching when error is caused. If “error”
or “errorsub” is not used, execution is resumed from the next statement when error is
detected.
Specifying <error identifier> permits to identify the error-caused location in the error han-
dling phase, which provides the identifier value using a built-in function.
TIP
It is recommended to use just one “wait for qsignal” statement, in either one of the two formats, in the SFC
block, and program so that execution returns to the statement for successive signal processing upon
completion of the current signal processing.
SEE ALSO
See H1.13, “Error Handling,” for the details of error processing.

■ Fetching Signal Parameters
Upon completion of the “wait for qsignal” statement with a signal fetched from the queue,
the parameter and name of that signal can be read.
Built-in function “creadpara,” “lreadpara,” or “dreadpara” can be used to read the signal
parameter; and built-in function “creadpara” can be used to read the signal name.

D061408E.EPS

“dreadpara” is a long double-precision floating-point real-number function, and they can be
used to read character-string, integer, and real-number signal parameters respectively.
Running any of these built-in functions after the expressed condition in the “wait for qsignal”
statement with waiting and testing condition options has been established will cause error
when executed.

■ Examples of Queue Signal Processing
Examples of queue signal processing using the syntax of the “wait for qsignal” statement
are shown below.
● Waiting for Signal

An example of executing the “wait for qsignal” statement with Waiting for Signal Syntax.
......
......
char*16 signame
J01
wait for qsignal signame
......
signame == "SG1" signame == "SG2"
J01 J01
D061409E.EPS
Figure Example of Queue Signal Processing Using Waiting for Signal Syntax
The “wait for qsignal” statement is executed in step 2 and a signal is fetched from the
queue. The signal name is then evaluated according to the transition condition defined
following step 2, selecting either SG1 or SG2 for processing.

● Waiting for Signal or Testing Condition
An example of executing the “wait for qsignal” statement with Waiting for Signal and Testing
Condition Syntax.
......
......
char*16 signame
J01
wait for qsignal signame (<expression>)
......
signame == "" signame == "SG1" signame == "SG2"

Process when
03 <expression> is 04 "SG1" process 1 06 "SG2" process 1
satisfied
J01 J01 J01

D061410E.EPS
Figure Example of Queue Signal Processing Using Waiting for Signal and Testing Condition
Syntax
The “wait for qsignal” statement is executed in step 2, determining to wait for a signal or to
calculate the expression. The result of the expression is checked for the first transition
condition defined following Step 2. Either SG1 or SG2 is selected for processing according
to the other two transition conditions.

■ Referencing
▼ Reference Signal Parameter Numbers
Either the signal name or the signal parameter of the queued signal can be set to
operation’s data item QUEUE[] as one element. All queued elements can be accessed by
SEBOL as CHR16 character-strings.
The data of the signal being processed can not be put into QUEUE[], only the data waiting
for processing can be put into QUEUE[] data item.
● Example of Referencing
When the queue has four signals, for example, referencing can be made as described
below:
SG1 SG2 SG2 SG1
SUMMER AUTUMN WINTER SPRING

*1 *1 *1 *1
*1: The first parameter

D061411E.EPS
Figure Queue Holding Four Signals
If the reference signal parameter number is 1, the contents of QUEUE elements are as
follows:
Queue[1] = "SUMMER"
Queue[2] = "AUTUMN"
Queue[3] = "WINTER"
Queue[4] = "SPRING"
Queue[5] = " "
.....
Queue[10] = " "
QUEUE[5] to QUEUE[10] are zero-length character strings since there is no data.

D6.14.2 Status Change Processing

There are following two types of the interrupt processes executed with a block
status change command:
• Status-change pre-processing
• Status-change post-processing
■ Processing Flow Operation

The flow of processing when an operation block receives a status change command is
shown below:
Status change command received
No
Is the command viable?
Yes
Executed as the
Status-change pre-process command is received.
No
Is the change feasible?
Yes
Status change executed
Status-change post-process
End
D061412E.EPS
Figure Flow of Status Change Process
As the operation block receives a status change command, the feasibility of the com-
manded change and the interrupt processes are checked in relation to the current status.
The conditions for block status changes are shown below:
Table Feasibility of Block Status Change
Status commanded for change
Current status
STOP RUN PAUS RSET ABRT
STOP (*1)
RUN (*1)
PAUS (*1)
ABRT (*1)
D061413E.EPS
: Status change feasible. Both pre- & post-processes executable.

: Status change feasible, but pre- & post-processes not executable.
Blank: Status change not feasible.
*1: Command ignored.

● Feasibility Checking
When an operation block current status is STOP and receives a command to change to
RUN or PAUS status, it will start a pre-process to interrupt the main program. If the block
receives a command to change to RSET, ABRT, or STOP status when current status is
STOP, an error will occur. A change command RSET is accepted only when the current
status is ABRT.
A change command ABRT can be accepted when the current status is RUN or PAUS.
When the operation block receives ABRT command, the operation block will be forcibly
terminated and the status will change to ABRT.
IMPORTANT
The command to change the status to ABRT is a command to forcibly terminate the opera-
tion block and should not be used during normal operation.
The ABRT command is different from other status change commands, the differences are
as follows.
• Pre- and post-processing cannot be defined for the command.
• The command can be received even when another status change command post-
processing is running.
● Pre-Processing
The feasibility of status change is determined in the pre-process. If the change is denied,
the source of the command is notified of the error. The status is changed as commanded if
the pre-process is not defined.
● Status Changing
The status of an operation block is changed as commanded when the change is justified
both in the initial check in relation to the current status and the check performed in pre-
processing.
● Post-Processing
Status-change post-processing is executed in accordance with the execution of the opera-
tion block itself, not with the receiving of the status change command.
The status change is prohibited when the current post-process is running; the received
status change command will be treated as an error and ignored.

■ Status Change Pre-Process - Operation
The status-change pre-process is one-shot-executed upon receipt of the status change
command before changing the block status. There are three types of scripts for status-
change pre-process.
• Sequence table one-shot execution step (Sequence table one-shot)
• Logic chart one-shot execution step (Logic chart one-shot)
Since the status-change pre-process is one-shot-executed, it must be completed as quickly

as possible. Do not access data of another control station and delay the process. Only one
step can be executed as pre-process, where no transition condition can be defined.
STOP
01 Pre-process
D061414E.EPS
Figure Status-Change Pre-Process
At the SEBOL and sequence table one-shot steps, the feasibility of status change can be
determined. With the logic chart one-shot step, the status can be changed. If the pre-
process is not defined, the status can also be changed. At the pre-process, the status and
mode of the pre-process-described operation block or other operation blocks cannot be
changed.

● Pre-Processing Using SEBOL Oneshot Step
The SEBOL oneshot step will be completed when the last line, or “return” or “quit” state-
ment is executed.
If the last line or “quit” statement is executed, the feasibility of status change will be tested.
If the “return” statement is executed, the feasibility of status change will be determined
according to the returned value as follows:
return[<status change feasibility>]
<status change feasibility>: Integer constant or numerical expression.

==0: Change denied.
<>0: Change justified.
Omitted: Change justified.
D061415E.EPS
The SEBOL oneshot step in which the pre-process is defined has the following additional
restrictions over the normal steps:
• “exit” statement cannot be used. Error occurs if used.
• “signal” statement cannot be used. Error occurs if used.
• “qsigcancel” and “qsigmove” statements cannot be used. Error occurs if used.
• “isigmask” and “isigunmask” statements cannot be used. Error occurs if used.
• “semlock”: and “semunlock” statements cannot be used. Error occurs if used.
• In the case of fatal error, only a SEBOL error message is output and the operation
block is not terminated. Any status change will be denied.
• When an execution error is detected, no branching is made to common error process-
ing and a SEBOL error message is output. Any status change will be denied.
• The block status and mode of the present operation block or any other operation block
cannot be changed.

● Pre-Processing Using Sequence Table One-Shot Step
In the sequence table one-shot step, the feasibility of status change is determined accord-
ing to the result of sequence-table evaluation. The status change is justified when the result
is true (1) and denied if false (0).
• Non-step sequence table:
The condition testing result is true (1) when at least one of 32 rules is satisfied and
false (0) if none of them is satisfied.
• Step sequence table:
All rules of the oneshot-executed step and step 00 are evaluated and the result is true
(1) when at least one of the rules is satisfied and false (0) if none of them is satisfied.
In the pre-process, no variable can be specified to receive the condition testing result, any
specified variable is ignored. The block status and mode cannot be changed in pre-pro-
cessing for the operation block in which the pre-process is defined or for any other opera-
tion block.
● Pre-Processing Using Logic Chart One-Shot Step

With the logic chart one-shot step, the status can be changed. At the pre-processing, the
status of the pre-process-described operation block or other operation blocks cannot be
changed.

■ Status Change Post-Process - Operation
The status-change post-process will be executed after the status is changed. The process
is executed as an interrupt signal processing, interrupting the main program in accordance
with the basic scan period of the operation block.
Both step and selective sequences can be used in the post-process. A status change
command is prohibited when the current post-process is not completed; the command will
be ignored if received, causing error.
IMPORTANT
The post-process should not be kept suspended by means of a selective sequence transi-
tion condition, or a “wait until,” “compare,” or “dialogue” statement. If the process is sus-
pended, the block status cannot then be changed unless the program is forcibly terminated
using a command to change to ABRT.
The execution of the post-process defined in a SEBOL step can be controlled using “quit”
and “return” statements:
Executing this statement in a step sequence terminates the current action and ex-
ecutes the next step. Executing it in a selective sequence starts evaluation of transi-
tion conditions. Executing the statement in the last post-process step terminates the
process.
Executing this statement terminates the post-process without executing the remaining

■ Referencing Block Status - Operation
Data item PREBSTS (previous block status) is used in the post-process to permit referenc-
ing the block status before the change. When the status is changed, data item BSTS (block
status) which contains information on the status before the change is copied to PREBSTS.
These two data items are operated as follows:
1. The BSTS data is copied to PREBSTS.
2. BSTS is changed to the new block status.
The BSTS data is referenced for testing the feasibility of block status change in the pre-
process. The PREBSTS data is also referenced in the post-process. Referencing BSTS
and PREBSTS take place in the following timings:
• When the current status of RUN is changed to STOP by a commanded.
• When the current status of PAUS is changed to STOP by a commanded.
Table BSTS & PREBSTS

RUN ➝ STOP PAUS ➝ STOP
Process being executed
BSTS PREBSTS BSTS PREBSTS
Status-change pre-process RUN (*1) PAUS (*1)
Status-change
STOP RUN STOP PAUS
post-process
D061416E.EPS
*1: Previous status.

● Operation Block Status Referencing in Pre-Process
An example of referencing the block status in the pre-process. The two different scripts are
based on the current status of the operation block.
switch (%.BSTS)
case "RUN":
!Process changing from RUN to STOP.
case "PAUS"
!Process changing from PAUS to STOP.
end switch
● Operation Block Status Referencing in Post-Process

An example of referencing the block status in the post-process. The two different scripts
are based on the current status of the operation block.
switch (%.PREBSTS)
case "RUN"
!Process when changed from RUN to STOP.
case "PAUS"
!Process when changed from PAUS to STOP.
end switch

■ Changing Status of the Unit Instrument
When the status (data item BSTS) of the unit instrument is changed, the operation can
perform status-change pre- and post- processing. The status-change pre- and post- pro-
cessing is created as an interrupt program.
SEE ALSO
See D6.6, “State Transition Matrix,” for more information on the execution timing of the operation status-
change pre- and post- processing and the rules for changing block status of an operation when the status
of the unit instrument changes.
● “independent” Statement
The monitoring operation is a special operation for monitoring the unit instrument. Use the
“independent” statement to make the monitoring operation continue to execute even when
the unit instrument stops or pauses.
The “independent” statement can be scripted anywhere so long as it is a place where a
declare statement for the initial step can be written in the operation. The action of an opera-
tion using the “independent” statement is as follows:
• An operation that uses “independent” statement executes status-change pre- and
post- processing.
• The block status of an operation that uses “independent” statement does not change.
For example, actions that occur when PAUS is specified in the action instruction for the unit
instrument are shown in the table below.
Table Difference of Operation (PAUS) by Presence/Absence of “independent” Specification
Execution
independent Pre-processing for status change Post-processing for status change BETS
status
Used Executes PAUS pre-processing Executes PAUS post-processing No change No change
Changed to
Not used Executes PAUS pre-processing Executes PAUS post-processing PAUS
PAUS
D061417E.EPS
For example, actions that occur when RSM is specified in the operation instruction for the
unit instrument are shown in the table below.
Table Difference of Operation (RSM) by Presence/Absence of “independent” Specification
Execution
independent Pre-processing for status change Post-processing for status change BETS
status
Used Executes RUN pre-processing Executes RUN post-processing No change No change
Changed to Restarts
Not used Executes RUN pre-processing Executes RUN post-processing
RUN execution
D061418E.EPS

Even if a STOP change command is output to an operation (via the unit instrument) with
the “independent” specification, the operation does not stop and the block status remains
unchanged. Only the STOP status-change pre-process and post-process are executed.
Similarly, even if a PAUS change command is output to an operation (via the unit instru-
ment) with the “independent” specification, the operation does not pause and the block
status remains unchanged. Only the PAUS status-change pre-process and post-process
are executed.
Unless the status change command of an operation including the monitoring operation
goes through the unit instrument, the change command will not be output.
To force the termination of an operation with the “independent” specification, output an
ABRT change command to the operation. If the MSTART change command is output to the
unit instrument, the monitoring operation that was forcibly terminated can be restarted.
The following precautions are necessary when using an “independent” statement in other
than the monitoring operation:
• The unit instrument can be stopped even when an operation with the “independent”
specification is being executed.
When the execution of the independent operation is completed, the unit instrument
stops.
• To stop the unit instrument immediately, terminate the execution by using an “exit”
statement in the status-change post-process of the independent operation.
TIP
The unit instrument can be stopped even when the monitoring operation has an “independent” specifica-
tion and is being executed.

● “ckstep” Statement
The built-in function ckstep may be applied to check if the operation block is restarted after
the block is paused.
SEE ALSO
See “■ Identification of Restart Condition,” in D6.13.2, “Pause an Operation,” for more information on the
return value of the built-in function “ckstep()” when the operation block is executed.
● “creadpara” Statement
In an operation, when “creadpara” is executed by specifying “0” in the argument of the
status-change pre-process or post-process for RUN, PAUS or STOP, the mode/status
change command for the unit instrument can be acquired.
!Step scripted in SEBOL for operation block
char*8 stscmd
stscmd = "creadpara" (0) !Acquire a status change command for the unit instrument
.....
When manually change an operation block status, if “creadpara” is executed by specifying

“0” in the argument for the status-change pre-process or post-process, it returns a “” (a
character string of length 0).

D6.14.3 Interrupt Signal Processing

Interrupt signal processing is executed interrupting the main program when an
interrupt signal is received.
■ Interrupt Signals
Interrupt signals are sent from the operation block, sequence table and logic chart. Every
interrupt signal can be named using a character string of up to 8 bytes and attached with up
to 8 parameters.
Whether a signal is taken as a queue signal or an interrupt signal depends on the definition
in the operation block which receives the signal and cannot be specified at the signal
source.
Queue and interrupt signals are distinguished as follows:
• Signals defined in the initial step using the “queue signal” statement are handled as
queue signals.
• Signals having their names written at the entrance of interrupt signal processing are
handled as interrupt signals.
If the same name is used both in the initial-step definition and at the interrupt-signal en-
trance, an error will occur.
Interrupt signals can be received only when the operation block is in the RUN or PAUS
status, any signal transmitted is ignored otherwise and an error is returned to the source.
Interrupt signals received during the course of the PAUS status are stored in a queue and
will be processed when the status is changed to RUN for restarting the block.

■ Interrupt Signal Processing
▼ Maximum Number of Receive Interrupt Signals
Interrupt signals are processed interrupting the main program, which resumes execution as
soon as the signal has been processed.
Main program Interrupt signal processing
Interrupt signal received
D061419E.EPS
Figure Interrupt Signal Processing
Interrupt signals can be processed only when the operation block is in the RUN status. The
signal processing is canceled if the status is changed to PAUS during the processing and
will not be resumed when the status is returned to RUN.
If another interrupt signal is received while one is being processed, the received signal is
queued and will be processed as soon as the current processing is completed. The maxi-
mum number of interrupt signals which can be queued can be defined for each operation
block using the Function Block Detail Builder. The number is 5 at default and can be de-
fined up to 99. The defined capacity includes the signal currently being processed. If a
signal is received when the queue is full, the signal is ignored causing an error.
The execution of the interrupt signal process defined in a SEBOL step can be controlled
using “quit” and “return” statements:
Executing this statement terminates the current step action and executes the next
step. Executing it in a selective sequence starts evaluation of transition conditions.
Executing the statement in the last step of interrupt signal processing terminates the
process.
Executing this statement terminates the process without executing the remaining

■ Fetching Interrupt Signal Parameters
▼ Maximum Number of Interrupt Signal Parameters
Queue signal parameters can be fetched using built-in functions during interrupt signal
processing.

D061420E.EPS

used to fetch character-string, integer, and real-number signal parameters respectively.
The maximum number of signals can be defined in a range of 2 to 8 (2 at default) for the
parameter attached to an interrupt signal. If the operation block receives an interrupt signal
exceeding its parameter setting, the signal is ignored causing an error.

D6.14.4 Error Processing

Error processing needs to be defined in an operation block separately from the
operation block of the main program. Only one set of processing can be scripted in
one operation block.
■ Error Processing Description

Similar to other interrupt processes, error processing needs to be defined in an SFC sepa-
rately from the operation of the main program. Only one set of processing can be described
in one operation.
Both step and selective sequences can be used in error processing. It is necessary for a
selective sequence, however, that the transition conditions are so defined that they can be
easily satisfied; the process being executed when error is caused will not be resumed
otherwise.
SEE ALSO
See H1.13, “Error Handling,” for the details of common error processing.
The execution of the error processing defined in a SEBOL step can be controlled using
“quit” and “return” statements:
Executing this statement in a step sequence terminates the current step action and
executes the next step. Executing it in a selective sequence starts evaluation of
transition conditions. Executing the statement in the last error processing step termi-
nates the process.
Executing this statement can terminate error processing without executing the remain-
ing steps. Any operand specified in this statement will be ignored.

<Toc> <Ind> <D6.15 Initialization Operation and Monitoring Operation> D6-173
D6.15 Initialization Operation and Monitoring

Operation
Initialization and monitoring operations can be executed in a unit instrument in
addition to other operations started from the unit procedure.
FCS starts.
Initialization
operation executed.
First time N
after system start?
Monitoring
operation starts.
Wait for unit start.
starts.
Unit procedure
executed.
D061501E.EPS
Figure Initialization Operation and Monitoring Operation

■ Initialization Operation
▼ Initialize Operation
The initialization operation is applied to carry out the process initialization for a unit instru-
ment to run its procedure. The operation designated as the initialization operation will be
definitely started at the beginning of the system start or right after the unit instrument
complete its unit procedure.
When a unit instrument is running the initialization operation, it does not accept mode
change or status change command until the initialization is completed.
There is one exception, the command for changing to O/S mode will be accepted even
when the initialization operation is running. When the O/S command is received, the
initialization operation will be immediately terminated.
When the O/S mode is canceled, the block mode returns to its previous mode first then
changes to END status, thus the initialization operation will then be started again.
The interrupt processing for mode and status changes can not interrupt the initialization
operation.
The initialization operation’s name may be defined on the Function Block Detail Builder for
the unit instrument. It is required to put the initialization operation in the same drawing with
the unit instrument.

■ Monitoring Operation
▼ Monitoring Operation
A monitoring operation is the operation applied for monitoring the unit instrument especially
when the equipment entity is required to be monitored even when the unit procedure is not
running.
The monitoring operation is started when the system starts. It is different from the initializa-
tion operation, a unit instrument can only start the monitoring operation but does not care
for its stop. When the monitoring operation is stopped for some reason, it may be restarted
by sending a MSTART status-change command from the unit instrument.
When a block mode or status change command is sent to the unit instrument, the monitor-
ing operation will be notified to advance to the state in accordance with the state transition
matrix. The interrupt processing for mode and status change will interrupt the monitoring
operation.
The monitoring operation’s name may be defined on the function block detail builder for the
unit instrument. Each unit instrument may have two monitoring operations. It is required to
put the monitoring operations in the same drawing with the unit instrument.
● Continuous Execution of Monitoring Operation with “independent”

Statement
When a unit block mode or status change command is given to the monitoring operation,
the monitoring operation may be paused or stopped in accordance with the state transition
matrix same as other operations.
To avoid this and keep the monitoring operation continuously executed, describe the
“independent” statement, which is a SEBOL declaration statement, in the first step of the
monitoring operation.
An operation with "independent" statement may only be aborted when the unit instrument
send a command (ABRT) for changing to O/S state. When recovered from O/S state, the
monitoring operation will be restarted.
To terminate the “independent”-specified monitoring operation, declare termination of the
program using the “exit” statement. To specify the termination of the operation when it is
notified of the ABRT command, describe the “exit” statement at the end of the interrupt
processing for the command.

Blank Page
<Toc> <Ind> <D7. Valve Pattern Monitors> D7-1
D7. Valve Pattern Monitors

The valve pattern monitor is a function block which runs in an FCS (Field Control
Station). One valve pattern monitor can simultaneously monitor a maximum of 512
valves in a transfer-system plant.
This valve pattern monitor is controlled by a user created application program as the
operation of a unit.
■ Position of Valve Pattern Monitor £

The valve pattern monitor is one of the functions runs in FCS.
This valve pattern monitor is controlled by the user application represents a operation
scripted in SEBOL statements (i.e. an SFC block initiated from a “Unit” in the unit supervi-
sion function).
Placement of Valve Pattern Monitor is shown as follows.
FCS
Basic control
Software I/O
Arithmetic calculation blocks Sequence control message
Faceplate blocks
SFC blocks
Options
FCS I/O Interfaces
D070001E.EPS
*1: ¡ £ Valve pattern monitoring and off-site blocks are available in CS 3000.
Figure Position of Valve Pattern Monitor £
SEE ALSO
For information about the unit supervision function, refer to D6, “Unit Supervision.”

■ Function of Valve Pattern Monitor £
● Simultaneous Monitoring of Multiple Valves £

The valve pattern monitor is a function block for monitoring the valve opening/closing state
in a transfer-system plant. One valve pattern monitor can simultaneously monitor a maxi-
mum of 512 valves in a transfer-system plant.
The valves to be monitored are registered in the valve pattern monitor under operation of a
unit. SEBOL statements specific to the valve pattern monitor are used to register the valves
to be monitored.
● Abnormality Signal £
The valve pattern monitor returns an alarm signal to the unit upon detection of a valve
abnormality. If such a signal is received, the unit performs alarm processing.
Prior to using the valve pattern monitor, create the alarm process program for abnormality
detection, and incorporate it in the operation of the unit.
The following figure shows the configuration of a valve monitoring system which uses the
valve pattern monitor.
Unit
User Application
Monitoring operation
Signal transmission
Valve Pattern Monitor
Securing the valve
Operation pattern monitor
vpmstart SIO302.PV
Reference value (PV)
• Output
drive vpmon SIO302.PV Reference value (MV) SIO302.MV

Output
• The acquired data is compared
• with the reference values. If they
are not identical, the valve pattern
monitor transmits a signal.
Answer-back
check result
Data is acquired once
per monitoring cycle.
Function
block
PV
MV value MV
Remark
: Operation made with SEBOL
statements
: Data acquisition by the valve
pattern monitor
: Operation made with function
block
Valve
D070002E.EPS
Figure Example Configuration of Valve Monitoring System £

● Run Screen Display: Tuning Screen £
The following figure shows the Tuning screen of the valve pattern monitor. This screen
displays valve pattern monitor run statuses such as the block mode, alarm status, and
block status.
SOVP64 TUN
SOVP64
MODE = AUT ALRM : VPTN BSTS = RUN SOVP64
OWNER : SOUNT201
ENTRY [ 3, 64]
AUT RUN
VPTN
RUN
PAUSE
STOP
Ready
D070003E.EPS
Figure Tuning Screen of Valve Pattern Monitor £
■ SEBOL Statements Specific to Valve Pattern Monitor £

There are six SEBOL statements specific to the valve pattern monitor. These statements
are used for creating application programs.
● vpmstart Statement £
This statement secures the specified valve pattern monitor and makes it available.
● drive vpmon Statement £

This statement checks the valve to be monitored for output operation, then registers the
object valve in the valve pattern monitor.
If the drive vpmon statement is executed, it modifies the output status of the function block
(motor control block or switch instrument block) to be operated by this statement, and it
checks the valve for proper operation using the answer-back check of the function block.
Then, the valve to be monitored and the data will be registered in the valve pattern monitor.

● drive vpmoff Statement £
This statement deletes registration of the object valve and data, and then it checks the
output operation of the valve.
If the drive vpmoff statement is executed, it deletes registration of the object valve and data,
and then it sets the data for modifying the output status in the function block which operates
the valve deleted from the valve pattern monitor.
● vpmon Statement £
This statement registers the object valve and data in the valve pattern monitor. It does not
perform output operation of the valve, which is different from the drive vpmon statement.
Normally, vpmon statement is used after the output action of the valves under the monitor-
ing of drive statement.
● vpmoff Statement £
This statement deletes registration of the object valve and data from the valve pattern
monitor. It does not perform output operation of the valve, which is different from the drive
vpmoff statement.
● vpmreset Statement £
This statement deletes all of the object valves and data registered in the valve pattern
monitor.
TIP
If the drive vpmoff statement or the vpmoff statement is used, monitoring of any one of the valves can be
stopped (i.e. any object valve that has been registered in the valve pattern monitor can be deleted).
Also, the valve pattern monitor can be paused and resumed by modifying the block status of the valve
pattern monitor.
SEE ALSO
• For more information about the above SEBOL statements, refer to D7.8, “SEBOL Statements for Valve
Pattern Monitor.”
• For information about the block status of valve pattern monitor, refer to D7.6, “Block Status of Valve
Pattern Monitor.”
■ Creating Application Programs £

Before using any valve pattern monitor, it is necessary to create an operation for the valve
pattern monitor and to specify the required builder definition items. The processing timing
of the valve pattern monitor should also be specified if required.
User can check whether the valve pattern monitor is operated properly by the created
application program, using the simulation function.

<Toc> <Ind> <D7.1 Valve Pattern Monitor Type and Size> D7-5
D7.1 Valve Pattern Monitor Type and Size

There are eight types of valve pattern monitors. Select the appropriate one accord-
ing to the number of valves to be monitored and whether there is a need for alarm
checking in the transfer-system plant.
■ Valve Pattern Monitor Type and Size £

Of the eight types of valve pattern monitors, four types have a different number of valves
that can be monitored without the alarm check function and the other four types have a
different number of valves that can be monitored with the alarm check function. Each of
them has a different application capacity in the FCS database area (application loading
area). Select the appropriate type of valve pattern monitor according to the transfer-system
plant to be monitored.
Table Valve Pattern Monitor Type and Size £
Block type Name
VPM64 64-Data Valve Pattern Monitor
VPM64A 64-Data Valve Pattern Monitor with Alarm
D070101E.EPS
Valve pattern monitors with an alarm check determine if the alarm status of the specified
valve is “NR.”
TIP
For the valve pattern monitor to be used for monitoring valves, define the tag name and the function block
model name using the control drawing builder, the same as the PID Controller Block and the sequence
table block. Then specify the valve pattern monitor to be used for monitoring valves by the vpmstart
statement using the tag name which is defined previously.
Specify the valve pattern monitor by the vpmstart statement before specifying the valves to be monitored
by the drive vpmon or vpmon statement.

<Toc> <Ind> <D7.2 System Environment> D7-6
D7.2 System Environment

This section describes the hardware and software environments required to operate
the valve pattern monitor.
■ Hardware Environment £
● Object Hardware £
PFCS-H, PFCD-H, AFS10S, AFS10D, AFS20S, AFS20D, AFS30S, AFS30D, AFS40S,
AFS40D, AFS71S, AFS71D, AFS72S, AFS72D, AFS81S, AFS81D, AFS82S, AFS82D,
AFS83S, AFS83D, AFS84S, AFS84D
● Main Memory £
16 Mbytes
■ Software Environment £
● Valve Pattern Monitor Package £

Supported in standard control function (LFS1100) and compact control function (LFS1120).
SEE ALSO
To use the valve pattern monitor, an optional program name must be registered in the FCS. For informa-
tion about registration, refer to D7.10, “Builder Items for Creating Application Program.”

<Toc> <Ind> <D7.3 Procedure for Operating Valve Pattern Monitor> D7-7
D7.3 Procedure for Operating Valve Pattern Monitor

To operate the valve pattern monitor, the builder of the valve pattern monitor blocks must
be defined, and the operation (application program) must be scripted in SEBOL statements
dedicated for the valve pattern monitor.
■ Procedure for Operating Valve Pattern Monitor £
Setup start
Install the valve pattern monitor package.
Determine the type and number of

valve pattern monitors to be used. • • • See D7.1,
“Valve Pattern Monitor
Type and Size.”
Specify the builder definition items of
valve pattern monitor blocks using • • • See D7.10,
the Function Block Overview Builder. “Specifying Builder Definition
Items for Creating Application
Program.”
Create an operation • • • See D7.8,

“SEBOL Statements for
Valve Pattern Monitor.”
See D7.11,
“Example of Creation
Run Application Program.”
Remark
: Work flow
D070301E.EPS
Figure Procedure for Operating Valve Pattern Monitor £
SEE ALSO
For details on installing valve pattern monitoring function, refer to CS 3000 Installation (IM 33Q01C10-
01E).

<Toc> <Ind> <D7.4 Data Items for Valve Pattern Monitor> D7-8
D7.4 Data Items for Valve Pattern Monitor

There are 31 data items in the valve pattern monitor.
Of those items ENTRY is a special data item that has an array. The data stored in
ENTRY differs depending on the value of array elements.
NUM1, NUM2, NUM2CHK, and HMAX are data items related to the number of pieces
of data. Refer to these data item values if checking whether the valve pattern moni-
tor to be used is appropriate.

■ Data Items £
Each data item of the valve pattern monitor can be accessed through execution of SEBOL
statements from the operation, and through entry from the operation and monitoring function (in ICS).
The data items of the valve pattern monitor are listed in the following table.
Table Data Items £
Symbol Name Data type Entry Range Default
MODE Block mode char*8 YES NO “AUT”
OMOD Block mode (lowest priority) char*4 NO NO “AUT”
CMOD Block mode (highest priority) char*4 NO NO “” (*1)
BSTS Block status char*8 (*2) NO “STOP”
ALRM Alarm status char*8 NO NO “NR”
AFLS Alarm flashing status char*8 NO NO “” (*1)
AF Alarm detection specification char*8 NO NO “” (*1)
AOFS Alarm suppression specification char*8 NO NO “” (*1)
OPMK Operation mark integer YES 0 to 255 0
SAID System user ID integer YES NO 0
UAID User application ID integer YES NO 0
OWNER Owner (unit name) char*16 NO NO “” (*1)
ENTRY[3,N] Registration data char*16 NO NO “” (*1)
Number of pieces of data in the
NUM1 integer NO 0 to 512 0
present station
Number of pieces of data in other
NUM2 integer NO 0 to 512 0
stations
Number of pieces of data in other
NUM2CHK integer NO 0 to 512 0
stations to be monitored
History of the maximum number of
HMAX integer NO 0 to 512 0
pieces of data
SIMM Simulation switch integer NO 0 to 1 0
ERRE Error code long NO NO 0
SGNLTAG SGNL alarm, tag name char*16 NO NO “” (*1)
SGNLITEM SGNL alarm, data item char*16 NO NO “” (*1)
SGNLERRE SGNL alarm, error code long NO NO 0
VPTNTAG VPTN alarm, tag name char*16 NO NO “” (*1)
VPTNITEM VPTN alarm, data item char*16 NO NO “” (*1)
VPTNERRE VPTN alarm, error code long NO NO 0
DATATAG DATA alarm, tag name char*16 NO NO “” (*1)
DATAITEM DATA alarm, data item char*16 NO NO “” (*1)
DATAERRE DATA alarm, error code long NO NO 0
TYPETAG TYPE alarm, tag name char*16 NO NO “” (*1)
TYPEITEM TYPE alarm, data item char*16 NO NO “” (*1)
TYPEERRE TYPE alarm, error code long NO NO 0
D070401E.EPS
YES: Entry from the operation and monitoring function is allowed.

NO: Entry from the operation and monitoring function is not allowed.
*1: Double quotation marks (“”) stand for null.
*2: In the entry from the operation and monitoring function, the block status, BSTS cannot be modified from “STOP” to “RUN.”

TIP
The data items listed in Table are all objects to be saved as tuning parameters.
■ Data Stored in Data Item “ENTRY[3,N]” £

The registration data is stored in ENTRY[3,N]. The data stored in ENTRY[3,N] can be
displayed in the operation and monitoring function.
The number of elements in ENTRY[3,N] differs depending on the type of valve pattern
monitor. The following table lists the number of elements in ENTRY[3,N] for various types.
• VPM64, VPM64A: ENTRY [3,64]
• VPM128, VPM128A: ENTRY [3,128]
• VPM256, VPM256A: ENTRY [3,256]
• VPM512, VPM512A: ENTRY [3,512]
The data registered by the SEBOL statement (drive vpmon statement or vpmon statement)
is stored in ENTRY. The following table lists the data stored in ENTRY.
Table Data Stored in ENTRY £
Kind of
Content Remark
ENTRY
If a generic name is set in the drive vpmon or vpmon statement, a tag
ENTRY[1,N] Tag name
name corresponding to the generic name is stored in ENTRY[1,N].
ENTRY[2,N] Data item
Reference value
ENTRY[3,N]
and status
D070402E.EPS
● Example of Data Storing in ENTRY[3,N] £

The relationship between the execution content of the SEBOL statement and the data
stored in ENTRY[3,N] is described below as an example.
The vmpon statement in the first line sets the reference value to 1 and the signal parameter
to 0.
Both MV and PV may be displayed on the operation and monitoring window by the third
line script.
vpmon [SW101.PV==1:0]
vpmon [SW301.PV==0:0]
drive vpmon [SIO301=2:10]
The execution results of the above SEBOL statements are displayed in the operation and
monitoring function as follows.
ENTRY [1,1] SW101 ENTRY [2,1] PV ENTRY [3,1] 1 a 0 8EBD
ENTRY [1,2] SW301 ENTRY [2,2] PV ENTRY [3,2] 0 a 0
ENTRY [1,3] SIO301 ENTRY [2,3] MV ENTRY [3,3] 2 a 1 0
ENTRY [1,4] SIO301 ENTRY [2,4] PV ENTRY [3,4] 2 1 0

The reference value, signal parameter, error code, etc., have been set in each ENTRY
displayed in the operation and monitoring function. For example, the execution results
displayed in [ENTRY[3,1]], among those in the operation and monitoring function, have the
following definitions.
ENTRY [3,1] 1 a 0 8EBD
Error code
Space (present station data) / s (other station data)
Parameter
Space (ALARM check not performed) / a (ALARM check performed)
Reference value
D070403E.EPS
Figure Screen Display Definitions £
If there is no abnormality with the data, only a reference value and a parameter are dis-
played in the operation and monitoring function. If there is an abnormality with the data, a
4-digit hexadecimal error code is displayed (at the right of parameter), in addition to the
reference value and parameter. In the above example, the error code is displayed in EN-
TRY[3,1], and therefore, SW101.PV is assumed to have an error.
● Rule for Data Storage in ENTRY[3,N] £

• If registration of the valves to be monitored is reset in the drive vpmoff or vpmoff
statement, the character strings stored in ENTRY[1,N], ENTRY[2,N], and ENTRY[3,N]
are cleared.
• Even if the valve pattern monitor with the alarm check function is used, <tag
name>.ALRM is not stored in ENTRY.
• If multiple pieces of data with different data items are registered under the same tag
name for the valve pattern monitor with the alarm check function, the valve pattern
monitor checks ALRM for one piece of data. “a” (ALRM check performed) is stored in
data item ENTRY[3,N] of the data to be checked.
• If the reference value is between -32768 and 32767, it is stored in ENTRY[3,N] in
decimal notation. If the reference value is out of that range, it is stored in hexadecimal
notation.
• If the data registered in ENTRY resides in an FCS other than the valve pattern moni-
tor, “s” (other station data) is stored in ENTRY[3,N]. If any registered data is not
acquired because of a different tag name, “s” is also stored in ENTRY[3,N].
SEE ALSO
The error code is the same as the details of SEBOL error code. For the error code, refer to H1, “SEBOL
Details.”

■ Data Items Related to Number of Pieces of Data £
NUM1, NUM2, NUM2CHK, and HMAX are data items related to the number of pieces of
data. Operation of the valve pattern monitor can be determined from those data item
values.
● NUM1 £
NUM1 stores the number of pieces of present station data currently registered. The present
station data represents the data which resides in the same FCS as the valve pattern
monitor.
The NUM1 value increases as data is registered with the drive vpmon statement or vpmon
statement. The NUM1 value decreases as registered data is deleted with the drive vpmoff
statement or vpmoff statement.
● NUM2 £
NUM2 stores the number of pieces of other station data currently registered.
The other station data represents the data which resides in the FCS in which the valve
pattern monitor does not reside.
The NUM2 value increases as data is registered with the drive vpmon statement or vpmon
statement. The NUM2 value decreases as registered data is deleted with the drive vpmoff
statement or vpmoff statement.
● NUM2CHK £
NUM2CHK stores the number of pieces of other station data that have been actually
checked within the monitoring cycle.
If all pieces of other station data can be checked within the monitoring cycle, the
NUM2CHK value will be identical to the NUM2 value. Depending on communication timing,
the NUM2CHK value may temporarily be greater than the NUM2 value.
If many pieces of other station data have been registered in the valve pattern monitor which
resides in the FCS, it may not be possible to check all pieces of other station data within the
monitoring cycle. The number of pieces of other station data that has been checked can be
confirmed with NUM2CHK.
The NUM2CHK value will be 0 immediately after initiating the valve pattern monitor with the
vpmstart statement, or after modifying the valve pattern monitor data item BSTS from
“PAUS” to “RUN.”
TIP
Monitoring scan cycle is a number stands for the multiple of the basic scan period (one FCS data acquisi-
tion scan time), means among this number of data acquisition scans, only one scan have monitoring
process. A valve pattern monitor checks the gathered data once per how many basic scans is indicated
by the number for monitoring scan cycle setting.
The default setting for valve pattern monitoring cycle is fixed as 5. It means, the monitoring process takes
place at every 5 basic scans.

● HMAX £
HMAX stores the maximum total of NUM1 and NUM2.
The number of valves to be monitored with the valve pattern monitor is obtained from the
HMAX value. This allows the user to determine whether the appropriate type of valve
pattern monitor has been selected according to the number of valves to be monitored.
The HMAX value will be 0 immediately after the valve pattern monitor data item BSTS is
modified from “STOP” to “RUN.” If the NUM1 and NUM2 values have increased because
additional data is registered with the drive vpmon or vpmon statement, the HMAX value will
be the total of the NUM1 and NUM2 values.
However, even if the registered data is reset with the drive vpmoff, vpmoff, or vpmreset
statement, the HMAX value will not decrease.
SEE ALSO
• For information about acquisition and inspection of other station data, refer to D7.9, “Inspection of Data
Acquired from FCS.”
• For information about error codes stored in ENTRY[3,N], SGNLERRE, DATAERRE, and TYPEERRE,
refer to H1, “SEBOL Details.”

<Toc> <Ind> <D7.5 Block Mode of Valve Pattern Monitor> D7-14
D7.5 Block Mode of Valve Pattern Monitor

There are two block modes (values in data item MODE) of the valve pattern monitor:
“O/S” and “AUT.”
To perform online maintenance for the valve pattern monitor using the online main-
tenance function, the block mode must be “O/S.”
■ Types of Block Modes £

The following table lists the types of block modes.
Table Block Modes of Valve Pattern Monitor £
Symbol Name
O/S Out of Service
AUT AUTomatic
D070501E.EPS
While the online maintenance function is used, the block mode will be “O/S.” The block
mode returns to the previous state when the online maintenance has been completed.
To perform the online maintenance, the block status BSTS of the valve pattern monitor
needs to be “STOP.” If the block status is “RUN” or “PAUS,” the valve pattern monitor
cannot apply the online maintenance function.

<Toc> <Ind> <D7.6 Block Status of Valve Pattern Monitor> D7-15
D7.6 Block Status of Valve Pattern Monitor

There are three valve pattern monitor block statuses (values of data item BSTS):
“STOP,” “RUN,” and “PAUS.”
By changing these block statuses the system can pause or restart valve pattern
monitor operation.
■ Types of Block Statuses £

The following table lists the types of block statuses.
• STOP (Stop inspection)
No unit uses the valve pattern monitor for inspection.
• RUN (Run inspection)
The valve patterns are being inspected.
• PAUS (Pause inspection)
The valve pattern inspection is paused.
■ Block Status Transition £

The following illustrates the transition of valve pattern monitor block statuses.
RUN
vpmstart
statement RUN
STOP PAUS
STOP
STOP PAUS
D070601E.EPS
Figure Block Status Transition £
To change the valve pattern monitor block status from “STOP” to “RUN,” execute the
vpmstart statement.
For transitions other than those above, use either of the following transition methods. One
method that can be used is to modify the value of data item BSTS through entry from the
operation and monitoring function. The other method that can be used is to modify the
value of data item BSTS using the assignment statement in the SEBOL statements for
operation.
SEE ALSO
For information about modifying the value of data item BSTS with the assignment statement, refer to
D7.11, “Example for Creating an Application Program.”

<Toc> <Ind> <D7.7 Signal Transmission and Alarm of Valve Pattern Monitor> D7-16
D7.7 Signal Transmission and Alarm of Valve Pattern

Monitor
If the valve pattern monitor detects a valve abnormality, it transmits a signal to the
unit. Information about processes distributed in the unit and on alarms has been
included in the signal parameters transmitted to the unit. The unit executes alarm
processes according to that information.
■ Signal Transmission £
The valve pattern monitor generates an alarm and transmits a signal (signal name:
VPMSIG) to the unit if a valve abnormality is detected. The signal the valve pattern monitor
transmits contains five parameters. The following table gives the contents of each param-
eter.
Table Parameter Contents in Signal VPMSIG £
Item Type Content
Signal name char*8 VPMSIG
1st parameter long Parameter specified in the vpmon or drive vpmon statement
2nd parameter char*16 Kind of abnormality (VPTN, DATA, TYPE)
3rd parameter char*16 Tag name
4th parameter char*16 Data item
5th parameter long Error code
D070701E.EPS
According to the number of parameters the valve pattern monitor transmits, specify “5” or
more as the maximum number of signal parameters for the SFC block (operation) that
receives the VPMSIG signal. If default value “2” is retained as the maximum number of
signal parameters, the SFC block may not receive the VPMSIG signal.
SEE ALSO
“Error code” in the table above is the same as the detailed SEBOL error code. For information about
detailed error codes, refer to H1, “SEBOL Details.”
The data item of the 4th parameter differs depending on the 2nd parameter value. The
relationship between those parameters is described below.
Table Relationship between the 2nd and 4th Parameters £
Kind of abnormality Definition Data item
Data inconsistency Registered data item
VPTN
Alarm status is not NR. ALARM
DATA No data can be acquired. Data item without data acquisition
TYPE Not integer type data Registered data item
D070702E.EPS

■ Kinds of Alarms £
If the valve pattern monitor detects an alarm, one of the alarm statuses which denote kinds
of alarms is stored in data item ALRM of the valve pattern monitor. The following table lists
the kinds of alarms that the valve pattern monitor detects.
• SGNL: Signal transmission failure
• VPTN: Valve pattern inconsistency
• TYPE: Incorrect data type
• NR: Normal status
Alarms other than “NR” are described below.
● SGNL (Signal Transmission Failure Alarm) £

If the valve pattern monitor cannot transmit the signal to the unit upon detection of a valve
abnormality, the SGNL alarm will occur. If the SGNL alarm occurs, the monitoring process
on that cycle is aborted.
If the valve pattern monitor succeeds in signal transmission on the next monitoring cycle,
recovery from the SGNL alarm is made. Recovery from the SGNL alarm is also made when
the value of data item BSTS of the valve pattern monitor changes from “PAUS” to “RUN,” or
from “STOP” to “RUN.”
If the SGNL alarm occurs, a system alarm message appears on the operation and monitor-
ing function panel. The display format is shown in the figure below. The error code of signal
transmission failure in the valve pattern monitor is classified as 20740.
Control Station name

Tag name
Classified error code
Detailed error code
0721 <Time> STN0031 VPM0301 S=0 (0) L=0 20740-AD35

SW101.PV
Data item name of

abnormal value
Tag name of
abnormal value
D070703E.EPS
Figure Display Example of System Alarm Message £
On the second line of the system alarm message, the tag name and data item name of the
abnormal value that caused the signal transmission failure are displayed.
If the valve pattern monitor fails to transmit the signal when no SGNL alarm is being gener-
ated, it outputs a system alarm message. While the SGNL alarm is being generated, the
valve pattern monitor will not output a system alarm message, even if it fails to transmit the
signal.

TIP
If the valve pattern monitor fails to transmit the signal upon detection of a valve abnormality and monitor-
ing on that cycle is aborted, signal transmission to the unit will not be performed again even if an abnor-
mality is detected in the same valve on the next monitoring cycle.
If the valve pattern monitor detects another valve abnormality and succeeds in transmitting the signal to
the unit, recovery from the SGNL alarm will be made.
● VPTN (Valve Pattern Inconsistency Alarm) £

If the acquired valve data is not identical to the reference value stored in ENTRY[3,N], the
VPTN alarm will occur assuming the valve as abnormal.
In addition, the valve pattern monitor with the alarm check function checks the function
block that controls the valve to be monitored for ALRM. Unless the checked ALRM is “NR,”
the VPTN alarm will occur.
If the value of data item BSTS of the valve pattern monitor is “RUN,” recovery from the
VPTN alarm will be made when all pieces of valve data are identical to the reference value
on the following monitoring cycles. Recovery from the VPTN alarm is also made when the
value of data item BSTS of the valve pattern monitor changes from “PAUS” to “RUN,” or
from “STOP” to “RUN.”
● DATA (Data Acquisition Failure Alarm) £

If the valve pattern monitor cannot acquire any valve data, the DATA alarm occurs and the
valve pattern monitor transmits a signal to the unit.
If the value of data item BSTS of the valve pattern monitor is “RUN,” recovery from the
DATA alarm will be made when all pieces of valve data are able to be acquired on the
following monitoring cycle. Recovery from the DATA alarm is also made when the value of
data item BSTS of the valve pattern monitor changes from “PAUS” to “RUN,” or from
“STOP” to “RUN.”
● TYPE (Incorrect Data Type Alarm) £

If the registered data is not integer-type data (real number type or character type), the
TYPE alarm occurs. This alarm also occurs if there is an error in the application program.
Modify the application program.
Recovery from the TYPE alarm is made when the value of data item BSTS of the valve
pattern monitor changes from “PAUS” to “RUN,” or from “STOP” to “RUN.”

■ Precautions for Detecting Alarms in the Valve Pattern Monitor £
The valve pattern monitor can detect an alarm if the value of data item BSTS of the valve
pattern monitor is “RUN.” However, data is checked only once on a monitoring cycle even
though the BSTS value is “RUN.” Therefore, the valve pattern monitor cannot detect a
temporary data abnormality, unless check timing (process timing) corresponds to the
abnormal time.
Monitoring cycle
VPM process timing VPM process timing
Valve status Normal Normal
Abnormal Time
D070704E.EPS
Figure Example: Abnormality that Cannot be Detected £
If a certain period of time has passed since the valve pattern monitor generated an alarm,
the system allows the alarm to be regenerated. Whether the alarm is regenerated, is
specified by the FCS Constants Builder. Only the active valve pattern monitor (the value of
data item BSTS is “PAUS” or “RUN”) can regenerate an alarm.
TIP
The valve pattern monitor transmits the generated alarm according to the settings of the alarm detection
specification (AF) and alarm suppression specification (AOFS).

■ Data Item Status for Valve Pattern Monitor Alarm £
• Even if the data status is changed from “abnormal” to “normal” when the value of data
item BSTS of the valve pattern monitor is “PAUS” or “STOP,” recovery from the valve
pattern monitor alarm will not be made (ALRM value will not change).
• If the value of data item BSTS of the valve pattern monitor changes from “PAUS” or
STOP” to “RUN,” recovery from all alarms will be made (ALRM value will be “NR”).
The following table lists the data item statuses for alarms.
Table Data Item Status for Alarms £
Valve pattern
Data item Name Builder default Initialize start (*1)
monitor startup
ALRM Alarm status NR Previous status NR
Alarm detection
AF
specification
Specification reset
Alarm suppression Previous status Previous status
AOFS status
specification
D070705E.EPS
*1: Includes the operation in which the block mode changes from “O/S” to “AUT.”
TIP
If a process alarm message is generated, the value of data item “OWNER” is appended to the message
and displayed in the operation and monitoring function.
SEE ALSO
For information about the alarm detection specification refer to C5.13, “Deactivate Alarm Detection” and
for the alarm suppression specification, refer to C5.14, “Alarm Inhibition (Alarm OFF) .”
■ Alarm Recovery If Multiple Pieces of Data Detect the Same Alarm £

If the same alarm is detected in multiple pieces of data, the system outputs the process
alarm message for the first piece of data. For example, assume that valve 1 detects the
valve pattern inconsistency and then valve 2 detects the valve pattern inconsistency. In this
case, only the process alarm message of valve 1 is output.
If the valve patterns of both valve 1 and valve 2 are identical, and if there is no other valve
with an inconsistent valve pattern, recovery from the VPTN alarm will be made.

■ Error Information Stored in Data Item upon Detection of Abnormality £
If any abnormality is detected, the valve pattern monitor stores the tag name, data item,
error code, etc., in one of the data items listed in the following table. These data items are
updated each time an abnormality is detected. If the same alarm is detected in multiple
pieces of data, the system outputs the process alarm message for the first piece of data.
The data items listed in the table below will give the most recent information about abnor-
malities.
Table Data Items Where Error Information Is Stored £
Detected abnormality Tag name and data item Error code
Signal transmission failure (*1) SGNLTAG, SGNLITEM SGNLERRE
Valve pattern inconsistency VPTNTAG, VPTNITEM VPTNERRE
Data acquisition failure DATATAG, DATAITEM DATAERRE
Incorrect data type TYPETAG, TYPEITEM TYPEERRE
D070706E.EPS
*1: The tag name and data item of the abnormal valve that causes signal transmission are stored in “SGNLTAG,
SGNLITEM.”
If the valve pattern monitor which has been paused (PAUS) is re-executed (RUN), recovery
from all generated alarms will be made.
The alarm recovery timing of the valve pattern monitor will synchronize to its process timing
on the basic cycle immediately after the block status changes from “PAUS” to “RUN.”
Even if the valve pattern monitor is re-executed, the values of SGNLTAG, SGNLITEM,
VPTNTAG, VPTNITEM, DATATAG, DATAITEM, TYPETAG, TYPEITEM, SGNLERRE,
VPTNERRE, DATAERRE, TYPEERRE, and ERRE will not change.

<Toc> <Ind> <D7.8 SEBOL Statements for Valve Pattern Monitor> D7-22
D7.8 SEBOL Statements for Valve Pattern Monitor

There are six SEBOL statements dedicated to the valve pattern monitor. With these
SEBOL statements, user applications which control the valve pattern monitor can be
created.
■ Application of SEBOL Statements £

▼ SEBOL Statement for Valve Pattern Monitor
The following figure illustrates valve pattern monitor operation through execution of SEBOL
statements (vpmstart, drive vpmon, drive vpmoff, vpmon, vpmoff, and vpmreset).
The SEBOL statements are executed by initiating the operation from the unit.
Unit
User Application
Monitoring operation
Signal transmission
Valve Pattern Monitor
Securing the valve
Operation pattern monitor
vpmstart SIO302.PV
Reference value (PV)
• Output
drive vpmon SIO302.PV Reference value (MV) SIO302.MV

Output
• The acquired data is compared
• with the reference values. If they
are not identical, the valve pattern
monitor transmits a signal.
Answer-back
check result
Data is acquired once
per monitoring cycle.
Function
block
PV
MV value MV
Remark
: Operation made with SEBOL
statements
: Data acquisition by the valve
pattern monitor
: Operation made with function
block
Valve
D070801E.EPS
Figure Example of Valve Pattern Monitor Operation by SEBOL Statements £

D7.8.1 vpmstart Statement

This statement secures the specified valve pattern monitor and makes it available
for use (monitoring of the valves is possible). The unit, from which the operation is
initiated and executes the vpmstart statement, is the “Owner” of the valve pattern
monitor.
If “STOP” is set as data item BSTS of the valve pattern monitor, the system can
terminate (reset) the valve pattern monitor.
■ vpmstart Statement Format £

The following shows the format of the vpmstart statement.
vpmstart <valve pattern monitor>

errorsub
D070802E.EPS
● <valve pattern monitor> £

Specifies the valve pattern monitor using a tag name, local generic name, generic name,
etc.
● <error variable> £
Specifies a local variable where an error code is stored. If no error occurs, 0 is stored in the
variable.
● <label> £
Specifies a branch destination where processing at error generation is performed.
● <error identifier> £
Specifies a constant or a local variable to identify the location where the error is generated
in the error processing unit.
■ Detailed vpmstart Statement £

Detailed information about the vpmstart statement, such as operation at statement execu-
tion, is given below.
• If the valve pattern monitor specified in the vpmstart statement has already been
initiated from the same unit, the statement will normally be terminated without error
generation.
• If the vpmstart statement is executed, the value of data item BSTS of the valve pattern
monitor changes from “STOP” to “RUN.”
• The tag name of the unit which has executed the vpmstart statement is stored in data
item OWNER of the valve pattern monitor.
• If the valve pattern monitor detects a valve abnormality, a signal is transmitted to the
unit that executed the vpmstart statement.
• If the character-type (CHR16) user definition data, VPMNAME, is defined in the unit,
the tag name of the valve pattern monitor is stored in VPMNAME upon execution of
the vpmstart statement. However, if the status (BSTS) of the unit is “END” or
“ABORTED,” it is unclear which character string is to be stored in VPMNAME.

If the vpmstart statement is executed, the following initialization processing will be ex-
ecuted.
• The valve pattern monitor is initialized so that no valve is registered.
• If the vpmstart statement is executed, the alarm status ALRM of the valve pattern
monitor is initialized (“NR” is stored). The initialization timing corresponds to the
monitoring process start time of the valve pattern monitor, which is on the basic cycle
immediately after the vpmstart statement is executed. This is not the time the vpmstart
statement was executed.
• Upon execution of the vpmstart statement, the valve pattern monitor data items,
SGNLTAG, SGNLITEM, VPTNTAG, VPTNITEM, DATATAG, DATAITEM, TYPETAG,
and TYPEITEM are initialized (a character string with a length of 0 is stored).
• The valve pattern monitor data items, SGNLERRE, VPTNERRE, DATAERRE,
TYPEERRE, and ERRE are initialized (0 is stored).
If the vpmstart statement is executed in the following cases, an error will result.
• If the valve pattern monitor specified in the vpmstart statement has already been
initiated from another unit, the statement results in an error.
• If the unit has already initiated another valve pattern monitor, an additional vpmstart
statement results in an error. The unit can initiate only one valve pattern monitor at the
same time.
• If the vpmstart statement is executed from the monitoring operation when the unit
status (BSTS) is “END” or “ABORTED,” an error will result.
■ Terminating the Valve Pattern Monitor £

If the unit is deactivated (its status is “END” or “ABORTED”), the value of data item BSTS of
the valve pattern monitor automatically changes from “RUN” to “STOP,” then the valve
pattern monitor is terminated (reset). Here, another unit can secure this valve pattern
monitor.
If the user definition data, VPMNAME, has been set in the unit, the value of VPMNAME will
be a null character string (string comprised of 0s).
To reset the valve pattern monitor during execution of the unit, script the following assign-
ment statement and set data item BSTS of the valve pattern monitor to “STOP.”
<valve pattern monitor>.BSTS=”STOP”
If a batch assignment statement is used as shown below, an error check will be performed
upon assignment of “STOP.”
unit genname VPM128 VPM03
integer ierr
......
[VPM03.BSTS=”STOP”]ierr
if(ierr<>0) then ! Process if an error is detected
end if
.....

D7.8.2 drive vpmon Statement

If the drive vpmon statement is executed, the drive statement operation is per-
formed, then the valves (function blocks to operate the valves) and the data (func-
tion block data) are registered in the valve pattern monitor, and the monitoring
process is started.
The drive statement operation is used to modify the output status of the valve oper-
ating function block (motor control block or switch instrument block) and to check
the valve for proper operation with the answer-back check of the function block.
■ drive vpmon Statement Format £

The following shows the format of the drive vpmon statement.
drive vpmon '['<function block array> = <output value and parameter array>']'
[<error array'['*']'>][; error <label>[,<error identifier>]]
errorsub
D070803E.EPS
● <function block array> £

Specifies the valves (function blocks) to be registered. A maximum of 16 valves can be
specified. No data item name is scripted in the drive vpmon statement, because the data
items to be registered are fixed.
The following table lists the contents that can be specified in this item.
Table Contents Specified in <function block array> of drive vpmon Statement £
Content Specification
Constant NO
Local variable simplified NO
Local variable array element NO
Local variable array whole NO
Tag name +data item simplified NO
Generic name simplified+data item array element NO
Generic name array element+data item array element NO
Generic name array whole+data item simplified NO
Tag name YES
Generic name simplified YES
Generic name array element YES
Generic name array whole YES
D070804E.EPS
YES: Can be specified.

NO: Cannot be specified.
• A tag name is declared with the block statement or global block statement.
• A generic name is declared with the unit genname statement.
• For the section where a generic name can be scripted, a global generic name (global
genname declaration), local generic name (genname declaration), global unit generic
name (global unit genname declaration), or dummy argument function block (argblock
declaration) can be used.
• Global variables (global integer declaration, etc.) of the SFC sequence cannot be
used.

● <output value and parameter array> £
Specifies an output value (0 or 2) and a parameter with a local variable or a constant.
Though a 3-position output function block (SIO-22 etc.,) may give an output value 1, the
drive vpmon can not give a command to do so. In the situation like this, drive statement
may be applied first to set the output value to 1, then use vpmon statement for monitoring.
Specify an integer between 0 and 19 as a parameter. If a value other than integers 0 to 19
is specified, an error will result upon execution of the statement. If an integer other than one
between 0 and 19 is specified, an error will result upon execution of the statement. This
parameter is the first signal parameter of a signal the valve pattern monitor transmits to the
unit.
The following table lists the contents that can be specified as the output value and param-
eter.
Table Contents Specified in <output value and parameter array> of the drive vpmon Statement
£
Content Output Parameter
Constant YES YES
Local variable simplified YES YES
Local variable array element YES YES
Local variable array whole YES NO
Tag name +data item simplified NO NO
Generic name simplified+data item array element NO NO
Generic name array element+data item simplified NO NO
Generic name array element+data item array element NO NO
Generic name array whole+data item simplified NO NO
Tag name NO NO
Generic name simplified NO NO
Generic name array element NO NO
Generic name array whole NO NO
D070805E.EPS

• Global variables (global integer declaration, etc.) of the SFC sequence can be used.
• If the whole array is specified for a reference value, all parameters become identical.
• The whole array cannot be specified for a parameter. Only one array element can be
specified for a parameter.
● <error array> £
Specifies an integer-type local variable array. An error code is stored in this array if an error
occurs. A zero (0) is stored in this array if no error occurs.
If only one piece of data is stored in this array, a simple variable or array element can be
specified in place of a local variable array.
● <label> £

in the processing unit.
TIP
The drive vpmon statement registers the valves and function block data in the valve pattern monitor after
the drive statement operation has been completed. Therefore, there is no specification corresponding to
the time specification of the vpmon statement.
■ Detailed drive vpmon Statement £

Detailed information about the drive vpmon statement, such as operation at statement
execution is given below.
• The system performs monitor processing by using an output value as the reference
value of the PV and MV values.
• If the drive statement operation of all the specified valves has been completed prop-
erly, the drive vpmon registers the valves and function block data in the valve pattern
monitor. If there is an abnormal valve in the drive statement operation, the drive
vpmon statement will be aborted without registering the function block data.
• If the specified valve has already been registered in the valve pattern monitor, regis-
tered content (valve and data) deletion, drive statement operation, and re-registration
will be performed in this order.
• If an error (including one in deleting the registered content) occurs before the output
status of the function block to be controlled by the drive statement operation is modi-
fied, registered content deletion and re-registration will not be performed. The registra-
tion statuses of the valve and function block data remain as they were before execu-
tion of the drive vpmon statement.
• If an error (e.g. an answer-back check abnormality) occurs after the output status of
the function block to be controlled by the drive statement operation is modified, only
registered content deletion is performed.
• If there is any array element out of the array suffix range, the drive vpmon statement
will not perform registered data deletion, drive statement operation, and re-registration
for all valves. Upon detection of an error out of the array suffix range, processing of
the drive vpmon statement on that line is aborted.
• A maximum of 16 valves and their function block data can be registered on one line
(each array element is counted as one for arrays).
• Even if the same valve is registered repeatedly, the valve pattern monitor registers the
valve once. The most recently registered output value and parameter are stored in
memory.
• If an SO-1 or SO-2 type switch instrument block is specified as a valve, the PV value
will not be registered even if both PV and MV values, or only the PV value is specified
as the station common item. This is because such a switch instrument does not have
the data item, PV. In such a case, the drive vpmon statement will not result in an error.
• If a valve that cannot be specified is included, none of the valves is registered.

If the drive vpmon statement is executed in the following cases, an error will result.
• The SI-1 and SI-2 type switch instrument blocks cannot be specified as valves in the
drive vpmon statement. If either type has been specified, an error will result at execu-
tion of the statement.
• If “1” is specified as an output value in the drive vpmon statement, an error will occur
at execution of the statement. Even if an error occurs, the drive statement operation is
performed, but registered content deletion and re-registration are not performed. For
the switch instrument or motor control instrument, the output status in the drive state-
ment operation becomes “1,” but answer-back check is not performed.
SEE ALSO
• For information about the drive statement and error codes, refer to H1, “SEBOL Details.”
• For information about the time specification of the vpmon statement, refer to D7.8.4, “vpmon Statement.”
■ Signal Transmission Processing Based on Parameter £

Parameters specified when valves are registered with the drive vpmon statement are used
to perform signal transmission processing according to the valve importance level in the
valve pattern monitor.
● Parameter between 10 and 19 £

Specify a parameter between 10 and 19 for valves of such important that emergency stop
processing must be made upon detection of an abnormality.
If an abnormal valve is detected, the valve pattern monitor transmits the valve information
to the unit as a signal. After one signal is transmitted to the unit, processing on that monitor-
ing cycle is terminated, if a parameter between 10 and 19 is specified. The statuses of
other valves are not checked. Information about the valve where an abnormality has been
detected is stored in data item ENTRY.
● Parameter between 0 and 9 £

Specify a parameter between 0 and 9 for valves other than those of such important that
emergency stop processing must be made upon detection of an abnormality. If a parameter
between 0 and 9 is specified, the valve pattern monitor checks valves one by one and
transmits the valve information to the unit as a signal. If abnormalities are detected in
multiple valves, the valve pattern monitor transmits multiple signals on one processing
timing.

The following figure shows the valve pattern monitor processing flowchart.
Start
Valves with
Absent
a parameter between
10 and 19
Present
Valves with Absent
a parameter between
Normal 0 and 9
Valve check
Present
Abnormal
Normal
Error code is set Valve check
in ENTRY.
Abnormal
Error code is set

Alarm is generated. in ENTRY.
Signal is transmitted Alarm is generated.

to the unit.
Failure Signal is transmitted

Signal transmission to the unit.
Success
Success
Signal transmission
Failure
SGNL alarm is
generated.
End
D070806E.EPS
Figure Flowchart of Priority Ordered Processing Based on Parameter £

D7.8.3 drive vpmoff Statement

The system deletes the valves (function blocks) and data (function block data) that
are registered in the valve pattern monitor by executing the drive vpmoff statement,
then performs the drive statement operation.
■ drive vpmoff Statement Format £

The following shows the format of drive vpmoff statement.
drive vpmoff '['<function block array> = <output value array>']'

[<error array'['*']'>][; error <label>[,<error identifier>]]
errorsub
D070807E.EPS
● <function block array> £

Specifies the valves (function blocks) to be deleted. A maximum of 16 valves can be speci-
fied. No data item name is scripted in the drive vpmoff statement because the data items of
the function block to be deleted are fixed.
Table Contents Specified in <function block array> of drive vpmoff Statement £
Constant NO
Tag name +data item simplified NO
Generic name simplified+data item array element NO
Generic name array element+data item simplified NO
Generic name array element+data item array element NO
Generic name array whole+data item simplified NO
Tag name YES
D070808E.EPS

used.

● <output value array> £
Specifies an output value (0, 1 or 2) with a local variable or a constant.
● <error array> £
Specifies an integer-type local variable array. An error code is stored in this array if an error
occurs. A zero (0) is stored in this array if no error occurs.
If only one piece of data is stored in this array, a simple variable or array element can be
specified in place of a local variable array.
● <label> £
Specifies a local variable or a constant to identify the location where the error is generated
■ Detailed drive vpmoff Statement £

Detailed information on the drive vpmoff statement, such as operation at statement execu-
• If the drive vpmoff statement is executed, the valves and function block data are
deleted from the valve pattern monitor before the drive statement operation is per-
formed.
• Even if an error occurs when the function block data is deleted with the drive vpmoff
statement, the drive statement operation is performed.
• If there is an array element out of the array suffix range, the drive vpmoff statement will
not perform the registered content (valve and data) deletion and the drive statement
operation. Upon detection of an error out of array suffix range, processing of the drive
vpmoff statement on that line is aborted.
• A maximum of 16 valves and their function block data can be deleted on one line
(each array element is counted as one for arrays).
• If an SO-1 or SO-2 type switch instrument block is specified as a valve, the PV value
will not be deleted even if both PV and MV values or only the PV value is specified.
Because such a switch instrument block does not have the data item, PV. In such a
case, the drive vpmoff statement will not result in an error.
• If a valve that cannot be specified is included, none of the valves is deleted. However,
the drive statement operation is performed for other valves.
• “1” can be specified as an output value in the drive vpmoff statement.
• The SI-1 and SI-2 type switch instrument blocks cannot be specified as valves in the
drive vpmoff statement. If either type has been specified, an error will result at execu-
tion of the statement.
SEE ALSO
For information about error codes, refer to H1, “SEBOL Details.”

■ Recovery from Alarm by drive vpmoff Statement £
If the valve where an abnormality occurs is deleted by executing the drive vpmoff state-
ment, the valve pattern monitor is recovered from an alarm.
The alarm recovery timing of the valve pattern monitor will synchronize to its processing
timing on the basic cycle immediately after the valve and function block data have been
deleted. It is not identical to the execution timing of the drive vpmoff statement.
The procedure for alarm recovery is described below using the example status in which the
DATA alarm (error code: D102) and VPTN alarm (error code: D001) occur.
ENTRY [1,1] VLV301 ENTRY [2,1] PV ENTRY [3,1] 1 0
ENTRY [1,2] VLV302 ENTRY [2,2] PV ENTRY [3,2] 1 0 D102
In the above status, if VLV302.PV in data item ENTRY is deleted by executing drive vpmoff
[VLV302], recovery from the DATA alarm will be made because the valve in data acquisition
failure is deleted. The status recovered from the DATA alarm is shown below.
ENTRY [1,2] ENTRY [2,2] ENTRY [3,2]
In the above status, if VLV305.PV is deleted by executing drive vpmoff [VLV305], the
following status is given. Since VLV303.PV is also inconsistent in valve pattern, recovery
from the VPTN will not be made.
In the above status, if VLV303.PV is also deleted by executing drive vpmoff [VLV303],
recovery from the VPTN will be made because no other valves with valve pattern inconsis-
tencies exist. The status recovered from the VPTN alarm is shown below.
The above operation is performed in the same way by executing the vpmoff statement in
place of the drive vpmoff statement.

D7.8.4 vpmon Statement

The system registers the valves (function blocks) and data (function block data) in the valve
pattern monitor by executing the vpmon statement, and then performs monitoring processing.
■ vpmon Statement Format £

The following shows the format of the vpmon statement.
vpmon '['<function block data array> == <reference value and parameter array>']'
[<error array>][; time <time>[, error <label>[,<error identifier>]] ]
errorsub
error <label> [,<error identifier>]
errorsub
D070809E.EPS
● <function block data array> £

Specifies the valves and integer-type function block data to be registered in the valve pattern
monitor. A maximum of 32 valves and pieces of function block data can be specified.
Table Contents Specified in <function block data array> of the vpmon Statement £
Constant NO
Tag name +data item simplified YES
Generic name simplified+data item array element YES
Generic name array element+data item simplified YES
Generic name array element+data item array element YES
Generic name array whole+data item simplified YES
Tag name NO
Generic name simplified NO
Generic name array element NO
Generic name array whole NO
D070810E.EPS

name (global unit genname declaration), and dummy argument function block
(argblock declaration) can be used.
• Global variables (global integer declaration, etc.) of the SFC sequence cannot be used.
TIP
The scripting method of <function block data array> is the same as that of a group assignment statement
or that of <variable array> in the compare statement. However, a local variable and a constant cannot be
specified in <function block data array>.

SEE ALSO
For information about a group assignment statement and the compare statement, refer to H1, “SEBOL
Details.”
● <reference value and parameter array> £

Specifies a reference value and a parameter with a local variable or a constant. A reference
value is treated as a long type. If a value other than the long type is specified, type conver-
sion is performed.
Specify an integer between 0 and 19 as a parameter. If a value other than integers 0 to 19
is specified, an error will result upon execution of the statement. This parameter is the first
signal parameter of a signal the valve pattern monitor transmits to the unit.
A reference value and a parameter are scripted and are separated using “,” and “:.” An
example of a script is shown below.
<reference value>:<parameter>[,<reference value>:<parameter>...]
The following table lists the contents that can be specified as the output value and param-
eter.
Table Contents Specified in <reference value and parameter array> of the vpmon Statement £
Content Output Parameter
Constant YES YES
Local variable simplified YES YES
Local variable array element YES YES
Local variable array whole YES NO
Tag name +data item simplified NO NO
Generic name simplified+data item array element NO NO
Generic name array element+data item simplified NO NO
Generic name array element+data item array element NO NO
Generic name array whole+data item simplified NO NO
Tag name NO NO
Generic name simplified NO NO
Generic name array element NO NO
Generic name array whole NO NO
D070811E.EPS

• Global variables (global integer declaration, etc.) of the SFC sequence can be used.
• If the whole array is specified for a reference value, all parameters become identical.
• The whole array cannot be specified for a parameter. Only one array element can be
specified for a parameter.
Specifies a local variable (simple variable or array element) where an error code is stored.
The whole array cannot be specified. A zero (0) is stored in this variable if no error occurs.

● <time> £
Specifies a wait time until the valve pattern monitor starts a valve check. Specify a value
between 0 and 127. The unit of a wait time is the basic cycle.
● <label> £
■ Detailed vpmon Statement £

Detailed information about the vpmon statement, such as operation at statement execu-
• A maximum of 32 valves (function blocks) and pieces of data (function block data) can
be registered on one line (arrays are tabulated for each array element).
• If the vpmon statement has been completed properly, the valves (function blocks) and
data (function block data) are registered in the valve pattern monitor. If an error occurs
in this statement execution, no valve and data is registered in the valve pattern moni-
tor.
• Even if the same valve is registered repeatedly, the valve pattern monitor registers the
valve once. The most recently registered reference value and parameter are stored in
memory.
• Specify integer-type function block data in <function block data array>. If data other
than integer-type data is specified, the valve pattern monitor generates the TYPE
alarm (data type error alarm), although an error will not occur at execution of the
vpmon statement.
An error will result in the following cases if the vpmon statement is executed.
• If a value outside of the long-type range is specified for the reference value, an over-
flow error will occur at execution of this statement.
• If a value other than one between 0 and 19 is specified for the parameter, an error will
occur at execution of this statement.
• If a value other than one between 0 and 127 is specified in <time>, an error will occur
at execution of this statement.

■ Script Example of the vpmon Statement: <function block data array> £
unit genname SIO-22 V1,V2
drive [V1,V2 == 2,1]

delay 1000
vpmon [V1.PV.MV,V2.PV.MV == 2:0,2:0,1:0,1:0]

! V1.PV,V1.MV,V2.PV,V2.MV are registered.
......
vpmoff [V1.PV]
! V1.PV registration is deleted.
......
■ Script Example: Parameter Specification If Reference Value Is Array £

unit genname SIO-22 VALV1[3],VALV2[3]
integer DAT1[3],DAT2[3]
vpmon [V1.PV,V2.PV == 2:0,1:10]

! V1.PV reference value is 2, parameter is 0.
! V2.PV reference value is 1, parameter is 10.
......
vpmon [VALVE1[*].PV == DAT1[*]:10]

! VALVE1[1].PV reference value is DAT1[1] value, parameter is 10.
......
vpmon [VALVE2[*].MV == DAT2[1]:0,DAT2[2]:0,

DAT2[2]:0,DAT3[3]:10]
! VALVE2[1].MV reference value is DAT2[1] value, parameter is 0.
......

■ Detailed time Specification in the vpmon Statement £
Specify the wait time until the valve pattern monitor starts monitoring in <time> of the
vpmon statement, assuming the next basic cycle after the vpmon statement is executed as
“0.” If the value of the function block data is identical to the reference value before the
specified <time> passes, the valve pattern monitor starts monitoring, irrespective of the
time specification.
Time
One basic cycle
Function block SEBOL Function block SEBOL Function block SEBOL Function block SEBOL
0 1 2
Executes the vpmon statement. If time1 has been specified, the valve
pattern monitor starts monitoring valves
from this basic cycle.
D070812E.EPS
Figure Timing between Time Specification Value and Monitoring £
Even if a wait time has been specified, execution of a SEBOL statement will not be de-
layed. If the function block data is registered in the valve pattern monitor, the SEBOL
statement on the next line is executed without delay, immediately when the vpmon state-
ment is executed. A wait time for monitoring is counted down when the value of data item
BSTS of the valve pattern monitor is “RUN” or “PAUS.”
If the monitoring cycle is set to 5, and the time specification to 4, the valve pattern monitor
starts valve data inspection after four basic cycles have passed, as shown below.
One basic cycle Valve pattern monitor operation timing: *1 to *3
*1 *2 *3
0 1 2 3 4 5 6 7 8 9
The vpmon statement is Four basic cycles have

executed (time 4). passed. Time
*1: Execution timing of vpmon statement

*2, *3: Operation timing of Valve Pattern Monitor
D070813E.EPS
Figure Operation under Setting of Monitoring Cycle: 5 and Time Specification: 4 £
The ALRM check function is not affected by the time specification. If data with time specifi-
cation is registered in the valve pattern monitor with the alarm check function (VPM64A to
VPM512A types), data inspection starts at the specified time, but the ALRM check starts
immediately after registration of the valves and data.
SEE ALSO
The data processing timing in the valve pattern monitor synchronizes to the function block processing
timing with a basic cycle specification. For details on process timing, refer to C7, “Process Timing.”

D7.8.5 vpmoff Statement

The valves (function blocks) and data (function block data) that have been registered in the
valve pattern monitor can be deleted by executing the vpmoff statement.
■ vpmoff Statement Format £

The following shows the format of the drive vpmoff statement.
vpmoff '['<function block data array>']'

[<error variable>][; error <label>[,<error identifier>]]
errorsub
D070814E.EPS
● <function block data array> £

Specifies the valves and integer-type function block data registered in the valve pattern
monitor. A maximum of 32 valves and pieces of function block data can be specified.
Table Contents Specified in <function block data array> of the vpmoff Statement £
Constant NO
Tag name +data item simplified YES
Generic name simplified+data item array element YES
Generic name array element+data item simplified YES
Generic name array element+data item array element YES
Generic name array whole+data item simplified YES
Tag name YES
D070815E.EPS

• Only the valve name is specified in the vpmoff statement. The data item name does
not need to be specified. If the data item name is not specified, all data items of the
valve are deleted.
used.

The scripting method of <function block data array> is the same as that of a group assign-
ment statement or that of <variable array> in the compare statement. However, a local
variable and a constant cannot be specified in <function block data array>.
SEE ALSO
For information about a group assignment statement and compare statement, refer to H1, “SEBOL
Details.”
Specifies a local variable (simple variable or array element) where an error code is stored.
The whole array cannot be specified. A zero (0) is stored in this variable if no error occurs.
● <label> £
Specifies a local variable or a constant to identify the location where the error is generated
■ Detailed vpmoff Statement £

Detailed information on the vpmoff statement, such as operation at statement execution, is
given below.
• A maximum of 32 valves (function blocks) and pieces of data (function block data) can
be registered on one line (arrays are tabulated for each array element).
• If the vpmoff statement has been completed properly, the valves (function blocks) and
data (function block data) are deleted from the valve pattern monitor. If an error occurs
in this statement execution, no valve and data is deleted.
• Even if an unregistered valve is specified in the vpmoff statement, no error will result
at execution of the statement.

■ Script Example of the vpmoff Statement: <function block data array> £
drive [V1,V2 == 2,1]

delay 1000
vpmon [V1.PV.MV,V2.PV.MV == 2:0,2:0,1:0,1:0]

! V1.PV,V1.MV,V2.PV,V2.MV are registered.
......
vpmoff [V1.PV]
! V1.PV registration is deleted.
......
vpmoff [V2]
! V2.PV,V2.MV registration is deleted.
......
■ Recovery from Alarm by the vpmoff Statement £

If the valve and function block data where an abnormality occurs are deleted by executing
the vpmoff statement, the valve pattern monitor is recovered from an alarm.
The alarm recovery timing of the valve pattern monitor will synchronize to its processing
timing on the basic cycle immediately after the valve and function block data have been
deleted. It is not identical to the execution timing of the vpmoff statement.
SEE ALSO
For information about the relationship between valve (function block) and data (function block data)
deletion and alarm recovery, refer to D7.8.3, “drive vpmoff Statement.”

D7.8.6 vpmreset Statement

If the vpmreset statement is executed, all the valves (function blocks) and data (function
block data) that have been registered in the valve pattern monitor are deleted.
■ vpmreset Statement Format £

The following shows the format of the vpmreset statement.
vpmreset [;<error variable>][; error <label>[,<error identifier>]]

errorsub
D070816E.EPS
Specifies a local variable where an error code is stored. A zero (0) is stored in this variable
if no error occurs.
● <label> £
Specifies an identifier to identify the location where the error is generated in the error
processing unit by a local variable or a constant.
■ Detailed vpmreset Statement £

Detailed information about the vpmreset statement such as operation at statement execu-
tion is given below.
• No valve is registered in the valve pattern monitor.
• The unit keeps the same the owner of the valve pattern monitor.
• Recovery from all alarms will be made while changing the value of valve pattern
monitor’s data item ALRM to “NR.” The alarm recovery timing of the valve pattern
monitor will synchronize to its processing timing on the basic cycle immediately after
the vpmreset statement has been executed. It is not identical to the execution timing
of the vpmreset statement.
The values of data items after execution of the vpmreset statement are as follows:
• The value of data item BSTS of the valve pattern monitor will not change.
• The valve pattern monitor data items, SGNLTAG, SGNLITEM, VPTNTAG,
VPTNITEM, DATATAG, DATAITEM, TYPETAG, TYPEITEM, SGNLERRE,
VPTNERRE, DATAERRE, TYPEERRE, ERRE and HMAX are not changed.
• The values of NUM1 and NUM2 of the valve pattern monitor become 0.
• If the unit is not the owner of the valve pattern monitor, the vpmreset statement will
result in an error.
SEE ALSO
For information about error codes, refer to H1, “SEBOL Details.”

<Toc> <Ind> <D7.9 Inspection of Data Acquired from FCS> D7-42
D7.9 Inspection of Data Acquired from FCS

There are two data inspection modes in the valve pattern monitor: one is the present
station data inspection and another is other stations data inspection.
■ Acquisition and Inspection of Present Station Data £

The valve pattern monitor acquires and inspects specified data about the valves (function
blocks) that have been registered once for each monitoring cycle. The FCS assigns mul-
tiple pieces of data to all valve pattern monitors in the station, so that each valve pattern
monitor inspects an even number of pieces of data for each basic cycle.
The monitoring cycle is a numeric value which denotes the number of basic cycles required
to perform one cycle of a monitoring process. The value of a monitoring cycle denotes that
the valve pattern monitor will perform data acquisition and inspection once within that
number of basic cycles.
If the monitoring cycle is 5, for example, one cycle of the monitoring process is performed
during 5w basic cycles (the FCS acquires data once for one basic cycle).
● Calculating the Number of Pieces of Data £

For each basic cycle, it monitors the present station data with the number of pieces
(rounded-up integer) which are obtained by dividing the total number of data by the moni-
toring cycle (number of basic cycles).
● Data Inspection by Valve Pattern Monitor £

The valve pattern monitor acquires a given amount of data every inspection execution
timing and inspects it.
For example, assume that one valve pattern monitor monitors 320 valves, the valve pattern
monitor acquires 64 pieces of data for each basic scan cycle (64 x 5 = 320) to check data, it
is shown as follows.
One monitoring cycle
VPM101 64 64 64 64 64 64
D070901E.EPS
Figure Present Station Data Acquisition and Inspection: One Active Valve Pattern Monitor £
Next, assume that three valve pattern monitors are activated and each of them inspects 64
valves. The three valve pattern monitors sequentially acquire and inspect data on each
basic cycle, as shown below.
One monitoring cycle
VPM301 64 0 0 64 0 0
VPM302 0 64 0 0 64 0
VPM303 0 0 64 0 0 64
D070902E.EPS
Figure Present Station Data Acquisition and Inspection: Three Active Valve Pattern Monitors £

■ Acquisition and Inspection of Other Station Data £
The system requires data acquisition of other stations at the beginning of basic cycles. The
valve pattern monitor inspects the data on the first process timing.
For example, assume that two valve pattern monitors reside in FCS1. The VPM201 moni-
tors the valves in FCS2 and the VPM301 monitors the valves in FCS3. In this case, the
FCS1 requires data acquisition of FCS2 and FCS3 at the beginning of basic cycles, as
shown below.
FCS2 FCS3
Completion Completion
Data acquisition Data acquisition
• • • VPM201 VPM301 • • • • • • VPM201 VPM301 • • •

Beginning of basic cycle
One basic cycle
D070903E.EPS
Figure Data Acquisition of Other Stations £
In the above condition the data acquisition of FCS2 has been completed prior to the pro-
cessing timing of VPM201 which has the same basic cycle, and therefore the VPM201
inspects the data of FCS2 on the first processing timing. Data acquisition of FCS3 has
been completed after the processing timing of VPM301, and therefore the VPM301 in-
spects the data of FCS3 on the processing timing of the next basic cycle.
● Data Acquisition of Other Stations £

To acquire data from other stations, the system totalizes the number of pieces of data from
other stations which all active valve pattern monitors supervise, at the beginning of basic
cycles. It acquires other station data with the number of pieces (rounded-up integer) which
are obtained by dividing the total number of pieces of data by the monitoring cycle (number
of basic cycles). The maximum number of pieces of data that the FCS can acquire at the
beginning of basic cycles must be 128.
If designing a application program for a valve pattern monitor, set the number of pieces of
data to be acquired for one basic cycle to a maximum of 128.
There may be a case where more than 128 (the maximum 256) pieces of data can be
acquired for one basic cycle. (If the number obtained by dividing the total number of pieces
of acquired data by the monitoring cycle is over 128, the acquisition requirement for the
excess number of pieces of data is made after the 128 pieces of data have been acquired.)
However, the number of pieces of data that can be acquired depends on the execution
amount of other applications, and therefore the excess pieces of data may or may not be
acquired.
The number of pieces of data from other stations that are actually inspected in the monitor-
ing cycle can be checked by the data item, NUM2CHK, of the valve pattern monitor.
Even if the number of pieces of data from other stations that can be acquired for one basic
cycle is less than 128, a “monitoring cycle + one basic cycle” period may be required to
detect any abnormality in other stations. This is because there is a time period between
data acquisition requirement for other stations and data acquisition completion.

■ Number of Pieces of Data Actually Acquired in Other Stations £
Other station data differs in the number of pieces of data actually acquired, depending on
the valve pattern monitor without the alarm check function and that with the alarm check
function.
Detailed information is given below.
● No Alarm Check Type (VPM64, VPM128, VPM256, VPM512) £

For the valve pattern monitor without alarm check function, the number of pieces of data
actually acquired is identical to that of other stations registered. Specifically, the number of
pieces of data acquired is identical to the NUM2 data item of the valve pattern monitor.
● Alarm Check Type (VPM64A, VPM128A, VPM256A, VPM512A) £

For the valve pattern monitor with alarm check function, the number of pieces of data
actually acquired is identical to the total of the number of pieces of data in the other stations
registered and the value of the ALRM data item . Specifically, the number of pieces of data
acquired is identical to the sum of SUM2 and the number of registered tag names.
One ALRM data item value is acquired every tag name.
Example 1: If vpmon [TAG1.PV,TAG1.MV] is specified, three pieces of data, TAG1.PV,
TAG1.MV, and TAG1.ALRM are acquired.
Example 2: If vpmon [TAG2.PV,TAG3.PV,TAG3.MV] is specified, five pieces of data,
TAG2.PV, TAG2.ALRM, TAG3.PV, TAG3.MV and TAG3.ALRM are acquired.

<Toc> <Ind> <D7.10 Builder Items for Creating Application Program> D7-45
D7.10 Builder Items for Creating Application

Program
For creating application programs, it is necessary to specify the builder definition
items.
■ Option Program Name £

The valve pattern monitor is an optional FCS function. Specify “VPMON” for “Option Pro-
gram Name.”
■ Valve Pattern Monitor Block £

The following table lists the builder definition items for the valve pattern monitor block,
which are defined by the control drawing builder.
Table Builder Definition Items for Valve Pattern Monitor Block £
Type of item Builder definition item Specification range Default
Tag name 16 or fewer alphanumeric characters -
Tag comment 24 one-byte characters or less -
Kind of tag mark 1 to 8 2
Common item Security level 1 to 8 4
Scan cycle Unspecified -
Processing timing Basic scan cycle fixed -
Message bypass for changing status With/without (*1) With
Alarm process Alarm processing level 1 to 16 2 (all middle)
D071001E.EPS
*1: If the message bypass is set to “without,” a message is output. However, for status modification, such as
“START@RUN” using the vpmstart statement and “RUN or PAUS@STOP,” due to the unit termination no message is
output, irrespective of the “without” setting.
The builder definition items for the valve pattern monitor block can be modified using the
online maintenance function.

<Toc> <Ind> <D7.11 Example for Creating Application Program> D7-46
D7.11 Example for Creating Application Program

Before using the valve pattern monitor create an application program of operation to
control it from valve registration to monitoring termination. In addition, to signal
execution reception processing any time, create an application program of monitor-
ing operation.
■ Application Programs of Operation and Monitoring Operation £

Create application programs for operating the valve patterns, as an example of application
program. The position of these application programs in the system is shown below.
Signal (VPMSIG)
Unit
Valve pattern
1 Routine processing
monitor
Monitoring
operation VPMSIG signal reception
1 Interruption
Routine processing
1 Valve registration
Operation
2 Charging
Processing after changing to PAUS : An application

program created
1 Pause by a user.
D071101E.EPS
Figure Position of Application Programs to be Created £
Operation and monitoring operation are described below.
● Operation £
This is a sequence which is started from the unit procedure and can execute SEBOL
statements specific to the valve pattern monitor. The unit procedure is a control group
configured by one or more operations.
● Monitoring operation £
This is a sequence which allows interrupt processing (signal reception processing) to be
executed immediately upon reception of the signal (VPMSIG). To create the application
program of this sequence, specify “independent” which allows signal reception at any time.
SEE ALSO
For information about unit procedure, refer to Part D6, “Unit Supervision.”

■ Interrupt Processing by Monitoring Operation £
The operation does not always receive the signal, as described later. If the signal has not
been received, signal transmission is assumed to fail and the valve pattern monitor gener-
ates the SGNL alarm.
Create an application program for monitoring operation which always resides as the signal
reception sequence so that the signal “VPMSIG” can always be received from the valve
pattern monitor. Also, specify “independent” for the valve pattern monitor there is no
pause.
In the following cases, the interrupt processing by operation may not be performed upon
signal reception and signal reception itself cannot be made by operation.
● Signal Reception Cannot be Performed since it is Paused. £

If “independent” is not specified for the operation, signal reception is paused when the unit
is paused. The operation can receive the signal while it is paused, but cannot execute the
interrupt processing on the timing of signal reception. Specifically, unless the block status
of the operation is changed from “PAUS” to “RUN,” interrupt processing cannot be per-
formed.
If “independent” has been specified for the monitoring operation, the monitoring operation
continues to be run while the unit is paused. It can execute interrupt processing immedi-
ately upon reception of the signal.
● Signal Reception Cannot be Performed due to Checking of the Transition

Condition. £
While the unit checks the transition condition, both operations before and after the transi-
tion condition are paused, and therefore the signal cannot be received.
5 Operation
Transition condition
6 Operation
D071102E.EPS
Figure Status at Checking of Transition Condition £
● Signal Reception Cannot be Performed since the Unit is in the SEMI

Mode. £
If the unit is in the SEMI mode and is paused at the beginning of step (unit’s status is
“SUSPEND”), the signal cannot be received since the operation in that step is not started.
7 Operation
Paused at the beginning of step 8
8 Operation
D071103E.EPS
Figure Pause due to SEMI Mode £

■ Program Example of Operation £
The following example shows a program in which the operation secures the valve pattern
monitor with the vpmstart statement, and then registers the valves to be monitored in the
valve pattern monitor with the vpmon statement.
.....
vpmstart VPM01
drive [V301,V302 == 1,1]
delay 1000
drive [V701,V702 == 0,0]
vpmon [V301.PV,V302.PV == 1:10,1:10]
vpmon [V701.PV,V702.PV == 0:0,0:0]
......
■ Program Example of Monitoring Operation £

The following example shows an application program in which the monitoring operation
receives the VPMSIG signal.
In this program, if the signal parameter is 10 and if the present unit is being run, the present
unit is paused at reception of the VPMSIG signal. Otherwise, the operator guide massage
is output.
char*16 tango,item
if (lreadpara(1) == 10 AND %%.BSTS == “RUNNING”) then

VPM03.BSTS = “PAUS” ! Pauses the valve pattern monitor.
%%.BSTS = “PAUS” ! Pauses the present unit.
return
***Even if the present unit is paused, the monitoring operation with
***“independent” specified continues the interrupt signal processing.
***Then, return needs to be entered.
end if
tango = creadpara(3) ! Tag name

item = creadpara(4) ! Data item
switch (creadpara(2)) ! Type of abnormality

“VPTN”:
opeguide”%s.%s valve pattern is inconsistent (error code: $%04X)”,\
tango,item,lreadpara(5)
“DATA”
opeguide “%s.%s data cannot be read (error code: $%04X)”,\
“TYPE”
opeguide”%s.%s is not integer-type data (error code: $%04X)”,\
end switch
return
■ Program Example of “Pause” for PAUS Modification Post-Processing
£
Create an application program in which the operation executes “PAUS Modification Post-
processing” if the value of the unit data item BSTS is modified to “PAUS.”
In the “Pause” program, the value of the valve pattern monitor’s data item BSTS is modified
from “RUN” to “PAUS,” using an assignment statement. If the value of data item BSTS
changes to “PAUS,” the valve pattern monitor pauses data acquisition and inspection. At
this time, valve registration is retained.
The following shows an example of the “Pause” program.
<valve pattern monitor>.BSTS = “PAUS”
If the group assignment statement is used in place of the assignment statement, assign-
ment with error check can be performed.
unit ierr
......
[VPM03.BSTS = “PAUS”] ierr
if (ierr <> 0) then ! Processing if an error is detected.
end if
......
To restart monitoring, modify the value of the valve pattern monitor’s data item BSTS from
“PAUS” to “RUN.”
<valve pattern monitor>.BSTS = “RUN”
● Relationship between Pause and Alarm Status £

If the paused valve pattern monitor is restarted, recovery from all alarms in the valve
pattern monitor will be made and the value of ALRM will be “NR.” The alarm recovery
timing of the valve pattern monitor will synchronize to its processing timing on the basic
cycle immediately after the value of data item BSTS is changed from “PAUS” to “RUN.”
• To re-execute monitoring, modify the value of the valve pattern monitor’s data item
BSTS from “PAUS” to “RUN.”
• The values of SGNLTAG, SGNLITEM, VPTNTAG, VPTNITEM, DATATAG,
DATAITEM, TYPETAG, and TYPEITEM in the valve pattern monitor are not changed.
• The values of SGNLERRE, VPTNERRE, DATAERRE, TYPEERRE, and ERRE in the
valve pattern monitor are not changed.

<Toc> <Ind> <D7.12 Specifying Processing Timing> D7-50
D7.12 Specifying Processing Timing

The valve pattern monitor processing timing can be specified by placing the names
of control drawings to which the valve pattern monitor belongs in alphabetical order.
■ Specifying the Processing Timing £

The processing timing of the valve pattern monitor corresponds to that of a function block
for which the normal basic cycle is specified. If the processing timing of the valve pattern
monitor within the basic cycle needs to be delayed beyond that of the function block to be
monitored, observe the following procedure.
• Bring the valve pattern monitor into the specific control drawing.
• The control drawings are executed in alphabetical order. Specify by name the control
drawing to which the valve pattern monitor belongs so that it appears last in the
alphabetical order. For example, apply Z to the beginning of the name.
SEE ALSO
For information about the function block processing timing, refer to C7, “Process Timing.”
The following example shows the execution order of ten control drawings.
One basic cycle
DRW0001 DRW0002 ...... DRW0009 ZTAIL SEBOL

The control drawing, “ZTAIL” is executed in last.
Time
D071201E.EPS
Figure Execution Order of Control Drawings £
In this example, there in only one control area. There are ten control drawings named
“DRW0001” to “DRW0009,” and “ZTAIL.” The control drawings are executed in alphabeti-
cal order: “DRW0001,” “DRW0002,” ... , “DRW0009,” and “ZTAIL.”
The user should collect the valve pattern monitor into the control drawing “ZTAIL.” Locate
the function blocks which control valves in the control drawings “DRW001” to “DRW009,”
then the processing timing of the valve pattern monitor comes after the valve controlling
function blocks.

<Toc> <Ind> <D7.13 Using Simulation Programs> D7-51
D7.13 Using Simulation Programs

Simulation function executes the simulated operation to test a valve without collecting the
valve’s data. This function may only be applied for testing valve pattern monitor.
Setting or cancelling of the simulation mode can be transferred by the setpoint value of the
data item SIMM of the simulation switch.
■ Using the Simulation Programs £

The valve pattern monitor is provided with a simulation function. This simulation function
may only be applied for testing the valve pattern monitors. To use this simulation function,
set the value of data item SIMM so the valve pattern monitor is put in the simulation mode.
● Setting the Simulation Mode £

To put the valve pattern monitor in the simulation mode on tuning window, set the data item
SIMM of the simulation switch to 1.
● Canceling the Simulation Mode £

To cancel the simulation mode of the valve pattern monitor on tuning window, set the data
item SIMM of the simulation switch to 0.
If the valve pattern monitor is put in the simulation mode during execution, it stops data
acquisition and inspection (valve monitoring).
■ Alarm Status in the Simulation Mode £

Even if you put the valve pattern monitor in the simulation mode, the alarm status will not
change.
However, if the value of the valve pattern monitor’s data item BSTS is changed from
“PAUS” to “RUN,” recovery from all generated alarms will be made and the value of data
item ALRM will change to “NR,” even if the valve pattern monitor is in the simulation mode.

Blank Page
<Toc> <Ind> <D8. Offsite Block> D8-1
D8. Offsite Block

The offsite block is a function block used for batch blending and shipment control
performed offsite at oil refineries and other plant facilities.
Offsite blocks include the Batch Set Control Block (FSBSET) and the Blending
Master Control Block (BLEND).
This chapter explains the detail of functions available with each offsite block.
■ Offsite Block £
The offsite function block performs blending control and shipment control offsite by control-
ling flow rate and batch quantity.
This block is used to implement batch shipment control and blending shipment control of
products offsite in combination with motor control blocks (MC-2, MC-3) and switch units
(SIOs).
Flow rate
totalizer value
Blending master
BLEND
control block
Flow rate setpoint
Switch Motor control Batch set

instrument block block control block
SIO MC-2 FSBSET
TANK
Switch Motor control Batch set

instrument block block control block
SIO MC-2 FSBSET
Product
storage tank
TANK
Valve Pump Flowmeter Control valve

D080001E.EPS
Figure Example of Application with Offsite Blocks £

■ Relationship between Offsite Blocks and JOB Controllers £
Blending, shipment and other work (jobs) performed offsite are controlled with offsite
blocks, motor control blocks (MC-2, MC-3) and switch units (SIOs) in the FCS. These
function blocks operate via commands and operation from JOB controllers being set under
the supervisory computer. They can also be operated and monitored from an HIS that
serves as a backup supervisory computer.
Supervisory computer
JOB JOB
controller controller
FCS
Offsite Motor control Switch Offsite Motor control Switch

block block instrument block block instrument
block block
D080002E.EPS
Figure Relationship between Offsite Blocks and JOB Controllers £

■ Overview of Offsite Block Control
The offsite block is used mainly for batch loader control, tank blending control and direct
blending shipment control.
● Batch Loader Control

Batch loader control is implemented with the FSBSET control block.
The FSBSET is operated by commands from an operator or supervisory computer, and
controls flow rate and batch quantity according to the flow rate signals received from
positive displacement flowmeters.
The figure below shows an example of FSBSET application for batch loader control:
Batch quantity and

flow rate setting
Command from operator or
supervisory computer
FSBSET
Product
tank
Positive Control Loading arm
Pump
displacement valve (at port)
flowmeter
D080003E.EPS
Figure Example of Batch Loader Control

● Tank Blending Control £
FSBSET and BLEND control blocks are used for tank blending.
The FSBSET receives commands from the BLEND, and controls flow rate according to the
flow rate signals from positive displacement flowmeters.
The BLEND receives the ratio of each component from the supervisory computer, and
multiplies it by its own flow rate setpoint (SV) at the tank entry point. It then sets the result
as an SV for the FSBSET of the corresponding component. The BLEND also accumulates
the instantaneous flows (PVs) obtained from each of the component FSBSET blocks, and
performs batch control based on the result.
The figure below shows an example of tank blending application using FSBSET and
BLEND control blocks:
Component configuration
Component ratios
PV collection Batch quantity

BLEND and flow rate
Setting of setpoint or setting
operation command
FSBSET
FSBSET
FSBSET
Blend header
Product tank
Tank of Positive Control

Pump
semi- displacement valve
finished flowmeter
product
D080004E.EPS
Figure Example of Tank Blending Control £

● Direct Blending Shipment Control £
For direct blending shipment control performed offsite, batch quantity is controlled by the
FSBSET blocks or BLENDs located at the port.
The FSBSET control block at the port receives commands from an operator or supervisory
computer, and controls flow rate and batch quantity according to the flow rate signals from
positive displacement flowmeters at the port.
The BLEND control block at the port receives the port blending ratio for each component
from the supervisory computer, and multiplies it by its own port flow rate setpoint (SV). It
then sets the result as a port blending SV for the corresponding component FSBSET. The
BLEND also accumulates the instantaneous flows (PVs) obtained from each of the compo-
nent FSBSET blocks used for port blending, and performs batch control based on the
result.
The BLEND used for blend header shown in Figure, “Example of Direct Blending Shipment
Control” totalizes the flow rate setpoints (SVs) of the FSBSET blocks or BLENDs located
downstream of the blend header at the port, and sets the sum as its own SV. (The BLEND
can also be set by the builder to obtain a totalized instantaneous flow (PV) for the FSBSET
blocks or BLENDs at the port and set the sum as its own SV.) It then multiplies the SV by
the ratio for each component specified by the supervisory computer, and sets the result as
an SV for the corresponding component FSBSET.

Component configuration
Component ratios
Port configuration
PV collection
BLEND
Setting of setpoint or
operation command
FSBSET
FSBSET
Batch quantity
and flow rate
setting
FSBSET
FSBSET
Blend header
BLEND
Tank of Positive Control

Pump
semi- displacement valve
finished flowmeter
FSBSET
product
FSBSET
D080005E.EPS
Figure Example of Direct Blending Shipment Control £

<Toc> <Ind> <D8.1 Batch Set Control Block (FSBSET)> D8-7
D8.1 Batch Set Control Block (FSBSET)

The FSBSET control block provides functions necessary for batch loader control,
blending control, and X% preset MV control.
■ Batch Loader Functions - FSBSET £

The FSBSET provides all the functions required for controlling flow rate and batch quantity
at a port or the like.
For flow rate control, the block can calculate corrections such as ASTM on pulse flow-rate
signals from positive displacement flowmeters or turbine flowmeters; it also performs PI
control calculations to maintain the flow as specified by the setpoint.
Batch program control provides gradual flow ramp-up and ramp-down functions. The block
also provides automatic early-point detection and emergency-stop processing functions
necessary for batch control.
■ Batch Blending Control Functions - FSBSET £

The FSBSET is used for in-line blending to control flow rate for each component. When
performing PI flow rate blending control, according to a setpoint demand signal and com-
mands from the Blend master controller (BLEND) block, one batch set control block is used
for each component whose flow rate is to be controlled.
In this case, the FSBSET can calculate corrections, such as ASTM, on the pulse flow-rate
signals from positive displacement flowmeters or turbine flowmeters; it also performs PI
control calculations to keep accumulated deviations at or near zero (termed PI blending
calculations).
The FSBSET can also be set on the builder to perform instantaneous deviation control
instead of accumulated deviation control.
■ X% Preset MV Control Functions - FSBSET £

The FSBSET can be used not only to perform flow or batch control, but it can also be used
to provide a fixed output. On receiving a start or restart command, it outputs the fixed
output. The fixed output (MV) may be entered in the tuning parameter NCVV. If an emer-
gency stop or abort command is received, the block clamps the output (MV) at zero (valve
closed).

D8.1.1 Operation for Batch Loader Control - FSBSET

During batch loader control, the FSBSET performs CV-kick, release of initial flow
rate control, early-point detection processing and pre-batch processing.
The operation of the FSBSET is indicated by a sequence of control steps.
■ Operation for Batch Loader Control - FSBSET £

The figure below shows the flow of FSBSET operation during batch loader control:
Flow rate setpoint (SV)

t2 t2
SVH
(Final flow rate
setpoint)
t1
SVL
(Initial
flow rate
setpoint)
SVPR
(Pre-batch
flow rate t3 t4
setpoint) t0
CVK
(extent of
CV-kick) t
Initial flow rate Re-
Start control start
SET SET EMST SET P.B. NON-
Control status NON- Steady EMST Steady Early Wait End
Ctrl UP UP end UP Ctrl Ctrl
Control step
(zone) 0 (10) 1 2 1 3 8 9 (11) 1 3 4 5 6 7 0
Block mode MAN AUT or CAS MAN
t0: SET-UP waiting time

t1: Waiting time after completion of SET-UP to initial flow rate
t2: Waiting time after completion of SET-UP to final flow rate
t3: Batch end waiting time
t4: Waiting time for completion of end processing
D080101E.EPS
Figure Operation Overview of Batch Loader Control £
The basic operation of the FSBSET during batch loader control is explained below. The
explanations are based on the above figure.
• At the start of batch loader control, the block mode of the FSBSET is changed to AUT
or CAS via a JOB controller or by an operator. A start command is then sent to the
FSBSET.
• When the FSBSET Block receives the start command with CV-kick (CMND=1), the
control step proceeds to ZONE10, initializing an alarm, integral and others of the
FSBSET block and opening a control valve (CV) by a preset degree. This is called CV-
kick. After CV-kick, the control step proceeds to ZONE1.

• When the SET-UP waiting time (t0) elapses following the transition to ZONE 1, SET-
UP is started. In SET-UP, the current flow rate setpoint (SV) is ramped at a preset rate
until it reaches the initial flow rate setpoint (SVL) or final flow rate setpoint (SVH), while
PI control is carried out based on the SV.
• When the waiting time for the end of SET-UP to initial flow rate (T1) elapses after the
current flow rate setpoint (SV) reached the initial flow rate setpoint (SVL), the control
step proceeds to ZONE 2.
• When the totalized flow (SUM) reaches the initial (totalized) flow setpoint (ILST), or
when an operator directs the release, the control step returns to ZONE 1, and SET-UP
is performed to ramp the current flow rate setpoint (SV) at a preset rate until it reaches
the final flow rate setpoint (SVH).
• When the waiting time for the end of SET-UP to final flow rate (T2) elapses after the
current flow rate setpoint (SV) reached the final flow rate setpoint (SVH), the control
• When the totalized flow (SUM) reaches the batch setpoint (BSET) less the pre-batch
quantity and predicted leakage value (VL), the control step proceeds to ZONE 4. The
block status changes to measure tracking, in which the current flow rate setpoint (SV)
is caused to follow the momentary flow (PV), and the control valve is throttled gradu-
ally at a preset rate.
• When the flow rate setpoint (SV) drops to the flow rate setpoint for pre-batch (SVPR)
during measure tracking, the control step proceeds to ZONE 5. At this point, the
measure tracking status is released and the control mode returns to normal PI control.
• When the totalized flow (SUM) reaches the batch setpoint (BSET) less the predicted
leakage value (VL), the control step proceeds to ZONE 6 and the control valve is shut
tightly. Calculation for the totalized flow (SUM) will continue after the valve is tightly
shut.
• When the waiting time for batch end (t3) elapses following the transition to ZONE 6,
the totalized flow (SUM) at the end of t3 is stored as the previous totalized flow. Batch-
end processing is performed, and the control step proceeds to ZONE 7.
• When the waiting time for completion of end processing (t4) elapses following the
transition to ZONE 7, the block mode changes to MAN and the control step returns to
ZONE 0. This completes a batch loader control cycle.
• If an emergency stop command (CMND=4) is issued or a critical alarm is detected
during the batch cycle, the control step proceeds to ZONE 8 and the control valve
shuts off in steps. When the manipulated output value (MV) drops to 0 during the step
shut-off process, the control step proceeds to ZONE 9. This changes the block status
to EMST END (emergency stop end).
• If a command for restart with CV-kick (CMND=2) is received in the EMST END state,
the control step proceeds to ZONE 11 and the CV opens by a preset amount. Then,
the control step returns to ZONE 1 and batch loader control is restarted.

The following operations are not shown in the above figure:
• When a command for start without CV-kick (CMND=11) is received, the control step
proceeds to ZONE 12. Initialization processing for the FSBSET is performed and the
control step returns to ZONE 1.
• When a command for restart without CV-kick (CMND=12) is received, the control step
proceeds to ZONE 13 then returns to ZONE 1 without implementing CV-kick.
• During SET-UP in ZONE 1, if initial flow rate control is not specified or when the
totalized flow (SUM) reaches or exceeds the initial totalized flow setpoint, SET-UP is
performed based on the final flow rate setpoint (SV).
• If an abort command (CMND=3) is received in the EMST END state, the control step
returns to ZONE 6 and batch end processing is performed, starting from the operation
in ZONE 6 explained above.

D8.1.2 Operation for Batch Blending Control - FSBSET

During batch blending control, the FSBSET performs CV-kick and PI blending control.
The operation of the FSBSET is indicated by a sequence of control steps.
■ Operation for Batch Blending Control £

The figure below shows the flow of FSBSET operation during batch blending control.
Flow rate
setpoint
(SV)
CVK
NON- CV PI blending CV PI blending Waiting NON-

Control status EMST End
Ctrl Kick control Kick control for END Ctrl
Control step
0 20 22 24 21 22 23 26 0
(zone)
Block mode MAN CAS MAN
D080102E.EPS
Figure Operation Overview of Batch Blending Control £
The basic operation of the FSBSET during batch blending control is explained below. The
• When a component start command (CMND=21) is received from a supervisory loop
(normally a BLEND block), the control step proceeds to ZONE 20 and the control
valve opens by a preset amount (CV-kick). Initialization processing for the FSBSET,
such as alarm, totalization and accumulated deviation processing, will also be per-
formed.
• When the initialization processing is completed, the control step proceeds to ZONE 22
and PI blending calculation is performed according to the flow rate setpoint (SV)
specified by the supervisory loop.
• When the status of the supervisory loop changes to batch end, a command to wait for
component END (CMND=26) is sent from the supervisory loop. When this command
is received, the control step proceeds to ZONE 23 and the control valve shuts tightly.
• When a component release command (CMND=23) is received from the supervisory
loop, the control step proceeds to ZONE 26 and the control valve shuts tightly. Then,
the block mode changes to MAN and the control step returns to ZONE 0. This com-
pletes a batch blending control cycle.
• When subjected to an emergency stop, the supervisory loop sends a component
EMST command (CMND=24). When this command is received, the control step
proceeds to ZONE 24 and the control valve shuts tightly.

• If a component cut-off command (CMND=25) is received from the supervisory loop
while control is in ZONE 22, the control step proceeds to ZONE 25 and the control
valve is throttled at a preset rate. When the manipulated output value (MV) drops to 0
or below, the control step proceeds to ZONE 26 and the control valve shuts tightly.
Then, the block mode changes to MAN and the control step returns to ZONE 0. This
completes a batch blending control cycle.
The figure below shows the flow of component release (cut-off):
Flow rate
setpoint
(SV)
t
Component cut-off
PI blending
Control status control End NON-Ctrl
Control step
22 25 26 0
(zone)
Block mode CAS MAN
D080103E.EPS
Figure Component Cut-off (Batch Blending Control) £

D8.1.3 Operation for X% Preset MV Control - FSBSET

During X% preset MV control, the FSBSET controls the opening of control valve
(fixed at X% or fully closed) according to the command received from outside the
block.
■ Operation for X% Preset MV Control - FSBSET £

The figure below shows the operation of the FSBSET during X% preset MV control:
CMND 41 44 42 43
Operation Start EMST Restart End
Block mode AUT or CAS Start mode AUT or CAS Start mode
MV
(%)
0 t
NON- Re- NON-

Control status Start Steady EMST Steady End
Ctrl Start Ctrl
Control step
(zone) 0 40 42 44 41 42 43 0
D080104E.EPS
Figure Operation Overview of X% Preset MV Control £

The basic operation of the FSBSET during X% preset MV control is explained below. The
• When performing X% preset MV control, the block mode of the FSBSET is set to AUT
or CAS via a JOB controller or by an operator. Then, a command to start X% preset
MV control is issued.
• When the FSBSET receives a command to start X% preset MV control (CMND=41),
the control step proceeds to ZONE 40 and the manipulated output value (MV)
changes from zero to the value set by the NCCV data item. Then, the control step
proceeds to ZONE 42.
• When the FSBSET receives a command to stop X% preset MV control in an emer-
gency (CMND=44), the control step proceeds to ZONE 44 and the manipulated output
value (MV) drops to zero.
• When the FSBSET receives a command to restart X% preset MV control (CMND=42),
the control step proceeds to ZONE 41 and the manipulated output value (MV)
changes from 0 to the value set by the NCCV data item. Then, the control step pro-
ceeds to ZONE 42.
• When the FSBSET receives a command to end X% preset MV control (CMND=43),
the control step proceeds to ZONE 43 and the manipulated output value (MV) drops
to zero. Then, the block mode changes to MAN and the control step returns to ZONE
0. This completes an X% preset MV control cycle.

D8.1.4 Configuration of Batch Set Control Block (FSBSET)

This section explains the function block diagram of the FSBSET control block and
connection destinations for the I/O connection terminals.
■ Function Block Diagram of the Batch Set Control Block (FSBSET) £

▼ Connection
Compensation before Temperature Compensation after Control calculations

temperature compensation compensation temperature compensation Accumulated-deviation PI control algorithm
Instantaneous-deviation PI control algorithm
CCX DENS VCF CCY

SIMM
Simulation
PV value
Output
conversion
PV process MV
digital -ing
Input filtering
processing Actual pulse Simulation
IN Pulse quantity
conversion DSM
SV
Analog
Pulse train input OUT
SUM1 SUM B-MODE

Batch control C-MODE
Analog input function
V-MODE
SUM2
BSET ZONE COMD
TMI
BLEND
D080105E.EPS
Figure Function Block Diagram of Batch Set Control Block (FSBSET) £
SEE ALSO
• For input processing, see D8.1.5, “Input Processing of Batch Set Control Block (FSBSET).”
• For output processing, see D8.1.6, “Output Processing of Batch Set Control Block (FSBSET).”

■ I/O terminals of the Batch Set Control Block (FSBSET) £
The input and output terminals of FSBSET block and the connection methods of the termi-
nals are shown in the following table.
Table Types of Connection and Connection Destinations of I/O Terminals for Batch Set Control
Block (FSBSET) £
Type of Connection Connection Destination
Terminal Name Data Data Terminal Process Software Function
IN Measuring input N/A N/A N/A
OUT Control output N/A N/A
Compensating
TMI N/A Cond. N/A
temperature input
D080106E.EPS
: available
N/A: not available
Cond.:available only from the switch block

D8.1.5 Input Processing of Batch Set Control Block (FSBSET)

The input processing items of the FSBSET include input reading, pulse weight
normalization, correction before temperature compensation, temperature compen-
sation, correction after temperature compensation, instantaneous flow computation,
totalization and simulation.

■ Input Processing of the Batch Set Control Block (FSBSET) £
Table Table of Input Processing Items for Batch Set Control Block (FSBSET) £
Input Processing
No. Processing Item Provided Remarks
1 Pulse train input reading
2
3 Analog input reading
4 Pulse normalization (not normalized)
5 Puss normalization (normalized) According to pulse weight normalization factor
Correction before temperature
6
compensation -0 (no correction)
Correction before temperature Flow rate correction before temperature
7
compensation -1 (with correction) compensation
8
9
Correction after temperature
10
compensation -0 (no correction)
Correction after temperature Flow rate correction after temperature
11
compensation -1 (with correction) compensation
12
13
Temperature compensation -0
14
(no compensation)
15
(new ASTM) for crude oil
16
(new ASTM) for fuel oil
17
(new ASTM) for lubrication oil
18 Temperature compensation -4 (old ASTM)
19 Temperature compensation -5 (VCF entry)
20
21
22
23
24
25
26
27
28
29
30 Totalized value (uncorrected, non-reset) SUM1

31 Totalized value (corrected, reset) SUM
32 Totalized value (corrected, non-reset) SUM2
33 Input filter
Simulation
34
(specified for each flow controller block)
D080107E.EPS
: available

■ Input Reading - FSBSET £
▼ Input Connection Specification, Totalizer Shutdown during Non-Control
● Normal Input Reading £

When the “Input Signal Type” on the Function Block Detail Builder is “Pulse,” the FSBSET
block reads pulse train inputs from process I/O.
The volumetric flow pulse (QR1) between T seconds of control cycle is calculated from
the difference in the number of pulses to be read this time and previously.
When the “Input Signal Type” is “Analog,” 0 to 100 % of input signals is converted to the PV
scale low limit (SL) to PV scale high limit (SH).
The “Input Signal Type” parameter of the builder is set as follows:
• Input Signal Type: Select “Pulse” or “Analog.”
The default is “Pulse.”
Whether or not pulse train input will be added to non-reset totalized values (SUM1, SUM2)
and batch-type totalized value (SUM) while the FSBSET is in the non-control status (control
step: ZONE 0) can also be specified in the Function Block Detail Builder.
The “Totalizer Shutdown during Non-control” parameter of the builder is set as follows:
• Totalizer Shutdown during Non-control: Select “Yes” or “No.”
The figure below shows the processing flow of input data:
Pulse weight Correction before Correction after

Temperature
normalizing temperature temperature
QR1 QR2 QR3 compensation QR4 QR5
processing compensation compensation
D080108E.EPS
Figure Processing Flow of Input Data £
● Input Reading During Simulation £

When simulation is specified for the FSBSET, the flow rate for the closed-loop test is
deduced from the opening (MV) of the current control valve (CV).
Maximum
flow rate
(KI/h)
Instantaneous
flow rate (Linear)
0% 100 %
Control valve opening (MV)
D080109E.EPS
Figure Calculation of Flow Rate During Simulation

■ Pulse Weight Normalization - FSBSET £
▼ Pulse Weight Normalization Coefficient
Pulse weight correction is performed on the flow before temperature compensation (QR1).
Input pulses can be corrected using the following expression to calculate flow reading:
QR2=QR1 • pulse weight normalization factor
Pulse weight normalization factor is set in the builder (L/P, i.e., liters per pulse, or CC/P), and QR2 is the flow after
pulse weight normalization (L, i. e., liters, or CC, i. e. cm3).
The “Pulse Weight Normalization Coefficient” parameter of the Function Block Detail
Builder is set as follows:
• Pulse Weight Normalization Coefficient: 0.000000 to 1.0000.00
■ Correction Before Temperature Compensation - FSBSET £

▼ Flow Rate Conversion Code Before Correction
Input pulses can be corrected as follows before temperature compensation.
QR3=CCX • QR2
(QR3: measured input pulse count, CCX: flow rate correction factor before temperature compensation)
The “Flow Rate Conversion Code Before Correction” parameter of the Function Block
Detail Builder is set as follows:
• Flow Rate Conversion Code Before Correction:
Select “0 (No)” or “1 (Yes).”
■ Temperature Compensation - FSBSET £

▼ Temperature Correction Code
Given a measured input pulse count of QR3, and a temperature T (C) measured by
another function block, the QR4 compensated pulse count is determined as follows:
QR4=QR3 • VCF
(QR4: measured input pulse after temperature compensation, VCF: volume conversion factor)
Temperature compensation code number

0: No compensation
(ICC) 1: New ASTM (Crude oil) <New ASTM: ASTM D1250-80>
2: New ASTM (Fuel oil)
3: New ASTM (Lubrication oil)
4: Old ASTM
5: VCF input • QR3
The “Temperature Correction Code” parameter of the Function Block Detail Builder is set
as follows:
• Temperature Correction Code: Select “0,” “1,” “2,” “3,” “4” or “5.”

The compensation calculations are as follows:
● New ASTM Compensation £
V15 t
VCF= = exp [-tt (1.0+0.8tt) ]
Vt 15
K0+K115 K0 K1
t = = +
(15)2 (15)2 15
B
t =A+
(15)2 D080110E.EPS
where
VCF is the volume conversion factor (at 15 C),
V15 is the volume (m3) at 15 C.
Vt is the volume (m3) at an arbitrary temperature t C,
t is the density (kg/m3) at t C,
15 is the density (kg/m3) at 15 C,
t is the coefficient of thermal expansion (C-1) at 15 C,
t is the temperature difference of t=t-15 (C), and
K0, K1, A and B are parameters (see the table below).
Table Parameter for ASTM (New JIS Standards) Compensation £
Range of Density (at 15 C) Parameter

Oil Types
kg/m3 K0 K1 A B
Crude 610.51075.0 613.9723 0.0 ... ...
653.0<770.25 346.4228 0.4388 ... ...
770.25<787.75 ... ... -0.00336312 2680.3206
Fuel
787.75838.75 594.5418 0.0 ... ...
838.751075.0 186.9696 0.4862 ... ...
Lubrication 800.01164.0 0.0 0.6278 ... ...
D080111E.EPS

● Old ASTM Compensation £
VCF=1+Q1 (T-15 )+Q2 (T-15)2 D080112E.EPS

VCF is the density conversion factor
Q1= -P1/D154 +P2
Q2= -P3/D154 +P2
D154 is the density ratio between 15 C and 4 C,
T is the measurement temperature (C), and
P1-P4 are parameters.
Table Parameters for ASTM (Old JIS Standards) Compensation £

Specific Gravity Range P1 • 106 P2 • 106 P3 • 106 P4 • 106
0.5000D154 <0.5050 4517.7 5919.2 30.466 51.948
0.5050D154 <0.5100 4522.6 5934.8 23.957 39.098
0.5100D154 <0.5150 4076.3 5059.8 27.668 46.373
0.5150D154 <0.5200 4140.2 5183.8 16.175 24.058
0.5200D154 <0.5250 4499.0 5873.9 31.553 53.631
0.5250D154 <0.5300 4574.4 6017.5 25.376 41.886
0.5300D154 <0.5400 4058.3 5043.7 21.064 33.730
0.5400D154 <0.5500 3911.5 4771.8 22.551 36.483
0.5500D154 <0.5600 4154.9 5214.4 19.946 31.747
0.5600D154 <0.5700 3718.6 4435.4 13.942 21.026
0.5700D154 <0.5800 3494.4 4042.0 14.192 21.464
0.5800D154 <0.5900 3945.5 4819.9 27.444 44.313
0.5900D154 <0.6000 4893.6 6426.7 47.623 78.514
0.6000D154 <0.6200 2448.9 2340.9 1.589 1.947
0.6200D154 <0.6399 2225.1 1980.0 1.588 1.946
0.6399D154 <0.6599 1936.6 1529.1 1.588 1.946
0.6599D154 <0.6798 1817.7 1348.9 1.588 1.945
0.6798D154 <0.6998 1756.4 1258.7 1.588 1.945
0.6998D154 <0.7497 1806.8 1330.8 1.588 1.945
0.7497D154 <0.7697 2226.8 1889.8 1.588 1.946
0.7697D154 <0.7897 1949.2 1529.1 1.588 1.946
0.7897D154 <0.8096 1734.8 1258.7 1.588 1.945
0.8096D154 <0.8296 1515.9 988.4 1.588 1.945
0.8296D154 <0.8496 1291.7 718.1 1.587 1.945
0.8496D154 <0.8745 1108.1 502.0 1.587 1.945
0.8745D154 <0.8995 919.1 285.9 1.586 1.944
0.8995D154 <0.9994 708.2 51.8 1.587 1.944
0.9994D154 <1.0993 984.2 328.0 -7.481 -7.129
1.0993D154 <1.2000 890.0 242.3 -7.830 -7.453
D080113E.EPS
● Other Temperature Compensation Methods £

When temperature compensation code “5” (VCF*F0) is selected in the Function Block
Detail Builder, the VCF can be set by an external calculation.

■ Correction after Temperature Compensation - FSBSET £
▼ Flow Rate Conversion Code After Correction
The measured input pulse after temperature compensation (QR4) can be corrected as
follows by setting the correction calculation in the builder:
QR5 = CCY • QR4 (L or CC)
QR5: Corrected flow rate/input pulse after temperature compensation; CCY: flow rate correction factor after tempera-
ture compensation
The “Flow Rate Conversion Code After Correction” parameter of the Function Block Detail
• Flow Rate Conversion Code After Correction:
Select “0 (No)” or “1 (Yes).”
■ Instantaneous Flow Computation - FSBSET £

Based on the measured flow after compensation, the instantaneous flow (PV) is calculated
as follows (note that the PV value is not stored if the data status is CAL):
In=QR5 • 3600/1000
PVn= (1 - ) In+ • PVn-1
where
QR5 is the flow value (in L or CC) after temperature compensation,
PVn-1 is the previous PV value,
In is the instantaneous flow rate, in KL/H or L/H, calculated from the pulse count,
and
: The filter constant (When “Pulse” is selected, the default is 0.5).
The PV value determined after filtering/compensation is used with the current SV value to
calculate instantaneous deviation PV-SV; this deviation is totalized during accumulated
deviation control.
SEE ALSO
For the filter constant, refer to C3.2, “Digital Filter.”
■ Totalizing Processing - FSBSET £

▼ Totalizer
The FSBSET totalizes the corrected flow rate/input pulse after temperature compensation
(QR5) in liters or cc’s into the totalizer SUM, as follows:
SUM =QR5 (From batch start to end)
The FSBSET also provides the following totalizers:

SUM1: Non-reset counter of uncompensated value
SUM1=QR3
(Always totalized; QR3: measured input flow after pulse weight normalization)
SUM2: Non-reset counter of compensated value

SUM =QR5
(Always totalized)

■ Simulation - FSBSET £
▼ Non-Reset Totalizer Shutdown at SIM
A simulation can be specified for each FSBSET.
Set the tuning parameter as follows to change the mode to simulation:
SIMM0 (Set a value other than 0.)
The MV is not output to outside the block (i. e., it is not updated).
A simulated pulse equal to the input range multiplied by the output ratio is applied to the
input.
The totalizing processing of non-reset counters (SUM1, SUM2) can be stopped or contin-
ued during simulation via specification in the Function Block Detail Builder.
The “Non-reset Totalizer Shutdown at SIM” parameter of the Function Block Detail Builder
is set as follows:
• Non-reset Totalizer Shutdown at SIM: Select “Yes” or “No.”
When the “Non-reset Totalizer Shutdown at SIM” parameter of the builder is set to “Yes,”
the non-reset counters (SUM1, SUM2) will not count in the simulation mode. However, the
reset counter SUM still counts irrespective of the setting of the parameter.

D8.1.6 Output Processing of Batch Set Control Block (FSBSET)

The output processing items of the FSBSET include analog output, connection to
the SET terminal of another instrument block, output tracking and output velocity
limiter.
■ Output Processing of the Batch Set Control Block £

The table below shows the output processing items of the FSBSET block.
Table Table of Output Processing Items for Batch Set Control Block (FSBSET) £
Output Processing
1 Analog output (4 to 20 m) Control valve: used
Connection to the SET terminal of another
2 Control valve: used
function block
3
4
5 Output tracking
6 Output velocity limiter
D080114E.EPS
: available
■ Analog Output - FSBSET £

The FSBSET can output to analog output modules. During output, the tight-shut function
and full-open function are automatically added to the manipulated output value (MV). The
direction of analog output can also be set.
Outputs to analog output modules are used to set data.
An MV in the range of 0 to 100 % is output from the OUT terminal.
Upon receiving an MV between 0 and 100 %, the analog output module outputs the corre-
sponding current between 4 and 20 mA to drive the control valve or other final control
element.
■ Connection to the SET Terminal of Another Function Block - FSBSET

£
The FSBSET sets an MV for the cascade setpoint (CSV) of the function block being con-
nected, via connection between its OUT terminal and the SET terminal of the function
block.
■ Output Tracking - FSBSET £

When the cascade loop connecting the FSBSET’s OUT terminal and the SET terminal of
another function block is open, then the block mode changes to initialization manual
(IMAN). This activates output tracking and causes the MV to agree with the value at the
connection destination of the OUT terminal.

■ Output Velocity Limiter - FSBSET £
The output velocity limiter restricts the amount of change in output value acquired last time
and this time according to its setting value, in order to prevent abrupt change in output
value. The output velocity limiter is an allowable amount of change in output value per scan
period. When it becomes active during manual operation, a non-restricted value is dis-
played, though the amount of change in MV is restricted. Setting the “Output Velocity
Limiter Bypass in MAN” to “No” prevents the output velocity limiter from operating during
manual operation. When the FSBSET block mode is in the Tracking (TRK) mode, the
Limiter does not work.
The Output Velocity Limiter and Output Velocity Limiter Bypass in MAN settings are speci-
fied as follows in the Function Block Detail Builder:
• Output velocity limiter:
A percentage value or a data item value in industrial scale unit within the range be-
tween 0 and the MV scale span limit
The set value must be positive (effective digits: 6 digits).
The default is “100.0 %.”
• Output velocity limiter Bypass in MAN: Select “Yes” or “No.”

D8.1.7 Alarm and Notification Processing of Batch Set Control

Block (FSBSET)
The alarm and notification processing items of the FSBSET include leakage alarm,
input failure, deviation error, output failure and processing in response to an exter-
nal EMST command.
■ Alarm and Notification Processing of the Batch Set Control Block

(FSBSET) £
The table below shows the alarm processing items of the FSBSET block.
Table Table of Alarm and Notification Processing Items for Batch Set Control Block (FSBSET)
£
Alarm Processing
1 Leakage alarm (LEAK)
2 Input failure (IOP)
3 Output failure (OOP)
4 First-stage deviation error (DV1)
5 Second-stage deviation error (DV2)
6
7 Loss-of-pulse (NPLS)
8
9 Alarm off (AOFS)
10
11
12 External EMST command (EMST)
13
14 Output stoppage (OUTS)
15 Connection failure (CFN)
16
17
18
19
20
D080115E.EPS
: available

■ Leakage Alarm (LEAK) - FSBSET £
▼ Leak Check, Detection Set Value
During the interval from the end of the current batch to the start of the next, flow rate calcu-
lation and totalization continue to be performed. The FSBSET compares this totalized
value and that at the previous batch end (stored upon batch end). This is called “leak
check.” If their difference exceeds the setpoint for leakage alarm detection, the alarm status
changes to LEAK. Leakage alarm detection is performed only when the block mode is
MAN and the control step is in ZONE 0.
To reset the leakage alarm and restart leakage checking, set Leak Reset tuning parameter
(LRSW) to “1.”
Leakage alarm detection can be enabled or disabled in the Function Block Detail Builder.
The “Leak Check” parameter of the builder is set as follows:
• Leak Check: Select “Yes” or “No.”
The setpoint for leakage alarm detection is set in the Function Block Detail Builder.
The “Detection Set Value” parameter of the builder is set as follows:
• Detection Set Value: 0.00 to 10000.00
■ Input Failure (IOP) - FSBSET £

▼ Input Open Alarm
If an input card fails, the IOP alarm of the FSBSET Block appears as input failure. If ASTM
temperature compensation is specified and the IOP alarm of temperature loops appears, or
if data is referenced by input connection and the IOP alarm of the connected function block
appears, the IOP alarm of the FSBSET block also appears as input failure.
■ Output Failure (OOP) - FSBSET £

▼ Output Open Alarm
If the output card fails or the output becomes otherwise abnormal, the alarm status
changes to OOP.
■ Deviation Errors (DV1, DV2) - FSBSET £

▼ Level-One Deviation Alarm, Level-Two Deviation Alarm
If a first-stage deviation error occurs in the instantaneous deviation or accumulated deviation,
the alarm status changes to DV1. If a second-stage deviation error occurs in the instantaneous
deviation or accumulated deviation, the alarm status changes to DV2.
If instantaneous deviation control is set as the deviation control type for FSBSET in the Func-
tion Block Detail Builder, the DV1 and DV2 indicate instantaneous deviation errors.
If accumulated deviation control is set as the deviation control type for FSBSET in the Function
Block Detail Builder, the DV1 and DV2 indicate accumulated deviation errors.
The first-stage deviation alarm and second-stage deviation alarm can be enabled or
disabled in the builder.
The “Level-one Deviation Alarm” and “Level-two Deviation Alarm” parameters of the Func-
tion Block Detail Builder are set as follows:
• Level-One Deviation Alarm: Select “Yes” or “No.”
• Level-Two Deviation Alarm: Select “Yes” or “No.”

● Instantaneous Deviation Error £
▼ Momentary Deviation Alarm Hysteresis
When the FSBSET is in the steps in which constant-flow control is performed (ZONE 2,
ZONE 3 or ZONE 5; also Zone 22 if specified in the builder), and if the instantaneous
deviation exceeds the corresponding alarm setpoint, the following processing is performed:
First-step deviation: When DL1 < En, the alarm status is changed to DV1.
Second-step deviation: When DL2 < En, the alarm status is changed to DV2.
Where
En is the instantaneous deviation,
DL1 is the first-stage deviation alarm point, and
DL2 is the second-stage deviation alarm point.
The instantaneous deviation alarm hysteresis can be specified for each function block in
the builder.
The “Momentary Deviation Alarm Hysteresis” parameter of the Function Block Detail
• Momentary Deviation Alarm Hysteresis: 0 to (SHSL).
The default is a value equivalent to 1 %.
SH: Scale high limit
SL: Scale low limit
● Accumulated Deviation Error £

▼ Accumulated Deviation Alarm Hysteresis
When the current control step is ZONE 22, ZONE 23 or ZONE 24, and if the accumulated
deviation exceeds an alarm setpoint, the following processing is performed:
First-step deviation: When DL1X < En, the alarm status is changed to DV1.
Second-step deviation: When DL2X < En, the alarm status is changed to DV2.
Where
En is the accumulated deviation,
DL1X is the first-stage deviation alarm point, and
DL2X is the second-stage deviation alarm point.
The accumulated deviation alarm hysteresis can be specified for each function block in the
builder.
The “Accumulated Deviation Alarm Hysteresis” parameter of the Function Block Detail
• Accumulated Deviation Alarm Hysteresis: 0.00 to 10000.00.
■ External EMST Command - FSBSET £

When an emergency stop command (EMSW=1) is received, the FSBSET outputs an alarm
(EMST) and performs emergency stop processing (EMST processing).

■ Loss-of-Pulse Error - FSBSET £
▼ Non-Incoming Pulse Alarm, Detection Mask Time, Detection Interval Time
If no pulses are received during loss-of-pulse detection processing within a preset period of
time, the data status changes to NPLS.
Loss-of-pulse detection processing is performed only during SET-UP (ZONE 1), flow rate
control (ZONE 2), STEADY (ZONE 3), EARLY (ZONE 4), PB control (ZONE 5) and PI
blending control (ZONE 22).
No loss-of-pulse detection is executed if MV=0 or SV=0.
The figure below shows the processing flow of loss-of-pulse detection:
SVH
(Final flow
rate setpoint)
Flow rate SVL

setpoint (Initial flow
(SV) rate setpoint)
CVK
(Extent of
CV kick) t
Initial flow rate
Start
control
EMST
Control status NON- SET UP SET UP Steady EMST Restart SET UP
Ctrl end
Control step
0 10 1 2 1 3 8 9 11 1
(zone)
Timer .......... ..........

t6 t7 t7 t7 t7 t6 t7 t7
Monitor Monitor
t6: Check mask time (set in builder)
t7: Check time (set in builder)
D080116E.EPS
Figure Loss-of-Pulse Detection Processing £
SEE ALSO
For the details of each control step, see D8.1.8, “Control Processing of Batch Set Control Block
(FSBSET).”

The loss-of-pulse alarm can be enabled or disabled in the builder.
The “Non-incoming Pulse Alarm” parameter of the Function Block Detail Builder is set as
follows:
• Non-incoming Pulse Alarm: Select “Yes” or “No.”
The check mask time (t6) shown in Figure “Loss-of-Pulse Detection Processing” indicates
the time immediately after start or restart during which loss-of-pulse detection is stopped.
The check mask time is specified in the builder.
The “Detection Mask Time” parameter of the Function Block Detail Builder is set as follows:
• Detection Mask Time: 0 to 10000 (unit: basic scan period).
The check time (t7) shown in Figure “Loss-of-Pulse Detection Processing” indicates the
period during which loss-of-pulse detection is performed. The check period is specified in
the builder.
The “Detection Interval Time” parameter of the Function Block Detail Builder is set as
follows:
• Detection Interval Time: 0 to 10000 (unit: basic scan period).
■ Output Stoppage Alarm - FSBSET

▼ Output Shutdown Alarm
When the block mode of a function block downstream in a cascade connection changes
from CAS to non-CAS, or when the cascade path is disconnected by a switch or the like,
the alarm status changes to OUTS.
The output stoppage alarm can be enabled or disabled in the builder.
The “Output Shutdown Alarm” parameter of the Function Block Detail Builder is set as
follows:
• Output Shutdown Alarm: Select “Yes” or “No.”

■ Alarm Statuses (Alarm and Notification Processing) of the Batch Set
Control Block (FSBSET) £
The table below shows alarm statuses related to alarm and notification processing of the
FSBSET block.
Table Table of Alarm Statuses for Batch Set Control Block (FSBSET) £
Abbreviation Service Description
NR Normal No alarm has occurred.
The status of the output is “output failure” (PTPF), caused by a malfunction of or
OOP Output open alarm break in the control element or process I/O device, or by a data error in the output
destination. Normally, the output function stops.
The status of the input is BAD, caused by a malfunction of or break in the control
element or process I/O device, or by a data error in the input destination.
IOP High input-open alarm
Normally, all processing which uses input data stops. If the cause is input
overshooting by some factor such as a break, the input overshoots upwards.
The input overshoots downwards by some factor such as a break. The status of the
IOP- Low input-open alarm
input turns to BAD. Normally, all processing which uses input data stops.
The absolute value of an instantaneous deviation between the measured value and
DV1 First-stage deviation alarm setpoint exceeds the DL1 alarm setpoint, or the absolute value of an accumulated
deviation exceeds the DL1X alarm setpoint.
The absolute value of an instantaneous deviation between the measured value and
DV2 Second-stage deviation alarm setpoint exceeds the DL2 alarm setpoint or the absolute value of an accumulated
deviation exceeds the DL2X alarm setpoint.
The totalization is still being executed while waiting for the next batch after the
end of a batch. If the current totalized value minus the totalized value at the end of
LEAK Leakage alarm
the previous batch exceeds the leakage detection setpoint, the leakage alarm is
activated.
When an emergency stop is commanded (EMSW=1), this alarm is activated. The
EMST Emergency stop alarm
alarm is on until the completion of the emergency stop procedure (EMST end).
If no pulse is detected during the specified interval, the loss-of-pulse alarm is
NPLS Loss-of-pulse alarm
activated.
Warns that the cascade connection is open. The OUTS alarm occurs when the
OUTS Output stoppage alarm secondary block turns to the modes other than CAS or when the cascade
connection has been disconnected by a switch or the like.
The status of the I/O destination block is O/S (out of service). This alarm enables
the user to identify the block still operating in the group of control blocks which
CNF Connection failure alarm
were put out of service for maintenance. Normally, IOP and OOP are activated at
the same time.
D080117E.EPS
■ Action Upon Activation of Alarms in the Batch Set Control Block

(FSBSET) £
▼ Emergency Stop by OOP/IOP/IOP-/NPLS/DV1/DV2/OUTS Alarms
The control action of the FSBSET (emergency stop or continuation of action) upon activa-
tion of an alarm can be specified in the Function Block Detail Builder for each alarm type.
The “Emergency Stop” parameters can be enabled or disabled for each of the alarm types
shown below:
IOP-, IOP, DV1, DV2, NPLS, OOP, OUTS

■ Bypassing Alarms or Notifications - FSBSET £
For each of the following alarms, the detection function can be bypassed individually via
specification in the Function Block Detail Builder:
IOP-, IOP, DV1, DV2, NPLS, LEAK, OOP, OUTS
For all of the following alarms and notifications, the notification functions can be bypassed
collectively by specifying AOFS (alarm off):
IOP-, IOP, DV1, DV2, NPLS, LEAK, OOP, OUTS, EMST
■ Control Steps of the Batch Set Control Block (FSBSET) and

Applicable Alarm Processing £
The table below shows whether alarms are detected at each control step of the FSBSET
block.
Table Table of Control Steps for Batch Set Control Block (FSBSET) and Applicable Alarm
Processing £
Deviation External
Control Leakage
Status Alarm Loss-of-Pulse IOP OOP EMST
Step Check
Processing Command
0 NON-CONTROL
1 SET-UP
2 I. F. CONTROL
3 STEADY
4 EARLY
5 P. B. CONTROL
6 WAIT
7 END
8 EMST
9 EMST END
10 START
11 RESTART
12 START
13 RESTART
20 START
21 RESTART
PI BLENDING
22
CONTROL
23 END WAIT
24 EMST
COMPONENT
25
CUT-OFF
26 END
D080118E.EPS
: available

D8.1.8 Control Processing of Batch Set Control Block (FSBSET)

Some of the processing performed in each of the FSBSET’s control steps are re-
peated over multiple steps (common processing), while others are performed only in
a specific control step.
■ Control Processing of Batch Set Control Block (FSBSET) £

The table below shows the control processing items performed by FSBSET block.
Table Table of Control Processing Items Performed by Batch Set Control Block (FSBSET) £
Alarm Processing
Item
Purpose Step Provided Remarks
Contents
No.
Common 0 Non-Control
1 Set-Up
2 Initial Flow Rate Control
3 Steady
4 Early
5 Pre-Batch Control
6 Wait
Batch Loader
7 End
(at Port)
8 During EMST Processing
9 EMST End
10 Start (CV-Kick)
11 Restart (CV-Kick)
12 Start
13 Restart
20 CV-Kick (Start)
21 CV-Kick (Restart)
22 Blend PI Control
Blending
23 Waiting END
Control
24 EMST
25 Component Being Released
26 End
D080119E.EPS
: available

■ Common Processing - FSBSET £
This section describes the common processing items of the FSBSET: PI control, emer-
gency stop processing, batch-end detection processing, early-point detection processing,
manual operation and operation commands. The batch end processing and early-point
detection processing are not performed if an endless shipment is specified.
● PI Control £
▼ Gain-Up Value
Flow rate control based on PI action (proportional action+integral action) is called PI con-
trol. The computation expression used for PI control is shown below:
T
MVn=KS • KP (En+ • En)
I
Where
MVn is the manipulated variable increment,
En is the deviation increment,
En is the deviation (En=PVn-SVn),
T is the control period (1 second),
I is the integral time (in seconds),
100
Kp is (= ) gain (set gain), and
P
MSH-MSL
Ks is the scaling factor (= ).
SH-SL D080120E.EPS
However, when P=0, the following I control computation is executed. The computational
expression used for I control is shown below:
I
MVn=KS • • En
I D080121E.EPS
The PI control algorithm is shown below:

For ZONE 1 only, (Kp=set gain+gain increment)
(Where the gain increment is a parameter set in the Function Block Detail Builder.)
Gap (dead band) PI control is also possible, that is:
MVn=0 when | En | BS (gap width)
The “Gain-up Value” parameter of the Function Block Detail Builder is set as follows:
• Gain-up Value: 0.00 to 100.00
● Emergency Stop Processing £

When an emergency stop alarm occurs or an emergency stop command is received
(EMSW0 or CMND=4), the FSBSET resets this command (EMSW=0 or CMND=0) and
proceeds to emergency stop processing (Zone 8).
● Batch-End Detection Processing £

When the totalized value reaches or exceeds (batch setpoint - predicted leakage value),
the control valve shuts tightly and processing proceeds to WAIT (ZONE 6). The conditional
expression for batch end detection is shown below:
SUMBSET-VL
However, when designation is “no batch processing” (NONB0), the batch does not end
even when the totalizer reading reaches the batch quantity (does not proceed to ZONE 6).

● Early-Point Detection Processing £
▼ Early Detection Bias Time
When batch processing is about to end (batch end), the flow rate gradually slow. Early-
point detection processing detects the point at which the flow rate starts to slow down.
When the SUM is equal to or exceeds the batch setpoint value from which pre-batch
quantity and expected leakage have been subtracted, the control step proceeds to ZONE4
“Early Processing.” The computational expression is shown below.
SUMBSET-QE-VL
The pre-batch quantity (QE) is automatically calculated from the current setpoint (SV). The
computational expression used varies depending on whether or not a control valve is used.
• Calculating QE when a control valve is used:
During early detection, the control valve is throttled back in increments of M. Thus,
the throttling time T can be calculated. The bias time (a) is added to T, and the pre-
batch quantity (QE) is calculated from the current setpoint (SV) as follows:
1000 1
QE (liters)=SV(%) • Max. flow (kl/h) • T (sec) • •
3600 2
When the current MV > the first-stage throttle setting, then
the first-stage throttle setting
T= • T (sec) + a (sec),
M
and when current MV the first-stage throttle setting, then
MV
T= • T (sec) + a (sec)
M D080122E.EPS
where
QE is the pre-batch quantity (liters),
MV is the current control valve opening (%),
M is the control valve throttling decrement when the EARLY status occurs (%) (set in the builder),
a is the bias time (sec), and
T is the control period (1 second).
The bias time for early-point detection (a) is specified in the builder.
The “Early Detection Bias Time” parameter of the Function Block Detail Builder is set
as follows:
- Early Detection Bias Time: 0 to 10000 (unit: basic scan period).

The figure below shows how each variable changes during early detection:
EARLY point EARLY point
Current SV T Current SV T
First-stage Current MV
throttle setting
Current MV First-stage
throttle
M setting M
QE QE
t t
MV First-stage throttle setting
a a
MV MV
T T
Time (sec) Time (sec)
D080123E.EPS
Figure Change in Variables During Early Detection (When Control Valve Is Used) £
TIP
When the designation is “no batch processing” (NONB0), early detection is bypassed.

• Calculating QE when a control valve is not used:
Although the calculation uses a similar expression, T is calculated from the current
flow rate setpoint (SV) since there is no value for control valve opening (MV).
1000 1
QE (liters)=SV (%) • Max. flow (kl/h) • T (sec) • •
3600 2 D080124E.EPS
If the current SV > the first-stage throttle setting
the first-stage throttle setting

M D080125E.EPS
If the current SV % the first-stage throttle setting
SV
M D080126E.EPS
where
QE is the pre-batch quantity (liters),
SV is the current flow rate setpoint (kiloliters per hour),
M is the control valve throttling decrement when the EARLY status occurs (kiloliters per hour),
a is the bias time (seconds), and
T is the control period (1 second).
The figure below shows how each variable changes during early detection:
EARLY point
T
M
Flow rate
setpoint
(%)
SV
QE
t
a
T
Time (sec)
D080127E.EPS
Figure Change in Variables During Early Detection (When Control Valve Is Not Used) £
The control valve throttling decrement (M) during early detection is specified in the
builder. Since M is defined as a percentage value regardless of whether or not the
OUT terminal of the FSBSET is connected, M is converted to a value in industrial
scale unit to calculate the pre-batch quantity (QE). In the same manner, the first-stage
throttle setting is also converted to the SV industrial scale unit.

● Manual Operation £
▼ MAN Intervention Processing
Changing the block mode to MAN allows manual operation of the FSBSET block (Auto-
matic control is interrupted). However, by setting the “MAN Intervention Processing” to
“Yes” on the Function Block Detail Builder, you can automatic control by changing the
control step during manual operation when the EMST command is received or a batch end
is detected. In this case, the block mode is automatically set to AUT or CAS.
The “MAN Intervention Processing” parameter of the Function Block Detail Builder is set as
follows:
• MAN Intervention Processing: Select “Yes” or “No.”
● Operation Commands £
Transition of control steps occurs via commands from a JOB controller, supervisory loop or
operator. Or, it may occur via commands issued by the FSBSET itself. Transition com-
mands that are sent from a JOB controller, supervisory loop or operator, are called opera-
tion commands.
The figure below shows the action of a batch loader FSBSET in response to operation
commands (CMNDs). The operation commands (1) through (4) in the figure indicate when
the start, emergency stop, restart and reset (abort) commands are issued.
CMND 1 (*1) 4 2 (*2) 3

Operation Start EMST Restart Forced reset
(1) (2) (3) (4)
SVH
(Final flow
rate setpoint)
Flow rate SVL

setpoint (Initial flow
(SV) rate setpoint)
CVK
(extent of
CV-kick setpoint) t
Initial flow rate Re-
Start
control start
SET SET EMST SET NON-
Control status NON- Steady EMST Steady Wait End
Ctrl UP UP end UP Ctrl
Control step
(zone) 0 (10) 1 2 1 3 8 9 (11) 1 3 6 7 0
D080128E.EPS
*1: Start action is for CMND=1 (with CV-kick).

*2: Restart action is for CMND=2 (with CV-kick).
Figure Action of FSBSET by Operation Commands (Batch Loader) £

• Start
Change the block mode to AUT or CAS and set as CMND=1 to enable CV-kick, or as
CMND=11 to disable CV-kick. This executes the startup process appropriate for the
specified action of CV-kick.
This process does not run unless the block mode is either AUT or CAS.
• Emergency Stop
Setting EMSW=1 or CMND=4 starts emergency stop processing.
• Restart
Set as CMND=2 to enable CV-kick, or as CMND=12 to disable CV-kick. This executes
the restart process appropriate for the specified action of CV-kick.
The process does not run unless the block mode is either AUT or CAS.
• Reset (abort)
Setting CMND=3 performs batch end processing and resets the instrument to the
block mode specified when starting the batch.
If the FSBSET is used as a component FSBSET, operation commands for the block are
automatically issued by the BLEND control block. The operator cannot issue operation
commands to the FSBSET directly.
The figure below shows the action of a component FSBSET (for blending control).
The operation commands (5) through (9) in the figure indicate when the start, emergency
stop, restart, waiting END and END commands are issued.
CMND Command 21 24 22 26 23
Operation Start EMST Restart Waiting END END
Block mode CAS CAS CAS CAS CAS
(5) (6) (7) (8) (9)
Flow rate
setpoint
(SV)
CVK
CV PI blending CV PI blending Waiting

Control status NON-Ctrl EMST End NON-Ctrl
Kick control Kick control for END
Control step
0 20 22 24 21 22 23 26 0
(zone)
Block mode MAN CAS MAN
D080129E.EPS
Figure Action of Batch Set Control Block (FSBSET) by Operation Commands (Components in
Blending) £

The figure below shows the component cut-off action of a component FSBSET (for blend-
ing control).
In the figure, (10) indicates when the component cut-off command is issued.
CMND Command 25
Operation Component cut-off
Block mode CAS
(10)
Flow rate
setpoint
(SV)
t
Component cut-off
Control
status PI blending control End Non Control
Control step
22 25 26 0
(zone)
Block mode CAS MAN
D080130E.EPS
Figure Component Cut-Off Action of Batch Set Control Block (FSBSET) by Operation Command
(Components in Blending) £

The figure below shows the control functions available in each control step of the FSBSET:
Table Table of Functions Available in Each Control Step of Batch Set Control Block (FSBSET)
(1/2) £
Control Block Emergency PI Batch End Early

Status Function Initialization
Step Mode Stop Control Detection Detection
0 NON-CONTROL Leakage check MAN

CAS
1 SET-UP SV increase in steps
(AUT)
CAS
2 I. F. CONTROL Initial flow rate control
(AUT)
CAS
3 STEADY Steady flow rate control
(AUT)
First-stage control valve (CV) CAS
4 EARLY
throttling (AUT)
Flow rate control at pre-batch CAS
5 P. B. CONTROL
setting flow rate (AUT)
CAS
6 WAIT Tightly shut control valve
(AUT)
After waiting a certain
predetermined time, the block CAS
7 END
mode changes to MAN and (AUT)
proceeds to step 0.
Multi-stage closing of control CAS
8 EMST
valve (AUT)
CAS
9 EMST END Tightly shut control valve
(AUT)
• Initialization processing CAS
10 START
• CV-kick (AUT)
• CV-kick CAS
11 RESTART
• Alarm status initialization (AUT)
CAS
12 START Initialization processing
(AUT)
CAS
13 RESTART Alarm status initialization
(AUT)
D080131E.EPS

Table Table of Functions Available in Each Control Step of Batch Set Control Block (FSBSET)
(2/2) £
PI Blend or
Batch Early- Deviation
Control Block Emergency Instantaneous
Status Function Initialization End Point Alarm
Step Mode Stop Dev PI
Detection Detection Processing
Control
Valve control with a

20 START specified opening kick CAS
quantity (CVK)
Valve control with a

specified opening kick
21 RESTART quantity (CVK) (Initializing CAS
information other than
batch totalized value)
PI blending control or
PI BLENDING
22 instantaneous deviation CAS
CONTROL
control
• Tightly shut control valve

(CV)
23 END WAIT CAS
• Retain totalized value as
the previous totalized value
24 EMST CV tightly shut CAS
COMPONENT
25 CV throttling CAS
CUT-OFF
• CV tightly shut
• Retain totalized value as
the previous totalized value
26 END MAN
• Change the block mode
to MAN and proceed to
step 0.
D080132E.EPS

■ Processing in Each Control Step - FSBSET £
This section describes the processing performed in each control step.
● ZONE 0 (Control status: NON-CONTROL) £

When the mode is MAN, only the leakage check is performed.
SEE ALSO
For the leakage check, see D8.1.7, “Alarm and Notification Processing of Batch Set Control Block
(FSBSET).”
● ZONE 1 (Control status: SET-UP) £

▼ SETUP Interval Time, Initial Flow Speed SET UP End Waiting Time, Normal Flow Speed SET UP
End Waiting Time
When a batch cycle is started, or the flow rate setpoint (final flow rate setpoint: SVH; or
initial flow rate setpoint: SVL) is updated, the current flow rate setpoint (SV) is changed in
steps during each control period until it agrees with the target value (SVL or SVH), after the
SET-UP waiting time (1 second, fixed) has elapsed. This flow rate setpoint (SV) is used to
perform PI control. When the SV reaches or overshoots the target value, it is held at the
current value (where SV=target value) for a certain predefined WAIT time, before process-
ing proceeds to the next control step.
The intervals in which the SV is changed in steps is specified in the Function Block Detail
Builder.
The “SETUP Interval Time” parameter of the builder is set as follows:
• SETUP Interval Time: 0 to 10000 (unit: basic scan period)
The increments in which the SV is changed in steps are specified as the STUP data item
(SV SET-UP increment), while the decrements are specified as the STDN data item (SV
SET-DOWN decrement).
The waiting time when the target value is reached is specified in the Function Block Detail
Builder.
The “Initial Flow Speed SET UP End Waiting Time” and “Normal Flow Speed SET UP End
Waiting Time” parameters of the builder are set as follows:
• Initial Flow Speed SET UP End Waiting Time:
0 to 10000 (unit: basic scan period)
• Normal Flow Speed SET UP End Waiting Time:
0 to 10000 (unit: basic scan period)
In this step, PI control, emergency stop processing, batch-end detection processing and
early-point detection processing are performed as common processing.

t0
SVH
or SV
SVL t0 (%) Set Down
decrement
SVH
or
SVL
SV
(%)
t t
Start
Set Up
increment t0: SET-UP interval time
D080133E.EPS
Figure SET-UP Processing and SET-DOWN Processing £
In ZONE 1, initial flow rate control is needed when the following conditions are met. There-
fore, the initial flow rate setpoint (SVL) is adopted as the target value during SET-UP
processing.
ILSW=1 (initial flow rate control command)
ILST > SUM (the totalized flow is less than the initial totalized flow setpoint)
If the above conditions are not met while setting up toward SVL, SET-UP toward SVH is
started immediately.
After SET-UP is completed, if the above conditions are met, then the step proceeds to initial
flow rate control (ZONE 2); if they are not, it proceeds to STEADY (ZONE 3).
● ZONE 2: Initial flow rate control £

PI control is carried out by using the initial flow rate setpoint (SVL) as the flow rate setpoint
(SV).
If the SVL is updated, control proceeds to ZONE 1. When initial flow rate control is released
or when the totalized flow reaches the initial totalized flow setpoint, the final flow rate
setpoint (SVH) is used as the target value and the control proceeds to ZONE 1.
● ZONE 3 (Control status: STEADY) £

PI control is carried out based on the final flow rate setpoint (SVH) as the flow rate setpoint
(SV).
If the SVH is updated, control proceeds to ZONE 1.

● ZONE 4 (Control status: EARLY) £
▼ Valve Throttling Quantity in Early Status, Previous-Batch Transition Decision Coefficient, First
Stage Valve Throttle Level in Early Status
The control valve is throttled back a fixed amount during each control period, and measure-
ment tracking is performed. Then, control proceeds to ZONE 5 (pre-batch control).
The computational expression used varies depending on whether or not a control valve is used.
In this step, emergency stop processing and batch-end detection processing are performed
as common processing.
SEE ALSO
For the details of early-point detection processing, see “■ Common Processing - FSBSET” in this section.
• Early-point detection processing when a control valve is used:

The manipulated output value (MV) is decreased in steps by M. M is the throttling
decrement during early-point detection processing specified in the Function Block
Detail Builder. The computational expression for this throttling is shown below:
MVn=MVn-1 - M
SVn=PVn (SV value tracks PV value.)
When MV0 or SVn • aSVPR (data item SVPR is the flow rate setpoint for pre-
batch; a is the pre-batch transition coefficient set in the Function Block Detail Builder)
is reached via throttling, the SV is set as SVPR and control proceeds to ZONE 5.
The figure below shows the throttling process until MV0 or SVn • aSVPR is
reached:
SV(=PV) • a
SV(=PV) • a
Flow rate Flow rate
setpoint setpoint
(%) (%)
MV MV
M M
SV
PV
SV PV
T
SVPR SVPR T
t t
Steady Early P.B.Ctrl Steady Early P.B.Ctrl
T: Control period T: Control period
(a) Transition to step 5 by [MV0] (b) Transition to step 5 by [SV • aSVPR]
D080134E.EPS
Figure Early-point Detection Processing (When Control Valve Is Used) £

The “Valve Throttling Quantity in Early Status” and “Previous-batch Transition Deci-
sion Coefficient” parameters of the builder are set as follows:
- Valve Throttling Quantity in Early Status: 0.001 to 100.000 %.
- Previous-batch Transition Decision Coefficient: 0.000 to 100.000 %.
TIP
When a control valve is used, control proceeds to ZONE 8 (EMST processing) if the status is IOP or OOP
alarm. If EMST is not specified, the block mode changes to IMAN and control remains at ZONE 4.
When the early point is detected, throttling back of the control valve starts from the
specified value (MP: the first-stage throttle setting at early detection, specified in the
Function Block Detail Builder).
Early point detection
MP
M
T
MV
(%)
t
T: Control period
(a) MP
MV
D080135E.EPS
Figure Throttling from Specified Value (MP) at Early Point Detection £
If the MP is larger than the current value, throttling back starts from the current value.
Early point detection

MP
M
T
MV
(%)
t
T: Control period
(b)MPMV
D080136E.EPS
Figure Throttling from Current Value (MV) at Early Point Detection £
The “First Stage Valve Throttling Level in Early Status” parameter of the builder is set
as follows:
- First Stage Valve Throttling Level in Early Status: 0.000 to 100.000 %.

• Early-point detection processing when a control valve is not used:
The SV is decreased in steps by M. The computational expression for this throttling
is shown below:
SVn=SVn-1 - M
MVn=SVn
When SVnSVPR (flow rate setpoint for pre-batch) is reached, control proceeds to
ZONE 5 with the setting of SV=SVPR.
The figure below shows the throttling process until SVnSVPR is reached:
SV
Flow rate MV
setpoint M
(%)
T
SVPR
t
Steady Early P.B.Ctrl
T: Control period

D080137E.EPS
Figure Early-point Detection Processing (When Control Valve Is Not Used) £
● ZONE 5 (Control status: PRE-BATCH-CONTROL) £

PI control continues with the flow rate setpoint for pre-batch (SVPR) used as the flow rate
setpoint (SV) until the totalized flow reaches the batch setting, and then control proceeds to
ZONE 6.
In this step, PI control, emergency stop processing and batch-end detection processing are
performed as common processing.
● ZONE 6 (Control status: WAIT) £

▼ Waiting Time during Batch End
The control valve is tightly shut, and control WAITs for a certain predetermined time to
totalize the flow rate while the valve is being shut.
Then, batch end processing is performed before control proceeds to ZONE 7.
The totalizer value is stored as the previous totalizer value for the next batch.
The time of WAIT processing is set in the builder.
The “Waiting Time during Batch End” parameter of the Function Block Detail Builder is set
as follows:
• Waiting Time during Batch End: 0 to 10000 (unit: basic scan period).

● ZONE 7 (Control status: END) £
▼ Waiting Time during End Process Completion
The control valve is tightly shut, and again WAITs for a preset time.
Control then returns to ZONE 0 after the mode changes to MAN.
The “Waiting Time during End Process Completion” parameter of the Function Block Detail
• Waiting Time during End Process Completion: 0 to 10000 (unit: basic scan period).
● ZONE 8 (Control status: EMERGENCY STOP) £

▼ Valve Throttling Quantity in Emergency Shutdown Status, First Stage Valve Throttle Level in
Emergency Shutdown Status
This step closes the control valve in steps, with control proceeding to ZONE 8 when an
emergency stop alarm is generated or an emergency stop command is detected.
The processing details of multi-step closing vary depending on whether or not a control
valve is used.
In this step, batch-end detection processing is performed as common processing.
• Multi-step closing when a control valve is used:
The MV is decreased in steps by ME during each control period, and control pro
ceeds to ZONE 9 when MV0 is reached. Measurement tracking is performed during
valve throttling.
The computational expressions for this throttling are shown below:
MVn=MVn-1 - ME
SVn=PVn
where
ME is the control valve throttling decrement in the EMST status (%) (specified in the
If the status is IOP or OOP alarm, then the following computational expression for
throttling is used instead:
MVn=MVn-1 - ME
SVn=MVn
The “Valve Throttling Quantity in Emergency Shutdown Status” parameter of the
Function Block Detail Builder is set as follows:
- Valve Throttling Quantity in Emergency Shutdown Status:
0.001 to 100.00 %.
The figure below shows the throttling process until MV0 is reached:
T
ME
MV
(%)
t
T: Control period
(a) When control valve is used
D080138E.EPS
Figure Emergency Stop Processing (When Control Valve Is Used) £

• Multi-step closing when a control valve is not used:
The SV is decreased in steps by ME until SV0 is reached, and then control pro-
ceeds to ZONE 9.
The computational expression for this throttling is shown below:
SVn=SVn-1 - ME
MVn=SVn
where
ME is the control valve throttling decrement in the EMST status (%) (specified in the
The figure below shows the throttling process until SV0 is reached:
T
ME
SV
(%)
t
T: Control period
D080139E.EPS
Figure Emergency Stop Processing (When Control Valve Is Not Used) £
• First-stage throttling specified in the builder:

When a control valve is used, it is throttled to the specified first-stage throttle level. At
that point, start normal throttling at the start of emergency stop processing at the
specified value (MPE). However, if the MPE value is larger than the current value,
throttling starts at the current value.
MPE is the valve first-stage throttle setting at the EMST status (%)
(specified in the Function Block Detail Builder).
The figure below shows the first-stage throttle setting for control valve specified in the
builder:
EMST detection
EMST detection
MPE MPE
ME
ME
T
MV MV T
(%) (%)
t t
T: Control period T: Control period
(a) MPE
MV (b) MPEMV
D080140E.EPS
Figure Control Valve First Stage Throttle Setting Specified in Builder £
The “Valve of First Stage Valve Throttle Level in Emergency Shutdown Status” param-
eter of the Function Block Detail Builder is set as follows:
- Valve of First Stage Valve Throttle Level in Emergency Shutdown Status:
0.000 to 100.00 %.

● ZONE 9 (Control status: EMST END) £
▼ Batch End Detection during Emergency Shutdown
This step completes the emergency stop. The details of processing vary depending on
whether or not a control valve is used.
In this step, batch-end detection processing is performed as common processing, even in
the EMST END status (specified in the Function Block Detail Builder).
• When a control valve is used:

Sets MV=0 to tightly shut the control valve.
Performs measurement tracking.
SVn=PVn
Or, SVn=MVn (if the status is IOP or OOP alarm)
• When a control valve is not used:
Sets SV=0 and MV=0.
The “Batch End Detection during Emergency Shutdown” parameter of the Function Block
Detail Builder are set as follows:
• Batch End Detection during Emergency Shutdown: Select “Yes” or “No.”

● ZONE 10 (RESET START) £

▼ SV Kick Width
After the initialization processing, control proceeds to ZONE 1 and starts batch processing.
The following are initialization processing items performed in this step:
• Initializes totalizer value: Clears SUM to 0.
• Initializes alarm status: Alarm status=NR
• Clears the accumulated deviation to 0.
• Resets emergency stop command:EMSW=0.
• CV (control valve) kick: Sets the kick value (CVK) to the MV.
• SV kick:
Same as the value set for SV kick width on the Function Block Detail Builder.
Definition item “SV Kick Width” may be defined as follows
- SV Kick Width: 0.000 - 100.000 %
Default setting is 0.000 %.
● ZONE 11 (Control status: RESTART FROM EMST) £

After the initialization processing, control returns to ZONE 1 and batch processing is restarted.
• CV kick:
Sets the kick value (CVK) to the MV, and outputs this value as position data.
• SV kick:
• Initializes alarm status:
Alarm status=NR.

● ZONE 20 (Control status: RESET START) £
For blending control, the batch starts with this step.
When the mode is CAS, control first performs the initial processing, then starts batch
processing.
• Initializes totalizer value: Clears SUM to 0.
• Initializes alarms status: Alarm status=NR.
• Clears the accumulated deviation (DV1, DV2) to 0.
• Proceeds to ZONE 22.
• CV kick: Sets the kick value (CVK) to the MV.
• SV kick:
● ZONE 21 (Control status: RESTART FROM EMST) £

Similar to ZONE 20.
However, does not clear SUM or accumulated deviation.
● ZONE 22 (Control status: BLEND PI CONTROL) £

▼ COMP Control Specification
Performs PI blending control or instantaneous deviation control (whichever is set in the
Function Block Detail Builder) based on the SV set from the supervisory loop. A deviation
alarm is applied to the totalizer value or instantaneous deviation, respectively.
• PI blending control
The computational expression for PI blending control is as follows:
T 3600
MVn=KS • KP (En+ • En • )
Ix 1000
Where
MVn is the manipulated variable increment (decrement),
En is the accumulated deviation,
En is the deviation (Kl/h),
T is the control period (seconds),
Ix is the integral time (seconds),
100
KP is the (= ) gain, and
Px
MSH-MSL
KS is the scale conversion factor ( = ).
SH-SL D080141E.EPS
TIP
The data item names of proportional band and integral time differ between blend PI control and instanta-
neous deviation control “P” and “I” are used in instantaneous deviation control, and “Px” and “Ix” in blend
PI control.

• Instantaneous deviation control
The computational expression for instantaneous deviation control is as follows:
T
MVn=KS • KP (En+ • En)
I
Where
MVn is the manipulated variable increment (decrement),
En is the deviation (PVn-SVn),
T is the control period (seconds),
I is the integral time (seconds),
100
KP is the gain (= ), and
P
MSH-MSL
KS is the scale conversion factor ( = ).
SH-SL D080142E.EPS
The “Control Computation Type” parameter of the Function Block Detail Builder is set
as follows:
- Control Computation Type:
Select “Accumulated deviation” or “Instantaneous deviation.”
The default is “Accumulated deviation.”
● ZONE 23 (Control status: WAIT FOR END) £

When the FSBSET reaches this step, the flow rate setpoint (SV) has already been set to 0
via specification from the supervisory loop.
The system confirms that the SV is 0, and performs the following end processing:
• Tightly shuts the control valve (MV=0).
● ZONE 24 (Control status: EMST) £

The supervisory loop is in the emergency stop status. The control valve is tightly shut. The
block mode may fallback to MAN/IMAN.
● ZONE 25 (Control status: COMPONENT CUT-OFF) £

▼ Valve Throttling Quantity in COMP Cut-Off Status
Component cut-off h as been ordered by the supervisory loop, and the following end
processing is being performed. The details of processing vary depending on whether or not
a control valve is used.
• When a control valve is used:
Throttle the MV by MR during each control period. When MV0 is reached, proceed
to ZONE 26. The computational expression for this throttling is shown below:
MVn=MVn-1 - MR
SVn=PVn
where MR is the valve throttling decrement (set in the Function Block Detail
Builder).
When a control valve is used, the valve is throttled based on the following expression
if the status is IOP or OOP alarm:
MVn=MVn-1 - MR
SVn=MVn

The figure below shows the throttling process until MV0 is reached:
T
MR
MV
(%)
t
T: Control period
D080143E.EPS
Figure Emergency Stop Processing (When Control Valve Is Used)
The “Valve Throttling Quantity in COMP Cut-off Status” parameter of the Function
Block Detail Builder is set as follows:
- Valve Throttling Quantity in COMP Cut-off Status:
0.001 to 100.000 %
• When a control valve is not used:
The SV is set as 0, and MVn as SVn. Then, control proceeds to ZONE 26.
The figure below shows the throttling process:
T
SV
(%)
t
T: Control period
D080144E.EPS
Figure Emergency Stop Processing (When Control Valve Is Not Used) £
● ZONE 26 (END) £
The following end processing is performed.
• Tightly shuts the control valve (MV=0).
• Changes the block mode to MAN and returns to ZONE 0.

■ Control Step Transition Diagram - FSBSET £
The figure below shows the control step transition diagram:
(f)
(e)
(c)
(b)
1 2 3 4 5 6 (g) 7
P.B.
SET UP Steady Early Wait End
Ctrl
(d)
Initial flow rate control (i) (l)
11 9 8
(k) (n) (j)
EMST
Restart
end
Emergency Stop
(o)
10 0
(a) (m) (h)
NON-
Start
Ctrl
ZONE
Control
status
D080145E.EPS
(a) Batch start completed
(b) SET-UP ready (initial flow rate control)
(c) SET-UP end
(d) Initial flow rate control end (the operator directs the release, or the totalized value reaches the initial flow rate control
release quantity)
(e) Early-point detection (SUM > BSET-QE-VL)
(f) Batch-end detection (SUM > BSET-VL)
(g) WAIT end (batch-end processing completed)
(h) Batch end
(i) Emergency stop command (EMSW=1 or CMND=4)
(j) Emergency stop end
(k) RESTART end
(l) Batch end detection during emergency stop
(m) START command (CMND=1)
(n) RESTART command (CMND=2)
(o) Batch end detected, or Abort command (CMND=3)
Figure Control Step Transition Diagram of Batch Set Control Block (FSBSET) for Batch Loader
£

■ Commands - FSBSET £
The table below shows the commands available with FSBSET block.
Table Table of Commands Available with Batch Set Control Block (FSBSET) £
CMND Zone (Step) Status Description of Command
0
1 10 Supervisory setting Batch loader mode - start (with CV-kick)
2 11 Supervisory setting Batch loader mode - restart (with CV-kick)
3 6 Start mode Batch loader mode - abort
4 8 Start mode Batch loader mode - EMST
5
6
7
8
9
10
11 12 Supervisory setting Batch loader mode - start (without CVkick)
12 13 Supervisory setting Batch loader mode - restart (without CVkick)
21 20 CAS Component blending mode - start
22 21 CAS Component blending mode - restart
23 26 CAS Component blending mode - end (release)
24 24 CAS Component blending mode - EMST
25 25 CAS Component blending mode - component cut-off
26 23 CAS Component blending mode - waiting end
17
18
19
41 40 Supervisory setting Start with valve opened X% (NCCV)
42 41 Supervisory setting Restart with valve opened X% (NCCV)
43 43 Start mode X% (NCCV) end
44 44 Start mode X% (NCCV) EMST
D080146E.EPS

D8.1.9 Block Modes of Batch Set Control Block (FSBSET)

The block modes of the FSBSET include out of service, initialization manual,
manual, automatic and cascade.
■ Block Modes of the Batch Set Control Block (FSBSET) £

The table blow shows the block modes for FSBSET block.
Table Table of Block Modes for Batch Set Control Block (FSBSET) £
O/S Out of service All the functions are stopped.
IMAN MANual initialization Control computation and output actions are stopped.
MAN MANual Control calculation is stopped and output is manually manipulated.
AUT AUTomatic Control calculation is made and the result is output.
When used as a blending component controller, a control calculation is made
CAS CAScade using the setpoint (CSV) set by the supervisory block and the result is output.
When used as a batch loader, the action is the same as AUT above.
D080147E.EPS

D8.1.10 Data Items of Batch Set Control Block (FSBSET)

There are 61 types of data items that can be set with the FSBSET.

■ Data Items of the Batch Set Control Block (FSBSET) £
The table below shows the data items set with FSBSET block.
Table Table of Data Items Set with Batch Set Control Block (FSBSET) (1/2) £
Abbreviation Service Entry Range/Unit Default
BSTS Block status N/A ----- -----
ALRM Alarm status N/A ----- NR
AFLS Alarm flashing status N/A ----- -----
AF Alarm detection specification N/A ----- -----
AOFS Alarm masking specification N/A ----- -----
PV Instantaneous flow rate Cond. Industrial scale unit used for PV -----
RAW Raw data Cond. Scale unit used for IN-terminal destination -----
SV Setpoint of flow rate Industrial scale unit used for PV SL
MV Manipulated output value Industrial scale unit used for MV MSL
DV Instantaneous deviation N/A (SL - SH) to (SH - SL) 0
DVX Accumulated deviation SUM, industrial unit 0
SVPR Flow rate setpoint for pre-batch SL to SH SL
SVH Final flow rate setpoint SL to SH SL
SVL Initial flow rate setpoint SL to SH SL
ILST Setting to release initial flow rate control Industrial unit used for SUM 0
VL Predicted leakage value Industrial unit used for SUM 0
P Proportional band (Instateneous deviation control) 0-1000.0 % 100.0
I Integral time (Instateneous deviation control) 0.1-10,000.0 seconds 20.0
PX Proportional band (PI blending control) 0-1000.0 % 100.0
IX Integral time (PI blending control) 0.1-10,000.0 seconds 20.0
BS Non-linear gap width 0-100.0 % 0.00
First-stage deviation alarm setting for
DL1 0 to (SL - SH) SH-SL
instantaneous flow rate
Second-stage deviation alarm setting for
DL2 0 to (SL - SH) SH-SL
instantaneous flow rate
First-stage deviation alarm setting for
DL1X Industrial unit used for SUM SH*1000
accumulated deviation
Second-stage deviation alarm setting for
DL2X Industrial unit used for SUM SH*1000
accumulated deviation
SUM Totalized value of corrected value Industrial unit used for SUM 0
SUM1 Non-reset and non-corrected totalized value Industrial unit used for SUM 0
SUM2 Non-reset and corrected totalized value Industrial unit used for SUM 0
D080148E.EPS
: entry possible
Cond.:entry possible under certain conditions
N/A: entry not possible

Table Table of Data Items Set with Batch Set Control Block (FSBSET) (2/2) £
BSET Batch setpoint Industrial unit used for SUM 0
CMND Command switch 0-63 0
ZONE Control step N/A 0-63 0
EMSW Emergency-stop command switch 0 or 1 0
LRSW Leakage-reset command switch 0 or 1 0
NONB Endless-batch command switch 0 or 1 0
ILSW Command switch for initial flow rate control 0 or 1 0
OPHI Output high limit index MSL to MSH MSH
OPLO Output low limit index MSL to MSH MSL
DR Control action N/A 0 (for direct) or 1 (for reverse) 1
EMCD EM-ST factor code N/A 0-32,767 0
STUP SV set-up increment 0-100 % 1
STDN SV set-down decrement 0-100 % 2
CVK Extent of CV kick 0-100 % 0
SIMM Simulation designation 0 or 1 0
Factor for flow rate correction before
CCX 0.00000-100.0000 1.00000
temperature compensation
Factor for flow rate correction after
CCY 0.00000-100.0000 1.00000
temperature compensation
DENS Density used for temperature compensation 0.00000-100.0000 0.00000
Temperature compensation factor
VCF 0.00000-100.0000 1.00000
(for setting/displaying VCF)
NCCV Extent of valve opening in non-control zone 0.000-100.000 % 100.000
DSM Instantaneous flow after correction N/A Industrial unit used for SUM 0
Y01-Y04 Optional buffer 1-4 -100.00000-100.00000 0
Y05-Y09 Optional buffer 5-9 -32,768-32,767 0
OT01[16] Option tag 1 16 alphanumeric characters NULL
OPMK Operation mark 0-255 0
SH Scale high limit N/A Industrial scale unit used for PV -----
SL Scale low limit N/A Industrial scale unit used for PV -----
MSH Scale high limit for MV N/A Industrial scale unit used for MV -----
MSL Scale low limit for MV N/A Industrial scale unit used for MV -----
CRD Ratio control designation N/A 0 or 1 0
D080149E.EPS
: entry possible

<Toc> <Ind> <D8.2 Blending Master Control Block (BLEND)> D8-61
D8.2 Blending Master Control Block (BLEND)

The Blending Master Control Block (BLEND) provides functions required for tank
blending control and direct blending shipment control; it controls flow rate and
batch quantity at the port or for a blend header used to set component flow rates.
■ Classification Between Tank Blending and Direct Shipment - BLEND £

Although tank blending and direct blending shipment are both blending work, the two are
classified as different works based on whether or not an FSBSET that performs batch
control is located at the port. The blending work is considered direct blending shipment if
there is an FSBSET, and tank blending if there is no FSBSET.
Hence, even if the work consists of blending in a tank, if batch quantity control is performed
by an FSBSET control block, then the control is classified as direct blending shipment.
■ Tank Blending Control Functions - BLEND £

Tank blending control uses BLEND master and FSBSET control blocks.
The BLEND master manages secondary-loop FSBSET blocks that control the flow rate of
each component. The BLEND master controls batch quantity, managing both the flow rate
and totalized flow of each component; it sets the initial flow rate setpoint (SV) for each
component FSBSET by multiplying its own SV by the blending ratio for the corresponding
component, and performs batching control by totalizing the instantaneous flow rates of all
FSBSET blocks.
■ Direct Blending Shipment Functions - BLEND £

Direct blending shipment control uses BLEND master and FSBSET control blocks.
The BLEND master manages secondary-loop component FSBSET blocks and the “port
FSBSET” (or “port BLEND” block) which manages flow rate and batch control at each port.
Batch control itself is performed by the “port FSBSET” block (or “port BLEND” block).
The BLEND master sets the flow rate setpoints (SV) for each of the component FSBSET
blocks by multiplying its own SV by the corresponding blending ratio.
IMPORTANT
The BLEND located at the port (“port BLEND”) can only perform the functions allowed for a
tank blending BLEND. No flowmeter signal (from the port) can be connected to a “port
BLEND.”

D8.2.1 Operation for Tank Blending Control

During tank blending control, the BLEND master performs SET-UP, release of initial
flow rate control, early-point detection processing and pre-batch processing.
The operation of the BLEND master is indicated by a sequence of control steps.
■ Operation for Tank Blending Control - BLEND £

The figure below shows the flow of BLEND master operation during tank blending control:
(BLEND) t2 t2
SVH
Supervisory
flow rate
setpoint
(SV)
t1
SVL
SVPR
t3 t4
t
Supervisory Initial flow rate
controller (BLEND) control
Control NON- SET SET EMST Re- SET P.B. NON-
Start Steady EMST Steady Early Wait End
status Ctrl UP UP end start UP Ctrl Ctrl
Control
0 10 1 2 1 3 8 9 11 1 3 4 5 6 7 0
step
(zone)
Block
MAN AUT or CAS MAN
mode
Component (FSBSET) Start

Control NON- EMST Re- NON-
PI blending control PI blending control End
status Ctrl end start Ctrl
Block
MAN CAS CAS MAN
mode
Control 0 20 22 24 21 22 23 26 0
step
t1: Waiting time after completion of SET-UP to initial flow rate

t2: Waiting time after completion of SET-UP to final flow rate
t3: Batch end waiting time
t4: Waiting time for completion of end processing
D080201E.EPS
Figure Operation Overview of Tank Blending Control £

The basic operation of the BLEND master during tank blending control is explained below.
The explanations are based on the above figure.
• At the start of tank blending control, the block status of the BLEND master is changed
to AUT or CAS via a JOB controller or by an operator. A start command is then sent to
the BLEND master.
• When the BLEND master receives a start command (CMND=1), the control step
proceeds to ZONE 10 and a start command (CMND=21) is sent to component
FSBSET blocks.
Initialization processing for the BLEND master itself such as alarm or totalization
processing is performed, then the control step returns to ZONE 1. From the start until
the end of control, the BLEND master constantly multiplies its own flow rate setpoint
(SV) by the blending ratio for each of the components and distributes the results as
SVs to the corresponding components.
• SET-UP is started upon transition to ZONE 1. In SET-UP, the current flow rate setpoint
(SV) is ramped at a preset rate until it reaches the initial flow rate setpoint (SVL) or
final flow rate setpoint (SVH).
• When the waiting time for the end of SET-UP to initial flow rate (T1) elapses after the
current flow rate setpoint (SV) reached the initial flow rate setpoint (SVL), the control
• When the totalized flow (SUM) reaches the initial (totalized) flow setpoint (ILST), or
when an operator directs the release, the control step returns to ZONE 1, and SET-UP
is performed to ramp the current flow rate setpoint (SV) at a preset rate until it reaches
the final flow rate setpoint (SVH).
• When the waiting time for the end of SET-UP to final flow rate (T2) elapses after the
current flow rate setpoint (SV) reached the final flow rate setpoint (SVH), the control
• When the totalized flow (SUM) reaches the batch setpoint (BSET) less the pre-batch
quantity and predicted leakage value (VL), the control step proceeds to ZONE 4. The
flow rate setpoint (SV) decreases at a preset rate, and when the SV reaches the flow
rate setpoint for pre-batch (SVPR), the control step proceeds to ZONE 5.
• When the totalized flow (SUM) reaches the batch setpoint (BSET) less the predicted
leakage value (VL), the control step proceeds to ZONE 6. The flow rate setpoint (SV)
of each component FSBSET is set to 0, and an Wait for END command (CMND=26)
is sent to the component FSBSET blocks. Calculation for the totalized flow (SUM) still
continues during this time. When the waiting time for batch end (t3) elapses following
the transition to ZONE 6, the control step proceeds to ZONE 7.
• When the waiting time after the completion of end procedure (t4) elapses following the
transition to ZONE 7, a component release command (CMND=26) is sent to each
component FSBSET and the BLEND master itself changes its block mode to MAN.
The control step returns to ZONE 0, and tank blending control is completed.
• If an emergency stop command (CMND=4) is issued or a critical alarm is detected
during the batch cycle, the control step proceeds to ZONE 8 and the flow rate setpoint
(SV) decreases in steps until it reaches 0. When the SV drops to 0 or below, a compo-
nent EMST command (CMND=24) is sent to each component FSBSET, and the
control step of the BLEND master itself proceeds to ZONE 9. The block status
changes to EMST END (emergency stop end).
• If a restart command (CMND=2) is received in the EMST END status, the control step
proceeds to ZONE 11 and a restart command (CMND=22) is sent to each component
FSBSET. The control step of the BLEND master itself proceeds to ZONE 1, and tank
blending control is restarted.

The following operations are not shown in the above figure:
• During SET-UP in ZONE 1, if initial flow rate control is not specified or when the
totalized flow (SUM) reaches or exceeds the initial totalized flow setpoint, SET-UP is
performed based on the final flow rate setpoint (SV).
• If an abort command (CMND=3) is received in the EMST END state, the control step
returns to ZONE 6 and the processing is performed, starting from the operation in
ZONE 6 explained above.

D8.2.2 Operation for Direct Blending Shipment Control

During direct blending shipment control, the BLEND master performs blending
control and other processing operation.
The operation of the BLEND master is indicated by a sequence of control steps.
■ Operation for Direct Blending Shipment Control - BLEND £

The figure below shows the flow of BLEND master operation during direct blending ship-
ment control:
Supervisory
flow rate
(BLEND) setpoint
(SV)
t
Supervisory
controller (BLEND)
Control NON- NON-
Start Blending control EMST Blending control
status Ctrl Ctrl
Control
step 0 30 31 32 31 0
(zone)
Block
MAN CAS MAN
mode
Component (FSBSET)
Control NON- PI blending Re- PI blending NON-

EMST End
status Ctrl control start control Ctrl
Block
MAN CAS CAS
mode
FSBSET/BLEND at port
All Any Any

Control All During All
NON- one During control one
status EMST control End
Ctrll Start Re-start
D080202E.EPS
Figure Operation Overview of Direct Blending Shipment Control £

The basic operation of the BLEND master during direct blending shipment control is ex-
plained below. The explanations are based on the above figure.
• At the start of direct blending shipment control, the block status of the BLEND master
is changed to AUT or CAS via a JOB controller or by an operator.
• When control is started with any port FSBSET block (or port BLEND block) set to
perform product shipment, the control step immediately proceeds to ZONE 30 and
blending is started. A component start command (CMND=21) is sent to each compo-
nent FSBSET after a preset period of time. The control step of the BLEND master
itself proceeds to ZONE 31.
• When the control step reaches ZONE 31, the sum of the flow rate setpoints (SVs) or
instantaneous flow rates (PVs) of the port FSBSET blocks (or port BLEND blocks)
becomes the BLEND master’s own SV. The BLEND master then multiplies the SV by
the blending ratio for each of the component FSBSET blocks and distributes the
results as SVs to the corresponding FSBSET blocks.
• When the batch cycle is completed at all port FSBSET blocks (or port BLEND blocks),
a component release command (CMND=23) is sent to each component FSBSET.
The block mode of the BLEND master itself changes to MAN, and the control step
returns to ZONE 0.
• If all port FSBSET blocks (or port BLEND blocks) are shut down by an emergency
stop command during direct blending shipment control (ZONE 9), a component EMST
command (CMND=24) is sent to each component FSBSET. The control step of the
BLEND master itself proceeds to ZONE 32.
• If any of the port FSBSET blocks (or port BLEND blocks) is still operating while the
control step of the BLEND master is at ZONE 32, the BLEND master returns to ZONE
31, and direct blending shipment is restarted.

D8.2.3 Configuration of Blending Master Control Block (BLEND)

This section explains the function block diagram of the BLEND control block.
■ Function Block Diagram of Blending Master Control Block (BLEND) £

The figure below shows the function block diagram of the BLEND control block:
DV1 DV2 IOP NPLS OOP EMST
No. 1
data status Component Port No. 1
AOF
managing managing SV step
Releasing functions functions Release
No. 2 end
data status No. 2
SV step
ZONE
No. 14
data status Control step
CMND
No.1 Input processing
PV functions
(SUM) Operation command
(SUM) Release
end Control
No.2 Instanta- PV
functions
PV neous (SUM)
flow calc.
(SUM)
(SUM)
SUM SV SV
No.14
PV Totalization No. 14
(SUM) SV step
Component Component
FSBSET/BLEND FSBSET/BLEND
No.1 No.2 No.6
SV SV SV
Port FSBSET/BLEND
D080203E.EPS
Figure Function Block Diagram of Blending Master Control Block (BLEND) £
● Input Processing Functions £

The BLEND master acquires instantaneous-flow data from component FSBSET blocks to
summarize and totalize them, and reads flow rate setpoints from port FSBSET blocks and
BLEND blocks to obtain the totalized current flow rate setpoint.
● Component Management Functions £

The BLEND master manages the component configuration and monitors for component
flow alarms.
● Port Management Functions £

The BLEND master can also provide port batch functions.

D8.2.4 Component Management

The BLEND master can be configured to manage up to fourteen component FSBSET
blocks in secondary loops. The functions required to manage these FSBSET blocks
are called component management functions.
Information regarding the blocks managed by the BLEND master (component con-
figuration) is updated by the supervisory computer (JOB controller). It cannot be
changed by the user directly.
■ Component Management - BLEND £

When adding or deleting tag names of component FSBSET blocks managed by the
BLEND master or changing the blending ratio, the supervisory computer (JOB controller)
sets the tag names, blending ratios and release DT in the BLEND control block receive
buffer, and then issues a “change” command to MOD1. The BLEND block control buffer
cannot be changed by the user directly.
The figure below describes the concept of component management functions:
(JOB controller)
MOD1 (=0, 1, 2)
Control buffer Receive buffer

Data
Tag name (1) transition Tag name (1)
Tag name (2) Tag name (2)
• •
• •
• •
Blending ratio (1) Blending ratio (1)
• •
• •
• •
D080204E.EPS
Figure Conceptual Diagram of Component Management £

■ Structure of TAG Name and Release DT Data - BLEND £
The figure below shows the structure of tag name and release DT data set by the supervi-
sory computer (JOB controller) in the BLEND control block receive buffer:
Tag name Characters
Release DT . . . 1 1
Releasing (cut-off) bit

Release end bit
D080205E.EPS
Figure Structure of Tag Name and Release DT Data £
“Releasing (cut-off) bit” means that release processing (processing to cut off component) is
being performed for the specified component FSBSET; “release end bit” means that re-
lease processing is completed.
■ MOD1 Change Commands - BLEND £

The following change commands are issued by the supervisory computer (JOB controller)
to the MOD1 of the BLEND control block.
MOD1=0
(Disabled)
MOD1=1
(Copies new tag name and blending ratio data to the control buffer, and changes them.)
MOD1=2
(Sets to zero (or clears) the tag name and blending ratio data in the BLEND.)
When MOD1=1 or MOD1=2 is set, the MOD1 automatically returns to zero and
the processing for MOD1=1 or MOD1=2 is performed.

■ Component Release Processing (Delete Processing) - BLEND £
When a component is to be cut off during blending, first the flow rate of that component
must be set to zero. The processing for this is called “Release Processing.”
In release processing, the supervisory computer (JOB controller) sets the releasing (cut-
off) bit for the specified function block in the BLEND control block release buffer, then
issues a notification to set MOD1=1 in the BLEND, thereby executing the release.
The following processing is performed for the release-requested function block:
1. A component cut-off command (CMND=25) is issued to the specified component
FSBSET. The release request sets the FSBSET to ZONE 25. This component
FSBSET begins end processing, throttling back the MV by MR during each control
period. (If a control valve is not used, the SV is reduced step by step.) During release
processing, the BLEND still totalizes the SUM and PV of the releasing FSBSET.
Valve throttling MR may be specified on the Function Block Detail Builder.
Item to be defined.
- Valve Throttling Quantity in COMP cut-off status:
0.001 to 100.00
2. For the specified component FSBSET, when MV=0 or SV=0, first ZONE=26 is set,
then ZONE=0 is set; when the BLEND detects ZONE=0 then releasing is complete,
and it subsequently ignores that tag (no further processing will be performed).
If, before release processing for the component FSBSET is complete, a component
configuration change command is received from the supervisory computer, the com-
ponent being released will be included in the targets of change processing.
The figure below shows how each variable changes during release processing:
Releasing command
Each
variable MR
(%)
SV
PV
Releasing end
T
t
T: Control period
D080206E.EPS
Figure Change in Each Variable During Release Processing £

D8.2.5 Port Management

The BLEND master can be configured to manage up to six FSBSET or BLEND con-
trol blocks at ports in secondary loops. The functions required to manage these
blocks are called port management functions.
Information regarding the blocks managed by the BLEND master (shipment port
configuration) is updated by the supervisory computer (JOB controller). It cannot be
■ Port Management Functions - BLEND £

When adding or deleting port FSBSET blocks or BLENDs managed by the BLEND master,
the supervisory computer sets the tag names in the BLEND control block receive buffer,
and then issues a “change” command to MOD2. The BLEND control buffer cannot be
The figure below describes the concept of port management functions:
MOD2 Receive buffer
Control buffer
Shipment port
Tag name (1) tag name
Tag name (2)
•
•
•
Data transition
Tag name (6) processing
D080207E.EPS
Figure Conceptual Diagram of Port Management £

■ Structure of Tag Name Data - BLEND £
The figure below shows the structure of tag name data set by the supervisory computer in
the BLEND control block receive buffer:
Port tag name

(Characters)
D080208E.EPS
Figure Structure of Tag Name £
■ MOD2 Change Commands - BLEND £

The following change commands are issued by the supervisory computer (JOB controller)
to the MOD2 of the BLEND control block:
MOD2=0 (No operation)
MOD2=1 (Adds the specified port)
MOD2=2 (Deletes the specified port)
MOD2=3 (Deletes all ports)
When MOD20 is set, the processing for MOD20 is performed and the MOD2 automati-
cally returns to zero.
■ Connection with Blocks of Other Stations - BLEND £

▼ Scan Specification
When the port FSBSET block (or port BLEND block) is used as dummy block in the self
station, the scan of the block should be specified “OFF” on the Function Block Detail
Builder.
Item to be defined.
• Scan Specification: “ON” or “OFF”
The default setting is “ON.”
Normally, port FSBSET blocks and component FSBSET blocks must be located at the
same station as the BLEND master. However, it is possible to locate port FSBSET blocks
and component FSBSET blocks at other stations.
That is, direct blending shipment can be performed by using an ADL data link block to copy
the SV and ZONE values of the port FSBSET blocks to dummy port FSBSET blocks of the
self station.

D8.2.6 Input Processing of Blending Master Control Block

(BLEND)
The input processing items of the BLEND master include component PV acquisition,
SV acquisition from FSBSET at port and component alarm acquisition.
■ Input Processing of the Blending Master Control Block (BLEND) £

Table Table of Input Processing Items for Blending Master Control Block (BLEND) £
Input Processing
1 Component PV acquisition
2 SV acquisition from FSBSET at port
3 Component alarm acquisition
4
5
6
7
8
9
10
D080209E.EPS
: available
■ Component PV Acquisition - BLEND £

The BLEND master acquires, from all secondary-loop component FSBSET blocks, their
instantaneous flows (PVs) and variations (SUM) of totalized flows (SUM) from the previ-
ous values.
The BLEND master sets the sum of acquired PVs as its own PV, and adds the sum of
acquired variations in totalized flow (SUM) to its own totalized flow (SUM).
It does not acquire data from component FSBSET blocks that are in the release end status.
■ SV Acquisition from FSBSET at Port - BLEND £

▼ Standard Setting Flow Rate Specification of Shipping Outlet
The BLEND master acquires flow rate setpoints (SVs) from the port FSBSET blocks or
BLEND blocks corresponding to the tag names registered in its control buffer, then sets the
sum as its own SV. The BLEND master can be set in the builder to acquire instantaneous
flows (PVs) instead of SVs and set the sum as its own SV.
The “Standard Setting Flow Rate Specification of Shipping Outlet” parameter of the builder
is set as follows:
• Standard Setting Flow Rate Specification of Shipping Outlet:
Select “SV” or “PV.”
The default is “SV.”

■ Component Alarm Acquisition - BLEND £
The BLEND master acquires alarm statuses from all secondary-loop component FSBSET
blocks, then sets its own alarm status based on the result.
SEE ALSO
For the alarm processing of the blending master control block, see D8.2.8 “Alarm and Notification
Processing of Blending Master Control Block (BLEND).”

D8.2.7 Output Processing of Blending Master Control Block

(BLEND)
The output processing items of the BLEND master include component SV setting
and component command setting.
■ Output Processing of the Blending Master Control Block (BLEND) £

The table below shows the output processing items for BLEND block.
Table Table of Output Processing Items for Blending Master Control Block (BLEND) £
Output Processing
1 Component SV setting
2 Component command setting
3
4
5
D080210E.EPS
: available
■ Component SV Setting - BLEND £

The BLEND master multiplies by its own flow rate setpoint (SV) the blending ratio for each
of the secondary-loop component FSBSET blocks that are neither being cut off or in the
release end status, and distributes the results as SVs to the corresponding components.
■ Component Command Setting - BLEND £

The BLEND master sets the following commands for the CMND data items of secondary-
loop component FSBSET blocks:
21: Component start
22: Component restart
23: Component release
24: Component EMST
25: Component cut-off
26: Component wait for end
SEE ALSO
As for when to perform component command setting, see D8.2.9, “Control Processing of Blending Master
Control Block (BLEND).”

D8.2.8 Alarm and Notification Processing of Blending Master

Control Block (BLEND)
The alarm and notification processing items of the BLEND master include input
failure, deviation error, output failure, loss-of-pulse, alarm off, external EMST com-
mand, output stoppage and connection failure processing.
■ Alarm and Notification Processing of Blending Master Control Block

(BLEND) £
▼ Input Open Alarm, Non-Incoming Pulse Alarm, Level-One Deviation Alarm, Level-Two Deviation
Alarm, Output Shutdown Alarm, Output Open Alarm
Table Table of Alarm and Notification Processing Items for Blending Master Control Block
(BLEND) £
Alarm Processing
By component alarm tracking or by IOP
1 Input failure (IOP)
detection in itself
2 First-stage deviation error (DV1) By component alarm tracking
3 Second-stage deviation error (DV2) By component alarm tracking
4 Output failure (OOP) By component alarm tracking
5 Loss-of-pulse (NPLS) By component alarm tracking
6 Alarm off (AOFS) Determined by the designation in the BLEND.
By component alarm tracking or by an EMST
7 External EMST command (EMST)
command to itself (EMSW=1)
8 Output stoppage (OUTS) By component alarm tracking
9 Connection failure (CFN) By component alarm tracking
D080211E.EPS
■ Alarm Processing - BLEND £

Except for control blocks that are being cut off or in the release end status, the BLEND
master reads alarm statuses of all component FSBSET blocks and uses the result to
determine its own alarm status.
The figure below shows the types of failure and corresponding alarm statuses:
• Input failure or output failure: IOP, IOP-, OOP
• Deviation error alarm: DV1, DV2
• Loss of pulse alarm: NPLS
• Output stoppage: OUTS

■ External EMST Command - BLEND £
When an emergency stop command (EMSW=1) is received, the BLEND outputs an alarm
(EMST) and performs emergency stop processing (EMST processing). When an EMST
alarm is generated in a secondary component FSBSET, the alarm status of the BLEND
master itself changes to EMST.
■ Action Upon Occurrence of Alarms in the Blending Master Control Block

(BLEND) £
▼ Emergency Stop by OOP/IOP/IOP-/NPLS/DV1/DV2/OUTS Alarms
The control action taken for component FSBSET blocks (EMST or continue) upon occur-
rence of an alarm in the BLEND master, can be specified for each alarm type in the builder.
However, the specification on each component FSBSET is invalid; it must be specified in
the BLEND master.
The alarms for which control action can be specified are shown below:
■ Alarm Statuses (Alarm and Notification Processing) of Blending Master

Control Block (BLEND) £
Table Table of Alarm Statuses (Alarm and Notification Processing) for Blending Master Control
Block (BLEND) £
NR Normal No alarm has occurred.
OOP Output open alarm An OOP alarm has occurred in any of the component FSBSETs connected.
An IOP alarm has occurred in any of the component FSBSETs connected. Or, a
IOP High input-open alarm connection-status error on FSBSET/BLENDs at the port or component FSBSETs
has occurred.
IOP- Low input-open alarm An IOP- alarm has occurred in any of the component FSBSETs connected.
DV1 First-stage deviation alarm A DV1 alarm has occurred in any of the component FSBSETs connected.
DV2 Second-stage deviation alarm A DV2 alarm has occurred in any of the component FSBSETs connected.
An EMST alarm has occurred in any of the component FSBSETs connected. Or,
EMST Emergency stop alarm
an emergency stop has been activated by an EMST command (EMSW=1).
NPLS Loss-of-pulse alarm An NPLS alarm has occurred in any of the component FSBSETs connected.
CNF Connection failure alarm A CNF alarm has occurred in any of the component FSBSETs connected.
OUTS Output stoppage An OUTS alarm has occurred in any of the component FSBSETs connected.
D080212E.EPS

■ Alarm/Message Bypass - BLEND £
For each of the following alarms, the detection function can be bypassed individually via
specification in the builder:
For all of the following alarms and notifications, the notification functions can be bypassed
collectively by specifying AOFS (alarm off):
IOP-, IOP, DV1, DV2, NPLS, OOP, OUTS, EMST
■ Control Steps of the Blending Master Control Block (BLEND) and

Applicable Alarm Processing £
Table Table of Control Steps for Blending Master Control Block (BLEND) and Applicable Alarm
Processing £
Control Deviation Component Alarm Detection

Status
Step Error EM-ST Alarm NPLS IOP OOP
0 NON CONTROL
1 SET-UP
2 I. F. CONTROL
3 STEADY
4 EARLY
5 P. B. CONTROL
6 WAIT
7 END
8 EMST
9 EMST END
10 START
11 RESTART
31 BLEND CONTROL
32 EMST RESTART
30 START
D080213E.EPS

D8.2.9 Control Processing of Blending Master Control Block

(BLEND)
Some of the processing performed in each control step of the Blending Master
Control Block (BLEND) are repeated over multiple steps (common processing),
while others are performed only in a specific control step.

■ Control Processing Performed by Blending Master Control Block
(BLEND) £
Table Table of Control Processing Items Performed by Blending Master Control Block (BLEND)
£
Control Function
Item
Purpose Step Provided Remarks
No. Contents
Common 0 Non-Control
1 Set-up
2 Initial flow rate control
3 Steady
4 Early
Tank
5 Pre-batch control
blending
(batch 6 Wait
loader
7 End
mode)
8 During EMST processing
9 EMST end
10 Start
11 Restart
Direct 31 PI blending control
blending
32 EMST
shipment
(relay mode) 30 Waiting start
1-9, 31, By command from
Component release
32 supervisory system
3, 31 Pacing -0 (none)
Others
3, 31 Pacing -1 (first-stage deviation)
3, 31 Pacing -2 (pressure)
3, 31 Pacing -3
D080214E.EPS

■ Common Processing - BLEND £
This section describes the common processing items of the BLEND master: emergency
stop processing, batch-end detection processing, SV distribution processing, early-point
detection processing, pacing and operation commands. The batch-end processing and
early-point detection processing are not performed if an endless shipment is specified.
● Emergency Stop Processing £

▼ Emergency Shutdown Specification of All Shipping Outlets
In a tank blending application, if an emergency stop alarm occurs or if the emergency stop
command is received (EMSW0 or CMND=4), then the emergency stop status is reset
(EMSW=0 or CMND=0) and the sequence proceeds to emergency stop processing (ZONE
8).
After the completion of its own emergency stop processing, it initiates an emergency stop
command to all component FSBSET blocks.
In the case of direct blending shipment, the emergency stop for all FSBSET blocks of all
ports move the blocks into emergency stop processing (ZONE 32) step. While in the case
that the emergency stop command is triggered by the event other than CMND, the BLEND
block may send an emergency stop to all FSBSET blocks of all ports if the item on the
Function Block Detail Builder is specified so. Thus, all the FSBSET blocks move to emer-
gency stop processing.
Item to be defined.
• Emergency Shutdown Specification of All Shipping Outlets:
“YES” or “NO”
The default setting is “YES.”
● Batch-End Detection Processing £

When the totalized value reaches (batch setpoint - predicted leakage value), the SVs of
component FSBSET blocks are set to zero to issue a batch-end command, and the se-
quence proceeds to WAIT processing (ZONE 6). The conditional expression for batch-end
detection is shown below:
SUMBSET - VL

● SV Distribution Processing £
▼ Ratio Control Specification
The BLEND multiplies its SV by each component’s blend ratio and distributes the SV
values to each component FSBSET that is neither in the status “release processing” nor
“release processing end.” In this case, however, no component SV value must exceed the
corresponding SV’s range.
For component FSBSET blocks added during the batch action (this must be at the initial
step (ZONE 0)), a start command is sent. If “PPM” is designated for a component FSBSET
in a builder, the blending ratio is set in “PPM” (parts per million) and the units of the compo-
nent FSBSET are regarded as L/H (the flow rate in liters per hour) or L (the totalized flow in
liters).
The “Ratio Control Specification” parameter of the builder is set as follows:
Ratio Control Specification: Select “%” or “PPM.”
• Running port FSBSET with its control valve fully open during direct blending shipment
For a direct blending shipment, one FSBSET at the port can be run with its control
valve fully open; if the sum of the component flow setpoints is set to slightly less than
the flow rate setpoint of the port FSBSET, the output from this FSBSET is gradually
opened to fully open. This coefficient (sum of component flow rate setpoints: sum of
port flow rate setpoints) can be “tuned.”
Total of component flow settings=Total of flow setting at port • CPLO
where
CPLO is throttling prevention coefficient (the default is 100 % to 0 %).
● Early-Point Detection Processing £

▼ Early Detection Bias Time, Width of SV Drop in Early Status
When the end of batch processing (bath end) becomes close, the flow rate starts to de-
crease gradually. The early-point detection processing is performed to detect the point at
which the flow rate starts to decrease.
When the totalized value reaches or exceeds (batch setpoint - pre-batch quantity - pre-
dicted leakage value), the control step proceeds to ZONE 4 (early-point detection process-
ing). The computational expression is shown below:
SUMBSET-QE-VL
The pre-batch quantity (QE) is calculated as shown below.
During early-point detection processing, the control valve is throttled in preset decrements
S. Thus, the throttling time T can be calculated. T includes the bias time b, and the QE
can be calculated using the flow rate setpoint (SV). The calculation method to obtain QE is
shown below:
1000 1
QE (liters)=SV (kl/h) • T (set) • •
3600 2
SV(kl/h)
T= • T (sec) + b (sec)
SV(kl/h) D080215E.EPS
where
QE is the pre-batch quantity (L),
SV is the current flow rate setpoint (kl/h),
S is the early-point status setpoint decrement (kl/h),
b is the bias time (seconds), and
T is the control period.

The figure below shows how the flow rate setpoint (SV) changes during early-point detec-
tion processing:
Early point
T
S
Flow rate
setpoint
(%)
SV
QE
t
b
D080216E.EPS
Figure Change in Flow Rate Setpoint (SV) During Early-point Detection Processing £
Early-point detection is bypassed when an endless batch (NONB=1) is specified for the
BLEND.
• Specifying decrement for early-point detection processing
The setpoint decrement (S) during early-point detection processing is set in the
builder.
The “Width of SV Drop in Early Status” parameter of the Function Block Detail Builder
is set as follows:
Width of SV Drop in Early Status: 0.001 to 100.000 %.
• Specifying bias time for early-point detection
The bias time for early-point detection (b) is set in the builder.
The “Early Detection Bias Time” parameter of the Function Block Detail Builder is set
as follows:
Early Detection Bias Time: 0 to 10000 (unit: basic scan period).
● Master Pacing £
Execution of master pacing is determined not by a control block but rather by functions
outside the control block; start of pacing is then notified to the block. This judgment is
based on the detected alarm status of the function block.
Examples of alarm detection are listed below:
• when a HI alarm occurs in a specified pressure tag; or
• when DV1 (level-one deviation alarm) occurs in any of the component FSBSET
blocks.

The figure below shows the flow of master pacing action:
T
Hold SV value
MPSV
BLEND
MPDN MPUP
(Step-down (Step-up increment)
increment)
MPSPSV
Master pacing start command Master pacing release command

MPSP=*** MPSP=100 %
D080217E.EPS
Figure Flow of Master Pacing Action £
When the BLEND master is in the steps where constant-flow control is performed (ZONE
31 or 3) and if the master pacing setpoint (MPSP) is set, the BLEND maintains its current
SV while distributing the master pacing SV (MPSV) to the components. The MPSV is
initially same as the SV at the start of master pacing, and is changed in steps in set incre-
ments/decrements during each control period until it agrees with the target value (MPSP •
SV). The degree of this increment/decrement is set separately from the SV set-up incre-
ment (STUP) or set-down decrement (STDN) in normal operation, but by master pacing
set-up increment (MPUP) and set-down decrement (MPDN).
Master Pacing applies to ZONE3 or ZONE31 only. It does not apply to other zones where
the MPSP is always set to 100%. If the zone moves to zone other than ZONE3 or ZONE31
during Master Pacing, the MPSP immediately returns to 100%, but step-up or step-down
processing to return the MPSV to an SV continues. The figure below shows how the EMST
step-down processing occurs during Master Pacing.
EMST detection
SV
MPSV SV Step down
on EMST
MPDN
MPSP reverts SV (=MPSV)

to 100 %
Release from master pacing

D080218E.EPS
Figure Example of Change in MPSV During Pacing £
● Manual Operation £
▼ MAN Intervention Processing
The automatic control of BLEND block may be intervened by changing the block mode into
MAN. However, if MAN intervention processing is specified on the Function Block Detail
Builder, the BLEND block may behave the same as it is in AUT mode to transit its status
when receiving EMST command or when batch end detected. At this time, the block mode
changes to AUT or CAS.
Item to be defined.
MAN Intervention Processing: “YES” or “NO”
The default setting is “NO.”

● Operation Commands £
During tank blending control, the BLEND master can be operated via operation commands
(CMNDs).
During direct blending shipment control, the BLEND master itself monitors the FSBSET
blocks at the port and performs automatic operation. Therefore, an operator cannot operate
the BLEND master directly.
The figure below shows the action of BLEND by operation commands during tank blending
control.
The figure below shows the action of a batch loader FSBSET in response to operation
commands (CMNDs). The operation commands (1) through (4) in the figure indicate when
the start, emergency stop, restart and reset (abort) commands are issued.
CMND Command 1 4 2 3
Operation Start EMST Restart Forced reset
(1) (4) (2) (3)

(BLEND)
SVH
Supervisory
block flow
rate setpoint
(SV) SVL
t
Initial flow
Start
rate control
Control NON- SET SET EMST Re- SET
Steady EMST Steady Wait End
status Ctrl UP UP end start UP
Supervisory Control
controller step 0 10 1 2 1 3 8 9 11 1 3 6 7
(BLEND) (zone)
Block
MAN AUT or CAS MAN
mode
Start
Control NON- Re- PI blending NON-

PI blending control EMST End
status Ctrl start control Ctrl
Component Block
MAN CAS CAS MAN
(FSBSET) mode
Control
step 0 20 22 24 21 22 23 26 0
(zone)
D080219E.EPS
Figure Action of BLEND by Operation Commands £

• Start
Start processing is executed by changing the block mode to CAS or AUT and setting
(CMND=1).
• Emergency stop
Emergency stop processing is executed by setting (EMSW=1) or (CMND=4).
• Restart
Restart processing is executed by setting (CMND=2) only when the block mode is
AUT or CAS.
• Forced reset (abort)
Setting (CMND=3) will automatically change the block mode to the mode at the start,
and batch-end processing is executed.

■ Processing in Each Control Step - BLEND £
Table Table of Processing Items Performed in Each Control Step of BLEND £
Flow Rate
Sum of Distribu- Batch
Control Block Emergency Early Pacing
Status Step Functions Initialization SVs at tion (SV End
Step Mode Stop Detection Function
Port distribu- Detection
tion)
If any FSBSETs at the

port are in the start status,
NON
0 the BLEND changes its MAN
CONTROL
own block mode to CAS
and moves to step 30.
CAS
1 SET-UP SV increase in steps
(AUT)
CAS
2 I. F. CONTROL Initial flow rate control
(AUT)
CAS
3 STEADY Steady flow rate control
(AUT)
• Alarm status is set as

CAS
4 EARLY BPRE.
(AUT)
• SV decrements by S.
Flow rate control in pre- CAS

5 P. B. CONTROL
batch flow rate setpoint (AUT)
CAS
6 WAIT Batch end processing
(AUT)
• Moves the control of

component FSBSETs to
step 26. CAS
7 END
• Changes BLEND's own (AUT)
block mode to MAN and
proceeds to step 0.
CAS
8 EMST Multistage decrease of SV
(AUT)
Moves the control of

CAS
9 EMST END component FSBSETs to
(AUT)
step 24.
Changes the mode of CAS

10 START component FSBSETs to
(AUT)
CAS.
Changes the mode of

CAS
11 RESTART component FSBSETs to
(AUT)
CAS.
BLEND CAS
31 Performs blending control.
CONTROL (AUT)
Moves the control of

EMST CAS
32 component FSBSETs to
RESTART (AUT)
step 24.
Sets start delay timer and

CAS
30 START moves its own control to
(AUT)
step 31.
D080220E.EPS

The following describes the processing performed in a specific control step:
● ZONE 0 (Control Status: NON-CONTROL) £

When the port FSBSET/BLEND block is in operation (in zone other than ZONE0 or
ZONE7) in the MAN block mode, the block mode of the BLEND block turns to CAS, pro-
ceeding to ZONE30.
● ZONE 1 (Control Status: SET-UP) £

▼ SET UP Interval Time, Initial Flow Speed SET UP End Waiting Time, Normal Flow Speed SET UP
End Waiting Time
When a batch cycle is started, or the flow rate setpoint (final flow rate setpoint: SVH; or
initial flow rate setpoint: SVL) is updated, the current flow rate setpoint (SV) is changed in
steps during each control period until it agrees with the target value (SVL or SVH), after the
SET-UP waiting time (t0: 1 second, fixed) has elapsed. When the SV reaches or over-
shoots the target value, it is held at the current value (where SV=target value) for a certain
predefined WAIT time, before processing proceeds to the next control step.
The intervals in which the SV is changed in steps is specified in the builder.
The “SET-UP Interval Time” parameter of the Function Block Detail Builder is set as fol-
lows:
• SET-UP Interval Time: 0 to 10000 (unit: basic scan period).
The increments in which the SV is changed in steps are specified as the STUP data item
(SV SET-UP increment), while the decrements are specified as the STDN data item (SV
SET-DOWN decrement).
The waiting time when the target value is reached is specified in the builder.
The “Initial Flow Speed SET UP End Waiting Time” and “Normal Flow Speed SET UP End
Waiting Time” parameters of the Function Block Detail Builder are set as follows:
• Initial Flow Speed SET UP End Waiting Time:
0 to 10000 (unit: basic period).
• Normal Flow Speed SET UP End Waiting Time:
0 to 10000 (unit: basic period).
In this step, emergency stop processing, batch-end detection processing, early-point
detection processing and SV distribution processing are performed as common process-
ing.
t0: SET-UP waiting time

t0
SVH
or SV
SVL (%) SET-DOWN
t0 decrement
SVH
or
SV SVL
(%)
t t
SET-UP
Start
increment
Set Up Set Down
D080221E.EPS
Figure SET-UP and SET-DOWN Processing £

In ZONE 1, initial flow rate control is needed when the following conditions are met. There-
fore, the initial flow rate setpoint (SVL) is adopted as the target value during SET-UP
processing.
ILSW=1 (initial flow rate control command)
ILST > SUM (the totalized flow is less than the initial totalized flow setpoint)
If the above conditions are not met while setting up toward SVL, SET-UP toward SVH is
started immediately.
After SET-UP is completed, if the above conditions are met, then the step proceeds to initial
flow rate control (ZONE 2); if they are not, it proceeds to STEADY (ZONE 3).
● ZONE 2: Initial Flow Rate Control £

Initial flow rate control is carried out.
If the initial flow rate setpoint (SVL) is updated, control proceeds to ZONE 1, making the
SVL the target value. When initial flow rate control is released or when the totalized flow
reaches the initial totalized flow setpoint, the final flow rate setpoint (SVH) is used as the
target value and the control proceeds to ZONE 1.
ing.
● ZONE 3 (Control Status: STEADY) £

In this step, the setpoint value (SV) is held at the final flow rate setpoint (SVH).
If the SVH is updated, control proceeds to ZONE 1.
ing.
● ZONE 4 (Control Status: EARLY) £

The flow rate setpoint (SV) is decreased in steps by S. The throttling calculation is shown
below:
SVn=SVn-1 - S
When SVnSVPR is reached, control proceeds to ZONE 5 with the setting of SV=SVPR.
The figure below shows the throttling process until SVnSVPR is reached:
Flow rate SV
setpoint
(%) S
T
SVPR
t
Steady Early P.B.Ctrl
D080222E.EPS
Figure Early-Point Detection Processing £
In this step, emergency stop processing, batch-end detection processing and SV distribu-
tion processing are performed as common processing.

● ZONE 5 (Control Status: PRE-BATCH-CONTROL) £
The SV is held at SVPR (flow rate setpoint for pre-batch) until the totalized value reaches
the “pre-batch” totalized setting, then control proceeds to ZONE 6.
In this step, emergency stop processing, batch-end detection processing and SV distribu-
tion processing are performed as common processing.
● ZONE 6 (Control Status: WAIT) £

▼ Waiting Time during Batch End
During the waiting time for batch end, the BLEND master sets 0 for the SVs of component
FSBSET blocks that are neither being released nor in the release end status and sends
them an “Wait for END” command. Also, component FSBSET blocks operating in the MAN
mode are forced to change to the CAS mode.
Then, the BLEND master WAITs a certain predetermined time to allow for leakage.
The totalized value is stored as the previous totalized value, and control proceeds to ZONE
7 after batch end processing.
The “Waiting Time during Batch End” parameter of the Function Block Detail Builder is set
as follows:
• Waiting Time during Batch End: 0 to 10000 (unit: basic period).
● ZONE 7 (Control Status: END) £

▼ Waiting Time during End Process Completion, Configuring Devices Clear at Batch End
After again WAITing a certain predetermined time, the BLEND master performs the follow-
ing processing:
• It sends an END command to component FSBSET blocks that are neither being
released nor in the release end status. Component FSBSET blocks operating in the
MAN mode are forced to change to the CAS mode.
• If the BLEND master is set in the builder to clear configuration data at batch end, this
sequence clears the port and component tag names from the control buffer.
The block mode then changes to MAN and control returns to ZONE 0.
The time of WAIT processing is set in the Function Block Detail Builder.
The “Waiting Time during End Process Completion” parameter of the builder is set as
follows:
• Waiting Time during End Process Completion: 0 to 10000 (unit: basic scan period).
The “Configuring Devices Clear at Batch End” parameter of the Function Block Detail
• Configuring Devices Clear at Batch End: Select “Yes” or “No.”

● ZONE 8 (Control Status: EMERGENCY STOP) £
▼ Width of SV Drop in Emergency Shutdown Status
This step closes the control valve in steps, with control proceeding to ZONE 8 when an
emergency stop alarm is generated or an emergency stop command is detected.
The SV is decreased by SE in steps until it reaches 0.
SVn = SVn-1 - SE
where
SE is the decrement of SV in the EMST status.
When SV0 is reached (note that PV0 is not monitored), the BLEND master performs
the following processing:
• It sends an EMST command to component FSBSET blocks that are neither being cut
off nor in the release end status. Component FSBSET blocks operating in the MAN
mode are forced to change to the CAS mode.
• The BLEND master itself proceeds to ZONE 9.
The figure below shows the throttling of SV during emergency stop processing:
T
SE
SV
(%)
t
T
D080223E.EPS
Figure Throttling of SV During Emergency Stop Processing £
The decrement of SV in the EMST status is specified in the builder.

The “Width of SV Drop in Emergency Shutdown Status” parameter of the Function
Block Detail Builder is set as follows:
- Width of SV Drop in Emergency Shutdown Status: 0.001 to 100.000 %.
The default is “1.000 %”

● ZONE 9 (Control Status: EMST END) £
▼ Batch End Detection during Emergency Shutdown
After the BLEND master sends an EMST command to component FSBSET blocks that are
neither being cut-off nor in release end status, the BLEND block may continue to detect the
batch end status if it is defined on the Function Block Detail Builder.
Item to be defined.
• Batch End Detection during Emergency Shutdown:
“YES” or “NO”
The default setting is “YES.”
● ZONE 10 (RESET START) £

The BLEND master sends a start command to component FSBSET blocks.
The BLEND master proceeds to ZONE 1, changing its alarm status to NR.
● ZONE 11 (Control Status: RESTART FROM EMST) £

The BLEND master sends a restart command to component FSBSET blocks that are
neither being cut off nor in the release end status. For the component FSBSET blocks that
have not been started, it sends a start command.
The BLEND master proceeds to ZONE 1, changing its alarm status to NR.
● ZONE 31 (Control Status: BLEND CONTROL) £

Blending control is carried out.
• End processing
When all the FSBSET/BLEND blocks at the port are in the end status (ZONE 7) or
initial status (ZONE 0), the BLEND master issues an END command to component
FSBSET blocks that are neither being cut off nor in the release status.
The BLEND master returns to the initial status (ZONE 0) after changing its block mode
to MAN.
• Emergency stop processing
When all the FSBSET blocks/BLENDs at the port are in the emergency stop status
(ZONE 9), the BLEND master issues an EMST command to component FSBSET
blocks that are neither being cut off nor in the release status.
The BLEND master changes its status to emergency stop processing (ZONE 32).
• SV distribution processing
If the conditions for end processing or emergency stop processing are not met, the
total of the defined flow rate (kl/h) or instantaneous flow rate (specified on the Function
Block Detail Builder) of the port FSBSET/BLEND blocks is calculated as an SV of the
BLEND block. And after multiplying its SV by each blending ratio, the value is set to
the SV of component FSBSET block that is neither released nor completed to release.
However, this setpoint for each component must not exceed the range of the
component’s SV.
A start command is sent to all component FSBSET blocks that are in the initial status
(ZONE 0).

● ZONE 32 (Control Status: EMST) £
The BLEND master is in the emergency stop status.
The BLEND master sends an EMST command to all component FSBSET blocks that are
neither being cur off nor in the release end status. However, if even one of the FSBSET
blocks/BLENDs at the port is not in the emergency stop status, the BLEND master returns
to ZONE 31 and performs SV distribution processing.
If all the FSBSET/BLEND blocks at the port are in the end status (ZONE 7) or initial status
(ZONE 0), the BLEND master issues an END command to component FSBSET blocks that
are neither being cut off nor in the release status.
The BLEND master returns to the initial status (ZONE 0) after changing its block mode to
MAN.
● ZONE 30 (Control Status: START) £

▼ COMP Start Delay Time
The BLEND master sets the start delay timer, then performs the following processing after
WAITing for a preset period of time (set by the start delay timer):
• The BLEND master sends a start command to component FSBSET blocks and
proceeds to ZONE 31.
• It uses a start delay timer to adjust the times between when port FSBSET blocks are
started and when component FSBSET blocks are started, and reduces or eliminates
pressure-related interference between components.
The figure below shows the start delay processing by the BLEND master:
Port FSBSET SV
(%)
t
t6
BLEND component
FSBSET SV
(%)
t
t6: Start delay timer (set in the builder; normally, 1 sec)

D080224E.EPS
Figure Start Delay for Port FSBSET Blocks and Component FSBSET Blocks £
The start delay timer setting is specified in the builder.

The “COMP Start Delay Time” parameter of the Function Block Detail Builder is set as
follows:
- COMP Start Delay Time: 0 to 10000 (unit: basic scan period).

■ Control Step Transition Diagram - BLEND £
The figure below shows the control step transition diagram:
(f)
(o)
(e)
(c)
(b)
1 2 3 4 5 6 (g) 7
P.B.
SET UP Steady Early Wait End
Ctrl
(d)
(i) (l)
Initial flow rate control
11 9 8
(k) (n) (j)
EMST
Restart
end
Emergency Stop
(o)
Step
10 0
(a) (m) (h) Control
NON- status
Start
Ctrl
D080225E.EPS
(a) Batch start completed

(b) SET-UP ready (in initial flow rate control)
(c) SET-UP end
(d) Initial flow rate control end (command released, or setting to release reached)
(e) Early-point detection (SUM > BSET-QE-VL)
(f) Batch end detection (SUM > BSET-VL)
(g) WAIT end (batch end processing completed)
(h) Batch end
(i) Emergency stop command (EMSW=1 or CMND=4)
(j) Emergency stop end
(k) RESTART end
(l) Batch end detection during emergency stop
(m) START command (CMND=1)
(n) RESTART command (CMND=2)
(o) ABORT command (CMND=3)
Figure Control Step Transition Diagram of Blending Master Control Block (BLEND) £

■ Commands - BLEND £
Table Table of Commands Available with BLEND £
CMND Zone (Step) Status Description of Command
0
1 10 Supervisory setting Batch controller - start
2 11 Supervisory setting Batch controller - restart
3 6 Start mode Batch controller - abort
4 8 Start mode Batch controller - EMST
D080226E.EPS

D8.2.10 Block Modes of Blending Master Control Block (BLEND)

The block modes of the BLEND include out of service, initialization manual, manual,
automatic and cascade.
■ Block Modes of Blending Master Control Block (BLEND) £

Table Table of Block Modes for Blending Master Control Block (BLEND) £
O/S Out of Service All functions are stopped.
MAN MANual Control calculation is stopped.
AUT AUTomatic Control calculation is performed and the results are output.
When used in direct blending shipment, a control computation is performed using
CAS CAScade the setpoint input from the supervisory block and the results are output. When used
in tank blending, the action is the same as AUT above.
D080227E.EPS

D8.2.11 Data Items of Blending Master Control Block (BLEND)

There are 147 data items that can be set with the BLEND. Multiple settings are
available for port tags, component tags, blending ratios, totalized values of compo-
nents and component status flags.

■ Data Items of the Blending Master Control Block (BLEND) £
Table Table of Data Items Set with Blending Master Control Block (BLEND) (1/4) £
BSTS Block status N/A ----- -----
ALRM Alarm status N/A ----- NR
AFLS Alarm flashing status N/A ----- -----
AF Alarm detection specification N/A ----- -----
AOFS Alarm masking specification N/A ----- -----
PV Instantaneous flow rate Cond. Industrial scale unit used for PV -----
SV Setpoint of flow rate Industrial scale unit used for PV SL
SVPR Flow rate setpoint for pre-batch SL to SH SL
SVH Final flow rate setpoint SL to SH SL
SVL Initial flow rate setpoint SL to SH SL
ILST Setting to release initial flow rate control Industrial unit used for SUM 0
VL Predicted leakage value Industrial unit used for SUM 0
SUM Totalized corrected value Industrial unit used for SUM 0
BSET Batch setpoint Industrial unit used for SUM 0
CMND Command switch 0-63 0
ZONE Control step N/A 0-63 0
EMSW Emergency-stop command switch 0 or 1 0
NONB Endless-batch command switch 0 or 1 0
Command switch for initial flow rate
ILSW 0 or 1 0
control
EMCD EMST factor code N/A 0-32, 767 0
EMCP[16] EMST factor tag N/A ----- NULL
STUP SV set-up increment 0.00-100.00 % 1.00
STDN SV set-down decrement 0.00-100.00 % 2.00
MS01[16] Port tag 1 (for execution) N/A 16 alphanumeric characters NULL
CP01[16] Component tag 01 (for execution) N/A 16 alphanumeric characters NULL
D080228E.EPS
: entry possible

CR01 Blending ratio 01 (for execution) N/A 0.000-10,000.000 0.000
SM01 Totalized value of component 01 Industrial unit used for SUM 0
LC01 Component 01 status flag (for execution) N/A 0-3 0
D080229E.EPS
: entry possible

WP01[16] Component tag 01 (for setting) 16 alphanumeric characters NULL
WR01 Blending ratio 01 (for setting) 0.000-10,000.000 0.000
D080230E.EPS
: entry possible

WL01 Component 01 status flag (for setting) 0-3 0
Component configuration change
MOD1 —- 0
command
MOD2 Port change switch —- 0
MSMD[16] Port tag to be changed —- NULL
CPLO Throttling prevention coefficient 0.00-100.00 % 100.00
MPSV Master pacing SV Industrial scale unit used for PV SL
MPSP Master pacing factor 0.00-100.00 % 100.00
MPUP Master pacing set-up increment 0.00-100.00 % 1.00
MPDN Master pacing set-down decrement 0.00-100.00 % 2.00
DSM Instantaneous flow after corrections N/A Industrial unit used for SUM 0
Y01-Y04 Optional buffer 1-4 -100.00000-100.00000 0
Y05-Y09 Optional buffer 5-9 -32,768-32,767 0
OPMK Operation mark 0-255 0
SH Scale high limit N/A Industrial scale unit used for PV 0
SL Scale low limit N/A Industrial scale unit used for PV 0
CRD Ratio control designation N/A 0 or 1 0
D080231E.EPS
: entry possible

Blank Page

2008102523572200001

Transféré par

Informations du document

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

2008102523572200001

Transféré par

Droits d'auteur :

Formats disponibles

<Int> <Ind> <Rev> <Document Map> <Reference Map> Toc C-1

IM 33S01B30-01E 8th Edition : Dec.21,2001-00

IM 33S01B30-01E 8th Edition : Dec.21,2001-00

IM 33S01B30-01E 8th Edition : Dec.21,2001-00

C1. Structure of a Function Block

■ Basic Structure of the Function Block

Input Input PV, etc. Calculation Output MV, etc. Output

Data items Legend

Alarm processing flow

Figure Basic Structure of the Function Block

IM 33S01B30-01E 7th Edition : Apr.20,2001-00

IM 33S01B30-01E 7th Edition : Apr.20,2001-00

IM 33S01B30-01E 7th Edition : Apr.20,2001-00

IM 33S01B30-01E 7th Edition : Apr.20,2001-00

C2. I/O Connection

■ Connection Destination of I/O Connection

● Other Function Blocks

IM 33S01B30-01E 7th Edition : Apr.20,2001-00

IM 33S01B30-01E 7th Edition : Apr.20,2001-00

C2.1 Data Connection

■ Data Reference and Data Setting

IM 33S01B30-01E 7th Edition : Apr.20,2001-00

● Data Connection with Process I/O

Data reference Data setting

Input module Output module

Figure Data Connection with Process I/O

● Data Connection with Software I/O

Figure Data Connection with Software I/O

IM 33S01B30-01E 7th Edition : Apr.20,2001-00

Data reference Data setting

Figure Data Connection with Communication I/O

● Data Connection with Fieldbus I/O

Data reference Data setting

Fieldbus Communication Module

Figure Data Connection with Fieldbus I/O

IM 33S01B30-01E 8th Edition : Dec.21,2001-00

Data reference Data setting

PVI LDLAG PID

Figure Data Connection with Other Function Blocks’ Data Items

Data reference connection or cascade

Figure Data Setting for Calculated Input Value (RV)

IM 33S01B30-01E 7th Edition : Apr.20,2001-00

Element symbol name.data item name

Figure I/O Information Symbols ¡

*1: £ Can only be used with SFCS.

Figure I/O Information Symbols £ : LFCS2/LFCS2/SFCS

*1: For fieldbus communication, terminal “mm” ranges between 01 to 48.

Figure I/O Information Symbols £ : KFCS2/KFCS

IM 33S01B30-01E 8th Edition : Dec.21,2001-00

Table I/O Terminals for Character Strings

■ Data Reference with Respect to Dual-Redundant Input ¡ £

● Dual-Redundant Analog Input : PFCS/LFCS2/LFCS/SFCS

Figure Dual-Redundant Input Connection : PFCS/LFCS2/LFCS/SFCS

IM 33S01B30-01E 8th Edition : Dec.21,2001-00

● Dual-Redundant Multi-Point Analog Input : KFCS2/KFCS £

IM 33S01B30-01E 8th Edition : Dec.21,2001-00

■ Data Setting with Respect to Dual-Redundant Output ¡ £

● Dual-Redundant Analog Output : PFCS/LFCS2/LFCS/SFCS

IM 33S01B30-01E 8th Edition : Dec.21,2001-00

● Dual-Redundant Multi-Point Analog Output : KFCS2/KFCS £

IM 33S01B30-01E 8th Edition : Dec.21,2001-00

IM 33S01B30-01E 8th Edition : Dec.21,2001-00

C2.2 Terminal Connection

● Connection Between Function Blocks