Function Blocks Reference Vol.3

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 manual consists of the following chapters:
• Chapter 1 Sequential Function Chart
This chapter describes the structure and actions of the sequential function charts, how to create
and operate the sequential function charts, and the interfaces of the unit instruments.
• Chapter 2 Unit Supervision
This chapter describes the details on the components and their actions when configuring the unit
supervision.
• Chapter 3 Valve Pattern Monitors
This chapter describes the details on the components and their actions when configuring the
valve pattern monitors.
• Chapter 4 Offsite Blocks
This chapter describes the functional details of the offsite blocks include the batch set control
blocks (FSBSET) and the blending master control blocks (BLEND).
• Chapter 5 System Function Blocks
This chapter describes the common functionalities of the system function blocks and their types
as well as how to reference the data of the system function 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. Sequential Function Chart Page 1 of 3
1. Sequential Function Chart

The sequential function chart (SFC) is a graphical programming language used to define control
sequences.
SFC can be written using the SFC block, which is a function block included in the sequence control
function.
SFC
▼ SFC Block
The SFC language describes a program defining sequential control steps for every group of
processes.
An example of SFC involving three steps, which are initialization, water feed, and heating, is shown
below:
Figure 1-1 Example of SFC
TIP SFC is also used in functions other than the SFC block as indicated below, but the SFC
specifications for each of these will vary somewhat.
• Unit instrument
• Operation
SEE For more information about unit instruments and operations, refer to:
ALSO 2., "Unit Supervision"
Elements
SFC uses the following three elements to define a sequence:
• Step
Defines the action of a step.
• Transition
Defines the condition of transition to next step.
• Link
Defines connections from step to transition and transition to step.
The flow of SFC processing is in accordance with a step sequence in which the action defined for
each step is sequentially executed from the top. Upon completion of one step, further processing is
determined by the defined transition condition.
SFC can define a selective sequence as well, in which steps are defined in parallel to have them
branched for execution. Interrupt steps, which interrupt a normal process for their execution, can
also be described.
Architecture of SFC Block

SFC block may be applied to execute the program written in SFC which is one of the FCS functions.
SFC blocks are usually applied for the comparatively large scale sequence control or device control
system. With the application of SFC, the process management (status display) becomes convenient.
The following figure gives a draft image of the SFC architecture.
Figure 1-2 Image of SFC Block Architecture
Describing Step Actions

SEBOL, a sequence table or a logic chart can be used to describe step actions.
An example of SEBOL-written step actions is shown below:
Figure 1-3 SFC Block Control Algorithm
Although all step actions are written in SEBOL in the above example, a different manner of
description can be used for each step action according to the disposition of the involved process.
SEE For more information about SEBOL, refer to:

ALSO 1., “Basics of SEBOL” in SEBOL Reference (IM 33J05L20-01EN)
For more information about the sequence table and the logic chart, refer to:
2., “Sequence Control” in Function Blocks Reference Vol.2 (IM 33J15A31-01EN)
SFC Block
SFC-written programs are classified according to their processing types as follows:
• Queue-signal processing
Processing executed according to the contents of a queue signal in an SFC main program
designed for normal processing.
• Status-change processing
Interrupt processing executed due to a status change of the SFC block. Different processing may
be executed before and after the status change.
• Interrupt-signal processing
Interrupt processing executed according the contents of an interrupt signal in an SFC main
program designed for normal processing.
• Error processing
Interrupt processing executed when error is caused during the execution of the SFC block.
With the SFC block, a process step which is being executed can be stopped temporarily, referenced
for its step number, or changed.
Data Items
The SFC block has data items to identify SFC status.
These items are either system-specific predetermined data or user-defined data.
Block Modes and Status

The SFC block uses the block mode to identify its control status and the block status to identify the
state of operation as follows:
• Block modes
AUT: automatic
SEMI: semi-automatic
O/S: out-of-service
• Block status
STOP: stopped
RUN: running
PAUS: paused
ABRT: aborted
1.1 SFC Elements Page 1 of 1
1.1 SFC Elements

SFC uses “step,” “transition,” and “link” elements in combinations to define a sequence.
Description of SFC Elements

The step and link elements use varied symbols according to their actions. Their details are shown
below:
Table 1.1-1 SFC Block Elements
Element Name Symbol
Step
Initial step
Double-Width Step
Step
Initial Double-Width Step
Interrupt step
Transition Transition
Selective Sequence Split
Selective Sequence Join
Loop-Branch
Loop-Join
Link
Jump Down
Jump Up
Jump To
Link
SFC defines processes to be executed using these three basic elements in combinations. Both step
and selective sequences can be defined according to the flow of SFC processing. Interrupt steps can
also be described to interrupt the normal flow of process.
1.1.1 Step Page 1 of 4
1.1.1 Step
There are five elements as step elements. Each step needs to be defined with attributes and action.
Step
“Step” is the most basic element for defining SFC processings.
The following five step elements are used:
• Step
• Initial step
• Step with expanded comment
• Initial step with expanded comment
• Interrupt step
Up to 99 steps can be described in one SFC, with attributes and action defined for each step.
Step
This is an ordinary step. In an example shown below, the step number is indicated in the square on
the left and a comment identifying the action defined for the step is shown in the rectangle on the
right:
An example of step is shown below:
Figure 1.1.1-1 Example of Step
Initial Step
This is the step to be executed first. The step number is indicated in the square on the left and a
comment identifying the action defined for the step is shown in the rectangle on the right. The use
of the square and rectangle is the same as the ordinary “step” described above except that a double
square is used instead:
An example of Initial Step is shown below:
Figure 1.1.1-2 Example of Initial Step
Double-Height Step
This element is also for an ordinary step except that a larger rectangle permits to enter three-times
the normal volume of action comment:
An example of Double-Height Step is shown below:
Figure 1.1.1-3 Example of Double-Height Step
Initial Double-Height Step

This element is also for an initial step except that a larger rectangle permits to enter three-times the
normal volume of action comment:
An example of Initial Double-Height Step is shown below:
Figure 1.1.1-4 Example of Initial Double-Height Step
Interrupt Step
An interrupt step is used to interrupt the execution of the main program and execute an interrupt
program. The interrupt step in the main program specified the destination for the expansion to an
interrupt program.
An example of interrupt steps is shown below:
Figure 1.1.1-5 Example of Interrupt Step
Step Attributes
Each step needs to be defined with attributes such as step type and step number.
The table below lists the step attributes.
Table 1.1.1-1 Step Attributes
Attribute Description
Select one of the following:
• SEBOL step
• SEBOL one-shot execution step (SEBOL one-shot)
Action-describing methods • Sequence table step (sequence table step)
• Sequence table one-shot execution step (sequence table one-shot)
• Logic chart step (logic chart)
• Logic chart one-shot execution step (logic chart one-shot)
Step number Integer 1 through 99 (*1)
Step comment Character string of up to 16 bytes.
Phase name Character string of up to 16 bytes.
*1: Duplicate numbers must not be assigned.
Step Action
Each step is described as an action to execute a processing.

The types of action and the description of each step are shown below:
• Initial step
in SEBOL
• SEBOL step
in SEBOL
• SEBOL one-shot
in SEBOL
• Sequence table one-shot execution step (sequence table step)
in Sequence table
• Sequence table one-shot execution step (sequence table one-shot step)
in Sequence table
• Logic chart step (logic chart)
in Logic chart
• Logic chart one-shot execution step (logic chart one-shot)
in Logic chart
Some steps require the use of parameters to define action as described below:
Table 1.1.1-2 Action Parameters
Action when
Step Parameter
unspecified
Initial step None -
SEBOL step & SEBOL oneshot None -
Parameter-storing variable in action
Sequence table one-shot execution Ignored (*1)
column.
step
Name of step executed. -
Condition testing result-storing variable. Ignored (*2)
Sequence table one-shot execution
Name of step executed. -
Parameter-storing variable in action
Logic chart step Ignored (*1)
column
Logic chart one-shot None -
*1: The operation & monitoring parameter is ignored.
*2: The condition testing result is ignored.
SEE For more information about action description, refer to:

ALSO 1.2, "Action Description Using SEBOL"
1.3, "Action Description Using Sequence Table"
1.4, "Action Description Using Logic Chart"
For more information about the action signal parameter and condition testing result for sequence
table and sequence table one-shot steps, refer to:
1.3.1, "Step Common Item Description Using the Sequence Table"
For more information about the action signal parameter for logic chart steps, refer to:
1.4.1, "Step Common Item Description Using Logic Chart"
Step Status
A step is “active” when it is being executed or “inactive” when it is not yet executed or its execution
is completed.
When step status changes to active, the step action is executed.
Ending of the step action, step status changes to inactive and the step advances to the next
precessing.
1.1.2 Transition Page 1 of 2
1.1.2 Transition
The transition is an element to evaluate the transition condition to the next step.
Transition
The transition is an element used for evaluating the transition condition between steps. The
transition condition must defined with a single logical expression.
The condition is evaluated when the current step is completed and the next step is activated if the
condition is determined to be true.
The transition is denoted by a short horizontal line crossing the vertical link line between steps.
SFC can describe step sequence transition and selective sequence transition.
Step Sequence Transition

In step sequence, steps are executed in the programmed order from top to bottom. When the
transition condition of the current step is satisfied, the next step is activated and the action is
executed. If no condition is defined for the transition, the next step is activated and the step action
is executed.
Step sequence is SFC basic action.
Figure 1.1.2-1 Example of Step Sequence Transition
SEE For more information about transition conditions, refer to:

ALSO 1.5, "Transition Conditions"
Selective Sequence Transition

In case of a selective sequence with a number of steps defined in parallel, the transition condition is
evaluated for every step from left to right. When the transition condition of the current step is
satisfied, the next step is activated. If no transition condition is defined for the transition, the next
step is activated and the action is executed. At the moment the action is executed, the selective
sequence transition is already completed.
No other transition conditions are evaluated within the selective sequence during execution of one
step.
1.1.2 Transition Page 2 of 2
Figure 1.1.2-2 Example of Selective Sequence Transition
The transition condition is evaluated once every basic cycle, or once in a few cycles unless time is
allocated to the SFC block specifically for once-per-cycle evaluation.
SEE For more information about Step & Selective Sequences, refer to:
ALSO 1.1.4, "Step & Selective Sequences"
1.1.3 Links Page 1 of 3
1.1.3 Links
The Links define the order of step execution. The following eight links are available:
• Selective Sequence Split
• Selective Sequence Join
• Loop-Branch
• Loop-Join
• Jump Down
• Jump Up
• Jump To
• Link
These links, except for ordinary “Link,” must be used in the following combinations:
• Selective Sequence Split and Selective Sequence Join
• Loop-Branch and Loop-Join
• Jump Down and Jump To
• Jump Up and Jump To
Selective Sequence Split and Selective Sequence Join

These links are used in a selective sequence as shown below:
Figure 1.1.3-1 Selective Sequence Split and Selective Sequence Join
Up to a maximum of eight horizontal rows of steps can be defined within a selective sequence. The
transition of steps in a selective sequence is determined as the steps are evaluated from left to right.
The step located under the transition element is activated if the transition condition is true.
SEE For more information about Selective Sequence, refer to:

ALSO " Selective Sequence" in 1.1.4, "Step & Selective Sequences"
Loop-Branch and Loop-Join

These links are used to define a loop as shown below.
The step or steps located between Loop-Branch and Loop-Join are repeatedly executed as long as
the transition condition for the loop is true.
An example of Loop-Branch and Loop-Join is shown below:
Figure 1.1.3-2 Example of Loop-Branch and Loop-Join
If all of the following conditions are satisfied in a periodic SEBOL program, the
upward transition with a Loop-Branch is not interrupted and the sequence
goes to the step of the destination Loop-Join within the same scan. As a
result, the periodic SEBOL program continues to execute up to the upper limit
of 2000 lines in the same scan, and the CPU idle time may decrease.
• [Continue] after step transition is selected in Function Block Detail Builder.
• Loop-Branch is used.
• The upward transition condition of the Loop-Branch is true, or the
transition condition is not described.
• Interruptive statements are never described in SEBOL processing with loop
structure.
In order to run one cycle of SFC loop in one scan, write a delaycycle
statement in the step immediately before the Loop-Branch. You can add the
description anywhere in the step.
SEE For more information about [Continue] after step transition when transition conditions are
ALSO satisfied, refer to:
“ Periodic SEBOL Action after Step Transition : FFCS-C/FFCS-V” in “ Periodic SEBOL
Programs : FFCS-C/FFCS-V” in 7.4, “SEBOL Process Timing” in Function Blocks Overview (IM
33J15A20-01EN)
For more information about process of interruptive statements, refer to:
“ Interrupting and Restarting SEBOL Programs” in 7.4, “SEBOL Process Timing” in Function
Blocks Overview (IM 33J15A20-01EN)
For more information about delaycycle statement, refer to:
8.9, “delaycycle” in SEBOL Reference (IM 33J05L20-01EN)
Jump Down, Jump Up and Jump To

These links are used when the process sequence must forcibly be skipped.
The Jump Down element defines downward skipping and the Jump Up element defines upward
skipping. The Jump To element, which must be used in combination with either one of the skipping
elements, defines the destination of skipping.
The Jump To is executed when the transition condition defined proceeding the Jump Down or
succeeding the Jump Up is true.
Examples of skipping are shown below:
Figure 1.1.3-3 Examples of Jumping
When a new skip label is created, it is automatically numbered adding 1 to the number of the most
recent skip label.
Link
The “link” is used to connect steps.
The vertical lines are for Linking a step with another step.
An example of Link is shown below.
Figure 1.1.3-4 Example of Link
1.1.4 Step & Selective Sequences Page 1 of 2
1.1.4 Step & Selective Sequences

SFC can describe step-sequence and selective-sequence as well as interrupt programs which thrust
into those processing steps.
Step Sequence
In a step sequence, steps are executed in the programmed order from the top and only one
transition is defined between steps.
An example is shown below:
Figure 1.1.4-1 Example of Step Sequence
The defined action is executed when the step is activated. As soon as the action is completed, the
transition condition is evaluated and the successive step is activated when the condition is true. The
successive step will be activated immediately upon completion of the current step if no transition
condition is defined.
Selective Sequence
In a selective sequence, one of two to eight steps defined in parallel is executed selectively.
Figure 1.1.4-2 Example of Selective Sequence
The transition condition is evaluated from left to right for every step; and the step for which the
condition is true will be activated, which is defined preceding the step. If no transition condition is
defined, the step will be activated unconditionally.
No other transition conditions are evaluated within the selective sequence during execution of one
step.
Interrupt Program
The interrupt program is an SFC program designed to interrupt the main SFC program for the
execution of a non-sequential event. The interrupt program needs to be written for each non-
sequential event and is developed from an interrupt step defined for the event in the main program.
1.1.4 Step & Selective Sequences Page 2 of 2
An example of the interrupt program for pausing (PAUS) developed from an SFC block containing
three interrupt steps is shown below:
Figure 1.1.4-3 Example of Interrupt Program Developed from Interrupt Step
1.2 Action Description Using SEBOL Page 1 of 1
1.2 Action Description Using SEBOL

The following methods of describing step actions using SEBOL are explained in this section:
• Step common items
• Initial steps
• SEBOL steps
• SEBOL one-shot steps
Using SEBOL
Global and local variables can be used to define steps in the SFC block using SEBOL.
Enabling access to a function block from a SEBOL-written step requires global or local function-block
declaration.
TIP Parameters cannot be specified when describing action using SEBOL. They can be specified when
describing action using a sequence table, however.
1.2.1 Step Common Items Page 1 of 4
1.2.1 Step Common Items

Items common to all steps for which SEBOL is used to write actions are as follows:
• SEBOL variables
• Function-block declaration
• Branching range
• “quit” statement
• #define
SEBOL Variables
Global and local SEBOL variables can be used in the SFC block when a step is described using
SEBOL. The global variable can be accessed from all the SEBOL-written steps in the SFC block, while
the local variable can be accessed from only one step.
Areas are allocated to both variables and they are initialized to zero when the SFC block is started.
The areas are released when the SFC block has been executed.
TIP In the case of a character-string variable, the global or local variable is initialized to a null-length
character string when the SFC block is started.
Global Variables
Global variables can be accessed from any SEBOL-written step in the SFC block. To use global
variables, they should be specified in the initial step as shown below:
Figure 1.2.1-1 Global Variables
TIP Global variables cannot be accessed from any sequence table or logic chart described step.
Local Variables
Local variables can be accessed only from the steps for which the use of local variables is declared.
To use local variables, they should be specified in the initial step as shown below:
Figure 1.2.1-2 Local Variables
The same local variable can be used in different steps under the same variable name, in which case
area is allocated independently for each variable.
If a step is repeatedly executed in a loop, the local variable remains unchanged throughout the
repeated execution.
Note Points
The same name cannot be assigned to global and local variables. An error is caused if the two has
the same name.
Function Block Declaration

The use of a function block can be declared globally or locally. The global declaration permits access
from all SEBOL-written steps, while the local declaration permits access only from the declared step.
Global Declaration
A function block can be accessed from any SEBOL-written step when the use of that function block
is globally declared in the initial step as shown below:
Figure 1.2.1-3 Global Declaration
Local Declaration
A function block can be accessed from just one step when the use of the function block is locally
declared in that step as shown below:
Figure 1.2.1-4 Local Declaration
Note Points
• No error occurs when the tag name specified in global declaration is used also in local
declaration; however, an error will occur if different block codes are specified. An error also
occurs if specified global and local generic names are identical.
For the tag name used in the arithmetic expression of a SEBOL or a general-
purpose calculation block, if it is started with a numeric character or if it
contains a [-] (hyphen) character, an error will occur during compilation.
Thus, it is necessary to use the alias statement to declare the tag with a new
name, which started with an alphabet character and contains no hyphen, and
then use the alias.
• Using multiple-project-tag name, the function block data of other projects can be accessed. Since
a multiple-project-tag has an @ mark in its name, it is necessary to declare an alias for the
multiple-project-tag. Multiple-project-tag is named in the following format:
TagName@ProjectID
The project ID should be defined in Multiple projects connection builder of the upper project,
with two alphanumeric characters. Up to 16 alphanumeric characters can be used for naming a
tag with project ID including the “@” mark.
When declaring a tag with project ID, since “@” mark is used, an alias should be used to replace
the original tag. An example of declaring an alias for function block tag with project ID is shown
below:
block PID FIC100
block PID TAG001 alias TIC100@P1
FIC100.CSV = TAG001.MV
SEE For more information about calling up multiple-project tag name, refer to:
ALSO “ Identical Tag Names” in 6.2.1, “Operation and Monitoring Multiple Projects” in Optional
Functions Reference (IM 33J05H10-01EN)
Branching Range
The destination for branching is restricted to be within the step in which branching is specified using
a “goto” statement, for example. Processing cannot be branched to other steps using “error”
and “errorsub” specifications, “goto” statements, etc.
SEE For more information about "error" and "errorsub" specifications, refer to:
ALSO 13., “Error Handling” in SEBOL Reference (IM 33J05L20-01EN)
For more information about "goto" statement, refer to:
8.7, “goto” in SEBOL Reference (IM 33J05L20-01EN)
“quit” Statement
The “quit” statement terminates the action being executed.
When this statement is executed as a step action, the transition condition defined succeeding the
step will then be evaluated.
#define
A name can be defined using “#define” only in the initial step. The defined name can then be used
in all SEBOL-written steps.
SEE For more information about "#define", refer to:

ALSO “ #define Statement” in 1.8, “Substitution of Character String” in SEBOL Reference (IM
33J05L20-01EN)
1.2.2 Initial Step Page 1 of 2
1.2.2 Initial Step

The following methods of describing the initial step are described in this section:
• Order of description
• Example of description
• Use of “#define”
• Use of “#include”
• Use of “#IMPLICIT”
Order of Description
The initial step action should be described in order of global variables, local variables, and execution
statements as shown below; an error will be caused otherwise.
Figure 1.2.2-1 Order of Description
The initial step action can be described using up to 2000 lines. No parameters are used in describing
the action.
The initial step is completed when the last described execution statement or a “quit” statement has
been executed.
Example of Description
The following is an example of initial-step description:
!global variable declaration
global block TM TM301, TM302
global block SIO-11 VL301, VL302
global integer loop
global char*16 name
!local variable declaration
integer i, j, k
!action execution statement
[ VL301.MODE.MV = "MAN", 0]
.......
quit
Use of “#define”
Names can be defined using “#define” anywhere within the initial step.
The defined names can then be used in any SEBOL-written step and transition condition.
SEE For more information about "#define", refer to:

ALSO “ #define Statement” in 1.8, “Substitution of Character String” in SEBOL Reference (IM
33J05L20-01EN)
1.2.2 Initial Step Page 2 of 2
Use of “#include”
“#include” can be specified for file-inclusion anywhere within the initial step.
The order of all statements in the included file, however, must be in conformity with that of the
initial step. Otherwise, an error is caused for the statements in the included file.
SEE For more information about "#include", refer to:

ALSO “ #include” in 1.9, “Include File” in SEBOL Reference (IM 33J05L20-01EN)
Use of “#IMPLICIT”
A “#IMPLICIT” command can be used in the initial step. The command is then valid within the entire
SFC block.
This command cannot be entered in any other steps.
SEE For more information about "#IMPLICIT", refer to:

ALSO “ #IMPLICIT Instruction” in 1.7, “Implicit Declarations of Variables” in SEBOL Reference (IM
33J05L20-01EN)
1.2.3 SEBOL Steps Page 1 of 1
1.2.3 SEBOL Steps

The following items as to describing SEBOL steps are explained in this section:
• Restrictions
The SEBOL step action should be described in order of variables and execution statements as shown
below; an error will be caused otherwise.
The SEBOL step action can be described using up to 2000 lines. No parameters are used in
describing the action.
The step is completed when the last described execution statement or a “quit” statement has been
executed.
The following is an example of SEBOL-step description:
block PVI LI303
integer ierr
wait until (LI303.PV >= 10.0) ; ierr
.......
quit
Note Points
#define, #include, and #IMPLICIT command cannot be used with SEBOL steps. These commands
can be used only by the initial step. However, the name defined by means of “#define” in the initial
step can be used.
1.2.4 SEBOL One-Shot Steps Page 1 of 2
1.2.4 SEBOL One-Shot Steps

The following items as to describing SEBOL oneshot steps are explained in this section:
• Execution
• Restrictions
The SEBOL oneshot-step action should be described in order of variables and execution statements
as shown below; an error will be caused otherwise.
No parameters are used in describing the action. The step is completed when the last described
execution statement or a “quit” statement has been executed.
The following is an example of SEBOL oneshot-step description:
block %SW SW301, SW302
SW301.PV = 1
SW302.PV = 1
quit
Execution
The SEBOL oneshot-step action will be executed without any break once it is activated. Its
processing time will not be shared by any other SFC program. No interrupt signals nor status change
instructions are allowed to interrupt the execution until it is completed.
Note Points
The SEBOL oneshot-step action can be continuously executed up to 20 lines. If a “for” statement is
used, for example, and one line is repeatedly executed, each repetition is counted as one line. If
execution is attempted exceeding 20 lines, an execution error is caused and the successive action
will be executed not as oneshot but normal step action.
The following statements should not be used in order to avoid any execution error:
• Statement for accessing function-block data at another control station.
• “signal” statement for sending signals to another control station.
• “qsigcancel” and “qsigmove” statements for manipulating an SFC block at another control station.
Also the following statements should not be used in order to avoid any error:
• “drive” statement, “seqstable” and “logicchart” statements with “drivewait” specification.
• “wend,” “until,” and “next” statements without “@.”
1.2.4 SEBOL One-Shot Steps Page 2 of 2
• “wait until,” “delay,” and “delaycycle” statements.

• “dialogue” statement.
• “nopreempt begin” and “nopreempt end” statements.
• “semlock wait” statement.
• “wait for qsignal” statement.
• “ssdtwrite” and “ssdtwritebit” statements.
#define, #include, and #IMPLICIT command cannot be used with SEBOL oneshot steps. These
commands can be used only by the initial step. However, the name defined by means of “#define”
in the initial step can be used.
1.3 Action Description Using Sequence Table Page 1 of 1
1.3 Action Description Using Sequence Table

The following items as to describing step actions using a sequence table are explained in this section.
• Step common items using the sequence table
• Sequence table (ST) steps
• Sequence table (ST) one-shot steps
Using the Sequence Table

When using a sequence table to describe a step, the sequence table block needs to be assigned with
a tag name.
The sequence table needs a step name as the action parameter and the name of a variable to store
the action-signal column parameter.
The sequence table one-shot step needs a step name as the action parameter and the name of a
variable to store condition testing result.
1.3.1 Step Common Item Description Using the Sequence Table Page 1 of 3
1.3.1 Step Common Item Description Using the Sequence

Table
Items common to all sequence table steps are as follows:
• Tag name
• Step name
• Variable to store action-signal column parameter or sequence table-condition testing result
Tag Name
The sequence table needs to be tagged so that its tangle can be used as the step name. The
specified sequence table can be shared by different steps.
The tag names that can be specified for the step execution name are only the sequence tables in the
same control station.
Step Name
When using step type sequence table, a sequence table step name can be designated as a step
action for execution. How to specify step names as the sequence table step actions are shown
below.
Table 1.3.1-1 Step Name Specification
Specification Action
No specification (default) The first step is executed.
An execution step name specified using up to 2 characters. The specified step is executed.
Continuation is specified. The current step is executed (*1)
*1: The current step is retained in sequence table data item PV.
In the case of sequence table one-shot steps, the specified step and step 00 are oneshot-executed.
In the case of sequence table steps, the sequence table is periodically executed at its own timing
after the specified step and step 00 have been oneshot-executed. Step 00 is executed in every scan
period. Specifying a step name for a non-step sequence table is ignored.
SEE For more information about sequence tables, refer to:

ALSO 2.2, “Sequence Table Block (ST16, ST16E)” in Function Blocks Reference Vol.2 (IM 33J15A31-
01EN)
Specified Variable to Store Action-signal Column

Parameter or Condition Testing Result
In the case of sequence table step or sequence table one-shot step, a variable to store the
parameter for the action signal of SFC/SEBOL return event message (%RE) or condition testing
result may be specified in the action signal column. When sequence table step or sequence table
one-shot step is executed, the “parameter in action signal column” and the “condition testing result”
will be stored in the specified variable. Both “parameter in action signal column” and the “condition
testing result” are Long type data.
Which one will be stored in the variable depends on the step types, shown as below.
Table 1.3.1-2 Representation of the Variable
Step Parameter in Action-signal column(*1) Condition testing result(*1)

Sequence table step x -
Sequence table one-shot step - x
*1: x: Stored.
-: Not stored.
These variables will be ignored if their names are not specified in step action.
Action-Signal Column Parameter

This parameter for the SFC/SEBOL return even message (%RE), which is an output of software I/O
messages, is stored in the specified variable using 0 through 65535 defined in the action-signal
column of the sequence table.
Sequence Table Condition Testing Result

This is a result of condition testing the sequence table, which is either true (1) or false (0).
• In the case of a non-step sequence table, the result is true if at least one of 32 rules is satisfied
and false if none is satisfied.
• In the case of a step sequence table, all the rules for the specified step and step 00 are
evaluated. Then the result is true if at least one rule is satisfied and false if none is satisfied.
Variable Name
The names of both variables can be specified in one of the following four different manners:
• Present SFC-block data item
When storing data as a data item in the present SFC block, specify the variable name as follows:
%.<data item>
• Global variable
When storing data in a global variable, specify the name of the simple variable declared
using “global long” in the initial step.
• Tag name-specified function-block data item
When storing data as a data item in the tag name-specified function block, specify the variable
name as follows:
<tag name>.<data item>
In this case, the tag name should have been declared using “global block” in the initial step.
When storing the condition testing result for an ST oneshot step, the tag name must be present
within the same control station as the SFC block; specifying a tag name from another control
station causes error when the SFC block is executed.
• Global generic name-specified function-block data item
When storing data as a data item in the global generic name-specified function block, specify the
variable name as follows:
<global variable>.<data item>
The global generic name, which must be a simple variable, should be declared using “global
block” in the initial step. When storing the condition testing result for an sequence table oneshot
step, the tag name present within the same control station as the SFC block must be assigned to
the global generic name using the “assign” statement.
SEE For more information about sequence tables, refer to:

01EN)
1.3.2 Sequence Table Steps Page 1 of 1
1.3.2 Sequence Table Steps

The following items as to describing sequence table steps are explained in this section.
• Step action description
• Step execution
Step Action Description

The sequence table step action is described using a periodic start sequence table (TE or TC).
Step Execution
The sequence table step is oneshot-executed when its action is activated, and the sequence table
block mode changes to AUT at the same time. The sequence table will then be periodically executed
according to its own action timing.
The sequence table step action is terminated when an SFC/SEBOL return event message (%RE) is
received from the sequence table. The sequence table block mode then changes from AUT to MAN.
1.3.3 Sequence Table One-Shot Steps Page 1 of 1
1.3.3 Sequence Table One-Shot Steps

The following methods of describing sequence table one-shot steps is explained in this section.
• Step execution

The sequence table one-shot step is described using a non-step sequence table (OE or OC).
Step Execution
The sequence table one-shot step is oneshot-executed when its action is activated. The sequence
table block mode remains unchanged.
1.4 Action Description Using Logic Chart Page 1 of 1
1.4 Action Description Using Logic Chart

The following methods of describing step actions using logic chart are explained in this section.
• Step common items using logic chart
• Logic chart steps
• Logic chart one-shot execution steps
Using Logic Chart

To describe steps using logic charts, tag names of logic chart blocks must be specified. At logic chart
steps, variable names to store action signal column parameters can be specified as parameters for
action.
1.4.1 Step Common Item Description Using Logic Chart Page 1 of 1
1.4.1 Step Common Item Description Using Logic Chart

Items common to all logic chart steps are as follows:
• Tag name
• Variable to store action signal column parameters
Tag Name
The logic chart needs to be tagged so that its tangle can be used as the step name. The specified logic chart
can be shared by different steps.
The tag names that can be specified for the step execution name are only the logic chart in the same control
station.
Specified Variable to Store Action-Signal Column

In the case of logic chart step, a variable to store the parameter for the action signal of SFC/SEBOL return
event message (%RE) may be specified in the action signal column. When logic chart step is executed,
the “parameter in action signal column” will be stored in the specified variable. “Parameter in action signal
column” is Long type data.
The variable will be ignored if the name is not specified in step action.
Action-Signal Column Parameter

This parameter for the SFC/SEBOL return even message (%RE), which is an output of software I/O
messages, is stored in the specified variable using 0 through 65535 defined in the action-signal column of
the sequence table.
Variable Name
The names of both variables can be specified in one of the following four different manners:
• Present SFC-block data item
When storing data as a data item in the present SFC block, specify the variable name as follows:
%.<data item>
• Global variable
When storing data in a global variable, specify the name of the simple variable declared using “global
long” in the initial step.
When storing data as a data item in the tag name-specified function block, specify the variable name as
follows:
In this case, the tag name should have been declared using “global block” in the initial step.
When storing data as a data item in the global generic name-specified function block, specify the variable
name as follows:
The global generic name, which must be a simple variable, should be declared using “global block” in the
initial step.
SEE For more information about logic chart, refer to:

ALSO 2.3, “Logic Chart Block (LC64, LC64-E)” in Function Blocks Reference Vol.2 (IM 33J15A31-01EN)
1.4.2 Logic Chart Steps Page 1 of 1
1.4.2 Logic Chart Steps

The following items as to describing logic chart steps are explained in this section.
• Step execution

The logic chart step action is described using a periodic start logic chart (TE).
Step Execution
The logic chart step is one-shot-executed when its step is activated, and the logic chart block mode
changes to AUT at the same time. The sequence table will then be periodically executed according
to its own action timing.
The logic chart step action is terminated when an SFC/SEBOL return event message (%RE) is
received from the logic chart. The logic chart block mode then changes from AUT to MAN.
1.4.3 Logic Chart One-Shot Steps Page 1 of 1
1.4.3 Logic Chart One-Shot Steps

The following method of describing logic chart one-shot steps is explained in this section.
Step Execution
The logic chart one-shot step is one-shot-executed when the step is activated. The logic chart block
mode remains unchanged.
1.5 Transition Conditions Page 1 of 1
1.5 Transition Conditions

The following methods as to describing transition conditions are explained in this section:
• Description of transition conditions
• Variables applicable to transition conditions
Description
Conditional expressions is SEBOL statement are used to define conditions for the transition of steps.
The condition is satisfied when the result of the conditional expression is not zero and not satisfied
when it is zero. When equivalence operators (==, <>) or relational operators (>=, <=, >, <) are
used, the condition is satisfied when the relation is true (1) and not satisfied when it is false (0).
The same manner of describing the transition condition applies to all types of steps.
For a selective sequence, up to eight transition conditions can be defined. It is not necessary to
describe transition condition since the step transition is unconditional. Moreover, the maximum
number of transitions including the unconditional transitions is 99 per FCS.
Variables
The following variables can be used in the conditional expressions for transition:
Table 1.5-1 Variables Applicable to Conditional Expressions
Variable Remarks
Constant -
Global variable -
Local variable Declared in step action.
Global tag name Tag name declared using “global block.”
Tag name declared using “block” in SEBOL-step action.
Tag name Sequence table tag name in sequence table step action.
Logic chart tag name in logic chart step action.
Global generic name Generic name declared using “global genname.”
Local generic name Declared using “genname” in step action.
Unit generic name Declared using “global unit genname,” or declared using “unit genname” in step action.
%$ Replaced by tag name of action-written sequence table/logic chart.
Restrictions of variable applicable to conditional expressions are shown below:

• Global variables, step local variables, and constants can be used in array subscript expressions for
array-element variables.
• SEBOL built-in functions can be used in conditional expressions.
• “%$” entered in transition condition is replaced by the tag name of the sequence table/logic
chart which defines action. The conditional expression %$.MODE==“AUT” will be changed to
ST0101.MODE==“AUT” if the sequence table tag name is ST0101, for example.
• If the sequence table/logic chart is specified using a unit generic name, “%$” cannot be replaced
by the generic name. The generic name must be written in the conditional expression in this
case.
1.6 SFC Block Action Page 1 of 4
1.6 SFC Block Action

The SFC block is designed to execute SFC-written programs.
SFC Programs
An SFC program that executes normal processing is the main program and an SFC program that
interrupts the main program for execution is the interrupt program.
SFC-written programs are classified according to their function and behavior.
Main Programs
• Queue signal processing
This process is executed according to the queue signal contents in the SFC main program, which
executes normal processing.
• Exit of the SFC block
• Pause of the SFC block
• Reference of the current step.
• Change of the step to be executed
• Alarm processing of the SFC block
Interrupt Programs
• Status change
This program is run together with SFC block status change. Separated programs before/after
status changes may be implemented.
• Interrupt signal
Interrupt signal interrupts the SFC main program to run the programs requested by the interrupt
signal.
Error occurrence when SFC block is running may trigger an interrupt program for error
processing.
SFC Block Online Maintenance

When part of system is added or modified while the system is running, online maintenance is
required so as to update the database.
SFC Block Execution Timing

When all the basic control functions are executed, the SFC block is executed using the idle time left.
SFC Block Data Items

SFC blocks have fixed data items as well as user-definable data items.
SFC Block Status
SFC block running state can be indicated by block mode and block status.
Interrupt Programs
Interrupt programs must be described separately for every different purpose.
When the block status has been changed and if it is necessary to pause or terminate the process, an
interrupt program or programs can be executed as required. For example, the heater needs to be
stopped if the process is to be terminated during heating, or the valve needs to be closed if the
process is to be paused during tank charging.
An example of executing an interrupt program for pausing from the main program, which contains
SIGNAL 1, RUN, STOP, and PAUS interrupt steps is shown below:
Figure 1.6-1 Example of Interrupt Program Execution
Although the first step of the interrupt program is shown in a double square in the above example, it
does not mean that the step is the initial step.
Global variables cannot be declared using “global integer” nor “global block” for the first step of an
interrupt program. They can be read or written, however.
Interrupt Program Types of Processing

Interrupt programs can be used for the following processing:
• Status change pre-processing
• Status change post-processing
• Interrupt signal processing
The following steps can be used in these interrupt programs as well as the main program:
Table 1.6-1 Steps Applicable to SFC Programs
Program (*1)
Step
Main Status change Status change Interrupt signal Error
program pre-processing post-processing processing processing

Initial step x - - - -
SEBOL step x - x x x
SEBOL one-
x x x x x
shot step
Sequence table
x - x x x
step
Sequence table
x x x x x
one-shot step
Logic chart step x - x x x
Logic chart one-
x x x x x
shot step
Interrupt step x - - - -
*1: x: Applicable
-: Not applicable
TIP Transition can be defined for programs other than the status change pre-processing program.
Interrupt Program Parameters

Parameters must be specified according to the type of interrupt processing.
For Status Change Pre-processing & Post-processing

One of the following parameters needs to be specified according to which status change instruction
is to be executed:
• RUN
Starts the SFC block or restarts the paused SFC block.
• STOP
Terminates the SFC block being executed.
• PAUS
Pauses the SFC block being executed.
SEE For more information about Status Change Processing, refer to:
ALSO 1.6.2, "Status Change Processing"
For Interrupt Signal Processing

The name of the signal needs to be specified to execute the interrupt program.
SEE For more information about Interrupt Signal Processing, refer to:
ALSO 1.6.3, "Interrupt Signal Processing"
For Error Processing

No parameter can be specified for error processing.
SEE For more information about Error Processing, refer to:

ALSO 1.6.4, "Error Processing"
1.6.1 Queue Signal Processing Page 1 of 5
1.6.1 Queue Signal Processing

Queue signals are processed in the SFC main program.
Signal Declaration
Queue signals to be sent to the SFC block must be so declared in the initial step using the “queue
signal” statement.
Figure 1.6.1-1 Signal Declaration
• The signal is ignored and error is returned to the source if an undeclared signal or any non-
defined interrupt signal is received.
• The “queue signal” statement can be used wherever declaration is allowed in the initial step
(global and local variable declarations).
• The “queue signal” statement cannot be used in steps other than the initial step.
• An error is caused if the same signal name is declared in duplication.
• An error is also caused if the same signal name as an interrupt signal name is declared.
The following is an example of queue signal declaration:
queue signal "SG1","SG2"
Signal Processing
The SFC block fetches the first signal in the queue to process the signal in the main program.
When the SFC block in the RUN or PAUS status receives a queue signal, it is stored in the signal
queue. If the block is in a status other than RUN and PAUS, the received signal is ignored and error
is returned to the signal source.
The SFC block signal queue may be cancelled as required.
Queue signals are transmitted using the “signal” statement and pending signals can be manipulated
using “qsigcancel” and “qsigmove” statements.
SEE For more information about "queue signal" statement., refer to:
ALSO 12.1, “Signal Transmission Processing” in SEBOL Reference (IM 33J05L20-01EN)
For more information about pending signal manipulation, refer to:
12.2, “Processing of Queue Signal” in SEBOL Reference (IM 33J05L20-01EN)
Fetching Queue Signals

▼ Maximum Number of Queue Signal Parameters, Maximum Number of Acceptable Queue Signal
Parameters
The first signal in the queue is fetched for processing when the “wait for qsignal” statement (see
below) is executed in the SFC block.
Figure 1.6.1-2 Fetching Queue Signals
The maximum number of received signal parameters can be specified in a range of 2 to 8 (2 at

default) for the parameter attached to a queue signal on the Function Block Detail Builder. Any
signal received exceeding the specified number will be ignored, causing an error.
The maximum number of signals received in the queue can be specified in a range of 0 to 99 (5 at
default) on the Function Block Detail Builder. No additional signals can be received exceeding the
specified number. Any signal transmitted when the queue is full, an error will be returned to the
signal source.
The signal fetched used “wait for qsignal” statement from the queue and being processed is
included in the count of the specified maximum number of signals. The processed signal will be
dequeued when the next signal is fetched used wait for “qsignal” statement.
Format-1 “wait for qsignal” Statement

This format is used to wait until a queue signal is received. If no signal is in the queue when
the “wait for qsignal” statement in this format is executed, the SFC block waits until a signal is
received while the queue is checked for any received signal once every scan period of the block at
most. As soon as a signal is received and fetched from the queue for processing, the name of the
signal is stored in the specified variable.
TIP • Status change pre-processing or post-processing, or interrupt signal processing will be

executed while the waiting for the receiving of queue signals.
• If time cannot be shared sufficiently for the once-every-scan-period check for received signals,
the check will be made no more than once every few scan periods.
Format-2 “wait for qsignal” Statement

This format is used to wait until a queue signal is received or the condition specified by the
expression is satisfied.
The expression is first calculated when the “wait for qsignal” statement in this format is executed. If
the result is true (other than 0), the condition is satisfied and the statement is closed. If the result is
false (0), the presence of signals in the queue is checked.
When the statement is closed with the condition satisfied, a null-length character string (“”) is stored
in the signal name-storing variable. When a signal has been fetched from the queue, the name of
the signal is stored in the variable. When the result of the expression is false and no signal is in the
queue, both the expression and the queue will be checked once every scan period of the block at
most.
<label> can be used to specify the destination for branching when error is caused. If “error”
or “errorsub” is not used, execution is resumed from the next statement when error is detected.
Specifying <error identifier> permits to identify the error-caused location in the error handling
phase, which provides the identifier value using a built-in function.
TIP It is recommended to use just one “wait for qsignal” statement, in either one of the two formats,
in the SFC block, and program so that execution returns to the statement for successive signal
processing upon completion of the current signal processing.

Fetching Signal Parameters

Upon completion of the “wait for qsignal” statement with a signal fetched from the queue, the
parameter and name of that signal can be read.
Built-in function “creadpara,” “lreadpara,” or “dreadpara” is used to read the signal parameter; and
built-in function “creadpara” is used to read the signal name.
Figure 1.6.1-3 Fetching Signal Parameters
“creadpara” is a character-string function, “lreadpara” is a long integer function, and “dreadpara” is

a long double-precision floating-point real-number function, and they are used to read character-
string, integer, and real-number signal parameters respectively.
Using any of these built-in functions after the expressed condition is the format-2 “wait for qsignal”
statement has been satisfied will cause error when executed.
Examples of Queue Signal Processing

Examples of queue signal processing using the two formats of the “wait for qsignal” statement are
shown below.
Waiting for Signal-Receiving Only
An example of executing the format-1 “wait for qsignal” statement:
Figure 1.6.1-4 Example of Queue Signal Processing Using Format-1 Statement
The “wait for qsignal” statement is executed in step 2 and a signal is fetched from the queue. The
signal name is then evaluated according to the transition condition defined following step 2,
selecting either SG1 or SG2 for processing.
Waiting for Signal-Receiving or Satisfied Condition

An example of executing the format-2 “wait for qsignal” statement:
Figure 1.6.1-5 Example of Queue Signal Processing Using Format-2 Statement
The “wait for qsignal” statement is executed in step 2, determining to wait for a signal or to
calculate the expression. The result of the expression is checked for the first transition condition
defined following Step 2. Either SG1 or SG2 is selected for processing according to the other two
transition conditions.
Referencing
▼ Reference Signal Parameter Numbers
User-defined data item QUEUE is used to reference the queue of signals. QUEUE is defined as a one-
dimensional CHR16 character-string array and each of its elements can be accessed as a char*16
character string in SEBOL. The name of the signal stored in the queue or one of signal parameters is
set at a QUEUE element. The data of signals pending to be processed are set in the QUEUE array
but the data of the signal being processed is not.
Definition of User-Defined Data Item QUEUE

Data item QUEUE can be defined for the purpose of referencing the queue of signals as follows:
• Define a CHR16 one-dimensional array named QUEUE. No data type other than character strings
nor simple variables cannot be used.
• Specify 1 to 32 array elements. Any elements specified exceeding 32 are ignored.
• Do not define QUEUE if there is no need for referencing the queue of signals.
Use the Function Block Detail Builder to specify the use of signal names and parameter numbers for
QUEUE array elements. The parameter numbers specified are then used as reference signal
parameter numbers. The signal name is set if the reference signal parameter number is 0; if the
number is 1 to 8, the signal parameter of that number is set at the QUEUE element. When numeric
signal parameters are used, they are converted to character strings and set at QUEUE elements
starting from the first element.
Example of Referencing
When the queue has four signals, for example, referencing can be made as described below:
Figure 1.6.1-6 Queue Holding Four Signals
If the reference signal parameter number is 1, the contents of QUEUE array elements are as follows:
Queue[1] = "SUMMER"
Queue[2] = "AUTUMN"
Queue[3] = "WINTER"
Queue[4] = "SPRING"
Queue[5] = " "
.....
Queue[10] = " "
QUEUE[5] to QUEUE[10] are null-length character strings since there are no signals.
1.6.2 Status Change Processing Page 1 of 5
1.6.2 Status Change Processing

There are following two types of the interrupt processes executed with a block status change
command:
• Status-change pre-processing
• Status-change post-processing
Processing Flow - SFC

The flow of processing when the SFC block receives a status change command is shown below:
Figure 1.6.2-1 Flow of Status Change Process
As the SFC block receives a status change command, the feasibility of the commanded change and
the interrupt processes are checked in relation to the current status. The conditions for block status
changes are shown below:
Table 1.6.2-1 Feasibility of Block Status Change
Status commanded for change(*1)

Current status
STOP RUN PAUS RSET ABRT
STOP (*2) xx xx - -
RUN xx (*2) xx - x
PAUS xx xx (*2) - x
ABRT - - - x (*2)
*1: xx: Status change feasible. Both pre- & post-processes executable.
x: Status change feasible, but pre- & post-processes not executable.
-: Status change not feasible.
*2: Command ignored.
Feasibility Checking
The command to change the current block status of STOP to RUN or PAUS is executed, interrupting
the main program to start the pre-process; a change to RSET, ABRT, or STOP causes error. A
change to RSET is accepted only when the current status is ABRT.
A change to ABRT is accepted when the current status is RUN or PAUS. When the command to
change the current status to ABRT is received, the SFC block is forcibly terminated and the status is
changed to ABRT; the pre-process is executed when feasible.
The command to change the status to ABRT is a command to forcibly

terminate the SFC block and should not be used during normal operation. It
may be used if the SFC block is locked due to application error causing infinite
looping during status-change post-processing, and so forth.
The change-to-ABRT command is different from other status change
commands as follows:
• Pre- and post-processing cannot be defined for the command.
• The command can be received even while another status change command
is being post-processed.
Pre-Processing
The feasibility of status change is determined in the pre-process. If the change is denied, the source
of the command is notified of the error. The status is changed as commanded if the pre-process is
not defined.
Status Changing
The status of the SFC block is changed as commanded when the change is justified both in the initial
check in relation to the current status and the check performed in pre-processing.
Post-Processing
Status-change post-processing is executed in accordance with the execution of the SFC block itself,
not with the receiving of the status change command.
Any additional status change command is prohibited until the current post-process is completed; the
command will be ignored if received, causing error.
Status-Change Pre-Process - SFC

The status-change pre-process is one-shot-executed upon receipt of the status change command
before changing the block status. There are three steps to describe status-change pre-process.
• Sequence table one-shot execution step (Sequence table one-shot)
• Logic chart one-shot execution step (Logic chart one-shot)
Since the status-change pre-process is one-shot-executed, it must be completed as quickly as
possible. Do not access data of another control station and delay the process. Only one step can be
executed as pre-process, where no transition condition can be defined.
Figure 1.6.2-2 Status-Change Pre-Process
With the SEBOL one-shot step, the feasibility of status change can be determined. With the
sequence table one-shot or logic chart one-shot step, the status can be changed. If the pre-process
is not defined, the status can also be changed. At the pre-process, the status and mode of the pre-
process-described SFC block or other SFC blocks cannot be changed.
Pre-Processing Using SEBOL Oneshot Step

The SEBOL oneshot step is completed when the last line, or “return” or “quit” statement has been
executed.
If the last line or “quit” statement has been executed, the feasibility of status change is justified. If
the “return” statement has been executed, the feasibility of status change is determined according
to the returned value as follows:
Figure 1.6.2-3 Status-Change Permission
The SEBOL oneshot step in which the pre-process is defined has the following additional restrictions
over the normal steps:
• “exit” statement cannot be used. Error is caused if used.
• “signal” statement cannot be used. Error is caused if used.
• “qsigcancel” and “qsigmove” statements cannot be used. Error is caused if used.
• “isigmask” and “isigunmask” statements cannot be used. Error is caused if used.
• “semlock”: and “semunlock” statements cannot be used. Error is caused if used.
• In the case of fatal error, only a SEBOL error message is output and the SFC block is not
terminated. Any status change will be denied.
• When an execution error is detected, no branching is made to common error processing and a
SEBOL error message is output. Any status change will be denied.
• The block status and mode of the present SFC block or any other SFC block cannot be changed.
Pre-Processing Using Sequence Table One-Shot Step

With the sequence table one-shot step, the status can be changed. The block status and mode
cannot be changed in pre-processing for the SFC block in which the pre-process is defined or for any
other SFC block.
Pre-Processing Using Logic Chart One-Shot Step

With the logic chart one-shot step, the status can be changed. At the pre-processing, the status of
the pre-process-described SFC block or other SFC blocks cannot be changed.
Status-Change Post-Process - SFC

The status-change post-process is executed after the status has been changed. The process is
executed as an interrupt signal processing, interrupting the main program in accordance with the
basic scan period of the SFC block.
Both step and selective sequences can be used in the post-process. Any additional status change
command is prohibited until the current post-process is completed; the command will be ignored if
received, causing error.
The post-process should not be kept suspended by means of a selective

sequence transition condition, or a “wait until,” “compare,” or “dialogue”
statement. If the process is suspended, the block status cannot then be
changed unless the program is forcibly terminated using a command to
change to ABRT.
The execution of the post-process defined in a SEBOL step can be controlled using “quit”
and “return” statements:
• Using “quit” statement
Executing this statement in a step sequence terminates the current action and executes the next
step. Executing it in a selective sequence starts evaluation of transition conditions. Executing the
statement in the last post-process step terminates the process.
• Using “return” statement
Executing this statement terminates the post-process without executing the remaining steps. Any
operand specified in this statement will be ignored.
Referencing Block Status - SFC

Data item PREBSTS (previous block status) is used in the post-process to permit referencing the
block status before the change. When the status is changed, data item BSTS (block status) which
contains information on the status before the change is copied to PREBSTS. These two data items
are operated as follows:
1. The BSTS data is copied to PREBSTS.
2. BSTS is changed to the new block status.
The BSTS data is referenced to justify the change of block status for the pre-process. The PREBSTS
data is referenced to justify the status change for the post-process. Two cases of referencing BSTS
and PREBSTS are shown below:
• In the first case, the current status of RUN is changed to STOP as commanded.
• In the second case, the current status of PAUS is changed to STOP as commanded.
Table 1.6.2-2 BSTS & PREBSTS
RUN → STOP PAUS → STOP

Process being executed
BSTS PREBSTS BSTS PREBSTS
Status-change pre-process RUN (*1) PAUS (*1)
Status-change post-process STOP RUN STOP PAUS
*1: Status before changing to the commanded status.
Block Status Referencing in Pre-Process

An example of referencing the block status in the pre-process using the two cases described above:
switch (%.BSTS)
case "RUN":
!Process changing from RUN to STOP.
case "PAUS":
!Process changing from PAUS to STOP.
end switch
Block Status Referencing in Post-Process

An example of referencing the block status in the post-process using the two cases described above:
switch (%.PREBSTS)
case "RUN":
!Process when changed from RUN to STOP.
case "PAUS":
!Process when changed from PAUS to STOP.
end switch
1.6.3 Interrupt Signal Processing Page 1 of 2
1.6.3 Interrupt Signal Processing

Interrupt signal processing is executed interrupting the main program when an interrupt signal is
received.
Interrupt Signals - SFC

Interrupt signals are sent from the SFC block, sequence table and logic chart. Every interrupt signal
can be named using a character string of up to 8 bytes and attached with up to 8 parameters.
Whether a signal is taken as a queue signal or an interrupt signal depends on the definition in the
SFC block which receives the signal and cannot be specified at the signal source.
Queue and interrupt signals are distinguished as follows:
• Signals defined in the initial step using the “queue signal” statement are handled as queue signals.
• Signals having their names written at the entrance of interrupt signal processing are handled as
interrupt signals.
If the same name is used both in the initial-step definition and at the interrupt-signal entrance, an
error is caused.
Interrupt signals can be received only when the SFC block is in the RUN or PAUS status, any signal
transmitted is ignored otherwise and an error is returned to the source.
Interrupt signals received during the course of the PAUS status are stored in a queue and will be
processed when the status is changed to RUN restarting the block.
Interrupt Signal Processing - SFC

▼ Maximum Number of Receive Interrupt Signals
Interrupt signals are processed interrupting the main program, which resumes execution as soon as
the signal has been processed.
Figure 1.6.3-1 Interrupt Signal Processing
Interrupt signals can be processed only when the SFC block is in the RUN status. The signal
processing is canceled if the status is changed to PAUS during the processing and will not be
resumed when the status is returned to RUN.
If another interrupt signal is received while one is being processed, the received signal is queued
and will be processed as soon as the current processing is completed. The maximum number of
interrupt signals which can be queued can be defined for each SFC block using the Function Block
Detail Builder. The number is 5 at default and can be defined up to 99. The defined capacity
includes the signal currently being processed. If a signal is received when the queue is full, the
signal is ignored causing an error.
The execution of the interrupt signal process defined in a SEBOL step can be controlled using “quit”

Executing this statement terminates the current step action and executes the next step.
Executing it in a selective sequence starts evaluation of transition conditions. Executing the
statement in the last step of interrupt signal processing terminates the process.
Executing this statement terminates the process without executing the remaining steps. Any
Fetching Interrupt Signal Parameters

▼ Maximum Number of Interrupt Signal Parameters
Queue signal parameters can be fetched using built-in functions during interrupt signal processing.
Figure 1.6.3-2 Fetching Interrupt Signal Parameters

a long double-precision floating-point real-number function, and they are used to fetch character-
The maximum number of signals can be defined in a range of 2 to 8 (2 at default) for the parameter
attached to an interrupt signal. If the SFC block receives an interrupt signal exceeding its parameter
setting, the signal is ignored causing an error.
1.6.4 Error Processing Page 1 of 1
1.6.4 Error Processing

Error processing needs to be defined in an SFC block separately from the SFC block of the main
program. Only one set of processing can be described in one SFC block.
Error Processing Description

Similar to other interrupt processes, error processing needs to be defined in an SFC block separately
from the SFC block of the main program. Only one set of processing can be described in one SFC
block.
Both step and selective sequences can be used in error processing. It is necessary for a selective
sequence, however, that the transition conditions are so defined that they can be easily satisfied;
the process being executed when error is caused will not be resumed otherwise.
The execution of the error processing defined in a SEBOL step can be controlled using “quit”
Executing this statement in a step sequence terminates the current step action and executes the
next step. Executing it in a selective sequence starts evaluation of transition conditions. Executing
the statement in the last error processing step terminates the process.
Executing this statement terminates error processing without executing the remaining steps. Any
SEE For more information about common error processing, refer to:
1.6.5 Terminating SFC Block Execution Page 1 of 1
1.6.5 Terminating SFC Block Execution

The execution of the SFC block can be terminated as described below:
Programs Permitted of Terminating Execution

The execution of the SFC block can be terminated in one of the following manners:
• Executing an “exit” statement.
• Changing block data item BSTS to STOP.
The programs which permit terminating the block execution are as follows:
Table 1.6.5-1 Programs Permitted of Terminating Block Execution
Program “exit” statement(*1) BSTS change(*1)

Main program x x
Status-change pre-process - -
Status-change post-process x -
Interrupt signal processing x x
Common error processing x (*2)
*1: x: Definable.
–: Not definable.
*2: The feasibility of block status change during error processing is determined by the location where the
error involved has been caused. If the error is in the main program, the status can be changed. If the
error is in the status-change post-process, the status cannot be changed.
Termination Using “exit” Statement

Use the “exit” statement to terminate the block execution unconditionally, which can be written as
follows:
Figure 1.6.5-1 “exit” Statement
The block is terminated when the statement is executed and the block status changes to STOP. The
status change pre-/post-processes are not executed.
Termination by Changing Block Status

Set the command to change the status to STOP in data item BSTS as in the example shown below:
.......
.......
%.BSTS = "STOP"
.......
Status-change pre- and post-processes can be executed when changing the block status to STOP.
1.6.6 Pausing SFC Block Execution Page 1 of 4
1.6.6 Pausing SFC Block Execution

The execution of the SFC block is paused in one of the following conditions, which are further
described below:
• When the block mode is SEMI.
• When the block being executed receives the command to change the status to PAUS.
• When the block standing-by for execution receives the command to change the status to PAUS.
• When the block standing-by for execution in the SEMI mode receives the command to change
the status to RUN.
When the block is paused while a program line is being executed, how the interrupted action is
affected varies according to the contents of that line.
The restarting of the paused block is determined by the built-in function “ckstep” and action when
the block is restarted varies according to the condition of the block at the time of pause.
Pausing
The four conditions in which the SFC block is paused are described below, the paused block can be
restarted by commanding a status change to RUN in any of these conditions:
Block in SEMI Mode

When the block is in the SEMI mode and executed to the start of a main program step, the block
status changes from RUN to PAUS and the block pauses at the start of action.
• No status-change processing takes place at this time.
• Execution is not paused at the start of an interrupt processing step.
PAUS Command to Block in Execution

When the block being executed receives a PAUS command, the block status is changed from RUN to
PAUS and the block is paused.
• Status-change processing takes place.
• If the block is paused during a SEBOL-described action, the builder-defined PAUS position will be
applied to the restarting of the block.
• If the block is paused during a sequence table described action, the block will be restarted from
the start of the step at all times even if the PAUS position is defined as the current line.
• If the block is paused during a sequence table or logic chart described action, the sequence table
or logic chart block mode changes from AUT to MAN.
PAUS Command to Block at Stand-by for Execution

When the block standing-by for execution receives a PAUS command, the block status changes from
STOP to PAUS and the block is paused at the start of the initial step.
RUN Command to Block at Stand-by in SEMI Mode

When the block standing-by for execution in the SEMI mode receives a RUN command, the block
status changes from STOP to RUN and then to PAUS and the block is paused at the start of the
initial step.
• Status-change processing takes place for the STOP-RUN status change but does not for the RUN-
PAUS change.
• If post-processing is executed for the STOP-to-RUN change, the RUN-to-PAUS changes takes
place after the post-processing is completed.
• If an interrupt signal is received during the post-processing for the STOP-to-RUN change, the
signal is processed first when the post-processing is completed and then the RUN-to-PAUS
change takes place upon completion of the signal processing.
Pause-Interrupted Actions
Actions when the SFC block, for which the PAUS position is defined as the current line, is paused
during execution of a SEBOL step are described.
“dialogue” Statement Used

When the block has been paused while waiting for input from the operation and monitoring function
after executing a “dialogue” statement, the block is restarted from the line following the “dialogue”
statement unless the operator has not input anything. Since the “time” specified wait time advanced
even while the block is paused, a time-out error is caused if the wait time has been counted up
during the pause.
“delaycycle” and “delay” Statements Used

The time specified to “delaycycle” and “delay” statements advances even while the block is paused.
“wait until” and “compare” Statements Used

The time specified to “wait until” and “compare” statements advances even while the block is
paused. Comparison or condition evaluation is executed at lease once after the block is restarted,
however, even if the specified time has elapsed.
“semlock wait” Statement Used

When the block has been paused while waiting for the unlocking of semaphore, the block is
restarted from the line following the “semlock wait” statement if the semaphore has been unlocked
by another SFC block during the pause. If the semaphore has not been unlocked and is secured, the
state of waiting for the unlocking will be maintained.
“seqtable drivewait” Statement Used

When the block has been paused while waiting for the output of an SFC/SEBOL return event
message (%RE) from the sequence table after starting the sequence table using a “seqtable
drivewait” statement, the sequence table block mode remains AUT. The block is restarted from the
line following the “seqtable drivewait” statement if %RE is output from the sequence table during
the pause. If not, the state of waiting for the output will be maintained.
“logicchart drivewait” Statement Used

message (%RE) from the logic chart after starting the logic chart using a “logicchart drivewait”
statement, the logic chart block mode remains AUT. The block is restarted from the line following
the “logicchart drivewait” statement if %RE is output from the logic chart during the pause. If not,
the state of waiting for the output will be maintained.
Identification of Restart Condition

The data returned when the built-in function “ckstep” is executed identifies the condition in which
the SFC block has been restarted.
“ckstep” return values are as follows:
• Data returned 1
When SFC block is restarted after changing STEPNO in the PAUS mode.
• Data returned 2
When SFC block is restarted without changing STEPNO in the PAUS mode.
• Data returned 0
In cases other than listed above.
“ckstep” Returns “2”

“ckstep” returns “2” when the SFC block, for which the PAUS position defined as the start of the
step, was paused by a PAUS command and restarted without changing STEPNO.
TIP For the SFC block with the PAUS position defined as the current line, “ckstep” returns the same
data when the block was paused by a PAUS command and restarted without changing STEPNO.
Even after the block has been restarted, “ckstep” returns the same data as that returned before
the pause.

“ckstep” returns “1” when the SFC block was paused, STEPNO has been changed, and then
restarted.
Cases of “0” Returned by “ckstep”

• When the block is being executed without being paused.
• When the block was paused at the start of a step in the SEMI mode and has been restarted
without changing STEPNO.
• For interrupt signal processing, “0” is returned at all times.
• For status-change pre-processing, “0” is returned at all times.
• For status-change post-processing, “0” is returned at all times.
• For error processing, “0” is returned at all times.
• When the built-in function “ckstepcl” is executed to clear the status following a pause.
• When the action of the restarted step has been completed.
SEE For more information about changing of data item STEPNO, refer to:
ALSO 1.6.8, "Changing Current Step"
Restarting Actions
Actions when the SFC block is restarted with its status changed to RUN are described:
Restarting after Paused during SEBOL-Defined Action

The block restarts execution from the PAUS position defined on Function Block Detail Builder.
Execution is restarted from the start of the action when the start of the step is builder-defined, or
resumed from where the action was interrupted when the current line is builder-defined.
Restarting after Paused during Sequence Table or Logic Chart-

Defined Action
The block restarts execution from the start of the step regardless of the PAUS position defined on
Function Block Detail Builder.
Restarting after Paused during Transition Evaluation

Evaluation is restarted from the leftmost transition condition.
Restarting after Paused during Interrupt Signal Processing

The interrupt signal process is canceled and not resumed when the block is restarted.
Handling of Queued Signals when Restarted

Any signals already queued when the block was paused remain in the queue when the block is
restarted.
Handling of Signal Received during Pause

Any signals received during the pause are queued and available when the block is restarted.
Restarting After Paused during Error Processing

Restarting action varies depending on whether post-processing is executed or not when PAUS was
commanded.
• When post-processing is not executed
The block is restarted first resuming the interrupted error processing and then resuming the main
program from the builder-defined PAUS position.
• When post-processing is executed
The ongoing error processing is completed first and then the block status is changed and post-
processed when PAUS is commanded. The block resumes execution of the main program from
the builder-defined PAUS position when restarted.
1.6.7 Referencing Current Step Page 1 of 1
1.6.7 Referencing Current Step

The step number of the step being executed in the SFC block main program can be referenced.
Procedure
Data item STEPNO is used to reference the step number of the step being executed. As the
execution of the main program advances, the step number of the current step is sent to STEPNO.
TIP Data item PHASE is used to hold the name of the current process, which can also be referenced
to check the progress of the block execution. When using PHASE, however, every phase in
program steps should be uniquely named.
1.6.8 Changing Current Step Page 1 of 1
1.6.8 Changing Current Step

The following items as to changing the current step are explained in this section.
• Procedure
• Restrictions
• Actions after STEPNO change
Procedure
The number of the current step can be changed by changing the step number set in main program
data item STEPNO when the block is the PAUS status. The use of STEPNO, however, is only
applicable to main program steps but not to interrupt program steps.
Note Points
The number of the current step cannot be changed in the following cases:
• When status-change pre- or post-processing is being executed, even if the block is in the PAUS
status.
• Step numbers in the present SFC block cannot be changed, doing so causes error when executed.
Actions after STEPNO Change

Actions following a step number change are as follows:
• No user-defined application program can be executed following a step number change.
• When the block with the PAUS position defined as the current line is paused, the restarting
position may be changed to the start of step action by setting the current step number in
STEPNO.
• When the block is paused during transition condition evaluation, the restarting position may be
changed to the start of step action by setting the current step number in STEPNO.
• The current STEPNO data is retained when the block status is changed to STOP.
• The block is restarted from the start of step action when a change to the RUN status is
commanded after STEPNO has been changed.
• The condition in which the block has been restarted can be identified using built-in
function “ckstep.”
1.6.9 SFC Block Alarm Processing Page 1 of 2
1.6.9 SFC Block Alarm Processing

The SFC block alarm processing and alarm status indication can be scripted using SEBOL when
required.
SFC Block Alarm Processing Scripts

Unlike regulatory control function blocks, SFC blocks do not have built-in alarm processing functions.
Thus alarm processing and alarm status indication must be programmed using SEBOL, if required.
There are four process alarm related data items of the SFC block shown as follows:
• ALRM (Alarm Status)
• AF (Alarm Detection)
• AOFS (Alarm Inhibition)
• AFLS (Alarm Flashing Status)
ALRM (Alarm Status)
The alarm status strings for indicating SFC alarm status contains 23 user-defined strings and a NR
string (string for normal status), which can be specified for all SFC blocks.
If there is no alarm status is in active state, the data item ALRM will be in NR status.
When using a “prcsalarm” statement in a SEBOL step, an alarm status string and a process alarm
can be output together. Using “prcsalarm recover” statement can recover from the alarm status.
SEE For more information about AF, AOFS and AFLS, refer to:
ALSO 5.13, “Deactivate Alarm Detection” in Function Blocks Overview (IM 33J15A20-01EN)
5.14, “Alarm Inhibition (Alarm OFF)” in Function Blocks Overview (IM 33J15A20-01EN)
5.15.1, “Alarm Display Flashing Actions” in Function Blocks Overview (IM 33J15A20-01EN)
For more information about changing and referencing alarm data items, refer to:
5.10, “Referencing Alarm Status” in SEBOL Reference (IM 33J05L20-01EN)
5.12, “Referencing Alarm Status Individually” in SEBOL Reference (IM 33J05L20-01EN)
For more information about alarm status character strings, refer to:
“ User-Defined Alarm Status Character String” in 7.4, “Alarm Status Character String and
Alarm Processing” in Human Interface Stations Reference Vol.2 (IM 33J05A11-01EN)
Changing Alarm Status for Present SFC Block

Data items AF, AOFS, and AFLS of the present SFC block can be changed so that the block’s alarm
status can all be group-controlled. The following alarm status-change commands are used:
Table 1.6.9-1 Alarm Status Change Commands
Status-change command
Data item
AOF AON ACK
AF Alarm detection group-bypassing. Alarm group-suppression. -
AOFS Undo group-bypassing. Undo group-suppression. -
AFLS - - Alarm group-acknowledging.
Changing Alarms of Other SFC Blocks
1.6.9 SFC Block Alarm Processing Page 2 of 2
Process alarms of other SFC blocks can be controlled changing data items AF and AOFS.
The SFC block with its data item AF externally specified for the group-bypassing of alarm detection,
for example, will not output any process alarm and the alarm status will not be changed even when
the “prcsalarm” statement is executed by the present block. Also, changing data item AFLS permits
alarm acknowledging while disabling flashing.
Alarm Data Items

The alarm data items are initialized as follows:
Table 1.6.9-2 Data Item Initialization
Data When initialization When SFC block Builder

Name
item started executed default
ALRM Alarm status NR NR
Alarm detection
AF
specification Previous status
maintained Previous status Despecified
Alarm suppression
AOFS maintained status
specification
AFLS Alarm flashing status
The alarm status is initialized to the normal status (NR) when the SFC block is executed. When the
execution of the block is terminated with any process alarm caused, the normal state is recovered
when the block is executed again. This is the same when the block mode is changed from O/S to
AUT.
Alarm Repeating - SFC Block

If an alarm state is not normalized for a predetermined period of time, repeating alarm defined on
FCS Constants Builder will be caused as long as the SFC block is being executed or paused. The
repeating alarm is not caused for the SFC block not being executed or paused, nor if the execution
of the block has been terminated with a process alarm caused.
Actions related to repeating alarms are otherwise the same as other function blocks.
SEE For more information about Repeated Warning Alarm, refer to:
ALSO 5.15.2, “Repeated Warning Alarm” in Function Blocks Overview (IM 33J15A20-01EN)
1.6.10 SFC Online Maintenance Page 1 of 1
1.6.10 SFC Online Maintenance

In online maintenance operation, SFC block databases can be manipulated for system retrofitting,
modification, and so forth.
Characteristic of SFC Block Online Maintenance

Only the SFC block requiring maintenance is stopped and only the part to be manipulated is
downloaded to FCS for online maintenance so that other control functions will remain unaffected.
The online SFC block maintenance is different as described below from the normal maintenance of
regulatory control block, sequence control block, calculation block, and faceplate block functions:
• Online maintenance operation cannot be performed on the SFC block if it is in the RUN or PAUS
status but can be performed only in the STOP or ABRT status.
• The SFC block mode changes to O/S during online maintenance operation. The block status
changes to STOP and the mode returns to the previous mode.
• After the downloading for online maintenance, the execution of the SFC block is resumed when
the status is changed to RUN from the operation and monitoring function or user-defined
application program.
Block Code Definition

SFC block codes cannot be changed, deleted, nor added. The block’s user-defined data items can be
changed, deleted, or added, however.
Block Manipulation
SFC block can be added, deleted and changed under the following circumstances:
Adding SFC block: The maximum number of SFC blocks in the FCS is not reached.
Deleting SFC block: The SFC block is stopped.
Changing SFC block: The SFC block is stopped.
1.6.11 SFC Block Execution Page 1 of 1
1.6.11 SFC Block Execution

SFC blocks are executed in the idle time of one control period after the execution of all other basic
control functions.
Order of Execution
SFC blocks are repeatedly executed in the basic scan period according to the following rules:
• SFC blocks are executed in the idle time available after the execution of all other basic control
functions has been completed, which include regulatory control, sequence control, calculation,
and faceplate blocks. The rule also applies when both basic control functions and SFC blocks
reside in the same control drawing.
• SFC blocks are infinitely executed within one scan period during the time available after the
execution of other basic control functions. In the next scan period, execution is resumed from
where it was interrupted last.
• SFC blocks are not executed and terminated if sufficient time is not available after the execution
of other basic control functions. In the next scan period, execution is resumed from where it was
interrupted last.
An example of two control drawings each defined with three SFC blocks is shown below. SFC blocks
are assigned with time for execution in the numbered order:
Figure 1.6.11-1 The Order of Execution Time Allocation
After the last SFC block 6 in control drawing 2 was allocated with execution time, the order returns
to the top SFC block 1 in control drawing 1 and execution time is reallocated. Execution time is not
allocated to any SFC blocks which are not being executed.
However, the SFC blocks and perations that consist of periodic SEBOL programs are executed at
each basic scan.
1.6.12 Data Items - SFC Page 1 of 7
1.6.12 Data Items - SFC

SFC blocks use system-specific and user-defined data items. Every different SFC block using a
different group of data items needs to be differently coded. If a group of same data items is used by
a number of blocks, the blocks can be identically coded and they can share the same group of data
items.
SFC Block Models

It is necessary to define SFC block model as follows:
1. Select one of the three available models of system-specific data sets (see below).
2. Specify the name and data type for the user-defined data item to be used. Different SFC block
codes are needed for different models as well as different user-defined data items.
The following three SFC block models are available:
• _SFCSW: 3-position switch
• _SFCPB: Pushbutton
• _SFCAS: Analog
The following are their details:
Table 1.6.12-1 Details of Models
Model
Item
_SFCSW _SFCPB _SFCAS
No. of items 32 32 32
User-defined data item high limit
Max. area size 8180 bytes 8180 bytes 8180 bytes
Data item comment Availability Not available Available Available
3-position-switch type x - -
Instrument faceplate 5-pushbutton type - x -
Basic type - - x
None x x -
Trend
PV, SV, MV - - x
The instrument faceplates of the three block models are shown below:
Figure 1.6.12-1 SFC Block Instrument Faceplates
System-Specific Data Items
▼ System Definition Data Items

SFC block system-specific data items and their availability in block models are listed below:
Table 1.6.12-2 System-Specific Data Items & Block Models (1/2)
SFC block model(*1)

Data item Data name
MODE Block mode x x x
OMOD Block mode (lowest priority) x x x
CMOD Block mode (highest priority) x x x
BSTS Block status x x x
PREBSTS Previous block status x x x
ALRM Alarm x x x
AFLS Alarm flashing x x x
AF Alarm detection x x x
AOFS Alarm suppression x x x
ERRC Classified error code x x x
ERRE Detailed error code x x x
ERRP Error-caused plane number x x x
ERRS Error-caused step number x x x
ERRL Error-caused line number x x x
ERRF Error-caused program unit x x x
STEPNO Current-step number x x x
PHASE Phase name x x x
IPHASE Interrupt-phase name x x x
*1: x: Available
Table 1.6.12-3 System-Specific Data Items & Block Models (2/2)
SFC block model(*1)

Data item Data name
OPMK Operation mark x x x
UAID User application ID x x x
DILG Dialog acknowledgement x x x
SEMA Semaphore name x x x
SWLB[5] Switch label - x x
SWCR[5] Switch display color - x x
SWST[5] Switch flashing status - x x
SWOP[5] Switch operation disable status - x x
PV Process variable - - x
SV Setpoint value - - x
MV Manipulated output value - - x
SH Scale high-limit value - - x
SL Scale low-limit value - - x
SVH Setpoint high limit - - x
SVL Setpoint low limit - - x
MH Manipulated variable high-limit setpoint - - x

ML Manipulated variable low-limit setpoint - - x
MSH MV scale high limit - - x
MSL MV scale low limit - - x
*1: x: Available
–: Not available
The accessibility of the system-specific data items is shown below:

Table 1.6.12-4 System-Specific Data Item Accessibility (1/2)
SEBOL(*1) General-purpose calculation block(*1) Sequence table(*1)

Data item
Read Write Read Write Condition Manipulation
MODE x x x(*2) x(*2) x x
OMOD x - - - - -
CMOD x - - - - -
BSTS x x x(*2) x(*2) x x
PREBSTS x - - - x -
ALRM x - x(*2) - x -
AFLS x x x(*2) x(*2) x x
AF x x x(*2) x(*2) x x
AOFS x x x(*2) x(*2) x x
ERRC x - x - - -
ERRE x - x - - -
ERRP x - x - - -
ERRS x - x - - -
ERRL x - x - - -
ERRF x - x - - -
STEPNO (*3) x x x x x x
PHASE x - x - - -
IPHASE x - x - - -
*1: x: Accessible
–: Not available
*2: Accessible by connecting sequences.
*3: See 1.6.8, “Changing Current Step,” for restrictions.
Table 1.6.12-5 System-Specific Data Item Accessibility (2/2)
SEBOL(*1) General-purpose calculation block(*1) Sequence table(*1)

Data item
Read Write Read Write Condition Manipulation
OPMK x x x x - -
UAID x x x x - -
DILG x x x x - -
SEMA x - x - - -
SWLB[5] x x x x - -
SWCR[5] x x x x x x
SWST[5] x x x x x x
SWOP[5] x x x x x x
PV x x x x - -
SV x x x x - -
MV x x x x - -
SH x - x - - -
SL x - x - - -
SVH x x x x - -
SVL x x x x - -
MH x x x x - -
ML x x x x - -
MSH x - x - - -
MSL x - x - - -
*1: x: Accessible
–: Not available
SEE For more information about setting step numbers, refer to:
Step-Number & Phase-Name Data Items

Step numbers and phase names are set in the following data items:
• Main program
Step No.: STEPNO
Phase name: PHASE
• Interrupt programs
Step No.: None
Phase name: IPHASE
The main program current step number is set at STEPNO and current phase name at PHASE. The
interrupt program current phase name is set at IPHASE. During the execution of an interrupt
program, the step number and the phase name of the main program when the interrupt program
was invoked are retained at STEPNO and PHASE respectively.
TIP One exception with interrupt programs is that the phase name of status-change pre-processing is
not set at IPHASE.
When interrupt programs of different levels are being executed simultaneously, only the phase name
of the highest-level interrupt program is set at IPHASE. A null-length character string (“”) is set at
IPHASE for a regular-level interrupt program.
Default STEPNO, PHASE, and IPHASE are as follows:
Table 1.6.12-6 Default STEPNO, PHASE, & IPHASE
Data Builder
Name At initialization At SFC block start
item default
Step number of initial
STEPNO Current step number 0
step
Phase name of initial

PHASE Phase name “” (*1)
Previous state step
Interrupt program phase retained
IPHASE “” (*1) “” (*1)
name
*1: Null-length character string.
Alarm Data Items

ALRM, AFLS, AF, and AOFS are process alarm data items.
SEE For more information about SFC Block Alarm Processing, refer to:
ALSO 1.6.9, "SFC Block Alarm Processing"
Error Data Items

When an error is caused, the classified error code is set at ERRC and the detailed error code at
ERRE. The error-caused plane number is set at ERRP and the error-caused step number at ERRS,
making it easy to identify the location of the error caused.
• When an error is detected in a SEBOL-described action, ERRL identifies the error-caused line
number and ERRF identifies the error-caused function name. A null-length character string is set
at ERRF if the detected error is in the main program.
• When an error is detected in a sequence table-described action, 0 is set at ERRL and a null-
length character string at ERRF.
• When an error is detected in a transitional condition, the negative transition condition number (-1
through -8) is set at ERRL and a null-length character string at ERRF.
User-Defined Data Items

In addition to the system-specific data items, up to 32 data items can be optionally user-defined,
using up to 8180 bytes in total.
Date Types Available

The following data types can be used for user-defined data items:
Table 1.6.12-7 Data Types of User-Defined Data Items
Data type Symbol No. of bits Min. data Max. data

Character string CHRn 8*n bits n=2 n=16
Integer I16 16 bits -32768 32767
Long integer I32 32 bits -2147483648 2147483647
38 38
Single-precision floating point F32 32 bits -3.402823*10 3.402823*10
308 308
Double-precision floating point F64 64 bits -1.79769313486231*10 1.79769313486231*10
Simple variables and one- and two-dimensional arrays can be used with every type. Up to 999 array
elements can be used and up to 10000 elements can be used for arrays 1 and 2 in total. The data
status-attached data type is not available.
Mainly, the following settings may be defined for a user defined data item of SFC block.
• Data item name
• Data type
• Array element 1
• Array element 2
• Data item comment
Accessing User-Defined Data Items

Accessing user-defined data items from function blocks and some restrictions are as follows:
• Data as well as sequences can be connected for user-defined data items.
• User-defined data items cannot be described in the condition and action signal columns of a
sequence table.
• In the case of general-purpose calculation blocks (CALCU, CALCU-C), user-defined data items
cannot be accessed even if “<tag name>.<data item name>” is directly specified in the block.
• User-defined data items can be accessed from SEBOL programs in SFC blocks.
• SFC block queue signals can be referenced when a CHR16 one-dimensional array named QUEUE
is defined as a user-defined data item.
SEBOL data-type specifiers for data-type symbols are listed below:
CHR2 to CHR16: char *2 to char*16
I16: integer
I32: long
F32: float
F64: double
SEE For more information about queue signals, refer to:

ALSO 1.6.1, "Queue Signal Processing"
Definition Items for User-Defined Data Items

▼ User Definition Data Items
The definition Items for user defined-data items of an SFC block are the same as those of a unit
instrument. However, the user-defined data items of an SFC block differ from those of a unit
instrument in the following points:
• Entry Method
For menu labels, menu data, and menu numbers, memory areas are used in units of "sets." For
an SFC block, menu labels, menu data, and menu numbers can be defined to use up to four sets
in total.
TIP The following table shows how the number of sets used is determined.
Table 1.6.12-8 Maximum Number That You Define and the Number of Sets Used
Maximum number that you define for Menu Label, Menu Data, or Menu Number of sets
Number used
1 to 16 1
17 to 32 2
33 to 48 3
49 to 64 4
• Check
For an SFC block, user-defined check can be specified for up to four user-defined data items.
SEE For more information about the definition items of user-defined data items of a unit instrument,
ALSO refer to:
" Definition of User Definable Data Item" in 2.3.3, "User-Definable Data Items"
For more information about number of patterns for checking the entered data and the number of
menu definitions for user-defined data items of FFCS-R, refer to:
“ Number of patterns for checking the entered data and the number of menu definitions for
user-defined data items” in 6., “Function blocks” in FCS for RIO System Upgrade Reference
(IM 33J01B10-01EN)
1.6.13 SFC Block Mode & Status Page 1 of 3
1.6.13 SFC Block Mode & Status

The modes, status, and status transition of SFC blocks are described.
Block Modes - SFC

▼ SEMI Mode Operation
The SFC block has three control modes.
Description of Modes - SFC

The control status in each block mode is described below:
• O/S
Out-of-service
• SEMI
Semi automatic
• AUT
Automatic
The actions of SFC block in each block mode are shown below:
• AUT (automatic) mode
Every step is successively executed.
• SEMI (semi-automatic) mode
The block stops at the start of each step, and the step is executed at a command from the
operation and monitoring function, etc. The mode can be enabled or disabled for each block.
• O/S (out-of-service) mode
The block cannot be executed. Online maintenance operation is performed in this mode.
Rules for Changing Block Modes - SFC

The following rules are applied to the changing of block modes:
• The mode cannot be changed to O/S when the block status is RUN or PAUS.
• The block status remains unchanged when the block mode is changed to O/S.
• The block status changes to STOP when the block mode is changed from AUT to O/S, or from
O/S to SEMI.
• The block status cannot be changed when the block mode is O/S.
• The block mode can be changed from AUT to SEMI or vice versa without any restriction, except
that the mode cannot be change to SEMI if its use is prohibited by the builder.
• No user applications can be executed following a block mode change.
An example of changing the mode of the SFC block tag-named SFC001 using a SEBOL program is
shown below:
......
SFC001.MODE = "SEMI"
......
SFC001.MODE = "AUT"
......
SFC Block Status

The SFC block status shows the SFC block operation status as executing, paused, stopped, and
aborted.
The SFC block has four status as described below:
Table 1.6.13-1 SFC Block Status
Name Status Description

STOP Stopped The block is stopped and standing-by for a start command.
RUN Executing Step actions are being executed or transition conditions are being evaluated.
PAUS Paused Execution is suspended.
ABRT Aborted Execution has been aborted due to fatal or internal error or insufficient memory.
The following commands are used to change the block status:

• RUN
Changes status to RUN, starting execution of the block or restarting the paused block.
• STOP
Changes status to STOP, stopping execution of the block.
• PAUS
Changes status to PAUS, suspending execution of the block.
• RSET
Resets status of the aborted block to STOP.
• ABRT
Changes status to ABRT, forcibly terminating execution of the block.
Transition of SFC Block Status

▼ PAUS Stop Position
The transition of block status when the SFC block is in the AUT or SEMI mode is described.
Figure 1.6.13-1 Transition of Block Status
• The RUN command starts execution of the SFC block in the STOP status, which then changes to
RUN when started.
• The PAUS command suspends execution of the SFC block in the STOP status at the start of the
initial step, the status then changes to PAUS.
• The stopping position when the status is changed to PAUS during execution of a SEBOL step
action can be specified either at the start of the step or the current program line.
• In the SEMI mode, the block status changes from RUN to PAUS at the start of every step. The
step can then be executed upon receiving the RUN command from the operation and monitoring
function, etc.
An example of changing the status of the SFC block tag-named SFC001 using a SEBOL program is
shown below, in which a status change command character string is entered on the right-hand side
of each assignment statement:
.....
SFC001.BSTS = "RUN"
......
SFC001.BSTS = "PAUS"
......
SFC001.BSTS = "STOP"
......
1.7 Manipulating Unit Instrument from SFC Block Page 1 of 2
1.7 Manipulating Unit Instrument from SFC

Block
Accessing unit data and transmitting signal to units from the SFC block are described.
Accessing Unit Data

Unit data can be accessed from the SFC block as described below.
Use one of the following manners to access unit data:
• Declare the unit tag name using the “block” or “global block” statement. Or assign the unit tag
name using the “assign” statement to the local generic name in the “genname” statement or the
global generic name in the “global genname” statement.
• Define the unit data name in place of the function block data item name.
An example of accessing unit data from a SEBOL step is shown below:
!_UTSW is the unit model name.
block _UTSW UNIT001
char*8 umode, ustat
!Acquire the mode.
umode = UNIT001.MODE
!Acquire the status.
ustat = UNIT001.BSTS
.....
The <block model> referred by “block” statement, or etc., are the model name of unit function
blocks displayed in the Function Block Detail Builder.
The following three models of unit are supported.
• _UTSW:Non-Resident Unit Instrument with Three-Position Switch
• _UTPB:Non-Resident Unit Instrument with Five-Pushbutton Switch
• _UTAS:Analog Non-Resident Unit Instrument
SEE For more information about unit instruments, refer to:

ALSO 2.2, "Unit Instrument"
Transmitting Signals to Units

Signals can be transmitted to units from the SFC block using the “signal” statement. Upon receiving
a signal, the unit sends the same signal to every unit operation being executed.
1.7 Manipulating Unit Instrument from SFC Block Page 2 of 2
Figure 1.7-1 Transmitting Signals to Units
It is required to designate a <tag name> when unit instrument transmitting a signal. If the unit tag
name is not specified, the signal is transmitted to the present unit.
The “signal” statement is normally terminated when the signal has been received by operations of
the destination unit. Error is caused if none of unit operations receive the signal.
TIP The “signal” statement is used for transmitting both queue and interrupt signals.
SEE For more information about operations, refer to:

ALSO 2.8, "Operations"
2. Unit Supervision Page 1 of 1
2. Unit Supervision
Unit Supervision is an operating and monitoring activity for controlling the devices grouped as a unit,
of batch process or continuous process. Unit Supervision may define a group of processing devices
as a “unit,” each “unit” may be assigned with a “unit instrument,” so that the operation on the
grouped devices may be carried out as a unit.
Usually, the devices of a process are operated and monitored individually, when applying Unit
Supervision, a plant may be operated in a much-simplified manner.
2.1 Outline of Unit Supervision Page 1 of 1
2.1 Outline of Unit Supervision

In this section, Unit Supervision of CENTUM VP is explained.
2.1.1 What is a Unit? Page 1 of 2
2.1.1 What is a Unit?

A unit is a group of device modules for controlling main process procedures in a plant, such as the
modules, assigned with tag names, for distillation columns or reactors. So that the operation may be
carried out by groups instead of individual devices. Control and management for devices can be
performed cooperatively as a grouped unit.
A Continuous Process Unit

When a complicated application for process control and management is applied to a continuous
process, many sequence tables may be used. Using the Unit Supervision, the process management
may be controlled by a single unit instrument, and the detailed process steps may be controlled by
the operations related to the unit instrument.
Figure 2.1.1-1 A Continuous Process (Cracking Furnace) Unit
Figure 2.1.1-2 Decoking Work Flow
A Batch Process Unit

In batch processing for a chemical plant, devices used for control operations are grouped into
2.1.1 What is a Unit? Page 2 of 2
several equipment entities for different processes, such as reaction process and crystallization
process. By assigning a unit instrument to each group, operation can be performed by equipment
entities.
Figure 2.1.1-3 A Batch Process Unit
SEE For more information about Batch Management, refer to:

ALSO 4., “Unit Supervision under Batch Management” in Batch Management System Reference (IM
33J05L10-01EN)
2.1.2 Application Capacity of Unit Supervision Page 1 of 5
2.1.2 Application Capacity of Unit Supervision

Application capacity for Unit Supervision is described below.
Application Capacity of PFCS

Table 2.1.2-1 Application Capacity of PFCS
Item Max. capacity

No. of units 2 per FCS, 10 per FCS, 15 per FCS(*1)
No. of operation 30 per FCS, 100 per FCS, 120 per FCS(*1)
No. of generic tag names (arrays) 256 per unit
No. of generic tag names (array elements) 512 per unit
Resident unit 64 per unit
No. of operation generic names
Nonresident unit 99 per unit
No. of user-defined data items 256 per unit
User-defined data memory size 32768 byte per unit
No. of unit procedure steps 99 steps
No. of SFC operation steps 99 steps
No. of Transitional Matrixes 16 per project
*1: The maximum number varies with the FCS database types.
SEE For more information about FCS database type of PFCS, refer to:
ALSO “ FCS Database Types Selectable in the Standard Type PFCS : PFCS” in “ Define Database
Type” in 2.4.1, “Creating a New FCS” in Engineering Reference Vol.1 (IM 33J10D10-01EN)
“ FCS Database Types Selectable in the Enhanced Type PFCS : PFCS” in “ Define Database
Type” in 2.4.1, “Creating a New FCS” in Engineering Reference Vol.1 (IM 33J10D10-01EN)
Application Capacity of SFCS

Table 2.1.2-2 Application Capacity of SFCS
Item Max. capacity

No. of unit instruments 20 per FCS (*1)
No. of operations 150 per FCS (*1)
No. of generic operation names 99 per unit
SEE For more information about FCS database type of SFCS, refer to:
ALSO “ FCS Database Types Selectable in the SFCS : SFCS” in “ Define Database Type” in
2.4.1, “Creating a New FCS” in Engineering Reference Vol.1 (IM 33J10D10-01EN)
Application Capacity of LFCS

Table 2.1.2-3 Application Capacity of LFCS
Item Max. capacity

No. of unit instruments 5 per FCS, 35 per FCS, 30 per FCS (*1)
No. of operation 20 per FCS, 250 per FCS, 200 per FCS (*1)
SEE For more information about FCS database type of LFCS, refer to:
ALSO “ FCS Database Types Selectable in the LFCS : LFCS” in “ Define Database Type” in
Application Capacity of LFCS2

Table 2.1.2-4 Application Capacity of LFCS2
Item Max. capacity

No. of operation 400 per FCS (*1)
SEE For more information about FCS database type of LFCS2, refer to:
ALSO “ FCS Database Types Selectable in the LFCS2 : LFCS2” in “ Define Database Type” in
Application Capacity of KFCS

Table 2.1.2-5 Application Capacity of KFCS
Item Max. capacity

No. of unit instruments 5 per FCS, 30 per FCS (*1)
No. of operation 20 per FCS, 250 per FCS, 200 per FCS (*1)
SEE For more information about FCS database type of KFCS, refer to:
ALSO “ FCS Database Types Selectable in the KFCS : KFCS” in “ Define Database Type” in
Application Capacity of KFCS2

Table 2.1.2-6 Application Capacity of KFCS2
Item Max. capacity

SEE For more information about FCS database type of KFCS2, refer to:
ALSO “ FCS Database Types Selectable in the KFCS2 : KFCS2” in “ Define Database Type” in
Application Capacity of FFCS

Table 2.1.2-7 Application Capacity of FFCS
Item Max. capacity

No. of unit instruments 30 per FCS
No. of operation 200 per FCS
SEE For more information about FCS database type of FFCS, refer to:
ALSO “ FCS Database Types Selectable in the FFCS : FFCS” in “ Define Database Type” in
Application Capacity of FFCS-L

Table 2.1.2-8 Application Capacity of FFCS-L
Item Max. capacity

No. of unit instruments 30 per FCS, 60 per FCS(*1)
No. of operation 200 per FCS, 400 per FCS(*1)
SEE For more information about FCS database type of FFCS-L, refer to:
ALSO “ FCS Database Types Selectable in the FFCS-L : general-purpose and expanded” in “
Define Database Type” in 2.4.1, “Creating a New FCS” in Engineering Reference Vol.1 (IM
33J10D10-01EN)
Application Capacity of FFCS-C and FFCS-V

Table 2.1.2-9 Application Capacity of FFCS-C and FFCS-V
Item Max. capacity

No. of unit instruments 80 per FCS(*1)
No. of unit operation instruments 400 per FCS (*1)
99 per unit
No. of generic operation names
200 per unit instrument with recipe operation
No. of recipe operation procedure steps 99 steps
SEE For more information about FCS database type of FFCS-V, refer to:
ALSO “ FCS Database Types Selectable in the FFCS-V : General-Purpose, Extended Type, Large
Type, Batch Standard Type, Batch Extended Type and Batch Large Type” in “ Define
Database Type” in 2.4.1, “Creating a New FCS” in Engineering Reference Vol.1 (IM 33J10D10-
01EN)
For more information about FCS database type of FFCS-C, refer to:
“ FCS Database Types Selectable in the FFCS-C : General-Purpose, Extended Type, Large
Type, Batch Standard Type, Batch Extended Type and Batch Large Type” in “ Define
Database Type” in 2.4.1, “Creating a New FCS” in Engineering Reference Vol.1 (IM 33J10D10-
01EN)
2.2 Unit Instrument Page 1 of 4
2.2 Unit Instrument

Unit Instrument is a part of Unit Supervision application. Unit Instruments can be applied for
controlling and operating a series of processes, such as heating, agitation, reaction and distillation.
The process control can be carried out with the operations called from unit procedures, while the
unit procedures are called from the unit instrument.
Type of Unit Instruments

A unit instrument consists of unit instrument data items and unit procedures.
A unit procedure is an ordered set of operations for controlling the process of product manufacture.
An operation is an ordered set of the control sequences, the operations consist of the following
types.
• The operation may be started by a unit procedure
• The operation for real-time monitoring
• The operation for process initialization to the unit instrument execution.
• The operation for interrupt processing which interrupts to the sequentially started control
sequences.
The data items of a unit instrument are mainly for tuning parameters and monitoring the process.
Some data items on the unit instrument are user definable.
There are two types of unit instruments, resident type and non-resident type.
Resident Unit
A resident unit means that a unit instrument is assigned with fixed unit procedure (SFC). When the
manufacturing procedure for production is always the same, the resident unit may be applied.
Figure 2.2-1 Resident Unit Instrument
Non-Resident Unit
A non-resident unit means that a unit instrument is not assigned with fixed unit procedure. So that a
non-resident unit may use the recipe unit procedure created by Batch Management for application.
The recipe unit procedure may be downloaded to the specified non-resident unit instrument when
setting up the recipe.
The non-resident unit may be applied together with Batch Management.
Figure 2.2-2 Non-Resident Unit Instrument
The unit operation instrument is used when the recipe unit procedure of the unit instrument is to be
created by splitting it into more detailed processes.
SEE For more information about unit operation instruments, refer to:
ALSO 2.16, "Unit Operation Instrument under Batch Management"
Unit Instrument Block Models

They are categorized into two types, resident type and nonresident type. Each type consists of three
models.
Resident Unit Models

Resident unit instruments consist of the following three block models.
• _UTAS: Analog Unit Instrument
• _UTPB: Unit Instrument with Five-Pushbutton Switch
• _UTSW: Unit Instrument with Three-Position Switch
Nonresident Unit Models

Nonresident unit instruments consist of the following function block models.
• _UTAS-N: Analog Non-Resident Unit Instrument
• _UTPB-N: Non-Resident Unit Instrument with Five-Pushbutton Switch
• _UTSW-N: Non-Resident Unit Instrument with Three-Position Switch
• _UTAS-SN: Analog Non-Resident Unit Instrument with Recipe Operation
• _UTPB-SN: Non-Resident Unit Instrument with Five-Pushbutton Switch and Recipe Operation
• _UTSW-SN: Non-Resident Unit Instrument with Three-Position Switch and Recipe Operation
Unit Instrument Elements

A unit instrument is constructed with the following elements.
Unit Instrument Data Items

The process data, the data controlled by the unit instrument such as the internal temperature and
pressure of a reactor can be assigned to the unit instrument data items for control and monitoring.
The information related to the process flow such as the load factor and the operating rate, or the
quality, the name and the information related to the products being manufactured may be displayed
via instrument data items.
There are 4 types of data items for unit instrument, shown as follows.
• System fixed data items
• User definable data items
• Data items for faceplate (Fixed by each model of unit instrument)
• Data items for process management (Fixed by each model of unit instrument)
Unit Procedure
A unit procedure controls an ordered set of operations. An operation is a set of control sequences
corresponds to the physical equipment.
The unit procedure may be formed in an SFC (Sequential Function Chart), by registering the names
of operations to the step action columns of SFC.
A unit instrument may not only execute the operations started by the unit procedure but may also
execute the operation for initialization and the operation for monitoring.
Furthermore, the recipe unit procedure created by Batch Management can be used for a nonresident
unit procedure.
Operation
There are two types of operations are available, the operations programmed in SEBOL and
operations programmed in SFC. The data items of operations are not user definable.
In the operations programmed in SEBOL, the main process, status change process and signal
conditioning process are all written in SEBOL.
While in the operations programmed in SFC, the main process and status change process are
described by SFC, but the sequences in each step are described in SEBOL, sequence table, or logic
chart. There are 6 models of operations programmed in SFC are available, they are classified
according to their available data items.
• OPSFC SFC Operation
• OPSFCP1 SFC operation with floating-data parameters
• OPSFCP2 SFC operation with character-data parameters
• OPSFCP3 SFC operation with floating/character-data parameters
• OPSFCP4 SFC operation with integer/character-data parameters
• OPSFCP5 SFC operation with floating/integer-data parameters
Unit Mode and Unit Status
A unit instrument likes other function blocks also has mode and status.
The mode and status of a unit instrument are referred to as unit mode and unit status respectively.
The unit mode includes AUT, SEMI etc. may indicate the control mode of the unit instrument.
The unit status includes END, ABORTED etc. may indicate the operation state of the unit instrument.
State Transition Matrix

State transition matrix determines the states to transit corresponding to a unit mode change or a
unit status change.
When a unit mode change or a unit status change command is given, the unit instrument may
change its unit mode or unit status according to the state transition matrix to control the programs
and operations in the unit instrument.
Interrupt Processing
The interrupt processing is available when an operation started from a unit procedure is interrupted.
The interrupt processing to an operation may have the following activities.
• Processing prior to status change
An interrupt processing triggered by an one-shot command for unit mode or unit status change.
This processing allows SEBOL or other programs to check and give the permission for the block
status change.
• Processing after status change
An interrupt processing after a unit mode or a unit status change.
• Processing upon an interruption signal
Upon a designated signal, the specified interrupt processing may be executed.
Alarm Status
A unit instrument may display its alarm status just like other function blocks. With a SEBOL
statement (unit prcsalarm) scripted in an operation, the unit instrument may generate messages for
occurrence and recovery of an alarming status. The alarm messages generated by a unit instrument,
just like other function blocks, may be displayed on the process alarm view. Moreover, the alarm
priority, alarm detection, alarm inhibition and so on may be defined for the unit instrument alarms.
Message
There are following types of messages related to the unit instrument. Just like other function blocks,
the unit instrument related messages are also stored in the historical message save file in HIS.
• Unit process alarm occurrence/recovery message
• Unit mode/status change message
• Sequence message
• System alarm message
• Operation record message
2.3 Unit Instrument Data Items Page 1 of 1
2.3 Unit Instrument Data Items

Unit instrument data items are used to indicate the process data of unit-controlled equipment
modules. And the temperature and pressure of reactors and other process data such as material
feed quantities can be set on the data items.
Data Types of Unit Instrument

The data can be used on the unit instrument data items are shown below. Different from the data of
function blocks, the data of unit instruments are not attached with data status information.
Table 2.3-1 Unit Instrument Data Types
Type Description Remarks

I16 16-bit signed integer -32768 to 32767
U32 32-bit unsigned integer 0 to 4294967295
38 38
F32 Single-precision floating-point (32 bits) -3.402823 • 10 to 3.402823 • 10
F64 Double-precision floating-point (64 bits) -1.79769313486231 • 10308 to 1.79769313486231 • 10308
CHR*n Character-string (2≤n≤16) -
Data Items of Unit Instrument

A unit instrument has the following groups of data items:
• System-fixed data items
• Faceplate data items
• User-defined data items
• Data items for process management (nonresident unit instrument)
2.3.1 System-Specific Data Items Page 1 of 2
2.3.1 System-Specific Data Items

System-fixed data items are a group of preset unit data items, such as data item names, data names
and data types. These system-fixed data items cannot be changed by the user.
System-Fixed Unit Instrument Data Items

▼ System Definition Data Items
The specifications of system-fixed data item names, data names and data types are shown below:
Table 2.3.1-1 System-Fixed Data Items
Data item Data Entry

Data name Default Remark
name type (*1)
MODE Unit mode CHAR*8 x AUT
BSTS Unit status CHAR*8 x END
SUBS Unit substatus CHAR*8
RUNS Unit control status CHAR*8
ALRM Alarm CHAR*8 NR
AFLS Alarm flashing U32
Alarm suppression
AOFS U32
specification
AF Alarm detection specification U32
ERRC Classified error code U32 0
ERRE Detailed error code U32 0x0000
ERRL Error-caused step number U32 0
STEPNO SFC step number I16 0
OPMK Operation mark I16 x 0
UAID User APID I16 x
SUAID Self-user reserved I16 x 0
OMOD Unit mode (lowest priority) CHAR*4
CMOD Unit mode (highest priority) CHAR*4
DILG Dialog acknowledgement U32
PREMODE Previous unit mode U32 AUT
PREBSTS Previous unit status U32 END
STARTIME Execution start date & time U32
ENDTIME Execution end date & time U32
For Process
BATCHID Batch ID CHAR*16
Management
For Process
USER1 User code 1 CHAR*16 x
Management
For Process
USER2 User cord 2 CHAR*16 x
Management
For Process
Management
For Process
Management
2.3.1 System-Specific Data Items Page 2 of 2
For Process
RECIPEGR Recipe group number I16 0
Management
For Process
RECIPE Recipe name CHAR*16
Management
For Process
PARTNO Unit recipe number I16 0
Management
*1: x:Entry allowed at all times.
Blank:Entry not allowed.
2.3.2 Faceplate Data Items Page 1 of 2
2.3.2 Faceplate Data Items

These data items are used for displaying data of unit faceplates. Different sets of data items are
applied to different faceplates.
Data Items for Analog Unit Instrument Faceplate

The specifications of faceplate data items for analog unit instrument faceplates, which are in
accordance with the _UTAS, _UTAS-N, or _UTAS-SN unit model, are shown below:
Table 2.3.2-1 Analog Type Faceplate Data Items

Data name Range Default
name type (*1)
PV Process variable F32 PV engineering-unit data SL
PV engineering- unit
SV Setpoint value F32 x SL
data
Manipulated output MV engineering-unit
MV F32 x MSL
value data
SH Scale high limit F32 PV engineering-unit data 100.0
SL Scale low limit F32 PV engineering-unit data 0.0
MH MV high-limit setpoint F32 x MSL to MSH MSH
ML MV low-limit setpoint F32 x MSL to MSH MSL
SVH Setpoint high limit F32 x SL to SH SH
SVL Setpoint low limit F32 x SL to SH SL
MV engineering-unit
MSH MV-scale high limit F32 100.0
data
MV engineering-unit
MSL MV-scale low limit F32 0.0
data
SWCR[5] Switch display color I16 x 0 to 15 7 (*2)
SWLB[5] Switch label CHAR*8 x None null (*3)
SWST[5] Switch flashing status I16 x 0,1 0 (*2)
SWOP[5] Switch disabled status I16 x -15 to 15 0 (*2)
*1: x: Entry allowed at all times.
Blank: Entry not allowed.
*2: Array [1] to array [5] are the same.
*3: The default settings for SWLB[1] to SWLB[5] are as follows.
SWLB[1]: START, SWLB[2]: PAUSE, SWLB[3]: RESTART, SWLB[4]: SUSPEND, SWLB[5]: END
TIP For the data display on [PV], [SV], [MV], it is required to define them in the monitoring operations
or etc..
Data Items for 5-Pushbutton Switch Faceplate

The specifications of faceplate data items for 5-pushbutton switch faceplates, which are in
accordance with the _UTPB, _UTPB-N, or _UTPB-SN unit instrument model, are shown below:
Table 2.3.2-2 5-Pushbutton Faceplate Data Items
Data item name Data name Data type Entry (*1) Range Default
2.3.2 Faceplate Data Items Page 2 of 2
SWCR[5] Switch display color I16 x 0 to 15 7: White (*2)

SWLB[5] Switch label CHAR*8 x None (*3)
SWST[5] Switch flashing status I16 x 0,1 0: Stop (*2)
SWOP[5] Switch disabled status I16 x -15 to 15 0: None (*2)
*2: Array [1] to array [5] are the same.
*3: The default settings for SWLB[1] to SWLB[5] are as follows.
SWLB[1]: START, SWLB[2]: PAUSE, SWLB[3]: RESTART, SWLB[4]: SUSPEND, SWLB[5]: END
Data Items for 3-Position Switch Faceplate

There are no data items for 3-position switch faceplates, which are in accordance with the _UTSW,
_UTSW-N, or _UTSW-SN unit instrument model.
2.3.3 User-Definable Data Items Page 1 of 4
2.3.3 User-Definable Data Items

User-definable data items refer to a data item group defined by the user for unit instrument data.
Number of Unit Instrument Data Items that can be

Defined by User : PFCS
A maximum of 256 data items can be defined by user for a unit instrument. However, the total
memory sizes for the unit instrument data defined by user must be smaller than 32K byte.
Number of Unit Instrument Data Items that can be

Defined by User
A maximum of 256 data items can be defined by user for a unit instrument. However, the total
memory sizes for the unit instrument data defined by user must be smaller than 8K byte.
Definition of User Definable Data Item

▼ User Definition Data Items
The definitions on a user definable data item of a unit instrument are as follows.
Data Item
Data item name may be defined with up to 8 alphanumeric character including underscore ( _ ) , but
the underscore can not be used as the first character of the data item name.
Data Type
The data type may be specified. Unit instruments support the following data types.
I16 : 16-bit signed integer
I32 : 32-bit signed integer
F32 : 32-bit floating point
F64 : 64-bit floating point
CHR2 to 16 : character string
Array 1, Array 2
When the array is not specified, the default settings will be applied. The default settings only use
one array, array 2 will be specified as 0.
When array is required, the number of array element 1 and the number of array element 2 need to
be specified. The value set for array1 is the number of array element for array1 and the value set for
array2 is the number of array element for array2. If only array1 is required, the array1 may be
specified from 1 to 999 and the array2 may be specified as 0.
The total number of data may be arrayed is 10000 or less. The area for the specified data size varies
with FCS database types.
Comment
The comment may be defined with up to 16 alphanumeric characters or 8 double-byte characters.
Comment can be omitted.

When comment is defined, the comment will be displayed on the tuning view for the data item
instead of the data item name.
Engineering Unit Symbol

The engineering unit may be defined with up to 6 alphanumeric characters or 3 double-byte
characters.
Security Level
The data item may be specified with a security level from 1 to 8.
SEE For more information about data item's security level, refer to:
ALSO “ Security Levels” in 3.4, “Function Block Security” in Engineering Reference Vol.1 (IM
33J10D10-01EN)
Display Format
The number of digits to be displayed on the tuning view may be specified. The actual display varies
with data types.
For I16 and I32 data type, the integer part digits may be specified.
For F32 and F64 data type, the number of digits for integer part and fraction part may be specified.
For example 7.1 means 7 digits for the whole string and 1 digit for the fraction after decimal point.
CHR* means the data is a character string with a number of * characters.
Entry Method
Data entry method may be specified. There are 4 types of data entry methods.
When specifying Menu label, Menu Data, or Menu Number, the labels and data values for displaying
on menu need to be defined in the Menu Data Definition dialog box.
TIP Menu Data Definition dialog box can be opened from [Tools] menu on Function Block Detail
Builder.
• Direct Input
A datum may directly be entered on the tuning view to the data item.
• Menu Label
The label for the menu display may be entered as a datum. A menu label must be a datum with
CHR2 to CHR16 data type.
Figure 2.3.3-1 Using Menu Label for Data Entry
• Menu Data
A datum displayed to the corresponding data item on the menu may be entered.
Figure 2.3.3-2 Using Menu Data for Data Entry
• Menu Number
The relative number (1 to 64) displayed for the menu label on the menu dialog box may be
entered as a datum. A menu number must be a datum with I16 or I32 data type.
Figure 2.3.3-3 Using Menu Number for Data Entry
For menu labels, menu data, and menu numbers, memory areas are used in units of "sets."
Table 2.3.3-1 Maximum Number That You Define and the Number of Sets Used
Maximum number that you define for Menu Label, Menu Data, or Menu Number of sets
Number used
1 to 16 1
17 to 32 2
33 to 48 3
49 to 64 4
Menu labels, menu data, and menu numbers can be defined to use up to 16 sets in total.
SEE For more information about the number of menu definitions for user-defined data items of FFCS-
ALSO R, refer to:
(IM 33J01B10-01EN)
Display Position
The display position of the data item on the tuning view may be specified. It may be selected from
AUTO, NONE, Column1 and Column2.
When choosing AUTO, the data item will be automatically placed to an idle position start from the
column 1.
When Column1 or Column2 is selected, the Line (horizontal position) needs to be specified.
Line
When Column1 or Column2 is selected as display position, the line position (from 3 to 150) may be
specified.
Check
The method to check the entered data may be specified. There are methods provided by the system
and the methods that may be specified by users. When using the user specified methods, the high
and low limits need to be defined.
Moreover, specification of user-defined check is only allowed for data of the I16 and I32 data types.
User-defined check can be specified for up to 16 user-defined data items.
SEE For more information about the number of check patterns for user-defined data items of FFCS-R,
ALSO refer to:
(IM 33J01B10-01EN)
High Limit, Low Limit

The range (High limit, Low Limit) for entered data may be specified.
In the [Check] column, only when “User definition” or “User definition with Acknowledgment” is
specified, this range is valid.
2.3.4 Data Items for Process Management Page 1 of 2
2.3.4 Data Items for Process Management

Data items for Process Management refer to a data item group in which data for Process
Management can be set when a unit instrument operates under the control of Process Management.
SEE For more information about recipe management and process management, refer to:
ALSO 2., “Recipe Management” in Batch Management System Reference (IM 33J05L10-01EN)
3., “Process Management” in Batch Management System Reference (IM 33J05L10-01EN)
System Fixed Data Items for Process Management

Listed in the table below are the unit instrument data items may be used by Process Management.
When the nonresident unit instrument operates under the control of Process Management, the
Process Management data can be set in the unit instrument data items shown in the table below at
the time the unit instrument starts (when the recipe unit procedure starts). After the unit instrument
is started, USER 1 through USER 4 are overwritten as formula data for the recipe, but even if these
values are changed, they are not reflected in the unit instrument data.
The data set in the unit instrument when the unit instrument started will be cleared after the unit
instrument is ended (status of the unit instrument becomes END).
Table 2.3.4-1 Data Items for Process Management
Data item name Data name Data type Entry(*1) Default

BATCHID Batch ID CHR*16 - null
USER1 User code 1 CHR*16 - null
RECIPEGR Recipe group number I16 - 0
RECIPE Recipe name CHR*16 - null
PARTNO Unit recipe number I16 - 0
*1: -: Entry not possible
User Definable Data Items may be Applied to Process

Management
Among the user definable data items, the following items are provided with unique functions.
RESERVED Batch ID (RP_QUEUE[ ])

For the RESERVED Batch ID, the reserved recipe’s batch ID and the first queued unit name are
stored. The RESERVED Batch ID may be used when using SEBOL to download a recipe or start a
recipe.
When using Batch ID, it is required to define the array data item for the unit instrument, and to
specify the destination tag name to be set to the RESERVED Batch ID, on the Process Management
Configuration Builder for each recipe group, or to define the destination tag name to be set to the
RESERVED Batch ID.
2.3.4 Data Items for Process Management Page 2 of 2
After loading the recipe, the status of the recipe will change from RESERVED to READY.
The Batch ID and the Unit name will be removed from the QUEUE. The RESERVED Batch IDs are
stored in the order of the time they were reserved. When the number of RESERVED Batch ID
queued is more than array elements after recipe setup, the new batch ID and unit name can not be
stored as RESERVED Batch ID. However, after deleting a batch ID from the array and load the
recipe, a new batch ID can be added to the end of the array.
The RESERVED batch ID may be defined on the unit instrument user definable data items as follows.
Data Item Name : RP_QUEUE (may be modified)
Data Type : CHR16
Array1 : 10
Array2 : 2
Display Format : 16
To be Executed Batch ID (BIDQUEUE[ ])

For the To be Executed Batch ID (BIDQUEUE), the unit recipe whose status changed to READY is
stored.
When using the To be Executed Batch ID, it is required to define the array data item for the unit
instrument.
When the number of batch ID reguired is greater than number of array element, the old batch ID
will be deserted in FIFO manner. Furthermore, when a unit starts running, the active Batch ID will
be deleted from the queue of BIDQUEUE.
The To be Executed Batch ID may be defined on the unit instrument user definable data items as
follows.
Data Item Name : BIDQUEUE
Data Type : CHR16
Array1 : 10
Array2 : 0
Display Format : 16
2.3.5 Accessing Unit Data Page 1 of 3
2.3.5 Accessing Unit Data

Unit instrument data items can be accessed from other function blocks or faceplate blocks for
referencing or setting.
Accessing Unit Instrument Data Items from Other

Function Blocks
The operations started from unit instrument can access all data items of the unit instrument’s data
items.
When accessing unit instrument data items from the function blocks which are not controlled by the
unit subject to the following restrictions:
Accessing from Function Blocks Other Than SFC Blocks

Among all unit instrument data items, only the system-fixed data items can be connected to the
function blocks with data connection or sequence connection.
Accessing from Sequence Table Blocks

sequence table blocks with sequence connection by entering the item into the condition or operation
column of the sequence table.
Accessing from Logic Chart Blocks

logic chart blocks with sequence connection by entering item as a condition or an operation symbol
in the logic chart.
Accessing from General-Purpose Calculation Blocks (CALCU,

CALCU-C)
Among all unit instrument data items, only the system-fixed data items can be used in CALCU,
CALCU-C calculation blocks in the format of [<TagName>.<DataItem>] as a variable in the
calculation.
Accessing from SFC Blocks

All unit instrument data items are accessible from SEBOL programs in SFC blocks.
Accessing Unit Instrument Data Items from Faceplates

There are one analog type faceplates and two switch types faceplates may be applied for unit
instruments. These faceplates may be applied to 6 kinds of unit instruments. Using the push buttons
or switches on the faceplate may send status manipulation commands to the unit instruments. When
sending a status change command to a nonresident unit instrument, if the unit procedure does not
exist, an error will occur.
The example of the faceplate displays for unit instruments are shown as follows.
Figure 2.3.5-1 Unit Instrument Faceplates
SEE For more information about status change commands, refer to:
ALSO 2.5.4, "Unit Mode and Unit Status Change Command"
Analog Unit Instrument Faceplate

This type of faceplate may be applied to the unit instrument with _UTAS, _UTAS-N, or _UTAS-SN
model name. The default status change commands assigned to the pushbuttons of the faceplate are
as follows. The status change commands in the State Transition Matrix can be user-defined to the
pushbuttons.
SWLB[1] (START) : PSTART
SWLB[2] (PAUSE) : PAUSE
SWLB[3] (RESTART) : RESTART
SWLB[4] (SUSPEND) : SUSPEND
SWLB[5] (END) : END
Five-Pushbutton type Unit Instrument Faceplate

This type of faceplate may be applied to the unit instrument with _UTPB, _UTPB-N, or _UTPB-SN
model name. The default status change commands assigned to the pushbuttons of the faceplate are
as follows. The status change commands in the State Transition Matrix can be user-defined to the
pushbuttons.
SWLB[1] (START) : PSTART
SWLB[2] (PAUSE) : PAUSE
SWLB[3] (RESTART) : RESTART
SWLB[4] (SUSPEND) : SUSPEND

SWLB[5] (END) : END
Three-Position Switch Type Unit Instrument Faceplate

This type of faceplate may be applied to the unit instrument with _UTSW, _UTSW-N, or _UTSW-SN
model name. The default status change commands assigned to the switch label positions of the
faceplate are as follows. The status change commands in the State Transition Matrix can be user-
defined to the pushbuttons.
Label position 1 (START) : PSTART
Label position 2 (PAUSE) : PAUSE
Label position 3 (RESTART) : RESTART
2.4 Unit Procedure Page 1 of 1
2.4 Unit Procedure

The unit procedure controls the modules grouped in a unit for the production process assigned to
the unit.
Positioning of Unit Procedure

▼ Unit Procedure
A unit procedure consists of more than one operations executed according to the unit procedure
defined for a unit. Execution time is automatically shared when more than one operations required
to be executed in parallel.
A unit procedure can be described using the sequential function chart (SFC) designed for the
purpose. The positioning of a unit procedure is shown below:
Figure 2.4-1 Positioning of Unit Procedure
2.4.1 Unit Procedure SFC Page 1 of 4
2.4.1 Unit Procedure SFC

A sequential function chart (SFC) for describing unit procedures represent the running orders of
operating procedures and multiple operations in a unit instrument. The name or generic name of an
operation can be registered as a step action of in the unit procedure SFC.
Composition of Unit Procedure

Operation names or operation generic names may be described in the action column of each SFC
step. The operations are executed according to the step sequence.
An example of unit-procedure composition is shown below:
Figure 2.4.1-1 Composition of Unit Procedure SFC
In the above example, the steps are executed successively as described. The heating and agitation
steps are executed simultaneously.
Basic Unit Procedure Elements

The unit procedure SFC uses the following basic elements:
• Step
Describes action.
• Transition
Describes transition condition.
• Connection
Connects a step to transition, and transition to a step.
Table 2.4.1-1 Unit Procedure SFC Basic Elements
Element Name Symbol Remarks

Double height initialization step is also
Initial Step
available.
Step Double height step is also available.

Step
Wait Step Only available with unit procedure SFC
Selective Seq.-
Split
Selective Seq.-Join
Parallel-Start Only available with unit procedure SFC
Parallel-End Only available with unit procedure SFC
Link Loop-Branch
Loop-Join
Jump Down nn: numerals
Jump Up nn: numerals
Jump To nn: numerals
Link
These elements are applicable to all SFC blocks, however the three elements below are only
applicable to the unit procedures.
• Wait Step
• Parallel-Start
• Parallel-End
Unit Procedure SFC Steps

The square in the step is for placing the step number (01 to 99).
The unit-procedure SFC step is scripted with its step number indicated in a square and its action in a
rectangle shown to the right of the step number square. When the step is activated, the operation
identified by its tagname in the action box is started. The operation tag name or the operation
generic name may be put into the action column.
When using the operation generic name, it is necessary to define tag names to the corresponding
operation generic names on the function block detail builder.
Figure 2.4.1-2 SFC Step
Every step is either in the active state, in which the step is being executed, or the inactive state, in
which the step has been completed or is yet to be executed.
TIP A maximum number of steps can be described in one column is 50. With parallel, transition, and
jump sequences, up to 99 steps can be described in one SFC.
Step Action
The step action is the process executed when the step is active. For a unit-procedure SFC step, the
process is the operation defined in the action box. When execution of the action or operation is
completed, the step is inactivated and processing is shifted to the next step according to the
connection of the step.
TIP When a comment is entered when defining the steps properties, the comment may be displayed
in the action column of the SFC view displayed on a HIS.
Initial Step
The initial step is the first step to be executed in a unit procedure. The step number in this case is
shown in a double square, however, the basic function of this step is the same as other steps.
Figure 2.4.1-3 Initial Step
Wait Step
The wait step is a step which is not defined for any action in a unit procedure. It is used when
synchronization with another step is required, for example. When this step is activated, it is
completed without executing any action and then inactivated.
Figure 2.4.1-4 Wait Step
SFC Transition
Transition is shown with a short horizontal line crossing the step-connecting link. Transition defines
the condition of transition using a logical expression. Execution advances to the linked step when the
result of the expression is true. If the transition condition is not established, the check for the
condition will continue at each basic cycle.
The transition condition will be parsed as soon as the previous step operation is completed.
Figure 2.4.1-5 SFC Transition
SFC Links
Link elements, which are vertical or horizontal lines connecting unit-procedure steps and transitions,
indicating the execution order or path of steps. Examples of their use are shown below:
Figure 2.4.1-6 Connection Elements
SFC Execution Order

An SFC-described unit procedure is executed in the following order:
1. As soon as the execution of a unit procedure is started, the initial step is activated.
2. The operation described in the action box is started when the step is activated.
3. The step is deactivated when the execution of the operation is completed.
4. One of the following processes starts when the step has been inactivated:
• When the linked destination is a step
The step will be activated.
• When the linked destination is a transition
The transition condition is evaluated, when the result of the evaluation is true, the linked step
will be activated.
If the transition condition is not established, the check for the conditions will continue at each
basic cycle.
2.4.2 Compound Sequence Page 1 of 2
2.4.2 Compound Sequence

A compound sequence is composed of a number of laterally described sequences. A selective
sequence and a simultaneous sequence are compound sequences.
In the selective sequence, a step is selected for execution according to the defined transition
conditions. In the simultaneous sequence, more than one operation are executed simultaneously.
Selective Sequence
In the case of executing a step by switching among the multiple choices according to transition
condition, the selective sequence may be applied. For one selective sequence, eight choices may be
set in parallel.
An example of selective sequence is shown as follows.
Figure 2.4.2-1 A Selective Sequence
In the above example, the three laterally linked transition conditions are evaluated from the left
when step 05 has been completed and inactivated. If one of the conditions is true, the step linked to
that transition is activated. If there are two or more true conditions, the one on the left has priority
over the others.
If none of the conditions is true, the evaluation will be repeated at every basic scan period until one
of the conditions becomes true.
Parallel Sequence
A Parallel sequence is used when it is required to execute multiple sequences simultaneously. The
parallel sequence is indicated with a double-line. The steps described below and in parallel with the
double-line are activated for simultaneous execution. The sequence returns to the original sequence
upon completion of the execution, which is indicated again with a double-line.
Figure 2.4.2-2 A Parallel Sequence
The transition condition for the parallel sequence will not be evaluated until all the steps in the
sequence are completed.
A slash (/) can be used as a special processing to end parallel sequences. When it is described in the
transition condition, if any one of the parallel operations finishes executing, a STOP change
instruction is sent to the other operation being simultaneously executed and the control moves to
the next step.
TIP Parallel sequence is only available in unit procedure SFC.
Notice on Using Parallel Sequence

The Parallel sequence has the following conditions for its use:
• Up to eight steps can be described in one Parallel sequence.
• Up to 32 steps can be executed simultaneously including nested Parallel sequences.
• Up to three Parallel sequences can be nested in one parallel sequence. System alarm will be
invoked if the sequence is nested to four levels.
An example of nested Parallel sequences is shown below:
Figure 2.4.2-3 Nested Parallel Sequences
2.4.3 Transition Conditions Page 1 of 3
2.4.3 Transition Conditions

The logical expressions which can be described as transition conditions are explained. Moreover, the
maximum number of transitions including the unconditional transitions is 99 per FCS.
Logical Expression
The logical expression can be described in one line composed of the left-hand side data, an
operator, and the right-hand side data.
Figure 2.4.3-1 Transition Conditional Expression
Left-Hand Side Data

One of the following data items can be used on the left-hand side:
• Unit instrument data
• Function block data
• Common block data
The unit instrument data and the function block data running in other control stations can not be
used as the transition condition.
However, the common block data may be used as the transition condition in the recipe unit
procedure applied as a nonresident unit instrument procedure.
SEE For more information about recipe unit procedures, refer to:
ALSO “ Recipe Unit Procedure” in 2.1.2, “Procedure” in Batch Management System Reference (IM
33J05L10-01EN)
Operators
One of the following operators can be used:
Table 2.4.3-1 Logical Expression Operators
Operator Description
== True if left and right side are equal. False if not equal.
<> True if left and right side are not equal. False if equal.
< True if right side is larger than left side. False if not.
<= True if right side is larger than or equal to left side. False if not.
> True if right side is smaller than left side. False if not.
>= True if right side is smaller than or equal to left side. False if not.
Right-Hand Side Data

One of the following data items or constants can be used on the right-hand side:
• Unit instrument data
• Function block data

• Common block data
• Constants
The unit instrument data and the function block data running in other control stations can not be
used as the transition condition.
However, the common block data may be used as the transition condition in the recipe unit
procedure applied as a nonresident unit instrument procedure.
SEE For more information about recipe unit procedures, refer to:
ALSO “ Recipe Unit Procedure” in 2.1.2, “Procedure” in Batch Management System Reference (IM
33J05L10-01EN)
Left- & Right-Hand Side Scripts

Left- & Right-Hand Side Scripts of transition conditions are shown below.
Table 2.4.3-2 Left- & Right-Hand Side Scripts
Data Format Remarks

<unit name>.<data item>
%%.<data item> Present-unit data
Unit instrument data $<generic name>.<data item>
$<generic name array>[constant].<data
item>
<tagname>.<data item>
$<generic name>.<data item> Operations included.
Function block data
$<generic name array>[constant].<data
item>
Available with recipe unit
Common block data #<common block name>.<data item>
procedure
Numeric data nnnn.nn or nnnn
Constant cannot be used at left
Constants Character-string
"cccc" side.
data
Special Processing Specification

A slash (/) is used in the transition condition for a parallel sequence join. No character string can be
scripted following the slash.
When the condition contains a slash, the STOP command is sent to the other operations being
executed in the parallel sequence as soon as one of the parallel operations is completed, and
execution advances to the next step when the operation status changes to STOP. In the normal
parallel sequence join, for which the slash is not used, the transition condition is not evaluated until
all parallel operations are completed.
If the operation status cannot be changed because it is determined not permissible in the pre-
processing for the status change command, the command will be sent at every basic scan period
until the change is permitted.
Examples of Transition Condition
Examples of describing transition conditions are shown below:
Example 1
In this example, the condition is true if unit data STEPNO of the present unit is smaller than or equal
to 10:
%%.STEPNO<=10
Example 2
In this example, the condition is true if unit data MODE of the present unit is equal to character-
string AUT:
%%.MODE=="AUT"
Comparison of Data in Transition Condition

The following should be noted regarding the comparison of data performed in transition conditions:
Comparison of Numeric & Character-String Data

An error message will be generated by transition condition check if comparing a character string to a
numeric value in transition condition.
Comparison of Floating-Point Data

Floating-point data contain very small errors because of calculation accuracy, and they could actually
be different internally even if two units of floating-point data are apparently the same. So their
comparison could be determined false when they are compared using (==) or (<>).
It is recommended to use (>=) or (<=) for comparing floating-point data instead of (==) or (<>).
2.4.4 Interrupt Processing of Unit Procedure Page 1 of 1
2.4.4 Interrupt Processing of Unit Procedure

The interrupt processing of a unit instrument may start upon a mode change or status change or an
event signal. When an interruption event occurs, the normal process procedure is interrupted, and
the interrupt processing will be executed.
An interrupt processing of unit instrument may be created by defining it as an event signal
processing in an operation or a monitoring operation.
Interrupt Processing for Unit Mode/Status Changes

The interrupt processing can not be programmed in the unit procedure scripts but can be put in the
operations started by the unit procedure as for unit instrument mode and status change interrupt
processing.
When the interrupt processing for the mode and status change gives an error return, the mode and
status change command may end with an error.
Table 2.4.4-1 Interrupt Processing for Mode/status Changes
Execution status Operation Monitoring operation

Step activated Interrupt processing executed. Interrupt processing executed.
Evaluation of transition condition Interrupt processing not executed. Interrupt processing executed.
Stopped at start of step Interrupt processing not executed. Interrupt processing executed.
For a unit procedure-started operation, interrupt processing can be executed only when the
operation is being executed. It is thus necessary to describe interrupt processing according to the
action of the operation involved.
For a monitoring operation, interrupt processing can be executed anytime. It is thus necessary to
describe interrupt processing according to the action of the unit instrument.
SEE For more information about state transition matrix, refer to:
ALSO 2.6, "State Transition Matrix"
Interrupt Processing upon a Signal

When sending a signal to a unit instrument, the unit instrument passes the signal to the operation
started from the unit procedure of the unit instrument.
An operation started from unit procedure accepts signals only when it is being executed. However, a
monitoring operation accepts signals at all times.
If more than one operations are being executed, the signal will be sent to all of them. Since the unit
instrument has no signal queue, it cannot keep the received signals for waiting. An operation can
hold the signal sent to it in QUEUE [5] data item.
SEE For more information about the interrupt processing upon a signal, refer to:
ALSO 2.14.1, "Queue Signal Processing"
2.4.5 Unit Procedure Sharing Page 1 of 2
2.4.5 Unit Procedure Sharing

Normally, one unit procedure is assigned to one unit instrument.
When multiple unit instruments corresponding to the same type of equipment entity which have the
same control sequence, unit procedures may be shared.
What is Unit Procedure Sharing

▼ Sharing a Unit Procedure
One unit procedure can be shared by multiple unit instruments.
Unit procedure sharing means to allow multiple unit instruments with the same control algorithm to
share the same unit procedure.
For example, if one unit procedure is shared by 3 unit instruments, only one unit procedure will be
prepared for three unit instruments on the FCS, so that it reduces the unit procedure process
memory use to 1/3 of the original. When modifying one unit procedure, all the unit instruments'
procedures will be changed together.
However, the shared unit procedure can be modified only when the procedure is no used by any of
the unit instruments.
Sharing a Unit Procedure

The shared unit procedure may be created on FCS sequence library builder. The name of the
created unit procedure may be defined on the Function Block Detail Builder.
In the action column of the shared unit procedure, the tag name of the operation or the generic
name of the operation may be specified.
When the generic name of the operation is used, the generic name of the operation used by unit
instrument corresponds the tag name of the actually used operation. For one unit instrument, up to
99 generic names for operations may be specified.
Moreover, the transition condition for unit instrument or the tag generic names in the unit
instrument may be used. When using the tag generic names, the tag generic names in the unit
instrument corresponding to the actually used tag names may be defined.
SEE For more information about FCS sequence library, refer to:
ALSO 5., “FCS Sequence Library” in Engineering Reference Vol.2 (IM 33J10D11-01EN)
Operation Generic Name Definition Items

▼ Operation Generic Name
The definition items for operation generic names are shown as follows. If the unit instrument calls
out the unit operation instrument, the operation generic name used by the procedure within the unit
operation instrument is defined as the operation generic name for the Unit instrument.
Operation Generic Name

The operation generic name may be specified in the action column of the unit procedure in the FCS
sequence library. The generic name of the unit operation instrument is also defined as the operation
generic name. An operation generic name may be defined with up to 8 alphanumeric characters.
2.4.5 Unit Procedure Sharing Page 2 of 2
Tag Name
Corresponding to the operation’s generic name, the actually used tag name for the operation may
be specified.
Example of Sharing a Unit Procedure

The sharing of a unit procedure is explained using the following diagram as an example. In the
example, unit instruments A and B share unit procedure X. In unit procedure X, the generic
operation names “OP001” and “OP002” are described as the startup operation names. Unit
instrument A has a correspondence table between the generic operation names and tag names for
unit instrument A, and unit instrument B has a correspondence table between the generic operation
names and tag names for unit instrument B. When unit procedure X operates as a unit procedure for
unit instrument A, generic operation names “OP001” and “OP002” reference the correspondence
table and are converted to tag names “ABC1” and “XYZ1,” then operations ABC1 and XYZ1 will start
in succession. When unit procedure X operates as a unit procedure for unit instrument B, generic
operation names “OP001” and “OP002” use the correspondence table to convert themselves to tag
numbers “ABC2” and “XYZ2,” then operations ABC2 and XYZ2 will start in succession.
Figure 2.4.5-1 Sharing a Unit Procedure
2.5 Unit Mode and Unit Status Page 1 of 1
2.5 Unit Mode and Unit Status

The block mode of units is called unit mode, and the block status of units is called unit status.
The block mode change or status change command may change the control state or running state of
a unit instrument.
2.5.1 Unit Mode Page 1 of 1
2.5.1 Unit Mode

The unit mode indicates the control mode of the unit instrument. When a command for changing the
unit instrument mode is given, the behaviors of the unit procedure and operation may be changed.
Available Modes
▼ Unit Mode
Available unit modes, which are system-specific, are shown below:
Out-of-Service (O/S) Mode

The execution of the unit, including initialization and monitoring operations, is completely stopped in
this mode for the purpose of maintenance, etc.
Transition to O/S mode is possible only when the unit is in the completed (END) or aborted (ABRT)
status. The other statuses may cause errors. Transition to the O/S mode is completely stopped the
unit for the purpose of the maintenance, etc.
Manual (MAN) Mode

The unit procedure cannot be run in this mode.
Semi-Automatic (SEMI) Mode

The operation of each unit-procedure step is automatically executed in this mode but stopped for
manual transition to the next step.
Automatic (AUT) Mode

The operations of all unit-procedure steps are automatically transited in this mode. It indicating the
unit is in automatic unit execution.
2.5.2 Unit Status Page 1 of 1
2.5.2 Unit Status

The unit status indicates the running state of a unit instrument (running state of a unit procedure).
Default Unit Status

▼ Default Unit Status
There are following types of system-fixed unit status.
User-defined status character strings in column USER2 of block status file are applied as the default
character strings for unit status display.
END
Execution of unit procedure completed.
ABORTED
Unit procedure execution aborted.
RUNNING
Unit procedure being executed.
SUSPEND
Unit procedure execution suspended at the start of a step.
PAUSED
Execution of operation paused at the start of a phase.
User-Defined Unit Status

▼ User-Defined Unit Status, USER 2 to 8 (Unit Instrument)
The character strings for user-defined unit status can be specified in tables of USER2 to USER8 in
the Block Status Character String builder.
The user-defined status character strings (USER2 to USER8) can be used only when they are
designated in State Transition Matrix builder. In this State Transition Matrix builder, the character
strings defined in the table at the position 4 to 17 and 23 can be used.
The character string [ABORTED] at the table position 4 and the character string [END] at the table
position 23 can not be changed. User can define the character strings for the table position 5 to 17.
A character string for the status can be defined using up to 8 alphanumeric characters including
underscore ( _ ) started with an alphabet letter.
When character string table USER2 is modified, the default State Transition
Matrix (Matrix1) will change its action accordingly.
2.5.3 Unit Sub-Status Page 1 of 1
2.5.3 Unit Sub-Status

Unit sub-status is provided to indicate more detailed running state under each unit status.
Type of Sub-Status
Unit sub-status is an auxiliary information to indicate more detailed running state under a unit
status.
The unit substatus and the unit status have the following relationship.
Table 2.5.3-1 Unit Status and Unit Sub-Status
Unit Status Substatus Description

CNCT Waiting for starting of unit procedure execution.
NOCNCT No unit procedure available.
END
INIT Initialization being executed.
INIR Interrupt processing being executed.
USER User-aborted state.
ABORTED
SYSTEM System-aborted state.
RUNNING INTR Interrupt processing being executed.
INTR Interrupt processing being executed.
SUSPEND
CKTR Transition condition being evaluated.
PAUSED INTR Interrupt processing being executed.
2.5.4 Unit Mode and Unit Status Change Command Page 1 of 6
2.5.4 Unit Mode and Unit Status Change Command

The unit instrument can receive operation commands from the operation and monitoring consoles,
sequence table or logic chart, other units and actions such as emergency stop caused by equipment
failure, as a unit mode change command or unit status change command.
Figure 2.5.4-1 Unit Mode/Unit Status Change Commands Sent to Unit
Unit Mode Change Commands

▼ Mode Change Commands
Available unit-mode change commands, which are also system-fixed, are described below:
AUT
Transition to the automatic mode.
SEMI
Transition to the semi-automatic mode.
MAN
Transition to the manual mode.
O/S
Transition to the out-of-service mode.
System-Fixed Unit Status Change Commands

▼ System-Fixed Unit Status Change Commands, Status Change Commands, Directives to Change the
Status
Available unit status change commands are described below:
Table 2.5.4-1 Unit Status Change Commands
Execution
Symbol Command Description
level
Start
PSTART Starts unit procedure. Low
command
Restart
RESTART Restarts suspended/paused unit procedure. Low
command
END End command Terminates unit-procedure execution. Low
Abort Forcibly terminates unit execution.

ABORT High
command (Unit Status interrupt processing cannot be described).
Suspend
SUSPEND Suspends execution of unit-procedure step. Low
command
Pause
PAUSE Pauses execution of unit-procedure operation phase. Low
command
Reset
RESET Resets aborted status. Low
command
Monitoring-
MSTART start Restarts monitoring operation. High
command
SCOMP Step end Stops execution at the start of next step in SEMI mode.
Low
(*1) command (Unit Status interrupt processing cannot be described).
Step change Changes steps when the unit is stopped.
STEP (*1) Low
command (Unit Status interrupt processing cannot be described).
Stops execution at the start of step when error is caused during
Execution
EXECERR operation. Specifying a pause during the state transition by this
error High
(*1) change command can pause execution at the start of the step
command
when an error is caused during operation.
*1: SCOMP, STEP, and EXECERR commands are system-initiated (see below), user cannot issue the
commands.
The MSTART command and system-initiated SCOMP, STEP, and EXECERR commands are described
below:
MSTART Change Command

This command restarts the monitoring operation when it has been stopped for some reason. The
monitoring operation is normally kept being executed regardless of unit status. When the monitoring
operation stops, MSTART command may be issued to restart it.
SCOMP Change Command

This is a status change command issued by the system. The users are not allowed to issue this
command.
The SCOMP change command is a change command that creates a pause between steps when the
mode is semi-automatic (SEMI).
When the block mode is in semi-automatic (SEMI), the system issues an SCOMP change command
each time an SFC step of the unit procedure and the transition in connection with that step have
been executed. When an SCOMP change command is issued, the unit instrument pauses execution
at the start of the next step according to the status transition matrix.
STEP Change Command

When performing batch stepping of unit procedure SFC, a step change is executed by setting the
step number of the stepping target in the STEPNO data item and instructing a STEP change. When a
STEP change command is received, the unit executes the process stepping according to the status
transition matrix.
EXECERR Change Command

command.
When the unit procedure starts an operation, there are times when the operation is in the middle of
maintenance or being started by another unit procedure. In this case, the EXECERR change
command is issued. When the EXECERR change command is received, the unit enters the pause
state according to the status transition matrix.
User-Defined Status Change Commands

▼ User-Defined Status Change Commands, CUSER1 to CUSER8
The character strings for user-defined status change commands can be specified in tables of
CUSER1 to CUSER8 in Status Change Command Character String builder.
The user-defined status change command character strings (CUSER1 to CUSER8) can be used only
when they are designated in State Transition Matrix builder.
A character string for a status change command can be defined using up to 8 alphanumeric
characters including underscore ( _ ) started with an alphabet letter. The identical character strings
can not defined in the same table. The reserved strings [RUN], [STOP] and [PAUS] can not be
defined.
The following default character strings for status changes commands can not be changed by user.
String Number 1: PSTART
String Number 2: STEP
String Number 3: SCOMP
String Number 4: EXECERR
String Number 21: MSTART
String Number 22: ABORT
When character string table CUSER1 is modified, the default State Transition
Matrix (Matrix1) will change its action accordingly.
Start Action
▼ Start Action
The action for FCS initialization start or unit stop (Unit mode changes to END) may be defined. The
start action of a unit include 3 types, they are “Manual Start,” “Auto Start” or “Auto Start when FCS
initialization start.”
• Auto Start
When Auto Start is defined, the unit is automatically start the PSTART command when the unit
status changes to END.
• Manual Start
When Manual Start is defined, the unit does not send PSTART command when the unit status
changes to END. The PSTART command has to be manually send to start the unit.
• Auto Start when FCS initialization start
When Auto Start when FCS initialization start is defined, the PSTART command is sent when the
FCS initialization start.
Unit Procedure Step Jump

When a unit procedure’s unit is in SUSPEND status, it is possible to jump its sequence to a
designated step. Step jump means a unit procedure to transit to a desired step for execution, either
forward or backward is allowed. There two ways to set the unit into SUSPEND status, by setting the
unit into Semi-automatic (SEMI) mode or by sending a command for changing to SUSPEND status
methods.
To perform step jump, first to set the unit into SUSPEND status, then perform a step jump on the
SFC view, then send a RESTART command to the unit. After the above operations, the unit starts its
execution from the jumped step.
In a unit procedure, multiple steps may be executed in parallel. It is possible to jump to a step
which is one of the parallel steps but only the jumped step is activated. If there two steps running in
parallel, after the step jump, only one step starts running, the other step is not. In the case like this,
it is required to jump to another step again.
Receiving Status Change Command

When unit instrument receives a mode/status change command, the feasibility of changing to the
mode or status is checked by the unit instrument according to the status transition matrix. It will
give an error return when the check result is negative.
If the change is permitted, all the running operations under the management of the unit will execute
the mode change or status change commands following the unit mode and status change.
For operations, the interrupt processing programs should be prepared in advance, so that when an
operation is interrupted by a mode change or status change command, the prepared processing can
be executed accordingly.
Figure 2.5.4-2 Receiving Processing of Mode/Status Change Command
SEE For more information about the state transition matrix, refer to:
Errors Caused by Change Commands

The errors caused when a unit mode/status change command is denied are described below.
Transition Error
Error is caused if the change command is not defined in the status transition matrix.
Previous Change Command being Processed

Error may be caused if a new change command is received while a previously received change
command is still being processed.
The change commands classified as high execution-level commands have priority over the low
execution-level commands. Error is caused if the previously received command has not been
completed when its level is the same as the newly received command. When a high-level change
command is received during processing of a low-level command, the newly received command is
accepted for processing.
Table 2.5.4-2 Processing According to Command Levels
State Low-level command received High-level command received

Previous command completed Accepted. Accepted.
Low-level command being processed Error caused. Accepted.
High-level command being processed Error caused. Error caused.
Completion of Change Command Processing

The completion of the mode or status change command means the running operation has completed
its mode and status change processing including the processing prior mode and status change and
the processing after the mode and status change.
Completion of Pre-Processing
The pre-processing for a mode/status change command is a user-written interrupt program. The
feasibility of the change can be determined by this interrupt program. When no interrupt program is
described for pre-processing, it will be assumed that pre-processing has been normally executed
justifying the change.
Completion of Post-Processing
The post-processing for a mode/status change command is also a user-created interrupt program. It
is executed after the change is made and any new mode/status change command is denied until the
post-processing is completed. Error is caused if a new mode/status change command is issued prior
to the completion.
SEE For more information about the Status Change Pre-Process, or the Status Change Post-Process,
ALSO refer to:
2.14.2, "Status Change Processing"
2.6 State Transition Matrix Page 1 of 1
2.6 State Transition Matrix

The status transition matrix determines transition action for unit mode/status change commands and
the actions. The unit instrument changes its mode and status in accordance with the state transition
matrix. A default standard transition matrix and a user-defined transition matrix are available.
State Transition
The control status of a unit instrument is indicated by the unit mode. The running state of the unit
instrument is indicated by the unit status. The unit state transition means the unit instrument
transfers its mode or status to another mode or status.
The transition of the unit mode or unit status is initiated by the unit mode or unit status change
command. When the transition command is given, the unit instrument refers to the state transition
matrix to check if it is allowed to transit from the current mode or status to the required mode or
status.
Designation of State Transition Matrix

▼ State Transition Matrix
The table number of state transition matrix for the unit instrument should be designated. The tables
of Matrix1 to Matrix16 are available. Matrix1 is designated as the default setting. The standard state
transition should use Matrix1.
2.6.1 Standard State Transition Matrix Page 1 of 9
2.6.1 Standard State Transition Matrix

How the standard state transition matrix, set as default, behaves will be explained in this section.
Standard State Transition

How a unit instrument transit its state when it receives a mode change or a status change command
is decided in the State Transition Matrix. The state to be transited will be decided according to the
current unit status, unit mode and the command received.
When a unit instrument receives a transition command, it will follow the transition rules in the State
Transition Matrix to change to a new mode and new status. At the same time, the unit instrument
transmits the actions to running operations so as to control the running state and controlling state of
the operations and the unit instrument itself.
When using the standard state transition matrix, the contents defined in
USER2 on State Transition Matrix builder and the contents in CUSER1 on
Status Change Command Character String builder can not be modified.
Transition Feasibility when Unit Instrument in AUT Mode
Figure 2.6.1-1 Transition Feasibility when Unit Instrument in AUT Mode
Transition Feasibility when Unit Instrument in SEMI Mode
Figure 2.6.1-2 Transition Feasibility when Unit Instrument in SEMI Mode
Transition Matrix for Mode Change Commands

The status transition matrix for mode change commands is shown below:
Table 2.6.1-1 Transition Matrix for Mode Change Commands
Mode Change command

Current status Current mode
AUT SEMI MAN
AUT ABORTED, A, CONTN ABORTED, S, CONT ABORTED, M, CONT
ABORTED SEMI ABORTED, A, CONT ABORTED, S,CONTN ABORTED, M, CONT
MAN ABORTED, A, CONT ABORTED, S,CONT ABORTED, M, CONTN
AUT RUNNIN, A, CONTN RUNNING, S, CONT
RUNNING SEMI RUNNIN, A, CONT RUNNING, S, CONTN
MAN
AUT SUSPEND, A,CONTN SUSPEND, S,CONT
SUSPEND SEMI SUSPEND, A,CONT SUSPEND, S,CONTN
MAN
AUT PAUSED, A, CONTN PAUSED, S, CONT
PAUSED SEMI PAUSED, A, CONT PAUSED, S, CONTN
MAN
AUT END, A, CONTN END, S, CONT END, M, CONT
END SEMI END, A, CONT END, S, CONTN END, M, CONT
MAN END, A, CONT END, S, CONT END, M, CONTN
Data in the “mode change command” columns in the above table are from the left: “unit status
changed to,” “unit mode changed to,” and “action instruction for unit or operation” .
“Unit mode changed to” are shown below:
• A : AUT mode
• S : SEMI mode
• M : MAN mode
Blank cells indicate that transition is not allowed.
Note Points Regarding Mode Change Commands

The following points need to be noted in regarding unit instrument mode change commands.
• The mode can be changed to MAN from any mode in the END or ABORTED status. No unit
procedure can be executed in the MAN mode and error is caused at any attempt to change
status.
• The mode can be changed to O/S from any mode in the END or ABORTED status. No
mode/status change commands are allowed in the O/S mode and error is caused at any attempt
while the END or ABORTED status is retained.
Transition Matrix for Unit Status Change Commands

The status transition matrix for unit status change commands is shown below:
Table 2.6.1-2 Transition Matrix for Unit Status Change Commands (1/3)
Status Change command

PSTART STEP SCOMP
AUT
ABORTED SEMI
MAN
AUT
RUNNING SEMI SUSPEND, S, SUSP+
MAN
AUT SUSPEND, A, STEP
SUSPEND SEMI SUSPEND, S, STEP
MAN
AUT
PAUSE SEMI
MAN
AUT RUNNING, A, STRA
END SEMI RUNNING, A, STRA
MAN
Data in the “Status Change command” columns in the above table are from the left: “unit status
• A : AUT mode
• S : SEMI mode
• M : MAN mode

EXECERR RESTART END
AUT
ABORTED SEMI
MAN
AUT SUSPEND, A, SUSPA END, A, END
RUNNING SEMI SUSPEND, S, SUSPA END, S, END
MAN
AUT SUSPEND, A, SUSPA RUNNING, A, RSMA END, A, END
SUSPEND SEMI SUSPEND, S, SUSPA RUNNING, S, RSMA END, S, END
MAN
AUT SUSPEND, A, SUSPA RUNNING, A, RSMA END, A, END
PAUSED SEMI SUSPEND, S, SUSPA RUNNING, S, RSMA END, S, END
MAN
AUT
END SEMI
MAN
• A : AUT mode
• S : SEMI mode
• M : MAN mode

SUSPEND PAUSE RESET
AUT END, A, END
ABORTED SEMI END, S, END
MAN END, M, END
AUT SUSPEND, A, SUSPA PAUSED, A, PAUSA
RUNNING SEMI SUSPEND, S, SUSPA PAUSED, S, PAUSA
MAN
AUT
SUSPEND SEMI
MAN
AUT SUSPEND, A, SUSPA
PAUSED SEMI SUSPEND, S, SUSPA
MAN
AUT
END SEMI
MAN

• A : AUT mode
• S : SEMI mode
• M : MAN mode
Action Instructions for Unit Instrument or Operation

The action instructions for the unit instrument or operation following the unit mode or status change
commands are described as follows:
Table 2.6.1-5 Action Instruction for Unit/Operation (1/2)
Symbol Action Operation

STRA Start Initial-step operation started (operation mode: AUT).
STRS Start Initial-step operation started (operation mode: SEMI).
STR Start Initial-step operation started.
Current-step operation started (operation mode: AUT).
RSMA Restart
RUN command sent to the operation.
Current-step operation started (operation mode: SEMI).
RSMS Restart
Current-step operation started.
RSM Restart
Processing started from current-step transition condition (operation mode: AUT).
RSMA+ Restart STOP command sent to current-step operation and processing started from current-step
transition condition.
RSMS+ Restart Processing started from current-step transition condition (operation mode: AUT).
RSM+ Restart Processing started from current-step transition condition.
Current-step operation restarted from start (operation mode: AUT).
RSMA- Restart STOP command sent to current-step operation and START command sent again after
completion of the operation.
RSMS- Restart Current-step operation restarted from start (operation mode: SEMI).
RSM- Restart Current-step operation restarted from start.
END End STOP command sent to all current operations.
ABRT Abort ABRT command sent to all current operations.
STOP command sent to all current operations (operation mode: AUT).
SUSPA Suspend
Stop position shifted to start of current step after completion of operation.
STOP command sent to all current operations (operation mode: SEMI).
SUSPS Suspend
STOP command sent to all current operations.
SUSP Suspend
STOP command sent to all current operations (operation mode: AUT).
SUSPA+ Suspend Step transition condition evaluated for current operation upon its completion and then
execution stopped at start of the next step when the condition is satisfied.
STOP command sent to all current operations (operation mode: SEMI).
SUSPS+ Suspend Step transition condition evaluated for current operation upon its completion and then
execution stopped.
STOP command sent to all current operations.
SUSP+ Suspend Step transition condition evaluated for current operation upon its completion and then
execution stopped.
Table 2.6.1-6 Action Instruction for Unit/Operation (2/2)
Symbol Action Operation

PAUS command sent to all current operations.
PAUSA Phase pause Execution stopped at start of the current phase of operation (operation mode:
AUT).
PAUSS Phase pause Execution stopped at start of the current phase of operation (operation mode:
SEMI).
PAUS Phase pause
Execution stopped at start of the current phase of operation.
CONTA Continue Current conditions and action continued (operation mode: AUT).
CONTS Continue Current conditions and action continued (operation mode: SEMI).
CONT Continue Current conditions and action continued.
CONTN Continue Current conditions and action continued (no interrupt processing).
Phase
STEP Step advanced to STEPNO-specified step.
advance
If an action instruction suffixed with a (+) plus, such as SUSP+ and RSM+, is
given and the current-step transition condition is not satisfied, the condition
will be maintained until the condition is satisfied. Be sure to define a transition
condition which never fails when describing it for a selective sequence.
Actions Invoked by Action Instructions

The actions of the unit or operation after having been instructed following mode/status change
commands are described below:
Table 2.6.1-7 Actions Invoked by Action Instructions
Change-command interrupt Operation Operation

Instruction Unit action
processing status mode
STRA AUT
Only monitoring operation permitted as
STRS Execution started. RUN SEMI
RUN-command interrupt processing.
STR (None)
RSMA+
RSMA- AUT
RSMA
RSMA+
Suspended Only monitoring operation permitted as
RSMA- RUN SEMI
execution restarted. RUN-command interrupt processing.
RSMS
RSM+
RSM- (None)
RSM
RSMA AUT
RUN-command interrupt processing
RSMS RUN SEMI
executed.
Phase-paused
RSM (None)
execution restarted.
RSMA+
AUT
RSMA-
RSMS+
SEMI
RSMS- STOP-command interrupt processing
RUN
RSM+ executed.
(None)
RSM-
STOP-command interrupt processing
END Execution ended. STOP (None)
executed.
ABRT Execution aborted. No interrupt processing allowed. ABRT (None)
SUSPA[+] AUT
Execution STOP-command interrupt processing
SUSPS{+} STOP SEMI
suspended. executed.
SUSP{+} (None)
PAUSA AUT
Phase execution PAUS-command interrupt processing
PAUSS PAUS SEMI
paused. executed.
PAUS (None)
CONTA AUT
RUN-command interrupt processing
CONTS RUN SEMI
Execution continued. allowed during execution.
CONT (None)
CONTN No interrupt processing allowed. (Continued) (None)
STEP Step feed. No interrupt processing allowed. (Continued) (None)
Details of Action Instruction for Unit Instruments

The details of action instruction for unit instruments are described below.
STRA, STRS, STR (starting)

These action instructions start the operation of the unit-procedure initial step. They are effective
only when the unit is stopped or its execution has been aborted. They do not execute any interrupt
processing when the operation is started except for the monitoring operation, for which RUN-
command interrupt processing can be described.
RSMA, RSMS, RSM (restarting)

When a unit is in PAUSE status (including the phase’s PAUSE status), these instructions may be
applied.
RSMA, RSMS, RSM instructions may restart the operation where the unit procedure paused at the
beginning of the step. However, the interrupt processing do not function when the restarting is
running.
There is one exception, i.e. the RUN instruction may used for interruption in a monitoring operation.
When restarting a paused phase, RSMA, RSMS and RSM instructions send the RUN command to the
current operation. If the operation has any RUN-command interrupt processing, it will be first
executed. If error is caused during status-change pre-processing, the status will not be changed.
After the restarting, the SFC step of current operation is executed.
RSMA+, RSMS+, RSM+ (restarting)

When a unit instrument is in PAUSE status (including the phase’s PAUSE status), these instructions
may be applied.
RSMA+, RSMS+, RSM+ instructions may restart the condition check for transition at that step.
However, the interrupt processing can not be used in the operation.
There is one exception, i.e. the STOP instruction may used for interruption in a monitoring operation.
When restarting a paused phase, RSMA+, RSMS+ and RSM+ instructions send the STOP command
to the current operation. If the operation has any STOP-command interrupt processing, it will be
first executed. If error is caused during status-change pre-processing, the status will not be
changed. After the execution of operation is completed, the transition-condition evaluation for the
current step is restarted.
RSMA-, RSMS-, RSM- (restarting)

When a unit instrument is in PAUSE status (including the phase’s PAUSE status), these instructions
may be applied.
RSMA-, RSMS-, RSM- instructions may restart the operation where the unit procedure paused at the
beginning of the step. However, the interrupt processing of an operation do not function when the
restarting is running.
There is one exception, i.e. the STOP instruction may used for interruption in a monitoring operation.
When restarting a paused phase, RSMA-, RSMS- and RSM- instructions send the STOP command to
the current operation. If the operation has any STOP-command interrupt processing, it will be first
executed. If error is caused during status-change pre-processing, the status will not be changed.
The operation will be restarted upon completion of its execution.
END (ending)
It is effective only when the unit is being executed or suspended, including a paused phase.
This action instruction ends the execution of the unit procedure.
If the current operation has any STOP-command interrupt processing, it will be first executed. If
error is caused during status-change pre-processing, the status will not be changed. When any
interrupt processing is executed, the unit execution ends when status-change post-processing for all
current operations is completed.
ABRT (aborting)
It is effective only when the unit is being executed or suspended, including a paused phase.
This action instruction sends the ABRT command to all current operations and forcibly terminates
the execution of the unit procedure SFC.
No interrupt processing can be executed, including the monitoring operation.
SUSPA, SUSPS, SUSP (suspending)

It is effective only when the unit is being executed or a phase is paused.
These action instructions send the STOP command to all current operations and then stop the
execution of the unit procedure at the start of the current step.
error is caused during status-change pre-processing, the status will not be changed. The current
step will be retained after execution has been suspended.
SUSPA+, SUSPS+, SUSP+ (suspending)
They are effective only when the unit is being executed or a phase is paused.
These action instructions send the STOP command to all current operations, start transition-
condition evaluation for the step upon completion of the operation, and then stop the execution of
the unit procedure at the start of the next step when the transition condition is satisfied.
error is caused during status-change pre-processing, the status will not be changed. The next step
will be executed when execution is restarted, but the suspension will be maintained if the transition
condition for the current step is not satisfied.
PAUSA, PAUSS, PAUS (phase pause)

They are effective only when the unit is being executed or is suspended.
These action instructions send the PAUS command to all current operations and stop the execution
of the unit procedure at the start of the current operation phase, or at the start of the current
operation if in a suspended status.
If the current operation has any PAUS-command interrupt processing, it will be first executed. If
error is caused during status-change pre-processing, the status will not be changed.
CONTA, CONTS, CONT (continuation)

They are effective in any unit status.
These action instructions continue execution retaining the current conditions.
If the current operation has any RUN-command interrupt processing, it will be first executed. If error
is caused during status-change pre-processing, the status will not be changed. When a phase is
paused and the operation has any RUN-command interrupt processing, its pre-processing will be
executed.
CONTN (continuation)
It is effective in any unit status.
This action instruction also continues execution retaining the current conditions. Interrupt processing
is not executed, however, for the current operation.
STEP (step change)

It is effective when the unit is suspended.
This action instruction jumps execution to a step specified by unit data item STEPNO. Any step
number can be entered to STEPNO as long as it exists. No interrupt processing can be executed,
including the monitoring operation.
2.6.2 User Defined State Transition Matrix Page 1 of 3
2.6.2 User Defined State Transition Matrix

When creating a user-defined state transition matrix, the corresponding unit status character strings
and the unit status change command character strings need to be defined first.
Setting the State Transition Matrix Table

From the data tree of System View, select [COMMON] > [MATRIX] folder. Then, from the File menu
of System View, select [Create New] > [State Transition Matrix]. A Create New dialog box appears.
On this dialog box, State Transition Matrix, Status Label, Status Change Command, and Comment
can be set. The following figure shows the Create New dialog box for a state transition matrix.
Figure 2.6.2-1 State Transition Matrix Create New Dialog Box

▼ State Transition Matrix Name
A matrix (Matrix1 to Matrix16) can be designated as the State Transition Matrix. Then the status
character strings and status change command strings corresponding to the designated matrix should
be set.
The name of the defined State Transition Matrix can be designated on the Unit Instrument Function
Block Detail Builder as State Transition Matrix.
Status Label
▼ Status Character String Table Name
The table of character strings (USER2 to USER8) corresponding to the designated State Transition
Matrix should be specified. The labels in the specified character string table can be used as the state
transition destination.
Status Change Command

▼ Status Change Command Character
The table of character strings (CUSER1 to CUSER8) corresponding to the designated State Transition
Matrix should be specified. The strings in the specified character string table can be used as the
status change commands.
Comment
▼ Comment
Up to 24 alphanumeric characters or 12 double-byte characters can be used for comment.
TIP After setting the State Transition Matrix, when the designated table for status label and status
change command character strings are changed, the settings for the matrix will not be changed.
The State Transition Matrix settings can be changed if required.
Configuring State Transition Matrix

The state transition matrix can be configured on the State Transition Matrix builder. The state
transition consists of unit mode transition and unit status transition.
Figure 2.6.2-2 State Transition Matrix Builder
In the State Transition Matrix builder, the following three items need to be configured:
• Unit status for transition
• Unit mode for transition
• Action after transition
The blank in the matrix means the transition can not be set.
Unit Status for Transition

Under the current unit mode and unit status, when receiving a change command, the unit may
transit to a designated status. This designated status can be defined here.
The status character strings to be displayed will be the strings in the table whose number is
configured for the matrix.
Unit Mode for Transition

transit to a designated mode. This designated mode can be defined here. O/S can not be configured
as a mode for transition and blank means no transition.
The mode for transition can be selected from the following:
• Blank
• AUT
• SEMI
• MAN
When defining AUT, SEMI and MAN as the mode for transition, use A, S, M, the signs representing
the modes.
Action After Transition

perform a designated action. This designated action can be defined here.
SEE For more information about action after transition, refer to:
ALSO " Action Instructions for Unit Instrument or Operation" in 2.6.1, "Standard State Transition
Matrix"
2.7 Unit Supervision Messages Page 1 of 1
2.7 Unit Supervision Messages

The following messages are used with the unit supervision. They will be stored in the historical
message file of the HIS:
• Unit process alarm messages
• Unit mode and unit status change messages
• Sequence control messages
• System alarm messages
2.7.1 Unit Process Alarm Messages Page 1 of 3
2.7.1 Unit Process Alarm Messages

Unit instrument is provided with the process alarm message handling function same as other
function blocks. This chapter explains the process alarm handling function of the unit instrument.
Unit Process Alarms

The process alarm of unit control is referred to as unit process alarm. These alarms can be described
in the operation written in SEBOL programs. Their generation and recovery can be optionally
defined. Their priority, detection, suppression, and repetition requirements can also be specified.
Process alarms caused in a unit can be shown in process-alarm and other views.
Unit Alarm Status

▼ Alarm Status
The alarm status of a unit is called the unit alarm status.
A priority is assigned to each unit alarm status. When more than one unit alarm status occur at the
same time, the unit alarm status with the higher priority will take place in the ALRM, a unit data
item.
Alarm status character strings defined in the User-defined Status Character String Builder (USER11
to USER16) can be used for indicating unit instrument’s alarm status.
SEE For more information about user-defined alarm status character string, refer to:
ALSO “ User-Defined Alarm Status Character String” in 7.4, “Alarm Status Character String and
Alarm Processing” in Human Interface Stations Reference Vol.2 (IM 33J05A11-01EN)
Alarm Generation and Recovery

“unit prcsalarm” and “unit prcsalarm recover” SEBOL statements used in the operations in unit
instrument can define unit process-alarm generation and recovery.
An alarm may occur or recover either in a unit interment or in an operation. These alarms can be
applied to either a unit or an operation by specifying it in the SEBOL program. The flows of process-
alarm generation and recovery are shown below:
Figure 2.7.1-1 Flows of Unit Process-alarm Generation & Recovery
Unit Process Alarm Initialization

Unit process alarms are initialized when the unit starts to run. If a unit process alarm already exists,
that alarm will also be forcibly initialized and the recovery message will be output.
Unit Process Alarm Repetition

If a unit is kept running for a predetermined period of time without resetting the existing unit-
process alarms, the alarms can be repeatedly output as long as the unit is in the RUNNING,
PAUSED, or SUSPEND status. Alarm repetition can be specified using the function block detail builder.
Unit Process Alarm Detection & Suppression

The detection and suppression of unit process alarms can be specified at unit data items AF and
AOFS respectively. Unit process alarms are output by the specification of these two data items.
Unit Process Alarm Flashing

The flashing of unit process alarms can be specified for the operation and monitoring function using
unit data item AFLS. The flashing action is same as other function blocks.
Unit Process Alarm Messages

The messages to notify the occurrence of a unit process alarm and the recovery of the alarm status
can be output in the same manner as other function blocks. The message is displayed in the process
alarm view, while the unit name appears in place of the normal tag name and the unit comment in
place of the tag comment.
Unit Alarms of Unit Instrument

Tag mark and level of alarm priority can be specified for unit instrument. The level of alarm priority
determines the view display, alarm sound, acknowledgment action, etc.
2.7.2 Unit Mode and Unit Status Change Messages Page 1 of 1
2.7.2 Unit Mode and Unit Status Change Messages

The unit has unit mode change messages and status change messages.
Unit Mode Change Message

A message is output when unit mode is changed.
Unit Status Change Message

A message is output when unit status is changed.
2.7.3 Sequence Control Messages - Unit Instrument Page 1 of 1
2.7.3 Sequence Control Messages - Unit Instrument

Five types of messages can be output from operations of the unit instruments. Outputting the
messages can be programed in the operations written in SEBOL.
SEE For more information about SEBOL message statements, refer to:
ALSO 9., “SEBOL Message Statements” in SEBOL Reference (IM 33J05L20-01EN)
Operator Guide Message

This message can be written using an optional character string or a character string specified by the
element number of an operator guide message. The output of the message can be programed using
the “opeguide” statement in the operations written in SEBOL.
Dialog Message
element number of an operator guide message. The output of the message can be programed using
the “dialogue” statement in the operations written in SEBOL. The use of this message permits
exchanging data between the operator and the operation and monitoring console by dialog message
window.
Printout Message
A message written using an optional character string or a character string specified by the element
number of a printout message can be output to the printer. The output of this message can be
programed using the “message” statement in the operations written in SEBOL. The message will be
saved in the historical message file.
Historical Message
element number of a historical message. The output of the message can be programed using
the “history” statement in the operations written in SEBOL. The message will be saved in the
historical message file.
Request Sequence Message

element number of a request message. The output of the message can be programed using
the “request” statement in the operations written in SEBOL.
2.7.4 System Alarm Messages Page 1 of 1
2.7.4 System Alarm Messages

System alarm messages include system-fixed and user-defined alarm messages.
System-Fixed Alarm Messages

System-fixed alarms are output when error is caused in the action of the unit, such as follows:
• Errors caused during execution of the unit.
• Errors caused during execution of operations.
• Errors caused during execution of commands from Process Management.
SEE For more information about the output format of each message, refer to:
ALSO 2., “Message Output Details” in Operating Messages (IM 33J05A30-01EN)
User-Defined Alarm Messages

User-defined alarms can be output from operations. Alarm generation and recovery messages can
be written using optional character strings and their output can be programed using the “sysalarm”
statement in the operations written in SEBOL.
SEE For more information about SEBOL sysalarm statement, refer to:
ALSO 9.6, “sysalarm” in SEBOL Reference (IM 33J05L20-01EN)
2.8 Operations Page 1 of 2
2.8 Operations
An operation is an independent phase in an ordered set of production phases assigned to a unit
instrument and executes a sequence of control steps within the unit procedure.
Positioning of Operations
▼ Operation
Each step in a unit procedure represents an operation. When a unit procedure of a unit instrument
starts, the operation will be executed while the step is activated in the sequence.
Execution time is automatically shared when more than one operation are executed in parallel.
Figure 2.8-1 Positioning of Operations
Types of Operations
There are two types of operations are available, the operations are programmed in SEBOL or in SFC,
so that they are distinguished as SEBOL type and SFC type operations.
SEBOL Type Operations

Operations and phases are programmed in SEBOL. The model of the SEBOL operation block is
OPSBL.
SFC Type Operations

Operations are programmed in SFC but the phases are programmed in SEBOL, logic charts or
sequence tables. Moreover, the SFC type operations categorized into 6 block models according to
their available data items.
• OPSFC (SFC Operation)
• OPSFCP1 (SFC operation with floating-data parameters)
2.8 Operations Page 2 of 2
• OPSFCP2 (SFC operation with character-data parameters)

• OPSFCP3 (SFC operation with floating/character-data parameters)
• OPSFCP4 (SFC operation with integer/character-data parameters)
• OPSFCP5 (SFC operation with floating/integer-data parameters)
Special Operations
In addition to ordinary unit procedure-started operations, there are two types of special operations:
• Initialization operation:
An operation to initialize the process before execution.
• Monitoring operation:
An operation to permit execution according to the process status which is monitored at all times.
2.9 Data Items of Operation Page 1 of 3
2.9 Data Items of Operation

Only system-fixed data items are available in an operation. There is no user-defined data items. If
user defined data items are required, a unit instrument for starting operations should be created.
Data Types of Operation

The data types of an operation are shown as follows. The data of other function blocks are attached
with data status signals but the data of operation cannot be attached with data status signals.
Table 2.9-1 Data Types of Operation
Type Description Remarks

U32 32-bit unsigned integer 0 to 4294967295
38 38
F32 Single-precision floating-point (32 bits) -3.402823 • 10 to 3.402823 • 10
308 308
F64 Double-precision floating-point (64 bits) -1.79769313486231 • 10 to 1.79769313486231 • 10
CHR*n Character-string (2≤n≤16) –
Operation Data Items Available

The following data items can be applied to the operations of all models.
Table 2.9-2 Operation Data Items

Data name Default Remark
name type (*1)
MODE Block mode CHAR*8 x AUT
OMOD Block mode( lowest priority) CHAR*4 AUT
CMOD Block mode( highest priority) CHAR*4
BSTS Block status CHAR*8 x STOP
PREBSTS Previous block status CHAR*8
AFLS Alarm flashing CHAR*8 x
AF Alarm detection specification CHAR*8 x
Alarm suppression
AOFS CHAR*8 x
specification
ERRP Error-caused plane number U32 0
ERRS Error-caused step number U32 0
ERRL Error-caused line U32 0
ERRF Error-caused program unit CHAR*8
STEPNO Current step number U32 0
PHASE Phase name CHAR*16
Interrupt processing phase
IHASE CHAR*16
name

UAID User application ID I16 x 0
DILG Dialog acknowledgement U32 x
SEMA Semaphore name CHAR*8
For Process
Management
UNITNAME Unit name CHAR*16
For Process
Management
OPID Operation ID I16 0
QUEUE[5] Signal queue display CHAR*16
Data Items of SFC Operation with Floating-Data Parameters

Data items may be applied to the SFC operation with floating-data parameters (OPSFCP1) are as
follows.
Table 2.9-3 Data Items of SFC Operation with Floating-Data Parameters
Data Item Data Type Entry Security Level Input Check

DT01 to DT14 F64 Yes 3 None
Data Items of SFC Operation with Character-Data Parameters

Data items may be applied to the SFC operation with character-data parameters (OPSFCP2) are as
follows.
Table 2.9-4 Data Items of SFC Operation with Character-Data Parameters

CH01 to CH07 CHR16 Yes 3 None
Data Items of SFC Operation with Floating/Character-Data

Parameters
Data items may be applied to the SFC operation with floating/character-data parameters (OPSFCP3)
are as follows.
Table 2.9-5 Data Items of SFC Operation with Floating/Character-Data Parameters

Data Items of SFC Operation with Integer/Character-Data

Parameters
Data items may be applied to the SFC operation with integer/character-data parameters (OPSFCP4)
are as follows.
Table 2.9-6 Data Items of SFC Operation with Integer/Character-Data Parameters

INT01 to INT08 I16 Yes 3 None
Data Items of SFC Operation with Floating/Integer-Data

Parameters
Data items may be applied to the SFC operation with floating/integer-data parameters (OPSFCP5)
are as follows.
Table 2.9-7 Data Items of SFC Operation with Floating/Integer-Data Parameters

INT01 to INT08 I16 Yes 3 None
2.10 SFC Operation Page 1 of 2
2.10 SFC Operation

The functions of an SFC operation is the same as a normal SFC block.
Composition of An SFC Operation

The composition of an SFC operation is shown below, in which steps are regarded as phases:
Figure 2.10-1 Composition of an SFC Operation
Differences between Operation and Unit Procedure

The SFC (Sequential Function Chart) in an operation and the SFC in a unit procedure have the
following differences:
• The SFC cannot handle parallel sequences and wait steps.
• The SFC in an operation describes transition conditions using SEBOL expressions.
The SFC in a unit-procedure uses logical expressions, which are used exclusively for unit
instruments.
• The actions of SFC in an operation may be redirected to a program written in SEBOL, sequence
table or logic chart for execution.
The actions of SFC in a unit procedure may be redirected to an operation name or an operation
generic name for executing the operations.
Differences between Operation and SFC Block

The SFC in an operation and the SFC in an SFC block have similar functions. An operation started
from a unit instrument can be considered as an SFC block. Also an SEBOL type operation is about
the same as an SFC block which only has an initial step.
The following are the differences between the SFC in an operation and the SFC in an SFC block:
2.10 SFC Operation Page 2 of 2
Accessing Unit Instrument Data

An operation may access the unit instrument data in the format of <TagName.DataItemName>. If
the unit instrument is where the operation is started, the unit instrument data may be accessed in
the format of <%%.DataItemName>. While, an SFC block may access the unit instrument data only
with the format of <TagName.DataItemName>.
Starting an Operation
An operation can be started only from a unit instrument. An operation can not be started separately.
Accessing Common Block Data

When Batch Management is applied, common block data for the recipe can be accessed from the
SFC in a operation. However, it cannot be accessed from an SFC block.
Start and End of Recipe Unit Procedure

When Batch Management is applied, the SFC in an operation can start and end the recipe unit
procedure operated by other unit instruments in the same recipe.
• A download of the recipe unit procedure operated by other unit instruments in the same recipe
can be requested.
• A unit instrument to be executed by the recipe unit procedure operated by a unit instrument in
the same recipe can be assigned (dynamic assignment of unit).
Setpoint of PAUS Stop Position

The following can be set for the PAUS stop position of an SFC operation (OPSFC, OPSFCP1,
OPSFCP2, OPSFCP3, OPSFCP4, OPSFCP5). These cannot be set for an SFC block.
• Initial step
After PAUS stop, execution will restart from the initial step. If "Initial step" is set for the PAUS
stop position, the local variable, local generic name, and tag generic name of the unit instrument
will not be initialized when returning to the initial step. The SEBOL program will continue to use
the data entry value input so far after resuming from PAUS.
2.10.1 SFC Operation Page 1 of 4
2.10.1 SFC Operation

The SFC (Sequential Function Chart) in an operation runs an ordered set of running procedures i.e.,
an ordered set of phases. In one word, the steps of the SFC in the operation may be assigned with
the functions by entering the designated tag names of the phases.
Basic SFC Elements of Operation

The SFC in an operation uses the following basic elements:
• Step
Describes action.
• Transition
Describes transition condition.
• Connection
Connects a step to transition, and transition to a step.
Table 2.10.1-1 Unit Procedure SFC Basic Elements
Element Name Symbol Remarks

Double height initialization step is also
Initial Step
available.
Step Step Double height step is also available.
Interrupting Step
Selective Seq.-
Split
Selective Seq.-
Join
Loop-Branch
Connection Loop-Join
Jump Down nn: numerals
Jump Up nn: numerals
Jump To nn: numerals
Link
Operation SFC Steps

The square in the step is for placing the step number (01 to 99).
The action of the SFC step is scripted in a rectangle shown to the right of the step. When the step is
activated, the phase in the action box will be started. In the phase, a SEBOL, sequence table or logic
chart program may be redirected.
Figure 2.10.1-1 SFC Step
Every step is either in the active state, in which the step is being executed, or the inactive state, in
which the step has been completed or is yet to be executed.
TIP A maximum number of steps can be described in one column is 50. With parallel, transition, and
jump sequences, up to 99 steps can be described in one SFC.
Operation Step Action

The step action is the process executed when the step is active. For an operation SFC step, the
process is the phase defined in the action box. When execution of the phase is completed, the step
is inactivated and processing is shifted according to the connection of the step.
TIP When a comment is defined entered when defining he steps properties, the comment may be
displayed in the action column of the SFC view displayed on a HIS.
Operation Initial Step

The initial step is the first step to be executed in an operation. The step number in this case is
shown in a double square, however, the basic function of this step is the same as other steps.
Figure 2.10.1-2 Initial Step
Interrupting Steps in an Operation

The program for normal processing is referred to as main program, the programs for interrupt the
main program invoked by certain events are referred to as interrupting SFC programs. The
interrupting programs are extended from interrupting steps.
Figure 2.10.1-3 Interrupting Steps
Step Actions
The steps other than interrupting steps are scripted as actions for execution.
When using SEBOL, clicking the step may open the editing window for editing SEBOL scripts. When
using sequence table or logic chart, the tag name or the generic name of the sequence table or the
logic chart shall be assigned to the step. When assigning a generic name, the tag name of the unit
instrument where the generic name belongs to needs be designated.
There are following types of step actions.
• SEBOL
• SEBOL one-shot
• Sequence table
• Sequence table one-shot
• Logic chart
• Logic chart one-shot
SEE For more information about action description, refer to:

ALSO 2.12, "Actions of Operation"
Operation SFC Transition

Transition is shown with a short horizontal line crossing the step-connecting link. Transition defines
the condition of transition using a logical expression. Execution advances to the linked step when the
result of the expression is true. If the transition condition is not established, the check for the
conditions will continue at each basic cycle.
The transition condition will be parsed as soon as the current step operation is completed.
Figure 2.10.1-4 SFC Transition
Operation SFC Connections

Link elements, which are vertical or horizontal lines connecting unit-procedure steps and transitions,
indicating the execution order or path of steps. Examples of their use are shown below:
Figure 2.10.1-5 Link Elements
2.10.2 Compound Sequence

A compound sequence is composed of a number of laterally described sequences. A selective
sequence is a compound sequences.
Selective Sequence
In the case of executing a step by switching among the multiple choices according to transition
condition, the selective sequence may be applied. For one selective sequence, eight choices may be
set in parallel.
An example of selective sequence is shown as follows.
Figure 2.10.2-1 A Selective Sequence
In the above example, the three laterally linked transition conditions are evaluated from the left
when step 05 has been completed and inactivated. If one of the conditions is true, the step linked to
that transition is activated. If there are two or more true conditions, the one on the left has priority
over the others.
If none of the conditions is true, the evaluation will be repeated at every basic scan period until one
of the conditions becomes true.
2.10.3 Transition Conditions

The transition conditions in the operation SFC are explained.
Scripts of Conditional Transition

The conditional transition expression may be scripted in SEBOL. When the result of the condition
expression for the transition is not 0, the transition will be committed while when the result is 0, the
transition will not. When an arithmetic expression is used, transition will be committed when the
result is 1, transition will not committed when the result is 0.
If the condition expression is omitted, the transition will be committed unconditionally. Moreover,
the maximum number of transitions including the unconditional transitions is 99 per FCS.
Operators in Condition Expression

The following operators can be applied in the expressions for conditional transition.
Table 2.10.3-1 Operators in Condition Expression
Operator Description
== True if left and right side are equal. False if not equal.
<> True if left and right side are not equal. False if equal.
< True if right side is larger than left side. False if not.
<= True if right side is larger than or equal to left side. False if not.
> True if right side is smaller than right side. False if not.
>= True if right side is smaller than or equal to left side. False if not.
Variables in Condition Expression

The following variables can be used in the condition expressions for conditional transition:
Table 2.10.3-2 Variables in Condition Expressions
Variable Remarks
Constant -
Global variable -
Local variable Need to be declared in step action.
Global tag name Tag name declared by “global block.”
Tag name declared by “block” in SEBOL-step action.
Tag name Sequence table tag name in sequence table step action.
Logic chart tag name in logic chart step action.
Global generic name Generic name declared by “global genname.”
Local generic name Declared by “genname” in step action.
Unit generic name Declared by “global unit genname,” or declared by “unit genname” in step action.
%$ Replaced by tag name of sequence table or logic chart used in action step.
Restrictions of Variables in Condition Expression are shown below.

• Global variables, step local variables, and constants can be used in array subscript expressions for
array-element variables.
• SEBOL built-in functions can be used in condition expressions.

• “%$” entered in transition condition is replaced by the tag name of the sequence table/logic
chart which defines action. The condition expression %$.MODE=“AUT” will be changed to
ST0101.MODE=“AUT” if the sequence table tag name is ST0101, for example.
• If the sequence table/logic chart is specified using a unit generic name, “%$” cannot be replaced
by the generic name. The generic name must be written in the condition expression in this case.
Comparison of Data in Transition Condition

The following should be noted regarding the comparison of data performed in transition conditions:
Comparison of Numeric & Character-String Data

An error message will be generated (by transition condition check) if comparing a character string to
a numeric value in transition condition.
Comparison of Floating-point Data

Floating-point data contain very small errors because of calculation accuracy, and they could actually
be different internally even if two units of floating-point data are apparently the same. So their
comparison could be determined false when they are compared using (==) or (<>).
It is thus necessary to use (>=) or (<=) in comparing floating-point data instead of (==) or (<>).
2.10.4 Operation Sharing Page 1 of 3
2.10.4 Operation Sharing

One operation consists of an operation logic program (SFC). Multiple unit instruments corresponding
to the same type of equipment entity which have the same control sequence can share the same
operation.
What is Operation Sharing

▼ Sharing an Operation
One SFC may be shared by multiple operations. the shared SFC may be created on FCS Sequence
Library Builder. The SFC sequence name of the created SFC may be defined on the Function Block
Detail Builder.
In the shared SFC program, the tag name or the tag generic name may be specified.
When a program in an operation access a function block or another unit instrument, the tag generic
name is used instead of using the tag name. Using the tag generic name, the program may created
independently from the tag name assignment, thus enables the sharing of the SFC program. The
table corresponding the generic tag names in the operation and the actually used tag names is held
in the unit instrument. The tag generic name is defined on unit instrument when the operation is
started. One unit instrument may define up to 512 tag generic names.
SEE For more information about FCS sequence library, refer to:
ALSO 5., “FCS Sequence Library” in Engineering Reference Vol.2 (IM 33J10D11-01EN)
Operation Generic Name Definition

▼ Tag Generic Name
Tag generic name is an ID of an operation, it can be used even when the operation is not shared.
The items to be defined for an operation are shown as follows.
Tag Generic Name

The tag generic name may be defined by a SEBOL statement in the operation. A tag generic name
may be defined with up to 8 alphanumeric characters.
Array Element Number

The array element for the tag generic name may be defined from 0 to 99. When array is not used,
the default setting is 0.
Tag Name
Corresponding to the tag generic name, the actually used tag name may be specified.
Example of Sharing an Operation

For example, if an operation may be called from unit instrument A or unit instrument B, when called
from unit instrument A, the table corresponding tag generic name and tag name in the unit
instrument A is referred, while when called from called from unit instrument B, the table
corresponding tag generic name and tag name in the unit instrument B is referred.
When using the tag generic name of the operation’s program like this, the table corresponding the
generic tag names and the tag names in the unit instrument may be referred, thus the logic in the
operation may be shared. The sharing is only ranged within the same station. When beyond one
station, they should be created separately.
The data area of the operation (function block data) can not be shared.
Figure 2.10.4-1 Sharing an Operation
Operation ID
In a unit-procedure SFC, the same operations described in the same control algorithm are often
repeatedly invoked from a number of steps. It then becomes necessary to identify the round of the
repetition in order to change operation processing accordingly. For this purpose, every step needs
an operation ID. In the case like this, each step of the procedure will assign the operation with an
operation ID. When the operation is started, the operation ID assigned will be attached to the
operation.
Figure 2.10.4-2 Operation ID
When creating an unit procedure SFC, the operation to be called from a step may be defined with a
name and an arbitrary ID number. If the user does not define the ID for the operation, a system
default ID number will be assigned to the operation. Actually, there is no need for a user to worry
about the operation’s ID.
For example, in the case that the operation of step 2 (Charging 1) is assigned with an ID number 1,
and the operation for step 3 (Charging 2) is assigned with an ID number 2, when unit instrument
starts execution, the operation ID will be used as the arguments for calling the operation. An
operation’s SEBOL program can read the argument to determine the step where it is called, so that
the operation may switch it processing accordingly.
2.11 Mode and Status of an Operation Page 1 of 1
2.11 Mode and Status of an Operation

Like a function block, mode and status are also provided to an operation. The block mode of an
operation is referred to as operation mode, while the block status of an operation is referred to as
operation status. This chapter will give explanations on the operation mode, operation status and
the operation state transition.
2.11.1 Operation Mode Page 1 of 1
2.11.1 Operation Mode

Operation mode indicates the operation’s control state. Normally, an operation is defined as apart of
a unit instrument, the operation mode and operation status changes are controlled from the unit
instrument.
Operation Mode
An operation may have the following modes. The modes of operation are system-fixed.
O/S (Out Service) Mode

The operation is not running.
SEMI (Semi-Automatic) Mode

▼ SEMI Mode Operation
The block stops at the start step of each operation, and the step is executed upon a external
command such as a command from the operation and monitoring console.
The mode can be “enabled” or “disabled” for each operation.
When it is “disabled”, the operation will not have the SEMI mode.
AUT (Automatic) mode:

The operation continuously runs from one step to another.
2.11.2 Operation Status Page 1 of 1
2.11.2 Operation Status

An operation’s status may indicate the operation’s running state.
Operation Status
The running state of an operation such as PAUSE is indicated by the operation’s status. The statuses
of the operation are system-fixed.
The statuses of an operation are shown as follows.
STOP
The operation is stopped and ready for starting.
RUN
The operation is running by executing its actions while checking transition conditions.
PAUS
The operation is temporarily suspended.
ABRT
The operation is terminated abnormally.
2.11.3 Operation Mode and Status Change Command Page 1 of 1
2.11.3 Operation Mode and Status Change Command

Just like other function blocks, an operation’s mode and status may be changed by an operation
mode change or status change command.
Mode Change - Operation

To change an operation block mode, the block mode change command can be used. The block
mode of an operation may be changed by a mode change command or a status change command
from unit instrument. An operation may change its mode without designation. The modes of an
operation are system-fixed.
AUT
Command for changing the operation to automatic mode
SEMI
Command for changing the operation to semi-automatic mode
O/S
Command for changing the operation to out-service mode
Status Change - Operation

An operation may be started by a command from a unit instrument. A status change command from
the unit instrument may also change the operation’s block status. An operation can not start by the
command from itself.
Table 2.11.3-1 Block Status Change Commands
Symbol Service Description

RUN Run Starts operation or restarts paused operation.
STOP Stop Stops current operation.
PAUS Pause Pauses current operation.
RSET Reset Changes ABRT status to STOP.
ABRT Abort Forcibly terminates current operation.
2.11.4 Operation Block Status Transition Page 1 of 2
2.11.4 Operation Block Status Transition

Operation block status transition will be committed accordingly when a mode change or a status
change command is given.
Operation Block Status Transition

▼ PAUS Stop Position
The status transition scheme of the operation block is shown below:
Figure 2.11.4-1 FigureTransition of Operation Block Status
• The RUN command starts execution of the SFC block in the STOP status, which then changes to
RUN when started. When an operation is started, the operation's status changes to RUN.
• The PAUS command suspends execution of the SFC block in the STOP status at the start of the
initial step, the status then changes to PAUS.
• When the operation block status is changed to PAUS during execution of a SEBOL step action,
the stopping position can be specified at the start of the step, the current line, or the initial step.
• When an operation is in SEMI mode, the operation status changes from RUN to PAUS at the start
of every step. The step can then be executed upon receiving the RUN command from the
operator consoles.
Operation Step Jump

When an operation SFC is in SUSPEND status, it is possible to jump its sequence to a designated
step. Step jump enables an operation SFC to transit to a desired step for execution, either forward
or backward is allowed. There are two ways to set the unit into SUSPEND status, by setting the unit
into Semi-automatic (SEMI) mode or by sending a command for changing to PAUS status.
Changing the Operation to SEMI Mode
2.11.4 Operation Block Status Transition Page 2 of 2
This method changes the running operation started from a unit instrument into the semi-automatic
(SEMI) mode first.
When the operation changes to SEMI mode, the operation temporarily stops at the beginning of a
step (phase), the sequence status becomes PAUS.
Under this situation, on the SFC view, the step may jump forward or backward. Then sending a RUN
command to the operation may start the execution from the jumped step.
Changing the Operation to PAUS Status

Sending a PAUS status change command may change an operation to a temporary stop (PAUS)
status.
Under this situation, on the SFC view, the step may jump forward or backward. Then sending a RUN
command to the operation may start the execution from the jumped step.
2.12 Actions of Operation Page 1 of 1
2.12 Actions of Operation

This section explains the SEBOL, sequence table and logic chart related to setting the actions in an
operation.
2.12.1 Action Scripts in SEBOL Page 1 of 6
2.12.1 Action Scripts in SEBOL

The following three types of steps can be scripted in SEBOL.
• Initial step
• SEBOL step
• SEBOL one-shot step
SEBOL Variables
Global and local SEBOL variables can be used in the operation when a step is scripted using SEBOL.
The global variable can be accessed from all the SEBOL steps in the operation, while the local
variable can be accessed from only one step.
Areas are allocated to both types of variables and they are initialized to zero when the operation is
started.
The reserved areas will be released when the operation is completed.
TIP In the case of a character-string variable, the global or local variable is initialized to a zero-length
character string when the operation is started.
Global Variables
Global variables can be accessed from any SEBOL step in the operation. To use global variables,
they should be specified in the initial step as shown below:
Figure 2.12.1-1 Global Variables
TIP Global variables cannot be accessed from the steps described in sequence table or logic chart.
Local Variables
Local variables can be accessed only from the steps for which the use of local variables is declared.
To use local variables, they should be specified in the step as shown below:
Figure 2.12.1-2 Local Variables
The same local variable name can be used in different steps, in this case, each variable will be
allocated with a separate area.
If a step is repeatedly executed in a loop, the local variable remains unchanged throughout the
repeated execution.
Restrictions
The same name cannot be assigned to global and local variables. An error will occur if the two has
the same name.
Function Block Declaration

The use of a function block can be declared globally or locally. The global declaration permits access
from all SEBOL steps, while the local declaration permits access only from the declared step.
SEE For more information about how to access function block data, refer to:
ALSO 5.1, “Usage of Function Block Data” in SEBOL Reference (IM 33J05L20-01EN)
Global Declaration
A function block can be accessed from all SEBOL steps when the use of that function block is
globally declared in the initial step as shown below:
Figure 2.12.1-3 Global Declaration
Local Declaration
A function block can be accessed from just one step when the use of the function block is locally
declared in that step as shown below:
Figure 2.12.1-4 Local Declaration
Restrictions
No error will occur when the tag name specified in global declaration is used also in local
declaration; however, an error will occur if different block codes are specified. An error will also
occur if specified global and local generic names are identical.
Branching
The destination for branching is restricted to be within the step in which branching is specified using
a “goto” statement, for example. Processing cannot be branched to other steps using “error”
and “errorsub” specifications, “goto” statements, etc.
SEE For more information about "error" and "errorsub" specifications, refer to:
ALSO “ Setting Branching Destination for Error Occurrence” in 13.1, “Error Handling for
Statements with I/O or Communication” in SEBOL Reference (IM 33J05L20-01EN)
For more information about "goto" statements, refer to:
8.7, “goto” in SEBOL Reference (IM 33J05L20-01EN)
“quit” Statement
The “quit” statement terminates the action being executed.
When this statement is executed as a step action, the transition condition defined succeeding the
step will then be evaluated.
Initial Step
The scripts for initial step are described in this section:
Order of Scripts
The initial step action should be described in the order of global variables, local variables, and
execution statements as shown below; an error will be caused otherwise.
Figure 2.12.1-5 Order of Scripts
The initial step action can be described using up to 2000 lines. No parameters are used in the action
scripts.
The initial step will be ended when the last statement or a “quit” statement is executed.
Example of Scripts
The following is an example of initial-step scripts.
!global variable declaration
global block TM TM301, TM302
global block SIO-11 VL301, VL302
global integer loop
global char*16 name
integer i, j, k
!action statement
.......
Use of “#define”
Names can be defined using “#define” anywhere within the initial step.
The defined names can then be used in all SEBOL steps or in transition condition.
SEE For more information about "#define" statement, refer to:

ALSO 1.8, “Substitution of Character String” in SEBOL Reference (IM 33J05L20-01EN)
Use of “#include”
“#include” can be specified for file-inclusion anywhere within the initial step.
The order of all statements in the included file, however, must be in conformity with that of the
initial step. Otherwise, an error is caused for the statements in the included file.
SEE For more information about "#include" , refer to:

ALSO 1.9, “Include File” in SEBOL Reference (IM 33J05L20-01EN)
Use of “#IMPLICIT”
A “#IMPLICIT” command can be used in the initial step. The command is then valid within the entire
operation.
This command cannot be scripted in any other steps.
SEE For more information about "#IMPLICIT" , refer to:

ALSO 1.7, “Implicit Declarations of Variables” in SEBOL Reference (IM 33J05L20-01EN)
SEBOL Steps
The SEBOL step action should be scripted in the order of variables and execution statements as
shown below; otherwise an error will occur.
The SEBOL step action can be scripted using up to 2000 lines. No parameters are used in the action.
The step will be ended when the last statement or a “quit” statement is executed.
Figure 2.12.1-6 SEBOL Steps
Example of Scripts
The following is an example of SEBOL step scripts:
block PVI LI303
integer ierr
!action statement
wait until (LI303.PV >= 10.0) ; ierr
.......
Restrictions
#define, #include, and #IMPLICIT command cannot be used with SEBOL steps. These commands
can be used only by the initial step. However, the name defined by means of “#define” in the initial
step can be used.
SEBOL One-Shot Steps

The SEBOL oneshot steps are explained in this section:
Order of Scripts
The SEBOL oneshot-step action should be scripted in the order of variables and execution
statements as shown below; otherwise an error will occur.
No parameters are used in the action. The step will be ended when the last statement or a “quit”
statement is executed.
Figure 2.12.1-7 Order of Scripts
Example of Scripts
The following is an example of SEBOL oneshot-step scripts. In the following example, the common
switches SW301 and SW302 should be defined on the common switched builder before they are
used in the scripts.
block %SW SW301, SW302
!action statement
SW301.PV = 1
SW302.PV = 1
Execution
The SEBOL oneshot-step action will be executed without any break once it is activated. Its
processing time will not be shared by any other SFC program. No interrupt signals nor status change
instructions are allowed to interrupt the execution until it is completed.
Restrictions
The SEBOL oneshot-step action can be continuously executed up to 20 lines. If a “for” statement is
used, for example, and one line is repeatedly executed, each repetition is counted as one line. If
execution is attempted exceeding 20 lines, an execution error is caused and the successive action
will be executed not as oneshot but normal step action.
The following statements should not be used in order to avoid any execution error:
• Statement for accessing function-block data at another control station.
• “signal” statement for sending signals to another control station.
• “qsigcancel” and “qsigmove” statements for manipulating function block at another control
station.
Also the following statements should not be used in order to avoid any error:
• “drive” statement, “seqstable” and “logicchart” statements with “drivewait” specification.
• “wend,” “until,” and “next” statements without “@.”
• “wait until,” “delay,” and “delaycycle” statements.
• “dialogue” statement.
• “nopreempt begin” and “nopreempt end” statements.
• “semlock wait” statement.
• “wait for qsignal” statement.
• “ssdtwrite” and “ssdtwritebit” statements.
#define, #include, and #IMPLICIT command cannot be used with SEBOL oneshot steps. These
commands can be used only by the initial step. However, the name defined by means of “#define”
in the initial step can be used.
2.12.2 Action Description Using the Sequence Table Page 1 of 3
2.12.2 Action Description Using the Sequence Table

The following two types of step actions can be described by sequence table.
• Sequence table (ST) step
• Sequence table (ST) one-shot step
SEE For more information about Sequence Table, refer to:

01EN)
Tag Name
The tag name or the generic name of the sequence table for the step needs to be designated. The
same sequence table can be shared by different steps.
An operation or a sequence table in the same control station may be designated as the step. When
using a generic name, the link between the generic name and the tag name should be defined in the
unit instrument that running the operation.
Step Designation
When using a step of step type sequence table as a step action, the step name of the step type
sequence table can be designated.
In the case that the sequence table step is an one-shot step, the specified step and step 00 will be
executed for a one-shot.
In the case that the sequence table is an periodic sequence table, the specified step and step 00 will
be executed for a one-shot, then the sequence table will continue in its own pace of execution
periodically. Step 00 will also be executed in every scan period. If a step name designated for a non-
step sequence table, the designation will be ignored.
The step can be configured with following options.
Head
The sequence starts from the beginning of the sequence table when the it is invoked.
Continue
The sequence starts its execution from the current running step. The running step number is stored
in the data item PV of the sequence table.
Specification
The sequence starts its execution from the specified step. The specified step name should be
entered for this type execution.
Variable Designation
Vary with the types of action, the variables designated for the step are different.
Sequence Tables
When [Sequence Tables] is designated, the variable will be kept in the SFC/SEBOL return even
message (%RE) as a parameter.
The value 0 through 65535 defined in the action-signal column of the sequence table is stored as a
variable.
Sequence Table One-Shot

When [Sequence Table One-Shot] is designated, the result of condition test of the sequence table is
stored as the variable, which is either true (1) or false (0).
• In the case of a non-step sequence table, the result is true if at least one of 32 rules is satisfied
and false if none is satisfied.
• In the case of a step sequence table, all the rules for the specified step and step 00 are
evaluated. Then the result is true if at least one rule is satisfied and false if none is satisfied.
Variable Name
The variable names for SFC/SEBOL return event message parameters and the condition test results
are as following 4 types.
• Operation data item
When storing data as a data item in the operation, specify the variable name as follows:
%.<data item>
• Global variable
name as follows:
In this case, the tag name should have been declared using “global long” in the initial step. When
storing the condition testing result for an ST oneshot step, the tag name must be present within
the same control station as the SFC block; specifying a tag name from another control station
causes error when the operation is executed.
genname” in the initial step. When storing the condition testing result for an sequence table
oneshot step, the tag name present within the same control station as the operation block must
be assigned to the global generic name using the “assign” statement.
Sequence Table Steps

When sequence table step is designated, the sequence table action is a periodic start (T) sequence
table.
The sequence table step is oneshot-executed when its action is activated, and the sequence table
block mode changes to AUT at the same time. The sequence table will then be periodically executed
according to its own action timing.
The sequence table step action is terminated when an SFC/SEBOL return event message (%RE) is
received. The sequence table block mode then changes from AUT to MAN.
Sequence Table One-Shot Step

When sequence table one-shot step is designated, the sequence table action is an one-shot start (O)
sequence table.
The sequence table one-shot step is oneshot-executed when its action is activated. The sequence
table block mode remains unchanged after the execution.
2.12.3 Action Description Using Logic Charts Page 1 of 2
2.12.3 Action Description Using Logic Charts

The following two types of step actions can be described by logic chart.
• Logic chart step
• Logic chart one-shot step
SEE For more information about logic chart, refer to:

ALSO 2.3, “Logic Chart Block (LC64, LC64-E)” in Function Blocks Reference Vol.2 (IM 33J15A31-
01EN)
Tag Name
The Tag name or generic name of the logic chart for the step needs to be designated. One logic
chart can be shared by different steps. The tag names that can be specified for the step execution
name are limited to the logic chart in the same control station.
An operation or a sequence table in the same control station may be designated as the step. When
using a generic name, the link between the generic name and the tag name should be defined in the
unit instrument that running the operation.
Variable Designation
When [Logic Chart] is designated, the variable will be kept in the SFC/SEBOL return even message
(%RE) as a parameter.
The value 0 through 65535 defined in the action-signal column of the sequence table is stored as a
variable.
When [Logic Chart One-Shot] is designated, the variable can not be used.
Variable Name
The variable names for SFC/SEBOL return event message parameters are as following 4 types. The
names of both variables can be specified in one of the following four different manners:
• Operation data item
When storing data as a data item in the operation, specify the variable name as follows:
%.<data item>
• Global variable
name as follows:
In this case, the tag name should have been declared using “global long” in the initial step.
2.12.3 Action Description Using Logic Charts Page 2 of 2
genname” in the initial step.
Logic Chart Step

When logic chart step is designated, the logic chart action is a periodic start (T) logic chart.
The logic chart step is oneshot-executed when its action is activated, and the logic chart block mode
changes to AUT at the same time. The logic chart will then be periodically executed according to its
own action timing.
The logic chart step action is terminated when an SFC/SEBOL return event message (%RE) is
received. The logic chart block mode then changes from AUT to MAN.
Logic Chart One-Shot Step

When logic chart one-shot step is designated, the logic chart action is an one-shot start (O) logic
chart.
The logic chart one-shot step is oneshot-executed when its action is activated. The logic chart block
mode remains unchanged after the execution.
2.13 Operation Actions Page 1 of 1
2.13 Operation Actions

Operation internal processing and actions are explained in this section.
2.13.1 Start and End of An Operation Page 1 of 2
2.13.1 Start and End of An Operation

This section explains how to start and how to end an operation.
Start an Operation
An operation can be started from a unit instrument. An operation can not start by itself.
End an Operation
One of the following methods may end an operation.
• By exit statement
• Change block status (BSTS) to STOP
• By a command from a unit instrument
The programs in which the exit statement and the status change scripts are allowed are shown as
follows.
Table 2.13.1-1 Programs Allow exit Statement and Status Change Scripts
Program “exit” statement (*1) BSTS change (*1)

Main program x x
Status-change pre-process - -
Status-change post-process x -
Interrupt signal processing x x
Common error processing x (*2)
*1: x: available
-: unavailable
*2: The feasibility of block status change during error processing is determined by the location where the
error involved has been caused. If the error is in the main program, the status can be changed. If the
error is in the status-change post-process, the status cannot be changed.
SEE For more information about commands from unit instruments, refer to:
End an Operation by “exit” Statement

Use the “exit” statement may terminate an operation unconditionally, which can be written as
follows:
Figure 2.13.1-1 End an Operation by “exit” Statement
The operation block will be terminated when the exit statement is executed and the block status
changes to STOP. The status change pre-/post-processes will not be executed.
End an Operation by Changing Block Status

In a SEBOL program, by changing an operation block’s status BSTS into STOP may end the
operation.
2.13.1 Start and End of An Operation Page 2 of 2
Example:
.......
.......
%.BSTS = "STOP"
.......
Status-change pre- and post-processes can be executed when changing the block status to STOP.
2.13.2 Pause an Operation Page 1 of 5
2.13.2 Pause an Operation

The execution of an operation can be paused in one of the following conditions.
• When the operation block mode is SEMI.
• When the operation block being executed receives a command to change the status to PAUS.
• When the operation block ready for execution receives a command to change the status to PAUS.
• When the operation block ready for execution in the SEMI mode receives a command to change
the status to RUN.
When the block is paused while a program line is being executed, how the interrupted action is
affected varies according to the contents of that line.
The restarting of the paused block is determined by the built-in function “ckstep” and action when
the block is restarted varies according to the condition of the block at the time of pause.
Pausing
The four conditions in which an operation may be paused are described below, the paused operation
block can be restarted by commanding a status change to RUN in any of these conditions:
When the Operation Block in SEMI Mode

When the block is in SEMI mode and executed to the start of a main program step, the block status
changes from RUN to PAUS and the block pauses at the start action of the operation.
• No status-change processing takes place at this time.
• Execution is not paused at the start of an interrupt processing step.
When the Operation Block Receives a PAUS Command

When the block being executed receives a PAUS command, the block status is changed from RUN to
PAUS and the block will be paused.
• If the block is paused during a SEBOL-described action, the builder-defined PAUS position will be
applied to the restarting of the block.
• If the block is paused during a sequence table described action, the block will be restarted from
the start of the step at all times even if the PAUS position is defined as the current line.
• If the block is paused during a sequence table or logic chart described action, the sequence table
or logic chart block mode changes from AUT to MAN.
When a Ready for Execution Block Receives a PAUS Command

When the block standing-by for execution receives a PAUS command, the block status changes from
STOP to PAUS and the block is paused at the start of the initial step.
When a Ready for Execution Block in SEMI Mode Receives a

RUN Command
When the block ready for execution in SEMI mode receives a RUN command, the operation block
status changes from STOP to RUN and then to PAUS and the operation block is paused at the start
of the initial step.
• Status-change processing takes place for the STOP-RUN status change but does not for the RUN-
PAUS change.
• If post-processing is executed for the STOP-to-RUN change, the RUN-to-PAUS changes takes
place after the post-processing is completed.
• If an interrupt signal is received during the post-processing for the STOP-to-RUN change, the
signal is processed first when the post-processing is completed and then the RUN-to-PAUS
change takes place upon completion of the signal processing.
Pause-Position Actions
When an operation has been designated an execution script as the PAUS position, the action of the
SEBOL step is explained as follows.
“dialogue” Statement Used

When the block has been paused while waiting for input from the operation and monitoring function
after executing a “dialogue” statement, the block is restarted from the line following the “dialogue”
statement unless the operator has not input anything. Since the “time” specified wait time advanced
even while the block is paused, a time-out error is caused if the wait time has been counted up
during the pause.
“delaycycle” and “delay” Statements Used

The time specified to “delaycycle” and “delay” statements advances even while the block is paused.
“wait until” and “compare” Statements Used

The time specified to “wait until” and “compare” statements advances even while the block is
paused. Comparison or condition evaluation is executed at lease once after the block is restarted,
however, even if the specified time has elapsed.
“semlock wait” Statement Used

When the block has been paused while waiting for the unlocking of semaphore, the block is
restarted from the line following the “semlock wait” statement if the semaphore has been unlocked
by another SFC block during the pause. If the semaphore has not been unlocked and is secured, the
state of waiting for the unlocking will be maintained.
“seqtable drivewait” Statement Used

message (%RE) from the sequence table after starting the sequence table using a “seqtable
drivewait” statement, the sequence table block mode remains AUT. The block is restarted from the
line following the “seqtable drivewait” statement if %RE is output from the sequence table during
the pause. If not, the state of waiting for the output will be maintained.
“logicchart drivewait” Statement Used

message (%RE) from the logic chart after starting the logic chart using a “logicchart drivewait”
statement, the logic chart block mode remains AUT. The block is restarted from the line following
the “logicchart drivewait” statement if %RE is output from the logic chart during the pause. If not,
the state of waiting for the output will be maintained.
Identification of Restart Condition

The data returned when the built-in function “ckstep” is executed identifies the condition in which
the operation block has been restarted.
“ckstep” return values are as follows:
• Data returned 1
When operation block is restarted after changing STEPNO in the PAUS mode.
• Data returned 2
When operation block is restarted without changing STEPNO in the PAUS mode.
• Data returned 101
When unit instrument is restarted after changing STEPNO in the PAUSED mode.
When unit instrument is restarted without changing STEPNO in the PAUSED mode.
When unit instrument is restarted without changing STEPNO in the SUSPEND mode.
• Data returned 0
In cases other than listed above.
"ckstep" Returns "2"

"ckstep" returns "2" when the SFC block, for which the PAUS position defined as the start of the step
or the initial step, was paused by a PAUS command and restarted without changing STEPNO.
TIP For the operation block with the PAUS position defined as the stop line, "ckstep" returns the same
data when the block was paused by a PAUS command and restarted without changing STEPNO.
Even after the block has been restarted, "ckstep" returns the same data as that returned before
the pause.

“ckstep” returns “1” when the SFC block was paused, STEPNO has been changed, and then
restarted.
Cases of “0” Returned by “ckstep”

• When the operation is being executed without being paused.
• When the block was paused at the start of a step in the SEMI mode and has been restarted
without changing STEPNO.
• For interrupt signal processing, “0” is returned at all times.
• For status-change pre-processing, “0” is returned at all times.
• For status-change post-processing, “0” is returned at all times.
• For error processing, “0” is returned at all times.
• When the built-in function “ckstepcl” is executed to clear the status following a pause.
• When the action of the restarted step has been completed.
SEE For more information about the changing of data item STEPNO, refer to:
Values Returned by ckstep for an Unit Instrument

When the operation is executed as an operation from the unit, "ckstep" additionally returns the
following values:
• When the unit instrument restarts execution and the operation begins executing after the unit
instrument has been paused and the unit instrument data STEPNO has been changed, "ckstep"
returns "101".
• When the unit restarts execution and the operation resumes executing after the operation BSTS
had changed to PAUS because the unit status changed to the PAUSED, "ckstep" returns "102" if
the PAUS position defined as the start of the step or the initial step. If the PAUS Stop Position is
defined as the current line, "ckstep" returns the same value when the execution restarts as the
one returned prior to the pause.
• When the unit restarts execution and the operation resumes executing after the operation BSTS
had changed to STOP because the unit status changed to the SUSPEND, "ckstep" returns "103".
• When the unit pauses at the top of the steps (of the unit) because the unit is in the SEMI mode,
and the unit restarts execution and the operation resumes executing without changing the unit
instrument data STEPNO, "ckstep" returns "0".
Restarting Actions of an Operation

Actions when an operation block is restarted with its status changed to RUN are described:
Restarting after Paused by SEBOL Scripted Action

The block restarts execution from the PAUS position defined on Function Block Detail Builder.
Execution is restarted from the start of the action when the start of the step is builder-defined, or
resumed from where the action was interrupted when the current line is builder-defined.
If the "initial step" is specified, execution restarts from the initial step.
Restarting after Paused during Sequence Table or Logic Chart-

defined Action
The block restarts execution from the start of the step regardless of the PAUS position defined on
Restarting after Paused during Transition Evaluation

Evaluation is restarted from the leftmost transition condition.
Restarting after Paused during Interrupt Signal Processing

The interrupt signal process is canceled and not resumed when the block is restarted.
Handling of Queued Signals when Restarted

Any signals already queued when the block was paused remain in the queue when the block is
restarted.
Handling of Signal Received during Pause

Any signals received during the pause are queued and available when the block is restarted.
Restarting After Paused during Error Processing

Restarting action varies depending on whether post-processing is executed or not when PAUS was
commanded.
• When post-processing is not executed:
The block is restarted first resuming the interrupted error processing and then resuming the main
program from the builder-defined PAUS position.
• When post-processing is executed:
The ongoing error processing is completed first and then the block status is changed and post-
processed when PAUS is commanded. The block resumes execution of the main program from
the builder-defined PAUS position when restarted.
2.13.3 Referencing Current Step Page 1 of 1
2.13.3 Referencing Current Step

The step number of the step being executed in the operation main program can be referenced.
Procedure
Data item STEPNO can be used to reference the step number of the step being executed in an
operation. As the execution of the main program advances, the step number of the current step is
sent to STEPNO.
TIP Data item PHASE is used to hold the name of the current process in the operation, which can also
be referenced to check the progress of the block execution. When using PHASE, however, every
phase in program steps should be uniquely named.
2.13.4 Changing Current Step Page 1 of 1
2.13.4 Changing Current Step

The following items as to changing the current step are explained in this section.
• Procedure
• Restrictions
• Actions after STEPNO change
Procedure
The number of the current step can be changed by changing the step number set in main program
data item STEPNO when the operation block is PAUS status. The use of STEPNO, however, is only
applicable to main program steps but not to interrupt program steps.
Restrictions
The number of the current step cannot be changed in the following cases:
• When status-change pre- or post-processing is being executed, even if the operation block is in
the PAUS status.
• Step numbers in the operation block cannot be changed, doing so causes error when executed.
Actions after STEPNO Change

Actions following a step number change are as follows:
• No user-defined application program can be executed following a step number change.
• When the block with the PAUS position defined as the current line or the initial step is paused,
the restarting position may be changed to the start of step action by setting the current step
number in STEPNO.
• When the block is paused during transition condition evaluation, the restarting position may be
changed to the start of step action by setting the current step number in STEPNO.
• The current STEPNO data is retained when the block status is changed to STOP.
• The block is restarted from the start of step action when a change to the RUN status is
commanded after STEPNO has been changed.
• The condition in which the block has been restarted can be identified using built-in
function "ckstep."
2.13.5 Operation Alarm Processing Page 1 of 2
2.13.5 Operation Alarm Processing

In an operation, if required, the alarm processing and alarm status-indicating program must be
scripted in SEBOL.
Scripts of Operation Alarm Processing

Unlike regulatory control blocks, an operation block does not have built-in alarm-processing
functions. Thus the alarm processing and alarm status-indicating program must be scripted in SEBOL
when required.
The 4 data items of process alarms applicable to operations are as follows.
• ALRM (alarm status)
• AF (alarm detection specification)
• AOFS (alarm suppression specification)
• AFLS (alarm flashing status)
Data item ALRM identifies the state of occurrence and recovery (normal state) for each alarm. It
indicates NR when there is no alarm or the normal state has been restored. An alarm status
character string can be output using the “prcsalarm” statement when a process alarm occurs in
SEBOL steps. The “prcsalarm recover” statement is used to recover from an alarm state.
SEE For more information about the functions of AF, AOFS, and AFLS, which are the same as other
ALSO function blocks, refer to:
5., “Alarm Processing – FCS” in Function Blocks Overview (IM 33J15A20-01EN)
For more information about the manner of changing and referencing alarm data items, refer to:
5., “Function Block Data” in SEBOL Reference (IM 33J05L20-01EN)
Changing Alarm Status of Operation Block

Data items AF, AOFS, and AFLS of operation block can be changed so that the block’s alarm status
can all be controlled. The following alarm status-change commands can be used:
Table 2.13.5-1 Alarm Status Change Commands
Status-change command
Data item
AOF AON ACK
AF Alarm detection group-bypassing. Alarm group-suppression. -
AOFS Undo group-bypassing. Undo group-suppression. -
AFLS - - Alarm group-acknowledging.
Changing Alarms of Other Operation Blocks

Process alarms of other operation blocks can be controlled by changing data items AF and AOFS.
The operation block with its data item AF externally specified for the group-bypassing of alarm
detection, for example, will not output any process alarm and the alarm status will not be changed
even when the “prcsalarm” statement is executed by the operation block. Also, changing data item
AFLS permits alarm acknowledging while disabling flashing.
Alarm Data Items
2.13.5 Operation Alarm Processing Page 2 of 2
The alarm data items are initialized as follows:

Table 2.13.5-2 Data Item Initialization
Data When initialization When Operation block is Default

Name
item started running setting
ALRM Alarm status NR NR
Alarm detection
AF
specification Previous status
maintained Released
Alarm suppression Previous status maintained
AOFS status
specification
The alarm status is initialized to the normal status (NR) when the operation block is executed. When
the execution of the block is terminated with any process alarm, the normal state will be recovered
when the block is executed again. This is the same when the block mode is changed from O/S to
AUT.
Operation Block Alarm Repeating

If an alarm state is not normalized for a predetermined period of time, repeating alarm defined on
FCS constants builder will be invoked as long as the operation block is being executed or paused.
The repeating alarm will not be initiated for the operation block not being executed or paused, nor if
the execution of the block has been terminated with a process alarm.
Actions related to repeating alarms are the same as other function blocks.
SEE For more information about Repeated Warning Alarm, refer to:
ALSO 5.15.2, “Repeated Warning Alarm” in Function Blocks Overview (IM 33J15A20-01EN)
2.14 Interrupt Processing of Operation Page 1 of 5
2.14 Interrupt Processing of Operation

Operation interrupting processes are explained, in general, below.
Interrupting Processing of Operation

When an operation block status is changed for a pause or abort action, a program may be required
for the processing of the status change. For example, the heater needs to be stopped when aborting
the heating operation, or the valve needs to be closed when pausing a tank charging operation.
The main programs for the ordinary processing can be scripted in the main planes, the interrupting
processes can be put into other planes according to the types of event.
A SEBOL Operation Interrupt Program

An example of the SEBOL operation interrupt program is shown below:
Figure 2.14-1 A SEBOL Operation Interrupt Program
An SFC Operation Interrupt Program

[STOP Processing] and [Emergency Shutdown] are two interrupt programs in an operation, the
extension of the [Emergency Shutdown] interrupt program is shown as follows.
Figure 2.14-2 An SFC Operation Interrupt Program
Although the first step of the interrupt program is shown in a double square in the above example, it
does not mean that the step is the initial step.
Global variables cannot be declared using “global integer” or “global block” for the first step of an
interrupt program. They can be read or written, however.
Interrupt Program Types of Processing

Interrupt programs can be used for the following processing:
• Status change pre-processing
• Status change post-processing
• Interrupt signal processing
The following steps can be used in these interrupt programs as well as the main program:
Table 2.14-1 Steps Applicable to SFC Programs
Program(*1)
Step Main Status change Status change Interrupt signal Error
program pre-processing post-processing processing processing
Initial step x
SEBOL step x x x x
SEBOL one-shot
x x x x x
step
Sequence table
x x x x
step
Sequence table
x x x x x
one-shot step
Logic chart step x x x x
Logic chart one-
x x x x x
shot step
Interrupt step x
*1: x: Applicable
Blank: Not applicable
Note: Transition can be defined for programs other than the status change pre-processing program.
Interrupt Program Parameters

Parameters must be specified according to the type of interrupt processing.
For Status Change Pre-Processing & Post-Processing

One of the following parameters needs to be specified according to which status change instruction
is to be executed:
• RUN
Starts the operation block or restarts the paused operation.
• STOP
Terminates the operation block being executed.
• PAUS
Pauses the operation block being executed.
SEE For more information about Status Change Processing, refer to:
ALSO 2.14.2, "Status Change Processing"
For Interrupt Signal Processing

The name of the signal needs to be specified to execute the interrupt program.
SEE For more information about Interrupt Signal Processing, refer to:
ALSO 2.14.3, "Interrupt Signal Processing"
For Error Processing

No parameter can be specified for error processing.

ALSO 2.14.4, "Error Processing"
Interrupt Processing for Mode or Status Change

The following points should be noted regarding the operation interrupt processing executed for
mode or status changes.
• When unit instrument is given a mode change or a status change command, the operation starts
the interrupt process corresponds to the RUN, STOP or PAUS status.
• When a unit instrument changes its mode or status, for instance, the pre-processes of RUN an
operation will interrupt the unit instrument for mode change from RESTART, AUT to SEMI. In the
case like this, to change more than one mode or status of a unit, the operation only interrupt once.
• To execute interrupt processing separately for each mode/status change command, the built-in
(SEBOL) function “creadpara(0)” can be used in the interrupting program. With this creadpara(0)
command, the mode change and status change command to the unit will be returned.
• When a unit is in SUSPEND status, only the operations in STOP state accept status change
command, the operations in RUN or in PAUSE state do not accept status change command.
Nevertheless, a Monitoring Operation will accept status change command even in RUN or PAUSE
state.
Operation Interrupt Processes

Operation interrupt processings are shown as follows.
Table 2.14-2 Overview of Operation Interrupt Processes
Interrupt Processing CREADPARA-read data Description

"RESTART" Restarting of operation from PAUS.
"" Restarting command from operation SFC view.
RUN pre-processing
"AUT" AUT command received during RUN.
"SEMI" SEMI command received during RUN.
"" Restarting command from operation SFC view.
RUN post-processing "AUT" AUT command received during RUN.
"RUN" When operation started (*1).
"PAUSE" PAUS command received.
"" PAUS command from operation SFC view.
PAUS pre-processing
"AUT" AUT command received during PAUS (*2).
"SEMI" SEMI command received during PAUS (*2).
"PAUSE" PAUS command received.
PAUS post-processing
"" PAUS command received from operation SFC view.
"END" Unit ending command received.
STOP pre-processing "" STOP command received from operation SFC view.
"SUSPEND" Unit procedure suspending command received.
STOP post-processing "" STOP command received from operation SFC view.
*1: Post-processing is executed when operation is started at the start of a step during execution of a unit
procedure. No pre-processing is executed.
*2: Only pre-processing is executed for block mode (AUT, SEMI or stc.) change commands in the PAUS
status. No post-processing is executed.
Monitoring Operation Interrupt Processes

Monitoring operation interrupt processings are shown as follows.
Table 2.14-3 Overview of Monitoring Operation Interrupt Processes
Interrupt Processing CREADPARA-read data Description
"PSTART" Unit started

RUN pre-processing
"AUT" AUT command received during RUN.
"PSTART" Unit started
RUN post-processing "AUT" AUT command received during RUN.
"MSTART" When monitoring-operation started (*1).
"PAUSE" Operation PAUS command received.
"" PAUS command from operation SFC view.
PAUS pre-processing
"AUT" AUT command received during PAUS.
"SEMI" SEMI command received during PAUS.
"PAUSE" Operation PAUS command received.
PAUS post-processing
"" PAUS command received from operation SFC view.
STOP pre-processing "" STOP command received from operation SFC view.
STOP post-processing "" STOP command received from operation SFC view.
*1: Post-processing is executed when monitoring operation is started. No pre-processing is executed.
2.14.1 Queue Signal Processing

Queue signals are processed in the SFC main program.
Signal Declaration
Queue signals to be sent to the operation must be so declared in the initial step using the “queue
signal” statement.
Figure 2.14.1-1 “queue signal” statement.
• The signal is ignored and error is returned to the source if an undeclared signal or any non-
defined interrupt signal is received.
• The “queue signal” statement can be used wherever declaration is allowed in the initial step
(global and local variable declarations).
• The “queue signal” statement cannot be used in steps other than the initial step.
• An error is caused if the same signal name is declared in duplication.
• An error is also caused if the same signal name as an interrupt signal name is declared.
The following is an example of queue signal declaration:
queue signal "SG1,""SG2"
Signal Processing
The operation block fetches the first signal in the queue to process the signal in the main program.
When the operation block in the RUN or PAUS status receives a queue signal, it is stored in the
signal queue. If the block is in a status other than RUN or PAUS, the received signal will be ignored
and an error will be returned to the signal source.
The operation block signal queue may be cancelled as required.
Queue signals are transmitted using the “signal” statement and pending signals can be manipulated
using “qsigcancel” and “qsigmove” statements.
SEE For more information about queue signal transmission and pending signal manipulation, refer to:
ALSO 12., “Signal Processing” in SEBOL Reference (IM 33J05L20-01EN)
Fetching Queue Signals

▼ Maximum Number of Queue Signal Parameters, Maximum Number of Acceptable Queue Signal
Parameters
The first signal in the queue is fetched for processing when the “wait for qsignal” statement (see
below) is executed in an operation block.
Figure 2.14.1-2 Fetching Queue Signals
The maximum number of received signal parameters can be specified in a range of 2 to 8 (2 at

default) for the parameter attached to a queue signal on the Function Block Detail Builder. Any
signal received exceeding the specified number will be ignored, and initiate an error.
The maximum number of signals received in the queue can be specified in a range of 0 to 99 (5 at
default) on the Function Block Detail Builder. No additional signals can be received exceeding the
specified number. Any signal transmitted when the queue is full, an error will be returned to the
signal source.
The signal fetched used “wait for qsignal” statement from the queue and being processed is
included in the count of the specified maximum number of signals. The processed signal will be
dequeued when the next signal is fetched used wait for “qsignal” statement.
Syntax of “wait for qsignal” Statement - Waiting only

This syntax is used to wait until a queue signal is received. If no signal is in the queue when
the “wait for qsignal” statement in this format is executed, the operation waits until a signal is
received while the queue is checked for any received signal once every scan period of the block at
most. As soon as a signal is received and fetched from the queue for processing, the name of the
signal is stored in the specified variable.
TIP • Status change pre-processing or post-processing, or interrupt signal processing will be

executed while the waiting for the receiving of queue signals.
• If time cannot be shared sufficiently for the once-every-scan-period check for received signals,
the check will be made no more than once every few scan periods.
Syntax of “wait for qsignal” Statement - Waiting and Testing

Conditions
This syntax is used to wait until a queue signal is received or the condition specified by the
expression is satisfied.
The expression is first calculated when the “wait for qsignal” statement in this format is executed. If
the result is true (other than 0), the condition is satisfied and the statement is closed. If the result is
false (0), the presence of signals in the queue is checked.
When the statement is closed with the condition satisfied, a null-length character string (“”) is stored
in the signal name-storing variable. When a signal has been fetched from the queue, the name of
the signal is stored in the variable. When the result of the expression is false and no signal is in the
queue, both the expression and the queue will be checked once every scan period of the block at
most.
<label> can be used to specify the destination for branching when error is caused. If “error”
or “errorsub” is not used, execution is resumed from the next statement when error is detected.
Specifying <error identifier> permits to identify the error-caused location in the error handling
phase, which provides the identifier value using a built-in function.
TIP It is recommended to use just one “wait for qsignal” statement, in either one of the two formats,
in the SFC block, and program so that execution returns to the statement for successive signal
processing upon completion of the current signal processing.
SEE For more information about error processing, refer to:

Fetching Signal Parameters

Upon completion of the “wait for qsignal” statement with a signal fetched from the queue, the
parameter and name of that signal can be read.
Built-in function “creadpara,” “lreadpara,” or “dreadpara” can be used to read the signal parameter;
and built-in function “creadpara” can be used to read the signal name.
Figure 2.14.1-3 Fetching Signal Parameters

a long double-precision floating-point real-number function, and they can be used to read character-
Running any of these built-in functions after the expressed condition in the “wait for qsignal”
statement with waiting and testing condition options has been established will cause error when
executed.
Examples of Queue Signal Processing

Examples of queue signal processing using the syntax of the “wait for qsignal” statement are shown
below.
Waiting for Signal

An example of executing the “wait for qsignal” statement with Waiting for Signal Syntax.
Figure 2.14.1-4 Example of Queue Signal Processing Using Waiting for Signal Syntax
The “wait for qsignal” statement is executed in step 2 and a signal is fetched from the queue. The
signal name is then evaluated according to the transition condition defined following step 2,
selecting either SG1 or SG2 for processing.
Waiting for Signal or Testing Condition

An example of executing the “wait for qsignal” statement with Waiting for Signal and Testing
Condition Syntax.
Figure 2.14.1-5 Example of Queue Signal Processing Using Waiting for Signal and Testing
Condition Syntax
The “wait for qsignal” statement is executed in step 2, determining to wait for a signal or to
calculate the expression. The result of the expression is checked for the first transition condition
defined following Step 2. Either SG1 or SG2 is selected for processing according to the other two
transition conditions.
Referencing
▼ Reference Signal Parameter Numbers

Either the signal name or the signal parameter of the queued signal can be set to operation’s data
item QUEUE[ ] as one element. All queued elements can be accessed by SEBOL as CHR16 character-
strings.
The data of the signal being processed can not be put into QUEUE[ ], only the data waiting for
processing can be put into QUEUE[ ] data item.
Example of Referencing
When the queue has four signals, for example, referencing can be made as described below:
Figure 2.14.1-6 Queue Holding Four Signals
If the reference signal parameter number is 1, the contents of QUEUE elements are as follows:
Queue[1] = "SUMMER"
Queue[2] = "AUTUMN"
Queue[3] = "WINTER"
Queue[4] = "SPRING"
Queue[5] = " "
.....
Queue[10] = " "
QUEUE[5] to QUEUE[10] are zero-length character strings since there is no data.
2.14.2 Status Change Processing

There are following two types of the interrupt processes executed with a block status change
command:
• Status-change pre-processing
• Status-change post-processing
Processing Flow Operation

The flow of processing when an operation block receives a status change command is shown below:
Figure 2.14.2-1 Flow of Status Change Process
As the operation block receives a status change command, the feasibility of the commanded change
and the interrupt processes are checked in relation to the current status. The conditions for block
status changes are shown below:
Table 2.14.2-1 Feasibility of Block Status Change
Status commanded for change(*1)

Current status
STOP RUN PAUS RSET ABRT
STOP (*2) xx xx
RUN xx (*2) xx x
PAUS xx xx (*2) x
ABRT x (*2)
*1: xx: Status change feasible. Both pre- & post-processes executable.
x: Status change feasible, but pre- & post-processes not executable.
Blank: Status change not feasible.
*2: Command ignored.
Feasibility Checking
When an operation block current status is STOP and receives a command to change to RUN or PAUS
status, it will start a pre-process to interrupt the main program. If the block receives a command to
change to RSET, ABRT, or STOP status when current status is STOP, an error will occur. A change
command RSET is accepted only when the current status is ABRT.
A change command ABRT can be accepted when the current status is RUN or PAUS. When the
operation block receives ABRT command, the operation block will be forcibly terminated and the
status will change to ABRT.
The command to change the status to ABRT is a command to forcibly

terminate the operation block and should not be used during normal operation.
The ABRT command is different from other status change commands, the
differences are as follows.
• Pre- and post-processing cannot be defined for the command.
• The command can be received even when another status change
command post-processing is running.
Pre-Processing
The feasibility of status change is determined in the pre-process. If the change is denied, the source
of the command is notified of the error. The status is changed as commanded if the pre-process is
not defined.
Status Changing
▼ Notification message for status change of batch operations
The status of an operation block is changed as commanded when the change is justified both in the
initial check in relation to the current status and the check performed in pre-processing. If the
[Status Change Message Bypass] option is set to “NO” on the Function Block Detail Builder,
messages are generated as follows:
If the [Notification message for status change of batch operations] option is set to “YES” on the FCS
Constants Builder, a block status change information message (No. = 1405) is generated at any of
the following BSTS (block status) changes:
• BSTS is changed on the faceplate of an operation block.
• BSTS is changed from a unit instrument.
• BSTS change that occurs at the end of a batch operation.
If the [Notification message for status change of batch operations] option is set to “NO” on the FCS
Constants Builder, a block status change information message (No. = 1405) is only generated when
BSTS (block status) is changed on the faceplate of an operation block.
Post-Processing
Status-change post-processing is executed in accordance with the execution of the operation block
itself, not with the receiving of the status change command.
The status change is prohibited when the current post-process is running; the received status
change command will be treated as an error and ignored.
Status Change Pre-Process - Operation

The status-change pre-process is one-shot-executed upon receipt of the status change command
before changing the block status. There are three types of scripts for status-change pre-process.
• Sequence table one-shot execution step (Sequence table one-shot)
• Logic chart one-shot execution step (Logic chart one-shot)
Since the status-change pre-process is one-shot-executed, it must be completed as quickly as
possible. Do not access data of another control station and delay the process. Only one step can be
executed as pre-process, where no transition condition can be defined.
Figure 2.14.2-2 Status-Change Pre-Process
At the SEBOL and sequence table one-shot steps, the feasibility of status change can be determined.
With the logic chart one-shot step, the status can be changed. If the pre-process is not defined, the
status can also be changed. At the pre-process, the status and mode of the pre-process-described
operation block or other operation blocks cannot be changed.
Pre-Processing Using SEBOL Oneshot Step

The SEBOL oneshot step will be completed when the last line, or “return” or “quit” statement is
executed.
If the last line or “quit” statement is executed, the feasibility of status change will be tested. If
the “return” statement is executed, the feasibility of status change will be determined according to
the returned value as follows:
Figure 2.14.2-3 Status-Change Permission
The SEBOL oneshot step in which the pre-process is defined has the following additional restrictions
over the normal steps:
• “exit” statement cannot be used. Error occurs if used.
• “signal” statement cannot be used. Error occurs if used.
• “qsigcancel” and “qsigmove” statements cannot be used. Error occurs if used.
• “isigmask” and “isigunmask” statements cannot be used. Error occurs if used.
• “semlock”: and “semunlock” statements cannot be used. Error occurs if used.
• In the case of fatal error, only a SEBOL error message is output and the operation block is not
terminated. Any status change will be denied.
• When an execution error is detected, no branching is made to common error processing and a
SEBOL error message is output. Any status change will be denied.
• The block status and mode of the present operation block or any other operation block cannot be
changed.
Pre-Processing Using Sequence Table One-Shot Step

With the sequence table one-shot step, the status can be changed. The block status and mode
cannot be changed in pre-processing for the SFC block in which the pre-process is defined or for any
other SFC block.
Pre-Processing Using Logic Chart One-Shot Step

With the logic chart one-shot step, the status can be changed. At the pre-processing, the status of
the pre-process-described operation block or other operation blocks cannot be changed.
Status Change Post-Process - Operation

The status-change post-process will be executed after the status is changed. The process is
executed as an interrupt signal processing, interrupting the main program in accordance with the
basic scan period of the operation block.
Both step and selective sequences can be used in the post-process. A status change command is
prohibited when the current post-process is not completed; the command will be ignored if received,
causing error.
The post-process should not be kept suspended by means of a selective

sequence transition condition, or a “wait until,” “compare,” or “dialogue”
statement. If the process is suspended, the block status cannot then be
changed unless the program is forcibly terminated using a command to
change to ABRT.
The execution of the post-process defined in a SEBOL step can be controlled using “quit”
Executing this statement in a step sequence terminates the current action and executes the next
step. Executing it in a selective sequence starts evaluation of transition conditions.
Executing the statement in the last post-process step terminates the process.
Executing this statement terminates the post-process without executing the remaining steps. Any
Referencing Block Status - Operation

Data item PREBSTS (previous block status) is used in the post-process to permit referencing the
block status before the change. When the status is changed, data item BSTS (block status) which
contains information on the status before the change is copied to PREBSTS. These two data items
are operated as follows:
1. The BSTS data is copied to PREBSTS.
2. BSTS is changed to the new block status.
The BSTS data is referenced for testing the feasibility of block status change in the pre-process. The
PREBSTS data is also referenced in the post-process. Referencing BSTS and PREBSTS take place in
the following timings:
• When the current status of RUN is changed to STOP by a commanded.
• When the current status of PAUS is changed to STOP by a commanded.
Table 2.14.2-2 BSTS & PREBSTS
RUN → STOP PAUS → STOP

Process being executed
BSTS PREBSTS BSTS PREBSTS
Status-change pre-process RUN (*1) PAUS (*1)
Status-change post-process STOP RUN STOP PAUS
*1: Previous status.
Operation Block Status Referencing in Pre-Process

An example of referencing the block status in the pre-process. The two different scripts are based
on the current status of the operation block.
switch (%.BSTS)
case "RUN":
!Process changing from RUN to STOP.
case "PAUS"
!Process changing from PAUS to STOP.
end switch
Operation Block Status Referencing in Post-Process

An example of referencing the block status in the post-process. The two different scripts are based
on the current status of the operation block.
switch (%.PREBSTS)
case "RUN"
!Process when changed from RUN to STOP.
case "PAUS"
!Process when changed from PAUS to STOP.
end switch
Changing Status of the Unit Instrument

When the status (data item BSTS) of the unit instrument is changed, the operation can perform
status-change pre- and post- processing. The status-change pre- and post- processing is created as
an interrupt program.
SEE For more information about the execution timing of the operation status-change pre- and post-
ALSO processing and the rules for changing block status of an operation when the status of the unit
instrument changes, refer to:
2.6, "State Transition Matrix"
"independent" Statement
The monitoring operation is a special operation for monitoring the unit instrument. Use
the "independent" statement to make the monitoring operation continue to execute even when the
unit instrument stops or pauses.
The "independent" statement can be scripted anywhere so long as it is a place where a declare
statement for the initial step can be written in the operation. The action of an operation using
the "independent" statement is as follows:
• An operation that uses "independent" statement executes status-change pre- and post-
processing.
• The block status of an operation that uses "independent" statement does not change.
For example, actions that occur when PAUS is specified in the action instruction for the unit
instrument are shown in the table below.
Table 2.14.2-3 Difference of Operation (PAUS) by Presence/Absence of "independent"
Specification
Pre-processing for Post-processing for Execution

independent BETS
status change status change status
Executes PAUS pre- Executes PAUS post-
Used No change No change
processing processing
Executes PAUS pre- Executes PAUS post- Changed to
Not used PAUS
processing processing PAUS
For example, actions that occur when RSM is specified in the operation instruction for the unit
instrument are shown in the table below.
Table 2.14.2-4 Difference of Operation (RSM) by Presence/Absence of "independent"
Specification
Pre-processing for Post-processing for Execution

independent BETS
status change status change status
Executes RUN pre- Executes RUN post-
Used No change No change
processing processing
Executes RUN pre- Executes RUN post- Changed to Restarts
Not used
processing processing RUN execution
Even if a STOP change command is output to an operation (via the unit instrument) with
the "independent" specification, the operation does not stop and the block status remains
unchanged. Only the STOP status-change pre-process and post-process are executed. Similarly,
even if a PAUS change command is output to an operation (via the unit instrument) with
the "independent" specification, the operation does not pause and the block status remains
unchanged. Only the PAUS status-change pre-process and post-process are executed.
Unless the status change command of an operation including the monitoring operation goes through
the unit instrument, the change command will not be output.
To force the termination of an operation with the "independent" specification, output an ABRT
change command to the operation. If the MSTART change command is output to the unit
instrument, the monitoring operation that was forcibly terminated can be restarted.
The following precautions are necessary when using an "independent" statement in other than the
monitoring operation:
• The unit instrument can be stopped even when an operation with the "independent" specification
is being executed.
The unit instrument stops without waiting for the execution of the independent operation to
complete.
• To stop the unit instrument immediately, terminate the execution by using an "exit" statement in
the status-change post-process of the independent operation.
• If the transition condition is scripted with (/) for parallel operations, and the parallel operations
contain the independent operations, consequently, when one operation is completed, other
operations may continue running.
TIP The unit instrument can be stopped even when the monitoring operation has an "independent"
specification and is being executed.
“ckstep” Statement
The built-in function ckstep may be applied to check if the operation block is restarted after the
block is paused.
SEE For more information about the return value of the built-in function "ckstep()" when the operation
ALSO block is executed, refer to:
" Identification of Restart Condition" in 2.13.2, "Pause an Operation"
“creadpara” Statement
In an operation, when “creadpara” is executed by specifying “0” in the argument of the status-
change pre-process or post-process for RUN, PAUS or STOP, the mode/status change command for
the unit instrument can be acquired.
!Step scripted in SEBOL for operation block
char*8 stscmd
stscmd = "creadpara" (0) !Acquire a status change command for the unit instrument
.....
When manually change an operation block status, if “creadpara” is executed by specifying “0” in the
argument for the status-change pre-process or post-process, it returns a “” (a character string of
length 0).
2.14.3 Interrupt Signal Processing

Interrupt signal processing is executed interrupting the main program when an interrupt signal is
received.
Interrupt Signals
Interrupt signals are sent from the operation block, sequence table and logic chart. Every interrupt
signal can be named using a character string of up to 8 bytes and attached with up to 8 parameters.
Whether a signal is taken as a queue signal or an interrupt signal depends on the definition in the
operation block which receives the signal and cannot be specified at the signal source.
Queue and interrupt signals are distinguished as follows:
• Signals defined in the initial step using the “queue signal” statement are handled as queue signals.
• Signals having their names written at the entrance of interrupt signal processing are handled as
interrupt signals.
If the same name is used both in the initial-step definition and at the interrupt-signal entrance, an
error will occur.
Interrupt signals can be received only when the operation block is in the RUN or PAUS status, any
signal transmitted is ignored otherwise and an error is returned to the source.
Interrupt signals received during the course of the PAUS status are stored in a queue and will be
processed when the status is changed to RUN for restarting the block.
Interrupt Signal Processing

▼ Maximum Number of Receive Interrupt Signals
Interrupt signals are processed interrupting the main program, which resumes execution as soon as
the signal has been processed.
Figure 2.14.3-1 Interrupt Signal Processing
Interrupt signals can be processed only when the operation block is in the RUN status. The signal
processing is canceled if the status is changed to PAUS during the processing and will not be
resumed when the status is returned to RUN.
If another interrupt signal is received while one is being processed, the received signal is queued
and will be processed as soon as the current processing is completed. The maximum number of
interrupt signals which can be queued can be defined for each operation block using the Function
Block Detail Builder. The number is 5 at default and can be defined up to 99. The defined capacity
includes the signal currently being processed. If a signal is received when the queue is full, the
signal is ignored causing an error.
The execution of the interrupt signal process defined in a SEBOL step can be controlled using “quit”

Executing this statement terminates the current step action and executes the next step.
Executing it in a selective sequence starts evaluation of transition conditions.
Executing the statement in the last step of interrupt signal processing terminates the process.
Executing this statement terminates the process without executing the remaining steps. Any
Fetching Interrupt Signal Parameters

▼ Maximum Number of Interrupt Signal Parameters
Queue signal parameters can be fetched using built-in functions during interrupt signal processing.
Figure 2.14.3-2 Fetching Interrupt Signal Parameters

a long double-precision floating-point real-number function, and they are used to fetch character-
The maximum number of signals can be defined in a range of 2 to 8 (2 at default) for the parameter
attached to an interrupt signal. If the operation block receives an interrupt signal exceeding its
parameter setting, the signal is ignored causing an error.
2.14.4 Error Processing Page 1 of 1
2.14.4 Error Processing

Error processing needs to be defined in an SFC other than the main program. Only one set of
processing can be scripted in one operation.
Error Processing Description

Similar to other interrupt processes, error processing needs to be defined in an SFC separately from
the operation of the main program. Only one set of processing can be described in one operation.
Both step and selective sequences can be used in error processing. It is necessary for a selective
sequence, however, that the transition conditions are so defined that they can be easily satisfied;
the process being executed when error is caused will not be resumed otherwise.
The execution of the error processing defined in a SEBOL step can be controlled using “quit”
Executing this statement in a step sequence terminates the current step action and executes the
next step. Executing it in a selective sequence starts evaluation of transition conditions.
Executing the statement in the last error processing step terminates the process.
Executing this statement can terminate error processing without executing the remaining steps.
Any operand specified in this statement will be ignored.
SEE For more information about common error processing, refer to:
2.15 Initialization Operation and Monitoring Operation Page 1 of 2
2.15 Initialization Operation and Monitoring

Operation
Initialization and monitoring operations can be executed in a unit instrument in addition to other
operations started from the unit procedure.
Figure 2.15-1 Initialization Operation and Monitoring Operation
Initialization Operation
▼ Initialize Operation
The initialization operation is applied to carry out the process initialization for a unit instrument to
run its procedure. The operation designated as the initialization operation will be definitely started at
the beginning of the system start or right after the unit instrument complete its unit procedure.
When a unit instrument is running the initialization operation, it does not accept mode change or
status change command until the initialization is completed.
There is one exception, the command for changing to O/S mode will be accepted even when the
initialization operation is running. When the O/S command is received, the initialization operation will
be immediately terminated. When the O/S mode is canceled, the block mode returns to its previous
mode first then changes to END status, thus the initialization operation will then be started again.
The interrupt processing for mode and status changes can not interrupt the initialization operation.
The initialization operation’s name may be defined on the Function Block Detail Builder for the unit
instrument. It is required to put the initialization operation in the same drawing with the unit
instrument.
Monitoring Operation
2.15 Initialization Operation and Monitoring Operation Page 2 of 2
▼ Monitoring Operation
A monitoring operation is the operation applied for monitoring the unit instrument especially when
the equipment entity is required to be monitored even when the unit procedure is not running.
The monitoring operation is started when the system starts. It is different from the initialization
operation, a unit instrument can only start the monitoring operation but does not care for its stop.
When the monitoring operation is stopped for some reason, it may be restarted by sending a
MSTART status-change command from the unit instrument.
When a block mode or status change command is sent to the unit instrument, the monitoring
operation will be notified to advance to the state in accordance with the state transition matrix. The
interrupt processing for mode and status change will interrupt the monitoring operation.
The monitoring operation’s name may be defined on the function block detail builder for the unit
instrument. Each unit instrument may have two monitoring operations. It is required to put the
monitoring operations in the same drawing with the unit instrument.
Continuous Execution of Monitoring Operation

with “independent” Statement
When a unit block mode or status change command is given to the monitoring operation, the
monitoring operation may be paused or stopped in accordance with the state transition matrix same
as other operations.
To avoid this and keep the monitoring operation continuously executed, describe the “independent”
statement, which is a SEBOL declaration statement, in the first step of the monitoring operation.
An operation with “independent” statement may only be aborted when the unit instrument send a
command (ABRT) for changing to O/S state. When recovered from O/S state, the monitoring
operation will be restarted.
To terminate the “independent”-specified monitoring operation, declare termination of the program
using the “exit” statement. To specify the termination of the operation when it is notified of the
ABRT command, describe the “exit” statement at the end of the interrupt processing for the
command.
2.16 Unit Operation Instrument under Batch Management Page 1 of 3
2.16 Unit Operation Instrument under Batch

Management
The unit operation instrument is a collection of procedures called up by the unit instrument and
executes operations in order.
Procedures handled by the unit operation instrument conform to ISA-88 procedure model operation
procedures.
The unit operation instrument may be applied together with Batch Management.
Figure 2.16-1 Unit Operation Instrument Called Up by the Unit Instrument
SEE For more information about Batch Management, refer to:

ALSO 4.1, “Nonresident Unit Instrument” in Batch Management System Reference (IM 33J05L10-
01EN)
Outline of Unit Operation Instrument

The unit operation instrument consists of unit operation instrument data items and recipe operation
procedures.
The data items of a unit operation instrument are mainly for tuning parameters and monitoring the
process.
The recipe operation procedure is created by Recipe Management, indicates the manufacturing
procedure following a set of pre-configured physical or chemical changes, and controls an ordered
set of operations.
The unit operation instrument is a non-resident instrument that does not have procedures resident.
When downloading unit recipes, recipe procedures are downloaded to the FCS. The unit operation
instrument is used when the recipe unit procedure of the unit instrument is to be created by splitting
it into a more detailed hierarchical structure processes.
Unit Operation Instrument Block Models
The unit operation instrument uses the following function block model name.
• UTOP-SN (non-resident unit operation function instrument)
Unit Operation Instrument Elements

A unit operation instrument is constructed with the following elements.
Recipe Operation Procedure

The unit operation instrument starts operations in succession.
The recipe operation procedure is formed in an SFC. The name or generic name of an operation can
be registered as a step action in the SFC.
Operation
The operation for initialization and the operation for monitoring cannot be started from the unit
operation instrument.
Other operations are the same as operations used by the unit instrument.
Operations started from a unit operation instrument can access the data of the calling unit
instrument by using the "%%.DataItemName" format.
SEE For more information about operations, refer to:

ALSO 2.8, "Operations"
Unit Operation Mode and Unit Operation Status

Like other function blocks, a unit operation instrument also has mode and status. The mode and
status of a unit operation instrument are referred to as unit operation mode and unit operation
status respectively.
The unit operation mode includes AUT, SEMI etc. and indicates the control mode of the unit
The unit operation status includes END, ABORTED etc. and indicates the operation state of the unit

When the unit operation instrument receives a mode change command or status change command,
the unit operation instrument changes its mode and status to the requested mode and status.
When a change command is received, the unit operation instrument refers to the state transition
matrix to check if it is allowed to change from the current mode and status to the requested mode
and status of the change command.
The unit operation instrument uses the state transition matrix specified for the calling unit
instrument.
The built-in action of the unit operation instrument is as follows.
When the unit operation instrument receives a mode change command from the unit instrument, it
refers to the "action instruction for unit instrument or operation" of the state transition matrix.
For example, when the unit operation instrument receives a mode change command, and
the "action instruction for unit instrument or operation" of the state transition matrix is CONT, the
unit operation instrument will continue to use the current mode.
SEE For more information about state transition matrix, refer to:
For more information about the mode and status change commands, refer to:
2.16.6, "Unit Operation Instrument Mode and Status Change Command"
Message
There are following types of messages related to the unit operation instrument. Just like other
function blocks, the unit operation instrument related messages are also stored in the historical
message save file in HIS.
• Unit operation mode / status change messages
• System alarm messages
2.16.1 Unit Operation Instrument Data Items Page 1 of 1
2.16.1 Unit Operation Instrument Data Items

Unit operation instrument data items are used to control execution of unit operation instruments. Unit
operation instrument data items do not have any user specified data items.
Data Items of Unit Operation Instrument

Unit operation instruments only have system-fixed data items.
The specifications of data item names, data names and data types are shown below:
Table 2.16.1-1 Unit Operation Instrument Data Items

Data name Default Remarks
name type (*1)
MODE Unit operation mode CHAR*8 x AUT
BETS Unit operation status CHAR*8 x END
SUBS Unit operation sub-status CHAR*8
RUNS Unit operation control status CHAR*8
AFLS Alarm flashing U32
AOFS Alarm suppression specification U32
AF Alarm detection specification U32
ERRL Error-caused step number U32 0
STEPNO SFC step number I16 0
UAID User APID I16 x
SUAID Self-user reserved I16 x 0
Unit operation mode (lowest
OMOD CHAR*4
priority)
Unit operation mode (highest
CMOD CHAR*4
priority)
DILG Dialog acknowledgment U32
PREMODE Previous unit operation mode U32 AUT
PREBSTS Previous unit operation status U32 END
STARTIME Execution start date & time U32
ENDTIME Execution end date & time U32
For Process
Management
For Process
Management
For Process
RECIPE Recipe name CHAR*16
Management
For Process
PARTNO Unit recipe number I16 0
Management
UNITNAME Unit name CHAR*16
2.16.2 Accessing Unit Operation Instrument Data Items Page 1 of 1
2.16.2 Accessing Unit Operation Instrument Data Items

Unit operation instrument data items can be accessed from other function blocks or faceplate blocks
for referencing or setting.
Accessing from Function Blocks Other Than SFC Blocks

Access from function blocks other than SFC blocks is possible with data connection or sequence
connection.
Accessing from Sequence Table Blocks

This access can be specified as the connection destination of the sequence connection in the
condition or operation column of the sequence table block.
Accessing from Logic Chart Blocks

This access can be specified as the connection destination of the sequence connection in the
condition symbol or operation symbol of the logic chart block.
Accessing from General-Purpose Calculation Blocks

(CALCU, CALCU-C)
This access can be specified as a variable in the format of "TagName.DataItem" in the CALCU and
CALCU-C calculation blocks.
Accessing from SFC Blocks

Access is possible from the SFC block SEBOL program.
2.16.3 Unit Operation Mode Page 1 of 1
2.16.3 Unit Operation Mode

The unit operation mode indicates the control mode of the unit operation instrument. When a
command for changing the unit operation instrument mode is given, the behaviors of the recipe
operation procedure and operation may be changed.
Type of Unit Operation Mode

There are the following types of unit operation modes. Unit operation modes are system-fixed.
Out-of-Service (O/S) Mode

This unit operation mode completely stops execution of the unit operation instrument.
Transition to O/S mode is possible only when the unit operation is in the completed (END) or
aborted (ABRT) status. The other unit operation statuses may cause errors.
Transition to the O/S mode completely stops unit operation instrument execution for the purpose of
the maintenance, etc.
Manual (MAN) Mode

The recipe operation procedure cannot be run in this mode.
Semi-Automatic (SEMI) Mode

The operation of each recipe operation procedure is automatically executed in this mode but always
paused in unit operation mode before moving to the next step. In semi-automatic mode, movement
between steps is executed manually.
Automatic (AUT) Mode

The operations of all recipe operation procedure steps are automatically transited in this unit
operation mode. It indicating the unit is in automatic unit execution.
2.16.4 Unit Operation Status Page 1 of 1
2.16.4 Unit Operation Status

The unit operation status indicates the running state of a unit operation instrument (running state of
a recipe operation procedure).
Default Unit Operation Status

There are following types of default unit operation status.
END
Execution of recipe operation procedure completed.
ABORTED
Recipe operation procedure is aborted.
RUNNING
Recipe operation procedure being executed.
SUSPEND
Recipe operation procedure suspended at the running step or at the start of a step.
PAUSED
Execution of operation paused at the start of a phase.
2.16.5 Unit Operation Sub-Status Page 1 of 1
2.16.5 Unit Operation Sub-Status

Unit operation sub-status is provided to indicate more detailed running state under each unit
operation status.
Type of Unit Operation Sub-Status

Unit operation sub-status is an auxiliary information to indicate more detailed running state under a
unit operation status. Unit operation sub-status is system-fixed.
The relationship between unit operation status and unit operation sub-status is shown below.
Table 2.16.5-1 Relationship between Unit Operation Status and Unit Operation Sub-Status
Unit operation status Unit operation sub-status Description

NOCNCT Status with no recipe operation procedure available
END
USER User-aborted state.
ABORTED
SYSTEM System-aborted state.
RUNNING INTR Interrupt processing being executed.
SUSPEND
CKTR Transition condition being evaluated.
PAUSED INTR Interrupt processing being executed.
2.16.6 Unit Operation Instrument Mode and Status Change Command Page 1 of 3
2.16.6 Unit Operation Instrument Mode and Status

Change Command
The unit operation instrument can receive operation commands from the operation and monitoring
consoles, sequence table or logic chart, and units and actions such as emergency stop caused by
equipment failure, as a mode change command or status change command.
Figure 2.16.6-1 Change Commands Received by Unit Operation Instrument
Mode Change Commands

These commands change the unit operation mode. The mode change commands are system-fixed.
The mode change commands are described below.
AUT
Transition to the automatic mode.
SEMI
Transition to the semi-automatic mode.
MAN
Transition to the manual mode.
O/S
Transition to the out-of-service mode.
Status Change Commands

Status change command is a command to change the unit operation status.
Available unit status change commands are described below:
Table 2.16.6-1 Status Change Commands of the Unit Operation Instrument
Status
Execution
change Command Description
level
command
Restart
RESTART command Restarts suspended/paused unit procedure. Low

END End command Terminates recipe operation procedure execution. Low
Abort
ABORT Forcibly terminates unit operation instrument execution. High
command
Suspend
SUSPEND Suspends execution of recipe operation procedure. Low
command
Pause Pauses execution of recipe operation procedure operation
PAUSE Low
command phase.
Reset
RESET Resets aborted status. Low
command
Stops execution at the start of next step in SEMI mode.
Specifying a pause during the state transition by this
Step end change command can pause execution at the start of the
SCOMP (*1) Low
command step.
(Unit Operation Status interrupt processing cannot be
described).
Changes steps when the unit operation instrument is
Step change stopped.
STEP (*1) Low
command (Unit Operation Status interrupt processing cannot be
described).
Stops execution at the start of step when error is caused
during operation.
Execution error
EXECERR (*1) Specifying a pause during the state transition by this High
command
change command can pause execution at the start of the
step when an error is caused during operation.
*1: SCOMP, STEP, and EXECERR commands are system-initiated (see below), user cannot issue the
commands.
The system-initiated SCOMP, STEP, and EXECERR commands are described below:
SCOMP Change Command

command.
The SCOMP change command is a change command that creates a pause between steps when the
mode is semi-automatic (SEMI).
When the unit operation mode is in semi-automatic (SEMI), the system issues an SCOMP change
command each time an SFC step of the recipe operation procedure and the transition in connection
with that step have been executed. When an SCOMP change command is issued, the unit operation
instrument pauses execution at the start of the next step according to the status transition matrix.
STEP Change Command

When performing batch stepping of recipe operation procedure SFC, a step change is executed by
setting the step number of the stepping target in the STEPNO data item and instructing a STEP
change. When a STEP change command is received, the unit operation instrument executes the
process stepping according to the status transition matrix.
EXECERR Change Command

command.
When the recipe operation procedure starts an operation, there are times when the operation is in
the middle of maintenance or being started by another recipe operation procedure. In this case, the
EXECERR change command is issued. When the EXECERR change command is received, the unit
operation enters the pause state according to the status transition matrix.
SUSPEND Stop Position

▼ SUSPEND Stop Position
The "SUSPEND Stop Position" defined on the unit operation instrument Function Block Detail Builder
specifies the stop position with SUSPEND. The following can be defined as the stop position.
• Running step
• Initial step
When restarting execution from SUSPEND, it will restart from the stop position.
2.16.7 Message Page 1 of 1
2.16.7 Message
There are following types of messages related to the unit operation instrument. Just like other
function blocks, the unit operation instrument related messages are also stored in the historical
message save file in HIS.
Unit Operation Mode Change Messages

A message is output when the unit operation mode is changed.
Unit Operation Status Change Messages

A message is output when unit operation status is changed.
System Alarm Messages

System-fixed alarms are output when error is caused in the action of the unit operation instrument.
System-fixed alarms generated by the unit operation instrument are as follows.
• Errors caused during execution of unit operation instruments
• Errors caused during execution of operations.
• Errors caused during execution of commands from Process Management.
SEE For more information about the output format of each message, refer to:
ALSO 2., “Message Output Details” in Operating Messages (IM 33J05A30-01EN)
3. Valve Pattern Monitors Page 1 of 4
3. Valve Pattern Monitors

The valve pattern monitor is a function block which runs in an FCS (Field Control Station). One valve
pattern monitor can simultaneously monitor a maximum of 512 valves in a transfer-system plant.
This valve pattern monitor is controlled by a user created application program as the operation of a
unit.
Position of Valve Pattern Monitor

The valve pattern monitor is one of the functions runs in FCS.
This valve pattern monitor is controlled by the user application represents a operation scripted in
SEBOL statements (i.e. an SFC block initiated from a “Unit” in the unit supervision function).
Placement of Valve Pattern Monitor is shown as follows.
Figure 3-1 Position of Valve Pattern Monitor
SEE For more information about the unit supervision function, refer to:
Function of Valve Pattern Monitor
Simultaneous Monitoring of Multiple Valves

The valve pattern monitor is a function block for monitoring the valve opening/closing state in a
transfer-system plant. One valve pattern monitor can simultaneously monitor a maximum of 512
valves in a transfer-system plant.
The valves to be monitored are registered in the valve pattern monitor under operation of a unit.
SEBOL statements specific to the valve pattern monitor are used to register the valves to be
monitored.
Abnormality Signal
The valve pattern monitor returns an alarm signal to the unit upon detection of a valve abnormality.
If such a signal is received, the unit performs alarm processing.
Prior to using the valve pattern monitor, create the alarm process program for abnormality
detection, and incorporate it in the operation of the unit.
The following figure shows the configuration of a valve monitoring system which uses the valve
pattern monitor.
Figure 3-2 Example Configuration of Valve Monitoring System
Run Screen Display: Tuning View

The following figure shows the Tuning view of the valve pattern monitor. This view displays valve
pattern monitor run statuses such as the block mode, alarm status, and block status.
Figure 3-3 Tuning View of Valve Pattern Monitor
SEBOL Statements Specific to Valve Pattern Monitor

There are six SEBOL statements specific to the valve pattern monitor. These statements are used for
creating application programs.
vpmstart Statement
This statement secures the specified valve pattern monitor and makes it available.
drive vpmon Statement

This statement checks the valve to be monitored for output operation, then registers the object
valve in the valve pattern monitor.
If the drive vpmon statement is executed, it modifies the output status of the function block (motor
control block or switch instrument block) to be operated by this statement, and it checks the valve
for proper operation using the answer-back check of the function block. Then, the valve to be
monitored and the data will be registered in the valve pattern monitor.
drive vpmoff Statement

This statement deletes registration of the object valve and data, and then it checks the output
operation of the valve.
If the drive vpmoff statement is executed, it deletes registration of the object valve and data, and
then it sets the data for modifying the output status in the function block which operates the valve
deleted from the valve pattern monitor.
vpmon Statement
This statement registers the object valve and data in the valve pattern monitor. It does not perform
output operation of the valve, which is different from the drive vpmon statement. Normally, vpmon
statement is used after the output action of the valves under the monitoring of drive statement.
vpmoff Statement
This statement deletes registration of the object valve and data from the valve pattern monitor. It
does not perform output operation of the valve, which is different from the drive vpmoff statement.
vpmreset Statement
This statement deletes all of the object valves and data registered in the valve pattern monitor.
TIP If the drive vpmoff statement or the vpmoff statement is used, monitoring of any one of the
valves can be stopped (i.e. any object valve that has been registered in the valve pattern monitor
can be deleted).
Also, the valve pattern monitor can be paused and resumed by modifying the block status of the
valve pattern monitor.
SEE For more information about the above SEBOL statements, refer to:
ALSO 3.8, "SEBOL Statements for Valve Pattern Monitor"
For more information about the block status of valve pattern monitor, refer to:
3.6, "Block Status of Valve Pattern Monitor"
Creating Application Programs

Before using any valve pattern monitor, it is necessary to create an operation for the valve pattern
monitor and to specify the required builder definition items. The processing timing of the valve
pattern monitor should also be specified if required.
User can check whether the valve pattern monitor is operated properly by the created application
program, using the simulation function.
3.1 Valve Pattern Monitor Type and Size Page 1 of 1
3.1 Valve Pattern Monitor Type and Size

There are eight types of valve pattern monitors. Select the appropriate one according to the number
of valves to be monitored and whether there is a need for alarm checking in the transfer-system
plant.
Valve Pattern Monitor Type and Size

Of the eight types of valve pattern monitors, four types have a different number of valves that can
be monitored without the alarm check function and the other four types have a different number of
valves that can be monitored with the alarm check function. Each of them has a different application
capacity in the FCS database area (application loading area). Select the appropriate type of valve
pattern monitor according to the transfer-system plant to be monitored.
Table 3.1-1 Valve Pattern Monitor Type and Size
Block type Name

VPM64 64-Data Valve Pattern Monitor
VPM64A 64-Data Valve Pattern Monitor with Alarm
Valve pattern monitors with an alarm check determine if the alarm status of the specified valve
is “NR.”
TIP For the valve pattern monitor to be used for monitoring valves, define the tag name and the
function block model name using the control drawing builder, the same as the PID Controller
Block and the sequence table block. Then specify the valve pattern monitor to be used for
monitoring valves by the vpmstart statement using the tag name which is defined previously.
Specify the valve pattern monitor by the vpmstart statement before specifying the valves to be
monitored by the drive vpmon or vpmon statement.
3.2 System Environment Page 1 of 1
3.2 System Environment

This section describes the hardware and software environments required to operate the valve
pattern monitor.
Hardware Environment
Object Hardware
The valve pattern monitor are applicable in all FCSs except PFCS.
FFCS series/KFCS2/KFCS/LFCS2/LFCS/SFCS/RFCS5/RFCS2 are enable.
Software Environment
Valve Pattern Monitor Package

The Valve Pattern Monitor package can be used with the following control station packages.
• Control Function for Standard Field Control Station (for RIO)
• Control Function for Enhanced Field Control Station (for RIO)
• Control Function for Standard Field Control Station (for FIO)
• Control Function for Enhanced Field Control Station (for FIO)
• Control Function for Compact Field Control Unit (for FIO)
• Control Function for Compact Field Control Station
• Control Function for Field Control Station (for AFV30□/AFV40□)
• Control Function for Field Control Station (for A2FV50□)
• Control Function for Field Control Station (for AFV10□)
To use the valve pattern monitor, an optional program name must be registered in the FCS.
SEE For more information about the registration, refer to:

ALSO 3.10, "Builder Items for Creating Application Program"
3.3 Procedure for Operating Valve Pattern Monitor Page 1 of 1
3.3 Procedure for Operating Valve Pattern

Monitor
To operate the valve pattern monitor, the builder of the valve pattern monitor blocks must be
defined, and the operation (application program) must be scripted in SEBOL statements dedicated
for the valve pattern monitor.
Procedure for Operating Valve Pattern Monitor
Figure 3.3-1 Procedure for Operating Valve Pattern Monitor
3.4 Data Items for Valve Pattern Monitor Page 1 of 5
3.4 Data Items for Valve Pattern Monitor

There are 31 data items in the valve pattern monitor.
Of those items ENTRY is a special data item that has an array. The data stored in ENTRY differs
depending on the value of array elements.
NUM1, NUM2, NUM2CHK, and HMAX are data items related to the number of pieces of data. Refer
to these data item values if checking whether the valve pattern monitor to be used is appropriate.
Data Items
Each data item of the valve pattern monitor can be accessed through execution of SEBOL
statements from the operation, and through entry from the operation and monitoring function (in
HIS).
The data items of the valve pattern monitor are listed in the following table.
Table 3.4-1 Data Items
Data Entry
Symbol Name Range Default
type (*1)
MODE Block mode char*8 YES NO "AUT"
OMOD Block mode (lowest priority) char*4 NO NO "AUT"
CMOD Block mode (highest priority) char*4 NO NO "" (*2)
BSTS Block status char*8 Δ (*3) NO "STOP"
ALRM Alarm status char*8 NO NO "NR"
AFLS Alarm flashing status char*8 NO NO "" (*2)
AF Alarm detection specification char*8 NO NO "" (*2)
AOFS Alarm suppression specification char*8 NO NO "" (*2)
OPMK Operation mark integer YES 0 to 64 0
UAID User application ID integer YES NO 0
OWNER Owner (unit name) char*16 NO NO "" (*2)
ENTRY
Registration data char*16 NO NO "" (*2)
[3,N]
0 to
NUM1 Number of pieces of data in the present station integer NO 0
512
0 to
NUM2 Number of pieces of data in other stations integer NO 0
512
Number of pieces of data in other stations to be 0 to
NUM2CHK integer NO 0
monitored 512
0 to
HMAX History of the maximum number of pieces of data integer NO 0
512
SIMM Simulation switch integer NO 0 to 1 0
ERRE Error code long NO NO 0
SGNLTAG SGNL alarm, tag name char*16 NO NO "" (*2)
SGNLITEM SGNL alarm, data item char*16 NO NO "" (*2)
SGNLERRE SGNL alarm, error code long NO NO 0
VPTNTAG VPTN alarm, tag name char*16 NO NO "" (*2)
VPTNITEM VPTN alarm, data item char*16 NO NO "" (*2)

VPTNERRE VPTN alarm, error code long NO NO 0
DATATAG DATA alarm, tag name char*16 NO NO "" (*2)
DATAITEM DATA alarm, data item char*16 NO NO "" (*2)
DATAERRE DATA alarm, error code long NO NO 0
TYPETAG TYPE alarm, tag name char*16 NO NO "" (*2)
TYPEITEM TYPE alarm, data item char*16 NO NO "" (*2)
TYPEERRE TYPE alarm, error code long NO NO 0
*1: YES: Entry from the operation and monitoring function is allowed.
NO: Entry from the operation and monitoring function is not allowed.
*2: Double quotation marks ("") stand for null.
*3: In the entry from the operation and monitoring function, the block status, BSTS cannot be modified
from "STOP" to "RUN."
TIP The data items listed in Table are all objects to be saved as tuning parameters.
Data Stored in Data Item “ENTRY[3,N]”

The registration data is stored in ENTRY[3,N]. The data stored in ENTRY[3,N] can be displayed in
the operation and monitoring function.
The number of elements in ENTRY[3,N] differs depending on the type of valve pattern monitor. The
following table lists the number of elements in ENTRY[3,N] for various types.
• VPM64, VPM64A: ENTRY [3,64]
• VPM128, VPM128A: ENTRY [3,128]
• VPM256, VPM256A: ENTRY [3,256]
• VPM512, VPM512A: ENTRY [3,512]
The data registered by the SEBOL statement (drive vpmon statement or vpmon statement) is stored
in ENTRY. The following table lists the data stored in ENTRY.
Table 3.4-2 Data Stored in ENTRY
Kind of
Content Remark
ENTRY
ENTRY If a generic name is set in the drive vpmon or vpmon statement, a tag
Tag name
[1,N] name corresponding to the generic name is stored in ENTRY[1,N].
ENTRY
Data item
[2,N]
ENTRY Reference value
[3,N] and status
Example of Data Storing in ENTRY[3,N]

The relationship between the execution content of the SEBOL statement and the data stored in
ENTRY[3,N] is described below as an example.
The vmpon statement in the first line sets the reference value to 1 and the signal parameter to 0.
Both MV and PV may be displayed on the operation and monitoring window by the third line script.
vpmon [SW101.PV==1:0]
vpmon [SW301.PV==0:0]
drive vpmon [SIO301=2:10]
The execution results of the above SEBOL statements are displayed in the operation and monitoring
function as follows.
ENTRY [1,1] SW101 ENTRY [2,1] PV ENTRY [3,1] 1 a 0 8EBD
ENTRY [1,2] SW301 ENTRY [2,2] PV ENTRY [3,2] 0 a 0
ENTRY [1,3] SIO301 ENTRY [2,3] MV ENTRY [3,3] 2 a 1 0
ENTRY [1,4] SIO301 ENTRY [2,4] PV ENTRY [3,4] 2 1 0
The reference value, signal parameter, error code, etc., have been set in each ENTRY displayed in
the operation and monitoring function. For example, the execution results displayed in [ENTRY
[3,1]], among those in the operation and monitoring function, have the following definitions.
Figure 3.4-1 Screen Display Definitions
If there is no abnormality with the data, only a reference value and a parameter are displayed in the
operation and monitoring function. If there is an abnormality with the data, a 4-digit hexadecimal
error code is displayed (at the right of parameter), in addition to the reference value and parameter.
In the above example, the error code is displayed in ENTRY[3,1], and therefore, SW101.PV is
assumed to have an error.
Rule for Data Storage in ENTRY[3,N]

• If registration of the valves to be monitored is reset in the drive vpmoff or vpmoff statement, the
character strings stored in ENTRY[1,N], ENTRY[2,N], and ENTRY[3,N] are cleared.
• Even if the valve pattern monitor with the alarm check function is used, <tag name>.ALRM is not
stored in ENTRY.
• If multiple pieces of data with different data items are registered under the same tag name for
the valve pattern monitor with the alarm check function, the valve pattern monitor checks ALRM
for one piece of data. “a” (ALRM check performed) is stored in data item ENTRY[3,N] of the data
to be checked.
• If the reference value is between -32768 and 32767, it is stored in ENTRY[3,N] in decimal
notation. If the reference value is out of that range, it is stored in hexadecimal notation.
• If the data registered in ENTRY resides in an FCS other than the valve pattern monitor, “s” (other
station data) is stored in ENTRY[3,N]. If any registered data is not acquired because of a
different tag name, “s” is also stored in ENTRY[3,N].
TIP The error code is the same as the details of SEBOL error code.
SEE For more information about SEBOL error codes, refer to:
Data Items Related to Number of Pieces of Data

NUM1, NUM2, NUM2CHK, and HMAX are data items related to the number of pieces of data.
Operation of the valve pattern monitor can be determined from those data item values.
NUM1
NUM1 stores the number of pieces of present station data currently registered. The present station
data represents the data which resides in the same FCS as the valve pattern monitor.
The NUM1 value increases as data is registered with the drive vpmon statement or vpmon
statement. The NUM1 value decreases as registered data is deleted with the drive vpmoff statement
or vpmoff statement.
NUM2
NUM2 stores the number of pieces of other station data currently registered.
The other station data represents the data which resides in the FCS in which the valve pattern
monitor does not reside.
The NUM2 value increases as data is registered with the drive vpmon statement or vpmon
statement. The NUM2 value decreases as registered data is deleted with the drive vpmoff statement
or vpmoff statement.
NUM2CHK
NUM2CHK stores the number of pieces of other station data that have been actually checked within
the monitoring cycle.
If all pieces of other station data can be checked within the monitoring cycle, the NUM2CHK value
will be identical to the NUM2 value. Depending on communication timing, the NUM2CHK value may
temporarily be greater than the NUM2 value.
If many pieces of other station data have been registered in the valve pattern monitor which resides
in the FCS, it may not be possible to check all pieces of other station data within the monitoring
cycle. The number of pieces of other station data that has been checked can be confirmed with
NUM2CHK.
The NUM2CHK value will be 0 immediately after initiating the valve pattern monitor with the
vpmstart statement, or after modifying the valve pattern monitor data item BSTS from “PAUS”
to “RUN.”
TIP Monitoring scan cycle is a number stands for the multiple of the basic scan period (one FCS data
acquisition scan time), means among this number of data acquisition scans, only one scan have
monitoring process. A valve pattern monitor checks the gathered data once per how many basic
scans is indicated by the number for monitoring scan cycle setting.
The default setting for valve pattern monitoring cycle is fixed as 5. It means, the monitoring
process takes place at every 5 basic scans.
HMAX
HMAX stores the maximum total of NUM1 and NUM2.
The number of valves to be monitored with the valve pattern monitor is obtained from the HMAX
value. This allows the user to determine whether the appropriate type of valve pattern monitor has
been selected according to the number of valves to be monitored.
The HMAX value will be 0 immediately after the valve pattern monitor data item BSTS is modified
from “STOP” to “RUN.” If the NUM1 and NUM2 values have increased because additional data is
registered with the drive vpmon or vpmon statement, the HMAX value will be the total of the NUM1
and NUM2 values.
However, even if the registered data is reset with the drive vpmoff, vpmoff, or vpmreset statement,
the HMAX value will not decrease.
SEE For more information about acquisition and inspection of other station data, refer to:
ALSO 3.9, "Inspection of Data Acquired from FCS"
For more information about error codes stored in ENTRY[3,N], SGNLERRE, DATAERRE, and
TYPEERRE, refer to:
13., “Error Handling” in SEBOL Reference (IM 33J05L20-01EN)
3.5 Block Mode of Valve Pattern Monitor Page 1 of 1
3.5 Block Mode of Valve Pattern Monitor

There are two block modes (values in data item MODE) of the valve pattern monitor: “O/S”
and “AUT.”
To perform online maintenance for the valve pattern monitor using the online maintenance function,
the block mode must be “O/S.”
Types of Block Modes

The following table lists the types of block modes.
Table 3.5-1 Block Modes of Valve Pattern Monitor
Symbol Name
O/S Out of Service
AUT AUTomatic
While the online maintenance function is used, the block mode will be “O/S.” The block mode
returns to the previous state when the online maintenance has been completed.
To perform the online maintenance, the block status BSTS of the valve pattern monitor needs to
be “STOP.” If the block status is “RUN” or “PAUS,” the valve pattern monitor cannot apply the online
maintenance function.
3.6 Block Status of Valve Pattern Monitor Page 1 of 1
3.6 Block Status of Valve Pattern Monitor

There are three valve pattern monitor block statuses (values of data item BSTS): “STOP,” “RUN,”
and “PAUS.”
By changing these block statuses the system can pause or restart valve pattern monitor operation.
Types of Block Statuses

The following table lists the types of block statuses.
• STOP (Stop inspection)
No unit uses the valve pattern monitor for inspection.
• RUN (Run inspection)
The valve patterns are being inspected.
• PAUS (Pause inspection)
The valve pattern inspection is paused.
Block Status Transition

The following illustrates the transition of valve pattern monitor block statuses.
Figure 3.6-1 Block Status Transition
To change the valve pattern monitor block status from “STOP” to “RUN,” execute the vpmstart
statement.
For transitions other than those above, use either of the following transition methods. One method
that can be used is to modify the value of data item BSTS through entry from the operation and
monitoring function. The other method that can be used is to modify the value of data item BSTS
using the assignment statement in the SEBOL statements for operation.
SEE For more information about modifying the value of data item BSTS with the assignment
ALSO statement, refer to:
3.11, "Example for Creating Application Program"
3.7 Signal Transmission and Alarm of Valve Pattern Monitor Page 1 of 5
3.7 Signal Transmission and Alarm of Valve

Pattern Monitor
If the valve pattern monitor detects a valve abnormality, it transmits a signal to the unit. Information
about processes distributed in the unit and on alarms has been included in the signal parameters
transmitted to the unit. The unit executes alarm processes according to that information.
Signal Transmission
The valve pattern monitor generates an alarm and transmits a signal (signal name: VPMSIG) to the
unit if a valve abnormality is detected. The signal the valve pattern monitor transmits contains five
parameters. The following table gives the contents of each parameter.
Table 3.7-1 Parameter Contents in Signal VPMSIG
Item Type Content

Signal name char*8 VPMSIG
1st parameter long Parameter specified in the vpmon or drive vpmon statement
2nd parameter char*16 Kind of abnormality (VPTN, DATA, TYPE)
3rd parameter char*16 Tag name
4th parameter char*16 Data item
5th parameter long Error code
According to the number of parameters the valve pattern monitor transmits, specify “5” or more as
the maximum number of signal parameters for the SFC block (operation) that receives the VPMSIG
signal. If default value “2” is retained as the maximum number of signal parameters, the SFC block
may not receive the VPMSIG signal.
TIP “Error code” in the table above is the same as the detailed SEBOL error code.
The data item of the 4th parameter differs depending on the 2nd parameter value. The relationship
between those parameters is described below.
Table 3.7-2 Relationship between the 2nd and 4th Parameters
Kind of abnormality Definition Data item

Data inconsistency Registered data item
VPTN
Alarm status is not NR. ALARM
DATA No data can be acquired. Data item without data acquisition
TYPE Not integer type data Registered data item
SEE For more information about error codes, refer to:

Kinds of Alarms
If the valve pattern monitor detects an alarm, one of the alarm statuses which denote kinds of
alarms is stored in data item ALRM of the valve pattern monitor. The following table lists the kinds of
alarms that the valve pattern monitor detects.
• SGNL
Signal transmission failure
• VPTN
Valve pattern inconsistency
• DATA
Data acquisition failure
• TYPE
Incorrect data type
• NR
Normal status
Alarms other than “NR” are described below.
SGNL (Signal Transmission Failure Alarm)

If the valve pattern monitor cannot transmit the signal to the unit upon detection of a valve
abnormality, the SGNL alarm will occur. If the SGNL alarm occurs, the monitoring process on that
cycle is aborted.
If the valve pattern monitor succeeds in signal transmission on the next monitoring cycle, recovery
from the SGNL alarm is made. Recovery from the SGNL alarm is also made when the value of data
item BSTS of the valve pattern monitor changes from “PAUS” to “RUN,” or from “STOP” to “RUN.”
If the SGNL alarm occurs, a system alarm message appears on the operation and monitoring
function panel. The display format is shown in the figure below. The error code of signal
transmission failure in the valve pattern monitor is classified as 20740.
Figure 3.7-1 Display Example of System Alarm Message
On the second line of the system alarm message, the tag name and data item name of the abnormal
value that caused the signal transmission failure are displayed.
If the valve pattern monitor fails to transmit the signal when no SGNL alarm is being generated, it
outputs a system alarm message. While the SGNL alarm is being generated, the valve pattern
monitor will not output a system alarm message, even if it fails to transmit the signal.
TIP If the valve pattern monitor fails to transmit the signal upon detection of a valve abnormality and
monitoring on that cycle is aborted, signal transmission to the unit will not be performed again
even if an abnormality is detected in the same valve on the next monitoring cycle.
If the valve pattern monitor detects another valve abnormality and succeeds in transmitting the
signal to the unit, recovery from the SGNL alarm will be made.
VPTN (Valve Pattern Inconsistency Alarm)

If the acquired valve data is not identical to the reference value stored in ENTRY[3,N], the VPTN
alarm will occur assuming the valve as abnormal.
In addition, the valve pattern monitor with the alarm check function checks the function block that
controls the valve to be monitored for ALRM. Unless the checked ALRM is “NR,” the VPTN alarm will
occur.
If the value of data item BSTS of the valve pattern monitor is “RUN,” recovery from the VPTN alarm
will be made when all pieces of valve data are identical to the reference value on the following
monitoring cycles. Recovery from the VPTN alarm is also made when the value of data item BSTS of
the valve pattern monitor changes from “PAUS” to “RUN,” or from “STOP” to “RUN.”
DATA (Data Acquisition Failure Alarm)

If the valve pattern monitor cannot acquire any valve data, the DATA alarm occurs and the valve
pattern monitor transmits a signal to the unit.
If the value of data item BSTS of the valve pattern monitor is “RUN,” recovery from the DATA alarm
will be made when all pieces of valve data are able to be acquired on the following monitoring cycle.
Recovery from the DATA alarm is also made when the value of data item BSTS of the valve pattern
monitor changes from “PAUS” to “RUN,” or from “STOP” to “RUN.”
TYPE (Incorrect Data Type Alarm)

If the registered data is not integer-type data (real number type or character type), the TYPE alarm
occurs. This alarm also occurs if there is an error in the application program. Modify the application
program.
Recovery from the TYPE alarm is made when the value of data item BSTS of the valve pattern
monitor changes from “PAUS” to “RUN,” or from “STOP” to “RUN.”
Precautions for Detecting Alarms in the Valve Pattern

Monitor
The valve pattern monitor can detect an alarm if the value of data item BSTS of the valve pattern
monitor is “RUN.” However, data is checked only once on a monitoring cycle even though the BSTS
value is “RUN.” Therefore, the valve pattern monitor cannot detect a temporary data abnormality,
unless check timing (process timing) corresponds to the abnormal time.
Figure 3.7-2 Example: Abnormality that Cannot be Detected
If a certain period of time has passed since the valve pattern monitor generated an alarm, the
system allows the alarm to be regenerated. Whether the alarm is regenerated, is specified by the
FCS Constants Builder. Only the active valve pattern monitor (the value of data item BSTS is “PAUS”
or “RUN”) can regenerate an alarm.
TIP The valve pattern monitor transmits the generated alarm according to the settings of the alarm
detection specification (AF) and alarm suppression specification (AOFS).
Data Item Status for Valve Pattern Monitor Alarm

• Even if the data status is changed from “abnormal” to “normal” when the value of data item
BSTS of the valve pattern monitor is “PAUS” or “STOP,” recovery from the valve pattern monitor
alarm will not be made (ALRM value will not change).
• If the value of data item BSTS of the valve pattern monitor changes from “PAUS” or STOP”
to “RUN,” recovery from all alarms will be made (ALRM value will be “NR”).
The following table lists the data item statuses for alarms.
Table 3.7-3 Data Item Status for Alarms
Data Initialize start Valve pattern monitor

Name Builder default
item (*1) startup
ALRM Alarm status NR Previous status NR
Alarm detction
AF
specification
Specification reset
Alarm suppression Previous status Previous status
AOFS status
specification
*1: Includes the operation in which the block mode changes from “O/S” to “AUT.”
TIP If a process alarm message is generated, the value of data item “OWNER” is appended to the
message and displayed in the operation and monitoring function.
SEE For more information about the alarm detection specification, refer to:
ALSO 5.13, “Deactivate Alarm Detection” in Function Blocks Overview (IM 33J15A20-01EN)
For more information about the alarm suppression specification, refer to:
5.14, “Alarm Inhibition (Alarm OFF)” in Function Blocks Overview (IM 33J15A20-01EN)
Alarm Recovery If Multiple Pieces of Data Detect the

Same Alarm
If the same alarm is detected in multiple pieces of data, the system outputs the process alarm
message for the first piece of data. For example, assume that valve 1 detects the valve pattern
inconsistency and then valve 2 detects the valve pattern inconsistency. In this case, only the process
alarm message of valve 1 is output.
If the valve patterns of both valve 1 and valve 2 are identical, and if there is no other valve with an
inconsistent valve pattern, recovery from the VPTN alarm will be made.
Error Information Stored in Data Item upon Detection

of Abnormality
If any abnormality is detected, the valve pattern monitor stores the tag name, data item, error code,
etc., in one of the data items listed in the following table. These data items are updated each time
an abnormality is detected. If the same alarm is detected in multiple pieces of data, the system
outputs the process alarm message for the first piece of data. The data items listed in the table
below will give the most recent information about abnormalities.
Table 3.7-4 Data Items Where Error Information Is Stored
Detected abnormality Tag name and data item Error code

Signal transmission failure (*1) SGNLTAG, SGNLITEM SGNLERRE
Valve pattern inconsistency VPTNTAG, VPTNITEM VPTNERRE
Data acquisition failure DATATAG, DATAITEM DATAERRE
Incorrect data type TYPETAG, TYPEITEM TYPEERRE
*1: The tag name and data item of the abnormal valve that causes signal transmission are stored
in “SGNLTAG, SGNLITEM.”
If the valve pattern monitor which has been paused (PAUS) is re-executed (RUN), recovery from all
generated alarms will be made.
The alarm recovery timing of the valve pattern monitor will synchronize to its process timing on the
basic cycle immediately after the block status changes from “PAUS” to “RUN.”
Even if the valve pattern monitor is re-executed, the values of SGNLTAG, SGNLITEM, VPTNTAG,
VPTNITEM, DATATAG, DATAITEM, TYPETAG, TYPEITEM, SGNLERRE, VPTNERRE, DATAERRE,
TYPEERRE, and ERRE will not change.
3.8 SEBOL Statements for Valve Pattern Monitor Page 1 of 1
3.8 SEBOL Statements for Valve Pattern Monitor

There are six SEBOL statements dedicated to the valve pattern monitor. With these SEBOL
statements, user applications which control the valve pattern monitor can be created.
Application of SEBOL Statements

▼ SEBOL Statement for Valve Pattern Monitor
The following figure illustrates valve pattern monitor operation through execution of SEBOL
statements (vpmstart, drive vpmon, drive vpmoff, vpmon, vpmoff, and vpmreset).
The SEBOL statements are executed by initiating the operation from the unit.
Figure 3.8-1 Example of Valve Pattern Monitor Operation by SEBOL Statements
3.8.1 vpmstart Statement Page 1 of 2
3.8.1 vpmstart Statement

This statement secures the specified valve pattern monitor and makes it available for use
(monitoring of the valves is possible). The unit, from which the operation is initiated and executes
the vpmstart statement, is the “Owner” of the valve pattern monitor.
If “STOP” is set as data item BSTS of the valve pattern monitor, the system can terminate (reset)
the valve pattern monitor.
vpmstart Statement Format

The following shows the format of the vpmstart statement.
Figure 3.8.1-1 vpmstart Statement Format
<valve pattern monitor>

Specifies the valve pattern monitor using a tag name, local generic name, generic name, etc.
<error variable>
Specifies a local variable where an error code is stored. If no error occurs, 0 is stored in the variable.
<label>
Specifies a branch destination where processing at error generation is performed.
<error identifier>
Specifies a constant or a local variable to identify the location where the error is generated in the
error processing unit.
Detailed vpmstart Statement

Detailed information about the vpmstart statement, such as operation at statement execution, is
given below.
• If the valve pattern monitor specified in the vpmstart statement has already been initiated from
the same unit, the statement will normally be terminated without error generation.
• If the vpmstart statement is executed, the value of data item BSTS of the valve pattern monitor
changes from “STOP” to “RUN.”
• The tag name of the unit which has executed the vpmstart statement is stored in data item
OWNER of the valve pattern monitor.
• If the valve pattern monitor detects a valve abnormality, a signal is transmitted to the unit that
executed the vpmstart statement.
• If the character-type (CHR16) user definition data, VPMNAME, is defined in the unit, the tag
name of the valve pattern monitor is stored in VPMNAME upon execution of the vpmstart
statement. However, if the status (BSTS) of the unit is “END” or “ABORTED,” it is unclear which
character string is to be stored in VPMNAME.
If the vpmstart statement is executed, the following initialization processing will be executed.
3.8.1 vpmstart Statement Page 2 of 2
• The valve pattern monitor is initialized so that no valve is registered.

• If the vpmstart statement is executed, the alarm status ALRM of the valve pattern monitor is
initialized (“NR” is stored). The initialization timing corresponds to the monitoring process start
time of the valve pattern monitor, which is on the basic cycle immediately after the vpmstart
statement is executed. This is not the time the vpmstart statement was executed.
• Upon execution of the vpmstart statement, the valve pattern monitor data items, SGNLTAG,
SGNLITEM, VPTNTAG, VPTNITEM, DATATAG, DATAITEM, TYPETAG, and TYPEITEM are
initialized (a character string with a length of 0 is stored).
• The valve pattern monitor data items, SGNLERRE, VPTNERRE, DATAERRE, TYPEERRE, and ERRE
are initialized (0 is stored).
If the vpmstart statement is executed in the following cases, an error will result.
• If the valve pattern monitor specified in the vpmstart statement has already been initiated from
another unit, the statement results in an error.
• If the unit has already initiated another valve pattern monitor, an additional vpmstart statement
results in an error. The unit can initiate only one valve pattern monitor at the same time.
• If the vpmstart statement is executed from the monitoring operation when the unit status (BSTS)
is “END” or “ABORTED,” an error will result.
Terminating the Valve Pattern Monitor

If the unit is deactivated (its status is “END” or “ABORTED”), the value of data item BSTS of the
valve pattern monitor automatically changes from “RUN” to “STOP,” then the valve pattern monitor
is terminated (reset). Here, another unit can secure this valve pattern monitor.
If the user definition data, VPMNAME, has been set in the unit, the value of VPMNAME will be a null
character string (string comprised of 0s).
To reset the valve pattern monitor during execution of the unit, script the following assignment
statement and set data item BSTS of the valve pattern monitor to “STOP.”
<valve pattern monitor>.BSTS="STOP"
If a batch assignment statement is used as shown below, an error check will be performed upon
assignment of “STOP.”
unit genname VPM128 VPM03
integer ierr
......
[VPM03.BSTS = "STOP"]ierr
if(ierr <> 0) then ! Process if an error is detected
end if
.....
3.8.2 drive vpmon Statement Page 1 of 5
3.8.2 drive vpmon Statement

If the drive vpmon statement is executed, the drive statement operation is performed, then the
valves (function blocks to operate the valves) and the data (function block data) are registered in
the valve pattern monitor, and the monitoring process is started.
The drive statement operation is used to modify the output status of the valve operating function
block (motor control block or switch instrument block) and to check the valve for proper operation
with the answer-back check of the function block.
drive vpmon Statement Format

The following shows the format of the drive vpmon statement.
Figure 3.8.2-1 drive vpmon Statement Format
<function block array>

Specifies the valves (function blocks) to be registered. A maximum of 16 valves can be specified. No
data item name is scripted in the drive vpmon statement, because the data items to be registered
are fixed.
The following table lists the contents that can be specified in this item.
Table 3.8.2-1 Contents Specified in <function block array> of drive vpmon Statement
Content Specification(*1)
Constant NO
Local variable simplified NO
Local variable array element NO
Local variable array whole NO
Tag name +data item simplified NO
Generic name simplified+data item array element NO
Generic name array element+data item simplified NO
Generic name array element+data item array element NO
Generic name array whole+data item simplified NO
Tag name YES
Generic name simplified YES
Generic name array element YES
Generic name array whole YES
*1: YES: Can be specified.
NO: Cannot be specified.
• A tag name is declared with the block statement or global block statement.
• A generic name is declared with the unit genname statement.
• For the section where a generic name can be scripted, a global generic name (global genname
declaration), local generic name (genname declaration), global unit generic name (global unit
genname declaration), or dummy argument function block (argblock declaration) can be used.
• Global variables (global integer declaration, etc.) of the SFC sequence cannot be used.
<output value and parameter array>

Specifies an output value (0 or 2) and a parameter with a local variable or a constant.
Though a 3-position output function block (SIO-22 etc.,) may give an output value 1, the drive
vpmon can not give a command to do so. In the situation like this, drive statement may be applied
first to set the output value to 1, then use vpmon statement for monitoring.
Specify an integer between 0 and 19 as a parameter. If a value other than integers 0 to 19 is
specified, an error will result upon execution of the statement. If an integer other than one between
0 and 19 is specified, an error will result upon execution of the statement. This parameter is the first
signal parameter of a signal the valve pattern monitor transmits to the unit.
The following table lists the contents that can be specified as the output value and parameter.
Table 3.8.2-2 Contents Specified in <output value and parameter array> of the drive vpmon
Statement
Content Output(*1) Parameter(*1)

Constant YES YES
Local variable simplified YES YES
Local variable array element YES YES
Local variable array whole YES NO
Tag name +data item simplified NO NO
Generic name simplified+data item array element NO NO
Generic name array element+data item simplified NO NO
Generic name array element+data item array element NO NO
Generic name array whole+data item simplified NO NO
Tag name NO NO
Generic name simplified NO NO
Generic name array element NO NO
Generic name array whole NO NO
• Global variables (global integer declaration, etc.) of the SFC sequence can be used.
• If the whole array is specified for a reference value, all parameters become identical.
• The whole array cannot be specified for a parameter. Only one array element can be specified for
a parameter.
<error array>
Specifies an integer-type local variable array. An error code is stored in this array if an error occurs.
A zero (0) is stored in this array if no error occurs.
If only one piece of data is stored in this array, a simple variable or array element can be specified in
place of a local variable array.
<label>
<error identifier>
processing unit.
TIP The drive vpmon statement registers the valves and function block data in the valve pattern
monitor after the drive statement operation has been completed. Therefore, there is no
specification corresponding to the time specification of the vpmon statement.
Detailed drive vpmon Statement

Detailed information about the drive vpmon statement, such as operation at statement execution is
given below.
• The system performs monitor processing by using an output value as the reference value of the
PV and MV values.
• If the drive statement operation of all the specified valves has been completed properly, the drive
vpmon registers the valves and function block data in the valve pattern monitor. If there is an
abnormal valve in the drive statement operation, the drive vpmon statement will be aborted
without registering the function block data.
• If the specified valve has already been registered in the valve pattern monitor, registered content
(valve and data) deletion, drive statement operation, and re-registration will be performed in this
order.
• If an error (including one in deleting the registered content) occurs before the output status of
the function block to be controlled by the drive statement operation is modified, registered
content deletion and re-registration will not be performed. The registration statuses of the valve
and function block data remain as they were before execution of the drive vpmon statement.
• If an error (e.g. an answer-back check abnormality) occurs after the output status of the function
block to be controlled by the drive statement operation is modified, only registered content
deletion is performed.
• If there is any array element out of the array suffix range, the drive vpmon statement will not
perform registered data deletion, drive statement operation, and re-registration for all valves.
Upon detection of an error out of the array suffix range, processing of the drive vpmon
statement on that line is aborted.
• A maximum of 16 valves and their function block data can be registered on one line (each array
element is counted as one for arrays).
• Even if the same valve is registered repeatedly, the valve pattern monitor registers the valve
once. The most recently registered output value and parameter are stored in memory.
• If an SO-1 or SO-2 type switch instrument block is specified as a valve, the PV value will not be
registered even if both PV and MV values, or only the PV value is specified as the station
common item. This is because such a switch instrument does not have the data item, PV. In such
a case, the drive vpmon statement will not result in an error.
• If a valve that cannot be specified is included, none of the valves is registered.
If the drive vpmon statement is executed in the following cases, an error will result.
• The SI-1, SI-1ALM, and SI-2 type switch instrument blocks cannot be specified as valves in the
drive vpmon statement. If either type has been specified, an error will result at execution of the
statement.
• If “1” is specified as an output value in the drive vpmon statement, an error will occur at
execution of the statement. Even if an error occurs, the drive statement operation is performed,
but registered content deletion and re-registration are not performed. For the switch instrument or
motor control instrument, the output status in the drive statement operation becomes “1,” but
answer-back check is not performed.
SEE For more information about the drive statement and error codes, refer to:
ALSO 5.4, “drive Statement” in SEBOL Reference (IM 33J05L20-01EN)
13., “Error Handling” in SEBOL Reference (IM 33J05L20-01EN)
For more information about the time specification of the vpmon statement, refer to:
3.8.4, "vpmon Statement"
Signal Transmission Processing Based on Parameter

Parameters specified when valves are registered with the drive vpmon statement are used to
perform signal transmission processing according to the valve importance level in the valve pattern
monitor.
Parameter between 10 and 19

Specify a parameter between 10 and 19 for valves of such important that emergency stop
processing must be made upon detection of an abnormality.
If an abnormal valve is detected, the valve pattern monitor transmits the valve information to the
unit as a signal. After one signal is transmitted to the unit, processing on that monitoring cycle is
terminated, if a parameter between 10 and 19 is specified. The statuses of other valves are not
checked. Information about the valve where an abnormality has been detected is stored in data item
ENTRY.
Parameter between 0 and 9

Specify a parameter between 0 and 9 for valves other than those of such important that emergency
stop processing must be made upon detection of an abnormality. If a parameter between 0 and 9 is
specified, the valve pattern monitor checks valves one by one and transmits the valve information to
the unit as a signal. If abnormalities are detected in multiple valves, the valve pattern monitor
transmits multiple signals on one processing timing.
The following figure shows the valve pattern monitor processing flowchart.
Figure 3.8.2-2 Flowchart of Priority Ordered Processing Based on Parameter
3.8.3 drive vpmoff Statement Page 1 of 3
3.8.3 drive vpmoff Statement

The system deletes the valves (function blocks) and data (function block data) that are registered in
the valve pattern monitor by executing the drive vpmoff statement, then performs the drive
statement operation.
drive vpmoff Statement Format

The following shows the format of drive vpmoff statement.
Figure 3.8.3-1 drive vpmoff Statement Format
<function block array>

Specifies the valves (function blocks) to be deleted. A maximum of 16 valves can be specified. No
data item name is scripted in the drive vpmoff statement because the data items of the function
block to be deleted are fixed.
The following table lists the contents that can be specified in this item.
Table 3.8.3-1 Contents Specified in <function block array> of drive vpmoff Statement
Constant NO
Tag name +data item simplified NO
Generic name simplified+data item array element NO
Generic name array element+data item simplified NO
Generic name array element+data item array element NO
Generic name array whole+data item simplified NO
Tag name YES
<output value array>

Specifies an output value (0, 1 or 2) with a local variable or a constant.
<error array>
Specifies an integer-type local variable array. An error code is stored in this array if an error occurs.
A zero (0) is stored in this array if no error occurs. If only one piece of data is stored in this array, a
simple variable or array element can be specified in place of a local variable array.
<label>
<error identifier>
Specifies a local variable or a constant to identify the location where the error is generated in the
Detailed drive vpmoff Statement

Detailed information on the drive vpmoff statement, such as operation at statement execution, is
given below.
• If the drive vpmoff statement is executed, the valves and function block data are deleted from
the valve pattern monitor before the drive statement operation is performed.
• Even if an error occurs when the function block data is deleted with the drive vpmoff statement,
the drive statement operation is performed.
• If there is an array element out of the array suffix range, the drive vpmoff statement will not
perform the registered content (valve and data) deletion and the drive statement operation.
Upon detection of an error out of array suffix range, processing of the drive vpmoff statement on
that line is aborted.
• A maximum of 16 valves and their function block data can be deleted on one line (each array
element is counted as one for arrays).
• If an SO-1 or SO-2 type switch instrument block is specified as a valve, the PV value will not be
deleted even if both PV and MV values or only the PV value is specified. Because such a switch
instrument block does not have the data item, PV. In such a case, the drive vpmoff statement
will not result in an error.
• If a valve that cannot be specified is included, none of the valves is deleted. However, the drive
statement operation is performed for other valves.
• “1” can be specified as an output value in the drive vpmoff statement.
• The SI-1, SI-1ALM, and SI-2 type switch instrument blocks cannot be specified as valves in the
drive vpmoff statement. If either type has been specified, an error will result at execution of the
statement.

Recovery from Alarm by drive vpmoff Statement

If the valve where an abnormality occurs is deleted by executing the drive vpmoff statement, the
valve pattern monitor is recovered from an alarm.
The alarm recovery timing of the valve pattern monitor will synchronize to its processing timing on
the basic cycle immediately after the valve and function block data have been deleted. It is not
identical to the execution timing of the drive vpmoff statement.
The procedure for alarm recovery is described below using the example status in which the DATA
alarm (error code: D102) and VPTN alarm (error code: D001) occur.
ENTRY [1,1] VLV301 ENTRY [2,1] PV ENTRY [3,1] 1 0
ENTRY [1,2] VLV302 ENTRY [2,2] PV ENTRY [3,2] 1 0 D102
In the above status, if VLV302.PV in data item ENTRY is deleted by executing drive vpmoff
[VLV302], recovery from the DATA alarm will be made because the valve in data acquisition failure
is deleted. The status recovered from the DATA alarm is shown below.
ENTRY [1,2] ENTRY [2,2] ENTRY [3,2]
In the above status, if VLV305.PV is deleted by executing drive vpmoff [VLV305], the following
status is given. Since VLV303.PV is also inconsistent in valve pattern, recovery from the VPTN will
not be made.
In the above status, if VLV303.PV is also deleted by executing drive vpmoff [VLV303], recovery from
the VPTN will be made because no other valves with valve pattern inconsistencies exist. The status
recovered from the VPTN alarm is shown below.
The above operation is performed in the same way by executing the vpmoff statement in place of
the drive vpmoff statement.
3.8.4 vpmon Statement Page 1 of 5
3.8.4 vpmon Statement

The system registers the valves (function blocks) and data (function block data) in the valve pattern
monitor by executing the vpmon statement, and then performs monitoring processing.
vpmon Statement Format

The following shows the format of the vpmon statement.
Figure 3.8.4-1 vpmon Statement Format
<function block data array>

Specifies the valves and integer-type function block data to be registered in the valve pattern
monitor. A maximum of 32 valves and pieces of function block data can be specified. The following
table lists the contents that can be specified in this item.
Table 3.8.4-1 Contents Specified in <function block data array> of the vpmon Statement
Constant NO
Tag name +data item simplified YES
Generic name simplified+data item array element YES
Generic name array element+data item simplified YES
Generic name array element+data item array element YES
Generic name array whole+data item simplified YES
Tag name NO
Generic name simplified NO
Generic name array element NO
Generic name array whole NO
genname declaration), and dummy argument function block (argblock declaration) can be used.
TIP The scripting method of <function block data array> is the same as that of a group assignment
statement or that of <variable array> in the compare statement. However, a local variable and a
constant cannot be specified in <function block data array>.
SEE For more information about a group assignment statement and the compare statement, refer to:
ALSO 5.2, “Group Assignment Statement” in SEBOL Reference (IM 33J05L20-01EN)
5.3, “compare Statement” in SEBOL Reference (IM 33J05L20-01EN)
<reference value and parameter array>

Specifies a reference value and a parameter with a local variable or a constant. A reference value is
treated as a long type. If a value other than the long type is specified, type conversion is performed.
Specify an integer between 0 and 19 as a parameter. If a value other than integers 0 to 19 is
specified, an error will result upon execution of the statement. This parameter is the first signal
parameter of a signal the valve pattern monitor transmits to the unit.
A reference value and a parameter are scripted and are separated using “,” and “:.” An example of a
script is shown below.
<reference value>:<parameter>[,<reference value>:<parameter>...]
The following table lists the contents that can be specified as the output value and parameter.
Table 3.8.4-2 Contents Specified in <reference value and parameter array> of the vpmon
Statement
Content Output (*1) Parameter (*1)

Constant YES YES
Local variable simplified YES YES
Local variable array element YES YES
Local variable array whole YES NO
Tag name +data item simplified NO NO
Generic name simplified+data item array element NO NO
Generic name array element+data item simplified NO NO
Generic name array element+data item array element NO NO
Generic name array whole+data item simplified NO NO
Tag name NO NO
Generic name simplified NO NO
Generic name array element NO NO
Generic name array whole NO NO
• Global variables (global integer declaration, etc.) of the SFC sequence can be used.
• If the whole array is specified for a reference value, all parameters become identical.
• The whole array cannot be specified for a parameter. Only one array element can be specified for
a parameter.
<error variable>
Specifies a local variable (simple variable or array element) where an error code is stored. The whole
array cannot be specified. A zero (0) is stored in this variable if no error occurs.
<time>
Specifies a wait time until the valve pattern monitor starts a valve check. Specify a value between 0
and 127. The unit of a wait time is the basic cycle.
<label>
<error identifier>
Detailed vpmon Statement

Detailed information about the vpmon statement, such as operation at statement execution, is given
below.
• A maximum of 32 valves (function blocks) and pieces of data (function block data) can be
registered on one line (arrays are tabulated for each array element).
• If the vpmon statement has been completed properly, the valves (function blocks) and data
(function block data) are registered in the valve pattern monitor. If an error occurs in this
statement execution, no valve and data is registered in the valve pattern monitor.
• Even if the same valve is registered repeatedly, the valve pattern monitor registers the valve
once. The most recently registered reference value and parameter are stored in memory.
• Specify integer-type function block data in <function block data array>. If data other than
integer-type data is specified, the valve pattern monitor generates the TYPE alarm (data type
error alarm), although an error will not occur at execution of the vpmon statement.
An error will result in the following cases if the vpmon statement is executed.
• If a value outside of the long-type range is specified for the reference value, an overflow error
will occur at execution of this statement.
• If a value other than one between 0 and 19 is specified for the parameter, an error will occur at
execution of this statement.
• If a value other than one between 0 and 127 is specified in <time>, an error will occur at
execution of this statement.
Script Example of the vpmon Statement: <function

block data array>
unit genname SIO-22 V1,V2
drive [V1,V2 == 2,1]

delay 1000
vpmon [V1.PV.MV,V2.PV.MV == 2:0,2:0,1:0,1:0]

! V1.PV,V1.MV,V2.PV,V2.MV are registered.
......
vpmoff [V1.PV]
! V1.PV registration is deleted.

......
Script Example: Parameter Specification If Reference

Value Is Array
unit genname SIO-22 VALV1[3],VALV2[3]
integer DAT1[3],DAT2[3]
vpmon [V1.PV,V2.PV == 2:0,1:10]

! V1.PV reference value is 2, parameter is 0.
! V2.PV reference value is 1, parameter is 10.
......
vpmon [VALVE1[*].PV == DAT1[*]:10]

! VALVE1[1].PV reference value is DAT1[1] value, parameter is 10.
......
vpmon [VALVE2[*].MV == DAT2[1]:0,DAT2[2]:0,

DAT2[2]:0,DAT3[3]:10]
! VALVE2[1].MV reference value is DAT2[1] value, parameter is 0.
......
Detailed time Specification in the vpmon Statement

Specify the wait time until the valve pattern monitor starts monitoring in <time> of the vpmon
statement, assuming the next basic cycle after the vpmon statement is executed as “0.” If the value
of the function block data is identical to the reference value before the specified <time> passes, the
valve pattern monitor starts monitoring, irrespective of the time specification.
Figure 3.8.4-2 Timing between Time Specification Value and Monitoring
Even if a wait time has been specified, execution of a SEBOL statement will not be delayed. If the
function block data is registered in the valve pattern monitor, the SEBOL statement on the next line
is executed without delay, immediately when the vpmon statement is executed. A wait time for
monitoring is counted down when the value of data item BSTS of the valve pattern monitor is “RUN”
or “PAUS.”
If the monitoring cycle is set to 5, and the time specification to 4, the valve pattern monitor starts
valve data inspection after four basic cycles have passed, as shown below.
Figure 3.8.4-3 Operation under Setting of Monitoring Cycle: 5 and Time Specification: 4
The ALRM check function is not affected by the time specification. If data with time specification is
registered in the valve pattern monitor with the alarm check function (VPM64A to VPM512A types),
data inspection starts at the specified time, but the ALRM check starts immediately after registration
of the valves and data.
TIP The data processing timing in the valve pattern monitor synchronizes to the function block
processing timing with a basic cycle specification.
SEE For more information about process timing, refer to:

ALSO 7., “Process Timing” in Function Blocks Overview (IM 33J15A20-01EN)
3.8.5 vpmoff Statement Page 1 of 3
3.8.5 vpmoff Statement

The valves (function blocks) and data (function block data) that have been registered in the valve
pattern monitor can be deleted by executing the vpmoff statement.
vpmoff Statement Format

The following shows the format of the drive vpmoff statement.
Figure 3.8.5-1 vpmoff Statement Format
<function block data array>

Specifies the valves and integer-type function block data registered in the valve pattern monitor. A
maximum of 32 valves and pieces of function block data can be specified. The following table lists
the contents that can be specified in this item.
Table 3.8.5-1 Contents Specified in <function block data array> of the vpmoff Statement
Constant NO
Tag name +data item simplified YES
Generic name simplified+data item array element YES
Generic name array element+data item simplified YES
Generic name array element+data item array element YES
Generic name array whole+data item simplified YES
Tag name YES
• Only the valve name is specified in the vpmoff statement. The data item name does not need to
be specified. If the data item name is not specified, all data items of the valve are deleted.
The scripting method of <function block data array> is the same as that of a group assignment
statement or that of <variable array> in the compare statement. However, a local variable and a
constant cannot be specified in <function block data array>.
SEE For more information about a group assignment statement and compare statement, refer to:
ALSO 5.2, “Group Assignment Statement” in SEBOL Reference (IM 33J05L20-01EN)
5.3, “compare Statement” in SEBOL Reference (IM 33J05L20-01EN)
<error variable>
Specifies a local variable (simple variable or array element) where an error code is stored. The whole
array cannot be specified. A zero (0) is stored in this variable if no error occurs.
<label>
<error identifier>
Specifies a local variable or a constant to identify the location where the error is generated in the
Detailed vpmoff Statement

Detailed information on the vpmoff statement, such as operation at statement execution, is given
below.
• A maximum of 32 valves (function blocks) and pieces of data (function block data) can be
registered on one line (arrays are tabulated for each array element).
• If the vpmoff statement has been completed properly, the valves (function blocks) and data
(function block data) are deleted from the valve pattern monitor. If an error occurs in this
statement execution, no valve and data is deleted.
• Even if an unregistered valve is specified in the vpmoff statement, no error will result at
execution of the statement.
Script Example of the vpmoff Statement: <function

block data array>
drive [V1,V2 == 2,1]

delay 1000
vpmon [V1.PV.MV,V2.PV.MV == 2:0,2:0,1:0,1:0]

! V1.PV,V1.MV,V2.PV,V2.MV are registered.
......
vpmoff [V1.PV]
! V1.PV registration is deleted.
......
vpmoff [V2]
! V2.PV,V2.MV registration is deleted.
......
Recovery from Alarm by the vpmoff Statement
If the valve and function block data where an abnormality occurs are deleted by executing the
vpmoff statement, the valve pattern monitor is recovered from an alarm.
The alarm recovery timing of the valve pattern monitor will synchronize to its processing timing on
the basic cycle immediately after the valve and function block data have been deleted. It is not
identical to the execution timing of the vpmoff statement.
SEE For more information about the relationship between valve (function block) and data (function
ALSO block data) deletion and alarm recovery, refer to:
3.8.3, "drive vpmoff Statement"
3.8.6 vpmreset Statement Page 1 of 1
3.8.6 vpmreset Statement

If the vpmreset statement is executed, all the valves (function blocks) and data (function block data)
that have been registered in the valve pattern monitor are deleted.
vpmreset Statement Format

The following shows the format of the vpmreset statement.
Figure 3.8.6-1 vpmreset Statement Format
<error variable>
Specifies a local variable where an error code is stored. A zero (0) is stored in this variable if no
error occurs.
<label>
<error identifier>
Specifies an identifier to identify the location where the error is generated in the error processing
unit by a local variable or a constant.
Detailed vpmreset Statement

Detailed information about the vpmreset statement such as operation at statement execution is
given below.
• No valve is registered in the valve pattern monitor.
• The unit keeps the same the owner of the valve pattern monitor.
• Recovery from all alarms will be made while changing the value of valve pattern monitor’s data
item ALRM to “NR.” The alarm recovery timing of the valve pattern monitor will synchronize to its
processing timing on the basic cycle immediately after the vpmreset statement has been
executed. It is not identical to the execution timing of the vpmreset statement.
The values of data items after execution of the vpmreset statement are as follows:
• The value of data item BSTS of the valve pattern monitor will not change.
• The valve pattern monitor data items, SGNLTAG, SGNLITEM, VPTNTAG, VPTNITEM, DATATAG,
DATAITEM, TYPETAG, TYPEITEM, SGNLERRE, VPTNERRE, DATAERRE, TYPEERRE, ERRE and
HMAX are not changed.
• The values of NUM1 and NUM2 of the valve pattern monitor become 0.
• If the unit is not the owner of the valve pattern monitor, the vpmreset statement will result in an
error.

3.9 Inspection of Data Acquired from FCS Page 1 of 3
3.9 Inspection of Data Acquired from FCS

There are two data inspection modes in the valve pattern monitor: one is the present station data
inspection and another is other stations data inspection.
Acquisition and Inspection of Present Station Data

The valve pattern monitor acquires and inspects specified data about the valves (function blocks)
that have been registered once for each monitoring cycle. The FCS assigns multiple pieces of data to
all valve pattern monitors in the station, so that each valve pattern monitor inspects an even number
of pieces of data for each basic cycle.
The monitoring cycle is a numeric value which denotes the number of basic cycles required to
perform one cycle of a monitoring process. The value of a monitoring cycle denotes that the valve
pattern monitor will perform data acquisition and inspection once within that number of basic cycles.
If the monitoring cycle is 5, for example, one cycle of the monitoring process is performed during 5w
basic cycles (the FCS acquires data once for one basic cycle).
Calculating the Number of Pieces of Data

For each basic cycle, it monitors the present station data with the number of pieces (rounded-up
integer) which are obtained by dividing the total number of data by the monitoring cycle (number of
basic cycles).
Data Inspection by Valve Pattern Monitor

The valve pattern monitor acquires a given amount of data every inspection execution timing and
inspects it.
For example, assume that one valve pattern monitor monitors 320 valves, the valve pattern monitor
acquires 64 pieces of data for each basic scan cycle (64 x 5 = 320) to check data, it is shown as
follows.
Figure 3.9-1 Present Station Data Acquisition and Inspection: One Active Valve Pattern Monitor
Next, assume that three valve pattern monitors are activated and each of them inspects 64 valves.
The three valve pattern monitors sequentially acquire and inspect data on each basic cycle, as
shown below.
Figure 3.9-2 Present Station Data Acquisition and Inspection: Three Active Valve Pattern
Monitors
Acquisition and Inspection of Other Station Data

The system requires data acquisition of other stations at the beginning of basic cycles. The valve
pattern monitor inspects the data on the first process timing.

For example, assume that two valve pattern monitors reside in FCS1. The VPM201 monitors the
valves in FCS2 and the VPM301 monitors the valves in FCS3. In this case, the FCS1 requires data
acquisition of FCS2 and FCS3 at the beginning of basic cycles, as shown below.
Figure 3.9-3 Data Acquisition of Other Stations
In the above condition the data acquisition of FCS2 has been completed prior to the processing
timing of VPM201 which has the same basic cycle, and therefore the VPM201 inspects the data of
FCS2 on the first processing timing. Data acquisition of FCS3 has been completed after the
processing timing of VPM301, and therefore the VPM301 inspects the data of FCS3 on the
processing timing of the next basic cycle.
Data Acquisition of Other Stations

To acquire data from other stations, the system totalizes the number of pieces of data from other
stations which all active valve pattern monitors supervise, at the beginning of basic cycles. It
acquires other station data with the number of pieces (rounded-up integer) which are obtained by
dividing the total number of pieces of data by the monitoring cycle (number of basic cycles). The
maximum number of pieces of data that the FCS can acquire at the beginning of basic cycles must
be 128.
If designing a application program for a valve pattern monitor, set the number of pieces of data to
be acquired for one basic cycle to a maximum of 128.
There may be a case where more than 128 (the maximum 256) pieces of data can be acquired for
one basic cycle. (If the number obtained by dividing the total number of pieces of acquired data by
the monitoring cycle is over 128, the acquisition requirement for the excess number of pieces of
data is made after the 128 pieces of data have been acquired.) However, the number of pieces of
data that can be acquired depends on the execution amount of other applications, and therefore the
excess pieces of data may or may not be acquired.
The number of pieces of data from other stations that are actually inspected in the monitoring cycle
can be checked by the data item, NUM2CHK, of the valve pattern monitor.
Even if the number of pieces of data from other stations that can be acquired for one basic cycle is
less than 128, a “monitoring cycle + one basic cycle” period may be required to detect any
abnormality in other stations. This is because there is a time period between data acquisition
requirement for other stations and data acquisition completion.
Number of Pieces of Data Actually Acquired in Other

Stations
Other station data differs in the number of pieces of data actually acquired, depending on the valve
pattern monitor without the alarm check function and that with the alarm check function. Detailed
information is given below.
No Alarm Check Type (VPM64, VPM128, VPM256, VPM512)

For the valve pattern monitor without alarm check function, the number of pieces of data actually
acquired is identical to that of other stations registered. Specifically, the number of pieces of data
acquired is identical to the NUM2 data item of the valve pattern monitor.
Alarm Check Type (VPM64A, VPM128A, VPM256A, VPM512A)

For the valve pattern monitor with alarm check function, the number of pieces of data actually
acquired is identical to the total of the number of pieces of data in the other stations registered and
the value of the ALRM data item . Specifically, the number of pieces of data acquired is identical to
the sum of SUM2 and the number of registered tag names.
One ALRM data item value is acquired every tag name.
Examples of the number of pieces of data actually acquired are shown below:
• If vpmon [TAG1.PV,TAG1.MV] is specified, three pieces of data, TAG1.PV, TAG1.MV, and
TAG1.ALRM are acquired.
• If vpmon [TAG2.PV,TAG3.PV,TAG3.MV] is specified, five pieces of data, TAG2.PV, TAG2.ALRM,
TAG3.PV, TAG3.MV and TAG3.ALRM are acquired.
3.10 Builder Items for Creating Application Program Page 1 of 1
3.10 Builder Items for Creating Application

Program
For creating application programs, it is necessary to specify the builder definition items.
Option Program Name

The valve pattern monitor is an optional FCS function. Specify “VPMON” for “Option Program Name”
on the property sheet of the FCS.
Valve Pattern Monitor Block

The following table lists the builder definition items for the valve pattern monitor block, which are
defined by the control drawing builder.
Table 3.10-1 Builder Definition Items for Valve Pattern Monitor Block
Type of item Builder definition item Specification range Default

Tag name 16 or fewer alphanumeric characters -
Tag comment 24 one-byte characters or less -
Kind of tag mark 1 to 8 2
Common item Security level 1 to 8 4
Scan cycle Unspecified -
Processing timing Basic scan cycle fixed -
Message bypass for changing status With/without (*1) With
Alarm process Alarm processing level 1 to 16 2 (all middle)
*1: If the message bypass is set to “without,” a message is output. However, for status modification, such
as “START←RUN” using the vpmstart statement and “RUN or PAUS←STOP,” due to the unit
termination no message is output, irrespective of the “without” setting.
The builder definition items for the valve pattern monitor block can be modified using the online
maintenance function.
3.11 Example for Creating Application Program Page 1 of 4
3.11 Example for Creating Application Program

Before using the valve pattern monitor create an application program of operation to control it from
valve registration to monitoring termination. In addition, to signal execution reception processing
any time, create an application program of monitoring operation.
Application Programs of Operation and Monitoring

Operation
Create application programs for operating the valve patterns, as an example of application program.
The position of these application programs in the system is shown below.
Figure 3.11-1 Position of Application Programs to be Created
Operation and monitoring operation are described below.
Operation
This is a sequence which is started from the unit procedure and can execute SEBOL statements
specific to the valve pattern monitor. The unit procedure is a control group configured by one or
more operations.
Monitoring operation
This is a sequence which allows interrupt processing (signal reception processing) to be executed
immediately upon reception of the signal (VPMSIG). To create the application program of this
sequence, specify “independent” which allows signal reception at any time.
SEE For more information about unit procedure, refer to:

Interrupt Processing by Monitoring Operation
The operation does not always receive the signal, as described later. If the signal has not been
received, signal transmission is assumed to fail and the valve pattern monitor generates the SGNL
alarm.
Create an application program for monitoring operation which always resides as the signal reception
sequence so that the signal “VPMSIG” can always be received from the valve pattern monitor. Also,
specify “independent” for the valve pattern monitor there is no pause.
In the following cases, the interrupt processing by operation may not be performed upon signal
reception and signal reception itself cannot be made by operation.
Signal Reception Cannot be Performed since it is Paused.

If “independent” is not specified for the operation, signal reception is paused when the unit is
paused. The operation can receive the signal while it is paused, but cannot execute the interrupt
processing on the timing of signal reception. Specifically, unless the block status of the operation is
changed from “PAUS” to “RUN,” interrupt processing cannot be performed.
If “independent” has been specified for the monitoring operation, the monitoring operation
continues to be run while the unit is paused. It can execute interrupt processing immediately upon
reception of the signal.
Signal Reception Cannot be Performed due to Checking of the

Transition Condition.
While the unit checks the transition condition, both operations before and after the transition
condition are paused, and therefore the signal cannot be received.
Figure 3.11-2 Status at Checking of Transition Condition
Signal Reception Cannot be Performed since the Unit is in the

SEMI Mode.
If the unit is in the SEMI mode and is paused at the beginning of step (unit’s status is “SUSPEND”),
the signal cannot be received since the operation in that step is not started.
Figure 3.11-3 Pause due to SEMI Mode
Program Example of Operation

The following example shows a program in which the operation secures the valve pattern monitor
with the vpmstart statement, and then registers the valves to be monitored in the valve pattern
monitor with the vpmon statement.
.....
vpmstart VPM01
drive [V301,V302 == 1,1]
delay 1000
drive [V701,V702 == 0,0]
vpmon [V301.PV,V302.PV == 1:10,1:10]
vpmon [V701.PV,V702.PV == 0:0,0:0]
......
Program Example of Monitoring Operation

The following example shows an application program in which the monitoring operation receives the
VPMSIG signal.
In this program, if the signal parameter is 10 and if the present unit is being run, the present unit is
paused at reception of the VPMSIG signal. Otherwise, the operator guide message is output.
char*16 tango,item
if (lreadpara(1) == 10 AND %%.BSTS == "RUNNING") then

VPM03.BSTS = "PAUS" ! Pauses the valve pattern monitor.
%%.BSTS = "PAUS" ! Pauses the present unit.
return
***Even if the present unit is paused, the monitoring operation with
***"independent" specified continues the interrupt signal processing.
***Then, return needs to be entered.
end if
tango = creadpara(3) ! Tag name

item = creadpara(4) ! Data item
switch (creadpara(2)) ! Type of abnormality

"VPTN":
opeguide"%s.%s valve pattern is inconsistent (error code: $%04X)",\
tango,item,lreadpara(5)
"DATA"
opeguide "%s.%s data cannot be read (error code: $%04X)",\
"TYPE"
opeguide"%s.%s is not integer-type data (error code: $%04X)",\
end switch
return
Program Example of “Pause” for PAUS Modification

Post-Processing
Create an application program in which the operation executes “PAUS Modification Post-processing”
if the value of the unit data item BSTS is modified to “PAUS.” In the “Pause” program, the value of
the valve pattern monitor’s data item BSTS is modified from “RUN” to “PAUS,” using an assignment
statement. If the value of data item BSTS changes to “PAUS,” the valve pattern monitor pauses data
acquisition and inspection. At this time, valve registration is retained.
The following shows an example of the “Pause” program.
<valve pattern monitor>.BSTS = "PAUS"
If the group assignment statement is used in place of the assignment statement, assignment with
error check can be performed.
unit ierr
......
[VPM03.BSTS = "PAUS"] ierr
if (ierr <> 0) then ! Processing if an error is detected.
end if
......
To restart monitoring, modify the value of the valve pattern monitor’s data item BSTS from “PAUS”
to “RUN.”
<valve pattern monitor>.BSTS = "RUN"
Relationship between Pause and Alarm Status

If the paused valve pattern monitor is restarted, recovery from all alarms in the valve pattern
monitor will be made and the value of ALRM will be “NR.” The alarm recovery timing of the valve
pattern monitor will synchronize to its processing timing on the basic cycle immediately after the
value of data item BSTS is changed from “PAUS” to “RUN.”
• To re-execute monitoring, modify the value of the valve pattern monitor’s data item BSTS
from “PAUS” to “RUN.”
• The values of SGNLTAG, SGNLITEM, VPTNTAG, VPTNITEM, DATATAG, DATAITEM, TYPETAG, and
TYPEITEM in the valve pattern monitor are not changed.
• The values of SGNLERRE, VPTNERRE, DATAERRE, TYPEERRE, and ERRE in the valve pattern
monitor are not changed.
3.12 Specifying Processing Timing Page 1 of 1
3.12 Specifying Processing Timing

The processing timing of the valve pattern monitor can be specified by considering the timing of
running the control drawing that contains it.
Specifying the Processing Timing

The processing timing of the valve pattern monitor corresponds to that of a function block for which
the normal basic cycle is specified. If the processing timing of the valve pattern monitor within the
basic cycle needs to be delayed beyond that of the function block to be monitored, observe the
following procedure.
• Bring the valve pattern monitor into the specific control drawing.
• The control drawings run in numerical order. If a control drawing contains the valve pattern
monitor, assign a high number to it.
SEE For more information about the function block processing timing, refer to:
ALSO 7., “Process Timing” in Function Blocks Overview (IM 33J15A20-01EN)
3.13 Using Simulation Programs Page 1 of 1
3.13 Using Simulation Programs

Simulation function executes the simulated operation to test a valve without collecting the valve’s
data. This function may only be applied for testing valve pattern monitor. Setting or cancelling of the
simulation mode can be transferred by the setpoint value of the data item SIMM of the simulation
switch.
Using the Simulation Programs

The valve pattern monitor is provided with a simulation function. This simulation function may only
be applied for testing the valve pattern monitors. To use this simulation function, set the value of
data item SIMM so the valve pattern monitor is put in the simulation mode.
Setting the Simulation Mode

To put the valve pattern monitor in the simulation mode on tuning view, set the data item SIMM of
the simulation switch to 1.
Canceling the Simulation Mode

To cancel the simulation mode of the valve pattern monitor on tuning view, set the data item SIMM
of the simulation switch to 0.
If the valve pattern monitor is put in the simulation mode during execution, it stops data acquisition
and inspection (valve monitoring).
Alarm Status in the Simulation Mode

Even if you put the valve pattern monitor in the simulation mode, the alarm status will not change.
However, if the value of the valve pattern monitor’s data item BSTS is changed from “PAUS”
to “RUN,” recovery from all generated alarms will be made and the value of data item ALRM will
change to “NR,” even if the valve pattern monitor is in the simulation mode.
4. Offsite Block Page 1 of 5
4. Offsite Block
The offsite block (*1) is a function block used for batch blending and shipment control performed
offsite at oil refineries and other plant facilities.
Offsite blocks include the Batch Set Control Block (FSBSET) and the Blending Master Control Block
(BLEND).
This chapter explains the detail of functions available with each offsite block.
*1: Offsite block can be used in FCSs except PFCS.
Offsite Block
The offsite function block performs blending control and shipment control offsite by controlling flow
rate and batch quantity.
This block is used to implement batch shipment control and blending shipment control of products
offsite in combination with motor control blocks (MC-2, MC-2E, MC-3, and MC-3E) and switch
instrument blocks (SIOs) and enhanced switch instrument block.
Figure 4-1 Example of Application with Offsite Blocks
Relationship between Offsite Blocks and JOB Controllers

Blending, shipment and other work (jobs) performed offsite are controlled with offsite blocks, motor
control blocks (MC-2, MC-2E, MC-3, and MC-3E), switch instrument blocks and enhanced switch
instrument blocks in the FCS. These function blocks operate via commands and operation from JOB
controllers being set under the supervisory computer. They can also be operated and monitored
from an HIS that serves as a backup supervisory computer.
Figure 4-2 Relationship between Offsite Blocks and JOB Controllers
Overview of Offsite Block Control

The offsite block is used mainly for batch loader control, tank blending control and direct blending
shipment control.
Batch Loader Control

Batch loader control is implemented with the FSBSET control block.
The FSBSET is operated by commands from an operator or supervisory computer, and controls flow
rate and batch quantity according to the flow rate signals received from positive displacement
flowmeters.
The figure below shows an example of FSBSET application for batch loader control:
Figure 4-3 Example of Batch Loader Control
Tank Blending Control

FSBSET and BLEND control blocks are used for tank blending.
The FSBSET receives commands from the BLEND, and controls flow rate according to the flow rate
signals from positive displacement flowmeters.
The BLEND receives the ratio of each component from the supervisory computer, and multiplies it by
its own flow rate setpoint (SV) at the tank entry point. It then sets the result as an SV for the
FSBSET of the corresponding component. The BLEND also accumulates the instantaneous flows
(PVs) obtained from each of the component FSBSET blocks, and performs batch control based on
the result.
The figure below shows an example of tank blending application using FSBSET and BLEND control
blocks:
Figure 4-4 Example of Tank Blending Control
Direct Blending Shipment Control

For direct blending shipment control performed offsite, batch quantity is controlled by the FSBSET
blocks or BLENDs located at the port.

The FSBSET control block at the port receives commands from an operator or supervisory computer,
and controls flow rate and batch quantity according to the flow rate signals from positive
displacement flowmeters at the port.
The BLEND control block at the port receives the port blending ratio for each component from the
supervisory computer, and multiplies it by its own port flow rate setpoint (SV). It then sets the result
as a port blending SV for the corresponding component FSBSET. The BLEND also accumulates the
instantaneous flows (PVs) obtained from each of the component FSBSET blocks used for port
blending, and performs batch control based on the result.
The BLEND used for blend header shown in Figure, “Example of Direct Blending Shipment Control”
totalizes the flow rate setpoints (SVs) of the FSBSET blocks or BLENDs located downstream of the
blend header at the port, and sets the sum as its own SV. (The BLEND can also be set by the builder
to obtain a totalized instantaneous flow (PV) for the FSBSET blocks or BLENDs at the port and set
the sum as its own SV.) It then multiplies the SV by the ratio for each component specified by the
supervisory computer, and sets the result as an SV for the corresponding component FSBSET.
Figure 4-5 Example of Direct Blending Shipment Control
4.1 Batch Set Control Block (FSBSET) Page 1 of 1
4.1 Batch Set Control Block (FSBSET)

The FSBSET control block provides functions necessary for batch loader control, blending control,
and X% preset MV control.
Batch Loader Functions - FSBSET

The FSBSET provides all the functions required for controlling flow rate and batch quantity at a port
or the like.
For flow rate control, the block can calculate corrections such as ASTM on pulse flow-rate signals
from positive displacement flowmeters or turbine flowmeters; it also performs PI control calculations
to maintain the flow as specified by the setpoint.
Batch program control provides gradual flow ramp-up and ramp-down functions. The block also
provides automatic early-point detection and emergency-stop processing functions necessary for
batch control.
Batch Blending Control Functions - FSBSET

The FSBSET is used for in-line blending to control flow rate for each component. When performing
PI flow rate blending control, according to a setpoint demand signal and commands from the Blend
master controller (BLEND) block, one batch set control block is used for each component whose flow
rate is to be controlled.
In this case, the FSBSET can calculate corrections, such as ASTM, on the pulse flow-rate signals
from positive displacement flowmeters or turbine flowmeters; it also performs PI control calculations
to keep accumulated deviations at or near zero (termed PI blending calculations).
The FSBSET can also be set on the builder to perform instantaneous deviation control instead of
accumulated deviation control.
X% Preset MV Control Functions - FSBSET

The FSBSET can be used not only to perform flow or batch control, but it can also be used to
provide a fixed output. On receiving a start or restart command, it outputs the fixed output. The
fixed output (MV) may be entered in the tuning parameter NCVV. If an emergency stop or abort
command is received, the block clamps the output (MV) at zero (valve closed).
4.1.1 Operation for Batch Loader Control - FSBSET Page 1 of 2
4.1.1 Operation for Batch Loader Control - FSBSET

During batch loader control, the FSBSET performs CV-kick, release of initial flow rate control, early-
point detection processing and pre-batch processing.
The operation of the FSBSET is indicated by a sequence of control steps.
Operation for Batch Loader Control - FSBSET

The figure below shows the flow of FSBSET operation during batch loader control:
Figure 4.1.1-1 Operation Overview of Batch Loader Control
The basic operation of the FSBSET during batch loader control is explained below. The explanations
are based on the above figure.
• At the start of batch loader control, the block mode of the FSBSET is changed to AUT or CAS via
a JOB controller or by an operator. A start command is then sent to the FSBSET.
• When the FSBSET Block receives the start command with CV-kick (CMND=1), the control step
proceeds to ZONE10, initializing an alarm, integral and others of the FSBSET block and opening a
control valve (CV) by a preset degree. This is called CV-kick. After CV-kick, the control step
proceeds to ZONE1.
• When the SET-UP waiting time (t0) elapses following the transition to ZONE 1, SET-UP is started.
In SET-UP, the current flow rate setpoint (SV) is ramped at a preset rate until it reaches the
initial flow rate setpoint (SVL) or final flow rate setpoint (SVH), while PI control is carried out
based on the SV.
• When the waiting time for the end of SET-UP to initial flow rate (T1) elapses after the current
4.1.1 Operation for Batch Loader Control - FSBSET Page 2 of 2
flow rate setpoint (SV) reached the initial flow rate setpoint (SVL), the control step proceeds to
ZONE 2.
• When the totalized flow (SUM) reaches the initial (totalized) flow setpoint (ILST), or when an
operator directs the release, the control step returns to ZONE 1, and SET-UP is performed to
ramp the current flow rate setpoint (SV) at a preset rate until it reaches the final flow rate
setpoint (SVH).
• When the waiting time for the end of SET-UP to final flow rate (T2) elapses after the current flow
rate setpoint (SV) reached the final flow rate setpoint (SVH), the control step proceeds to ZONE
3.
• When the totalized flow (SUM) reaches the batch setpoint (BSET) less the pre-batch quantity and
predicted leakage value (VL), the control step proceeds to ZONE 4. The block status changes to
measure tracking, in which the current flow rate setpoint (SV) is caused to follow the momentary
flow (PV), and the control valve is throttled gradually at a preset rate.
• When the flow rate setpoint (SV) drops to the flow rate setpoint for pre-batch (SVPR) during
measure tracking, the control step proceeds to ZONE 5. At this point, the measure tracking
status is released and the control mode returns to normal PI control.
• When the totalized flow (SUM) reaches the batch setpoint (BSET) less the predicted leakage
value (VL), the control step proceeds to ZONE 6 and the control valve is shut tightly. Calculation
for the totalized flow (SUM) will continue after the valve is tightly shut.
• When the waiting time for batch end (t3) elapses following the transition to ZONE 6, the totalized
flow (SUM) at the end of t3 is stored as the previous totalized flow. Batch-end processing is
performed, and the control step proceeds to ZONE 7.
• When the waiting time for completion of end processing (t4) elapses following the transition to
ZONE 7, the block mode changes to MAN and the control step returns to ZONE 0. This completes
a batch loader control cycle.
• If an emergency stop command (CMND=4) is issued or a critical alarm is detected during the
batch cycle, the control step proceeds to ZONE 8 and the control valve shuts off in steps. When
the manipulated output value (MV) drops to 0 during the step shut-off process, the control step
proceeds to ZONE 9. This changes the block status to EMST END (emergency stop end).
• If a command for restart with CV-kick (CMND=2) is received in the EMST END state, the control
step proceeds to ZONE 11 and the CV opens by a preset amount. Then, the control step returns
to ZONE 1 and batch loader control is restarted.
The following operations are not shown in the above figure:
• When a command for start without CV-kick (CMND=11) is received, the control step proceeds to
ZONE 12. Initialization processing for the FSBSET is performed and the control step returns to
ZONE 1.
• When a command for restart without CV-kick (CMND=12) is received, the control step proceeds
to ZONE 13 then returns to ZONE 1 without implementing CV-kick.
• During SET-UP in ZONE 1, if initial flow rate control is not specified or when the totalized flow
(SUM) reaches or exceeds the initial totalized flow setpoint, SET-UP is performed based on the
final flow rate setpoint (SV).
• If an abort command (CMND=3) is received in the EMST END state, the control step returns to
ZONE 6 and batch end processing is performed, starting from the operation in ZONE 6 explained
above.
4.1.2 Operation for Batch Blending Control - FSBSET Page 1 of 2
4.1.2 Operation for Batch Blending Control - FSBSET

During batch blending control, the FSBSET performs CV-kick and PI blending control.
The operation of the FSBSET is indicated by a sequence of control steps.
Operation for Batch Blending Control

The figure below shows the flow of FSBSET operation during batch blending control.
Figure 4.1.2-1 Operation Overview of Batch Blending Control
The basic operation of the FSBSET during batch blending control is explained below. The
explanations are based on the above figure.
• When a component start command (CMND=21) is received from a supervisory loop (normally a
BLEND block), the control step proceeds to ZONE 20 and the control valve opens by a preset
amount (CV-kick). Initialization processing for the FSBSET, such as alarm, totalization and
accumulated deviation processing, will also be performed.
• When the initialization processing is completed, the control step proceeds to ZONE 22 and PI
blending calculation is performed according to the flow rate setpoint (SV) specified by the
supervisory loop.
• When the status of the supervisory loop changes to batch end, a command to wait for
component END (CMND=26) is sent from the supervisory loop. When this command is received,
the control step proceeds to ZONE 23 and the control valve shuts tightly.
• When a component release command (CMND=23) is received from the supervisory loop, the
control step proceeds to ZONE 26 and the control valve shuts tightly. Then, the block mode
changes to MAN and the control step returns to ZONE 0. This completes a batch blending control
cycle.
• When subjected to an emergency stop, the supervisory loop sends a component EMST command
(CMND=24). When this command is received, the control step proceeds to ZONE 24 and the
control valve shuts tightly.
• If a component cut-off command (CMND=25) is received from the supervisory loop while control
is in ZONE 22, the control step proceeds to ZONE 25 and the control valve is throttled at a preset
rate. When the manipulated output value (MV) drops to 0 or below, the control step proceeds to
4.1.2 Operation for Batch Blending Control - FSBSET Page 2 of 2
ZONE 26 and the control valve shuts tightly. Then, the block mode changes to MAN and the control
step returns to ZONE 0. This completes a batch blending control cycle.
The figure below shows the flow of component release (cut-off):
Figure 4.1.2-2 Component Cut-off (Batch Blending Control)
4.1.3 Operation for X% Preset MV Control - FSBSET Page 1 of 1
4.1.3 Operation for X% Preset MV Control - FSBSET

During X% preset MV control, the FSBSET controls the opening of control valve (fixed at X% or fully
closed) according to the command received from outside the block.
Operation for X% Preset MV Control - FSBSET

The figure below shows the operation of the FSBSET during X% preset MV control:
Figure 4.1.3-1 Operation Overview of X% Preset MV Control
The basic operation of the FSBSET during X% preset MV control is explained below. The
• When performing X% preset MV control, the block mode of the FSBSET is set to AUT or CAS via
a JOB controller or by an operator. Then, a command to start X% preset MV control is issued.
• When the FSBSET receives a command to start X% preset MV control (CMND=41), the control
step proceeds to ZONE 40 and the manipulated output value (MV) changes from zero to the
value set by the NCCV data item. Then, the control step proceeds to ZONE 42.
• When the FSBSET receives a command to stop X% preset MV control in an emergency
(CMND=44), the control step proceeds to ZONE 44 and the manipulated output value (MV) drops
to zero.
• When the FSBSET receives a command to restart X% preset MV control (CMND=42), the control
step proceeds to ZONE 41 and the manipulated output value (MV) changes from 0 to the value
set by the NCCV data item. Then, the control step proceeds to ZONE 42.
• When the FSBSET receives a command to end X% preset MV control (CMND=43), the control
step proceeds to ZONE 43 and the manipulated output value (MV) drops to zero. Then, the block
mode changes to MAN and the control step returns to ZONE 0. This completes an X% preset MV
control cycle.
4.1.4 Configuration of Batch Set Control Block (FSBSET) Page 1 of 2
4.1.4 Configuration of Batch Set Control Block (FSBSET)

This section explains the function block diagram of the FSBSET control block and connection
destinations for the I/O connection terminals.
Function Block Diagram of the Batch Set Control Block

(FSBSET)
▼ Connection
FSBSET function block consists of input processing, control computation (for flow rate control and
batch control), output processing, and alarm processing. A diagram of the FSBSET function block
with all the functionalities except the alarm processing is shown as follows:
Figure 4.1.4-1 Function Block Diagram of Batch Set Control Block (FSBSET)
SEE For more information about input processing, refer to:

ALSO 4.1.5, "Input Processing of Batch Set Control Block (FSBSET)"
For more information about output processing, refer to:
4.1.6, "Output Processing of Batch Set Control Block (FSBSET)"
I/O terminals of the Batch Set Control Block (FSBSET)

The input and output terminals of FSBSET block and the connection methods of the terminals are
shown in the following table.
Table 4.1.4-1 Types of Connection and Connection Destinations of I/O Terminals for Batch Set
Control Block (FSBSET)
Type of Connection(*1) Connection Destination(*1)

Terminal Name
Data Data Terminal Process Software Function
4.1.4 Configuration of Batch Set Control Block (FSBSET) Page 2 of 2
reference setting connection I/O I/O block

IN Measuring input x N/A N/A x N/A x
OUT Control output N/A x x x N/A x
Compensating
TMI x N/A Cond. x N/A x
temperature input
*1: x: available
N/A: not available
Cond.: available only from the switch block
4.1.5 Input Processing of Batch Set Control Block (FSBSET) Page 1 of 7
4.1.5 Input Processing of Batch Set Control Block

(FSBSET)
The input processing items of the FSBSET include input reading, pulse weight normalization,
correction before temperature compensation, temperature compensation, correction after
temperature compensation, instantaneous flow computation, totalization and simulation.
Input Processing of the Batch Set Control Block

(FSBSET)
The items of input processing for the Batch Set Control Block (FSBSET) are shown as follows:
Table 4.1.5-1 Table of Input Processing Items for Batch Set Control Block (FSBSET)
Provided
No. Processing Item Remarks
(*1)
1 Pulse train input reading x
2
3 Analog input reading x
4 Pulse normalization (not normalized) x
According to pulse weight
5 Puss normalization (normalized) x
normalization factor
Correction before temperature compensation -
6 x
0 (no correction)
Correction before temperature compensation - Flow rate correction before
7 x
1 (with correction) temperature compensation
8
9
Correction after temperature compensation -0
10 x
(no correction)
Correction after temperature compensation -1 Flow rate correction after temperature
11 x
(with correction) compensation
12
13
Temperature compensation -0 (no
14 x
compensation)
Temperature compensation -1 (new ASTM)
15 x
for crude oil
16 x
for fuel oil
17 x
for lubrication oil
18 Temperature compensation -4 (old ASTM) x
19 Temperature compensation -5 (VCF entry) x
20
21
22
23
24
25
26
27
28
29
30 Totalized value (uncorrected, non-reset) x SUM1
31 Totalized value (corrected, reset) x SUM
32 Totalized value (corrected, non-reset) x SUM2
33 Input filter x
Simulation (specified for each flow controller
34 x
block)
*1: x: available
Input Reading - FSBSET

▼ Input Connection Specification, Totalizer Shutdown during Non-Control
Normal Input Reading

When the “Input Signal Type” on the Function Block Detail Builder is “Pulse,” the FSBSET block
reads pulse train inputs from process I/O.
The volumetric flow pulse (QR1) between ΔT seconds of control cycle is calculated from the
difference in the number of pulses to be read this time and previously.
When the “Input Signal Type” is “Analog,” 0 to 100 % of input signals is converted to the PV scale
low limit (SL) to PV scale high limit (SH).
The “Input Signal Type” parameter of the builder is set as follows:
Input Signal Type: Select “Pulse” or “Analog.”
The default is “Pulse.”
Whether or not pulse train input will be added to non-reset totalized values (SUM1, SUM2) and
batch-type totalized value (SUM) while the FSBSET is in the non-control status (block mode: MAN,
and control step: ZONE 0) can also be specified in the Function Block Detail Builder.
The “Totalizer Shutdown during Non-control” parameter of the builder is set as follows:
Totalizer Shutdown during Non-control: Select “Yes” or “No.”
The default is “No.”
The figure below shows the processing flow of input data:
Figure 4.1.5-1 Processing Flow of Input Data
If the IN terminal of the FSBSET function block is not connected to any place,
the data status of SUM will become BAD.
Input Reading During Simulation
When simulation is specified for the FSBSET, the flow rate for the closed-loop test is deduced from
the opening (MV) of the current control valve (CV).
Figure 4.1.5-2 Calculation of Flow Rate During Simulation
Pulse Weight Normalization - FSBSET

▼ Pulse Weight Normalization Coefficient
Pulse weight correction is performed on the flow before temperature compensation (QR1). Input
pulses can be corrected using the following expression to calculate flow reading:
QR2=QR1 • pulse weight normalization factor
• Pulse weight normalization factor : setting data (L/P, i.e., liters per pulse, or CC/P)
3
• QR2 : flow after pulse weight normalization (L, i. e., liters, or CC, i. e. cm ).
The “Pulse Weight Normalization Coefficient” parameter of the Function Block Detail Builder is set as
follows:
Pulse Weight Normalization Coefficient: 0.000000 to 10000.00
The default is “1.000000.”
Correction Before Temperature Compensation - FSBSET

▼ Flow Rate Conversion Code Before Correction
Input pulses can be corrected as follows before temperature compensation.
QR3=CCX • QR2
QR3 : measured input pulse count
CCX : flow rate correction factor before temperature compensation
The “Flow Rate Conversion Code Before Correction” parameter of the Function Block Detail Builder is
set as follows:
Flow Rate Conversion Code Before Correction: Select “0 (No)” or “1 (Yes).”
The default is “0.”
Temperature Compensation - FSBSET

▼ Temperature Correction Code
Given a measured input pulse count of QR3, and a temperature T (°C) measured by another
function block, the QR4 compensated pulse count is determined as follows:
QR4=QR3 • VCF
QR4 : measured input pulse after temperature compensation
VCF : volume conversion factor
Temperature compensation code number (ICC)
0: No compensation
1: New ASTM (Crude oil) <New ASTM: ASTM D1250-80>
2: New ASTM (Fuel oil)

3: New ASTM (Lubrication oil)
4: Old ASTM
5: VCF input • QR3
The “Temperature Correction Code” parameter of the Function Block Detail Builder is set as follows:
Temperature Correction Code: Select “0,” “1,” “2,” “3,” “4” or “5.”
The compensation calculations are as follows:
New ASTM Compensation
where
VCF : the volume conversion factor (at 15 °C)
3
V15 : the volume (m ) at 15 °C
3
Vt : the volume (m ) at an arbitrary temperature t °C
3
ρt : the density (kg/m ) at t °C
3
ρ15 : the density (kg/m ) at 15 °C
αt : the coefficient of thermal expansion (°C-1) at 15 °C
Δt : the temperature difference of Δt=t-15 (°C)
K0, K1, A and B : Parameters (see the table below)
Table 4.1.5-2 Parameter for ASTM (New JIS Standards) Compensation
Parameter
3
Oil Types Range of Density (at 15 °C) kg/m
K0 K1 A B
Crude 610.5≤ρ≤1075.0 613.9723 0.0 ... ...
653.0≤ρ<770.25 346.4228 0.4388 ... ...
770.25≤ρ<787.75 ... ... -0.00336312 2680.3206
Fuel
787.75≤ρ≤838.75 594.5418 0.0 ... ...
838.75≤ρ≤1075.0 186.9696 0.4862 ... ...
Lubrication 800.0≤ρ≤1164.0 0.0 0.6278 ... ...
Old ASTM Compensation
Figure 4.1.5-3 Parameters for ASTM (Old JIS Standards) Compensation
Other Temperature Compensation Methods

When temperature compensation code “5” (VCF*F0) is selected in the Function Block Detail Builder,
the VCF can be set by an external calculation.
Correction after Temperature Compensation - FSBSET

▼ Flow Rate Conversion Code After Correction
The measured input pulse after temperature compensation (QR4) can be corrected as follows by
setting the correction calculation in the builder:
QR5 = CCY • QR4 (L or CC)
QR5 : Corrected flow rate/input pulse after temperature compensation
CCY : flow rate correction factor after temperature compensation
The “Flow Rate Conversion Code After Correction” parameter of the Function Block Detail Builder is
set as follows:
Flow Rate Conversion Code After Correction: Select “0 (No)” or “1 (Yes).”

Instantaneous Flow Computation - FSBSET

Based on the measured flow after compensation, the instantaneous flow (PV) is calculated as
follows. Note that the PV value is not stored if the data status is CAL:
In=QR5 • 3600/1000
PVn= (1 - α) In+ α • PVn-1
QR5 : flow value (in L or CC) after temperature compensation
PVn-1 : the previous PV value
In : the instantaneous flow rate, in KL/H or L/H, calculated from the pulse count
α : The filter constant (When “Pulse” is selected, the default is 0.5).
The PV value determined after filtering/compensation is used with the current SV value to calculate
instantaneous deviation PV-SV; this deviation is totalized during accumulated deviation control.
SEE For more information about the filter constant, refer to:
ALSO 3.2, “Digital Filter” in Function Blocks Overview (IM 33J15A20-01EN)
Totalizing Processing - FSBSET

The FSBSET totalizes the corrected flow rate/input pulse after temperature compensation (QR5) in
liters or cc’s into the totalizer SUM, as follows:
SUM =ΣQR5 (From batch start to end)
The FSBSET also provides the following totalizers:
• SUM1: Non-reset counter of uncompensated value
SUM1=ΣQR3 (Always totalized)
QR3 : measured input flow after pulse weight normalization
• SUM2: Non-reset counter of compensated value
SUM2 =ΣQR5 (Always totalized)
Number of SUM Digits - FSBSET

▼ Number of Digits for Indicating SUM
The number of SUM digits for each FSBSET block can be selected between 8 and 9.
This is set on Function Block Detail Builder.
Number of digits for indicating SUM: Choose [8] or [9].
The default setting is 8.
The following data items are subject to this setting.
SUM: Value of compensated summation
SUM1: Non-reset total value of uncompensated summation
SUM2: Non-reset total value of compensated summation
BSET: Batch Quantity Set Value
DLX1: The first alarm point of accumulated deviation.
DLX1: The second alarm point of accumulated deviation.
DSM: Instantaneous compensated flow rate
DVX: Accumulated deviation
ILST: End point of primary flow

VL: Predicted leak quantity
Simulation - FSBSET
▼ Non-Reset Totalizer Shutdown at SIM
A simulation can be specified for each FSBSET.
Set the tuning parameter as follows to change the mode to simulation:
SIMM≠0 (Set a value other than 0.)
The MV is not output to outside the block (i. e., it is not updated).
A simulated pulse equal to the input range multiplied by the output ratio is applied to the input.
The totalizing processing of non-reset counters (SUM1, SUM2) can be stopped or continued during
simulation via specification in the Function Block Detail Builder.
The “Non-reset Totalizer Shutdown at SIM” parameter of the Function Block Detail Builder is set as
follows:
Non-reset Totalizer Shutdown at SIM: Select “Yes” or “No.”
When the “Non-reset Totalizer Shutdown at SIM” parameter of the builder is set to “Yes,” the non-
reset counters (SUM1, SUM2) will not count in the simulation mode. However, the reset counter
SUM still counts irrespective of the setting of the parameter.
4.1.6 Output Processing of Batch Set Control Block (FSBSET) Page 1 of 2
4.1.6 Output Processing of Batch Set Control Block

(FSBSET)
The output processing items of the FSBSET include analog output, connection to the SET terminal of
another instrument block, output tracking and output velocity limiter.
Output Processing of the Batch Set Control Block

The table below shows the output processing items of the FSBSET block.
Table 4.1.6-1 Table of Output Processing Items for Batch Set Control Block (FSBSET)
No. Processing Item Provided (*1) Remarks

1 Analog output (4 to 20 m) x Control valve: used
2 Connection to the SET terminal of another function block x Control valve: used
3
4
5 Output tracking x
6 Output velocity limiter x
*1: x: available
Analog Output - FSBSET

The FSBSET can output to analog output modules. During output, the tight-shut function and full-
open function are automatically added to the manipulated output value (MV). The direction of
analog output can also be set.
Outputs to analog output modules are used to set data.
An MV in the range of 0 to 100 % is output from the OUT terminal.
Upon receiving an MV between 0 and 100 %, the analog output module outputs the corresponding
current between 4 and 20 mA to drive the control valve or other final control element.
Connection to the SET Terminal of Another Function

Block - FSBSET
The FSBSET sets an MV for the cascade setpoint (CSV) of the function block being connected, via
connection between its OUT terminal and the SET terminal of the function block.
Output Tracking - FSBSET

When the cascade loop connecting the FSBSET’s OUT terminal and the SET terminal of another
function block is open, then the block mode changes to initialization manual (IMAN). This activates
output tracking and causes the MV to agree with the value at the connection destination of the OUT
terminal.
Output Velocity Limiter - FSBSET

The output velocity limiter restricts the amount of change in output value acquired last time and this
time according to its setting value, in order to prevent abrupt change in output value. The output
4.1.6 Output Processing of Batch Set Control Block (FSBSET) Page 2 of 2
velocity limiter is an allowable amount of change in output value per scan period. When it becomes
active during manual operation, a non-restricted value is displayed, though the amount of change in
MV is restricted. Setting the “Output Velocity Limiter Bypass in MAN” to “No” prevents the output
velocity limiter from operating during manual operation. When the FSBSET block mode is in the
Tracking (TRK) mode, the Limiter does not work.
The Output Velocity Limiter and Output Velocity Limiter Bypass in MAN settings are specified as
follows in the Function Block Detail Builder:
• Output velocity limiter
A percentage value or a data item value in industrial scale unit within the range between 0 and
the MV scale span limit
The set value must be positive (effective digits: 6 digits).
The default is “100.0 %.”
• Output velocity limiter Bypass in MAN
Select “Yes” or “No.”
4.1.7 Alarm and Notification Processing of Batch Set Control Block (FSBSET) Page 1 of 7
4.1.7 Alarm and Notification Processing of Batch Set

The alarm and notification processing items of the FSBSET include leakage alarm, input failure,
deviation error, output failure and processing in response to an external EMST command.
Alarm and Notification Processing of the Batch Set

The table below shows the alarm processing items of the FSBSET block.
Table 4.1.7-1 Table of Alarm and Notification Processing Items for Batch Set Control Block
(FSBSET)
No. Processing Item Provided (*1) Remarks

1 Leakage alarm (LEAK) x
2 Input failure (IOP) x
3 Output failure (OOP) x
4 First-stage deviation error (DV1) x
5 Second-stage deviation error (DV2) x
6
7 Loss-of-pulse (NPLS) x
8
9 Alarm off (AOFS) x
10
11
12 External EMST command (EMST) x
13
14 Output stoppage (OUTS) x
15 Connection failure (CFN) x
16
17
18
19
20
*1: x: available
Leakage Alarm (LEAK) - FSBSET

▼ Leak Check, Detection Set Value
During the interval from the end of the current batch to the start of the next, flow rate calculation
and totalization continue to be performed. The FSBSET compares this totalized value and that at the
previous batch end (stored upon batch end). This is called “leak check.” If their difference exceeds
the setpoint for leakage alarm detection, the alarm status changes to LEAK. Leakage alarm detection
is performed only when the block mode is MAN and the control step is in ZONE 0.
To reset the leakage alarm and restart leakage checking, set Leak Reset tuning parameter (LRSW)
to “1.”
Leakage alarm detection can be enabled or disabled in the Function Block Detail Builder.
The “Leak Check” parameter of the builder is set as follows:
• Leak Check
The default is “Yes.”
The setpoint for leakage alarm detection is set in the Function Block Detail Builder.
The “Detection Set Value” parameter of the builder is set as follows:
• Detection Set Value
0.00 to 10000.00
Input Failure (IOP) - FSBSET

▼ Input Open Alarm
If an input card fails, the IOP alarm of the FSBSET Block appears as input failure.
If ASTM temperature compensation is specified and the IOP alarm of temperature loops appears, or
if data is referenced by input connection and the IOP alarm of the connected function block appears,
the IOP alarm of the FSBSET block also appears as input failure.
Output Failure (OOP) - FSBSET

▼ Output Open Alarm
If the output card fails or the output becomes otherwise abnormal, the alarm status changes to OOP.
Deviation Errors (DV1, DV2) - FSBSET

▼ Level-One Deviation Alarm, Level-Two Deviation Alarm
If a first-stage deviation error occurs in the instantaneous deviation or accumulated deviation, the
alarm status changes to DV1. If a second-stage deviation error occurs in the instantaneous deviation
or accumulated deviation, the alarm status changes to DV2.
If instantaneous deviation control is set as the deviation control type for FSBSET in the Function
Block Detail Builder, the DV1 and DV2 indicate instantaneous deviation errors.
If accumulated deviation control is set as the deviation control type for FSBSET in the Function Block
Detail Builder, the DV1 and DV2 indicate accumulated deviation errors.
The first-stage deviation alarm and second-stage deviation alarm can be enabled or disabled in the
builder.
The “Level-one Deviation Alarm” and “Level-two Deviation Alarm” parameters of the Function Block
Detail Builder are set as follows:
• Level-One Deviation Alarm
• Level-Two Deviation Alarm
Instantaneous Deviation Error

▼ Momentary Deviation Alarm Hysteresis
When the FSBSET is in the steps in which constant-flow control is performed (ZONE 2, ZONE 3 or
ZONE 5; also Zone 22 if specified in the builder), and if the instantaneous deviation exceeds the
corresponding alarm setpoint, the following processing is performed:
• First-step deviation: When DL1 < En, the alarm status is changed to DV1.
• Second-step deviation: When DL2 < En, the alarm status is changed to DV2.
Where
En : the instantaneous deviation
DL1 : the first-stage deviation alarm point
DL2 : the second-stage deviation alarm point
The instantaneous deviation alarm hysteresis can be specified for each function block in the builder.
The “Momentary Deviation Alarm Hysteresis” parameter of the Function Block Detail Builder is set as
follows:
• Momentary Deviation Alarm Hysteresis
0 to (SH-SL).
The default is a value equivalent to 1 %.
SH: Scale high limit
SL: Scale low limit
Accumulated Deviation Error

▼ Accumulated Deviation Alarm Hysteresis
When the current control step is ZONE 22, ZONE 23 or ZONE 24, and if the accumulated deviation
exceeds an alarm setpoint, the following processing is performed:
• First-step deviation: When DL1X < En, the alarm status is changed to DV1.
• Second-step deviation: When DL2X < En, the alarm status is changed to DV2.
Where
En : the accumulated deviation
DL1X : the first-stage deviation alarm point
DL2X : the second-stage deviation alarm point
The accumulated deviation alarm hysteresis can be specified for each function block in the builder.
The “Accumulated Deviation Alarm Hysteresis” parameter of the Function Block Detail Builder is set
as follows:
• Accumulated Deviation Alarm Hysteresis:
0.00 to 10000.00.
External EMST Command - FSBSET

When an emergency stop command (EMSW=1) is received, the FSBSET outputs an alarm (EMST)
and performs emergency stop processing (EMST processing).
Loss-of-Pulse Error - FSBSET

▼ Non-Incoming Pulse Alarm, Detection Mask Time, Detection Interval Time
If no pulses are received during loss-of-pulse detection processing within a preset period of time,
the data status changes to NPLS.
Loss-of-pulse detection processing is performed only during SET-UP (ZONE 1), flow rate control
(ZONE 2), STEADY (ZONE 3), EARLY (ZONE 4), PB control (ZONE 5), PI blending control (ZONE 22)
and X % Preset MV Control (ZONE 42).
No loss-of-pulse detection is executed if MV=0 or SV=0.
The figure below shows the processing flow of loss-of-pulse detection:
Figure 4.1.7-1 Loss-of-Pulse Detection Processing
The loss-of-pulse alarm can be enabled or disabled in the builder.

The “Non-incoming Pulse Alarm” parameter of the Function Block Detail Builder is set as follows:
• Non-incoming Pulse Alarm
The check mask time (t6) shown in Figure “Loss-of-Pulse Detection Processing” indicates the time
immediately after start or restart during which loss-of-pulse detection is stopped. The check mask
time is specified in the builder.
The “Detection Mask Time” parameter of the Function Block Detail Builder is set as follows:
• Detection Mask Time
0 to 10000 (unit: basic scan period).
The check time (t7) shown in Figure “Loss-of-Pulse Detection Processing” indicates the period during
which loss-of-pulse detection is performed. The check period is specified in the builder.
The “Detection Interval Time” parameter of the Function Block Detail Builder is set as follows:
• Detection Interval Time
If the ER bus interface modules (EB401) of KFCS2/KFCS/FFCS/FFCS-L, or RIO

bus interface modules (RB301) of FCS2/FCS are dual-redundantly configured,
when switching from one module to another, the pulse input may halt for a
few seconds. The detection interval time for the loss-of-pulse error should be
set with the following consideration.
• For RB301 (halt time: 1 or 2 seconds)
Detection interval time setting should be greater than 2.
• For EB401 (halt time: 2 or 3 seconds)
Detection interval time setting should be greater than 4.
SEE For more information about each control step, refer to:
ALSO 4.1.8, "Control Processing of Batch Set Control Block (FSBSET)"
Output Stoppage Alarm - FSBSET

▼ Output Shutdown Alarm
When the block mode of a function block downstream in a cascade connection changes from CAS to
non-CAS, or when the cascade path is disconnected by a switch or the like, the alarm status changes
to OUTS.
The output stoppage alarm can be enabled or disabled in the builder.
The “Output Shutdown Alarm” parameter of the Function Block Detail Builder is set as follows:
Output Shutdown Alarm: Select “Yes” or “No.”
Alarm Statuses (Alarm and Notification Processing) of

the Batch Set Control Block (FSBSET)
The table below shows alarm statuses related to alarm and notification processing of the FSBSET
block.
Table 4.1.7-2 Table of Alarm Statuses for Batch Set Control Block (FSBSET)
Abbreviation Service Description

NR Normal No alarm has occurred.
The status of the output is “output failure” (PTPF), caused by a malfunction
Output open
OOP of or break in the control element or process I/O device, or by a data error
alarm
in the output destination. Normally, the output function stops.
The status of the input is BAD, caused by a malfunction of or break in the
control element or process I/O device, or by a data error in the input
High input-
IOP destination. Normally, all processing which uses input data stops. If the
open alarm
cause is input overshooting by some factor such as a break, the input
overshoots upwards.
The input overshoots downwards by some factor such as a break. The

Low input-
IOP- status of the input turns to BAD. Normally, all processing which uses input
open alarm
data stops.
First-stage The absolute value of an instantaneous deviation between the measured
DV1 deviation value and setpoint exceeds the DL1 alarm setpoint, or the absolute value of
alarm an accumulated deviation exceeds the DL1X alarm setpoint.
Second-stage The absolute value of an instantaneous deviation between the measured
DV2 deviation value and setpoint exceeds the DL2 alarm setpoint or the absolute value of
alarm an accumulated deviation exceeds the DL2X alarm setpoint.
The totalization is still being executed while waiting for the next batch after
the end of a batch. If the current totalized value minus the totalized value
LEAK Leakage alarm
at the end of the previous batch exceeds the leakage detection setpoint,
the leakage alarm is activated.
When an emergency stop is commanded (EMSW=1), this alarm is
Emergency
EMST activated. The alarm is on until the completion of the emergency stop
stop alarm
procedure (EMST end).
Loss-of-pulse If no pulse is detected during the specified interval, the loss-of-pulse alarm
NPLS
alarm is activated.
Output Warns that the cascade connection is open. The OUTS alarm occurs when
OUTS stoppage the secondary block turns to the modes other than CAS or when the
alarm cascade connection has been disconnected by a switch or the like.
The status of the I/O destination block is O/S (out of service). This alarm
Connection enables the user to identify the block still operating in the group of control
CNF
failure alarm blocks which were put out of service for maintenance. Normally, IOP and
OOP are activated at the same time.
Action Upon Activation of Alarms in the Batch Set

▼ Emergency Stop by OOP/IOP/IOP-/NPLS/DV1/DV2/OUTS Alarms
The control action of the FSBSET (emergency stop or continuation of action) upon activation of an
alarm can be specified in the Function Block Detail Builder for each alarm type.
The “Emergency Stop” parameters can be enabled or disabled for each of the alarm types shown
below:
IOP-, IOP, DV1, DV2, NPLS, OOP, OUTS
The default is "Yes" except for DV1 alarm.
Bypassing Alarms or Notifications - FSBSET

For each of the following alarms, the detection function can be bypassed individually via
specification in the Function Block Detail Builder:
IOP-, IOP, DV1, DV2, NPLS, LEAK, OOP, OUTS
For all of the following alarms and notifications, the notification functions can be bypassed
collectively by specifying AOFS (alarm off):
IOP-, IOP, DV1, DV2, NPLS, LEAK, OOP, OUTS, EMST
Control Steps of the Batch Set Control Block (FSBSET)

and Applicable Alarm Processing
The table below shows whether alarms are detected at each control step of the FSBSET block.
Table 4.1.7-3 Table of Control Steps for Batch Set Control Block (FSBSET) and Applicable Alarm
Processing
Deviation Loss-of-
Control Leakage IOP OOP External EMST
Status Alarm Pulse
Step Check(*1) (*1) (*1) Command(*1)
Processing(*1) (*1)
0 NON-CONTROL x x x
1 SET-UP x x x x
2 I. F. CONTROL x x x x x
3 STEADY x x x x x
4 EARLY x x x x
5 P. B. CONTROL x x x x x
6 WAIT x x
7 END x x
8 EMST x x x
9 EMST END x x
10 START x x
11 RESTART x x
12 START x x
13 RESTART x x
20 START x x
21 RESTART x x
PI BLENDING
22 x x x x x
CONTROL
23 END WAIT x x x
24 EMST x x x
COMPONENT
25 x x
CUT-OFF
26 END x x
*1: x: available
4.1.8 Control Processing of Batch Set Control Block (FSBSET) Page 1 of 19
4.1.8 Control Processing of Batch Set Control Block

(FSBSET)
Some of the processing performed in each of the FSBSET’s control steps are repeated over multiple
steps (common processing), while others are performed only in a specific control step.
Control Processing of Batch Set Control Block (FSBSET)

The table below shows the control processing items performed by FSBSET block.
Table 4.1.8-1 Table of Control Processing Items Performed by Batch Set Control Block (FSBSET)
Item
Purpose Step
Contents Function
No.
Common 0 Non-Control Leakage check
1 Set-Up SV increase in steps
Initial Flow Rate
2 Initial Flow Rate Control
Control
3 Steady Steady flow rate control
4 Early First-stage control valve (CV) throttling
5 Pre-Batch Control Flow rate control at pre-batch setting flow rate
6 Wait Tightly shut control valve
After waiting a certain pre-determined time, the block mode
7 End
Batch Loader changes to MAN and proceeds to step 0.
(at Port)
During EMST
8 Multi-stage closing of control valve
Processing
9 EMST End Tightly shut control valve
• Initialization processing
10 Start (CV-Kick)
• CV-kick
• CV-kick
11 Restart (CV-Kick)
• Alarm status initialization
12 Start Initialization processing
13 Restart Alarm status initialization
20 CV-Kick (Start) Valve control with a specified opening kick quantity (CVK)
Valve control with a specified opening kick quantity (CVK)
21 CV-Kick (Restart)
(Initializing information other than batch totalized value)
22 Blend PI Control PI blending control or instantaneous deviation control
• Tightly shut control valve (CV)
23 Waiting END
Blending • Retain totalized value as the previous totalized value
Control
24 EMST CV tightly shut
Component Being
25 CV throttling
Released
• CV tightly shut
26 End • Retain totalized value as the previous totalized value
• Change the block mode to MAN and proceed to step 0.
Common Processing - FSBSET

This section describes the common processing items of the FSBSET: PI control, emergency stop
processing, batch-end detection processing, early-point detection processing, manual operation and
operation commands. The batch end processing and early-point detection processing are not performed
if an endless shipment is specified.
PI Control
▼ Gain-Up Value
Flow rate control based on PI action (proportional action+integral action) is called PI control. The
computation expression used for PI control is shown below:
However, when P=0, the following I control computation is executed. The computational expression
used for I control is shown below:
The PI control algorithm is shown below:

For ZONE 1 only, (Kp=set gain+gain increment)
(Where the gain increment is a parameter set in the Function Block Detail Builder.)
Gap (dead band) PI control is also possible, that is:
ΔMVn=0 when | En | ≤BS (gap width)
The “Gain-up Value” parameter of the Function Block Detail Builder is set as follows:
Gain-up Value: 0.00 to 100.00
Emergency Stop Processing

When an emergency stop alarm occurs or an emergency stop command is received (EMSW≠0 or
CMND=4), the FSBSET resets this command (EMSW=0 or CMND=0) and proceeds to emergency stop
processing (Zone 8).
Batch-End Detection Processing

When the totalized value reaches or exceeds (batch setpoint - predicted leakage value), the control
valve shuts tightly and processing proceeds to WAIT (ZONE 6). The conditional expression for batch
end detection is shown below:
SUM≥BSET-VL
However, when designation is “no batch processing” (NONB≠0), the batch does not end even when the
totalizer reading reaches the batch quantity (does not proceed to ZONE 6).
Early-Point Detection Processing
▼ Early Detection Bias Time

When batch processing is about to end (batch end), the flow rate gradually slow. Early-point detection
processing detects the point at which the flow rate starts to slow down.
When the SUM is equal to or exceeds the batch setpoint value from which pre-batch quantity and
expected leakage have been subtracted, the control step proceeds to ZONE4 “Early Processing.” The
computational expression is shown below.
SUM≥BSET-QE-VL
The pre-batch quantity (QE) is automatically calculated from the current setpoint (SV). The
computational expression used varies depending on whether or not a control valve is used.
• Calculating QE when a control valve is used
During early detection, the control valve is throttled back in increments of ΔM. Thus, the throttling
time T can be calculated. The bias time (a) is added to T, and the pre-batch quantity (QE) is
calculated from the current setpoint (SV) as follows:
Figure 4.1.8-1 The calculation of the pre- batch quantity (QE)
where
QE : the pre-batch quantity (liters)
MV : the current control valve opening (%)
ΔM : the control valve throttling decrement when the EARLY status occurs (%) (set in the builder)
a : the bias time (sec)
ΔT : the control period (1 second)
The bias time for early-point detection (a) is specified in the builder.
The “Early Detection Bias Time” parameter of the Function Block Detail Builder is set as follows:
Early Detection Bias Time : 0 to 10000 (unit: basic scan period).
The figure below shows how each variable changes during early detection:
Figure 4.1.8-2 Change in Variables During Early Detection (When Control Valve Is Used)
TIP When the designation is “no batch processing” (NONB≠0), early detection is bypassed.
• Calculating QE when a control valve is not used:

Although the calculation uses a similar expression, T is calculated from the current flow rate setpoint
(SV) since there is no value for control valve opening (MV).
If the current SV > the first-stage throttle setting
If the current SV ≤ the first-stage throttle setting
where
QE : the pre-batch quantity (liters)
SV : the current flow rate setpoint (kiloliters per hour)
ΔM : the control valve throttling decrement when the EARLY status occurs (kiloliters per hour)
a : the bias time (seconds)
ΔT : the control period (1 second)
The figure below shows how each variable changes during early detection:
Figure 4.1.8-3 Change in Variables During Early Detection (When Control Valve Is Not Used)
The control valve throttling decrement (ΔM) during early detection is specified in the builder. Since ΔM
is defined as a percentage value regardless of whether or not the OUT terminal of the FSBSET is
connected, ΔM is converted to a value in industrial scale unit to calculate the pre-batch quantity (QE).
In the same manner, the first-stage throttle setting is also converted to the SV industrial scale unit.
Manual Operation
▼ MAN Intervention Processing
Changing the block mode to MAN allows manual operation of the FSBSET block (Automatic control is
interrupted).
However, by setting the “MAN Intervention Processing” to “Yes” on the Function Block Detail Builder,
you can automatic control by changing the control step during manual operation when the EMST
command is received or a batch end is detected. In this case, the block mode is automatically set to
AUT or CAS.
The “MAN Intervention Processing” parameter of the Function Block Detail Builder is set as follows:
MAN Intervention Processing: Select “Yes” or “No.”
Operation Commands
Transition of control steps occurs via commands from a JOB controller, supervisory loop or operator. Or,
it may occur via commands issued by the FSBSET itself. Transition commands that are sent from a JOB
controller, supervisory loop or operator, are called operation commands.
The figure below shows the action of a batch loader FSBSET in response to operation commands
(CMNDs). The operation commands (1) through (4) in the figure indicate when the start, emergency
stop, restart and reset (abort) commands are issued.
Figure 4.1.8-4 Action of FSBSET by Operation Commands (Batch Loader)
• Start
Change the block mode to AUT or CAS and set as CMND=1 to enable CV-kick, or as CMND=11 to
disable CV-kick. This executes the startup process appropriate for the specified action of CV-kick.
This process does not run unless the block mode is either AUT or CAS.
• Emergency Stop
Setting EMSW=1 or CMND=4 starts emergency stop processing.
• Restart
Set as CMND=2 to enable CV-kick, or as CMND=12 to disable CV-kick. This executes the restart
process appropriate for the specified action of CV-kick.
The process does not run unless the block mode is either AUT or CAS.
• Reset (abort)
Setting CMND=3 performs batch end processing and resets the instrument to the block mode
specified when starting the batch.
If the FSBSET is used as a component FSBSET, operation commands for the block are automatically
issued by the BLEND control block. The operator cannot issue operation commands to the FSBSET
directly.
The figure below shows the action of a component FSBSET (for blending control).
The operation commands (5) through (9) in the figure indicate when the start, emergency stop, restart,
waiting END and END commands are issued.
Figure 4.1.8-5 Action of Batch Set Control Block (FSBSET) by Operation Commands (Components in
Blending)
The figure below shows the component cut-off action of a component FSBSET (for blending control).
In the figure, (10) indicates when the component cut-off command is issued.
Figure 4.1.8-6 Component Cut-Off Action of Batch Set Control Block (FSBSET) by Operation
Command (Components in Blending)
The figure below shows the control functions available in each control step of the FSBSET:
Table 4.1.8-2 Table of Functions Available in Each Control Step of Batch Set Control Block (FSBSET)
Batch Deviation
PI Early
Control Block Initialization Emergency End Alarm
Status Control Detection
Step Mode (*1) Stop(*1) Detection Processing
(*1) (*1)
(*1) (*1)
NON-
0 MAN
CONTROL
CAS
1 SET-UP x x x x
(AUT)
I. F. CAS
2 x x x x
CONTROL (AUT)
CAS
3 STEADY x x x x
(AUT)
CAS
4 EARLY x x
(AUT)
P. B. CAS
5 x x x
CONTROL (AUT)
CAS
6 WAIT
(AUT)
CAS
7 END
(AUT)
CAS
8 EMST x
(AUT)
9 EMST END x
CAS
(AUT)
CAS
10 START x
(AUT)
CAS
11 RESTART
(AUT)
CAS
12 START x
(AUT)
CAS
13 RESTART
(AUT)
20 START CAS x
21 RESTART CAS
PI
22 BLENDING CAS x x
CONTROL
23 END WAIT CAS x
24 EMST CAS x
COMPONENT
25 CAS
CUT-OFF
26 END MAN
*1: x: Yes
Processing in Each Control Step - FSBSET

This section describes the processing performed in each control step.
ZONE 0 (Control status: NON-CONTROL)

When the mode is MAN, only the leakage check is performed.
SEE For more information about the leakage check, refer to:
ALSO " Leakage Alarm (LEAK) - FSBSET" in 4.1.7, "Alarm and Notification Processing of Batch Set
Control Block (FSBSET)"
ZONE 1 (Control status: SET-UP)

▼ SETUP Interval Time, Initial Flow Speed SET UP End Waiting Time, Normal Flow Speed SET UP End
Waiting Time
When a batch cycle is started, or the flow rate setpoint (final flow rate setpoint: SVH; or initial flow rate
setpoint: SVL) is updated, the current flow rate setpoint (SV) is changed in steps during each control
period until it agrees with the target value (SVL or SVH), after the SET-UP waiting time (1 second,
fixed) has elapsed. This flow rate setpoint (SV) is used to perform PI control. When the SV reaches or
overshoots the target value, it is held at the current value (where SV=target value) for a certain
predefined WAIT time, before processing proceeds to the next control step.
The intervals in which the SV is changed in steps is specified in the Function Block Detail Builder.
The “SETUP Interval Time” parameter of the builder is set as follows:
• SETUP Interval Time
0 to 10000 (unit: basic scan period)
The increments in which the SV is changed in steps are specified as the STUP data item (SV SET-UP
increment), while the decrements are specified as the STDN data item (SV SET-DOWN decrement).
The waiting time when the target value is reached is specified in the Function Block Detail Builder.
The “Initial Flow Speed SET UP End Waiting Time” and “Normal Flow Speed SET UP End Waiting Time”
parameters of the builder are set as follows:
• Initial Flow Speed SET UP End Waiting Time
• Normal Flow Speed SET UP End Waiting Time
In this step, PI control, emergency stop processing, batch-end detection processing and early-point
detection processing are performed as common processing.
Figure 4.1.8-7 SET-UP Processing and SET-DOWN Processing
In ZONE 1, initial flow rate control is needed when the following conditions are met. Therefore, the
initial flow rate setpoint (SVL) is adopted as the target value during SET-UP processing.
ILSW=1 (initial flow rate control command)
ILST > SUM (the totalized flow is less than the initial totalized flow setpoint)
If the above conditions are not met while setting up toward SVL, SET-UP toward SVH is started
immediately. After SET-UP is completed, if the above conditions are met, then the step proceeds to
initial flow rate control (ZONE 2); if they are not, it proceeds to STEADY (ZONE 3).
ZONE 2: Initial flow rate control

PI control is carried out by using the initial flow rate setpoint (SVL) as the flow rate setpoint (SV).
If the SVL is updated, control proceeds to ZONE 1. When initial flow rate control is released or when the
totalized flow reaches the initial totalized flow setpoint, the final flow rate setpoint (SVH) is used as the
target valu e and the control proceeds to ZONE 1.
ZONE 3 (Control status: STEADY)

PI control is carried out based on the final flow rate setpoint (SVH) as the flow rate setpoint (SV).
If the SVH is updated, control proceeds to ZONE 1.
ZONE 4 (Control status: EARLY)

▼ Valve Throttling Quantity in Early Status, Previous-Batch Transition Decision Coefficient, First Stage
Valve Throttle Level in Early Status
The control valve is throttled back a fixed amount during each control period, and measurement
tracking is performed. Then, control proceeds to ZONE 5 (pre-batch control).
The computational expression used varies depending on whether or not a control valve is used.
In this step, emergency stop processing and batch-end detection processing are performed as common
processing.
• Early-point detection processing when a control valve is used
The manipulated output value (MV) is decreased in steps by ΔM. ΔM is the throttling decrement
during early-point detection processing specified in the Function Block Detail Builder. The
computational expression for this throttling is shown below:
MVn=MVn-1 - ΔM
SVn=PVn (SV value tracks PV value.)
When MV≤0 or SVn • a≤SVPR (data item SVPR is the flow rate setpoint for pre-batch; a is the pre-
batch transition coefficient set in the Function Block Detail Builder) is reached via throttling, the SV is
set as SVPR and control proceeds to ZONE 5.
The figure below shows the throttling process until MV≤0 or SVn • a≤SVPR is reached:
Figure 4.1.8-8 Early-point Detection Processing (When Control Valve Is Used)
The “Valve Throttling Quantity in Early Status” and “Previous-batch Transition Decision Coefficient”
parameters of the builder are set as follows:
• Valve Throttling Quantity in Early Status
0.001 to 100.000 %.
• Previous-batch Transition Decision Coefficient
0.000 to 100.000 %.
TIP When a control valve is used, control proceeds to ZONE 8 (EMST processing) if the status is IOP or
OOP alarm. If EMST is not specified, the block mode changes to IMAN and control remains at ZONE
4.
When the early point is detected, throttling back of the control valve starts from the specified value
(MP: the first-stage throttle setting at early detection, specified in the Function Block Detail Builder).
Figure 4.1.8-9 Throttling from Specified Value (MP) at Early Point Detection
If the MP is larger than the current value, throttling back starts from the current value.
Figure 4.1.8-10 Throttling from Current Value (MV) at Early Point Detection
The “First Stage Valve Throttling Level in Early Status” parameter of the builder is set as follows:
First Stage Valve Throttling Level in Early Status : 0.000 to 100.000 %.
• Early-point detection processing when a control valve is not used
The SV is decreased in steps by ΔM. The computational expression for this throttling is shown below:
SVn=SVn-1 - ΔM
MVn=SVn
When SVn≤SVPR (flow rate setpoint for pre-batch) is reached, control proceeds to ZONE 5 with the
setting of SV=SVPR.
The figure below shows the throttling process until SVn≤SVPR is reached:
Figure 4.1.8-11 Early-point Detection Processing (When Control Valve Is Not Used)
SEE For more information about the details of early-point detection processing, refer to:
ALSO " Early-Point Detection Processing" in " Common Processing - FSBSET" in 4.1.8, "Control
Processing of Batch Set Control Block (FSBSET)"
ZONE 5 (Control status: PRE-BATCH-CONTROL)

PI control continues with the flow rate setpoint for pre-batch (SVPR) used as the flow rate setpoint (SV)
until the totalized flow reaches the batch setting, and then control proceeds to ZONE 6.
In this step, PI control, emergency stop processing and batch-end detection processing are performed
as common processing.
ZONE 6 (Control status: WAIT)

▼ Waiting Time during Batch End
The control valve is tightly shut, and control WAITs for a certain predetermined time to totalize the flow
rate while the valve is being shut.
Then, batch end processing is performed before control proceeds to ZONE 7. The totalizer value is
stored as the previous totalizer value for the next batch.
The time of WAIT processing is set in the builder.
The “Waiting Time during Batch End” parameter of the Function Block Detail Builder is set as follows:
Waiting Time during Batch End: 0 to 10000 (unit: basic scan period).
ZONE 7 (Control status: END)

▼ Waiting Time during End Process Completion
The control valve is tightly shut, and again WAITs for a preset time.
Control then returns to ZONE 0 after the mode changes to MAN.
The “Waiting Time during End Process Completion” parameter of the Function Block Detail Builder is set
as follows:
Waiting Time during End Process Completion: 0 to 10000 (unit: basic scan period).
ZONE 8 (Control status: EMERGENCY STOP)

▼ Valve Throttling Quantity in Emergency Shutdown Status, First Stage Valve Throttle Level in Emergency
Shutdown Status
This step closes the control valve in steps, with control proceeding to ZONE 8 when an emergency stop
alarm is generated or an emergency stop command is detected.
The processing details of multi-step closing vary depending on whether or not a control valve is used.
In this step, batch-end detection processing is performed as common processing.
• Multi-step closing when a control valve is used
The MV is decreased in steps by ΔME during each control period, and control proceeds to ZONE 9
when MV≤0 is reached. Measurement tracking is performed during valve throttling.
The computational expressions for this throttling are shown below:
MVn=MVn-1 - ΔME
SVn=PVn
where
ΔME : control valve throttling decrement in the EMST status (%) (specified in the Function Block
Detail Builder)
If the status is IOP or OOP alarm, then the following computational expression for throttling is used
instead:
MVn=MVn-1 - ΔME
SVn=MVn
The “Valve Throttling Quantity in Emergency Shutdown Status” parameter of the Function Block
Detail Builder is set as follows:
Valve Throttling Quantity in Emergency Shutdown Status: 0.001 to 100.00 %.
The figure below shows the throttling process until MV≤0 is reached:
Figure 4.1.8-12 Emergency Stop Processing (When Control Valve Is Used)
• Multi-step closing when a control valve is not used:

The SV is decreased in steps by ΔME until SV≤0 is reached, and then control proceeds to ZONE 9.
The computational expression for this throttling is shown below:
SVn=SVn-1- ΔME
MVn=SVn
where
ΔME : control valve throttling decrement in the EMST status (%) (specified in the Function Block
Detail Builder)
The figure below shows the throttling process until SV≤0 is reached:
Figure 4.1.8-13 Emergency Stop Processing (When Control Valve Is Not Used)
• First-stage throttling specified in the builder:

When a control valve is used, it is throttled to the specified first-stage throttle level. At that point,
start normal throttling at the start of emergency stop processing at the specified value (MPE).
However, if the MPE value is larger than the current value, throttling starts at the current value.
• MPE is the valve first-stage throttle setting at the EMST status (%)
(specified in the Function Block Detail Builder).
The figure below shows the first-stage throttle setting for control valve specified in the builder:
Figure 4.1.8-14 Control Valve First Stage Throttle Setting Specified in Builder
The “Valve of First Stage Valve Throttle Level in Emergency Shutdown Status” parameter of the
Function Block Detail Builder is set as follows:
• Valve of First Stage Valve Throttle Level in Emergency Shutdown Status
0.000 to 100.00 %.
ZONE 9 (Control status: EMST END)

▼ Batch End Detection during Emergency Shutdown
This step completes the emergency stop. The details of processing vary depending on whether or not a
control valve is used.
In this step, batch-end detection processing is performed as common processing, even in the EMST
END status (specified in the Function Block Detail Builder).
• When a control valve is used
Sets MV=0 to tightly shut the control valve.
Performs measurement tracking.
SVn=PVn
Or, SVn=MVn (if the status is IOP or OOP alarm)
• When a control valve is not used
Sets SV=0 and MV=0.
The “Batch End Detection during Emergency Shutdown” parameter of the Function Block Detail Builder
are set as follows:
Batch End Detection during Emergency Shutdown: Select “Yes” or “No.”
Default is “Yes.”
ZONE 10 (RESET START)

▼ SV Kick Width
After the initialization processing, control proceeds to ZONE 1 and starts batch processing.
The following are initialization processing items performed in this step:
• Initializes totalizer value
Clears SUM to 0.
• Initializes alarm status
Alarm status=NR
• Clears the accumulated deviation to 0.
• Resets emergency stop command
EMSW=0.
• CV (control valve) kick
Sets the kick value (CVK) to the MV.
• SV kick
Same as the value set for SV kick width on the Function Block Detail Builder.
Definition item “SV Kick Width” may be defined as follows:
SV Kick Width: 0.000 - 100.000 %
Default setting is 0.000 %.
ZONE 11 (Control status: RESTART FROM EMST)

After the initialization processing, control returns to ZONE 1 and batch processing is restarted.
• CV kick
Sets the kick value (CVK) to the MV, and outputs this value as position data.
• SV kick
• Initializes alarm status
Alarm status=NR.
ZONE 20 (Control status: RESET START)

For blending control, the batch starts with this step.
When the mode is CAS, control first performs the initial processing, then starts batch processing.
• Initializes totalizer value
Clears SUM to 0.
• Initializes alarms status
Alarm status=NR.
• Clears the accumulated deviation (DV1, DV2) to 0.
• Proceeds to ZONE 22.
• CV kick
Sets the kick value (CVK) to the MV.
• SV kick
ZONE 21 (Control status: RESTART FROM EMST)

Similar to ZONE 20.
However, does not clear SUM or accumulated deviation.
ZONE 22 (Control status: BLEND PI CONTROL)

▼ COMP Control Specification
Performs PI blending control or instantaneous deviation control (whichever is set in the Function Block
Detail Builder) based on the SV set from the supervisory loop.
A deviation alarm is applied to the totalizer value or instantaneous deviation, respectively.
• PI blending control
The computational expression for PI blending control is as follows:
TIP The data item names of proportional band and integral time differ between blend PI control and
instantaneous deviation control “P” and “I” are used in instantaneous deviation control, and “Px”
and “Ix” in blend PI control.
• Instantaneous deviation control

The computational expression for instantaneous deviation control is as follows:
The “Control Computation Type” parameter of the Function Block Detail Builder is set as follows:
• Control Computation Type
Select “Accumulated deviation” or “Instantaneous deviation.”
The default is “Accumulated deviation.”
ZONE 23 (Control status: WAIT FOR END)

When the FSBSET reaches this step, the flow rate setpoint (SV) has already been set to 0 via
specification from the supervisory loop.
The system confirms that the SV is 0, and performs the following end processing:
• Tightly shuts the control valve (MV=0).
ZONE 24 (Control status: EMST)

The supervisory loop is in the emergency stop status. The control valve is tightly shut. The block mode
may fallback to MAN/IMAN.
ZONE 25 (Control status: COMPONENT CUT-OFF)

▼ Valve Throttling Quantity in COMP Cut-Off Status
Component cut-off hπas been ordered by the supervisory loop, and the following end processing is
being performed. The details of processing vary depending on whether or not a control valve is used.
• When a control valve is used
Throttle the MV by ΔMR during each control period. When MV≤0 is reached, proceed to ZONE 26.
The computational expression for this throttling is shown below:

MVn=MVn-1 - ΔMR
SVn=PVn-1
ΔMR: the valve throttling decrement (set in the Function Block Detail Builder)
When a control valve is used, the valve is throttled based on the following expression if the status is
IOP or OOP alarm:
MVn=MVn-1 - ΔMR
SVn=MVn
The figure below shows the throttling process until MV≤0 is reached:
Figure 4.1.8-15 Emergency Stop Processing (When Control Valve Is Used)
The “Valve Throttling Quantity in COMP Cut-off Status” parameter of the Function Block Detail
Builder is set as follows:
Valve Throttling Quantity in COMP Cut-off Status: 0.001 to 100.000 %
• When a control valve is not used
The SV is set as 0, and MVn as SVn. Then, control proceeds to ZONE 26. The figure below shows the
throttling process:
Figure 4.1.8-16 Emergency Stop Processing (When Control Valve Is Not Used)
ZONE 26 (END)
The following end processing is performed.
• Tightly shuts the control valve (MV=0).
• Changes the block mode to MAN and returns to ZONE 0.
Control Step Transition Diagram - FSBSET

The figure below shows the control step transition diagram:
Figure 4.1.8-17 Control Step Transition Diagram of Batch Set Control Block (FSBSET) for Batch
Loader
Commands - FSBSET
The table below shows the commands available with FSBSET block.
Table 4.1.8-3 Table of Commands Available with Batch Set Control Block (FSBSET)
CMND Zone (Step) Status Description of Command

0
1 10 Supervisory setting Batch loader mode - start (with CV-kick)
2 11 Supervisory setting Batch loader mode - restart (with CV-kick)
3 6 Start mode Batch loader mode - abort
4 8 Start mode Batch loader mode - EMST
5
6
7
8
9
10
11 12 Supervisory setting Batch loader mode - start (without CVkick)
12 13 Supervisory setting Batch loader mode - restart (without CVkick)

21 20 CAS Component blending mode - start
22 21 CAS Component blending mode - restart
23 26 CAS Component blending mode - end (release)
24 24 CAS Component blending mode - EMST
25 25 CAS Component blending mode - component cut-off
26 23 CAS Component blending mode - waiting end
17
18
19
41 40 Supervisory setting Start with valve opened X% (NCCV)
42 41 Supervisory setting Restart with valve opened X% (NCCV)
43 43 Start mode X% (NCCV) end
44 44 Start mode X% (NCCV) EMST
4.1.9 Block Modes of Batch Set Control Block (FSBSET) Page 1 of 1
4.1.9 Block Modes of Batch Set Control Block (FSBSET)

The block modes of the FSBSET include out of service, initialization manual, manual, automatic and
cascade.
Block Modes of the Batch Set Control Block (FSBSET)

The table blow shows the block modes for FSBSET block.
Table 4.1.9-1 Table of Block Modes for Batch Set Control Block (FSBSET)

O/S Out of service All the functions are stopped.
MANual
IMAN Control computation and output actions are stopped.
initialization
MAN MANual Control calculation is stopped and output is manually manipulated.
AUT AUTomatic Control calculation is made and the result is output.
When used as a blending component controller, a control calculation is
CAS CAScade made using the setpoint (CSV) set by the supervisory block and the result is
output. When used as a batch loader, the action is the same as AUT above.
4.1.10 Data Items of Batch Set Control Block (FSBSET) Page 1 of 3
4.1.10 Data Items of Batch Set Control Block (FSBSET)

There are 61 types of data items that can be set with the FSBSET.
Data Items of the Batch Set Control Block (FSBSET)

The table below shows the data items set with FSBSET block.
Table 4.1.10-1 Table of Data Items Set with Batch Set Control Block (FSBSET)
Data Entry
Data Item Range/Unit Default
Name (*1)
O/S
MODE Block mode -----
(MAN)
BSTS Block status N/A ----- -----
ALRM Alarm status N/A ----- NR
AFLS Alarm flashing status N/A ----- -----
AF Alarm detection specification N/A ----- -----
AOFS Alarm masking specification N/A ----- -----
Industrial scale unit used for
PV Instantaneous flow rate Cond. -----
PV
Scale unit used for IN-
RAW Raw data Cond. -----
terminal destination
SV Setpoint of flow rate x SL
PV
MV Manipulated output value x MSL
MV
DV Instantaneous deviation N/A (SL - SH) to (SH - SL) 0
DVX Accumulated deviation x ±SUM, industrial unit 0
SVPR Flow rate setpoint for pre-batch x SL to SH SL
SVH Final flow rate setpoint x SL to SH SL
SVL Initial flow rate setpoint x SL to SH SL
ILST Setting to release initial flow rate control x Industrial unit used for SUM 0
VL Predicted leakage value x Industrial unit used for SUM 0
Proportional band (Instateneous deviation
P x 0-1000.0 % 100.0
control)
Integral time (Instateneous deviation
I x 0.1-10,000.0 seconds 20.0
control)
PX Proportional band (PI blending control) x 0-1000.0 % 100.0
IX Integral time (PI blending control) x 0.1-10,000.0 seconds 20.0
BS Non-linear gap width x 0-100.0 % 0.00
First-stage deviation alarm setting for
DL1 x 0 to (SL - SH) SH-SL
instantaneous flow rate
Second-stage deviation alarm setting for
DL2 x 0 to (SL - SH) SH-SL
instantaneous flow rate
First-stage deviation alarm setting for
DL1X x Industrial unit used for SUM SH*1000
accumulated deviation
DL2X Second-stage deviation alarm setting for x Industrial unit used for SUM SH*1000
accumulated deviation
SUM Totalized value of corrected value x Industrial unit used for SUM 0
Non-reset and non-corrected totalized
SUM1 x Industrial unit used for SUM 0
value
SUM2 Non-reset and corrected totalized value x Industrial unit used for SUM 0
BSET Batch setpoint x Industrial unit used for SUM 0
CMND Command switch x 0-63 0
ZONE Control step N/A 0-63 0
EMSW Emergency-stop command switch x 0 or 1 0
LRSW Leakage-reset command switch x 0 or 1 0
NONB Endless-batch command switch x 0 or 1 0
Command switch for initial flow rate
ILSW x 0 or 1 0
control
OPHI Output high limit index x MSL to MSH MSH
OPLO Output low limit index x MSL to MSH MSL
0 (for direct) or 1 (for
DR Control action N/A 1
reverse)
EMCD EM-ST factor code N/A 0-32,767 0
STUP SV set-up increment x 0-100 % 1
STDN SV set-down decrement x 0-100 % 2
CVK Extent of CV kick x 0-100 % 0
SIMM Simulation designation x 0 or 1 0
Factor for flow rate correction before
CCX x 0.00000-100.0000 1.00000
temperature compensation
Factor for flow rate correction after
CCY x 0.00000-100.0000 1.00000
temperature compensation
Density used for temperature
DENS x 0.00000-100.0000 0.00000
compensation
Temperature compensation factor (for
VCF x 0.00000-100.0000 1.00000
setting/displaying VCF)
Extent of valve opening in non-control
NCCV x 0.000-100.000 % 100.000
zone
DSM Instantaneous flow after correction N/A Industrial unit used for SUM 0
Y01-Y04 Optional buffer 1-4 x -100.00000-100.00000 0
Y05-Y09 Optional buffer 5-9 x -32,768-32,767 0
OT01[16] Option tag 1 x 16 alphanumeric characters NULL
OPMK Operation mark x 0-64 0
SH Scale high limit N/A -----
PV
SL Scale low limit N/A -----
PV
MSH Scale high limit for MV N/A -----
MV

MSL Scale low limit for MV N/A -----
MV
CRD Ratio control designation N/A 0 or 1 0
*1: x: entry possible
Cond.: entry possible under certain conditions
N/A: entry not possible
4.2 Blending Master Control Block (BLEND) Page 1 of 1
4.2 Blending Master Control Block (BLEND)

The Blending Master Control Block (BLEND) provides functions required for tank blending control
and direct blending shipment control; it controls flow rate and batch quantity at the port or for a
blend header used to set component flow rates.
Classification Between Tank Blending and Direct

Shipment - BLEND
Although tank blending and direct blending shipment are both blending work, the two are classified
as different works based on whether or not an FSBSET that performs batch control is located at the
port. The blending work is considered direct blending shipment if there is an FSBSET, and tank
blending if there is no FSBSET.
Hence, even if the work consists of blending in a tank, if batch quantity control is performed by an
FSBSET control block, then the control is classified as direct blending shipment.
Tank Blending Control Functions - BLEND

Tank blending control uses BLEND master and FSBSET control blocks.
The BLEND master manages secondary-loop FSBSET blocks that control the flow rate of each
component. The BLEND master controls batch quantity, managing both the flow rate and totalized
flow of each component; it sets the initial flow rate setpoint (SV) for each component FSBSET by
multiplying its own SV by the blending ratio for the corresponding component, and performs
batching control by totalizing the instantaneous flow rates of all FSBSET blocks.
Direct Blending Shipment Functions - BLEND

Direct blending shipment control uses BLEND master and FSBSET control blocks.
The BLEND master manages secondary-loop component FSBSET blocks and the “port FSBSET”
(or “port BLEND” block) which manages flow rate and batch control at each port.
Batch control itself is performed by the “port FSBSET” block (or “port BLEND” block). The BLEND
master sets the flow rate setpoints (SV) for each of the component FSBSET blocks by multiplying its
own SV by the corresponding blending ratio.
The BLEND located at the port (“port BLEND”) can only perform the functions
allowed for a tank blending BLEND. No flowmeter signal (from the port) can
be connected to a “port BLEND.”
4.2.1 Operation for Tank Blending Control Page 1 of 2
4.2.1 Operation for Tank Blending Control

During tank blending control, the BLEND master performs SET-UP, release of initial flow rate control,
early-point detection processing and pre-batch processing.
The operation of the BLEND master is indicated by a sequence of control steps.
Operation for Tank Blending Control - BLEND

The figure below shows the flow of BLEND master operation during tank blending control:
Figure 4.2.1-1 Operation Overview of Tank Blending Control
The basic operation of the BLEND master during tank blending control is explained below. The
• At the start of tank blending control, the block status of the BLEND master is changed to AUT or
CAS via a JOB controller or by an operator. A start command is then sent to the BLEND master.
• When the BLEND master receives a start command (CMND=1), the control step proceeds to
ZONE 10 and a start command (CMND=21) is sent to component FSBSET blocks. Initialization
processing for the BLEND master itself such as alarm or totalization processing is performed,
then the control step returns to ZONE 1. From the start until the end of control, the BLEND
master constantly multiplies its own flow rate setpoint (SV) by the blending ratio for each of the
components and distributes the results as SVs to the corresponding components.
• SET-UP is started upon transition to ZONE 1. In SET-UP, the current flow rate setpoint (SV) is
ramped at a preset rate until it reaches the initial flow rate setpoint (SVL) or final flow rate
4.2.1 Operation for Tank Blending Control Page 2 of 2
setpoint (SVH).
• When the waiting time for the end of SET-UP to initial flow rate (T1) elapses after the current
flow rate setpoint (SV) reached the initial flow rate setpoint (SVL), the control step proceeds to
ZONE 2.
• When the totalized flow (SUM) reaches the initial (totalized) flow setpoint (ILST), or when an
operator directs the release, the control step returns to ZONE 1, and SET-UP is performed to
ramp the current flow rate setpoint (SV) at a preset rate until it reaches the final flow rate
setpoint (SVH).
• When the waiting time for the end of SET-UP to final flow rate (T2) elapses after the current flow
rate setpoint (SV) reached the final flow rate setpoint (SVH), the control step proceeds to ZONE
3.
• When the totalized flow (SUM) reaches the batch setpoint (BSET) less the pre-batch quantity and
predicted leakage value (VL), the control step proceeds to ZONE 4. The flow rate setpoint (SV)
decreases at a preset rate, and when the SV reaches the flow rate setpoint for pre-batch (SVPR),
the control step proceeds to ZONE 5.
• When the totalized flow (SUM) reaches the batch setpoint (BSET) less the predicted leakage
value (VL), the control step proceeds to ZONE 6. The flow rate setpoint (SV) of each component
FSBSET is set to 0, and an Wait for END command (CMND=26) is sent to the component FSBSET
blocks. Calculation for the totalized flow (SUM) still continues during this time. When the waiting
time for batch end (t3) elapses following the transition to ZONE 6, the control step proceeds to
ZONE 7.
• When the waiting time after the completion of end procedure (t4) elapses following the transition
to ZONE 7, a component release command (CMND=26) is sent to each component FSBSET and
the BLEND master itself changes its block mode to MAN. The control step returns to ZONE 0, and
tank blending control is completed.
• If an emergency stop command (CMND=4) is issued or a critical alarm is detected during the
batch cycle, the control step proceeds to ZONE 8 and the flow rate setpoint (SV) decreases in
steps until it reaches 0. When the SV drops to 0 or below, a component EMST command
(CMND=24) is sent to each component FSBSET, and the control step of the BLEND master itself
proceeds to ZONE 9. The block status changes to EMST END (emergency stop end).
• If a restart command (CMND=2) is received in the EMST END status, the control step proceeds to
ZONE 11 and a restart command (CMND=22) is sent to each component FSBSET. The control
step of the BLEND master itself proceeds to ZONE 1, and tank blending control is restarted.
The following operations are not shown in the above figure:
• During SET-UP in ZONE 1, if initial flow rate control is not specified or when the totalized flow
(SUM) reaches or exceeds the initial totalized flow setpoint, SET-UP is performed based on the
final flow rate setpoint (SV).
• If an abort command (CMND=3) is received in the EMST END state, the control step returns to
ZONE 6 and the processing is performed, starting from the operation in ZONE 6 explained above.
4.2.2 Operation for Direct Blending Shipment Control Page 1 of 2
4.2.2 Operation for Direct Blending Shipment Control

During direct blending shipment control, the BLEND master performs blending control and other
processing operation.
The operation of the BLEND master is indicated by a sequence of control steps.
Operation for Direct Blending Shipment Control - BLEND

The figure below shows the flow of BLEND master operation during direct blending shipment
control:
Figure 4.2.2-1 Operation Overview of Direct Blending Shipment Control
The basic operation of the BLEND master during direct blending shipment control is explained below.
The explanations are based on the above figure.
• At the start of direct blending shipment control, the block status of the BLEND master is changed
to AUT or CAS via a JOB controller or by an operator.
• When control is started with any port FSBSET block (or port BLEND block) set to perform product
shipment, the control step immediately proceeds to ZONE 30 and blending is started. A
component start command (CMND=21) is sent to each component FSBSET after a preset period
of time. The control step of the BLEND master itself proceeds to ZONE 31.
• When the control step reaches ZONE 31, the sum of the flow rate setpoints (SVs) or
instantaneous flow rates (PVs) of the port FSBSET blocks (or port BLEND blocks) becomes the
BLEND master’s own SV. The BLEND master then multiplies the SV by the blending ratio for each
of the component FSBSET blocks and distributes the results as SVs to the corresponding FSBSET
blocks.
4.2.2 Operation for Direct Blending Shipment Control Page 2 of 2
• When the batch cycle is completed at all port FSBSET blocks (or port BLEND blocks), a
component release command (CMND=23) is sent to each component FSBSET. The block mode of
the BLEND master itself changes to MAN, and the control step returns to ZONE 0.
• If all port FSBSET blocks (or port BLEND blocks) are shut down by an emergency stop command
during direct blending shipment control (ZONE 9), a component EMST command (CMND=24) is
sent to each component FSBSET. The control step of the BLEND master itself proceeds to ZONE
32.
• If any of the port FSBSET blocks (or port BLEND blocks) is still operating while the control step of
the BLEND master is at ZONE 32, the BLEND master returns to ZONE 31, and direct blending
shipment is restarted.
4.2.3 Configuration of Blending Master Control Block (BLEND) Page 1 of 1
4.2.3 Configuration of Blending Master Control Block

(BLEND)
This section explains the function block diagram of the BLEND control block.
Function Block Diagram of Blending Master Control

Block (BLEND)
The figure below shows the function block diagram of the BLEND control block:
Figure 4.2.3-1 Function Block Diagram of Blending Master Control Block (BLEND)
Input Processing Functions

The BLEND master acquires instantaneous-flow data from component FSBSET blocks to summarize
and totalize them, and reads flow rate setpoints from port FSBSET blocks and BLEND blocks to
obtain the totalized current flow rate setpoint.
Component Management Functions

The BLEND master manages the component configuration and monitors for component flow alarms.
Port Management Functions

The BLEND master can also provide port batch functions.
4.2.4 Component Management Page 1 of 3
4.2.4 Component Management

The BLEND master can be configured to manage up to fourteen component FSBSET blocks in
secondary loops. The functions required to manage these FSBSET blocks are called component
management functions.
Information regarding the blocks managed by the BLEND master (component configuration) is
updated by the supervisory computer (JOB controller). It cannot be changed by the user directly.
Component Management - BLEND

When adding or deleting tag names of component FSBSET blocks managed by the BLEND master or
changing the blending ratio, the supervisory computer (JOB controller) sets the tag names, blending
ratios and release DT in the BLEND control block receive buffer, and then issues a “change”
command to MOD1. The BLEND block control buffer cannot be changed by the user directly.
The figure below describes the concept of component management functions:
Figure 4.2.4-1 Conceptual Diagram of Component Management
Structure of TAG Name and Release DT Data - BLEND

The figure below shows the structure of tag name and release DT data set by the supervisory
computer (JOB controller) in the BLEND control block receive buffer:
Figure 4.2.4-2 Structure of Tag Name and Release DT Data
“Releasing (cut-off) bit” means that release processing (processing to cut off component) is being
performed for the specified component FSBSET; “release end bit” means that release processing is
completed.
MOD1 Change Commands - BLEND

The following change commands are issued by the supervisory computer (JOB controller) to the
MOD1 of the BLEND control block.
MOD1=0 (Disabled)
MOD1=1 (Copies new tag name and blending ratio data to the control buffer, and changes them.)
MOD1=2 (Sets to zero (or clears) the tag name and blending ratio data in the BLEND.)
When MOD1=1 or MOD1=2 is set, the MOD1 automatically returns to zero and the processing for
MOD1=1 or MOD1=2 is performed.
Component Release Processing (Delete Processing) -

BLEND
When a component is to be cut off during blending, first the flow rate of that component must be
set to zero. The processing for this is called “Release Processing.”
In release processing, the supervisory computer (JOB controller) sets the releasing (cut-off) bit for
the specified function block in the BLEND control block release buffer, then issues a notification to
set MOD1=1 in the BLEND, thereby executing the release.
The following processing is performed for the release-requested function block:
1. A component cut-off command (CMND=25) is issued to the specified component FSBSET. The
release request sets the FSBSET to ZONE 25. This component FSBSET begins end processing,
throttling back the MV by ΔMR during each control period. (If a control valve is not used, the SV
is reduced step by step.) During release processing, the BLEND still totalizes the SUM and PV of
the releasing FSBSET. Valve throttling ΔMR may be specified on the Function Block Detail Builder.
Item to be defined.
Valve Throttling Quantity in COMP cut-off status: 0.001 to 100.00
The default setting is 2.000.
2. For the specified component FSBSET, when MV=0 or SV=0, first ZONE=26 is set, then ZONE=0
is set; when the BLEND detects ZONE=0 then releasing is complete, and it subsequently ignores
that tag (no further processing will be performed).
If, before release processing for the component FSBSET is complete, a component configuration
change command is received from the supervisory computer, the component being released will
be included in the targets of change processing.
The figure below shows how each variable changes during release processing:
Figure 4.2.4-3 Change in Each Variable During Release Processing
4.2.5 Port Management Page 1 of 2
4.2.5 Port Management

The BLEND master can be configured to manage up to six FSBSET or BLEND control blocks at ports
in secondary loops. The functions required to manage these blocks are called port management
functions.
Information regarding the blocks managed by the BLEND master (shipment port configuration) is
updated by the supervisory computer (JOB controller). It cannot be changed by the user directly.
Port Management Functions - BLEND

When adding or deleting port FSBSET blocks or BLENDs managed by the BLEND master, the
supervisory computer sets the tag names in the BLEND control block receive buffer, and then issues
a “change” command to MOD2. The BLEND control buffer cannot be changed by the user directly.
The figure below describes the concept of port management functions:
Figure 4.2.5-1 Conceptual Diagram of Port Management
Structure of Tag Name Data - BLEND

The figure below shows the structure of tag name data set by the supervisory computer in the
BLEND control block receive buffer:
Figure 4.2.5-2 Structure of Tag Name
MOD2 Change Commands - BLEND

The following change commands are issued by the supervisory computer (JOB controller) to the
MOD2 of the BLEND control block:
MOD2=0 (No operation)
MOD2=1 (Adds the specified port)
MOD2=2 (Deletes the specified port)
MOD2=3 (Deletes all ports)
When MOD2≠0 is set, the processing for MOD2≠0 is performed and the MOD2 automatically returns
to zero.
4.2.5 Port Management Page 2 of 2
Connection with Blocks of Other Stations - BLEND

▼ Scan Specification
Normally, port FSBSET blocks and component FSBSET blocks must be located at the same station as
the BLEND master. However, it is possible to locate port FSBSET blocks and component FSBSET
blocks at other stations.
By using an inter-station data link block (ADL), the SV and ZONE values of the port FSBSET blocks
are copied to dummy port FSBSET blocks of the self station. That is, direct blending shipment can be
performed.
When the port FSBSET block (or port BLEND block) is used as dummy block in the self station, the
scan of the block should be specified “OFF” on the Function Block Detail Builder.
Item to be defined.
Scan Specification: “ON” or “OFF”
The default setting is “ON.”
4.2.6 Input Processing of Blending Master Control Block (BLEND) Page 1 of 2
4.2.6 Input Processing of Blending Master Control Block

(BLEND)
The input processing items of the BLEND master include component PV acquisition, SV acquisition
from FSBSET at port and component alarm acquisition.
Input Processing of the Blending Master Control Block

(BLEND)
The table below shows the input processing items for BLEND block.
Table 4.2.6-1 Table of Input Processing Items for Blending Master Control Block (BLEND)
No. Processing Item Provided (*1)

1 Component PV acquisition x
2 SV acquisition from FSBSET at port x
3 Component alarm acquisition x
*1: x: available
Component PV Acquisition - BLEND

The BLEND master acquires, from all secondary-loop component FSBSET blocks, their instantaneous
flows (PVs) and variations (ΔSUM) of totalized flows (SUM) from the previous values.
The BLEND master sets the sum of acquired PVs as its own PV, and adds the sum of acquired
variations in totalized flow (ΔSUM) to its own totalized flow (SUM).
It does not acquire data from component FSBSET blocks that are in the release end status.
Number of SUM Digits - BLEND

▼ Number of Digits for Indicating SUM
The number of SUM digits for each BLEND block can be selected between 8 and 9.
This is set on the function block detail builder.
Number of digits for indicating SUM: Choose [8] or [9].
The default setting is 8.
The following data items are subject to this setting.
SUM: Value of compensated summation after compensation
SM01 to SM14: Sums of component 1 to component 14
BSET: Batch Quantity Set Value
DSM: Instantaneous compensated flow rate
ILST: End point of primary flow
VL: Predicted leak quantity
SV Acquisition from FSBSET at Port - BLEND

▼ Standard Setting Flow Rate Specification of Shipping Outlet
The BLEND master acquires flow rate setpoints (SVs) from the port FSBSET blocks or BLEND blocks
corresponding to the tag names registered in its control buffer, then sets the sum as its own SV. The
BLEND master can be set in the builder to acquire instantaneous flows (PVs) instead of SVs and set
4.2.6 Input Processing of Blending Master Control Block (BLEND) Page 2 of 2
the sum as its own SV.

The “Standard Setting Flow Rate Specification of Shipping Outlet” parameter of the builder is set as
follows:
• Standard Setting Flow Rate Specification of Shipping Outlet
Select “SV” or “PV.”
The default is “SV.”
Component Alarm Acquisition - BLEND

The BLEND master acquires alarm statuses from all secondary-loop component FSBSET blocks, then
sets its own alarm status based on the result.
SEE For more information about the alarm processing of the blending master control block, refer to:
ALSO 4.2.8, "Alarm and Notification Processing of Blending Master Control Block (BLEND)"
4.2.7 Output Processing of Blending Master Control Block (BLEND) Page 1 of 1
4.2.7 Output Processing of Blending Master Control Block

(BLEND)
The output processing items of the BLEND master include component SV setting and component
command setting.
Output Processing of the Blending Master Control Block

(BLEND)
The table below shows the output processing items for BLEND block.
Table 4.2.7-1 Table of Output Processing Items for Blending Master Control Block (BLEND)
No. Processing Item Provided (*1)

1 Component SV setting x
2 Component command setting x
*1: x: available
Component SV Setting - BLEND

The BLEND master multiplies by its own flow rate setpoint (SV) the blending ratio for each of the
secondary-loop component FSBSET blocks that are neither being cut off or in the release end status,
and distributes the results as SVs to the corresponding components.
Component Command Setting - BLEND

The BLEND master sets the following commands for the CMND data items of secondary-loop
component FSBSET blocks:
21: Component start
22: Component restart
23: Component release
24: Component EMST
25: Component cut-off
26: Component wait for end
SEE For more information about component command setting, refer to:
ALSO 4.2.9, "Control Processing of Blending Master Control Block (BLEND)"
4.2.8 Alarm and Notification Processing of Blending Master Control Block (BLEND) Page 1 of 3
4.2.8 Alarm and Notification Processing of Blending

Master Control Block (BLEND)
The alarm and notification processing items of the BLEND master include input failure, deviation
error, output failure, loss-of-pulse, alarm off, external EMST command, output stoppage and
connection failure processing.
Alarm and Notification Processing of Blending Master

Control Block (BLEND)
▼ Input Open Alarm, Non-Incoming Pulse Alarm, Level-One Deviation Alarm, Level-Two Deviation
Alarm, Output Shutdown Alarm, Output Open Alarm
Alarm and Notification Processing Items for Blending Master Control Block (BLEND) are shown
below:
Table 4.2.8-1 Table of Alarm and Notification Processing Items for Blending Master Control
Block (BLEND)
No. Processing Item Provided Remarks

1 Input failure (IOP) x By component alarm tracking or by IOP detection in itself
First-stage deviation error
2 x By component alarm tracking
(DV1)
Second-stage deviation error
3 x By component alarm tracking
(DV2)
4 Output failure (OOP) x By component alarm tracking
5 Loss-of-pulse (NPLS) x By component alarm tracking
6 Alarm off (AOFS) x Determined by the designation in the BLEND.
External EMST command By component alarm tracking or by an EMST command to
7 x
(EMST) itself (EMSW=1)
8 Output stoppage (OUTS) x By component alarm tracking
9 Connection failure (CFN) x By component alarm tracking
Alarm Processing - BLEND

Except for control blocks that are being cut off or in the release end status, the BLEND master reads
alarm statuses of all component FSBSET blocks and uses the result to determine its own alarm
status.
The figure below shows the types of failure and corresponding alarm statuses:
• Input failure or output failure: IOP, IOP-, OOP
• Deviation error alarm: DV1, DV2
• Loss of pulse alarm: NPLS
• Output stoppage: OUTS
External EMST Command - BLEND

When an emergency stop command (EMSW=1) is received, the BLEND outputs an alarm (EMST)
and performs emergency stop processing (EMST processing). When an EMST alarm is generated in a
secondary component FSBSET, the alarm status of the BLEND master itself changes to EMST.
Action Upon Occurrence of Alarms in the Blending

Master Control Block (BLEND)
▼ Emergency Stop by OOP/IOP/IOP-/NPLS/DV1/DV2/OUTS Alarms
The control action taken for component FSBSET blocks (EMST or continue) upon occurrence of an
alarm in the BLEND master, can be specified for each alarm type in the builder. However, the
specification on each component FSBSET is invalid; it must be specified in the BLEND master.
The alarms for which control action can be specified are shown below:
Alarm Statuses (Alarm and Notification Processing) of

Blending Master Control Block (BLEND)
Alarm Statuses (Alarm and Notification Processing) for Blending Master Control Block (BLEND) are
shown below:
Table 4.2.8-2 Table of Alarm Statuses (Alarm and Notification Processing) for Blending Master
Control Block (BLEND)

NR Normal No alarm has occurred.
Output open An OOP alarm has occurred in any of the component FSBSETs
OOP
alarm connected.
An IOP alarm has occurred in any of the component FSBSETs connected.
High input-open
IOP Or, a connection-status error on FSBSET/BLENDs at the port or
alarm
component FSBSETs has occurred.
Low input-open An IOP- alarm has occurred in any of the component FSBSETs
IOP-
alarm connected.
First-stage
DV1 A DV1 alarm has occurred in any of the component FSBSETs connected.
deviation alarm
Second-stage
DV2 A DV2 alarm has occurred in any of the component FSBSETs connected.
deviation alarm
An EMST alarm has occurred in any of the component FSBSETs
Emergency stop connected
EMST
alarm Or,an emergency stop has been activated by an EMST command
(EMSW=1).
Loss-of-pulse An NPLS alarm has occurred in any of the component FSBSETs
NPLS
alarm connected.
Connection
CNF A CNF alarm has occurred in any of the component FSBSETs connected.
failure alarm
An OUTS alarm has occurred in any of the component FSBSETs
OUTS Output stoppage
connected.
Alarm/Message Bypass - BLEND

For each of the following alarms, the detection function can be bypassed individually via
specification in the builder:
For all of the following alarms and notifications, the notification functions can be bypassed
collectively by specifying AOFS (alarm off):

IOP-, IOP, DV1, DV2, NPLS, OOP, OUTS, EMST
Control Steps of the Blending Master Control Block

(BLEND) and Applicable Alarm Processing
The table below shows whether alarms are detected at each control step of the Blending Master
Control Block(BLEND).
Table 4.2.8-3 Table of Control Steps for Blending Master Control Block (BLEND) and Applicable
Alarm Processing
Component Alarm Detection (*1)

Control Step Status Deviation Error (*1)
EM-ST Alarm NPLS IOP OOP
0 NON CONTROL
1 SET-UP x x x x
2 I. F. CONTROL x x x x x
3 STEADY x x x x x
4 EARLY x x x x
5 P. B. CONTROL x x x x x
6 WAIT x x
7 END x x
8 EMST x x x
9 EMST END x x
10 START x x
11 RESTART x x
31 BLEND CONTROL x x x x x
32 EMST RESTART x x
30 START x x
*1: x: available
4.2.9 Control Processing of Blending Master Control Block (BLEND) Page 1 of 12
4.2.9 Control Processing of Blending Master Control Block

(BLEND)
Some of the processing performed in each control step of the Blending Master Control Block (BLEND) are
repeated over multiple steps (common processing), while others are performed only in a specific control step.
Control Processing Performed by Blending Master Control

Block (BLEND)
Control Processing Items Performed by Blending Master Control Block (BLEND) are shown below.
Table 4.2.9-1 Table of Control Processing Items Performed by Blending Master Control Block (BLEND)
Item
Purpose Step
Contents Step Functions
No.
If any FSBSETs at the port are in the start status, the
Common 0 Non-Control BLEND changes its own block mode to CAS and moves to
step 30..
1 Set-up SV increase in steps
2 Initial flow rate control Initial flow rate control
3 Steady Steady flow rate control
• Alarm status is set as BPRE.
4 Early
• SV decrements by ΔS.
5 Pre-batch control Flow rate control in pre-batch flow rate setpoint
6 Wait Batch end processing
Tank blending (batch
loader mode) • Moves the control of component FSBSETs to step 26.
7 End • Changes BLEND’s own block mode to MAN and proceeds
to step 0.
During EMST
8 Multistage decrease of SV
processing
9 EMST end Moves the control of component FSBSETs to step 24.
10 Start Changes the mode of component FSBSETs to CAS.
11 Restart Changes the mode of component FSBSETs to CAS.
30 Waiting start Sets start delay timer and moves its own control to step 31.
Direct blending
shipment (relay 31 PI blending control Performs blending control.
mode)
32 EMST Moves the control of component FSBSETs to step 24.
By command from
1-9,
supervisory system
31, 32
Component release
3, 31 Pacing -0 (none)
Others
Pacing -1 (first-stage
3, 31
deviation)
3, 31 Pacing -2 (pressure)
3, 31 Pacing -3
Common Processing - BLEND

This section describes the common processing items of the BLEND master: emergency stop processing, batch-
end detection processing, SV distribution processing, early-point detection processing, pacing and operation
commands. The batch-end processing and early-point detection processing are not performed if an endless
shipment is specified.
Emergency Stop Processing

▼ Emergency Shutdown Specification of All Shipping Outlets
In a tank blending application, if an emergency stop alarm occurs or if the emergency stop command is
received (EMSW≠0 or CMND=4), then the emergency stop status is reset (EMSW=0 or CMND=0) and the
sequence proceeds to emergency stop processing (ZONE 8).
After the completion of its own emergency stop processing, it initiates an emergency stop command to all
component FSBSET blocks.
In the case of direct blending shipment, the emergency stop for all FSBSET blocks of all ports move the blocks
into emergency stop processing (ZONE 32) step. While in the case that the emergency stop command is
triggered by the event other than CMND, the BLEND block may send an emergency stop to all FSBSET blocks
of all ports if the item on the Function Block Detail Builder is specified so. Thus, all the FSBSET blocks move to
emergency stop processing. Item to be defined.
• Emergency Shutdown Specification of All Shipping Outlets
“YES” or “NO”
The default setting is “YES.”
Batch-End Detection Processing

When the totalized value reaches (batch setpoint - predicted leakage value), the SVs of component FSBSET
blocks are set to zero to issue a batch-end command, and the sequence proceeds to WAIT processing (ZONE
6). The conditional expression for batch-end detection is shown below:
SUM≥BSET - VL
SV Distribution Processing
▼ Ratio Control Specification
The BLEND multiplies its SV by each component’s blend ratio and distributes the SV values to each component
FSBSET that is neither in the status “release processing” nor “release processing end.” In this case, however,
no component SV value must exceed the corresponding SV’s range.
For component FSBSET blocks added during the batch action (this must be at the initial step (ZONE 0)), a
start command is sent. If “PPM” is designated for a component FSBSET in a builder, the blending ratio is set
in “PPM” (parts per million) and the units of the component FSBSET are regarded as L/H (the flow rate in
liters per hour) or L (the totalized flow in liters).
The “Ratio Control Specification” parameter of the builder is set as follows:
Ratio Control Specification: Select “%” or “PPM.”
The default is “%.”
• Running port FSBSET with its control valve fully open during direct blending shipment
For a direct blending shipment, one FSBSET at the port can be run with its control valve fully open; if the
sum of the component flow setpoints is set to slightly less than the flow rate setpoint of the port FSBSET,
the output from this FSBSET is gradually opened to fully open. This coefficient (sum of component flow
rate setpoints: sum of port flow rate setpoints) can be “tuned.”
Total of component flow settings=Total of flow setting at port • CPLO
where
CPLO ( throttling prevention coefficient): 0.00 to 100.00 %
Early-Point Detection Processing

▼ Early Detection Bias Time, Width of SV Drop in Early Status
When the end of batch processing (bath end) becomes close, the flow rate starts to decrease gradually. The
early-point detection processing is performed to detect the point at which the flow rate starts to decrease.
When the totalized value reaches or exceeds (batch setpoint - pre-batch quantity - predicted leakage value),
the control step proceeds to ZONE 4 (early-point detection processing). The computational expression is
shown below:
SUM≥BSET-QE-VL
The pre-batch quantity (QE) is calculated as shown below.
During early-point detection processing, the control valve is throttled in preset decrements ΔS. Thus, the
throttling time T can be calculated. T includes the bias time b, and the QE can be calculated using the flow
rate setpoint (SV). The calculation method to obtain QE is shown below:
Where
QE : the pre-batch quantity (L)
SV : the current flow rate setpoint (kl/h)
ΔS : the early-point status setpoint decrement (kl/h)
b : the bias time (seconds)
ΔT : the control period
The figure below shows how the flow rate setpoint (SV) changes during early-point detection processing:
Figure 4.2.9-1 Change in Flow Rate Setpoint (SV) During Early-point Detection Processing
Early-point detection is bypassed when an endless batch (NONB=1) is specified for the BLEND.
• Specifying decrement for early-point detection processing
The setpoint decrement (ΔS) during early-point detection processing is set in the builder.
The “Width of SV Drop in Early Status” parameter of the Function Block Detail Builder is set as follows:
Width of SV Drop in Early Status: 0.001 to 100.000 %
The default is “1.000 %
• Specifying bias time for early-point detection
The bias time for early-point detection (b) is set in the builder.
The “Early Detection Bias Time” parameter of the Function Block Detail Builder is set as follows:
Early Detection Bias Time: 0 to 10000 (unit: basic scan period).
Master Pacing
Execution of master pacing is determined not by a control block but rather by functions outside the control
block; start of pacing is then notified to the block. This judgment is based on the detected alarm status of the
function block.
Examples of alarm detection are listed below:
• when a HI alarm occurs in a specified pressure tag; or
• when DV1 (level-one deviation alarm) occurs in any of the component FSBSET blocks.
The figure below shows the flow of master pacing action:
Figure 4.2.9-2 Flow of Master Pacing Action
When the BLEND master is in the steps where constant-flow control is performed (ZONE 31 or 3) and if the
master pacing setpoint (MPSP) is set, the BLEND maintains its current SV while distributing the master pacing
SV (MPSV) to the components. The MPSV is initially same as the SV at the start of master pacing, and is
changed in steps in set increments/decrements during each control period until it agrees with the target value
(MPSP • SV). The degree of this increment/decrement is set separately from the SV set-up increment (STUP)
or set-down decrement (STDN) in normal operation, but by master pacing set-up increment (MPUP) and set-
down decrement (MPDN).
Master Pacing applies to ZONE3 or ZONE31 only. It does not apply to other zones where the MPSP is always
set to 100%. If the zone moves to zone other than ZONE3 or ZONE31 during Master Pacing, the MPSP
immediately returns to 100%, but step-up or step-down processing to return the MPSV to an SV continues.
The figure below shows how the EMST step-down processing occurs during Master Pacing.
Figure 4.2.9-3 Example of Change in MPSV During Pacing
Manual Operation
▼ MAN Intervention Processing
The automatic control of BLEND block may be intervened by changing the block mode into MAN. However, if
MAN intervention processing is specified on the Function Block Detail Builder, the BLEND block may behave
the same as it is in AUT mode to transit its status when receiving EMST command or when batch end
detected. At this time, the block mode changes to AUT or CAS. Item to be defined.
MAN Intervention Processing: “YES” or “NO”
The default setting is “NO.”
Operation Commands
During tank blending control, the BLEND master can be operated via operation commands (CMNDs).
During direct blending shipment control, the BLEND master itself monitors the FSBSET blocks at the port and
performs automatic operation. Therefore, an operator cannot operate the BLEND master directly.
The figure below shows the action of BLEND by operation commands during tank blending control. The figure
below shows the action of a batch loader FSBSET in response to operation commands (CMNDs). The
operation commands (1) through (4) in the figure indicate when the start, emergency stop, restart and reset
(abort) commands are issued.
Figure 4.2.9-4 Action of BLEND by Operation Commands
• Start
Start processing is executed by changing the block mode to CAS or AUT and setting (CMND=1).
• Emergency stop
Emergency stop processing is executed by setting (EMSW=1) or (CMND=4).
• Restart
Restart processing is executed by setting (CMND=2) only when the block mode is AUT or CAS.
• Forced reset (abort)
Setting (CMND=3) will automatically change the block mode to the mode at the start, and batch-end
processing is executed.
Processing in Each Control Step - BLEND

Processing Items Performed in Each Control Step of BLEND are shown below.
Table 4.2.9-2 Table of Processing Items Performed in Each Control Step of BLEND
Sum
Flow Rate
of Batch
Distribution Early Pacing
Control Block Initialization Emergency SVs End
Status (SV Detection Function
Step Mode (*1) Stop(*1) at Detection
distribution) (*1) (*1)
Port (*1)
(*1)
(*1)
0 NON MAN
CONTROL
CAS
1 SET-UP x x x
(AUT)
I. F. CAS
2 x x x x
CONTROL (AUT)
CAS
3 STEADY x x x x x
(AUT)
CAS
4 EARLY x x x
(AUT)
P. B. CAS
5 x x x
CONTROL (AUT)
CAS
6 WAIT x
(AUT)
CAS
7 END
(AUT)
CAS
8 EMST x x
(AUT)
EMST CAS
9 x
END (AUT)
CAS
10 START x
(AUT)
CAS
11 RESTART
(AUT)
BLEND CAS
31 x x x x
CONTROL (AUT)
EMST CAS
32 x
RESTART (AUT)
CAS
30 START x
(AUT)
*1: x: Yes
The following describes the processing performed in a specific control step:
ZONE 0 (Control Status: NON-CONTROL)

When the port FSBSET/BLEND block is in operation (in zone other than ZONE0 or ZONE7) in the MAN block
mode, the block mode of the BLEND block turns to CAS, proceeding to ZONE30.
ZONE 1 (Control Status: SET-UP)

▼ SET UP Interval Time, Initial Flow Speed SET UP End Waiting Time, Normal Flow Speed SET UP End Waiting
Time
When a batch cycle is started, or the flow rate setpoint (final flow rate setpoint: SVH; or initial flow rate
setpoint: SVL) is updated, the current flow rate setpoint (SV) is changed in steps during each control period
until it agrees with the target value (SVL or SVH), after the SET-UP waiting time (t0: 1 second, fixed) has
elapsed. When the SV reaches or overshoots the target value, it is held at the current value (where SV=target
value) for a certain predefined WAIT time, before processing proceeds to the next control step.
The intervals in which the SV is changed in steps is specified in the builder.
The “SET-UP Interval Time” parameter of the Function Block Detail Builder is set as follows:
• SET-UP Interval Time
The increments in which the SV is changed in steps are specified as the STUP data item (SV SET-UP
increment), while the decrements are specified as the STDN data item (SV SET-DOWN decrement).
The waiting time when the target value is reached is specified in the builder.
The “Initial Flow Speed SET UP End Waiting Time” and “Normal Flow Speed SET UP End Waiting Time”
parameters of the Function Block Detail Builder are set as follows:
• Initial Flow Speed SET UP End Waiting Time
0 to 10000 (unit: basic period).
• Normal Flow Speed SET UP End Waiting Time
0 to 10000 (unit: basic period).
In this step, emergency stop processing, batch-end detection processing, early-point detection processing and
SV distribution processing are performed as common processing.
Figure 4.2.9-5 SET-UP and SET-DOWN Processing
In ZONE 1, initial flow rate control is needed when the following conditions are met. Therefore, the initial flow
rate setpoint (SVL) is adopted as the target value during SET-UP processing.
ILSW=1 (initial flow rate control command)
ILST > SUM (the totalized flow is less than the initial totalized flow setpoint)
If the above conditions are not met while setting up toward SVL, SET-UP toward SVH is started immediately.
After SET-UP is completed, if the above conditions are met, then the step proceeds to initial flow rate control
(ZONE 2); if they are not, it proceeds to STEADY (ZONE 3).
ZONE 2: Initial Flow Rate Control

Initial flow rate control is carried out.
If the initial flow rate setpoint (SVL) is updated, control proceeds to ZONE 1, making the SVL the target value.
When initial flow rate control is released or when the totalized flow reaches the initial totalized flow setpoint,
the final flow rate setpoint (SVH) is used as the target value and the control proceeds to ZONE 1.
ZONE 3 (Control Status: STEADY)

In this step, the setpoint value (SV) is held at the final flow rate setpoint (SVH).
If the SVH is updated, control proceeds to ZONE 1.
ZONE 4 (Control Status: EARLY)

The flow rate setpoint (SV) is decreased in steps by ΔS. The throttling calculation is shown below:
SVn=SVn-1 - ΔS
When SVn≤SVPR is reached, control proceeds to ZONE 5 with the setting of SV=SVPR.
The figure below shows the throttling process until SVn≤SVPR is reached:
Figure 4.2.9-6 Early-Point Detection Processing
In this step, emergency stop processing, batch-end detection processing and SV distribution processing are
performed as common processing.
ZONE 5 (Control Status: PRE-BATCH-CONTROL)

The SV is held at SVPR (flow rate setpoint for pre-batch) until the totalized value reaches the “pre-batch”
totalized setting, then control proceeds to ZONE 6.
In this step, emergency stop processing, batch-end detection processing and SV distribution processing are
performed as common processing.
ZONE 6 (Control Status: WAIT)

▼ Waiting Time during Batch End
During the waiting time for batch end, the BLEND master sets 0 for the SVs of component FSBSET blocks that
are neither being released nor in the release end status and sends them an “Wait for END” command. Also,
component FSBSET blocks operating in the MAN mode are forced to change to the CAS mode.
Then, the BLEND master WAITs a certain predetermined time to allow for leakage.
The totalized value is stored as the previous totalized value, and control proceeds to ZONE 7 after batch end
processing.
The “Waiting Time during Batch End” parameter of the Function Block Detail Builder is set as follows:
Waiting Time during Batch End: 0 to 10000 (unit: basic period).
ZONE 7 (Control Status: END)

▼ Waiting Time during End Process Completion, Configuring Devices Clear at Batch End
After again WAITing a certain predetermined time, the BLEND master performs the following processing:
• It sends an END command to component FSBSET blocks that are neither being released nor in the release
end status. Component FSBSET blocks operating in the MAN mode are forced to change to the CAS mode.
• If the BLEND master is set in the builder to clear configuration data at batch end, this sequence clears the
port and component tag names from the control buffer. The block mode then changes to MAN and control
returns to ZONE 0.
The time of WAIT processing is set in the Function Block Detail Builder.
The “Waiting Time during End Process Completion” parameter of the builder is set as follows:
• Waiting Time during End Process Completion

The “Configuring Devices Clear at Batch End” parameter of the Function Block Detail Builder is set as follows:
• Configuring Devices Clear at Batch End
ZONE 8 (Control Status: EMERGENCY STOP)

▼ Width of SV Drop in Emergency Shutdown Status
This step closes the control valve in steps, with control proceeding to ZONE 8 when an emergency stop alarm
is generated or an emergency stop command is detected.
The SV is decreased by ΔSE in steps until it reaches 0.
SVn = SVn-1 - ΔSE
Where
ΔSE : the decrement of SV in the EMST status
When SV≤0 is reached (note that PV≤0 is not monitored), the BLEND master performs the following
processing:
• It sends an EMST command to component FSBSET blocks that are neither being cut off nor in the release
end status. Component FSBSET blocks operating in the MAN mode are forced to change to the CAS mode.
• The BLEND master itself proceeds to ZONE 9.
The figure below shows the throttling of SV during emergency stop processing:
Figure 4.2.9-7 Throttling of SV During Emergency Stop Processing
The decrement of SV in the EMST status is specified in the builder.

The “Width of SV Drop in Emergency Shutdown Status” parameter of the Function Block Detail Builder is set
as follows:
Width of SV Drop in Emergency Shutdown Status: 0.001 to 100.000 %.
The default is “1.000 %”
ZONE 9 (Control Status: EMST END)

▼ Batch End Detection during Emergency Shutdown
After the BLEND master sends an EMST command to component FSBSET blocks that are neither being cut-off
nor in release end status, the BLEND block may continue to detect the batch end status if it is defined on the
Item to be defined.
Batch End Detection during Emergency Shutdown: “YES” or “NO”
The default setting is “YES.”
ZONE 10 (RESET START)
The BLEND master sends a start command to component FSBSET blocks.

The BLEND master proceeds to ZONE 1, changing its alarm status to NR.
ZONE 11 (Control Status: RESTART FROM EMST)

The BLEND master sends a restart command to component FSBSET blocks that are neither being cut off nor
in the release end status. For the component FSBSET blocks that have not been started, it sends a start
command.
The BLEND master proceeds to ZONE 1, changing its alarm status to NR.
ZONE 31 (Control Status: BLEND CONTROL)

Blending control is carried out.
• End processing
When all the FSBSET/BLEND blocks at the port are in the end status (ZONE 7) or initial status (ZONE 0),
the BLEND master issues an END command to component FSBSET blocks that are neither being cut off nor
in the release status.
The BLEND master returns to the initial status (ZONE 0) after changing its block mode to MAN.
• Emergency stop processing
When all the FSBSET blocks/BLENDs at the port are in the emergency stop status (ZONE 9), the BLEND
master issues an EMST command to component FSBSET blocks that are neither being cut off nor in the
release status.
The BLEND master changes its status to emergency stop processing (ZONE 32).
• SV distribution processing
If the conditions for end processing or emergency stop processing are not met, the total of the defined
flow rate (kl/h) or instantaneous flow rate (specified on the Function Block Detail Builder) of the port
FSBSET/BLEND blocks is calculated as an SV of the BLEND block. And after multiplying its SV by each
blending ratio, the value is set to the SV of component FSBSET block that is neither released nor
completed to release.
However, this setpoint for each component must not exceed the range of the component’s SV.
A start command is sent to all component FSBSET blocks that are in the initial status (ZONE 0).
ZONE 32 (Control Status: EMST)

The BLEND master is in the emergency stop status.
The BLEND master sends an EMST command to all component FSBSET blocks that are neither being cur off
nor in the release end status. However, if even one of the FSBSET blocks/BLENDs at the port is not in the
emergency stop status, the BLEND master returns to ZONE 31 and performs SV distribution processing.
If all the FSBSET/BLEND blocks at the port are in the end status (ZONE 7) or initial status (ZONE 0), the
BLEND master issues an END command to component FSBSET blocks that are neither being cut off nor in the
release status. The BLEND master returns to the initial status (ZONE 0) after changing its block mode to MAN.
ZONE 30 (Control Status: START)

▼ COMP Start Delay Time
The BLEND master sets the start delay timer, then performs the following processing after WAITing for a
preset period of time (set by the start delay timer):
• The BLEND master sends a start command to component FSBSET blocks and proceeds to ZONE 31.
• It uses a start delay timer to adjust the times between when port FSBSET blocks are started and when
component FSBSET blocks are started, and reduces or eliminates pressure-related interference between
components.
The figure below shows the start delay processing by the BLEND master:
Figure 4.2.9-8 Start Delay for Port FSBSET Blocks and Component FSBSET Blocks
The start delay timer setting is specified in the builder.

The “COMP Start Delay Time” parameter of the Function Block Detail Builder is set as follows:
COMP Start Delay Time: 0 to 10000 (unit: basic scan period).
Control Step Transition Diagram - BLEND

The figure below shows the control step transition diagram:
Figure 4.2.9-9 FigureControl Step Transition Diagram of Blending Master Control Block (BLEND)
Commands - BLEND
Commands Available with BLEND are shown below.
Table 4.2.9-3 Table of Commands Available with BLEND
CMND Zone (Step) Status Description of Command

0
1 10 Supervisory setting Batch controller - start
2 11 Supervisory setting Batch controller - restart
3 6 Start mode Batch controller - abort
4 8 Start mode Batch controller - EMST
4.2.10 Block Modes of Blending Master Control Block (BLEND) Page 1 of 1
4.2.10 Block Modes of Blending Master Control Block

(BLEND)
The block modes of the BLEND include out of service, initialization manual, manual, automatic and
cascade.
Block Modes of Blending Master Control Block (BLEND)

Block Modes for Blending Master Control Block (BLEND) are shown below.
Table 4.2.10-1 Table of Block Modes for Blending Master Control Block (BLEND)

Out of
O/S All functions are stopped.
Service
MAN MANual Control calculation is stopped.
AUT AUTomatic Control calculation is performed and the results are output.
When used in direct blending shipment, a control computation is performed
CAS CAScade using the setpoint input from the supervisory block and the results are output.
When used in tank blending, the action is the same as AUT above.
4.2.11 Data Items of Blending Master Control Block (BLEND) Page 1 of 5
4.2.11 Data Items of Blending Master Control Block

(BLEND)
There are 147 data items that can be set with the BLEND. Multiple settings are available for port
tags, component tags, blending ratios, totalized values of components and component status flags.
Data Items of the Blending Master Control Block

(BLEND)
Data Items Set with Blending Master Control Block (BLEND) are shown below.
Table 4.2.11-1 Table of Data Items Set with Blending Master Control Block (BLEND)
Data Entry
Data Item Range/Unit Default
Name (*1)
O/S
MODE Block mode x -----
(MAN)
BSTS Block status N/A ----- 0
ALRM Alarm status N/A ----- NR
AFLS Alarm flashing status N/A ----- 0
AF Alarm detection specification N/A ----- 0
AOFS Alarm masking specification N/A ----- 0
PV Instantaneous flow rate Cond. SL
PV
SV Setpoint of flow rate x SL
PV
SVPR Flow rate setpoint for pre-batch x SL to SH SL
SVH Final flow rate setpoint x SL to SH SL
SVL Initial flow rate setpoint x SL to SH SL
Setting to release initial flow rate
ILST x Industrial unit used for SUM 0
control
VL Predicted leakage value x Industrial unit used for SUM 0
SUM Totalized corrected value x Industrial unit used for SUM 0
BSET Batch setpoint x Industrial unit used for SUM 0
CMND Command switch x 0-63 0
ZONE Control step N/A 0-63 0
EMSW Emergency-stop command switch x 0 or 1 0
NONB Endless-batch command switch x 0 or 1 0
Command switch for initial flow rate
ILSW x 0 or 1 0
control
EMCD EMST factor code N/A 0-32, 767 0
EMCP[16] EMST factor tag N/A ----- NULL
STUP SV set-up increment x 0.00-100.00 % 1.00
STDN SV set-down decrement x 0.00-100.00 % 2.00
MS01[16] Port tag 1 (for execution) N/A 16 alphanumeric characters NULL

CP01[16] Component tag 01 (for execution) N/A 16 alphanumeric characters NULL
CR01 Blending ratio 01 (for execution) N/A 0.000-10,000.000 0.000
SM01 Totalized value of component 01 x Industrial unit used for SUM 0
SM11
Totalized value of component 11 x Industrial unit used for SUM 0

Component 01 status flag (for
LC01 N/A 0-3 0
execution)
LC02 N/A 0-3 0
execution)
LC03 N/A 0-3 0
execution)
LC04 N/A 0-3 0
execution)
LC05 N/A 0-3 0
execution)
LC06 N/A 0-3 0
execution)
LC07 N/A 0-3 0
execution)
LC08 N/A 0-3 0
execution)
LC09 N/A 0-3 0
execution)
LC10 N/A 0-3 0
execution)
LC11 N/A 0-3 0
execution)
LC12 N/A 0-3 0
execution)
LC13 N/A 0-3 0
execution)
LC14 N/A 0-3 0
execution)
WP01[16] Component tag 01 (for setting) x 16 alphanumeric characters NULL
WR01 Blending ratio 01 (for setting) x 0.000-10,000.000 0.000

WL01 Component 01 status flag (for setting) x 0-3 0
Component configuration change
MOD1 x —- 0
command
MOD2 Port change switch x —- 0
MSMD[16] Port tag to be changed x —- NULL
CPLO Throttling prevention coefficient x 0.00-100.00 % 100.00
MPSV Master pacing SV x SL
PV
MPSP Master pacing factor x 0.00-100.00 % 100.00
MPUP Master pacing set-up increment x 0.00-100.00 % 1.00
MPDN Master pacing set-down decrement x 0.00-100.00 % 2.00
DSM Instantaneous flow after corrections N/A Industrial unit used for SUM 0
Y01-Y04 Optional buffer 1-4 x -100.00000-100.00000 0
Y05-Y09 Optional buffer 5-9 x -32,768-32,767 0

OPMK Operation mark x 0-64 0
SH Scale high limit N/A 0
PV
SL Scale low limit N/A 0
PV
CRD Ratio control designation N/A 0 or 1 0
*1: x: entry possible
Cond.: entry possible under certain conditions
N/A: entry not possible
5. System Function Blocks Page 1 of 2
5. System Function Blocks

The system function blocks can be used by the users for freely displaying the FCS running statuses
and internal resources on HIS graphic views. This feature is available in FFCS-C and FFCS-V.
Position of System Function Blocks

The system function blocks are positioned for displaying the FCS running statuses and internal
resource information with the same style of the other types of FCS function blocks. The FCS internal
resource information can be notified to or accessed by the external functions. However, the FCS
resource information cannot be manipulated.
Figure 5-1 Position of System Function Blocks
Outline of System Function Block Features

The system function blocks can be used in the same manner as using the other types of function
blocks for displaying the FCS running statuses and internal resource information.
The system function blocks can provide the following information:
• CPU load information
• Communication load information
• I/O load information
5. System Function Blocks Page 2 of 2
• SEBOL related information

The system function blocks are available in FFCS-C and FFCS-V. The FCSs other than FFCS-C and
FFCS-V do not have this feature.
The data of system function blocks can be displayed on graphic or trend windows on HIS.
The system function blocks will be automatically generated when a FCS is created and defined on
SystemView.
Users cannot define the tag names for the system function blocks.
The security level of the system function blocks cannot be changed on the
builder. The security level is fixed to level 4.
• The privilege level for monitoring is S1 (OFF User).
• The privilege level for changing MODE is S2 (ON User) or higher.
5.1 Common Features of System Function Blocks Page 1 of 2
5.1 Common Features of System Function

Blocks
The common features of system function blocks will be explained in this section.
Operating Environment
System function blocks are available in FFCS-C and FFCS-V.
Though the system function blocks can also run on FFCS-C simulator and FFCS-V simulator, the
displayed resource information will be different from that of actual FCS. Thus the system load data
obtained from the FFCS-C simulator or FFCS-V simulator cannot be used for evaluation of the real
system load.
Process Timing
The data acquisition of system function blocks will be performed at the beginning of each basic
scan. The real data of the previous scan will be held until the next scan. However, the data
acquisition for high-speed scan blocks will be performed before the system function blocks since the
system function blocks are basic scan blocks.
Block Mode and Status

The common features of system function block mode and block status will be explained in this
paragraph.
SEE For more information about the specific features of each type of system function blocks, refer to:
ALSO 5.4, "System Function Block Types"
Block Mode
Block mode is a data item to indicate the system function block mode. The system function blocks
have the following modes:
Table 5.1-1 System Function Block Modes
Mode Description
O/S All services become Out of Service mode
MAN Function block stops updating, the previous data will be held.
AUT Function block periodically updates and performs data acquisition.
When changing the block from a mode to AUT, the previously held statistic summery data, such as
maximum and minimum values, will be initialized.
SEE For more information about the data initialization of each type of system function blocks, refer to:
5.1 Common Features of System Function Blocks Page 2 of 2
Block Status
System function blocks do not have the Block Status data item.
Alarm Status
System function blocks do not have alarms for Alarm Status data item. The alarm status is fixed to
NR (Normal) status only.
After Starting FCS

After starting FCS, the block mode and the previous statistic summaries of system function blocks
may be initialized.
• Initial Cold Start: The block mode will become AUT and all the previous statistic summaries will
be initialized.
• Restart: Previous block mode and static summaries will be retained.
• After offline downloading: Same as the initial cold start, the block mode will become AUT and all
the previous statistic summaries will be initialized.
Saving Tuning Parameters

When saving FCS tuning parameters, the parameters of system function blocks will also be saved.
The snapshot saving and downloading of Test Function environment are also supported.
5.2 System Function Block Data Reference Page 1 of 1
5.2 System Function Block Data Reference

How to reference the system function block data will be explained in this section.
Data Reference in FCS

In an FCS, the data of system function blocks cannot be referenced by other function blocks.
Similarly, data references from the other FCS through the inter-station link blocks (ADL) are not supported
either.
Displaying on HIS
By designating the data items, the data of system function blocks can be displayed on HIS for operation and
monitoring purposes.
Faceplate
The faceplate of each type of system function blocks can display the typical data of system function blocks in
digital style. No data bar or tuning button is displayed on the faceplate.
Tuning View
On the tuning view of system function block, there is no tuning trend. However, you can assign a data item to
a trend pen on a trend view so as to display the trend.
Trend
The data of the system function blocks can be assigned to the trend pens for displaying on trend views. The
data can be assigned to various sampling period trends including 1-second period trends. However, when
assigning the data of system function blocks to trend pens, the data ranges need to be manually defined.
Data Reference Syntax of System Function Blocks

For displaying the data of system function blocks on HIS, the syntax for designating the data item is as
follows:
%BLnnnnSddmm01.<Data Item>
nnnn: Block Number
dd: Domain Number
mm: Station Number
Block Number
The numbering of system function blocks is as follows:
• %BL0001 : CPU Load Information
• %BL0002 : Communication Load Information
• %BL0003 : I/O Load Information
• %BL0004 : SEBOL Related Information
SEE For more information about the ranges of system function block data, refer to:
5.3 FCS Performance Index Page 1 of 1
5.3 FCS Performance Index

The numerical performance indexes can be placed for data items of system function blocks so as to provide
the references for the displayed numerical data. The performance indexes are calculated according to the
various factors. For an example, the expected performance of the CPU usage is calculated according to the
number of basic control loops and this index will be used when perform engineering works. However, the
performance may vary with complexity of control functions. You can use the reference for optimizing the idle
capacities.
Performance Indexes and Their Displays

The FCS performance indexes include the following:
• Number of control loops
• I/O access factor
• Communication target factor
With the performance indexes (PI), you can figure out the idle capacity of the FCS. For example, you can put
the performance data into a trend graph using the high limit of the performance index for the FCS as the
high limit of the trend scale. The scale high limit can also be 100 % with the scale low limit of 0 %.
Definitions of Performance Indexes of FFCS-C and FFCS-V

The following table shows the performance indexes and the definitions of the performance indexes.
The high limit of the index is for FFCS-C and FFCS-V. Other types of FCS are not supported.
Table 5.3-1 Performance Indexes of FFCS-C and FFCS-V
High
Limit
for
Category Usage Index Definition of Performance Index
FFCS-C
and
FFCS-V
Number of basic control loops that the CPU
can process per unit of time (1-second scan
Control Number of
Main CPU capacity 2300 period). A PID block with an analog input, a
processing control loops
manipulated output and the control algorithm
is deemed as a basic control loop.
For FFCS-V, capacity of ESB bus for processing
the I/O signals per unit of time (1-second scan
period). The I/O access factor of 1 stands for
the ESB capacity of processing the data of one
Capacity of N-ESB FIO analog I/O module.
I/O bus communication I/O access For FFCS-C, the total capacity of N-ESB bus
3000
communication and ESB bus factor and ESB bus for processing the I/O signals per
communication unit of time (1-second scan period). The
amount of data for one N-IO I/O module is
the same as that for one FIO analog I/O
module. Therefore, the I/O access factor is
calculated as 1 for both of these modules.
FCS control The communication target factor equals to 1
Control Communication
communication 20 stands for the capacity of communicating 20
communication target factor
capacity frames and each frame contains 32 data.
5.4 System Function Block Types Page 1 of 1
5.4 System Function Block Types

System function blocks consist of the followings:
• CPU Load Information Block (FCS_CPU)
• Communication Load Information Block(FCS_COM)
• I/O Load Information Block (FCS_IOC)
• SEBOL Related Information Block (FCS_SBL)
5.4.1 CPU Load Information Block (FCS_CPU) Page 1 of 3
5.4.1 CPU Load Information Block (FCS_CPU)

The CPU load information block is used for displaying the CPU usage and processing time of FCS
applications.
Data Items
Table 5.4.1-1 Data Items of CPU Load Information Block (FCS_CPU)
Data Type Entry FCS Initialization

Data Name Range Default
Item (*1) (*2) Simulation (*3)
O/S
MODE Block mode U32 Y N N N
(AUT)
ALRM Alarm status U32 N N NR N N
AFLS Alarm flashing U32 N N 0 N N
AF Alarm detection U32 N N 0 N N
AOFS Alarm inhibition U32 N N 0 N N
MRGN Basic CPU idle capacity U32 N 0 to PI 0 0 Fixed N
MRGE Actual CPU idle capacity U32 N 0 to PI 0 0 Fixed N
CPU usage - 0 to 100
CUR U32 N 0% 0 Fixed N
Instantaneous %
0 to 100
CURA CPU usage - Average U32 N 0% 0 Fixed N
%
0 to 100
CURH CPU usage - Maximum U32 N 0% 0 Fixed Y
%
0 to 100
CURL CPU usage - Minimum U32 N 0% 0 Fixed Y
%
1000 ms
SCNT Basic scan period U32 N 1000 ms N N
Fixed
Basic scan processing 0 to
SCN U32 N 0 ms 0 Fixed N
time - Instantaneous 1000 ms
SCNH U32 N 0 ms 0 Fixed Y
time - Maximum 1000 ms
SCNL U32 N 0 ms 0 Fixed Y
time - Minimum 1000 ms
0 to
HSCT High-speed scan period U32 N 0 ms N N
1000 ms
High-speed scan
0 to
HSC processing time - U32 N 0 ms 0 Fixed N
1000 ms
Instantaneous
High-speed scan
0 to
HSCH processing time - U32 N 0 ms 0 Fixed Y
1000 ms
Maximum
High-speed scan
0 to
HSCL processing time - U32 N 0 ms 0 Fixed Y
1000 ms
Minimum
Medium-speed scan 0 to
MSCT U32 N 0 ms N N
period 1000 ms
MSC Medium-speed scan U32 N 0 ms 0 Fixed N

processing time - 0 to
Instantaneous 1000 ms
Medium-speed scan
0 to
MSCH processing time - U32 N 0 ms 0 Fixed Y
1000 ms
Maximum
Medium-speed scan
0 to
MSCL processing time - U32 N 0 ms 0 Fixed Y
1000 ms
Minimum
UAID User ID I16 Y N N N N
OPMK Operation mark I16 Y 0 to 64 N N N
*1: Data type U32: 32-bit unsigned integer I16: 16-bit signed integer
*2: Allow user to enter a value to the item Y: Yes, N: No
*3: IInitialize the block when changing mode Y: Yes, N: No
Descriptions of Data Items

The symbols and the meanings of data items of CPU load information block are as follows:
• MRGN
Displays the idle time of CPU processes including the timeshare type SEBOL processes in regard
of performance index.
• MRGE
Different from MRGN, this displays the idle time of CPU processes excluding the timeshare type
SEBOL processes in regard of performance index.
• CUR
Displays CPU usage rate of FCS. This indication includes the periodic type SEBOL processes but
excludes the timeshare type SEBOL processes.
• CURA
Display the moving average of past 60 samples (60 seconds) of CUR.
• CURH, CURL
Displays the largest and smallest CUR so far.
• SCN
Displays processing time of basic scan. This indication includes the periodic type SEBOL
processes but excludes the timeshare type SEBOL processes. Moreover, the processing time
interrupted by high-speed and medium-speed scan processes is excluded. However, the
processing time for online maintenance and saving the tuning parameters are included.
• SCNH, SCNL
Displays the largest and smallest SCN so far.
• HSC
Displays processing time of high-speed scan. HSCH and HSCL respectively display the largest and
smallest HSC so far.
• MSC
Displays processing time of medium-speed scan. The processing time interrupted by high-speed
processes is excluded.
• MSCH, MSCL
Displays the largest and smallest MSC so far.
SEE For more information about the performance index, refer to:
ALSO " Performance Indexes and Their Displays" in 5.3, "FCS Performance Index"
For more information about SEBOL executions, refer to:
7.1.2, “Order of Process Execution” in Function Blocks Overview (IM 33J15A20-01EN)
Assign Data to Trend Pen

The data of MRGN or MRGE can be assigned to a trend pen and use the high limit of CPU
performance index as the high limit of the trend scale for displaying the idle capacity.
Displays on FCS Simulator

This system function block can work on FCS simulator too. However, the displays are different from
the physical FCS.
The displays of SCNT, HSCT and MSCT (scan periods) will be the values defined on the builder while
the other items will be fixed to 0.
5.4.2 Communication Load Information Block (FCS_COM) Page 1 of 4
5.4.2 Communication Load Information Block (FCS_COM)

The communication load information block is used for displaying the FCS control communication load
status.
Data Items
Table 5.4.2-1 Data Items of Communication Load Information Block (FCS_COM)

O/S
MODE Block mode Item U32 Y N N N
(AUT)
Communication idle
MRGN U32 N 0 to PI 0 N N
capacity
Number of outward
TRC communication frames - U32 N N 0 N N
Instantaneous
Number of outward
TRCH communication frames - U32 N N 0 N Y
Maximum
Processing time of
0 to
TRT outward communication - U32 N 0 ms N N
1000 ms
Instantaneous
Processing time of
0 to
TRTH outward communication - U32 N 0 ms N Y
1000 ms
Maximum
Number of overflow
TRO U32 N N 0 N N
frames - Instantaneous
Number of overflow
TROH U32 N N 0 N Y
frames - Maximum
Number of overflow
TROV U32 N N 0 N Y
occurrences
Number of 1-second
TRN U32 N N 0 N N
trend assignments
Number of inward
TSC communication frames - U32 N N 0 N N
Instantaneous
Number of inward
TSCH communication frames - U32 N N 0 N Y
Maximum
Number of tag list query
TST U32 N N 0 N N
frames - Instantaneous
Number of tag list query
TSTH U32 N N 0 N Y
frames - Maximum
THIS HIS for tag list queries U32 N N 0 N N
Total number of message

MEST U32 N N 0 N Y
communication frames
MRRT U32 N N 0 N Y
retransmission requests
Number of retransmission
MRS message frames - U32 N N 0 N N
Instantaneous
Number of retransmission
MRSH message frames - U32 N N 0 N Y
Maximum
MRST U32 N N 0 N Y
retransmission frames
Number of unsent
MBL messages - U32 N N 0 0 Fixed N
Instantaneous
Number of unsent
MBLH U32 N N 0 0 Fixed Y
messages - Maximum
*1: Data type U32: 32-bit unsigned integer I16: 16-bit signed integer
*2: Allow user to enter a value to the item Y: Yes, N: No
*3: Initialize the block when changing mode Y: Yes, N: No

The symbols and the meanings of data items of communication load information block are as
follows:
MRGN and the items prefixed with TR are used for displaying the information relevant to the data
communication with other stations.
• MRGN
Displays the idle capacity of communication processing against the maximum capacity specified
for the system in regard of communication target index (Performance Index of communication
load).
• TRC
Displays the instantaneous number of frames for referencing tags and common data exchanged
with other stations per second.
• TRCH
Displays the largest TRC so far.
• TRT
Displays the instantaneous processing time (unit: ms) for processing the frames of referencing
tags and common data exchanged with other stations per second. This datum is the identical
datum of Comm Load displayed in Station Status Display window on HIS.
• TRTH
Displays the largest TRT (unit: ms) so far.
• TRO
Displays the instantaneous number of erroneous overflow frames for referencing tags and
common data exchanged with other stations per second.
• TROH
Displays the largest TRO so far.
• TROV
Displays the total number of communication overflow occurrences.
• TRN
Displays the number of 1-second trend assignments. The communication load of 1-second trend
is not included in TRC and TRT. However, the communication load of the trend with a sampling
period longer than one second is included in TRC and TRT.
The items prefixed with TS are used for displaying the information relevant to the communications
for function block data referencing and data setting (such as ADL and SEBOL related
communications) within the local station.
• TSC
Displays the instantaneous number of frames for referencing tags and common data exchanged
within the local station per second.
• TSCH
Displays the largest TSC so far.
• TST
Displays the instantaneous number of frames for querying the tag list between local station and
HIS per second.
• TSTH
Displays the largest TST so far.
• THIS
Displays the address of the HIS for tag list queries. The address is a decimal integer, the last two
digits are station address and the domain address is indicated by the digits from the third from
the last.
The items prefixed with M are used for displaying the information relevant to the message
communication.
• MEST
Displays the total number of message communication frames. This number is different from the
total number of messages. Moreover, the message retransmission frames are not included.
• MRRT
Displays the total number of message retransmission requests sent from the HIS.
• MRS
Displays the instantaneous number of message retransmission frames per second.
• MRSH
Displays the maximum number of message retransmission frames per second.
• MRST
Displays the total number of message retransmission frames.
• MBL
Displays the instantaneous number of unsent messages per second.
• MBLH
Displays the maximum number of unsent messages per second.

The data of MRGN can be assigned to a trend pen and use the high limit of control communication
performance index as the high limit of the trend scale for displaying the idle capacity.

This system function block can work on FCS simulator too.
However, the displays of TRT (Processing time of outward communication - Instantaneous) and
TRTH (Processing time of outward communication - Maximum) are different from the physical FCS;
each transaction for function block data referencing and data setting is counted for 0.5 ms while
each transaction for common data is counted for 2 ms.
The processing times for other data are identical with the physical FCS.
5.4.3 I/O Load Information Block (FCS_IOC) Page 1 of 2
5.4.3 I/O Load Information Block (FCS_IOC)

The I/O load information block is used to indicate the CPU loads related to communications with I/O
modules.
For FFCS-C, this function block indicates the load resulting from communications with FIO modules
and N-IO modules.
Data Items
Table 5.4.3-1 Data Items of I/O Load Information Block (FCS_IOC)

O/S
(AUT)
I/O Communication idle
MRGN U32 N 0 to PI 0 0 Fixed N
capacity
Total load of I/O
TTL U32 N 0 to PI 0 0 Fixed N
communication
Total load of I/O
TTLH communication - U32 N 0 to PI 0 0 Fixed Y
Maximum
Load of control
CTL U32 N 0 to PI 0 0 Fixed N
communication
Load of control
CTLH communication - U32 N 0 to PI 0 0 Fixed Y
Maximum
Load of SOE
SOE U32 N 0 to PI 0 0 Fixed N
communication
Load of SOE
SOEH communication - U32 N 0 to PI 0 0 Fixed Y
Maximum
Load of device data
DC U32 N 0 to PI 0 0 Fixed N
communication
Load of device data
DCH communication - U32 N 0 to PI 0 0 Fixed Y
Maximum
Load of base
BS U32 N 0 to PI 0 0 Fixed N
communication
Load of base
BSH communication - U32 N 0 to PI 0 0 Fixed Y
Maximum
*1: Data type
U32: 32-bit unsigned integer
5.4.3 I/O Load Information Block (FCS_IOC) Page 2 of 2
I16: 16-bit signed integer

*2: Allow user to enter a value to the item
Y: Yes
N: No
*3: Initialize the block when changing mode
Y: Yes
N: No

The symbols and the meanings of data items of I/O load information block are as follows:
• MRGN
Displays the idle capacity of I/O communication in regard of I/O access index (Performance Index
of I/O communication).
• TTL
Display the total I/O communication load per second. The total means the sum of the
communication loads of the CTL, SOE, DC and BS items to be described below.
• CTL
Displays the load of control data I/O communication of various scans per second. This
communication load includes the load of data refresh, data flash, instantaneous output,
predictive output and MC instrument inching output communications of basic scans and high-
speed scans. However, the View communication for refreshing the FF faceplates is not included.
• SOE
Displays the I/O communication load for SOE communication per second.
• DC
Displays the I/O communication load for device data communication per second.
• BS
Displays the I/O communication load for the communications excluded from CTL, SOE and DC.
The load of the View communication for refreshing the FF faceplates is included in BS.

By assigning MRGN or other data items ranging from 0 to PI to a trend pen and using the high limit
value of the I/O communication performance index as the high limit of the trend scale, you can view
the idle capacity of I/O communication.

This system function block can work on FCS simulator too. However, the displays of are different
from the physical FCS. The communication loads will be displayed with zeros.
5.4.4 SEBOL Related Information Block (FCS_SBL) Page 1 of 3
5.4.4 SEBOL Related Information Block (FCS_SBL)

The SEBOL related information block is used for displaying the status of the FCS for running SEBOL
programs.
Data Items
Table 5.4.4-1 Data Items of SEBOL Related Information Block (FCS_SBL)

O/S
(AUT)
Number of periodic type
PFEL SEBOL lines - U32 N N 0 N N
Instantaneous
PXEL U32 N N 0 N Y
SEBOL lines - Maximum
PSDB U32 N N 0 N N
SEBOL blocks
PFMB SEBOL blocks - U32 N N 0 ms N N
Instantaneous
PXMB U32 N N 0 ms N Y
SEBOL blocks - Maximum
Number of accesses to
other stations from
PFSA U32 N N 0 N N
periodic type SEBOL -
Instantaneous
other stations from
PXSA U32 N N 0 N Y
periodic type SEBOL -
Maximum
Number of execution
lines in the periodic type
PMLC U32 N N 0 N N
SEBOL block that runs
most lines
Tag name of the periodic
16
PMLB type SEBOL block that CHR N N N N
characters
runs most lines
Number of timeshare
TFEL type SEBOL lines - U32 N N 0 N N
Instantaneous
Number of timeshare
TXEL type SEBOL lines - U32 N N 0 N Y
Maximum
Number of defined
TSDB U32 N N 0 N N
timeshare type SEBOL
blocks
Number of running
TFMB timeshare type SEBOL U32 N N 0 N N
blocks - Instantaneous
Number of running
TXMB timeshare type SEBOL U32 N N 0 N Y
blocks - Maximum
other stations from
TFSA U32 N N 0 N N
timeshare type SEBOL -
Instantaneous
other stations from
TXSA U32 N N 0 N Y
timeshare type SEBOL -
Maximum
*1: Data type
U32: 32-bit unsigned integer
I16: 16-bit signed integer
CHR: Characters
*2: Allow user to enter a value to the item
Y: Yes
N: No
*3: Initialize the block when changing mode
Y: Yes
N: No

The symbols and the meanings of data items of SEBOL related information block are as follows:
• PFEL
Displays the instantaneous number of execution lines in all the periodic type SEBOL blocks per
second.
• PXEL
Displays the maximum number of execution lines in all periodic type SEBOL blocks per second.
• PSDB
Displays the number of defined periodic type SEBOL blocks.
• PFMB
Displays the instantaneous number of running periodic type SEBOL blocks per second (When
block’s BSTS is RUN or PAUSE, the block is deemed as a running block).
• PXMB
Displays the maximum number of running periodic type SEBOL blocks per second.
• PFSA
Displays the instantaneous number of accesses to other stations from periodic type SEBOL blocks
per second.
• PXSA
Displays the maximum number of accesses to other stations from periodic type SEBOL blocks per
second.
• PMLC
Displays the maximum number of execution lines in the periodic type SEBOL blocks that runs
most lines per second.

• PMLB
Displays the tag name of the periodic type SEBOL blocks that runs most lines per second.
• TFEL
Displays the instantaneous number of execution lines in all the timeshare type SEBOL blocks per
second.
• TXEL
Displays the maximum number of execution lines in all the timeshare type SEBOL blocks per
second.
• TSDB
Displays the number of defined timeshare type SEBOL blocks.
• TFMB
Displays the maximum number of running timeshare type SEBOL blocks per second (A block in
BSTS, RUN or PAUSE status is deemed as a running block).
• TXMB
Displays the maximum number of running timeshare type SEBOL blocks per second.
• TFSA
Displays the instantaneous number of accesses to other stations from SEBOL blocks of timeshare
type per second.
• TXSA
Displays the maximum number of execution lines in the timeshare type SEBOL blocks that runs
most lines per second.

The SEBOL related information block does not provide the range information for its parameters.
When assigning the data to a trend pen, the range needs to be properly defined according to the
applications.

When this system function block is used on FCS simulator, it does not provide correct information;
therefore, it should not be used on FCS simulator.
Revision Information Page 1 of 1
Revision Information
Title : Function Blocks Reference Vol.3
Manual No. : IM 33J15A32-01EN
Feb. 2021/7th Edition/R6.08 or later

1.1.3 Added descriptions to “ Loop-Branch and Loop-Join.”
May. 2020/6th Edition/R6.07.10

2.7.1 Updated descriptions in “ Unit Alarm Status.”
Aug. 2019/5th Edition/R6.07

Preface Updated descriptions in “ Trademark Acknowledgements.”
Aug. 2018/4th Edition/R6.06

Cover Deleted logo.
Apr. 2017/3rd Edition/R6.04

3.8.2 Updated description in “ Detailed drive vpmon Statement.”
3.8.3 Updated description in “ Detailed drive vpmoff Statement.”
5.3 Updated description in “ Definitions of Performance Indexes of FFCS-C and FFCS-V.”
Jun. 2016/2nd Edition/R6.03

1.6.1 Changed the title " QUEUE Definition" to " Definition of User-Defined Data Item QUEUE".
1.6.12 Added " Definition Items for User-Defined Data Items".
2.3.3 Added descriptions to " Entry Method".
Added descriptions to " Check".
5.2 Corrected an error in " Data Reference Syntax of System Function Blocks".
Mar. 2015/1st Edition/R6.01

Newly published.

Function Blocks Reference Vol.3

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

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

1. Sequential Function Chart

Figure 1-1 Example of SFC

Architecture of SFC Block

Figure 1-2 Image of SFC Block Architecture

Describing Step Actions

Figure 1-3 SFC Block Control Algorithm

SEE For more information about SEBOL, refer to:

Block Modes and Status

1.1 SFC Elements

Description of SFC Elements

Element Name Symbol

Initial Double-Width Step

Selective Sequence Split

Selective Sequence Join

Figure 1.1.1-1 Example of Step

Figure 1.1.1-2 Example of Initial Step

Figure 1.1.1-3 Example of Double-Height Step

Initial Double-Height Step

Figure 1.1.1-4 Example of Initial Double-Height Step

Figure 1.1.1-5 Example of Interrupt Step

Each step is described as an action to execute a processing.

SEE For more information about action description, refer to:

Step Sequence Transition

Figure 1.1.2-1 Example of Step Sequence Transition

SEE For more information about transition conditions, refer to:

Selective Sequence Transition

Figure 1.1.2-2 Example of Selective Sequence Transition

Selective Sequence Split and Selective Sequence Join

Figure 1.1.3-1 Selective Sequence Split and Selective Sequence Join

SEE For more information about Selective Sequence, refer to:

Loop-Branch and Loop-Join

Figure 1.1.3-2 Example of Loop-Branch and Loop-Join

Jump Down, Jump Up and Jump To

Figure 1.1.3-3 Examples of Jumping

Figure 1.1.3-4 Example of Link

1.1.4 Step & Selective Sequences

Figure 1.1.4-1 Example of Step Sequence

Figure 1.1.4-2 Example of Selective Sequence

Figure 1.1.4-3 Example of Interrupt Program Developed from Interrupt Step

1.2 Action Description Using SEBOL

1.2.1 Step Common Items

Figure 1.2.1-1 Global Variables

Figure 1.2.1-2 Local Variables

Function Block Declaration

Figure 1.2.1-3 Global Declaration

Figure 1.2.1-4 Local Declaration

SEE For more information about "#define", refer to:

1.2.2 Initial Step

Figure 1.2.2-1 Order of Description

Step Parameter in Action-signal column(1) Condition testing result(1)