Function Blocks Reference Vol.1

Introduction Page 1 of 1
Introduction
The integrated production control system CENTUM VP is the products of distributed control system
(DCS) for large and medium-small scale process control.
This manual is written for use as a part of reference manual describing the functional details of
CENTUM VP. This manual focuses on the function block details. You can read the required chapters
when you need the details of function blocks.
In this user's manual, FFCS, FFCS-L, FFCS-V, and FFCS-C are referred to as "FFCS series" or "FFCS
series FCS." If the individual types of FCS need to be particularly mentioned, the FCSs may be
described respectively with their particular types.
This user's manual consists of the following chapters:
• Chapter 1 Regulatory Control
This chapter describes the detailed descriptions on all the regulatory control blocks except the
FOUNDATION fieldbus faceplate blocks.
file:///C:/Program%20Files%20(x86)/YOKOGAWA/IA/iPCS/Products/CENTUMVP/Pr... 8/6/2022
Safety Precautions for Use Page 1 of 2
Safety Precautions for Use

Safety, Protection, and Modification of the Product
• To protect the system controlled by the Product and the Product itself and to ensure safe
operation, please observe the safety precautions described in this Manual. Yokogawa Electric
Corporation ("YOKOGAWA") assumes no liability for safety if users fail to observe the safety
precautions and instructions when operating the Product.
• If the Product is used in a manner not specified in the User's Manuals, the protection provided by
the Product may be impaired.
• If any protection or safety circuit is required for the system controlled by the Product or for the
Product itself, please install it externally.
• Be sure to confirm the specifications and required settings of the devices that are used in
combination with the Product by referring to the instruction manual or other documents of the
devices.
• Use only spare parts that are approved by YOKOGAWA when replacing parts or consumables of
the Product.
• Do not use the Product and its accessories such as power cords on devices that are not approved
by YOKOGAWA. Do not use the Product and its accessories for any purpose other than those
intended by YOKOGAWA.
• Modification of the Product is strictly prohibited.
• The following symbols are used in the Product and User's Manuals to indicate the accompanying
safety precautions:
Indicates that caution is required. This symbol for the Product indicates the possibility of
dangers such as electric shock on personnel and equipment, and also indicates that the
user must refer to the User’s Manuals for necessary actions. In the User’s Manuals, this
symbol is used together with a word “CAUTION” or “WARNING” at the locations where
precautions for avoiding dangers are described.
Indicates that caution is required for hot surface. Note that the devices with this symbol
become hot. The risk of burn injury or some damages exists if the devices are touched or
contacted.
Identifies a protective conductor terminal. Before using the Product, you must ground the
protective conductor terminal to avoid electric shock.
Identifies a functional grounding terminal. A terminal marked "FG" also has the same
function. This terminal is used for grounding other than protective grounding. Before using
the Product, you must ground this terminal.
Indicates an AC supply.
Indicates a DC supply.
Safety Precautions for Use Page 2 of 2
Indicates that a component such as a power supply switch is turned ON.

Indicates that a component such as a power supply switch is turned OFF.
Notes on Handling User's Manuals

• Hand over the User's Manuals to your end users so that they can keep the User's Manuals on
hand for convenient reference.
• Thoroughly read and understand the information in the User's Manuals before using the Product.
• For the avoidance of doubt, the purpose of the User's Manuals is not to warrant that the Product
is suitable for any particular purpose but to describe the functional details of the Product.
• Contents of the User's Manuals are subject to change without notice.
• Every effort has been made to ensure the accuracy of contents in the User's Manuals. However,
should you have any questions or find any errors, contact us or your local distributor. The User's
Manuals with unordered or missing pages will be replaced.
Warning and Disclaimer

• Except as specified in the warranty terms, YOKOGAWA shall not provide any warranty for the
Product.
• YOKOGAWA shall not be liable for any indirect or consequential loss incurred by either using or
not being able to use the Product.
Notes on Software
• YOKOGAWA makes no warranties, either expressed or implied, with respect to the Software
Product's merchantability or suitability for any particular purpose, except as specified in the
warranty terms.
• Purchase the appropriate number of licenses of the Software Product according to the number of
computers to be used.
• No copy of the Software Product may be made for any purpose other than backup; otherwise, it
is deemed as an infringement of YOKOGAWA's Intellectual Property rights.
• Keep the software medium of the Software Product in a safe place.
• No reverse engineering, reverse compiling, reverse assembling, or converting the Software
Product to human-readable format may be performed for the Software Product.
• No part of the Software Product may be transferred, converted, or sublet for use by any third-
party, without prior written consent from YOKOGAWA.
Documentation Conventions Page 1 of 2
Documentation Conventions
Symbols
The following symbols are used in the User's Manuals.
Indicates precautions to avoid a danger that may lead to death or severe
injury.
Indicates precautions to avoid a danger that may lead to minor or

moderate injury or property damage.
Indicates important information required to understand operations or

functions.
Indicates additional information.
Indicates referenced content.

In online manuals, you can view the referenced content by clicking the
links that are in green text. However, this action does not apply to the
links that are in black text.
Typographical Conventions
The following typographical conventions are used throughout the User's Manuals.
Commonly Used Conventions throughout the User's Manuals

• Character string to be entered
The characters that must be entered are shown in monospace font as follows:
Example:
FIC100.SV=50.0
• ▼ Mark
This symbol indicates the description for an item for which you should make a setting in the
product's engineering window.
While operating an engineering window, the help information for the selected item can be
accessed from "Builder Definition Items" in the Help menu. Listing more than one definition item
after this symbol implies that the paragraph on the page describes more than one definition
items.
Example:
▼ Tag Name, Station Name
• Δ Mark
Indicates that a space must be entered between character strings.
Example:
.ALΔPIC010Δ-SC
• Character string enclosed by braces { }

Indicates character strings that may be omitted.
Example:
Documentation Conventions Page 2 of 2
.PRΔTAG{Δ.sheet name}
Conventions Used to Show Key or Button Operations

• Characters enclosed by brackets [ ]
When characters are enclosed by brackets in the description of a key or button operation, it
indicates a key on the keyboard, a key on the operation keyboard, a button name in a window,
or an item in a list box displayed in a window.
Example:
To alter the function, press the [ESC] key.
Conventions Used in Command Syntax or Program Statements

The following conventions are used within a command syntax or program statement format:
• Characters enclosed by angle brackets < >
Indicate character strings that user can specify freely according to certain guidelines.
Example:
#define <Identifier> <Character string>
• "..."
Indicates previous command or argument that may be repeated.
Example:
Imax (arg1, arg2, ...)
• Characters enclosed by brackets [ ]

Indicate character strings that may be omitted.
Example:
sysalarm <format character string> [, <output value>…]
• Characters enclosed by separators | |

Indicates character strings that can be selected from more than one option.
Example:
Drawing Conventions
Drawings used in the User's Manuals may be partially emphasized, simplified, or omitted for the
convenience of description.
Drawings of windows may be slightly different from the actual screenshots with different settings or
fonts. The difference does not hamper the understanding of basic functionalities and operation and
monitoring tasks.
Copyright and Trademark Notices Page 1 of 1
Copyright and Trademark Notices

All Rights Reserved
The copyright of the programs and online manuals contained in the software medium of the
Software Product shall remain with YOKOGAWA.
You are allowed to print the required pages of the online manuals for the purposes of using or
operating the Product; however, reprinting or reproducing the entire document is strictly prohibited
by the Copyright Law.
Except as stated above, no part of the online manuals may be reproduced, transferred, sold, or
distributed to a third party in any manner (either in electronic or written form including, without
limitation, in the forms of paper documents, electronic media, and transmission via the network).
Nor it may be registered or recorded in the media such as films without permission.
Trademark Acknowledgements
• CENTUM, ProSafe, Vnet/IP, PRM, Exaopc, Exapilot, Exaquantum, Exasmoc, Exarqe, Multivariable
Optimizing Control/Robust Quality Estimation, StoryVIEW and FieldMate Validator are the
registered trademarks or trademarks of Yokogawa Electric Corporation.
• The names of corporations, organizations, products and logos herein are either registered
trademarks or trademarks of Yokogawa Electric Corporation and their respective holders.
1. Regulatory Control Page 1 of 1
1. Regulatory Control
The regulatory control performs control computation processing using analog process values for
process monitor and process control. The function blocks that provide the regulatory control function
are referred as “regulatory control blocks.”
This chapter presents a detailed description of the function of each of the regulatory control blocks,
excluding the FOUNDATION fieldbus faceplate block.
SEE For more information about the FOUNDATION fieldbus faceplate blocks, refer to:
ALSO A2., “Overview of FF Faceplate Blocks” in FOUNDATION fieldbus Reference (IM 33J20T10-01EN)
Regulatory Control Positioning

The regulatory control is one of the basic controls in the FCS and performs control computation
processing to monitor and control processes. The function blocks that perform the this regulatory
control are referred as “regulatory control blocks.”
The regulatory control blocks include Input indication blocks, controller blocks, manual loader blocks,
signal set blocks, signal limiter blocks, Signal selector blocks, signal distribution blocks, pulse-count
blocks, alarm blocks and YS blocks.
The figure below shows the position of the regulatory control function in the basic control architecture:
Figure 1-1 Regulatory Control Block in the Basic Control Function Architecture
1.1 Regulatory Control Blocks Page 1 of 2
1.1 Regulatory Control Blocks

The regulatory control blocks are the function blocks that perform control computation processing
mainly on the analog input as input signals. The calculated results are used for process monitor and
process control.
The regulatory control blocks support the following types of processing: input processing, control
computation processing, output processing and alarm processing.
This section describes the structure and processing of regulatory control blocks.
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 1.2 for each function block.
SEE For more information about the input processing that are common to various types of regulatory
ALSO control blocks, refer to:
3., “Input Processing” in Function Blocks Overview (IM 33J15A20-01EN)
For more information about output processing that are common to various types of regulatory
control blocks, refer to:
4., “Output Processing” in Function Blocks Overview (IM 33J15A20-01EN)
For more information about alarm processing that are common to various types of regulatory
control blocks, refer to:
5., “Alarm Processing – FCS” in Function Blocks Overview (IM 33J15A20-01EN)
Structure of Regulatory Control Blocks

The function blocks that provide the regulatory control function are called “regulatory control blocks.”
The regulatory control blocks perform control computation processing mainly on analog signals
(analog values) as input values. The results of control computation processing performed by the
regulatory control blocks are output as manipulated output values (MV).
The figure below shows a function block diagram of a general regulatory control block:
Figure 1.1-1 Function Block Diagram of the Regulatory Control Block
1.1 Regulatory Control Blocks Page 2 of 2
• IN: Input terminal

• SET: Setpoint value input terminal
• BIN: Compensation input terminal
• RLn: Reset signal input terminal
• TIN: Tracking signal input terminal
• TSI: Tracking switch input terminal
• INT: Interlock switch input terminal
• SUB: Auxiliary output terminal
• OUT: Output terminal
• RAW: Raw data input signal
• PV: Process variable
• SV: Setpoint value
• CSV: Cascade setpoint value
• RSV: Remote setpoint value
• VN: Compensated value Input
• RMV: Remote manipulated output value
• RLVn: Reset signal
• MV: Manipulated output value
• TSW: Tracking switch
Functions of the Regulatory Control Blocks

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

Performs control computation processing by reading the process variable (PV) and outputs a
manipulated output value (MV).
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 processing.
1.1.1 Types of the Regulatory Control Blocks Page 1 of 3
1.1.1 Types of the Regulatory Control Blocks

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

The table below shows a list of input indicator blocks:
Table 1.1.1-1 Input Indicator Blocks
Block type Code Name

PVI Input Indicator Block
Input indicators
PVI-DV Input Indicator Block with Deviation Alarm
Controller Blocks
The table below shows a list of controller blocks:
Table 1.1.1-2 Controller Blocks

PID PID Controller Block
PI-HLD Sampling PI Controller Block
PID-BSW PID Controller Block with Batch Switch
ONOFF 2-Position ON/OFF Controller Block
ONOFF-E Enhanced 2-position ON/OFF Controller Block(*1)
ONOFF-G 3-Position ON/OFF Controller Block
Controllers
ONOFF-GE Enhanced 3-position ON/OFF Controller Block(*1)
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
ZWOPID (*2) PID Controller with Output Loss Compensation for Wireless Block (*3)
*1: This type of function blocks can be applied to all field control stations except standard PFCS.
*2: This function block requires PID with Packet Loss Compensation Package (for Field Wireless).
*3: This type of function block can be applied to FFCS-C and FFCS-V.
Manual Loader Blocks

The table below shows a list of manual loader blocks:
Table 1.1.1-3 Manual Loader Blocks

MLD Manual Loader Block
MLD-PVI Manual Loader Block with Input Indicator
MLD-SW Manual Loader Block with Auto/Man Switch
Manual Loader MC-2 2-Position Motor Control Block
MC-2E Enhanced 2-Position Motor Control Block (*1)
MC-3 3-Position Motor Control Block
MC-3E Enhanced 3-Position Motor Control Block (*1)
*1: This type of function blocks can be applied to all field control stations except standard PFCS.
Signal Setter Blocks

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

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

The table below shows the signal limiter block:
Table 1.1.1-5 Signal Limiter Block

Signal Limiters VELLIM Velocity Limiter Block
Signal Selector Blocks

The table below shows a list of Signal selector blocks:
Table 1.1.1-6 Signal Selector Blocks

AS-H/M/L Autoselector Block
Signal selectors SS-H/M/L Signal Selector Block
SS-DUAL Dual-Redundant Signal Selector Block
Signal Distributor Blocks

The table below shows a list of signal distributor blocks:
Table 1.1.1-7 Signal Distributor Blocks

FOUT Cascade Signal Distributor Block
FFSUM Feedforward Signal Summing Block
Signal Distributors
XCPL Non-Interference Control Output Block
SPLIT Control Signal Splitter Block
Alarm Block
The table below shows the alarm block:
Table 1.1.1-8 Alarm Block

Alarm ALM-R Representative Alarm Block
Pulse Count Input Block

The table below shows the pulse count input connection block:
Table 1.1.1-9 Pulse Count Input Connection Block

Pulse Count Input Connection Block PTC Pulse Count Input Block
YS Blocks
The table below shows the YS blocks:
Table 1.1.1-10 YS Blocks

SLCD YS Controller Block
SLPC YS Programmable Controller Block
SLMC YS Programmable Controller Block with Pulse-Width Output
SMST-111 YS Manual Station Block with SV Output
SMST-121 YS Manual Station Block with MV Output Lever
YS instrument
SMRT YS Ratio Set Station Block
SBSD YS Batch Set Station Block
SLCC YS Blending Controller Block
SLBC YS Batch Controller Block
STLD YS Totalizer Block
1.1.2 I/O Data Handled by the Regulatory Control Blocks Page 1 of 4
1.1.2 I/O Data Handled by the Regulatory Control Blocks

As a rule, the data transmitted via I/O terminals handled by the regulatory control blocks must be
the engineering unit data. Each data item consists of data value and data status.
Data Value
The data value is a numeric data that is transmitted in or out of a function block. The data values
handled by the blocks include process variable (PV), cascade setpoint value (CSV) and manipulated
output value (MV).
The data values handled by the regulatory control blocks are numeric data in engineering unit.
However, the data received from the input modules (excluding the input modules for temperature
measurement as well as for pulse trains) and the setpoint data sent to analogue 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 connection 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 For more information about the details of data status, refer to:
ALSO 6.4, “Data Status” in Function Blocks Overview (IM 33J15A20-01EN)
Input Data
The input data is numeric data that the function blocks read from input terminals.
The types of input data are shown below:
• Process variable (PV)
• Setpoint value (SV), cascade setpoint value (CSV), remote setpoint value (RSV)
• Input signal values (RV1, RV2, RV3)
• Reset limit values (RLV1, RLV2)
• Input or Output Compensated value (VN)
• Tracking switch (TSW)
Process Variable (PV)

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

Setpoint Value (RSV)
The engineering unit and scale range of the setpoint value (SV), cascade setpoint value (CSV) and
remote setpoint value (RSV) agree with the engineering unit and scale range of the process variable
(PV) except in the function blocks shown below:
Table 1.1.2-1 Engineering Unit Symbol and Scale Range of the Setpoint Value (SV), Cascade
Setpoint Value (CSV) and Remote Setpoint Value (RSV)
Function Blocks Engineering unit symbol and Scale Range

Ratio Set Block (RATIO)
Velocity Limiter Block (VELLIM)
Control Signal Splitter Block
(SPLIT) Use the Function Block Detail Builder to set the engineering unit symbol
and scale range of SV for the function blocks shown to the left.
Cascade Signal Distributor Block The engineering unit and scale range of CSV and RSV are same as those
(FOUT) of SV. The FOUT and FFSUM blocks have no RSV.
Feedforward Signal Summing
Block (FFSUM)
YS Ratio Set Station Block (SMRT)
Motor Control Blocks (MC-2, MC-
2E, MC-3, and MC-3E)
13-Zone Program Set Block (PG- The engineering unit symbol and scale range of the function blocks
L13) shown to the left are fixed for each block.
Representative Alarm Block (ALM-
R)
Input Signal Values (RV1, RV2, RV3)

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

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

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

The data handled by the tracking switch (TSW) for the TSI terminal must be an integer value of “0”
or “1.” “1” and “0” indicate ON and OFF, respectively.
Output Data
The output data is a numeric data value that is written out of a function block via an output terminal.
The types of output data are shown below:
• Manipulated output value (MV)
• Auxiliary output values (PV, ΔPV, MV, ΔMV)
• Process variable (PV)
Manipulated Output Value (MV)

▼ MV Display Style
Use the Function Block Detail Builder to set the display form for the manipulated output value (MV).
• MV Display Style
Select “Automatic Determination” or “User Define.”
The default is “Automatic Determination.”
When “Automatic Determination” is selected, the engineering unit and scale range of the
manipulated output value (MV) change according to the connected destination of the OUT terminal.
• If the connection destination is a process I/O, the scale range and engineering unit of the
manipulated output value (MV) is fixed to “0 to 100” and “%,” respectively. However, 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 engineering 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 manipulated output
value (MV). The engineering unit and the range should be the same as the output destination.
• 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.”
• Event when the user wants to display the MV in percentage on HIS

faceplate, there is no need to change the setting for [MV Display Style] -
[User-Define] to 0 % - 100 %. The setting in this field should be kept the
same as the output destination; but to change the setting [MV Display on
Faceplate] from [Indicate Actual Quantity] to [Indicate %].
• If you set the output range to values that are different from the output
destination in the Function Block Detail Builder, the MV-related parameters
may have a value outside the MV range after online downloading due to
output range tracking. If the parameter value goes beyond the range,
manually set it to a value within the range. If you repeat online
downloading with out-of-range parameter values, the function block will
end up in an overflow and stop operation.
Auxiliary Output Values (PV, ΔPV, MV, ΔMV)

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

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

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

Block
Table 1.1.3-1 Input Processing Possible for Each Regulatory Control Block
Input signal conversion Digital filter Totalizer PV Overshoot CAL

Model
(*1) (*1) (*1) (*1) (*1)
PVI
PVI-DV
PID
PI-HLD
PID-BSW
ONOFF
ONOFF-E B/A/R/Pb/Sb/L x x x x
ONOFF-G
ONOFF-GE
PID-TP
PD-MR
PI-BLEND
PID-STC
ZWOPID B/A/R/Sb/L x x x x
MLD
MLD-PVI B/A/R/Pb/Sb/L x x x x
MLD-SW
MC-2
MC-2E
S2/S3/L x
MC-3
MC-3E
RATIO (*2) B/A/R/Pb/Sb/L x x x x
PG-L13
BSETU-2 B/A/R/Pb/Sb/L x x x x
BSETU-3 B/A/C/Sb x x
VELLIM
SS-H/M/L
AS-H/M/L
SS-DUAL
B/A/Sb/L x x x x
(*3)
FOUT
FFSUM
XCPL
SPLIT
PTC (*4) (*4) x
ALM-R
SLCD B/R x x
SLPC x x
SLMC x x
SMST-111 x x
SMST-121 x x
SMRT x x
SBSD (*5) x
SLBC (*5) x
SLCC (*5) x
STLD (*5) x
*1: B: No conversion (function block)
A: No conversion (analog input)
R: Square root conversion (analog input)
Pb: Pulse-train input conversion
S2: Two-position status input (for MC-2/3 and MC-2E/3E only)
S3: Three-position status input (for MC-2/3 and MC-2E/3E only)
C: Code input (for BSETU-3 only)
Sb: Subsystem input
L: PV limit
x: Exists
Blank: Not exist
*2: The input processing will not function when the data setting is performed to the PV by cascade
connection.
*3: The input processing is performed against the input signal on the selected side.
*4: Performs a PTC block independent processing
*5: Display the sum of YS Instrument.
Output Processing Possible for Each Regulatory Control

Block
Table 1.1.3-2 Output Processing Possible for Each Regulatory Control Block
Output Output signal

Output Velocity Clamped Output Auxiliary
Model PMV range conversion
limit limit output tracking output(*1)
tracking (*2)
PVI
P/Pd B/A/Sb
PVI-DV
PID
x x x x x x P/Pd/M/Md B/A/Pw/Pwf/Sb
PI-HLD
PID-
x x x x x x P/Pd/M/Md B/A/Pwf/Sb
BSW
ONOFF x P/Pd S2
ONOFF-
E x (*3) P/Pd S2
ONOFF-
x P/Pd S3
G
ONOFF-
x (*3) P/Pd S3
GE
PID-TP x x (*4) x P/Pd/M/Md D
PD-MR x x x x x x P/Pd/M/Md B/A/Pwf/Sb
PI-
BLEND x x x x x x P/Pd/M/Md B/A/Pw/Pwf/Sb
PID-STC
ZWOPID x x x x x x P/Pd/M/Md B/A
MLD x x (*3) x M/Md B/A/Pwf/Sb
MLD-PVI x x (*3) x P/Pd/M/Md B/A/Pwf/Sb
MLD-SW x x x x (*3) x M/Md B/A/Pwf/Sb
MC-2 x S2/P2
MC-2E x S2/P2
MC-3 x S3/P3
MC-3E x S3/P3
RATIO x x x x x x P/Pd/M/Md B/A/Pwf/Sb
PG-L13 (*5) x x x B/A/Sb
BSETU-2 x x x B/A/S2b/S3b/
BSETU-3 x x x S2s/S3s/Sb
VELLIM x x x x x x M/Md B/A/Sb

SS-
B/A/Sb
H/M/L
AS-
x x x x x x B/A/Sb
H/M/L
SS-DUAL B/A/Sb
FOUT (*6) x x B
FFSUM x x x x x x P/Pd/M/Md B/A/Pwf/Sb
XCPL x x x x x x M/Md B/A/Pwf/Sb
SPLIT x x x x B/A
PTC (*7)
ALM-R
YS
Blocks
(*8)
*1: P: PV
Pd: ΔPV
M: MV
Md: ΔMV
*2: 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
*3: Selectable by builder setting.
*4: 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].
*5: Always restricted by MSH/MSL
*6: Only tracking of the CLP ± status of the output destination is performed.
*7: Performs processing unique to PTC block.
*8: YS Blocks contain the following models:
SLCD, SLPC, SLMC, SMST-111, SMST-121, SMRT, SBSD, SLBC, SLCC, STLD.
Alarm Processing Possible for Each Regulatory Control

Table 1.1.3-3 Alarm Processing Possible for Each Regulatory Control Block-1
Process alarms (*1)

Model
NR OOP IOP IOP- HH LL HI LO
PVI
x x x x x x x
PVI-DV
PID
PI-HLD
PID-BSW
ONOFF
ONOFF-E
ONOFF-G
x x x x x x x x
ONOFF-GE
PID-TP
PD-MR
PI-BLEND
PID-STC
ZWOPID
MLD x x
MLD-PVI x x x x x x x x
MLD-SW x x x x
MC-2
MC-2E
x x x x x x
MC-3
MC-3E
RATIO x x x x x x x x
PG-L13 x x x x
BSETU-2
x x x x x x x
BSETU-3
VELLIM x x x x
SS-H/M/L x x x
AS-H/M/L x x x x
SS-DUAL x x x x x x x
FOUT (*2)
FFSUM x x x x
XCPL x x x x
SPLIT x x
PTC x x x
ALM-R x
SLCD x x x x x x
SLPC x x x x x x
SLMC x x x x x x
SMST-111 x x x x x x
SMST-121 x x x x x x
SMRT x x x x x x
SBSD x x x x
SLBC x x x x
SLCC x x x x
STLD x x x x
*1: x: Available
Blank: Not available
*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.
Table 1.1.3-4 Alarm Processing Possible for Each Regulatory Control Block-2
Process alarms (*1)

Model Other
DV+ DV- VEL+ VEL- MHI MLO CNF
alarms
PVI x x x
PVI-DV x x x x x
PID
x x x x x x x
PI-HLD
PID-BSW
ONOFF
ONOFF-E x x x x x
ONOFF-G
ONOFF-GE
PID-TP
x x x x x x x
PD-MR
HDV
PI-BLEND x x x x x
LDV
PID-STC
x x x x x x x
ZWOPID
MLD x
MLD-PVI x x x
MLD-SW x x x
MC-2 TRIP
MC-2E PERR
x ANS+
MC-3 ANS-
MC-3E INT
RATIO x x x x x Not available

PG-L13 x Not available
NPLS (*2)
BSETU-2 BDV+
BDV-
x
LEAK
BSETU-3 BEND
BPRE
VELLIM x x x x x Not available
SS-H/M/L x
AS-H/M/L x x x
SS-DUAL x x x x x
FOUT (*3)
FFSUM x x x
XCPL x x x
SPLIT x
PTC x
HALM
MALM
ALM-R x
LALM
RALM
SLCD x x x
SLPC x x x
SLMC x x x
SMST-111 x
SMST-121 x
SMRT x
END
SBSD x PRE
LEAK
END
SLBC x PRE
LEAK
SLCC x x HDV
STLD x
*1: x: Available
Blank: Not available
*2: The NPLS alarm is only supported in the BSETU-2 but not in the BSETU-3.
*3: 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.
1.1.4 Valid Block Modes for Each Regulatory Control Block Page 1 of 2
1.1.4 Valid Block Modes for Each Regulatory Control Block

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

Table 1.1.4-1 Valid Basic Block Modes for Each Regulatory Control Blocks
Basic block modes(*1)

Model Name of function block
O/S IMAN TRK MAN AUT CAS PRD RCAS ROUT
PVI Input indicator block
Input indicator block with x - - - x - - - -
PVI- DV
deviation alarm
PID PID controller block
PI-HLD Sampling PI controller block
x x x x x x x x x
PID controller block with
PID-BSW
batch switch
Two-position ON/OFF
ONOFF
controller block
Enhanced two-position
ONOFF-E
ON/OFF controller block
ONOFF- Three-position ON/OFF
x x - x x x - x x
G controller block
ONOFF- Enhanced three-position
GE ON/OFF controller block
Time-proportioning ON/OFF
PID-TP
controller block
PD controller block with
PD-MR x x x x x x x x x
manual reset
PI-
Blending PI controller block x x x x x x - x x
BLEND
Self-tuning PID controller
PID-STC
block
PID Controller with Output x x x x x x x x x
ZWOPID Loss Compensation for
Wireless block
MLD Manual loader block
Manual loader block with x x x x - - - - -
MLD-PVI
input indicator
Manual loader block with
MLD-SW x x x x x Δ - - -
Auto/Man SW
Two-position motor control
MC-2
block
Enhanced two-position motor
MC-2E
control block
x x x x x x - - x
Three-position motor control
MC-3
block
Enhanced three-position
MC-3E
motor control block
1.1.4 Valid Block Modes for Each Regulatory Control Block Page 2 of 2
RATIO Ratio set block x x x x x x - x x

PG-L13 13-zone program set block x x - x x x - - -
BSETU -
Flow-totalizing batch set block
2
x x - x x - - - -
BSETU - Weight-totalizing batch set
3 block
VELLIM Velocity limiter block x x - x x x - x x
SS-
Signal selector block x - - - x - - - -
H/M/L
AS-
Autoselector block x x - x x - - - -
H/M/L
Dual-redundant signal
SS-DUAL x - - - x - - - -
selector block
Cascade signal distributor
FOUT - - - - - - - - -
block
Feedforward signal summing
FFSUM x x x x x x - - -
block
Non-inteference control
XCPL x x x x x - - - -
output block
SPLIT Control signal splitter block x x - - x x - x -
PTC Pulse count input block x - - - x - - - -
ALM-R Representative alarm block x - - - x - - - -
SLCD YS controller block x x - x x x - x x
YS programmable controller
SLPC x x - x x x - x x
block
YS programmable controller
SLMC x x - x x x - x x
block with pulse-width output
SMST- YS manual station block with
x x - x - x - x -
111 SV output
SMST- YS manual station block with
x x - x - x - - x
121 MV output lever
SMRT YS ratio set station block x x - x x x - x x
SBCD YS batch set station block x x - - x - - x -
SLCC YS blending controller block x x - x x - - x x
SLBC YS batch controller block x x - x x - - x x
STLD YS totalizer block x x - - x - - x -
*1: x: Valid
-: Invalid
Δ: For MLD-SW, CAS mode can be specified instead of AUT mode.
1.2 Input Indicator Block (PVI) Page 1 of 3
1.2 Input Indicator Block (PVI)

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

▼ Connection
The figure below shows a function block diagram of the Input Indicator Block (PVI):
Figure 1.2-1 Function Block Diagram of Input Indicator Block (PVI)
The table below shows the connection method and connected destination of the I/O terminals of the
Input Indicator Block (PVI):
Table 1.2-1 Connection Method and Connected Destination of I/O Terminals of Input Indicator
Block (PVI)
Connection method(*1) Connection destination(*1)

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

The PVI block performs input processing, output processing, and alarm processing.
The only processing timing available for the PVI block is a periodic startup. Selections available for
the scan period used to execute a periodic startup include the basic scan period, the medium-speed
scan period (*1), and the high-speed scan period. Moreover, it is possible to specify the scan
coefficient and the scan phase.
*1: The medium-speed scan period can only be used for the FFCS series, KFCS2, KFCS, LFCS2, and LFCS.
SEE For more information about the types of input processing, output processing, and alarm
ALSO processing possible for the PVI block, refer to:
1.1.3, "Input Processing, Output Processing, and Alarm Processing Possible for Each
Regulatory Control Block"

For more information about the input processing, refer to:
For more information about the output processing, refer to:
For more information about the alarm processing, refer to:
Data Items - PVI

Table 1.2-2 Data Items of Input Indicator Block (PVI)
Data Entry Permitted or

Data Name Range Default
Item Not (*1)
O/S
MODE Block mode x -----
(AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- 0
Alarm detection
AF ----- 0
specification
Alarm masking
AOFS ----- 0
specification
PV Process variable Δ (*2) PV engineering unit value SL
Value in the unit at the
RAW Raw input data -----
connection destination
SUM Totalizer value x Engineering unit value 0
High - high limit alarm
HH x SL to SH SH
setpoint
Low - low limit alarm
LL x SL to SH SL
setpoint
High - limit alarm
PH x SL to SH SH
setpoint
Low - limit alarm
PL x SL to SH SL
setpoint
VL Velocity alarm setpoint x ±(SH - SL) SH - SL
Velocity-Reference Value in the same engineering
PVP -----
Sample unit as PV
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
Value in the same engineering
SH PV scale high limit -----
unit as PV
SL PV scale low limit x -----
unit as PV
*1: x: Entry is permitted unconditionally
Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*2: Entry is permitted when the data status is CAL
SEE For more information about valid block modes of the PVI block, refer to:
ALSO 1.1.4, "Valid Block Modes for Each Regulatory Control Block"
1.3 Input Indicator Block with Deviation Alarm (PVI-DV) Page 1 of 4
1.3 Input Indicator Block with Deviation Alarm

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

▼ Connection
The Input Indicator Block with Deviation Alarm (PVI-DV) displays an input signal received from an
I/O module or other function block as a process variable (PV).
In addition to the function to display an input signal as a process variable (PV), Input Indicator Block
with Deviation Alarm (PVI-DV) provides two other functions: “deviation alarm check” and “setpoint
value limiter.”
By presetting a deviation alarm setpoint (DL), the deviation (DV) of the setpoint value (SV) from
process variable (PV) can be confirmed.
The figure below shows a function block diagram of Input Indicator Block with Deviation Alarm (PVI-
DV):
Figure 1.3-1 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 1.3-1 Connection Methods and Connected Destinations of I/O Terminals of Input Indicator
Block with Deviation Alarm (PVI)

Measurement
IN x Δ x x
input
Process variable
OUT x Δ x x
output
link block (ADL).
Function of Input Indicator Block with Deviation Alarm

(PVI-DV)
The PVI-DV block performs input processing, output processing, and alarm processing.
The only processing timing available for the PVI-DV block is a periodic startup. Selections available
for the scan period used to execute a periodic startup include the basic scan period, the medium-
speed scan period (*1), and the high-speed scan period. Moreover, it is possible to specify the scan
coefficient and the scan phase.
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.
ALSO processing possible for the PVI-DV block, refer to:
Deviation Alarm Check

The deviation alarm check function generates a deviation alarm when the absolute value of
deviation (DV) between the setpoint value (SV) and process variable (PV) exceeds the absolute
value of the preset deviation alarm setpoint (DL).
• When the deviation (DV) exceeds the high limit of the deviation alarm setpoint (DL):
A positive deviation alarm (DV+) is generated.
• When the deviation (DV) falls below the low limit of the deviation alarm setpoint (DL):
A negative deviation alarm (DV-) is generated.
The deviation (DV) of the process variable (PV) from the setpoint value (SV) is represented by the
following expression:
DV=PV-SV
SEE For more information about the deviation alarm check, refer to:
ALSO 5.6, “Deviation Alarm Check” in Function Blocks Overview (IM 33J15A20-01EN)
Setpoint Value Limiter

The setpoint value limiter function limits the setpoint value (SV) within a range between the setpoint
high limit (SVH) and setpoint low limit (SVL).
SEE For more information about the setpoint value limiter, refer to:
ALSO " Actions in the Automatic or Manual Mode" in " Setpoint Value Limiter" in 1.4, "Control
Computation Processing Common to Controller Blocks"
" Set Parameters of the Setpoint Value Limiter" in " Setpoint Value Limiter" in 1.4, "Control
Data Items – PVI-DV

Table 1.3-2 Data Items of Input Indicator Block with Deviation Alarm (PVI-DV)

Item Not (*1)
O/S
(AUT)
Alarm detection
AF ----- 0
specification
Alarm masking
AOFS ----- 0
specification
SV Setpoint value x SL
unit as PV
DV Deviation 0
unit as PV
HH x SL to SH SH
setpoint
LL x SL to SH SL
setpoint
High - limit alarm
PH x SL to SH SH
setpoint
Low - limit alarm
PL x SL to SH SL
setpoint
VL Velocity alarm setpoint x ±(SH - SL) SH - SL
PVP -----
Sample unit as PV
Deviation alarm
DL x ±(SH - SL) SH - SL
setpoint
SVH Setpoint high limit x SL to SH SH
SVL Setpoint low limit x SL to SH SL
unit as PV
SL PV scale low limit unit as PV -----

SEE For more information about valid block modes of the PVI-DV block, refer to:
1.4 Control Computation Processing Common to Controller Blocks Page 1 of 24
1.4 Control Computation Processing Common

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

Blocks
The table below shows the control computation processing functions that are common to multiple
controller blocks:
Table 1.4-1 Control Computation Processing Common to Controller Blocks
Control computation
Description
processing
Changes the proportional gain in accordance with the degree of deviation
Non-linear gain so that the relationship between the deviation and control output change
(ΔMV) becomes non-linear.
Lowers the proportional gain to moderate control effects when the
Gap action
Non-linear deviation is within the gap width (GW) range.
gain Squared Changes the proportional gain according to the degree of deviation when
deviation action the deviation is within the gap width (GW) range.
Converts the manipulated output change (ΔMV) during each control period
Control output action to an actual manipulated output value (MV). The control output actions
include “positional type” and “velocity type.”
Switches the direction of the output action (reverse action or direct action)
Control action direction
in accordance with the increase or decrease in deviation.
Performs correction computation using values read from the connection
Reset limit function destinations of input terminals RL1 and RL2 during PID control
computation. This function prevents reset windup.
Adjusts the manipulated output change (ΔMV) to “0” when the deviation is
Deadband action within the deadband range, in order to stop the manipulated output value
(MV) from changing.
Adds the I/O compensated value (VN) received from outside to the input
I/O compensation signal or control output signal of PID computation when the controller
block is operating automatically.
Input Adds the I/O compensated value (VN) received from the outside to the
I/O compensation input signal of the PID control computation.
compensation Output Adds the I/O compensated value (VN) received from outside to the output
compensation signal of the PID control computation.
Process variable tracking Causes the setpoint value (SV) to agree with the process variable (PV).
Limits the setpoint value (SV) within the setpoint high/low limits (SVH,
Setpoint value limiter
SVL).
Causes two of the three setpoint values (SV, CSV, RSV) to agree with the
Setpoint value pushback
remaining one.
Switches the manipulated output value (MV) without causing it to change
abruptly when the block mode has been changed or when the
Bumpless switching manipulated output value (MV) has been switched in a downstream block
in cascade.
Changes the block mode to IMAN to temporarily suspend the control
Initialization manual action. This action takes place when the initialization manual condition
becomes satisfied.
Temporarily suspends the control action while maintaining the current
Control hold
block mode. During control hold, the output action is performed normally.
Changes the block mode to MAN to forcibly stop the control action. This
MAN fallback
action takes 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 mode, so that the control action is continued using values
AUT fallback
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
Computer failure
while the function block is operating 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
Block mode change interlock automatically, while disabling the stopped function blocks from changing
to the automatic operating mode.
Outputs the cascade setpoint value (CSV) after converting it to a
PRD mode action manipulated output value (MV) when the block mode has been changed
to PRD.
SEE For more information about the control computation processing functions specific to each
ALSO controller block, refer to:
1.5, "PID Controller Block (PID)"
1.6, "Sampling PI Controller Block (PI-HLD)"
1.7, "PID Controller Block with Batch Switch (PID-BSW)"
1.8, "Two-Position ON/OFF Controller Block (ONOFF), Enhanced Two-Position ON/OFF
Controller Block (ONOFF-E)"
1.9, "Three-Position ON/OFF Controller Block (ONOFF-G), Enhanced Three-Position ON/OFF
Controller Block (ONOFF-GE)"
1.10, "Time-Proportioning ON/OFF Controller Block (PID-TP)"
1.11, "PD Controller Block with Manual Reset (PD-MR)"
1.12, "Blending PI Controller Block (PI-BLEND)"
1.13, "Self-Tuning PID Controller Block (PID-STC)"
Non-Linear Gain
▼ Non-Linear Gain
The non-linear gain function changes the proportional gain in accordance with the deviation of the
process variable (PV) from the setpoint value (SV) in the control computation. As a result, a non-
linear relationship is formed between the manipulated output change (ΔMV) and the deviation of the
process variable (PV) from setpoint value (SV).
The non-linear gain function is used for pH control, in which the process gain often becomes too
high near the target value, or for buffer tank level control, whose purpose is to stabilize the
discharge volume while maintaining the tank level within the limits.
The actions that realize the non-linear gain function include “gap actions” and “squared deviation
actions.”
Processing Flow of Non-Linear Gain

The non-linear gain function calculates the control output change (ΔMV), using the effective
proportional gain (Kpe) obtained through non-linear correction of proportional gain (Kp).
The figure below shows a flow of the non-linear gain.
Figure 1.4-1 Processing Flow of the Non-Linear Gain
Setting Non-Linear Gain

Use the Function Block Detail Builder to set the non-linear gain.
Non-linear gain: Select “No,” “Gap Action” or “Squared Deviation Action.”
The default is “No.”
Gap Action
The gap action moderates control effects by lowering the proportional gain when the deviation is
within the preset gap width (GW).
Non-Linear Gain Characteristics of Gap Action

If a non-linear gain coefficient (Knl) has been set, the effective proportional gain (Kpe) is obtained by
the following expression when the deviation is within the gap width (GW):
Kpe = Kp • Knl
Once the deviation exceeds the limits of the gap width (GW), the effective proportional gain (Kpe) is
obtained by the following expression:
The figure below shows the non-linear gain characteristics of the gap action:
Figure 1.4-2 Non-Linear Gain Characteristics of Gap Action
Setting Gap Action

Use the Function Block Detail Builder to set the non-linear gain coefficient.
Gap Gain: Select “1.0,” “0.5,” “0.25” or “0.”
The default is “1.0.”
Figure 1.4-3 Relationship between the Non-linear Gain Coefficient and Effective Proportional
Gain
Set Parameter of Gap Action

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

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

If a gap width (GW) has been set, the effective proportional gain (Kpe) is obtained by the following
expression when the deviation is within the gap width (GW):
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:
Figure 1.4-4 Non-Linear Characteristics of the Squared Deviation Action
Set Parameter of Squared Deviation Action

The parameter of the squared deviation action:
Gap width (GW): Engineering unit data between 0 and the PV scale span range limit.
The default is 0.
Control Output Action

The control output action converts the manipulated output change (ΔMV) during each control period
to an actual manipulated output value (MV). There are two types of control output actions: velocity
type and positional type.
Velocity Type
Adds the current manipulated output change (ΔMVn) 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 (ΔMVn) to the previous output value (MVn-1) and
determines the manipulated output value (MVn).
The computational expression of the positional-type control output action is shown below:
MVn=MVn-1+ΔMVn
Setting Control Calculation Output Action

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

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

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

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

The reset limit function prevents the occurrence of reset windup (integral saturation) by setting
limits to the integral term in PID control computation. The reset limit function is applied only to the
positional-type control output actions.
Reset Windup
In PID control computation, the value obtained via the integral action represents an integrated 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 process
becomes unstable. In a control loop that reset windup may happen, you should select positional-
type control output action and use the reset limit function.
Reset Limit Function

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

ΔMVn0: PID computed value (manipulated output change before correction)
MV'n-1: Previously computed MV value (value before output limiting)
RLV1: Reset signal from the RL1 terminal
RLV2: Reset signal from the RL2 terminal
ΔT: Control period
TI: Integral time
WU: Reset limit coefficient
Reset limit coefficient is a parameter for adjusting the reset limiter calculation. The bigger this
coefficient is, the faster the MV can pullback against the reset windup.
Reset limit coefficient can be defined on Output tab of the Function Block Detail Builder.
Reset Limit Coefficient: Select 1, 2, 5 or 10
Default: 1
The following phenomena occur during velocity-type Control Action:
• Reset windup
Normally reset windup do not happen to the velocity-type control output actions, since the
cumulative value of manipulated output changes (ΔMV) of each scan period is limited. However,
if the values readback from the output destination are not limited by the MV H/L scale setpoints
nor by the MV H/L limiter, the manipulated output change (ΔMV) of each scan period is
accumulated, similar to the positional-type actions. Consequently, the reset windup happens.
• Output excess pullback phenomenon
When the manipulated output value (MV) is limited by the manipulated variable high-limit or low-
limit setpoint (MH, ML) as a result of changes caused by pulse-type disturbances, an output
excess pullback phenomenon happens if the control output action is velocity type.
When the manipulated output value was limited by the manipulated variable high-limit or low-
limit setpoint (MH, ML), a significant change in the process variable (PV) caused by disturbances
can pullback the manipulated output value (MV) excessively from the original value. When the
disturbance disappears, the process variable returns to the original level. This is called
the “output excess pullback phenomenon.” This phenomenon happens because, although the
delta MV caused by the disturbance is limited by MH or ML, the delta MV when PV returns to the
original level is not limited by MH or ML.
The output excess pullback phenomenon does not happen if the control output action is
positional type.
Example for Positional-Type Control Output Action

The following section explains the example that how the reset limit acts when the control
computation value of the function block with positional-type output action exceed the manipulated
variable high-limit or low-limit setpoint (MH, ML).
With a positional-type control output action, the control computation value in the current control
period (MV'n) is the sum of the manipulated output change (ΔMVn) obtained from the current PID
computation, and the control computation value in the previous control period (MV'n-1).
MV'n=ΔMVn+MV'n-1
The control computation value (MV'n) in the current control period limited by the manipulated
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:
Figure 1.4-5 Reset Limit Function for a Positional-Type Control Output Action
When the reset limit function is not used, positive or negative values is continuously added to the
integral term of the manipulated output change (ΔMVn) so long the positive or negative 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 computation. Even if
the deviation sustains, the reset windup does not happens.
Example on the “Figure Reset Limit Function for a Positional-Type Control Output Action,” neither
the RL1 or RL2 terminal is connected. Therefore, the reset signal RLV1 is the readback value from
the output destination, while the value of reset signal RLV2 is “0.” For example, suppose a loop is in
cascade (CAS) mode, if the manipulated output (MV) is limited by the manipulated variable high-
limit setpoint (MH), the reset signal RLV1 becomes the manipulated variable high-limit setpoint
(MH). In this situation, the integral term of the control computation value (MV') is adjusted gradually
to the value obtained by subtracting RLV2 from RLV1 (i.e., MH), even when the deviation sustains, it
does not exceed the manipulated variable high-limit setpoint (MH).
The manipulated output value (MV) will quickly move away from the limit when the sign of the
manipulated output change (ΔMV) reverses and agrees to the pullback direction of the value from
output limiting. This is because the control computation value (MV') is limited within the manipulated
variable high-limit and low-limit setpoints (MH, ML).
Example for a Simple Cascade Control loop

The figure below shows an application example of using the reset limit function to a simple cascade
control loop. The RL1 and RL2 terminals are not connected.
Since the RL1 or RL2 terminals are not connected the reset signal RLV1 becomes the readback value
from the output destination and the value of the reset signal RLV2 becomes “0.”
If use the readback value of the manipulated output value (MV) output destination to compute the
difference of the two reset signals (RLV1 - RLV2), there is no need to have terminal RL1 or RL2
connected.
Figure 1.4-6 Reset Limit Function for a Simple Cascade Control loop
Application Example to Auto-Selection via Auto-Selector Blocks

(AS-H)
The figure below shows an example of the reset limit function when automatically selecting the
signals from two function blocks using an Auto-selector blocks (AS-H).
Suppose the two PID Controller Blocks (PID) on the left side of the figure are velocity-type, even
when the deviation is within the switching point, the disturbance of the process variable may trigger
the output excess pullback to the manipulated output value (MV). Thus make the Auto-selector
blocks (AS-H) switch temporarily to the other controller. To define the positional-type output action
using the reset limit function can avoid this happening.
Figure 1.4-7 Reset Limit Function Used for Auto-Selection via Auto-Selector Blocks (AS-H)
Application Example in Feedforward Control

The figure below shows an example of the reset limit function used in feedforward control. This
example assumes base load control that uses the feedforward signals from the OUT terminal of the
General-Purpose Calculation Block (CALCU) as the base load values. To prevent reset windup of the
upstream PID Controller Block (PID), the RL2 terminal references the feedforward signals, while the
RL1 terminal references the process variable of the downstream PID Controller Block (PID).
Figure 1.4-8 Reset Limit Function Used in Feedforward Control (Base Load Control)
Deadband Action
▼ Deadband Action
The deadband action stops the manipulated output value (MV) from changing while the deviation
(DV) is within the preset deadband (DB) range, by causing the manipulated output change (ΔMV) to
be “0.”
Characteristics of Deadband Action

The deadband action causes the manipulated output change (ΔMVn) to be “0” when the absolute
value of the deviation (DV) minus the hysteresis value becomes smaller than the deadband width
(DB). When the absolute value of deviation (DV) increases greater than the deadband width (DB),
the manipulated output change after the deadband action (ΔMVn) will be brought back to the
manipulated output change before the deadband action (ΔMVn0).
The figure below shows the characteristics of the deadband action:
Figure 1.4-9 Characteristics of Deadband Action
Setting Deadband Action

Use the Function Block Detail Builder to set the deadband action.
Deadband action: Select “Yes” or “No.”
When the deadband action is set as “Yes,” the hysteresis (HYS) must be set. Use the Function Block
Detail Builder to set the hysteresis (HYS).
Hysteresis: 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.
Set Parameter of Deadband Action

The parameter of the deadband action:
Deadband width (DB): Engineering unit data between 0 and the PV scale span range limit.
The default is 0.
Input or Output Compensation

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

Use the Function Block Detail Builder to define the Input or Output compensation.
I/O Compensation: Select “No,” “Input Compensation” or “Output Compensation.”
For the 2-Position ON/OFF Controller Block (ONOFF), 3-Position ON/OFF Controller Block (ONOFF-G),
PD Controller Block with Manual Reset (PD-MR) and Feedforward Signal Summing Block (FFSUM),
only the input compensation can be defined.
Input Compensation: Select “No” or “Input Compensation.”
Set Parameters of I/O Compensation

The parameters of the I/O compensation:
I/O compensation gain (CK): -10.000 to +10.000.
The default is 1.000.
I/O compensation bias (CB): Arbitrary engineering unit data.
The default is 0.0.
Input Compensation
▼ Input Compensation
The input compensation is a control action that adds the compensation value (VN) received from
outside to the input signal of PID control computation.
Characteristics of Input Compensation

The computational expression of the input compensation:
CVn=PVn+CK(VN+CB)
CVn : Control variable (PV after input compensation)
PVn : Process variable
CK : I/O compensation gain
CB : I/O compensation bias (internal bias)
VN : I/O compensated value (bias signal)
The figure below shows a processing flow of the input compensation:
Figure 1.4-10 Processing Flow of the Input Compensation
Example Using Input Compensation

The input compensation is used to improve the controllability of a process with a long dead time, by
subtracting from the input signal the signal from the Dead-Time Compensation Block (DLAY-C) to
perform PID control computation (Smith Dead Time Compensation).
The figure below shows an example of dead time compensation:
Figure 1.4-11 Example of Dead Time Compensation
Output Compensation
The output compensation is a control action that adds the I/O compensated value (VN) received
from the outside to the output signal of PID control computation.
Characteristics of the Output Compensation

The computational expression of the output compensation:
MVn=MVn0+CK(VN+CB)
MVn : Manipulated output after output compensation

MVno : manipulated output before output compensation
The figure below shows a processing flow of the output compensation:
Figure 1.4-12 Processing Flow of the Output Compensation
Example of Using the Output Compensation

The output compensation is used for feedforward control that adds the feedforward signal to the
control output signal, or for non-interacting control that adds the output signal from the interacting
loop to the control output signal.
The figure below shows an example of feedforward control:
Figure 1.4-13 Example of Feedforward Control
Process Variable Tracking (Measurement Tracking)

▼ Measurement Tracking
The process variable tracking function prevent the abrupt changes in the manipulated output value
(MV) when change from the manual (MAN) mode to automatic (AUT) mode, by forcing the setpoint
value (SV) to agree with the process variable (PV).
Characteristics of Process Variable Tracking

When switching from the manual (MAN) mode to automatic (AUT) mode, the existence of a large
deviation is harmful, since it makes the manipulated output change (ΔMV) very large.
If force the setpoint value (SV) to agree with the process variable (PV) in manual mode operation
via process variable tracking, abrupt Control Action can be avoided when the mode switches to
automatic (AUT).
Suppose a primary loop is in cascade connection and controls in the automatic (AUT) or cascade
(CAS) mode. If the mode of the secondary loop in the cascade connection switches from cascade
(CAS) to automatic (AUT), the cascade connection becomes open and the control action of the
primary side loop can stop. In this situation, the setpoint value (SV) of the primary loop can be
forced to agree with the process variable (PV) by the process variable tracking function.
Define Process Variable Tracking

Use the Function Block Detail Builder to define the process variable tracking.
• Measurement tracking
• MAN mode
Select “Yes” or “No.” The default is “No.”
• AUT and CND mode
Select “Yes” or “No.” The default is “No.”
• CAS and CND mode
Select “Yes” or “No.” The default is “Yes.”
The statuses referred to as MAN, AUT and CAS include remote backup modes such as AUT
(ROUT) and AUT (RCAS).
For a 2-Position ON/OFF Controller Block (ONOFF), 3-Position ON/OFF Controller Block (ONOFF-G)
or Time - Proportioning ON/OFF Controller Block (PID-TP), the definition is allowed for MAN mode
only.

The setpoint value limiter function limits the setpoint value (SV) within a range between the setpoint
high limit (SVH) and setpoint low limit (SVL).
The action of the setpoint value limiter varies with the block mode of the function block.
Actions in the Automatic or Manual Mode

The action of the setpoint value limiter in automatic (AUT) or manual (MAN) mode varies depending
on whether the setpoint value (SV) can be set to a value beyond the range between SVH and SVL or
not. This setting can be changed from the option of [Prohibit setting SV to a value beyond the range
of SVL and SVH] on the properties sheet of the project.
When the option of [Prohibit setting SV to a value beyond the range of SVL and SVH] is checked,
the setpoint value limiter performs the following actions:
• When try to set a setpoint value (SV) greater than the setpoint high limit (SVH):
An error message will be displayed and the value beyond the setpoint high limit becomes invalid,
the previous setpoint value will be held.
• When try to set a setpoint value (SV) smaller than the setpoint low limit (SVL):
An error message will be displayed and the value beyond the setpoint low limit becomes invalid,
the previous setpoint value will be held.
When the option of [Prohibit setting SV to a value beyond the range of SVL and SVH] is not
checked, the setpoint value limiter performs the following actions:
• When try to set a setpoint value (SV) greater than the setpoint high limit (SVH):
An acknowledgment dialog box appears to prompt for the operator's confirmation. When
confirms, the operator can set a value greater than the setpoint high limit (SVH) as the setpoint
value.
• When try to set a setpoint value (SV) smaller than the setpoint low limit (SVL):
confirms, the operator can set a value smaller than the setpoint low limit (SVL) as the setpoint
value.
However, when try to set a setpoint value (SV) to a value beyond the range between the process
high alarm setpoint (PH) and the process low alarm setpoint (PL), the setpoint value limiter performs
the following actions regardless if the option of [Prohibit setting SV to a value beyond the range of
SVL and SVH] is checked or unchecked:
• When try to set a setpoint value (SV) greater than the process high alarm setpoint (PH):
confirms, the operator can set a value greater than the process high alarm setpoint (PH) as the
setpoint value.
• When try to set a setpoint value (SV) smaller than the process low alarm setpoint (PL):
confirms, the operator can set a value smaller than the process low alarm setpoint (PL) as the
setpoint value.
Actions in the Remote Cascade Mode

When the function block is in remote cascade (RCAS) mode and the setpoint value (SV) is defined to
automatically follow the remote setpoint value (RSV) received from the supervisory system
computer, the setpoint value limiter performs the following actions:
• The value exceeds the setpoint high limit (SVH) is forced to be equal to the setpoint high limit
(SVH).
• The value smaller than the setpoint low limit (SVL) is forced to be equal to the setpoint low limit
(SVL).
Set Parameters of the Setpoint Value Limiter

The parameters of the setpoint value limiter:
Setpoint high limit (SVH): Engineering unit data within the PV scale range.
The default is the scale high limit.
Setpoint low limit (SVL): Engineering unit data within the PV scale range.
The default is the scale low limit.
Setpoint Value Pushback

The setpoint value pushback function sets the same value for the three types of setpoint values (SV,
CSV, RSV). The figure below explains the relationship among the setpoint value (SV), cascade
setpoint value (CSV) and remote setpoint value (RSV):
Figure 1.4-14 Relationship among Setpoint Values (SV, CSV and RSV)
The action of the setpoint value pushback varies in accordance with the block mode of the function
block.
Action in the Automatic (AUT) or Manual (MAN) Mode

Causes the cascade setpoint value (CSV) and remote setpoint value (RSV) to agree with the setpoint
value (SV). Even when a data value is set to the setpoint value (SV) from outside the function block,
the same value is automatically set to the cascade setpoint value (CSV) and remote setpoint value
(RSV).
Action in the Cascade (CAS) Mode

Force the setpoint value (SV) and remote setpoint value (RSV) to be equal to the cascade setpoint
value (CSV).
Action in the Remote Cascade (RCAS) Mode

Force the setpoint value (SV) and cascade setpoint value (CSV) to be equal to the remote setpoint
value (RSV).
Bumpless Switching
The bumpless switching function switches the block mode of the function block or manipulated
output value downstream in cascade without causing the manipulated output value (MV) to change
abruptly (i.e., bumpless change).
The action during bumpless switching varies with the control output action and block mode status.
Action for Velocity-Type Control Output Action

For a velocity-type control output action, the manipulated output change (ΔMVn) obtained by control
computation is added to the present value readback from the connected destination. Therefore, the
block mode or cascade switch can be changed without causing an abrupt change in the manipulated
output value (MV).
Action for Positional-Type Control Output Action
For a positional-type control action, when the function block mode changes to tracking (TRK) mode,
or when the cascade connection to the downstream is open then close again, or for the similar
reason the cascade control loop regain the control, the manipulated output value (MV) may change
abruptly. To prevent this, the output value is forced to be equal (or to track) to the value of the
output destination while the control action stops. This enables the block mode switch causes no
abrupt change in the manipulated output value (MV).
Action when a Cascade Connected Downstream Loop Changes

from Automatic (AUT) to Cascade
When a cascade connected downstream loop changes its mode from automatic (AUT) to cascade
(CAS), the tracking process described above is performed in the upstream loop if the downstream is
only connected to one loop. Therefore, the block mode switches without causing an abrupt change
in the manipulated output value (MV).
Action when Manipulated Output of an Upstream Loop is

Connected to Multiple Downstream Loops as Setpoint Value
When multiple downstream loops are receiving the manipulated output signals of an upstream loop
as setpoint value signals via a Cascade Signal Distributor Block (FOUT), Control Signal Splitter Block
(SPLIT) or switch block (SW-33, SW-91), the setpoint value downstream may change abruptly. In
this case, control computation is not performed in downstream loops in the first control period
following the switching of modes from automatic (AUT) to cascade (CAS). In other words, the block
mode can be changed without causing an abrupt change in the output as a result of a proportional
or derivative action, by resuming the control computation from the next control period in which the
change in the setpoint value caused by the block mode change will not be reflected by the change in
the deviation (ΔEn).
The figure below shows an example of a multiple downstream loop configuration:
Figure 1.4-15 Example of a Multiple Downstream Loop Configuration (when a Cascade Signal
Distributor Block is Used)
Figure 1.4-16 Example of a Multiple Downstream Loop Configuration (when a Control Signal
Splitter Block is Used)
Figure 1.4-17 Example of a Multiple Downstream Loop Configuration (when a Switch Block is
Used)
Initialization Manual
The initialization manual is an error processing function that suspends the control action temporarily
by changing the block mode to initialization manual (IMAN). This action takes place when the
initialization manual condition is established.
Characteristics of the Initialization Manual

The initialization manual function suspends the control action and control output action temporarily
during the automatic (AUT) mode or other automatic control operation mode when the initialization
manual condition is established, and changes the function block to initialization manual (IMAN)
mode.
Since the initialization manual action causes the manipulated output value (MV) to track the value of
the connected destination, even when the mode changes from initialization manual (IMAN) mode to
manual (MAN) mode, the initialization manual (IMAN) mode will precede the manual (MAN) mode.
Therefore, the manual (MAN) mode does not take effect.
The block returns to the original mode as soon as the initialization manual condition vanishes.
However, if the mode change operation is performed in the initialization manual (IMAN) mode, the
block will switch to the mode of this operation after the initialization manual condition vanishes.
Initialization Manual Condition

The initialization manual condition is a block mode transition condition. It suspends the control
action and control output action temporarily by changing the block mode to initialization manual
(IMAN) mode.
The initialization manual (IMAN) block mode becomes active only when the initialization manual
condition is established.
The initialization manual condition is depicted as follows:
AUT
↓ Initialization manual condition is established
IMAN (AUT)
↓ Initialization manual condition vanishes
AUT
The initialization manual condition is established in the following situation:
• When the manipulated output value (MV) connected destination’s data status is conditional (CND)
(i.e., the cascade loop open).
• When the manipulated output value (MV) connected destination’s data status is communication
error (NCOM) or output failure (PTPF).
• When the manipulated output value (MV) connected destination is a switch block (SW-33, SW-
91) and the cascade connection is switched off (i.e., the cascade loop open).
• When the manipulated output value (MV) connected destination is a process output, and a failure
or output open alarm has occurred in the process output.
• When the data status of the input signal at the TIN or TSI terminals become invalid (BAD) in the
tracking (TRK) mode while the output signal is not a pulse-width type.
Control Hold
The control hold is an error processing function that suspends the control action temporarily while
maintaining the current block mode. Unlike initialization manual, the control output action is
performed normally during control hold.
The control hold action takes place when the following condition is established during automatic
operation (AUT, CAS, RCAS):
• The connected destination of the IN terminal is open (i.e., not selected via a selector switch).
The control is resumed when the condition becomes unsatisfied.
MAN Fallback
The MAN fallback is an error processing function that stops the control forcibly by changing the
block mode to manual (MAN). This action takes place when the MAN fallback condition is established.
Characteristics of the Man Fallback

The MAN fallback stops the control by changing the function block to manual (MAN) mode
regardless of the current operation status, and forces the function block to manual operation state.
Once the MAN fallback condition is established, the block mode remain manual (MAN) even after the
condition vanishes.
MAN Fallback Condition

The MAN fallback condition is used to stop the control by changing the function block to manual
(MAN) mode regardless of the current operation status, and forces the function block to enter
manual operation state. When the MAN fallback condition is established, it indicates that a fatal error
has occurred and requests operator interruption.
An example of the MAN fallback condition is shown as follows:
AUT→MAN
IMAN (CAS)→IMAN (MAN)
The MAN fallback condition is established in the following situation:
• When the data status of the process variable (PV) is invalid (BAD) or calibration (CAL). However,
the MAN fallback condition will not be established when the block mode is primary direct (PRD),
or remote output (ROUT) excluding any compound mode during computer backup.
• When the data status of the manipulated output value (MV) is output failure (PTPF).
• When the data status of the setpoint value (SV) is invalid (BAD).
• When the manipulated output value (MV) is connected to a process I/O and the FCS is having an
initial cold start.
• When the block mode change interlock condition is established.
• When the manipulated output value (MV) is connected to a process I/O, and one of the I/O
points connected to the module has been changed via maintenance.
AUT Fallback
▼ AUT Fallback
The AUT fallback is an error processing function that switches the block mode from cascade (CAS)
or primary direct (PRD) to automatic (AUT) when the AUT fallback condition is established. Thus the
set value of the control loop can be set by the operator.
Characteristics of the AUT Fallback
Changes the block mode from cascade (CAS) or primary direct (PRD) to automatic (AUT) to continue
control using values set by the operator.
Once the AUT fallback condition is established, the block mode remain automatic (AUT) even after
the condition vanishes.
AUT Fallback Condition

The AUT fallback condition is used to change the block mode of the function block from cascade
(CAS) or primary direct (PRD) to automatic (AUT) so that control can be continued using the values
set by the operator. When this condition is established, it indicates that abnormality has been
detected in the cascade setpoint value (CSV) for some reason.
An example of when the AUT fallback condition establishment is as follows:
CAS→AUT
IMAN (CAS)→IMAN (AUT)
Setting AUT Fallback Condition

Use the Function Block Detail Builder to enable/disable the AUT fallback function.
AUT Fallback: Select “Yes” or “No.”
If the AUT fallback is defined as “Yes” via the Function Block Detail Builder, the AUT fallback
condition is established when the data status of the cascade setpoint value (CSV) become invalid
(BAD) or communication error (NCOM).
Computer Fail
▼ Computer Backup Mode
When the computer fail is detected, the function block suspends the action in the remote cascade
(RCAS) mode or remote output (ROUT) mode temporarily and switches to the computer backup
mode.
Characteristics of Computer Fail

When the function block mode is remote cascade (RCAS) or remote output (ROUT), the function
block receives the setpoint value (SV) or manipulated output value (MV) from a supervisory system
computer via Control bus communication.
When the computer fails, the block changes mode to the preset computer backup mode (MAN, AUT
or CAS) which indicates that an abnormality has been detected in the supervisory computer. When
the computer recovers, the block returns to the mode before the change.
The following actions will take place when a block mode change command from MAN, AUT, CAS or
PRD to RCAS or ROUT is sent while the computer fails:
1. When a block mode change command from MAN, AUT, CAS or PRD to RCAS or PRD is sent while
the computer fails (BSW=ON), the function block does not switch to the computer backup mode
directly but switches to the transient state mode first.
The transient state mode is a compound block mode consisting of the block mode before the
execution of the block mode change command (MAN, AUT, CAS, PRD) and a remote mode
(RCAS, ROUT).
2. Then the function block tests the computer condition in the first scan after the block mode
change command and switches to the computer backup mode.
The computer backup mode is a compound block mode consisting of the backup mode set via
the Function Block Detail Builder (MAN, AUT, CAS) and a remote mode (RCAS, ROUT).
3. If the computer recovers while the function block is in the computer backup mode, the block
mode changes to remote cascade (RCAS) or remote output (ROUT).
Computer Fail Condition

The computer fail condition is a block-mode transition condition used to suspend actions in the
remote cascade (RCAS) or remote output (ROUT) mode and switches the mode to the computer
backup mode.
A backup switch (BSW) is provided in function block to define the remote cascade (RCAS) or remote
output (ROUT) mode. The status of this switch determines whether the computer has failed or
recovered. The value of the backup switch (BSW) can be set from a sequence table or other function
blocks.
Switching to a computer backup mode does not take effect if the backup switch (BSW) is on a block
mode other than remote cascade (RCAS) or remote output (ROUT).
• When BSW=ON, computer has failed
• When BSW=OFF, computer has recovered
An example when the automatic (AUT) mode has been specified for the computer backup mode is
shown as follows:
RCAS
↓ Computer fails
AUT (RCAS)
↓ Computer recovers
RCAS
An example when the manual (MAN) mode has been specified for the computer backup 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)
Define Computer Backup Mode

Use the Function Block Detail Builder to define the computer backup mode for each function block.
• Computer Backup Mode
Select “MAN,” “AUT” or “CAS” as the mode to be switched to when the computer becomes down.
The default is “MAN.”
For a Control Signal Splitter Block (SPLIT), select “AUT” or “CAS.” The default is “AUT.”
Block Mode Change Interlock

When the block mode change interlock condition is established, the block mode change interlock
function stops the control computation processing of the function block running in auto mode, and
prohibit the function block changing to automatic operation mode.
Characteristics of the Block Mode Change Interlock

Stops the control computation processing of the function blocks that are operating automatically,
and disables the currently stopped function blocks from changing to an automatic operation state.
The following actions will take place:
• The block mode changes to manual (MAN).
• Any block mode change command to make the function block into automatic operation state
(AUT, CAS, PRD, RCAS or ROUT mode) becomes invalid.
Block Mode Change Interlock Condition

The Block mode change interlock condition is established when the switch at the connected
destination of the interlock switch input terminal (INT) is turned ON. This switch is manipulated in
the process control sequence and the switch is turned on when the sequence judge that the loop
can not run in Auto mode, or etc.,.
Primary Direct (PRD) Mode Action

The primary direct (PRD) mode action enables the downstream block to output the setpoint value
received from the cascade connected upstream block (CSV) after converting it into manipulated
output value (MV).
The conversion action from the cascade setpoint value (CSV) to the manipulated output value (MV)
varies with the control action direction, i.e., direct or reverse.
When an error such as process input signal error is detected in the cascade connected downstream
block, the block changes to primary direct (PRD) mode, to allow the upstream block temporarily
takes over control.
The output tracking function for the cascade connected upstream block is used so that an abrupt
change in the manipulated output does not occur when the block mode for the cascade connected
downstream block is changing to the primary direct (PRD) mode. The cascade connected
downstream block returns the manipulated output value (MV) to the setpoint value (SV, CSV, RSV)
in order to make the downstream block manipulated output value (MV) track the upstream block
manipulated output value (MV) when the block mode for the downstream block changes to the
primary direct (PRD) mode.
• 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.
• When change a block to primary direct (PRD) mode, it is necessary to
change the upper stream block in the same cascade loop to manual (MAN)
mode.
• When change a block from primary direct (PRD) mode to automatic (AUT)
mode, it is better to change the block into manual (MAN) mode first.
However, it is possible to change the block from primary direct (PRD)
mode to automatic (AUT) mode directly. In this case, the block runs
measurement tracking to force the set point value (SV) to track the
process variable value (PV) so as to avoid the radical change to the control
output.
SEE For more information about primary direct (PRD) mode, refer to:
ALSO 6.1.1, “Basic Block Mode” in Function Blocks Overview (IM 33J15A20-01EN)
When the Control is Direct Action

The computational expression of the primary direct (PRD) mode action when the control action is
direct:
RMV=MV
SH : PV scale high limit
SL : PV scale low limit
MSH : MV scale high limit
MSL : MV scale low limit
When the block mode changes to primary direct (PRD), the downstream block sets its the
manipulated output value (MV) to the setpoint value (SV, CSV, RSV), using the computational
expression shown below:
CSV=RSV=SV
When the Control is Reverse Action

The following computational expression is used as a basis of the primary direct (PRD) mode action
when the control action is reverse:
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 computational
expression shown below:
CSV=RSV=SV
Output Limiter in PRD Mode: FFCS Series/KFCS2/LFCS2

▼ Enable output limiter in PRD mode (XL compatible)
The output limiter can also be applied when the block mode is PRD.
To limit the direct output value of primary loop, check the option of [Enable output limiter in PRD
mode (XL compatible)] on [Constant 3] tab of FCS properties sheet.
SEE For more information about the output limiter actions when the function block is in Primary Direct
ALSO mode, refer to:
“ Pulse Width Output in PRD Mode” in 4.8.2, “Pulse Width Output Conversion” in Function
Blocks Overview (IM 33J15A20-01EN)
1.5 PID Controller Block (PID) Page 1 of 10
1.5 PID Controller Block (PID)

The PID Controller Block (PID) provides the most general control function to perform proportional-
integral-derivative control based on the deviation of the process variable (PV) from the setpoint
value (SV).
PID Controller Block (PID)

▼ Connection
The figure below shows a function block diagram of PID Controller Block (PID):
Figure 1.5-1 Function Block Diagram of PID Controller Block (PID)
PID Controller Block (PID):
Table 1.5-1 Connection Methods and Connected destinations of the I/O Terminals of PID
Controller Block (PID)

Measurement
IN x Δ x x
input
SET Setting input x x
Manipulated
OUT x x x x
output
Reset signal 1
RL1 x Δ x x
input
Reset signal 2
RL2 x Δ x x
input
Compensation
BIN x Δ x x
input
Tracking signal
TIN x Δ x x
input
Tracking SW
TSI x Δ x x x
input
Interlock SW
INT x Δ x x x
input
link block (ADL).
Function of PID Controller Block (PID)

The PID block performs input processing, control computation processing, output processing, and
alarm processing.
The only processing timing available for the PID block is a periodic startup. Selections available for
scan period (*1), and the high-speed scan period.
ALSO processing possible for the PID block, refer to:
Control Computation Processing of the PID Controller Block

(PID)
The table below shows the control computation processing functions of the PID Controller Block
(PID):
Table 1.5-2 Control Computation Processing Functions of the PID Controller Block (PID)
Control computation
Description
processing
Calculates the manipulated output value (MV) and manipulated output
PID control
change (ΔMV) using the PID control algorithms.
Performs the PID control actions by bypassing derivative control actions
Control action bypass (D), proportional control actions (P) or both proportional and derivative
control actions (P+D).
Non-linear gain so that the relationship between the deviation and manipulated output
change (ΔMV) becomes nonlinear.
Gap action
to an actual manipulated output value (MV). The control output actions

Control output action
(MV) from changing.
SVL).
remaining one.
Bumpless switching
manipulated output value (MV) has been switched in a downstream block
in cascade.
becomes satisfied.
Control hold
MAN fallback
AUT fallback
Computer failure
to PRD.
SEE For more information about control computation processing functions applied in the PID
ALSO Controller Block, refer to:
1.4, "Control Computation Processing Common to Controller Blocks"
PID Control Computation

▼ PID Control Algorithm
The PID control computation is the core of the PID control computation processing, calculating a
manipulated output change (ΔMV) by using the PID control algorithms. The PID control is the most
widely used, it combines three types of actions: proportional, integral and derivative.
The figure below shows a block diagram of PID control computation:
Figure 1.5-2 Block Diagram of PID Control Computation
PID Control Computation Expression

The PID control computation expression used in a regulatory control system (analog control
system):
MV(t): Manipulated output

E(t): Deviation E(t) = PV(t) - SV(t)
PV(t): Process variable
SV(t): Setpoint value
PB: Proportional band (%)
TI: Integral time
TD: Derivative time
If we use the sampling value derived at each interval of the control period for the above expression,
the differential expression of the PID control computation is transformed as follows:
ΔMVn: Manipulated output change

En: Deviation En=PVn-SVn
PVn: Process variable
SVn: Setpoint value’
ΔEn: Change in deviation ΔEn=En-En-1
ΔT: Control period
The subscripts “n” and “n-1” represent the sample against the control period, it stands for the nth
sample or n-1th sample.
The above differential expression calculates a change in manipulated output (difference). A new
output value is obtained by adding the current change in manipulated output (ΔMVn) to the previous
manipulated output value (MVn-1).
Types of PID Control Computation

The PID Controller Block uses the following five PID control algorithms to perform PID control
computation. The actions vary with the characteristics of a controlled system and the purpose of
control.
• Basic type PID control (PID)
• PV proportional and derivative type PID control (I-PD)
• PV derivative type PID control (PI-D)
• Automatic determination type
• Automatic determination type 2
Define PID Control Computation

For PID control computation, the input variables of the proportional, integral and derivative terms
are different for each PID control algorithm.
The table below shows the PID control algorithms and the input variable of each term:
Table 1.5-3 PID Control Algorithms and the Input Variables
Trinomial input variables

PID control algorithm
Proportional term Derivative term Integral term
PID En En En
I-PD PV PV En
PI-D En PV En
Same as I-PD in the AUT mode.
Automatic determination
Same as PI-D in the CAS or RCAS mode.
Same as I-PD in the AUT or RCAS mode.
Automatic determination 2
Same as PI-D in the CAS mode.
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 follows:
Automatic determination type: Same actions as in the cascade (CAS) mode.
Automatic determination type 2: Same actions as in the automatic (AUT) mode.
Basic Type PID Control Algorithm (PID)

The basic type PID control algorithm performs proportional, integral and derivative Control Action
following the changes in the setpoint value.

This algorithm is used when the process time constant is long and the control is oriented on the
prompt response to the change in the setpoint value. For example, when use a 13-Zone Program
Set Block (PG-L13) to change the setpoint value of a controller block, this algorithm is used for the
PID block.
The computational expression of the basic type PID control algorithm (PID):
En=PVn-SVn
ΔT: Control period

ΔEn: Change in deviation ΔEn=En-En-1
Kp: Proportional gain
TI: Integral time
TD: Derivative time
Ks: Scale conversion coefficient
PVn: Process variable (engineering unit)
SVn: Setpoint value (engineering unit)
SH: PV scale high limit
SL: PV scale low limit
MSH: MV scale high limit
MSL: MV scale low limit
The process variable (PV) and setpoint value (SV) used in the computation are both engineering unit
data. The manipulated output change (ΔMV) obtained in an engineering unit by the range
conversion performed via the scale conversion coefficient (Ks).
PV Proportional and Derivative Type PID Control Algorithm (I-

PD)
The PV proportional and derivative type PID control algorithm (I-PI) differs from the basic type that
it performs only integral actions when the setpoint value changes.
This algorithm ensures stable control characteristics even when the setpoint value changes abruptly
when the SV is set via numerical value entry. At the same time, the algorithm ensures proper control
in response to the characteristic changes occurring in controlled processes, load variations and
disturbances by performing proportional, derivative and integral Control Action accordingly.
The computational expression of the PV proportional and derivative type PID control algorithm (I-
PD):
ΔPVn : Process variable change ΔPVn=PVn-PVn-1
PV Derivative Type PID Control Algorithm (PI-D)

Compared to the basic type, the PV derivative type PID control algorithm (PI-D) only performs
proportional and integral Control Action when setpoint value changes, but not derivative Control
Action. This algorithm is used in the situations where the better follow up to the setpoint value
change is required, such a downstream control block in a cascade control loop.
The computational expression of the PV derivative type PID control algorithm:
Automatic Determination Type

When a PID Controller Block is in cascade (CAS) or remote cascade (RCAS) mode, it uses the PV
derivative type PID control algorithm (PI-D) to perform computation so that the follow-up the
setpoint value change can be improved.
When the block is in automatic (AUT) mode, it uses the PV proportional and derivative type PID
control algorithm (I-PD) to perform computation so that stable control characteristics can be
ensured in the event that an abrupt change occurs in the setpoint value due to a numeric value
setting.
Automatic Determination Type 2

When a PID Controller Block is in cascade (CAS) mode, it uses the PV derivative type PID control
algorithm (PI-D) to perform computation. When the block is in remote cascade (RCAS) mode or
automatic (AUT) mode, it uses the PV proportional and derivative type PID control algorithm (I-PD)
to perform computation.
In the cascade (CAS) mode, the automatic determination type 2 orients to the follow-up capability to
setpoint value (CSV) change. In the remote cascade (RCAS) mode, it orients to prevent the abrupt
change in the output due to an abrupt change in the remote setpoint value (RSV).
Set Parameters of the PID Control Algorithms

The set parameters of the PID control algorithms:
• Proportional band (P): 0 to 1000 % (*1)
• Integral time (I): 0.1 to 10000 seconds
• Derivative time (D): 0 to 10000 seconds (*1)
*1: The control action bypass function is enabled when “0” is set.
If the integral time of control block is set to zero or to a value beyond the
range, the control algorithm stops functioning. No process alarm or system
alarm message is initiated for this trouble. So that when using a general
purpose calculation block or sequence table block to set the value of integral
time, it is necessary to enforce the value within the proper range and to avoid
it to be set to zero.
Control Action Bypass

The PID Controller Block can perform the following two types of control action by bypassing
proportional and/or derivative actions among the proportional, integral and derivative actions:
Table 1.5-4 Control Action Bypass
Control actions bypassed Control actions after bypassing Set parameter setpoint
Derivative (D) Proportional (P)+integral (I) P≠0, D=0
Proportional (P), derivative (D) Integral (I) P=0
To set the control action bypass, specify “0” to the set parameter P or D, as shown in the table
above. The proportional gain (Kp) is fixed to “1” when only integral action is required.
Data Items - PID

Table 1.5-5 Data Items of PID Controller Block (PID) (1/2)
Data Entry Permitted or Default

Data Name Range (*2)
Item Not (*1) (*2)
MODE Block mode x ----- O/S (MAN)
Alarm detection
AF ----- 0
specification
Alarm masking
AOFS ----- 0
specification
SV Setpoint value Δ (*4) SL
unit as PV
CSV Cascade setpoint value x SL
unit as PV
RSV Remote setpoint value Δ (*5) SL
unit as PV
DV Control deviation value 0
unit as PV
VN I/O compensation value x ----- 0
MV Manipulated output value Δ (*6) MV engineering unit value MSL
Remote manipulated Value in the same engineering
RMV Δ (*7) MSL
output value unit as MV
RLV1 Reset limit value 1 MSL
unit as MV
unit as MV
HH x SL to SH SH
setpoint
LL setpoint x SL to SH SL
High - limit alarm
PH x SL to SH SH
setpoint
PL Low - limit alarm setpoint x SL to SH SL
VL Velocity alarm setpoint x ± (SH - SL) SH - SL
PVP -----
Sample unit as PV
DL Deviation alarm setpoint x ± (SH - SL) SH - SL
*1: x: Entry is permitted unconditionally.
Blank: Entry is not permitted.
Δ: Entry is permitted conditionally.
*2: SH: PV scale high limit
*3: Entry is permitted when the data status is CAL.
*4: Entry is not permitted when the block mode is CAS or RCAS.
*5: Entry is permitted when the block mode is RCAS.
*6: Entry is permitted when the block mode is MAN.
*7: Entry is permitted when the block mode is ROUT.
Table 1.5-6 Data Items of PID Controller Block (PID) (2/2)

Item Not (*1) (*2)
Manipulated variable high-
MH x MSL to MSH MSH
limit setpoint
Manipulated variable low-
ML x MSL to MSH MSL
limit setpoint
P Proportional band x 0 to 1000 % 100 %
I Integral time x 0.1 to 10,000 seconds 20 seconds
D Derivative time x 0 to 10,000 seconds 0 second
GW Gap width x 0 to (SH - SL) 0.0
DB Deadband x 0 to (SH - SL) 0.0
CK Compensation gain x -10.000 to 10.000 1.000
CB Compensation bias x ----- 0.000
Preset manipulated output
PMV x MSL to MSH MSL
value
TSW Tracking switch x 0, 1 0
CSW Control switch x 0, 1 0
PSW Preset MV switch x 0, 1, 2, 3 0
RSW Pulse width reset switch x 0, 1 0
BSW Backup switch x 0, 1 0
OPHI Output high-limit index x MSL to MSH MSH
OPLO Output low-limit index x MSL to MSH MSL
Value in the same
SH PV scale high limit engineering unit as PV -----

Value in the same
SL PV scale low limit -----
engineering unit as PV
Value in the same
MSH MV scale high limit -----
engineering unit as MV
Value in the same
MSL MV scale low limit -----
SEE For more information about valid block modes of the PID block, refer to:
1.6 Sampling PI Controller Block (PI-HLD) Page 1 of 9
1.6 Sampling PI Controller Block (PI-HLD)

Sampling PI Controller Block (PI-HLD) stops after performing each control action and waits for the
result to come out. This block may be used to control processes with a long dead time or for the
control that relies on the data from sampling unit of analyzers.
Sampling PI Controller Block (PI-HLD)

▼ Connection
The figure below shows a function block diagram of Sampling PI Controller Block (PI-HLD):
Figure 1.6-1 Function Block Diagram of Sampling PI Controller Block (PI-HLD)
the Sampling PI Controller Block (PI-HLD):
Table 1.6-1 Connection Methods and Connected destinations of the I/O Terminals of Sampling
PI Controller Block (PI-HLD)

Measurement
IN x Δ x x
input
Manipulated
OUT x x x x
output
Reset signal 1
RL1 x Δ x x
input
Reset signal 2
RL2 x Δ x x
input
Compensation
BIN x Δ x x
input
Tracking signal
TIN x Δ x x
input
Tracking SW
TSI x Δ x x x
input
Interlock SW
INT x Δ x x x
input
Blank: Connectio not allowed
link block (ADL).
Function of Sampling PI Controller Block (PI-HLD)

The PI-HLD block performs input processing, control computation processing, output processing,
and alarm processing.
The only processing timing available for the PI-HLD block is a periodic startup. Selections available
speed scan period (*1), and the high-speed scan period.
ALSO processing possible for the PI-HLD block, refer to:
Control Computation Processing of Sampling PI Controller

Block (PI-HLD)
The table below shows the control computation processing functions of the Sampling PI Controller
Block (PI-HLD):
Table 1.6-2 Control Computation Processing Functions of Sampling PI Controller Block (PI-HLD)
Control computation
Description
processing
Performs PI control computation for each sampling period only during the
PI control computation with hold specified control time, and holds the manipulated output value (MV) for
the remainder of the period.
Gap action
Control output action to an actual manipulated output value (MV). The control output actions
(MV) from changing.
SVL) .
remaining one.
Bumpless switching
manipulated output value (MV) has been switched in a downstream block
in cascade.
becomes satisfied.
Control hold
MAN fallback
AUT fallback
Computer failure
to PRD.
SEE For more information about control computation processing functions of Sampling PI Controller
ALSO Block (PI-HLD), refer to:
PI Control Computation with Hold

The PI control computation with hold is a control algorithm of the Sampling PI Controller Block. It is
a control computation function that performs PI control computation to obtain a manipulated output
value (MV) and manipulated output change (ΔMV).
Characteristics of the PI Control Computation with Hold

The PI control computation with hold action performs PI control for each sampling period (TC) only
during the control time (TC) in an automatic operating mode (AUT, CAS or RCAS), and holds
manipulated output for the remainder of the period (TS - TC).
The figure below shows the sampling PI control action:
Figure 1.6-2 Sampling PI Control Action
Set the sampling period and control time in advance, in accordance with the following principle:
• Sampling period
TS = L+T • (2 to 3)
L : Dead time of the process (second)
T : Lag constant of the process (second)
• Control time
The value of sampling period represents the time required for the process variable (PV) to be
stabilized after the manipulated output is actually output to the process and its effects are
transmitted throughout the process. When the shortest period of a major disturbance affecting the
process is Tn, if Tn is shorter than the sampling period, the control may become impossible.
Therefore, refer the following expression to adjust the sampling period shorter than Tn:
The sampling period and control time are considered as set parameters, and their setting can be
changed during operation.
Computational Expressions of the PI Control Algorithm with

Hold
The computational expressions of the PI control algorithm:
En=PVn-SVn
ΔMVn : Manipulated output change

Kp : Proportional gain
Ks : Scale conversion coefficient
ΔPVn : Process variable change ΔPVn=PVn-PVn-1 (engineering unit)
PVn : Process variable (engineering unit)
SVn : Setpoint value (engineering unit)
En : Deviation
ΔT : Control period
PB : Proportional band (% unit)
TI : Integral time
SH PV scale high limit
The above PI control algorithm is the same as the PV proportional and derivative type PID control
algorithm (I-PD) of the PID Controller Block (PID) except that the former does not have a derivative
term.
Set Parameters of the PI Control Algorithm with Hold

The following are set parameters for control computation processing of the PI control algorithm with
hold:
• Sampling period (TS)
0 to 10000 seconds.
The default is 1 second.
• Control time (TC)
0 to 10000 seconds.
• Proportional band (P)
0 to 1000 %.
When P=0, the proportional action does not function but only the integral action is performed.
The proportional gain Kp is “1” when only the integral action is performed.
• Integral time (I)
0.1 to 10000 seconds.

PI-HLD Action after Hold

▼ PI-HLD Action after Hold
When PI-HLD starts the control calculation after its Hold period elapsed, the previous process
variable is used as the PVn-1 in proportional term computation, the following two methods can be
selected:
• Use the PV right before the Hold status as the PVn-1
• Use the current PV as the PVn-1 (Same as the PI-HLD in CENTUM-XL)
The two calculation methods can be selected on FCS properties sheet. Check the check box of
[CENTUM-XL compatible] in the column of [PI-HLD Control Action after Hold]. When this option is
checked, the PVn-1 in the control algorithm uses the current process variable PVn. Otherwise, the PVn-
1 in the control algorithm uses the process variable right before the Hold started. By default,
[CENTUM-XL compatible] is not checked.
Externally Started Sampling PI Control Action

When “0” is set for the sampling period (TS), the externally started sampling PI control action will
take place, as shown in the figure below.
The externally started sampling PI control action starts control when a switch signal is received from
outside the Sampling PI Controller Block.
The externally started sampling PI control action starts PI control when the control switch (CSW) is
turned ON from outside the block during automatic operation. Once started, PI control will continue
throughout the control time (TC). When the TC time has elapsed, output is held and the control
switch (CSW) is turned OFF until the next action is started.
Figure 1.6-3 Externally Started Sampling PI Control Action
The control switch (CSW) is turned ON by other function block, such as a sequence control block.
When the control switch (CSW) is turned OFF forcibly from outside the block during the control time,
output is held immediately.
Data Items - PI-HLD

Table 1.6-3 Data Items of Sampling PI Controller Block (PI-HLD) (1/2)

Item Not (*1) (*2)
Alarm detection
AF ----- 0
specification
Alarm masking
AOFS ----- 0
specification
unit as PV
unit as PV
unit as PV
unit as PV
RMV Δ (*7) MSL
unit as MV
unit as MV
HH x SL to SH SH
setpoint
LL x SL to SH SL
setpoint
High - limit alarm
PH x SL to SH SH
setpoint
PVP -----
Sample unit as PV

Table 1.6-4 Data Items of Sampling PI Controller Block (PI-HLD) (2/2)

Item Not (*1) (*2)
MH x MSL to MSH MSH
limit setpoint
ML x MSL to MSH MSL
limit setpoint
TS Sampling period x 0 to 10,000 seconds 1 second
TC Control time x 1 to 10,000 seconds 1 second
value
Value in the same
Value in the same
Value in the same
Value in the same

SEE For more information about valid block modes of the PI-HLD block, refer to:
1.7 PID Controller Block with Batch Switch (PID-BSW) Page 1 of 8
1.7 PID Controller Block with Batch Switch (PID-

BSW)
PID Controller Block with Batch Switch (PID-BSW) outputs a high limit or low limit manipulated
output signal unconditionally when control deviation becomes large. This block may be applied to
batch reactor temperature control process.
PID Controller Block with Batch Switch (PID-BSW)

▼ Connection
The PID Controller Block with Batch Switch (PID-BSW) prevent overshooting so that the process
variable (PV) may be brought closer to the target value sooner.
The figure below shows a function block diagram of the PID Controller Block with Batch Switch (PID-
BSW):
Figure 1.7-1 Function Block Diagram of PID Controller Block with Batch Switch (PID-BSW)
the PID Controller Block with Batch Switch (PID-BSW):
Table 1.7-1 Connection Methods and Connected destinations of the I/O Terminals of PID
Controller Block with Batch Switch (PID-BSW)

Measurement
IN x Δ x x
input
Manipulated
OUT x x x x
output
Reset signal 1
RL1 x Δ x x
input
Reset signal 2
RL2 x Δ x x
input
Tracking signal
TIN input x Δ x x
Tracking SW
TSI x Δ x x x
input
Interlock SW
INT x Δ x x x
input
link block (ADL).
Function of PID Controller Block with Batch Switch

(PID-BSW)
The PID-BSW block performs input processing, control computation processing, output processing,
The only processing timing available for the PID-BSW 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.
ALSO processing possible for the PID-BSW block, refer to:
Control Computation Processing of PID Controller Block with

Batch Switch (PID-BSW)
The table below shows the control computation processing functions of PID Controller Block with
Batch Switch (PID-BSW).
Table 1.7-2 Control Computation Processing Functions of PID Controller Block with Batch Switch
(PID-BSW)
Control
computation Description
processing
PID with two-level Changes the manipulated output computational expression in accordance with the
output switching value of control deviation. PID control computation is performed in a steady state.
Converts the manipulated output change (ΔMV) during each control period to an actual
Control output
manipulated output value (MV). The control output actions include “positional type”
action
and “velocity type.”
Control action Switches the direction of the output action (reverse action or direct action) in
direction accordance with the increase or decrease in deviation.
Performs correction computation using values read from the connection destinations of
Reset limit function input terminals RL1 and RL2 during PID control computation. This function prevents
reset windup.
Process variable
Causes the setpoint value (SV) to agree with the process variable (PV).
tracking
Setpoint value
Limits the setpoint value (SV) within the setpoint high/low limits (SVH, SVL).
limiter
Setpoint value Causes two of the three setpoint values (SV, CSV, RSV) to agree with the remaining
pushback one.
Switches the manipulated output value (MV) without causing it to change abruptly
Bumpless switching when the block mode has been changed or when the manipulated output value (MV)
has been switched in a downstream block in cascade.
Initialization Changes the block mode to IMAN to temporarily suspend the control action. This action
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
Computer failure
operating in the RCAS or ROUT mode. This action takes place when the computer
failure condition becomes satisfied.
Block mode change Stops the control action of function blocks currently operating automatically, while
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
PRD mode action
value (MV) when the block mode has been changed to PRD.
SEE For more information about control computation processing functions applied in PID Controller
ALSO Block with Batch Switch (PID-BSW), refer to:
PID Control Computation with Two-Level Output

Switching
In PID control computation with two-level output switching, the computational expression for a
manipulated output value (MV) is switched in accordance with the state of control deviation, as
shown below:
• When the control deviation is negative and excessive.
• When the control deviation is positive, or negative and extremely small.
The figure below shows an example of control action performed by the PID Controller Block with
Batch Switch (PID-BSW) when the control action direction is reverse:
Figure 1.7-2 Example of Control Action (Reverse Action) Performed by PID Controller Block with
Batch Switch (PID-BSW)
Control Algorithms when the Deviation is Negative and

Excessive
The following expressions represent the algorithms of calculating the manipulated output value
when the process variable (PV) is smaller than the setpoint value minus deviation alarm setpoint (SV-
| DL |) value:
• When the control action direction is “reverse”
Manipulated output value (MV)=Manipulated variable high-limit setpoint (MH)
• When the control action direction is “direct”
Manipulated output value (MV)=Manipulated variable low-limit setpoint (ML)
When the deviation immediately after the start of batch operation exceeds the deviation alarm
setpoint, the PID Controller Block with Batch Switch (PID-BSW) outputs a manipulated output value
(MV) that is the same as the manipulated variable high-limit setpoint (MH) or manipulated variable
low-limit setpoint (ML). As a result, the process variable quickly approaches the setpoint value.
Control Algorithms when the Control Deviation is Positive, or

Negative but Small
The following expressions represent the algorithms of calculating the control output value when the
process variable (PV) is larger than the setpoint value minus deviation alarm setpoint (SV-| DL |)
value:
• When the control action direction is “Reverse”
Manipulated output value (MV)=Manipulated variable high-limit setpoint (MH)−Bias setpoint
(BIAS). PID control computation is performed by using the result obtained from the above
calculation as an initial value.
• When the control action direction is “Direct”
Manipulated output value (MV)=Manipulated variable low-limit setpoint (ML)+Bias setpoint
(BIAS)
PID control computation is performed by using the result obtained from the above calculation 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 manipulated 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 For more information about PID control algorithm, refer to:
ALSO " PID Control Computation" in 1.5, "PID Controller Block (PID)"
Lockup Function
Once the PID control action resumes, even when the deviation exceeds the deviation alarm setpoint
(DL), the manipulated output value (MV) does not immediately ramp to the manipulated variable
high-limit setpoint (MH) or manipulated output low-limit setpoint (ML). This is because of the lockup
function.
When the following condition exists, the manipulated output value (MV) does not change to the
manipulated variable high-limit setpoint (MH) if the control action direction is Reverse, nor to the
manipulated variable low-limit setpoint (ML) if the control action direction is Direct:
• Condition
PV<SV-| DL |-LK
LK: Lockup setpoint
Set Parameters of the PID Control Computation with Two-

Level Output Switching
The set parameters of the PID control computation with two-level output switching:
0 to 1000 %.
When P = 0, the proportional action does not function but only the integral action is performed.
• Derivative time (D)
0 to 10000 seconds.
When D=0, the derivative action does not function.
• Deviation alarm setpoint (DL)
Engineering unit data between 0 and the ±PV scale span range limit.
The default is the ±scale span.
• Bias setpoint (BIAS)

Engineering unit data within the MV scale span range.
The default is “0.”
• Lockup setpoint (LK)
Engineering unit data within the PV scale span range.
• Manipulated variable high-limit setpoint (MH)
Engineering unit data within the MV scale range.
The default is the MV scale’s high limit.
• Manipulated variable low-limit setpoint (ML)
Engineering unit data within the MV scale range.
The default is the MV scale’s low limit.
Data Items - PID-BSW

Table 1.7-3 Data Items of PID Controller Block with Batch Switch (PID-BSW) (1/2)

Item Not (*1) (*2)
Alarm detection
AF ----- 0
specification
Alarm masking
AOFS ----- 0
specification
unit as PV
unit as PV
unit as PV
unit as PV
Manipulated output
MV Δ (*6) MV engineering unit value MSL
value

RMV Δ (*7) MSL
unit as MV
unit as MV
HH x SL to SH SH
setpoint
LL x SL to SH SL
setpoint
High - limit alarm
PH x SL to SH SH
setpoint
Low - limit alarm
PL x SL to SH SL
setpoint
PVP -----
Sample unit as PV
Table 1.7-4 Data Items of PID Controller Block with Batch Switch (PID-BSW) (2/2)

Item Not (*1) (*2)
MH x MSL to MSH MSH
limit setpoint
ML x MSL to MSH MSL
limit setpoint
LK Lockup setpoint x 0 to (SH - SL) 0.0
value
BIAS Bias setpoint value x 0 to (MSH - MSL) 0.0

Value in the same
Value in the same
Value in the same
Value in the same
SEE For more information about valid block modes of the PI-BSW block, refer to:
1.8 Two-Position ON/OFF Controller Block (ONOFF), Enhanced Two-Position ON/... Page 1 of 7
1.8 Two-Position ON/OFF Controller Block

(ONOFF), Enhanced Two-Position ON/OFF
Controller Block (ONOFF-E)
The Two-Position ON/OFF Controller Block (ONOFF) performs control by ON/OFF action via a single
contact output. The Enhanced Two-Position ONOFF Controller Block (ONOFF-E) functions the same
but have the additional capability to connect to FF faceplate blocks and fieldbus function blocks.
Two-Position ON/OFF Controller Block (ONOFF),

Enhanced Two-Position ON/OFF Controller Block
(ONOFF-E)
▼ Connection
The ONOFF and ONOFF-E (*1) blocks turn On or Off the contact output according to the result in
comparing the process variable (PV) and setpoint value (SV).
*1: ONOFF-E block can be applied to all field control stations except standard PFCS. When using ONOFF-E
block, it is necessary to add the option [DIOENH] on the [Constant] tab of the FCS properties sheet.
The figure below shows a function block diagram of the Two-Position ON/OFF Controller Block
(ONOFF or ONOFF-E) :
Figure 1.8-1 Function Block Diagram of ONOFF, ONOFF-E Block
the Two-Position ON/OFF Controller Block (ONOFF):
Table 1.8-1 Connection Methods and Connected destinations of the I/O Terminals of Two-
Position ON/OFF Controller Block (ONOFF):
Connection method (*1) Connection destination (*1)

Measurement
IN x Δ x x
input
Manipulated
OUT x Δ x x
output

Compensation
BIN x Δ x x
input
Interlock SW
INT x Δ x x x
input
link block (ADL).
the Enhanced Two-Position ON/OFF Controller Block (ONOFF-E):
Table 1.8-2 Connection Methods and Connected destinations of the I/O Terminals of Enhanced
Two-Position ON/OFF Controller Block (ONOFF-E):

Measurement
IN x Δ x x
input
Manipulated
OUT x x x x
output
Compensation
BIN x Δ x x
input
Interlock SW
INT x Δ x x x
input
link block (ADL).
Function of Two-Position ON/OFF Controller Block

(ONOFF) and Enhanced Two-Position ON/OFF
The ONOFF and ONOFF-E blocks perform input processing, control computation processing, output
processing, and alarm processing.
The only processing timing available for the ONOFF and ONOFF-E blocks are 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.
ALSO processing possible for the ONOFF, ONOFF-E block, refer to:

Control Computation Processing of Two-Position ON/OFF

Controller Block (ONOFF) and Enhanced Two-Position ON/OFF
The table below shows the control computation processing functions of Two-Position ON/OFF
Controller Block (ONOFF or ONOFF-E):
Table 1.8-3 Control Computation Processing Functions of Two-Position ON/OFF Controller Block
(ONOFF) and Enhanced Two-Position ON/OFF Controller Block (ONOFF-E)
Control computation
Description
processing
Compares the deviation with ON/OFF hysteresis and obtains a manipulated
ON/OFF two-position control
output value (MV).
Control output action to an actual manipulated output value (MV). The available control output
actions are of “positional type” only.
block is operating automatically. Only “input compensation” can be used.
I/O Input Adds the I/O compensated value (VN) received from the outside to the
compensation compensation input signal of the PID control computation.
SVL).
remaining one.
becomes satisfied.
Control hold block mode.
MAN fallback
Changes the block mode to AUT when the function block is operating in the
CAS or PRD mode, so that the control action is continued using values set
AUT fallback
by the operator. This action takes place when the AUT fallback condition
becomes satisfied.
Computer failure
Block mode change interlock automatically, while disabling the stopped function blocks from changing to
the automatic operating mode.
SEE For more information about the control computation processing functions applied in Two-Position
ALSO ON/OFF Controller Block (ONOFF and ONOFF-E), refer to:
Output Processing Specific to Two-Position ON/OFF Controller

Block (ONOFF), Enhanced Two-Position ON/OFF Controller
Block (ONOFF-E)
The ONOFF and ONOFF-E blocks perform “two-position status output” as output signal conversion.
TIP The output tracking of ONOFF-E block can be set on the function block detail builder in related to
the settings of output processing. The ONOFF block does not have the capability of output
tracking.
SEE For more information about the output tracking, refer to:
ALSO 4.5, “Output Tracking” in Function Blocks Overview (IM 33J15A20-01EN)
ON/OFF Two-Position Control Computation

▼ ON/OFF Hysteresis
The ON/OFF two-position control computation is a control algorithm of the Two-Position ON/OFF
Controller Block (ONOFF and ONOFF-E). This algorithm compares the deviation (En=PVn-SVn) with
positive or negative ON/OFF hysteresis and outputs the manipulated output value (MV) by 0 % or
100 % based on the comparison result.
The action of the control algorithm varies with the control action directions.
Control Algorithm in Direct Action

Performs computation that outputs the manipulated output value (MVn) by 100 % (ON) when the
deviation (En) exceeds the positive ON/OFF hysteresis value, and by 0 % (OFF) when the deviation
falls below the negative ON/OFF hysteresis value.
Control Algorithm in Reverse Action

Performs computation that outputs the manipulated output value (MVn) by 0 % (OFF) when the
deviation (En) exceeds the positive ON/OFF hysteresis value, and by 100 % (ON) when the deviation
falls below the negative ON/OFF hysteresis value.
The figure below shows an example of the two-position ON/OFF control action:
Figure 1.8-2 Example of the Two-Position ON/OFF Control Action
Use the Function Block Detail Builder to define the ON/OFF hysteresis value.
ON/OFF Hysteresis: Engineering unit data within the PV scale span range.
The default is a value equivalent to 1.0 % of the PV scale span.
Two-Position Status Output

The ONOFF and ONOFF-E blocks perform two-position status output as output signal conversion.
For the 2-position status output, a contact output (1 point) or a internal switch (1 point) designated
to the OUT terminal is turned ON and OFF according to the manipulated output value (MV).
The following table shows the relationship between the manipulated output value (MV) and contact
output status. Note that the manipulated output value (MV) is always expressed in percentage (%).
Table 1.8-4 Relationship between Manipulated Output Value (MV) and Contact Output
Manipulated output value 0% 0.1 to 49.9 % 50 to 99.9 % 100 %

Contact output status OFF OFF ON ON
Data Items - ONOFF, ONOFF-E

Table 1.8-5 Data Items of Two-Position ON/OFF Controller Block (ONOFF or ONOFF-E) (1/2)

Data Name Range
Item Not (*1) (*2)
Alarm detection
AF ----- 0
specification
AOFS ----- 0
Alarm masking
specification
SV Set value Δ (*4) SL
unit as PV
unit as PV
unit as PV
unit as PV
Input compensation
VN x ----- 0
value
MV Manipulated output value Δ (*6) 0 to 100 % 0%
Remote manipulated
RMV Δ (*7) 0 to 100 % 0%
output value
*2: SL: PV scale low limit
Table 1.8-6 Data Items of Two-Position ON/OFF Controller Block (ONOFF or ONOFF-E) (2/2)

Item Not (*1) (*2)
HH x SL to SH SH
setpoint
LL x SL to SH SL
setpoint
High - limit alarm
PH x SL to SH SH
setpoint
PVP -----
Sample unit as PV
Preset manipulated
PMV x 0 to 100 % 0%
output value
PSW Preset MV switch x 0, 1, 2, x 0

unit as PV
unit as PV
SEE For more information about valid block modes of the ONOFF and ONOFF-E blocks, refer to:
1.9 Three-Position ON/OFF Controller Block (ONOFF-G), Enhanced Three-Position ... Page 1 of 8
1.9 Three-Position ON/OFF Controller Block

(ONOFF-G), Enhanced Three-Position
ON/OFF Controller Block (ONOFF-GE)
The Three-Position ON/OFF Controller Block (ONOFF-G) performs control by ON and OFF actions via
two contact outputs. The Enhanced Three-Position ONOFF Controller Block (ONOFF-GE) functions
the same but have the additional capability to connect to FF faceplate blocks and fieldbus function
blocks. Moreover, the output terminals for the two contacts can be defined separately so that the
two irrelevant channels can be used.
Three-Position ON/OFF Controller Block (ONOFF-G),

Enhanced Three-Position ON/OFF Controller Block
(ONOFF-GE)
▼ Connection
The ONOFF-G and ONOFF-GE (*1) Blocks change the ON/OFF status of two contact outputs
depending on whether a process variable (PV) is in the Low/Middle/High position compared to a
setpoint value (SV).
*1: ONOFF-GE block can be applied to all field control stations except standard PFCS. When using ONOFF-
GE block, it is necessary to add the option [DIOENH] on the [Constant] tab of the FCS properties sheet.
The figure below shows the ONOFF-G Block diagram.
Figure 1.9-1 Function Block Diagram of Three-Position ON/OFF Controller Block (ONOFF-G)
the Three-Position ON/OFF Controller Block (ONOFF-G):
Table 1.9-1 Connection Methods and Connected destinations of the I/O Terminals of Three-
Position ON/OFF Controller Block (ONOFF-G):

Measurement
IN x Δ x x
input
Manipulated
OUT x Δ x x
output
Compensation
BIN x Δ x x
input
Interlock SW
INT x Δ x x x
input
link block (ADL).
The figure below shows the ONOFF-GE Block diagram.
Figure 1.9-2 Function Block Diagram of Three-Position ON/OFF Controller Block (ONOFF-GE)
the Enhanced Three-Position ON/OFF Controller Block (ONOFF-GE):
Three-Position ON/OFF Controller Block (ONOFF-GE):

Measurement
IN x Δ x x
input
Manipulated
OUT1 x x x x x
output
Manipulated
OUT2 x x x x x
output
Compensation
BIN x Δ x x
input
Interlock SW
INT x Δ x x x
input
link block (ADL).
If the OUT1 terminal and the OUT2 terminal are connected to different output
modules or if OUT1 terminal and the OUT2 terminal are connected to FF
faceplate blocks or fieldbus function blocks, the simultaneity of the two
outputs are not guaranteed.
Function of Three-Position ON/OFF Controller Block

(ONOFF-G), Enhanced Three-Position ON/OFF
Controller Block (ONOFF-GE)
The ONOFF-G and ONOFF-GE blocks perform input processing, control computation processing,
output processing, and alarm processing.
The only processing timing available for the ONOFF-G and ONOFF-GE blocks are 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.
ALSO processing possible for the ONOFF-G and ONOFF-GE blocks, refer to:
Control Computation Processing of Three-Position ON/OFF

Controller Block (ONOFF-G), Enhanced Three-Position ON/OFF
The table below shows the control computation processing functions of the Three-Position ON/OFF
Controller Block (ONOFF-G, ONOFF-GE):
Table 1.9-3 Control Computation Processing Functions of Three-Position ON/OFF Controller
Block (ONOFF-G, ONOFF-GE)
Control computation
Description
processing
Compares the deviation with ON/OFF hysteresis and obtains a manipulated
ON/OFF three-position control
output value (MV).
Control action direction Switches the direction of the output action (reverse action or direct action)

SVL).
remaining one.
becomes satisfied.
Control hold
MAN fallback
CAS or PRD mode, so that the control action is continued using values set
AUT fallback
by the operator. This action takes place when the AUT fallback condition
becomes satisfied.
Computer failure
SEE For more information about the control computation processing functions applied in Three-
ALSO Position ON/OFF Controller Block (ONOFF, ONOFF-GE) , refer to:
Output Processing Specific to Three-Position ON/OFF

Controller Block (ONOFF-G), Enhanced Three-Position ON/OFF
The ONOFF-G and ONOFF-GE blocks perform “three-position status output” as output signal
conversion.
TIP The output tracking of ONOFF-GE block can be set on the function block detail builder in related
to the settings of output processing. The ONOFF-G block does not have the capability of output
tracking.
SEE For more information about the output tracking, refer to:
ALSO 4.5, “Output Tracking” in Function Blocks Overview (IM 33J15A20-01EN)
ON/OFF Three-Position Control Computation

▼ ON/OFF Hysteresis
The ON/OFF three-position control computation is a control algorithm of the 3-Position ON/OFF
Controller Block (ONOFF-G, ONOFF-GE). This algorithm compares the deviation (En=PVn-SVn) with
neutral status range (DB) that includes an ON/OFF hysteresis and outputs the manipulated output
value (MV) by 0 %, 50 % or 100 % based on the comparison result.
The action of the control algorithm varies with the control action directions.
Use the Function Block Detail Builder to define the ON/OFF hysteresis.
ON/OFF Hysteresis: Engineering unit data within the PV scale span range.
The default is the value equivalent to 2.0 % of the PV scale span.
Control Algorithm in Direct Action

The figure below shows the ON/OFF hysteresis when the control action direction is direct:
Figure 1.9-3 ON/OFF Hysteresis in Direct Action
Control Algorithm in Reverse Action

The figure below shows the ON/OFF hysteresis when the control action direction is reverse:
Figure 1.9-4 ON/OFF Hysteresis in Reverse Action
Set Parameter of ON/OFF Three-Position Control Computation

The parameter of the Three-Position ON/OFF Controller Block (ONOFF-G, ONOFF-GE):
Neutral status range (DB): Engineering unit data within the PV scale range.
The default is 0.
Three-Position Status Output

The ONOFF-G and ONOFF-GE blocks perform three-position status output as output signal
conversion.
In the 3-position status output, the contact output (2 points) are turned ON or OFF according to the
The following table shows the contact output status in relationship to the manipulated output value
(MV) at 0 %, 50 %, 100 % and other instances. Note that the manipulated output value (MV) is
always expressed in percentage (%).
Table 1.9-4 Relationship of the Manipulated Output Value (MV) and Contact Output Status (At 0
%, 50 % and 100 %)
Manipulated output value 0 % 50 % 100 %

Contact 1 output status OFF OFF ON
Contact 2 output status ON OFF OFF
Table 1.9-5 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
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
that the succeeding contact is not assigned for other contact output module.
When the ONOFF-GE block is configured for tree-position status outputs, the OUT1 terminal of the
ONOFF-GE block can be designated with a contact channel number as the first output and the OUT2
terminal can be designated with a different contact channel number as the second output.
Data Items - ONOFF-G, ONOFF-GE

Table 1.9-6 Data Items of Three-Position ON/OFF Controller Block (ONOFF-G, ONOFF-GE) (1/2)

Data Name Range
Item Not (*1) (*2)
Alarm detection
AF ----- 0
specification
Alarm masking
AOFS ----- 0
specification
unit as PV
unit as PV
unit as PV
unit as PV
Input compensation
VN x ----- 0
value
Remote manipulated
RMV Δ (*7) 0 to 100 % 0%
output value
Table 1.9-7 Data Items of Three-Position ON/OFF Controller Block (ONOFF-G, ONOFF-GE) (2/2)

Item Not (*1)
HH x SL to SH SH
setpoint
LL x SL to SH SL
setpoint
PH High - limit alarm setpoint x SL to SH SH
PVP Velocity-Reference Sample -----
unit as PV
SVH Setpoint high-limit x SL to SH SH
SVL Setpoint low-limit x SL to SH SL
DB Neutral status range x 0 to (SH - SL) 0.0
PMV x 0 to 100 % 0%
value
unit as PV
unit as PV
SEE For more information about valid block modes of the ONOFF-G, ONOFF-GE blocks, refer to:
1.10 Time-Proportioning ON/OFF Controller Block (PID-TP) Page 1 of 8
1.10 Time-Proportioning ON/OFF Controller

Block (PID-TP)
The Time-Proportioning ON/OFF Controller Block (PID-TP) changes ON time of contact output
proportional to the result of the PID control computation. This block is used for temperature control
of an electric furnace.
Time-Proportioning ON/OFF Controller Block (PID-TP)

▼ Connection
Time-Proportioning ON/OFF Controller Block (PID-TP) changes ON/OFF time ratio in proportion to
the manipulated output value (MV) obtained by PID control computation to the overall ON/OFF
period. Only the basic scan-cycle can be applied to PID-TP.
The figure below shows the function block diagram of Time-Proportioning ON/OFF Controller Block
(PID-TP):
Figure 1.10-1 Function Block Diagram of Time-Proportioning ON/OFF Controller Block (PID-TP)
the Time-Proportioning ON/OFF Controller Block (PID-TP):
Table 1.10-1 Connection Methods and Connected destinations of the I/O Terminals of Time-
Proportioning ON/OFF Controller Block (PID-TP):

Measurement
IN x Δ x x
input
Manipulated
OUT x Δ x
output
Reset signal 1
RL1 x Δ x x
input
Reset signal 2
RL2 x Δ x x
input
Compensation
BIN x Δ x x
input
Interlock SW
INT x Δ x x x
input
link block (ADL).
Function of Time-Proportioning ON/OFF Controller

Block (PID-TP)
The PID-TP block performs input processing, control computation processing, output processing, and
alarm processing.
The only processing timing available for the PID-TP block is a periodic startup. Moreover, only the
basic scan period can be selected as the scan period to execute the periodic startup.
ALSO processing possible for the PID-TP block, refer to:
Control Computation Processing of Time-Proportioning

ON/OFF Controller Block (PID-TP)
The table below shows the control computation processing functions of the Time-Proportioning
ON/OFF Controller Block (PID-TP):
Table 1.10-2 Control Computation Processing Functions of Time-Proportioning ON/OFF
Controller Block (PID-TP)
Control computation
Description
processing
Performs integral actions in accordance with changes in the setpoint value
PV proportional and derivative
(SV). This ensures stable control characteristics even when the setpoint
PID control
value changes abruptly. (*1)
Gap action
Converts the manipulated output change (ΔMV) during each control
period to an actual manipulated output value (MV). The control output

Control output action
actions are of “positional type” only. (*2)
Switches the direction of the output action (reverse action or direct
action) in accordance with the increase or decrease in deviation.
Adjusts the manipulated output change (ΔMV) to “0” when the deviation
Deadband action is within the deadband range, in order to stop the manipulated output
value (MV) from changing.
SVL).
remaining one.
Initialization manual action. This action takes place when the initialization manual condition is
established.
MAN fallback
action takes place when the MAN fallback condition is established.
AUT fallback
backup mode when an error is detected by supervisory computer while
Computer failure
the function block is operating in the RCAS or ROUT mode. This action
takes place when the computer failure condition is established.
Stops the automatic control action of function blocks. And prevents the
Interlock on block mode change function blocks currently operating in manual mode from changing to
automatic mode.
*1: On FFCS series, KFCS2, KFCS, LFCS2, and LFCS, the PID control algorithm can be selected on the
Function Block Detail Builder. The default is “PV proportional and derivative type PID control (I-PD).”
*2: On FFCS series, KFCS2, KFCS, LFCS2, and LFCS, the PID output action can be selected as “Velocity
Type” on the Function Block Detail Builder. However, the default is “Positional Type.”
SEE For more information about control computation processing functions applied in the Time-
ALSO Proportioning ON/OFF Controller Block (PID-TP), refer to:
Output Processing Specific to Time-Proportioning ON/OFF

Controller Block (PID-TP)
The PID-TP block performs “time-proportioning ON/OFF output” as output signal conversion.
PV Proportional and Derivative Type PID Control (I-PD)

The PV proportional and derivative type PID control algorithm (I-PI) is a control algorithm of the
Time-Proportioning ON/OFF Controller Block (PID-TP).
This algorithm performs only integral actions when the setpoint value changes, and ensures stable
control characteristics even when the setpoint value changes abruptly by a numerical value entry.
At the same time, the algorithm ensures proper control in response to the characteristic changes
occurring in the controlled process, load variations and disturbances by performing proportional,
derivative and integral Control Action accordingly.
Computational Expression of the PV Proportional and

Derivative Type of PID Control
The computational expression of the PV proportional and derivative type of PID control:
ΔPVn : Process variable change ΔPVn=PVn-PVn-1
Set Parameters of the PV Proportional and Derivative Type of

PID Control
The parameters the PV proportional and derivative type of PID control (I-PID):
0 to 1000 %
When P=0, only the integral action is performed.
When P=0, the proportional gain Kp=1.
0.1 to 10000 seconds
• Derivative time (D)
0 to 10000 seconds
No derivative action is performed when D=0.
Control Algorithms Other Than PV Proportional and

Derivative (I-PD) : FFCS
Series/KFCS2/KFCS/LFCS2/LFCS
▼ PID Control Algorithm
For control computation, the PID-TP block holds the same control algorithms as a PID controller
block. The algorithms are:
The control algorithm can be specified on the Function Block Detail Builder:
Choose one from the followings.
The default is "PV proportional and derivative type PID control (I-PD)."
When the block mode of the PID Controller Block is remote cascade (RCAS), the PID control
algorithm [Automatic determination] and [Automatic determination 2] will act as follows:
• Automatic determination type: Same actions as in the cascade (CAS) mode.
• Automatic determination type 2: Same actions as in the automatic (AUT) mode.
SEE For more information about PV proportional and derivative type PID control (I-PD) algorithm,
ALSO refer to:
" PV Proportional and Derivative Type PID Control (I-PD)" in 1.10, "Time-Proportioning
ON/OFF Controller Block (PID-TP)"
For more information about the control algorithms other than PV proportional and derivative type
PID control (I-PD), refer to:
" PID Control Computation" in 1.5, "PID Controller Block (PID)"
Time-Proportioning ON/OFF Output

▼ Time-Proportioning ON/OFF Period
The PID-TP block performs time-proportioning ON/OFF output as output signal conversion.
In the time-proportioning ON/OFF output, a contact output (1 point) defined to the OUT terminal is
turned ON for the period of time proportioning to the manipulated output value (MV) within the
ON/OFF period.
Figure 1.10-2 Operation of Time-Proportioning ON/OFF Output
The time-proportioning ON/OFF output is always off against 0 % and on against 100 % of the
manipulated output value (MV) respectively. For instance, if the ON/OFF period is 10 seconds and
manipulated output value (MV) is 80 %, the ON time will be 8 seconds.
The time-proportioning ON/OFF period is set through the Function Block Detail Builder.
Time-proportioning ON/OFF Period: 1.00 to 256.00 seconds
Default is 1.00 second.
If there are multiple PID-TP blocks, their simultaneous turning on at the beginning of the ON/OFF
period will cause a large fluctuation in the load of power supply for the final control element (such as
heaters). To reduce such load fluctuation, the phases of PID-TP blocks’ ON/OFF outputs are
automatically shifted.
• Phasing the ON/OFF period of the function blocks. The phasing is performed according to the
internal block numbers so as to prevent the multiple blocks ON/OFF in the same phase (*1).
• Phasing the ON/OFF period of the I/O modules. For the “time-proportioning ON/OFF pulse
period” in the Details Setting dialogue box of IOM Builder, set the same value as the “time-
proportioning ON/OFF period” specified with Function Block Detail Builder. In addition,
specify “Phasing” in the Details Setting dialogue box of IOM Builder so as to prevent a heavy
load caused by multiple outputs ON/OFF in the same period (*2).
*1: The function is supported in SFCS and PFCS
*2: The function is supported in FFCS series, KFCS2, KFCS, LFCS2, and LFCS
After FCS initial start, the PID-TP MV will be forced to 0 (MSL). The MV saved
by [Save tuning parameter] command will be ignored.
Data Items - PID-TP

Table 1.10-3 Data Items of Time-Proportioning ON/OFF Controller Block (PID-TP) (1/2)

Item Not (*1) (*2)
Alarm detection
AF ----- 0
specification
Alarm masking
AOFS ----- 0
specification

unit as PV
unit as PV
unit as PV
unit as PV
Input compensation
VN x ----- 0
value
Remote manipulated
RMV Δ (*7) 0 to 100 % 0%
output value
RLV1 Reset limit value1 0 to 100 % 0%
RLV2 Reset limit value 2 0 to 100 % 0%
HH x SL to SH SH
setpoint
LL x SL to SH SL
setpoint
High - limit alarm
PH x SL to SH SH
setpoint
PVP -----
Sample unit as PV
Table 1.10-4 Data Items of Time-Proportioning ON/OFF Controller Block (PID-TP) (2/2)

Item Not (*1)
MH x 0 to 100 % 100 %
limit setpoint
ML x 0 to 100 % 0%
limit setpoint
20
I Integral time x 0.1 to 10,000 seconds
seconds
PMV x 0 to 100 % 0%
value
OPHI Output high-limit index x 0 to 100 % 100 %
OPLO Output low-limit index x 0 to 100 % 0%
Value in the same
Value in the same
SEE For more information about valid block modes of the PID-TP block, refer to:
1.11 PD Controller Block with Manual Reset (PD-MR) Page 1 of 7
1.11 PD Controller Block with Manual Reset

(PD-MR)
PD Controller Block with Manual Reset (PD-MR) performs proportional-derivative (PD) control
function. This block may be applied to programmed temperature control process.
PD Controller Block with Manual Reset (PD-MR)

▼ Connection
The PD Controller Block with Manual Reset (PD-MR) performs proportional (P) and derivative (D)
control, while the integral (I) may be manually set to be applied to the control function.
In programmed temperature control process, operating conditions do not remain the same
throughout the process time. For example, a chemical process is accompanied by momentary
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):
Figure 1.11-1 Function Block Diagram of PD Controller Block with Manual Reset (PD-MR)
the PD Controller Block with Manual Reset (PD-MR):
Table 1.11-1 Connection Methods and Connected destinations of the I/O Terminals of PD
Controller Block with Manual Reset (PD-MR)

Measurement
IN x Δ x x
input

Manipulated
OUT x x x x
output
Compensation
BIN x Δ x x
input
Tracking signal
TIN x Δ x x
input
Tracking SW
TSI x Δ x x x
input
Interlock SW
INT x Δ x x x
input
link block (ADL).
Function of PD Controller Block with Manual Reset (PD-

MR)
The PD-MR block performs input processing, control computation processing, output processing,
The only processing timing available for the PD-MR block is a periodic startup. Selections available
ALSO processing possible for the PD-MR block, refer to:
Control Computation Processing of PD Controller Block with

Manual Reset (PD-MR)
The table below shows the control computation processing functions of the PD Controller Block with
Manual Reset (PD-MR):
Table 1.11-2 Control Computation Processing Functions of PD Controller Block with Manual
Reset (PD-MR)
Control computation
Description
processing
PD control with manual reset Performs PD actions. The reset value (MR) is set manually.
SVL).
remaining one.
Bumpless switching abruptly when the block mode has been changed or when the manipulated
output value (MV) has been switched in a downstream block in cascade.
Prevents abrupt changes in the manipulated output value (MV) by
Bumpless
Balance action initializing the balance term in the manipulated output computational
switching
expression.
becomes satisfied.
MAN fallback
AUT fallback
Computer failure
PRD mode action manipulated output value (MV) when the block mode has been changed to
PRD.
SEE For more information about the control computation processing available with the PD Controller
ALSO Block with Manual Reset (PD-MR), refer to:
PD Control with Manual Reset

The PD control with manual reset performs proportional and derivative (PD) actions. The reset value
(MR) must be set manually.
Computational Expression of the PD Control with Manual Reset

The computational expression of the PD control with manual reset:
En=PVn-SVn
CALCn: Calculated output value

Kp: Proportional gain
Ks: Scale conversion coefficient
En: Deviation
PVn: Process variable (engineering unit)
SVn: Setpoint value (engineering unit)
ΔPVn: Process variable change ΔPVn=PVn-PVn-1
MR: Manual reset value
BLn: Balance term. A correction variable used for bumpless switching from MAN to AUT.
TD: Derivative time
ΔT: Control period
Tbl: Balance rate time
In an automatic mode (AUT, CAS or RCAS), the calculated output value (CALCn) is converted into a
manipulated output value (MV) through output processing.
Set Parameters of the PD Control with Manual Reset

The parameters of the PD control with manual reset:
1 to 1000 %
• Derivative (D)
0 to 1000 seconds
When D=0, the proportional action does not function.

• Manual reset value (MR)
Engineering unit data within the MV scale range
• Balance rate time (I)
0.1 to 10000 seconds
The balance rate time (Tbl) is set to the parameter I on operation and monitoring functions.
If the balance rate time of control block is set to zero or to a value beyond the
purpose calculation block or sequence table block to set the value of balance
rate time, it is necessary to enforce the value within the proper range and to
avoid it to be set to zero.
Bumpless Switching
The bumpless switching function switches the function block mode or switches the cascade
connected downstream block’s manipulated output value (MV) without causing its own manipulated
output value (MV) to change abruptly (i.e., bumpless switch).
The PD Controller Block with Manual Reset performs bumpless switching based on “balance action.”
The PD Controller Block with Manual Reset performs bumpless switching of the block mode from
manual (MAN) to automatic (AUT), by using a value obtained by the following expression as the
initial value of the balance term (BLn0):
MV : Output in the manual mode

The figure below shows the balance action of the PD Controller Block with Manual Reset:
Figure 1.11-2 Bumpless Switching by PD Controller Block with Manual Reset (Balance Action)
When the block mode is not remote output (ROUT) or out of service (O/S), the remote manipulated
output value (RMV) tracks the manipulated output value (MV).
Data Items - PD-MR

Table 1.11-3 Data Items of PD Controller Block with Manual Reset (PD-MR) (1/2)

Item Not (*1) (*2)
Alarm detection
AF ----- 0
specification
Alarm masking
AOFS ----- 0
specification
unit as PV
unit as PV
unit as PV
unit as PV
Input compensation
VN x ----- 0
value
RMV Δ (*7) MSL
CALC Calculated output value MSL
unit as MV
HH x SL to SH SH
setpoint
LL x SL to SH SL
setpoint
High - limit alarm
PH x SL to SH SH
setpoint
PVP -----
Sample unit as PV
Table 1.11-4 Data Items of PD Controller Block with Manual Reset (PD-MR) (2/2)

Item Not (*1) (*2)
MH x MSL to MSH MSH
limit setpoint
ML x MSL to MSH MSL
limit setpoint
I Balancing rate time x 0.1 to 10,000 seconds 10 seconds
MR Manual reset value x MSL to MSH MSL
value
Value in the same
Value in the same
Value in the same
Value in the same
SEE For more information about valid block modes of the PD-MR block, refer to:
1.12 Blending PI Controller Block (PI-BLEND) Page 1 of 10
1.12 Blending PI Controller Block (PI-BLEND)

Blending PI Controller Block (PI-BLEND) may be applied to the multiple elements flow control
(blending control) to maintain the totalized flow value of each blending component at a constant
ratio (blending ratio).
Blending PI Controller Block (PI-BLEND)

▼ Connection
The figure below shows a function block diagram of Blending PI Controller Block (PI-BLEND):
Figure 1.12-1 Function Block Diagram of Blending PI controller Block (PI-BLEND)
Blending PI Controller Block (PI-BLEND):
Table 1.12-1 Connection Methods and Connected Destinations of the I/O Terminals of Blending
PI Controller Block (PI-BLEND)

reference reference connection I/O I/O block
Measurement
IN x Δ x x
input
Manipulated
OUT x x x x
output
Tracking signal
TIN x Δ x x
input
Tracking SW
TSI x Δ x x x
input
Interlock SW
INT x Δ x x x
input
link block (ADL).
Function of Blending PI Controller Block (PI-BLEND)

The PI-BLEND block performs input processing, control computation processing, output processing,
The only processing timing available for the PI-BLEND block is a periodic startup. Selections
ALSO processing possible for the PI-BLEND block, refer to:
Control Computation Processing of Blending PI Controller

Block (PI-BLEND)
The table below shows the control computation processing functions of Blending PI Controller Block
(PI-BLEND):
Table 1.12-2 Control Computation Processing Functions of Blending PI controller Block (PI-
BLEND)
Control computation
Description
processing
Performs proportional (P) control and integral (I) actions based on cumulative
PI control based on
deviation, and obtains a manipulated output value (MV) and manipulated output
cumulative deviation
change (ΔMV).
Converts the manipulated output change (ΔMV) during each control period to an
Control output action actual manipulated output value (MV). The control output actions
Switches the direction of the output action (reverse action or direct action) in
accordance with the increase or decrease in deviation.
Process variable
Causes the setpoint value (SV) to agree with the process variable (PV).
tracking
Setpoint value limiter Limits the setpoint value (SV) within the setpoint high/low limits (SVH, SVL).
remaining one.
Bumpless switching when the block mode has been changed or when the manipulated output value
(MV) has been switched in a downstream block in cascade.
Bumpless Balance Prevents abrupt changes in the manipulated output value (MV) by initializing the
switching action balance term in the manipulated output computational expression.
Changes the block mode to IMAN to temporarily suspend the control action. This
Initialization manual
action takes place when the initialization manual condition becomes satisfied.
Temporarily suspends the control action while maintaining the current block mode.
Control hold
Changes the block mode to MAN to forcibly stop the control action. This action
MAN fallback
takes place when the MAN fallback condition becomes satisfied.
Changes the block mode to AUT when the function block is operating in the CAS or
AUT fallback PRD 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
Computer failure
function block is operating 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
disabling the stopped function blocks from changing to the automatic operating
interlock
mode.
SEE For more information about the control computation processing functions applied in Blending PI
ALSO Controller Block (PI-BLEND), refer to:
Alarm Processing Specific to Blending PI Controller Block (PI-

BLEND)
The “cumulative deviation alarm check” and “control error alarm check,” which are two of the alarm
checks performed by the PI-BLEND block, are specific to this function block.
PI Control Based on Cumulative Deviation

The Blending PI Controller Block (PI-BLEND) performs proportional and integral actions based on
cumulative deviation. The cumulative deviation value (DVn) is obtained by totalizing deviations of the
process variable (PVn) from setpoint value (SVn) for each scan period and performing time scale-
conversion on the totalized deviation.
Computational Expression of the PI Control Algorithm Based

on Cumulative Deviation
DVRn=DVRn-1+(PVn-SVn)
DVRn : Raw cumulative deviation value

DVRn-1 : Previous raw cumulative deviation value
DVn : Cumulative deviation value
TS : Scan period
TK : Time scale conversion coefficient
The time scale conversion is to convert the raw cumulative deviation value that represents a
3
totalized deviation value, from a value of flowrate unit (e.g., m /h) to that in a weight or volume unit
3
(e.g., m ). The time scale conversion coefficient (TK) used in the above computational expression is
a value in seconds representing the unit time of the flowrate unit. For example, if the unit of the
3
process variable (PV) is m /h, set “3600” as a time scale conversion coefficient (TK).
The computational expression of the control algorithm used by the Blending PI Controller Block.
En= PVn-SVn
Kp : Proportional gain
Ks : Scale conversion coefficient
PVn : Process variable (engineering unit)
SVn : Setpoint value (engineering unit)
ESn : Control cumulative deviation (A DV value limited by DL)
BLn : Balance term. A correction variable used for bumpless switching from MAN to AUT.
ΔT : Control period
TI : Integral time
PB : Proportional band (%)
Control Cumulative Deviation Value (ESn) Used in the PI

Control Algorithm Based on Cumulative Deviation
The control cumulative deviation value (ESn) used for PI control computation is equivalent to the
cumulative deviation value (DVn) limited by the deviation alarm setpoint (DL).
• When DVn≥| DL |
ESn= +| DL | • TK
• When-| DL |<DVn<| DL |
ESn=DVRn • TS
• When DVn≤-| DL |
ESn=-| DL | • TK
The cumulative deviation value (DVn) is reset to “0” in the following cases:
• When the cumulative deviation reset switch (RST) is set to “1.”
• When “Yes” is specified for process variable tracking and the block mode changes from manual
(MAN) to automatic (AUT).
When the cumulative deviation reset switch (RST) is set to “1,” it returns to “0” automatically when
resetting is complete.
Set Parameters of the PI Control Algorithm Based on

Cumulative Deviation
The parameters of the PI control algorithm based on cumulative deviation:

• Time scale conversion coefficient (TK)
1 to 100,000
1 to 1000 %
When P = 0, only the integral action is performed.
• Ramp constant (RP)
Set engineering unit data within the scale span range of the manipulated output value (MV).
The default is the MV scale span.
Bumpless Switching
The bumpless switching function switches the function block mode or switches the downstream
block’s manipulated output value (MV) without causing its own manipulated output value (MV) to
change abruptly (i.e., bumpless change).
The Blending PI Controller Block performs bumpless switching based on “balance action.”
The Blending PI Controller Block performs bumpless switching of the block mode from manual
(MAN) to automatic (AUT), by using a value obtained by the following expression as the initial value
of the balance term (BLn0):
MV : Output in the manual mode

When the mode switches to automatic (AUT), the balance term (BLn) approaches “0” with each
control period for the increment of ramp constant, until it finally reaches “0.”
The figure below shows the balance action of Blending PI Controller Block:
Figure 1.12-2 Bumpless Switching by Blending PI Controller Block (PI-BLEND) (Balance Action)
Cumulative Deviation Alarm Check

▼ Accumulated Deviation Alarm
The cumulative deviation alarm check is a function that determines whether the absolute value of
the cumulative deviation (DV) exceeds the absolute value of the cumulative deviation alarm setpoint
value (DL).
When it is determined that the absolute value of the cumulative deviation (DV) exceeds the absolute
value of the cumulative deviation alarm setpoint value (DL) in the positive direction, a positive
direction cumulative deviation alarm (DV+) is activated. Similarly, when it exceeds the setpoint in
the negative direction, a negative direction cumulative deviation alarm (DV-) is activated.
When an alarm has occurred, if the cumulative deviation (DV) absolute value drops lower than the
cumulative deviation alarm setpoint (DL) absolute value minus the alarm hysteresis value (HYS), the
alarm is returned to normal state.
Figure 1.12-3 Actions of Cumulative Deviation Alarm Check
The cumulative deviation alarm check type, cumulative deviation alarm setpoint (DL), cumulative
deviation range (DV) and the alarm hysteresis value can be set.
Cumulative Deviation Alarm Check Types

The cumulative deviation alarm check type is set with the Function Block Detail Builder. The default
is “detection of both directions.”
• Detection of both directions
Monitors the deviation of both the positive and negative directions.
• Detection of single direction
Monitors the deviation of either the positive or negative direction only.
• No alarm
Detection is not performed.
When single direction is selected for the cumulative deviation alarm check type, only the deviation in
the positive direction is monitored when the cumulative deviation alarm setpoint (DL) has a plus
sign, and only the deviation in the negative direction is monitored when the cumulative deviation
alarm setpoint has a minus sign.
Cumulative Deviation Alarm Setpoint (DL)
The cumulative deviation alarm setpoint is set by the operation and monitoring function.
Cumulative deviation alarm setpoint: Engineering unit data within the ±DV scale span range
Default is DV scale span
Cumulative Deviation Range

▼ DV Range
The cumulative deviation range can be set with the Function Block Detail Builder.
Cumulative deviation range: Set engineering unit data (absolute value)
5 significant figures
Alarm Hysteresis Value

The alarm hysteresis value can be set with the Function Block Detail Builder.
Hysteresis: Engineering unit data within the range of 0 to DV scale span, or percentage data for
the DV scale span
When specifying percentage data, add % after the numeric value.
Default is 1.0 %.
Control Error Alarm Check

▼ Alarm for Control Error
In the control error alarm check it is determined whether or not the absolute value of the cumulative
deviation (DV), which may continue to increase even after the activation of the cumulative deviation
alarm, exceeds the absolute value of the control error alarm setpoint value (VL).
If it is determined that the absolute value of the cumulative deviation (DV) exceeds the absolute
value of the control error alarm setpoint value (VL), a positive direction control error alarm (HDV) is
activated if the deviation is in the positive direction. And, when the deviation is in the negative
direction, a negative direction control error alarm (LDV) occurs.
When an alarm has occurred, if the cumulative deviation (DV) absolute value drops lower than the
control error alarm setpoint (VL) absolute value minus the hysteresis value, the alarm is returned to
normal state.
Figure 1.12-4 Actions of Control Error Alarm Check
The control error alarm check type, control error alarm setpoint (VL) and the alarm hysteresis value
can be set.
Control Error Alarm Check Types

The control error alarm check type is set with the Function Block Detail Builder. The default
is “detection of both directions.”
Monitors the deviation of both the positive and negative directions.
Monitors the deviation of either the positive or negative direction only.
• No alarm
Detection is not performed.
When single direction is selected for the control error alarm check type, only the deviation in the
positive direction is monitored when the control error alarm setpoint (DL) has a plus sign, and only
the deviation in the negative direction is monitored when the control error alarm setpoint has a
minus sign.
Control Error Alarm Setpoint (VL)

The control error alarm setpoint is set by the operation and monitoring function.
Control error alarm setpoint: Engineering unit data within the ±DV scale span range
Default is DV scale span.
Alarm Hysteresis Value

The alarm hysteresis value can be set with the Function Block Detail Builder.
Hysteresis: Engineering unit data within the range of 0 to DV scale span, or percentage data for
the DV scale span.
Default is 1.0 %.
Data Items - PI-BLEND

Table 1.12-3 Data Items of Blending PI Controller Block (PI-BLEND) (1/2)

Item Not (*1) (*2)
Alarm detection
AF ----- 0
specification
Alarm masking
AOFS ----- 0
specification
unit as PV

unit as PV
unit as PV
Cumulative deviation
DV DV engineering unit value 0
value
RMV Δ (*7) MSL
HH x SL to SH SH
setpoint
LL x SL to SH SL
setpoint
High - limit alarm
PH x SL to SH SH
setpoint
Control error alarm
VL x ± (DSH - DSL) DSH - DSL
setpoint
Cumulative deviation
DL x ± (DSH - DSL) DSH - DSL
alarm setpoint
DSH: DV scale high limit
DSL: DV scale low limit
Table 1.12-4 Data Items of Blending PI Controller Block (PI-BLEND) (2/2)

Item Not (*1) (*2)
MH x MSL to MSH MSH
limit setpoint
ML x MSL to MSH MSL
limit setpoint
Time scale conversion
TK x 1 to 100,000 1
coefficient
MSH to
RP Ramp constant x 0 to (MSH - MSL)
MSL
value
Cumulative deviation reset

RST x 0, 1 0
switch
Value in the same
SH PV scale high limit O/S (MAN)
Value in the same
Value in the same
Value in the same
Value in the same
DSH DV scale high limit -----
engineering unit as DV
Value in the same
DSL DV scale low limit -----
engineering unit as DV
SEE For more information about valid block modes of the PI-BLEND block, refer to:
1.13 Self-Tuning PID Controller Block (PID-STC) Page 1 of 6
1.13 Self-Tuning PID Controller Block (PID-STC)

The Self-Tuning PID Controller Block (PID-STC) has both the PID control function and self-tuning
function (STC function). This function block is used to automatically adjust PID parameters (P, I, D).
Self-Tuning PID Controller Block - (PID-STC)

▼ Connection
The Self-Tuning PID Controller Block (PID-STC) has both the PID control function and self-tuning
function (STC function). The STC function automatically sets PID parameters (P, I, D).
The STC function provides the following two merits:
• Maintains optimum controllability in spite of the static and dynamic process characteristics
variation.
• Reduces the work load of tuning operation at process startup.
The figure below shows a function block diagram of Self-Tuning PID Controller Block (PID-STC):
Figure 1.13-1 Function Block Diagram of Self-Tuning PID Controller Block (PID-STC)
The figure below shows a block diagram of the self-tuning control computation processing area of
the Self-Tuning PID Controller Block (PID-STC):
Figure 1.13-2 Block Diagram of the Self-Tuning Control Computation Processing Area
The Self-Tuning PID Controller Block (PID-STC) estimates process characteristics while monitoring
process variables (PV) and manipulated output values (MV) to create an estimated process model.
Optimum PID parameters (P, I, D) are calculated based on the estimated process model.
the Self-Tuning PID Controller Block (PID-STC):
Table 1.13-1 Connection Methods and Connected Destinations of the I/O Terminals of Self-
Tuning PID Controller Block (PID-STC)

Measurement
IN x Δ x x
input
Manipulated
OUT x x x x
output
Reset signal 1
RL1 x Δ x x
input
Reset signal 2
RL2 x Δ x x
input
Compensation
BIN x Δ x x
input
Tracking signal
TIN x Δ x x
input
Tracking SW
TSI x Δ x x x
input
Interlock SW
INT x Δ x x x
input
link block (ADL).
Function of Self-Tuning PID Controller Block (PID-STC)

The PID-STC block performs input processing, control computation processing, output processing,
The only processing timing available for the PID-STC block is a periodic startup. Selections available
ALSO processing possible for the PID-STC block, refer to:

Control Computation Processing of Self-Tuning PID Controller

Block (PID-STC)
The function of the PID-STC block related to control computation processing includes the “PID
control function” and the “self-tuning function (STC function).”
SEE For more information about the PID control function, refer to:
ALSO 1.13.1, "Control Algorithm of Self-Tuning PID Controller Block (PID-STC)"
For more information about the self-tuning function (STC function), refer to:
1.13.2, "Self-Tuning Function (STC Function)"
1.13.3, "Self-Tuning Operating Modes and Block Status"
1.13.4, "Initializer Start"
1.13.5, "Auto-Startup"
1.13.6, "On-Demand Tuning"
1.13.7, "Tuning Parameters of Self-Tuning PID Controller Block (PID-STC)"
1.13.8, "Points of Using Self-Tuning PID Controller Block (PID-STC)"
Data Items - PID-STC

Table 1.13-2 Data Items of Self-Tuning PID Controller Block (PID-STC) (1/3)

Data Name Range
Item Not (*1) (*2)
BSTS Block status ----- RUN, OFF
Alarm detection
AF ----- 0
specification
Alarm masking
AOFS ----- 0
specification
unit as PV
unit as PV
unit as PV
DV Control deviation value unit as PV 0

RMV Δ (*7) MSL
RLV1 Reset limit value 1 x MSL
unit as MV
RLV2 Reset limit value 2 x MSL
unit as MV

Item Not (*1) (*2)
HH x SL to SH SH
setpoint
LL x SL to SH SL
setpoint
Value in the same
Manipulated variable high -
MH x MSL to MSH MSH
limit setpoint
Manipulated variable low -
ML x MSL to MSH MSL
limit setpoint
P Proportional band x 0.0 to 1000.0 % 100.0 %
20.0
I Integral time x 1.0 to 10,000.0 seconds
seconds
0.0
D Derivative time ○ 0.0 to 10,000.0 seconds
seconds
PMV Preset manipulated output x MSL to MSH MSL
value
Value in the same
Value in the same
Value in the same
Value in the same

Item Not (*1)
STC operation mode selection
STC x (*2) -1, 0, 1, 2, 3 0(*2)
switch
1 to 10,000
TR Process 95 % response time x 40 seconds
seconds
1.0 to 20.0 % of
NB Noise band x 1.0 % of PV
PV
OS Control target type x 0, 1, 2, 3 2
0.0 to 20.0 % of
MI MV impulse amplitude x 5.0 % of MV
MV
PMAX Proportional band high limit x 0.0 to 1000.0 % 1000.0 %
PMIN Proportional band low limit x 0.1 to 1000.0 % 0.1 %
0.1 to 1000.0 10000.0
IMAX Integral time high limit x
seconds seconds
0.1 to 1000.0
IMIN Integral time low limit x 0.1 seconds
seconds
0.0 to 1000.0 2000.0
DMAX Derivative time high limit x
seconds seconds
PIDC PID update ratio coefficient x 0.00 to 1.00 1.00
CR Estimation accuracy error 0.000 to 100.000 -----
LM Estimated equivalent dead time -----

0.0 to 10,000.0
seconds
Estimated equivalent first-order 0.0 to 10,000.0
TM -----
lag constant seconds
Estimated equivalent process
GM 0.000 to 100.000 -----
gain
Proportional band calculation
PA 0.0 to 1000.0 % -----
value
0.1 to 10000.0
IA Integral time calculation value -----
seconds
0.0 to 10000.0
DA Derivative time calculation value -----
seconds
*2: For PFCS, if there are more than 5 PID-STC in one FCS, the default value will be -1 for the blocks from
the 6th PID-STC.
For FCSs except PFCS, if there are more than 10 PID-STC in one FCS, the default value will be -1 for
the blocks from the 11th PID-STC.
SEE For more information about valid block modes of the PID-STC block, refer to:
1.13.1 Control Algorithm of Self-Tuning PID Controller Block (PID-STC) Page 1 of 1
1.13.1 Control Algorithm of Self-Tuning PID Controller

Block (PID-STC)
Self-Tuning PID Controller Block (PID-STC) obtains manipulated output value (MV) and manipulated
output change (ΔMV) based on PID algorithm.
PID Control Algorithm

The Self-Tuning PID Controller Block (PID-STC) uses the same PID control algorithm as the PID
controller block (PID).
SEE For more information about PID control algorithm, refer to:
ALSO " PID Control Computation" in 1.5, "PID Controller Block (PID)"
Control Action Bypass

When 0 is set for the PID parameter (P) or (D) of the Self-Tuning PID Controller Block (PID-STC),
parts of the control action can be bypassed.
The figure below shows the partially bypassed control action and setpoint values of PID parameters
(P, I, D):
Table 1.13.1-1 Partially Bypassed Control Action and Setpoint Values of PID Parameters (P, I, D)
Control action PID parameter setpoint value

Proportional (P) +integral (I) P≠0, D=0
Integral (I) P=0
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.
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.
1.13.2 Self-Tuning Function (STC Function) Page 1 of 2
1.13.2 Self-Tuning Function (STC Function)

The self-tuning function (STC function) determines a tuning index based on the estimated process
model, PID control algorithm, process type and control target type, to calculate optimum PID
parameters (P, I, D) in accordance with the obtained tuning index.
Self-Tuning Function (STC Function)

The self-tuning function (STC function) estimates process characteristics while monitoring process
variables (PV) and manipulated output values (MV) to create an estimated process model. It then
determines a tuning index based on the estimated process model, PID control algorithm, process
type and control target type, and calculates optimum PID parameters (P, I, D) in accordance with
the obtained tuning index.
The STC function can be started by the following three methods:
• Initialize start
• Auto-startup
• On-demand tuning
SEE For more information about initialize start, refer to:

ALSO 1.13.4, "Initializer Start"
For more information about auto-startup, refer to:
For more information about on-demand tuning, refer to:
Tuning Index
Generally, in a normal PID controller block (PID), optimum PID parameters (P, I, D) vary with the
purpose of control: to follow up the setpoint value or to prevent from disturbances. Therefore, it is
difficult to tune parameters in a single set of PID parameters (P, I, D) to obtain the optimum
responses for the prompt follow-up of set point value change as well as to restrain from external
disturbances. The Self-Tuning PID Controller Block (PID-STC) changes the index (tuning index)
according to the control target and the PID control function algorithm and block mode, so that
optimum responses can be obtained based on each tuning index.
The table below shows the tuning indexes of the Self-tuning function (STC function):
Table 1.13.2-1 Tuning Indexes
Tuning index
Control algorithm
Block mode AUT Block mode CAS Block mode RCAS
Setpoint value follow- Setpoint value follow- Setpoint value follow-
PID
up response up response up response
Disturbance Disturbance Disturbance
I-PD
suppression response suppression response suppression response
Setpoint value follow- Setpoint value follow- Setpoint value follow-
PI-D
up response up response up response
Automatic determination / Disturbance Setpoint value follow- Setpoint value follow-
Automatic determination 2 suppression response up response up response
The Self-Tuning PID Controller Block (PID-STC) calculates PID parameters (P, I, D) of the setpoint
1.13.2 Self-Tuning Function (STC Function) Page 2 of 2
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 estimation, the
following processing are performed:
• When the block detects that response is tending to hunt, the tuning stops when such hunting
occurs only for one cycle to ensure safety.
• When the gain of the controller block is increased, the change is limited to ensure safety.
• When the deviation remains large for a prolonged period of time, the gain of the controller block
increases.
Number of Simultaneously Executable Blocks

There is no limit to the number of Self-tuning PID controller blocks (PID-STC) that can be used in
one FCS. However, the number of Self-tuning PID controller blocks (PID-STC) executing self-tuning
function (STC function) at the same time is limited to 5 (*1) or 10 (*2) blocks per FCS.
If more than 5(*1) or 10 (*2) Self-tuning PID controller blocks (PID-STC) are defined by the
Function Block Detail Builder, the first 5 blocks (*1) or 10 blocks (*2) with the smaller block
numbers are set in the PID parameter display mode (STC=0), while the remaining Self-tuning PID
controller blocks (PID-STC) are set in the STC operation stop mode (STC=-1).
If 5 (*1) or 10 (*2) Self-tuning PID controller blocks (PID-STC) are currently executing the STC
function, the STC function of a new Self-Tuning PID Controller Block cannot be started. Only after
one of the currently executing Self-Tuning PID Controller Blocks (PID-STC) stops the STC function
i.e., changes its STC operation mode (STC=-1), the new Self-Tuning PID Controller Block can start
the STC function.
*1: For PFCS.
*2: For FCSs except PFCS.
1.13.3 Self-Tuning Operating Modes and Block Status Page 1 of 5
1.13.3 Self-Tuning Operating Modes and Block Status

The self-tuning operating mode (STC operating mode) determines the action of the Self-tuning
function (STC function). The Self-Tuning PID Controller Block (PID-STC) uses five types of STC
operating modes.
The block status of PID-STC indicates the running function of the STC block.
Self-Tuning Operating Mode (STC Operating Mode)

Switching between the STC operating modes is done via an STC operating mode selection switch
(STC).
STC Stop Mode (STC=-1)

The STC function is not executed in this mode.
Neither process characteristic estimation nor PID parameter (P, I, D) calculation are performed.
The block acts in the same way as a PID Controller Block (PID).
PID Parameter Display Mode (STC=0)

In this mode, process characteristic estimation and PID parameter (P, I, D) calculation are
performed, but the calculated PID parameters (P, I, D) are only displayed and not used for control.
In the PID parameter display mode, process characteristic estimation is performed when the process
variable (PV) moves out of the noise band (NB), and PID parameter (P, I, D) calculation is
performed if the estimation accuracy is high. The calculated PID parameters (P, I, D) are only
displayed and not used for control.
PID Parameter Automatic Updating Mode (STC=1)

In this mode, process characteristic estimation and PID parameter (P, I, D) calculation are
performed, and the calculated PID parameters (P, I, D) are used for control. In the PID parameter
automatic updating mode, process characteristic estimation is performed when the process variable
(PV) moves out of the noise band (NB), and PID parameter (P, I, D) calculation is performed if the
estimation accuracy is high. The calculated PID parameters (P, I, D) are used for control.
Auto-Startup Mode (STC=2)

Auto-startup is executed in this mode.
The process 95 % response time, noise band and PID parameters (P, I, D) are calculated
automatically. This mode is used when initial setpoint values are not known, such as during plant
startup.
On-Demand Mode (STC=3)

On-demand tuning is executed in this mode.
Step test signals are added to the manipulated output value (MV), and PID parameters (P, I, D) are
calculated based on the response waveform of the corresponding process variable (PV).
SEE
ALSO For more information about auto-startup, refer to:

For more information about on-demand tuning, refer to:
Flow of Self-Tuning Actions

During each control period, the Self-Tuning PID Controller Block (PID-STC) performs actions in
accordance with the Self-tuning operating mode (STC operating mode).
Figure 1.13.3-1 Flow of Self-Tuning Actions
Actions in Self-Tuning Operating Modes (STC Operating

Modes)
Table 1.13.3-1 Table of Actions in Self-Tuning Operating Modes (STC Operating Modes)
STC operating mode Block

selection switch mode Action
Previous Current (*1)
MAN Remains in the initialization processing state (*2).

0
AUT Starts normal processing after initialization processing (*2).
MAN Remains in the initialization processing state (*2).
1
AUT Starts normal processing after initialization processing (*2).
-1
Remains in the initialization processing state.
MAN
2 Startup mode waiting state (*2).
AUT Operation disabled. Returns to STC=-1.
3 All Operation disabled. Returns to STC=-1.
-1 All Stops STC actions. The block mode remains the same.
1 All No special processing. The block mode remains the same.
MAN Remains in the startup mode waiting state.
0 2
AUT Operation disabled. Returns to STC=0.
MAN Operation disabled. Returns to STC=0.
3
AUT On-demand mode. Returns to STC=0 after applying signals to MV.
-1 All Stops STC actions. The block mode remains the same.
0 All No special processing. The block mode remains the same.
MAN Remains in the startup mode waiting state.
1 2
AUT Operation disabled. Returns to STC=1.
MAN Operation disabled. Returns to STC=1.
3
AUT On-demand mode. Returns to STC=1 after applying signals to MV.
MAN Stops STC actions. The block mode remains the same.
-1 Suspends the startup action. Stops STC actions. The block mode
AUT
changes to MAN.
Stops the startup action. The block mode and block status change to
2 0 All
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.
*1: 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 “No” is selected for the STC bypass specification during the MAN mode.
*2: For PFCS, 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 FCSs except PFCS, 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.
SEE For more information about self-tuning operating mode selection switch (STC), refer to:
ALSO " STC Operating Mode Selection Switch (STC)" in 1.13.7, "Tuning Parameters of Self-Tuning
PID Controller Block (PID-STC)"
Block Statuses
The block status of the PID-STC block shows the current operating status of the STC functions. PID-
STC has 7 block statuses, the basic statuses and the combined statuses (combination of multiple
statuses) are all indicating the STC running functions.
Basic Block Status

The following shows basic STC Block Status.
Table 1.13.3-2 Basic STC Block Status
Symbol Name Explanation

Indicates that input and output signals are acquired periodically.
RUN RUN This block status is indicated when STC operation mode is set to zero or
over.
Indicates that the STC functions are stopped.(*1)
OFF OFF This block status is indicated for example when STC operation mode is
set to -1.
Initialization (WarM Indicates that the I/O data required to run the STC functions is being
WMUP
UP) acquired. The STC functions are disabled during the acquisition.(*1)
PID parameter
Indicates that optimum PID parameters that are calculated by STC
PLMT limitation (PID
functions are out of builder-set limits.
Parameters LiMiTed)
Auto-startup (Auto
STUP Indicates that auto startup is in process.
STart UP)
Abnormal termination
Indicates that auto startup is aborted because new PID parameters
PVER of auto-startup (PV
cannot be calculated from abnormal PV.
ERror)
Shows that because some setting is invalid, STC functions cannot be
Invalid STC function executed. Either some tuning parameter is invalid, or an attempt was
INVL
(INVaLid condition) made to simultaneously execute a larger number of STC control blocks
than the limit.
*1: Self tuning functions are stopped, but the equivalent PID block functions are operating normally.
SEE For more information about WMUP (Warm up), refer to:
ALSO " STC Warmup (Initialization)" in " Block Statuses" in 1.13.3, "Self-Tuning Operating
Modes and Block Status"
Composite Block Status

The following describes valid STC block status combinations, and shows the corresponding status
codes displayed on the HIS.
Table 1.13.3-3 Composite Block Statuses
Code
Status shown on Explanation
HIS
Shows that STC functions are stopped. This means that STC operation mode is
OFF OFF
set to –1. However the PID block functions are operating normally.
STC operation mode was set to STC execution status (STC≥0), but the maximum
INVL(OFF) INVL permitted number of PID-STC blocks that can operate simultaneously are already
operating, so shows that no more STC functions can be operated.
RUN RUN STC functions are running.
Performing initialization - gathering necessary I/O data to start STC functions.
WMUP
WMUP While this is occurring, the STC functions are disabled, However the PID block
(RUN)
functions are operating normally.
PLMT Optimum PID parameters calculated by the STC functions can’t be set because
PLMT
(RUN) they are outside builder-set limits.
STUP
STUP Shows that auto startup processing is being performed.
(RUN)
PVER Shows that because PV is abnormal, new PID constants couldn’t be computed,
PVER
(RUN) and auto startup processing was aborted.
Shows that STC operation mode is set to STC function execution status (STC≥0),
but because some parameter is invalid, STC functions cannot be executed.
INVL(RUN) INVL
However, the PID block functions are operating normally.
If you correct the problem, STC functions will operate again.
INVL
Shows that although an attempt was made to acquire I/O data, some data is
(WMUP INVL
missing.
(RUN))
Shows that because some parameter is invalid, STC auto startup functions can’t
INVL(STUP
INVL be run. However, the PID block functions are operating normally.
(RUN))
If you correct the problem, STC functions will start to operate.
STC Warmup (Initialization)

Except when block status of the STC functions is OFF, I/O data is continuously sampled. The process
model depends not only on current data but also on data over a preset period into the past.
While the STC functions are acquiring necessary data for estimating the process model, the STC
functions operate in standby - in WMUP status. STC initialization is performed in the following cases:
• When STC mode is switched from STC= –1 to STC=0 or from STC= –1 to STC=1.
• When the 95 % process response time value TR changes.
• When the scan period is changed.
• When the block mode recovers from O/S or IMAN.
• When on-line maintenance is performed on the current block.
• When an alarm such as IOP, which indicates that I/O data is affected, occurs.
• When the corresponding control area is started up.
The length of the initialization period is related to the PID-STC controller block mode at the time that
initialization is started, as follows:
For auto mode (AUT, CAS, RCAS) : 4 TR
Otherwise: 2 TR
1.13.4 Initializer Start Page 1 of 1
1.13.4 Initializer Start

Initializer start can be executed in the situation that allows to use the estimated initial values of PID
parameters (P, I, D).
The initializer start function uses estimated PID parameters (P, I, D) to start control.
Execution of Initializer Start

The methods used to start initialization are shown below. To execute initializer start, the following
conditions must be satisfied:
• The self-tuning operating mode (STC operating mode) is STC stop.
• The block mode is manual (MAN).
• The following parameters are set:
• PID parameters (P, I, D)
• Process 95 % response time (TR)
• Noise band (NB)
• Control target type (OS)
• PID data set high/low limits (PMAX, PMIN, IMAX, IMIN, DMAX)
• PID update ratio coefficient (PIDC)
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.
1.13.5 Auto-Startup Page 1 of 4
1.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:
• MV Impulse amplitude (MI)
• PID parameter (P)
• PID parameter (D)
When the following operations are performed after the above conditions established, auto-startup
can be executed.
1. Change the STC operating mode to auto-startup.
2. Change the block mode to any of the automatic modes (AUT/CAS/RCAS).
Upon auto-startup, the following actions take place:
1. The block status changes to STUP (during auto-startup), and the current manipulated output
value (MV) is held for 30 seconds.
2. Step signal set as the MV Impulse amplitude (MI) is added to the manipulated output value (MV)
in the direction of increasing deviation.
3. Observation of the response waveform of measured signals relative to the step change is started.
If, during the observation, the measured signal change (ΔPV) becomes equivalent to or larger
than 1.5 times of the MV Impulse amplitude (MI), the manipulated output value (MV) returns to
the original value to ensure safety.
4. If the target process is a static system (IP=0), the manipulated output value (MV) returns to the
original value after the response waveform is observed for a specified period of time. If the
process is an astatic system (IP=1), the step changes equivalent to the MV Impulse amplitude
(MI) is added to the manipulated variable in the reverse direction, then the manipulated output
(MV) returns to the original value.
5. Process characteristics is estimated based on the data obtained by the step response
observation.
6. The process 95 % response time (TR) and PID parameters (P, I, D) are calculated based on the
estimated model.
7. The following computations on the PID parameters (P, I, D) of the estimated model are
performed, and the computed results are set as PID parameters’ high/low limits (PMAX, PMIN,
IMAX, IMIN, DMAX).
Figure 1.13.5-1 Computational expressions
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 (2xTR; minimum 2 minutes, maximum
5 minutes), and the noise band (NB) is calculated based on the peak value.
9. The STC operating mode automatically changes to the PID parameter automatic updating mode
(STC=1), then PID control and self-tuning start to run.
Example of the Auto-Startup Action in Static Process
Figure 1.13.5-2 Example of the Auto-Startup Action in Static (Non-Integral) System
Example of the Auto-Startup Action in Astatic Process
Figure 1.13.5-3 Example of the Auto-Startup Action in Astatic (Integral) System
Abnormal Termination of Auto-Startup

The following section explains the abnormal termination of auto-startup.
Causes of the Abnormal Termination of Auto-Startup

The auto-startup action is terminated abnormally if the following events occur:
• Power failure
• Change in the self-tuning operating mode (STC operating mode)
• Change to a block mode other than automatic modes (AUT, CAS, RCAS).
• Failure to create an estimated process model
• The measured signal change (ΔPV) remains under 0.5 % of the MV Impulse amplitude (MI) after
the maximum observation time (90 minutes) elapsed.
• Insufficient information from step response.
• The data status of the manipulated output value (MV) changes to CLP or CND.
• The alarm status changes to IOP+, IOP-, OOP or CNF.
Self-Tuning PID Controller Block (PID-STC) upon Abnormal

Termination of Auto-Startup
When the auto-startup action is stopped, the following changes take place inside the Self-tuning PID
controller block (PID-STC):
• The block changes to automatic (AUT) mode.
• The STC operating mode changes to PID parameter display (STC=0).
• The block status changes to auto-startup abnormal termination (PVER).
The block status changes or set the STC operating mode operation stop (STC=-1) cancels the auto-
startup abnormal termination status.
Do not use auto-startup for systems whose process dead-time is short. This is
because an abnormal termination processing of the auto-startup may not be
carried out if the process dead-time is 4 seconds or less. If an abnormal

termination processing could not be carried out, the block status remains as
STUP.
If an auto-startup has been used by mistake, change the block mode to MAN
mode and interrupt the auto-startup.
Setup Items for Auto-Startup

The following items must be set in the auto-startup mode:
Specify the type of response waveform to be targeted by the self-tuning function (STC function)
Select a target suitable for the controlled plant
• MV Impulse amplitude (MI)
Set a value that may trigger the process variable (PV)’s impulse response around 5 %.
• Control method (P, I, D)
Specify a desired control method
Specify one of the following three types of control methods:
I control : P=0
PI control : P≠0, D=0
PID control : P≠0, D≠0
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.
1.13.6 On-Demand Tuning Page 1 of 1
1.13.6 On-Demand Tuning

On-demand tuning is applied to tune PID parameters (P, I, D) when tuning request is given from the
operator. On-demand tuning may be applied to the loops where the change of setpoint values need to be
avoided.
Execution of On-Demand Tuning

For on-demand tuning, when a tuning demand is given from the operator, a step test signal is added to the
manipulated output value (MV) in a closed loop. Then the self-tuning is performed based on the response
waveform of the corresponding process variable (PV).
The method of on-demand tuning is shown below. To execute on-demand tuning, the following conditions
must be satisfied:
• The self-tuning operating mode (STC operating mode) is the PID parameter display or PID automatic
updating mode
• The block mode is one of the automatic modes
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.
Figure 1.13.6-1 Responses in the On-Demand Mode
If responses from the process are extremely monotonous, an estimated model may not be created. In this
case, increase the MV Impulse amplitude (MI) and retry the self-tuning.
Setup Item for On-Demand Tuning

The following item must be set in order to execute on-demand tuning:
MV Impulse amplitude Set a value that may trigger the process variable (PV)’s impulse response
(MI): around 5 %.
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.
1.13.7 Tuning Parameters of Self-Tuning PID Controller Block (PID-STC) Page 1 of 9
1.13.7 Tuning Parameters of Self-Tuning PID Controller

Block (PID-STC)
This tuning parameters of PID-STC block consist of three types; Setting parameters that may be set
on the tuning view; Parameters for indication and the parameters defined on the Function Block
Detail Builder.
Tuning Parameters
The tuning parameters of the Self-Tuning PID Controller Block (PID-STC) include the following types:
• Parameters may be set on tuning view
These tuning parameters can be set on the tuning view during operation.
• Parameters for indication
These parameters are displayed in the tuning view to indicate the operating status of the STC
function. The values of the parameters are calculated automatically by the Self-tuning PID
Controller Block (PID-STC).
• Parameters defined on the Function Block Detail Builder
These parameters are defined on the Function Block Detail Builder.
Parameters Set from the Tuning View

The table below shows the parameters that are set from the tuning view:
Table 1.13.7-1 Parameters Set from the Tuning View
Entry Setup items in each

Symbol Name enable/disable Range Default operating mode(*2)
(*1) -1 0 1 2 3
STC operating
STC mode selection x -1, 0, 1, 2, 3 0 (*3) (*4)
switch
Process 95 % 1 to 10000 40
TR x - xx
response time seconds seconds
1.0 to 20.0 %
NB Noise band x of the PV value 1.0 % (*5) - xx
(*5)
Control target
OS x 0, 1, 2, 3 2 -
type
0.0 to 20.0 %
MV Impulse
MI x of the MV 5.0 % (*6) - - -
amplitude
value (*6)
0.0 to 1000.0
P Proportional band x 100.0 % xx xx xx
%
0.1 to 10000.0 20.0
I Integral time x xx xx xx
seconds seconds
0.0 to 10000.0 0.0
D Derivative time x xx xx xx
seconds second
Proportional band 0.0 to 1000.0
PMAX x 1000.0 % - xx
high limit %
PMIN x 0.1 % - xx
low limit %
Integral time high 0.1 to 10000.0 10000.0

IMAX x - xx
limit seconds seconds
Integral time low 0.1 to 10000.0 0.1
IMIN x - xx
limit seconds seconds
Derivative time 0.0 to 10000.0 2000.0
DMAX x - xx
high limit seconds seconds
PID update ratio
PIDC x 0.00 to 1.00 1.00 - - - -
coefficient
*1: x: Can be entered from the tuning view at any time.
*2: : Setting required.
-: Setting not required.
xx: Setting is done automatically, but can be entered from the tuning view, as well.
*3: The default values of the 11th and subsequent PID-STC controller blocks within the same control
station will be -1.
*4: A determining factor of the operating mode.
*5: A percentage value converted from the PV engineering unit data.
*6: A percentage value converted from the MV engineering unit data.
Display Parameters
The table below shows display parameters. These parameters are displayed in the tuning view to
indicate the operating status of the STC function.
Table 1.13.7-2 Display Parameters
Setup items in each

Entry operating mode (*1)
Symbol Name Range
enable/disable (*1)
-1 0 1 2 3
0.000 to
CR Estimation accuracy error x x □ □ □ □
100.000
0.0 to
Estimated equivalent
LM x 10000.00 x □ □ □ □
dead time
seconds
Estimated equivalent first- 0.1 to 10000.0
TM x x □ □ □ □
order lag constant seconds
Estimated equivalent 0.000 to
GM x x □ □ □ □
process gain 100.000
PA x x □ □ □ □
calculation value %
Integral time calculation 1.0 to 10000.0
IA x x □ □ □ □
value seconds
Derivative time 0.0 to 10000.0
DA x x □ □ □ □
calculation value seconds
*1: x: Cannot be entered from the tuning view.
□: Items for automatic calculation and display only.
Items Defined in the Function Block Detail Builder

The table below shows the tuning parameters of the Self-Tuning PID Controller Block (PID-STC)
defined in the Function Block Detail Builder:
Table 1.13.7-3 Items defined in the Function Block Detail Builder
Entry Setup items in each
enable/disable(*1) operating mode(*1)

Symbol Name Range Default
-1 0 1 2 3
0 (non-
IP Process type Δ 0, 1 Δ Δ Δ Δ Δ
integral)
Manual mode STC ON,
- Δ ON Δ Δ Δ Δ Δ
function bypass OFF
*1: Δ: Item defined in the Function Block Detail Builder.
STC Operating Mode Selection Switch (STC)

Set the operating mode of the Self-Tuning PID Controller Block (PID-STC) to the STC operating
mode selection switch.
• STC: Specify the operating mode using a numeric value.
The following operating modes can be selected:
-1 : STC operation stop mode
0 : STC parameter display mode
1 : STC parameter automatic updating mode
2 : Auto-startup mode
3: : On-demand mode
Process 95 % Response Time (TR)

Set the rise time for 95 % of process step response in an open-loop.
Process 95 % Response Time Setting Methods

The Self-Tuning PID Controller Block (PID-STC) calculates the time for measured signal waveform
observation as well as sampling time for process characteristic estimation, based on the process 95
% response time (TR). To operate the STC function in a good condition, an optimum value for the
process 95 % response time (TR) is required.
• Process 95 % response time
Set the rising time for 95 % of process step response in an open-loop.
The procedure to set an optimum TR value is shown below:
• When step responses from the process are known
Set the time required for the process variable change (ΔPV) to reach 95 % of the settling value.
• When the process can be approximated based on the first-order lag system
Obtain TR that satisfied TR=L+3T, from the dead time (L) and first-order lag constant (T) of the
process, and set the obtained value as the process 95 % response time (TR).
• When the process is an astatic system (integral system)
The time required for the process variable change (ΔPV) reach 95 % peak can be set as the
response rising time (TR) after an impulse is applied to the process.
• When the past operating process behavior is known
Obtain the specific oscillation cycle (Tp) of the process from the past operation data, and set this
value as the process 95 % response time.
• When the response time is expected to change
Set a value in accordance with the particular response waveform to be controlled. As in the case
of furnace temperature, if the response rising time of the process variable (PV) is different from
the falling time, use the longer response time. In this way, estimated process characteristic
values will have less error than that the shorter response time is used.
Examples of Process 95 % Response Time (TR) Estimation

The figures below are examples of process response estimation when step responses from the
process are known (estimated from the step response waveform) and when the past operation
conditions are known (estimated from damped oscillatory waveform):
Figure 1.13.7-1 TR Estimation Methods
Noise Band (NB)

Set the noise band (NB) to prevent process characteristic estimation from being disturbed by noise.
For the noise band, set a value that is twice of the peak value of random noise being superimposed
over measured signals (maximum width of noise).
When a noise band (NB) is set, process characteristic estimation will be started when the process
variable (PV) changes beyond the limits of noise band (NB) during a single sampling period.
Figure 1.13.7-2 Noise Band
Noise Band Set a value that is twice of the peak value of random noise being superimposed over
(NB): measured signals (maximum width of noise).
Control Target Type (OS)

The desirable control target response waveform varies depending upon the process type and
operating method. Set a control target type (OS) from the tuning view according to the controlled
system.
Control target type Select a control target type and specify a numeric value indicating the
(OS): type.
The table below shows the control target types (OS) that can be set for the Self-Tuning PID
Controller Block (PID-STC):
Figure 1.13.7-3 Control Target Types
• 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.
Figure 1.13.7-4 Control Areas and PV Responses
MV Impulse Amplitude (MI)

The MV Impulse amplitude (MI) is the size of the test signal that is applied to the manipulated
output value (MV) during the auto-startup or on-demand mode. The value is set from the tuning
view.
MV Impulse amplitude Set a value that may trigger the process variable (PV)’s impulse response
(MI): around 5 %.
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 1.13.7-4 Directions of MV Step Changes
Action mode
Operating mode Deviation
Direct action Reverse action
SV≥PV +MI % -MI %
Auto-startup
SV<PV -MI % +MI %
SV≥PV -MI % +MI %
On-demand
SV<PV +MI % -MI %
PID Parameters (P, I, D)

The PID parameters (P, I, D) are used in control computation.
The values of respective parameters are shown below:
• P: Proportional band
• I: Integral time
• D: Derivative time
During operation in the PID parameter automatic updating mode, the values set for PID parameters
(P, I, D) are used as initial values and updated automatically when the self-tuning function (STC
function) is activated.
Set initial values for PID parameters (P, I, D) using the following methods:
New Process
• When estimation or calculation is possible based on the statistical data of other processes
Use values estimated or calculated based on the statistical data of other processes.
• When using estimated or calculated values is difficult
Use auto-startup. If auto-startup cannot be used, perform self-tuning in the PID parameter
display mode, and use the values displayed as new calculated values of PID parameter (PA, IA,
DA).
Existing Control System Replacement

Use the PID values before the replacement.
PID Data Set High/Low Limits (PMAX, PMIN, IMAX,

IMIN, DMAX)
If the process is likely to receive negative impacts when PID parameters (P, I, D) exceed their
specified limit, set PID data set high/low limits in advance.
The PID data set high/low limits indicate control ranges that are used to limit PID parameters (P, I,
D) when they are changed by the STC function.
• PMAX: Proportional band high limit
• PMIN: Proportional band low limit
• IMAX: Integral time high limit
• IMIN: Integral time low limit
• DMAX: Derivative time high limit
The PID parameters (P, I, D) are limited within the range of the corresponding high/low limits:
PMIN ≤ P ≤ PMAX (Same for PA when the STC value is “1”)
IMIN ≤ I ≤ IMAX (Same for IA when the STC value is “1”)
0 ≤ D ≤ PMAX (Same for DA when the STC value is “1”)
If the set high limit is smaller than low limit, the corresponding PID parameter (P, I or D) will be
fixed to the high limit value. If the DMAX value is 0, the value of the PID parameter (D) becomes 0.
If the PMAX value is 0, the value of the PID parameter (P or D) becomes 0.
If, due to the STC function any PID parameter (P, I, or D) exceeds the control range during
operation in the PID parameter automatic updating mode, the block status changes to PID
parameter limiting (PLMT) and the PID parameter (P, I or D) obtained by the STC function will be
limited within the range of the corresponding PID data set high/low limits (PMAX, PMIN, IMAX, IMIN
or DMAX).
The PID parameter limiting (PLMT) status is canceled when the applicable PID parameter (P, I or D)
has changed to a value inside the control range or when the STC actions have stopped (STC=-1).
PID Update Ratio Coefficient (PIDC)

The PID update ratio coefficient (PIDC) represents a ratio at which the current PID parameters (P, I,
D) are updated by the corresponding PID parameter values calculated by the STC function (PA, IA,
DA).
PID update ratio coefficient (PIDC): A value between 0.00 and 1.00.
The parameters are not updated if PIDC is 0.00. If PIDC is 1.00, the PID parameter values
calculated by the STC function (PA, IA, DA) will be set directly as PID parameters (P, I, D).
If the estimated model remains unstable due to disturbances and the PID parameters (P, I, D) tend
to change although slightly with every tuning, set a smaller PIDC value to stabilize the PID
parameters (P, I, D).
This coefficient is effective only in the PID parameter automatic updating mode.
PBnew = (1.0-PIDC) • PB +PIDC • PA
TInew = (1.0-PIDC) • TI +PIDC • IA
TDnew = (1.0-PIDC) • TD +PIDC • DA
PBnew : New effective proportional band value
PB : Current effective proportional band value
PA : PB calculated value
TInew : New effective integral time value
TI : Current effective integral time value
IA : TI calculated value
TDnew : New effective derivative time value
TD : Current effective derivative time value
DA : TD calculated value
PIDC : Update ratio coefficient (0.00 to 1.00)
When exceptional tuning is performed at slow response or hunting response

processing, the PID update ratio coefficient (PIDC) is ignored and the PID
parameter values (PA, IA, DA) calculated by the STC function will be set
directly as PID parameters (P, I, D).
Estimation Error (CR)
Whenever an estimated process model is created, the STC function simulates the output of the
model and calculates a squared error based on the actual process response. The estimation error is
a value obtained from the best parameter set which has the smallest estimation error.
If the estimated model matches perfectly with the actual process, the estimation error (CR) becomes
0.000. However, as the actual process is affected by measurement noise and various disturbances,
deviations exist between the estimated model and actual process and the value of the estimation
error (CR) varies accordingly.
When the value of the estimation error (CR) exceeds 5.000, the Self-Tuning PID Controller Block
(PID-STC) assumes that the current estimated model is not effective and starts creating a new
estimated model using new data without updating the PID parameters (P, I, D).
Estimated Models (LM, TM, GM)

The Self-Tuning PID Controller Block (PID-STC) creates estimated models by approximating the
target process based on the dead time and first-order lag system. The estimated models, LM, TM
and GM, represent the equivalent dead time, equivalent first-order lag constant and equivalent
process gain, respectively.
The estimated models (LM, TM, GM) hold the latest values as long as the estimation error (CR) is
under 5.000.
The estimation error (CR) is updated every time a process characteristic estimation is performed, but
the estimated models (LM, TM, GM) are updated if the estimation error (CR) is 5.000 or greater.
New Calculated Values of PID Parameters (PA, IA, DA)

The new calculated values of PID parameters obtained by the self-tuning function (STC function). If
the value of the Self-tuning operating mode (STC) is “1,” the new calculated values of PID
parameters (PA, IA, DA) are set as the corresponding PID parameters (P, I, D) after receiving
computation processing based on the PID update ratio coefficient (PIDC).
Process Type (IP)

▼ Process Type
The process type indicates whether the target process is a static system (non-integral system) or
astatic system (integral system). The process type is specified in the Function Block Detail Builder.
Process Type: Select “Static system” or “Astatic.”
The default is “Static system.”
The static system is a process whose process variable (PV) changes gradually toward a settling value
when step change is added to the manipulated output value (MV), until an equilibrium state is finally
reached. The astatic system is a process whose process variable (PV) rises or falls infinitely with
time when step change is added to the manipulated output value (MV). An example of astatic
system is a constant-flow pump whose flowrate is maintained at constant levels via level control.
The figures below show examples of step responses from static system and astatic system
processes:
Figure 1.13.7-5 Examples of Step Responses from Static System and Astatic System Processes
MAN Mode STC Function Bypass

▼ STC Function Bypass Designation for MAN Mode
Specify whether to use or bypass the self-tuning function (STC function) when the block is in a
manual operating mode (MAN, PRD or ROUT).
Use the Function Block Detail Builder to set the MAN mode STC function bypass specification.
STC function bypass designation for MAN mode: Select “Yes” or “No.”
The default is “Yes.”
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 constantly
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.
1.13.8 Points of Using Self-Tuning PID Controller Block (PID-STC) Page 1 of 8
1.13.8 Points of Using Self-Tuning PID Controller Block

(PID-STC)
This section explains the points to be noted when using the self-tuning function (STC function) in
various controlled systems and loops as well as applicability of the function.
Applicable Conditions of Self-Tuning PID Controller

Block (PID-STC)
The self-tuning function can be used only when the process satisfies the following conditions:
• PID control is allowed.
• The cycle of factors that can cause changes in the control deviation (changes in process
characteristics and setpoint values, etc.) is longer than the specific oscillation cycle of the control
loop.
• Responses between the manipulated variable (MV) and process variable (PV) can be
approximated by the dead time and first-order lag system or integral system.
In general, many processes can be approximated with a combination of higher-order lag element,
dead time, and process gain, by the following expression:
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 manipulated variable. Appropriate
control is ensured if the ratio of dead time to lag time (L/T) is 3 or smaller.
Stable Control Loops (Regulatory Control)

When using a Self-Tuning PID Controller Block (PID-STC) in a stable control loop in which the
setpoint value does not change frequently and process characteristics undergo little fluctuation, it is
recommended that the control be performed with the self-tuning function (STC function) turned OFF
once optimum PID parameters (P, I, D) are calculated. The procedure is shown below:
1. First, obtain optimum PID parameters (P, I, D) using the STC function.
2. Change the PID data set high/low limits to reduce the range of PID parameters (P, I, D) or turn
the STC function OFF (STC=-1).
Controlling a Process with a Longer Dead Time

The following section shows the points to be noted when using a Self-Tuning PID Controller Block
(PID-STC) in a process with a longer dead time:
When a Self-Tuning PID Controller Block (PID-STC) is used to control a process in which the dead
time element is dominant, determine whether or not appropriate control is feasible using the Self-
Tuning PID Controller Block (PID-STC), based on the value of the dead time/lag time ratio (L/T).
• When the dead time/lag time ratio (L/T) of the process is smaller than 3
Appropriate actions can be obtained by combining basic PID functions and the STC function.
• When the dead time/lag time ratio (L/T) of the process is larger than 3
It is difficult to perform control by combining basic PID functions and the STC function. In this
case, consider using the Smith’s Dead Time Compensation Control or sampled value PI control.
Note that the STC function cannot be used with either of these control methods.
Cascade Control with Quicker Downstream Responses

The following section shows the points to be noted when using Self-Tuning PID Controller Blocks
(PID-STC) in a process with quick responses coming from downstream, by using an example of a
cascade loop consisting of temperature control and flowrate control as the upstream and
downstream processes, respectively.
Figure 1.13.8-1 Cascade Control loop with Quicker Downstream Responses
Unless frequent changes occur in the process of the downstream Self-Tuning PID Controller Block
(PID-STC), it is recommended to use the Self-tuning function (STC function) of the upstream Self-
Tuning PID Controller Block (PID-STC) only. The procedure is shown below:
1. Change the downstream block to AUT mode to open the cascade connection.
2. Set an optimal PID value using the STC function of the downstream Self-Tuning PID Controller
Block (PID-STC).
3. Turn off the STC function of the downstream Self-Tuning PID Controller Block (PID-STC).
4. Establish the cascade connection.
5. Turn on the STC function of the upstream Self-Tuning PID Controller Block (PID-STC).
Cascade Control with Slower Downstream Responses

The following section shows the points to be noted when using Self-Tuning PID Controller Block
(PID-STC) in a process with slower responses coming from downstream, by using an example of a
cascade loop consisting of two temperature control processes in upstream and downstream.
Figure 1.13.8-2 Cascade Control with Slower Downstream Responses
The procedure to control this cascade loop is shown below:

1. Change the downstream block to AUT mode to open the cascade connection.
2. Set an optimal PID value using the STC function of the downstream Self-Tuning PID Controller
Block (PID-STC).
3. Turn off the STC function of the downstream Self-Tuning PID Controller Block (PID-STC).
4. Establish the cascade connection.
5. Turn on the STC function of the upstream Self-Tuning PID Controller Block (PID-STC).
In this type of cascade loop, it is generally recommended that the Self-tuning function (STC
function) be executed only in the upstream controller, which is the main target of control, in order to
avoid interaction between the two STC functions in upstream and downstream.
Controlling a Process with Changing Target Control

Characteristics
(PID-STC) in a process where target control characteristics, such as gain, lag time and dead time,
fluctuate.
Figure 1.13.8-3 Process with Changing Gain
The above example shows a process where the flowrate F is control target. Since the flowrate F1,
inflow of the tank, fluctuate periodically, the level control is activated to change the intermediate
outflow volume F0. The changes in F0 correspond to those in gain that occur in the target control
process of FIC.
If the change cycle of the target control characteristic is longer than the specific oscillation cycle of
the control loop, the self-tuning function (STC function) is activated to follow up the change. If
changes in the process variable response are detected as a result of the changes in the target
control characteristic, the STC function will be activated.
Neutralization Control
(PID-STC) for neutralization control.
Figure 1.13.8-4 Neutralization Control
In the neutralization control shown above, the pH process shows non-linear characteristics; i.e., the
gain increases significantly near the neutralizing point (pH=7) and becomes small on both sides.
The pH controller is controlled by calculating optimum PID parameter values (P, I, D) near the
neutralizing point. Therefore, the proportional band converges by several hundred percent, making it
impossible to obtain appropriate control away from the neutralizing point. In this case, specify non-
linear gain processing for the controller and use the STC function after obtaining linear
characteristics.
Tank Level Control with Integral Characteristics

(PID-STC) in a process with integral characteristics, by using a level control process as an example:
Figure 1.13.8-5 Control with Integral Characteristics
The level control shown above is a process that maintains a constant outflow volume via a constant-
flow pump, regardless of the fluid level. In this process, the fluid level (H) continues 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 process becomes unstable if the integral time is
short.
In this type of integral process, use the self-tuning function (STC function) by setting “1” for the
process type (IP). When the process type (IP) is “1,” proportional and derivative (PD) control is
executed by setting a longer integral time.
Controlling a Process with Phases of Varying Response

Speeds
(PID-STC) in a process where the response speed varies depending on the phase, by using an
example of temperature control.
Figure 1.13.8-6 Example of Step Responses in a Process with Phases of Varying Response Speeds
In a heating furnace or heat exchanger process that requires temperature control, the process
response time may vary with the heating phase and cooling phase. When using a Self-Tuning PID
Controller Block (PID-STC) to control these processes, set the process 95 % response time (TR)
based on the phase with a longer response time.
PID parameters changes between the optimum PID parameters (P, I, D) of the two phases in
accordance with the direction of process variable response actions.
Controlling a Process with Slower Actions at the Final

Control Element
(PID-STC) in a process whose final control element exhibits slower actions, by using an example of
flowrate control with a motor-operated valve.
Figure 1.13.8-7 Motor-Operated Valve Flowrate Control
Figure 1.13.8-8 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 control element.
If controllability needs to be further improved, consider using phase compensation by first-order lead
computation, in order to compensate for the derivative actions.
Program Pattern Control

The following shows points to be noted when applying a Self-Tuning PID Controller Block (PID-STC)
to program control, by using an example of a program controlling process where the setpoint value
of the temperature controller is changed in accordance with a specific temperature rise and fall
pattern:
Figure 1.13.8-9 Program Control
When applying a Self-Tuning PID Controller Block (PID-STC) to a program controlling process where
the setpoint value of the temperature controller is changed in accordance with a specific
temperature rise and fall pattern, note the following points:
• Select the PI-D type (PV derivative type) control algorithm. The I-PD type (PV proportional and
derivative type) algorithm provides poor follow-up capability relative to changes in SV.
• If it requires that overshoot of the rising temperature must be minimized, set “0” for the control
target type (OS) of the Self-Tuning PID Controller Block (PID-STC).
In general, when the setpoint value changes along a ramp pattern, as in the case of rising or falling
temperature, the Self-Tuning PID Controller Block (PID-STC) generates an offset. If on-demand
tuning is executed at this time, the MV Impulse amplitude (MI) is applied to the manipulated output
value (MV) in the direction of decreasing control deviation, then PID parameters (P, I, D) are
calculated and set automatically based on the response obtained. As a result, the offset is reduced.
Batch Control Combining a Self-Tuning PID Controller

Block (PID-STC)
(PID-STC) for batch control:
Figure 1.13.8-10 Batch Control
During PID control, simple batch processes are subject to large disturbances beyond the correctable
range through feedback control, as a result of additional charging of raw materials 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 unnecessary
action of the self-tuning function (STC function).
Controlling Interacting Loops Whose Interaction cannot

be Eliminated
The following section shows the points to be noted when using Self-tuning PID controller blocks
(PID-STC) to control interacting loops whose interaction cannot be eliminated, by using an example
of pressure control and flowrate control interacting with each other:
Figure 1.13.8-11 Controlling Interacting Loops Whose Interaction cannot be Eliminated
If interaction exists between pressure control and flowrate control, as shown in the figure above,
using the self-tuning function (STC function) in both control loops causes interacting oscillation when
their PID parameters (P, I, D) approach optimum values. In this case, turn off the STC function of
one Self-Tuning PID Controller Block (PID-STC) whose process variable (PV) is allowed to change,
and set larger values for the current effective proportional band (PB) and current effective integral
time (TI). (e.g.: PB=100 to 200 %, TI=30 to 80 seconds) After this, use the STC function of the
other Self-Tuning PID Controller Block (PID-STC) only.
Controlling Interacting Loops whose Interaction can be

Eliminated
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:
Figure 1.13.8-12 Controlling Interacting Loops whose Interaction Can Be Eliminated
If interaction exists between the column top temperature and column bottom temperature control
segments of a distillation column process, first execute non-interacting control.
The method of non-interacting control is shown below:
In the figure, when the transmission function between the output mi and temperature Tj of the
controller TCi is gij. T1 and T2 will be represented as follows after non-interacting elements LL-1 and
LL-2 are applied:
T1 = (g11-g12 • g21/g22) m1
T2 = (g22-g12 • g21/g11) m2
As a result, the process is divided into two control loops that are regulated based on T1 and T2,
respectively.
Configure STC after confirming the result of this non-interacting control.
Controlling a Loop Subject to Impulse Noise

When a Self-Tuning PID Controller Block (PID-STC) is used to control a loop subject to impulse
noise, the Self-Tuning PID Controller Block (PID-STC) estimates process characteristics after
removing the impulse noise. When noise generates frequently, set a noise band (NB).
If impulse noise is generated frequently at intervals of TR/10 or shorter, consider using filters to
remove the noise.
1.14 PID Controller with Output Loss Compensation for Wireless Block (ZWOPID) Page 1 of 8
1.14 PID Controller with Output Loss

Compensation for Wireless Block
(ZWOPID)
The ZWOPID block is applied to run the PID control involving wireless field devices. When the
communications with wireless field devices recover from a communication error, the output loss
compensation computation runs to prevent a change on the process variable (PV) and to lead it to
the setpoint value (SV) quickly. Actions of this function block are the same as those of the PID
Controller block (PID) except for the output loss compensation computation.
If a communication error occurs in the output to the wireless field device, the following system
alarm messages are generated:
• No.0089 Subsystem communication error
• No.0039 Process I/O error
On recovery from the output communication error, recovery messages are generated.
When the above system alarm messages occur, check to find out what is preventing wireless
communication.
SEE For more information about the control computation processing of the ZWOPID block, refer to:
ALSO 1.5, "PID Controller Block (PID)"
PID Controller with Output Loss Compensation for

Wireless Block (ZWOPID)
▼ Connection
You can apply ZWOPID block to FFCS-C and FFCS-V.

The PID with Packet Loss Compensation Package (for Field Wireless) is required to apply.
You need to activate PID with Packet Loss Compensation Package (for Field Wireless) and
add "ZWPID" option on the "Constant" tab of the FCS properties sheet.
The following figure shows the function block diagram of the ZWOPID block.
Figure 1.14-1 Function block diagram of the ZWOPID block
The following table shows methods and destinations to connect I/O terminals of the ZWOPID block.
Table 1.14-1 Connection method and connected destination of I/O terminals of ZWOPID block
Connection method(*1) Connected destination(*1)

Measurement
IN x - Δ x - x
input
SET Setting input - - x - - x
Manipulated
OUT - x x x - x
output
SUB Auxiliary output - x Δ x - x
Reset signal 1
RL1 x - Δ x - x
input
Reset signal 2
RL2 x - Δ x - x
input
Compensation
BIN x - Δ x - x
input
Tracking signal
TIN x - Δ x - x
input
TSI Tracking SW input x - Δ x x x
INT Interlock SW input x - Δ x x x
Data status input
RBS x - - x - -
for readback
RBV Readback value x - - x - -
−: Connection not allowed
link block (ADL)
Functions of ZWOPID block
The ZWOPID block performs input processing, output loss compensation computation, control
computation, output processing, and alarm processing.
The ZWOPID block performs these processing and computation only by a periodic execution. The
basic scan period, the medium-speed scan period, and the high-speed scan period are provided as
scan period options to run a periodic startup.
ALSO processing of the ZWOPID block, refer to:
Output loss compensation computation

The output loss compensation computation is a computation processing to recalculate the SV. When
a communication error occurs between function blocks and wireless field devices, the wireless field
devices hold their previous values of the manipulated output. In that event, a change may occur in
the PV of the function block when the communications recover and the PV delays in reaching the SV.
To avoid such delay, the output loss compensation computation recalculates the SV and leads the PV
to the SV quickly when the communications recover. The values assigned to a recalculation are the
readback values from wireless field devices when the communications recover.
In the case of PV proportional and derivative type PID control (I-PD), however, the function block
uses the current SV in the output loss compensation computation, without recalculating SV.
Figure 1.14-2 Outlines of processing timing for ZWOPID block
The wait time for recovery from output loss can be specified for the ZWOPID block. You can specify
it in the Details Setting of the ZWOPID block. The default is 5 seconds.
If the communications recover before the "wait time for recovery from output loss" expires, the
output loss compensation computation runs. If the communication error remains unresolved after
the "wait time for recovery from output loss" expires, or if a communication error occurs while 0 is
specified for the wait time, the ZWOPID block turns to IMAN and the data status turns to OOP. The
output loss compensation computation does not run in those cases.
If AO mode of wireless field devices turns to a mode except for CAS, the ZWOPID block turns to
IMAN and the data status turns to OOP after the wait time for recovery from output loss expires.
If ALE111 fails or Ethernet communications fail, the ZWOPID block turns to IMAN and the data
status turns to OOP regardless of the expiration of the wait time for recovery from output loss.
If the following operations are performed while a communication error has occurred between the
ZWOPID block and wireless field devices, the ZWOPID block turns to IMAN and the data status turns
to OOP regardless of the expiration of the wait time for recovery from output loss.
• Change the ZWOPID block mode to AUT/CAS/RCAS.
• Restart FCS
• Online download to the ZWOPID block
• Load snapshots
The data item RBVL of the ZWOPID block maintains the value immediately before an error while a
communication error or OOP occurs. Data items RBST and MPST in the ZWOPID block turn to 0 if an
error except for a communication error occurs and the status turns to OOP.
If online downloading to the ALE111 is executed while the ZWOPID block is in AUT, CAS, or RCAS
mode, a MAN fallback occurs.
The ZWOPID block does not have the Fully-open/Tightly-shut function. You can implement the same
operation as the Fully-open/Tightly-shut function by configuring the wireless device.
Connection between the ZWOPID block and wireless

field devices
You must use wireless field devices that conform to the ISA100.11a wireless communication
standard for process control applications.
TIP You must contact the vendors of each device if they provide the AO that conforms to "ISA100
Wireless Compliance Institute ISA100.11a Device Profile for Process Control Analog Output Object
Extension".
You must connect %W or %X to the IN, OUT, and RBS terminals in the ZWOPID block. You must
specify a parameter of the wireless field device to %W or %X. Terminals of the ZWOPID block and
their corresponding parameters of wireless field devices are as follows:
- IN of the ZWOPID block Input data (PV) from the wireless field devices
- OUT of the ZWOPID block Output data (OP) to the wireless field devices
- RBS of the ZWOPID block Readback data (READBACK) from the wireless field devices
If those connections are not satisfied, the output loss compensation computation does not run.
The following figure shows an example of connection between ZWOPID block and wireless field
devices.
Figure 1.14-3 Example of connection between the ZWOPID block and wireless field devices
Engineering on wireless field devices

You must set the following items in wireless field devices. If those setup items are not satisfied, the
output loss compensation computation may not provide effective results.
• Apply a star topology to configure a wireless network of the field wireless system
• Set the duo cast for wireless field devices
• For AO of wireless field devices, set the communication period to 1 second and the Stale Limit
count to 4
• Set AO parameters to avoid a wireless field device failsafe
The communication period and Stale Limit count must be set on both the output data of AO (OP)
and the readback data of AO (READBACK) in wireless field devices.
Wireless field devices may take Failsafe actions. Parameters of wireless field devices must be set as
follows to avoid Failsafe actions. Parameters can be set on the Plant Resource Manager (PRM) or the
FieldMate.
Table 1.14-2 Parameters of wireless field devices and their setting values
Parameter Setting value Description

Set “Fault State supported” to 1 to enable Failsafe
AO_FEATURE_SEL Set Bit 0 to 1
actions.
Set “Target to Man if Fault State activated” to 0 to
AO_OPTS Set Bit 5 to 0 recover AO automatically to the original CAS mode
after the communications recover.
The wait time until Failsafe actions begin after a
Set FSTATE_TIME to a value
communication error is detected based on the Stale
no less than 10 seconds that
Limit count. Set this parameter when FSTATE_OPT is
satisfies the following
set to a value other than 0. The time is indicated in
FSTATE_TIME condition: Publish period •
seconds. When connecting wireless field devices to a
StaleLimit + FSTATE_TIME >
ZWOPID block, you must set the values that cause no
Wait Time for Recovery from
Failsafe actions before the expiration of wait time for
Output Loss
recovery from output loss.
0: Hold last value (recommended)
1: Fail Closed
Set one of the values shown in
FSTATE_OPT 2: Fail Open
the right cell.
3: FSTATE_VAL
4 to 7: Reserved
MV value during Failsafe

FSTATE_VAL This parameter is valid when FSATAE_OPT is set to 3.
actions
SEE For more information about changing setup items, refer to:
ALSO YFGW410 Field Wireless Management Station (IM 01W02D01-01EN)
Data Items - PID Controller with Output Loss

Compensation for Wireless Block (ZWOPID)
Table 1.14-3 Data items of ZWOPID block (1/2)

Data Name Range(*2)
Item Not(*1) (*2)
O/S
MODE Block mode x n/a
(MAN)
ALRM Alarm status - n/a NR
AFLS Alarm flashing status - n/a 0
Alarm detection
AF - n/a 0
specification
Alarm masking
AOFS - n/a 0
specification
PV Process variable △(*3) PV engineering unit value SL
RAW Raw input data - n/a
SV Setpoint value △(*4) SL
unit as PV
unit as PV
RSV Remote setpoint value △(*5) SL
unit as PV
DV Control deviation value - 0
unit as PV
VN I/O compensation value x n/a 0
MV Manipulated output value △(*6) MV engineering unit value MSL
RMV △(*7) MSL
RLV1 Reset limit value 1 - MSL
unit as MV
RLV2 Reset limit value 2 - MSL
unit as MV
High-high limit alarm
HH x SL to SH SH
setpoint
Low-low limit alarm
LL x SL to SH SL
setpoint
PH High limit alarm setpoint x SL to SH SH
PL Low limit alarm setpoint x SL to SH SL

PVP - n/a
Sample unit as PV
−: Entry is not permitted.
Table 1.14-4 Data items of ZWOPID block (2/2)

Data Name Range(*2)
Item Not(*1) (*2)
MH x MSL to MSH MSH
limit setpoint
ML x MSL to MSH MSL
limit setpoint
20
I Integral time x 0.1 to 10,000 seconds
seconds
CB Compensation bias x n/a 0.000
value
OPHI Output high limit index x MSL to MSH MSH
OPLO Output low limit index x MSL to MSH MSL
UAID User application ID x n/a 0
Value in the same
SH PV scale high limit - n/a
Value in the same
SL PV scale low limit - n/a
Value in the same

MSH MV scale high limit - n/a
Value in the same
MSL MV scale low limit - n/a
Value in the same
RBVL AO readback value - 0
RBST Data status for AO readback - 0x00 to 0xFF 0x00
0 (No output loss)
MPST During MV loss - 0
1 (During output loss)
−: Entry is not permitted.
SEE For more information about valid block modes of the PID block, refer to:
1.15 Manual Loader Block (MLD) Page 1 of 2
1.15 Manual Loader Block (MLD)

Manual Loader Block (MLD) may be applied to output manipulated output value (MV) to manually
operate final control elements, such as control valves.
Manual Loader Block (MLD)

▼ Connection
Manual Loader Block (MLD) outputs manipulated output value (MV) set from operation and
monitoring function. When in tracking (TRK) mode, the tracking input signal received from the TIN
terminal is output as manipulated output value (MV).
The figure below shows a function block diagram of the Manual Loader Block (MLD):
Figure 1.15-1 Function Block Diagram of Manual Loader Block (MLD)
the Manual Loader Block (MLD):
Table 1.15-1 Connection Methods and Connected destinations of the I/O Terminals of Manual
Loader Block (MLD)

Manipulated
OUT x x x x
output
Tracking signal
TIN x Δ x x
input
Tracking SW
TSI x Δ x x x
input
link block (ADL).
Function of Manual Loader Block (MLD)

The MLD block performs output processing and alarm processing.
The only processing timing available for the MLD block is a periodic startup. Selections available for
1.15 Manual Loader Block (MLD) Page 2 of 2
SEE For more information about the types of output processing and alarm processing possible for the
ALSO MLD block, refer to:
Data Items - MLD

Table 1.15-2 Data Items of Manual Loader Block (MLD)

Item Not (*1) (*2)
AF Alarm detection specification ----- 0
AOFS Alarm masking specification ----- 0
MV engineering unit
MV Manipulated output value Δ (*3) MSL
value
Manipulated variable high-limit
MH x MSL to MSH MSH
setpoint
Manipulated variable low-limit
ML x MSL to MSH MSL
setpoint
*2: MSH: MV scale high limit
*3: Entry is permitted when the block mode is MAN
SEE For more information about valid block modes of the MLD block, refer to:
1.16 Manual Loader Block with Input Indicator (MLD-PVI) Page 1 of 3
1.16 Manual Loader Block with Input Indicator

(MLD-PVI)
Manual Loader Block with Input Indicator (MLD-PVI) may output manipulated output value while
displaying the process variable (PV). It may be applied to manually operate final control elements
and observing the process variable (PV) at the same time.
Manual Loader Block with Input Indicator (MLD-PVI)

▼ Connection
Manual Loader Block with Input Indicator (MLD-PVI) displays the value input from the IN terminal as
process variable (PV). It also outputs the value set from operation and monitoring function as
manipulated output value (MV). In tracking (TRK) mode, the block outputs the tracking input signal
received from the TIN terminal as manipulated output value (MV).
The figure below shows a function block diagram of the Manual Loader Block with Input Indicator
(MLD-PVI):
Figure 1.16-1 Function Block Diagram of Manual Loader Block with Input Indicator (MLD-PVI)
the Manual Loader Block with Input Indicator (MLD-PVI):
Loader Block with Input Indicator (MLD-PVI)

Measurement
IN x Δ x x
input
Manipulated
OUT x x x x
output
Tracking signal
TIN x Δ x x
input
Tracking SW
TSI x Δ x x x
input
link block (ADL).
Function of Manual Loader Block with Input Indicator

(MLD-PVI)
The MLD-PVI block performs input processing, output processing, and alarm processing.
The only processing timing available for the MLD-PVI block is a periodic startup. Selections available
ALSO processing possible for the MLD-PVI block, refer to:
Data Items - MLD-PVI

Table 1.16-2 Data Items of Manual Loader Block with Input Indicator (MLD-PVI)

Item Not (*1) (*2)
MODE Block mode x ----- O/S(MAN)
Alarm detection
AF ----- 0
specification
Alarm masking
AOFS ----- 0
specification
HH x SL to SH SH
setpoint
LL x SL to SH SL
setpoint

unit as PV
MH x MSL to MSH MSH
limit setpoint
ML x MSL to MSH MSL
limit setpoint
unit as PV
unit as PV
SEE For more information about valid block modes of the MLD block, refer to:
1.17 Manual Loader Block with Auto/Man SW (MLD-SW) Page 1 of 10
1.17 Manual Loader Block with Auto/Man SW

(MLD-SW)
Manual Loader Block with Auto/Man SW (MLD-SW) may be applied as the lowest downstream block
in the control loops that consist of multiple function blocks.
Manual Loader Block with Auto/Man SW (MLD-SW)

▼ MLD-SW AUT/CAS, Connection
The Manual Loader Block with Auto/Man SW (MLD-SW) selects the manipulated output signals to be
sent to final control elements, by switching between the output signal received from a controller and
its own manually manipulated output signal.
In the manual (MAN) mode, the Manual Loader Block with Auto/Man SW (MLD-SW) outputs the
value set from operation and monitoring function as manipulated output value (MV) to operate the
final control element. In the automatic (AUT) mode or cascade (CAS) mode, it performs control
computation processing to the value input from other function block (CSV), and outputs the result as
a manipulated output value (MV) while in the manual mode (MAN) it outputs the MV set from the
operation and monitoring function.
Whether to set the cascade (CAS) mode or automatic (AUT) block mode for outputting the result
obtained by control computation processing of the value input from other function block, may be
selected for each control station on the property sheet 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)
Figure 1.17-1 Function Block Diagram of Manual Loader Block with Auto/Man SW (MLD-SW)
the Manual Loader Block with Auto/Man SW (MLD-SW):
Loader Block with Auto/Man SW (MLD-SW)


Manipulated
OUT x x x x
output
Auxiliary
SUB x Δ x x
output
Tracking signal
TIN x Δ x x
input
Tracking SW
TSI x Δ x x x
input
Interlock SW
INT x Δ x x x
input
link block (ADL).
Function of Manual Loader Block with Auto/Man SW

(MLD-SW)
The MLD-SW block performs control computation processing, output processing, and alarm
processing.
The only processing timing available for the MLD-SW block is a periodic startup. Selections available
ALSO MLD-SW block, refer to:
Control Computation Processing of Manual Loader Block with

Auto/Man SW (MLD-SW)
The table below shows the control computation processing functions of the Manual Loader Block
with Auto/Man SW (MLD-SW):
Table 1.17-2 Control Computation Processing Functions of Manual Loader Block with Auto/Man
SW (MLD-SW)
Control computation
Description
processing
Performs computation processing to the cascade setpoint value (CSV) and
Automatic control output
obtains a setpoint value (SV). Then, performs range conversion to this SV and
computation
obtains a manipulated output value.
Control output action actual manipulated output value (MV). The control output actions available with
this function block are of “positional type” only.
Set the setpoint value (SV) which was converted to the cascade setpoint value
(CSV) to the CSU.
Performs inverse operation on the manipulated output value to obtain SV and
CSV and uses them as a setpoint value (SV) and cascade setpoint value (CSV),
Output
respectively. Combining this function with output tracking prevents the
pushback
manipulated output value (MV) from changing abruptly when the mode is
changed to automatic.
Bumpless Obtains a BIAS value to balance the manipulated output value and cascade
switching setpoint value, and resets the bias term. Combining this function with output
Bias tracking
tracking prevents the manipulated output value (MV) from changing abruptly
when the mode is changed to automatic.
Setpoint Causes the current manipulated output value (MV) to gradually approach the MV
value ramp value converted from the setpoint value. This prevents the manipulated output
action value (MV) from changing abruptly when the mode is changed to automatic.
MAN fallback
Stops the control action of function blocks currently operating automatically,
Block mode change
while disabling the stopped function blocks from changing to the automatic
interlock
operating mode.
Automatic Control Output Computation

The automatic control output computation function converts the value set from other function blocks
as a cascade setpoint value (CSV) to a manipulated output value (MV).
Characteristics of Automatic Control Output Computation

The following computational expression is used in automatic control output:
The computation processing shown below is performed to the cascade setpoint value (CSV) to
obtain a setpoint value (SV):
SV=GAIN • CSV+BIAS
When the block mode is automatic (AUT) or cascade (CAS), a manipulated output value (MV) is
obtained by performing range conversion to the setpoint value (SV).
The following computational expression is used in range conversion:

SSH : SV scale high limit
SSL : SV scale low limit
Set Parameters of Automatic Control Output Computation

The parameters of automatic control output computation:
• Gain (GAIN)
Arbitrary data.
• Bias value (BIAS)
Engineering unit data within the ±SV scale span range.
The default is 0.0.
Setpoint range (SV)

▼ SV Range
Referencing the output range of the connected function block, set the setpoint value (SV) range:
• SV range high limit
Numerical values of seven digits or less, where the sign and decimal point occupy one digit each.
The default is “100.0”.
• SV range low limit
Specify a numeric value of 7 digits or less, where the sign and decimal point occupy one digit
each.
The default is “0.0”.

The control output action converts the manipulated output change (MV) of each control period to an
actual manipulated output value (MV).
The control output actions applied in Manual loader with Aut/Man SW (MLD-SW) is “positional type.”
The manipulated output value (MV) is the value obtained from automatic control output computation.

When output is clamped, the setpoint value (SV) is converted to and set as a cascade setpoint value
(CSV), using the following computational expression:
The setpoint value pushback action does not take place if GAIN is 0.
Bumpless Switching
The bumpless switching performed by the Manual Loader Block with Auto/Man SW (MLD-SW)
include the following types:
• Output pushback
• Bias tracking
• Setpoint value ramp action
Output Pushback
The output pushback function calculates a setpoint value (SV) and cascade setpoint value (CSV)
from the manipulated output value (MV) when the block is in the manual (MAN) or initialization
manual (IMAN) mode, and put it to the setpoint value (SV) and cascade setpoint value (CSV),
respectively. Output pushback is used when an upstream block is cascade connected to the Manual
Loader Block with Auto/Man SW (MLD-SW), and the upstream block is tracking to the MLD-SW. With
the combination of the output pushback and the output tracking function of the cascade connected
upstream control block, the manipulated output value (MV) of the cascade connected upstream
block changes in accordance with the manipulated output value (MV) of the Manual Loader Block
with Auto/Man SW (MLD-SW) when the cascade connection is open. This action allows to change
the block mode for the Manual Loader Block with Auto/Man SW (MLD-SW) from manual (MAN) to
automatic (AUT) bumplessly and without balancing.
The computational expressions of output pushback:
The output pushback action takes place when the following settings are performed:
• “No” is set for bias tracking.
• A value other than “0” is set for GAIN.
The following figure shows an action example of output pushback:
A Manual Loader Block with output switch is cascade connected in the middle of this loop, when the
cascade connection is open the manipulated output value (MV) of the upstream block is forced to be
equal to the setpoint value (SV) of the downstream block in the same cascade loop:
Figure 1.17-2 Output Pushback and Output Value Tracking when Cascade is Open
In the above action example, bumpless switching is realized by the following three functions:
• Output value tracked by the upstream block in the cascade loop
• Output pushback by the Manual Loader Block with Auto/Man SW (MLD-SW)

• Output value tracks the downstream by the Manual Loader Block with Auto/Man SW (MLD-SW)
Bias Tracking
▼ Bias Tracking
The bias tracking function calculates a bias value (BIAS) that allows the manipulated output value
(MV) to agree with the MV value converted from the cascade setpoint value (CSV), and replaces the
current bias value (BIAS) with the calculated value. Bias tracking is used when an upstream block
cascade connected to the Manual Loader Block with Auto/Man SW (MLD-SW) performances the
output value tracking function. By using the bias tracking function, switching of the block mode from
manual (MAN) to automatic (AUT) can be performed bumplessly. When cascade connection is open,
the upstream block’s MV does not only follow the changes of MV of the Manual Loader Block with
Auto/Man SW (MLD-SW) but also adds the bias of the Manual Loader Block with Auto/Man SW (MLD-
SW), so that the bump can be avoided when connection switches back to cascade.
The computational expressions of bias tracking:
BIAS=SV-GAIN • CSV
Use the Function Block Detail Builder to define bias tracking.
Bias Tracking: Select “Yes” or “No.”
If “Yes” is defined for bias tracking, the output pushback and setpoint value ramp actions will not be
performed. If “No” is defined for bias tracking, these two actions will take place. However, the
setpoint value ramp action is not performed if the ramp constant (RP) set parameter remains at its
default value.
When the upstream function block in cascade connection is a Cascade Signal Distributor Block
(FOUT), define “Yes” for bias tracking. This activates the bias tracking action even when the
Cascade Signal Distributor Block (FOUT) has multiple output connected destinations and the Manual
Loader Block with Auto/Man SW (MLD-SW) in cascade is closed when connected to the second
output destination or thereafter.
Setpoint Value Ramp Action

The setpoint value ramp action causes the current manipulated output value (MV) to gradually
approach the manipulated output value (MV) converted from the setpoint value (SV). This function is
used when a upstream block cascade connected to the Manual Loader Block with Auto/Man SW
(MLD-SW) is not defined the output tracking function.
The setpoint value ramp action takes place when the following two block mode changes are
performed:
• The block mode changes from manual (MAN) to an automatic (AUT or CAS) mode.
• The initialization manual (IMAN) mode is canceled while the block is still in an automatic (AUT or
CAS) mode.
The setpoint value ramp action causes the current manipulated output value (MV) to approach the
manipulated output value (MV) converted from the setpoint value (SV), by limiting the change per-
scan period in the setpoint value (SV) that is used to calculate a manipulated output value (MV)
(effective setpoint value) to equivalent to or less than the ramp constant (RP), when the setpoint
value (SV) changes as a result of the above two block mode changes.
The following example shows the action of the setpoint value ramp:
Figure 1.17-3 Action Example of the Setpoint Value Ramp
The setpoint value ramp action takes place only when “No” is defined for the bias tracking.
The parameter of the setpoint value ramp action:
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.

manual condition is established, and changes the block mode of the function block to initialization
manual (IMAN).
When output value tracking is set to “Yes” with the Function Block Detail Builder, the manipulated
output value (MV) is tracked to the value of the connection destination when initialization manual
goes into effect. Because of this, even if the mode is changed to the manual (MAN) mode during
initialization manual (IMAN) mode, the initialization manual (IMAN) mode takes priority and the
operation to change to the manual (MAN) mode 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 the initialization condition vanishes.

The initialization manual condition is a block mode transition condition that suspends the control
(IMAN). The initialization manual (IMAN) block mode becomes active only when the initialization
manual condition is established.
The following example shows when the initialization manual condition establishes and vanishes:
AUT
↓ Initialization manual condition established
IMAN (AUT)
AUT
• When the manipulated output value (MV) connected destination’s data status is conditional (CND)
(i.e., the cascade loop open).
91) and the cascade connection is switched off (i.e., the cascade loop open).
or output open alarm has occurred in the module.
• When the data status of the input signal at the TIN or TSI terminals becomes invalid (BAD) in the
MAN Fallback
The MAN fallback is an error processing function that stops the control and forces the function block
to enter manual operation state. This action takes place when the MAN fallback condition is
established.
Characteristics of the MAN Fallback

regardless of the current operation status, and forces the function block to enter manual operation
state.
Once the MAN fallback condition is established, the block mode remains manual (MAN) even when
the condition later vanishes.

The following example shows when the MAN fallback condition is established:
AUT→MAN
IMAN (AUT) →IMAN (MAN)
• When the data status of the cascade setpoint value (CSV) is invalid (BAD).
• When the manipulated output value (MV) is connected to a process I/O module and the FCS is
having an initial cold start.
• When the manipulated output value (MV) is connected to a process I/O module, and one of the
I/O points connected to the module is undergoing maintenance load.

• Any block mode change command to make the function block into automatic operation state
(AUT or CAS mode) become invalid.

Data Items - MLD-SW

Table 1.17-3 Data Items of Manual Loader Block with Auto/Man SW (MLD-SW)

Item Not (*1) (*2)
SV Setpoint value SV engineering unit value SSL
Value in the same
CSV Cascade setpoint value x SSL
engineering unit as SV
MH x MSL to MSH MSH
limit setpoint
ML x MSL to MSH MSL
limit setpoint
GAIN Gain x ----- 1.000
BIAS Bias x ± (SSH - SSL) 0.0
RP Ramp consistant x 0 to (SSH - SSL) SSH to SSL
value

*2: SSH: SV scale high limit
SSL: SV scale low limit
SEE For more information about valid block modes of the MLD-SW block, refer to:
1.18 Motor Control Blocks (MC-2, MC-2E, MC-3, and MC-3E) Page 1 of 7
1.18 Motor Control Blocks (MC-2, MC-2E, MC-3,

and MC-3E)
The Motor Control Blocks MC-2, MC-2E, MC-3, and MC-3E are applied to operate motor-driven
pumps and motor-operated valves. These blocks may be used to start or stop motors from operation
and monitoring functions or to control them automatically.
There are four models of Motor Control Block (MC-2, MC-2E, MC-3, and MC-3E), which behaves in
different output manner.
• Two-Position Motor Control Block (MC-2)
• Enhanced Two-Position Motor Control Block (MC-2E)
• Three-Position Motor Control Block (MC-3)
• Enhanced Three-Position Motor Control Block (MC-3E)
Motor Control Blocks (MC-2, MC-2E, MC-3, and MC-3E)

▼ Connection
The motor control blocks are provided with function to operate motor-driven pumps and motor-
operated valves.
The motor control blocks enable starting and stopping of motors from operation and monitoring
functions. Also, combining the motor control blocks with the sequence control function to realize the
automatic control on motors.
The MC-2E (*1) and MC-3E (*1) blocks function the same as MC-2 and MC-3 blocks but have the
additional capability to connect to FF faceplate blocks and fieldbus function blocks. Moreover, the
input terminals for the two contacts and the output terminals for the two or three contacts can be
defined separately so that the two or three irrelevant channels can be used.
*1: MC-2E and MC-3E blocks can be applied to all field control stations except standard PFCS. When using
MC-2E or MC-3E block, it is necessary to add the option [DIOENH] on the [Constant] tab of the FCS
properties sheet.
The figure below shows the function block diagram of the motor control blocks (MC-2, MC-3):
Figure 1.18-1 Function Block Diagram of the Motor Control Blocks (MC-2, MC-3)
the Motor Control Blocks (MC-2, MC-3):
Table 1.18-1 Connection Methods and Connected destinations of the I/O Terminals of Motor
Control Blocks (MC-2, MC-3)
Data Data Terminal Process Software Function

I/O terminal
IN Answerback input x Δ x x
Manipulated
OUT x Δ x x
output
Feedback signal
FB x Δ x x
input
Thermal trip
TT x Δ x x x
signal input
Operation
IL x Δ x x x
interlock input
Bypass command
SWI x Δ x
SW input
TSI Tracking SW input x Δ x x x
Interlock SW
INT x Δ x x x
input
link block (ADL).
The figure below shows the function block diagram of the motor control blocks (MC-2E):
Figure 1.18-2 Function Block Diagram of the Enhanced Two-position Motor Control Blocks (MC-
2E)
the Motor Control Blocks (MC-2E):
Two-position Motor Control Blocks (MC-2E)

Answerback
IN1 x Δ x x x
input1
Answerback
IN2 x Δ x x x
input2
Manipulated
OUT1 x x x x x
output1
Manipulated
OUT2 x x x x x
output2
Feedback signal
FB x Δ x x
input
Thermal trip
TT x Δ x x x
signal input
Operation
IL x Δ x x x
interlock input
Bypass
SWI command SW x Δ x
input
Tracking SW
TSI x Δ x x x
input
Interlock SW
INT x Δ x x x
input
link block (ADL).
The figure below shows the function block diagram of the motor control blocks (MC-3E):
Figure 1.18-3 Function Block Diagram of the Enhanced Three-position Motor Control Blocks (MC-
3E)
the Motor Control Blocks (MC-3E):
Three-position Motor Control Blocks (MC-3E)

Answerback
IN1 x Δ x x x
input1
Answerback
IN2 x Δ x x x
input2
Manipulated
OUT1 x x x x x
output1
Manipulated
OUT2 x x x x x
output2
Manipulated
OUT3 x x x x x
output3
Feedback signal
FB input x Δ x x
Thermal trip
TT x Δ x x x
signal input
Operation
IL x Δ x x x
interlock input
Bypass
SWI command SW x Δ x
input
Tracking SW
TSI x Δ x x x
input
Interlock SW
INT x Δ x x x
input
link block (ADL).
If the OUTn terminals of MC-2E or MC-3E are connected to different output

modules or if the terminals are connected to FF faceplate blocks or fieldbus
function blocks, the simultaneity of the two or three outputs are not
guaranteed. The same phenomenon happens to IN1 and IN2 terminals under
the same circumstances.
Functions of Motor Control Blocks (MC-2, MC-2E, MC-3,

and MC-3E)
The motor control blocks perform input processing, control computation processing, output
The only processing timing available for the motor control blocks is a periodic startup. Moreover,
only the basic scan period can be selected as the scan period to execute the periodic startup.
ALSO motor control blocks, refer to:
Input Processing Specific to Motor Control Blocks (MC-2, MC-

The motor control blocks perform special input signal conversions.
Control Computation Processing of the Motor Control Blocks

(MC-2, MC-2E, MC-3, and MC-3E)
The table below shows the control computation processing functions of the Motor Control Blocks:
Table 1.18-4 Control Computation Processing Functions of the Motor Control Blocks (MC-2, MC-
Control
processing
Compares the answerback input value (PV) with manipulated output value (MV) and
Answerback check checks if the final control element is operating in accordance with the output signals
from the motor control block.
Changes the block mode to IMAN to temporarily suspend the control action. This action
takes place when the initialization manual condition becomes satisfied.
MAN fallback
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
Computer failure
operating in the ROUT mode. This action takes place when the computer failure
Starts sequentially and at specific intervals the multiple motor control blocks belonging
Serial start to the same group within the same control station , when start requests are issued to
these blocks simultaneously.
Counts the number of times the manipulated output value (MV) has changed from “0”
Start count
to “2” or from “1” to “2,” and uses the obtained value as the number of starts (OCNT).
Totalizes the periods of time during which the manipulated output value (MV) remains
Operating time
at “1” or “2,” and uses the obtained value as the operating time (ONTM).
Status change Outputs a status change message when block mode is changed or when a specific
message block status is changed.
Simulation function Simulates the internal processing actions of the motor control blocks.
Bypass command Bypasses actions in accordance with the condition specified by the bypass command
switch switch.
Output Processing Specific to Motor Control Blocks (MC-2, MC-

The motor control blocks perform output processing that is different from the output processing
performed by other function blocks. The following lists the output processing items specific to the
motor control blocks.
• Setting method of manipulated output value (MV)
• Output signal conversion
• Inching output
• Remote/local input function
• Answerback tracking function
• Interlock check function
• Off-service function
Alarm Processing Specific to Motor Control Blocks (MC-2, MC-

The following lists the alarm checks performed by the motor control blocks.
• Feedback input high and low limit alarm check
• Thermal trip alarm check
• Interlock alarm check
• Answerback unset alarm check
• Answerback error alarm check
Data Items - MC-2, MC-2E, MC-3, and MC-3E

Table 1.18-5 Data Items of Motor Control Blocks (MC-2, MC-2E, MC-3, and MC-3E) (1/2)
Data Entry Permitted or Not Default

Data Name Range
Item (*1) (*2)
BSTS Block status ----- NR
PV Answerback input value Δ (*3) 0 to 2 0
FV engineering unit
FV Feedback input value SL
value
Inching output setpoint
SV x 0 to 100 % 0%
value
CSV Sequence setpoint value x 0, 1, 2 0
MV Manipulated output value Δ (*4) 0, 1, 2 0
Remote manipulated output
RMV Δ (*5) 0, 1, 2 0
value
RAW Answerback raw signal 0, 1, 2 0
ONCT Number of starts x 0 to 99999999 0
0 to 99999999
ONTM Operating time count x 0 second
seconds
ONTH Operating time hour unit 0 to 27777 hours 0 hour
ONTS Operating time second unit 0 to 3599 seconds 0 second
*5: Entry is permitted when the block mode is ROUT
Table 1.18-6 Data Items of Motor Control Blocks (MC-2, MC-2E, MC-3, and MC-3E) (2/2)

Item Not (*1) (*2)
Feedback input high - limit

PH x SL to SH SH
alarm setpoint
Feedback input low - limit
PL x SL to SH SL
alarm setpoint
ANSP Answerback setpoint x SL to SH SL
Answerback check masking
MTM x 0 to 10,000 seconds 0 seconds
time
SVH Setpoint high limit x 0 to 100 % 100 %
SVL Setpoint low limit x 0 to 100 % 0%
BPSW Bypass command switch x 0, 1, 2, 3, 4 0
SIMM Simulation switch x 0, 1 0
Value in the same
SH FV scale high limit -----
engineering unit as FV
Value in the same
SL FV scale low limit -----
engineering unit as FV
*2: FV: Feedback input value
SEE For more information about valid block modes of the motor control blocks, refer to:
Block Status of Motor Control Blocks (MC-2, MC-2E, MC-

3, and MC-3E)
Table 1.18-7 Block Status of Motor Control Blocks (MC-2, MC-2E, MC-3, and MC-3E)
Block Status
Level Description
Symbol Name
3 ANCK Answer - Back Check Inhibition Answer - Back Check is inhibited
OFF Off Service Output is stopped
2
LOCK Interlock Forced to output a preset value.
SIM Simulation Stops output but simulates the output actions.
1
NR Normal Normal status
1.18.1 Input Processing of Motor Control Block (MC-2, MC-2E, MC-3, and MC-3E) Page 1 of 4
1.18.1 Input Processing of Motor Control Block (MC-2, MC-

Input signals specific to the Motor Control Blocks include feedback input signal and answerback
input signal. “Input Signal Conversion of Feedback Input,” “Input Signal Conversion of Answerback
Input” and “Input Signal Conversion of Feedback Input Value into Answerback Input Value” are
provided for conversion of these signals. “FV Overshoot” is an input processing of motor control
blocks.
SEE For more information about the FV overshoot, refer to:

ALSO 3.4, “PV/FV/CPV Overshoot” in Function Blocks Overview (IM 33J15A20-01EN)
Input Signal of Motor Control Block (MC-2, MC-2E, MC-

3, and MC-3E)
Input signals specific to the Motor Control Blocks are shown as follows.
Feedback Input Signal

Feedback input signal is used when the feedback terminal (FB) in the motor control block is
connected to analog input modules or other function blocks. The feedback signal often indicates the
connected field equipment status such as the openness of a motor-operated valve.
Answerback Input Signal

Answerback input signal is used when the IN terminal in the motor control block is connected to a
contact input or other internal status switch. For M2-CE and M3-CE blocks, the answerback signals
are the signals from the FF faceplate blocks, fieldbus function blocks, internal switches or contact
Inputs that connected to IN1 and IN2 terminals. The answerback signal often indicate the state of
onsite equipment such as the open/close status of motor-operated valve or the start/stop status of
pump operation.
Input Signal Conversion Specific to Motor Control Block (MC-2,

MC-3)
The motor control block uses a special input signal conversion corresponding to the feedback input
signal and answerback input signal.
• Input Signal Conversion of Feedback Input
• Input Signal Conversion of Answerback Input
• Input Signal Conversion of Feedback Input Value into Answerback Input Value
Input Signal Conversion of Feedback Input

▼ Feedback Low-Input Cutoff
Feedback value (FV) is the signal that the feedback terminal FB received from its connection
destination without conversion. However, if the value from FB is equal to or less than the low-input
cutoff value, the feedback value (FV) is set to 0.
Input signal conversion setting parameters for the feedback input signal are given below.
FV scale high limit (SH) : Set FV engineering unit data.
FV scale low limit (SL) : Set FV engineering unit data.
Also, the setup for feedback low-input cutoff can be executed on the Function Block Detail Builder.
Feedback Low-input Cutoff: Set FV engineering unit data.
The default setting is 0.0.
Input Signal Conversion of Answerback Input

▼ Input Signal Conversion
The answerback input value (PV) is the answerback input signal read from IN or IN1 and IN2
terminals’ connection destinations, such as connected contact inputs or other internal status
switches then converted into the code values.
Number of Answerback Input Points

There are two kinds of answerback input signal conversion methods. The number of answerback
input points is determined depending on the type of conversion.
• 2-Status Input (answerback=1 point)
• 3-Status Input (answerback=2 points)
The selection of input signal conversion type may be performed on the Function Block Detail Builder.
Input signal conversion type: Set “2-Status Input” or “3-Status Input.”
The default setting is “2-Status Input.”
Direction of Answerback
Direction of answerback specify the meaning of ON/OFF, status of answerback input signal, which
reflect the final control element status if it operates properly according to the manipulated output
value (MV) from the motor control block.
The setup for direction of answerback may be performed on the Function Block Detail Builder.
• Direction of Answerback
For MC-2, MC-3 blocks: Select “Direct,” “Reverse,” “Inverted connect direct action” or “Inverted
connect reverse action.”
For MC-2E, MC-3E blocks: Select “Direct” or “Reverse.”
The default setting is “Direct.”
Conversion of Answerback Input Signal into Answerback Input

Value (PV)
Either 0, 1 or 2 is set for the answerback input value in the function block depending on the
direction and contact status of answerback input signal. Connect the input n to the answerback
input signal indicating “open” and the input n+1 to the answerback input signal indicating “close,”
and vice versa for inverted connection. (*1)
*1: Inverted connection is not available for MC-2E and MC-3E blocks.
The table below shows the correlation between the answerback input value (PV) and contact status.
Table 1.18.1-1 Determination of Answerback Input Signal
Contact status
Action of answerback PV Alarm
Number of answerback
points n n+1
(*1) (*2)
ON - 2 -
Direct
OFF - 0 -
1
ON - 0 -
Reverse
OFF - 2 -
ON OFF 2 -
OFF OFF 1 -
Direct OFF ON 0 -
Hold previous
ON ON PERR
value (*3)
ON OFF 0 -
Hold previous
OFF OFF PERR
Reverse value (*3)
OFF ON 2 -
ON ON 1 -
2
OFF ON 2 -
OFF OFF 1 -
Inverted connection direct
action (*4) ON OFF 0 -
Hold previous
ON ON PERR
value (*3)
OFF ON 0 -
Hold previous
Inverted connection reversed OFF OFF PERR
value (*3)
action (*4)
ON OFF 2 -
ON ON 1 -
*1: “n” in the table indicates the element number specified to connect to IN terminal of MC-2 and MC-3
blocks, or the IN1 terminal of MC-2E and MC-3E blocks. The answerback input signal read from the
element n represents the status of “open;” vise versa, when the connection is inverted, the answerback
input signal read from the element n represents the status of “close.”
*2: “n+1” in the table indicates the element number succeeding the element number “n” that is specified
to connect to IN terminal of MC-2 and MC-3 blocks, or the element number specified to connect to IN2
terminal of MC-2E and MC-3E blocks. The answerback input signal read from the element n+1
represents the status of “close;” vise versa, when the connection is inverted, 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.
*4: “Inverted connection direct action” and “Inverted connection reversed action” are not available for MC-
2E and MC-3E blocks.
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
inconsistency alarm (PERR) is activated.
Input Signal Conversion of Feedback Input Value into
Answerback Input Value

If the answerback input terminal has no connection while the feedback input terminal is in
connection, the answerback input value (PV) is set to one of the following values after comparing
the feedback input value (FV) with the answerback setpoint (ANSP).
• If FV≥ANSP, PV=2
• If FV<ANSP, PV=0
The answerback setpoint (ANSP) is a data in the engineering unit that indicates the scale range
between feedback input value (FV), and can be updated as a setting parameter while the system is
running.
If the data status of feedback input value (FV) is invalid (BAD), the status of answerback input value
(PV) is set invalid (BAD) with the previous answerback input value (PV) latched.
If both the answerback input terminal and the feedback input terminal are in connection, the
answerback input precedes. The answerback input is converted into the answerback input value
(PV) through input signal conversion.
If neither the answerback input terminal nor the feedback input terminal are in connection, the
previous answerback input value (PV) is latched.
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.
1.18.2 Control Computation Processing of Motor Control Blocks (MC-2, MC-2E, MC... Page 1 of 10
1.18.2 Control Computation Processing of Motor Control

Blocks (MC-2, MC-2E, MC-3, and MC-3E)
This section describes the control computation processing functions of the motor control blocks,
which are listed below.
• Answerback check
• Initialization manual
• MAN fallback
• Computer fail
• Block mode change interlock
• Serial start
• Start count
• Operating time
• Status change message
• Simulation function
• Bypass command switch (BPSW)
Answerback Check
The answerback check function checks if the final control elements are operating normally in
accordance with the output signals from the Motor control blocks. Unless the manipulated output
value (MV) is changed, the answerback input value (PV) and manipulated output values (MV) are
constantly compared. If the two do not agree with each other, an alarm is generated.
The following types of alarms are generated:
• Positive answerback error alarm (ANS+)
Generated when the manipulated output value (MV) is “2” and the answerback input value (PV)
is not “2”.
• Negative answerback error alarm (ANS-)
Generated when the manipulated output value (MV) is “0” and the answerback input value (PV)
is not “0”.
While the answerback error alarm exists, if the answerback input value (PV) and manipulated 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 ANCK status,
indicating that the answerback check is in progress. The answerback check masking (ANCK) status
will be canceled when the answerback input value (PV) comes to meet the manipulated output value
(MV). When the answerback masking time is elapsed, the answerback check masking (ANCK) status
is also canceled even the answerback input value (PV) does not meet the manipulated output value
(MV).
The answerback check function stops in the following conditions:
• When the block status is simulation (SIM).
• When the block mode is tracking (TRK).
• When answerback bypass is specified (BPSW=1 or 3).

• When the manipulated output value (MV) is “1.”
• When the data status of the answerback input value (PV) is calibration (CAL).
• When out of service (BPSW=4) is specified.
In the initialization manual (IMAN) mode, the answerback check masking timer behaves as if the
masking time has already elapsed, and the Motor control blocks maintain their alarm status.
SEE For more information about answerback check masking status, conformity between answerback
ALSO input value (PV) manipulate output value (MV), refer to:
" Conditions to Release Answerback Check Mask" in " Answerback Check" in
1.18.2, "Control Computation Processing of Motor Control Blocks (MC-2, MC-2E, MC-3, and
MC-3E)"
Define the Answerback Check

▼ Answerback Check
Select the answerback check monitoring action from the following three types:
• Positive monitoring
Starts the answerback check masking timer at the start of output (OFF→ON). If the answerback
input value (PV) still disagrees with manipulated output value (MV) after the answerback check
masking time has elapsed, an alarm is generated. If output is OFF, no alarm will be generated
even when the answerback input value (PV) does not agree with manipulated output value (MV).
• Negative monitoring
Starts the answerback check masking timer at the end of output (ON→OFF). If the answerback
masking time has elapsed, an alarm is generated. If output is ON, no alarm will be generated
even when the answerback input value (PV) does not agree with manipulated output value (MV).
• Both-side monitoring
Starts the answerback check masking timer at the start and end of output. If the answerback
masking time elapsed, an alarm is generated.
Use the Function Block Detail Builder to define the answerback check.
Answerback Check: Choose [No], [Both Sides], [Open] or [Close].
The default is [No].
Conditions to Release Answerback Check Mask

▼ Release Answerback Check Mask
When the block is in the status that the answerback check is masked (ANCK), if the answerback
input value (PV) changes to meet the manipulate output (MV), the answerback check mask (ANCK)
will be released. However, user can change the condition for releasing the answerback check mask;
thus, the answerback check mask will not be released until the answerback check masking time
elapsed.
Moreover, when the block is in the status that the answerback check is masked (ANCK), the input
high-limit alarm (HI) and input low-limit alarm (LO) are also masked. However, if checking input
open (IOP) is specified, the input open alarm (IOP) will not be masked.
Conditions to release answerback check mask can be set on the Function Block Detail Builder.
• Release Answerback Check Mask

Choose [PV=MV or MTM Timeout] or [MTM Timeout Only].
The default is [PV=MV or MTM Timeout].
The “Release Answerback Check Mask” option can be set to the following motor control blocks:
• MC-2 and MC-3 blocks in FFCS series, KFCS2, and LFCS2.
• MC-2E and MC-3E blocks in FCSs except PFCS.
If [PV=MV or MTM Timeout] is chosen as the condition to release the answerback check mask,
when answerback input value (PV) changes to agree the manipulated output value (MV), the
answerback check mask (ANCK) will be released.
If [MTM Timeout Only] is chosen as the condition to release the answerback check mask, when
answerback input value (PV) changes to agree the manipulated output value (MV), the answerback
check mask (ANCK) will not be released until the answerback check masking timer (MTM) becomes
timeout. When the answerback input value (PV) changed to agree the manipulated output value
(MV) but the block is still in answerback check masking (ANCK) status, if the manipulated output
value (MV) is changed again, the answerback check masking timer (MTM) will be re-initiated.
Answerback Bypass
The answerback bypass function forces the answerback input value (PV) to be equal to the
manipulated output value (MV) and stops the answerback check. The answerback bypass function is
activated when the bypass command switch (BPSW) is 1 or 3.
Set Parameters of the Answerback Check

The parameters of the answerback check:
• Answerback checks masking time (MTM)
0 to 10000 seconds.
The default is 4 seconds.
• Bypass command switch (BPSW)
Select 0, 1, 3 or 4.
The default is 0.
TIP Even when the serial start is specified, changing the manipulated output value (MV) triggers a
transition to the answerback check inhibition (ANCK) status.
SEE For more information about the bypass command switch (BPSW), refer to:
ALSO " Bypass Command Switch (BPSW)" in 1.18.2, "Control Computation Processing of Motor
Control Blocks (MC-2, MC-2E, MC-3, and MC-3E)"
The initialization manual function suspends the control output action temporarily during operation
when the initialization manual condition is established, and changes the block mode of the function
block to initialization manual (IMAN).

(IMAN).
The following example shows when the initialization manual condition establishes or vanishes:
AUT
↓ Initialization manual condition established
IMAN (AUT)
AUT
The initialization manual condition establishes in the following situation:
91) and the connection is switched off.
• When the manipulated output value (MV) connected destination is a process output module, and
a failure or output open alarm has occurred in the module.
MAN Fallback
established.

state.

AUT→MAN
IMAN (CAS) →IMAN (MAN)
• When the data status of the answerback input value (PV) is calibration (CAL).
• When the answerback abnormality designated on the builder item [Fallback operation on the
abnormal answerback] occurs.
• When the data status of the manipulated output value (MV) becomes output failure (PTPF).(*1)
• When the bypass command switch (BPSW) is in the out-of-service position (= 4).(*1)
• When the switch connected to the INT terminal is ON. (When the block mode change interlock
condition is established.)(*1)
• When the manipulated output value (MV) is connected to a process I/O and FCS initial cold start
occurs.(*1)
• When the manipulated output value (MV) is connected to a process I/O, and any settings of the
relevant module have been changed in maintenance.(*1)
*1: If the simulation switch (SIMM) is ON (= 1), MAN fallback does not occur even if the condition is
established.
Computer Fail
When the computer fail is detected, the function block suspends the action in the remote output
(ROUT) mode temporarily and switches to the computer backup mode.

When the function block mode is remote output (ROUT), the function block receives the
manipulated output value (MV) from a supervisory system computer via control bus communication.
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
execution of the block mode change command (MAN, AUT, CAS) and a remote mode (ROUT).
the Function Block Detail Builder (MAN, AUT, CAS) and a remote mode (ROUT).
mode changes to remote output (ROUT).

remote output (ROUT) mode and switches the mode to the computer backup mode.
A backup switch (BSW) is provided in function block to define the remote output (ROUT) mode. The
status of this switch determines whether the computer has failed or recovered. The value of the
backup switch (BSW) can be set from a sequence table or other function blocks.
mode other than remote output (ROUT).
• When the backup switch BSW=ON, computer has failed
• When the backup switch BSW=OFF, computer has recovered
An example when the automatic (AUT) mode has been specified for the computer backup mode is
shown as follows:
ROUT
↓ Computer fails
AUT (ROUT)
ROUT
shown as follows:
AUT
↓ ROUT command
Define Computer Backup Mode

Use the Function Block Detail Builder to set the computer backup mode for each function block.


• Any block mode change command to obtain an automatic operation state (AUT, CAS, or ROUT
mode) becomes invalid.

The block mode change interlock condition is established when the switch at the connected
destination of the interlock switch input terminal (INT) is turned ON as a result of continued
automatic operation becoming impossible due to an abnormality in the plant, etc.
Serial Start
▼ Serial Startup Group, MC Block – Serial Startup Interval
The serial start function put the Motor control blocks in the same control station into groups and
starts multiple Motor control blocks 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 that are waiting for serial start will
remain in the state of “not performing output although the manipulated 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.
Define serial start on Function Block Detail Builder and System View.
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 not 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 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 arbitrary ONCT value is set. The
number of starts (ONCT) can be initialized at any time as necessary.
The number of starts (ONCT) is not counted in the simulation mode (SIM) or during inching output
operation.
Operating Time
Totalizes the periods of time during which the manipulated output value remained at 1 or 2, and
stores the obtained value in the operating time (ONTM). The operating time (ONTM) is indicated in
seconds.
The operating time (ONTM) value is totalized from 0 to 99999999, and upon reaching 99999999,
returns to 0 with the next count.
The values representing the hour and second digits of the operating time are stored in the operating
time hour unit (ONTH) and operating time second unit (ONTS), respectively. The operating time
hour unit (ONTH) and operating time second unit (ONTS) are constantly updated in accordance with
changes in the operating time (ONTM).
The operating time (ONTM) will not be initialized automatically, even during initial cold start.
However, if an arbitrary value is set for the operating time (ONTM), the operating time (ONTM) is
initialized by that value. The operating time (ONTM) can be initialized at any time as necessary.
The operating time (ONTM) is not updated in the simulation mode (SIM) or during inching output
operation.
Status Change Message

The Motor control blocks issue a status change message when changes occur in the block mode or
status. The statuses for which a status change message is issued are “OFF” and “LOCK.”
When the block status changes from “OFF” or “LOCK,” a status change message is issued.
Simulation Function
The simulation function simulates the internal processing actions of the Motor control blocks. This
function is used when testing the operation of devices using Motor control blocks.
Setting and Canceling the Simulation Mode

The following section explains how to set and cancel the simulation mode:
• Setting the simulation mode
When the simulation switch (SIMM) is set to ON (=1), the simulation mode becomes active. The
simulation mode is indicated by the block status, “SIM.”
• Canceling the simulation mode
When the simulation switch (SIMM) is set to OFF (=0), the simulation mode is canceled and the
block returns to a normal state.
The table below shows actions of the motor control blocks in the simulation mode:
Table 1.18.2-1 Actions of Motor Control Block (MC-2, MC-3) Functions in the Simulation Mode
Function Action
Block mode Same as in a normal state, except IMAN.
Block status SIM
Alarm status No alarm is generated.
Answerback input Only takes in values for RAW.
Feedback input Only takes in values.
Thermal trip check No action.
• The check and alarm actions do not stop.
• When the answerback check specification is set to “enable,” the MV value is set as
Answerback check the PV value after the answerback check masking time elapses (*1).
• When the answerback check specification is “disabled,” the MV value is set as the PV
value immediately.
Calibration function
Same as in a normal state.
Remote/local input
Answerback
tracking No action.
Interlock check
• The output action stops, but the MV action continues as normal.
Output signal
• In the status type output, the current status of the output destinations is retained.
conversion
• In the pulsive type output, the status of all output destinations changes to OFF.
Inching output The output action stops, but the MV and SV actions continue as normal.
Serial start
No action.
Start count
Operating time
Status change
Same as in a normal state.
message
*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 For more information about the thermal trip check, refer to:
ALSO " Thermal Trip Alarm Check" in 1.18.4, "Alarm Processing of Motor Control Blocks (MC-2,
MC-2E, MC-3, and MC-3E)"
Actions after Cancellation of the Simulation Mode

The following actions take place in the first scan period after the simulation mode is canceled:
• Status output type
The contact status of the output destination is read back and set as the manipulated output value
(MV).
• Pulsive output type
When “Yes” is set for the answerback tracking function, the answerback input value (PV) is set as
the manipulated output value (MV). This processing is not performed while the answerback
bypass function is active.
The above actions take place commonly when the output status changes from stop to start,
regardless the cancellation of simulation mode.
Bypass Command Switch (BPSW)

The bypass command switch is used to stop the answerback check function, interlock check
functions, or output actions.
The table below shows the commands and actions of the bypass command switch (BPSW)
corresponding to different switch positions (0 to 4):
Table 1.18.2-2 Commands and Actions of the Bypass Command Switch (BPSW) Corresponding to
Different Switch Positions (0 to 4)
BPSW Command Action

0 No bypass Normal actions.
1 Answerback bypass The answerback bypass action is executed.
2 Interlock bypass The interlock action is stopped.
The answerback bypass action is executed.
3 Answerback + interlock bypasses
The interlock action is stopped.
Block mode=MAN
4 Out of service Block status=OFF
The answerback tracking action is executed.
The “out of service” corresponding the switch position 4 instructs the Motor control block to stop the
output action.
The value of the bypass command switch (BPSW) is set by the input signal from the bypass
command switch input terminal (SWI). If the SWI terminal is not connected, the value is set directly
from operation and monitoring functions or other function block.
The table below summarizes various types of bypasses that are explained in the sections of
1.18.2 Control Computation Processing of Motor Control Blocks (MC-2, MC-2E, ... Page 10 of 10
corresponding functions:
Table 1.18.2-3 Table of Function Bypasses
Mode Block status

Function(*1) BPSW =1.3 PV.CAL
TRK IMAN OFF LOCK SIM
Feedback input x x x x x x x
Answerback input x x x x
Thermal trip check x x x x x x x
Answerback check x x
Answerback bypass action (MV→PV) - - - x x -
Answerback tracking action (*2)
x - x - - x -
(PV→MV)
Interlock check x x (*3) x
Signal output (*4) (*5) x x x
*1: x: Bypass unless other condition denoted by “x” exist
Blank: Not Bypass
-: Irrelevant
*2: The answerback tracking is not active when the “answerback tracking specification” is “No.”
*3: If BPSW=3, the interlock check is not active.
*4: If the signal output status changes from “enable” to “disable” while pulsive output is in progress, the
output action will not stop after specified pulse-width signals are outputted. If the change occurs during
inching processing, the output action does not continue to finish the inching processing. However, no
further inching operation request is accepted.
*5: Same as x during status output while the answerback tracking action is active.
1.18.3 Output Processing of Motor Control Blocks (MC-2, MC-2E, MC-3, and MC-3E) Page 1 of 15
1.18.3 Output Processing of Motor Control Blocks (MC-2,

MC-2E, MC-3, and MC-3E)
The Motor Control Blocks, execute special output processing different from other function blocks.
This section describes the output processing specific to Motor Control Blocks.
• Set manipulated output value MV
• Output Signal Conversion
• Inching Output
• MV Action on Setting CSV (*1)
• Remote/Local Input
• Answerback Tracking
• Interlock Check
• Off-service
• Output Tracking
*1: This MV action can be set only in the FFCS series, KFCS2, and LFCS2.
Set the Manipulated Output Value (MV) of Motor

Control Blocks (MC-2, MC-2E, MC-3, and MC-3E)
The setting method of the manipulated output value (MV), which is the target of the output
processing, varies depending on the block mode in the Motor Control Blocks.
In the Manual Mode (CRT Manual)

When the block mode is manual (MAN) mode (CRT manual), the manipulated output value (MV) is
set by the following method.
• The manipulated output value (MV) is set by the operator’s operation on the operation and
monitoring function.
• For the inching output, the manipulated output value (MV) is automatically set based on the
setpoint value (SV) set by the operator on the operation and monitoring function.
In the Automatic Mode (Sequence Automatic 1) or Cascade

Mode (Sequence Automatic 2)
When the block mode is in the automatic (AUT) mode (sequence automatic 1) or cascade (CAS)
mode (sequence automatic 2), the sequence setpoint value (CSV) set by another function block such
as a Sequence Control Block or Calculation Block is set as the manipulated output value (MV).
In the Remote Output Mode (Computer Remote)

When the block mode is in the remote output (ROUT) mode (computer remote), a remote
manipulated output value (RSV) set by an upper-level computer is set as the manipulated output
value (MV).
When the block mode is neither remote output (ROUT) or out of service (O/S) , a tracking is
executed so that the remote setpoint value (RSV) becomes the manipulated output value (MV).
In the Tracking Mode (On-Site Manual)
When the block mode is in the tracking (TRK) mode (on-site manual), the manipulated output value
(MV) is set by the following method:
• When the answer back tracking is set to “YES”
The answer back input value (PV) is set as the manipulated output value (MV).
• When the answer back tracking is “NO”
If the output signal conversion is “2-position status output” or “3-position status output,” the
status of the output destination (contact output or internal switch) is read back and the value
after the reverse-conversion of the output signal is set as the manipulated output value (MV).
If the output signal conversion is “2-position pulsive output” or “3-position pulsive output,” the
previous value is retained as the manipulated output value (MV).
Output Signal Conversion of Motor Control Blocks (MC-

2, MC-2E, MC-3, and MC-3E)
The motor control blocks execute the following output processing.
Table 1.18.3-1 Output Processing of the Motor Control Block (MC-2, MC-2E, MC-3, and MC-3E)
Output signal conversion Number of output Output action direction

specification contacts specification
2-position status output 1 Yes
3-position status output 2 Yes
2-position pulsive output 2 No
3-position pulsive output 3 No
The output signal conversion types and output action directions are described.
Output Signal Conversion Types

▼ Output Signal Conversion
The type of output signal conversion can be set with the Function Block Detail Builder.
• Output Signal Conversion
For a two-position motor control block (MC-2) and an enhanced two-position motor control block
(MC-2E), select from “2-position Status Output” and “2-position Pulsive Output.”
Default is “2-position Status Output.”
For a three-position motor control block (MC-3) and an enhanced three-position motor control
block (MC-3E), select from “3-position Status Output” and “3-position Pulsive Output.”
Default is “3-position Status Output.”
Output Action Direction

When “2-position Status Output” or “3-position Status Output” is specified, the “Output Action
Direction” can be defined too.
The output action direction can be set with the Function Block Detail Builder.
• Output Action Direction
For a MC-2 block and a MC-3 block, select from “Direct,” “Reverse” “Inverted connect direct
action” and “Inverted connect reversed action.”
For a MC-2E block and a MC-3E block, select from “Direct,” “Reverse.”
Default is “Direct.”
SEE For more information about the output action direction for the motor control blocks, refer to:
ALSO " Output Signal Conversion of 2-Position Status Output" in 1.18.3, "Output Processing of
Motor Control Blocks (MC-2, MC-2E, MC-3, and MC-3E)"
" Output Signal Conversion of 3-Position Status Output" in 1.18.3, "Output Processing of
Motor Control Blocks (MC-2, MC-2E, MC-3, and MC-3E)"
Pulse Width Time

▼ MC Block - Pulse Width
The time of ON for contact output for the converted signal of “2-position Pulsive Output” or “3-
position Pulsive Output” may be defined in each FCS.
Pulse width may be defined on the property sheet of the FCS.
Pulse Width: 1 to 100 Sec.
Default is 1 Sec.
TIP The actual duration of the ON state of the contact output will be one second longer than the
value set on the FCS property sheet. Therefore, it is ensured that the contact stays ON at least for
the set time even if an event that affects the timing of function block operation such as high CPU
load.
SEE For more information about pulsive width of motor control blocks, refer to:
ALSO " Output Signal Conversion of the 2-Position Pulsive Output" in 1.18.3, "Output Processing
of Motor Control Blocks (MC-2, MC-2E, MC-3, and MC-3E)"
" Output Signal Conversion of the 3-Position Pulsive Output" in 1.18.3, "Output Processing
of Motor Control Blocks (MC-2, MC-2E, MC-3, and MC-3E)"
Output Signal Conversion of 2-Position Status Output

The relationship between the manipulated output value (MV) and the ON/OFF status in the 2-
position status output is as follows:
Table 1.18.3-2 The Manipulated Output Value and the Contact Output Status of the 2-Position
Status Output
Contact output status

Output signal conversion specification Output action direction MV
n (*1) n+1 (*1) n+2 (*1)
2 ON
Direct action
0 OFF
2-position status output
0 ON
Reverse action
2 OFF
*1: “n” in the table indicates the element number specified to connect to OUT terminal of MC-2 and MC-3
blocks, or the OUT1 terminal of MC-2E and MC-3E blocks. “n+1” and “n+2” indicates the element
number succeeding the element number “n” that is specified to connect to OUT terminal or the element
number specified to connect to OUT2 and OUT3 terminal of MC-2E and MC-3E blocks.
The action of 2-position status output is shown as follows:
Figure 1.18.3-1 Action of the 2-Position Status Output
In the 2-position status output, the state of MV=1 is the same as the state of MV=2.
Output Signal Conversion of 3-Position Status Output

position status output is as follows:
Status Output

Output signal conversion
Output action MV n n+1 n+2
specification
(*1) (*1) (*1)
2 ON OFF —
Direct action 1 OFF OFF —
0 OFF ON —
2 OFF ON —
Reverse action 1 ON ON —
0 ON OFF —
3-position status output
2 OFF ON —
Inverted connection Direct action
1 OFF OFF —
(*2)
0 ON OFF —
2 ON OFF —
Inverted connection Reversed
1 ON ON —
action (*2)
0 OFF ON —
*2: Inverted connection is not available for MC-2E and MC-3E blocks.
The action of 3-position status output is shown as follows:
Figure 1.18.3-2 Action of the 3-Position Status Output
Output Signal Conversion of the 2-Position Pulsive

Output
position pulsive output is as follows:
Pulsive Output

n (*1) n+1 (*1) n+2 (*1)
2 ON OFF
2-position pulsive output ------
0 OFF ON
The action of an 2-position pulsive output is shown as follows:
Figure 1.18.3-3 Action of the 2-Position Pulsive Output
For pulsive output signal, the time of ON is set in the column of “MC block pulse width” on FCS
folder. The default is 1 sec.
Output Signal Conversion of the 3-Position Pulsive
Output
position pulsive output is as follows:
Pulsive Output

n (*1) n+1 (*1) n+2 (*1)
2 ON OFF OFF
3-position pulsive output ------ 1 OFF OFF ON
0 OFF ON OFF
The action of an 3-position pulsive output is shown as follows:
Figure 1.18.3-4 Action of the 3-Position Pulsive Output
For pulsive output signal, the time of ON is set in the column of “MC block pulse width” on FCS
folder. The default is 1 sec.
Inching Output
▼ Inching/Full-Stroke Time Width
Inching output is a function which drives or stops the motor for a specified duration according to the
manual operation of the operator using the operation and monitoring function.
The inching output is initiated when change the inching output setpoint value (SV). The final control
element is manipulated for a duration (Tout) proportional to the change in SV (ΔSV) from 0, 50 or
100 % shown below.
After Tout has elapsed, the inching output setpoint value (SV) follows the manipulated output value
(MV) prior to the modification. The inching operation is available only in manual (MAN) mode.
When the inching operation is not executed, the inching output setpoint value (SV) follows the
Table 1.18.3-6 The Relationship Between the Manipulated Output Value (MV) and the Inching
Output Setpoint Value (SV)
MV 0 1 2
SV 0% 50 % 100 %
Tout can be obtained by the following expression:
Tout : Inching output action time (second)

Tf : Inching full stroke time width (second)
ΔSV : Change in SV (%) = SV value after change - SV value before change
The “Inching/Full-stroke Time Width” indicates the time span for the operation of the final control
element when the inching output setpoint value (SV) is changed by 100 %.
The inching/full-stroke time width is set by the Function Block Detail Builder.
• Inching/Full-stroke Time Width
0 to 10000.0 seconds. For the pulsive output, however, the output within one second is invalid.
Default is 0 second.
Action of the Inching Output

The action of the inching output is explained for each type of the output signal conversion. In the
explanation, the full stroke time width is assumed to be 100 seconds.
In each output signal conversion, the inching operation is aborted when the setting of the
manipulated output value (MV) is modified during the operation.
Inching Output of a 2-Position Status Output

The output reverses from ON to OFF, or from OFF to ON only during Tout time.
The inching output only reverses the contact output to the OUT terminal connection destination; the
manipulated output value (MV) remains unchanged.
Figure 1.18.3-5 Inching Output of a 2-Position Status Output (When the Full Stroke Time Width
is 100 Seconds)
Inching Output of a 3-Position Status Output

• When MV=2, the output of the contact 1 is reversed for duration of Tout.
• When MV=0, the output of the contact 2 is reversed for duration of Tout.
• When MV=1, the output of the contact 1 is reversed for duration of Tout if the change in inching
output setpoint value (ΔSV) is positive. The output of the contact 2 is reversed for duration of
Tout if the inching output setpoint value (ΔSV) is negative.
The inching output only reverses the contact output, the manipulated output value (MV) remains
unchanged.
Figure 1.18.3-6 Inching Output of a 3-Position Status Output (When the Full Stroke Time Width
is 100 Seconds)
Inching Output of a 2-Position Pulsive Output

• When MV=2, performs pulsive output from the contact 2, then performs again from contact 1
after Tout has elapsed.
The inching output only executes the pulsive output from the contact and the manipulated output
value (MV) is not changed.
Figure 1.18.3-7 Inching Output of a 2-Position Pulsive Output (When the Full Stroke Time Width
is 100 Seconds)
Inching Output of a 3-Position Pulsive Output

• When MV=1, if the sign for the change in inching output setpoint (ΔSV) is positive, pulsive output
is performed from contact 1, then again from contact 3 after Tout has elapsed. If the sign for the
change in inching output setpoint (ΔSV) is negative, pulsive output is performed from contact 2,
then again from contact 3 after Tout has elapsed.
The inching output only executes the pulsive output from the contact and the manipulated output
value (MV) is not changed.
Figure 1.18.3-8 Inching Output of a 3-Position Pulsive Output (When the Full Stroke Time Width
is 100 Seconds)
MV Action on Setting CSV: FFCS Series/KFCS2/LFCS2

▼ MV of Switch Instrument/MC Instrument follows its CSV change
When CSV is changed by a sequence table or by a function block, whether the MV of motor
controller block to instantaneously follow the CSV change or to follow the change at the next
execution time can be specified.
On the Constant tab of FCS Properties sheet, if the option of [MV of Switch Instrument/MC
Instrument follows its CSV change] is checked, the MV will follow the CSV right after the CSV is
changed. Otherwise, the MV will follow the CSV at the next execution time of the motor controller
block. By default, this option is not checked.
Moreover, the option is valid not only for changing the CSV by sequence table blocks, but also valid
for changing the CSV by the logic chart blocks, calculation blocks as well as manipulating the CSV on
an HIS.
• When the Option is Checked
When the CSV is set from a sequence table, the MV of the motor controller block will
instantaneously follow the CSV change.
For example, if the CSV of an MC-2 motor controller block with two-position status outputs is set
to CSV=2, the direct MV action may be illustrated as follows:
1.18.3 Output Processing of Motor Control Blocks (MC-2, MC-2E, MC-3, and MC... Page 10 of 15
Figure 1.18.3-9 CSV, MV and Actual Output when the Option is Checked: FFCS
Series/KFCS2/LFCS2
• When the Option is Unchecked

When the CSV is set from a sequence table, the MV of the motor controller block will follow the
CSV change at the next execution time of the motor controller block.
For example, if the CSV of an MC-2 motor controller block with two-position status outputs is set
to CSV=2, the direct MV action may be illustrated as follows:
Figure 1.18.3-10 CSV, MV and Actual Output when the Option is Unchecked: FFCS
Series/KFCS2/LFCS2
Remote/Local Input
The remote/local input function reads the status of on-site push button switches installed near the
equipment such as valves and pumps, and to prevent the output from the motor control block since
the on-site operation is given higher priority when the system is in the local mode.
The remote/local input signal is fed through the TSI terminal of the motor control block. In addition
to the contact input, internal switches can be used as signal input too. The remote/local input signal
is stored in the tracking switch (TSW).
Table 1.18.3-7 Relationship Between the Remote/Local Input Signal and the Tracking Switch
Input signal (*1) Remote/Local TSW Mode

OFF (0) Remote 0 Mode except for TRK
ON (1) Local 1 TRK

*1: Input signal in () indicates the signal from an internal switch.
When the TSI terminal is not connected, the data can be set directly to the tracking switch (TSW)
from other function blocks. When TSW is 1, the block mode is set to the on-site manual mode
(TRK). When TSW becomes 0, the mode returns to the normal mode (MAN, AUT, CAS or ROUT)
from the on-site manual (TRK) mode.
Remote/Local Input Function in On-Site Manual (TRK) Mode

The action of the remote/local input function in the on-site manual (TRK) mode is as follows:
• The output action (output signal conversion) is not executed. But the output action is carried out
when the answer back tracking is defined in the status output.
• The interlock check is not performed.
• The answer back check is not performed because the answer back error alarm (ANS+, ANS-) is
reset.
Answerback Tracking
▼ Answerback Tracking
The answerback tracking is to force the manipulated output value (MV) to match the answerback
input value (PV), when the block is in on-site manual mode (TRK) or when the bypass command
switch (BPSW) is 4 (out-of-service command).
The answerback tracking is defined in the Function Block Detail Builder.
Answerback Tracking: Select either “Yes” or “No.”
Default is “Yes.”
Answerback Error Triggered Fallback

▼ Fallback Operation on the Abnormal Answerback
Answerback Error Triggered Fallback is a function that forces the block into MAN mode and forces
the block’s manipulated output (MV) into a designated value whenever answerback signals indicate
an error.
Triggers of Fallback may be selected from one of the three errors shown as below.
• Answerback error occurred due to abnormality of ON (ANS+) signal
• Answerback error occurred due to abnormality of OFF (ANS-) signal
• Answerback error occurred due to abnormality of either ON (ANS+) or OFF (ANS-) signal.
When fallback is activated, the manipulated output (MV) will be forced to the output position
designated in the builder item [Output when interlock status is true]. At the same time, the interlock
alarm (INT) will be initiated right after the output (MV) changed to the designated position.
Once the manipulated output (MV) is manually changed, the interlock alarm (INT) will be
deactivated.
If answerback check is not activated, the fallback will not be triggered by answerback error. The
interlock alarm (INT) subsequent to the fallback can be dissolved when any of the following
conditions establishes.
• When block mode changes to Tracking (TRK) mode.
• When answerback bypass is activated (BPSW=1 or 3).
• When the answerback input signal (PV) is switched to calibration (CAL) mode.
• When off service is activated (BPSW=4).

If the block is in simulation (SIM) status, the fallback will not be triggered by answerback error. The
interlock alarm (INT) subsequent to the fallback will be dissolved right after the block changes
simulation (SIM) status.
When a 2-position status output encounters the answerback error triggered fallback, its behavior is
shown in the following illustrate.
Figure 1.18.3-11 Answerback Error Triggered Fallback (2-Position Status Output)
When a 3-position status output encounters the answerback error triggered fallback, its behavior is
shown in the following illustrate.
Figure 1.18.3-12 Answerback Error Triggered Fallback (3-Position Status Output)
SEE For more information about interlock check functions, refer to:
ALSO
" Interlock Check" in 1.18.3, "Output Processing of Motor Control Blocks (MC-2, MC-2E, MC-
3, and MC-3E)"
For more information about interlock alarm (INT), refer to:
" Interlock Alarm Check" in 1.18.4, "Alarm Processing of Motor Control Blocks (MC-2, MC-
2E, MC-3, and MC-3E)"
Settings Answerback Triggers for Fallback

Setting the answerback triggers for fallback may be performed on the Function Block Detail Builder.
• Fallback operation on the abnormal answerback:
Select from “NONE,” “ANS+,” “ANS-” and “BOTH.”
The default setting is “NONE.”
Interlock Check
The interlock check is used to place the motor control blocks in the interlock state according to the
operation interlock input signal that is input to the IL terminal of the motor control blocks.
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)
Interlock Input Signal

▼ Interlock Input Signal Direction
The “Interlock Input Signal Direction” determines whether the interlock state is activated by ON or
OFF of the operation interlock input signal. An internal switch or contact output can be used as the
operation interlock input signal in addition to the contact input.
The “Interlock Input Signal Direction” may be defined on the Function Block Detail Builder.
Interlock Input Signal Direction: Choose [Direct] or [Reverse]
The default is [Direct].
If [Direct] is selected, the interlock status is activated when the interlock signal is ON.
If [Reverse] is selected, the interlock status is activated when the interlock signal is OFF.
When the signal connected to IL terminal becomes abnormal (i.e., data status
becomes BAD), the block will be released from interlocked status regardless if
the action is Direct or Reverse.
Output when Interlock Status is True

▼ Output when interlock status is true, Modify pulsive output when interlock status true, Hold output
when interlocked
In the interlock state, the predefined output action can be executed.
The “Output when Interlock Status is True” may be defined on the Function Block Detail Builder.
For a two-position motor control block (MC-2) and an enhanced twoposition motor control block (MC-
2E):
Output when Interlock Status is True: Choose [Open] or [Close]
The default is [Open].
For a three-position motor control block (MC-3) and an enhanced three-position motor control block
(MC-3E):
Output when Interlock Status is True: Choose [Open], [Close] or [Stop]
The default is [Close].
When the interlock state is activated, the change of the output is monitored and the interlock alarm
(INT) will be activated at the occurrence of output change by the output action of predefined
interlock state. When the interlock is released, the interlock alarm is deactivated at the same time.
The action and interlock alarm (INT) initiated by establishment of interlock conditions will be
activated when answerback error triggered fallback takes place.
In the interlock state, the output is switched to the status output even if it is pulsive output.
However, when “Direct Output” is specified in “Modify Pulsive Output when Interlock Status True” in
the Function Block Detail Builder, the pulsive output is retained. This option can be set on the
Function Block Detail Builder.
Modify Pulsive Output when Interlock Status True: Choose [Direct Output] or [Status Output]
The default is [Status Output].
When the motor control block is interlocked, the previous manipulated output value (MV) can be
held. This option can be set on the Function Block Detail Builder.
Hold Output when Interlocked : Choose [Valid] or [Invalid]
The default is [Invalid].
If [Valid] is selected, the block will hold the previous output when interlocked.
If [Invalid] is selected, the block will change the output according to the failsafe output specified in
the setting of [Output when interlock status is true].
The “Hold Output When Interlocked” option can be set to the following motor control blocks:
• MC-2 and MC-3 blocks in FFCS series, KFCS2, and LFCS2.
• MC-2E and MC-3E blocks in FCSs except PFCS.
If the “Hold Output When Interlocked” option is selected, note the followings:
• When the motor control block falls back due to answerback error or
thermo-trip alarm occurrence, the block cannot hold the previous output
changes to the failsafe output specified in the setting item of [Output
when interlock status is true].
• When the block is interlocked, inching action will result in an error and
triggers an error message.
• When the block is holding the previous manipulated output value (MV), if
the operator changes the MV, the MV will revert to the held value at the
next scan.
• When the block is holding the previous manipulated output value (MV), if
the block is changed to local mode, the held MV will no longer valid since
the local operation takes higher preference.
• When the block is interlocked and holds the previous manipulated output
value (MV), the occurred alarm for indicating the interlocked (INT) status will
be kept alive.
SEE For more information about the behavior of the fallback triggered by answerback errors, refer to:
ALSO " Answerback Error Triggered Fallback" in 1.18.3, "Output Processing of Motor Control
Blocks (MC-2, MC-2E, MC-3, and MC-3E)"
Off-Service Function
The off-service is used to stop the output from the MC-2 or MC-3 block via a command from the
bypass command switch (BPSW).
Off-service supports the following processes.
• The off-service is activated by putting the bypass command switch (BPSW) to 4. When the off-
service command is issued, the block mode is changed to the manual (MAN) mode and the block
status becomes OFF.
• No output action (output signal conversion) is executed in the off-service state.
• The answerback tracking operates in the off-service state.
Output Tracking – MC-2E, MC-3E

Output tracking is an output processing of MC-2E and MC-3E blocks.
The output tracking forces the manipulated output value (MV) to match value of the connected
destination.
If a MC-2E or MC-3E block is connected in a cascade loop with FF faceplate block or fieldbus
function block, the MC-2E or MC-3E block starts output tracking when the cascade loop is
disconnected and its block changes to IMAN mode.
Output tracking starts under the following circumstances:
• When the block becomes IMAN mode.
• When the block changes from service off (O/S) mode to MAN, AUT or CAS mode.
• When the I/O module connected to the output terminals recovered from failure.
• When the cascade loop is disconnected.
TIP The output tracking of MC-2 or MC-3 block starts under the following circumstances:
• When the block becomes IMAN mode.
• When the block changes from service off (O/S) mode to MAN, AUT or CAS mode.
• When the I/O module connected to the output terminals recovers from failure.
1.18.4 Alarm Processing of Motor Control Blocks (MC-2, MC-2E, MC-3, and MC-3E) Page 1 of 3
1.18.4 Alarm Processing of Motor Control Blocks (MC-2,

MC-2E, MC-3, and MC-3E)
The following lists the alarm checks performed by the motor control blocks which are specific to
these four function blocks.
• Feedback input high and low limit alarm check
• Thermal trip alarm check
• Interlock alarm check
• Answerback unset alarm check
• Answerback error alarm check
Feedback Input High Limit/Low Limit Alarm Check

▼ High/Low Limit Alarm
The input high limit and low limit alarm check in the motor control blocks is used for checking the
feedback input.
By means of this feedback input high limit and low limit alarm check, when the feedback input value
(FV) exceeds the feedback input high limit alarm setpoint (PH), a feedback input high limit alarm
(HI) is generated. Also, when the feedback input value (FV) drops below the feedback input low limit
alarm setpoint (PL), a feedback input low limit alarm (LO) is generated.
When an alarm has occurred, if the feedback input value (FV) drops lower than the value of the
feedback input high limit alarm setpoint (PH) minus the input high and low limit alarm hysteresis
(HYS), the feedback input high limit alarm (HI) is returned to normal state. Also, if the feedback
input value (FV) exceeds the feedback input low limit alarm setpoint (PL) plus the input high and low
limit alarm hysteresis (HYS), the feedback input low limit alarm (LO) is returned to normal state.
Figure 1.18.4-1 Actions of the Feedback Input High and Low Limit Alarm Check
Moreover, when the block is in the status that the answerback check is masked (ANCK), the
feedback input high-limit alarm (HI) and the feedback input low-limit alarm (LO) are also masked.
Feedback Input High Limit/Low Limit Alarm Settings

Setting of the feedback input high limit/low limit alarm setpoint (PH, PL) is done using the following
setting parameters:
• Feedback input high limit alarm setpoint (PH)

Engineering unit data within the FV scale range
The default is the FV scale high limit value.
• Feedback input low limit alarm setpoint (PL)
Engineering unit data within the FV scale range
The default is the FV scale low limit value.
The hysteresis is set with the Function Block Detail Builder.
Hysteresis : Engineering unit data within the range of 0 to FV scale span, or percentage data for
the FV scale span
The default is 2.0 %.
Thermal Trip Alarm Check

The thermal trip alarm check is a function that determines whether a thermal trip signal indicating a
motor overload condition was input to the motor control block.
If it is determined that when the signal for the thermal trip signal input terminal (TT) turns on in the
motor control block, a thermal trip alarm is generated. If the signal from the thermal trip signal input
terminal (TT) turns off while the alarm is being generated, the alarm is returned to normal state.
The output action of the motor control blocks when there is a thermal trip alarm is the same as
when the block is showing an interlock (LOCK) state.
When the signal connected to TT terminal becomes abnormal (i.e., data

status becomes BAD), if the block is in alarm status, the alarm status of the
block will be released.
SEE For more information about the interlock status of the motor control blocks, refer to:
ALSO " Interlock Check" in 1.18.3, "Output Processing of Motor Control Blocks (MC-2, MC-2E, MC-
3, and MC-3E)"
Interlock Alarm Check

For MC-2 or MC-3 Motor Controller blocks, when the Interlock Alarm Check function detects the
establishment of interlock condition, or fallback action is activated by answerback errors, the
manipulated output (MV) will be forced to the designated value predefined in the builder item
[Output when interlock status is true]. At the same time the Interlock Alarm (INT) will be initiated.
The interlock check triggered interlock alarm (INT) will be deactivated whenever the interlock
condition is dissolved.
The interlock alarm (INT) initiated by Answerback Error Triggered Fallback will become deactivated
once the manipulated output value (MV) is manually changed.
SEE For more information about the answerback error triggered fallback, refer to:
ALSO " Answerback Error Triggered Fallback" in 1.18.3, "Output Processing of Motor Control
Blocks (MC-2, MC-2E, MC-3, and MC-3E)"
Answer-Back Inconsistency Alarm Check

The answerback inconsistency alarm check is a function that determines whether two answerback
input signals indicate full-open and full-close simultaneously.
If it is determined that two answerback input signals indicated full-open and full-close
simultaneously, an answerback inconsistency alarm (PERR) occurs.
If the two answer-back input signals stop indicating full-open and full-close simultaneously while the
alarm is being generated, the alarm is returned to normal state.
Answer-Back Inconsistency Alarm Mask – MC-2E, MC-3E

▼ Inhibit Answerback Error Alarm
When IN1 terminal and the IN2 terminal of M2-CE or M3-CE block are connected to FF faceplate
blocks or fieldbus function blocks, the simultaneity of the two inputs is not guaranteed. If the both
the ON and OFF answerbacks exist at the same time even for a very short time, the Answer-Back
Inconsistency Alarm (PERR) may occur. To prevent the alarm occurring under this circumstance, the
alarm can be masked by stop the alarm check for a certain time period (Mask Time) after the
manipulated output (MV) changes. The data item MTM can be used for setting this answer-back
inconsistency alarm mask time.
For MC-2E and MC-3E block, the answer-back inconsistency alarm mask can be set on the function
block detail builder.
Inhibit Answerback Error Alarm: Choose [No] or [Yes].
The default setting is [Yes].
TIP Regarding to answer-backs of MC-2 and MC-3 blocks, since the simultaneity of the two inputs are
guaranteed, the Answer-Back Inconsistency Alarm Mask becomes unnecessary.
Answer Back Error Alarm Check

The answerback error alarm check is a function that determines if the manipulated output value and
the answerback input value do not match.
If it is determined that the manipulated output value and the answerback input value do not match
when the manipulated output value (MV) is 2, the ON side answerback error alarm (ANS+) occurs. If
the manipulated output value and the answerback input value do not match when the manipulated
output value (MV) is 0, the OFF side answerback error alarm (ANS-) occurs.
If the manipulated output value and the answer-back input value match while the alarm is being
generated, the alarm is returned to normal state.
1.19 Ratio Set Block (RATIO) Page 1 of 14
1.19 Ratio Set Block (RATIO)

The Ratio Set Block (RATIO) outputs its manipulated output value (MV) follows the change of
process variable (PV) times the ratio set value. This block is used to set a specific ratio at which two
controlled variables are maintained.
Ratio Set Block (RATIO)

▼ Connection
The RATIO Block defines a ratio for control of two control amounts. The figure below shows the
RATIO Block diagram.
The figure below shows the function block diagram of Ratio Set Block (RATIO):
Figure 1.19-1 Function Block Diagram of Ratio Set Block (RATIO)
The figure below shows the internal control computation processing of the Ratio Set Block (RATIO):
Figure 1.19-2 Control Computation Processing of Ratio Set Block (RATIO)
The figure below shows an example of using the Ratio Set Block (RATIO):
Figure 1.19-3 Example of Using Ratio Set Block (RATIO)
In this control loop, the flowrates F1 and F2 are maintained in a specific ratio r, by setting the value
of F1 multiplied by r, or rF1, as the setpoint value of F2.
the Ratio Set Block (RATIO):
Table 1.19-1 Connection Methods and Connected destinations of the I/O Terminals of Ratio Set
Block (RATIO)

Measurement
IN x x x x
input
Manipulated
OUT x x x x
output
Tracking signal
TIN x Δ x x
input
Tracking SW
TSI x Δ x x x
input
Interlock SW
INT x Δ x x x
input
link block (ADL).
Function of Ratio Set Block (RATIO)

The RATIO block performs input processing, control computation processing, output processing,
The only processing timing available for the RATIO block is a periodic startup. Selections available
ALSO processing possible for the RATIO block, refer to:
Control Computation Processing of Ratio Set Block (RATIO)

The table below shows the control computation processing functions of the Ratio Set Block (RATIO):
Table 1.19-2 Control Computation Processing Functions of Ratio Set Block (RATIO)
Control computation
Description
processing
Obtains a calculated output value (CALCn) by multiplying the process variable
Ratio computation
(PV) by the effective ratio setpoint value (SVe).
Converts the manipulated output change (ΔMV) during each control period to
Control output action an actual manipulated output value (MV). The available control output actions
are of “positional type” only.
remaining one.
Constantly updates the ratio setpoint value (SV) with a value calculated
backwards from the current manipulated output value (MV), when ratio
Ratio tracking
computation is stopped. This prevents the manipulated output value from
Bumpless changing abruptly.
switching Causes the change in the effective ratio setpoint value (SVe) to gradually
Ratio setpoint
approach the newratio setpoint value, when the ratio setpoint value (SV) has
value ramp
changed abruptly. This prevents the manipulated output value from changing
action
abruptly.
Changes the block mode to IMAN to temporarily suspend the control action.
Initialization manual This action takes place when the initialization manual condition becomes
satisfied.
Temporarily suspends the control action while maintaining the current block
Control hold
mode. During control hold, the output action is performed normally.
MAN fallback
CAS mode, so that the control action is continued using values set by the
AUT fallback
operator. This action takes place when the AUT fallback condition becomes
satisfied.
Temporarily suspends actions in the RCAS or ROUT mode and switches to the
Computer failure
computer backup mode.
Block mode change interlock while disabling the stopped function blocks from changing to the automatic
operating mode.
Ratio Computation
In ratio computation, the following computation processing is performed to obtain a calculated
output value (CALC) by multiplying the process variable (PV) by the effective ratio setpoint value
(SVe):
CALCn=KR • SVe • PVn+BIAS (1)
CALCn : Current calculated output value
PVn : Current process variable
SVe : Effective ratio setpoint value
KR : Ratio gain
BIAS : Bias value
The effective ratio setpoint value (SVe) is a ratio setpoint value (SV) that has been processed via the
setpoint value ramp action to be used for bumpless switching of block modes.
In any automatic operating mode (AUT, CAS or RCAS), the calculated output value (CALC) receives
output signal processing and is set as the manipulated output value (MV).
Setpoint Value (SV) Range

▼ SV Range
Use the Function Block Detail Builder to set the ratio setpoint value (SV) range:
• SV range high limit
each.
The default is 4.0.
• SV range low limit
each.
The default is 0.0.
Ratio Gain
▼ Ratio Gain
Use the Function Block Detail Builder to set the ratio gain:
Ratio Specify a numeric value of 7 digits or less, where the sign and decimal point occupy one
Gain: digit each.
The default is 1.0.
The expressions to obtain the ratio gain are shown below:
• Example 1
The figure below shows an example of operating a flow ratio control system where the flowrates
3 3
F1 and F2 range from 0 to 100 m /h and from 0 to 30 m /h, respectively, by maintaining the
ratio r between 0.0 and 0.3:
Figure 1.19-4 Example of Flow Ratio Control
When the above conditions are applied to the computational expression (1), the flowrate F1,
target flowrate value of F2, and ratio r are represented by the process variable (PV), calculated
output value (CALC) and ratio setpoint value (SV), respectively.
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:
3
When r is 0.1 and F1 is 100 m /h, the target value of F2 is the product of 100 and 0.1, or 10
3
m /h. If this condition is applied to the computational expression (3), the following computational
expression is obtained:
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 calculated output value (CALCn) are
in the same unit and the effective ratio setpoint value (SVe) has no unit.
• Example 2
In the figure “Example of Flow Ratio Control,” assume that the flow ratio control system provides
3
the flowrates F1 and F2 that range from 0 to 300 m /h and from 0 to 100 ℓ/min., respectively,
and is operated at the ratio r of between 0.0 and 2.0 %.
When F1 is 0, the target value of F2 is 0. Thus, set the bias setpoint value (BIAS) to 0 and apply
the expression (3) in Example 1.
3
When the assumed setting of r is 1.0 % and F1 is 300 m /h, the target value of F2 is the product
3
of 300 and 1.0/100, or 3 m /h, which is then converted to 50 ℓ/min. When this is applied to the
expression (3), the following computational expression is obtained:
As values of the process variable (PV) and calculated output value (CALCn) are engineering 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).

to an actual manipulated output value (MV).
The control output actions available with the Ratio Set Block (RATIO) are of “positional type” only.
The calculated output value (CAL) is set as the manipulated output value (MV).

The setpoint value limiter function limits the setpoint value (SV) within the range between the
setpoint high limit (SVH) and setpoint low limit (SVL), recognizing values only inside this range as
valid.
ALSO " Setpoint Value Limiter" in 1.4, "Control Computation Processing Common to Controller
Blocks"

CSV, RSV). The figure below explains the relationships among the setpoint value (SV), cascade
block.

(RSV).

Causes the setpoint value (SV) and remote setpoint value (RSV) to agree with the cascade setpoint
value (CSV).

Causes the setpoint value (SV) and cascade setpoint value (CSV) to agree with the remote setpoint
value (RSV).
Bumpless Switching
output value (MV) downstream in cascade without causing the manipulated output value (MV) to
change abruptly (i.e., bumpless change).
The functions of bumpless switching available with the Ratio Set Block (RATIO) include the following:
• Ratio tracking
• Ratio setpoint value ramp action
Ratio Tracking
▼ Ratio Tracking
The ratio tracking function sets as a ratio setpoint value (SV) the value calculated backwards from
the manipulated output value (MV), when ratio computation is stopped.
Ratio tracking enables bumpless switching of block modes from manual (MAN) to automatic (AUT).
Ratio tracking is executed in the following conditions:

• In the manual (MAN) mode
• In the initialization manual (IMAN) mode (e.g., when cascade connection to a downstream loop
becomes open)
Use the Function Block Detail Builder to set ratio tracking.
• Ratio tracking:
Set “Yes” or “No” for each condition of MAN, AUT plus CND or CAS plus CND.
The table below shows the default settings of ratio tracking:
Table 1.19-3 Default Settings of Ratio Tracking
Specification condition (status) (*1) Default

MAN Ratio tracking disable.
AUT plus CND Ratio tracking disable.
CAS plus CND Ratio tracking disable.
*1: The statuses of MAN, AUT and CAS include remote backup modes, such as AUT (ROUT) and AUT
(RCAS).
Ratio Setpoint Value Ramp Action

The ratio setpoint value tracking action executes bumpless switching in place of ratio tracking,
when “No” is specified for ratio tracking.
The ratio setpoint value ramp action limits the change in the effective ratio setpoint value (SVe)
during each scan period to be equal to or less than the ramp constant (RP), when changes occur in
the ratio setpoint value (SV).
When the block mode changes from manual (MAN) to automatic (AUT), an effective ratio setpoint
value (SVe) is calculated backwards from the manipulated output value (MV), and the obtained value
is set as the initial effective ratio setpoint value (SVe). Therefore, the same actions take place when
the ratio setpoint value (SV) changes, thus prevent the manipulated output value (MV) from
changing abruptly when the block mode changes.
The figure below shows an example of the ratio setpoint value ramp action.
Figure 1.19-6 Example of the Ratio Setpoint Value Ramp Action
Set the ramp constant from operation and monitoring functions as a set parameter.
Ramp constant (RP): Engineering unit data within the SV scale span range.
When “Yes” is specified for ratio tracking, the ratio setpoint value ramp action will not be executed
even when the block mode is changed from manual (MAN) to automatic (AUT).

manual (IMAN).
Because the initialization manual action causes the manipulated output value (MV) to track the value
at the connected destination, even when the initialization manual (IMAN) mode changes to manual
(MAN), the initialization manual (IMAN) mode will override the manual (MAN) mode. Therefore, no
actions in the manual (MAN) mode will take place.
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)
AUT
The initialization manual condition establishes in the following situation:
• When the data status at the connected destination of the manipulated output value (MV) is
conditional (CND) (i.e., the cascade connection is open).
91) and the connection is switched off. (i.e., the cascade connection is open).
or output open alarm has occurred in the module.
Control Hold
operation (AUT, CAS, or RCAS):
MAN Fallback
established.

state.

AUT→MAN
• When the data status of the process variable (PV) is invalid (BAD) or calibration (CAL). However,
the MAN fallback condition will not be established when the block mode is remote output (ROUT)
excluding any of the compound modes during computer backup.
initial cold start.
points connected to the module has been changed via maintenance.
AUT Fallback
The AUT fallback is an error processing function that switches the block mode from cascade (CAS) to
automatic (AUT) when the AUT fallback condition is established, and switches the control action to
the one that uses values set by the operator.

Changes the block mode from cascade (CAS) to automatic (AUT) to continue control using values
set by the operator.
Once the AUT fallback condition establishes, the block mode remains automatic (AUT) even when

The AUT fallback condition is used to change the function block mode from cascade (CAS) to
automatic (AUT) so that control can be continued using values set by the operator. When this
condition is established, it indicates that abnormality has been detected in the cascade setpoint
value (CSV) for some reason.
The following example shows when the AUT fallback condition establishes:
CAS→AUT
IMAN (CAS) →IMAN (AUT)
Use the Function Block Detail Builder to enable or disable the AUT fallback function.
The AUT fallback condition establishes when the AUT fallback is defined as “Yes” via the Function
Block Detail Builder and the data status of the cascade setpoint value (CSV) becomes invalid (BAD)
or communication error (NCOM).
Computer Fail
mode.

computer via control bus communication.
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
execution of the block mode change command (MAN, AUT, CAS and a remote mode (RCAS,
ROUT).

backup mode.
A backup switch (BSW) is provided in function blocks to define the remote cascade (RCAS) or
remote output (ROUT) mode. The status of this switch determines whether the computer has failed
or recovered. The value of the backup switch (BSW) can be set from a sequence table or other
function blocks.
The following example shows when the automatic (AUT) mode has been specified for the computer
backup mode:
RCAS
↓ Computer fails
AUT (RCAS)
RCAS
shown as follows:
AUT
↓ ROUT command
Setting Computer Backup Mode

Use the Function Block Detail Builder to set the computer backup mode for each function block.



• Any block mode change command to obtain an automatic operation state (AUT, CAS, RCAS or
ROUT mode) becomes invalid.

The block mode change interlock condition is established when the switch at the connected
destination of the interlock switch input terminal (INT) is turned ON as a result of continued
automatic operation becoming impossible due to an abnormality in the plant, etc.
Data Items - RATIO

Table 1.19-4 Data Items of Ratio Set Block (RATIO) (1/2)

Item Not (*1) (*2)
MODE Block mode x n/a O/S (MAN)
ALRM Alarm status - n/a NR
AFLS Alarm flashing status - n/a 0
Alarm detection
AF - n/a 0
specification
Alarm masking
AOFS - n/a 0
specification
RAW Raw input data - n/a
SV Ratio setpoint value Δ (*4) SV engineering unit value SSL
Cascade ratio setpoint Value in the same engineering
CSV x SSL
value unit as SV
Remote ratio setpoint Value in the same engineering
RSV Δ (*5) SSL
value unit as SV
Manipulated output
MV Δ (*6) MV engineering unit value MSL
value
RMV Δ (*7) MSL
CALC Calculated output value - MSL
unit as MV
HH x SL to SH SH
setpoint
LL x SL to SH SL
setpoint
High - limit alarm
PH x SL to SH SH
setpoint
Low - limit alarm
PL x SL to SH SL
setpoint
PVP Velocity-Reference - Value in the same engineering n/a
Sample unit as PV
-: Entry is not permitted.
Table 1.19-5 Data Items of Ratio Set Block (RATIO) (2/2)

Item Not (*1) (*2)
MH x MSL to MSH MSH
limit setpoint
ML x MSL to MSH MSL
limit setpoint
BIAS Bias value x ± (MSH - MSL) MSL
RP Ramp constant x 0 to (SSH - SSL) SSH - SSL
KR Ratio gain - n/a 1.000
value
UAID User application ID x n/a 0
Value in the same
SH PV scale high limit - n/a
Value in the same
SL PV scale low limit - n/a
-: Entry is not permitted.
SEE For more information about valid block modes of the RATIO block, refer to:
1.20 13-Zone Program Set Block (PG-L13) Page 1 of 10
1.20 13-Zone Program Set Block (PG-L13)

The 13-Zone Program Set Block (PG-L13) outputs the time function signals according to the
specified line segment graph against time-axis. Using the 13-Zone Program Set Block (PG-L13) in
combination with controller blocks enables program control of processes.
13-Zone Program Set Block (PG-L13)

▼ Connection
Specify the time function signal output of the 13-Zone Program Set Block (PG-L13) indicated in a
line-segment pattern. A program pattern of up to 166 hours or 166 minutes long can be set when
the time-axis setting unit is minute or second, respectively.
The figure below shows a function block diagram of 13-Zone Program Set Block (PG-L13):
Figure 1.20-1 Function Block Diagram of 13-Zone Program Set Block (PG-L13)
the 13-Zone Program Set Block (PG-L13):
Table 1.20-1 Connection Methods and Connected destinations of the I/O Terminals of 13-Zone
Program Set Block (PG-L13)

Manipulated
OUT x x x x
output
Annunciator
SUB x Δ x x x
output
Interlock SW
INT x Δ x x x
input
link block (ADL).
Function of 13-Zone Program Set Block (PG-L13)
The PG-L13 block performs control computation processing, output processing, and alarm
processing.
The only processing timing available for the PG-L13 block is a periodic startup. Moreover, only the
ALSO PG-L13 block, refer to:
Control Computation Processing of 13-Zone Program Set Block

(PG-L13)
The table below shows the control computation processing functions of the 13-Zone Program Set
Block (PG-L13):
Table 1.20-2 Control Computation Processing Functions of the 13-Zone Program Set Block (PG-
L13)
Control
processing
Line-segment Expresses a line-segment pattern of the program with line segments connecting up to
pattern signal 14 coordinates on a plane of time (X axis) and output (Y axis) including starting and
generation end points.
Calculates output values during each base period in accordance with the program set
Program set action
pattern, to obtain a calculated output value (CALC).
Saves or changes the calculated output value (CALC) and elapsed time (SV) at the end
Program end action
of the program.
Movement along the Moves along the time axis in accordance with the setting of set parameters (SV,
time axis ZONE).
Annunciator output Turns the annunciator message ON at the end of the program set action.
Converts the manipulated output change (ΔMV) during each control period to an actual
Control output
manipulated output value (MV). The available control output actions are of “positional
action
type” only.
when the block mode has been changed or when the manipulated output value (MV)
Bumpless switching
has been switched in a downstream block in cascade. The types of bumpless switching
include “bumpless start action.”
MAN fallback
Line-Segment Pattern Signal Generation

▼ Total Elapsed Time, Time Unit
The 13-Zone Program Set Block (PG-L13) performs control computation based on line-segment
pattern signal generation. The line-segment pattern used to set programs is expressed by line
segments that connect coordinate points of time and output including the starting and end points.
Line-Segment Pattern
The line-segment pattern used to set programs is expressed by line segments that connect up to 14
coordinate points on a plane of time (X axis) and output (Y axis) including the starting and end
points (maximum 13 line segments). The specifications of program-setting line-segment patterns are
shown below:
Number of Line-Segments: 1 to 13
Arbitrary line segments can be set on a coordinate plane of time (X axis) and output (Y axis).
If 0 is set to a segment on time axis (X02 to X14), the segment before this axis will be the end of
the time axis and the end of the line segments.
Zone Number (ZONE): 1 to 13

The space between the time-axis coordinates Xn and Xn+1 is called “Zone n.”
Setting Ranges
Line-segment patterns are set from operation and monitoring functions.
Time-axis breakpoint coordinate (X01 to X14): 0 to 9999 minutes, or 0 to 9999 seconds.
Output-axis breakpoint coordinate (Y01 to Y14): Engineering unit MV data.
Use the Function Block Detail Builder to set the time unit of time-axis breakpoint coordinates or total
running time of the program.
Time Unit: Select “seconds” or “minutes”
The default is “second.”
Total Elapsed Time: 0 to 10000
The default is 10000.
Program Set Action

In the automatic (AUT) or cascade (CAS) mode, the program set action calculates output values set
by the program set pattern during each basic scan period (1 second), and uses the obtained result
as a calculated output value (CALC). In the cascade (CAS) mode, the current position returns to the
start of the program set pattern when its end is reached, and output is repeated along the program
set pattern.
Figure 1.20-2 Program Set Pattern
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 : Maximum output value between the current elapsed time and
high limit (MH) intra-zone time high limit (PH)
Remaining intra-zone output : Minimum output value between the current elapsed time and
low limit (ML) intra-zone time low limit (PL)
In the automatic (AUT) or cascade (CAS) mode, output processing is performed to the calculated
output value (CALC) and the result is output as a manipulated output value (MV).
When the automatic (AUT) or cascade (CAS) mode is changed to manual (MAN) or initialization
manual (IMAN), the set action will stop. However, computation data, such as time and calculated
output values, will be stored.
If the block mode is changed back to automatic (AUT) or cascade (CAS), the program set action
resumes from the stored time.
If breakpoints are partially set in a reverse direction on the time axis (e.g., X01 > X02), the reversed
portion will be ignored. The figure below shows an example of the reversed portion on the time axis
being ignored:
Figure 1.20-3 An Instance of the Reversed Portion on the Time Axis
In this example, the original line-segment pattern is represented by a dotted line. However, the 13-
Zone Program Set Block (PG-L13) only recognizes the pattern represented by the solid line.
Program End Action

▼ When Program Exits
The actions performed in the automatic (AUT) mode at the end of the program include the following
two types:
In each action, the manipulated output value (MV) is caused to agree with the calculated output
value (CALC). Use the Function Block Detail Builder to set the program end action.
When program exits: Select “Holding PV” or “Quick Return.”
The default is “Holding PV.”
Final Value Holding Type

The calculated output value (CALC) and elapsed time (SV) at the end of the program are held and
the operating mode is switched to manual.
Quick Return Type

The current position returns to the beginning of the program pattern (time value=0), and the
operating mode is switched to manual after the calculated output value (CALC) and elapsed time
(SV) are changed to the values at the starting point.
Movement Precedence Along the Time Axis

The 13-Zone Program Set Block (PG-L13) moves along the time axis not only as time elapses but
also when data is set from operation and monitoring functions to the SV or ZONE set parameter or
when bumpless start is executed.
The three methods to force the block to move along the time axis have the following movement
precedence:
Movement precedence
1: Bumpless start action
2: Setting the zone number (ZONE)
3: Setting the elapsed time (SV)
Setting the Zone Number

When a value between 1 and 13 is set for the zone number (ZONE), actions will be continued from
the beginning of the zone that has been set. The zone number (ZONE) can be set in any block mode.
Setting the Elapsed Time (SV)

When any of the time data between the starting point and end point is set for the elapsed time (SV),
actions will continue from the point on time axis that has been set. The elapsed time (SV) can be set
in any block mode.
SEE For more information about the bumpless start action, refer to:
ALSO " Bumpless Switching" in 1.20, "13-Zone Program Set Block (PG-L13)"
Annunciator Output
When the software annunciator message (%AN) is specified for the output destination of the
annunciator output terminal (SUB), the annunciator message function will be turned ON at the end
of the program set action. However, the program set block only turns the function ON but does not
reset it. Use a sequence control block, or etc. to reset the alarm.

The control output action converts the manipulated output change (ΔMV) of each control period to
an actual manipulated output value (MV).
The control output action applied in the 13-Zone Program Set Block (PG-L13) is of “positional type”
only.
The calculated output value (CALC) is set as the manipulated output value (MV).
Bumpless Switching
▼ Bumpless Start
output value of the downstream block in the cascade loop without causing the manipulated output
value (MV) to change abruptly (i.e., bumpless change).
The type of bumpless switching action varies with the control output action and block mode status.
The type of bumpless switching performed by the 13-Zone Program Set Block (PG-L13) is “bumpless
start action.”
The bumpless start action prevents the value of the output destination from changing abruptly when
the program set action is started from zero elapsed time (SV) by changing the block mode from
manual (MAN) to automatic (AUT) or cascade (CAS).
When the program set action is started from zero elapsed time (SV), the position on time axis is fast-
forwarded until the calculated output value (CALC) agrees with the setpoint value of the output
destination. The range of program pattern in which this agreement point is searched is specified by
the bumpless start zone (ZSTR) and bumpless end zone (ZEND).
If no matching pattern is found in the search range, the program set action is started from the end
point of the last zone that exists inside the search range.
Use the Function Block Detail Builder to define the bumpless start action.
Bumpless Start: Select “Yes” or “No.”
The bumpless start zone (ZSTR) and bumpless end zone (ZEND) are set from operation and
monitoring functions as set parameters.
Bumpless start zone (ZSTR): Select a value between 1 and 13.
Bumpless end zone (ZEND): Select a value between 1 and 13.
Figure 1.20-4 Bumpless Start Action
If two successive mode change commands, one to the manual (MAN) mode and the other to the
automatic (AUT) or cascade (CAS) mode, are issued from a sequence control block, etc. within a
single scan period, bumpless start is not executed. Instead, the program set action is started from
the starting point of the program pattern.
If a mode change command to the automatic (AUT) mode is issued by itself, bumpless start is
executed.

manual (IMAN).
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.

(IMAN).
AUT
IMAN (AUT)
AUT
• When the data status at the connected destination of the manipulated output value (MV) is a
communication error (NCOM) or output failure (PTPF).
• When the connected destination of the manipulated output value (MV) is a switch block (SW-33,
SW-91) and the switch off the cascade connection (i.e., the cascade connection is open).
• When the connected destination of the manipulated output value (MV) is a process output and a
failure or output open alarm is detected in module.
MAN Fallback
established.

The MAN fallback stops the control by changing the block to manual (MAN) mode regardless of the
current operation status, and forces the function block to enter manual operation state.

Example)
AUT→MAN
MAN (CAS) →IMAN (MAN)
initial cold start.
points connected to the I/O module has been changed via maintenance.


The following actions take place:
• Any block mode change command to obtain an automatic operation state (AUT or CAS mode)
becomes invalid.

can not run in Auto mode, or etc.
Data Items - PG-L13

Table 1.20-3 Data Items of 13-Zone Program Set Block (PG-L13)

Item Not (*1)
O/S
(MAN)
SV Elapsed time x Value in seconds or minutes 0
Value in the same
CALC Calculated output value MSL
PH Intra - zone time high limit Value in seconds or minutes 0
PL Intra - zone time low limit Value in seconds or minutes 0
Output high-limit for
MH MSL to MSH MSL
remainder of zone
Output low-limit for
ML MSL to MSH MSL
remainder of zone
ZONE Zone number (*3) 1 to 13 1
ZSTR Bumpless start zone x 1 to 13 1
ZEND Bumpless end zone x 1 to 13 1
X01 to Time - axis breakpoint
x (*4) Value in seconds or minutes 0
X14 coordinate
Y01 to Output - axis breakpoint
x MSL to MSH MSL
Y14 coordinate
OPLO Output high-limit index x MSL to MSH MSL
SH Time-axis scale high limit Value in seconds or minutes -----
SL Time-axis scale low limit Value in seconds or minutes -----
MSH MV scale high limit MV engineering unit value -----
MSL MV scale low limit MV engineering unit value -----
*3: Data for ZONE can be set through an I/O connection with another function block, such as a calculation
block, but not externally as from the operation and monitoring functions.
*4: X01 cannot be set because it is a time-axis origin and fixed at 0.
SEE For more information about a list of valid block modes of the PG-L13 block, refer to:
1.21 Totalizing Batch Set Blocks (BSETU-2, BSETU-3) Page 1 of 1
1.21 Totalizing Batch Set Blocks (BSETU-2, BSETU-

3)
The term “totalizing batch set block” is a generic name for the flow-totalizing batch set block (BSETU-2) and
the weight-totalizing batch set block (BSETU-3).
This section describes the functions common to these two function blocks.
Common Functions of Totalizing Batch Set Blocks

The following explains the functions common to the BSETU-2 and BSETU-3 blocks.
SEE For more information about the functions specific to the BSETU-2 block, refer to:
ALSO 1.22, "Flow-Totalizing Batch Set Block (BSETU-2)"
For more information about the functions specific to the BSETU-3 block, refer to:
1.23, "Weight-Totalizing Batch Set Block (BSETU-3)"
Input Processing Common to Totalizing Batch Set Blocks

The BSETU-2 and BSETU-3 blocks perform a special integration.
Control Computation Processing Common to Totalizing Batch Set

Blocks
The control computation processing functions of the BSETU-2 and BSETU-3 blocks are the same. The control
computation processing functions possessed by these two function blocks are as follows:
• Batch operation
• MAN fallback
Output Processing Common to Totalizing Batch Set Blocks

The BSET-2 and BSETU-3 blocks perform a special output signal conversion.
Alarm Processing Common to Totalizing Batch Set Blocks

The alarm checks commonly performed by and specific to the BSETU-2 and BSETU-3 blocks are as follows:
• Pre-batch alarm check
• Batch end alarm check
• Cumulative deviation high and low limit check
• Leak alarm check
Compatibility between Totalizing Batch Set Block and CENTUM V,

CENTUM-XL Totalizing Batch Set Unit: FFCS Series/KFCS2/LFCS2
The Totalizing Batch Set Blocks (BSETU-2 and BSETU-3) are provided with optional compatibilities with the
Totalizing Batch Set Units of CENTUM V and CENTUM-XL.
1.21.1 Input Processing of Totalizing Batch Set Blocks (BSETU-2, BSETU-3) Page 1 of 1
1.21.1 Input Processing of Totalizing Batch Set Blocks

(BSETU-2, BSETU-3)
The BSETU-2 and BSETU-3 blocks perform a special integration.
Integration in the Totalizing Batch Set Blocks

In the BSETU-2 and BSETU-3 blocks, the following two types of integration are available:
• Integrator value (SUM):
The integration specification is the same as for other Regulatory Control Blocks, but when batch
begins the integrator value is cleared to 0.
• Total integrator value (SUM1):
The total integrator value (SUM1) accumulates the integrator value (SUM) for each batch
completion.
Total integrator value (SUM1)=(Total integrator value up to the previous batch)+Integrator value
(SUM)
SEE For more information about the integration, refer to:

ALSO 3.3, “Integration” in Function Blocks Overview (IM 33J15A20-01EN)
1.21.2 Control Algorithm of Totalizing Batch Set Blocks (BSETU-2, BSETU-3) Page 1 of 17
1.21.2 Control Algorithm of Totalizing Batch Set Blocks

(BSETU-2, BSETU-3)
The following functions are common to the control computation processing performed by the BSETU-
2 and BSETU-3 blocks.
• Batch operation
• MAN fallback
Batch Operation (Analog Output)

The batch operation performed by the Totalizing Batch Set Blocks varies depending upon the type of
output (analog output, 2-position ON/OFF output or 3-position ON/OFF output). The figure below
shows an example of batch operation in the case of analog output or data setting output to other
function block:
Figure 1.21.2-1 Batch Operation (Analog Output)
The operating status is indicated by the block status and control step. The operating status is
switched via the command switch (SW), emergency stop switch (EMSW) or control step (ZONE). The
commands issued by the command switch (SW) and emergency stop switch (EMSW) are shown
below:
• Command switch (SW)
1: Start
2: Restart
3: Abort
4: Emergency stop
0: Changes to “0” automatically when the command (1 to 4) is acknowledged.
• Emergency stop switch (EMSW)
1: Emergency stop
0: After the executes command (1), it changes to “0” automatically.
Basic Batch Operation

▼ Accept Batch-End during EMST
The following section explains the basic operation of the Totalizing Batch Set Blocks at each control
step (ZONE):
1. ZONE10: Batch start (Block status: STRT)
Sets data to the set parameters including batch setpoint (BSET) prior to batch start. If the
command switch is set to start (SW=1) while in the automatic (AUT) block mode, the current
control step moves to ZONE10 and the block starts batch operation after resetting the totalized
value (SUM) to 0.
Once batch starts, the control step moves to ZONE1.
2. ZONE1: Initial batch (Block status: IBCH)
After batch start, outputs the low flowrate setpoint (ML) as the manipulated output value (MV)
until the totalized value (SUM) reaches the initial forecast value (ILST). The output velocity
limiter does not operate. When the totalized value (SUM) exceeds ILST, the control step moves
to ZONE2.
The “low flowrate setpoint (ML)” and “initial forecast value (ILST)” are set from the operation
and monitoring functions as set parameters.
• Low flowrate setpoint (ML)
Set engineering unit data within the manipulated output value (MV) scale range.
The default is the manipulated output value (MV) scale’s low limit.
• Initial forecast value (ILST)
Set data in the same unit as the totalized value (SUM).
The default is 0.
The set value consist of 8 digits or less.
3. ZONE2: Setup (Block status: STUP)
Changes the manipulated output value (MV) to the high flowrate setpoint (MH) value during the
Ramp Up time (TU). The high flowrate setpoint (MH) is an output value in a steady state.
When the set TU time elapses in the setup mode, the control step moves to ZONE3.
The “high flowrate setpoint (MH)” and “Ramp Up time (TU)” are set from the operation and
• High flowrate setpoint (MH)
Set engineering unit data within the manipulated output value (MV) scale range.
• Ramp Up time (TU)
Set a value between 0 and 10000 seconds.
4. ZONE3: Steady (Block status: STDY)
Outputs the high flowrate setpoint (MH) as the manipulated output value (MV). When the
totalized value (SUM) reaches the value of batch setpoint (BSET) less pre-batch setpoint (PLST),
the control step moves to ZONE4.

The “batch setpoint (BSET)” and “pre-batch setpoint (PLST)” are set from the operation and
• Batch setpoint (BSET)
The default is 0.
Specify a numeric value consisting of 8 digits or less.
• Pre-batch setpoint (PLST)
The default is 0.
Specify a numeric value consisting of 8 digits or less.
5. ZONE4: Early (Block status: ERLY)
In the course of Ramp Down time (TD), the manipulated output value (MV) is changed to PRE
(pre-batch flowrate setpoint) on the gradient that leads to the low-flowrate setpoint (ML). When
the manipulated output value (MV) becomes the same value as the pre-batch flowrate setpoint
(PRE), the control step moves to ZONE5.
The “pre-batch flowrate setpoint (PRE)” and “Ramp Down time (TD)” are set from the operation
and monitoring functions as set parameters.
• Pre-batch flowrate setpoint (PRE)
Set engineering unit data within the MV scale range.
• Ramp Down time (TD)
6. ZONE5: Pre-batch (Block status: PBCH)
Outputs the pre-batch flowrate setpoint (PRE) as the manipulated output value (MV). When the
totalized value (SUM) reaches the value of batch setpoint (BSET) less leakage predictive value
(LPV), the control step moves to ZONE7.
The “leakage predictive value (LPV)” is set from the operation and monitoring functions as a set
parameter.
• Leakage predictive value (LPV)
The default is 0.
Specify a numeric value of 4 digits or less.
7. ZONE7: Batch end (Block status: END)
Batch operation ends after the manipulated output value (MV) is reset to “0.” When the batch
end wait time (TW) elapses in the batch end mode, the block mode changes to manual (MAN)
and the control step moves to ZONE0. At this time, the totalized value (SUM) is added to the
cumulative totalized value (SUM1). However, this addition will not take place in the manual
(MAN) mode.
The “batch end wait time (TW)” is set from the operation and monitoring functions as a set
parameter.
• Batch end wait time (TW)
8. ZONE0: Batch operation stop (Block status: NCNT)
In this mode, batch Control Action stops and a manually manipulated variable can be output.
9. ZONE6: Reset (Block status: RSET)
When the command switch is set to Abort (SW=3) during batch operation, the control step
moves to ZONE6 and the manipulated output value (MV) is brought down to 0 % at a speed of
changing it from the high flowrate setpoint (MH) to low flowrate setpoint (ML) over the Ramp
Down time (TD).
When the manipulated output value reaches 0 %, the control step moves to ZONE7. When the
totalized value exceeds the value of batch setpoint (BSET) less leakage predictive value (LPV),
the status changes to batch end and generates an alarm (BEND). The batch ends other than this
way does not generate batch end alarm (BEND).
10. ZONE8: Emergency stop (Block status: EMST)
When the emergency command switch is set to emergency stop (EMSW=1), or when the
command switch is set to emergency stop (SW=4), the control step moves to ZONE8, and the
manipulated output value (MV) is brought down to 0 % at a speed of changing it from the high
flowrate setpoint (MH) to low flowrate setpoint (ML) over TD (Ramp Down time). When the
manipulated output value (MV) reaches 0 %, the control step moves to ZONE9.
Even when the block is in Emergency Stop (EMST) status, if the totalized value (SUM) reaches
the batch setpoint (BSET) value minus the leakage predictive value (LPV), the control step may
shift to ZONE7. However, this behavior is alternative by changing the setting of [Accept Batch-
End during EMST] on the FCS properties sheet. By default, this check box is checked.
11. ZONE9: Emergency stop complete (Block status: EEMS)
When the totalized value (SUM) reaches the value of batch setpoint (BSET) less leakage
predictive value (LPV) during emergency stop, the control step moves to ZONE7. However, if the
option of [Accept Batch-End during EMST] on the FCS properties sheet is not checked, it will not
move to ZONE7 but stays in ZONE9.
12. ZONE11: Restart (Block status: RSTR)
When the command switch is set to restart (SW=2) during the emergency stop complete mode
(ZONE9), the control stop moves to ZONE2 via ZONE11.
Actions Triggered by Command Switch

The figure below shows the actions of batch operation triggered by the command switch (SW):
Figure 1.21.2-2 Actions of Batch Operation Triggered by Command Switch
Other than by the emergency stop command (SW=4), emergency stop can also be triggered via the
emergency stop switch (EMSW=1).
Transition of Control Step Status

The figure below shows a status transition diagram of control steps in normal operation:
Figure 1.21.2-3 Transition of Control Step Status
Status transition can also be induced by changing the control step. The control step (ZONE) can be
changed from a sequence table or calculation block, but not from the operation and monitoring
functions. Note that change commands issued by the command switch (SW) precede any operation
to change the control step (ZONE).
The totalized value (SUM) is added to the cumulative totalized value (SUM1) when batch end
processing is completed.
Manual Operation
When the block mode changes to manual (MAN), automatic control processing is suspended and
manual operation is enabled. The control step changes even during the manual (MAN) mode. When
the block mode is changed from manual (MAN) to automatic (AUT) during manual operation,
automatic control is started.
Automatic Prediction
When batch end is detected during each scan period, a flowrate error equivalent to a maximum of
one scan period may generate. The Totalizing Batch Set Blocks automatically predicts batch end in
order to minimize this error.
When the alarm status changes to pre-batch alarm (BPRE), the totalized value during the next scan
is predicted based on the totalized value increase during the current scan period (totalized value
during the current scan-totalized value during the previous scan). If the predicted value exceeds the
batch setpoint (BSET), a duration of time to keep the valve fully open is calculated in 25 msec. units,
based on the totalized value (SUM). The valve is fully opened when the time calculated using this
formula elapses.
The automatic prediction function is executed only in ZONE5. This function is also activated for
outputs via a switch instrument block.
Beginning Point of Ramp-Up When Restart

▼ Ramp Up from ML Upon Start/Restart
When a Restart command is applied while the block is in the status of emergency stop (Block Status:
EEMS), the block will move to the control step ZONE11 (Block Status: RSTR) first, and then move to
the setup step ZONE2 (Block Status: STUP). At this step, the output will ramp up. However, the
ramp-up begins from the low flow rate setpoint (ML) or from 0 % needs to be defined.
This option can be defined on the Function Block Detail Builder.
Ramp Up from ML Upon Start/Restart: Choose [Yes] or [No]
If [Yes] is selected, upon the restart command, the ramp-up of the manipulated output value (MV)
will begin from the low flowrate setpoint (ML). The setup step (Block Status: STUP) will be the same
as before but the ramp-up time (TU) will be the time of the manipulated output value (MV) ramps
from the low flowrate setpoint (ML) to the high flowrate setpoint (MH).
The batch operation will act as follows if “Ramp Up from ML Upon Start/Restart” is applied.
Figure 1.21.2-4 Ramp Up from ML Upon Restart
If [No] is selected, upon the restart command, the ramp-up of the manipulated output value (MV)
will begin from the 0 % of flowrate. The manipulated output value (MV) ramps from the 0 %
flowrate to the high flowrate setpoint (MH) at the same ramp rate specified by ramp-up time (TU).
The batch operation will act as follows if “Ramp Up from ML Upon Start/Restart” is not applied.
Figure 1.21.2-5 Ramp Up from 0 % Upon Restart
Start Action when Totalizing Batch Set Block (BSETU-2,

BSETU-3) and Controller Blocks (such as PID) in
Cascade Loop
▼ Ramp Up from ML Upon Start/Restart
If the initial forecast value (ILST) is 0, the ramp-up beginning point can be specified upon the timing
of the start command and the timing that the connected function block becomes a cascade loop.
The ramp-up begins from the low flow rate setpoint (ML) or from 0 % needs to be defined.
This option can be defined on the Function Block Detail Builder. The setting of “Ramp Up from ML
Upon Start/Restart” also functions for this purpose.
Ramp Up from ML Upon Start/Restart: Choose [Yes] or [No]
If [Yes] is selected, upon the start command, the block will not move to initial batch status (Block
Status: IBCH) but directly to go to setup step (Block Status: STUP). The ramp-up of the manipulated
output value (MV) will begin from the low flowrate setpoint (ML). The ramp-up time (TU) will be the
time of the manipulated output value (MV) ramps from the low flowrate setpoint (ML) to the high
flowrate setpoint (MH).
The batch operation will act as follows if “Ramp Up from ML Upon Start/Restart” is applied.
Figure 1.21.2-6 Ramp Up from ML Upon Start
If [No] is selected, upon the start command, the block will not move to initial batch status (Block
Status: IBCH) but directly to go to setup step (Block Status: STUP). The ramp-up of the manipulated
output value (MV) will begin from the 0 % flowrate. The manipulated output value (MV) ramps from
the 0 % flowrate to the high flowrate setpoint (MH) at the same ramp rate specified by ramp-up
time (TU).
The batch operation will act as follows if “Ramp Up from ML Upon Start/Restart” is not applied.
Figure 1.21.2-7 Ramp Up from 0 % Upon Start
However, if the initial forecast value (ILST) is greater than 0 and the block moves to initial batch
status (Block Status: IBCH) before ramp-up, the manipulated output value (MV) ramps from the low
flowrate setpoint (ML) to the high flowrate setpoint (MH) regardless what is specified for “Ramp Up
from ML Upon Start/Restart.”
Batch Operation (2-Position ON/OFF Output)

Simple batch control based on the two-position ON/OFF output method can be performed by
connecting the output terminal (OUT) of the Totalizing Batch Set Blocks to a contact output or
switch instrument block. Valve closure processing can also be performed via automatic prediction
when the block is connected to a switch instrument.
The table below shows the relationship between the manipulated output values (MV) during manual
operation and those of a contact output or switch instrument block.
Table 1.21.2-1 Relationship between Manipulated Output Values (MV) during Manual Operation
and Those of a Contact Output or Switch Instrument Block
MV value 0 % to 49.9 % 50 % to 100 %

Contact output OFF ON
Switch instrument MV=0 MV=2
When a BSETU-2 or BSETU-3 function block is applied with two-position

ON/OFF output, the parameters of the ramp up time (TU) and the ramp down
time (TD) should be set to zero.
If the ramp down time (TD) is not zero, when the function block runs
emergency shutdown to force MV to 0 %, but the control calculation will ramp
down the MV slowly based on the setting value of TD. Since the ON/OFF
output only acts in accordance with 100 % MV or 0 % MV, thus, the output
cannot become OFF if the MV is not ramping down to zero but hooked at 100
%. Consequently, the valve cannot be closed by the emergency shutdown
(EMST) action.
The same phenomenon occurs when the ramp up time (TU) is not zero. In
setup mode of the function block, the MV may be hooked at 0 % and the
valve cannot be opened.
Actions when Switch Instrument is in Cascade (CAS) Mode

When the connected switch instrument is in the cascade (CAS) mode, the BSETU-2 and BSETU-3
blocks output the manipulated output value (MV) to the sequence setpoint value (CSV) of the switch
instrument, and the switch instrument outputs the received sequence setpoint value (CSV) as its
own manipulated output value (MV). In the case of emergency stop, the manipulated output value
(MV) drops to 0 % immediately.
The figure below shows an example of simple batch operation based on the 2-position ON/OFF
output method, when the switch instrument is in the cascade (CAS) mode.
In this example, the parameters are set as follows:
• Output velocity limiter: 100%
• Ramp Up time (TU): 0 second
• Ramp Down (TD): 0 second
• High flowrate setpoint (MH): 100%
• Low flowrate setpoint (ML): 100%
• Pre-batch flowrate setpoint (PRE): 100%
Figure 1.21.2-8 Example of Simple Batch Operation Using 2-Position ON/OFF Output Method
when the Both Switch Instruments are in Cascade (CAS) Mode
SEE For more information about the switch instrument block, refer to:
ALSO 2.4, “Switch Instrument Block and Enhanced Switch Instrument Block” in Function Blocks
Reference Vol.2 (IM 33J15A31-01EN)
Actions when Switch Instrument is not in Cascade (CAS) Mode

When the connected switch instrument is not in the cascade (CAS) mode, the Flow/Weight-
Totalizing Batch Set Block (BSETU-2, BSETU-3) changes to the initialization manual (IMAN) mode. In
this mode, the MV value of the switch instrument is set as the MV of the Flow/Weight-Totalizing
Batch Set Block (BSETU-2, BSETU-3) after having been converted via the output value tracking
function.
Batch Operation (3-Position ON/OFF Output)

Simple batch control using the 3-position ON/OFF output method can be performed by connecting
the output terminals (OUT, OUT2) of the Flow-Totalizing Batch Set Block (BSETU-2) to contact
outputs or switch instruments.
When connecting to contact outputs, use two contact outputs with successive terminal numbers.
Register the contact output with the smaller terminal number as I/O connection information of the
OUT terminal. The contact output with the smaller terminal number becomes output contact 1.
When connecting to switch instruments, the switch instrument connected to the OUT terminal
becomes switch instrument 1, and the one connected to the OUT2 terminal becomes switch
instrument 2.
The table below shows the relationship between the manipulated output values (MV) during manual
operation and those of contact outputs or switch instruments:
Table 1.21.2-2 Relationship between Manipulated Output Values (MV) during Manual Operation
and Contact Outputs or Switch Instrument Blocks
MV value 0 % to 24.9 % 25 % to 74.9 % 75 % to 100 %
Contact output 1 OFF OFF ON

Contact output 2 OFF ON ON
Switch instrument 1 MV=0 MV=0 MV=2
Switch instrument 2 MV=0 MV=2 MV=2
When a BSETU-2 or BSETU-3 function block is applied with three-position

ON/OFF output, the parameters of the ramp up time (TU) and the ramp down
time (TD) should be set to zero.
output only acts in accordance with 100 % MV, 50 % MV or 0 % MV, thus,
the output cannot become OFF if the MV is not ramping down to zero but
hooked at 100 %. (or 50 %.) Consequently, the valve cannot be closed by the
emergency shutdown (EMST) action.
Actions when Both Switch Instruments are in Cascade (CAS)

Mode
When both of the connected switch instruments are in the cascade (CAS) mode, the BSETU-2 or
BSETU-3 blocks output two manipulated output values (MV) to the corresponding sequence setpoint
values (CSV) of switch instruments 1 and 2, and each switch instrument outputs the received
sequence setpoint value (CSV) as its own manipulated output value (MV). In the case of emergency
stop, the manipulated output value (MV) drops to 0 % immediately.
The figure below shows an example of simple batch operation based on the three-position ON/OFF
output method, when the switch instruments are in the cascade (CAS) mode. In this example, the
parameters are set as follows:
• Output velocity limiter: 100 %
• Ramp Up time (TU): 0 second
• Ramp Down time (TD): 0 second
• High flowrate setpoint (MH): 100 %
• Low flowrate setpoint (ML): 50 %
• Pre-batch flowrate setpoint (PRE): 50 %
Figure 1.21.2-9 Example of Simple Batch Operation Based on 3-Position ON/OFF Output Method
when Both Switch Instruments are in the Cascade (CAS) Mode
Actions when Only Switch Instrument 2 is in Cascade (CAS)

Mode
When only switch instrument 2 is in the cascade mode, the Flow/Weight-Totalizing Batch Set Block
(BSETU-2, BSETU-3) outputs only to switch instrument 2.
output method, when only switch instrument 2 is in the cascade (CAS) mode:
Figure 1.21.2-10 Example of Batch Operation when Only Switch Instrument 2 is in Cascade
(CAS) Mode
Actions when Only Switch Instrument 1 is in Cascade Mode

In batch operation where only switch instrument 1 is in the cascade (CAS) mode, the manipulated
output value (MV) of switch instrument 1 becomes 0 in the initial batch (ZONE1) and pre-batch
(ZONE5) modes. Therefore, if the manipulated output value (MV) of switch instrument 2 is 0, the
emergency stop mode (ZONE9) becomes active.
To perform output in this state, set either of the following:
• ILST (initial forecast value)=0
• PLST (pre-batch setpoint)=0
This eliminates the mode of ZONE1 or 5 and sets the command switch (SW) to “2” (restart
specification). As a result, the control step changes to ZONE3 and batch operation resumes.
output method, when only switch instrument 1 is in the cascade (CAS) mode:
Figure 1.21.2-11 Example of Batch Operation when Only Switch Instrument 1 is in Cascade
(CAS) Mode
Actions when Neither Switch Instrument is in Cascade (CAS)

Mode
When neither switch instrument is in the cascade (CAS) mode, the Flow/Weight-Totalizing Batch Set
Block (BSETU-2, BSETU-3) enters the initialization manual (IMAN) mode. In this mode, the MV value
of the switch instrument is set as the MV of the Flow/Weight-Totalizing Batch Set Block (BSETU-2,
BSETU-3) after having been converted via the output value tracking function.
Emergency Stop when an Alarm Occurs

▼ Emergency Stop when Input Open, Emergency Stop when Low-Low Alarm, Emergency Stop when
High Alarm, Emergency Stop when Low Alarm, Emergency Stop when Missing Pulse
The batch operation can be set to the emergency stop state when an alarm occurs. Emergency stop
execution can be specified for the alarms indicated below:
• Input open alarm (IOP, IOP-)
• Input low-low limit alarm (LL)
• Input high limit alarm (HI)
• Input low limit alarm (LO)
• Missing pulse alarm (NPLS) (*1)

The setting for whether the batch operation comes to an emergency stop or continues when an
alarm occurs is performed for each alarm using the Function Block Detail Builder. The setting
selections are “Yes” or “No.” When “Yes” is selected, the operation performs an emergency stop
when an alarm occurs. When “No” is selected, there is no emergency stop and the batch operation
continues. Default settings are given below:
• Emergency Stop When Input Open: The default is “Yes”
• Emergency Stop When Low-Low Alarm: The default is “No.”
• Emergency Stop When High Alarm: The default is “No.”
• Emergency Stop When Low Alarm: The default is “No.”
• Emergency Stop When Missing Pulse: The default is “Yes.” (*2)
*1: The missing pulse alarm (NPLS) is available only for BSETU-2, but not for BSETU-3.
*2: Emergency Stop When Missing Pulse is available only for BSETU-2, but not for BSETU-3.
SEE For more information about the input open, input low-low limit, input high limit and input low limit
ALSO alarms, refer to:
5.1, “Input Open Alarm Check” in Function Blocks Overview (IM 33J15A20-01EN)
5.3, “Input High-High and Low-Low Limit Alarm Check” in Function Blocks Overview (IM
33J15A20-01EN)
5.4, “Input High and Low Limit Alarm Check” in Function Blocks Overview (IM 33J15A20-
01EN)
For more information about the missing pulse alarm, refer to:
" Missing Pulse Alarm Check" in 1.22, "Flow-Totalizing Batch Set Block (BSETU-2)"

manual (IMAN).
at the connected destination, even when the initialization manual (IMAN) mode is changed to
manual (MAN), the initialization manual (IMAN) mode will precede the manual (MAN) mode and any
operation to change to the manual (MAN) mode will become invalid.
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
IMAN (AUT)
AUT
SW-91) and the switches off the cascade connection.
failure or output open alarm is detected in the process output.
MAN Fallback
established. In the Flow-Totalizing Batch Set Block (BSETU-2), the emergency stop action triggered
by an input open alarm will override the MAN fallback action only when input open emergency stop
is defined “Yes” in the function block builder. When an input open alarm occurs, the emergency stop
(EMST) mode becomes active and the manipulated output value (MV) drops to the manipulated
output scale low limit (MSL).
Once the emergency stop action is completed, the MAN fallback action is executed and the block
mode changes to manual (MAN) mode.
Characteristics of MAN Fallback


AUT→MAN
The MAN fallback condition is established in the following situations:
• When the data status of the process variable (PV) is invalid (BAD) or calibration (CAL).
initial cold start.


The block mode change interlock function stops the control computation processing of function
blocks that are operating automatically, while disabling the currently stopped function blocks from
changing to an automatic operation state. This action takes place when the block mode change
interlock condition is established.

• Any block mode change command to obtain an automatic operation state (AUT mode) becomes
invalid.

1.21.3 Output Processing of Totalizing Batch Set Blocks (BSETU-2, BSETU-3) Page 1 of 4
1.21.3 Output Processing of Totalizing Batch Set Blocks

(BSETU-2, BSETU-3)
The BSETU-2 and BSETU-3 blocks perform a special output signal conversion.
This section describes the output signal conversion, using the BSETU-2 block as an example.
Output Signal Conversion of the Flow/Weight-Totalizing

Batch Set Block (BSETU-2 and BSETU-3)
▼ Output Signal Conversion
The types of output signal processing available in the BSETU-2 and BSETU-3 blocks are analog
output, data set output for other function block, subsystem output, and 2-position/3-position
ON/OFF output. Pulse width output is not available.
Not only the process I/O contact output but also Switch Instrument blocks can be used as the
destination of 2-position/3-position ON/OFF output.
The following list shows the Switch Instrument block that may be connected to BSETU-2 and BSETU-
3. Switch Instrument block with two status output can not be connected.
• SIO-11, SIO-11E
• SIO-21, SIO-21E
• SO-1, SO-1E
When a BSETU-2 or BSETU-3 function block is applied with two-position

ON/OFF output or three-position ON/OFF output, the parameters of the ramp
up time (TU) and the ramp down time (TD) should be set to zero.
output only acts in accordance with 100 % MV, 50 % MV or 0 % MV, thus,
the output cannot become OFF if the MV is not ramping down to zero but
hooked at 100 %. (or 50 %.) Consequently, the valve cannot be closed by the
emergency shutdown (EMST) action.
Connecting a 2-Position ON/OFF Output to a Contact Output

The following figure illustrates the connection of an I/O contact output to the output terminal (OUT)
of the BSETU-2 block:
Figure 1.21.3-1 An Example of 2-Position ON/OFF Output
The following table shows the relationship between the manipulated output value (MV) in the
manual operating mode and the contact output status:
Table 1.21.3-1 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
Figure 1.21.3-2 Simplified Batch Operation of the 2-Position ON/OFF Output System
Connecting a 3-Position ON/OFF Output to Contact Outputs

The following figure illustrates the connection of the I/O contact outputs to the output terminals
(OUT and OUT2) of the BSETU-2 block:
manual operating mode and the contact outputs status:
Table 1.21.3-2 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
Figure 1.21.3-4 3-Position ON/OFF Output
2-Position ON/OFF Output Connected to a Switch Instrument

in Cascade
The following figure illustrates the connection of a 2-position ON/OFF output to a switch instrument
in cascade. In this example, the switch instrument CSV is connected to the output terminal (OUT) of
the Flow-Totalizing Batch Set Block (BSETU-2) in cascade.
manual operating mode and the switch instrument status:
Table 1.21.3-3 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
When the connected switch instrument is in the cascade (CAS) mode, the BSETU-2 block outputs a
manipulated output value (MV) to the sequence setpoint value (CSV) of the switch instrument, and
the instrument will output the sequence setpoint value (CSV) as its own manipulated output value
(MV). If the switch instrument is not in the cascade (CAS) mode, the BSETU-2 block will be in the
initialization manual mode (IMAN). Then, the switch instrument manipulated output value (MV)
converted to the manipulated output value (MV) data of the BSETU-2 block will be set as the
manipulated output value (MV) of the BSETU-2 by the output tracking function. Even when
connected to a switch instrument block, the automatic prediction is still functioning to close the
valve.
3-Position ON/OFF Output Connected to a Switch instrument

in Cascade
The following figure illustrates the connection of the 3-position ON/OFF output to a switch
instrument in cascade. In this example, the switch instrument CSV is connected to the output
terminals (OUT or OUT2) of the Flow-Totalizing Batch Set Block (BSETU-2) in cascade. In the case
of 3-position ON/OFF output, Switch Instrument Block with 1 Output (SO-1) and Switch Instrument
Block with 1 Output (SO-1) are connected to the OUT and OUT2 terminals, respectively.
manual operating mode and the switch instrument status:
Table 1.21.3-4 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
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 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.
1.21.4 Alarm Processing of Totalizing Batch Set Blocks (BSETU-2, BSETU-3) Page 1 of 3
1.21.4 Alarm Processing of Totalizing Batch Set Blocks

(BSETU-2, BSETU-3)
The alarm checks commonly performed by and specific to the BSETU-2 and BSETU-3 blocks are as
follows:
• Pre-batch alarm check
• Batch end alarm check
• Cumulative deviation high and low limit check
• Leak alarm check
The pre-batch alarm and the batch end alarm will be initiated only under the
conditions described later in this section.
When checking the BSETU-2 or BSETU-3 running state with sequence table or
other blocks, it is recommended not using the alarm status but using the
block status or the zone number.
Pre-Batch Alarm Check

▼ Pre-Batch Alarm
The pre-batch alarm check is a function that determines if the integral value (SUM) has reached a
value (BSET-PLST) obtained by subtracting the pre-batch setpoint value (PLST) from the batch
setpoint value (BSET).
If it is determined that the integral value (SUM) has reached a value (BSET-PLST) obtained by
subtracting the pre-batch setpoint value (PLST) from the batch setpoint value (BSET), a pre-batch
alarm (BPRE) is activated.
To enable the pre-batch alarm function, set the alarm detect as “enabled” in the Function Block
Detail Builder.
The pre-batch alarm can be set with the Function Block Detail Builder.
Pre-batch alarm: Choose [Yes] or [No].
Default is [No].
Batch End Alarm Check

▼ Batch End Alarm
The batch end alarm check is a function that determines if the integral value (SUM) has reached a
value (BSET-LPV) obtained by subtracting the leakage predictive value (LPV) from the batch setpoint
value (BSET).
If it is determined that the integral value (SUM) has reached a value (BSET-LPV) obtained by
subtracting the leakage predictive value (LPV) from the batch setpoint value (BSET), a batch end
alarm (BEND) is generated.
To enable the batch end alarm check, set the alarm detect as “enabled” in the Function Block Detail
Builder.
The batch end alarm can be set with the Function Block Detail Builder.
Batch End Alarm: Choose [Yes] or [No].
Default is [No].
Cumulative Deviation High and Low Limit Check

▼ Accumulated Deviation High/Low Limit Alarm
The cumulative deviation high and low limit check is a function that determines whether the
deviation (SUM-BSET) between the integral value (SUM) and batch setpoint value (BSET) falls
outside the range of the absolute value of the cumulative deviation alarm setpoint value (DL).
If it is determined that the deviation exceeds the cumulative deviation alarm setpoint value (DL) in
the positive direction, a cumulative deviation high limit alarm (BDV+) occurs. Similarly, if it exceeds
the DL in the negative direction, a cumulative deviation low limit alarm (BDV-) occurs. These alarms
are checked upon batch completion (transits from ZONE7 to ZONE0) and are maintained as long as
the control step is ZONE0 (batch stopped status). However, when a reset (SW=3) is done, the alarm
check is not performed.
To activate the cumulative deviation high and low limit alarm check, set the type of cumulative
deviation high and low limit alarm check and the cumulative deviation high and low limit alarm check
setpoint value (DL).
Cumulative Deviation High and Low Limit Alarm Check Type

The type of cumulative deviation high and low limit alarm is set by the “cumulative deviation high
and low limit alarm” item in the Function Block Detail Builder. The types of cumulative deviation high
and low limit alarms are given below. The default is “high and low limit alarm.”
• High and low limit alarm
Monitors the deviation for both the high and low limits
• High limit only
Monitors the deviation for the high limit only
• Low limit only
Monitors the deviation for the low limit only
• No alarm
No detection is performed
When single direction is specified for the cumulative deviation high and low limit alarm type, only
the cumulative deviation high limit alarm is monitored when the cumulative deviation alarm setpoint
(DL) has a plus sign, and only the low limit alarm is monitored when the setpoint has a minus sign.
Cumulative Deviation Alarm Setpoint (DL)

The cumulative deviation alarm setpoint (DL) is set by the operation and monitoring function. The
cumulative deviation alarm setpoint (DL) can changed as setting parameters.
• Cumulative deviation alarm setpoint (DL): Same unit data as SUM
• Number of digits for the setting: Maximum 4 digits
Default is 1000.
Leak Alarm Check

▼ Leak Check
The leak alarm check is a function that compares the integral value and the previous integral value
at the time of batch completion (saved when batch is completed) and determines whether the
difference exceeds the leak setpoint value (LK).
If it is determined that the difference exceeds the leak setpoint value (LK), a leak alarm (LEAK)
occurs. Flowrate accumulation is being performed from the time the batch is completed until the
next batch starts.
• Flow-Totalizing Batch Set Block (BSETU-2)
For the BSETU-2 block, the leak alarm check is performed only for an increase (the difference is a
positive number).
• Weight-Totalizing Batch Set Block (BSETU-3)
For the BSETU-3 block, the leak alarm check is performed for both an increase (the difference is
a positive number) and decrease (the difference is a minus number). However, the alarm status
will be leak alarm (LEAK) whether the leak is an increase or a decrease.
To activate the leak alarm check, set whether the leak alarm check is enabled or disabled and the
leak setpoint value (LEAK).
Leak Alarm Enabled/Disabled

The leak alarm can be set with the Function Block Detail Builder.
Leak alarm: Select from “enabled” and “disabled”
Default is “enabled”.
Leak Setpoint (LK)

The leak setpoint is set by the operation and monitoring function.
Leak setpoint (LK): Same unit data as SUM
Maximum 4 digits
Default is 100.
1.21.5 Compatibility between Totalizing Batch Set Block and CENTUM V, CENTU... Page 1 of 5
1.21.5 Compatibility between Totalizing Batch Set Block

and CENTUM V, CENTUM-XL Totalizing Batch Set
Unit
The Totalizing Batch Set Blocks (BSETU-2 and BSETU-3) are provided with optional compatibilities
with the Totalizing Batch Set Units of CENTUM V and CENTUM-XL. The optional compatibilities are
as follows:
• Start/Restart upon ACT.ON command
• Accept restart command when emergently stopped
• Inhibit Pre-Batch alarm when emergently stopped
• Initiate Batch-End alarm when batch ended
• Release Pre-Batch alarm when batch ended
• Actions of manipulated output value (MV) when changing from MAN to AUT mode
These features are available only for FFCS series, KFCS2, and LFCS2.
Start/Restart upon ACT.ON Command: FFCS

Series/KFCS2/LFCS2
When this optional compatibility is selected, the ACT.ON action command in a sequence table can
also initiate the BSETU-2 or BSETU-3 blocks Batch Start action according to the block status, and the
Batch Restart action during emergency stop status.
Upon the ACT.ON, the BSETU-2 and BSETU-3 block will behave as follows:
• When the batch operation is stopped (Block Status: NCNT) and the block is manual (MAN) mode,
upon the ACT.ON command, as if starting batch operation using the Command Switch to start
(SW=1) while the block is in automatic (AUT) mode.
• When the batch is running emergency stop (Block Status: EMST) or when the batch is
emergently stopped (Block Status: EEMS), upon the ACT.ON command, as if restarting batch
operation using the Command Switch to restart (SW=2) while the block is in automatic (AUT)
mode.
• When the batch is running emergency stop (Block Status: EMST) or when the batch is
emergently stopped (Block Status: EEMS), upon the ACT.ON and ZONE.0 commands, the block
will start the batch operation from the beginning instead of restart. However, in the sequence
table, the ACT.ON and ZONE.0 must be scripted in the same scan time.
• When the batch is at a status other than the above described status such as batch stop (NCNT),
emergency stop (EMST) or emergency stop complete (EEMS) and the block is at automatic (AUT)
mode, upon the ACT.ON command, no action will be initiated. However, if the block is at manual
(MAN) mode, upon the ACT.ON command, the block will shift to automatic (AUT) mode.
Table 1.21.5-1 Scripts in Sequence Table When Migrating CENTUM V 7BS or CENTUM-XL BSETU
Action 7BS/BSETU BSETU-2 Remarks

LOOP=AUT, ACT.ON (*1); Same as starting batch using Command Switch to start
Start
SV=0 ZONE.0 (SW=1) while the block is in automatic (AUT) mode.
Emergency SW.4 or
LOOP=CAS
Stop EMSW.1
Same as restarting batch using Command Switch to restart
Restart LOOP=AUT ACT.ON (*1)
(SW=2) while the block is in automatic (AUT) mode.
Reset LOOP=MAN SW.3 The output (MV) may vary upon SW.3 and MODE.MAN.
*1: For Start, use ACT.ON instead of LOOP=AUT and ZONE.0 instead of SV=0. For Restart, use ACT.ON
instead of LOOP=AUT. Moreover, the control step (ZONE) cannot be changed from HIS, but can be changed
from sequence table.
Moreover, from HIS, ACT.ON command cannot be entered. To start a batch from HIS, the operator
can change the block into automatic (AUT) mode and use the Command Switch (SW=1). However,
if the optional compatibility is not enabled, the ACT.ON command in the sequence table cannot
change the block and ZONE.
Accept Restart Command when Emergently Stopped:

FFCS Series/KFCS2/LFCS2
Normally, when the BSETU-2 or BSETU-3 block is undergoing the ramp-down (ZONE8) triggered by
emergency stop (Block Status: EMST), the restart command SW=2 will not be accepted.
However, if the optional compatibility is enabled, the restart command SW=2 and ACT.ON from the
sequence table will be accepted.
Inhibit Pre-Batch when Emergently Stopped: FFCS

Series/KFCS2/LFCS2
Normally, when the BSETU-2 or BSETU-3 block is undergoing an emergency stop (Block Status:
EMST) while the totalized flow (SUM) becomes equal to Batch Setpoint (BSET) minus Pre-Batch
Setpoint (PLST), the pre-batch alarm (BPRE) will be initiated.
If the optional compatibility is enabled, the pre-batch alarm (BPRE) will be inhibited when
emergently stopped.
Initiate Batch-End Alarm when Batch Ended: FFCS

Series/KFCS2/LFCS2
Normally, when automatic prediction is applied while the totalized flow (SUM) becomes equal to
Batch Setpoint (BSET) minus Leakage Predictive Value (LPV) i.e., SUM = BSET - LPV, the block shifts
to batch end (Block Status: END) but the Batch-End alarm will not be initiated.
If the optional compatibility is enabled, the batch-end alarm (BEND) will be initiated when the block
shifts to batch end status. The actions are as follows:
• The batch-end (BEND) alarm will be definitely imitated when the block shifts to batch end status.
• If the batch end wait time (TW) is set to 0, the control step will be shifted from ZONE7 of batch-
end (Block Status: END) to ZONE0 of batch-stop (Block Status: NCNT) immediately and the
batch-end (BEND) alarm will be initiated.
However, this option is valid only when the setting of [Batch End Alarm] is set to [Yes] on the
SEE For more information about automatic prediction, refer to:

ALSO " Automatic Prediction" in 1.21.2, "Control Algorithm of Totalizing Batch Set Blocks (BSETU-
2, BSETU-3)"
For more information about checking the batch-end alarm, refer to:
" Batch End Alarm Check" in 1.21.4, "Alarm Processing of Totalizing Batch Set Blocks
(BSETU-2, BSETU-3)"
Release Pre-Batch Alarm When Batch Ended: FFCS

Series/KFCS2/LFCS2
Normally, the pre-batch alarm (BPRE) is released together with the batch-end alarm (BEND) at the
time that the next batch is started. The pre-batch alarm (BPRE) cannot be released at batch end
status (Block Status: END).
If the optional compatibility is enabled, the pre-batch alarm (BPRE) will be released when the block
shifts to batch end status (Block Status: END).
However, this option is valid only when the setting of [Batch End Alarm] is set to [Yes] on the
SEE For more information about checking the pre-batch alarm, refer to:
ALSO " Pre-Batch Alarm Check" in 1.21.4, "Alarm Processing of Totalizing Batch Set Blocks
(BSETU-2, BSETU-3)"
Actions of Manipulated Output Value (MV) when

Changing from MAN to AUT Mode: FFCS
Series/KFCS2/LFCS2
If the optional compatibility is enabled, the actions of manipulated output value (MV) when changing
from manual (MAN) to automatic (AUT) mode are as follows:
• When batch is stopped (Block Status: NCNT), if the block is changed to automatic (AUT) mode,
the manipulated output value (MV) will become 0.
However, if the optional compatibility is not enabled, the manipulated output value (MV) will hold
the current value.
• When batch is running and in a status other than batch stopped (Block Status: NCNT), if the
block is changed from automatic (AUT) to manual (MAN) mode, and then changed to automatic
(AUT) mode again, the manipulated output value (MV) will ramp up to high flowrate setpoint
(MH) with the specified ramp-up rate for setup step (Block Status: STUP). When the batch
reaches Early status (Block Status: ERLY), the manipulated output value (MV) will ramp down to
pre-batch flowrate setpoint (PRE) with the specified ramp-down rate.
However, if the optional compatibility is not enabled, the manipulated output value (MV) will
change to a value according to its control step (ZONE) while the block is changed from automatic
(AUT) to manual (MAN) mode.
When the block is changed from automatic (AUT) to manual (MAN) mode, the manipulated output
value (MV) will act as follows:
Table 1.21.5-2 Actions of Manipulated Output Value (MV) when Changed from AUT to MAN
Mode: FFCS Series/KFCS2/LFCS2
Block Optional Compatibility Disabled

ZONE Optional Compatibility Enabled (*1)
Status (*1)
MV: Holds (or tracks the connected
0 NCNT MV=0
value)
1 IBCH MV=ML MV=ML
2 STUP MV: Ramps Up MV: Ramps Up
3 STDY MV=MH
If MV < MH, MV ramps up with the rate for
STUP(*2).
4 ERLY MV: Ramps Down MV: Ramps Down
If MV > PRE, MV ramps down with the rate for
5 PBCH MV=PRE
ERLY.
7 END MV=0 (*3) MV=0 (*3)
8 EMST MV: Ramps Down MV: Ramps Down
9 EEMS MV=0 MV=0
*1: MH: Manipulated variable high-limit setpoint
ML: Manipulated variable low-limit setpoint
PRE: Pre-batch flowrate set point
*2: In manual (MAN) mode, if MV is manipulated to a value smaller than MH, the block will not shift to
ZONE2 when changed to automatic (AUT) mode. When MV ramps up to MH, the low alarm (LO) and
the low-low alarm (LL) will be masked so as to prevent them to trigger the emergency stop.
*3: The batch end wait time (TW) also elapses in manual (MAN) mode. When the batch end wait time
(TW) is elapsed after batch end, the control step (ZONE) will shift to ZONE0.
Enable/Disable Optional Compatibilities: FFCS

Series/KFCS2/LFCS2
▼ CENTUM V/CENTUM-XL Compatible
The table below shows the settings for compatibilities of totalizing batch set block.
Table 1.21.5-3 Settings for Compatibilities of Totalizing Batch Set Block: FFCS
Series/KFCS2/LFCS2
Totalizing Batch Set Block Setting

Compatibilities between 7BS of CENTUM V, BSETU of CENTUM-XL and BSETU- [Compatible with 7BS,
2 /BSETU-3 BSETU].
Compatibilities between BSETU-2 of CENTUM-XL and BSETU-2
[CENTUM-XL Compatible].
Compatibilities between BSETU-3 of CENTUM-XL and BSETU-3
The settings can be performed on the FCS Properties sheet.

• CENTUM V/CENTUM-XL Compatible
Choose from [No], [Compatible with 7BS, BSETU] and [CENTUM-XL Compatible].
When [Compatible with 7BS, BSETU] is selected, the following compatibilities will be applied:
• Start/Restart upon ACT.ON command
• Release Pre-Batch alarm when batch ended
• Ramp Up from ML Upon Start/Restart (*1)
When [CENTUM-XL Compatible] is selected, the following compatibilities will be applied:
• Inhibit Pre-Batch alarm when emergently stopped
• Ramp Up from ML Upon Start/Restart (*1)
*1: When the option of [Compatible with 7BS, BSETU] or [CENTUM-XL Compatible] is checked, the
compatibility is also applied to the function block when the option of [Ramp Up from ML Upon Start/Restart] is
checked on the Function Block Detail builder.
SEE For more information about [Ramp Up from ML Upon Start/Restart] option, refer to:
ALSO " Beginning Point of Ramp-Up When Restart" in 1.21.2, "Control Algorithm of Totalizing
Batch Set Blocks (BSETU-2, BSETU-3)"
" Start Action when Totalizing Batch Set Block (BSETU-2, BSETU-3) and Controller Blocks
(such as PID) in Cascade Loop" in 1.21.2, "Control Algorithm of Totalizing Batch Set Blocks
(BSETU-2, BSETU-3)"
1.22 Flow-Totalizing Batch Set Block (BSETU-2) Page 1 of 10
1.22 Flow-Totalizing Batch Set Block (BSETU-2)

The Flow-Totalizing Batch Set Block (BSETU-2) totalizes flowrate signals and outputs the
manipulated output value in accordance with the totalized value. This block is used for batch control,
such as batch shipment control of products and batch charge control of raw materials.
Flow-Totalizing Batch Set Block (BSETU-2)

▼ Connection
The Flow-Totalizing Batch Set Block (BSETU-2) totalizes flowrate signals and outputs the
manipulated output value (MV) in accordance with the totalized value.
The Flow-Totalizing Batch Set Block (BSETU-2) changes the output to 0 % when the totalized value
reaches the batch setpoint.
The Flow-Totalizing Batch Set Block (BSETU-2) enables batch control, such as batch shipment
control of products and batch charge control of raw materials.
The figure below shows a function block diagram of Flow-Totalizing Batch Set Block (BSETU-2):
Figure 1.22-1 Function Block Diagram of Flow-Totalizing Batch Set Block (BSETU-2)
The figure below shows an example of simple batch shipment control:
Figure 1.22-2 Example of Simple Batch Shipment Control
The figure below shows an example of batch shipment control where flow velocity is PID controlled
in combination with other function blocks:
Figure 1.22-3 Example of Batch Shipment Control
The figure below shows an example of batch blend control:
Figure 1.22-4 Example of Batch Blend Control
the Flow-Totalizing Batch Set Block (BSETU-2):
Table 1.22-1 Connection Methods and Connected destinations of the I/O Terminals of Flow-
Totalizing Batch Set Block (BSETU-2)

Measurement
IN x Δ x x
input
Manipulated
OUT x x x x x
output
Manipulated
OUT2 x Δ x
output (*2)
Interlock SW
INT x Δ x x x
output
link block (ADL).
*2: The OUT2 terminal is used when connecting a 3-position ON/OFF output to switch instruments 1 and 2,
for connection to switch instrument 2.
OUT Terminal Manipulated Output
The OUT terminal outputs the manipulated output signals indicated below:
• Analog output
• Output to other function blocks
• Contact outputs for 2-position ON/OFF output and 3-position ON/OFF output
• Data setting to the 2-position ON/OFF output switch instrument
• Data setting to switch instrument 1 when the 3-position ON/OFF output is connected to switch
instruments 1 and 2.
OUT2 Terminal Manipulated Output

The OUT2 terminal outputs the data set to switch instrument 2 when the 3-position ON/OFF output
is connected to switch instruments 1 and 2.
Function of Flow-Totalizing Batch Set Block (BSETU-2)

The BSETU-2 block performs input processing, control computation processing, output processing,
The only processing timing available for the BSETU-2 block is a periodic startup. Selections available
SEE For more information about the functions common to the BSETU-2 and BSETU-3 blocks, refer to:
ALSO 1.21, "Totalizing Batch Set Blocks (BSETU-2, BSETU-3)"
For more information about the types of input processing, output processing, and alarm
processing possible for the BSETU-2 block, refer to:
Control Computation Processing of Flow-Totalizing Batch Set

Block (BSETU-2)
The table below shows the control computation processing functions of the Flow-Totalizing Batch Set
Block (BSETU-2).
Table 1.22-2 Control Computation Processing Functions of Flow-Totalizing Batch Set Block
(BSETU-2)
Control
processing
Performs batch operation in accordance with the type of output (analog output,
Batch operation
twoposition ON/OFF output or three-position ON/OFF output).
MAN fallback place when the MAN fallback condition becomes satisfied. However, the emergency
stop action precedes when an input open alarm has occurred.
Block mode change
interlock
mode.
SEE For more information about the control computation processing of the BSETU-2 block, refer to:
ALSO 1.21.2, "Control Algorithm of Totalizing Batch Set Blocks (BSETU-2, BSETU-3)"
Alarm Processing Specific to Flow-Totalizing Batch Set Block

(BSETU-2)
The “missing pulse alarm check” and “flowrate alarm check,” which are two of the alarm checks
performed by the BSETU-2 block, are specific to this function block.
In addition, the BSETU-2 block uses a unique alarm display priority order, which is different from
that of other function blocks.
Missing Pulse Alarm Check

▼ Missing Pulse
The missing pulse alarm check is a function that determines whether a pulse input for a set duration
is detected during pulse input detection.
If it is determined that when a pulse input is not detected for the set duration during pulse input
detection, a missing pulse alarm (NPLS) is generated. This check is performed during each missing
pulse check time (t3) after the missing pulse check mask interval (t2) has elapsed and only when
the control step is 1, 2, 3, 4 or 5.
The figure below illustrates the timing of the BSETU-2 block alarm check.
Figure 1.22-5 Alarm Check Timing
To activate the missing pulse alarm, set whether the missing pulse alarm check is enabled or
disabled, the missing pulse check mask interval, and the missing pulse check time.
Missing Pulse Alarm Check Enabled/Disabled

The missing pulse alarm can be set with the Function Block Detail Builder.
Missing pulse alarm: Select from “enabled” and “disabled.”
Default is “enabled.”
Missing Pulse Check Mask Interval

The missing pulse check mask interval can be set with the Function Block Detail Builder.
Missing pulse check mask interval: 0 to 10000
Unit is the scan period.
Default is 5.
Missing Pulse Check Time

The missing pulse check time can be set with the Function Block Detail Builder.
Missing pulse check time: 0 to 10000

Default is 1.
For FFCS/ FFCS-L/KFCS2/KFCS, if a pulse input signal is sent from an ER bus

node, missing pulse alarm may occur due to the delay of data refresh. Thus,
when setting the missing pulse check time, the data refresh delay from ER
bus node should be put into consideration.
Moreover, if the ER bus interface master modules (EB401) of FFCS/FFCS-
L/KFCS2/KFCS, or RIO bus interface modules (RB301) of LFCS2/LFCS are dual-
redundantly configured, when switching from one module to another, the data
refresh of pulse input may halt for a few seconds. The missing pulse check
time can be set with the following consideration:
• For RB301 (half time: 1 or 2 seconds)
Missing pulse check time should be greater than 2 divided by scan period.
(i.e., Missing pulse check time > 2 if scan period is 1 second; Missing pulse
check time > 4 if scan period is 500 ms; Missing pulse check time > 10 if
scan period is 200 ms)
• For EB401 (half time: 2 or 3 seconds)
Missing pulse check time should be greater than 4 divided by scan period.
(i.e., Missing pulse check time > 4 if scan period is 1 second; Missing pulse
check time > 8 if scan period is 500 ms; Missing pulse check time > 20 if
scan period is 200 ms)
SEE For more information about the data refresh cycle between the ER bus node of FFCS/FFCS-
ALSO L/KFCS2/KFCS and EB401, refer to:
“ Data Flow in Process I/O” in 7.1.3, “Timing of Process I/O” in Function Blocks Overview
(IM 33J15A20-01EN)
Flowrate Alarm Check

▼ Flow Check Mask Interval, Input Low-Low Limit Alarm, PV High/Low Limit Alarm
The flowrate checks take place upon expiration of the flowrate check masking interval (t1), as
shown in Figure below. Specify the masking interval with the Function Block Detail Builder.
Flowrate check masking interval: 0 to 10000
The default is 10.
The flowrate alarm check processing timing of BSETU-2 block is shown below.
Figure 1.22-6 Flowrate Check Processing Timing
The flowrate alarm check in the BSETU-2 block consists of the low-low limit check and the high-low
limit check.
Low-Low Limit Alarm

A low-low limit alarm (LL) is generated if the flowrate (PV) falls below the low-low limit alarm
setpoint (LL). This check operates in control steps 1, 2, 3, 4, and 5.
Low-Limit Alarm
A low-limit alarm (LO) is generated if the flowrate (PV) falls below the low-limit alarm setpoint (PL).
This check operates only in control step 3.
High-Limit Alarm
A high-limit alarm (HI) is generated if the flowrate (PV) exceeds the high-limit alarm setpoint (PH).
This check operates in control steps 1, 2, 3, 4, and 5.
Alarm Display Priority of the Flow-Totalizing Batch Set

Block (BSETU-2)
The following is the order for the alarm display priority specific to the BSETU-2 block:
OOP>IOP>IOP->NPLS>LL>HI>LO>LEAK>BDV+>BDV->BEND>BPRE>CNF
When there are absolutely no alarms generated, the alarm status is NR.
Table 1.22-3 Alarm Check for the Control Steps (ZONE) of the Flow-Totalizing Batch Set Block
ZONE(*1)
Alarm
0 1 2 3 4 5 6 7 8 9 10 11
IOP x x x x x x x x x x x x
IOP- x x x x x x x x x x x x
OOP x x x x x x x x x x x x
CNF x x x x x x x x x x x x
LL - x x x x x - - - - - -
HI - x x x x x - - - - - -
LO - - - x - - - - - - - -
BDV + Δ - - - - - - - - - - -
BDV- Δ - - - - - - - - - - -
LEAK x - - - - - - - - - - -
NPLS - x x x x x - - - - - -
BPRE ▲ x x x x x x x x x x x
BEND ▲ x x x x x x x x x x x
*1: x:Alarm check is executed for the ZONE.
Δ:Alarm check is executed only once when ZONE=7 changes to ZONE=0.
-:Alarm check is not executed for the ZONE.
The alarm is set to normal state (NR).
▲:Alarm check is not executed and the status prior to ZONE=0 is retained.
SEE For more information about operation of the control steps for the BSETU-2 block, refer to:
ALSO " Batch Operation (Analog Output)" in 1.21.2, "Control Algorithm of Totalizing Batch Set
Blocks (BSETU-2, BSETU-3)"
Data Items - BSETU-2

Table 1.22-4 Data Items of Flow-Totalizing Batch Set Block (BSETU-2) (1/2)

Item Not (*1) (*2)
BSTS Block status ----- NCNT
Alarm detection
AF ----- 0
specification
Alarm masking
AOFS ----- 0
specification
PV Flowrate process variable Δ (*3) PV engineering unit value SL
SUM Totalizer value x SUM engineering unit value 0
Cumulative totalized Value in the same engineering

SUM1 x 0
value unit as SUM
SW Command switch x 0, 1, 2, 3, 4 0
LL x SL to SH SL
setpoint
High - limit alarm
PH x SL to SH SH
setpoint
Cumulative deviation Value in the same engineering
DL x 1000
alarm setpoint unit as SUM
Table 1.22-5 Data Items of Flow-Totalizing Batch Set Block (BSETU-2) (2/2)

Item Not (*1) (*2)
High flowrate
MH x MSL to MSH MSH
setpoint
ML Low flowrate setpoint x MSL to MSH MSL
Pre-batch flowrate
PRE x MSL to MSH MSL
setpoint
Leakage predictive Value in the same engineering
LPV x 0
value unit as SUM
ILST Initial forecast value x 0
unit as SUM
PLST Pre-batch setpoint x 0
unit as SUM
BSET Batch setpoint x 0
unit as SUM
LK Leak setpoint x 100
unit as SUM
TU Up time x 0 to 10,000 seconds 0 second
TD Down time x 0 to 10,000 seconds 0 second
TW Batch end wait time x 0 to 10,000 seconds 0 second
ZONE Control step 0 to 11 0
Emergency stop
EMSW x 0, 1 0
switch
Output high-limit
OPHI x MSL to MSH MSH
index
Output low-limit
OPLO x MSL to MSH MSL
index

unit as PV
unit as PV
*2: SUM: Totalizer value
SEE For more information about valid block modes of the BSETU-2 block, refer to:
Block Status of Flow-Totalizing Batch Set Block (BSETU-

2)
Table 1.22-6 Block Status of Flow-Totalizing Batch Set Block (BSETU-2)
Block Status
Level
Symbol Name
STRT Batch Start
IBCH Batch Initialization
STUP Batch Setup
STDY Ready
ERLY Early
PBCH Pre-Batch
1
END Batch End
NCNT Batch Stopped
RSET Reset
EMST Emergency Shutdown
EEMS Emergency Shutdown Completed
RSTR Restart
1.23 Weight-Totalizing Batch Set Block (BSETU-3) Page 1 of 6
1.23 Weight-Totalizing Batch Set Block (BSETU-

3)
The Weight-Totalizing Batch Set Block (BSETU-3) calculates a totalized value of changes in weight
signals sent from a scale, and outputs the manipulated output value in accordance with the totalized
value. This block is used for batch control, such as batch shipment control of products and batch
charge control of raw materials.
Weight-Totalizing Batch Set Block (BSETU-3)

▼ Connection
The Weight-Totalizing Batch Set Block (BSETU-3) calculates a totalized value of changes in weight
signals sent from the scale, and outputs the specified manipulated output value in accordance with
the totalized value.
The Weight-Totalizing Batch Set Block (BSETU-3) changes the output to 0 % when the totalized
value reaches the batch setpoint.
The Weight-Totalizing Batch Set Block (BSETU-3) enables batch control, such as batch shipment
control of products and batch charge control of raw materials.
The figure below shows a function block diagram of Weight-Totalizing Batch Set Block (BSETU-3):
Figure 1.23-1 Function Block Diagram of Weight-Totalizing Batch Set Block (BSETU-3)
the Weight-Totalizing Batch Set Block (BSETU-3):
Table 1.23-1 Connection Methods and Connected destinations of the I/O Terminals of Weight-
Totalizing Batch Set Block (BSETU-3)

IN Analog input x Δ x x
IN2 Digital input x Δ x x
IN3 Sign bit input x Δ x x
IN4 Ready bit input x Δ x x
Manipulated
OUT x x x x
output
Manipulated
OUT2 x Δ x
output (*2)
Interlock SW
INT x Δ x x x
input
link block (ADL).
*2: The OUT2 terminal is used when connecting a 3-position ON/OFF output to switch instruments 1 and 2,
for connection to switch instrument 2.
IN Terminal Analog Input

If the weight signal from a scale is a analog signal, connect the weight signal to the IN terminal via
an analog process I/O module of process I/O. When reading weight data from other function blocks,
also connect the weight signal to the IN terminal.
IN2 Terminal Digital Input

If the weight signal from the scale is a digital datum that satisfy the following conditions, connect it
to the IN2 terminal via a contact module of process I/O.
Also use the IN2 terminal when inputting digital data of weight signals that satisfy the above
condition, from a software I/O.
Number of bits: 32 bits or less
Code: Binary or BCD
IN3 Terminal Sign Bit Input

Connect the sign bit of weight signal digital data to the IN3 terminal.
The sign bit indicates the sign of data. The length of this bit is 1 bit. “0” and “1” indicate positive
and negative, respectively.
IN4 Terminal Ready Bit Input

The ready bit transmits the timing of when the weight signals sent as digital data can be read. The
length of this bit is 1 bit.
Connect the ready bit to the IN4 terminal.
Use the Function Block Detail Builder to define the control action direction of the ready bit.
Ready-bit Action Direction: Select “Direct” or “Reverse.”
The default is “Direct.”
The table below shows actions of the IN4 terminal ready bit input:
Table 1.23-2 IN4 Terminal Ready Bit Input
Action specification Ready bit Status

0 Preparing data
Direct action
1 Read ready
0 Read ready
Reverse action
1 Preparing data
OUT Terminal Manipulated Output

The OUT terminal outputs the following manipulated output signals:
• Analog output
• Output to other function blocks
• Contact output of a 2-position or 3-position ON/OFF output
• Data setting of a 2-position ON/OFF output to the switch instrument
• Data setting to switch instrument 1, when a 3-position ON/OFF output is connected to switch
instruments 1 and 2.
OUT2 Terminal Manipulated Output

The OUT2 terminal transmits data setting output to switch instrument 2, when a 3-position ON/OFF
output is connected to switch instruments 1 and 2.
Function of Weight-Totalizing Batch Set Block (BSETU-

3)
The BSETU-3 block performs input processing, control computation processing, output processing,
The only processing timing available for the BSETU-3 block is a periodic startup. Selections available
SEE For more information about the functions common to the BSETU-2 and BSETU-3 blocks, refer to:
ALSO 1.21, "Totalizing Batch Set Blocks (BSETU-2, BSETU-3)"
processing possible for the BSETU-3 block, refer to:
Input Processing Specific to Weight-Totalizing Batch Set Block

(BSETU-3)
The BSETU-3 block performs special input signal conversions.
Control Computation Processing of Weight-Totalizing Batch

Set Block (BSETU-3)
The table below shows the control computation processing functions of the Weight-Totalizing Batch
Set Block (BSETU-3).
Table 1.23-3 Control Computation Processing of Weight-Totalizing Batch Set Block (BSETU-3)
Control
processing
Performs batch operation in accordance with the type of output (analog output,
Batch operation
twoposition ON/OFF output or three-position ON/OFF output).
MAN fallback place when the MAN fallback condition becomes satisfied. However, the emergency
stop action precedes when an input open alarm has occurred.
Block mode change
interlock
mode.
SEE For more information about the control computation processing of the weight-totalizing batch set
ALSO block (BSETU-3), refer to:
1.21.2, "Control Algorithm of Totalizing Batch Set Blocks (BSETU-2, BSETU-3)"
Alarm Processing Specific to Weight-Totalizing Batch Set Block

(BSETU-3)
The “flowrate alarm check,” which is one of the alarm checks performed by the BSETU-3 block, is
specific to this function block.
Data Items - BSETU-3

Table 1.23-4 Data Items of Weight-Totalizing Batch Set Block (BSETU-3) (1/2)

Item Not (*1) (*2)
BSTS Block status ----- NCNT
Alarm detection
AF ----- 0
specificaton
Alarm masking
AOFS ----- 0
specification
PV Flowrate process variable PV engineering unit value SL
SUM Totalizer value x SUM engineering unit value 0
SUM0 Absolute totalized value Δ unit as SUM 0

Cumulative totalized Value in the same engineering
SUM1 x 0
value unit as SUM
SW Command switch x 0, 1, 2, 3, 4 0
LL x SL to SH SL
setpoint
High - limit alarm
PH x SL to SH SH
setpoint
Cumulative deviation Value in the same engineering
DL x 1000
alarm setpoint unit as SUM
Table 1.23-5 Data Items of Weight-Totalizing Batch Set Block (BSETU-3) (2/2)

Item Not (*1) (*2)
High flowrate
MH x MSL to MSH MSH
setpoint
ML Low flowrate setpoint x MSL to MSH MSL
Pre-batch flowrate
PRE x MSL to MSH MSL
setpoint
Leakage predictive Value in the same engineering
LPV x 0
value unit as SUM
ILST Initial forecast value x 0
unit as SUM
PLST Pre-batch setpoint x 0
unit as SUM
BSET Batch setpoint x 0
unit as SUM
LK Leak setpoint x 100
unit as SUM
TU Up time x 0 to 10,000 seconds 0 second
TD Down time x 0 to 10,000 seconds 0 second
TW Batch end wait time x 0 to 10,000 seconds 0 second
ZONE Control step 0 to 11 0
Emergency stop
EMSW x 0, 1 0
switch
Output high-limit
OPHI x MSL to MSH MSH
index
Output low-limit
OPLO x MSL to MSH MSL
index

unit as PV
unit as PV
*2: SUM: Totalizer value
SEE For more information about valid block modes of the BSETU-3 block, refer to:
Block Status of Weight-Totalizing Batch Set Block

(BSETU-3)
Table 1.23-6 Block Status of Weight-Totalizing Batch Set Block (BSETU-3)
Block Status
Level
Symbol Name
STRT Batch Start
IBCH Batch Initialization
STUP Batch Setup
STDY Ready
ERLY Early
PBCH Pre-Batch
1
END Batch End
NCNT Batch Stopped
RSET Reset
EMST Emergency Shutdown
EEMS Emergency Shutdown Completed
RSTR Restart
1.23.1 Input Signal Conversion of Weight-Totalizing Batch Set Block (BSETU-3) Page 1 of 4
1.23.1 Input Signal Conversion of Weight-Totalizing Batch

Set Block (BSETU-3)
▼ Input Signal Conversion
The input signal conversion specific to the Weight-Totalizing Batch Set Block (BSETU-3) includes
three types of methods: “Weight Measurement Conversion,” “SUM Conversion” and “ΔSUM
Conversion.”
Input Signal Conversion of Weight-Totalizing Batch Set

Block (BSETU-3)
Shown below is the block chart for the input signal conversion of the Weight-Totalizing Batch Set
Block (BSETU-3).
Figure 1.23.1-1 Block Chart for Input Signal Conversion of Weight-Totalizing Batch Set Block
(BSETU-3)
As shown in above figure, the combination of input signal conversion includes the following three
types:
• Weight Measurement Conversion
• SUM Conversion
• ΔSUM Conversion
Weight-Totalizing Conversion
Weight-Totalizing Conversion refers to the processing in which the weight input data read from a
weighing machine are converted into the data in the same unit as the integrator value (SUM) to
obtain the absolute integrator value (SUM0).
The following is the computational expression for the absolute integrator value (SUM0):
SUM0 = quantity unit scale factor • input data
Quantity Unit Scale Factor

The quantity unit scale factor is the factor used to convert the input data into the data in the same
unit as integrator value (SUM). For example, if the unit of input data is “g” and that of integrator
value (SUM) is “kg,” the quantity unit scale factor is 0.001.
The setup for quantity unit scale factor can be executed with the Function Block Detail Builder.
Quantity unit scale factor: Within the range between 0.001 to 100000
The default setting is 1.
In the weight measurement conversion, the input data differs by the type of weight signal.
• If the weight signal is an analog signal, the input data is the 0 to 100 % data read from the
connection destination.
• If the weight signal is data read from the communication input, the input data is the data after
communication input conversion.
• If the weight signal is a digital signal, the input data can be obtained as follows:
When the ready bit is “Ready to Read,” the digital data and its sign bit are read for each scan
period and converted into the same format (double-precision floating-point) as the absolute
integrator value (SUM0) to obtain the input data.
If the ready bit is “Not Ready to Read,” the data setting for absolute integrator value (SUM0) is
bypassed while the previous value is latched.
SEE For more information about communication input conversion of the weight-totalizing signals, refer
ALSO to:
“ Communication Input Conversion” in 3.1.1, “Input Signal Conversions Common to
Regulatory Control Blocks and Calculation Blocks” in Function Blocks Overview (IM 33J15A20-
01EN)
Code Conversion
Code conversion is a function that converts the weight signal digital data read from IN terminal 2 to
binary code data. The weight signal digital data that can be read by the BSETU-3 block includes
binary codes and binary coded decimal (BCD) codes. Specify “No” when the weight signal is a binary
code and “BCD” in the case of BCD code using the Function Block Detail Builder, together with the
number of code contacts.
• Number of Code Contacts
Set by the unit of one bit within the range between 1 to 32 bits.
The default setting is 16 bits.
• Code Conversion
Set “BCD” if the input signal is a binary-coded decimal code (BCD) or “No” if it is a binary.
The default setting is “No conversion.”
Weight-Totalizing Conversion Bypass

Under the following circumstances, the weight-totalizing conversion is bypassed.
• The input signal is digital type and the ready bit is in the status of “Not Ready to Read.”
• The data status of the absolute integrator value (SUM0) is not good (BAD or IOP).
When the weight-totalizing conversion is bypassed, the absolute integrator value (SUM0) is not to be
updated, the previous good value is kept.
SUM Conversion
▼ Input Change Protrusion Bypass
SUM conversion refers to the processing in which the integrator value (SUM) is obtained by totalizing
the increment or decrement of the absolute integrator value (SUM0) from the batch start.
The following is the totalization formula for measurement in the incremental or decremental
direction:
• Measurement in the incremental direction: SUM=SUM0-zero point

• Measurement in the decremental direction: SUM=zero point-SUM0
The zero point refers to the absolute integrator value (SUM0) when the control step is 10
(initialization processing at batch start).
If the input change exceeds the input velocity limit setting value, it is considered as an abnormal
input signal so that the integrator value data setting is not executed and the previous value is held.
The data status, however, is not invalid in this case. The input velocity alarm bypass setting is a
value indicated by the process variable change in one scan period. The basic scan period is 1 scan
per 1 second.
The weight measurement direction specification, input velocity alarm bypass specification, and the
setting value for input velocity limit can be defined on the Function Block Detail Builder.
• Weighing Direction
Select “Increase” or “Decrease.”
The default setting is “Increase.”
• Input Velocity Alarm Bypass
Select “Yes” or “No.”
The default setting is “No.”
• Setting value
Set the value between 0 and 1000 in the same unit as SUM.
The cumulative integrator value (SUM1) is the accumulation of integrator values at the end of batch.
The cumulative integrator value (SUM1) is obtained at the end of each batch as follows:
SUM1=SUM1 (cumulative integrator value kept at the end of the previous batch) +SUM
Under the following circumstances, the SUM conversion is bypassed.
When the SUM conversion is bypassed, the integrator value (SUM) is not to be updated, the
previous good value is kept.
ΔSUM Conversion
▼ Flow Time Unit
ΔSUM conversion refers to the function in which the integrator value variation in the specified time
unit is passed to the digital filter. The value variation after digital filter processing is the flow rate
(PV). The following is the computational expression for the ΔSUM.
The PV time unit and scan period in the above formula are in the unit of second.
The flow measurement time unit can be defined on the Function Block Detail Builder.
Flow Time Unit: Select “Second,” “Minute,” “Hour” or “Day.”
The default setting is “Second.”
e.g. Select “Hour” for ton/h and “Minute” for kg/min.
Under the following circumstances, the input signal processing is bypassed.
In these cases, the flow rate value (PV) is not to be updated, the previous good value is kept.
1.23.2 Alarm Processing of Weight-Totalizing Batch Set Block (BSETU-3) Page 1 of 3
1.23.2 Alarm Processing of Weight-Totalizing Batch Set

Block (BSETU-3)
This section describes the “flowrate alarm check,” which is one of the alarm checks performed by
the BSETU-3 block and is specific to this function block.
Flowrate Alarm Check

▼ Flow Check Mask Interval, Flow Check Time Interval, Input Low-Low Limit Alarm, PV High/Low Limit
Alarm
Low-low limit and high and low-limit checks are made upon expiration of a specified period of time,
as shown in Figure below. The specified period of time is called the flowrate check masking interval.
The checks are made by comparing the SUM change (ΔSUM) for the flowrate check time interval
with an alarm setpoint.
Specify the flowrate check masking interval and the flowrate check time interval with the Function
Block Detail Builder.
• Flowrate check masking interval
0 to 10000
10 is assumed by default.
• Flowrate check time interval
0 to 10000
1 is assumed by default.
The flowrate alarm check processing timing of BSETU-3 block is shown below.
Figure 1.23.2-1 Flowrate Check Processing Timing
The flowrate alarm check in the BSETU-3 block consists of the low-low limit check and the high-low
limit check.
Low-Low Limit Check

A low-low limit check (LL) is generated if the value of ΔSUM in the flow check masking interval
converted to a flow measurement falls below the low-low limit alarm setpoint (LL). This check is
operable in control steps 1, 2, 3, 4, and 5.
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.
Alarm Display Priority Specific to Weight-Totalizing

Batch Set Block (BSETU-3)
The following is the order for the alarm display priority specific to the BSETU-3 block:
OOP>IOP>IOP-> LL>HI>LO>LEAK>BDV+>BDV->BEND>BPRE>CNF
When there are absolutely no alarms generated, the alarm status is NR.
Table 1.23.2-1 Alarm Check for the Control Steps (ZONE) of the Weight-Totalizing Batch Set
Block
ZONE(*1)
Alarm
0 1 2 3 4 5 6 7 8 9 10 11
IOP x x x x x x x x x x x x
IOP- x x x x x x x x x x x x
OOP x x x x x x x x x x x x
CNF x x x x x x x x x x x x
LL - x x x x x - - - - - -
HI - x x x x x - - - - - -
LO - - - x - - - - - - - -
BDV + Δ - - - - - - - - - - -
BDV- Δ - - - - - - - - - - -
LEAK x - - - - - - - - - - -
BPRE ▲ x x x x x x x x x x x
BEND ▲ x x x x x x x x x x x
*1: x :Alarm check is executed for the ZONE.
Δ:Alarm check is executed only once when ZONE=7 changes to ZONE=0.
-:Alarm check is not executed for the ZONE.
The alarm is set to normal state (NR).
▲:Alarm check is not executed and the status prior to ZONE=0 is retained.
SEE For more information about the operation of each control step in the BSETU-3 block, refer to:
ALSO " Batch Operation (Analog Output)" in 1.21.2, "Control Algorithm of Totalizing Batch Set
Blocks (BSETU-2, BSETU-3)"
1.24 Velocity Limiter Block (VELLIM) Page 1 of 14
1.24 Velocity Limiter Block (VELLIM)

The Velocity Limiter Block (VELLIM) outputs a change per unit time by limiting it within the velocity
limits. The Velocity Limiter Block may be applied to the control process that the abrupt change need
to be avoided.
Velocity Limiter Block (VELLIM)

▼ Connection
The Velocity Limiter Block (VELLIM) performs control computation processing to the setpoint signals
from other function blocks or setpoint values set by the operator, and outputs a change per unit
time by limiting it within the velocity limits. The velocity limiting processing is executed in the
cascade (CAS) or automatic (AUT) mode.
The Velocity Limiter Block (VELLIM) reads the abruptly changing manipulated output value (MV) of
other function blocks as a cascade setpoint signal, and outputs its change per scan period as a
manipulated output value (MV) by limiting it within the velocity limits. In the automatic (AUT) mode,
the block outputs a change per scan period in the setpoint value (SV) received from outside, such as
operation and monitoring functions, as a manipulated output value (MV) by limiting it within the
velocity limits. Separate velocity limits may be set for upward and downward directions.
The figure below shows the function block diagram of Velocity Limiter Block (VELLIM):
Figure 1.24-1 Function Block Diagram of Velocity Limiter Block (VELLIM)
the Velocity Limiter Block (VELLIM):
Table 1.24-1 Connection Methods and Connected Destinations of I/O Terminals of Velocity
Limiter Block (VELLIM):

Manipulated
OUT x x x x
output
Interlock SW
INT x Δ x x x
input

link block (ADL).
Function of Velocity Limiter Block (VELLIM)

The VELLIM block performs control computation processing, output processing, and alarm
processing.
The only processing timing available for the VELLIM block is a periodic startup. Selections available
ALSO VELLIM block, refer to:
Control Computation Processing of Velocity Limiter Block

(VELLIM)
The table below shows the control computation processing functions of the Velocity Limiter Block
(VELLIM):
Table 1.24-2 Control Computation Processing Functions of Velocity Limiter Block (VELLIM)
Control computation
Description
processing
Velocity limiting Performs velocity limiting to the setpoint value (SV) and obtains a manipulated
computation output value (MV).
remaining one.
Bumpless switching when the block mode has been changed or when the manipulated output value
(MV) has been switched in a downstream block in cascade.
Performs range conversion to the manipulated output value (MV) based on the
Bumpless Output
setpoint value range, and obtains a new setpoint value. This prevents the
switching pushback
manipulated output value from changing abruptly.
MAN fallback Changes the block mode to MAN to forcibly stop the control action. This action

Changes the block mode to AUT when the function block is operating in the CAS
or PRD mode, so that the control action is continued using values set by the
AUT fallback
operator. This action takes place when the AUT fallback condition becomes
satisfied.
Computer failure
function block is operating in the RCAS or ROUT mode. This action takes place
when the computer failure condition becomes satisfied.
Block mode change
interlock
mode.
Alarm Processing Specific to Velocity Limiter Block (VELLIM)

The “deviation alarm check,” which is one of the alarm checks performed by the VELLIM block, is
specific to this function block.
Velocity Limiting Computation

This function executes velocity limiting computation to the setpoint value when the block mode is
automatic (AUT), cascade (CAS) or remote cascade (RCAS), and uses the computed result as a
The velocity limiting computation action varies depending upon whether the rate of SV change is
below or on/over the velocity limits.
The figure below shows an action example of velocity limiting computation:
Figure 1.24-2 Action Example of Velocity Limiting Computation

▼ SV Range
Use the Function Block Detail Builder to set the setpoint value (SV) range:
• SV Range High Limit Value
each.
• SV Range Low Limit Value
each.
The default is 0.0.
When the Rate of Setpoint Value Change Is BELOW the

Velocity Limits
If the rate of SV change is below the velocity limits, the SV value receives velocity limiting
processing and is converted to an MV-range value to be used as an MV.
The computational expression of this velocity limiting computation is shown below:
MVn = MVc
MVc : Manipulated output computed value
MVn : Manipulated output current value
When the Rate of Setpoint Value Change Is ON or OVER the

Velocity Limits
If the rate of SV change is on or over the velocity limits, the SV value receives velocity limiting
processing and is converted to an MV-range value to be used as a manipulated output value. The
computational expressions of this velocity limiting computation are shown below:
MVn = MVn-1 + Dmp (When ΔMV≥Dmp)
MVn = MVn-1 - Dmm (When ΔMV≤-Dmm)
ΔMV = MVc - MVn-1
• Dmp
A per-scan rate-of-change value in the MV range, converted from the upward velocity limit value
(DMVP).
• Dmm
A per-scan rate-of-change value in the MV range, converted from the downward velocity limit
value (DMVM).
Set Parameters of Velocity Limiting Computation

The parameters of velocity limiting computation:
When 1 is set for the velocity limiting bypass switch (BPSW), the velocity limiting bypass function is
enabled. If 0 is set for the BPSW, the velocity limiting bypass function is disabled.
• Upward velocity limit value (DMVP)
Set engineering unit data between 0 and the SV scale span range limit.
• Downward velocity limit value (DMVM)
Set engineering unit data between 0 and the SV scale span range limit.
• Velocity limiting time unit (TU)
Select “0 (1 second)” or “1 (1 minute).”
• Bypass switch (BPSW)

Select “0 (limited)” or “1 (not limited).”

The control output action of Velocity limiter block is “positional type.” The result of velocity limiting
computation is output as the current manipulated output value (MV).

setpoint high limit (SVH) and setpoint low limit (SVL), and recognizes setpoint values (SV) within this
range as a valid one.
Blocks"

Figure 1.24-3 Relationship Among Setpoint Values (SV, CSV and RSV)
block.

(RSV).

value (CSV).

value (RSV).
Bumpless Switching
▼ Output Pushback
The bumpless switching function switches the function block mode or switches the cascade
connected downstream block’s manipulated output value (MV) without causing its own manipulated
output value (MV) to change abruptly (i.e., bumpless switch).
The type of bumpless switching performed by the Velocity Limiter Block (VELLIM) is “output
pushback.”
In the manual (MAN) or initialization manual (IMAN) mode, the output pushback function sets as a
setpoint value (SV), a SV-range value converted from the manipulated output value (MV). Also,
when the block mode is not remote output (ROUT) or off-service (O/S), the remote manipulated
output value (RMV) is caused to track the manipulated output value (MV). The figure below shows
the action of output pushback:
Figure 1.24-4 Output Pushback
Use the Function Block Detail Builder to set the output pushback.
Output pushback: Select “Yes” or “No.”
Using the output pushback function enables a balanceless bumpless switching of block modes from
manual (MAN) to automatic (AUT).
The following figure shows an example of bumpless cascade closing in a control loop:
Figure 1.24-5 Output Pushback and Output Tracking When Cascade Is Open
1. When cascade connection is open, the output tracking function causes the manipulated 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.

manual (IMAN).
manual (MAN), the initialization manual (IMAN) mode will override the manual (MAN) mode. In
other words, any operation to change to the manual (MAN) mode becomes invalid.
The block returns to the original mode as soon as 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
IMAN (AUT)
AUT
SW-91) and cascade connection is switched is off (i.e., the cascade connection is open).
MAN Fallback
established.


The following example shows when the MAN fallback condition is established and vanished:
AUT→MAN
initial cold start.
AUT Fallback


(CAS) to automatic (AUT) so that control can be continued using values set by the operator. When
this condition is established, it indicates that abnormality has been detected in the cascade setpoint
value for some reason.
CAS→AUT
Use the Function Block Detail Builder to set whether or not to use the AUT fallback.
The AUT fallback condition is established when the AUT fallback is set as “Yes” via the Function
Block Detail Builder and the data status of the cascade setpoint value (CSV) has become invalid
Computer Fail
mode.

computer via control bus communication.
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
execution of the block mode change command (MAN, AUT, CAS) and a remote mode (RCAS,
ROUT).

backup mode.
A backup switch (BSW) is provided in function blocks to define the remote cascade (RCAS) or
remote output (ROUT) mode. The status of this switch determines whether the computer has failed
or recovered. The value of the backup switch (BSW) can be set from a sequence table or other
function blocks.
backup mode:
RCAS
↓ Computer fails
AUT (RCAS)
RCAS
shown as follows:
AUT
↓ ROUT command



• Any block mode change command to obtain an automatic operation state (AUT, CAS, RCAS or
ROUT mode) becomes invalid.

Deviation Alarm Check

▼ Deviation Alarm
The deviation alarm check in the VELLIM block is applicable to the deviation (DV) between the
manipulated output value (MV) converted to a value in the setpoint (SV) range and the setpoint
value (SV).
When the absolute value of the deviation (DV) exceeds the absolute value of the deviation alarm
setpoint (DL), either a positive direction deviation alarm (DV+) or a negative direction deviation
alarm (DV-) is generated. When an alarm has occurred, if the deviation (DV) absolute value drops
lower than the absolute value of the deviation alarm setpoint (DL) minus the hysteresis value (HYS),
the alarm is returned to normal state.
There is no deviation check filter function in the VELLIM block deviation alarm check.
The deviation (DV) that is subject to the deviation alarm check of the VELLIM block is expressed in
the following format.
DV=MVs-SV
MVs : Manipulated output value (MV) after conversion to the SV range

When the deviation (DV) absolute value exceeds the absolute value of the deviation alarm setpoint
(DL) and the deviation is for the positive direction, a positive direction deviation alarm (DV+) occurs.
If the deviation is for the minus direction, a negative direction deviation alarm (DV-) occurs. When
an alarm has occurred, if the deviation (DV) absolute value drops lower than the absolute value of
the deviation alarm setpoint (DL) minus the hysteresis 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 deviation alarm
setpoint (DL), neither a positive direction nor negative direction deviation alarm occurs regardless of
the deviation alarm check.
Figure 1.24-6 Actions of Deviation Alarm Check in the Velocity Limiter Block (VELLIM)
Deviation Alarm Check Settings

The type of deviation alarm check, deviation alarm setpoint (DL), and alarm hysteresis value can be
set.
The type of deviation alarm check is defined by the “deviation alarm check” item in the Function
Block Detail Builder. The types of deviation alarm checks are given below. The default is “detection
of both directions.”
Monitors the deviation of both the positive and negative directions
Monitors the deviation of either the positive or negative direction only
• No alarm
No detection is performed
When single direction is selected for the deviation alarm check type, only the deviation in the
positive direction is monitored when the deviation alarm setpoint (DL) has a plus sign, and only the
deviation in the negative direction is monitored when the deviation alarm setpoint has a minus sign.
Setting of the deviation alarm check type can be performed in the sequence control block or CALCU,
CALCU-C blocks in addition to the Function Block Detail Builder.
The deviation alarm setpoint (DL) is set by the operation and monitoring function.
Deviation alarm setpoint (DL): Engineering unit data within the ±SV scale span range
Default is ±SV scale span.
When single direction is selected for the deviation alarm check type, add the sign (+ or -) for the
direction to be detected to the deviation alarm setpoint (DL) engineering unit data.
Setting for the alarm hysteresis value is done by the Function Block Detail Builder for each
regulatory control block.
Hysteresis: Engineering unit data within the range of 0 to SV scale span, or percentage data for the
SV scale span
The default is 1.0 %.
Data Items - VELLIM
Table 1.24-3 Data Items of Velocity Limiter Block (VELLIM)

Item Not (*1) (*2)
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
SV Setpoint value Δ (*3) SV engineering unit value -----
Value in the same
CSV Cascade setpoint value x -----
Value in the same
RSV Remote setpoint value Δ (*4) -----
Value in the same
DV Deviation -----
MV Manipulated output value Δ (*5) MV engineering unit value -----
Remote manipulated output Value in the same
RMV Δ (*6) -----
value engineering unit as MV
DL Deviation alarm setpoint x ± (SSH - SSL) SSH-SSL
MH x MSL to MSH MSH
limit setpoint
ML x MSL to MSH MSL
limit setpoint
SVH Setpoint high limit x SSL to SSH SSH
SVL Setpoint low limit x SSL to SSH SSL
DMVP Upward velocity limit value x 0 to (SSH - SSL) SSH-SSL
Downward velocity limit
DMVM x 0 to (SSH - SSL) SSH-SSL
value
value
TU Velocity limit timer unit x 0 (second) or 1 (minute) 0
BPSW Velocity limit bypass switch x 0, 1 0
*4: Entry is permitted when the block mode is RCAS

*6: Entry is permitted when the block mode is ROUT
SEE For more information about valid block modes of the VELLIM block, refer to:
1.25 Signal Selector Blocks (SS-H/M/L) Page 1 of 6
1.25 Signal Selector Blocks (SS-H/M/L)

The Signal Selector Blocks (SS-H/M/L) compares the value of the signals from multiple inputs, then
selects 1 signal (PV) as output. This block may be applied to the signal selection loop.
Signal Selector Blocks (SS-H/M/L)

▼ Connection, Constant Input
The Signal Selector Blocks (SS-H/M/L) compare the signals from 2-position input or 3-position input,
then selects the maximum, minimum or medium value signal (PV) as output. The selection may be
operated manually.
The figure below shows the function block diagram of Signal Selector Blocks (SS-H/M/L):
Figure 1.25-1 Function Block Diagram of Signal Selector Blocks (SS-H/M/L)
The Signal Selector Blocks (SS-H/M/L) are classified into three types according to the automatic
selection rule used:
Table 1.25-1 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)
the Signal Selector Blocks (SS-H/M/L):
Table 1.25-2 Connection Methods and Connected destinations of the I/O Terminals of Signal
Selector Blocks (SS-H/M/L)

IN1 Input signal 1 x x x
Manipulated
OUT x Δ x x
output
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 signal 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 (IN1 to IN3): Select “Constant Input” or “Connection Input.”
The default is “Connection Input.”
Functions of Signal Selector Blocks (SS-H/M/L)

The SS-H/M/L blocks perform control computation processing, output processing, and alarm
processing.
The only processing timing available for the SS-H/M/L blocks is a periodic startup. Selections
ALSO SS-H/M/L blocks, refer to:
Control Computation Processing of Signal Selector Blocks (SS-

H/M/L)
The table below shows the control computation processing functions of the Signal selector blocks
(SS-H/M/L):
Table 1.25-3 Control Computation Processing Functions of Signal Selector Blocks (SS-H/M/L)
Control computation
Description
processing
Compares the sizes of three input signal values (RV1, RV2, RV3) and selects the
Signal selection
one that satisfies the condition set by the signal selection switch.
Causes the non-selected input signal values to agree with the selected signal
PV pushback
value (PV).
Signal Selection
The signal selection function selects one signal from multiple input signals. The signal to be selected
varies depending upon the type of the Signal Selector Blocks (SS-H/M/L) and value of the signal
selection switch (SW).
Function of the Signal Selection Switch (SW)

The table below shows the signal selection switch positions and corresponding actions:
Table 1.25-4 Signal Selection Switch Positions and Corresponding Actions
Switch position (SW) Action

0 Holds the selected signal value (PV).
1 Selects input signal 1
4 Selects the result of signal-size comparison (automatic selection).
• 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 unconditionally.
• 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 1.25-5 Invalid Input Signals and Corresponding Actions When Selecting the Medium Value
Input signal with BAD data status Action

RV1 RV2 is selected.
Any two signals RVn that is not BAD is selected.
All signals BAD The previously selected value is stored and the SEL is set to “0.”
The rules of determining the data status of the selected signal value (PV) are shown below:
• When SW = 0
The status of the previous value is stored.
• When SW = 1 to 3
The status of the selected signal value (PV) is determined based on the status of the currently
selected input signal.
• When SW = 4
selected input signal. If all input signals have invalid (BAD) data status, the data status of the
previous value is stored.
Display of Selected Number (SEL)

Whether it is performed automatically or manually, the signal selection action displays the number of
the currently selected input signal (1, 2 or 3) as a selected number (SEL). If the signal selection
switch position is “0” and no signal is selected, SEL becomes 0.
Change in Selected Signal Value (PV)

When the signal selection switch position is 0, the selected signal value (PV) can be set from
operation and monitoring functions or other function block.
Set Parameters of Signal Selection

The parameters of signal selection:
If the signal selection switch position is set above the switch high limit setpoint (SWH) or below the
switch low limit setpoint (SWL) via operation from operation and monitoring functions, an
acknowledgment dialog box appears to prompt for the operator’s confirmation. When confirms, the
switch position can be set outside the high/low limit setpoint range.
• Switch high limit setpoint (SWH)
Select “0,” “1,” “2,” “3” or “4.”
• Switch low limit setpoint (SWL)
Select “0,” “1,” “2,” “3” or “4.”
PV Pushback
The PV pushback function causes the non-selected input signal values (RV1 to RV3) to agree with
the selected signal value (PV).
The PV pushback action targets the input signal values that are obtained via terminal connection to
the input terminals. The PV pushback action is not performed to the input signal values which are
received via data reference or for which “constant input” is specified.
The figure below shows the action of PV pushback:
Figure 1.25-2 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 connected
destination function block enables the signal selection switch position to be changed bumplessly.
The following example shows a control loop where the signal selection switch position is changed
bumplessly.
Figure 1.25-3 PV Pushback and Output Tracking
1. The PV pushback function sets the selected signal value (PV) to the non-selected input signals
(RV1 to RV3).
2. The output value tracking functions of the upstream function blocks connected to the IN1 to IN3
terminals cause the output values of the upstream function blocks to track the values of input
signals (RV1 to RV3).
Data Items - SS-H/M/L

The table below shows the Data Items of Signal Selector Blocks (SS-H/M/L):
Table 1.25-6 Data Items of Signal Selector Blocks (SS-H/M/L)

Data Name Range
Item Not (*1) (*2)
MODE Block mode x ----- O/S(AUT)
Alarm detection
AF ----- 0
specification
Alarm masking
AOFS ----- 0
specification
PV Selected signal value Δ (*3) PV engineering unit value SL
SW Signal selection switch x 0, 1, 2, 3, 4 0
SEL Selected number 0, 1, 2, 3 0
RV1 Input signal value 1 Δ (*4) SL
unit as PV
unit as PV
unit as PV
Switch high limit
SWH x 0 to 4 4
setpoint
Switch low limit
SWL x 0 to 4 0
setpoint

unit as PV
unit as PV
*4: Entry is permitted if “Constant input” is specified
SEE For more information about valid block modes of the SS-H/M/L blocks, refer to:
1.26 Auto-Selector Blocks (AS-H/M/L) Page 1 of 9
1.26 Auto-Selector Blocks (AS-H/M/L)

The Auto-Selector Blocks (AS-H/M/L) compare signals from 2-position or 3-position input from 2 or 3
controller blocks and automatically select one signal as manipulated output value (MV). Auto-
selector blocks may be applied to the override control loops for signal selection.
Auto-Selector Blocks (AS-H/M/L)

▼ Connection, Constant Input
The Signal Selector Blocks (SS-H/M/L) compare the signals from 2-position input or 3-position input,
then selects the maximum, minimum or medium value signal (PV) as output. The selection may be
operated manually.
The figure below shows the function block diagram of Signal Selector Blocks (SS-H/M/L):
An auto-selector control system can be configured by combining an Auto-Selector Blocks (AS-H/M/L)
and 2 to 3 controller blocks. In other words, final control elements of a single loop can be controlled
in such a way that 2 to 3 variables are monitored and maintained on the safe side of their
presetpoint values using a signal selector unit; whereas, in a normal case the final elements are
controlled based on a single variable.
The figure below shows a function block diagram of the Auto-Selector Blocks (AS-H/M/L):
Figure 1.26-1 Function Block Diagram of Auto-Selector Blocks (AS-H/M/L)
The Auto-Selector Blocks (AS-H/M/L) are classified into three types according to the automatic
selection rule used:
Table 1.26-1 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)
the Auto-Selector Blocks (AS-H/M/L):
Table 1.26-2 Connection Methods and Connected destinations of the I/O Terminals of Auto-
Selector Blocks (AS-H/M/L)


IN2 Input signal2 x x x
Manipulated
OUT x x x x
output
Interlock SW
INT x Δ x x x
input
Δ: 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 signal 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 (IN1 to IN3): Select “Constant Input” or “Connection Input.”
The default is “Connection Input.”
When a controller block is terminal connected to the INx terminal of an Auto-

selector blocks (AS-H/M/L), be sure to specify “positional type” for the control
output action of the controller block.
Functions of Auto-Selector Blocks (AS-H/M/L)

The AS-H/M/L blocks perform control computation processing, output processing, and alarm
processing.
The only processing timing available for the AS-H/M/L blocks is a periodic startup. Selections
ALSO AS-H/M/L blocks, refer to:
For more information about the alarm processin, refer to:
Control Computation Processing of Auto-Selector Blocks (AS-

H/M/L)
The table below shows the control computation processing functions of the Auto-Selector blocks (AS-
H/M/L):
Table 1.26-3 Control Computation Processing Functions of Auto-Selector Blocks (AS-H/M/L)
Control computation
Description
processing
Compares the sizes of three input signal values (RV1, RV2, RV3) and selects one
Signal selection
input signal that satisfies the condition set by the signal selection switch.
Automatic control output Performs range conversion to the selected signal value (PV) to obtain a
computation manipulate output value (MV).
Causes the input signal values (RV1, RV2, RV3) to agree with the manipulated
Bumpless Output
output value (MV) to prevent the manipulated output value (MV) from changing
switching pushback
abruptly.
MAN fallback
Block mode change
interlock
operating mode.
Signal Selection
The signal selection function selects one signal from multiple input signals. The signal to be selected
varies depending upon the type of the Auto-Selector Blocks (AS-H/M/L) and value of the signal
selection switch (SW).
The Auto-Selector Blocks (AS-H/M/L) do not output the selected signal value (PV) if the block mode
is manual (MAN) or initialization manual (IMAN). However, as the signal selection function remains
active, the selected number (SEL) and selected signal value (PV) are updated constantly.
Function of the Signal Selection Switch (SW)


0 Holds the selected signal value (PV).

4 Selects the result of signal-size comparison (automatic selection).
• 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 unconditionally.
• 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 1.26-5 Invalid Input Signals and Corresponding Actions When Selecting the Medium Value
Input signal with BAD data status Action

Any two signals RVn that is not BAD is selected.
All signals BAD The previously selected value is stored and the SEL is set to “0.”
The rules of determining the data status of the selected signal value (PV) are shown below:
• When SW = 0
The previous status is stored.
• When SW = 1 to 3
selected input signal.
• When SW = 4
selected input signal. If all input signals are invalid (BAD), the data status of the previous value is
stored.
Display of Selected Number (SEL)

Whether it is performed automatically or manually, the signal selection action displays the number of
the currently selected input signal (1, 2 or 3) as a selected number (SEL). If the signal selection
switch position is “0” and no signal is selected, SEL becomes “0.”
Set Parameters of Signal Selection

The parameters of signal selection.
If the signal selection switch position is set above the switch high limit setpoint (SWH) or below the
switch low limit setpoint (SWL) from operation and monitoring functions, an acknowledgment dialog
box appears to prompt for the operator’s confirmation. When confirms, the switch position can be
set outside the high/low limit setpoint range.
• Switch high limit setpoint (SWH)

Select “0,” “1,” “2,” “3” or “4.”
• Switch low limit setpoint (SWL)
Select “0,” “1,” “2,” “3” or “4.”
Automatic Control Output Computation

The automatic control output computation function determines the manipulated output value (MV)
by performing range conversion to the selected signal value (PV). This action takes place in the
automatic (AUT) mode. The computational expression of range conversion:


an actual manipulated output value (MV). The action that converts the manipulated output change
to an actual manipulated output value (MV) is called, “control/calculation output action.”
The control action applied in the Auto-Selector Blocks (AS-H/M/L) are of “positional type” only. The
result of automatic control output computation is output as a manipulated output value (MV).
Bumpless Switching
output value of the downstream block in cascade loop without causing the manipulated output value
(MV) to change abruptly (i.e., bumpless change).
The action during bumpless switching varies in accordance with the control output action and block
mode status.
The type of bumpless switching performed by the Auto-Selector Blocks (AS-H/M/L) is “output
pushback.”
The output pushback function causes the input signal values (RV1 to RV3) to agree with the
Figure 1.26-2 Output Pushback
In any block mode, the output pushback function of the Auto-Selector Blocks (AS-H/M/L) sets as the
input signal values (RV1 to RV3), the range-converted values based on MV.
Output pushback operates in coordination with the output tracking function of the output processing
targets, and causes the input signal values (RV1 to RV3) to agree with the values at the output
destination blocks cascade connected downstream.
By using the output pushback function in a cascade control loop built around an Auto-Selector Blocks
(AS-H/M/L), the cascade status can be switched without causing an output bump.
Output pushback is performed only to the input signal values received from the input terminals used
for cascade connection. Output pushback is not performed to the input signal values that are
extracted via data reference or used as constants during “constant input.”
The following example shows a control loop where the signal selection switch position is changed
bumplessly.
Figure 1.26-3 PV Pushback and Output Tracking
1. The output tracking function causes the selected signal value (PV) to track data at the output
destination.
2. The output pushback function sets the tracked data as input signals (RV1 to RV3).
3. The output value tracking functions of the upstream function blocks connected to the IN1 to IN3
terminals cause the output values of the upstream function blocks to track the values of input
signals (RV1 to RV3).

manual (IMAN).
manual (MAN), the initialization manual (IMAN) mode will override the manual (MAN) mode.
Therefore, no actions in the manual (MAN) mode take place.

AUT
IMAN (AUT)
AUT
• When the data status at the connected destination of manipulated output value (MV) is
• When the data status at the connected destination of manipulated output value (MV) is a
communication error (NCOM) or output failure (PTPF) (i.e., the cascade connection is open).
• When the connected destination of manipulated output value (MV) is a switch block (SW-33, SW-
91) and the cascade connection is switched off.
• When the connected destination of manipulated output value (MV) is a process output and a
MAN Fallback
established.


AUT→MAN
• When the data status of the process variable (PV) is invalid (BAD) or calibration (CAL).
initial cold start.


invalid.

Data Items - AS-H/M/L

Table 1.26-6 Data Items of Auto-Selector Blocks (AS-H/M/L)

Item Not (*1) (*2)
SW Signal selection switch x 0, 1, 2, 3, 4 0
SEL Selected number 0, 1, 2, 3 0
Value in the same
Value in the same
RV2 Input signal value 2 Δ (*5) -----
Value in the same

RV3 Input signal value 3 Δ (*5) -----
SWH Switch high limit setpoint x 0 to 4 4
SWL Switch low limit setpoint x 0 to 4 0
MH x MSL to MSH MSH
limit setpoint
ML x MSL to MSH MSL
limit setpoint
value
Value in the same
Value in the same
*5: Entry is permitted if “Constant input” is specified
SEE For more information about valid block modes of the AS-H/M/L blocks, refer to:
1.27 Dual-Redundant Signal Selector Block (SS-DUAL) Page 1 of 5
1.27 Dual-Redundant Signal Selector Block (SS-

DUAL)
Dual-Redundant Signal Selector Block (SS-DUAL) may be applied in a redundant configuration to
automatically select one of the two input signals from the same process signal source but received
separately via two signal paths.
Dual-Redundant Signal Selector Block (SS-DUAL)

▼ Connection
The Dual-Redundant Signal Selector Block (SS-DUAL) automatically selects one of the two input
signals. The selected signal is output as process variable (PV).
With the Dual-Redundant Signal Selector Block (SS-DUAL), the redundant configuration become
possible. Similar to the dual-redundant transmitter configuration, the dual-redundant analog I/O
modules are provided in the process input and output configuration.
The figure below shows the function block diagram of Dual-Redundant Signal Selector Block (SS-
DUAL):
Figure 1.27-1 Function Block Diagram of Dual-Redundant Signal Selector Block (SS-DUAL)
the Dual-Redundant Signal Selector Block (SS-DUAL):
Table 1.27-1 Connection Methods and Connected Destinations of I/O Terminals of Dual-
Redundant Signal Selector Block (SS-DUAL):

IN1 Input signal 1 x Δ x x
IN2 Input signal 2 x Δ x x
Manipulated
OUT x Δ x x
output
link block (ADL).
Function of Dual-Redundant Signal Selector Block (SS-

DUAL)
The SS-DUAL block performs input processing, control computation processing, output processing,
The only processing timing available for the SS-DUAL block is a periodic startup. Selections available
ALSO processing possible for the SS-DUAL block, refer to:
Control Computation Processing of Dual-Redundant Signal

Selector Block (SS-DUAL)
The table below shows the control computation processing functions of the Dual-Redundant Signal
Selector Block (SS-DUAL):
Table 1.27-2 Control Computation Processings of Dual-Redundant Signal Selector Block (SS-
DUAL)
Control computation
Description
processing
Tests the data status of two input signal values (RV1, RV2) and selects the one
Signal selection
that satisfies the condition set by the signal selection switch.
Changes the data status of the selected signal (PV) to BAD when two input signals
Selected signal error
have an invalid (BAD) data status or when a deviation alarm is present.
Alarm Processing Specific to Dual-Redundant Signal Selector

Block (SS-DUAL)
The SS-DUAL block performs a special operation triggered by the presence of a deviation alarm in its
alarm processing.
Signal Selection
The signal selection function selects one of multiple input signals.
Signal Selection Switch (SW)

1 Selects input signal 1.
2 Selects input signal 2.
3 Selects input signal 1 or 2, whichever is in normal state.
If the signal selection switch is set to “3” (automatic selection), the data statuses of input signals
RV1 and RV2 are tested, and the signal whose data status is other than invalid (BAD) is selected as
the selected signal value (PV). If both input signals are normal or abnormal, the previously selected
input signal remains selected. If the signal selection switch is set to “1” or “2,” the specified input
signal is selected unconditionally.
Selected Number (SEL)

The currently selected input signal number (1 or 2) is stored as the selected number (SEL) and
displayed.
Non-Selected Signal Value (SV)

The input signal value of the signal not selected is stored as the non-selected signal value (SV) and
displayed.
Selected Signal Error

The selected signal error function changes the data status to invalid (BAD) when the selected signal
error conditions are satisfied.
Table 1.27-4 Selected Signal Error Conditions
Switch position (SW) Error condition

1 Input signal 1 is BAD.
2 Input signal 2 is BAD.
3 Both input signals 1 and 2 are BAD, or a deviation alarm is present.
In a control loop where the selected signal value (PV) that received this selected signal error
processing is input as a process variable, the block mode changes to manual (MAN).
Operations during Deviation Alarm

▼ Deviation Alarm, SS-DUAL PV Update during Deviation Alarm
If the signal selection switch is set to 3, when the difference between the selected signal value (PV)
and non-selected signal value (SV) exceeds the deviation alarm settings value (DL), a deviation
alarm will be generated and the PV data status will become invalid (BAD). While the deviation alarm
is being generated, the PV data value immediately prior to the alarm generation is maintained.
However, if “SS-DUAL PV Update during Deviation Alarm” is selected on the property sheet of the
FCS, the data value will be updated to the selected input value even if the PV data status is BAD due
to a deviation alarm.
The table below shows the difference in operations between when “SS-DUAL PV Update during
Deviation Alarm” is selected and when “Maintain PV value” is selected.
Table 1.27-5 Operations during Deviation Alarm Generation when SW=3
Item Maintain PV Value (Default) Update PV Value

PV data status BAD (Data value invalid) BAD (Data value invalid)
Maintains value immediately prior to
PV data value Updates value
deviation alarm generation
Digital filter No operation Operates
Totalizer No operation No operation
High-limit, low-limit
alarm
Performs check Performs check
High-high limit, low-
low limit alarm
Velocity alarm Does not perform check Does not perform check
Output from OUT
Maintained value is output Updated value is output
terminal
Operation of Performs MAN fallback since the PV data Performs MAN fallback since the PV data
connected function status is BAD. The destination data value status is BAD. The destination data value
block is not updated. is not updated.
Specifying Operation during Deviation Alarm

The operation during deviation alarm generation is specified for each FCS station using the FCS
Properties. The operation cannot be specified for individual SS-DUAL blocks. The specification can
only be changed off-line.
• Update PV Value during SS-DUAL Deviation Alarm Generation:
Select this specification by placing a check in the check box. By default, the PV value immediately
prior to the generation of a deviation alarm is maintained during the alarm generation (the check
box is left blank)
Data Items - SS-DUAL

Table 1.27-6 Data Items of Dual-Redundant Signal Selector Block (SS-DUAL)

Item Not (*1) (*2)
MODE Block mode x ----- O/S(AUT)
Alarm detection
AF ----- 0
specification
Alarm masking
AOFS ----- 0
specification
Non-selected signal Value in the same engineering
SV SL
value unit as PV
DV Deviation 0
unit as PV
RV1 Input signal value 1 Δ SL
unit as PV
RV2 Input signal value 2 Δ unit as PV SL

SW Signal selection switch x 1, 2, 3 3
SEL Selected number 1, 2 1
HH x SL to SH SH
setpoint
LL x SL to SH SL
setpoint
High - limit alarm
PH x SL to SH SH
setpoint
Low - limit alarm
PL x SL to SH SL
setpoint
unit as PV
unit as PV
SEE For more information about valid block modes of the SS-DUAL block, refer to:
1.28 Cascade Signal Distributor Block (FOUT) Page 1 of 6
1.28 Cascade Signal Distributor Block (FOUT)

The Cascade Signal Distributor Block (FOUT) distributes cascade setpoint signals input from
controller blocks to multiple down-stream controller blocks. This block may be applied in a cascade
control loop with multiple function blocks in parallel downstream connected.
Cascade Signal Distributor Block (FOUT)

▼ Connection
The Cascade Signal Distributor Block (FOUT) can distribute cascade signals to as many as 8 function
blocks.
Using the Cascade Signal Distributor Block (FOUT) enables the creation of a cascade control loop
where multiple controller blocks are connected in parallel downstream. The system does not support
to simply link the downstream controller blocks in a chain connection.
The Cascade Signal Distributor Block transmits the cascade open or clamp status of the downstream
controller blocks to the upstream controller block.
The figure below shows the function block diagram of the Cascade Signal Distributor Block (FOUT):
Figure 1.28-1 Function Block Diagram of Cascade Signal Distributor Block
The setpoint value (SV) of the Cascade Signal Distributor Block (FOUT) can be used for data
reference but not for data setting.
The figure below shows an application example of the Cascade Signal Distributor Block (FOUT):
Figure 1.28-2 Application Example of Cascade Signal Distributor Block (FOUT)
Considering the range of each output destination, the cascade setpoint signals to be distributed
undergo range matching. Assume that the SV range of the Cascade Signal Distributor Block (FOUT)
is 0 to 100 %, while the PV ranges of the two downstream controller blocks are 0 to 20.00 KG/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 10.00 KG/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).
the Cascade Signal Distributor Block (FOUT):
Table 1.28-1 Connection Methods and Connected Destinations of I/O Terminals of Cascade
Signal Distributor Block (FPIT):

Manipulated
J01 x x
output 1
Manipulated
J02 x x
output 2
Manipulated
J03 x x
output 3
Manipulated
J04 x x
output 4
Manipulated
J05 x x
output 5
Manipulated
J06 x x
output 6
Manipulated
J07 x x
output 7
Manipulated
J08 x x
output 8
SET terminal can not be connected to the terminals of other station’s function block.
Function of Cascade Signal Distributor Block (FOUT)

The FOUT block performs control computation processing and output processing.
The FOUT block does not have its own processing timing specification. Processing is performed at
the time when the connected function block is executed. When multiple FOUT blocks are connected
in cascade in multiple levels, processing is performed at the time when the function block that is
connected to the top block is executed.
SEE For more information about the types of output processing possible for the FOUT block, see the
ALSO following:, refer to:
Control Computation Processing of Cascade Signal Distributor

Block (FOUT)
The table below shows the control computation processing functions of the Cascade Signal
Distributor Block (FOUT):
Table 1.28-2 Control Computation Processing Functions of Cascade Signal Distributor Block
(FOUT)
Control computation
Description
processing
Performs range matching to the cascade setpoint value (CSV) based on the
Range conversion output
range of the output destination, and uses the result as a manipulated output
distribution
value (MV). Range matching is performed for each output destination.
Obtains a cascade setpoint value (CSV) from the Cascade Signal Distributor
Bumpless Output
Block’s (FOUT) manipulated output value (MVn) via range conversion. Prevents
switching pushback
abrupt changes in the manipulated output by utilizing output tracking.
Output Processing Specific to Cascade Signal Distributor Block

(FOUT)
As part of its output processing, the FOUT block employs a special “output clamp.”
Range Conversion Output Distribution

The control algorithm used by the Cascade Signal Distributor Block (FOUT) is based on range
conversion output distribution.
The range conversion output distribution function performs range matching to the cascade setpoint
value (CSV) set from the upstream function block, for each connected destination based on the
destination range. During range conversion output distribution, range matching is performed using
output range tracking.
Range matching is based on the following expression:
MVn : nth manipulated output value (MV1 to MV8)

SLS : SV scale low limit
MSHn : MVn scale high limit
MSLn : MVn scale low limit
MSHn and MSLn are caused to automatically agree with the scale high limit and low limit of the
output destination via the output range tracking function.

▼ SV Range
each.
each.
The default is 0.0.
Bumpless Switching
mode status.
The type of bumpless switching performed by the Cascade Signal Distributor Block (FOUT) is “output
pushback.”
The output pushback function sets as the setpoint value (SV) and cascade setpoint value (CSV), the
SV-range values converted from the manipulated output value (MVn) via range conversion.
Combining the output pushback and output tracking functions enables the creation of a control loop
where a balanceless bumpless transfer can be performed.
The computational expression of range conversion:
Output pushback is executed when the following occur:

• When the cascade status of one output destination of the Cascade Signal Distributor Block
(FOUT) has changed to close, while the cascade statuses of all other output destinations remain
open.
• In a configuration where a selector switch exists between the Cascade Signal Distributor Block
(FOUT) and the upstream function block in cascade connected to the FOUT, the switch status
has changed from open to close.
• When cascade is open and tracking is enabled at the J01 terminal.
1. When cascade is open, the output tracking function causes the manipulated output value (MVn)
to track data at the output destination.
2. When cascade is closed, the manipulated output value (MVn) is pushed back to the level of SV.
However, this occurs only when one of the above output pushback execution 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-, respectively.
SEE For more information about the output clamp, refer to:
ALSO 4.3, “Output Clamp” in Function Blocks Overview (IM 33J15A20-01EN)
Data Items - FOUT

Table 1.28-3 Data Items of Cascade Signal Distributor Block (FOUT)

Data Name Range
Item Not (*1) (*2)
SV Setpoint value SV engineering unit value SSL
Cascade setpoint Value in the same engineering unit
CSV x SSL
value as SV
Manipulated output Value in the same unit as
MV1 MSL1
value 1 connection destination JO1
MV2 MSL2
MV3 MSL3
MV4 MSL4
MV5 MSL5
MV6 MSL6

MV7 MSL7
MV8 MSL8
*2: SSL: SV scale low limit
MSLn: MVn scale low limit
1.29 Feedforward Signal Summing Block (FFSUM) Page 1 of 12
1.29 Feedforward Signal Summing Block

(FFSUM)
Feedforward Signal Summing Block (FFSUM) adds the feedforward signal to the feedback control
signal then outputs the result. This block may be applied to the control loop that performs
feedforward compensation control or base load control.
Feedforward Signal Summing Block (FFSUM)

▼ Connection
Feedforward Signal Summing Block (FFSUM) adds up the feedback signal (manipulated output
value) input to the IN terminal from an up-stream controller block via cascade connection and the
feedforward signal input to the SET terminal via cascade connection, and outputs the result.
The figure below shows the function block diagram of Feedforward Signal Summing Block (FFSUM):
Figure 1.29-1 Function Block Diagram of Feedforward Signal Summing Block (FFSUM)
the Feedforward Signal Summing Block (FFSUM):
Table 1.29-1 Connection Methods and Connected Destinations of I/O Terminals of Feedforward
Signal Summing Block (FFSUM)

IN FB signal input x x
SET FF setting input x x
Manipulated
OUT x x x x
output
Compensation
BIN x Δ x x
input
Tracking signal
TIN x Δ x x
input
Tracking SW
TSI x Δ x x x
input
Interlock SW
INT x Δ x x x
input
Δ: Connection allowed only when connecting to a switch block (SW-33, SW-91) or an inter-station data
link block (ADL).
Function of Feedforward Signal Summing Block (FFSUM)

The FFSUM block performs control computation processing, output processing, and alarm
processing.
The only processing timing available for the FFSUM block is a periodic startup. Selections available
ALSO FFSUM block, refer to:
Control Computation Processing of Feedforward Signal

Summing Block (FFSUM)
The table below shows the control computation processing functions of the Feedforward Signal
Summing Block (FFSUM):
Table 1.29-2 Control Computation Processings of Feedforward Signal Summing Block (FFSUM)
Control computation
Description
processing
Obtains a manipulated output value (MV) by adding to the feedforward
Feedforward control signal
setpoint value (SV) the feedback input value (PV) corrected by the input
addition
corrected value (VN).
Converts the manipulated output change (ΔMV) during each control
Control output action period to an actual manipulated output value (MV). The control output
actions available with this function block are of “positional type” only.
block is operating automatically. Only “input compensation” is available.
Setpoint value limiter Limits the setpoint value (SV) within the setpoint high/low limits.
remaining one.
Bumpless switching manipulated output value (MV) has been switched in a downstream block
in cascade.
Forcibly sets as the feedback input value, the PV value calculated back
Output
from the MV output destination readback value (MVrb). This prevents the
pushback
Bumpless manipulated output value (MV) from changing abruptly.
switching Prevents abrupt changes in the manipulated output value (MV) by
Balance action initializing the balance term in the manipulated output computational
expression.
becomes satisfied.
Control hold
MAN fallback
the CAS mode, so that the control action is continued using values set by
AUT fallback
the operator. This action takes place when the AUT fallback condition
becomes satisfied.
Feedforward Signal Summing

The feedforward signal summing function adds the feedforward setpoint value (SV) to the feedback
input value (PV), after correcting the latter by the input compensated value (VN), to obtain a
manipulated output value (MV) when the block mode is automatic (AUT) or cascade (CAS).
Figure 1.29-2 Feedforward Signal Summing Action
Signal Addition
The following computational expressions are used to add up the PV value (CV) after input
compensation and feedforward setpoint value (SV) via range conversion to obtain a manipulated
output value (MV).
MV=CVm+SVm+BLn
MV : Manipulated output value

SV : Feedforward setpoint value
SVm : SV after range conversion
CV : PV after input compensation
CVm : CV after range conversion
BLn : Balance term
Feedforward Signal Cut

Depending upon the operating condition of the plant, it is sometimes desirable that Feedforward
Signal Summing be disabled completely. When the feedforward control signal cut switch (FSW) is
turned ON, the feedback input value after input compensation directly receives range conversion
and is output as a manipulated output value (MV) in the automatic (AUT) or cascade (CAS) mode.
MV=CVm+BLn
During the automatic (AUT) or cascade (CAS) mode, the following balance operation is performed to
prevent an output bump as a result of switching the feedforward control signal cut switch.
When the feedforward signal cut switch (FSW) is turned ON, BLn changes to the value shown below:
BLn=MVrb-CVm
MVrb : MV output destination readback value
When the feedforward switch (FSW) is turned OFF, the following computation is performed to
determine the BLn value.
BLn=MVrb-SVm-CVm’

▼ SV Range
each
each
The default is 0.0.
I/O Compensation
The I/O compensation function adds the I/O compensated value (VN) received from outside to the
input signal or output signal of PID control computation, while the controller block is operating
automatically in the automatic (AUT) or cascade (CAS) mode.
Only input compensation is available with the Feedforward Signal Summing Block (FFSUM).
Characteristics of Input Compensation

The following is a computational expression of input compensation:
CVn=PVn+CK (VN+CB)
CVn : Control variable (PV after input compensation)
PVn : Process variable
The figure below shows a processing flow of input compensation:
Figure 1.29-3 Processing Flow of Input Compensation
When creating a base load control system, set the median value of feedforward signals in a normal
operating state as the input compensated value (VN). Also, preset CK and CV to -1.0 and 0.0,
respectively. As a result, the feedback control signal (PV) is compensated by its deviation from the
median value of feedforward signals (SV) and obtained as a final manipulated output value (MV).
Set Parameters of Input Compensation

The parameters of input compensation:
Compensation gain (CK): -10.000 to 10.000
Compensation bias (CB): Arbitrary engineering unit data
The default is 0.
The input compensated value (VN) can not only be set from other function block via data setting,
but also be entered via data reference from the compensation input terminal (BIN).

The control output actions available with the Feedforward Signal Summing Block (FFSUM) are
of “positional type” only. The result of signal summing computation is output as a manipulated
output value (MV).

setpoint high limit (SVH) and setpoint low limit (SVL), and recognizes the setpoint values (SV) only
within this range as valid.
ALSO " Actions in the Automatic or Manual Mode" in " Setpoint Value Limiter" in 1.4, "Control
" Set Parameters of the Setpoint Value Limiter" in " Setpoint Value Limiter" in 1.4, "Control

The setpoint value pushback function sets the same value for the two types of setpoint values (SV,
CSV). The figure below explains the relationship between the setpoint value (SV) and cascade
setpoint value (CSV):
Figure 1.29-4 Relationship between Setpoint Values (SV and CSV)
block.
Action in Automatic (AUT) or Manual (MAN) Mode

Causes the cascade setpoint value (CSV) to agree with the setpoint value (SV). Even when a data
value is set to the setpoint value (SV) from outside the function block, the same value is
automatically set to the cascade setpoint value.
Action in Cascade (CAS) Mode

Causes the setpoint value (SV) to agree with the cascade setpoint value (CSV).
Bumpless Switching
mode status.
The bumpless switching functions available with the Feedforward Signal Summing Block (FFSUM)
include:
• Output pushback
• Balance action
Output Pushback
The output pushback function sets as the feedback input value (PV), the value calculated back from
the MV output destination readback value (MVrb).
The following computational expressions are used to calculate PV back from MVrb:
PV=CV-CK • (VN+CB)
CVm=MVrb-SVm-BLn
BLn: Balance term

In the manual (MAN) or initialization manual (IMAN) mode
BLn=0.0
When output is clamped in the automatic (AUT) or cascade (CAS) mode
BLn=BLn-1
If no input compensation is performed, the feedback input value (PV) in the above computational
expression is the same as CV.
If the calculated value exceeds the feedback input value (PV) range, it is limited to the SH or SL
value.
An abrupt change in the manipulated output value (MV) upon changing of block modes from manual
(MAN) to automatic (MAN), may have a negative impact on the process. Preventing this abrupt
change in the manipulated output value (MV) is called, “bumpless switching.”
Using the output pushback function in combination with the output tracking function enables
balanceless bumpless transfer of a cascade loop.
Figure 1.29-5 Output Pushback and Output Tracking when Cascade is Open
1. When cascade is open, the output tracking function causes MVrb to track data at the output
destination.
2. When cascade is closed, the output pushback function calculates the feedback input value (PV)
from MVrb, and sets the obtained value as PV.
3. The output value tracking function of the upstream block in cascade causes the output value of
the upstream function block to track the feedback input value (PV).
Balance Action
The balance action function adjusts the balance term value when the feedback input value (PV)
changes abruptly during automatic operation in the auto (AUT) or cascade (CAS) mode, in order to
prevent the manipulated output value (MV) from changing abruptly.
An abrupt change in the manipulated output value (MV) during automatic operation may have a
negative impact on the process. Preventing this abrupt change in the manipulated output value (MV)
is called, “bumpless switching.”
The balance action prevents the manipulated output value from changing abruptly when the
feedback input value undergoes an abrupt change.
The balance term is adjusted based on the following computational expressions:
BLn=MVrb-CVm-SVm
CV=PV+CK • (VN+CB)
If no input compensation is performed, CV in the above computational expressions is the same as
PV.
The Feedforward Signal Summing Block (FFSUM) executes this balance action when the feedback
control function block connected upstream in cascade issues a warning that the setpoint value will
be bumped.
The execution conditions of the balance action:
• When a Cascade Signal Distributor Block (FOUT) is connected upstream and the conditional
(CND) status of the upstream output value is canceled.
• A calculation block that does not provide a balance function is connected upstream.
• The initialization manual (MAN) mode is canceled while the output pushback value is being
limited to the MSH or MSL value.
When the balance action is executed, BLn is moved toward 0 by the ramp constant (RP) during each
of the subsequent scan periods, until it finally reaches 0.
Ramp constant Engineering unit data between 0 and the MV scale span range limit
(RP): The default is the MV scale span.
The setting can be changed from operation and monitoring functions during
operation.
Characteristics of Initialization Manual

manual (IMAN).
manual (MAN), the initialization manual (IMAN) mode will precede the manual (MAN) mode. In other
words, any operation to change to the manual (MAN) mode becomes invalid.
mode when initialization condition vanishes.

AUT
IMAN (AUT)
AUT
SW-91) and the switch is disconnected (i.e., the cascade connection is open).
failure or output open alarm has occurred in the process output.
• The output signal is not a pulse-width output and the data status of the input signal at the TIN or
TSI terminal has become invalid (BAD) during the tracking (TRK) mode.
Control Hold
operation (AUT, CAS):
MAN Fallback
established.
Characteristics of Man Fallback


AUT→MAN
• When the data status of the process variable (PV) is invalid (BAD).
initial cold start.
• When the block mode change interlock condition establishes.
AUT Fallback
Characteristics of AUT Fallback


The following examples shows when the AUT fallback condition is established:
CAS→AUT
Use the Function Block Detail Builder to define whether or not to use the AUT fallback.

Characteristics of Block Mode Change Interlock

• Any block mode change command to obtain an automatic operation state (AUT or CAS mode)
becomes invalid.

Data Items - FFSUM

Table 1.29-3 Data Items of Feedforward Signal Summing Block (FFSUM)

Item Not (*1) (*2)
PV Feedback input signal value PV engineering unit value SL
SV Feedforward setpoint value x SV engineering unit value SSL
Feedforward control signal Value in the same

CSV x SSL
cascade setpoint engineering unit as PV
MH x MSL to MSH MSH
limit setpoint
ML x MSL to MSH MSL
limit setpoint
VN Input compensation value x ----- 0.0
RP Ramp constant x 0 to (MSH - MSL) MSH - MSL
Remote manipulated output Value in the same
RMV x MSL
value engineering unit as MV
Feedforward control signal cut
FSW x 0, 1 0
switch
Value in the same
Value in the same
SSH: SV scale high limit
SEE For more information about valid block modes of the FFSUM block, refer to:
1.30 Non-Interference Control Output Block (XCPL) Page 1 of 9
1.30 Non-Interference Control Output Block

(XCPL)
Non-Interference Control Output Block (XCPL) adds output compensation signals to the feedback
control signal the outputs the result. This block may be applied to add non-interference
compensation signals to two mutually non-interference control loops.
Non-Interference Control Output Block (XCPL)

▼ Connection
Non-Interference Control Output Block (XCPL) adds output compensation signals to the feedback
control signal (manipulated output value) that are received by the IN terminal from an upstream
control loop via cascade connection.
The figure below shows the function block diagram of Non-Interference Control Output Block (XCPL):
Figure 1.30-1 Function Block Diagram of Non-Interference Control Output Block (XCPL)
The figure below shows an example of mutually non-interacting control using Non-interference
Control Output Blocks (XCPL):
Figure 1.30-2 Example of Mutually Non-Interference Control Using Non-Interference Control

Output Block (XCPL):
the Non-Interference Control Output Block (XCPL):
Table 1.30-1 Connection Methods and Connected destinations of the I/O Terminals of Non-
Interference Control Output Block (XCPL):
Data Data Terminal Process Software Function

I/O terminal
IN FB signal input x x
Manipulated
OUT x x x x
output
Compensation
BIN x Δ x x
input
Tracking signal
TIN x Δ x x
input
Tracking SW
TSI x Δ x x x
input
Interlock SW
INT x Δ x x x
input
link block (ADL).
Function of Non-Interference Control Output Block

(XCPL)
The XCPL block performs control computation processing, output processing, and alarm processing.
The only processing timing available for the XCPL block is a periodic startup. Selections available for
ALSO XCPL block, refer to:
Control Computation Processing of Non-Interference Control

Output Block (XCPL)
The table below shows the control computation processing functions of the Non-Interference Control
Output Block (XCPL):
Table 1.30-2 Control Computation Processings of Non-Interference Control Output Block (XCPL)
Control computation
Description
processing
Non-interference Adjusts the noninteracting compensated value (VN) using the compensation
compensation signal gain (CK) and compensation bias (CB). The adjusted value is added to the
addition feedback input signal value (PV) to obtain a manipulated output value (MV).
Converts the manipulated output change (ΔMV) during each control period to
Control output action an actual manipulated output value (MV). The control output actions available
with this function block are of “positional type” only.
Switches the increasing/decreasing direction of the manipulated output value
Control action direction (MV) in accordance with the increase or decrease in the feedback input signal
(PB). The control action direction of this function block is always “direct.”
Forcibly sets as the feedback input value (PV) the value calculated back from
Output
the manipulated output value (MV). This prevents the manipulated output
Bumpless pushback
value (MV) from change abruptly.
switching
Balance Prevents abrupt changes in the manipulated output value (MV) by initializing
action the balance term in the manipulated output computational expression.
Changes the block mode to IMAN to temporarily suspend the control action.
Initialization manual This action takes place when the initialization manual condition becomes
satisfied.
MAN fallback
Block mode change
interlock
operating mode.
Non-Interference Compensation Signal Addition

The non-interference compensation signal addition function adds the non-interference compensated
value (VN) to the feedback input signal value (PV) to obtain a manipulated output value (MV) during
the automatic (AUT) mode.
Figure 1.30-3 Non-Interference Compensation Signal Addition Action
The following expression is used to add the non-interference compensated value (VN) to the
feedback input signal value (PV):
MV=PV+CK • (VN+CB)+BLn
MV : Manipulated output value
PV : Feedback input signal value
VN : Non-interacting compensated value
CK : Compensation gain
CB : Compensation bias
BLn : Balance term
• Input compensation gain (CK)

-10.000 to +10.000
The setting can be changed during operation.
• Input compensation bias (CB)
Arbitrary engineering unit data
The default is 0.
The setting can be changed during operation.
The non-interference compensation value (VN) can be set from other function block via data setting
and also can be input via data reference from the compensation input terminal BIN. If the
compensation input terminal (BIN) is not connected, this value is considered to the handled via data
setting.
For the Non-Interference Control Output Block (XCPL), only the MV scale may be defined. The
process variable (PV) uses the same scale as the manipulated output value (MV).

an actual manipulated output value (MV). The control output action applied in the Non-Interference
Control Output Block (ΔCPL) is “positional type” only. The computed result of non-interacting
compensation signal addition is output as a manipulated output value (MV).

The control action direction function switches the increasing/decreasing direction of the manipulated
output value (MV) in accordance with the increase or decrease in the feedback input signal value
(PV).
The manipulated output value (MV) changes in the same direction as the change in the process
variable (PV) in “direct action,” while the manipulated output value (MV) changes in the opposite
direction to the change in the process variable (PV) in “reversed action.”
The control output action of the Non-Interference Control Output Block (XCPL) is always “direct
action.”
Bumpless Switching
mode status.
The bumpless switching functions available with the Non-Interference Control Output Block (XCPL)
include:
• Output pushback
• Balance action
Output Pushback
The output pushback function sets as the feedback input value (PV), the value calculated back from
the manipulated output value (MV).
The following computational expression is used to calculate the manipulated output value (MV):
PV=MVrb-CK • (VN+CB)-BLn
MVrb : MV output destination readback value
BLn : Balance term
In the manual (MAN) or initialization manual (IMAN) mode
BLn=0.0
When output is clamped in the automatic (AUT)
BLn=BLn-1
Output pushback is executed in the following conditions:
• In the manual (MAN) mode
• When the mode status is initialization manual (IMAN)
• When output is clamped in the automatic (AUT) mode
If the calculated value exceeds the PV range, it is limited to the MSH or MSL value.
Using the output pushback function in combination with the output tracking function enables
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 manipulated output
value (MV), and sets the obtained value as the feedback input value (PV).
3. The output value tracking function of the upstream block in cascade causes the output value of
the upstream function block to track the feedback input value (PV).
Balance Action
The balance action function adjusts the balance term value when the feedback input value (PV)
changes abruptly during automatic operation in the auto (AUT) or cascade (CAS) mode, in order to
prevent the manipulated output value (MV) from changing abruptly.
The BLn is adjusted by the following computational expression. Using the balance action prevents
the manipulated output value from changing abruptly when the feedback input value undergoes an
abrupt change.
BLn=MVrb-PV-CK • (VN+CB)
The Non-Interference Control Output Block (XCPL) executes this balance action when the feedback
control function block connected upstream in cascade issues a warning that the setpoint value will
be bumped.
The following are execution conditions of the balance action:
• When a Cascade Signal Distributor Block (FOUT) is connected upstream and the conditional
(CND) status of the upstream output value is canceled
• A calculation block that does not provide a balance function is connected upstream
• The initialization manual (MAN) mode is canceled while the output pushback value is being
limited to the MSH or MSL value
When the balance action is executed, BLn is moved toward “0” by the ramp constant (RP) during
each of the subsequent scan periods, until it finally reaches “0.”
Ramp constant (RP): Engineering unit data between 0 and the MV scale span range limit.
The default is the MV scale span.
Observe the following rules when creating a control system that includes a
Non-Interference Control Output Block (XCPL):
• Always specify “velocity type” for the control output action of the upstream
controller blocks in cascade.
• Specify “output limiters” or “output velocity limiters” for the upstream
controller blocks in cascade in such a way that no limiting action will
actually take place.
• Specify “No” for the “output compensation” specification of the upstream
controller blocks in cascade.
• To manually control the loop, change the block mode of the Non-
Interference Control Output Block (XCPL) to manual (MAN).
Characteristics of Initialization Manual

manual (IMAN).
manual (MAN), the initialization manual (IMAN) mode will override the manual (MAN) mode. In
other words, any operation to change to the manual (MAN) mode becomes invalid.

AUT
IMAN (AUT)
AUT
SW-91) and the connection is switched off (i.e., the cascade connection is open).
• The output signal is not a pulse-width output and the data status of the input signal at the TIN or
TSI terminal has become invalid (BAD) during the tracking (TRK) mode.
MAN Fallback
established.
Characteristics of Man Fallback


AUT→MAN
• When the data status of the feedback input signal (PV) is invalid (BAD).
initial cold start.

Characteristics of Block Mode Change Interlock

The following actions take place:

invalid.

Data Items - XCPL

Table 1.30-3 Data Items of Non-Interference Control Output Block (XCPL)

Item Not (*1) (*2)
Value in the same
PV Feedback input signal value MSL
MH x MSL to MSH MSH
limit setpoint
ML x MSL to MSH MSL
limit setpoint
VN Input compensation value x ----- 0.0
RP Ramp constant x 0 to (MSH - MSL) MSH - MSL
value
SEE For more information about valid block modes of the XCPL block, refer to:
1.31 Control Signal Splitter Block (SPLIT) Page 1 of 11
1.31 Control Signal Splitter Block (SPLIT)

Control Signal Splitter Block (SPLIT) is capable of distributing the manipulated output signals from
the upstream control loop to two output destinations via a signal distribution switch. This block may
be applied to the loops when split the upstream signal to multiple downstream control loops with
different operation ranges.
Control Signal Splitter Block (SPLIT)

▼ Connection
Control Signal Splitter Blocks (SPLIT) may be applied to the multiple downstream control loops with
different operation ranges.
The figure below shows the function block diagram of Control Signal Splitter Block (SPLIT):
Figure 1.31-1 Function Block Diagram of Control Signal Splitter Block (SPLIT)
Data setting cannot be performed to the manipulated output values (MV1, MV2) of the Control
Signal Splitter Block (SPLIT).
the Control Signal Splitter Block (SPLIT):
Table 1.31-1 Connection Methods and Connected Destinations of I/O Terminals of Control Signal
Splitter Block (SPLIT)

Manipulated
OUT1 x x x x
output 1
Manipulated
OUT2 x x x x
output 2
Function of Control Signal Splitter Block (SPLIT)

The SPLIT block performs control computation processing, output processing, and alarm
processing.
The only processing timing available for the SPLIT block is a periodic startup. Selections available
ALSO SPLIT block, refer to:
Control Computation Processing of Control Signal Splitter

Block (SPLIT)
The table below shows the control computation processing functions of the Control Signal Splitter
Block (SPLIT):
Table 1.31-2 Control Computation Processing Functions of Control Signal Splitter Block (SPLIT)
Control computation
Description
processing
Signal distribution with
Obtains two manipulated output values (MV1, MV2) based on the process
output destination
variable (PV).
switching
Switches the increasing/decreasing direction of the manipulated output value
(MVn) in accordance with the increase or decrease in the setpoint value (SV).
MV output action direction
The control action direction of this function block is set for each output
destination.
remaining one.
Bumpless Balance Prevents abrupt changes in the manipulated output value (MV) by initializing the
switching action balance term in the manipulated output computational expression.
Changes the block mode to AUT when the function block is operating in the CAS
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.
Computer failure
function block is operating in the RCAS mode. This action takes place when the
computer failure condition becomes satisfied.
Output Processing Specific to Control Signal Splitter Block

(SPLIT)
As part of its output processing, the SPLIT block employs a special “output clamp.”
Signal Distribution with Output Destination Switching

The figure below shows the control signal splitter action:
Figure 1.31-2 Control Signal Splitter Action

▼ SV Range
• SV Range high Limit Value
each.
each.
The default is 0.0.
Manipulated Output Value Computation

▼ MVn Operation Range
The Control Signal Splitter Block (SPLIT) gives two manipulated output values (MV1, MV2) calculated
from the process variable (SV). The computational expressions are shown in the later paragraphs.
In the Function Block Detail Builder, user can preset the SV-based action range for two manipulated
outputs (SRH1, SRL1, SRH2, SRL2), the values defined should be within the SV range. The figure
below shows an example of action ranges:
Figure 1.31-3 Control Signal Splitter
Use the Function Block Detail Builder to define the manipulated output value computation:
• MVn Operation Range:
Specify “SRH1,” “SRL1,” “SRH2” and “SRL2” values within the SV range.
The default for “SRH1” and “SRH2” is the SV scale high limit (SSH).
The default for “SRL1” and “SRL2” is the SV scale low limit (SSL).
The two manipulated output values (MV1, MV2) can be obtained by the following expressions when
the SV is meaningful:
MVi=CALCi+BLi (n)
When the MV output action direction is “direct”
When the MV output action direction is “reverse”
MVi : Manipulated output (i=1 or 2)

CALCi : Manipulated output computed value
BLi (n) : Balance term
SV : Setpoint value
MSHi : MVi scale high limit
MSLi : MVi scale low limit
SRHi : MVi action range high limit
SRLi : MVi action range low limit
Signal Distribution Switch

The normal actions of the Control Signal Splitter Block (SPLIT) consist of computing a manipulated
output value for each output point based on the setpoint value and distributing signals to both
output destinations. However, the signal distribution action can be limited to a specific output point
by operating the signal distribution switch (SW).
The table below shows the signal distribution switch positions and corresponding actions:
Table 1.31-3 Signal Distribution Switch Positions and Corresponding Actions:
0 Stops signal distribution.

1 Distributes signals to MV1 only.
2 Distributes signals to MV2 only.
3 Distributes signals to both output points.
The value at the manipulated output point that has not been selected by the signal distribution
switch is always caused to agree with the value at the output destination via output tracking.

an actual manipulated output value (MV). The action to convert a change of the manipulated output
to an actual manipulated output value (MV) is called “control output action.” The control output
actions available with Control Signal Splitter Block (SPLIT) are of “positional type.” The result of
manipulated output computation corresponding to the signal distribution switch position, is output as
the manipulated output value (MV).

▼ MVn Output Direction
The control action direction function switches the increasing/decreasing direction of a manipulated
output value (MVn) corresponding to the increase or decrease in the setpoint value (SV).
The manipulated output value (MV) changes in the same direction as the change of the setpoint
variable (SV) is called “direct action,” while the MV value changing to the reverse direction to the
change of SV is called “reverse action.”
Use the Function Block Detail Builder as define the control action direction:
MV1 Output Direction/MV2 Output Direction: Select “Direct” or “Reverse”
The default is “Direct.”

setpoint high limit (SVH) and setpoint low limit (SVL), and recognizes the setpoint values (SV) only
within this range as valid.
Blocks"

block.
Action in Automatic (AUT) Mode

(RSV).
Action in Cascade (CAS) Mode

value (CSV).
Action in Remote Cascade (RCAS) Mode

value (RSV).
Bumpless Switching
The type of bumpless switching performed by the Control Signal Splitter Block (SPLIT) is “balance
action.”
The balance action adjusts the balance term value when the feedback input value (PV) changes
abruptly during automatic operation in the auto (AUT) or cascade (CAS) mode, in order to prevent
the manipulated output value (MV) from changing abruptly.
Using the balance action enables bumpless switching of block modes from automatic (AUT) to
cascade (CAS).
The balance action prevents the manipulated output value from changing abruptly when the
operating condition of the plant has changed. The following computational expression is used to
adjust BLi:
BLi (n)=MVRBi-CALCi
BLi (n) : Balance term (i=1 or 2)
MVRBi : Manipulated output readback value
CALCi : Manipulated output computed value
The execution conditions of the balance action (switching of operating conditions):
• When signal distribution is started after the setting of the signal distribution switch (SW) has
been changed
• When the initialization manual condition is canceled during signal distribution
• When an initialization request is issued from an upstream block in cascade during signal
distribution
• When an initialization request is issued from an output destination function block during signal
distribution
When the balance action is executed, BLi is moved toward “0” by the specified value of ramp
constant (RP) during each of the subsequent scan periods, until it finally reaches “0.”
• MV1 ramp constant (RP1)
Set engineering unit data between 0 and the MV1 scale span range limit.
The default is the MV1 scale span.
• MV2 ramp constant (RP1)
Set engineering unit data between 0 and the MV2 scale span range limit.
The default is the MV2 scale span.
TIP Initialization requests from upstream blocks are issued automatically.

manual (IMAN).

AUT
IMAN (AUT)
AUT
The initialization manual condition for the Control Signal Splitter Block (SPLIT) is satisfied in the
following cases:
• When SW=1 and the initialization manual condition is established at the connected destination of
the OUT1 terminal.
• When SW=2 and the initialization manual condition is established at the connected destination of
the OUT2 terminal.
• When SW=3 and the initialization manual condition (same as above) is satisfied at the connected
destinations of the OUT1 and OUT2 terminals.
SW-91) and the cascade connection is switched off (i.e., the cascade connection is open).
AUT Fallback

Once the AUT fallback condition establishes, the block mode will remain automatic (AUT) even after

The following example shows when the AUT fallback condition is established:
CAS→AUT
Use the Function Block Detail Builder to define whether or not to use the AUT fallback.
Computer Fail
(RCAS) mode temporarily and switches to the computer backup mode.

When the function block mode is remote cascade (RCAS), the function block receives the setpoint
value (SV) or manipulated output value (MV) from a supervisory system computer via control bus
communication.
When the computer fails, the block changes mode to the preset computer backup mode (AUT or
CAS) which indicates that an abnormality has been detected in the supervisory computer. When the
computer recovers, the block returns to the mode before the change.
The following actions take place when the computer failure condition exist and a block mode change
command from AUT or CAS to RCAS is sent:
1. When a block mode change command from AUT or CAS to RCAS is sent while the computer fails
(BSW=ON), the function block does not switch to the computer backup mode directly but
switches to the transient state mode first.
execution of the block mode change command (AUT, CAS) and a remote mode (RCAS).
the Function Block Detail Builder (AUT, CAS) and a remote mode (RCAS).
mode changes to remote cascade (RCAS).

remote cascade (RCAS) mode and switches the mode to the computer backup mode.
A backup switch (BSW) is provided in function blocks to define the remote cascade (RCAS) mode.
The status of this switch determines whether the computer has failed or recovered. The value of the
backup switch (BSW) can be set from a sequence table or other function blocks.
mode other than remote cascade (RCAS)
backup mode:
RCAS
↓ Computer fails
AUT (RCAS)
RCAS
Select “AUT” or “CAS” as the mode to be switched to when the computer becomes down.
The default is “AUT.”
Output Clamp
The output clamp is a function that limits the manipulated output value (MV) in such a way that it
cannot be changed to a value greater than or less than the current output value. The status where
the manipulated output value (MV) is limited in this way is called the output clamp status.
In the SPLIT block, the output clamp statuses for manipulated output values MV1 and MV2
respectively are indicated as data status high limit clamp (CLP+) and low limit clamp (CLP-).
The clamp status of the cascade setpoint value (CSV) is as follows:
• When SW=0
There is no clamp data status.
• When SW=1
When the MV1 output operation is direct, the clamp status is the same as for MV1. For reverse
operation, if MV1 is CLP+ status, then the status is CLP-, if MV1 is CLP- status, then the status is
CLP+.
• When SW=2
When the MV2 output operation is direct, the clamp status is the same as for MV2. For reverse
operation, if MV2 is CLP+ status, then the status is CLP-, if MV2 is CLP- status, then the status is
CLP+.
• When SW=3
If output operation is direct and both MV1 and MV2 are CLP+ status, or if output operation is
reverse and MV1, MV2 are CLP- status, then the status becomes CLP+. Or, if the output
operation is direct and both MV1 and MV2 are CLP- status, or if the output operation is reverse
and MV1, MV2 are CLP+, then the status becomes CLP-.
SEE For more information about the output clamp, refer to:
ALSO 4.3, “Output Clamp” in Function Blocks Overview (IM 33J15A20-01EN)
Data Items - SPLIT

Table 1.31-4 Data Items of Control Signal Splitter Block (SPLIT)

Item Not (*1) (*2)
MODE Block mode x ----- O/S (AUT)
AFLS Alarm flashing status ----- -----
Alarm detection
AF ----- -----
specification
Alarm masking
AOFS ----- -----
specification
SV Setpoint value x SV engineering unit value SSL
CSV Cascade setpoint value x Value in the same engineering SSL
unit as SV
RSV Remote setpoint value Δ (*3) SSL
unit as SV
Manipulated output
MV1 MV1 engineering unit value MSL1
value 1
Manipulated output
MV2 MV2 engineering unit value MSL2
value 2
MSH1 -
RP1 MV1 ramp constant x 0 to (MSH1 - MSL1)
MSL1
MSH2 -
RP2 MV2 ramp constant x 0 to (MSH2 - MSL2)
MSL2
Signal distributor
SW x 0, 1, 2, 3 0
switch
MSHn: MVn scale high limit
MSLn: MVn scale low limit
*3: Entry is permitted when the block mode is RCAS
SEE For more information about valid block modes of the SPLIT block, refer to:
1.32 Representative Alarm Block (ALM-R) Page 1 of 7
1.32 Representative Alarm Block (ALM-R)

Representative Alarm Block (ALM-R) manages the alarms initiated from up to 16 function blocks.
This block may be applied to inhibit the unnecessary alarm notifications from the function blocks.
Representative Alarm Block (ALM-R)

▼ Representative Alarm
The Representative Alarm Block (ALM-R) controls alarms initiated from up to 16 function blocks. The
block has function to activate or inhibit the alarms sent from other function blocks.
The figure below shows the function block diagram of Representative Alarm Block (ALM-R):
Figure 1.32-1 Function Block Diagram of Representative Alarm Block (ALM-R)
the Representative Alarm Block (ALM-R):
Table 1.32-1 Connection Methods and Connected destinations of the I/O Terminals of
Representative Alarm Block (ALM-R):

Q01 to Alarm
x x (*2) x
Q16 input
*2: Connection allowed to any input terminal only when specifying an annunciator message to a software
I/O.
Function of Representative Alarm Block (ALM-R)

The ALM-R block performs only alarm processing.
The only processing timing available for the ALM-R block is a periodic startup. Moreover, only the
SEE For more information about the types of alarm processing possible for the ALM-R block, refer to:
ALSO " Alarm Processing Possible for Each Regulatory Control" in 1.1.3, "Input Processing, Output
Processing, and Alarm Processing Possible for Each Regulatory Control Block"
Alarm Input Specification

The targets of a maximum of 16 alarm inputs that can be controlled by a Representative Alarm Block
(ALM-R):
• Alarm status of function blocks
• Annunciator messages
To specify an alarm input controlled by the representative alarm, use the Function Block Detail
Builder to specify a tag name for the corresponding function block or annunciator message.
Each function block has a number of alarm items. The alarm processing range, i.e., whether all
alarm items of a function block are regarded as input targets or only some of them are regarded,
can be specified for each input terminal. The alarm processing range specification is determined by
the priority level of the alarm.
Specify one of the following four types of alarm processing ranges for each input terminal:
Table 1.32-2 Alarms under different handling categories
Range setting Target alarms

Full alarm All alarms
Medium-priority alarm or lower Alarms excluding high-priority alarms
Low-priority alarm or lower Alarms excluding high- and medium-priority alarms
Logging alarm or lower Alarms excluding high-, medium- and low-priority alarms
Those alarms excluded from the alarm processing range cannot be controlled collectively by the
Representative Alarm Block (ALM-R). Individual alarms of the annunciator messages or function
blocks that are specified as input targets of the Representative Alarm Block (ALM-R) are notified via
the block. Alarm notifications issued directly to operation and monitoring functions are masked.
However, the target of this alarm masking is limited by priority masking
Representative Alarm Processing

The Representative Alarm Block (ALM-R) checks the status of all alarm inputs and determines its
own alarm status (representative alarm) based on the alarm of the highest priority.
The table below shows the alarm statuses of the Representative Alarm Block (ALM-R):
Table 1.32-3 Table of Alarm Statuses of Representative Alarm Block (ALM-R)
Alarm status Name

NR Normal
HALM High-priority alarm present
MALM Medium-priority alarm present
LALM Low-priority alarm present
RALM Logging alarm present
CNF Connection failure alarm
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 Representative 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 representative
alarm processing.
Input Masking
The input masking function specifies by the setpoint value (SV), which input points are and are not
regarded as a target of representative alarm processing among the 16 alarm input points connected
to the input terminals.
Input masking is performed by setting as setpoint value (SV), an input masking pattern represented
by a numeric value between 0 and 15. The setpoint value (SV) can be changed via setting from
operation and monitoring functions or other function block.
The table below shows the setpoint values (input masking patterns) and corresponding targets of
representative alarm processing:
Table 1.32-4 Setpoint Values and Corresponding Targets of Representative Alarm Processing
SV Target of representative alarm processing

0 No input is regarded as a target of representative alarm processing
1 All inputs are regarded as targets of representative alarm processing
2 to 15 Defined by the user
When the setpoint value (SV) is 2 through 15, the targets of representative alarm processing 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 1.32-5 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 Defined by the user
4 . Y ‘Y’ or ‘N’ or ‘.’
···
16 . Y
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.
When releasing all the alarm inputs from masking, a pattern of SV defined with “N”s for all alarm
inputs should be used.
However, for the alarms that beyond the ALM-R handling scope, the alarm masking cannot be
released by the SV pattern with all “N”s.
For an example, the pattern when SV=2 is defined with all “N”s. If the ALM-R handling scope is
defined with “Medium-priority alarm,” when releasing alarm mask, only the input alarms under the
Medium-priority are released, the masked High-priority alarms cannot be released.
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 destination after the change will
not be masked. Therefore, caution should be exercised when changing the input masking pattern
from “N” to “Y,” from “N” to “.,” or from “.” to “Y.”
Priority Masking
The priority masking function specifies the range of alarm masking via the priority masking switch
(SW) for each alarm of the annunciator message and function block that is connected to a terminal
of the Representative Alarm Block (ALM-R).
Priority masking targets the alarms included in the alarm processing range.
Specification of Priority Masking

Priority masking is specified by setting a numeric value between 0 and 5 for the priority masking
switch. The table below shows the priority masking switch (SW) values and corresponding alarm
masking actions:
Table 1.32-6 Priority Masking Switch Values and Alarm Masking Actions
SW Name Action
0 No masking Does not manipulate the alarm masking status at all.
1 Full alarm masking Performs alarm masking (AOF) to all alarms at once.
Medium-priority Masks medium-priority alarms and alarms of lower priorities.
2
alarm masking Only high-priority alarms are not masked.
Low-priority alarm Masks low-priority alarms and alarms of lower priorities.
3
masking High- and medium-priority alarms are not masked.
Logging alarm Masks logging alarms and alarms of lower priorities.
4
masking High-, medium- and low-priority alarms are not masked.
Masks the alarms whose priority is lower than that of the highest-priority alarm
5 Dynamic masking currently occurred in the connected function block.
Only the alarm of the highest priority at the moment is not masked.
Among all alarms at the alarm inputs of the Representative Alarm Block (ALM-R), those of the
priority (priority level) specified by the value of the priority masking switch (SW) or lower will be
masked. In case of priority mask, all the alarms of the connected function block with lower level
than the alarm of the highest priority level occurred so far will be masked.
The priority masking switch (SW) can be changed by the operator or via setting operation from
other function block.
When the setting of the priority masking switch (SW) is changed, any changes in the alarm masking
status will be limited by the priorities that are included in the alarm processing range specified by
the builder. The table below shows alarm masking ranges for different combinations of the alarm
processing range specification and SW setting:
Table 1.32-7 Alarm Masking Ranges
“Alarm processing range” specification by the builder

SW Medium-priority alarm Low-priority alarm or Logging alarm or
Full alarm
or lower lower lower
0 Alarm masking status is not manipulated at all.
1 Full alarm
Medium-priority alarm or
Medium-priority alarm lower
2 Low-priority alarm or
or lower Logging alarm or
lower
Low-priority alarm or lower
3 Low-priority alarm or lower
lower
4 Logging alarm or lower Logging alarm or lower Logging alarm or lower
5 (*1) (*2) (*3) (*4)
*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.
is lower than that of the most important alarm currently present among medium-priority alarms and
alarms of lower priorities.
is lower than that of the most important alarm currently present among low-priority alarms and alarms
of lower priorities.
is lower than that of the most important alarm currently present among logging alarms and alarms of
lower priorities.
Action Example of Priority Masking

The figure below shows an example of how the alarm masking status changes during priority
masking when dynamic masking (SW=5) is specified:
Figure 1.32-2 Action of Dynamic Masking (SW=5)
In this example, the builder-specified alarm range is assumed to be “All alarms.” The figure is based
on a scenario in which a high-priority alarm, medium-priority alarm and low-priority alarm have
occurred simultaneously at a function block controlled by the Representative Alarm Block (ALM-R),
to depict how the alarm masking status changes, or how the alarm status is recovered in the order
of higher to lower priority alarms.
Among all alarms present, only the alarm of the highest priority is not subject to masking.
Dynamic masking checks the priority level of alarms in each function block. For an example, if a
function block is sending an alarm with high priority level, the new alarms with lower levels will be
masked. While if another function block connected in the same ALM-R is in normal status, an new
alarm with medium level sent from this block will not be masked.
So that it is useful to used dynamic masking for handling alarms with multiple priority levels.
Inhibiting Alarm of Connected Function Block

The alarms of a function block that connected to ALM-R can be inhibited by changing the state of
the priority level switch (SW) on ALM-R block.
• No masking (SW=0)
The current alarm masking status of the input source is held.
This also applies to the action of specifying “N” by switching the setpoint value (SV). Although
the alarms for which “N” is specified are normally unmasked, they are not unmasked if the SW
value is 0.
• Dynamic masking (SW=5)
The alarm masking status of the input source is set every period in accordance with the alarm
occurrence status.
• Other masking (SW=1, 2, 3, 4)
The alarm masking status of the input source is set only when the setting of the priority masking
switch (SW) or SV has been changed.
In some cases the alarm masking status of a function block controlled by the Representative Alarm
Block (ALM-R) may not be changed directly from operation and monitoring functions or via other
means.
During on-line maintenance, merely changing the alarm processing level of

the tag assigned 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 representative alarm itself as

a target of on-line loading, as well.
Data Items - ALM-R

Table 1.32-8 Data Items of Representative Alarm Block (ALM-R)
Data Item Data Name Entry Permitted or Not (*1) Range Default
SV Setpoint value x 0 to 15 1
SW Priority masking switch x 0, 1, 2, 3, 4, 5 0
SEE For more information about valid block modes of the ALM-R block, refer to:
1.33 Pulse Count Input Block (PTC) Page 1 of 5
1.33 Pulse Count Input Block (PTC)

Pulse Count Input Block (PTC) counts process values that are products of pulse signals multiplied by the pulse
conversion coefficient. This block may be applied to count process values obtained by multiplying the input
pulse signals by pulse conversion coefficient.
Pulse Count Input Block (PTC)

▼ Connection
Pulse Count Input Block (PTC) counts process values that are products of pulse signals multiplied by the pulse
conversion coefficient. In addition, the Pulse Count Input Block (PTC) has a preset counter function.
Counting operations of the counter, such as issuing of reset and hold commands, are performed from a
sequence control block, calculation block or other function blocks. The block status that indicates the action
status can be referenced from other function blocks.
The figure below shows the function block diagram of Pulse Count Input Block (PTC):
Figure 1.33-1 Function Block Diagram of Pulse Count Input Block (PTC)
The table below shows the connection methods and connected destinations of the I/O terminals of the Pulse
Count Input Block (PTC):
Table 1.33-1 Connection Methods and Connected Destinations of I/O Terminals of Pulse Count Input Block
(PTC):

I/O terminal Data Data Condition Status Terminal Process Software Function
reference setting testing manipulation connection I/O I/O block
Measurement
IN x Δ x
input
Manipulated
OUT x x x x
output
Δ: Connection allowed only when connecting to a switch block (SW-33, SW-91) or inter-station data link block
(ADL).
Function of Pulse Count Input Block (PTC)

The PTC block performs input processing, control computation processing (count processing), output
The only processing timing available for the PTC block is a periodic startup. Selections available for the scan
period used to execute a periodic startup include the basic scan period, the medium-speed scan period (*1),
and the high-speed scan period.
SEE For more information about the types of input processing, output processing, and alarm processing possible
ALSO for the PTC block, refer to:
1.1.3, "Input Processing, Output Processing, and Alarm Processing Possible for Each Regulatory Control
Block"
Input Processing Specific to Pulse Count Block (PTC)

The PTC block performs special input signal conversions.
Control Computation Processing of Pulse Count Block (PTC)

The PTC block performs count processing as its control computation processing. The count processing contains
the following functions.
• Counter update operation
• Preset counter function
• Pause operation
• Restart operation
Output Processing Specific to Pulse Count Block (PTC)

The PTC block performs special output signal conversions.
Input Signal Conversion of Pulse Count Input Block (PTC)

▼ Pulse Conversion Factor
The input signal conversion for the Pulse Count Input Block (PTC) counts the increments of integrated pulse
count values (P) read from the input connection terminal then multiply it by the pulse conversion factor to
convert it into count value (PV).
The following is the computational expression for the count value (PV):
PVn = Pfactor • (Pn - Pn-1)+PVn-1
P : Integrated pulse count value
Pfactor : Pulse conversion factor
PV : Count value, decimal-point notation is valid, the value returns to 0 when exceeding 8 digits.
The subscripts “n” and “n-1” indicate the number of sampling scan periods.
The setup for the pulse conversion factor can be executed on the Function Block Detail Builder.
Pulse Conversion Factor: Within the range between 0.001 to 1000
Counter Updating Operation

When a counter reset command is received, counting is started after the counter value (PV) is reset to “0.”
Counter reset command is issued by setting the reset command switch (data item: RST) to “1” from operation
and monitoring functions or a sequence control block. The reset command switch (RST) automatically returns
to “0” when the reset command is executed.
When a counter reset command is received, the block status changes to normal (NR). When counting, PV is
updated every scan period.
Figure 1.33-2 Basic Pulse Counting Action
Preset Counter Function

The preset counter function notifies when the count value (PV) has reached the preset number.
Besides this count-up completed notification function based on the presetpoint (PH), the Pulse Count Input
Block (PTC) also has the pre-alarm function by which a warning is issued before the presetpoint is reached.
When the block mode is automatic (AUT), the block status changes to pre-alarm (PALM) or count-up completed
(CTUP) when the following conditions are satisfied:
• Pre-alarm (PALM) status
0≤DV≤DL
DV=PH-PV
DV : Remaining count value
DL : Pre-alarm setpoint (8 digits)
PH : Presetpoint (8 digits)
PV : Count value
• Count-up completed (CTUP) status
PH-PV≤0
PH : Presetpoint (8 digits)
PV : Count value
The pre-alarm (PALM) status and count-up completed (CTUP) status are mutually exclusive. When DV=0, the
pre-alarm (PALM) status is canceled and changes to count-up completed (CTUP).
When the setting is DL=0, the status will never become pre-alarm (PALM).
The setting of PH and DL can be changed during operation as set parameters.
The count value continues to be updated even after the count-up completed (CTUP) status is obtained. When
the count value exceeds 8 digits, PV changes to “0” and the block status returns to normal (NR) before
counting is continued.
Pause Operation
A pause command is issued by setting the hold command switch (data item: HSW) to “1” from operation and
monitoring functions or via other function blocks such as a sequence control block or calculation block. When a
pause command is received, the counter action stops temporarily. The counter value and other data are held
during the pause. The current block status of normal (NR), pre-alarm (PAL) or count-up completed is held,
while a new pause (PAUS) status is added. The block status display on the operation and monitoring functions
shows only the pause (PAUS) status that has a higher priority.
When a counter reset command is received in a pause (PAUS) state, the count value is reset to “0” and the
currently held block status (NR, PALM or CTUP) is changed to NR.
The figure below shows an example of pause/restart actions of the pulse-count block:
Figure 1.33-3 Example of Pause/Restart Actions of the Pulse-Count Block
Restart Operation
The pause command is canceled by setting 0 for the hold command switch (data item: HSW). When the pause
command is canceled, the count action currently in pause (PAUS) is resumed. The pause (PAUS) status is
removed from the block status, and the original status that has been saved is recovered. Updating of the count
value resumes from the value that has been held.
Output Signal Conversion of the Pulse Count Input Block (PTC)

In the Pulse Count Input Block (PTC), a processing specific to the PTC Block takes place when it is connected in
sequence connection.
If the output terminal is defined to the manipulation of sequence connection status, then its status can be
manipulated according to the block status of the PTC Block.
Table 1.33-2 Description of Manipulation for Each Block Status
Block status Description of manipulation

CTUP plus NOT PAUS Status manipulation for the logical value “true” is executed.
(NR or PALM) plus NOT PAUS Status manipulation for the logical value “false” is executed.
PAUS Not valid
Data Items - PTC

Table 1.33-3 Data Items of Pulse Count Input Block (PTC)
Data Entry Permitted or Not Default

Data Name Range
Item (*1) (*2)
BSTS Block status ----- NR
Alarm detection
AF ----- 0
specification
Alarm masking
AOFS specification ----- 0

PV Count value Δ ----- SL
PH Presetpoint x ----- SH
DV Remaining count value ----- -----
DL Pre-alarm setpoint x ----- 0
PL PV initial value 0 0
RST Reset command switch x 0, 1 0
HSW Hold command switch x 0, 1 0
Value in the same engineering unit
as PV
Value in the same engineering unit
as PV
SEE For more information about valid block modes of the PTC block, refer to:
Block Status of Pulse Count Input Block (PTC)

Table 1.33-4 Table Block Status of Pulse Count Input Block (PTC)
Block Status
Level Description
Symbol Name
2 PAUS Pause Pauses pulse counter
CTP Count Up Counter reaches a preset value
1 PALM Pre-Alarm Counter reaches Pre Count Up.
NR Normal Counting or CTUP, PALM not active.
1.34 Control Operations of YS Blocks Page 1 of 1
1.34 Control Operations of YS Blocks

The YS80/YS100 communication blocks (hereinafter referred to as YS blocks) are function blocks
designated to act as gateways for displaying the faceplate of the YS100 SERIES/YEWSERIES
80/YEWSERIES BCS electronic control systems (hereinafter referred to as YS instruments) via the
operation and monitoring function of the HIS. The YS instruments are connected via the ALR121
modules of the FFCS Series/KFCS2/KFCS, via the ACM12 modules of the LFCS2/LFCS/SFCS/PFCS (RS-
422/RS-485 communication modules) or the LCS (loop communication card) of the migrated FCS
(RFCS5, RFCS2). Function block models, such as SLCD and SLPC, are available for respective YS
instruments.
YS Block Functions
The YS block offers the following functions:
• Operation and monitoring of YS instruments from the HIS
Operates and monitors YS instruments via the YS block.
• Cascade control of YS instruments and FCS function blocks
By using the SET terminal of the YS block, a cascade loop can be created for the FCS of the
function block and the YS instruments, which are used as a slave loop.
Similar to the faceplate block, the YS block has no special control algorithm. This function block
simply sends and receives data to/from the YS instruments connected to it.
The YS block is used to operate and monitor YS instruments from the HIS, or to control them from
an FCS or supervisory computer.
Correspondence between Function Block Models and YS

Instruments
See the table below to select the applicable YS block according to the YS instrument to be
connected.
Table 1.34-1 YS Block Model List
Corresponding YS Instrument
Function Corresponding YS80 Corresponding YS
Block Model Instrument BCS Instrument Connected Connected to
via SICU ALR121
YS150,
SLCD SLCD YS170 User-selectable
multifunction mode
YS170 User-
SLPC SLPC YS170, YS150
programmable mode
SLMC SLMC
SMST-111 SMST-111 YS135 YS135
SMST-121 SMST-121 YS136 YS136
SMRT SMRT
SBSD SBSD
SLBC SLBC
SLCC SLCC
STLD STLD
1.34.1 Applying YS Blocks Page 1 of 1
1.34.1 Applying YS Blocks

The YS block is a function block operating on the FCS. YS instruments can be operated and
monitored from the HIS via the YS block on the FCS.
Positioning of the YS Block within the System

Similarly to other function blocks, the YS block is generated with a tag name via the Engineering
function and is executed periodically on the FCS. It can also be connected with other function
blocks. The HIS displays the YS block’s process data or parameters, such as PV, SV, and MV. This
allows for indirect operation and monitoring of YS instruments via the YS block.
The figure below shows the positioning of the YS block within the system.
Figure 1.34.1-1 YS Block Positioning
The YS block and YS instruments are connected via the ALR121/ACM12 on the
FFCS series/KFCS2/KFCS/LFCS2/LFCS/SFCS/PFCS. 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 controller
block.”
SEE For more information about communication time, refer to:

ALSO 7., “YS Instrument Communication” in Communication with Subsystems Using RIO (IM
33J20A20-01EN)
6., “YS Instrument Communication (ALR121)” in Communication with Subsystems Using FIO
(IM 33J20A30-01EN)
1.34.2 Common Specification of YS Blocks Page 1 of 11
1.34.2 Common Specification of YS Blocks

The YS block provides the following common specification of function block models.
• Block Mode Tracking Function
• Data Tracking Function
• Input Processing
• Fully-open/Tightly-shut
• Alarm Processing
• Others
• Processing Timing
Overview of Common Specification of YS Blocks

The following describes common specifications of YS block. Some YS block models may not have
block modes or data items that correspond to the functions described below.
Block Mode Tracking Function

This function synchronizes the YS block mode and the operation mode of the YS instrument. It
notifies the YS instruments of a change made from the HIS or Sequence Control functions to the YS
block mode as an operation change. This function also detects changes in the operation mode of the
YS instruments and changes the YS block mode accordingly.
Data Tracking Function

This function synchronizes process data and various control parameters between the YS block and
YS instruments.
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.
Block Mode Tracking Function
This function synchronizes the YS block mode and the operation mode of the YS instrument. It
notifies the YS instruments of a change made from the HIS or Sequence Control functions to the YS
block mode as an operation change. This function also detects changes in the operation mode of the
YS instruments and changes the YS block mode accordingly.
The operation of a YS instrument, while in cascade mode, is either Analog CAS or Communication
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 Communication CAS is
used.
The block mode change operation will differ between Analog CAS and Communication CAS.
In Communication CAS, do not use the YS block in RCAS or ROUT mode for
the FFCS series/KFCS2/KFCS/LFCS2/LFCS/SFCS/PFCS that communicate with
YS instruments via the ALR121/ACM12, since high-speed communications
cannot be achieved. The YS block can be used in CAS mode.
Mode Changes for Analog CAS

In Analog CAS, set points are entered from other YS instruments.
Figure 1.34.2-1 Connection Example for Analog CAS
When using the YS instrument in Analog CAS, the mode changes will be as shown below.
Figure 1.34.2-2 Mode Changes for Analog CAS
In Analog CAS, the YS instrument’s mode changes are handled in the same way as the YS block’s
mode changes made from the HIS or sequence table. When in MAN mode, neither YS block mode
nor YS instrument’s operation mode can be switched to CAS mode.
In Analog CAS, the cascade setting input value on the YS instrument will be used as an SV in CAS
mode. The YS block matches its SV value to the SV value on the YS instrument side. If the SET
terminal of the YS block is connected, the IMAN status of the master loop will not be changed even
when the mode is switched to CAS. In RCAS or ROUT mode, no controls can be performed from the
supervisory computer.
Mode Changes when Using the Set Terminal in Communication

CAS
In Communication CAS, the mode changes differ depending on whether the SET terminal of the YS
block is used.
If the SET terminal of the YS block is used in Communication CAS, a value entered from the SET
terminal is set in the YS instrument in CAS mode. RCAS and ROUT modes are not available.
Figure 1.34.2-3 Connection when Using the Set Terminal in Communication CAS
When using the SET terminal in Communication CAS, the mode changes will be as shown below.
Figure 1.34.2-4 Mode Changes when Using the SET Terminal in Communication CAS
When mode is changed from AUT to CAS, the YS block will enter CAS mode and the YS instrument
will enter SPC mode.
When changing from MAN mode to CAS mode, it is necessary to change from MAN to AUT first, then
to CAS.
A YS instrument will enter the backup mode when the FCS fails while its YS block is in CAS mode. A
setting on the YS instrument can be set to determine whether the backup mode will be MAN or AUT.
Mode Changes when the SET Terminal is not Used in

Communication CAS
Do not use the FFCS series/KFCS2/KFCS/LFCS2/LFCS/SFCS/PFCS, 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.
Figure 1.34.2-5 Connection Example when the SET Terminal is not Used in Communication CAS
Figure 1.34.2-6 Mode Changes when the SET Terminal is not Used in Communication CAS
During MAN mode, if an attempt is made on the YS instrument to change the mode to CAS, that
operation will be disabled if the SPC/DDC flag of the YS Instrument Internal Status is SPC. If the
SPC/DDC flag is DDC, the YS instrument enters DDC mode, and the YS block enters ROUT mode.
The SPC/DDC flag status is determined by the previous remote mode.
Only AUT mode can be changed to RCAS mode, while only MAN mode can be changed to ROUT
mode.
Mode Changes Specific to the SMST Block
In Communication CAS, do not use the YS block in RCAS or ROUT mode for
the FFCS series/KFCS2/KFCS/LFCS2/LFCS/SFCS/PFCS 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.
Figure 1.34.2-7 Mode Changes of the SMST Blocks
When Analog CAS is applied in the SMST-111 block, the mode will either be MAN or CAS. When
Communication CAS is connected to set terminal of SMST-111 block, the mode will be MAN, CAS,
otherwise the mode will be RCAS. (When the mode is CAS or RCAS, the YS instrument will perform
DDC operation.)
If Analog CAS is applied in the SMST-121 block, the mode will either be MAN or CAS. While, if
communication CAS is applied in the SMST-121 block, the mode will be either MAN or ROUT.
Mode Changes Specific to the SBSD and STLD Blocks

The SBSD and STLD instruments can only operate in AUT mode. AUT or CAS can be selected for the
display, depending on the YS instrument setting. From the YS block side, the mode can be changed
to out of service (O/S), and from O/S to AUT or CAS. The mode may change from O/S to something
other than specified in the YS instrument. This is because the mode first changes to the one
specified in the YS block before switching to the mode specified in the YS instrument.
Fixing to MAN Mode using the Mode Change Interlock Function

The mode can be fixed to MAN via the value of the connection destination of the YS block’s INT
terminal. When the mode change is interlocked, sending a command to the YS block to change the
mode to other than MAN will generate an error. Any attempt to change the mode on the YS
instrument side will be canceled since the mode is forcibly fixed to MAN from the YS block.
Mode Changes in the Event of a Communication Error

When an error occurs in communication with the YS instrument, the YS block enters IMAN mode
(combined mode with the previous modes).
If communication between the YS instrument and FCS is interrupted during the CAS operation
(Communication CAS), the YS instrument enters the backup mode automatically. If the YS
instrument is still in the backup mode after communication has resumed, the YS block issues a
command to the YS instrument to cancel the backup mode.
Data Tracking Function

The Data Tracking Function synchronizes process data and various control parameters between the
YS block and YS instruments.
This function collects control parameters and process data such as PV, SV, and MV from the YS
instruments and sets them as YS block data. If any data is set for the YS block from the HIS, that
data will also be set in the YS instruments via this function.
Each YS instrument model has different process data and control parameters. Accordingly, each YS
block has different process data and control parameters, depending on the corresponding YS
instrument. Some data only exists in the YS block but not in the YS instrument.
Process data and parameters of the YS block can be handled in one of the following manners:
• Only tracks YS instrument data but cannot be changed from the YS block side
Example: PV
• Exchanges data between the YS instrument and YS block
Examples: SV, MV, MH, ML, P, I, D
• Maintains value in the YS block, independent of the YS instrument
Examples: SUM, PH, PL
In certain types of YS instruments, parameters cannot be changed via communication. Such data
can only reference the YS instrument data.
Data relating to the Input Processing and Alarm Processing, such as SUM, PH, and PL, which will be
discussed later, are handled independently from the YS instrument.
Details on which data relates to which function will be explained with the functions of respective
function block models.
Be sure to set batch setpoints (BSET) to the SBSD and SLBC from the HIS
prior to a batch start. Changing a BSET after a batch start may result in an
immediate batch end.
Input Processing
The YS block can perform the following Common Input Processing.
Digital Filter and Calibration functions are not available.
Input Signal Conversion
▼ IOP Detection Value

There are two options for YS block input signal conversions: non-conversion and square root
conversion. Square root conversion can be selected when the connected YS instrument uses the
square-law scale. The YS blocks other than SLCD have only one option that is non-conversion.
An YS block can have its own PV input open high limit and low limit for IOP+/IOP- detection. When
a PV is greater than the value for IOP+ detection limit, the data will be in IOP+ status, vice versa,
when the PV is smaller than the IOP- detection limit, the data will be in IOP- status. IOP detection
value can be specified on Function Block Detail Builder.
IOP Detection Value
• IOP+ Detection Set Value
Can be set between 100 % to 125 %.
• IOP- Detection Set Value
Can be set between -25 % to 0 %.
The default setting is -5.50.
Totalizer
In the YS80 Block (SLCD, SLPC, SLMC, SMST-111, SMST-121, SMRT), the PVs are totalized and the
SUM is created.
The YS BCS Block (SBSD, SLBC, SLCC, STLD) displays the YS instrument SUM without any changes.
To display the correct totalized value, set the SH and SL according to the decimal places on the YS
instruments.
The decimal point positions of PV and SUM can be set independently of the YS
instruments. On the other hand, the YS BCS block sets the same decimal
point positions for SUM and PV. Therefore, when the decimal point positions
are different between PV and SUM on the YS instrument, the decimal point
position of SUM displayed on the YS BCS block differs from that of the YS
instrument.
PV Overshoot
PV is set to an SH value when the IOP+ is detected via the Alarm Processing function. PV is also set
to an SL value when IOP- is detected or when there is an error in communication with the YS
instruments.
Output Signal Processing

When the MV is set to 0 % or 100 % from the YS block, the YS instrument outputs Fully-
open/Tightly-shut values. When the Operation Low Limit Setpoint (ML) and the Manipulated Variable
High Limit Setpoint (MH) are set to 0 % and 100 %, respectively, from the YS block, the ML and MH
on the YS instrument will be -6.3 % and +106.3 %, respectively.
Tight-Shut and Full-Open

An YS instrument can continuously output an MV ranging from -6.3 % and +106.3 %. In MAN
mode, an YS instrument can output an MV less than 0 % and greater than 100 %, as long as the
value is within the above range.
A YS block can output an MV ranging from 0 % to 100 %. When the YS block passes a 0 % MV or a
100 % MV to YS instrument, the YS instrument will output a -6.3 % MV or a 106.3 % MV as Tight-
Shut or Full-Open signals of the YS instrument. When the YS block passes an output signal to YS
instrument between the value of 0 % and 100 %, the YS instrument will output the same output
without change. If a YS block’s ML is set as 0 % and MH is set as 100 %, the ML and MH in the
corresponding YS instrument will be -6.3 % for ML and 106.3 % for MH respectively. This is caused
by the Tight-Shut and Full-Open functionality of the YS instrument. So that if the ML or the MH
needs to be set as 0 % and 100 %, the setting should be performed on YS instrument but not on YS
block. A YS instrument MV can be manipulated on YS block when the YS instrument is in MAN mode
and the YS block is in ROUT mode.
When a YS block is in ROUT mode, it always tracks the values in YS instrument unless the YS block
is being manipulated for passing an MV to the YS instrument. When the MV in the YS instrument is
less than 0 %, the YS block will take it as a 0 % value, while if the MV in the YS instrument is
greater than 100 %, the YS block will take it as a 100 % value.
Manipulated Variable High Limit Setpoint (MH) / Manipulated

Variable Low Limit Setpoint (ML)
The Manipulated Variable High Limit Setpoint (MH) and the Manipulated Variable Low Limit Setpoint
(ML) are specified within the range between -6.3 % and +106.3 % when set from the YS
instrument, and between 0 % and 100 % when set from the YS block. However, if the ML is set to 0
% from the YS block, the ML on the YS instrument will be -6.3 %. Similarly, if the MH is set to 100
% from the YS block, the ML on the YS instrument will be +106.3 %. If you wish to set the ML to 0
% or MH to 100 %, set these values on the YS instrument.
Alarm Processing
▼ Leak Check, Pre-Batch Alarm, Batch End Alarm, Integral Deviation Alarm Level-One, Integral
Deviation Alarm Level-Two
The YS block handles alarms generated on the YS block and some alarms generated on the YS
instruments.
Processing of Alarms Detected by YS Instrument

The YS instrument checks for OOP, IOP, HI, LO, DV+, and DV-. The YS block only acquires the OOP
and reflects it in the alarm status.
The SBSD and SLBC blocks not only acquire the OOP but also the END (Batch End), PRE (Pre-batch),
LEAK (Leak) alarms from the YS instrument and reflects them in the alarm status. The SLCC block
not only acquires the OOP but also DV+ (Level-1 Totalization Deviation Alarm) and HDV (Level-2
Totalization Deviation Alarm) alarms from the YS instrument and reflects them in the alarm status.
Enable or disable the END, PRE, LEAK alarm statuses on SBSD, SLBC blocks, enable or disable the
DV+, HDV alarm statuses on SLCC blocks can be set on Function Block Detail Builder.
Leak Check : Choose [Yes] or [No].
The default setting is [No].
Pre-Batch Alarm : Choose [Yes] or [No].
Batch End Alarm: Choose [Yes] or [No].
Integral Deviation Alarm Level-One: Choose [Yes] or [No].

Integral Deviation Alarm Level-Two: Choose [Yes] or [No].
Processing of Alarms Detected by YS Block

All YS blocks detect IOP/IOP- independently of the YS instrument. When the PV exceeds the IOP+
detection set value, it is considered an IOP. When the PV falls below the IOP- detection set value, it
is considered an IOP-. The detection of IOP or IOP- will not change the block mode.
The YS80 blocks independently check HI, LO, DV+, and DV- as part of the Input Signal Conversion
functions. Alarm setpoints such as PH, PL, and DL are set independently from the YS instrument
parameters.
All YS blocks will generate both an OOP and IOP in the event of an error in communication with the
YS instrument. Thus, the OOP and IOP each contains two meanings, one being the alarm detected
by the YS instruments mentioned previously.
An invalid terminal definition will cause all YS blocks to generate a CNF. Causes of invalid definitions
include when the terminal is not connected to the applicable YS instrument model and when it is not
connected via an ACM12 or an LCS.
SEE For more information about YS block’s alarm checks, refer to:
ALSO 5., “Alarm Processing – FCS” in Function Blocks Overview (IM 33J15A20-01EN)
Others
The YS block has the following functions according to the standard PID blocks.
Setpoint Push-Back
This function equalizes SV, CSV, and RSV according to the mode of the function block.
Table 1.34.2-1 Block Modes and Equalization
Block Mode Equalization Operation

AUT, MAN, ROUT, CAS (analog CAS) SV→ CSV, RSV
CAS (Communication CAS) CSV→ SV, RSV
RCAS RSV→ SV, CSV
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 For more information about Setpoint Push-back and Setpoint Limiter, refer to:
ALSO " Setpoint Value Pushback" in 1.4, "Control Computation Processing Common to Controller
Blocks"
" Setpoint Value Limiter" in 1.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.35 YS Controller Block (SLCD) Page 1 of 4
1.35 YS Controller Block (SLCD)

By connecting the SLCD block to the SLCD Indicating Controller, the SLCD Indicating Controller can
be operated and monitored from the HIS.
YS Controller Block (SLCD)

▼ Connection
The connection of the SLCD block and the SLCD Indicating Controller allows the HIS to operate and
monitor the controller.
The figure below shows the function block diagram of the SLCD block.
Figure 1.35-1 Function Block Diagram of the YS Controller Block (SLCD)
The table below shows the connection methods and the connection destinations of SLCD block I/O
terminals.
Table 1.35-1 I/O Terminal Connection Methods and Connection Destinations of YS Controller
Block (SLCD)
Connection Method(*1) Connection Destination(*1)

I/O Terminal Data Data Terminal Process Soft Function
Reference Setting Connection I/O I/O Block
IN YS Instrument x - - x (*2) - -
SET Set Value Input - - x - - x
Interlock Switch
INT x - Δ x x x
Input
*1: x: 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)
*2: Connection is possible only when integrating with YS instruments
Function of YS Controller Block (SLCD)

The SLCD block performs input processing, control computation processing, output processing, and
alarm processing.
The only processing timing available for the SLCD block is a periodic startup. Moreover, only the
SEE For more information about the common functions of the YS blocks, refer to:
ALSO 1.34, "Control Operations of YS Blocks"
processing possible for the SLCD block, refer to:
Control Computation Processing of the YS Controller

Block (SLCD)
Setpoint Push-Back Function

This function equalizes the setpoints (SV), cascade setpoints (CSV), and remote setpoints (RSV) in
respect to the YS block mode.
SEE For more information about the setpoint pushback function, refer to:
ALSO " Setpoint Push-Back" in " Others" in 1.34.2, "Common Specification of YS Blocks"
" Setpoint Value Pushback" in 1.4, "Control Computation Processing Common to Controller
Blocks"
Setpoint Limiter Function

and low limits when the YS block is in RCAS mode (SPC mode).
SEE For more information about the setpoint limiter function, refer to:
ALSO " Setpoint Limiter" in " Others" in 1.34.2, "Common Specification of YS Blocks"
Blocks"
Mode Change Interlock Function

This function locks the YS block mode to MAN depending on the connection destination of the YS
block’s INT terminal.
SEE For more information about the mode change interlock function, refer to:
ALSO " Fixing to MAN Mode using the Mode Change Interlock Function" in " Block Mode
Tracking Function" in 1.34.2, "Common Specification of YS Blocks"
Data Items of YS Controller Block (SLCD)

Table 1.35-2 Data Items of YS Controller Block (SLCD)

Item Not (*1)
O/S
MODE Block mode xx -
(MAN)
ALRM Alarm status - - NR
AFLS Alarm flashing status - - 0
Alarm detection
AF - - 0
specification
Alarm masking
AOFS - - 0
specification
PV Process variable - PV engineering unit value SL
SV Setpoint xx SL
unit as PV
CSV Cascade setpoint - SL
unit as PV
RSV Remote setpoint - SL
unit as PV
unit as PV
MV Manipulated output value xx 0.0 to 100.0 % 0
Remote manipulated
RMV - 0.0 to 100.0 % 0
output value
PH High-limit alarm setpoint ▲ SL to SH SH
PL Low-limit alarm setpoint ▲ SL to SH SL
DL Deviation alarm setpoint ▲ ± (SH-SL) 0
Manipulated variable high
MH xx (*2) 0.0 to 100.0 % 100
setpoint
Manipulated variable low
ML xx (*2) 0.0 to 100.0 % 0
setpoint
SVH Set high setpoint x SL to SH SH
SVL Set low setpoint x SL to SH SL
P Proportional band xx (*2) 6.3 to 999.9 % 100
I Integral time xx (*2) 1 to 9999 sec 20
D Derivative time xx (*2) 0 to 9999 sec 0
OPHI Output high-limit index x 0.0 to 100.0 % 100
OPLO Output low-limit index x 0.0 to 100.0 % 0
UAID User application ID x - 0

SH PV scale high limit - -
unit as PV
SL PV scale low limit - -
unit as PV
MSH MV scale high limit - Fixed to 100 % 100 %
MSL MV scale low limit - Fixed to 0 % 0%
RAW Raw input data - 4096 to 20480 (*3) -
*1: xx: Entry is permitted from both the YS instrument and HIS
x: Entry is permitted from the HIS only
▲: Data for the YS block can be entered from the HIS, the data for the YS instrument can be entered
from the YS instrument
-: Entry is not permitted
*2: MH, ML, P, I, D parameters can be entered from the HIS with SLCD Style E only.
*3: The range of 4096 (0x1000) to 20480 (0x5000) corresponds to the range of 0.0 % to 100.0 %.
SEE For more information about valid block modes of the SLCD block, refer to:
1.36 YS Programmable Controller Block (SLPC) Page 1 of 4
1.36 YS Programmable Controller Block (SLPC)

By connecting the SLPC block to the SLPC programmable indicating controller, the SLPC
programmable indicating controller can be operated and monitored from the HIS.
YS Programmable Controller Block (SLPC)

▼ Connection
The connection of the SLPC block and the SLPC programmable indicating controller allows the HIS to
operate and monitor the controller.
The figure below shows the function block diagram of the SLPC block.
Figure 1.36-1 Function Block Diagram of the YS Programmable Controller Block (SLPC)
The table below shows the connection methods and the connection destinations of SLPC block I/O
terminals.
Table 1.36-1 I/O Terminal Connection Methods and Connection Destinations of YS
Programmable Controller Block (SLPC)

I/O Terminal Data Data Terminal Process Software Function
Interlock
INT x - Δ x x x
Switch Input
Function of YS Programmable Controller Block (SLPC)

The SLPC block performs input processing, control computation processing, output processing, and
alarm processing.
The only processing timing available for the SLPC block is a periodic startup. Moreover, only the
processing possible for the SLPC block, refer to:
Control Computation Processing of the YS

Programmable Controller Block (SLPC)

Blocks"

Blocks"

Data Items of YS Programmable Controller Block (SLPC)

Table 1.36-2 Data Items of YS Programmable Controller Block (SLPC)

Item Not (*1)
O/S
(MAN)
Alarm detection
AF - - 0
specification
Alarm masking
AOFS - - 0
specification
SV Setpoint xx SL
unit as PV
unit as PV
unit as PV
unit as PV
Remote manipulated
RMV - 0.0 to 100.0 % 0
output value
MH xx 0.0 to 100.0 % 100
setpoint
ML xx 0.0 to 100.0 % 0
setpoint
I Integral time xx 1 to 9999 sec 20
D Derivative time xx 0 to 9999 sec 0
BS (*3) Computation parameter 1 xx -8.000 to 8.000 0.0
CS (*3) Computation parameter 2 xx -8.000 to 8.000 1.000
AUX1 (*3) Auxiliary input 1 - 0.0 to 100.0 % -

unit as PV
unit as PV
*2: If the parameter is entered on HIS, the parameter may not be properly transmitted to SLPC instrument
so that it is necessary to set the parameter on SLPC instrument.
*3: BS and CS correspond to P01 and P02 of the SLPC instrument. AUX1 to AUX3 correspond to analog
output registers Y4 to Y6 of the SLPC instrument.
SEE For more information about valid block modes of the SLPC block, refer to:
1.37 YS Programmable Controller Block with Pulse Width Output (SLMC) Page 1 of 4
1.37 YS Programmable Controller Block with

Pulse Width Output (SLMC)
By connecting the SLMC block to the SLMC Programmable Indicating Controller with Pulse Width
Output, the SLMC Programmable Indicating Controller with Pulse Width Output can be operated and
monitored from the HIS.
YS Programmable Controller Block with Pulse Width

Output (SLMC)
▼ Connection
The connection of the SLMC block and the SLMC Programmable Indicating Controller Block with
Pulse Width Output allows the HIS to operate and monitor the controller.
The figure below shows the function block diagram of the SLMC block.
Figure 1.37-1 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 1.37-1 I/O Terminal Connection Methods and Connection Destinations of YS
Programmable Controller Block with Pulse Width Output (SLMC)

Interlock
INT x - Δ x x x
Switch Input
Function of YS Programmable Controller Block with

The SLMC block performs input processing, control computation processing, output processing, and
alarm processing.
The only processing timing available for the SLMC block is a periodic startup. Moreover, only the
processing possible for the SLMC block, refer to:
Control Computation Processing of the YS

Programmable Controller Block with Pulse Width
Output (SLMC)

Blocks"

Blocks"

Data Items of YS Programmable Controller Block with

Table 1.37-2 Data Items of YS Programmable Controller Block with Pulse Width Output (SLMC)

Item Not (*1)
O/S
(MAN)
Alarm detection
AF - - 0
specification
Alarm masking
AOFS - - 0
specification
SV Setpoint xx SL
unit as PV
unit as PV
unit as PV
unit as PV
Remote manipulated
RMV - 0.0 to 100.0 % 0
output value
MH xx 0.0 to 100.0 % 100
setpoint
ML xx 0.0 to 100.0 % 0
setpoint

I Integral time xx 1 to 9999 sec 20
BS (*3) Computation parameter 1 xx -8.000 to 8.000 0.0
CS (*3) Computation parameter 2 xx -8.000 to 8.000 1.000
unit as PV
unit as PV
*2: If the parameter is entered on HIS, the parameter may not be properly transmitted to SLMC instrument
so that it is necessary to set the parameter on SLMC instrument.
*3: BS and CS correspond to P01 and P02 of the SLMC instrument. AUX1 to AUX3 correspond to analog
output registers Y4 to Y6 of the SLMC instrument.
SEE For more information about valid block modes of the SLMC block, refer to:
1.38 YS Manual Station Block with SV Output (SMST-111) Page 1 of 4
1.38 YS Manual Station Block with SV Output

(SMST-111)
By connecting the SMST-111 block to the SMST-111 AUTO/MANUAL Station for SV Setting, the
SMST-111 AUTO/MANUAL Station for SV Setting can be operated and monitored from the HIS.
YS Manual Station Block with SV Output (SMST-111)

▼ Connection
The connection of the SMST-111 block and the SMST-111 AUTO/MANUAL Station for SV Setting
allows the HIS to operate and monitor the station.
The figure below shows the function block diagram of the SMST-111 block.
Figure 1.38-1 Function Block Diagram of the YS Manual 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 1.38-1 I/O Terminal Connection Methods and Connection Destinations of YS Manual
Station Block with SV Output (SMST-111)

Interlock
INT x - Δ x x x
Switch Input
Function of YS Manual Station Block with SV Output
(SMST-111)
The SMST-111 block performs input processing, control computation processing, and alarm
processing.
The only processing timing available for the SMST-111 block is a periodic startup. Moreover, only the
For more information about the types of input processing and alarm processing possible for the
SMST-111 block, refer to:
Control Computation Processing of the YS Manual

Station Block with SV Output (SMST-111)

Blocks"

Blocks"

Data Items of YS Manual Station Block with SV Output

(SMST-111)
Table 1.38-2 Data Items of YS Manual Station Block with SV Output (SMST-111)

Item Not (*1)
O/S
(MAN)
Alarm detection
AF - - 0
specification
Alarm masking
AOFS - - 0
specification
SV Setpoint xx SL
unit as PV
unit as PV
unit as PV
High-limit alarm
PH ▲ SL to SH SH
setpoint
Low-limit alarm
PL ▲ SL to SH SL
setpoint
unit as PV
unit as PV
SEE For more information about valid block modes of the SMST-111 block, refer to:
1.39 YS Manual Station Block with MV Output Lever (SMST-121) Page 1 of 3
1.39 YS Manual Station Block with MV Output

Lever (SMST-121)
By connecting the SMST-121 block to the SMST-121 AUTO/MANUAL Station for MV Setting, the
SMST-121 AUTO/MANUAL Station for MV Setting can be operated and monitored from the HIS.
YS Manual Station Block with MV Output Lever (SMST-

121)
▼ Connection
The connection of the SMST-121 block and the SMST-121 AUTO/MANUAL Station for MV Setting
allows the HIS to operate and monitor the station.
The figure below shows the function block diagram of the SMST-121 block.
Figure 1.39-1 Function Block Diagram of the YS Manual 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 1.39-1 I/O Terminal Connection Methods and Connection Destinations of YS Manual
Station Block with MV Output Lever (SMST-121)

Interlock
INT x - Δ x x x
Switch Input
Function of YS Manual Station Block with MV Output
(SMST-121)
The SMST-121 block performs input processing, control computation processing, output processing,
The only processing timing available for the SMST-121 block is a periodic startup. Moreover, only the
processing possible for the SMST-121 block, refer to:
Control Computation Processing of the YS Manual

Station Block with MV Output Lever (SMST-121)

Data Items of YS Manual Station Block with MV Output

Lever (SMST-121)
Table 1.39-2 Data Items of YS Manual Station Block with MV Output Lever (SMST-121)

Item Not(*1)
O/S
(MAN)
Alarm detection
AF - - 0
specification
AOFS - - 0
Alarm masking
specification
Remote manipulated
RMV - 0.0 to 100.0 % 0
output value
MH xx 0.0 to 100.0 % 100
setpoint
ML xx 0.0 to 100.0 % 0
setpoint
unit as PV
unit as PV
SEE For more information about valid block modes of the SMST-121 block, refer to:
1.40 YS Ratio Set Station Block (SMRT) Page 1 of 5
1.40 YS Ratio Set Station Block (SMRT)

By connecting the SMRT block to the Ratio Set Station (SMRT), the SMRT Ratio Set Station can be
operated and monitored from the HIS.
YS Ratio Set Station Block (SMRT)

▼ Connection
The connection of the SMRT block and the SMRT Ratio Set Station allows the HIS to operate and
monitor the station.
The figure below shows the function block diagram of the SMRT block.
Figure 1.40-1 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 1.40-1 I/O Terminal Connection Methods and Connection Destinations of YS Ratio Set
Station Block (SMRT)

Interlock
INT x - Δ x x x
Switch Input
Function of YS Ratio Set Station Block (SMRT)

The SMRT block performs input processing, control computation processing, output processing, and
alarm processing.
The only processing timing available for the SMRT block is a periodic startup. Moreover, only the
processing possible for the SMRT block, refer to:
Control Computation Processing of the YS Ratio Set

Station Block (SMRT)

Blocks"

Blocks"

▼ SV Range, Internally Computed Ratio Range
SMRT Ratio Set Instrument converts the ratio setpoint value (SV), based on the engineering unit,
into an internal ratio value (SVn) for internal computation.
The communication between the SMRT Ratio Set Instrument and the SMRT function block only
conveys the internal ratio value (SVn), the setpoint value based on the engineering unit (SV) is not
conveyed.
In order to make the setpoint value (SV) on the SMRT function block equal to the setpoint value
(SV) on SMRT Ratio Set Instrument, when the SMRT function block receives or sends the internal
ratio value, the conversion based on the scale settings is performed with the following formulae:
When SMRT function block converts the received internal ratio svn into its SV:
When SMRT function block sends it SV to SMRT Ratio Set Instrument, it converts the SV into the
internal ratio svn:
SV : Ratio Setpoint value

svn : Internal ratio value communicated between the SMRT Ratio Set Instrument and the SMRT
function block
svnHi : Upper limit of Internal ratio value
svnLo : Lower limit of Internal ratio value
SVH : Upper limit of SV
SVL : Lower limit of SV
If both the upper limit and lower limit of the internal ratio value are set with 0.0, the scale
conversion cannot be performed. Under this circumstance, the internal ratio value in SMRT Ratio Set
Instrument will become the setpoint value of SMRT function block.
The ranges of the SMRT function block ratio setpoint value (SV) and the internal ratio value (svn)
can be defined on the function block details builder.
The upper limit of (SSH) and the lower limit (SSL) of the SMRT function block SV range should be
the same as the upper limit of (SEH) and the lower limit (SEL) of SMRT Ratio Set Instrument SV
range respectively. The upper limit (svnHi) and the lower limit (svnLo) of the SMRT function block
svn range should be the same as the upper limit of the range (SRH) and the lower limit (SRL) of
SMRT Ratio Set Instrument SVn range respectively.
• Upper Limit of SV Range
Up to 7 digits including sign and decimal point
Default 8.000
• Lower Limit of SV Range
Up to 7 digits including sign and decimal point
Default 0.000
• Upper Limit of svn Range
A value between 0.000 and 8.000
Default 8.000
• Lower Limit of svn Range
A value between 0.000 and 8.000
Default 0.000
Data Items of YS Ratio Set Station Block (SMRT)

Table 1.40-2 Data Items of YS Ratio Set Station Block (SMRT)

Item Not (*1)
O/S
(MAN)
Alarm detection
AF - - 0
specification
Alarm masking
AOFS - - 0
specification
SV (*2) Ratio setpoint xx SSL to SSH SL
CSV Cascade ratio setpoint - SSL to SSH SL
RSV Remote ratio setpoint - SSL to SSH SL
Remote manipulated
RMV - 0.0 to 100.0 % 0
output value
DL Lamp constant xx ± (SSH-SSL) 100.0
MH xx 0.0 to 100.0 % 100
setpoint
ML xx 0.0 to 100.0 % 0
setpoint
SVH Ratio setting high setpoint x SSL to SSH SSH
SVL Ratio setting low setpoint x SSL to SSH SSL
EB External bias - 0.0 to 100.0 % 0
P1 Computation parameter 1 xx -800.0 to 800.0 0
CALC Computed value - 0.0 to 100.0 % 0.0 %

unit as PV
unit as PV
SSH (*3) SV scale high limit - Fixed to 8.000 8.000
SSL (*3) SV scale low limit - Fixed to 0.000 0.000
*2: The setpoint value (SV) of SMRT function block should be the same as the setpoint value (SV) based on
the engineering unit in SMRT Ratio Set Instrument.
*3: The upper limit of (SSH) and the lower limit (SSL) of the setpoint value (SV) in SMRT function block SV
should be the same as the upper limit of (SEH) and the lower limit (SEL) of the setpoint value (SV) in
SMRT Ratio Set Instrument respectively.
SEE For more information about valid block modes of the SMRT block, refer to:
1.41 YS Batch Set Station Block (SBSD) Page 1 of 3
1.41 YS Batch Set Station Block (SBSD)

By connecting the SBSD block to the Batch Set Station (SBSD), the SBSD Batch Set Station can be
YS Batch Set Station Block (SBSD)

▼ Connection
The connection of the SBSD block and the SBSD Batch Set Station allows the HIS to operate and
monitor the station.
The figure below shows the function block diagram of the SBSD block.
Figure 1.41-1 Function Block Diagram of the YS Batch Set Station Block (SBSD)
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 1.41-1 I/O Terminal Connection Methods and Connection Destinations of YS Batch Set
Station Block (SBSD)

YS
IN x - - x (*2) - -
Instrument
Function of YS Batch Set Station Block (SBSD)

The SBSD block performs input processing and alarm processing.
The only processing timing available for the SBSD block is a periodic startup. Moreover, only the
SBSD block, refer to:
Control Computation Processing of YS Batch Set Station

Block (SBSD)
There are no items subject to the SBSD block’s control computation processing.
Data Items of YS Batch Set Station Block (SBSD)

Table 1.41-2 Data Items of YS Batch Set Station Block (SBSD)

Item Not (*1)
O/S
(AUT)
AF Alarm detection specification - - 0
AOFS Alarm masking specification - - 0
PV Instantaneous flow - PV engineering unit value SL
SV Command switch xx 0 to 8 0
RSV Remote command switch - 0 to 8 0
MV Demand output value xx 0.0 to 100.0 % 0
PH High-limit flow setpoint xx SL to SH SH
PL Initial flow setpoint xx SL to SH SL
VL Initial flow totalizer limit value xx SL to SH SL
BSET Batch setpoint xx Engineering unit value 0
Instrumental error compensation
CC1 xx -1.0000 to 1.0000 0.0000
coefficient a (*2)
First-order compensation
CC2 xx -1.0000 to 1.0000 0.0000
coefficient b (*3)(*2)
Second-order compensation
CC3 xx -1.0000 to 1.0000 0.0000
coefficient g (*3)(*2)
CC4 Density r (*4) xx 0.5000 to 1.2000 1.0000
Value in the same
Value in the same
*2: The decimal point position for the coefficient can be specified on the YS instrument, while that is fixed
to 4 decimal places on the YS BCS block. Therefore, the decimal point position of the YS BCS block will
not match that of the YS instrument unless the coefficient on the YS instrument also has 4 decimal
places. For example, if the YS BCS block shows the coefficient to 3 decimal places, e.g. 1.000, the YS
BCS block will display 0.1000.
*3: Valid only when the general secondary expression is selected for the correction computation. Setting a
new value for CC2 will change the CC4 data.
*4: Valid only when the ASTM method is selected for the correction computation. Setting a new value for
CC4 will change the CC2 data.
SEE For more information about valid block modes of the SBSD block, refer to:
1.42 YS Batch Controller Block (SLBC) Page 1 of 3
1.42 YS Batch Controller Block (SLBC)

By connecting the SLBC block to the Batch Controller (SLBC), the SLBC Batch Controller can be
YS Batch Controller Block (SLBC)

▼ Connection
The connection of the SLBC block and the SLBC Batch Controller allows the HIS to operate and
The figure below shows the function block diagram of the SLBC block.
Figure 1.42-1 Function Block Diagram of the YS Batch Controller Block (SLBC)
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 1.42-1 I/O Terminal Connection Methods and Connection Destinations of YS Batch
Controller Block (SLBC)

Interlock
INT x - Δ x x x
Switch Input
Function of YS Batch Controller Block (SLBC)

The SLBC block performs input processing, control computation processing, output processing, and
alarm processing.
The only processing timing available for the SLBC block is a periodic startup. Moreover, only the
processing possible for the SLBC block, refer to:
Control Computation Processing of the YS Batch

Controller Block (SLBC)

Data Items of YS Batch Controller Block (SLBC)

Table 1.42-2 Data Items of YS Batch Controller Block (SLBC)

Item Not (*1)
O/S
(MAN)

SV Command switch xx 0 to 8 0
RSV Remote command switch - 0 to 8 0
RMV - 0.0 to 100.0 % 0
value
PH High-limit flow setpoint xx SL to SH SH
PL Initial flow setpoint xx SL to SH SL
VL Initial flow totalizer limit value xx SL to SH SL
BSET Batch setpoint xx Engineering unit value 0
CC1 xx -1.0000 to 1.0000 0.0000
coefficient α (*2)
CC2 xx -1.0000 to 1.0000 0.0000
coefficient β (*3)(*2)
CC3 xx -1.0000 to 1.0000 0.0000
coefficient γ (*3)(*2)
CC4 Density ρ (*4) xx 0.5000 to 1.2000 1.0000
Value in the same
Value in the same
not match that of the YS instrument unless the coefficient on the YS instrument also has 4 decimal
places. For example, if the YS BCS block shows the coefficient to 3 decimal places, e.g. 1.000, the YS
BCS block will display 0.1000.
SEE For more information about valid block modes of the SLBC block, refer to:
1.43 YS Blending Controller Block (SLCC) Page 1 of 4
1.43 YS Blending Controller Block (SLCC)

By connecting the SLCC block to the SLCC Blending Controller, the SLCC Blending Controller can be
YS Blending Controller Block (SLCC)

▼ Connection
The connection of the SLCC block and SLCC Blending Controller allows the HIS to operate and
The figure below shows the function block diagram of the SLCC block.
Figure 1.43-1 Function Block Diagram of the YS Blending Controller Block (SLCC)
The table below shows the connection methods and the connection destinations of SLCC block I/O
terminals.
Table 1.43-1 I/O Terminal Connection Methods and Connection Destinations of YS Blending
Controller Block (SLCC)

Interlock
INT x - Δ x x x
Switch Input
Function of YS Blending Controller Block (SLCC)

The SLCC block performs input processing, control computation processing, output processing, and
alarm processing.
The only processing timing available for the SLCC block is a periodic startup. Moreover, only the
processing possible for the SLCC block, refer to:
Control Computation Processing of the YS Blending

Controller Block (SLCC)

SV Range Display Format of YS Blending Controller

Block (SLCC)
▼ SV Range Display Format
This sets the SV Range Display Format so the decimal point of the ratio setting value (SV) of the
SLCC block will match that of the SLCC Blending Controller Block.
Setting the SV Range Display Format

The SV Range Display Format is setting using the Function Block Detail Builder.
• SV Range Display Format: Select one from [0] to [4].
[0]: 10000
[1]: 1000.0
[2]: 100.00
[3]: 10.000
[4]: 1.0000
Default is [2].
Data Items of YS Blending Controller Block (SLCC)

Table 1.43-2 Data Items of YS Blending Controller Block (SLCC)
Data Entry Permitted

Item or Not (*1)
O/S
(MAN)
SV Ratio setpoint xx SSL to SSH 0
RSV Remote ratio setpoint - SSL to SSH 0
RMV - 0.0 to 100.0 % 0
value
DV Totalized deviation value - Engineering unit value 0
Instrumental error
CC1 xx -1.0000 to 1.0000 0.0000
compensation coefficient α (*2)
CC2 xx -1.0000 to 1.0000 0.0000
coefficient β(*2)(*3)
CC3 xx -1.0000 to 1.0000 0.0000
CC4 Density ρ (*4) xx 0.5000 to 1.2000 1.0000
Value in the same
Value in the same
10000, 1000.0, 100.00, 100.00
SSH SV scale high limit -
10.000, or 1.0000 % (*5) %
0, 0.0, 0.00, 0.000, or 0.0000
SSL SV scale low limit - 0.000
% (*5)
not match that of the YS instrument unless the coefficient on the YS instrument also has 4 decimal places. For
example, if the YS BCS block shows the coefficient to 3 decimal places, e.g. 1.000, the YS BCS block
will display 0.1000.
*5: The High and low limit of SV scale varies with the setting in [SV Range Display Format] on the builder.
For an YS instrument (SLCC), the SV range can be set between 0 to 299.99, but for a SLCC block, the
setting will be limited to 0 to 99.99 % when the option 2 is selected for the setting of [SV Range
Display Format]. When changing this setting, the decimal point position will be changed accordingly.
SEE For more information about valid block modes of the SLCC block, refer to:
1.44 YS Totalizer Block (STLD) Page 1 of 3
1.44 YS Totalizer Block (STLD)

By connecting the STLD block to the Totalizer (STLD), the STLD Totalizer can be operated and
monitored from the HIS.
YS Totalizer Block (STLD)

▼ Connection
The connection of the STLD block and the STLD Totalizer allows the HIS to operate and monitor the
totalizer.
The figure below shows the function block diagram of the STLD block.
Figure 1.44-1 Function Block Diagram of the YS Totalizer Block (STLD)
The table below shows the connection methods and the connection destinations of STLD block I/O
terminals.
Table 1.44-1 I/O Terminal Connection Methods and Connection Destinations of YS Totalizer
Block (STLD)

YS
IN x - - x (*2) - -
Instrument
Function of YS Totalizer Block (STLD)

The STLD block performs input processing and alarm processing.
The only processing timing available for the STLD block is a periodic startup. Moreover, only the
STLD block, refer to:
Control Computation Processing of YS Totalizer Block

(STLD)
There are no items subject to the STLD block’s control computation processing.
Data Items of YS Totalizer Block (STLD)

Table 1.44-2 Data Items of YS Totalizer Block (STLD)

Item Not (*1)
O/S
(AUT)
CC1 xx -1.0000 to 1.0000 0.0000
coefficient α (*2)
CC2 xx -1.0000 to 1.0000 0.0000
coefficient β (*3)(*2)
CC3 xx -1.0000 to 1.0000 0.0000
CC4 Density ρ (*4) xx 0.5000 to 1.2000 1.0000
Value in the same
Value in the same
to 4 decimal places on the YS BCS block. Therefore, the decimal point position of the YS BCS block will not
match that of the YS instrument unless the coefficient on the YS instrument also has 4 decimal places.
For example, if the YS BCS block shows the coefficient to 3 decimal places, e.g. 1.000, the YS BCS
block will display 0.1000.
SEE For more information about valid block modes of the STLD block, refer to:
Revision Information Page 1 of 1
Revision Information
Title : Function Blocks Reference Vol.1
Manual No. : IM 33J15A30-01EN
Feb. 2021/7th Edition/R6.08 or later

1.4 Deleted description in “ Reset Limit Function.”
1.17 Added description in " MAN Fallback Condition.”
May 2020/6th Edition/R6.07.10

1.1.3 Updated descriptions in “ Alarm Processing Possible for Each Regulatory Control.”
Aug. 2019/5th Edition/R6.07

Preface Updated descriptions in “ Trademark Acknowledgements.”
Aug. 2018/4th Edition/R6.06

1.1.3 Updated descriptions in " Output Processing Possible for Each Regulatory Control."
1.4 Updated descriptions in “ Control Hold.”
1.28 Updated descriptions in “ Function of Cascade Signal Distributor Block (FOUT).”
Apr. 2017/3rd Edition/R6.04

1.1.2 Added descriptions in " Manipulated Output Value (MV)."
1.18.3 Added descriptions in " Pulse Width Time."
Jun. 2016/2nd Edition/R6.03

1.1.3 Updated descriptions in " Output Processing Possible for Each Regulatory Control."
1.18.2 Updated descriptions in " MAN Fallback Condition.”
Mar. 2015/1st Edition/R6.01

Newly published.

Function Blocks Reference Vol.1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Function Blocks Reference Vol.1

Uploaded by

Copyright:

Available Formats

Introduction Page 1 of 1

Safety Precautions for Use

Indicates that a component such as a power supply switch is turned ON.

Notes on Handling User's Manuals

Warning and Disclaimer

Indicates precautions to avoid a danger that may lead to minor or

Indicates important information required to understand operations or

Indicates referenced content.

Commonly Used Conventions throughout the User's Manuals

• Character string enclosed by braces { }

Conventions Used to Show Key or Button Operations

Conventions Used in Command Syntax or Program Statements

• Characters enclosed by brackets [ ]

• Characters enclosed by separators | |

Copyright and Trademark Notices

Regulatory Control Positioning

1.1 Regulatory Control Blocks

Structure of Regulatory Control Blocks

Figure 1.1-1 Function Block Diagram of the Regulatory Control Block

• IN: Input terminal

Functions of the Regulatory Control Blocks

Control Computation Processing

1.1.1 Types of the Regulatory Control Blocks

Input Indicator Blocks

Block type Code Name

Block type Code Name

Manual Loader Blocks

Block type Code Name

Signal Setter Blocks

Block type Code Name

Signal Limiter Block

Block type Code Name

Signal Selector Blocks

Block type Code Name

Signal Distributor Blocks

Table 1.1.1-7 Signal Distributor Blocks

Block type Code Name

Block type Code Name

Pulse Count Input Block

Block type Code Name

Block type Code Name

1.1.2 I/O Data Handled by the Regulatory Control Blocks

Process Variable (PV)

Setpoint Value (SV), Cascade Setpoint Value (CSV), Remote

Function Blocks Engineering unit symbol and Scale Range

Input Signal Values (RV1, RV2, RV3)

Reset Limit Values (RLV1, RLV2)

Input or Output Compensated Value (VN)

Tracking Switch (TSW)

Manipulated Output Value (MV)

• Event when the user wants to display the MV in percentage on HIS

Auxiliary Output Values (PV, ΔPV, MV, ΔMV)

Process Variable (PV)

1.1.3 Input Processing, Output Processing, and Alarm

Input Processing Possible for Each Regulatory Control

Input signal conversion Digital filter Totalizer PV Overshoot CAL

Output Processing Possible for Each Regulatory Control

Output Output signal

VELLIM x x x x x x M/Md B/A/Sb

S3: 3-position status output

Alarm Processing Possible for Each Regulatory Control

Process alarms (*1)

Process alarms (*1)

RATIO x x x x x Not available

Connection method(1) Connection destination(1)

Connection method(1) Connection destination(1)