Professional Documents
Culture Documents
CS 1000/CS 3000 Reference Function Block Details: Toc C-1
CS 1000/CS 3000 Reference Function Block Details: 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
Other
function
Set input terminal
block
SET
Function block
Alarm
processing
CSV,
SV,
Input terminal etc. Output terminal
C010001E.EPS
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.”
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.”
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.”
● 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
● 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.
■ 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
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.
PID
Process input Process output
IN OUT
C020101E.EPS
Data setting
PG-L13
%AN
SUB
Annunciator message
C020102E.EPS
CALCU
IN OUT
%WW, %WB
Communication I/O data
C020103E.EPS
SEE ALSO
For the details of communication I/O, see Part J, “Subsystem Communication (Using RIO)” or Part K,
“Subsystem Communication (Using FIO).”
CALCU
IN OUT
C020104E.EPS
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.
PV IN OUT VN
C020105E.EPS
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
%Z01usmm
Terminal (01 to 32)
Slot (1 to 4)
Unit (1 to 5)
C020107E.EPS
%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
%Znnusmm
Terminal (01 to 64) (*1)
Segment (1 to 4) (*2)
Slot (1 to 8)
Node number (01 to 10)
C020111E.EPS
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.
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:
Data reference
Data reference
Input
SS-DUAL
module IN1 PID
PV IN
IN2
Input
module
Data reference
C020110E.EPS
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.”
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
For more information about multi-point analog I/O module dual-redundant configuration, see a section
“■ Dual-FIO Analog Input/Output : KFCS2/KFCS £” in chapter A3.4.1, “Parameters for FIO Analog
Inputs/Outputs.”
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.”
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 : PFCS/LFCS/SFCS in chapter A3.3.2, “Parameters for Multiple
Analog Control Input/Output.”
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
For more information about multi-point analog I/O module dual-redundant configuration, see a section
“■ Dual-FIO Analog Input/Output : KFCS2/KFCS £ in chapter A3.4.1, “Parameters for FIO Analog
Inputs/Outputs.”
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.”
■ 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:
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.
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
PID AS-H
C020202E.EPS
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.
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
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)
SW33
PID AS-H
S11
OUT S12 S10 IN1 RV1
S13
C020205E.EPS
SW33
PVI
S11
I/O module S12 S10 IN
S13
C020206E.EPS
SW-33
PID
S11
OUT S12 S10 I/O module
S13
C020207E.EPS
SW-33
PID AS-H
S11
OUT S12 S10 IN RV1
S13
Input module
Data reference
C020208E.EPS
■ 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
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.
SEE ALSO
For condition specification and manipulation specification, see a chapter D3.3, “Logic Chart Block
(LC64).”
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
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
C020401E.EPS
Figure Connection between Control Stations (FCS) (Example of the Cascade Control) ¡ £
Function block
FCS 1 FCS 2
Function block Function block
IN
D1 ADL Data reference
OUT
Data setting ADL D2
D1: Data 1
Inter-station connection block D2: Data 2
C020402E.EPS
Terminal
ADL connection
Function block Function block SET
PID PID
IN OUT IN OUT
Terminal
connection
C020403E.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.
*1: With communication I/O, the same I/O points can be accessed as word data (%WW) or bit data (%WB).
■ 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).”
C030001E.EPS
Figure Block Chart of Input Processing Common to All Regulatory Control Blocks
BAD1
Q01 RV1
CPV
BADn Overshoot
Qn RVn
Calculation
IN No Conversion RV
Processing
C030002E.EPS
Q01 RV1
Qn No RVn
Conversion
Calculation
IN RV
Processing
C030003E.EPS
● 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.
● 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.
SEE ALSO
For more information about input processing for sequence connection, see a chapter C3.7, “Input
Processing for Sequence Connection.”
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.”
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 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.
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).”
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).”
SEE ALSO
For details on Input Signal Conversion of Pulse Count Input Block (PTC), see a chapter D1.32, “Pulse
Count Input Block (PTC).”
■ 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
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
8-Channel Current Input;
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
Thermocouple Measured
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
Thermocouple Measured
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) –
4-Channel Current Input 1 to 4 Current Input 4 to 20 mA 0 to 100%
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.
Type IOM Model Terminal No. I/O Type Input Range Raw Data
*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
Calculated Output
Enlarged View
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.
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.
+
/ • Scale PV
-
Pulse Input +
Module
C030104E.EPS
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
+
/ • Scale PV
-
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
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.
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.
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.
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
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.”
● 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.
The default setting is 0.000.
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).
■ 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.
■ 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.
Yn=(1-) • X + • Yn-1
: Filter coefficient
X: Input value
Yn: Current filtering data
Yn-1: Previous filtering data
=0.5
Calculation interval
0
0 1 2 3 4 5 6 7 Time (sec)
C030201E.EPS
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)
• Digital Filter Coefficient 2: 0.75
(When the digital filter coefficient is 0.75 and scan period is 1 second, the time con-
stant is 3 seconds)
• Digital Filter Coefficient 3: 0.875
(When the digital filter coefficient is 0.875 and scan period is 1 second, the time
constant is 7 seconds)
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
Digital Filter Coefficient 2 is used.
• 3
Digital Filter Coefficient 3 is used.
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.
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).”
Ts
SUMn = X • +SUMn-1
Tk C030301E.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.
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 %.
■ 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
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.
■ 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.
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.
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.
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).
● 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.
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.”
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.”
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
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
RV and RV1 BAD RV priority
4
RV1 QST No transmission
RV and RV1 BAD RV priority
5
RV or RV1 QST No transmission
6 RV or RV1 BAD RV priority
C030602E.EPS
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.
SEE ALSO
For more information about the behavior of AVE block when input error is detected, see a chapter D2.7,
“Averaging Blocks (AVE).”
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.
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).”
CAL
IN
Condition testing RV
CPV
Q01 CAL
Condition testing RV1 CPV1
Logic
operation
Qn CAL
Condition testing RVn CPVn
C030701E.EPS
SEE ALSO
For the condition specification on the I/O connection information, see a chapter D3.3, “Logic Chart Block
(LC64).”
■ 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).”
AUT/CAS/RCAS/PRD
Preset manipulated output
AUT/CAS/RCAS/ROUT/PRD
SV MAN/ MH ML
TRK MAN TRK
OUT
RMV MVrb Output signal
Readback value from conversion
output destination
Auxiliary
TIN output SUB
Output
module
C040001E.EPS
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).
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 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.
● 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 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).”
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
C040003E.EPS
Calculation OUT
CPV Output signal conversion
processing
C040004E.EPS
Figure Block Diagram of Output Processing Common to the Logic Operation Blocks (*1) £
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 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.
● 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.
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.”
■ 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):
Data in an engineering unit and within the MV range.
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.
The following figure shows the operation of the High/Low-limit Expansion function:
MV
MV Unlimited MV
MH
ML
Time
Mode
AUT MAN AUT
Alarm
NR MHI NR
C040101E.EPS
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.”
■ 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-.
The restriction of the direction of changes in clamped output can be set with the Function
Block Detail Builder.
• Limit output in direction when clamped:
Selectable from “Yes” and “No.”
Default is “Yes.”
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
CAS
AUT
IN OUT
Not output
clamp state RATIO
Output
IN high/low limit
AUT CAS
IN OUT
C040303E.EPS
Figure An Example of Connecting to the Input Terminal of a Ratio Set Block (RATIO)
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
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
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
Turn off the “limit output in direction when clamped” at the upstream control block can avoid
this state.
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.
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.
■ 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).
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.”
Default is “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).
The output tracking can be defined on the Function Block Detail Builder.
• Output Value Tracking: Selectable from “Yes” or “No.”
Default is “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.
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.
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.
PID
MSH
OUT
MSL
SET
PID CSV
Data value
SH
Output range tracking SL
C040601E.EPS
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 %.
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
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
FIC100
MAN
NR
OPN 100.0
High output limit index
Low output limit index
CLS 0.0
Prohibit
C040701E.EPS
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.
● No-Conversion Output
The manipulated output value (MV) resulted from the control-calculation process is No-
Conversion output.
● No-Conversion Outputs
The calculated output value (CPV) resulted from the control-calculation process is no-
conversion output.
● 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
manipulated output value (MV).
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).”
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).”
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).”
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).”
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).”
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:
Actual
output
Mf
100 %
0% 100 %
MV
Ms
C040801E.EPS
50 100 (%)
MV
C040802E.EPS
Figure Relationship between the Manipulated Output Value and Output Current
: available
Blank: not available
MV
Tout=Pf •
100 C040804E.EPS
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.
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.).
Default is 0.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.).
Default is 0.00 sec.
■ 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 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.
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
AUT LOCAL
Output Pulse width
MV OUT
velocity output
MAN limiter conversion REM
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.
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)
(a) When moving 50% or less of the full span (b) When moving 50% or above of the full span
C040809E.EPS
1
OUT= • (MV-BIAS)
GAIN C040810E.EPS
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)
TIP
In bitwise logic operation blocks, CPV is displayed in 8 digits hexadecimal.
• 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.
PV-SL
Output value= •100.0
SH-SL C040902E.EPS
PV
Output value= •100.0
SH-SL C040903E.EPS
MV-MSL
Output value= •100.0
MSH-MSL C040904E.EPS
MV
Output value= •100.0
MSH-MSL C040905E.EPS
: Allowed
Blank: Not allowed
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
the Function Block Detail Builder.
• 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.”
■ 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 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.
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
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 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.
■ 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).”
Function
block
Alarm
setpoint values
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
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
The alarm check can be executed among the detection functions varies by the function
block.
SEE ALSO
For more information about alarm check specific to PI-Blend block, see D1.12, “Blending PI Controller
Block (PI-BLEND).”
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).”
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).”
SEE ALSO
For more information about alarm check of VELLIM block, see D1.23, “Velocity Limiter Block (VELLIM).”
SEE ALSO
For more information about alarm check of Switch Instrument blocks, see D3.4, “ Switch Instrument
Block.”
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 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
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.”
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.
■ 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.
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.
■ 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
Time
HH
LL C050301E.EPS
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.”
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.
This alarm hysteresis value is also used for the input high and low limit alarm check.
PV
PH
HYS
Alarm activation conditions
PV PH
PV
PL
Time
HI
LO C050401E.EPS
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.
This alarm hysteresis value is also used for the high-high limit/low-low limit alarm check.
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
VL
VL
C050501E.EPS
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.
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.
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.
DV
DLe
HYS
Alarm activation conditions
DV DLe
DV
DLe
Time
Alarm restoration conditions
0
DVDLeHYS
DVDLeHYS
HYS
DLe
DV
DV C050601E.EPS
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.
DL
deviation deviation
SV
check filter r check
DLe
PV DV PID
C050602E.EPS
KSV • TSVs
r(s) • SV(s)
1TSVs C050603E.EPS
SV DLe
DV
DL
DLe
0 t
DLe
DL
C050604E.EPS
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).
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).
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.
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.
The reaction is the same as described above when the output fail alarm activates.
■ 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.
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.
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.
■ 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”.
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.”
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.
■ 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
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.”
Alarm condition
Acknowledgment Acknowledgment
Flashing status
C051502E.EPS
Alarm condition
Acknowledgment
Flashing status
C051503E.EPS
Alarm condition
Flashing status
C051504E.EPS
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.”
■ 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.
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.”
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.”
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.”
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
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.
SEE ALSO
For the over transition block mode, refer to C6.1.3, “Block Mode Transition.”
SEE ALSO
For the mode transition conditions, see a chapter C6.1.5, “Block Mode Transition Condition.”
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)
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)
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))
SEE ALSO
For block mode transition conditions, see a chapter C6.1.5, “Block Mode Transition Condition.”
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)
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)
Compound block modes established when the initialization manual condition is
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:
Display on the operation and monitoring function: RCAS IMAN
Block mode: IMAN (TRK (RCAS))
• 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.”
SEE ALSO
For the block mode transition conditions, see a chapter C6.1.5, “Block Mode Transition Condition.”
Example)
When the initialization manual condition is satisfied during the operation in the com-
puter backup mode (AUT mode) and in the RCAS mode:
Display on the operation and monitoring function: RCAS IMAN
Block mode: IMAN (AUT (RCAS))
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:
Display on the operation and monitoring function: RCAS IMAN
Block mode: IMAN (TRK (AUT (RCAS))
O/S command
O/S mode Normal mode (*1)
MAN command
MAN PRD
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 satisfied
TSW TSW
ON OFF
IMAN recovered
IMAN (TRK) mode (*2)
IMAN IMAN
(TRK (MAN) ) (TRK (PRD) )
C060105E.EPS
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.”
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.
MAN/AUT command
RCAS RCAS RCAS RCAS
CAS/PRD command
command command command command
MAN fallback
MAN PRD AUT CAS
command command command command
MAN/AUT command
ROUT ROUT ROUT ROUT
CAS/PRD command
command command command command
MAN fallback
CMP recovered
ROUT
CMP failure CMP failure
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.
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))
C060107E.EPS
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) AUT
? IMAN condition establish
IMAN (AUT)
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)
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.”
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.
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.
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 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 default is “No.”
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.
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.”
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.
■ 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
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.
Symbol Name Description
C060301E.EPS
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
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.
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.”
■ 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)
Symbol Name Description
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.
Symbol Name Description
C060401E.EPS
■ 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.
● 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.
■ 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.
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
● 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.
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.
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)
Time
......
Other process
Enlarged
b b Control drawing
1 2 3 4 5 Function block
C070101E.EPS
TIP
Each function block is executed asynchronously among the plural FCSes.
*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
C070102E.EPS
*2: £ The medium-speed processing function is available only for KFCS2, KFCS, LFCS2 or LFCS.
TIP
Each function block is executed asynchronously among the plural FCSes.
● 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
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
C070103E.EPS
Processor Unit
Function block
Local Node
Refresh Periodically(*2)
Remote Node
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.
Processor Unit
Function blocks
C070119E.EPS
Processor Unit
C070106E.EPS
Processor unit
C070107E.EPS
Processor Unit
Local Node
Refresh Periodically(*2)
Remote Node
C070108E.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 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.
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
Local Node
Refresh Periodically(*2)
Remote Node
C070110E.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 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.
*1: The pulse-width output between IOM and field devices behaves differently, the output timing is controlled in the output
module.
Processor Unit
C070120E.EPS
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
C070121E.EPS
● 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.
Time
High-speed
ABC ABC ABC AB
processing
Enlarged
b b Control drawing
Time
High-speed
ABC ABC ABC AB
processing
Enlarged
b b Control drawing
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.
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.
Time
Enlarged
b b Control drawing
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.
Time
High-speed
ABC ABC ABC AB
processing
Enlarged
b b Control drawing
MV
Control
period
Scan period
Time
C070116E.EPS
MV
Control
period
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.
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.
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.
■ 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
See a chapter C7.1.1, “Scan Period” for the scan period.
*1: £ The medium-speed scan setting is available only for KFCS2, KFCS, LFCS2 and LFCS.
SEE ALSO
See a chapter C7.1.2, “Order of Process Execution” for the order of process execution.
SEE ALSO
See a chapter C7.1.3, “Timing of Process I/O” for the process input/output timing.
Time
C070301E.EPS
The one-shot execution is used when a calculation block is invoked from a sequence table
block.
*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.
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.
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.
*1: £ The medium-speed scan setting is available only for KFCS2, KFCS, LFCS2 and LFCS.
● 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
See a chapter C7.1.1, “Scan Period” for the scan period.
● 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
See a chapter C7.1.1, “Scan Period” for the scan period.
*1: £ The medium-speed scan setting is available only for KFCS2, KFCS, LFCS2 and LFCS.
SEE ALSO
See a chapter C7.1.2, “Order of Process Execution” for the order of process execution.
SEE ALSO
See a chapter C7.1.3, “Timing of Process I/O” for the process input/output timing.
Time
C070201E.EPS
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.
When the periodic execution (T) is selected for execution timing, set a scan period in the
Function Block Detail Builder.
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.
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.
The control phase can be set in the Function Block Detail Builder.
• Control phase: Set a value between 0 and 15 seconds.
Default is 0 second.
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).”
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
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).
Faceplate blocks
SFC blocks
Options
D010001E.EPS
*1: ¡ £ The valve pattern monitor and the off-site block can only be used for the CS 3000.
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
SUB
D010101E.EPS
● Input Processing
Receives a signal from the input terminal and outputs a process variable (PV).
● Output Processing
Reads the manipulated output value (MV) and outputs the result of control computation
processing to the output terminal as an output signal.
● Alarm Processing
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.
■ Controller Blocks
The table below shows a list of controller blocks:
Table Controller Blocks
Block type Code Name
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
■ Alarm Block
The table below shows the alarm block:
Table Alarm Block
Block type Code Name
Alarm ALM-R Representative Alarm Block
D010109E.EPS
■ YS Blocks
The table below shows the YS blocks:
Table YS Blocks
■ 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.”
● 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:
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
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-
lated output value (MV).
• MV Engineering Unit Symbol:
Consists of six or less standard-width characters or three double-width characters.
The default is “%.”
• MV Range:
High and low limits.
Numerical values of seven digits or less, where the sign and decimal point occupy one
digit each.
The default is “100.0” for the upper limit and “0.0” for the lower limit.
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.”
B: No conversion
R: Square root conversion
: Exists
Blank: Not exist
*1: Display the sum of YS Instrument.
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
S3: 3-position status output
P2: 2-position pulsive output
P3: 3-position pulsive output
S2b: 2-position status output (BSETU-2/3 only)
S3b: 3-position status output (BSETU-2/3 only)
S2s: 2-position status output through switch instrument (BSETU-2/3 only)
S3s: 3-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].
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
S3: 3-position status output
P2: 2-position pulsive output
P3: 3-position pulsive output
S2b: 2-position status output (BSETU-2/3 only)
S3b: 3-position status output (BSETU-2/3 only)
S2s: 2-position status output through switch instrument (BSETU-2/3 only)
S3s: 3-position status output through switch instrument (BSETU-2/3 only)
Sb: Subsystem 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.
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
NPLS (*1)
BSETU-2 BDV+
BDV-
LEAK
BSETU-3 BEND
BPRE
: Available
Blank: Not 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.
SLCD
SLPC
SLMC
SMST-111
SMST-121
SMRT
END
SBSD PRE
LERK
END
SLBC PRE
LERK
SLCC HDV
STLD
D010120E.EPS
: Available
Blank: Not available
: Valid
-: Invalid
: For MLD-SW, CAS mode can be specified instead of AUT mode.
: Valid
-: Invalid
Input
IN PV OUT
processing
(PV, PV)
SUB
D010201E.EPS
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 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).
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.”
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.”
-
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)
: 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).
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the PVI-DV 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.”
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.
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.”
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.”
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
PID control computation.
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
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).”
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
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
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
| 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:
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
● 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
● 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.
T
MVn=MVn0+ (RLV1-RLV2-MV'n-1)
TI D010409E.EPS
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
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.
RLV1
D010411E.EPS
RL1
IN OUT
PID
IN1
IN2 IN
IN OUT
PID
RL1
D010412E.EPS
Figure Reset Limit Function Used for Auto-Selection via Auto-Selector Blocks (AS-H)
IN
CALCU
OUT
RL2 SET
RL1 IN
D010413E.EPS
Figure Reset Limit Function Used in Feedforward Control (Base Load Control)
Output (MVn)
HYS HYS
MVn0
En
DB DB
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:
Engineering unit data between 0 and the PV scale span range limit.
The default is the value equivalent to 1.0 % of the PV scale span.
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.
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.”
The default is “No.”
CVn=PVn+CK(VN+CB)
VN
+
+
CB
CK
+
PVn CVn MV
PV PID control computation
+
D010415E.EPS
PID
IN OUT
VN
DLAY-C
D010416E.EPS
MVn=MVn0+CK(VN+CB)
VN
+
+
CB
CK
+
PVn PID control MVn0 MVn
PV
computation +
D010417E.EPS
IN OUT
CALCU
PID
IN OUT
VN
D010418E.EPS
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.
Set from the supervisory computer Input from the SET terminal
RSV CSV
AUT/MAN
RCAS CAS
SV
Setpoint value
Control
computation
D010419E.EPS
The action of the setpoint value pushback varies in accordance with the block mode of the
function block.
JO1 SET
PID
OUT SET
PID FOUT
JO8
SET
PID
D010420E.EPS
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)
AUT
? Initialization manual condition is established
IMAN (AUT)
? Initialization manual condition vanishes
AUT
AUTAMAN
IMAN (CAS)AIMAN (MAN)
CASAAUT
IMAN (CAS)AIMAN (AUT)
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).
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).
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
mode is shown as follows:
AUT
? ROUT command
AUT (ROUT) Transient state mode
? After one scan period
MAN (ROUT) Computer backup mode (When BSW=ON)
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.”
MSH-MSL
MV=MSH- • (CSV-SL)
SH-SL D010423E.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)
MSH-MSL D010424E.EPS
CSV=RSV=SV
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
MSH-MSL D010426E.EPS
CSV=RSV=SV
SUB
D010501E.EPS
The table below shows the connection methods and connected destinations of the I/O
terminals of PID Controller Block (PID):
Table Connection Methods and Connected destinations of the I/O Terminals of PID Controller
Block (PID)
Connection method Connection destination
I/O terminal Data Data Terminal Process Software Function
reference setting connection I/O I/O block
IN Measurement input
SET Setting input
OUT Manipulated output
SUB Auxiliary 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
: 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).
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the PID 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.”
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
PID control computation.
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.
D010503E.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.”
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)
100 1 dE(t)
MV(t)= E(t)+ E(t)dt+TD
PB TI dt D010506E.EPS
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
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).
PI-D En PV En
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.
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
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).
T TD
MVn=Kp • Ks PVn+ En+ (PVn)
TI T D010512E.EPS
T TD
MVn=Kp • Ks En+ En+ (PVn)
TI T D010513E.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.
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.”
SUB
D010601E.EPS
The table below shows the connection methods and connected destinations of the I/O
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)
Connection method Connection destination
I/O terminal Data Data Terminal Process Software Function
reference setting connection I/O I/O block
IN Measurement input
SET Setting input
OUT Manipulated output
SUB Auxiliary 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
D010602E.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).
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the PI-HLD 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.”
Deadband action Adjusts the manipulated output change (MV) to “0” when the deviation is within the
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
PID control computation.
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.
D010603E.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.”
MV T (control period)
Output hold
PI computation
output
Time
TC TC
(control time)
TS (sampling period) TS
D010605E.EPS
Set the sampling period and control time in advance, in accordance with the following
principle:
TS
Control time: TC=
10 D010606E.EPS
Tn
TS
5 D010607E.EPS
The sampling period and control time are considered as set parameters, and their setting
can be changed during operation.
T
MVn=Kp • Ks PVn+ • En
TI D010608E.EPS
En=PVn-SVn
100
Kp=
PB D010609E.EPS
MSH-MSL
Ks=
SH-SL D010610E.EPS
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.
T
(control period)
MV
Output hold
PI computation output
Time
TC TC TC
(control time) D010611E.EPS
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.
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.”
SUB
D010701E.EPS
Figure Function Block Diagram of PID Controller Block with Batch Switch (PID-BSW)
: 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).
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.”
• 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.”
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.”
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:
PV
MV
Time
Figure Example of Control Action (Reverse Action) Performed by PID Controller Block with
Batch Switch (PID-BSW)
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.
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
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.”
CAS (VN)
CSV
AUT
SV
MAN
RSV
RCAS
MAN
Control CAS/AUT
Input Output
IN PV computation MV OUT
processing processing
processing
ROUT
SUB
D010801E.EPS
The table below shows the connection methods and connected destinations of the I/O
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):
Connection method Connection destination
I/O terminal Data Data Terminal Process Software Function
reference setting connection I/O I/O block
IN Measurement input
SET Setting input
OUT Manipulated output
SUB Auxiliary output
Compensation
BIN
input
INT Interlock SW input
D010802E.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).
The ONOFF block performs input processing, control computation processing, output
processing, and alarm processing.
The only processing timing available for the ONOFF 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.
*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 ONOFF 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.”
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.”
The figure below shows an example of the two-position ON/OFF control action:
Deviation (En)
ON/OFF hysteresis
0
Time
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.
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.”
CAS (VN)
CSV
AUT
SV
MAN
RSV
RCAS
MAN
Control CAS/AUT
Input Output
IN PV computation MV OUT
processing processing
processing
ROUT
SUB
D010901E.EPS
The table below shows the connection methods and connected destinations of the I/O
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):
Connection method Connection destination
I/O terminal Data Data Terminal Process Software Function
reference setting connection I/O I/O block
IN Measurement input
SET Setting input
OUT Manipulated output
SUB Auxiliary output
Compensation
BIN
input
INT Interlock SW input
D010902E.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).
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the ONOFF-G
block, see D1.1.3, “Input Processing, Output Processing, and Alarm Processing Possible for Each Regu-
latory 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.”
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.”
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.
(3)
+ (4)
(2) (5)
0
Time
Deviation (En)
- (1)
(6)
(3)
+ (4)
(2) (5)
0
Time
Deviation (En)
- (1)
(6)
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.
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
Regulatory Control Block.”
SUB
D011001E.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).
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
Regulatory Control Block.”
• 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.”
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
PID control computation.
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.
D011003E.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.”
T TD
MVn=Kp • Ks PVn+ En+ (PVn)
TI T
D011005E.EPS
ON
OFF
Time
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).
SEE ALSO
For a list of valid block modes of the PID-TP block, see chapter D1.1.4, “Valid Block Modes for Each
Regulatory Control Block.”
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):
SUB
D011101E.EPS
Figure Function Block Diagram of PD Controller Block with Manual Reset (PD-MR)
: 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).
The PD-MR block performs input processing, control computation processing, output
processing, and alarm processing.
The only processing timing available for the PD-MR 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.
*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 PD-MR 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.”
Prevents abrupt changes in the manipulated output value (MV) by initializing the balance
Balance action
term in the manipulated output computational expression.
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.
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.”
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
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.
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
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).
SEE ALSO
For a list of valid block modes of the PD-MR block, see chapter D1.1.4, “Valid Block Modes for Each
Regulatory Control Block.”
CAS (TSW)
CSV
AUT
SV
MAN
RSV
RCAS
MAN
Control CAS/AUT
Input Output
IN PV computation MV OUT
processing processing
processing
ROUT
SUB
D011201E.EPS
The table below shows the connection methods and connected destinations of the I/O
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)
Connection method Connection destination
I/O terminal Data Data Terminal Process Software Function
reference reference connection I/O I/O block
IN Measurement input
SET Setting input
OUT Manipulated output
SUB Auxiliary output
Tracking signal
TIN
input
TSI Tracking SW input
INT Interlock SW input
D011202E.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).
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the PI-BLEND
block, see D1.1.3, “Input Processing, Output Processing, and Alarm Processing Possible for Each Regu-
latory 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.”
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.”
DVRn
DVn= • TS
TK D011204E.EPS
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).
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
• 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.
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
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:
Time
0
MAN AUT
D011209E.EPS
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).
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
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.
SV
0
Deviation PV
| VL |
| DL |
D011213E.EPS
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.
SEE ALSO
For a list of valid block modes of the PI-BLEND block, see D1.1.4, “Valid Block Modes for Each Regula-
tory Control Block.”
The figure below shows a function block diagram of Self-Tuning PID Controller Block (PID-
STC):
SUB
D011301E.EPS
Estimated
process
model
PID Process
parameter characteristic
calculation estimation
P I D Response
monitoring
SV - PID PV
Process
controller MV
D011302E.EPS
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.
The table below shows the connection methods and connected destinations of the I/O
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)
Connection method Connection destination
I/O terminal Data Data Terminal Process Software Function
reference setting connection I/O I/O block
IN Measurement input
SET Setting input
OUT Manipulated output
SUB Auxiliary 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
D011303E.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).
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the PID-STC
block, see D1.1.3, “Input Processing, Output Processing, and Alarm Processing Possible for Each Regu-
latory 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.”
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).”
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
Regulatory Control Block.”
SEE ALSO
For the details of PID control algorithm, see a section “■ PID Control Computation” in D1.5, “PID Control-
ler Block (PID).”
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.
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.”
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.
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.”
STC function
STC operating
STC=-1 mode
STC=2 STC=3
STC=0, 1
PV and MV data
Yes
Estimation of
Auto-startup On-demand
process
processing processing
characteristics
No High estimation
accuracy
Yes
Operating mode
Calculation of
recovery
PID parameters
STC=0
Operating mode
STC=1
Setting of PID
parameters
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.
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).”
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).
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.
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
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
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.
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.
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
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.
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.
■ 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.
MV
PV
settling value
PV
95 %
Time
TR
TR=TP
PV
TP
Specific
oscillation cycle
Time
D011320E.EPS
NB
Time
D011321E.EPS
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
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
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
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).
The PID parameters (P, I, D) are limited within the range of the corresponding high/low
limits:
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).
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.
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).
MV
PV settling value
PV
Time
MV
PV
Time
D011325E.EPS
Figure Examples of Step Responses from Static System and Astatic System Processes
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.
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.
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).
Distillation
column Temperature TIC
FIC
Flowrate
Steam
D011327E.EPS
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).
TC 1
Raw material
TC 2
Cooling
jacket
Water
Reactor
Steam
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.
Intermediate
outflow volume
Inflow volume Pump F0
F1 Outflow volume
F
LIC FIC
Level
Tank
Re-circulated
D011329E.EPS
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.
14
Neutralizing
agent 12
pHC
10
Controlled fluid
pH 8
7
6
pH transmitter
4
0
MV (neutralizing agent)
D011330E.EPS
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.
LIC
Q1
Q1 inflow volume
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.
MV Step input
Time
PV
Temperature
Time
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.
Motor-operated
M
valve
D011333E.EPS
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.
Temperature
Temperature pattern
Time
TIC
Heat treatment
furnace
Fuel
D011335E.EPS
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.
Additional
Temperature raw material
input Batch end
SV
PV
Time
STC stop STC stop
D011336E.EPS
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).
PC FC
Pressure Flowrate
D011337E.EPS
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.
The following section shows the points to be noted when using Self-Tuning PID Controller
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
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.
TIN TSI
(TSW)
Output
MV OUT
processing
(MV, MV)
SUB
D011401E.EPS
The table below shows the connection methods and connected destinations of the I/O
terminals of the Manual Loader Block (MLD):
Table Connection Methods and Connected destinations of the I/O Terminals of Manual Loader
Block (MLD)
Connection method Connection destination
I/O terminal Data Data Terminal Process Software Function
reference setting connection I/O I/O block
OUT Manipulated output
SUB Auxiliary output
Tracking signal
TIN
input
TSI Tracking SW input
D011402E.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).
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.”
• For details on the output processing, see C4, “Output Processing.”
• For details on the alarm processing, see C5, “Alarm Processing-FCS.”
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.”
TIN TSI
(TSW)
Input Output
IN PV MV OUT
processing processing
SUB
D011501E.EPS
Figure Function Block Diagram of Manual Loader Block with Input Indicator (MLD-PVI)
The table below shows the connection methods and connected destinations of the I/O
terminals of the Manual Loader Block with Input Indicator (MLD-PVI):
Table Connection Methods and Connected destinations of the I/O Terminals of Manual Loader
Block with Input Indicator (MLD-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
OUT Manipulated output
SUB Auxiliary output
Tracking signal
TIN
input
TSI Tracking SW input
D011502E.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).
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the MLD-PVI
block, see D1.1.3, “Input Processing, Output Processing, and Alarm Processing Possible for Each Regu-
latory 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.”
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.”
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)
(TSW)
CSV
GAI • CSV+BIAS
SV
SUB D011601E.EPS
Figure Function Block Diagram of Manual Loader Block with Auto/Man SW (MLD-SW)
: 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).
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.”
• For details on the output processing, see C4, “Output Processing.”
• For details on the alarm processing, see C5, “Alarm Processing-FCS.”
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
SV-BIAS
CSV=
GAIN D011605E.EPS
The setpoint value pushback action does not take place if GAIN is 0.
SSH-SSL
SV= • (MV-MSL)+SSL
MSH-MSL D011606E.EPS
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.
PV MV
CAS
PID (AUT) MAN
Output pushback
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)
SSH-SSL
SV= • (MV-MSL)+SSL
MSH-MSL
D011609E.EPS
BIAS=SV-GAIN • CSV
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.
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:
Scan period
Time
D011610.EPS
The setpoint value ramp action takes place only when “No” is defined for the bias tracking.
The parameter of the setpoint value ramp action:
• Ramp constant (RP):
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.
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.
AUT
? Initialization manual condition establishes
IMAN (AUT)
? Initialization manual condition vanishes
AUT
The following example shows when the MAN fallback condition is established:
AUTAMAN
IMAN (AUT)AIMAN (MAN)
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.”
SV CSV RMV
TT FV
FB
(BPSW)
Figure Function Block Diagram of the Motor Control Blocks (MC-2, MC-3)
: 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).
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.”
• 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.”
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
Each Regulatory Control Block.”
SEE ALSO
For the FV overshoot, see a chapter C3.4, “PV/FV/CPV Overshoot.”
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.
The default setting is 0.0.
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.”
*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.
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.
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.
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.
Use the Function Block Detail Builder to define the answerback check.
• Answerback Check: Select “No,” “Both Sides,” “Open,”
“Close.”
The default is “No.”
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.
AUT
? Initialization manual condition establishes
IMAN (AUT)
? Initialization manual condition vanishes
AUT
AUTAMAN
IMAN (CAS)AIMAN (MAN)
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.
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) and a
remote mode (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
(ROUT).
3. If the computer recovers while the function block is in the computer backup mode, the
block mode changes to remote output (ROUT).
An example when the automatic (AUT) mode has been specified for the computer backup
mode is shown as follows:
ROUT
? Computer fails
AUT (ROUT)
? Computer recovers
ROUT
An example when the manual (MAN) mode has been specified for the computer backup
mode is shown as follows:
AUT
? ROUT command
AUT (ROUT) Transient state mode
? After one scan period
MAN (ROUT) Computer backup mode (When BSW=ON)
■ 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.
*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).”
The above actions take place commonly when the output status changes from stop to start,
regardless the cancellation of simulation mode.
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.
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
The output signal conversion types and output action directions are described.
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 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.”
*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.
0 2 0
MV
ON
Direct action Contact output status OFF OFF
(n)
ON ON
Reverse action Contact output status OFF
(n)
D011712E.EPS
In the 2-position status output, the state of MV=1 is the same as the state of MV=2.
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
*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.
0 1 2
MV
ON
Output status of contact 1 OFF
(n)
Direct ON
action
Output status of contact 2 OFF
(n+1)
ON
Output status of contact 1 OFF
(n)
Reversed ON
action
Output status of contact 2 OFF
(n+1)
ON
Output status of contact 1 OFF
Reversed
(n)
connection ON
Direct Action
Output status of contact 2 OFF
(n+1)
ON
Output status of contact 1 OFF
Reversed
(n)
connection ON
Reversed Action
Output status of contact 2 OFF
(n+1)
D011714E.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.
0 2
MV
ON
Output status of contact 1 OFF OFF
(n)
ON
Output status of contact 2 OFF
(n+1)
D011716E.EPS
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.
*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.
0 1 2
MV
ON
Output status of contact 1 OFF OFF
(n)
ON
Output status of contact 2 OFF
(n+1)
ON
Output status of contact 3 OFF OFF
(n+2)
D011718E.EPS
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.
| SV |
Tout=Tf •
100 D011720E.EPS
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.
Default is 0 second.
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)
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)
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)
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)
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.
The answerback tracking function is defined in the function block detail definition builder.
• Answerback Tracking: Select either “Yes” or “No.”
Default is “Yes.”
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.
2
PV
0
Block
AUT MAN
mode
A
Block N
NR ANCK NR C NR
status
K
Alarm
NR INT NR
status
When a 3-position status output encounters the answerback error triggered fallback, its
behavior is shown in the following illustrate.
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
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.”
FV
PH
HYS
Conditions generating an alarm
FV PH
FV
PL
Time
HI
LO
D011728E.EPS
Figure Actions of the Feedback Input High and Low Limit Alarm Check
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.
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).”
CAS (TSW)
CSV
AUT
SV
MAN
RSV
RCAS
ROUT
SUB D011801E.EPS
Control computation
Ratio
SV
tracking
Setpoint value
ramp action
MAN
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
: 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).
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
Regulatory Control Block.”
• 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.”
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).
● Ratio Gain
▼ Ratio Gain
Use the Function Block Detail Builder to set the ratio gain:
• Ratio Gain:
Specify a numeric value of 7 digits or less, where the sign and decimal point occupy
one digit each.
The default is 1.0.
r=0 to 0.3
F2=0 to 30 m3/h
PID
D011806E.EPS
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= (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:
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.
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).
MSH: MV scale high limit
MSL: MV scale low limit
Set from the supervisory computer Input from the SET terminal
RSV CSV
AUT/MAN
RCAS CAS
SV
Setpoint value
Control
computation
D011810E.EPS
The action of the setpoint value pushback varies in accordance with the block mode of the
function block.
● 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
Note: The statuses of MAN, AUT and CAS include remote backup modes, such as AUT (ROUT) and AUT (RCAS).
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).
SV
Scan period
D011813E.EPS
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.
The default is the SV scale span.
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).
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
changes to that mode only when the initialization condition vanishes.
AUT
? Initialization manual condition establishes
IMAN (AUT)
? Initialization manual condition vanishes
AUT
AUTAMAN
IMAN (CAS)AIMAN (MAN)
CASAAUT
IMAN (CAS)AIMAN (AUT)
Use the Function Block Detail Builder to enable or disable the AUT fallback function.
• AUT Fallback: Select “Yes” or “No.”
The default is “No.”
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).
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
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 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).
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
An example when the manual (MAN) mode has been specified for the computer backup
mode is shown as follows:
AUT
? ROUT command
AUT (ROUT) Transient state mode
? After one scan period
MAN (ROUT) Computer backup mode (When BSW=ON)
SEE ALSO
For a list of valid block modes of the RATIO block, see chapter D1.1.4, “Valid Block Modes for Each
Regulatory Control Block.”
INT
SV
Control computation
(program setting)
CAS
AUT Output
CALC MV OUT
processing
MAN
(Annunciator output)
SUB D011901E.EPS
The table below shows the connection methods and connected destinations of the I/O
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)
Connection method Connection destination
I/O terminal Data Data Terminal Process Software Function
reference setting connection I/O I/O block
OUT Manipulated output
SUB Annunciator output
INT Interlock SW input
D011902E.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).
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.”
• 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.”
● 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).
● 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.
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
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.
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 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.
The default is “1.”
• Bumpless end zone (ZEND): Select a value between 1 and 13.
The default is “1.”
Present value of
output destination ZEND
ZSTR
0 Fast-forwarding
along the time axis SV
D011906E.EPS
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.
The block returns to the original mode when the initialization manual condition vanishes.
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.
AUT
? Initialization manual condition establishes
IMAN (AUT)
? Initialization manual condition vanishes
AUT
Example) AUTAMAN
IMAN (CAS)AIMAN (MAN)
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
Regulatory Control Block.”
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).”
SEE ALSO
For details on the integration, see a chapter C3.3, “Integration.”
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
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.
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.
The default is the manipulated output value (MV) scale’s low limit.
• Ramp Up time (TU):
Set a value between 0 and 10000 seconds.
The default is 0 second.
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.
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.
The default is the manipulated output value (MV) scale’s low limit.
• Ramp Down time (TD):
Set a value between 0 and 10000 seconds.
The default is 0 second.
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.
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.
The default is 0 second.
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
Other than by the emergency stop command (SW=4), emergency stop can also be trig-
gered via the emergency stop switch (EMSW=1).
(M)
(F)
(D)
6
RSET (N)
(H)
(J)
11 9 8
(L) (I) (F)
(B)
STRT NCNT
Legend
ZONE
Block status
D012003E.EPS
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.
■ 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.
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.”
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
MV
100 %
50 %
0 %
BSETU-2/ ZONE 0 1 3 9 3 5 7
BSETU-3
Figure Example of Batch Operation when Only Switch Instrument 2 is in Cascade (CAS) Mode
MV
100 %
50 %
0%
BSETU-2/ ZONE 0 1 9 3 9 3 7
BSETU-3
Figure Example of Batch Operation when Only Switch Instrument 1 is in Cascade (CAS) Mode
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 block returns to the original mode when the initialization manual condition vanishes.
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.
AUT
? Initialization manual condition establishes
IMAN (AUT)
? Initialization manual condition vanishes
AUT
AUTAMAN
IMAN (CAS)AIMAN (MAN)
IN BSETU-2 OUT
D012010E.EPS
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
IN BSETU-2 OUT
OUT2
D012013E.EPS
The following table shows the relationship between the manipulated output value (MV) in
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
IN OUT
BSETU-2
IN CSV OUT
SIO-11
D012016E.EPS
The following table shows the relationship between the manipulated output value (MV) in
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.
OUT
IN
BSETU-2 OUT2
D012018E.EPS
The following table shows the relationship between the manipulated output value (MV) in
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.
The pre-batch alarm can be set with the Function Block Detail Builder.
• Pre-batch alarm: Select from “enabled” and “disabled”
Default is “disabled.”
The batch end alarm can be set with the Function Block Detail Builder.
• Batch end alarm: Select from “enabled” and “disabled”
Default is “disabled.”
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).
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.
ZONE SW EMSW
SUM
INT D012101E.EPS
IN BSETU-2 OUT
D012102E.EPS
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
SET SET
D012104E.EPS
D012105E.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).
*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.
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
Each Regulatory Control Block.”
• 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.”
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).”
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
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
● 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.
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
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.
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
Regulatory Control Block.”
ZONE SW EMSW
IN
IN2 AUT
Input Output
PV Batch MV OUT
processing processing
IN3 set pattern
MAN OUT2
IN4
SUM0
SUM
INT D012201E.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).
*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.
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
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
Regulatory Control Block.”
• 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.”
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).”
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
Regulatory Control Block.”
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
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.”
When the weight-totalizing conversion is bypassed, the absolute integrator value (SUM0) is
not to be updated, the previous good value is kept.
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 default setting is 1000.
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
When the SUM conversion is bypassed, the integrator value (SUM) is not to be updated,
the previous good value is kept.
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.”
In these cases, the flow rate value (PV) is not to be updated, the previous good value is
kept.
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
t2
● 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.
● 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.
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
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).”
SET INT
CAS
CSV
AUT
SV
MAN
RSV
RCAS
MAN
ROUT
SUB
D012301E.EPS
The table below shows the connection methods and connected destinations of the I/O
terminals of the Velocity Limiter Block (VELLIM):
Table Connection Methods and Connected Destinations of I/O Terminals of Velocity Limiter Block
(VELLIM):
Connection method Connection destination
I/O terminal Data Data Terminal Process Software Function
reference setting connection I/O I/O block
SET Setting input
OUT Manipulated output
SUB Auxiliary output
INT Interlock SW input
D012302E.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).
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.”
• For details on the output processing, see chapter C4, “Output Processing.”
• For details on the alarm processing, see chapter C5, “Alarm Processing-FCS.”
D012304E.EPS
● 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
SSH-SSL D012305E.EPS
MVn = MVc
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 from the supervisory computer Input from the SET terminal
RSV CSV
AUT/MAN
RCAS CAS
SV
Setpoint value
Control
computation
D012306E.EPS
The action of the setpoint value pushback varies in accordance with the block mode of the
function block.
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
ROUT
RMV
D012307E.EPS
Use the Function Block Detail Builder to set the output pushback.
• Output pushback: Select “Yes” or “No.”
The default is “Yes.”
PV MV
PID MAN
Output pushback
Output tracking
SV
MV
CAS
VELLIM AUT/MAN
Output tracking
SV
PV MV
PID
D012308E.EPS
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.
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.
AUT
? Initialization manual condition establishes
IMAN (AUT)
? Initialization manual condition vanishes
AUT
AUTAMAN
IMAN (CAS)AIMAN (MAN)
CASAAUT
IMAN (CAS)AIMAN (AUT)
Use the Function Block Detail Builder to set whether or not to use the AUT fallback.
• AUT Fallback: Select “Yes” or “No.”
The default is “No.”
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
become invalid (BAD) or communication error (NCOM).
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
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) 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).
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
An example when the manual (MAN) mode has been specified for the computer backup
mode is shown as follows:
AUT
? ROUT command
AUT (ROUT) Transient state mode
? After one scan period
MAN (ROUT) Computer backup mode (When BSW=ON)
DV=MVs-SV
SSHSSL
MVS = • (MVMSL)SSL
MSHMSL D012309E.EPS
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)
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
When specifying percentage data, add % after the numeric value.
The default is 1.0 %.
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.”
0
1
2
IN1 RV1 PV OUT
3
Automatic 4
IN2 RV2 signal
selection
SW SEL
IN3 RV3
Selected
number
D012401E.EPS
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
: 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).
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.”
SEE ALSO
• For the types of output processing and alarm processing possible for the SS-H/M/L blocks, see D1.1.3,
“Input Processing, Output Processing, and Alarm Processing Possible for Each Regulatory Control
Block.”
• For details on the output processing, see C4, “Output Processing.”
• For details on the alarm processing, see C5, “Alarm Processing-FCS.”
PV pushback Causes the non-selected input signal values to agree with the selected signal value (PV).
D012404E.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.
RV2 RV1 is selected.
RV3 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
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
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).
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
Regulatory Control Block.”
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
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
: Connection allowed
Blank: Connection not allowed
: 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.
SEE ALSO
• For the types of output processing and alarm processing possible for the AS-H/M/L blocks, see D1.1.3,
“Input Processing, Output Processing, and Alarm Processing Possible for Each Regulatory Control
Block.”
• For details on the output processing, see C4, “Output Processing.”
• For details on the alarm processing, see C5, “Alarm Processing-FCS.”
• 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
RV1 RV2 is selected.
RV2 RV1 is selected.
RV3 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.”
D012506E.EPS
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
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
MSH-MSL D012509E.EPS
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.”
Output tracking
PV MV PV pushback
PID
PV
SS-H D012510E.EPS
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).
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.
AUT
? Initialization manual condition establishes
IMAN (AUT)
? Initialization manual condition vanishes
AUT
AUTAMAN
IMAN (CAS)AIMAN (MAN)
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
Regulatory Control Block.”
Deviation
check
1
IN1 RV1
Automatic
2 Input
signal PV OUT
processing
selection 3
IN2 RV2
SW SEL
Selected
number
D012601E.EPS
The table below shows the connection methods and connected destinations of the I/O
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):
Connection method Connection destination
I/O terminal Data Data Terminal Process Software Function
reference setting connection I/O I/O block
IN1 Input signal 1
IN2 Input signal 2
OUT Manipulated output
D012602E.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).
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the SS-DUAL
block, see chapter D1.1.3, “Input Processing, Output Processing, and Alarm Processing Possible for Each
Regulatory Control Block.”
• 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.”
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.
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).
SEE ALSO
For a list of valid block modes of the SS-DUAL block, see chapter D1.1.4, “Valid Block Modes for Each
Regulatory Control Block.”
MV1 J01
MV2 J02
SET CSV SV Output
computation
MV8 J08
D012701E.EPS
The setpoint value (SV) of the Cascade Signal Distributor Block (FOUT) can be used for
data reference but not for data setting.
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
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).
: Connection allowed
Blank: Connection not allowed
SET terminal can not be connected to the terminals of other station’s function block.
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.”
• For details on the output processing, see chapter C4, “Output Processing.”
MSHn-MSLn
MVn= • (SV-SSL)+MSLn
SSH-SSL D012705E.EPS
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.
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:
CSV=SV D012706E.EPS
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.”
MAN
FSW
(PV, PV, MV, MV)
SUB
D012801E.EPS
The table below shows the connection methods and connected destinations of the I/O
terminals of the Feedforward Signal Summing Block (FFSUM):
Table Connection Methods and Connected Destinations of I/O Terminals of Feedforward Signal
Summing Block (FFSUM)
Connection method Connection destination
I/O terminal Data Data Terminal Process Software Function
reference setting connection I/O I/O block
IN FB signal input
SET FF setting input
OUT Manipulated output
SUB Auxiliary output
Compensation
BIN
input
Tracking signal
TIN
input
TSI Tracking SW input
INT Interlock SW input
D012802E.EPS
: Connection allowed
Blank: Connection not allowed
: Connection allowed only when connecting to a switch block (SW-33, SW-91) or an inter-station data link block (ADL).
*1: ¡ £ The medium-speed scan period can only be used for the KFCS2, KFCS, LFCS2 and LFCS.
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.”
• For details on the output processing, see chapter C4, “Output Processing.”
• For details on the alarm processing, see chapter C5, “Alarm Processing-FCS.”
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 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.
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.
D012803E.EPS
Input
VN compensation
AUT/MAN CAS
CSV
+
+
CB
CK SV FSW
+
CV Signal MV
PV
+ addition
D012804E.EPS
● 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
SSH-SSL D012806E.EPS
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
When the feedforward switch (FSW) is turned OFF, the following computation is performed
to determine the BLn value.
BLn=MVrb-SVm-CVm’
CVn=PVn+CK (VN+CB)
VN
+
+
CB
CK
+
PVn CVn PID control MV
PV
+ computation
D012807E.EPS
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
manipulated output value (MV).
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).
CSV
AUT/MAN
CAS
SV
Setpoint value
Control
computation
D012808E.EPS
The action of the setpoint value pushback varies in accordance with the block mode of the
function block.
● 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
MSH-MSL D012809E.EPS
CVm=MVrb-SVm-BLn
MSH-MSL
SVm= • (SV-SSL)+MSL
SSH-SSL D012810E.EPS
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.”
AUT/MAN
SV
PV MV PV MV
PID FFSUM
CAS AUT/MAN
Output tracking
Output tracking SV
Output pushback PV MV
PID
D012811E.EPS
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).
BLn=MVrb-CVm-SVm
MSH-MSL
CVm= • (CV-SL)+MSL
SH-SL D012812E.EPS
MSH-MSL
SVm= • (SV-SSL)+MSL
SSH-SSL D012813E.EPS
CV=PV+CK • (VN+CB)
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
The default is the MV scale span.
The setting can be changed from operation and monitoring functions during operation.
In other words, any operation to change to the manual (MAN) mode becomes 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 initialization condition vanishes.
AUT
? Initialization manual condition establishes
IMAN (AUT)
? Initialization manual condition vanishes
AUT
AUTAMAN
IMAN (CAS)AIMAN (MAN)
CASAAUT
IMAN (CAS)AIMAN (AUT)
Use the Function Block Detail Builder to define whether or not to use the AUT fallback.
• AUT Fallback: Select “Yes” or “No.”
The default is “No.”
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
become invalid (BAD) or communication error (NCOM).
SEE ALSO
For a list of valid block modes of the FFSUM block, see a chapter D1.1.4, “Valid Block Modes for Each
Regulatory Control Block.”
(TSW)
VN
MAN
(MV, MV)
SUB
D012901E.EPS
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
: 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).
*1: ¡ £ The medium-speed scan period can only be used for the KFCS2, KFCS, LFCS2 and LFCS.
SEE ALSO
• For the types of output processing and alarm processing possible for the XCPL block, see chapter D1.1.3,
“Input Processing, Output Processing, and Alarm Processing Possible for Each Regulatory Control
Block.”
• For details on the output processing, see chapter C4, “Output Processing.”
• For details on the alarm processing, see chapter C5, “Alarm Processing-FCS.”
VN
+
+
CB
CK
+
MV
PV
+
D012905E.EPS
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
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).
● 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
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).
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.
The default is the MV scale span.
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).
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.
AUT
? Initialization manual condition establishes
IMAN (AUT)
? Initialization manual condition vanishes
AUT
AUTAMAN
IMAN (CAS)AIMAN (MAN)
SEE ALSO
For a list of valid block modes of the XCPL block, see a chapter D1.1.4, “Valid Block Modes for Each
Regulatory Control Block.”
0
1
Range
MV1 OUT1
CAS conversion
SET CSV
3
AUT SV
RSV
RCAS 2 Range
SW MV2 OUT2
conversion
D013001E.EPS
Data setting cannot be performed to the manipulated output values (MV1, MV2) of the
Control Signal Splitter Block (SPLIT).
The table below shows the connection methods and connected destinations of the I/O
terminals of the Control Signal Splitter Block (SPLIT):
Table Connection Methods and Connected Destinations of I/O Terminals of Control Signal
Splitter Block (SPLIT)
Connection method Connection destination
I/O terminal
Data Data Terminal Process Software Function
reference setting connection I/O I/O block
SET Setting input
Manipulated
OUT1
output 1
Manipulated
OUT2
output 2
D013002E.EPS
: Connection allowed
Blank: Connection not allowed
*1: ¡ £ The medium-speed scan period can only be used for the KFCS2, KFCS, LFCS2 and LFCS.
SEE ALSO
• For the types of output processing and alarm processing possible for the SPLIT block, see chapter D1.1.3,
“Input Processing, Output Processing, and Alarm Processing Possible for Each Regulatory Control
Block.”
• For details on the output processing, see chapter C4, “Output Processing.”
• For details on the alarm processing, see chapter C5, “Alarm Processing-FCS.”
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
MV1 MV2
MSH1 MSH2
MSL1 MSL2
SSL SV SSH
MVi=CALCi+BLi (n)
MSHi-MSLi
CALCi=MSLi+ (SV-SRLi)
SRHi-SRLi D013006E.EPS
MSHi-MSLi
CALCi=MSHi- (SV-SRLi)
SRHi-SRLi D013007E.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.
Set from the supervisory computer Input from the SET terminal
RSV CSV
AUT
RCAS CAS
SV
Setpoint value
Control
computation
D013009E.EPS
The action of the setpoint value pushback varies in accordance with the block mode of the
function block.
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
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.
AUT
? Initialization manual condition establishes
IMAN (AUT)
? Initialization manual condition vanishes
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.
CASAAUT
IMAN (CAS)AIMAN (AUT)
Use the Function Block Detail Builder to define whether or not to use the AUT fallback.
• AUT Fallback: Select “Yes” or “No.”
The default is “No.”
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
become invalid (BAD) or communication error (NCOM).
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.
The transient state mode is a compound block mode consisting of the block mode
before the execution of the block mode change command (AUT, CAS) and a remote
mode (RCAS).
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 (AUT, CAS) and a remote mode
(RCAS).
3. If the computer recovers while the function block is in the computer backup mode, the
block mode changes to 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
SEE ALSO
For details on the output clamp, see a chapter C4.3, “Output Clamp.”
SEE ALSO
For a list of valid block modes of the SPLIT block, see a chapter D1.1.4, “Valid Block Modes for Each
Regulatory Control Block.”
Representative alarm
ALRM Alarm
priority SW
masking
Input masking SV
The table below shows the connection methods and connected destinations of the I/O
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):
Connection method Connection destination
I/O terminal Data Data Terminal Process Software Function
reference setting connection I/O I/O block
Q01 to Q16 Alarm input (*1)
D013102E.EPS
: Connection allowed
Blank: Connection not allowed
*1: Connection allowed to any input terminal only when specifying an annunciator message to a software I/O.
*1: ¡ £ The medium-speed scan period can only be used for the KFCS2, KFCS, LFCS2 and LFCS.
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.”
• For details on the alarm processing, see chapter C5, “Alarm Processing-FCS.”
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:
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
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.
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.”
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.
*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.
*2: 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 among medium-priority alarms and alarms of lower priorities.
*3: 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 among low-priority alarms and alarms of lower priorities.
*4: 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 among logging alarms and alarms of lower priorities.
HH (high-priority alarm)
HI (medium-priority alarm)
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.
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.
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.”
CTUP
PH
DL - PALM
Input Count
IN PV OUT
processing processing
RMV HSW
D013201E.EPS
The table below shows the connection methods and connected destinations of the I/O
terminals of the Pulse Count Input Block (PTC):
Table Connection Methods and Connected Destinations of I/O Terminals of Pulse Count Input
Block (PTC):
Connection method Connection destination
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
: 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).
*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 PTC block,
see chapter D1.1.3, “Input Processing, Output Processing, and Alarm Processing Possible for Each
Regulatory Control Block.”
• 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.”
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
The default setting is 1.
PV
PH
DL
Block
NR PALM NR PALM CTUP
status
Reset Reset
command command D013203E.EPS
0DVDL
DV=PH-PV
PH-PV0
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.
PH
DL
DV
PV
■ 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.
SEE ALSO
For a list of valid block modes of the PTC block, see chapter D1.1.4, “Valid Block Modes for Each Regula-
tory Control Block.”
■ 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.
z FCS
YS instrument OUT
PID
SET
IN
YS block
D013302E.EPS
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.”
● Input Processing
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 %.
● Alarm Processing
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.
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.
FCS
YS block
IN
CIN
IN IN MV
MV
D013303E.EPS
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
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.
FCS
OUT
PID
SET
YS block
IN
PV MV
D013305E.EPS
******
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.
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
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.
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.
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
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.
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.
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 %.
The default is 105.50.
• 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.
SEE ALSO
For details on YS block’s alarm checks, see chapter C5, “Alarm Processing - FCS.”
● 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.
SET INT
CAS RCAS
CSV RSV
AUT/MAN
SV
PV MV
D013401E.EPS
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
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,
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.”
SEE ALSO
For details on the setpoint pushback function, see D1.33.2, “Common Specification of YS Blocks” and
D1.4, “Control Computation Processing Common to Controller Blocks.”
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.”
SEE ALSO
For details on the mode change interlock function, see D1.33.2, “Common Specification of YS Blocks.”
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.”
SET INT
CAS RCAS
CSV RSV
AUT/MAN
SV
PV MV
D013501E.EPS
The table below shows the connection methods and the connection destinations of SLPC
block I/O terminals.
Table I/O Terminal Connection Methods and Connection Destinations of YS Programmable
Controller Block (SLPC)
: 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
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 SLPC 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.”
SEE ALSO
For details on the setpoint pushback function, see D1.33.2, “Common Specification of YS Blocks” and
D1.4, “Control Computation Processing Common to Controller Blocks.”
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.”
SEE ALSO
For details on the mode change interlock function, see D1.33.2, “Common Specification of YS Blocks.”
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.”
SET INT
CAS RCAS
CSV RSV
AUT/MAN
SV
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
block I/O terminals.
Table I/O Terminal Connection Methods and Connection Destinations of YS Programmable
Controller Block with Pulse Width Output (SLMC)
: 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
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 SLMC 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.”
SEE ALSO
For details on the setpoint pushback function, see D1.33.2, “Common Specification of YS Blocks” and
D1.4, “Control Computation Processing Common to Controller Blocks.”
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.”
SEE ALSO
For details on the mode change interlock function, see D1.33.2, “Common Specification of YS Blocks.”
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.”
SET INT
CAS RCAS
CSV RSV
AUT/MAN
SV
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)
Connection Method Connection Destination
I/O Terminal Data Data Terminal Process Software Function
Reference Setting Connection I/O I/O Block
IN YS Instrument - - (*1) - -
SET Set Value Input - - - -
INT Interlock Switch Input -
D013702E.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
SEE ALSO
• For the common functions of the YS blocks, see D1.33, “Control Operations of YS Blocks.”
• For the types of input processing and alarm processing possible for the SMST-111 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 alarm processing, see C5, “Alarm Processing-FCS.”
SEE ALSO
For details on the setpoint pushback function, see D1.33.2, “Common Specification of YS Blocks” and
D1.4, “Control Computation Processing Common to Controller Blocks.”
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.”
SEE ALSO
For details on the mode change interlock function, see D1.33.2, “Common Specification of YS Blocks.”
SEE ALSO
For a list of valid block modes of the SMST-111 block, see D1.1.4, “Valid Block Modes for Each Regula-
tory Control Block.”
INT
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)
: 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
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 SMST-121
block, see D1.1.3, “Input Processing, Output Processing, and Alarm Processing Possible for Each Regu-
latory 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.”
SEE ALSO
For details on the mode change interlock function, see D1.33.2, “Common Specification of YS Blocks.”
SEE ALSO
For a list of valid block modes of the SMST-121 block, see D1.1.4, “Valid Block Modes for Each Regula-
tory Control Block.”
SET INT
CAS RCAS
CSV RSV
AUT/MAN
SV
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
block I/O terminals.
Table I/O Terminal Connection Methods and Connection Destinations of YS Ratio Set Station
Block (SMRT)
Connection Method Connection Destination
I/O Terminal Data Data Terminal Process Software Function
Reference Setting Connection I/O I/O Block
IN YS Instrument - - (*1) - -
SET Set Value Input - - - -
INT Interlock Switch Input -
D013902E.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
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 SMRT 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.”
SEE ALSO
For details on the setpoint pushback function, see D1.33.2, “Common Specification of YS Blocks” and
D1.4, “Control Computation Processing Common to Controller Blocks.”
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.”
SEE ALSO
For details on the mode change interlock function, see D1.33.2, “Common Specification of YS Blocks.”
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.”
RCAS
RSV
AUT
SV
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
block I/O terminals.
Table I/O Terminal Connection Methods and Connection Destinations of YS Batch Set Station
Block (SBSD)
Connection Method Connection Destination
I/O Terminal Data Data Terminal Process Software Function
Reference Setting Connection I/O I/O Block
IN YS Instrument - - (*1) - -
D014002E.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
SEE ALSO
• For the common functions of the YS blocks, see D1.33, “Control Operations of YS Blocks.”
• 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.”
• For details on the input processing, see C3, “Input Processing.”
• For details on the alarm processing, see C5, “Alarm Processing-FCS.”
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.”
INT
RCAS
RSV
AUT/MAN
SV
PV MV
D014101E.EPS
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
block I/O terminals.
Table I/O Terminal Connection Methods and Connection Destinations of YS Batch Controller
Block (SLBC)
Connection Method Connection Destination
I/O Terminal Data Data Terminal Process Software Function
Reference Setting Connection I/O I/O Block
IN YS Instrument - - (*1) - -
INT Interlock Switch Input -
D014102E.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
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 SLBC 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.”
SEE ALSO
For details on the mode change interlock function, see D1.33.2, “Common Specification of YS Blocks.”
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.”
INT
RCAS
RSV
AUT
SV
PV MV
D014201E.EPS
The table below shows the connection methods and the connection destinations of SLCC
block I/O terminals.
Table I/O Terminal Connection Methods and Connection Destinations of YS Blending Controller
Block (SLCC)
Connection Method Connection Destination
I/O Terminal Data Data Terminal Process Software Function
Reference Setting Connection I/O I/O Block
IN YS Instrument - - (*1) - -
INT Interlock Switch Input -
D014202E.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
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 SLCC 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.”
SEE ALSO
For details on the mode change interlock function, see D1.33.2, “Common Specification of YS Blocks.”
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.”
PV
D014301E.EPS
The table below shows the connection methods and the connection destinations of STLD
block I/O terminals.
Table I/O Terminal Connection Methods and Connection Destinations of YS Totalizer Block
(STLD)
Connection Method Connection Destination
I/O Terminal Data Data Terminal Process Software Function
Reference Setting Connection I/O I/O Block
IN YS Instrument - - (*1) - -
D014302E.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
SEE ALSO
• For the common functions of the YS blocks, see D1.33, “Control Operations of YS Blocks.”
• 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.”
• For details on the input processing, see C3, “Input Processing.”
• For details on the alarm processing, see C5, “Alarm Processing-FCS.”
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.”
*1: ¡ £ The logic operation blocks are only supported in CS 3000 system.
FCS
Basic control
Software I/O
Faceplate blocks
SFC blocks
Options
D020001E.EPS
■ 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
processing 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
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.”
The following diagram shows the architecture of the Logic Operation block.
IN RV CPV OUT
Qn RVn CPVn Jn
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
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.”
● 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.
● 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.
*1: ¡ £ Logic operation block is only available for CS 3000.
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.”
Input Output
Block type Code Name
terminals terminals
ADD Addition Block
: Exists
Blank: Not exist
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
S3: 3-position pulsive output
P2: 2-position pulsive output
P3: 3-position status output
S2b: 2-position status output (BSETU-2/3 only)
S3b: 3-position status output (BSETU-2/3 only)
S2s: 2-position status output through switch instrument (BSETU-2/3 only)
S3s: 3-position status output through switch instrument (BSETU-2/3 only)
Sb: Subsystem 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
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
S3: 3-position status output
P2: 2-position pulsive output
P3: 3-position pulsive output
S2b: 2-position status output (BSETU-2/3 only)
S3b: 3-position status output (BSETU-2/3 only)
S2s: 2-position status output through switch instrument (BSETU-2/3 only)
S3s: 3-position status output through switch instrument (BSETU-2/3 only)
Sb: Subsystem output
*1: Possible if explicitly input using computational expression
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
Blank: Not available
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
Blank: Not available
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
Blank: Not available
: Valid
-: Invalid
: Valid
-: Invalid
*1: ¡ £ Logic Operation blocks are only available for CS 3000.
: Valid
-: Invalid
Input
IN RV
processing
Gain
(GAIN),
Addition CPV OUT
bias
(BIAS)
RV1 gain
(GN1),
Q01 RV1
RV1 bias
(BS1)
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).
*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 ADD block,
see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Cal-
culation Block.”
• 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.”
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.”
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):
A numeric value of 7 digits or less including the sign and decimal point.
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
SEE ALSO
For the information about valid block mode for ADD block, see chapter D2.3.2, “Valid Block Modes for
Each Calculation Blocck.”
Input
IN RV
processing
Gain
(GAIN),
Multiplication CPV OUT
bias
(BIAS)
RV1 gain
(GN1),
Q01 RV1
RV1 bias
(BS1)
The following table shows the connection types and connection destinations of the I/O
terminals of the Multiplication Block (MUL).
Table Connection Types and Connection Destinations of the I/O Terminals of Multiplication Block
(MUL)
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
D020502E.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).
*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 MUL block,
see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Cal-
culation Block.”
• 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.”
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.”
■ Set Parameters
The set parameters of the Multiplication Block (MUL) 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):
A numeric value of 7 digits or less including the sign and decimal point.
The default is 1.00
• RV1 bias (BS1):
An engineering unit data value of 7 digits or less including the sign and decimal point.
The default is 0.00
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.”
Input
IN RV
processing
Gain
(GAIN),
Division CPV OUT
bias
(BIAS)
RV1 gain
(GN1),
Q01 RV1
RV1 bias
(BS1)
The following table shows the connection types and connection destinations of the I/O
terminals of the Division Block (DIV).
Table Connection Types and Connection Destinations of the I/O Terminals of Division Block (DIV)
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
D020602E.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).
*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 DIV block,
see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Cal-
culation Block.”
• 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.”
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.”
■ Set Parameters
The set parameters of the Division Block (DIV) 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):
A numeric value of 7 digits or less including the sign and decimal point.
The default is 1.00
• RV1 bias (BS1):
An engineering unit data value of 7 digits or less including the sign and decimal point.
The default is 0.00
SEE ALSO
For a list of valid block modes for DIV block, see chapter D2.3.2, “Valid Block Modes for Each Calculation
Block.”
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
: 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).
*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,
see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Cal-
culation Block.”
• 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.”
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
Function Block Detail Builder.
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 (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.
RV1 to RVn (n is an average number)
BAD RV1 to RVn (*2)
are all BAD.
RV1 to RVn (n is an average number)
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.
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.
RV1+RV2+RV3+...+RVN
CPV=GAIN •
N
D020704E.EPS
“Number of averaged” and “sampling candidate specification” is set using the Function
Block Detail Builder.
• 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.
SEE ALSO
For a list of valid block modes for AVE block, see chapter D2.3.2, “Valid Block Modes for Each Calculation
Block.”
Input
IN RV GAIN • RV CPV OUT
processing
(CPV, CPV)
SUB
D020801E.EPS
The following table shows the connection types and connection destinations of the I/O
terminals of the Square Root Block (SQRT).
Table Connection Types and Connection Destinations of the I/O Terminals of Square Root Block
(SQRT)
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
Calculation
IN
input
Calculation
OUT
output
Auxiliary
SUB
output
D020802E.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).
*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 SQRT block,
see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Cal-
culation Block.”
• 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.”
■ Calculation Algorithm
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):
A numeric value of 7 digits or less including the sign and decimal point.
The default is 1.00
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.”
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.”
Input
IN RV GAIN • eRV CPV OUT
processing
(CPV, CPV)
SUB
D020901E.EPS
The following table shows the connection types and connection destinations of the I/O
terminals of the Exponential Block (EXP).
Table Connection Types and Connection Destinations of the I/O Terminals of Exponential Block
(EXP)
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
Calculation
IN
input
Calculation
OUT
output
Auxiliary
SUB
output
D020902E.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).
*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 EXP block,
see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Cal-
culation Block.”
• 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.”
■ Calculation Algorithm
The Exponential Block (EXP) executes the following calculation processing to the input
data.
CPV=GAIN • eRV
■ Set Parameter
The parameters of the Exponential Block (EXP) 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.
CPV
RV=ln
GAIN
D020903E.EPS
If (CPV/GAIN) 0, the calculation input value (RV) retains the previous value.
SEE ALSO
For details on the CPV pushback, see chapter C4.11, “CPV Pushback.”
SEE ALSO
For a list of valid block modes for EXP block, see chapter D2.3.2, “Valid Block Modes for Each Calculation
Block.”
Input GAIN
IN RV CPV OUT
processing 1+Tis
(CPV, CPV)
SUB
D021001E.EPS
The following table shows the connection types and connection destinations of the I/O
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)
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
Calculation
IN
input
Calculation
OUT
output
Auxiliary
SUB
output
D021002E.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).
*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 LAG block,
see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Cal-
culation Block.”
• 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.”
GAIN
CPV= • RV
1+Tis
D021003E.EPS
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):
A numeric value of 7 digits or less including the sign and decimal point.
The default is 1.00.
• 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
Time t
Ti
Figure Example of the Step Response Action of First-Order Lag Block (LAG)
CPV
RV=
GAIN
D021005E.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."
SEE ALSO
For a list of valid block modes for LAG block, see chapter D2.3.2, “Valid Block Modes for Each Calculation
Block.”
Input GAIN
IN RV CPV OUT
processing Tis
(CPV, CPV)
SUB
D021101E.EPS
The following table shows the connection types and connection destinations of the I/O
terminals of the Integration Block (INTEG).
Table Connection Types and Connection Destinations of the I/O Terminals of Integration Block
(INTEG)
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
Calculation
IN
input
Calculation
OUT
output
Auxiliary
SUB
output
D021102E.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).
*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 INTEG block,
see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Cal-
culation Block.”
• 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.”
GAIN
CPV= • RV
Tis
D021103E.EPS
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.
• When Manipulation switch (SW) is 1
Starts the integration calculation. The calculated output value (CPV) is updated by
each scan period. Block status is RUN.
• When Manipulation switch (SW) is 2
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):
A numeric value of 7 digits or less including the sign and decimal point.
The default is 1.00.
• Integral time setpoint (I):
A numeric number between 0.1 and 10000.0. Unit: sec.
Input signal
Ts
GAIN RV
I
Output signal
Time t
2 1 2
SW
SW(2A0A1) SW(1A2)
D021104E.EPS
CPV
RV=
GAIN
D021105E.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.”
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.”
(CPV, CPV)
SUB
D021201E.EPS
The following table shows the connection types and connection destinations of the I/O
terminals of the Derivative Block (LD).
Table Connection Types and Connection Destinations of the I/O Terminals of Derivative Block
(LD)
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
Calculation
IN
input
Calculation
OUT
output
Auxiliary
SUB
output
D021202E.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).
*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 LD block, see
chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calcu-
lation Block.”
• 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.”
Tds
CPV=GAIN • • RV
1+Tds
D021203E.EPS
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):
A numeric value of 7 digits or less including the sign and decimal point.
The default is 1.00.
• Derivative time setpoint (D):
A numeric value between 0.1 and 1000.0. Unit: sec.
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
CPV
RV=
GAIN
D021205E.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.”
SEE ALSO
For a list of valid block modes for LD block, see chapter D2.3.2, “Valid Block Modes for Each Calculation
Block.”
Input
IN RV GAIN • (Ramp characteristic) CPV OUT
processing
(CPV, CPV)
SUB
D021301E.EPS
The following table shows the connection types and connection destinations of the I/O
terminals of the Ramp Block (RAMP).
Table Connection Types and Connection Destinations of the I/O Terminals of Ramp Block
(RAMP)
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
Calculation
IN
input
Calculation
OUT
output
Auxiliary
SUB
output
D021302E.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).
*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 RAMP block,
see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Cal-
culation Block.”
• 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.”
Input signal
(CPV span)
• Scan period (sec.)
STEP
Scan period
D021303E.EPS
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):
A numeric value of 7 digits or less including the sign and decimal point.
The default is 1.00.
• 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).
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.”
(CPV, CPV)
SUB
D021401E.EPS
The following table shows the connection types and connection destinations of the I/O
terminals of the Lead/Lag Block (LDLAG).
Table Connection Types and Connection Destinations of I/O Terminals of Lead/Lag Block
(LDLAG)
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
Calculation
IN
input
Calculation
OUT
output
Auxiliary
SUB
output
D021402E.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).
*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 LDLAG block,
see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Cal-
culation Block.”
• 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.”
GAIN • (1+Tds)
CPV= • RV
1+Tis
D021403E.EPS
■ Set Parameters
The parameters of the Lead/Lag Block (LDLAG) 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.
• Lead time setpoint (D):
A numeric value between 0.0 and 10000.0. Unit: sec.
• Lag time setpoint (I):
A numeric value between 0.0 and 10000.0. Unit: sec.
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
D/I<1
Time t D021404E.EPS
CPV
RV=
GAIN
D021405E.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.”
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.”
(CPV, CPV)
SUB
D021501E.EPS
The following table shows the connection types and connection destinations of the I/O
terminals of the Dead-Time Block (DLAY).
Table Connection Types and Connection Destinations of the I/O Terminals of Dead-Time Block
(DLAY)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting block
reference testing manipulation connection I/O I/O
IN Main input
Calculation
OUT
output
Auxiliary
SUB
output
D021502E.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).
*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 DLAY block,
see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Cal-
culation Block.”
• 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.”
GAIN
CPV= e-LS • RV
1+Tis D021503E.EPS
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):
A numeric value of 7 digits or less including the sign and decimal point.
• Sampling interval (SMPL):
A numeric value between 0.1 and 10000.0. Unit: sec.
Set a value which is a multiple of the scan period.
• First-order lag time (I):
A numeric value between 0.1 and 10000.0. Unit: sec.
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 (I) is same as the scan period.
Input signal
Time t
L Ti
L Dead time
Ti First-order lag time (Ti = I - Scan period)
D021504E.EPS
■ 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 DLAY 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 [Yes].
The following calculation formula is used in the CPV pushback of the DLAY block.
CPV
RV=
GAIN
D021505E.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.”
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.”
Input GAIN
IN RV (e-LS-1) CPV OUT
processing 1+Tis
(CPV, CPV)
SUB
D021601E.EPS
The following figure shows an example of dead time compensation control using the Dead-
Time Compensation Block (DLAY-C).
- 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)
The following table shows the connection types and connection destinations of the I/O
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)
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
Calculation
IN
input
Calculation
OUT
output
Auxiliary
SUB
output
D021603E.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).
*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 DLAY-C block,
see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Cal-
culation Block.”
• 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.”
■ Calculation Algorithm
▼ 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
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
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 (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
SEE ALSO
For a list of valid block modes for DLAY-C block, see chapter D2.3.2, “Valid Block Modes for Each
Calculation Block.”
Input Xr+Xr-1+...+Xr-m+1
IN RV GAIN CPV OUT
processing m
(CPV, CPV)
SUB
D021701E.EPS
The following table shows the connection types and connection destinations of the I/O
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)
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
Calculation
IN
input
Calculation
OUT
output
Auxiliary
SUB
output
D021702E.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).
*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-M block,
see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Cal-
culation Block.”
• 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.”
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.”
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
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.
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
SEE ALSO
For a list of valid block modes for AVE-M block, see a chapter D2.3.2, “Valid Block Modes for Each
Calculation Block.”
Manipulation SW
switch
Input
IN
processing
RV GAIN • Average CPV OUT
value
(CPV, CPV)
SUB
D021801E.EPS
The following table shows the connection types and connection destinations of the I/O
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)
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
Calculation
IN
input
Calculation
OUT
output
Auxiliary
SUB
output
D021802E.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).
*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-C block,
see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Cal-
culation Block.”
• 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.”
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).
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.
■ Action Example
The following figure shows an action example of the Cumulative-Average Block (AVE-C).
Calculated
output value
(CPV)
Calculated
input value
(RV)
Initialize Initialize
2 1 2 1
SW
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.”
Input Variable
IN RV GAIN • CPV OUT
processing line-segment function
(CPV, CPV)
SUB
D021901E.EPS
The following table shows the connection types and connection destinations of the I/O
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)
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
Calculation
IN
input
Calculation
OUT
output
Auxiliary
SUB
output
D021902E.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).
*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 FUNC-VAR
block, see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each
Calculation Block.”
• 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.”
■ Set Parameters
The parameters of the Variable Line-Segment Function Block (FUNC-VAR) are shown as
follows.
• Number of segments (SECT):
A numeric value between 1 and 14.
• 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)
X
D021903E.EPS
6
5
4
D021904E.EPS
■ 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 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.
The CPV pushback operates only when the output value tracking is set to [Yes].
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.
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.”
SEE ALSO
For a list of valid block modes for FUNC-VAR block, see chapter D2.3.2, “Valid Block Modes for Each
Calculation Block.”
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)
The following table shows the connection types and connection destinations of the I/O
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).
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
Measured
IN
flowrate
Measured
Q01
temperature
Measured
Q02
pressure
Calculation
OUT
output
Auxiliary
SUB
output
D022002E.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).
*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 TPCFL block,
see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Cal-
culation Block.”
• 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.”
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
With the pressure unit of kgf/cm2 and the temperature unit of F, the expression is given
below.
5 5
T'= (T -32) T'b= (Tb-32)
9 9
D022004E.EPS
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
P+1.01325 • 102
F0= • Fi [Pressure: kPa]
Pb+1.01325 • 102
D022007E.EPS
The expression for corrective calculation at the pressure unit kgf/cm2 is given below.
P+1.0332
F0= Fi
Pb+1.0332
D022008E.EPS
“Correction computation,” “temperature unit” and “pressure unit” are set in the
Function Block Detail Builder.
• 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.
D022009E.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.”
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)
The following table shows the connection types and connection destinations of the I/O
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)
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
Measured
IN
flowrate
Measured
Q01
temperature
Calculation
OUT
output
Auxiliary
SUB
output
D022102E.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).
*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 ASTM1 block,
see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Cal-
culation Block.”
• 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.”
-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
Figure Specific Gravity Ranges and Temperature Ranges of the ASTM Correction Computation
(Old JIS) and Table II of JIS K2249 (Old JIS)
F0 = Cf • Fi
Cf = 1 + (TMP-15) + (TMP-15)2
The calculated output value (CPV) is the corrected flowrate (F0) multiplied by the gain
(GAIN).
CPV = GAIN • F0
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.”
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)
The following table shows the connection types and connection destinations of the I/O
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)
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
Measured
IN
flowrate
Measured
Q01
temperature
Calculation
OUT
output
Auxiliary
SUB
output
D022202E.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).
*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 ASTM2 block,
see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Cal-
culation Block.”
• 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.”
F0 = Cf • Fi
K0 K1 B
= + or = A +
2
2
D022203E.EPS
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
The calculated output value (CPV) is the corrected flowrate (F0) multiplied by the gain
(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
Only Deg. C may be selected from the list. If use Fahrenheit degree, F may be manu-
ally entered in the entry box.
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.”
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) £
The following table shows the connection types and connection destinations of the I/O
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) £
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
Calculation
Q01
input 1
Calculation
Q02
input 2
Calculation
OUT
output
D022302E.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).
*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.”
• 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.”
■ 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
SEE ALSO
For a list of valid block modes for AND and OR blocks, see chapter D2.3.2, “Valid Block Modes for Each
Calculation Block.”
D022401E.EPS
The following table shows the connection types and connection destinations of the I/O
terminals of Logical NOT Block (NOT).
Table Connection Types and Connection Destinations of I/O Terminals of Logical NOT Block
(NOT) £
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
Calculation
IN
input
Calculation
OUT
output
D022402E.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).
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.”
• 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.”
■ 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
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.”
Input Output
Q01 RV1 CPV1 J01
Processing Processing
Calculation
Processing
Input
Q02 RV2
Processing
Input
Q01 RV1 CPV1 J01
Processing
Calculation Output
Processing Processing
Input
Q02 RV2 CPV2 J02
Processing
Figure Function Block Diagram of SRS1-S, SRS1-R, SRS2-S and SRS2-R Blocks £
: 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).
*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 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.”
• 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.”
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
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.”
Input
Q01 RV1
Processing
Calculation Output
CPV OUT
Processing Processing
Input
Q02 RV2
Processing
D022601E.EPS
The following table shows the connection types and connection destinations of the I/O
terminals of Wipeout Block (WOUT).
Table Connection Types and Connection Destinations of the I/O Terminals of Wipeout Block
(WOUT) £
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
Calculation
Q01
input 1
Calculation
Q02
input 2
Calculation
OUT
output
D022602E.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).
*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 WOUT block,
see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Cal-
culation Block.”
• 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.”
■ Calculation Algorithm £
The calculated output value (CPV) and the calculation input value (RV1, RV2) have the
following relationship.
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
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.”
D022701E.EPS
The following table shows the connection types and connection destinations of the I/O
terminals of ON-Delay Timer Block (OND).
Table Connection Types and Connection Destinations of the I/O Terminals of ON-Delay Timer
Block (OND) £
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
Calculation
IN
input
Calculation
OUT
output
D022702E.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).
*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 OND block,
see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Cal-
culation Block.”
• 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.”
0
RV
0
t
STM Timer start Timer reset
t<STM
1
CPV
D022703E.EPS
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
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.”
D022801E.EPS
The following table shows the connection types and connection destinations of the I/O
terminals of OFF-Delay Timer Block (OFFD).
Table Connection Types and Connection Destinations of the I/O Terminals of OFF-Delay Timer
Block (OFFD) £
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
Calculation
IN
input
Calculation
OUT
output
D022802E.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).
*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 OFFD block,
see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Cal-
culation Block.”
• 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.”
0
RV
0
t
STM
Timer start Timer reset
t<STM
1
CPV
D022803E.EPS
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
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.”
D022901E.EPS
The following table shows the connection types and connection destinations of the I/O
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 £
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
Calculation
IN
input
Calculation
OUT
output
D022902E.EPS
: Connection available
Blank: Connection not available
: Connection is available only when connecting to a switch block (SW-33, SW-91) or an inter-station data link block
(ADL).
*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 TON and
TOFF blocks, see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible
for Each Calculation Block.”
• 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.”
■ Calculation Algorithm £
The calculation algorithm of One-shot blocks TON and TOFF may be illustrated as follows.
0
IN
OUT
1 Scan
One-shot
Rise trigger
D022903E.EPS
0
IN
OUT
1 Scan
One-shot
Fall trigger
D022904E.EPS
SEE ALSO
For a list of valid block modes for TON and TOFF blocks, see chapter D2.3.2, “Valid Block Modes for
Each Calculation Block.”
Input
Q01 RV1
Processing
Calculation Output
CPV OUT
Processing Processing
Input
Q02 RV2
Processing
D023001E.EPS
Figure Function Block Diagram of Relational Operation Blocks (GT, GE, EQ) £
The following table shows the connection types and connection destinations of the I/O
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) £
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
Calculation
Q01
input 1
Calculation
Q02
input 2
Calculation
OUT
output
D023002E.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).
*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 GT, GE, and
EQ blocks, see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible
for Each Calculation Block.”
• 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.“
■ Calculation Algorithm £
The calculation algorithm of GT, GE, EQ may be described as follows.
SEE ALSO
For a list of valid block modes for GT, GE and EQ blocks, see chapter D2.3.2, “Valid Block Modes for
Each Calculation Block.”
Input
Q01 RV1
Processing
Calculation Output
CPV OUT
Processing Processing
Input
Q02 RV2
Processing
D023101E.EPS
Figure Function Block Diagram of Bitwise AND Block (BAND) and Bitwise OR Block (BOR) £
The following table shows the connection types and connection destinations of the I/O
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) £
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
Calculation
Q01
input 1
Calculation
Q02
input 2
Calculation
OUT
output
D023102E.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).
*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 BAND and
BOR blocks, see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible
for Each Calculation Block.”
• 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.”
■ Calculation Algorithm £
The I/O data of BAND and BOR blocks are integer type.
The calculation algorithm of BAND and BOR may be described as follows.
SEE ALSO
For a list of valid block modes for BAND and BOR blocks, see chapter D2.3.2, “Valid Block Modes for
Each Calculation Block.”
D023201E.EPS
The following table shows the connection types and connection destinations of the I/O
terminals of Bitwise NOT Block (BNOT).
Table Connection Types and Connection Destinations of the I/O Terminals of Bitwise NOT Block
(BNOT) £
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
Calculation
IN
input
Calculation
OUT
output
D023202E.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).
*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 BNOT block,
see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Cal-
culation Block.”
• 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.”
■ 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
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.”
P01 P08
IN RV CPV OUT
User-defined
Q01 RV1 CPV1 Output J01
Input arithmetic/logic
processing calculation processing
processing
(CPV, CPV)
SUB
D023301E.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).
: 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).
*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 CALCU and
CALCU-C blocks, see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing
Possible for Each Calculation Block.”
• 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.”
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.
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
Function Block Detail Builder.
The input signals that are directly specified in the calculation expression description be-
come the target of calculation input error detection.
SEE ALSO
For details on the description of calculation errors and the calculation error handling, see chapter
D2.47.7, “Error Handling.”
SEE ALSO
For a list of valid block modes for CALCU block, see chapter D2.3.2, “Valid Block Modes for Each
Calculation Block.”
SEE ALSO
For a list of valid block modes for CALCU-C block, see chapter D2.3.2, “Valid Block Modes for Each
Calculation Block.”
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)
: Connection available
Blank: Connection not available
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.
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.”
• For details on the input processing, see chapter C3, “Input Processing.”
■ 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.
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)
: Connection available
Blank: Connection not available
Note: Condition check and status manipulation signals of sequence connection cannot be handled. Inter-station data link
cannot be performed, either.
SEE ALSO
• For the types of input processing possible for the SW-91 block, see chapter D2.3.1, “Input Processing,
Output Processing, and Alarm Processing Possible for Each Calculation Block.”
• For details on the input processing, see chapter C3, “Input Processing.”
■ Set Parameters
The parameters of the One-Pole Nine-Position Selector Switch Block (SW-91) are shown
as follows.
• Selector switch (SW): A numeric value between 0 and 9
• 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.
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)
The following table shows the connection types and connection destinations of the I/O
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)
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
Calculation
OUT
output
D023702E.EPS
: Connection available
Blank: Connection not available
*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 DSW-16
block, see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each
Calculation Block.”
• 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.”
■ Calculation Algorithm
▼ 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.
• Output Velocity Limiter:
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.
• Selector switch (SW): A numeric value between 0 and 16
• Constants 1 to 16 (SD01 to SD16): Engineering unit data values
SEE ALSO
For a list of valid block modes for DSW-16 block, see chapter D2.3.2, “Valid Block Modes for Each
Calculation Block.”
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)
The following table shows the connection types and connection destinations of the I/O
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)
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
Calculation
OUT
output
D023802E.EPS
: Connection available
Blank: Connection not available
*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 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.”
• For details on the input processing, see chapter C3, “Input Processing.”
• For details on the alarm processing, see chapter C5, “Alarm Processing-FCS.”
■ Calculation Algorithm
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.
• Selector switch (SW): A numeric value between 0 and 16
• Constants 1 to 16 (SD01 to SD16):
Set string data of up to 16 standard-width characters or 8 double-width characters.
SEE ALSO
For a list of valid block modes for DSW-16C block, see chapter D2.3.2, “Valid Block Modes for Each
Calculation Block.”
D023901E.EPS
The following table shows the connection types and connection destinations of the I/O
terminals of Data Set Block (DSET).
Table Connection Types and Connection Destinations of the I/O Terminals of Data Set Block
(DSET)
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
Setting
OUT
output
D023902E.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).
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.”
• 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.”
The output velocity limiter value is set on the Function Block Detail Builder.
• Output Velocity Limiter:
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.
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.”
Here is a function block diagram of the Data Set Block with Input Indicator (DSET-PVI).
Input Velocity
IN CPV SV OUT
processing limiter
SUB
D024001E.EPS
Figure Function Block Diagram of Data Set Block with Input Indicator (DSET-PVI)
The following table shows the connection types and connection destinations of the I/O
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)
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
Calculation
IN
input
Calculation
OUT
output
Auxiliary
SUB
output
D024002E.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).
SEE ALSO
• For the types of input processing, output processing, and alarm processing possible for the DSET-PVI
block, see chapter D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each
Calculation Block.”
• 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.”
■ Calculation Algorithm
▼ Output Velocity Limiter
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.
• Output Velocity Limiter:
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.
SEE ALSO
For a list of valid block modes for DSET-PVI block, see chapter D2.3.2, “Valid Block Modes for Each
Calculation Block.”
Command switch SW
D024101E.EPS
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)
Connection type Connection destination
I/O terminal Data Data Condition Status Terminal Process Software Function
reference setting testing manipulation connection I/O I/O block
Calculation
J01 to J16
output
D024102E.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).
*1: ¡ £ The medium-speed scan period can only be used for the KFCS2, KFCS, LFCS2 and LFCS.
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.”
• For details on the alarm processing, see chapter C5, “Alarm Processing-FCS.”
*1: Switching of the switch position from “2” to “3” is performed automatically by the BDSET-1L block.
Element symbol.ACT.n
■ 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):
Engineering unit data values at output destinations
• Set limit low limit (DL01 to DL16):
Engineering unit data values at output destinations
SEE ALSO
For a list of valid block modes for BDSET-1L block, see chapter D2.3.2, “Valid Block Modes for Each
Calculation Block.”
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)
Connection type Connection destination
I/O terminal Data Data Condition Status Terminal Process Software Function
reference setting testing manipulation connection I/O I/O block
Calculation
J01 to J16
output
D024202E.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).
*1: ¡ £ The medium-speed scan period can only be used for the KFCS2, KFCS, LFCS2 and LFCS.
SEE ALSO
• For the types of alarm processing possible for the BDSET-1C block, see chapter D2.3.1, “Input Process-
ing, Output Processing, and Alarm Processing Possible for Each Calculation Block.”
• For details on the alarm processing, see chapter C5, “Alarm Processing-FCS.”
*1: Switching of the switch position from “2” to “3” is performed automatically by the One-Batch String Data Set Block
(BDSET-1C).
Element symbol.ACT.n
■ Set Parameters
The parameters of the One-Batch String Data Set Block (BDSET-1C) are shown as follows.
• Batch data (DT01 to DT16):
Set string data of up to 16 standard-width characters or 8 double-width characters.
• Command switch (SW): A numeric value between 0 and 3.
SEE ALSO
For a list of valid block modes for BDSET-1C block, see chapter D2.3.2, “Valid Block Modes for Each
Calculation Block.”
SW Command switch
D024301E.EPS
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)
Connection type Connection destination
I/O terminal Data Data Condition Status Terminal Process Software Function
reference setting testing manipulation connection I/O I/O block
Calculation
J01 to J16
output
D024302E.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).
*1: ¡ £ The medium-speed scan period can only be used for the KFCS2, KFCS, LFCS2 and LFCS.
SEE ALSO
• For the types of alarm processing possible for the BDSET-2L block, see chapter D2.3.1, “Input Process-
ing, Output Processing, and Alarm Processing Possible for Each Calculation Block.”
• For details on the alarm processing, see chapter C5, “Alarm Processing-FCS.”
*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.
Element symbol.ACT.n
■ 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.
SEE ALSO
For a list of valid block modes for BDSET-2L block, see chapter D2.3.2, “Valid Block Modes for Each
Calculation Block.”
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)
Connection type Connection destination
I/O terminal Data Data Condition Status Terminal Process Software Function
reference setting testing manipulation connection I/O I/O block
Calculation
J01 to J16
output
D024402E.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).
*1: ¡ £ The medium-speed scan period can only be used for the KFCS2, KFCS, LFCS2 and LFCS.
SEE ALSO
• For the types of alarm processing possible for the BDSET-2C block, see chapter D2.3.1, “Input Process-
ing, Output Processing, and Alarm Processing Possible for Each Calculation Block.”
• For details on the alarm processing, see chapter C5, “Alarm Processing-FCS.”
*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.
Element symbol.ACT.n
■ Set Parameters
The parameters of the Two-Batch String Data Set Block (BDSET-2C) are shown as follows.
• Current batch data (DT01 to DT16):
Set string data of up to 16 standard-width characters or 8 double-width characters.
• Next batch data (NX01 to NX16):
Set string data of up to 16 standard-width characters or 8 double-width characters.
• 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 has been performed.
SEE ALSO
For a list of valid block modes for BDSET-2C block, see chapter D2.3.2, “Valid Block Modes for Each
Calculation Block.”
Command switch SW
D024501E.EPS
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)
Connection type Connection destination
I/O terminal Data Data Condition Status Terminal Process Software Function
reference setting testing manipulation connection I/O I/O block
Calculation
J01 to J16
output
D024502E.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).
*1: ¡ £ The medium-speed scan period can only be used for the KFCS2, KFCS, LFCS2 and LFCS.
SEE ALSO
• For the types of alarm processing possible for the BDA-L block, see chapter D2.3.1, “Input Processing,
Output Processing, and Alarm Processing Possible for Each Calculation Block.”
• For details on the alarm processing, see chapter C5, “Alarm Processing-FCS.”
■ 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
Element symbol.ACT.n
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.”
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)
Connection type Connection destination
I/O terminal Data Data Condition Status Terminal Process Software Function
reference setting testing manipulation connection I/O I/O block
Calculation
J01 to J16
output
D024602E.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).
SEE ALSO
• For the types of alarm processing possible for the BDA-C block, see chapter D2.3.1, “Input Processing,
Output Processing, and Alarm Processing Possible for Each Calculation Block.”
• For details on the alarm processing, see chapter C5, “Alarm Processing-FCS.”
Element symbol.ACT.n
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.”
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
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
● 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.
D024703E.EPS
D024704E.EPS
D024705E.EPS
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.
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.
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.
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.”
● 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
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
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
char*n
integer
Integer 15 bits
long
Integer 31 bits
float
Exponent field Mantissa field
(E) 8 bits (M) 23 bits
double
Exponent field Mantissa field
(E) 11 bits (M) 52 bits
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.
TIP
• The block mode and alarm status are integer data.
• The size of the character string I/O variable is 16 bytes.
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 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.
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.
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.
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.
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.
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.
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
#define<identifier><character string>
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
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
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.”
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.
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.
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.
■ 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>
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.
• <variable>:
Variable to which the value of <expression> calculation should be assigned.
• <expression>:
Expression that calculates the substituting value for the <variable>.
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.
■ 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>
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.
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 (<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 <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.
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.
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
● Other Errors
Table List of Other Error Codes
Code Description
-1 to 32767 Internal error
D024815E.EPS
■ 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.
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.
■ 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.
Tb+273.15
TC (Fi, T, Tb) = • Fi
T+273.15
D024816E.EPS
P+1.01325 • 102
PCKP (Fi, P, Pb) = • Fi
Pb+1.01325 • 102 D024817E.EPS
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.
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.
F0 = Cf • Fi
Cf = 1 + (t - 15) + (t - 15)2
-P1(t) -P3(t)
= +P2(t) = +P4(t)
C1 C1 D024819E.EPS
Fi: Measured flowrate
t: Measured temperature
C1: 15/4 C specific gravity
F0: Corrected flow
P1(t) to P4(t): Temperature-dependent parameters
K0 K1
= +
2
D024823E.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.
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
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.
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
Faceplate blocks
Unit instruments
Options
D030001E.EPS
*1: ¡ £ Valve pattern monitorring and off-site blocks are available in CS 3000.
● 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).
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)
: available
Blank: Not available
The alarm status of ST16, LC64, TM and VLVM blocks are always indicated as NR (stands
for Normal status).
: valid
Blank: Invalid
D030201E.EPS
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
Connection type Connection destination
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
: Connection available
Blank: Connection not available
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
Two types of blocks are available in the Sequence Table Block (ST16, ST16E).
• ST16: Sequence Table Block
• ST16E: Rule Extension Block
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
D030204E.EPS
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
● 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.
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.
● 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.
● 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
“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”, “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 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).”
01 02 03
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
In the example in this figure, for OR operator, any one of the two conditions is established,
the operation may be performed.
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
D030208E.EPS
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
Processing timing
Scan period
OK Cancel
D030209E.EPS
SEE ALSO
For details of processing timing, refer to C7.3, “Process Timing for Sequence Control Block.”
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.”
SEE ALSO
For details of rule extension, refer to D3.2.9, “Rule Extension.”
Input processing
(condition testing)
....... Y
....... Y
....... N
....... Y
Output processing
(status manipulation)
D030210E.EPS
● Input Processing
The true/false status of the condition signal is determined by performing condition testing
based on the input signal.
● Output Processing
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.
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
• 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
HH
LI H
Inflow valve 100 L
VALVE-A LL
PVI
Differential Pressure
transmitter
LT100
Next process
D030213E.EPS
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.
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
• 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.
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
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)
Sequence start
Start button No
(PB001)
Yes
Switch A level Hi No
(SWA)
Yes
Start button No
PB001
Yes
Switch B level Lo No
(SWB)
Yes
D030219E.EPS
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
A A
THEN
2 1
Destination Step Label
ELSE
D030220E.EPS
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.
*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.
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
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
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.
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.
OK Cancel
D030225E.EPS
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?”
■ 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.
D030226E.EPS
SEE ALSO
For more information about control drawings, see F3. “Control Drawing Builder.”
■ 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
• Timer Block (TM)
• Software Counter Block (CTS)
• Pulse Train Input Counter Block (CTP)
• Code Input Block (CI)
• Code Output Block (CO)
• Relational Expression Block (RL)
• Resource Scheduler Block (RS)
• 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.
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 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
Nonstep type All rules
Step type Rule of Step 00 and that of the same step
Step type
name as reference source
D030255E.EPS
ST 003 ST 010
DO0001.PV H ................................ Y N
DO0011.PV H ................................ Y N
D030256E.EPS
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.
ST 003 ST 010
DO0001.PV H ................................ Y N
DO0011.PV H ................................ Y N
D030257E.EPS
The following describes the condition testing processing for the above example.
• 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.
ST 003 ST 010
DO0001.PV H ................................ Y N
DO0011.PV H ................................ Y N
D030258E.EPS
The following describes the condition testing processing for the above example.
• 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.
• 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.
• 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 a condition rule is unspecified, the
status becomes unconditionally true in the periodic processing of the above sequence
table.
• 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.
ST 003 ST 010
DO0001.PV H ................................ Y N
DO0011.PV H ................................ Y N
D030260E.EPS
The following describes the condition testing processing for the above example.
• 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 the
conditions at Rule 01 of Table ST010 are 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 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.
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 All rules
Nonstep type
Step type Rules of a specified step
Nonstep type All rules
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.
• 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 a condition rule is unspecified, the
status becomes unconditionally true in the periodic processing of the above sequence
table.
• 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.
ST 003 ST 010
DO0001.PV H ................................ Y N
DO0011.PV H ................................ Y N
D030263E.EPS
The following describes the condition testing processing for the above example.
• 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 the
conditions for Step 2, or Rule 03 of Table ST010 are 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 conditions for Step 2, or
Rule 03 of Table ST010 are false.
ST 003 ST 010
DO0001.PV H ................................ Y N
DO0011.PV H ................................ Y N
D030264E.EPS
The table reference range for the rule number 01 of Table ST003 are steps 00 and 2 of
Table ST010 in the above example.
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
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
D030268E.EPS
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.
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.
*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.
■ 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
• Timer Block (TM)
• Software Counter Block (CTS)
• Pulse Train Input Counter Block (CTP)
• Code Input Block (CI)
• 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
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)
• Communication I/O
*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)].
*1: AOF specification is only effective for changing the alarm masking specification. This action operates alarm masking
on all alarms except NR.
*1: AOF specification is only effective for changing the alarm masking specification. This action performs alarm masking
on all alarms except NR.
*2: The Output Timing of the sequence table that =XCAL is applied should be set to [Output Only When Condition
Changes (C)].
*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]
1: CSV = 1 when the action rule is [Y], Disable when [N]
2: CSV = 2 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]
*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.
*3: The Output Timing of the sequence table that =XCAL is applied should be set to [Output Only When Condition
Changes (C)].
*1: AOF specification is only effective for changing the alarm masking specification. This operation performs alarm
masking on all alarms except NR.
*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.
*1: AOF specification is only effective for changing the alarm masking specification. This operation performs alarm
masking on all alarms except NR.
*2: The Output Timing of the sequence table that =XCAL is applied should be set to [Output Only When Condition
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
*1: AOF specification is only effective for changing the alarm masking specification. This operation performs alarm
masking on all alarms except NR.
*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.”
*1 Integer type data (2-byte unsigned integer type data) can be specified for mm.
Range: Integer from 0 to 65535
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.
ST 005 ST 015
D030298E.EPS
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.
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
THEN 2 3 1
ELSE
D030299E.EPS
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 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.
ST 005 ST 015
THEN 2 1
ELSE
D0302A0E.EPS
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.
• 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.
ST 005 ST 015
D0302A2E.EPS
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 DO001.PV.H=Y operation
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.
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 All rules
Nonstep type
Step type Rules in specified step and step 00
Nonstep type All rules
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.
ST 005 ST 015
THEN
Description is
ELSE
not required.
D0302A5E.EPS
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.
A description example of specifying the execution step label of a specified sequence table
is shown below.
Assume that “Output Only when Conditions Change” is specified for the output timing.
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
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.
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.
• 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.
■ 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
OPMK Operation mark 0 to 255 0
UAID User application ID ---- 0
D0302B1E.EPS
SEE ALSO
For a list of valid block mode of the ST16, see D3.1.2 “Block Mode of Sequence Control Blocks.”
Q01 J01
Q02 J02
Logic operation
Q56 J56
D030301E.EPS
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)
Connection type Connection destination
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
D030302E.EPS
: Connection available
Blank: Connection not available
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
A logic chart with 32 inputs, 32 outputs and 64 logic elements (LC64) is provided.
Client area
D030304E.EPS
● 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
“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”, “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).”
● 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.”
● Action Signals
The output information such as tag names and data items or other specific manipulation
scripts should be entered for action signals.
Processing timing setting area Execution order of logic calculation setting area
Client area
D030305E.EPS
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
Processing timing
Scan period
OK Cancel
D030306E.EPS
SEE ALSO
For details of processing timing, refer to C7.3, “Process Timing for Sequence Control Block.”
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.”
D030307E.EPS
● Input Processing
The true or false status of a condition signal is determined by the condition test performed
on the input signal.
● Output Processing
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.
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.
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.
, , ,
D030308E.EPS
, , ,
D030309E.EPS
Figure OR symbols
● NOT: Negation
It gives the inverse of the input as an output.
D030310E.EPS
S S OUT1 S S OUT1
R R R R OUT2
S 0 1 0 1
Input
R 0 0 1 1
OUT1 Latched 1 0 0
Output
OUT2 Latched 0 1 1
D030312E.EPS
S S OUT1 S S OUT1
R R R R OUT2
S 0 1 0 1
Input
R 0 0 1 1
OUT1 Latched 1 0 1
Output
OUT2 Latched 0 1 0
D030314E.EPS
D030316E.EPS
IN
OUT
D030317E.EPS
D030318E.EPS
IN
OUT
D030319E.EPS
D030320E.EPS
1
IN
0
1
OUT
0
D030322E.EPS
1
IN
0
1
OUT
0
D030324E.EPS
● CMP-GT: Comparator
It compares the logic values of input 1 and input 2. It gives an output 1 when input 1 is
greater than input 2, otherwise it gives an output 0.
One Comparator operation is counted as two logic operation elements.
D030326E.EPS
● CMP-EQ: Comparator
It compares the logic values of input 1 and input 2. It gives an output 1 when input 1 is
equal to input 2, otherwise it gives an output 0.
One Comparator operation is counted as two logic operation elements.
D030328E.EPS
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.
■ 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
• Timer Block (TM)
• Software Counter Block (CTS)
• Pulse Train Input Counter Block (CTP)
• Code Input Block (CI)
• Code Output Block (CO)
• Relational Expression Block (RL)
• Resource Scheduler Block (RS)
• Valve Monitoring Block (VLVM)
• Regulatory Control Blocks
• Calculation Blocks
• Faceplate Blocks
• SFC Blocks
• Unit Instrument Blocks
• Sequence Table Blocks
• Logic Chart 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)
• Communication I/O
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 is True even in the compound block mode as long as the specified
basic block mode exists.
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
True Data status matches specification
Element symbol.CSV= Data status
False Data status does not match specification
True Remote manipulated output value matches specification
Element symbol.RMV 0, 1, 2
False Remote manipulated output value does not match specification
True Data status matches specification
Element symbol.RMV= Data status
False Data status does not match specification
True Bypass switch in specified state
Element symbol.BPSW. 0, 1
False Bypass switch not in specified state
True Data status matches specification
Element symbol.BPSW= Data status
False Data status does not match specification
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.
*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.
*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.
*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.
*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.
*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.
*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.
*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.
*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.
*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.
● 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
*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.
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.
*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.
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 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.
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.
• 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 a condition rule is unspecified, the
status becomes unconditionally true in the periodic processing of the above sequence
table.
• 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.
The following points should be taken into consideration when referencing a sequence table
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.
*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
inhibition status of each alarming item.
■ 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
• Timer Block (TM)
• Software Counter Block (CTS)
• Pulse Train Input Counter Block (CTP)
• Code Input Block (CI)
• Code Output Block (CO)
• Resource Scheduler Block (RS)
• 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 manipulated from logic chart:
• Process I/O
• Software I/O (internal switch, annunciator message, message output for sequence
control)
• Communication I/O
*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)].
*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.
*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.
*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: The type of logic chart that =XCAL is applied should be set to [One-Shot Processing Type (O)].
*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.”
1: CSV=1 when the manipulation rule column is “TRUE,” disabled when “FALSE.”
2: CSV=2 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.”
*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.
*2: 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.
*3: The type of logic chart that =XCAL is applied should be set to [One-Shot Processing Type (O)].
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.
*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: 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.
*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: The type of logic chart that =XCAL is applied should be set to [One-Shot Processing Type (O)].
*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.
*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.”
Table Syntax for Action Signal Description and Actions Corresponding to True/False
Manipulation signal description
True/False Manipulation description
Output signal Action Specifications
True Message output without parameter
NON
False Disable
Element symbol.PV.
True Message output with parameter
mm (*1)
False Disable
D030387E.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.
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
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.
ST
PT
■ Data Items
Table Data Items of the logic Chart Block (ST-16)
Entry parnitted
Data Item Data Name Range Default
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
OPMK Operation mark 0 to 255 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.”
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
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
Connection type Connection destination
: Connection available
Blank: Connection not available
: Connection is available only when connecting to a switch block (SW-33, SW-91).
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
: Yes
Blank: No
: 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.”
*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].
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.
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
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.”
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.
MV=2
Manipulated output
MV=0
PV=2
Answerback input
PV=0
MTM
Answerback check
suppression timer
0
● 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
MV=2
Manipulated output
MV=0
PV=2
Answerback input
PV=0
MTM
Answerback check
suppression timer
0
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].
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.
ON
n
Number of output points 2 OFF
(three-position type)
ON
n+1
OFF
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
■ 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.
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).
■ Initialization Manual
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.”
SEE ALSO
For a list of valid block modes for the switch instrument blocks, see D3.1.2 “Block Mode of Sequence
Control Blocks.”
*1: ANCK status is not available in SI-1, SI-2, SO-1 and SO-2.
Counting
PV01 OUT
process
D030501E.EPS
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)
Connection type Connection destination
: Connection available
Blank: Connection not available
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).
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.”
*1: An action for “N” is enabled only with the sequence table.
An action for “False” is enabled only with the logic chart.
PV Value
PH
DL
DV
PV
Time
The figure below shows the changes in the timer elapsed time (PV) by the timer start
command.
Start command
PV=0 Time
The following describes an example of the timer start specified in the action signal column
of the sequence table.
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
The following describes an example of specifying the timer stop in the action signal column
of the sequence table.
PH
DL
DV
PV
RUN STOP
Block
NR PALM CTUP
Status
PAUS PAUS
The following describes an example of specifying the timer restart in the action signal
column of the sequence table.
Use the Function Block Detail Builder to set the presence/absence of the periodic action.
• Periodic Action: Select from “Yes” or “No.”
The default is “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).
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
SEE ALSO
For a list of valid block modes of the timer block, see D3.1.2 “Block Mode of Sequence Control Blocks.”
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)
Connection type Connection destination
: Connection available
Blank: Connection not available
Sequence connection
DI010 Q01 CTS001.ACT.ON
CALCU OUT
DI011 Q02
■ 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).
7 Hold PV value
6
PH
(=6) DL=2 5
DV=4
4
3
2
PV=1 PV
Time
Counter operation
command
Operation Stop
command command
D030604E.EPS
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.
SEE ALSO
For a list of valid block modes of the CTS block, see D3.1.2 “Block Mode of Sequence Control Blocks.”
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
Connection type Connection destination
: Connection available
Blank: Connection not available
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.
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.
PL: The scale low limit (PV) of the count value (fixed to 0).
*1: Actions for “N” are valid only for the sequence table.
Actions for “False” are valid only for the logic chart.
PH
DL
DV
PV
5
2
4
4
Time
1 scan
PALM
Action Start Start command Stop
commands command command
4 4 2 5
Time
Scan Scan Scan Scan Scan
D030707E.EPS
PH
DL
DV
PV
Time
RUN STOP
Block
NR PALM CTUP
status
PAUS PAUS
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.
SEE ALSO
For a list of valid block modes of the CTP block, see D3.1.2 “Block Mode of Sequence Control Blocks.”
IN Bit Encoding PV
Inversion
D030801E.EPS
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
Connection type Connection destination
: Connection available
Blank: Connection not available
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.
■ 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.”
Default is “No.”
■ 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.
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)
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.
52 Meaningless
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.
SEE ALSO
For a list of valid block modes of the CI block, see D3.1.2 “Block Mode of Sequence Control Blocks.”
Bit
PV Encoding OUT
Inversion
D030901E.EPS
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
Connection type Connection destination
: Connection available
Blank: Connection not available
: 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.
■ 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.
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.
Default is “No.”
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
Significant digits
Output 1 1 1 1
D030906E.EPS
SEE ALSO
For a list of valid block modes of the CO block, see D3.1.2 “Block Mode of Sequence Control Blocks.”
Q01 RV01
(X01)
Q02 RV02
Q31 RV31
(X16)
Q32 RV32
D031001E.EPS
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
Connection type Connection destination
: Connection available
Blank: Connection not available
: Connection available only when connecting to switch blocks (SW-33, SW-91)
Process I/O
%Znnusmm Q01 RV01=%Znnusmm
(X01)
Q02 RV02=CALCU1.CPV1
Q31 RV31
(X16)
%SW0100 Q32 RV32
Software I/O
Relational Expression Block
D031003E.EPS
■ Process Timing
The process timing of RL block is only based on one-shot start.
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
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
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.
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 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.
■ Data Items - RL
Table Data Items of Relational Expression Block (RL)
Entry Permitted
Data Item Data Name Range Default
or Not
RV01 to RV32 Relational expression data ----- 0
AV01 to AV32 AND data ----- 0
OPMK Operation mark 0 to 255 0
UAID User application ID ----- 0
D031006E.EPS
1 32
D031101E.EPS
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.
Spot
P (Lorry shipping alarm)
Maximum
Pump count permissible number Request
Resource
control setting scheduler Spot control
Permission
D031102E.EPS
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.
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
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.)
Figure Sequence Table Block (ST16) used for Tank Level Control (1/2)
Figure Sequence Table Block (ST16) used for Tank Level Control (2/2)
Usage request
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.
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.
Usage request
Usage request 10
Usage request 9
Usage request
Usage request 10
Usage request 9
Ascending order
Usage request 4
Usage request 1
Waiting for permission
Usage request 6
■ Data Items - RS
Table Data Items of Resource Scheduler Block (RS)
Entry Permitted
Data Item Data Name Range Default
or Not
MODE Block mode ----- O/S (AUT)
RQ01 to RQ32 Usage request 0/1 0
PM01 to PM32 Usage permission 0/1 0
PMH Maximum permission number 0 to 32 32
OPMK Operation mark 0 to 255 0
UAID User application ID ----- 0
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.”
Q02,
Limit switch input
Q04, ...,
terminal
Q32
J01 Individual message
to J16 output terminal
Representative
J17 message output
terminal
D031202E.EPS
: Connection available
Blank: Connection not available
: Connection available only when connecting to switch blocks (SW-33, SW-91)
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).
Q03 Action
monitoring PV02 J02
Q04 timer
On/off valve
(with a limit switch)
D031203E.EPS
■ 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.
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
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.
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.”
ON
Output to valve
OFF
OPEN
Valve action
CLOSE
ON
Limit switch
OFF
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
• 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.
PV01
PV02
OR PVR=1
PV16
D031207E.EPS
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.
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).
: Present
Blank: Absent
: Depends on the builder specification
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 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.
SEE ALSO
For a list of valid block modes of the RS block, see D3.1.2 “Block Mode of Sequence Control 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
Faceplate blocks
SFC blocks
Options
D040001E.EPS
*1: ¡ £ Valve pattern monitoring and off-site blocks are available in CS 3000.
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.
*1: £ Extended 10-push-button switch block (PBS10C) is only available in CS 3000 system.
ST16
PID PV
TIC102 T1 IN TC 100
INDST3
TC100
IN1
AUT
CALCU IN2 NR
X103 F1 IN 100.0
SV
MV T1 IN
P2 IN T2 IN V OUT
D040101E.EPS
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.
● 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.
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
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
Block processing
timing Button operation Button operation
ON
MVnn OFF
ON
Output OFF
Time
t 2t 3t 4t 5t
t = Scan period
D040203E.EPS
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
timing Button operation Button operation
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
SEE ALSO
For more information about block mode and status, see a chapter C6 “Block Mode and Status.”
Note: MAN indicates a mode other than O/S. Actions are the same for all mode other than O/S.
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.
Note: SEMI (semi-automatic) has the same priority as AUT and MAN, and is mutually exclusive with the two.
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 (_).
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.
JMOD MODE
JBST BSTS
JALM ALRM
JPV PV
JSV SV
J01 SVH
J02 SVL
INT
D040401E.EPS
AIC100
System A
Concentration
AUT
NR
100.0
80.0
60.0
40.0
20.0
0.0
D040402E.EPS
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)
Connection type Connection destination
I/O terminal Data Data Condition Status Terminal Process Software Function
reference setting testing manipulation connection I/O I/O block
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 available
Blank: Connection not available
: Connection is available only when connecting to a selector switch block (SW-33, SW-91).
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).
JMOD MODE
JBST BSTS
JALM ALRM
JSV SV
JMV MV
J01 SVH
J02 SVL
J03 MH
J04 ML
INT
D040501E.EPS
AIC200
System B
Concentration
AUT
NR
100.0
80.0
60.0
40.0
20.0
0.0
D040502E.EPS
The table below shows the connection types and connection destinations of the I/O termi-
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)
Connection type Connection destination
I/O terminal Data Data Condition Status Terminal Process Software Function
reference setting testing manipulation connection I/O I/O block
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
: Connection available
Blank: Connection not available
: Connection is available only when connecting to a selector switch block (SW-33, SW-91).
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.
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
Manual Station Block (INDST2S).
JMOD MODE
JBST BSTS
JALM ALRM
JPV PV
JSV SV
JMV MV
J01 SVH
J02 SVL
J03 MH
J04 ML
INT
D040601E.EPS
AIC300
System C
Concentration
AUT
NR
100.0
80.0
60.0
40.0
20.0
0.0
D040602E.EPS
The table below shows the connection types and connection destinations of the I/O termi-
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)
Connection type Connection destination
I/O terminal Data Data Condition Status Terminal Process Software Function
reference setting testing manipulation connection I/O I/O block
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
: Connection available
Blank: Connection not available
: Connection is available only when connecting to a selector switch block (SW-33, SW-91).
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.
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 Triple-Pointer
Manual Station Block (INDST3).
JMOD MODE
JBST BSTS
JALM ALRM
SET SV PV
SWOP[1]
INT
SWST[1]
SWCR[1]
SVLMH
Q01 PV01 SWLB[1]
SVLMH
D040701E.EPS
BS100
Phase in
System A
MAN
NR
Cooling
16
START
HALT
STOP
1
D040702E.EPS
The table below shows the connection types and connection destinations of the I/O termi-
nals of the Batch Status Indicator Block (BSI).
Table Connection Types and Connection Destinations of I/O Terminals of Batch Status Indicator
Block (BSI)
Connection type Connection destination
I/O terminal Data Data Condition Status Terminal Process Software Function
reference setting testing manipulation connection I/O I/O block
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
: Connection available
Blank: Connection not available
: Connection is available only when connecting to a selector switch block (SW-33, SW-91).
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.
: Performed
Blank: Not performed
: Performed
Blank: Not performed
: Performed
Blank: Not performed
JMOD MODE
AKLB[1]
JBST BSTS SWOP[1]
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
INT
D040801E.EPS
SC100
System A
MAN NR
NR
SW1 OFF
V1
CLOSE
P1 STOP
SW2 OFF
V2
CLOSE
D040802E.EPS
: Connection available
Blank: Connection not available
: Connection is available only when connecting to a selector switch block (SW-33, SW-91).
No connection ------
Not used
Lamp
Connection
Button
Button with lamp
D040804E.EPS
: Performed
Blank: Not performed
: Performed
Blank: Not performed
: Performed
Blank: Not 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 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.
■ 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.
JMOD MODE
AKLB[1]
JBST BSTS SWOP[1]
SWCR[1]MV
SVH
Q01 PV01 SWLB[1]
MVSVH MV01 B01
SVL
Q02 PV02 SWLB[2]
SVHSVL MV02 B02
MH
SVLMH
MH
INT
D040901E.EPS
SC200
System B
MAN NR
NR
P1 STOP V3 CLOSE
D040902E.EPS
: Connection available
Blank: Connection not available
: Connection is available only when connecting to a selector switch block (SW-33, SW-91).
MV04
B04
connection
MV05
B05
connection
MV06
B06
connection
MV07
B07
connection
MV08
B08
connection
MV09
B09
connection
MV10
B10
connection
D040904E.EPS
: Connection available
Blank: Connection not available
: Performed
Blank: Not performed
: Performed
Blank: Not performed
: Performed
Blank: Not performed
■ 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.
JMOD MODE
AKLB[1]
JBST BSTS SWOP[1]
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
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)
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
: Connection available
Blank: Connection not available
: Connection is available only when connecting to a selector switch block (SW-33, SW-91).
The display form of the manipulated output value (MV) is set in the Function Block Detail
Builder.
• MV Display Style: Select from “Automatic determination” or “User Define.”
The default setting is “Automatic 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.
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 Extended Hybrid
Manual Station Block (HAS3C).
: Performed
Blank: Not performed
: Performed
Blank: Not performed
: Performed
Blank: Not 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 Extended Hybrid Manual Station Block (HAS3C) 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.
■ Reconfirmation Operation
A dialog box for reconfirming the switch 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.
■ 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
03 Heating
D050001E.EPS
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.”
Mode
Status SEBOL or
Sequence table
D050002E.EPS
......
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
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.”
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.
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 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
● 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
02
D050104E.EPS
01
D050105E.EPS
● 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
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
■ 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.
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.
06
Transition
07
D050109E.EPS
SEE ALSO
For details on transition conditions, refer to D5.5, “Transition Conditions.”
05
Transition
06 07 08
D050110E.EPS
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
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-Join
Loop-Branch
D050112E.EPS
Jump To
J2
Jump Down
J1
J2
Jump Up
Jump To
J1
Example of Jump Down Example of Jump Up
D050113E.EPS
When a new skip label is created, it is automatically numbered adding 1 to the number of
the most recent skip label.
02
Links
03
D050114E.EPS
■ 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
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.
05
Transition
06 07 08
D050116E.EPS
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.
Main program
01
Interrupt steps
02 RUN
03 STOP
04 PAUS
Developed
01
02
D050117E.EPS
■ 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.
■ 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:
D050201E.EPS
TIP
Global variables cannot be accessed from any sequence table or logic chart described step.
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.
● 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:
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:
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.
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”.
■ 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.
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
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.”
■ Order of Description
The SEBOL step action should be described in order of variables and execution statements
as shown below; an error will be caused otherwise.
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.
■ Example of Description
The following is an example of SEBOL-step description:
!local variable declaration
block PVI LI303
integer 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.
■ Order of Description
The SEBOL oneshot-step action should be described in order of variables and execution
statements as shown below; an error will be caused otherwise.
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.
■ Example of Description
The following is an example of SEBOL oneshot-step description:
!local variable declaration
block %SW SW301, SW302
■ 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.
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.
■ 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.
: Stored.
Blank: Not stored.
These variables will be ignored if their names are not specified in step action.
SEE ALSO
See D3.2, “Sequence Table Block (ST16, ST16E),” for the details of sequence tables.
■ 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.
■ Step Execution
The sequence table one-shot step is oneshot-executed when its action is activated. The
sequence table block mode remains unchanged.
■ 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.
SEE ALSO
See D3.3, “Logic Chart Block (LC64),” for the details of logic chart.
■ 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.
■ Step Execution
The logic chart one-shot step is one-shot-executed when the step is activated. The logic
chart block mode remains unchanged.
■ 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.
• 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.
■ 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.
Main program
Interrupt steps
01 SIGNAL 1
02 RUN
03 STOP
04 PAUS
Developed
01
02
D050601E.EPS
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.
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
SEE ALSO
See D5.6.2, “Status Change Processing,” for more information.
SEE ALSO
See D5.6.3, “Interrupt Signal Processing,” for more information.
SEE ALSO
See D5.6.4, “Error Processing,” for more information.
■ Signal Declaration
Queue signals to be sent to the SFC block must be so declared in the initial step using the
“queue signal” statement.
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.
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.”
• 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).
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.
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.
creadpara(<parameter number>)
lreadpara(<parameter number>)
dreadpara(<parameter number>)
D050605E.EPS
......
01 Initial step queue signal "SG1" "SG2"
......
char*16 signame
J01
wait for qsignal signame
02 Waiting for signal
! Signal name set at signame.
......
J01 J01
D050606E.EPS
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.
......
01 Initial step queue signal "SG1" "SG2"
......
char*16 signame
J01
wait for qsignal signame (<expression>)
02 Waiting for signal
! Signal name set at signame.
......
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.
● 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.
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.
No
Is the command viable?
Yes
Executed as the
Status-change pre-process command is received.
No
Is the change feasible?
Yes
Status-change post-process
End
D050609E.EPS
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
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.
STOP
01 Pre-process
D050611E.EPS
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.
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.
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.
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.
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.
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.
D050616E.EPS
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:
• Using “quit” statement
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.
• Using “return” statement
Executing this statement terminates the process without executing the remaining
steps. Any operand specified in this statement will be ignored.
creadpara(<parameter number>)
lreadpara(<parameter number>)
dreadpara(<parameter number>)
D050617E.EPS
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:
• Using “quit” statement
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.
• Using “return” statement
Executing this statement terminates error processing without executing the remaining
steps. Any operand specified in this statement will be ignored.
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.
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.
Status-change pre- and post-processes can be executed when changing the block status
to STOP.
■ 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:
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.
SEE ALSO
D5.6.8, “Changing Current Step,” for the changing of data item STEPNO.
■ 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.
■ 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.
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.
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.
SEE ALSO
See C5.15.2, “Repeated Warning Alarm,” for more information.
■ 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.
■ 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
1 2 3
Control drawing 2
4 5 6
D050622E.EPS
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.
Basic type - -
None -
Trend
PV, SV, MV - -
D050623E.EPS
60.0
PAUSE PAUSE PAUSE
40.0
20.0
: Available
: Available
–: Not available
: 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.”
: Accessible
–: Not available
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
SEE ALSO
See D5.6.9, “SFC Block Alarm Processing,” for details.
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
SEE ALSO
See D5.6.1, “Queue Signal Processing,” for the details of queue signals.
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.
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"
......
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
• 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"
......
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.”
D050633E.EPS
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.”
Raw material
Cracked gas
Steam
Fuel
D060101E.EPS
System disconnection
Cooling
Steam introduction
Heating
D060102E.EPS
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
■ 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.
Enterprise
Site
Area
Process Cell
Figure ISA S88.01 Physical Model and CS 1000/CS 3000 Unit Supervision
Process Management
Unit Supervision
Process Control
(Function Block)
D060202E.EPS
Figure ISA S88.01 Control Activity Model and CS 1000/CS 3000 Unit Supervision
ISA S88.01
Procedural Control Model
Procedure
Procedure 01 Blending
02 Reaction
Scope of Unit Supervision
Unit instrument
Unit procedure
01 Charging A
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
● 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.
■ 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.
SEE ALSO
For details on recipe management and process management, refer to Part G, “Batch Management.”
*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.”
*1: The maximum number varies with the FCS database types.
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.”
*1: The maximum number varies with the FCS database types.
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.”
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.”
*1: The maximum number varies with the FCS database types.
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.”
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.”
● 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
Agitation
Charging 2
D060201E.EPS
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
D060202E.EPS
● 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
● 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
TIP
For the data display on [PV], [SV], [MV], it is required to define them in the monitoring operations or etc..
● 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.
● 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.
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.
OK Cancel
D060305E.EPS
• 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
10 Temperature = 240 C
20
30
40
Lot number = 30
OK Cancel
D060307E.EPS
● 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.
100.0
START START START
80.0
PAUSE PAUSE
60.0
SUSPEND SUSPEND
20.0
SEE ALSO
For details on status change commands, refer to D6.5.4, “Unit Mode and Unit Status Change Command.”
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
01 Initial step
Step
03 Heating 04 Agitation
Action
or
05 Analyzing
Operation (OPSFC)
06 Discharging 1 07 Discharging 2
08 Washing
09 Termination
D060402E.EPS
In the above example, the steps are executed successively as described. The heating and
agitation steps are executed simultaneously.
Transition Transition
Selective Seq.-Split
Selective Seq.-Join
Loop-Branch
Link
Loop-Join
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
10
D060404E.EPS
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.
01 Initialization
D060405E.EPS
● 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
■ 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
Link
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
■ Selective Sequence
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
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.
05
06 07 08
Simultaneous
sequence
09
10
D060410E.EPS
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.
05
06 07
Nested parallel
08 09 10 sequences
11
12
D060411E.EPS
■ 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
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
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.”
● 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"
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.”
SEE ALSO
See D6.14.1, “Queue Signal Processing” for the details on the interrupt processing upon a signal.
SEE ALSO
For details on FCS sequence library, refer to F8, “FCS Sequence Library.”
● Tag Name
Corresponding to the operation’s generic name, the actually used tag name for the opera-
tion may be specified.
Unit instrument A
Unit instrument B
D060416E.EPS
■ Available Modes
▼ Unit Mode
Available unit modes, which are system-specific, are shown below:
● 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.
IMPORTANT
When character string table USER2 is modified, the default State Transition Matrix (Ma-
trix1) will change its action accordingly.
■ 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
D060502E.EPS
● 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.
*1: SCOMP, STEP, and EXECERR commands are system-initiated (see below), user cannot issue the commands.
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.
Mode/status change
command processing starts.
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
Normal termination
signal is returned.
Command processing
completed.
D060504E.EPS
SEE ALSO
Refer to D6.6, “State Transition Matrix,” for the details of the state transition matrix.
● Transition Error
Error is caused if the change command is not defined in the status transition matrix.
● 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.”
■ 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.
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.
RUNNING END
PSTART
ABORT
PAUSE
SUSPEND
SUSPEND
PAUSED SUSPEND
ABORT ABORT
RESET
ABORTED
D060601E.EPS
RUNNING END
PSTART
ABORT
PAUSE
At start of
step execution
or SUSPEND
SUSPEND
PAUSED SUSPEND
ABORT ABORT
RESET
ABORTED
D060602E.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.
ABORTED AUT
SEMI
MAN
RUNNING AUT
SEMI SUSPEND, S, SUSP+
MAN
PAUSE AUT
SEMI
MAN
Data in the “status 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.
ABORTED AUT
SEMI
MAN
END AUT
SEMI
MAN
D060605E.EPS
Data in the “status 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.
SUSPEND AUT
SEMI
MAN
END AUT
SEMI
MAN
D060606E.EPS
Data in the “status 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.
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.
● 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.
● 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.
Create New
OK Cancel
D060610E.EPS
● 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.
● 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.
Ready
Current unit status Current unit mode Unit mode for transition
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.
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.”
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.”
NO NO
Is alarm-detection NO Is alarm-detection NO
group-suppression enabled? group-suppression enabled?
YES YES
YES NO
Subject alarm has already Subject alarm has already
been generated. been generated.
NO YES
NO
Processing ends. All alarms normalized.
YES
Processing ends.
D060701E.EPS
SEE ALSO
Refer to H1.9, “SEBOL Message Statements” for the details of SEBOL message statements.
■ Dialog 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 “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
This message can be written using an optional character string or a character string speci-
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.
SEE ALSO
See Operating Messages (IM 33S02H10-01E) for the details of message output formats.
SEE ALSO
Refer to H1.9.6, “sysalarm” for the details of SEBOL sysalarm statement.
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.
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
■ 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.
01 Initialization
Phase
07 Discharging NYN
D061001E.EPS
● Starting an Operation
An operation can be started only from a unit instrument. An operation can not be started
separately.
Interrupting Step
Transition Transition
Selective Seq.-Split
Selective Seq.-Join
Loop-Branch
Loop-Join
Connection
Jump Down Jnn nn: numerals
Link
D061002E.EPS
10
D061003E.EPS
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.
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.
01 Initialization
D061004E.EPS
01
Interrupting steps
02 RUN
03 STOP
04 PAUS
D061005E.EPS
● 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.”
Transition
06
07
D061006E.EPS
Link
Loop Join
Loop Branch
Jump To
J2 Jump Down
J1
J2
Jump Up
Jump To
J1
■ Selective Sequence
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
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.
• 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.
SEE ALSO
For details on FCS sequence library, refer to F8, “FCS Sequence Library.”
● Tag Name
Corresponding to the tag generic name, the actually used tag name may be specified.
D061011E.EPS
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.
■ Operation Mode
An operation may have the following modes. The modes of operation are system-fixed.
■ 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.
● 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
PAUS
ABRT (*1)
PAUS
PAUS RUN
(*3)
STOP
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.
• 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.
■ 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:
D061201E.EPS
TIP
Global variables cannot be accessed from the steps described in sequence table or logic chart.
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.
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:
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:
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.
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.
● 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.
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.
!action statement
[ VL301.MODE.MV = "MAN", 0]
[ VL302.MODE.MV = "MAN", 0]
.......
■ 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.”
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.”
● Example of Scripts
The following is an example of SEBOL step scripts:
!local variable declaration
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.
● 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.
● Example of Scripts
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.
!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.
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.
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.
● 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.
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 Name
The variable names for SFC/SEBOL return event message parameters are as following 4
types.
The names of both variables can be specified in one of the following four different manners:
• Operation data item
When storing data as a data item in the operation, 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.
<global variable>
• 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.
• 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 genname” in the initial step.
■ 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.
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.
Status-change pre- and post-processes can be executed when changing the block status
to STOP.
■ 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 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.
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.
SEE ALSO
See D6.13.4, “Changing Current Step,” for the changing of data item STEPNO.
■ 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.
■ 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.
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.
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.
SEE ALSO
See C5.15.2, “Repeated Warning Alarm,” for more information.
Operation
Main program
SEBOL
Interrupt programs
SEBOL
D061401E.EPS
Operation
Main program
Interrupt program
invoking
STOP processing
Emergency shutdown
Interrupt program
Emergency shutdown
Start of interrupt step
D061402E.EPS
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.
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
SEE ALSO
See D6.14.2, “Status Change Processing,” for more information.
SEE ALSO
See D6.14.3, “Interrupt Signal Processing,” for more information.
SEE ALSO
See D6.14.4, “Error Processing,” for more information.
*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.
■ Signal Declaration
Queue signals to be sent to the operation must be so declared in the initial step using the
“queue signal” statement.
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.
■ 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.
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.
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.
creadpara(<parameter number>)
lreadpara(<parameter number>)
dreadpara(<parameter number>)
D061408E.EPS
......
01 Initial step queue signal "SG1" "SG2"
......
char*16 signame
J01
wait for qsignal signame
02 Waiting for signal
! Signal name set at signame.
......
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.
......
01 Initial step queue signal "SG1" "SG2"
......
char*16 signame
J01
wait for qsignal signame (<expression>)
02 Waiting for signal
! Signal name set at signame.
......
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.
● Example of Referencing
When the queue has four signals, for example, referencing can be made as described
below:
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] = " "
No
Is the command viable?
Yes
Executed as the
Status-change pre-process command is received.
No
Is the change feasible?
Yes
Status-change post-process
End
D061412E.EPS
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
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.
STOP
01 Pre-process
D061414E.EPS
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.
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.
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.
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.
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.
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
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.
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
.....
■ 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.
D061419E.EPS
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:
• Using “quit” statement
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.
• Using “return” statement
Executing this statement terminates the process without executing the remaining
steps. Any operand specified in this statement will be ignored.
creadpara(<parameter number>)
lreadpara(<parameter number>)
dreadpara(<parameter number>)
D061420E.EPS
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:
• Using “quit” statement
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.
• Using “return” statement
Executing this statement can terminate error processing without executing the remain-
ing steps. Any operand specified in this statement will be ignored.
FCS starts.
Initialization
operation executed.
First time N
after system start?
Monitoring
operation starts.
starts.
Unit procedure
executed.
D061501E.EPS
FCS
Basic control
Software I/O
Faceplate blocks
SFC blocks
Options
D070001E.EPS
*1: ¡ £ Valve pattern monitoring and off-site blocks are available in CS 3000.
SEE ALSO
For information about the unit supervision function, refer to D6, “Unit Supervision.”
● 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
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
SOVP64 TUN
SOVP64
MODE = AUT ALRM : VPTN BSTS = RUN SOVP64
OWNER : SOUNT201
ENTRY [ 3, 64]
AUT RUN
VPTN
RUN
PAUSE
STOP
Ready
D070003E.EPS
● vpmstart Statement £
This statement secures the specified valve pattern monitor and makes it available.
● 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.”
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.
■ 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 £
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.”
Setup start
Remark
: Work flow
D070301E.EPS
SEE ALSO
For details on installing valve pattern monitoring function, refer to CS 3000 Installation (IM 33Q01C10-
01E).
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
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
Error code
Space (present station data) / s (other station data)
Parameter
Space (ALARM check not performed) / a (ALARM check performed)
Reference value
D070403E.EPS
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.
SEE ALSO
The error code is the same as the details of SEBOL error code. For the error code, refer to H1, “SEBOL
Details.”
● 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.
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.”
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.
RUN
vpmstart
statement RUN
STOP PAUS
STOP
STOP PAUS
D070601E.EPS
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.”
■ 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
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.
D070703E.EPS
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.
Monitoring cycle
VPM process timing VPM process timing
Abnormal Time
D070704E.EPS
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).
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
AFLS Alarm flashing status
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) .”
*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.
Unit
User Application
Monitoring operation
Signal transmission
Valve Pattern Monitor
Securing the valve
Operation pattern monitor
vpmstart SIO302.PV
Reference value (PV)
• Output
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
● <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.
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.
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
.....
drive vpmon '['<function block array> = <output value and parameter array>']'
[<error array'['*']'>][; error <label>[,<error identifier>]]
errorsub
D070803E.EPS
• 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.
• 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> £
Specifies a branch destination where processing at error generation is performed.
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.
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.”
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
Success
Success
Signal transmission
Failure
SGNL alarm is
generated.
End
D070806E.EPS
• 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.
● <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 branch destination where processing at error generation is performed.
● <error identifier> £
Specifies a local variable or a constant to identify the location where the error is generated
in the error processing unit.
SEE ALSO
For information about error codes, refer to H1, “SEBOL Details.”
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
ENTRY [1,3] VLV303 ENTRY [2,3] PV ENTRY [3,3] 1 0 D001
ENTRY [1,4] VLV304 ENTRY [2,4] PV ENTRY [3,4] 1 0
ENTRY [1,5] VLV305 ENTRY [2,5] PV ENTRY [3,5] 1 0 D001
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,1] VLV301 ENTRY [2,1] PV ENTRY [3,1] 1 0
ENTRY [1,2] ENTRY [2,2] ENTRY [3,2]
ENTRY [1,3] VLV303 ENTRY [2,3] PV ENTRY [3,3] 1 0 D001
ENTRY [1,4] VLV304 ENTRY [2,4] PV ENTRY [3,4] 1 0
ENTRY [1,5] VLV305 ENTRY [2,5] PV ENTRY [3,5] 1 0 D001
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.
ENTRY [1,1] VLV301 ENTRY [2,1] PV ENTRY [3,1] 1 0
ENTRY [1,2] ENTRY [2,2] ENTRY [3,2]
ENTRY [1,3] VLV303 ENTRY [2,3] PV ENTRY [3,3] 1 0 D001
ENTRY [1,4] VLV304 ENTRY [2,4] PV ENTRY [3,4] 1 0
ENTRY [1,5] ENTRY [2,5] ENTRY [3,5]
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.
ENTRY [1,1] VLV301 ENTRY [2,1] PV ENTRY [3,1] 1 0
ENTRY [1,2] ENTRY [2,2] ENTRY [3,2]
ENTRY [1,3] ENTRY [2,3] ENTRY [3,3]
ENTRY [1,4] VLV304 ENTRY [2,4] PV ENTRY [3,4] 1 0
ENTRY [1,5] ENTRY [2,5] ENTRY [3,5]
The above operation is performed in the same way by executing the vpmoff statement in
place of the drive vpmoff 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
• 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), 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>.
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.
● <error variable> £
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 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.
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.
vpmoff [V1.PV]
! V1.PV registration is deleted.
......
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
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.
*1 *2 *3
0 1 2 3 4 5 6 7 8 9
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.”
• 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.
• 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.
SEE ALSO
For information about a group assignment statement and compare statement, refer to H1, “SEBOL
Details.”
● <error variable> £
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 branch destination where processing at error generation is performed.
● <error identifier> £
Specifies a local variable or a constant to identify the location where the error is generated
in the error processing unit.
vpmoff [V1.PV]
! V1.PV registration is deleted.
......
vpmoff [V2]
! V2.PV,V2.MV registration is deleted.
......
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.”
● <error variable> £
Specifies a local variable where an error code is stored. A zero (0) is stored in this variable
if no error occurs.
● <label> £
Specifies a branch destination where processing at error generation is performed.
● <error identifier> £
Specifies an identifier to identify the location where the error is generated in the error
processing unit by a local variable or a constant.
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.”
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.
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 £
FCS2 FCS3
Completion Completion
D070903E.EPS
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.
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.
*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.
Signal (VPMSIG)
Unit
Valve pattern
1 Routine processing
monitor
Monitoring
operation VPMSIG signal reception
1 Interruption
Routine processing
1 Valve registration
Operation
2 Charging
D071101E.EPS
● 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.”
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.
5 Operation
Transition condition
6 Operation
D071102E.EPS
7 Operation
8 Operation
D071103E.EPS
return
IM 33S01B30-01E 4th Edition : Jan.11,1999-00
<Toc> <Ind> <D7.11 Example for Creating Application Program> D7-49
■ 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 genname VPM128 VPM03
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”
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.
Time
D071201E.EPS
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.
If the valve pattern monitor is put in the simulation mode during execution, it stops data
acquisition and inspection (valve monitoring).
■ 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
TANK
Product
storage tank
TANK
Supervisory computer
JOB JOB
controller controller
FCS
D080002E.EPS
FSBSET
Product
tank
Positive Control Loading arm
Pump
displacement valve (at port)
flowmeter
D080003E.EPS
Component configuration
Component ratios
FSBSET
FSBSET
FSBSET
Blend header
Product tank
PV collection
BLEND
Setting of setpoint or
operation command
FSBSET
FSBSET
Batch quantity
and flow rate
setting
FSBSET
FSBSET
Blend header
BLEND
FSBSET
D080005E.EPS
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
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.
Flow rate
setpoint
(SV)
CVK
Control step
0 20 22 24 21 22 23 26 0
(zone)
D080102E.EPS
The basic operation of the FSBSET during batch blending control is explained below. The
explanations are based on the above figure.
• 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.
Flow rate
setpoint
(SV)
t
Component cut-off
PI blending
Control status control End NON-Ctrl
Control step
22 25 26 0
(zone)
D080103E.EPS
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
D080104E.EPS
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
TMI
BLEND
D080105E.EPS
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).”
: available
N/A: not available
Cond.:available only from the switch block
: available
Maximum
flow rate
(KI/h)
Instantaneous
flow rate (Linear)
0% 100 %
Control valve opening (MV)
D080109E.EPS
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
The default is “1.000000.”
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).”
The default is “0.”
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).
The “Flow Rate Conversion Code After Correction” parameter of the Function Block Detail
Builder is set as follows:
• Flow Rate Conversion Code After Correction:
Select “0 (No)” or “1 (Yes).”
The default is “0.”
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.”
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.”
The default is “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.
: available
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.”
The default is “No.”
: available
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
Builder is set as follows:
• Momentary Deviation Alarm Hysteresis: 0 to (SHSL).
The default is a value equivalent to 1 %.
SH: Scale high limit
SL: Scale low limit
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
Builder is set as follows:
• Accumulated Deviation Alarm Hysteresis: 0.00 to 10000.00.
The default is “10.00.”
SVH
(Final flow
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)
Monitor Monitor
t6: Check mask time (set in builder)
t7: Check time (set in builder)
D080116E.EPS
SEE ALSO
For the details of each control step, see D8.1.8, “Control Processing of Batch Set Control Block
(FSBSET).”
: available
: available
● 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
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 default is “10.”
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.
1000 1
QE (liters)=SV (%) • Max. flow (kl/h) • T (sec) • •
3600 2 D080124E.EPS
SV
T= • T (sec) + a (sec)
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.
● 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.
SVH
(Final flow
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
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
Control step
0 20 22 24 21 22 23 26 0
(zone)
D080129E.EPS
Figure Action of Batch Set Control Block (FSBSET) by Operation Commands (Components in
Blending) £
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)
D080130E.EPS
Figure Component Cut-Off Action of Batch Set Control Block (FSBSET) by Operation Command
(Components in Blending) £
PI blending control or
PI BLENDING
22 instantaneous deviation CAS
CONTROL
control
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
SEE ALSO
For the leakage check, see D8.1.7, “Alarm and Notification Processing of Batch Set Control Block
(FSBSET).”
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
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).
SEE ALSO
For the details of early-point detection processing, see “■ Common Processing - FSBSET” in this section.
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
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).
MP
M
T
MV
(%)
t
T: Control period
(a) MP
MV
D080135E.EPS
If the MP is larger than the current value, throttling back starts from the current value.
M
T
MV
(%)
t
T: Control period
(b)MPMV
D080136E.EPS
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 %.
The default is “50.000 %.”
SV
Flow rate MV
setpoint M
(%)
T
SVPR
t
Steady Early P.B.Ctrl
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
The figure below shows the throttling process until SV0 is reached:
T
ME
SV
(%)
t
T: Control period
D080139E.EPS
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
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 %.
The default is “50.000 %.”
The “Batch End Detection during Emergency Shutdown” parameter of the Function Block
Detail Builder are set 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.
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.”
T
MR
MV
(%)
t
T: Control period
D080143E.EPS
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 %
The default is “2.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
● 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.
(f)
(e)
(c)
(b)
1 2 3 4 5 6 (g) 7
P.B.
SET UP Steady Early Wait End
Ctrl
(d)
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
£
: entry possible
Cond.:entry possible under certain conditions
N/A: entry not possible
: entry possible
Cond.:entry possible under certain conditions
N/A: entry not possible
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.”
(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
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)
D080202E.EPS
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
Supervisory computer
(JOB controller)
MOD1 (=0, 1, 2)
• •
• •
• •
• •
• •
• •
D080204E.EPS
Release DT . . . 1 1
“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.
Releasing command
Each
variable MR
(%)
SV
PV
Releasing end
T
t
T: Control period
D080206E.EPS
Supervisory computer
Control buffer
Shipment port
Tag name (1) tag name
•
•
•
Data transition
Tag name (6) processing
D080207E.EPS
D080208E.EPS
: available
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).”
: available
SEE ALSO
As for when to perform component command setting, see D8.2.9, “Control Processing of Blending Master
Control Block (BLEND).”
Table Table of Alarm and Notification Processing Items for Blending Master Control Block
(BLEND) £
Alarm Processing
No. Processing Item Provided Remarks
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
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
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
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.
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 %.
The default is “1.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).
The default is “10.”
● 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.
T
Hold SV value
MPSV
BLEND
MPDN MPUP
(Step-down (Step-up increment)
increment)
MPSPSV
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
● 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.”
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
Block mode AUT or CAS Start mode AUT or CAS Start mode
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
Component Block
MAN CAS CAS MAN
(FSBSET) mode
Control
step 0 20 22 24 21 22 23 26 0
(zone)
D080219E.EPS
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)
CAS
8 EMST Multistage decrease of SV
(AUT)
BLEND CAS
31 Performs blending control.
CONTROL (AUT)
SVH
or
SV SVL
(%)
t t
SET-UP
Start
increment
Set Up Set Down
D080221E.EPS
Flow rate SV
setpoint
(%) S
T
SVPR
t
Steady Early P.B.Ctrl
D080222E.EPS
In this step, emergency stop processing, batch-end detection processing and SV distribu-
tion processing are performed as common processing.
The “Configuring Devices Clear at Batch End” parameter of the Function Block Detail
Builder is set as follows:
• Configuring Devices Clear at Batch End: Select “Yes” or “No.”
The default is “No.”
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
Port FSBSET SV
(%)
t
t6
BLEND component
FSBSET SV
(%)
t
Figure Start Delay for Port FSBSET Blocks and Component FSBSET Blocks £
(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
Figure Control Step Transition Diagram of Blending Master Control Block (BLEND) £
: entry possible
Cond.:entry possible under certain conditions
N/A: entry not possible
: entry possible
Cond.:entry possible under certain conditions
N/A: entry not possible
: entry possible
Cond.:entry possible under certain conditions
N/A: entry not possible
: entry possible
Cond.:entry possible under certain conditions
N/A: entry not possible