Reference

Function Block Details

Vol.2
IM 33M01A30-40E

IM 33M01A30-40E
2nd Edition
 TocD-1

CENTUM VP
Reference
Function Block Details Vol.2
IM 33M01A30-40E 2nd Edition

CONTENTS
PART-D Function Block Details
D2. Arithmetic Calculation, Logic Operation............................................................D2-1
D2.1 Common Functions of Calculation Blocks.................................................. D2-2
D2.2 Data Handled by Calculation Blocks............................................................ D2-5
D2.3 Types of Calculation Blocks.......................................................................... D2-7
D2.3.1 Input Processing, Output Processing, and Alarm Processing
Possible for Each Calculation Block.............................................. D2-10
D2.3.2 Valid Block Modes for Each Calculation Block.............................. D2-18
D2.4 Addition Block (ADD)................................................................................... D2-21
D2.5 Multiplication Block (MUL)........................................................................... D2-24
D2.6 Division Block (DIV)...................................................................................... D2-27
D2.7 Averaging Block (AVE)................................................................................. D2-30
D2.8 Square Root Block (SQRT).......................................................................... D2-36
D2.9 Exponential Block (EXP).............................................................................. D2-39
D2.10 First-Order Lag Block (LAG)........................................................................ D2-42
D2.11 Integration Block (INTEG)............................................................................ D2-46
D2.12 Derivative Block (LD).................................................................................... D2-51
D2.13 Ramp Block (RAMP)..................................................................................... D2-55
D2.14 Lead/Lag Block (LDLAG)............................................................................. D2-59
D2.15 Dead-Time Block (DLAY).............................................................................. D2-63
D2.16 Dead-Time Compensation Block (DLAY-C)................................................ D2-68
D2.17 Moving-Average Block (AVE-M).................................................................. D2-72
D2.18 Cumulative-Average Block (AVE-C)............................................................ D2-76
D2.19 Variable Line-Segment Function Block (FUNC-VAR)............................... D2-81
D2.20 Temperature and Pressure Correction Block (TPCFL)............................. D2-85
D2.21 ASTM Correction Block : Old JIS (ASTM1)................................................ D2-91
D2.22 ASTM Correction Block : New JIS (ASTM2)............................................... D2-95
D2.23 Logical AND Block (AND), Logical OR Block (OR).................................... D2-99
D2.24 Logical NOT Block (NOT)........................................................................... D2-102
D2.25 Flip-Flop Blocks (SRS1-S, SRS1-R, SRS2-S, SRS2-R)........................... D2-104
D2.26 Wipeout Block (WOUT) ............................................................................. D2-108
D2.27 ON-Delay Timer Block (OND)......................................................................D2-111
D2.28 OFF-Delay Timer Block (OFFD) ................................................................ D2-115

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 TocD-2
D2.29 One-Shot Blocks Rise Trigger (TON), Fall Trigger (TOFF)..................... D2-119
D2.30 Relational Operation Blocks (GT, GE, EQ)............................................... D2-122
D2.31 Bitwise AND Block (BAND), Bitwise OR Block (BOR) ........................... D2-125
D2.32 Bitwise NOT Block (BNOT)........................................................................ D2-128
D2.33 General-Purpose Calculation Blocks (CALCU, CALCU-C).................... D2-131
D2.34 Three-Pole Three-Position Selector Switch Block (SW-33)................... D2-151
D2.35 One-Pole Nine-Position Selector Switch Block (SW-91)........................ D2-154
D2.36 Selector Switch Block for 16 Data (DSW-16)........................................... D2-157
D2.37 Selector Switch Block for 16 String Data (DSW-16C)............................. D2-160
D2.38 Data Set Block (DSET)................................................................................ D2-163
D2.39 Data Set Block with Input Indicator (DSET-PVI)...................................... D2-166
D2.40 One-Batch Data Set Block (BDSET-1L).................................................... D2-170
D2.41 One-Batch String Data Set Block (BDSET-1C)........................................ D2-174
D2.42 Two-Batch Data Set Block (BDSET-2L).................................................... D2-177
D2.43 Two-Batch String Data Set Block (BDSET-2C)........................................ D2-181
D2.44 Batch Data Acquisition Block (BDA-L)..................................................... D2-184
D2.45 Batch String Data Acquisition Block (BDA-C)......................................... D2-187
D2.46 Inter-Station Data Link Block (ADL).......................................................... D2-190
D2.47 General-Purpose Arithmetic Expressions............................................... D2-195
D2.47.1 Basic Items of the General-Purpose Arithmetic Expressions...... D2-196
D2.47.2 Constants in General-Purpose Arithmetic Expressions.............. D2-200
D2.47.3 Variables...................................................................................... D2-202
D2.47.4 Operators..................................................................................... D2-209
D2.47.5 Arithmetic Expressions................................................................ D2-212
D2.47.6 Control Statements...................................................................... D2-216
D2.47.7 Error Handling.............................................................................. D2-221
D2.47.8 Built-In Functions......................................................................... D2-225
D2.47.9 Reserved Words for Numerical and Logical Arithmetic
Expressions................................................................................. D2-231
D3. Sequence Control....................................................................................D3-1
D3.1 Types of Sequence Control Blocks.............................................................. D3-3
D3.1.1 Alarm Processing of Sequence Control Blocks............................... D3-6
D3.1.2 Block Mode of Sequence Control Blocks........................................ D3-7
D3.2 Sequence Table Block (ST16, ST16E)........................................................... D3-8
D3.2.1 Sequence Table Configuration.......................................................D3-11
D3.2.2 Creating a Sequence Table........................................................... D3-16
D3.2.3 Sequence Table Processing Flow................................................. D3-19
D3.2.4 Input Processing of Sequence Table............................................. D3-28
D3.2.5 Condition Rule Processing of Sequence Table............................. D3-30
D3.2.6 Action Rule Processing of Sequence Table................................... D3-31
D3.2.7 Output Processing of Sequence Table.......................................... D3-32
D3.2.8 Number of Condition Signals and Action Signals.......................... D3-33

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 TocD-3
D3.2.9 Rule Extension............................................................................... D3-34
D3.2.10 Condition Signal Description: Referencing Other Function Blocks
and I/O Data .................................................................................. D3-36
D3.2.11 Control Signal Description: Referencing Sequence Table ........... D3-57
D3.2.12 Syntax for Condition Signal Description:
Logic Chart Reference in Sequence Table.................................... D3-67
D3.2.13 Description of Action Signal: Status Manipulation for Other
Function Blocks and I/O Data........................................................ D3-68
D3.2.14 Action Signal Description:
Status Manipulation for Sequence Table....................................... D3-88
D3.2.15 Action Signal Description:
Status Manipulation for a Logic Chart from a Sequence Table..... D3-97
D3.2.16 Data Items of the Sequence Table Block (ST16)........................... D3-98
D3.3 Logic Chart Block (LC64)............................................................................. D3-99
D3.3.1 Configuration of a Logic Chart..................................................... D3-101
D3.3.2 Creating a Logic Chart Block....................................................... D3-104
D3.3.3 Logic Chart Processing Flow....................................................... D3-106
D3.3.4 Input Processing of Logic Chart................................................... D3-107
D3.3.5 Logic Calculation Processing of Logic Chart............................... D3-108
D3.3.6 Output Processing of Logic Chart.................................................D3-114
D3.3.7 Condition Signal Description:
Referencing Other Function Blocks and I/O Data........................D3-115
D3.3.8 Syntax for Condition Signal Description:
Referencing Logic Chart.............................................................. D3-136
D3.3.9 Syntax for Condition Signal Description:
Referencing Sequence Table in a Logic Chart............................ D3-137
D3.3.10 Action Signal Description:
Status Manipulation for Other Function Blocks and I/O Data...... D3-140
D3.3.11 Syntax for Action Signal Description:
Status Manipulation of Logic Chart . ........................................... D3-158
D3.3.12 Syntax for Action Signal Description:
Status Manipulation of Sequence Table from Logic Chart.......... D3-159
D3.3.13 Behavior of Logic Chart Internal Timer........................................ D3-162
D3.3.14 Data Items of Logic Chart Block - LC64...................................... D3-163
D3.4 Switch Instrument Block and Enhanced Switch Instrument Block...... D3-164
D3.5 Timer Block (TM)......................................................................................... D3-190
D3.6 Software Counter Block (CTS).................................................................. D3-201
D3.7 Pulse Train Input Counter Block (CTP).................................................... D3-205
D3.8 Code Input Block (CI).................................................................................. D3-213
D3.9 Code Output Block (CO)............................................................................. D3-219
D3.10 Relational Expression Block (RL)............................................................. D3-224
D3.11 Resource Scheduler Block (RS)................................................................ D3-229
D3.12 Valve Monitoring Block (VLVM)................................................................. D3-239
D4. Faceplate Blocks.....................................................................................D4-1
D4.1 Types of Faceplate Blocks............................................................................. D4-2
D4.2 Push Button Operation of Faceplate Blocks............................................... D4-4

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 TocD-4
D4.3 Block Mode and Status of Faceplate Blocks............................................... D4-6
D4.3.1 Block Mode of Faceplate Blocks...................................................... D4-7
D4.3.2 Block Status of Faceplate Blocks.................................................. D4-10
D4.3.3 Alarm Status of Faceplate Blocks.................................................. D4-12
D4.3.4 Data Status of Faceplate Blocks.................................................... D4-14
D4.4 Dual-Pointer Indicating Station Block (INDST2)........................................ D4-15
D4.5 Dual-Pointer Manual Station Block (INDST2S).......................................... D4-19
D4.6 Triple-Pointer Manual Station Block (INDST3)........................................... D4-23
D4.7 Batch Status Indicator Block (BSI)............................................................. D4-27
D4.8 Extended 5-Push-Button Switch Block (PBS5C)......................................................D4-34
D4.9 Extended 10-Push-Button Switch Block (PBS10C).................................. D4-41
D4.10 Extended Hybrid Manual Station Block (HAS3C)...................................... D4-49
D5. Sequential Function Chart.....................................................................D5-1
D5.1 SFC Elements.................................................................................................. D5-5
D5.1.1 Step.................................................................................................. D5-6
D5.1.2 Transition....................................................................................... D5-10
D5.1.3 Links............................................................................................... D5-12
D5.1.4 Step & Selective Sequences......................................................... D5-14
D5.2 Action Description Using SEBOL............................................................... D5-16
D5.2.1 Step Common Items...................................................................... D5-17
D5.2.2 Initial Step...................................................................................... D5-21
D5.2.3 SEBOL Steps................................................................................. D5-23
D5.2.4 SEBOL One-Shot Steps................................................................ D5-24
D5.3 Action Description Using Sequence Table................................................ D5-26
D5.3.1 Step Common Item Description Using the Sequence Table......... D5-27
D5.3.2 Sequence Table Steps................................................................... D5-30
D5.3.3 Sequence Table One-Shot Steps.................................................. D5-31
D5.4 Action Description Using Logic Chart........................................................ D5-32
D5.4.1 Step Common Item Description Using Logic Chart....................... D5-33
D5.4.2 Logic Chart Steps.......................................................................... D5-35
D5.4.3 Logic Chart One-Shot Steps.......................................................... D5-36
D5.5 Transition Conditions................................................................................... D5-37
D5.6 SFC Block Action.......................................................................................... D5-38
D5.6.1 Queue Signal Processing.............................................................. D5-42
D5.6.2 Status Change Processing............................................................ D5-48
D5.6.3 Interrupt Signal Processing............................................................ D5-53
D5.6.4 Error Processing............................................................................ D5-56
D5.6.5 Terminating SFC Block Execution................................................. D5-57
D5.6.6 Pausing SFC Block Execution....................................................... D5-58
D5.6.7 Referencing Current Step.............................................................. D5-62
D5.6.8 Changing Current Step ................................................................ D5-63
D5.6.9 SFC Block Alarm Processing......................................................... D5-64

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 TocD-5
D5.6.10 SFC Online Maintenance.............................................................. D5-66
D5.6.11 SFC Block Execution..................................................................... D5-67
D5.6.12 Data Items - SFC........................................................................... D5-68
D5.6.13 SFC Block Mode & Status............................................................. D5-76
D5.7 Manipulating Unit Instrument from SFC Block.......................................... D5-79

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

Blank Page
 <D2. Arithmetic Calculation, Logic Operation> D2-1

D2. Arithmetic Calculation, Logic Operation

The arithmetic calculation and logic operation function blocks perform general-purpose
calculation processing, such as arithmetic calculation, analog calculation and logic
operation.
The arithmetic calculation and logic operation blocks include numeric calculation blocks,
analog calculation blocks, general-purpose calculation blocks, calculation auxiliary
blocks and logic operation blocks.
This chapter explains each model of calculation and logic operation function blocks.

n Arithmetic Calculation and Logic Operation

The general-purpose calculation processing such as arithmetic calculation, analog calculation
and logic operation (*1) are performed to input signals to improve the regulatory control and
sequence control. The function block that executes arithmetic calculation is referred as the
calculation block.
The following figure shows the calculation blocks in basic control architecture.
*1: Logic Operation Block can be used in FCSs except PFCS.

FCS

Basic control
Software I/O

Regulatory control blocks Internal switch

Calculation blocks Annunciator message

Sequence control blocks

Sequence control message

Faceplate blocks

SFC blocks

Unit instrument blocks

Options

Valve pattern monitoring (*1)

Off-site blocks (*1)

FCS I/O Interfaces

Process I/O Communication I/O Fieldbus I/O

D020001E.ai

*1: This option can be used in FCSs except PFCS.

Figure Calculation Blocks in Basic Control Architecture

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.1 Common Functions of Calculation Blocks> D2-2

D2.1 Common Functions of Calculation Blocks

Calculation blocks provide calculation functions for analog signals and contact signals.
Calculation blocks convert the calculation results into the signals that can be used by
other function blocks.

n Calculation Blocks
Calculation blocks receive analog signals (analog values) or contact signals (digital values) as
input values, and perform calculation according to the set parameters. The result of calculation is
outputted as the calculated output value (CPV).
Following diagram shows the architecture of calculation blocks.

P1 Pn

Input Output
IN RV CPV OUT
processing processing

Q01 RV1 CPV1 J01

Calculation
processing

Qn RVn CPVn Jn

(CPV, ∆CPV)

SUB

D020101E.ai

IN : Input terminal (main input)

Qn : Input terminal (subsidiary input)
RV : Calculated input value
RVn : Calculated input value
Pn : Set parameter
OUT : Output terminal (main output)
Jn : Output terminal (subsidiary output)
CPV : Calculated output value
CPVn : Calculated output value
SUB : Auxiliary output

Figure Architecture of Calculation Blocks

All calculation blocks are provided with the following three processing functions.
• Input processing:
Receive the signal from the input terminal and convert the signal into the calculation input
value (RV).
• Calculation processing:
Read the calculation input value (RV) and perform calculation processing then output the
result as calculated output value (CPV).
• Output processing:
Read the calculated output value (CPV) and output the calculation result as an output signal
to the connected destination of the output terminal.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.1 Common Functions of Calculation Blocks> D2-3
Furthermore, to perform calculation with data of other function blocks via data setting or data
reference functions may bypass the input processing and output processing.

SEE
ALSO • For details on input processing common to calculation blocks, see the following:
C3, “Input Processing”
• For details on output processing common to calculation blocks, see the following:
C4, “Output Processing”

n Logic Operation Blocks

Logic operation blocks (*1) receive analog signals (analog values) or contact signals (digital
values) as input values, and perform calculation according to the set parameters. The result of
calculation is outputted as the calculated output value (CPV).
*1: Logic Operation Block can be used in FCSs except PFCS.

The following diagram shows the architecture of the Logic Operation Block.

IN RV CPV OUT

Q01 RV1 CPV1 J01

Input Calculation Output
processing processing processing

Qn RVn CPVn Jn

Logic operation blocks (*1)

D020102E.ai

IN : Input terminal (main input)

Qn : Input terminal (subsidiary input)
RV : Calculated input value
RVn : Calculated input value
OUT : Output terminal (main output)
Jn : Output terminal (subsidiary output)
CPV : Calculated output value
CPVn : Calculated output value

Figure Architecture of Logic Operation Blocks

All calculation blocks are provided with the following three processing functions.
• Input processing:
Receive the signal from the input terminal and convert the signal into the calculation input
value (RV).
• Calculation processing:
Read the calculation input value (RV) and perform calculation processing then output the
result as calculated output value (CPV).
• Output processing:
Read the calculated output value (CPV) and output the calculation result as an output signal
to the connected destination of the output terminal.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.1 Common Functions of Calculation Blocks> D2-4
Furthermore, to perform calculation with data of other function blocks via data setting or data
reference functions may bypass the input processing and output processing.

SEE
ALSO • For details on input processing common to calculation blocks, see the following:
C3, “Input Processing”
• For details on output processing common to calculation blocks, see the following:
C4, “Output Processing”

n Calculation Output Operation

The calculation output operation is a function that converts the operation results of a calculation
block into actual calculated output values (CPV). There are two types of calculation output
operations: velocity type and positional type.

l Positional type
Changes the calculated output value (CPVn) for the present calculation result to the actual
calculated output value (CPVn).

l Velocity type
Adds the difference (CPVn) between the calculated output value for the present calculation result
(CPVn) and that for the previous calculation result (CPVn-1) to the value read back (CPVrb) from
the output destination, and determines the actual calculated output value (CPVn).
The arithmetic calculation block and analog calculation block are the only calculation blocks that
can use the velocity type.

l Setting the Calculation Output Operation

In the case of an arithmetic calculation block or an analog calculation block, the calculation output
operation is set using the Function Block Detail Builder. Calculation blocks that are neither an
arithmetic calculation block nor an analog calculation block only have the “Positional Output
Action” calculation output operation, so no setting is necessary.
• Control Calculation Output Type:
Select from either “Velocity Output Action” or “Positional Output Action”
The default is “Positional Output Action.”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.2 Data Handled by Calculation Blocks> D2-5

D2.2 Data Handled by Calculation Blocks

The calculation blocks can handle both the external data related to outside and the
internal data related only to inside calculation processing.

n I/O Data Handled by Calculation Blocks

The I/O data handled by calculation blocks consists of data values and data statuses.

l Data Value
The calculation blocks can handle the following types of data: floating-point, double-precision
floating-point, integer and character string.
When exchange data with other function blocks, if the data are in different type, the calculation
block executes the following processing.
• When refer data from a function block
The calculation block converts the data into the type suitable itself.
• When set data to a function block
The calculation block converts the data suitable to the objective function block.

Because of the above processing, the engineer need not worry about the data type difference
when generate and connect calculation blocks in the Function Block Detail Builder.
The I/O data types and set parameters applied to each type of calculation block are shown below.
Table I/O data types and set parameters
Block type Input data Output data Set parameter
Arithmetic calculation Double-precision floating-point Double-precision floating-point Not specified
Single-precision floating-point,
Analog calculation Single-precision floating-point Single-precision floating-point
integer
Logic operation (*1) integer (logical value) integer (logical value) Not specified
Double-precision floating-point,
Relational operation integer (logical value) Not specified
character string
Bitwise logic operation integer integer Not specified
General-purpose Double-precision floating-point, Double-precision floating-point, Double-precision floating-point,
calculation character string character string character string
Double-precision floating-point,
Calculation auxiliary Double-precision floating-point Double-precision floating-point
integer
Calculation auxiliary
Character string Character string Character string, integer
(for character strings only)
D020201E.ai

Note: The analog calculation blocks handle data in engineering unit so that the internal data is floating type.
The general-purpose calculation blocks and calculation auxiliary blocks can pre-determine each individual data item type in each
function block.
*1: Logic Operation Block can be used in FCSs except PFCS.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.2 Data Handled by Calculation Blocks> D2-6
l Data Status
The calculated output value (CPV) data status varies depending on whether the builder-specified
item “Output Value Tracking,” is enabled or disabled.
• When output value tracking is “No”
The calculated output value (CPV) is the result of calculation. It does not track to the data of
the output connected destination. Therefore, data statuses for the calculated output value
(CPV) are BAD (invalid), QST (questionable data value) and CAL (calibration).
• When output value tracking is “Yes”
The calculated output value (CPV) is the result of calculation. It tracks to the output
connected destination’s data under the certain status. Therefore, the data status, those
often used for other function blocks but seldom for calculation blocks such as CND
(conditional) or NFP (non process origin), may occur to the calculated output value (CPV).

The status of output value tracking can be indicated from the data status of the calculated output
value (CPV).
When CPV data status is BAD, QST, CAL, NEFV, (IOP+, IOP-, OOP, NRDY, PEAL, LPFL), the
CPV Output value tracking is disabled.
When CPV data status is BAD, QST, CAL, NEFV, CND, NFP, (IOP+, IOP-, OOP, NRDY, PEAL,
LPFL), the CPV Output value tracking is enabled.
Note: The data status in parentheses is only for CPV of the addition, multiplication, division, analog calculation or general-purpose
calculation blocks.

When a process I/O-related data status (IOP+, IOP-, OOP, NRDY) occurs to the calculated
input value (RV), the analog calculation blocks pass the data status to the calculated output
value (CPV), regardless of whether output tracking is enabled or disabled. Thus, the data status
occurred on the input side, such as IOP+ (input open high), is passed to the function block
connected to it.
The calculation block will set the status of calculated data as a bad data (BAD) when an error
occurs in the course of calculation.
Calculation error may be generated in the following cases.
•  When the calculation result overflows.
•  When the divisor of the calculation is zero, the calculation is zero divided.
•  When calculate the square root of a negative number in the calculation.

SEE
ALSO For the details of data status, see the following:
C6.4, “Data Status”

n Calculation Precision
In a calculation block, all numeric values are calculated as double-precision floating-point
numbers. Numeric value data other than double-precision floating-point data are converted
to double-precision floating-point data inside the calculation block prior to the execution of
calculation processing. Therefore, calculation precision up to the double-precision floating point
is ensured.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.3 Types of Calculation Blocks> D2-7

D2.3 Types of Calculation Blocks

According to the data type and calculation processing capability, the calculation function
blocks are classified into arithmetic calculation blocks, analog calculation blocks,
general-purpose calculation blocks and calculation auxiliary blocks.

n Arithmetic Calculation Blocks

Table Arithmetic Calculation Blocks
Input Output
Block type Code Name
terminals terminals
ADD Addition Block

Arithmetic calculation MUL Multiplication Block 2 2

blocks DIV Division Block
AVE Averaging Block 8 2
D020301E.ai

Note: The SUB terminal is counted as one of the output terminals.

n Analog Calculation Blocks

Table Analog Calculation Blocks
Input Output
Block type Code Name
terminals terminals
SQRT Square Root Block
EXP Exponential Block
LAG First-Order Lag Block
INTEG Integration Block
LD Derivative Block
RAMP Ramp Block
LDLAG Lead/Lag Block 1 2

Analog calculation blocks DLAY Dead-Time Block

DLAY-C Dead-Time Compensation Block
AVE-M Moving-Average Block
AVE-C Cumulative-Average Block
FUNC-VAR Variable Line-Segment Function Block
TPCFL Temperature and Pressure Correction Block 3 2
ASTM1 ASTM Correction Block: Old JIS
2 2
ASTM2 ASTM Correction Block: New JIS
D020302E.ai

Note: The SUB terminal is counted as one of the output terminals.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.3 Types of Calculation Blocks> D2-8

n Logic Operation Blocks

Table Logic Operation Blocks
Input Output
Block type Code Name
terminals terminals
AND Logical AND Block
2 1
OR Logical OR Block
NOT Logical NOT Block 1 1
SRS1-S Set-Dominant Flip-Flop Block with 1 Output
2 1
SRS1-R Reset-Dominant Flip-Flop Block with 1 Output
SRS2-S Set-Dominant Flip-Flop Block with 2 Outputs
2 2
SRS2-R Reset-Dominant Flip-Flop Block with 2 Outputs
WOUT Wipeout Block 2 1

Logic Operation OND ON-Delay Timer Block

blocks (*1) OFFD OFF-Delay Timer Block
1 1
TON One-Shot Block (Rising-Edge Trigger)
TOFF One-Shot Block (Falling-Edge Trigger)
GT Comparator Block (Greater Than)
GE Comparator Block (Greater Than or Equal)
EQ Equal Operator Block 2 1
BAND Bitwise AND Block
BOR Bitwise OR Block
BNOT Bitwise NOT Block 1 1
D020303E.ai

Note: The SUB terminal is counted as one of the output terminals.

*1 : Logic Operation Block can be used in FCSs except PFCS.

n General-Purpose Calculation Blocks

Table General-Purpose Calculation Blocks
Input Output
Block type Code Name
terminals terminals
CALCU General-Purpose Calculation Block
General-purpose
General-Purpose Calculation Block with 32 17
calculation blocks CALCU-C
String I/O
D020304E.ai

Note: The SUB terminal is counted as one of the output terminals.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.3 Types of Calculation Blocks> D2-9

n Calculation Auxiliary Blocks

Table Calculation Auxiliary Blocks
Input Output
Block type Code Name
terminals terminals
Three-Pole Three-Position Selector
SW-33 9 (3) (*1) 3 (9) (*1)
Switch Block
One-Pole Nine-Position Selector
SW-91 9 (1) (*2) 1 (9) (*2)
Switch Block
DSW-16 Selector Switch Block for 16 Data
DSW-16C Selector Switch Block for 16 String Data 0 1
DSET Data Set Block
Calculation auxiliary DSET-PVI Data Set Block with Input Indicator 1 2
blocks
BDSET-1L One-Batch Data Set Block
0 16
BDSET-1C One-Batch String Data Set Block
BDSET-2L Two-Batch Data Set Block
0 16
BDSET-2C Two-Batch String Data Set Block
BDA-L Batch Data Acquisition Block
16 0
BDA-C Batch String Data Acquisition Block
ADL Inter-Station Data Link Block 0 0
D020306E.ai

Note: The SUB terminal is counted as one of the output terminals.

*1: 3 input terminals and 9 output terminals can be used.
*2: One input terminal and 9 output terminals can be used.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.3 Types of Calculation Blocks> D2-10

D2.3.1 Input Processing, Output Processing, and Alarm

Processing Possible for Each Calculation Block
A list of the types of input processing, output processing, and alarm processing that can
be performed for each calculation block is shown below.

n Input Processing Possible in Each Calculation Block

Table Input Processing Possible in Each Calculation Block (1/3)
Input signal
Model Digital filter Totalizer PV overshoot CAL
conversion
ADD BARPPqSb x x
MUL BARPPqSb x x
DIV BARPPqSb x x
AVE B x
SQRT BARPPqSb (*1) (*1) x
EXP BARPPqSb (*1) (*1) x
LAG BARPPqSb (*1) (*1) x
INTEG BARPPqSb (*1) (*1) x
LD BARPPqSb (*1) (*1) x
RAMP BARPPqSb x x
LDLAG BARPPqSb (*1) (*1) x
DLAY BARPPqSb (*1) (*1) x
DLAY-C BARPPqSb (*1) (*1) x
AVE-M BARPPqSb x x
AVE-C BARPPqSb x x
FUNC-VAR BARPPqSb (*1) (*1) x
TPCFL BARPPqSb x x
ASTM1 BARPPqSb x x
ASTM2 BARPPqSb x x
D020307E.ai

B: No conversion (function block)

A: No conversion (analog input)
R: Square root conversion (analog input)
P: Control priority type pulse-train input conversion
Pq: Exact totalization pulse-train input conversion
Sb: Subsystem input
x: Exists
Blank: Not exist
*1: The input processing other than the calibration function will not function when data setting is performed to the PV by cascade
connection.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.3 Types of Calculation Blocks> D2-11
Table Input Processing Possible in Each Calculation Block (2/3) – Logic Operation Block (*1)
Input signal
Model Digital filter Totalizer PV overshoot CAL
conversion
AND x
OR x
NOT x
SRS1-S x
SRS1-R x
SRS2-S x
SRS2-R x
WOUT x
OND x
OFFD x
TON x
TOFF x
GT x
GE x
EQ x
BAND x
BOR x
BNOT x
D020308E.ai

x: Exists
Blank: Not exist
*1: Logic Operation Block can be used in FCSs except PFCS.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.3 Types of Calculation Blocks> D2-12
Table Input Processing Possible in Each Calculation Block (3/3)
Input signal
Model Digital filter Totalizer PV overshoot CAL
conversion
CALCU BARPPqSbL x x x x
CALCU-C BARPPqSbL x x x x
SW-33 x
SW-91 x
DSW-16 x
DSW-16C x
DSET x
DSET-PVI BARPSbL x x x x
BDSET-1L
BDSET-1C
BDSET-2L
BDSET-2C
BDA-L
BDA-C
D020309E.ai

B: No conversion (function block)

A: No conversion (analog input)
R: Square root conversion (analog input)
P: Control priority type pulse-train input conversion
Pq: Exact totalization type pulse-train input conversion
Sb: Subsystem input
L: PV limit
x: Exists
Blank: Not exist

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.3 Types of Calculation Blocks> D2-13

n Output Processing Possible in Each Calculation Block

Table Output Processing Possible in Each Calculation Block (1/2)
Output Velocity Clamped Output Range Auxiliary Output signal
Type PMV
limit limit output track track output conversion
ADD (*2) CCd BASb
MUL (*2) CCd BASb
DIV (*2) CCd BASb
AVE (*2) CCd BASb
AQRT (*1) (*2) CCd BASb
EXP (*1) (*2) CCd BASb
LAG (*1) (*2) CCd BASb
INTEG (*1) (*2) CCd BASb
LD (*1) (*2) CCd BASb
RAMP (*2) CCd BASb
LDLAG (*1) (*2) CCd BASb
DLAY (*1) (*2) CCd BASb
DLAY-C (*1) (*2) CCd BASb
AVE-M (*2) CCd BASb
AVE-C (*2) CCd BASb
FUNC-VAR (*1) (*2) CCd BASb
TPCFL (*2) CCd BASb
ASTM1 (*2) CCd BASb
ASTM2 (*2) CCd BASb
Logic
Operation
Blocks (*3)
D020310E.ai

C: CPV
Cd: ∆CPV
B: Unconverted output (function block)
A: Analog output
Sb: Subsystem output
*1: Only tracking of the CLP ± status of the output destination is performed.
*2: Selectable by builder setting.
*3: Logic Operation Blocks contain the following models. The Logic Operation Block can be used in FCSs except PFCS. If the
connection method of an output terminal is “status manipulation,” the operation specification defined for the output terminal is
executed.
AND, OR, NOT, SRS1-S, SRS1-R, SRS2-S, SRS2-R, WOUT, OND, OFFD, TON, TOFF, GT, GE, EQ, BAND, BOR, BNOT

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.3 Types of Calculation Blocks> D2-14
Table Output Processing Possible in Each Calculation Block (2/2)
Output Velocity Clamped Output Range Auxiliary Output signal
Type PMV
limit limit output track track output conversion
CALCU (*1) CCd BASb
CALCU-C (*1) CCd BASb
SW-33
SW-91
DSW-16 x BASb
DSW-16C
DSET x BASb
DSET-PVI x CCdSSd BASb
DSET-1L
DSET-1C
DSET-2L
DSET-2C
BDA-L
BDA-C
D020311E.ai

C: CPV
Cd: ∆CPV
S: SV
Sd: ∆SV
B: Unconverted output (function block)
A: Analog output
Sb: Subsystem output
*1: Possible if explicitly input using computational expression

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.3 Types of Calculation Blocks> D2-15

n Alarm Processing Possible in Each Calculation Block

Table Alarm Processing Possible in Each Calculation Block (1/3)
Common process alarms
N O I I H L H L D D V V M M C
Code R O O O H L I O V V E E H L N Other alarms
P P P + - L L I O F
- + -

ADD
MUL
DIV
AVE
SQRT
EXP
LAG
INTEG
LD
RAMP
x x x x
LDLAG
DLAY
DLAY-C
AVE-M
AVE-C
FUNC
FUNC-VAR
TPCFL
ASTM1
ASTM2
D020312E.ai

x: Available
Blank: Not available

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.3 Types of Calculation Blocks> D2-16
Table Alarm Processing Possible in Each Calculation Block (2/3) – Logic Operation Block (*1)
Common process alarms
N O I I H L H L D D V V M M C
Code R O O O H L I O V V E E H L N Other alarms
P P P + - L L I O F
- + -

AND
OR
NOT
SRS1-S
SRS1-R
SRS2-S
SRS2-R
WOUT
OND
x x x x
OFFD
TON
TOFF
GT
GE
EQ
BAND
BOR
BNOT
D020313E.ai

x: Available
Blank: Not available
*1: Logic Operation Block can be used in FCSs except PFCS.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.3 Types of Calculation Blocks> D2-17
Table Alarm Processing Possible in Each Calculation Block (3/3)
Common process alarms
N O I I H L H L D D V V M M C
Code R O O O H L I O V V E E H L N Other alarms
P P P + - L L I O F
- + -

CALCU
x x x x CERR
CALCU-C
SW-33
SW-91
DSW-16
DSW-16C x x
DSET
DSET-PVI x x x x x x x x x x
BDSET-1L
BDSET-1C
BDSET-2L
BDSET-2C x x

BDA-L
BDA-C
D020314E.ai

x: Available
Blank: Not available

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.3 Types of Calculation Blocks> D2-18

D2.3.2 Valid Block Modes for Each Calculation Block

A list of valid block modes for each calculation block is shown below.

n Valid Block Modes for Each Calculation Block

Table Valid Basic Block Modes for Calculation Blocks (1/3)
Valid basic block modes
O I T M A C P R R
Type Name / M R A U A R C O
S A K N T S D A U
N S T

ADD Addition Block

MUL Multiplication Block
DIV Division Block
AVE Averaging Block
SQRT Square Root Block
EXP Exponential Block
LAG First-order Lag Block
INTEG Integration Block
LD Derivative Block
RAMP Ramp Block x - - - x - - - -
LDLAG Lead/Lag Block
DLAY Dead-Time Block
DLAY-C Dead-Time Compensation Block
AVE-M Moving-Average Block
AVE-C Cumulative-Average Block
FUNC-VAR Variable Line-Segment Function Block
TPCFL Temperature and Pressure Correction Block
ASTM1 ASTM Correction Block:Old JIS
ASTM2 ASTM Correction Block:New JIS
D020315E.ai

x: Valid
-: Invalid

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.3 Types of Calculation Blocks> D2-19
Table Valid Basic Block Modes for Calculation Blocks (2/3)
Valid basic block modes
O I T M A C P R R
Type Name / M R A U A R C O
S A K N T S D A U
N S T

AND (*1) Logical AND Block

OR (*1) Logical OR Block
NOT (*1) Logical NOT Block
SRS1-S (*1) Set-Dominant Flip-Flop Block with 1 Output
SRS1-R (*1) Reset-Dominant Flip-Flop Block with 1 Output
SRS2-S (*1) Set-Dominant Flip-Flop Block with 2 Outputs
SRS2-R (*1) Reset-Dominant Flip-Flop Block with 2 Outputs
WOUT (*1) Wipeout Block
OND (*1) ON-Delay Timer Block
OFFD (*1) OFF-Delay Timer Block
x - - - x - - - -
TON (*1) One-Shot Block (Rising-Edge Trigger)
TOFF (*1) One-Shot Block (Falling-Edge Trigger)
GT (*1) Comparator Block (Greater Than)
GE (*1) Comparator Block (Greater Than or Equal)
EQ (*1) Equal Operator Block
BAND (*1) Bitwise AND Block
BOR (*1) Bitwise OR Block
BNOT (*1) Bitwise NOT Block
CALCU General-Purpose Calculation Block
CALCU-C General-Purpose Calculation Block with String I/O
D020316E.ai

x: Valid
-: Invalid
*1: Logic Operation Blocks can be used in FCSs except PFCS.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.3 Types of Calculation Blocks> D2-20
Table Valid Basic Block Modes for Calculation Blocks (3/3)
Valid basic block modes
O I T M A C P R R
Type Name / M R A U A R C O
S A K N T S D A U
N S T

SW-33 Three-Pole Three-Position Selector Switch Block

- - - - - - - - -
SW-91 One-Pole Nine-Position Selector Switch Block
DSW-16 Selector Switch Block for 16 Data
DSW-16C Selector Switch Block for 16 String Data
DSET Data Set Block
DSET-PVI Data Set Block with Input Indicator
BDSET-1L One-Batch Data Set Block
x - - - x - - - -
BDSET-1C One-Batch String Data Set Block
BDSET-2L Two-Batch Data Set Block
BDSET-2C Two-Batch String Data Set Block
BDA-L Batch Data Acquisition Block
BDA-C Batch String Data Acquisition Block
D020317E.ai

x: Valid
-: Invalid

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.4 Addition Block (ADD)> D2-21

D2.4 Addition Block (ADD)

The Addition Block (ADD) is used when performing addition processing or subtraction
processing.

n Addition Block (ADD)

▼ Connection
The Addition Block (ADD) is a function block that executes addition or subtraction of input data.
Here is the diagram of the Addition Block (ADD).

Input
IN RV
processing

Gain
(GAIN),
Addition CPV OUT
bias
(BIAS)
RV1 gain
(GN1),
Q01 RV1
RV1 bias
(BS1)

(CPV, ∆CPV) SUB

D020401E.ai

Figure Function Block Diagram of Addition Block (ADD)

The following table shows the connection types and connection destinations of the I/O terminals
of the Addition Block (ADD).
Table Connection Types and Connection Destinations of the I/O Terminals of Addition Block (ADD)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
IN Main input x Δ x x
Q01 Sub input x Δ x x
Calculation
OUT x x x x
output
Auxiliary Δ
SUB x x x
output
D020402E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.4 Addition Block (ADD)> D2-22

n Function of Addition Block (ADD)

The ADD block performs input processing, calculation processing, output processing, and alarm
processing.
The processing timings available for the ADD block are a periodic startup and a one-shot startup.
Selections available for the scan period used to execute a periodic startup include the basic scan
period, the medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the ADD block, see
the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Input Processing of Addition Block (ADD) When a Calculation Input Value

Error is Detected
The ADD block performs special input processing when an abnormal calculation input value is
detected.

SEE
ALSO For the input processing when an abnormal calculation input value is detected, see the following:
“l Input Processing at Calculated Input Value Error Detection in the Arithmetic Calculation” in “n Input
Processing at Calculated Input Value Error Detection” in chapter C3.6.2, “Input Processing of the
Calculation Block in Unsteady State”

l Calculation Processing of Addition Block (ADD)

The ADD block performs addition and subtraction using its calculation algorithm and setup
parameters.

n Calculation Algorithm
The Addition Block (ADD) executes the following calculation processing for addition or
subtraction of the input data.

CPV=GAIN • (RV+ ( (GN1 • RV1) +BS1) ) +BIAS

To perform addition processing of input data, set a positive numeric value for the RV1 gain.
To perform subtraction processing of input data, set a negative numeric value for the RV1 gain.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.4 Addition Block (ADD)> D2-23

n Set Parameters
The set parameters of the Addition Block (ADD) are shown as follows.
• Gain (GAIN):
A numeric value of 7 digits or less including the sign and decimal point.
The default is 1.00
• Bias (BIAS):
An engineering unit data value of 7 digits or less including the sign and decimal point.
The default is 0.00
• RV1 gain (GN1):
A numeric value of 7 digits or less including the sign and decimal point.
The default is 1.00
• RV1 bias (BS1):
An engineering unit data of 7 digits or less including the sign and decimal point.
The default is 0.00

n Data Items – ADD

Table Data Items of Addition Block (ADD)
Data Entry Permitted
Data Name Range Default
Item or Not
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
RV Calculated input value ----- 0
RAW Raw input data Value in the unit at the connection destination -----
RV1 Calculated input value ----- 0
RAW1 Raw input data Value in the unit at the connection destination -----
CPV Calculated output value Δ (*1) CPV engineering unit value SL
GAIN Gain x 7 - digit real number including sign and decimal point 1.00
BIAS Bias x 7 - digit real number including sign and decimal point 0.00
GN1 RV1 gain x 7 - digit real number including sign and decimal point 1.00
BS1 RV1 bias x 7 - digit real number including sign and decimal point 0.00
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
SH CPV scale high limit Value in the same engineering unit as CPV -----
SL CPV scale low limit Value in the same engineering unit as CPV -----
D020403E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For the information about valid block mode for ADD block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.5 Multiplication Block (MUL)> D2-24

D2.5 Multiplication Block (MUL)

The Multiplication Block (MUL) is used when performing multiplication processing.

n Multiplication Block (MUL)

▼ Connection
The Multiplication Block (MUL) is a function block that performs multiplication of input data.
Here is a function block diagram of the Multiplication Block (MUL).

Input
IN RV
processing

Gain
(GAIN),
Multiplication CPV OUT
bias
(BIAS)
RV1 gain
(GN1),
Q01 RV1
RV1 bias
(BS1)

(CPV, ∆CPV) SUB

D020501E.ai

Figure Function Block Diagram of Multiplication Block (MUL)

The following table shows the connection types and connection destinations of the I/O terminals
of the Multiplication Block (MUL).
Table Connection Types and Connection Destinations of the I/O Terminals of Multiplication Block
(MUL)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
IN Main input x Δ x x
Q01 Sub input x Δ x x
Calculation
OUT x x x x
output
Auxiliary
SUB x Δ x x
output
D020502E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.5 Multiplication Block (MUL)> D2-25

n Function of Multiplication Block (MUL)

The MUL block performs input processing, calculation processing, output processing, and alarm
processing.
The processing timings available for the MUL block are a periodic startup and a one-shot startup.
Selections available for the scan period used to execute a periodic startup include the basic scan
period, the medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the MUL block, see
the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Input Processing of Multiplication Block (MUL) When a Calculation Input Value

Error is Detected
The MUL block performs special input processing when an abnormal calculation input value is
detected.

SEE
ALSO For the input processing when an abnormal calculation input value is detected, see the following:
“l Input Processing at Calculated Input Value Error Detection in the Arithmetic Calculation” in “n Input
Processing at Calculated Input Value Error Detection” in chapter C3.6.2, “Input Processing of the
Calculation Block in Unsteady State”

l Calculation Processing of Multiplication Block (MUL)

The MUL block performs multiplication using its calculation algorithm and setup parameters.

n Calculation Algorithm
The Multiplication Block (MUL) executes the following calculation processing to perform
multiplication of input data.

CPV=GAIN • (RV • ( (GN1 • RV1) + BS1) ) +BIAS

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.5 Multiplication Block (MUL)> D2-26

n Set Parameters
The set parameters of the Multiplication Block (MUL) are shown as follows.
• Gain (GAIN):
A numeric value of 7 digits or less including the sign and decimal point.
The default is 1.00
• Bias (BIAS):
An engineering unit data value of 7 digits or less including the sign and decimal point.
The default is 0.00
• RV1 gain (GN1):
A numeric value of 7 digits or less including the sign and decimal point.
The default is 1.00
• RV1 bias (BS1):
An engineering unit data value of 7 digits or less including the sign and decimal point.
The default is 0.00

n Data Items – MUL

Table Data Items of Multiplication Block (MUL)
Data Entry Permitted
Data Name Range Default
Item or Not
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
RV Calculated input value ----- 0
RAW Raw input data Value in the unit at the connection destination -----
RV1 Calculated input value ----- 0
RAW1 Raw input data Value in the unit at the connection destination -----
CPV Calculated output value Δ (*1) CPV engineering unit value SL
GAIN Gain x 7 - digit real number including sign and decimal point 1.00
BIAS Bias x 7 - digit real number including sign and decimal point 0.00
GN1 RV1 gain x 7 - digit real number including sign and decimal point 1.00
BS1 RV1 bias x 7 - digit real number including sign and decimal point 0.00
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
SH CPV scale high limit Value in the same engineering unit as CPV -----
SL CPV scale low limit Value in the same engineering unit as CPV -----
D020503E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for MUL block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.6 Division Block (DIV)> D2-27

D2.6 Division Block (DIV)

The Division Block (DIV) is used when performing division processing.

n Division Block (DIV)

▼ Connection
The Division Block (DIV) is a function block that performs division of input data.
Here is a function block diagram of the Division Block (DIV).

Input
IN RV
processing

Gain
(GAIN),
Division CPV OUT
bias
(BIAS)
RV1 gain
(GN1),
Q01 RV1
RV1 bias
(BS1)

(CPV, ∆CPV) SUB

D020601E.ai

Figure Function Block Diagram of Division Block (DIV)

The following table shows the connection types and connection destinations of the I/O terminals
of the Division Block (DIV).
Table Connection Types and Connection Destinations of the I/O Terminals of Division Block (DIV)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
IN Main input x Δ x x
Q01 Sub input x Δ x x
Calculation
OUT x x x x
output
Auxiliary Δ
SUB x x x
output
D020602E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.6 Division Block (DIV)> D2-28

n Function of Division Block (DIV)

The DIV block performs input processing, calculation processing, output processing, and alarm
processing.
The processing timings available for the DIV block are a periodic startup and a one-shot startup.
Selections available for the scan period used to execute a periodic startup include the basic scan
period, the medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the DIV block, see
the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Input Processing of Division Block (DIV) When a Calculation Input Value Error
is Detected
The DIV block performs special input processing when an abnormal calculation input value is
detected.

SEE
ALSO For the input processing when an abnormal calculation input value is detected, see the following:
“l Input Processing at Calculated Input Value Error Detection in the Arithmetic Calculation” in “n Input
Processing at Calculated Input Value Error Detection” in chapter C3.6.2, “Input Processing of the
Calculation Block in Unsteady State”

l Calculation Processing of Division Block (DIV)

The DIV block performs division using its calculation algorithm and setup parameters.

n Calculation Algorithm
The Division Block (DIV) executes the following calculation processing for performing division of
input data.

CPV=GAIN • (RV/ ( (GN1 • RV1) +BS1) ) +BIAS

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.6 Division Block (DIV)> D2-29

n Set Parameters
The set parameters of the Division Block (DIV) are shown as follows.
• Gain (GAIN):
A numeric value of 7 digits or less including the sign and decimal point.
The default is 1.00
• Bias (BIAS):
An engineering unit data value of 7 digits or less including the sign and decimal point.
The default is 0.00
• RV1 gain (GN1):
A numeric value of 7 digits or less including the sign and decimal point.
The default is 1.00
• RV1 bias (BS1):
An engineering unit data value of 7 digits or less including the sign and decimal point.
The default is 0.00

n Data Items – DIV

Table Data Items of Division Block (DIV)
Data Entry Permitted
Data Name Range Default
Item or Not
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
RV Calculated input value ----- 0
RAW Raw input data Value in the unit at the connection destination -----
RV1 Calculated input value ----- 0
RAW1 Raw input data Value in the unit at the connection destination -----
CPV Calculated output value Δ (*1) CPV engineering unit value SL
GAIN Gain x 7 - digit real number including sign and decimal point 1.00
BIAS Bias x 7 - digit real number including sign and decimal point 0.00
GN1 RV1 gain x 7 - digit real number including sign and decimal point 1.00
BS1 RV1 bias x 7 - digit real number including sign and decimal point 0.00
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
SH CPV scale high limit Value in the same engineering unit as CPV -----
SL CPV scale low limit Value in the same engineering unit as CPV -----
D020603E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for DIV block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.7 Averaging Block (AVE)> D2-30

D2.7 Averaging Block (AVE)

The Averaging Block (AVE) is used when calculate the average value of input data.

n Averaging Block (AVE)

▼ Connection
The Averaging Block (AVE) is a function block that obtains the average value of input data.
Here is a function block diagram of the Averaging Block (AVE).

Q01 RV1

Q02 RV2

Q03 RV3

Q04 RV4
Averaging
CPV OUT
processing
Q05 RV5

Q06 RV6

Q07 RV7

Q08 RV8

(CPV, ∆CPV)

SUB
D020701E.ai

Figure Function Block Diagram of Averaging Block (AVE)

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.7 Averaging Block (AVE)> D2-31
The following table shows the connection types and connection destinations of the I/O terminals
of the Averaging Block (AVE).
Table Connection Types and Connection Destinations of the I/O Terminals of Averaging Block (AVE)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
First
Q01 calculation x Δ x x
input
Second
Q02 calculation x Δ x x
input
Third
Q03 calculation x Δ x x
input
Fourth
Q04 calculation x Δ x x
input
Fifth
Q05 calculation x Δ x x
input
Sixth
Q06 calculation x Δ x x
input
Seventh
Q07 calculation x Δ x x
input
Eighth
Q08 calculation x Δ x x
input
Calculation x x
OUT x x
output
Auxiliary Δ x x
SUB x
output
D020702E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.7 Averaging Block (AVE)> D2-32

n Function of Average Block (AVE)

The AVE block performs input processing, calculation processing, output processing, and alarm
processing.
The processing timings available for the AVE block are a periodic startup and a one-shot startup.
Selections available for the scan period used to execute a periodic startup include the basic scan
period, the medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the AVE block, see
the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Input Processing of Average Block (AVE) When a Calculation Input Value Error
is Detected
The AVE block performs special input processing when an abnormal calculation input value is
detected.

l Calculation Processing of Average Block (AVE)

The AVE block returns the average value of input data using its calculation algorithm and setup
parameters.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.7 Averaging Block (AVE)> D2-33

n Input Processing at Calculated Input Value Error Detection

▼ Calculated Input Value Error Detected
In the Average block (AVE), the detection of calculated input value error is executed for every
input terminal. For each input terminal, when the data status of the connection destination is
invalid (BAD), that of corresponding calculated input value (RVn) becomes invalid (BAD), and the
previous calculated input value is held.
The data status of the calculated output value (CPV) becomes invalid (BAD) or questionable
(QST) at calculated input value error detection.

The settings of the detection conditions for calculated input value error detection in the Average
block (AVE) and the data status of the calculated output value (CPV) at calculated input value
error detection are executed with “Calculated input value error detected” on the Function Block
Detail Builder.
The method to transfer the data status (IOP, IOP-, OOp, NRDY) of the process I/O relations,
which is generated with the calculated input value (RVn) in connection with the above settings, to
the calculated output value (CPV) is specified.
The table below lists the ranges of the calculated input value error detection. The default value is
“1.”
Table Processing at Calculated Input Value Error Detection in the Average Block (AVE)
Calculated input value Error detection conditions Data status
error detection (Data status of the CPV data status transmission
specification calculated input value) origin input value
0 - NR (*1)
RV1 to RVn (n is an average number)
NR (*1)
are all NR (*1). No transmission
At least one of RV1 to RVn
1 QST
(n is an average number) is BAD.
RV1 to RVn (n is an average number)
BAD RV1 to RVn (*2)
are all BAD.
RV1 to RVn (n is an average number)
NR (*1) No transmission
are all NR (*1).
2
At least one of RV1 to RVn
BAD RV1 to RVn (*2)
(n is an average number) is BAD.
D020703E.ai

*1: NR in the table indicates the state in which the data status is neither BAD nor QST.
*2: The priority of input values is in the order of RV1 to RVn. IOP and IOP- precede in the transfer status. IOP is transferred when
NRDY is generated in the input values of higher priority and IOP is generated in the input values of lower priority.

When the calculated input value error which causes the invalid (BAD) data status of calculated
output value (CPV) occurs, the calculation processing is halted, and the previous calculated
output value (CPV) is held.
When the calculated input value error which causes the questionable (QST) data status of
calculated output value (CPV) occurs, the previous calculated input value is held due to the
current calculated input value error. The calculation processing is continued using the previous
value (RV) held and the calculated output value (CPV) is updated.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.7 Averaging Block (AVE)> D2-34

n Calculation Algorithm
▼ Number of Averaged, Sampling Candidate Specification
The Averaging Block (AVE) performs the following calculation processing for obtaining the
average value of input data.

RV1+RV2+RV3+...+RVN
CPV=GAIN •
N
D020704E.ai

“Number of averaged” and “sampling candidate specification” is set using the Function Block
Detail Builder.
• Number of Averaged (N):
Any integer between 1 and 8.
The default is 1.
Set the number of data to be averaged.
• Sampling Candidate Specification:
Select from “Regardless of data status,” “other than BAD” or “other than BAD or QST.”

If the data status of the calculated input value (RVn) changes to the status indicating the data is
not good, this data can be excluded from the averaging calculation. The conditions to include or
exclude the data for the averaging calculation can be defined on the builder under the following
conditions.
• Regardless of data status
All input data (RVn) regardless of data status
• Other than BAD
All input data (RVn) except for BAD data
• Other than BAD and QST
All input data (RVn) except for BAD and QST data

The calculation block’s behavior is restricted by the input error detection function. When the
calculation input error detection is specified to “2,” only “Regardless of data status” is valid as
averaging calculation condition. Or else, any input detected BAD makes the calculated output
value (CPV) become BAD (invalid) and the averaging calculation stops.
While, when the condition is specified as “other than BAD” or “other than BAD or QST,” the above
described phenomena occur, i.e. the BAD input data stops the averaging calculation.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.7 Averaging Block (AVE)> D2-35

n Set Parameter
The parameters of the Averaging Block(AVE) are shown as follows.
• Gain (GAIN):
A numeric value of 7 digits or less including the sign and decimal point.
The default is 1.00

n Data Items – AVE

Table Data Items of Averaging Block (AVE)
Entry Permitted
Data Item Data Name Range Default
or Not
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
RV1 to RV8 Calculated input value 1to 8 ----- 0
RAW1 to RAW8 Raw input data 1to 8 Value in the unit at the connection destination -----
CPV Calculated output value Δ (*1) CPV engineering unit value SL

x 7 - digit real number including sign and

GAIN Gain 1.00
decimal point
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
SH CPV scale high limit Value in the same engineering unit as CPV -----
SL CPV scale low limit Value in the same engineering unit as CPV -----
D020705E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for AVE block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.8 Square Root Block (SQRT)> D2-36

D2.8 Square Root Block (SQRT)

The Square Root Block (SQRT) is used when obtaining the square root of input data.

n Square Root Block (SQRT)

▼ Connection
The Square Root Block (SQRT) is a function block that obtains the square root of input data.
Here is a function block diagram of the Square Root Block (SQRT).

Input
IN RV GAIN • RV CPV OUT
processing

(CPV, ∆CPV)

SUB
D020801E.ai

Figure Function Block Diagram of Square Root Block (SQRT)

The following table shows the connection types and connection destinations of the I/O terminals
of the Square Root Block (SQRT).
Table Connection Types and Connection Destinations of the I/O Terminals of Square Root Block
(SQRT)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
Calculation x
IN x x x
input
Calculation x
OUT x x x
output
Auxiliary Δ x
SUB x x
output
D020802E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.8 Square Root Block (SQRT)> D2-37

n Function of Square Root Block (SQRT)

The SQRT block performs input processing, calculation processing, output processing, and
alarm processing.
The only processing timing available for the SQRT block is a periodic startup. Selections
available for the scan period used to execute a periodic startup include the basic scan period, the
medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the SQRT block,
see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of Square Root Block (SQRT)

The SQRT block calculates the square root of input data using its calculation algorithm and setup
parameters.

l Output Processing Specific to Square Root Block (SQRT)

In the output processing of the SQRT block, it is possible to perform “CPV pushback.”

n Calculation Algorithm
The Square Root Block (SQRT) executes the following calculation processing to obtain the
square root of input data.
CPV=GAIN • RV
D020803E.ai

n Set Parameter
The parameters of the Square Root Block (SQRT) are shown as follows.
• Gain (GAIN):
A numeric value of 7 digits or less including the sign and decimal point.
The default is 1.00

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.8 Square Root Block (SQRT)> D2-38

n CPV Pushback
The CPV pushback is a function used to prevent a sudden change in an output value to the
process control output when the status of a cascade connection is changed from open to close.
If the SQRT block is connected by means of cascade connection and the cascade connection is
opened, the calculation input value (RV) is calculated back based on a calculation output value
(CPV) obtained from a downstream function block via tracking, thereby making the upstream
function block track the value.
The CPV pushback operates only when the output value tracking is set to [Yes].
The following calculation formula is used in the CPV pushback of the SQRT block.

CPV 2
RV=
GAIN
D020804E.ai

If GAIN is 0, the CPV pushback calculation is bypassed and the calculation input value (RV)
retains the previous value.

SEE
ALSO For details on the CPV pushback, see the following:
C4.11, “CPV Pushback”

n Data Items – SQRT

Table Data Items of Square Root Block (SQRT)
Data Entry Permitted
Data Name Range Default
Item or Not
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
RV Calculated input value ----- 0
RAW Raw input data Value in the unit at the connection destination -----
CPV Calculated output value Δ (*1) CPV engineering unit value SL
GAIN Gain x 7 - digit real number including sign and decimal point 1.00
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
SH CPV scale high limit Value in the same engineering unit as CPV -----
SL CPV scale low limit Value in the same engineering unit as CPV -----
D020805E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for SQRT block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.9 Exponential Block (EXP)> D2-39

D2.9 Exponential Block (EXP)

The Exponential Block (EXP) is used when obtaining the result of exponential value of the
base of natural logarithms with the input data.

n Exponential Block (EXP)

▼ Connection
The Exponential Block (EXP) is a function block that obtains the result of exponential value of the
base of natural logarithms with the input data.
Here is a function block diagram of the Exponential Block (EXP).

Input
IN RV GAIN • eRV CPV OUT
processing

(CPV, ∆CPV)

SUB
D020901E.ai

Figure Function Block Diagram of Exponential Block (EXP)

The following table shows the connection types and connection destinations of the I/O terminals
of the Exponential Block (EXP).
Table Connection Types and Connection Destinations of the I/O Terminals of Exponential Block (EXP)
Connection type Connection destination
I/O terminal
Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
Calculation x x x x
IN
input
Calculation x x x x
OUT
output
Auxiliary x Δ x x
SUB
output
D020902E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.9 Exponential Block (EXP)> D2-40

n Function of Exponential Block (EXP)

The EXP block performs input processing, calculation processing, output processing, and alarm
processing.
The only processing timing available for the EXP block is a periodic startup. Selections available
for the scan period used to execute a periodic startup include the basic scan period, the medium-
speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the EXP block, see
the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of Exponential Block (EXP)

The EXP block calculates the value where the base of the natural logarithm is raised to a power
given by the input data using its calculation algorithm and setup parameters.

l Output Processing Specific to Exponential Block (EXP)

In the output processing of the EXP block, it is possible to perform “CPV pushback.”

n Calculation Algorithm
The Exponential Block (EXP) executes the following calculation processing to the input data.

CPV=GAIN • eRV
e: Base of a natural logarithm

n Set Parameter
The parameters of the Exponential Block (EXP) are shown as follows.
• Gain (GAIN):
­A numeric value of 7 digits or less including the sign and decimal point.
The default is 1.00.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.9 Exponential Block (EXP)> D2-41

n CPV Pushback
The CPV pushback is a function used to prevent a sudden change in an output value to the
process control output when the status of a cascade connection is changed from open to close.
If the EXP block is connected by means of cascade connection and the cascade connection is
opened, the calculation input value (RV) is calculated back based on a calculation output value
(CPV) obtained from a downstream function block via tracking, thereby making the upstream
function block track the value.
The CPV pushback operates only when the output value tracking is set to [Yes].
The following calculation formula is used in the CPV pushback of the EXP block.
CPV
RV=ln
GAIN
D020903E.ai

If (CPV/GAIN) ≤ 0, the calculation input value (RV) retains the previous value.

SEE
ALSO For details on the CPV pushback, see the following:
C4.11, “CPV Pushback”

n Data Items – EXP

Table Data Items of Exponential Block (EXP)
Data Entry Permitted
Data Name Range Default
Item or Not
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
RV Calculated input value ----- 0
RAW Raw input data Value in the unit at the connection destination -----
CPV Calculated output value Δ (*1) CPV engineering unit value SL
GAIN Gain x 7 - digit real number including sign and decimal point 1.00
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
SH CPV scale high limit Value in the same engineering unit as CPV -----
SL CPV scale low limit Value in the same engineering unit as CPV -----
D020904E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for EXP block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.10 First-Order Lag Block (LAG)> D2-42

D2.10 First-Order Lag Block (LAG)

The First-Order Lag Block (LAG) is used when performing filtering processing to the input
signals or simulating process characteristics.

n First-Order Lag Block (LAG)

▼ Connection
The First-Order Lag Block (LAG) is a function block that outputs the first-order lag of input
signals.
The First-Order Lag Block (LAG) enables filtering processing of input signals as well as
simulation of process characteristics.
Here is a function block diagram of the First-Order Lag Block (LAG).

Input GAIN
IN RV CPV OUT
processing 1+Tis

(CPV, ∆CPV)

SUB
D021001E.ai

Figure Function Block Diagram of First-Order Lag Block (LAG)

The following table shows the connection types and connection destinations of the I/O terminals
of the First-Order Lag Block (LAG).
Table Connection Types and Connection Destinations of the I/O Terminals of First-Order Lag Block
(LAG)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
Calculation
IN x x x x
input
Calculation x x x x
OUT
output
Auxiliary Δ
SUB x x x
output
D021002E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.10 First-Order Lag Block (LAG)> D2-43

n Function of First-Order Lag Block (LAG)

The LAG block performs input processing, calculation processing, output processing, and alarm
processing.
The only processing timing available for the LAG block is a periodic startup. Selections available
for the scan period used to execute a periodic startup include the basic scan period, the medium-
speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the LAG block, see
the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of First-Order Lag Block (LAG)

The LAG block performs a first-order lag calculation using its calculation algorithm and setup
parameters.

l Output Processing Specific to First-Order Lag Block (LAG)

In the output processing of the LAG block, it is possible to perform “CPV pushback.”

n Calculation Algorithm
The First-Order Lag Block (LAG) executes the following calculation processing to the input data.
GAIN
CPV= • RV
1+Tis
D021003E.ai

Ti : First-order lag time (Ti = I - Scan period)

I : First-order lag time setpoint
s : Laplace transform operator

When the block mode is switched from O/S (out of service) to AUT (automatic), or when the data
status of the calculated output value (CPV) has returned to normal from CAL (calibration) or BAD
(invalid), first-order lag calculation is initialized with the calculated input value (RV).

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.10 First-Order Lag Block (LAG)> D2-44

n Set Parameters
The parameters of the First-Order Lag Block (LAG) are shown as follows.
• Gain (GAIN):
A numeric value of 7 digits or less including the sign and decimal point.
The default is 1.00.
• First-order lag time setpoint (I):
A numeric value between 0.1 and 1000.0. Unit: sec.
The default is 1.
If a time shorter than the scan period is set as the first-order lag time (I), calculation processing is
performed assuming that the first-order lag time setpoint (I) is the same as the scan period.

n Action Example
The following figure shows an example of step response action of the First-Order Lag Block
(LAG).
Input signal

Output signal (When GAIN = 1.000)

Time t
Ti

Ti: First-order lag time (Ti = I - Scan period)

D021004E.ai

Figure Example of the Step Response Action of First-Order Lag Block (LAG)

n CPV Pushback
The CPV pushback is a function used to prevent a sudden change in an output value to the
process control output when the status of a cascade connection is changed from open to close.
If the LAG block is connected by means of cascade connection and the cascade connection is
opened, the calculation input value (RV) is calculated back based on a calculation output value
(CPV) obtained from a downstream function block via tracking, thereby making the upstream
function block track the value.
The CPV pushback operates only when the output value tracking is set to [Yes].
The following calculation formula is used in the CPV pushback of the LAG block.
CPV
RV=
GAIN
D021005E.ai

If GAIN is 0, the CPV pushback calculation is bypassed and the calculation input value (RV)
retains the previous value.

SEE
ALSO For details on the CPV pushback, see the following:
C4.11, “CPV Pushback”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.10 First-Order Lag Block (LAG)> D2-45

n Data Items – LAG

Table Data Items of First-Order Lag Block (LAG)
Data Entry Permitted
Data Name Range Default
Item or Not
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
RV Calculated input value ----- 0
RAW Raw input data Value in the unit at the connection destination -----
CPV Calculated output value Δ (*1) CPV engineering unit value SL
GAIN Gain x 7 - digit real number including sign and decimal point 1.00
I First - order lag time x 0.1 to 10,000.0 seconds 1
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
SH CPV scale high limit Value in the same engineering unit as CPV -----
SL CPV scale low limit Value in the same engineering unit as CPV -----
D021006E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for LAG block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.11 Integration Block (INTEG)> D2-46

D2.11 Integration Block (INTEG)

The Integration Block (INTEG) is used when obtaining the integral value of input data.

n Integration Block (INTEG)

▼ Connection
The Integration Block (INTEG) is a function block that integrates input data.
Here is a function block diagram of the Integration Block (INTEG).

Input GAIN
IN RV CPV OUT
processing Tis

(CPV, ∆CPV)

SUB
D021101E.ai

Figure Function Block Diagram of Integration Block (INTEG)

The following table shows the connection types and connection destinations of the I/O terminals
of the Integration Block (INTEG).
Table Connection Types and Connection Destinations of the I/O Terminals of Integration Block (INTEG)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
Calculation
IN x x x x
input
Calculation x x x x
OUT
output
Auxiliary Δ
SUB x x x
output
D021102E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.11 Integration Block (INTEG)> D2-47

n Function of Integration Block (INTEG)

The INTEG block performs input processing, calculation processing, output processing, and
alarm processing.
The only processing timing available for the INTEG block is a periodic startup. Selections
available for the scan period used to execute a periodic startup include the basic scan period, the
medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the INTEG block,
see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of Integration Block (INTEG)

The INTEG block calculates the integrated value of input data using its calculation algorithm and
setup parameters.

l Output Processing Specific to Integration Block (INTEG)

In the output processing of the INTEG block, it is possible to perform “CPV pushback.”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.11 Integration Block (INTEG)> D2-48

n Calculation Algorithm
The Integration Block (INTEG) executes the following calculation processing for integrating input
data.
GAIN
CPV= • RV
Tis
D021103E.ai

Ti : Integral time (Ti = I)

s : Laplace transform operator

The Integration Block (INTEG) starts calculation actions in accordance with the values of the
manipulation switch (SW).
If the integral value overflows, the previous maximum value used as the calculation result. When
the integral value overflows, BAD (invalid) is set as the data status of the calculated output value
(CPV).
The following figure shows the manipulation switch values and the corresponding calculation
actions as well as block status transitions.
• When Manipulation switch (SW) is 0
Starts to initialize calculation block status, then the manipulation switch (SW) changes to 1
when initialization is completed. Block status is RUN.
• When Manipulation switch (SW) is 1
Starts the integration calculation. The calculated output value (CPV) is updated by each
scan period. Block status is RUN.
• When Manipulation switch (SW) is 2
Holds the current calculated output value (CPV), the calculation stops. Block status is STOP.

n Set Parameters
The parameters of the Integration Block (INTEG) are shown as follows.
• Gain (GAIN):
A numeric value of 7 digits or less including the sign and decimal point.
The default is 1.00.
• Integral time setpoint (I):
A numeric number between 0.1 and 10000.0. Unit: sec.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.11 Integration Block (INTEG)> D2-49

n Action Example
The following figure shows an action example of the Integration Block (INTEG).
Input signal

Ts
GAIN RV
I

Output signal

Time t

Scan period (Ts)

Hold Integration calculation Hold

Initialize Calculation stop

2 1 2
SW

SW(2→0→1) SW(1→2)
D021104E.ai

Figure Action Example of Integration Block (INTEG)

n CPV Pushback
The CPV pushback is a function used to prevent a sudden change in an output value to the
process control output when the status of a cascade connection is changed from open to close.
If the INTEG block is connected by means of cascade connection and the cascade connection is
opened, the calculation input value (RV) is calculated back based on a calculation output value
(CPV) obtained from a downstream function block via tracking, thereby making the upstream
function block track the value.
The CPV pushback operates only when the output value tracking is set to [Yes].
The following calculation formula is used in the CPV pushback of the INTEG block.
CPV
RV=
GAIN
D021105E.ai

If GAIN is 0, the CPV pushback calculation is bypassed and the calculation input value (RV)
retains the previous value.

SEE
ALSO For details on the CPV pushback, see the following:
C4.11, “CPV Pushback”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.11 Integration Block (INTEG)> D2-50

n Data Items – INTEG

Table Data Items of Integration Block (INTEG)
Data Entry Permitted
Data Name Range Default
Item or Not
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
RV Calculated input value ----- 0
BSTS Block status ----- RUN
RAW Raw input data Value in the unit at the connection destination -----
CPV Calculated output value Δ (*1) CPV engineering unit value SL
SW Manipulation switch x 0, 1, 2 -----
GAIN Gain x 7 - digit real number including sign and decimal point 1.00
I Integral time x 0.1 to 10,000.0 seconds 1
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
SH CPV scale high limit Value in the same engineering unit as CPV -----
SL CPV scale low limit Value in the same engineering unit as CPV -----
D021106E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for INTEG block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

n Block Status of Integration Block (INTEG)

Table Block Status of Integration Block (INTEG)
Block Status
Level Description
Symbol Name
RUN Integration Starts Initialization or integration starts.
1
STOP Integration Stops Integration stopped, the output is held.
D021107E.ai

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.12 Derivative Block (LD)> D2-51

D2.12 Derivative Block (LD)

The Derivative Block (LD) is used when obtaining the derivative value of input data.

n Derivative Block (LD)

▼ Connection
The Derivative Block (LD) is a function block that differentiates input data.
Here is a function block diagram of the Derivative Block (LD).

Input GAIN • Tds

IN RV CPV OUT
processing 1+Tds

(CPV, ∆CPV)

SUB
D021201E.ai

Figure Function Block Diagram of Derivative Block (LD)

The following table shows the connection types and connection destinations of the I/O terminals
of the Derivative Block (LD).
Table Connection Types and Connection Destinations of the I/O Terminals of Derivative Block (LD)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
Calculation x x x x
IN
input
Calculation x x x x
OUT
output
Auxiliary x Δ x x
SUB
output
D021202E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.12 Derivative Block (LD)> D2-52

n Function of Derivative Block (LD)

The LD block performs input processing, calculation processing, output processing, and alarm
processing.
The only processing timing available for the LD block is a periodic startup. Selections available
for the scan period used to execute a periodic startup include the basic scan period, the medium-
speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the LD block, see
the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of Derivative Block (LD)

The LD block calculates the derivative value of input data using its calculation algorithm and
setup parameters.

l Output Processing Specific to Derivative Block (LD)

In the output processing of the LD block, it is possible to perform “CPV pushback.”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.12 Derivative Block (LD)> D2-53

n Calculation Algorithm
The Derivative Block (LD) executes the following calculation processing to differentiate input
data.
Tds
CPV=GAIN • • RV
1+Tds
D021203E.ai

Td : Derivative time (Td = D)

s : Laplace transform operator

When the block mode is switched from O/S (out of service) to AUT (automatic), or when the
data status of the calculated input value (CPV) returns to normal from CAL (calibration) or BAD
(invalid), derivation calculation is initialized with the calculated input value (RV).

n Set Parameters
The parameters of the Derivative Block (LD) are shown as follows.
• Gain (GAIN):
A numeric value of 7 digits or less including the sign and decimal point.
The default is 1.00.
• Derivative time setpoint (D):
A numeric value between 0.1 and 1000.0. Unit: sec.

If a time shorter than the scan period is set as the derivative time setpoint (D), calculation
processing is performed assuming that the derivative time setpoint (D) is same as the scan period.

n Action Example
The following figure shows an action example of the Derivative Block (LD).
Input signal

Output signal (When GAIN = 1.000)

Time t
Td

Td: Derivative time (D) 0.0 to 10000.0 seconds

D021204E.ai

Figure Step Response of Derivative Block (LD)

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.12 Derivative Block (LD)> D2-54

n CPV Pushback
The CPV pushback is a function used to prevent a sudden change in an output value to the
process control output when the status of a cascade connection is changed from open to close.
If the LD block is connected by means of cascade connection and the cascade connection is
opened, the calculation input value (RV) is calculated back based on a calculation output value
(CPV) obtained from a downstream function block via tracking, thereby making the upstream
function block track the value.
The CPV pushback operates only when the output value tracking is set to [Yes].
The following calculation formula is used in the CPV pushback of the LD block.
CPV
RV=
GAIN
D021205E.ai

If GAIN is 0, the CPV pushback calculation is bypassed and the calculation input value (RV)
retains the previous value.

SEE
ALSO For details on the CPV pushback, see the following:
C4.11, “CPV Pushback”

n Data Items – LD
Table Data Items of Derivative Block (LD)
Data Entry Permitted
Data Name Range Default
Item or Not
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
RV Calculated input value ----- 0
RAW Raw input data Value in the unit at the connection destination -----
CPV Calculated output value Δ (*1) CPV engineering unit value SL
GAIN Gain x 7 - digit real number including sign and decimal point 1.00
D Derivative time x 0.0 to 10,000.0 seconds 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
SH CPV scale high limit Value in the same engineering unit as CPV -----
SL CPV scale low limit Value in the same engineering unit as CPV -----
D021206E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for LD block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.13 Ramp Block (RAMP)> D2-55

D2.13 Ramp Block (RAMP)

The Ramp Block (RAMP) is used to generate an output data to follow the step changes of
the input data with the ramp characteristic (constant velocity).

n Ramp Block (RAMP)

▼ Connection
The Ramp Block (RAMP) is a function block that generates an output data to follow the step
changes of the input data with the ramp characteristic (constant velocity).
Here is a function block diagram of the Ramp Block (RAMP).

Input
IN RV GAIN • (Ramp characteristic) CPV OUT
processing

(CPV, ∆CPV)

SUB
D021301E.ai

Figure Function Block Diagram of Ramp Block (RAMP)

The following table shows the connection types and connection destinations of the I/O terminals
of the Ramp Block (RAMP).
Table Connection Types and Connection Destinations of the I/O Terminals of Ramp Block (RAMP)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
Calculation Δ
IN x x x
input
Calculation
OUT x x x x
output
Auxiliary Δ
SUB x x x
output
D021302E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.13 Ramp Block (RAMP)> D2-56

n Function of Ramp Block (RAMP)

The RAMP block performs input processing, calculation processing, output processing, and
alarm processing.
The only processing timing available for the RAMP block is a periodic startup. Selections
available for the scan period used to execute a periodic startup include the basic scan period, the
medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the RAMP block,
see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of Ramp Block (RAMP)

The RAMP block performs computation using its calculation algorithm and setup parameters.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.13 Ramp Block (RAMP)> D2-57

n Calculation Algorithm
The Ramp Block (RAMP) executes the calculation processing that generates an output data to
follow the step changes of the input data with the ramp characteristic (constant velocity).
The calculated output value (CPV) is the Ramp characteristic output signal multiplied by the gain
(GAIN).

CPV = GAIN • (Ramp characteristic)

The ramp characteristic is shown below.

Input signal

(CPV span)
• Scan period (sec.)
STEP

Output signal (When GAIN = 1.00)

Scan period
D021303E.ai

Figure Ramp Characteristic

The rate of the output data change is determined by the value of the step (STEP) parameter,
scan period and span of the calculated output value (CPV).
CPV span
Output data change per second =
STEP
D021304E.ai

CPV span
Output data change per scan = • Scan period (seconds)
STEP
D021305E.ai

n Set Parameters
The parameters of the Ramp Block (RAMP) are shown as follows.
• Gain (GAIN):
A numeric value of 7 digits or less including the sign and decimal point.
The default is 1.00.
• Step (STEP):
A numeric number between 0.1 and 10000.0.

The step (STEP) defines in how many scans that the calculated output value (CPV) follows up
the full-span of the input change, in one second scan period. When the scan period is not one
second, the number of scans needed for the full-span input change can be calculated by dividing
the step (STEP) by the scan period (second).

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.13 Ramp Block (RAMP)> D2-58

n Data Items – RAMP

Table Data Items of Ramp Block (RAMP)
Data Entry Permitted
Data Name Range Default
Item or Not
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specificaton ----- -----
AOFS Alarm masking specification ----- -----
RV Calculated input value ----- 0
RAW Raw input data Value in the unit at the connection destination -----
CPV Calculated output value Δ (*1) CPV engineering unit value SL
GAIN Gain x 7 - digit real number including sign and decimal point 1.00
STEP Step x 0.1 to 10,000.0 seconds 1
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
SH CPV scale high limit Value in the same engineering unit as CPV -----
SL CPV scale low limit Value in the same engineering unit as CPV -----
D021306E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for RAMP block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.14 Lead/Lag Block (LDLAG)> D2-59

D2.14 Lead/Lag Block (LDLAG)

The Lead/Lag Block (LDLAG) is used for dynamic compensation in feedforward control.

n Lead/Lag Block (LDLAG)

▼ Connection
The Lead/Lag Block (LDLAG) is a function block that performs dynamic compensation in
feedforward control. Normally, this block is used in combination with the controller block or
Feedforward Signal Summing Block (FFSUM).
Here is a function block diagram of the Lead/Lag Block (LDLAG).

Input GAIN • (1+Tds)

IN RV CPV OUT
processing 1+Tis

(CPV, ∆CPV)

SUB
D021401E.ai

Figure Function Block Diagram of Lead/Lag Block (LDLAG)

The following table shows the connection types and connection destinations of the I/O terminals
of the Lead/Lag Block (LDLAG).
Table Connection Types and Connection Destinations of I/O Terminals of Lead/Lag Block (LDLAG)
Connection type Connection destination
I/O terminal
Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
Calculation
IN x x x x
input
Calculation
OUT x x x x
output
Auxiliary Δ
SUB x x x
output
D021402E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.14 Lead/Lag Block (LDLAG)> D2-60

n Function of Lead/Lag Block (LDLAG)

The LDLAG block performs input processing, calculation processing, output processing, and
alarm processing.
The only processing timing available for the LDLAG block is a periodic startup. Selections
available for the scan period used to execute a periodic startup include the basic scan period, the
medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the LDLAG block,
see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of Lead/Lag Block (LDLAG)

The LDLAG block performs computation using its calculation algorithm and setup parameters.

l Output Processing Specific to Lead/Lag Block (LDLAG)

In the output processing of the LDLAG block, it is possible to perform “CPV pushback.”

n Calculation Algorithm
The Lead/Lag Block (LDLAG) executes the following calculation processing to perform dynamic
compensation of the lead/lag element.
GAIN • (1+Tds)
CPV= • RV
1+Tis
D021403E.ai

Td : Lead time (Td = D)

Ti : Lag time (Ti = I - Scan period)
s : Laplace transform operator

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.14 Lead/Lag Block (LDLAG)> D2-61

n Set Parameters
The parameters of the Lead/Lag Block (LDLAG) are shown as follows.
• Gain (GAIN):
A numeric value of 7 digits or less including the sign and decimal point.
The default is 1.00.
• Lead time setpoint (D):
A numeric value between 0.0 and 10000.0. Unit: sec.
• Lag time setpoint (I):
A numeric value between 0.0 and 10000.0. Unit: sec.

If a time shorter than the scan period is set as the lag time setpoint (I), calculation processing is
performed assuming that the lag time (I) is same as the scan period.

n Action Example
The following figure shows the action of the Lead/Lag Block (LDLAG).

D/I>1

Input signal

Output signal (GAIN = 1.000)

D/I<1

Time t D021404E.ai

Figure Action of Lead/Lag Block (LDLAG)

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.14 Lead/Lag Block (LDLAG)> D2-62

n CPV Pushback
The CPV pushback is a function used to prevent a sudden change in an output value to the
process control output when the status of a cascade connection is changed from open to close.
If the LDLAG block is connected by means of cascade connection and the cascade connection
is opened, the calculation input value (RV) is calculated back based on a calculation output value
(CPV) obtained from a downstream function block via tracking, thereby making the upstream
function block track the value.
The CPV pushback operates only when the output value tracking is set to [Yes].
The following calculation formula is used in the CPV pushback of the LDLAG block.
CPV
RV=
GAIN
D021405E.ai

If GAIN is 0, the CPV pushback calculation is bypassed and the calculation input value (RV)
retains the previous value.

SEE
ALSO For details on the CPV pushback, see the following:
C4.11, “CPV Pushback”

n Data Items – LDLAG

Table Data Items of Lead/Lag Block (LDLAG)
Data Entry Permitted
Data Name Range Default
Item or Not
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
RV Calculated input value ----- 0
RAW Raw input data Value in the unit at the connection destination -----
CPV Calculated output value Δ (*1) CPV engineering unit value SL
GAIN Gain x 7 - digit real number including sign and decimal point 1.00
D Lead time x 0.0 to 10,000.0 seconds 0
I Lag time x 0.1 to 10,000.0 seconds 1
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
SH CPV scale high limit Value in the same engineering unit as CPV -----
SL CPV scale low limit Value in the same engineering unit as CPV -----
D021406E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for LDLAG block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.15 Dead-Time Block (DLAY)> D2-63

D2.15 Dead-Time Block (DLAY)

The Dead-Time Block (DLAY) is used when simulating the dynamic process
characteristics.

n Dead-Time Block (DLAY)

▼ Connection
The Dead-Time Block (DLAY) is a function block that simulates the dynamic process
characteristics using dead time and first-order lag.
Here is a function block diagram of the Dead-Time Block (DLAY).

Input GAIN -LS

IN RV e CPV OUT
processing 1+Tis

(CPV, ∆CPV)

SUB
D021501E.ai

Figure Function Block Diagram of Dead Block (DLAY)

The following table shows the connection types and connection destinations of the I/O terminals
of the Dead-Time Block (DLAY).
Table Connection Types and Connection Destinations of the I/O Terminals of Dead-Time Block (DLAY)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting block
reference testing manipulation connection I/O I/O
IN Main input x x x x
Calculation
OUT x x x x
output
Auxiliary Δ
SUB x x x
output
D021502E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.15 Dead-Time Block (DLAY)> D2-64

n Function of Dead-Time Block (DLAY)

The DLAY block performs input processing, calculation processing, output processing, and
alarm processing. The only processing timing available for the DLAY block is a periodic startup.
Selections available for the scan period used to execute a periodic startup include the basic scan
period, the medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the DLAY block,
see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of Dead-Time Block (DLAY)

The DLAY block performs computation using its calculation algorithm and setup parameters.

l Output Processing Specific to Dead-Time Block (DLAY)

In the output processing of the DLAY block, it is possible to perform “CPV pushback.”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.15 Dead-Time Block (DLAY)> D2-65

n Calculation Algorithm
▼ Number of Sample Points
The Dead-Time Block (DLAY) realizes the dead time characteristic through sampling. For this
reason, the following calculation processing that uses dead time and first-order lag is performed
to simulate the dynamic process characteristics.
GAIN
CPV= e-LS • RV
1+Tis D021503E.ai

L : Dead time L = Sampling interval (SMPL) • (m - I)

m : Number of sample points
Ti : First-order lag time (Ti = I - scan period)
e : Base number of natural logarithm
s : Laplace transform operator

In order to smoothen the calculated output value (CPV), the Dead-Time Block (DLAY) performs
complementary calculation to values between sampled values when obtaining the calculated
output value (CPV).
Initialization of all sampled data (dead time buffer) is done by the reset switch (RST). When the
reset switch (RST) is set to “1,” the dead time buffer is initialized with the calculated input value
(RV). When the initialization is complete, the reset switch (RST) returns to “0” (normal state).
When the data status of the calculated output value (CPV) returns to normal from IOP+ (input
open high) or CAL (calibration), the reset switch (RST) changes to “1” automatically and the dead
time buffer is initialized.

The number of sample points is set on the Function Block Detail Builder.
• Number of Sample Points: A numeric value between 1 and 60

n Set Parameters
The parameters of the Dead-Time Block (DLAY) are shown as follows.
• Gain (GAIN):
A numeric value of 7 digits or less including the sign and decimal point.
• Sampling interval (SMPL):
A numeric value between 0.1 and 10000.0. Unit: sec.
Set a value which is a multiple of the scan period.
• First-order lag time (I):
A numeric value between 0.1 and 10000.0. Unit: sec.

If a time shorter than the scan period is set as the first-order lag time (I), calculation processing is
performed assuming that the first-order lag time (I) is same as the scan period.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.15 Dead-Time Block (DLAY)> D2-66

n Action Example
The following figure shows an action example of the Dead-Time Block (DLAY).
Input signal

Output signal (When GAIN = 1.000)

Time t
L Ti

L Dead time
Ti First-order lag time (Ti = I - Scan period)
D021504E.ai

Figure Action Example of Dead Time Block (DLAY)

n CPV Pushback
The CPV pushback is a function used to prevent a sudden change in an output value to the
process control output when the status of a cascade connection is changed from open to close.
If the DLAY block is connected by means of cascade connection and the cascade connection is
opened, the calculation input value (RV) is calculated back based on a calculation output value
(CPV) obtained from a downstream function block via tracking, thereby making the upstream
function block track the value.
The CPV pushback operates only when the output value tracking is set to [Yes].
The following calculation formula is used in the CPV pushback of the DLAY block.
CPV
RV=
GAIN
D021505E.ai

If GAIN is 0, the CPV pushback calculation is bypassed and the calculation input value (RV)
retains the previous value.

SEE
ALSO For details on the CPV pushback, see the following:
C4.11, “CPV Pushback”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.15 Dead-Time Block (DLAY)> D2-67

n Data Items – DLAY

Table Data Items of Dead-Time Block (DLAY)
Data Entry Permitted
Data Name Range Default
Item or Not
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
RV Calculated input value ----- 0
RAW Raw input data Value in the unit at the connection destination -----
CPV Calculated output value Δ (*1) CPV engineering unit value SL
RST Reset switch x 0, 1 0
GAIN Gain x 7 - digit real number including sign and decimal point 1.00
SMPL Sampling interval x 0.1 to 10,000.0 seconds 1
I First - order lag time x 0.1 to 10,000.0 seconds 1
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
SH CPV scale high limit Value in the same engineering unit as CPV -----
SL CPV scale low limit Value in the same engineering unit as CPV -----
D021506E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for DLAY block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.16 Dead-Time Compensation Block (DLAY-C)> D2-68

D2.16 Dead-Time Compensation Block (DLAY-C)

The Dead-Time Compensation Block (DLAY-C) is used for dead time compensation
control.

n Dead-Time Compensation Block (DLAY-C)

▼ Connection
The Dead-Time Compensation Block (DLAY-C) is a function block that is used in combination
with the controller block when performing dead time compensation control.
Here is a function block diagram of the Dead-Time Compensation Block (DLAY-C).

Input GAIN
IN RV (e-LS-1) CPV OUT
processing 1+Tis

(CPV, ∆CPV)

SUB
D021601E.ai

Figure Function Block Diagram of Dead-Time Compensation Block (DLAY-C)

The following figure shows an example of dead time compensation control using the Dead-Time
Compensation Block (DLAY-C).
PID controller block (PID)

- PID
Set point value
calculation
+
Input compensated value (VN)

Measured value
Dead-Time
Output Compensation Input
Block
(DLAY-C)

Process
D021602E.ai

Figure Example of Dead Time Compensation Control Using Dead-Time Compensation Block (DLAY-C)

The following table shows the connection types and connection destinations of the I/O terminals
of the Dead-Time Compensation Block (DLAY-C).
Table Connection Types and Connection Destinations of the I/O Terminals of Dead Time Compensation
Block (DLAY-C)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
Calculation
IN x x x x
input
Calculation
OUT x x x x
output
Auxiliary Δ
SUB x x x
output
D021603E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.16 Dead-Time Compensation Block (DLAY-C)> D2-69

n Function of Dead-Time Compensation Block (DLAY-C)

The DLAY-C block performs input processing, calculation processing, output processing, and
alarm processing.
The only processing timing available for the DLAY-C block is a periodic startup. Selections
available for the scan period used to execute a periodic startup include the basic scan period, the
medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the DLAY-C block,
see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of Dead-Time Compensation Block (DLAY-C)

The DLAY-C block performs computation using its calculation algorithm and setup parameters.

n Calculation Algorithm
▼ Number of Sample Points
The Dead-Time Compensation Block (DLAY-C) performs the following calculation processing.
The dead time characteristic is realized through sampling.
GAIN
CPV= (e-LS -1) • RV
1+Tis
D021604E.ai

L : Dead time L = Sampling interval (SMPL) • (m - I)

m : Number of sample points
Ti : First-order lag time (Ti = I - Scan period)
e : Base number of natural logarithm
s : Laplace transform operator

In order to smoothen the calculated output value (CPV), the Dead-Time Compensation Block
(DLAY-C) performs complementary calculation to the values between the sampled values.
Initialization of all sampled data (dead time buffer) is done by the reset switch (RST). When the
reset switch (RST) is turned to “1,” the dead time buffer is initialized by the calculated input value
(RV). When the initialization is complete, the reset switch (RST) returns to “0” (normal state).
When the data status of the calculated output value (CPV) returns to normal from IOP+ (input
open high) or CAL (calibration), the reset switch (RST) changes to “1” automatically and the dead
time buffer is initialized.

The number of sample points is set on the Function Block Detail Builder.
• Number of Sample Points: A numeric value between 1 and 60

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.16 Dead-Time Compensation Block (DLAY-C)> D2-70

n Set Parameters
The parameters of the Dead-Time Compensation Block (DLAY-C) are shown as follows.
• Gain (GAIN):
A numeric value of 7 digits or less including the sign and decimal point.
• Sampling interval (SMPL):
A numeric value between 0.1 and 10000.0. Unit: sec.
Set a multiple of the scan period as the value.
• First-order lag time (I):
A numeric value between 0.1 and 10000.0. Unit: sec.

If a time shorter than the scan period is set as the first-order lag time (I), calculation processing is
performed assuming that the first-order lag time (I) is same as the scan period.

n Action Example
The following figure shows an action example of the Dead-Time Compensation Block (DLAY-C).
Input signal

Time t

Output signal (When GAIN = 1.000)

L Dead time
Ti Ti First-order lag time (Ti = I - Scan period)

L
D021605E.ai

Figure Action Example of Dead-Time Compensation Block (DLAY-C)

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.16 Dead-Time Compensation Block (DLAY-C)> D2-71

n Data Items – DLAY-C

Table Data Items of Dead-Time Compensation Block (DLAY-C)
Data Entry Permitted
Data Name Range Default
Item or Not
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specificaton ----- -----
AOFS Alarm masking specification ----- -----
RV Calculated input value ----- 0
RAW Raw input data Value in the unit at the connection destination -----
CPV Calculated output value Δ (*1) CPV engineering unit value SL
RST Reset switch x 0, 1 0
GAIN Gain x 7 - digit real number including sign and decimal point 1.00
SMPL Sampling interval x 0.1 to 10,000.0 seconds 1
I First - order lag time x 0.1 to 10,000.0 seconds 1
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
SH CPV scale high limit Value in the same engineering unit as CPV -----
SL CPV scale low limit Value in the same engineering unit as CPV -----
D021606E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for DLAY-C block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.17 Moving-Average Block (AVE-M)> D2-72

D2.17 Moving-Average Block (AVE-M)

The Moving-Average Block (AVE-M) is used when obtaining the moving average of the
input signals that have been received between the present and a certain time in the past.

n Moving-Average Block (AVE-M)

▼ Connection
The Moving-Average Block (AVE-M) is a function block that obtains the moving average of the
input signals that have been received between the present and a certain time in the past.
Here is a function block diagram of the Moving-Average Block (AVE-M).

Input Xr+Xr-1+...+Xr-m+1
IN RV GAIN CPV OUT
processing m

(CPV, ∆CPV)

SUB
D021701E.ai

Figure Function Block Diagram of Moving-Average Block (AVE-M)

The following table shows the connection types and connection destinations of the I/O terminals
of the Moving-Average Block (AVE-M).
Table Connection Types and Connection Destinations of the I/O Terminals of Moving-Average Block
(AVE-M)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
Calculation x Δ
IN x x
input
Calculation
OUT x x x x
output
Auxiliary Δ
SUB x x x
output
D021702E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.17 Moving-Average Block (AVE-M)> D2-73

n Function of Moving Average Block (AVE-M)

The AVE-M block performs input processing, calculation processing, output processing, and
alarm processing.
The only processing timing available for the AVE-M block is a periodic startup. Selections
available for the scan period used to execute a periodic startup include the basic scan period, the
medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the AVE-M block,
see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of Moving Average Block (AVE-M)

The AVE-M block calculates the moving average of an input signal using its calculation algorithm
and setup parameters.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.17 Moving-Average Block (AVE-M)> D2-74

n Calculation Algorithm
The Moving-Average Block (AVE-M) performs the following calculation processing to obtain the
moving average of input data.
Xr+Xr-1+...+Xr-m+1
CPV=GAIN •
m D021703E.ai

The Moving-Average Block (AVE-M) calculates the average value of past data that have been
sampled at a specified interval. The target input signals of this calculation are the specified
number of latest sampled data.
The following shows an action example of the Moving-Average Block (AVE-M) when the
specified number of samples is “6.”

Xr+Xr-1+...+Xr-m+1 Specified time interval (SMPL)

m CPV
X

RV GAIN

PREV
Xr

Xr-1 Xr-m+1

Moving average buffer r-8 r-7 r-6 r-5 r-4 r-3 r-2 r-1 r

Number of moving average samples at time r (6 points)

m Number of sample points: 1 to 60
SMPL Sampling interval: 0.1 to 10000.0 seconds
PREV Earliest sampled data: Number of moving average samples at time r-1 (6 points)
(Calculation input value of m • SMPL seconds before) • GAIN
Moving average measuring time = SMPL • m (second)
Number of moving average samples at time r-2 (6 points)
D021704E.ai

Figure Action of Moving-Average Block (AVE-M)

Initialization of the moving average is done by the reset switch (RST). When the reset switch
(RST) is turned to “1,” the buffer is initialized with the calculated input value (RV). When the
initialization is complete, the reset switch (RST) returns to “0” (normal state). When the data
status of the calculated output value (CPV) returns to normal from IOP+ (input open high) or
CAL (calibration), the reset switch (RST) changes to “1” automatically and the moving average is
initialized.
The earliest sampled data is stored in the earliest calculation input value (PREV) and is available
for reference.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.17 Moving-Average Block (AVE-M)> D2-75

n Set Parameters
The parameters of the Moving-Average Block (AVE-M) are shown as follows.
• Gain (GAIN):
A numeric value of 7 digits or less including the sign and decimal point.
• Number of Sample Point (NUM):
A numeric value between 1 and 60.
• Sampling interval (SMPL):
A numeric value between 0.1 and 10000.0. Unit: sec.

For the sampling interval (SMPL), set a multiple of the scan period. If any other value is set,
sampling is performed at an interval rounded up to the next larger multiple of the scan period.
How the sampling interval (SMPL) value is rounded up is shown as follows:
Scan period = 1 second SMPL = 0.5 → Action occurs assuming SMPL = 1
Scan period = 1 second SMPL = 1.1 → Action occurs assuming SMPL = 2
Scan period = 1 second SMPL = 2 → Action at SMPL = 2
Scan period = 0.1 second SMPL = 0.5 → Action at SMPL = 0.5

n Data Items – AVE-M

Table Data Items of Moving-Average Block (AVE-M)
Data Entry Permitted
Data Name Range Default
Item or Not
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
RV Calculated input value ----- 0
RAW Raw input data Value in the unit at the connection destination -----
CPV Calculated output value Δ (*1) CPV engineering unit value SL
RST Reset switch x 0, 1 0
PREV Earliest calculation input value Value in the same engineering unit as CPV 0
GAIN Gain x 7 - digit real number including sign and decimal point 1.00
SMPL Sampling interval x 0.1 to 10,000.0 seconds 1
NUM Number of samples x 0 to 60 1
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
SH CPV scale high limit Value in the same engineering unit as CPV -----
SL CPV scale low limit Value in the same engineering unit as CPV -----
D021705E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for AVE-M block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.18 Cumulative-Average Block (AVE-C)> D2-76

D2.18 Cumulative-Average Block (AVE-C)

The Cumulative-Average Block (AVE-C) is used when obtaining the average value
(integrated average value) of the input data received after a specified point in time.

n Cumulative-Average Block (AVE-C)

▼ Connection
The Cumulative-Average Block (AVE-C) is a function block that calculates the average value
(integrated average value) of the input data received after a specified point in time.
Here is a function block diagram of the Cumulative-Average Block (AVE-C).

Manipulation SW
switch

Input
IN
processing
RV GAIN • Average CPV OUT
value

(CPV, ∆CPV)

SUB
D021801E.ai

Figure Function Block Diagram of Cumulative-Average Block (AVE-C)

The following table shows the connection types and connection destinations of the I/O terminals
of the Cumulative-Average Block (AVE-C).
Table Connection Types and Connection Destinations of the I/O Terminals of Cumulative-Average
Block (AVE-C)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
Calculation Δ
IN x x x
input
Calculation
OUT x x x x
output
Auxiliary Δ
SUB x x x
output
D021802E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.18 Cumulative-Average Block (AVE-C)> D2-77

n Function of Cumulative Average Block (AVE-C)

The AVE-C block performs input processing, calculation processing, output processing, and
alarm processing.
The only processing timing available for the AVE-C block is a periodic startup. Selections
available for the scan period used to execute a periodic startup include the basic scan period, the
medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the AVE-C block,
see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of Cumulative Average Block (AVE-C)

The AVE-C block calculates the cumulative average (integral average value) of input data using
its calculation algorithm and setup parameters.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.18 Cumulative-Average Block (AVE-C)> D2-78

n Calculation Algorithm
The Cumulative-Average Block (AVE-C) performs the processing that calculates the average
value (integrated average value) of input data.

The Cumulative-Average Block (AVE-C) starts calculation actions in accordance with the values
of the manipulation switch (SW).
When the manipulation switch is turned to “0,” the current calculated output value (CPV) is saved
as the previous average value (PREV), then average calculation is started again. This is called
initialization of integration calculation.
After that point, the integrated average value of input data for each scan period to the current
time cumulates until the manipulation switch (SW) turns to “0” again.
The calculated output value(CPV) is the cumulated integrated average value multiplied by gain
(GAIN).

CPV=GAIN • Cumulated Integrated average value

The status of calculation action is indicated by the block status.

The following figure shows the manipulation switch values (SW), corresponding actions and
block status transitions.
• When Manipulation switch (SW) is 0
Starts to initialize calculation block status, then the manipulation switch (SW) changes to 1
when initialization is completed. Block status is RUN.
• When Manipulation switch (SW) is 1
Starts the average calculation. The calculated output value (CPV) is updated by each scan
period. Block status is RUN.
• When Manipulation switch (SW) is 2
Holds the current calculated output value (CPV), the calculation stops. Block status is STOP.

Start and end of integrated average calculation are set by the manipulation switch (SW). The
manipulation switch can be operated from operation and monitoring functions or other function
blocks.
Even when the block mode or alarm status has changed, the Cumulative-Average Block (AVE-C)
will not initialize the average value calculation automatically.
There is an integration number counter inside the Cumulative-Average Block (AVE-C). When
the manipulation switch (SW) is set to “1,” the value of this counter increases by one for each
scan period. When the counter value becomes 2,147,483,647, calculation will stops and set the
manipulation switch (SW) to “0,” then the calculation restarts.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.18 Cumulative-Average Block (AVE-C)> D2-79

n Set Parameters
The parameters of the Cumulative-Average Block (AVE-C) are shown as follows.
• Manipulation switch:
Specify a numeric value from 0, 1 and 2.
• Gain (GAIN):
A numeric value of 7 digits or less including the sign and decimal point.
The default is 1.00.

n Action Example
The following figure shows an action example of the Cumulative-Average Block (AVE-C).

Calculated
output value
(CPV)

Calculated
input value
(RV)

Average value Average value

Hold calculation Hold calculation

Initialize Initialize

2 1 2 1
SW

(2→1) (1→2) (2→1)

D021803E.ai

Figure Action Example of Cumulative-Average Block (AVE-C)

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.18 Cumulative-Average Block (AVE-C)> D2-80

n Data Items – AVE-C

Table Data Items of Cumulative-Average Block (AVE-C)
Data Entry Permitted
Data Name Range Default
Item or Not
MODE Block mode x ----- O/S (AUT)
BSTS Block status ----- RUN
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
RV Calculated input value ----- 0
RAW Raw input data Value in the unit at the connection destination -----
CPV Calculated output value Δ (*1) CPV engineering unit value SL
SW Manipulation switch x 0, 1, 2 0
PREV Previous average value Value in the same engineering unit as CPV SL
GAIN Gain x 7 - digit real number including sign and decimal point 1.00
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
SH CPV scale high limit Value in the same engineering unit as CPV -----
SL CPV scale low limit Value in the same engineering unit as CPV -----
D021804E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for AVE-C block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

n Block Status of Cumulative-Average Block (AVE-C)

Table Block Status of Block Status of Cumulative-Average Block (AVE-C)
Block Status
Level Description
Symbol Name
RUN Averaging Starts Initialization or averaging starts.
1
STOP Averaging Stops Averaging stopped, the output is held.
D021805E.ai

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.19 Variable Line-Segment Function Block (FUNC-VAR)> D2-81

D2.19 Variable Line-Segment Function Block

(FUNC-VAR)
The Variable Line-Segment Function Block (FUNC-VAR) converts the input signal into a
function by using arbitrary unequal line segments.
The line segment characteristics can be changed from the Variable Line-Segment
Function Block (FUNC-VAR) on operation and monitoring functions.

n Variable Line-Segment Function Block (FUNC-VAR)

▼ Connection
The Variable Line-Segment Function Block (FUNC-VAR) is a function block that converts input
signals in accordance with an arbitrary line-segment function.
Here is a function block diagram of the Variable Line-Segment Function Block (FUNC-VAR).

Input Variable
IN RV GAIN • CPV OUT
processing line-segment function

(CPV, ∆CPV)

SUB
D021901E.ai

Figure Function Block Diagram of Variable Line-Segment Function Block (FUNC-VAR)

The following table shows the connection types and connection destinations of the I/O terminals
of the Variable Line-Segment Function Block (FUNC-VAR).
Table Connection Types and Connection Destinations of the I/O Terminals of Variable Line-Segment
Function Block (FUNC-VAR)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
Calculation
IN x x x x
input
Calculation
OUT x x x x
output
Auxiliary Δ
SUB x x x
output
D021902E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.19 Variable Line-Segment Function Block (FUNC-VAR)> D2-82

n Function of Variable Line-Segment Function Block (FUNC-VAR)

The FUNC-VAR block performs input processing, calculation processing, output processing, and
alarm processing.
The only processing timing available for the FUNC-VAR block is a periodic startup. Selections
available for the scan period used to execute a periodic startup include the basic scan period, the
medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the FUNC-VAR
block, see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of Variable Line-Segment Function Block

(FUNC-VAR)
The FUNC-VAR block converts the value of an input signal using its calculation algorithm (line-
segment function) and setup parameters.

l Output Processing Specific to Variable Line-Segment Function Block

(FUNC-VAR)
In the output processing of the FUNC-VAR block, it is possible to perform “CPV pushback.”

n Calculation Algorithm
The Variable Line-Segment Function Block (FUNC-VAR) performs the calculation processing
that converts the input signal corresponding to the X coordinate of the set line segment, to the Y
coordinate value of the line segment.
The calculated output value (CPV) is the converted value multiplied by the gain (GAIN).

CPV=GAIN • Variable line-segment function output

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.19 Variable Line-Segment Function Block (FUNC-VAR)> D2-83

n Set Parameters
The parameters of the Variable Line-Segment Function Block (FUNC-VAR) are shown as follows.
• Number of segments (SECT):
A numeric value between 1 and 14.
• X_axis coordinate (input):
Set the engineering unit input signal after input signal conversion.
X01 to X15 (1 to Number of line-segment divisions + 1)
• Y_axis coordinate (output):
Set the engineering unit calculated output value (CPV).
Y01 to Y15 (1 to Number of line-segment divisions + 1)

Line-segment coordinates can be set from operation and monitoring functions or other function
blocks.

Set the X_axis coordinate line-segment function in the continues increasing direction. When the
setting does not allow the X coordinate to increase strictly, the function assumes that the function
is represented by the solid line shown in the figure below.
Y
Set line segment
(error)

Action line segment

X
D021903E.ai

Figure Action When Line-Segment Function Setting Error Occurs

n Action Example
The following figure shows an example of the variable line-segment function with six segments.
Y (Output value: Engineering unit data of CPV)

6
5
4

X (Input value: Engineering unit data)

D021904E.ai

Figure Example of a Variable Line-Segment Function with Six segments

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.19 Variable Line-Segment Function Block (FUNC-VAR)> D2-84

n CPV Pushback
The CPV pushback is a function used to prevent a sudden change in an output value to the
process control output when the status of a cascade connection is changed from open to close.
If the FUNC-VAR block is connected by means of cascade connection and the cascade
connection is opened, the calculation input value (RV) is calculated back based on a calculation
output value (CPV) obtained from a downstream function block via tracking, thereby making the
upstream function block track the value.
The CPV pushback operates only when the output value tracking is set to [Yes].

In the CPV pushback of the FUNC-VAR block, the value RV is obtained by calculating the x-axis
coordinate while using the value obtained by dividing CPV by GAIN as the input on the y-axis.
If GAIN is 0, the CPV pushback calculation is bypassed and the calculation input value (RV)
retains the previous value.

SEE
ALSO For details on the CPV pushback, see the following:
C4.11, “CPV Pushback”

n Data Items – FUNC-VAR

Table Data Items of Variable Line-Segment Function Block (FUNK-VAR)
Data Entry Permitted
Data Name Range Default
Item or Not
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
RV Calculated input value ----- 0
RAW Raw input data Value in the unit at the connection destination -----
CPV Calculated output value Δ (*1) CPV engineering unit value SL
7 - digit real number including sign and decimal
GAIN Gain x 1.00
point
SECT Number of segments x 1 to 14 1
X01 to X15 X-axis line-segment breakpont x ----- -----
Y01 to Y15 Y-axis line-segment breakpont x ----- -----
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
SH CPV scale high limit Value in the same engineering unit as CPV -----
SL CPV scale low limit Value in the same engineering unit as CPV -----
D021905E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for FUNC-VAR block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.20 Temperature and Pressure Correction Block (TPCFL)> D2-85

D2.20 Temperature and Pressure Correction Block

(TPCFL)
The Temperature and Pressure Correction Block (TPCFL) are used to correct the flowrate
measured by a differential pressure flowmeter on the basis of temperature and pressure.

n Temperature and Pressure Correction Block (TPCFL)

▼ Connection
The Temperature and Pressure Correction Block (TPCFL) are used to correct the flowrate, that
measured by a differential pressure flowmeter, of a gas relative to the ideal gas on the basis of
temperature and pressure.
Here is a function block diagram of the Temperature and Pressure Correction Block (TPCFL).

Input
IN processing RV

Correction
Q01 TMP CPV OUT
computation

Q02 PRS
(CPV, ∆CPV)

SUB
D022001E.ai

Figure Function Block Diagram of Temperature and Pressure Correction Block (TPCFL)

The following table shows the connection types and connection destinations of the I/O terminals
of the Temperature and Pressure Correction Block (TPCFL).
Table Connection Types and Connection Destinations of the I/O Terminals of Temperature and
Pressure Correction Block (TPCFL).
Connection type Connection destination
I/O terminal
Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
Measured Δ
IN x x x
flowrate
Measured Δ
Q01 x x x
temperature
Measured Δ
Q02 x x x
pressure
Calculation
OUT x x x x
output
Auxiliary x Δ x x
SUB
output
D022002E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.20 Temperature and Pressure Correction Block (TPCFL)> D2-86

n Function of Temperature and Pressure Correction Block (TPCFL)

The TPCFL block performs input processing, calculation processing, output processing, and
alarm processing.
The only processing timing available for the TPCFL block is a periodic startup. Selections
available for the scan period used to execute a periodic startup include the basic scan period, the
medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the TPCFL block,
see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of Temperature and Pressure Correction Block

(TPCFL)
The TPCFL block performs computation using its calculation algorithm and setup parameters.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.20 Temperature and Pressure Correction Block (TPCFL)> D2-87

n Calculation Algorithm
▼ Corrective Computation
The Temperature and Pressure Correction Block (TPCFL) correct the flowrate of a gas relative to
an ideal gas on the basis of temperature and pressure.
The following three types of correction computation algorithms are available:
• Temperature and pressure correction computations
• Temperature correction computation
• Pressure correction computation

Both the input and the output of the correction computation are floating-point data.
The calculated output value (CPV) is the corrected flowrate (F0) multiplied by the gain (GAIN).

CPV = GAIN • F0

l Temperature and Pressure Computation

In a temperature and pressure computation, correction computations of both temperature and
pressure are performed. The following is a correction computation expression with the measured
flowrate of Fi, reference pressure of Pb, reference temperature of Tb, measured pressure of P, and
when the pressure unit of the measured temperature T is [kPa].

P+1.01325 • 102 Tb+273.15 Pressure: kPa

F0= • • Fi
Pb+1.01325 • 102 T+273.15 Temperature: °C
D022003E.ai

Fi : Measured flowrate
F0 : Corrected flowrate
P : Measured pressure [kPa]
Pb : Reference pressure [kPa]
T : Measured temperature (°C)
Tb : Reference temperature (°C)

With the pressure unit of kgf/cm2 and the temperature unit of °F, the expression is given below.

P+1.0332 T'b+273.15 Pressure: kgf/cm2

F0= • Fi
Pb+1.0332 T'+273.15 Temperature: °F

5 5
T'= (T -32) T'b= (Tb-32)
9 9
D022004E.ai

Fi : Measured flowrate
P : Measured pressure [kgf/cm2]
T : Measured temperature (°F)
F0 : Corrected flowrate
Pb : Reference pressure [kgf/cm2]
Tb : Reference temperature (°F)

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.20 Temperature and Pressure Correction Block (TPCFL)> D2-88
l Temperature Correction Computation
In temperature correction computation, only a correction computation of temperature is
performed with the measured flowrate of Fi, reference temperature of Tb, and measured
temperature of T. A correction computation expression is shown below.

Tb+273.15
F0= • Fi [Temperature: °C]
T+273.15
D022005E.ai

Fi : Measured flowrate
F0 : Corrected flowrate
T : Measured temperature (°C)
Tb : Reference temperature (°C)

The formula for corrective calculation at the temperature unit °F is given below.

T'b+273.15
F0= Fi
T'+273.15
D022006E.ai

5 5
T'= (T-32) T'b= (Tb-32)
9 9
D022011E.ai

l Pressure Correction Computation

In pressure correction computation, only a correction computation of pressure is performed
with the measured flowrate of Fi, reference pressure of Pb, and measured pressure of P. The
correction computation expression is as follows when the pressure unit is [kPa].

P+1.01325 • 102
F0= • Fi [Pressure: kPa]
Pb+1.01325 • 102
D022007E.ai

Fi : Measured flowrate
F0 : Corrected flowrate
P : Measured pressure [kPa]
Pb : Reference pressure [kPa]

The expression for corrective calculation at the pressure unit kgf/cm2 is given below.

P+1.0332
F0= Fi
Pb+1.0332
D022008E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.20 Temperature and Pressure Correction Block (TPCFL)> D2-89

n Set Parameters
▼ Pressure Unit, Temperature Unit
The parameters of the Temperature and Pressure Correction Block (TPCFL) are shown as
follows.
• Reference temperature (TB):
Depends on the temperature unit specified in the builder. Degree C or F.
• Reference pressure (PB):
Depends on the unit specified in the builder.
• Gain (GAIN):
A numeric value of 7 digits or less including the sign and decimal point.
The default is 1.00.

“Correction computation,” “temperature unit” and “pressure unit” are set in the
Function Block Detail Builder.
• Corrective Computation:
Select from “Temperature and Pressure Correction,” “Pressure Correction,” and
“Temperature Correction.”
The default is “Temperature Correction.”
• Temperature Units:
Only Deg. C may be selected from the list. If use Fahrenheit degree, F may be manually
entered in the entry box.
• Pressure Units:
Select from “Pa,” “kPa,” and “MPa.”
The default is “kPa.”
If use kgf/cm2, KGF/CM2 may be manually entered in the entry box.

TIP
Only F can be manually entered in the temperature’s entry box, and only KGF/CM2 can be entered in the
pressure entry box. Entering other unit or strings may generated entry error.

Pjt:MYPJT Stn:FCS0101 Draw:DR0001 File:TPCFL1.edf-...

Pressure Alarm Control Calculation Output
Unit
3: kPa
2: Pa Pressure Unit KGF/CM2
4: MPa
Temperature Unit F

D022009E.ai

Figure Example of Manually Entry of F and KGF/CM2

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.20 Temperature and Pressure Correction Block (TPCFL)> D2-90

n Data Items – TPCFL

Table Data Items of Temperature and Pressure Correction Block (TPCFL)
Data Entry Permitted
Data Name Range Default
Item or Not
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
RV Measured flowrate ----- 0
RAW Raw input data Value in the unit at the connection destination -----
TMP Measured temperature ----- 0
RAW1 Raw input data Value in the unit at the connection destination -----
PRS Measured pressure ----- 0
RAW2 Raw input data Value in the unit at the connection destination -----
CPV Calculated output value Δ (*1) CPV engineering unit value SL
TB Reference temperature x ----- 0
PB Reference pressure x ----- 0
GAIN Gain x 7 - digit real number including sign and decimal point 1.00
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
SH CPV scale high limit Value in the same engineering unit as CPV -----
SL CPV scale low limit Value in the same engineering unit as CPV -----
D022010E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for TPCFL block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.21 ASTM Correction Block : Old JIS (ASTM1)> D2-91

D2.21 ASTM Correction Block : Old JIS (ASTM1)

The ASTM Correction Block: Old JIS (ASTM1) is used when performing correction
computation based on the ASTM correction (old JIS).

n ASTM Correction Block : Old JIS (ASTM1)

▼ Connection
The ASTM Correction Block: Old JIS (ASTM1) performs correction computation on the flowrate
of crude oil and petroleum products based on the ASTM correction (Old JIS) based on the
measured temperature and specific gravity.
Here is a function block diagram of the ASTM Correction Block: Old JIS (ASTM1).

Input
IN RV
processing

Correction
CPV OUT
computation

Q01 TMP
(CPV, ∆CPV)

SUB
D022101E.ai

Figure Function Block Diagram of ASTM Correction Block : Old JIS (ASTM1)

The following table shows the connection types and connection destinations of the I/O terminals
of the ASTM Correction Block: Old JIS (ASTM1).
Table Connection Types and Connection Destinations of the I/O Terminals of ASTM Correction Block :
Old JIS (ASTM1)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
Measured Δ
IN x x x
flowrate
Measured Δ
Q01 x x x
temperature
Calculation
OUT x x x x
output
Auxiliary Δ
SUB x x x
output
D022102E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.21 ASTM Correction Block : Old JIS (ASTM1)> D2-92

n Function of ASTM Correction Block : Old JIS (ASTM1)

The ASTM1 block performs input processing, calculation processing, output processing, and
alarm processing.
The only processing timing available for the ASTM1 block is a periodic startup. Selections
available for the scan period used to execute a periodic startup include the basic scan period, the
medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the ASTM1 block,
see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of ASTM Correction Block : Old JIS (ASTM1)

The ASTM1 block performs computation using its calculation algorithm and setup parameters.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.21 ASTM Correction Block : Old JIS (ASTM1)> D2-93

n Calculation Algorithm
▼ Temperature Unit
The ASTM Correction Block: Old JIS (ASTM1) performs temperature correction computation
of flowrates at the measured temperature of t and specific gravity of c, based on the ASTM
correction computation (Old JIS).
In a specific gravity range not shown in the ASTM table for the ASTM correction computation
(Old JIS), the same computation can be performed by extending the applicability to Table II of JIS
K2249.
The specific gravity ranges and temperature range of the ASTM and Table II of JIS K2249 are
shown below.

-25 °C 1.100
1.1
Old JIS
1
125 °C 0.960
0.9
100 °C 0.870
75 °C 0.840
Specific gravity 0.8 Old JIS & ASTM
at 15/4 °C (C1)
0.7

-46 °C 60 °C
0.6 0.600
Old JIS
55 °C 0.510
0.5

-50 0 50 100 150 200

Temperature (°C) D022103E.ai

Figure Specific Gravity Ranges and Temperature Ranges of the ASTM Correction Computation (Old JIS)
and Table II of JIS K2249 (Old JIS)

ASTM correction computation under the old JIS is shown below.

F0 = Cf • Fi

Cf = 1 + α (TMP-15) + β (TMP-15)2
-P1 (TMP) -P3 (TMP)
α= + P2 (TMP) , β = + P4 (TMP)
C1 C1
D022104E.ai

Fi : Measured flowrate
F0 : Corrected flowrate
TMP : Measured temperature (°C)
C1 : Specific gravity (15/4 °C)
P1 (TPM) to P4 (TPM): Parameters determined by temperature

The calculated output value (CPV) is the corrected flowrate (F0) multiplied by the gain (GAIN).

CPV = GAIN • F0

The temperature unit is specified in the Function Block Detail Builder.

• Temperature Units:
Deg. C
Only Deg. C may be selected from the list. If use Fahrenheit degree, F may be manually
entered in the entry box.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.21 ASTM Correction Block : Old JIS (ASTM1)> D2-94

n Set Parameters
The parameters of the ASTM Correction Block: Old JIS (ASTM1) are shown as follows.
• Specific gravity at 15/4 °C (DEN):
Set within the specific gravity range shown in Table II of JIS K2249.
• Gain (GAIN):
A numeric value of 7 digits or less including the sign and decimal point.
The default is 1.00.

n Data Items – ASTM1

Table Data Items of ASTM Correction Block : Old JIS (ASTM1)
Data Entry Permitted
Data Name Range Default
Item or Not
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
RV Measured flowrate ----- 0
RAW Raw input data Value in the unit at the connection destination -----
TMP Measured temperature ----- 0
RAW1 Raw input data Value in the unit at the connection destination -----
CPV Calculated output value Δ (*1) CPV engineering unit value SL
DEN Specific gravity x ----- 0
GAIN Gain x 7 - digit real number including sign and decimal point 1.00
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
SH CPV scale high limit Value in the same engineering unit as CPV -----
SL CPV scale low limit Value in the same engineering unit as CPV -----
D022105E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for ASTM1 block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.22 ASTM Correction Block : New JIS (ASTM2)> D2-95

D2.22 ASTM Correction Block : New JIS (ASTM2)

The ASTM Correction Block: New JIS (ASTM2) is used when performing correction
computation based on the ASTM correction (new JIS).

n ASTM Correction Block : New JIS (ASTM2)

▼ Connection
The ASTM Correction Block: New JIS (ASTM2) performs correction computation on the flowrate
of crude oil and petroleum products based on the ASTM correction (New JIS) based on the
measured temperature and specific gravity.
Here is a function block diagram of the ASTM Correction Block: New JIS (ASTM2).

Input
IN RV
processing

Correction
CPV OUT
computation

Q01 TMP
(CPV, ∆CPV)

SUB
D022201E.ai

Figure Function Block Diagram of ASTM Correction Block: New JIS (ASTM2)

The following table shows the connection types and connection destinations of the I/O terminals
of the ASTM Correction Block: New JIS (ASTM2).
Table Connection Types and Connection Destinations of the I/O Terminals of ASTM Correction Block:
NEW JIS (ASTM2)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
Measured Δ
IN x x x
flowrate
Measured Δ
Q01 x x x
temperature
Calculation
OUT x x x x
output
Auxiliary Δ
SUB x x x
output
D022202E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.22 ASTM Correction Block : New JIS (ASTM2)> D2-96

n Function of ASTM Correction Block : New JIS (ASTM2)

The ASTM2 block performs input processing, calculation processing, output processing, and
alarm processing.
The only processing timing available for the ASTM2 block is a periodic startup. Selections
available for the scan period used to execute a periodic startup include the basic scan period, the
medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the ASTM2 block,
see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of ASTM Correction Block : New JIS (ASTM2)

The ASTM2 block performs computation using its calculation algorithm and setup parameters.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.22 ASTM Correction Block : New JIS (ASTM2)> D2-97

n Calculation Algorithm
▼ Type of Oil, Temperature Unit
The ASTM Correction Block: New JIS (ASTM2) calculates the corrected flowrate of the flowrate
F at the measured temperature of t and density of p, based on the ASTM correction computation
(New JIS).
ASTM correction computation based on the new JIS is shown below.

F0 = Cf • Fi

Cf = exp {-α (TMP - 15) - 0.8α2 (TMP - 15)2}

K0 K1 B
α= + or α = A +
ρ2
ρ ρ2
D022203E.ai

F0 : Corrected flowrate
TMP : Measured temperature (°C)
ρ : Density at 15 °C (kg/m3)
Fi : Measured flowrate
K0, K1, A, B : Oil dependent constants

The specific correction computation under the ASTM correction (New JIS) varies depending
upon the type of oil used. Select appropriate constants from the table below.
Table Types of Oil and Oil Dependent Constants
Constants
Type of oil Density range at 15kg/m3
K0 K1 A B
Crude oil 610.5 ≤ ρ ≤ 1075.0 613.9723 0.0
653.0 ≤ ρ < 770.25 346.4228 0.4388
770.25 ≤ ρ < 787.75 -0.00336312 2680.3206
Fuel oil
787.75 ≤ ρ < 838.75 594.5418 0.0
838.75 ≤ ρ ≤ 1075.0 186.9696 0.4862
Lubricating oil 800.0 ≤ ρ ≤ 1164.0 0.0 0.6278
D022204E.ai

The calculated output value (CPV) is the corrected flowrate (F0) multiplied by the gain (GAIN).

CPV = GAIN • F 0

The “type of oil” and “temperature unit” are set on the Function Block Detail Builder.
• Type of Oil:
Select from “Crude,” “Fuel Oil” and “Lubricant.”
• Temperature Units:
Deg. C
Only Deg. C may be selected from the list. If use Fahrenheit degree, F may be manually
entered in the entry box.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.22 ASTM Correction Block : New JIS (ASTM2)> D2-98

n Set Parameters
The parameters of the ASTM Correction Block: New JIS (ASTM2) are shown as follows.
• Density at 15 °C (DEN):
Data with the unit of kg/m3.
• Gain (GAIN):
An actual quantity value of 7 digits or less including the sign and decimal point.

n Data Items – ASTM2

Table Data Items of ASTM Correction Block : New JIS (ASTM2)
Data Entry Permitted
Data Name Range Default
Item or Not
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
RV Measured flowrate ----- 0
RAW Raw input data Value in the unit at the connection destination -----
TMP Measured temperature ----- 0
RAW1 Raw input data Value in the unit at the connection destination -----
CPV Calculated output value Δ (*1) CPV engineering unit value SL
DEN Density x ----- 0
GAIN Gain x 7 - digit real number including sign and decimal point 1.00
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
SH CPV scale high limit Value in the same engineering unit as CPV -----
SL CPV scale low limit Value in the same engineering unit as CPV -----
D022205E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for ASTM2 block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.23 Logical AND Block (AND), Logical OR Block (OR)> D2-99

D2.23 Logical AND Block (AND), Logical OR Block

(OR)
AND block (*1) is used to calculated the product of RV1 and RV2. OR block (*1) is used to
calculate the sum of RV1 and RV2.
*1: AND and OR blocks can be used in FCSs except PFCS.

n Logical AND Block (AND), Logical OR Block (OR)

▼ Connection
AND is the function block to be used to calculate the product of RV1 and RV2 and OR is the
function block to be used to calculate the sum of RV1 and RV2.
Here is a function block diagram of Logical AND Block (AND) and Logical OR Block (OR).

Input
Q01 RV1
Processing
Calculation Output
CPV OUT
Processing Processing
Input
Q02 RV2
Processing

D022301E.ai

Figure Function Block Diagram of Logical AND Block (AND) and Logical OR Block (OR)

The following table shows the connection types and connection destinations of the I/O terminals
of Logical AND Block (AND) and Logical OR Block (OR).
Table Connection Types and Connection Destinations of I/O Terminals of Logical AND Block (AND) and
Logical OR Block (OR)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
Calculation Δ
Q01 x x x x x
input 1
Calculation Δ
Q02 x x x x x
input 2
Calculation x x Δ x x x
OUT
output
D022302E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.23 Logical AND Block (AND), Logical OR Block (OR)> D2-100

n Functions of Logical AND Block (AND) and Logical OR Block (OR)

The AND and OR blocks perform input processing, calculation processing, output processing,
and alarm processing.
The processing timings available for the AND and OR blocks are a periodic startup and a one-
shot startup. Selections available for the scan period used to execute a periodic startup include
the basic scan period, the medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the AND and OR
blocks, see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of Logical AND Block (AND) and Logical OR Block

(OR)
The AND block calculates the logic product of the calculation input values (RV1, RV2) using its
calculation algorithm. The OR block calculates the logic sum of the calculation input values (RV1,
RV2) using its calculation algorithm.

n Calculation Algorithm
The calculated output value (CPV) and the calculated input value (RV1, RV2) have the following
relationship.
Table Relationship of Input and Output of Logical AND Block (AND)
RV1 0 0 ≠0 ≠0
RV2 0 ≠0 0 ≠0
CPV 0 0 0 1
D022303E.ai

Table Relationship of Input and Output of Logical OR Block (OR)

RV1 0 0 ≠0 ≠0
RV2 0 ≠0 0 ≠0
CPV 0 1 1 1
D022304E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.23 Logical AND Block (AND), Logical OR Block (OR)> D2-101

n Data Items – AND and OR

Table Data Items of Logical AND Block (AND), Logical OR Block (OR)
Entry
Data Data Name Range Default
Permission
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
RV1 Calculation input value 1 0
RV2 Calculation input value 2 0
CPV Calculated output value Δ (*1) 0, 1 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D022305E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for AND and OR blocks, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.24 Logical NOT Block (NOT)> D2-102

D2.24 Logical NOT Block (NOT)

NOT block (*1) is used to perform the negation calculation.
*1: NOT block can be used in FCSs except PFCS.

n Logical NOT Block (NOT)

▼ Connection
NOT is the function block to be used to calculate the negation of the calculated input value (RV).
Here is a function block diagram of Logical NOT Block (NOT).

Input Calculation Output

IN RV CPV OUT
Processing Processing Processing

D022401E.ai

Figure Function Block Diagram of Logical NOT Block (NOT)

The following table shows the connection types and connection destinations of the I/O terminals
of Logical NOT Block (NOT).
Table Connection Types and Connection Destinations of I/O Terminals of Logical NOT Block (NOT)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
Calculation x x Δ x x x
IN
input
Calculation
OUT x x Δ x x x
output
D022402E.ai

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

n Function of Logical NOT Block (NOT)

The NOT block performs input processing, calculation processing, output processing, and alarm
processing.
The processing timings available for the NOT block are a periodic startup and a one-shot startup.
Selections available for the scan period used to execute a periodic startup include the basic scan
period, the medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the NOT block, see
the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.24 Logical NOT Block (NOT)> D2-103
l Calculation Processing of Negative Block (NOT)
The NOT block performs a negative operation on the calculation input value (RV) using its
calculation algorithm.

n Calculation Algorithm
The calculated output value (CPV) and the calculated input value (RV) have the following
relationship.
Table Relationship of Input and Output of Logical NOT Block (NOT)
RV 0 ≠0
CPV 1 0
D022403E.ai

n Data Items – NOT

Table Data Items of Logical NOT Block (NOT)
Entry
Data Data Name Range Default
Permission
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
RV Calculation input value 0
CPV Calculated output value Δ (*1) 0, 1 SL
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D022404E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for NOT block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.25 Flip-Flop Blocks (SRS1-S, SRS1-R, SRS2-S, SRS2-R)> D2-104

D2.25 Flip-Flop Blocks (SRS1-S, SRS1-R, SRS2-S,

SRS2-R)
SRS1-S, SRS1-R, SRS2-S and SRS2-R blocks (*1) are the function blocks used for flip-flop
operations.
*1: SRS1-S, SRS1-R, SRS2-S and SRS2-R blocks can be used in FCSs except PFCS.

n Flip-Flop Blocks (SRS1-S, SRS1-R, SRS2-S, SRS2-R)

▼ Connection
SRS1-S, SRS1-R, SRS2-S and SRS2-R blocks are the function blocks give the flip-flop
operation output CPV according the calculated input value of RV1 and RV2. SRS1-S, SRS1-R,
SRS2-S and SRS2-R blocks are classified as follows.
• Set-Dominant Flip-Flop Block with 1 Output (SRS1-S)
• Reset-Dominant Flip-Flop Block with 1 Output (SRS1-R)
• Set-Dominant Flip-Flop Block with 2 Outputs (SRS2-S)
• Reset-Dominant Flip-Flop Block with 2 Outputs (SRS2-R)

Input Output
Q01 RV1 CPV1 J01
Processing Processing
Calculation
Processing
Input
Q02 RV2
Processing

SRS1-S and SRS1-R

Input
Q01 RV1 CPV1 J01
Processing
Calculation Output
Processing Processing
Input
Q02 Processing RV2 CPV2 J02

SRS2-S and SRS2-R

D022501E.ai

Figure Function Block Diagram of SRS1-S, SRS1-R, SRS2-S and SRS2-R Blocks

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.25 Flip-Flop Blocks (SRS1-S, SRS1-R, SRS2-S, SRS2-R)> D2-105
The following table shows the connection types and connection destinations of the I/O terminals
of SRS1-S, SRS1-R, SRS2-S and SRS2-R blocks.
Table Connection Types and Connection Destinations of the I/O Terminals of SRS1-S, SRS1-R, SRS2-S
and SRS2-R Blocks
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
Calculation Δ
Q01 x x x x x
input 1
Calculation Δ
Q02 x x x x x
input 2
Calculation Δ
J01 x x x x x
output 1
Calculation x x Δ x x x
J02
output 2
D022502E.ai

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

n Functions of Flip-Flop Blocks (SRS1-S, SRS1-R, SRS2-S, SRS2-R)

The SRS1-S, SRS1-R, SRS2-S, and SRS2-R blocks perform input processing, calculation
processing, output processing, and alarm processing.
The processing timings available for the SRS1-S, SRS1-R, SRS2-S, and SRS2-R blocks are a
periodic startup and a one-shot startup. Selections available for the scan period used to execute
a periodic startup include the basic scan period, the medium-speed scan period (*1), and the
high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the SRS1-S, SRS1-
R, SRS2-S, and SRS2-R blocks, see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of Flip-Flop Blocks (SRS1-S, SRS1-R, SRS2-S, SRS2-R)

The SRS1-S, SRS1-R, SRS2-S, and SRS2-R blocks perform a flip-flop operation using their
calculation algorithms.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.25 Flip-Flop Blocks (SRS1-S, SRS1-R, SRS2-S, SRS2-R)> D2-106

n Calculation Algorithm
The calculated output value (CPV) and the calculated input value (RV1, RV2) have the following
relationship.
Table Relationship of Input and Output of Set-Dominant Flip-Flop Block with 1 Output (SRS1-S)
RV1 0 ≠0 0 ≠0
Input
RV2 0 0 ≠0 ≠0
CPV1 Hold 1 0 1
Output
- - - - -
D022503E.ai

Table Relationship of Input and Output of Reset-Dominant Flip-Flop Block with 1 Output (SRS1-R)
RV1 0 ≠0 0 ≠0
Input
RV2 0 0 ≠0 ≠0
CPV1 Hold 1 0 0
Output
- - - - -
D022504E.ai

Table Relationship of Input and Output of Set-Dominant Flip-Flop Block with 2 Outputs (SRS2-S)
RV1 0 ≠0 0 ≠0
Input
RV2 0 0 ≠0 ≠0
CPV1 Hold 1 0 1
Output
CPV2 Hold 0 1 0
D022505E.ai

Table Relationship of Input and Output of Reset-Dominant Flip-Flop Block with 2 Outputs
(SRS2-R)
RV1 0 ≠0 0 ≠0
Input
RV2 0 0 ≠0 ≠0
CPV1 Hold 1 0 0
Output
CPV2 Hold 0 1 1
D022506E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.25 Flip-Flop Blocks (SRS1-S, SRS1-R, SRS2-S, SRS2-R)> D2-107

n Data Items – SRS1-S, SRS1-R, SRS2-S, SRS2-R

Table Data Items of SRS1-S, SRS1-R, SRS2-S, SRS2-R flip-flop blocks
Entry
Data Data Name Range Default
Permission
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
RV1 Calculation input value1 0

RV2 Calculation input value2 0

CPV1 Calculated output value1 Δ (*1) 0, 1 0
CPV2 Calculated output value2 0, 1 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D022507E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for SRS1-S, SRS1-R, SRS2-S and SRS2-R blocks, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.26 Wipeout Block (WOUT)> D2-108

D2.26 Wipeout Block (WOUT)

The WOUT block (*1) is used for the logical operation to output the AND of the calculation
input value1 (RV1) and the NOT of the calculation input value2 (RV2).
*1: WOUT block can be used in FCSs except PFCS.

n Wipeout Block (WOUT)

▼ Connection
The WOUT block is the function block to be used for the logical operation to output the AND of
the calculation input value1 (RV1) and the NOT of the calculation input value2 (RV2).
Here is a function block diagram of Wipeout Block (WOUT).

Input
Q01 RV1
Processing
Calculation Output
CPV OUT
Processing Processing
Input
Q02 RV2
Processing

D022601E.ai

Figure Function Block Diagram of Wipeout Block (WOUT)

The following table shows the connection types and connection destinations of the I/O terminals
of Wipeout Block (WOUT).
Table Connection Types and Connection Destinations of the I/O Terminals of Wipeout Block (WOUT)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
Calculation Δ
Q01 x x x x x
input 1
Calculation Δ
Q02 x x x x x
input 2
Calculation x x x x x x
OUT
output
D022602E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.26 Wipeout Block (WOUT)> D2-109

n Function of Wipeout Block (WOUT)

The WOUT block performs input processing, calculation processing, output processing, and
alarm processing.
The processing timings available for the WOUT block are a periodic startup and a one-shot
startup. Selections available for the scan period used to execute a periodic startup include the
basic scan period, the medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the WOUT block,
see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of Wipeout Block (WOUT)

The WOUT block performs computation using its calculation algorithm.

n Calculation Algorithm
The calculated output value (CPV) and the calculation input value (RV1, RV2) have the following
relationship.
Table Relationship of Input and Output of Wipeout Block (WOUT)
RV1 0 ≠0 0 ≠0
Input
RV2 0 0 ≠0 ≠0
Output CPV 0 1 0 0
D022603E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.26 Wipeout Block (WOUT)> D2-110

n Data Items – WOUT

Table Data Items of Wipeout Block (WOUT)
Entry
Data Data Name Range Default
Permission
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
RV1 Calculation input value1 0
RV2 Calculation input value2 0
CPV Calculated output value Δ (*1) 0, 1 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D022604E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for WOUT block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.27 ON-Delay Timer Block (OND)> D2-111

D2.27 ON-Delay Timer Block (OND)

OND block (*1) is used for the operation to output the logic value 1 as calculated output
value (CPV) when the pre-defined time elapsed after the calculation input value (RV) is
changed to a value other than 0.
*1: OND block can be used in FCSs except PFCS.

n ON-Delay Timer Block (OND)

▼ Connection
OND block is used for the operation to output the logic value 1 when the pre-defined time
elapsed after the calculation input RV is changed to a value other than 0.
The calculated output value (CPV) is 0 when the calculation input value (RV) is 0.
Here is a function block diagram of ON-Delay Timer Block (OND).

Input Calculation Output

IN RV CPV OUT
Processing Processing Processing

D022701E.ai

Figure Function Block Diagram of ON-Delay Timer Block (OND)

The following table shows the connection types and connection destinations of the I/O terminals
of ON-Delay Timer Block (OND).
Table Connection Types and Connection Destinations of the I/O Terminals of ON-Delay Timer Block
(OND)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
Calculation Δ
IN x x x x x
input
Calculation
OUT x x Δ x x x
output
D022702E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.27 ON-Delay Timer Block (OND)> D2-112

n Function of ON-Delay Timer Block (OND)

The OND block performs input processing, calculation processing, output processing, and alarm
processing.
The only processing timing available for the OND block is a periodic startup. Selections available
for the scan period used to execute a periodic startup include the basic scan period, the medium-
speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the OND block, see
the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of ON-Delay Timer Block (OND)

The OND block sets the calculation output value (CPV) to 1 after the pre-defined time (STM) has
elapsed using its calculation algorithm and setup parameters.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.27 ON-Delay Timer Block (OND)> D2-113

n Calculation Algorithm
▼ Time Unit
The calculation algorithm of ON-Delay Timer Block may be illustrated as follows.
• The timer is initiated when the calculation input value (RV) is changed to a value other than 0.
• When timer is running, the current elapsed time (PTM) displays.
• When pre-defined time (STM) elapsed, the calculated output value (CPV) changes from 0 to 1.
• When the calculation input value (RV) changes to 0, the calculated output value (CPV) is
reset to 0.

≠0

RV

0
t
STM Timer start Timer reset
t<STM
1

CPV

D022703E.ai

Figure ON-Delay Timer Block (OND) Calculation Algorithm

The time unit of the timer block may be set on the Function Block Detail Builder.
• Time Unit:
Select between “Second” and “Minute.”
The default is “Second.”

n Setting Parameter
OND block has the following setting parameters.
• Set Time (STM):
1 to 10000

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.27 ON-Delay Timer Block (OND)> D2-114

n Data Items – OND

Table Data Items of ON-Delay Timer Block (OND)
Entry
Data Data Name Range Default
Permission
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
RV Calculation input value 0
CPV Calculated output value Δ (*1) 0, 1 0
STM Pre-defined time x 1 to 10000 1
PTM Elapsed time 0 to 10000 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D022704E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for OND block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.28 OFF-Delay Timer Block (OFFD)> D2-115

D2.28 OFF-Delay Timer Block (OFFD)

OFFD block (*1) is used for the operation to output the logic value 0 as calculated output
value (CPV) when the pre-defined time elapsed after the calculation input value (RV) is
changed to 0.
*1: OFFD block can be used in FCSs except PFCS.

n OFF-Delay Timer Block (OFFD)

▼ Connection
OFFD block is used for the operation to output the logic value 0 when the pre-defined time (STM)
elapsed after the calculation input RV is changed from 1 to 0.
Here is a function block diagram of OFF-Delay Timer Block (OFFD).

Input Calculation Output

IN RV CPV OUT
Processing Processing Processing

D022801E.ai

Figure Function Block Diagram of OFF-Delay Timer Block (OFFD)

The following table shows the connection types and connection destinations of the I/O terminals
of OFF-Delay Timer Block (OFFD).
Table Connection Types and Connection Destinations of the I/O Terminals of OFF-Delay Timer Block
(OFFD)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
Calculation x x Δ x x x
IN
input
Calculation
OUT x x Δ x x x
output
D022802E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.28 OFF-Delay Timer Block (OFFD)> D2-116

n Function of Off-Delay Timer Block (OFFD)

The OFFD block performs input processing, calculation processing, output processing, and
alarm processing.
The only processing timing available for the OFFD block is a periodic startup. Selections
available for the scan period used to execute a periodic startup include the basic scan period, the
medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the OFFD block,
see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of Off-Delay Timer Block (OFFD)

The OFFD block sets the calculation output value (CPV) to 0 after the pre-defined time (STM)
has elapsed using its calculation algorithm and setup parameters.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.28 OFF-Delay Timer Block (OFFD)> D2-117

n Calculation Algorithm
▼ Time Unit
The calculation algorithm of OFF-Delay Timer Block may be illustrated as follows.
• The timer is initiated when the calculation input value (RV) is changed to 0.
• When timer is running, the current elapsed time (PTM) displays.
• When pre-defined time (STM) elapsed, the calculated output value (CPV) changes from 1 to 0.
• When the calculation input value (RV) changes to a value other than 0, the calculated output
value (CPV) is reset to 1.

≠0

RV

0
t
STM
Timer start Timer reset
t<STM
1

CPV

D022803E.ai

Figure OFF-Delay Timer Block (OFFD) Calculation Algorithm

The time unit of the timer block may be set on the Function Block Detail Builder.
• Time Unit:
Select between “Second” and “Minute.”
The default is “Second.”

n Setting Parameter
OFFD timer block has the following setting parameters.
• Set Time (STM):
1 to 10000

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.28 OFF-Delay Timer Block (OFFD)> D2-118

n Data Items – OFFD

Table Data Items of OFF-Delay Timer Block (OFFD)
Entry
Data Data Name Range Default
Permission
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
RV Calculation input value 0
CPV Calculated output value Δ (*1) 0, 1 0
STM Pre-defined time x 1 to 10000 1
PTM Elapsed time 0 to 10000 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D022804E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for OFFD block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.29 One-Shot Blocks Rise Trigger (TON), Fall Trigger (TOFF)> D2-119

D2.29 One-Shot Blocks Rise Trigger (TON), Fall

Trigger (TOFF)
TON (*1) block is used for the operation to output the logic value 1 as calculated output
value (CPV) for one scan period when the calculation input value (RV) is changed to a
value other than 0.
TOFF block (*1) is used for the operation to output the logic value 1 for one scan period
when the calculation input value (RV) is changed to 0.
*1: TON and TOFF blocks can be used in FCSs except PFCS.

n One-Shot Blocks Rise Trigger (TON), Fall Trigger (TOFF)

▼ Connection
TON block and TOFF block are used for the operation to output the logic value 1 as calculated
output value (CPV) for one scan period when the calculation input value (RV) of TON block is
changed to a value other than 0, or the calculation input value (RV) of TOFF is changed to 0.
Otherwise, the calculated output value (CPV) is kept as 0.
Here is a function block diagram of One-shot blocks TON and TOFF.

Input Calculation Output

IN RV CPV OUT
Processing Processing Processing

D022901E.ai

Figure Function Block Diagram of One-shot Blocks TON and TOFF

The following table shows the connection types and connection destinations of the I/O terminals
of One-shot blocks TON and TOFF.
Table Connection Types and Connection Destinations of the I/O Terminals of One-shot Blocks TON
and TOFF
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
Calculation x x Δ x x x
IN
input
Calculation
OUT x x Δ x x x
output
D022902E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.29 One-Shot Blocks Rise Trigger (TON), Fall Trigger (TOFF)> D2-120

n Functions of One-Shot Block Rising-Edge Trigger (TON) and Falling-

Edge Trigger (TOFF)
The TON and TOFF blocks perform input processing, calculation processing, output processing,
and alarm processing.
The only processing timing available for the TON and TOFF blocks is a periodic startup.
Selections available for the scan period used to execute a periodic startup include the basic scan
period, the medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the TON and TOFF
blocks, see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of One-Shot Block Rising-Edge Trigger (TON) and

Falling-Edge Trigger (TOFF)
The TON and TOFF blocks set the calculation output value (CPV) to 1 for the duration of one
scan using their calculation algorithms.

n Calculation Algorithm
The calculation algorithm of One-shot blocks TON and TOFF may be illustrated as follows.

l One-Shot Block (Rising-Edge Trigger) (TON)

When the calculation input value (RV) is changed to a value other than 0, the logic value 1 is
output as calculated output value (CPV) for one scan period.

≠0

IN

OUT

1 Scan

One-shot
Rise trigger
D022903E.ai

Figure One-Shot Block (Rising-Edge Trigger) (TON)

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.29 One-Shot Blocks Rise Trigger (TON), Fall Trigger (TOFF)> D2-121
l One-Shot Block (Falling-Edge Trigger) (TOFF)
When the calculation input RV is changed from 1 to 0, the logic value 1 is output for one scan
period.

≠0

IN

OUT

1 Scan

One-shot
Fall trigger
D022904E.ai

Figure One-Shot Block (Falling-Edge Trigger) (TOFF)

n Data Items – TON and TOFF

Table Data Items of One-shot Blocks Rise Trigger (TON), Fall Trigger( TOFF)
Entry
Data Data Name Range Default
Permission
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
RV Calculation input value 0
CPV Calculated output value Δ (*1) 0, 1 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D022905E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for TON and TOFF blocks, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.30 Relational Operation Blocks (GT, GE, EQ)> D2-122

D2.30 Relational Operation Blocks (GT, GE, EQ)

GT, GE and EQ blocks (*1) are used to compare the two calculation input values RV1 and
RV2.
*1: GT, GE, and EQ blocks can be used in FCSs except PFCS.

n Relational Operation Blocks (GT, GE, EQ)

▼ Connection
GT, GE and EQ blocks are used to compare the two inputs (RV1, RV2). When the comparison
result is True, the calculated output value (CPV) becomes 1, otherwise the output value (CPV) is
0.
Here is a function block diagram of GT, GE and EQ.

Input
Q01 RV1
Processing
Calculation Output
CPV OUT
Processing Processing
Input
Q02 RV2
Processing

D023001E.ai

Figure Function Block Diagram of Relational Operation Blocks (GT, GE, EQ)

The following table shows the connection types and connection destinations of the I/O terminals
of Relational Operation Blocks (GT, GE, EQ).
Table Connection Types and Connection Destinations of the I/O Terminals of Relational Operation
Blocks (GT, GE, EQ)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
Calculation Δ
Q01 x x x
input 1
Calculation Δ
Q02 x x x
input 2
Calculation x x Δ x x x
OUT
output
D023002E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.30 Relational Operation Blocks (GT, GE, EQ)> D2-123

n Functions of Relational Operation Blocks (GT, GE, EQ)

The GT, GE, and EQ blocks perform input processing, calculation processing, output processing,
and alarm processing.
The processing timings available for the GT, GE, and EQ blocks are a periodic startup and a one-
shot startup. Selections available for the scan period used to execute a periodic startup include
the basic scan period, the medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the GT, GE, and
EQ blocks, see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS.”

l Calculation Processing of Relational Operation Blocks (GT, GE, EQ)

The GT, GE, and EQ blocks compare the calculation input values (RV1, RV2) using their
calculation algorithms.

n Calculation Algorithm
The calculation algorithm of GT, GE, EQ may be described as follows.

l Comparator Block (Greater Than) (GT)

The calculation input values (RV1, RV2) are the floating-point numeric data, while the calculated
output value (CPV) is integer.
When RV1 > RV2, the calculated output value (CPV) becomes 1, otherwise, it is 0.

l Comparator Block (Greater Than or Equal) (GE)

The calculation input values (RV1, RV2) are the floating-point numeric data, while the calculated
output value (CPV) is integer.
When RV1 ≥ RV2, the calculated output value (CPV) becomes 1, otherwise, it is 0.

l Equal Operator Block (EQ)

The calculation input values (RV1, RV2) are the floating-point numeric data, while the calculated
output value (CPV) is integer.
When RV1 = RV2, the calculated output value (CPV) becomes 1, otherwise, it is 0.
When the connection destination is engineering unit data, the comparison is carried out by
floating-point numeric values.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.30 Relational Operation Blocks (GT, GE, EQ)> D2-124

n Data Items – GT, GE, EQ

Table Data Items of Relational Operation Blocks (GT, GE, EQ)
Entry
Data Data Name Range Default
Permission
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- 0
AF Alarm detection specification ----- 0
AOFS Alarm masking specification ----- 0
RV1 Calculation input value 1 ----- 0
RV2 Calculation input value 2 ----- 0
CPV Calculated output value Δ (*1) 0, 1 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D023003E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for GT, GE and EQ blocks, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.31 Bitwise AND Block (BAND), Bitwise OR Block (BOR)> D2-125

D2.31 Bitwise AND Block (BAND), Bitwise OR

Block (BOR)
BAND block (*1) is used when the product of the calculation input values (RV1, RV2) is
calculated in bitwise.
BOR (*1) block is used when the sum of the calculation input values (RV1, RV2) is
calculated in bitwise.
*1: BAND and BOR blocks can be used in FCSs except PFCS.

n Bitwise AND Block (BAND), Bitwise OR Block (BOR)

▼ Connection
Based on the calculation input values (RV1, RV2), BAND Block calculates the bitwise product of
the two inputs while BOR block the bitwise sum of the two inputs.
Here is a function block diagram of Bitwise AND Block (BAND) and Bitwise OR Block (BOR).

Input
Q01 RV1
Processing
Calculation Output
CPV OUT
Processing Processing
Input
Q02 RV2
Processing

D023101E.ai

Figure Function Block Diagram of Bitwise AND Block (BAND) and Bitwise OR Block (BOR)

The following table shows the connection types and connection destinations of the I/O terminals
of Bitwise AND Block (BAND) and Bitwise OR Block (BOR).
Table Connection Types and Connection Destinations of the I/O Terminals of Bitwise AND Block
(BAND) and Bitwise OR Block (BOR)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
Calculation Δ
Q01 x x x
input 1
Calculation Δ
Q02 x x x
input 2
Calculation x Δ x x
OUT
output
D023102E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.31 Bitwise AND Block (BAND), Bitwise OR Block (BOR)> D2-126

n Functions of Bitwise AND Block (BAND) and Bitwise OR Block (BOR)

The BAND and BOR blocks perform input processing, calculation processing, output processing,
and alarm processing.
The processing timings available for the BAND and BOR blocks are a periodic startup and a one-
shot startup. Selections available for the scan period used to execute a periodic startup include
the basic scan period, the medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the BAND and
BOR blocks, see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of Bitwise AND Block (BAND) and Bitwise OR Block

(BOR)
The BAND and BOR blocks perform computation using their calculation algorithms.

n Calculation Algorithm
The I/O data of BAND and BOR blocks are integer type.
The calculation algorithm of BAND and BOR may be described as follows.

l Bitwise AND Block (BAND)

The bitwise product of calculation input values (RV1, RV2) is calculated.
Example

RV1 = 0xFFFF FF00, RV2 = 0x0000 0FFF

CPV = 0x0000 0F00

l Bitwise OR Block (BOR)

The bitwise sum of calculation input values (RV1, RV2) is calculated.
Example

RV1 = 0xFFFF FF00, RV2 = 0x0000 000F

CPV = 0xFFFF FF0F

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.31 Bitwise AND Block (BAND), Bitwise OR Block (BOR)> D2-127

n Data Items – BAND, BOR

Table Data Items of Bitwise AND Block (BAND) and Bitwise OR Block (BOR)
Entry
Data Data Name Range Default
Permission
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
RV1 Calculation input value 1 8 digits, hex 0
RV2 Calculation input value 2 8 digits, hex 0
CPV Calculated output value Δ (*1) 8 digits, hex 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D023103E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for BAND and BOR blocks, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.32 Bitwise NOT Block (BNOT)> D2-128

D2.32 Bitwise NOT Block (BNOT)

BNOT block (*1) is used when the negation of the calculation input values (RV1, RV2) is
calculated in bitwise.
*1: BNOT block can be used in FCSs except PFCS.

n Bitwise NOT Block (BNOT)

▼ Connection
Based on the calculation inputs (RV), BNOT block calculates the bitwise negation of the inputs.
Here is a function block diagram of Bitwise NOT Block (BNOT).

Input Calculation Output

IN RV CPV OUT
Processing Processing Processing

D023201E.ai

Figure Function Block Diagram of Bitwise NOT Block (BNOT)

The following table shows the connection types and connection destinations of the I/O terminals
of Bitwise NOT Block (BNOT).
Table Connection Types and Connection Destinations of the I/O Terminals of Bitwise NOT Block
(BNOT)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
Calculation x Δ x x
IN
input
Calculation
OUT x Δ x x
output
D023202E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.32 Bitwise NOT Block (BNOT)> D2-129

n Function of Bitwise NOT Block (BNOT)

The BNOT block performs input processing, calculation processing, output processing, and
alarm processing.
The processing timings available for the BNOT block are a periodic startup and a one-shot
startup. Selections available for the scan period used to execute a periodic startup include the
basic scan period, the medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the BNOT block,
see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of Bitwise NOT Block (BNOT)

The BNOT block performs computation using its calculation algorithm.

n Calculation Algorithm
The calculation input values (RV, CPV) of BNOT blocks is integer type.
The BNOT calculates its CPV according to the bitwise value of calculation input value (RV).
Example

RV = 0xFFFF FF00
CPV = 0x0000 00FF

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.32 Bitwise NOT Block (BNOT)> D2-130

n Data Items – BNOT

Table Data Items of Bitwise NOT Block (BNOT)
Entry
Data Data Name Range Default
Permission
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
RV Calculation input value 8 digits, hex 0
CPV Calculated output value Δ (*1) 8 digits, hex 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D023203E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for BNOT block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.33 General-Purpose Calculation Blocks (CALCU, CALCU-C)> D2-131

D2.33 General-Purpose Calculation Blocks

(CALCU, CALCU-C)
The General-Purpose Calculation Blocks (CALCU, CALCU-C) are used when defining
arbitrary calculation algorithms.

n General-Purpose Calculation Blocks (CALCU, CALCU-C)

▼ Connection
The General-Purpose Calculation Block (CALCU) is a function block that executes pre-defined
arbitrary calculation algorithms. Calculation algorithms are defined using the general-purpose
calculation expression description language.
The Calculation Block with String I/O (CALCU-C) has the same function as the General-Purpose
Calculation Block (CALCU), but the former has I/O terminals that can handle string data and a
part of the I/O data is used only for string data.
Here is a function block diagram of the General-Purpose Calculation Blocks (CALCU, CALCU-
C).

P01 P08

IN RV CPV OUT

User-defined
Q01 RV1 CPV1 Output J01
Input arithmetic/logic
processing calculation processing
processing

Q07 RV7 CPV3 J03

(CPV, ∆CPV)

SUB
D023301E.ai

Figure Function Block Diagram of General-Purpose Calculation Blocks (CALCU, CALCU-C)

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.33 General-Purpose Calculation Blocks (CALCU, CALCU-C)> D2-132
The following tables show the connection types and connection destinations of the I/O terminals
of General-Purpose Calculation Blocks (CALCU, CALCU-C).
Table Connection Types and Connection Destinations of the I/O Terminals of
General-Purpose Calculation Block (CALCU)
Connection type Connection destination
I/O terminal
Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
Calculation x x Δ x x x
IN
input
Q01 nth
to calculation x x Δ x x x
Q07 input
Calculation x x x x
OUT x x
output
J01 nth
to calculation x x Δ x x x
J03 output
Auxiliary Δ x x x
SUB x
output
D023302E.ai

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

Table Connection Types and Connection Destinations of the I/O Terminals of

General-Purpose Calculation Block with String I/O (CALCU-C)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
Calculation x Δ
IN x x x x
input
Q01 nth
to calculation x x Δ x x x
Q03 input
Q04 nth
to calculation x Δ x
Q07 input
Calculation
OUT x x x x x x
output
nth
J01 calculation x x Δ x x x
output
J02 nth
to calculation x Δ x
J03 output
Auxiliary Δ
SUB x x x x
output
D023303E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.33 General-Purpose Calculation Blocks (CALCU, CALCU-C)> D2-133

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

The CALCU and CALCU-C blocks perform input processing, calculation processing, output
processing, and alarm processing.
The processing timings available for the CALCU and CALCU-C blocks are a periodic startup and
a one-shot startup. Selections available for the scan period used to execute a periodic startup
include the basic scan period, the medium-speed scan period (*1), and the high-speed scan
period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the CALCU and
CALCU-C blocks, see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Input Processing of General-Purpose Calculation Blocks (CALCU, CALCU-C)

when a Calculation Input Value Error is Detected
The CALCU and CALCU-C blocks perform special input processing when an abnormal
calculation input value is detected.

l Exact Totalization Pulse Train Input of General-Purpose Calculation Blocks

(CALCU, CALCU-C)
When the input signal conversion is specified with [Exact Totalization Pulse Train Input], the
totalization can use the calculation output value (CPV).

l Calculation Processing of General-Purpose Calculation Blocks (CALCU,

CALCU-C)
The CALCU and CALCU-C blocks perform computation using arbitrarily defined calculation
algorithms and their setup parameters.

l Alarm Processing Specific to General-Purpose Calculation Blocks (CALCU,

CALCU-C)
The “calculation error alarm check,” which is one of the alarm checks performed by the CALCU
and CALCU-C blocks, is specific to these two function blocks.

l Calculation Output Value Range limit of General-Purpose Calculation Blocks

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D2.33 General-Purpose Calculation Blocks (CALCU, CALCU-C)> D2-134
l In/Out Data Normalization of General-Purpose Calculation Blocks (CALCU,
CALCU-C): KFCS2/LFCS2/FFCS
In CENTUM-XL system, the In/Out data of general-purpose calculation blocks are normalized
values. In CENTUM VP system, the In/Out data of general-purpose calculation blocks can be
either normalized values or engineering unit data values according to the designation on the
builder. Designating to use the normalized In/Out data of general-purpose calculation blocks can
retain consistency when migrating a CENTUM-XL calculations to CENTUM VP system.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.33 General-Purpose Calculation Blocks (CALCU, CALCU-C)> D2-135

n Input Processing when a Calculation Input Value Error is Detected

▼ Calculated Input Value Error Detected
Define the calculation value error detection condition of the CALCU and CALCU-C blocks and
the data status of the calculation output value (CPV) when an error is detected in “Calculation
input value error detection” of Function Block Detail Builder. By default, this setting is set as “0:
Non-Detecting Type.”
In connection with these settings, a method by which the data status (IOP, IOP-, OOP, NRDY)
related to the process control input/output generated with the calculation input values (RV, RVn)
is communicated to the calculation output value (CPV) will furthermore be determined. The data
status of the calculation output values (CPV1 to CPV3) is always NR (normal) regardless of the
setting in [Calculation Input Value Error Detection] item.
Table Specification of Calculation Input Value Error Detection of General-Purpose Calculation Blocks
(CALCU, CALCU-C)
Error detection condition
CPV data Input value of data status
Specification RV1 to RV7 Calculation
RV status communication source
(*2) processing
BAD – – BAD RV
Correction
NR (*1) BAD Normal QST
calculation type Do not communicate.
NR (*1) NR (*1) Normal NR (*1)
BAD – – BAD The priority order is from
Detect all type – BAD – BAD RV to RVn (*3).

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

Non-detection type – – Normal NR (*1) Do not communicate.
D023304E.ai

-: Ignore (don’t care)

*1: An “NR” entry in the table indicates a condition where the data status is neither BAD nor QST.
*2: “RV1 to RV7” means the logic sum of the data statuses from RV1 to RV7.
*3: The IOP and IOP- of a status to be communicated have higher priority. An IOP will be transmitted if an NRDY has been
generated for an input value with higher priority, and an IOP has been generated at the same time for an input value with lower
priority.

The following processing is performed if the data status of a calculation output value (CPV)
becomes a bad data value (BAD) or a questionable data value (QST) according to the
specification of the calculation input value error detection.
• If the data status of a calculation output value (CPV) becomes a bad data value (BAD)
The calculation processing is aborted, the value immediately before the error is retained
and the connected destination of OUT terminal will hold this retained previous value. The
previous good CPV is held and accessible from SUB terminal.
If CPV overshoot is set to the block, the data from the OUT terminal is not affected by the
CPV change caused by main calculation input (RV) abnormality. However, the CPV after
overshoot can be accessed using SUB terminal.
• If the data status of a calculation output value (CPV) becomes a questionable data value
(QST)
The calculation input values (RV, RVn) retain the values immediately before the error
generation. The calculation processing is continued using these values and the calculation
output value (CPV) is updated.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.33 General-Purpose Calculation Blocks (CALCU, CALCU-C)> D2-136

n Data for Totalization when Input Signal Conversion is Exact

Totalization Pulse Train
▼ Data Item for Totalization
When the input signal conversion is specified with [Exact Totalization Pulse Train Input], the
totalization can use the calculation outut value (CPV) instead of the integration of the calculation
input value (RV).
[Exact Totalization Pulse Train Input] can be specified on the Function Block Detail builder for the
item of [Input Signal Conversion].
• Data Item for Totalization:
Choose [RV] or [CPV].
The default is [RV].
Moreover, if the [Input Signal Conversion] is specified with another type of conversion, the
totalization can only use the calcaulation output [CPV], cannot use the calculation input [RV].

n Calculation Algorithm
The General-Purpose Calculation Blocks (CALCU, CALCU-C) execute algorithms that are
defined using the general-purpose calculation expression description language.

SEE
ALSO For the general-purpose calculation expression description language, see the following:
D2.47, “General-Purpose Arithmetic Expressions”

The calculation input values, calculated output values and set parameters of the General-
Purpose Calculation Block (CALCU) all use double-precision floating-point data type.
The calculation input values (RV4 to RV7) and calculated output values (CPV2, CPV3) of the
General-Purpose Calculation Block with String I/O (CALCU-C) all use string data type. When
data of other function block is referred or set using element symbols and a description of data
items without specifying I/O terminal connections in a calculation expression description, terminal
connections of the specified I/O data are performed automatically during compiling. The I/O
terminals used here are different from those connected in the Function Block Detail Builder.

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

l Restriction on the General-Purpose Calculation Blocks

(CALCU, CALCU-C)
• Up to eight input terminal connections and four output terminal connections can be defined
on the Function Block Detail Builder.
• Up to 24 input data and 12 output data can be referred or set as the element symbols and
data items in a calculation expression. However, for using alphanumeric strings in CALCU-
C, a maximum of 6 character strings and 6 numeric strings can be used.
• Data of other FCS cannot be used in an arithmetic/logic calculation expression.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.33 General-Purpose Calculation Blocks (CALCU, CALCU-C)> D2-137

n Set Parameters
The parameters of the General-Purpose Calculation Blocks (CALCU, CALCU-C) are shown as
follows.
• Calculation parameters 1 to 4 (P01 to P 04):
Engineering unit data values.
• Calculation parameters 5 to 8 (P05 to P08):
Engineering unit data values in the case of General-Purpose Calculation Block (CALCU).
A string data of up to 16 standard-width characters or 8 double-width characters can be
used for the General-Purpose Calculation Block with String I/O (CALCU-C).

n Computation Error Alarm Check

A computation error alarm (CERR) is generated if a calculation error occurs during the
processing of a user-defined calculation formula.
If a computation error alarm (CERR) is generated, the calculation processing stops and an error
message containing an error generation statement number and an error code is output. The error
occurrence statement number is set to the data item ERRL, and the previous value is held as the
calculated output value (CPV). The ERRL can be accessed from other function block, since it is
handled as a parameter.
If a computation error occurs, the computation executes again from the beginning of the
calculation in the next scan. If the second computation is completed correctly, the computation
error alarm (CERR) returns to normal. The value at the error occurrence is held in ERRL.

SEE
ALSO For details on the description of calculation errors and the calculation error handling, see the following:
D2.47.7, “Error Handling”

n CPV Range Limit: KFCS2/FFCS/LFCS2

▼ CPV range limit
The CPV Range Limit can be applied to limit the calculation output value (CPV) within a specified
range. The CPV can be limited in range between SL-(SH-SL) and SH.
When CPV is smaller than the low limit of SL-(SH-SL), the low limit will be used. When CPV is
greater than the high limit of SH, the high limit will be used.
The CPV range limit is different from the PV range limit, only limit the calculation output value
(CPV). The limited calculation output value will go through digital filter and used for totalization.
The CPV Range Limit functions only when the block mode is AUT.
The CPV Range Limit can be specified on Function Block Detail builder.
• CPV Range Limit:
Choose [Valid] or [Invalid].
The default is [Invalid].

SEE
ALSO For more information about PV range limit, see the following:
“n PV Range Limit: KFCS2/FFCS/LFCS2” in chapter C3.1.1, “Input Signal Conversions Common to
Regulatory Control Blocks and Calculation Blocks”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.33 General-Purpose Calculation Blocks (CALCU, CALCU-C)> D2-138

n Data Items – CALCU, CALCU-C

The table below shows the data items of the General-Purpose Calculation Block (CALCU):
Table Data Items of General-Purpose Calculation Block (CALCU)
Entry Permitted
Data Item Data Name Range Default
or Not
MODE Block mode x ----- O/S(AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
RV Calculated input value ----- 0
RAW Raw input data Value in the unit at the connection destination -----
RV1 to RV7 Calculated input value 1 to 7 ----- 0
RAW1 to RAW7 Raw input data 1 to 7 Value in the unit at the connection destination -----
CPV Calculated output value Δ (*1) CPV engineering unit value SL
SUM Totalizer value Value in the same engineering unit as CPV 0
CPV1 to CPV3 Calculated output value 1 to 3 ----- 0
P01 to P08 Calculation parameters 1 to 8 x ----- 0
EERL Error statement number ----- 0
ERRC (* 2) Error code ----- 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D023305E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL
*2: ERRC denotes a detailed error code and a class error code

SEE
ALSO For a list of valid block modes for CALCU block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.33 General-Purpose Calculation Blocks (CALCU, CALCU-C)> D2-139
The table below shows the data items of the General-Purpose Calculation Block with String
I/O (CALCU-C):
Table Data Items of General-Purpose Calculation Block with String I/O (CALCU-C)
Entry Permitted
Data Item Data Name Range Default
or Not
MODE Block mode x ----- O/S(AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
RV Calculated input value ----- 0
RAW Raw input data Value in the unit at the connection destination -----
RV1 to RV3 Calculated input value 1 to 3 ----- 0
RAW1 to RAW3 Raw input data 1 to 3 Value in the unit at the connection destination -----
RV4 to RV7 Calculated input value 4 to 7 16Byte NULL
CPV Calculated output value Δ (*1) CPV engineering unit value SL
SUM Totalizer value Value in the same engineering unit as CPV 0
CPV1 Calculated output value 1 16Byte NULL
CPV2 to CPV3 Calculated output value 2 and 3 ----- 0
P01 to P04 Calculation parameters 1 to 4 x ----- 0
P05 to P08 Calculation parameters 5 to 8 x 16Byte NULL
EERL Error statement number ----- 0
ERRC (* 2) Error code ----- 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D023306E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL
*2: ERRC denotes a detailed error code and a class error code

SEE
ALSO For a list of valid block modes for CALCU-C block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.33 General-Purpose Calculation Blocks (CALCU, CALCU-C)> D2-140

n Calculation Block In/Out Data Normalization

▼ Normalization of Input/Output Signal
By designating on the builder, the calculation can be performed using the normalized values for
the data connected to the IN terminal, Q01 to Q07 terminals, OUT terminal, J01 to J03 terminals
of a general-purpose calculation block and the data set to or referenced by the general-purpose
calculation block according to the PV range (SH, SL), SV range (SSH, SSL), MV range (MSH,
MSL) of the data.
The I/O terminals for numerical data and the numerical variables in the CALCU-C function block
are also affected by this feature. The numerical input and output terminals of CALCU-C function
block are as follows:
• Input Terminals for Numerical Data: IN, Q01 to Q03
• Output Terminals for Numerical Data: OUT, J01
• Numerical variables that referenced or defined by the expressions in the CALCU-C function
block

IMPORTANT
Even though the I/O normalization is specified on the builder, the CENTUM-XL calculation
expressions are not free from problems. After the CENTUM-XL migration, the application
debugging is necessary.

l In Data Normalization
The input engineering unit data (RV) of a calculation block can be normalized before used in the
calculation. When normalizing the RV, the range of the general-purpose calculation block will be
ignored but the range of the block connected to IN terminal or Q01 to Q07 terminal will be used.
The normalization is performed with the following formula:

RVN = (RV – SLi) / (SHi – SLi)

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

For the data item, such as DV or DL, that is differentiated from other data items, the normalization
is performed with the following formula:

RVN = RV / (SHi – SLi)

RVN: After normalization
RV: Before normalization
SHi: Scale high-limit of the connected data
SLi: Scale low -limit of the connected data

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.33 General-Purpose Calculation Blocks (CALCU, CALCU-C)> D2-141
l Convert Output Data to Engineering Unit Data
When outputing the calculated data, the normalized data can be converted to engineering unit
data. When converting CPV to an engineering unit data, the range of the CPV will be used. When
converting CPV1 to CPV3 and other internal variables to engineering unit data, the ranges of the
blocks connected to J01 to J03 terminal will be used.
The conversion is performed with the following formula:

CPV = CPVN x (SHo – SLo) + SLo

CPV: Before normalization (Engineering Unit Data)
CPVN: After normalization
SHo: Scale high-limit of the connected data (for CPV1 to CPV3 and other internal
variables)
Scale high-limit of CPV (for CPV)
SLo: Scale low-limit of the connected data (for CPV1 to CPV3 and other internal
variables)
Scale low-limit of CPV (for CPV)

For the data item, such as DV or DL, that is differentiated from other data items, the conversion is
performed with the following formula:

CPV = CPVN x (SHo – SLo)

CPV: Before normalization (Engineering Unit Data)
CPVN: After normalization
SHo: Scale high-limit of the connected data (for CPV1 to CPV3 and other internal
variables)
Scale high-limit of CPV (for CPV)
SLo: Scale low-limit of the connected data (for CPV1 to CPV3 and other internal
variables)
Scale low-limit of CPV (for CPV)

The formulas for normalizing the input data and for converting the output data to engineering unit
data in related to ranges are shown in the table below:
Table In/Out Data Normalization
Formula Converting output to
Range Normalizing input data
number engineering unit data
1 SH:SL RVN = (RV - SL) / (SH - SL) CPV = CPVN × (SH - SL) + SL
2 SSH:SSL RVN = (RV - SSL) / (SSH - SSL) CPV = CPVN × (SSH - SSL) + SSL
3 MSH:MSL RVN = (RV - MSL) / (MSH - MSL) CPV = CPVN × (MSH - MSL) + MSL
4 SH:SL (Difference) RVN = RV / (SH - SL) CPV = CPVN × (SH - SL)
5 SSH:SSL (Difference) RVN = RV / (SSH - SSL) CPV = CPVN × (SSH - SSL)
6 MSH:MSL (Difference) RVN = RV / (MSH - MSL) CPV = CPVN × (MSH - MSL)
7 DSH:DSL RVN = (RV - DSL) / (DSH - DSL) CPV = CPVN × (DSH - DSL) + DSL
8 DSH:DSL (Difference) RVN = RV / (DSH - DSL) CPV = CPVN × (DSH - DSL)
9 MSH1:MSL1 RVN = (RV - MSL1) / (MSH1 - MSL1) CPV = CPVN × (MSH1 - MSL1) + MSL1
10 MSH1:MSL1 (Difference) RVN = RV / (MSH1 - MSL1) CPV = CPVN × (MSH1 - MSL1)
11 MSH2:MSL2 RVN = (RV - MSL2) / (MSH2 - MSL2) CPV = CPVN × (MSH2 - MSL2) + MSL2
12 MSH2:MSL2 (Difference) RVN = RV / (MSH2 - MSL2) CPV = CPVN × (MSH2 - MSL2)
D023307E.ai

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.33 General-Purpose Calculation Blocks (CALCU, CALCU-C)> D2-142
l Input Limitation
The input data are limited by the range of the connected destination(SHi, SLi). The data that is
differentiated from other data items are limited within positive and negative differences +/-(SHi-
SLi). However, the values beyond the limitation can be visualized on Tuning View.

l Output Limitation
The calculation result CPV will be limited by the range of the CPV itself. The CPV1 to CPV3 and
other internal calculation variables will be limited by the ranges (between SHo and SLo) of the
blocks connected to J01 to J03 terminals.The data that is differentiated from other data items are
limited within positive and negative differences +/-(SHo-SLo). However, the values after limitation
can be visualized on Tuning View.

l Designating In/Out Data Normalization

Data normalization can be designated for each calculation block on the Function Block Detail
Builder of the general-purpose calculation block.
Normalization of input/output signal: Select “No” or “Yes”
Default: “No”

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

l Regarding DT or NX terminal of BDA-L, BDSET-1L/BDSET-2L Block

When a general-purpose calculation block is referencing or setting the data of a DT01 to DT16
or a NX01 to NX16 terminal of a BDA-L, BDSET-1L/BDSET-2L block, the data normalization
and the range limitation will be performed according to the range of the data connected to the
corresponding J01 to J16 terminal.
The data normalization and range limitation according to the range of the data connected to the
J01 to J16 terminals are performed only when the connected data is normalizable.
When the data connected to the J01 to J16 terminal is changed, CALCU that referencing the
previously connected data may become invalid element. In this case, you need to perform the
operations for resolving the invalid elements.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.33 General-Purpose Calculation Blocks (CALCU, CALCU-C)> D2-143
l Normalizable Data (Data Connection)
What data item can be normalized is automatically determined on the control drawing builder.
The normalizable data items (Data Connection) are listed below. In this table, the numbers that
represent different formulas are the same as in the table of In/Out Data Normalization.
• Regulatory Control Blocks
Table Relevant Data Item: Regulatory Control Blocks (Data Connection) (1/3)

Model Range Fomula

name Relevant data item number
HH / LL / PH / PL / PV / PVP / SH / SL SH:SL 1
PVI
VL SH:SL (Difference) 4
HH / LL / PH / PL / PV / PVP / SH / SL / SV / SVH / SVL SH:SL 1
PVI-DV
DL / DV / VL SH:SL (Difference) 4
CSV / HH / LL / PH / PL / PV / PVP / RSV / SH / SL / SV / SVH / SVL SH:SL 1
PID MH / ML / MSH / MSL / MV / OPHI / OPLO / PMV / RLV1-2 / RMV MSH:MSL 3
DB / DL / GW / VL / DV SH:SL (Difference) 4
CSV / HH / LL / PH / PL / PV / PVP / RSV / SH / SL / SV / SVH / SVL SH:SL 1
PI-HLD MH / ML / MSH / MSL / MV / OPHI / OPLO / PMV / RLV1-2 / RMV MSH:MSL 3
DB / DL / GW / VL / DV SH:SL (Difference) 4
CSV / HH / LL / PH / PL / PV / PVP / RSV / SH / SL / SV / SVH / SVL SH:SL 1
MH / ML / MSH / MSL / MV / OPHI / OPLO / PMV / RLV1-2 / RMV MSH:MSL 3
PID-BSW
DL / LK / VL / DV SH:SL (Difference) 4
BIAS MSH:MSL (Difference) 6
CSV / HH / LL / PH / PL / PV / PVP / RSV / SH / SL / SV / SVH / SVL SH:SL 1
ONOFF MV / PMV / RMV MSH:MSL 3
DL / VL / DV SH:SL (Difference) 4
CSV / HH / LL / PH / PL / PV / PVP / RSV / SH / SL / SV / SVH / SVL SH:SL 1
ONOFF-E MV / PMV / RMV MSH:MSL 3
DL / VL / DV SH:SL (Difference) 4
CSV / HH / LL / PH / PL / PV / PVP / RSV / SH / SL / SV / SVH / SVL SH:SL 1
ONOFF-G MV / PMV / RMV MSH:MSL 3
DB / DL / VL / DV SH:SL (Difference) 4
CSV / HH / LL / PH / PL / PV / PVP / RSV / SH / SL / SV / SVH / SVL SH:SL 1
ONOFF-GE MV / PMV / RMV MSH:MSL 3
DB / DL / VL / DV SH:SL (Difference) 4
CSV / HH / LL / PH / PL / PV / PVP / RSV / SH / SL / SV / SVH / SVL SH:SL 1
PID-TP MH / ML / MSH / MSL / MV / OPHI / OPLO / PMV / RLV1-2 / RMV MSH:MSL 3
DB / DL / GW / VL / DV SH:SL (Difference) 4
CSV / HH / LL / PH / PL / PV / PVP / RSV / SH / SL / SV / SVH / SVL SH:SL 1
PD-MR CALC / MH / ML / MR / MSH / MSL / MV / OPHI / OPLO / PMV / RMV MSH:MSL 3
DL / VL / DV SH:SL (Difference) 4
CSV / HH / LL / PH / PL / PV / RSV / SH / SL / SVH / SVL / SV SH:SL 1
MH / ML / MSH / MSL / MV / OPHI / OPLO / PMV / RMV MSH:MSL 3
PI-BLEND RP MSH:MSL (Difference) 6
DSH / DSL DSL:DSH 7
DL / VL / DV DSL:DSH (Difference) 8
D023308E.ai

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.33 General-Purpose Calculation Blocks (CALCU, CALCU-C)> D2-144
Table Relevant Data Item: Regulatory Control Blocks (Data Connection) (2/3)

Model Range Fomula

name Relevant data item number
CSV / HH / LL / PH / PL / PV / PVP / RSV / SH / SL / SV / SVH / SVL SH:SL 1
PID-STC MH / ML / MSH / MSL / MV / OPHI / OPLO / PMV / RLV1-2 / RMV MSH:MSL 3
DB / DL / GW / VL / DV SH:SL (Difference) 4
MLD MH / ML / MSH / MSL / MV / OPHI / OPLO MSH:MSL 3
HH / LL / PH / PL / PV / PVP / SH / SL SH:SL 1
MLD-PVI MH / ML / MSH / MSL / MV / OPHI / OPLO MSH:MSL 3
VL SH:SL (Difference) 4
CSV / SSH / SSL / SV / SVH / SVL SSH:SSL 2
MLD-SW MH / ML / MSH / MSL / MV / OPHI / OPLO / PMV MSH:MSL 3
BIAS / RP SSH:SSL (Difference) 5
MC-2 ANSP / FV / PH / PL / SH / SL SH:SL 1
MC-2E ANSP / FV / PH / PL / SH / SL SH:SL 1
MC-3 ANSP / FV / PH / PL / SH / SL SH:SL 1
MC-3E ANSP / FV / PH / PL / SH / SL SH:SL 1
HH / LL / PH / PL / PV / PVP / SH / SL SH:SL 1
CSV / RSV / SSH / SSL / SV / SVH / SVL SSH:SSL 2
CALC / MH / ML / MSH / MSL / MV / OPHI / OPLO / PMV / RMV MSH:MSL 3
RATIO
VL SH:SL (Difference) 4
RP SSH:SSL (Difference) 5
BIAS MSH:MSL (Difference) 6
PG-L13 (*1) CALC / MH / ML / MSH / MSL / MV / OPHI / OPLO / Y01-14 MSH:MSL 3
LL / PH / PL / PV / SH / SL SH:SL 1
BSETU-2
MH / ML / MSH / MSL / MV / OPHI / OPLO / PRE MSH:MSL 3
LL / PH / PL / PV / SH / SL SH:SL 1
BSETU-3
MH / ML / MSH / MSL / MV / OPHI / OPLO / PRE MSH:MSL 3
CSV / RSV / SSH / SSL / SV / SVH / SVL SSH:SSL 2
VELLIM MH / ML / MSH / MSL / MV / OPHI / OPLO / PMV / RMV MSH:MSL 3
DL / DMVM / DMVP / DV SSH:SSL (Difference) 5
SS-H/M/L PV / RV1-3 / SH / SL SH:SL 1
PV / RV1-3 / SH / SL SH:SL 1
AS-H/M/L
MH / ML / MSH / MSL / MV / OPHI / OPLO / PMV MSH:MSL 3
HH / LL / PH / PL / PV / PVP / RV1-2 / SH / SL / SV SH:SL 1
SS-DUAL
DL / DV / VL SH:SL (Difference) 4
FOUT CSV / SSH / SSL / SV SSH:SSL 2
PV / SH / SL SH:SL 1
CSV / SSH / SSL / SV / SVH / SVL SSH:SSL 2
FFSUM
MH / ML / MSH / MSL / MV / OPHI / OPLO / PMV MSH:MSL 3
RP MSH:MSL (Difference) 6
MH / ML / MSH / MSL / MV / OPHI / OPLO / PMV / PV MSH:MSL 3
XCPL
RP MSH:MSL (Difference) 6
D023309E.ai
*1: SV, X02 to X14, PH, PL of PG-L13 are not normalizable.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.33 General-Purpose Calculation Blocks (CALCU, CALCU-C)> D2-145
Table Relevant Data Item: Regulatory Control Blocks (Data Connection) (3/3)

Model Range Fomula

name Relevant data item number
CSV / RSV / SRH1-2 / SRL1-2 / SSH / SSL / SV / SVH / SVL SSH:SSL 2
MSH1 / MSL1 / MV1 MSH1:MSL1 9
SPLIT RP1 MSH1:MSL1 (Difference) 10
MSH2 / MSL2 / MV2 MSH2:MSL2 11
RP2 MSH2:MSL2 (Difference) 12
PH / PV / SH / SL SH:SL 1
PTC
DL SH:SL (Difference) 4
ALM-R Irrelevant to normalization ― ―
CSV / PH / PL / PV / RSV / SH / SL / SV / SVH / SVL SH:SL 1
SLCD
DL / DV SH:SL (Difference) 4
CSV / PH / PL / PV / RSV / SH / SL / SV / SVH / SVL SH:SL 1
SLPC
DL / DV SH:SL (Difference) 4
CSV / PH / PL / PV / RSV / SH / SL / SV / SVH / SVL SH:SL 1
SLMC
DL / DV SH:SL (Difference) 4
SMST-111 CSV / PH / PL / PV / RSV / SH / SL / SV / SVH / SVL SH:SL 1
SMST-121 PH / PL / PV / SH / SL SH:SL 1
PH / PL / PV / SH / SL SH:SL 1
SMRT CSV / RSV / SSH / SSL / SV / SVH / SVL SSH:SSL 2
DL SH:SL (Difference) 4
SBSD PH / PL / PV / SH / SL SH:SL 1
SLBC PH / PL / PV / SH / SL SH:SL 1
PV / SH / SL SH:SL 1
SLCC RSV / SSH / SSL / SV SSH:SSL 2
DV SH:SL (Difference) 4
STLD PV / SH / SL SH:SL 1
D023310E.ai

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.33 General-Purpose Calculation Blocks (CALCU, CALCU-C)> D2-146
• Calculation Blocks
Table Relevant Data Item: Calculation Blocks (Data Connection) (1/2)

Model Range Fomula

name Relevant data item number
ADD CPV / SH / SL SH:SL 1
MUL CPV / SH / SL SH:SL 1
DIV CPV / SH / SL SH:SL 1
AVE CPV / SH / SL SH:SL 1
SQRT CPV / SH / SL SH:SL 1
EXP CPV / SH / SL SH:SL 1
LAG CPV / SH / SL SH:SL 1
INTEG CPV / SH / SL SH:SL 1
LD CPV / SH / SL SH:SL 1
RAMP CPV / SH / SL SH:SL 1
LDLAG CPV / SH / SL SH:SL 1
DLAY CPV / SH / SL SH:SL 1
DLAY-C CPV / SH / SL SH:SL 1
AVE-M CPV / PREV / SH / SL SH:SL 1
AVE-C CPV / PREV / SH / SL SH:SL 1
FUNC-VAR CPV / SH / SL SH:SL 1
TPCFL CPV / SH / SL SH:SL 1
ASTM1 CPV / SH / SL SH:SL 1
ASTM2 CPV / SH / SL SH:SL 1
AND Irrelevant to normalization ― ―
OR Irrelevant to normalization ― ―
NOT Irrelevant to normalization ― ―
SRS1-S Irrelevant to normalization ― ―
SRS1-R Irrelevant to normalization ― ―
SRS2-S Irrelevant to normalization ― ―
SRS2-R Irrelevant to normalization ― ―
WOUT Irrelevant to normalization ― ―
OND Irrelevant to normalization ― ―
OFFD Irrelevant to normalization ― ―
TON Irrelevant to normalization ― ―
TOFF Irrelevant to normalization ― ―
GT Irrelevant to normalization ― ―
GE Irrelevant to normalization ― ―
EQ Irrelevant to normalization ― ―
BAND Irrelevant to normalization ― ―
BOR Irrelevant to normalization ― ―
BNOT Irrelevant to normalization ― ―
CALCU CPV / SH / SL SH:SL 1
CALCU-C CPV / SH / SL SH:SL 1
D023311E.ai

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.33 General-Purpose Calculation Blocks (CALCU, CALCU-C)> D2-147
Table Relevant Data Item: Calculation Blocks (Data Connection) (2/2)

Model Range Fomula

name Relevant data item number
SW-33 Irrelevant to normalization ― ―
SW-91 Irrelevant to normalization ― ―
DSW-16 CPV / SD01-16 / SH / SL SH:SL 1
DSW-16C Irrelevant to normalization ― ―
DSET SH / SL/ SV / SVH / SVL SH:SL 1
CPV / HH / LL/ PH / PL/ PVP / SH / SL/ SV / SVH / SVL SH:SL 1
DSET-PVI
VL SH:SL (Difference) 4
BDSET-1L DT01-DT16 Depending on the
1 to 12
connected data
BDSET-1C Irrelevant to normalization ― ―
DT01-DT16 / NX01-NX16 Depending on the
BDSET-2L 1 to 12
connected data
BDSET-2C Irrelevant to normalization ― ―
DT01-DT16 Depending on the
BDA-L 1 to 12
connected data
BDA-C Irrelevant to normalization ― ―
D023312E.ai

• Faceplate Blocks
Table Relevant Data Item: Faceplate Blocks (Data Connection)

Model Range Fomula

name Relevant data item number
INDST2 PV / SH / SL / SV / SVH / SVL SH:SL 1
SH / SL / SV / SVH / SVL SH:SL 1
INDST2S
MH / ML / MSH / MSL / MV MSH:MSL 3
PV / SH / SL / SV / SVH / SVL SH:SL 1
INDST3
MH / ML / MSH / MSL / MV MSH:MSL 3
BSI Irrelevant to normalization ― ―
PBS5C Irrelevant to normalization ― ―
PBS10C Irrelevant to normalization ― ―
PV / SH / SL / SV / SVH / SVL SH:SL 1
HAS3C
MH / ML / MSH / MSL / MV MSH:MSL 3
D023313E.ai

• SFC Blocks
Table Relevant Data Item: SFC Blocks (Data Connection)

Model Range Fomula

name Relevant data item number
_SFCSW Irrelevant to normalization ― ―
_SFCPB Irrelevant to normalization ― ―
PV / SH / SL / SV / SVH / SVL SH:SL 1
_SFCAS
MH / ML / MSH / MSL / MV MSH:MSL 3
D023314E.ai

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.33 General-Purpose Calculation Blocks (CALCU, CALCU-C)> D2-148
• UNIT Instrument Blocks
Table Relevant Data Item: UNIT Instrument Blocks (Data Connection)

Model Range Fomula

name Relevant data item number
_UTSW Irrelevant to normalization ― ―
_UTPB Irrelevant to normalization ― ―
PV / SH / SL / SV / SVH / SVL SH:SL 1
_UTAS
MH / ML / MSH / MSL / MV MSH:MSL 3
D023315E.ai

• Valve Pattern Monitors

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

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

Model Range Fomula

name Relevant data item number
PV / SH / SL / SV / SVH / SVL / SVPR SH:SL 1
FSBSET MSH / MSL / MV / OPHI / OPLO MSH:MSL 3
DL1 / DL2 / DV SH:SL (Difference) 4
BLEND MPSV / PV / SH / SL / SV / SVH / SVL / SVPR SH:SL 1
D023316E.ai

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.33 General-Purpose Calculation Blocks (CALCU, CALCU-C)> D2-149
• FF Faceplate Blocks
Table Relevant Data Item: FF Faceplate Blocks (Data Connection)

Model Range Fomula

name Relevant data item number
FF-AI HH / LL / OUT_V / PH / PL / PV / SH / SL SH:SL 1
FF-DI Irrelevant to normalization ― ―
BKCL_IN / MH / ML / MSH / MSL / MV / OPHI / OPLO / SEL1- SEL3 /
FF-CS MSH:MSL 3
BKCL_SL1- BKCL_SL3
BKCL_OUT / CSV / HH / LL / PH / PL / PV / RCAS_OUT / RSV / SH /
SH:SL 1
SL
FF-PID BKCL_IN / MH / ML / MSH / MSL / MV / OPHI / OPLO / RMV /
MSH:MSL 3
ROUT_OUT
DH SH:SL (Difference) 4
BKCL_OUT / CSV / HH / LL / PH / PL / PV / RCAS_OUT / RSV / SH / SL SH:SL 1
FF-RA BKCL_IN / MH / ML / MSH / MSL / MV / OPHI / OPLO MSH:MSL 3
DH SH:SL (Difference) 4
BKCL_OUT / CSV / FST_VAL / PV / RCAS_OUT / RSV / SH / SL SH:SL 1
FF-AO
MSH / MSL / MV / OPHI / OPLO / READBACK MSH:MSL 3
FF-DO Irrelevant to normalization ― ―
FF-OS CSV / SSH / SSL / SV SSH:SSL 2
FF-SC OUT1_V / OUT2_V ― ―
FF-IT SH / SL SH:SL 1
FF-IS CPV / SH / SL SH:SL 1
FF-MDI Irrelevant to normalization ― ―
FF-MDO Irrelevant to normalization ― ―
FF-MAI Irrelevant to normalization ― ―
FF-MAO Irrelevant to normalization ― ―
D023317E.ai

l Normalizable Data (Terminal Connection)

CPV is normalized or converted according to the range of itself.

SEE
ALSO For more information about terminal connection, see the following:
C2.2, “Terminal Connection”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.33 General-Purpose Calculation Blocks (CALCU, CALCU-C)> D2-150
l Data That Irrelevant to Data Normalization
The following data are irrelevant to data normalization.
• Data connected through switch blocks (SW-33, SW-91)
• Data connected through inter-station data link block
• Data connected through process I/O
• Data connected through software I/O
• Data connected to SUB terminal
• Data connected through sequence connection
• Data connected to MI, NB, CR and GM terminals of self-tuning PID controller block (PID-
STC)
• Data connected to MV1 to MV8 items of a cascade signal distributor block (FOUT)
• Data connected to MV, MSH, MSL, MH, ML and RMV items of YS blocks
If you want to normalize the above data, you can connect the data to a PVI block first and then
connect to the calculation block.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.34 Three-Pole Three-Position Selector Switch Block (SW-33)> D2-151

D2.34 Three-Pole Three-Position Selector Switch

Block (SW-33)
The Three-Pole Three-Position Selector Switch Block (SW-33) is used when changing
three-position signal paths.

n Three-Pole Three-Position Selector Switch Block (SW-33)

▼ Connection
The Three-Pole Three-Position Selector Switch Block (SW-33) is a function block that changes
signal paths in accordance with the switch command sent from the operation and monitoring
functions or other function blocks. Up to three three-position switches can be handled
simultaneously by one Three-Pole Three-Position Selector Switch Block (SW-33).
Here is a function block diagram of the Three-Pole Three-Position Selector Switch Block (SW-33).

Switch position

SW

OFF 0

S11 1

S12 2 S10

S13 3

OFF 0

S21 1

S22 2 S20

S23 3

OFF 0

S31 1

S32 2 S30

S33 3

D023501E.ai

Figure Function Block Diagram of Three-Pole Three-Position Selector Switch Block (SW-33)

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.34 Three-Pole Three-Position Selector Switch Block (SW-33)> D2-152
The following table shows the connection types and connection destinations of the I/O terminals
of the Three-Pole Three-Position Selector Switch Block (SW-33).
Table Connection Types and Connection Destinations of the I/O Terminals of Three-Pole Three-
Position Selector Switch Block (SW-33)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
S10 I/O terminal x x x x x x
S11 I/O terminal x x x x x x
S12 I/O terminal x x x x x x
S13 I/O terminal x x x x x x
S20 I/O terminal x x x x x x
S21 I/O terminal x x x x x x
S22 I/O terminal x x x x x x
S23 I/O terminal x x x x x x
S30 I/O terminal x x x x x x
S31 I/O terminal x x x x x x
S32 I/O terminal x x x x x x
S33 I/O terminal x x x x x x
D023502E.ai

x: Connection available
Blank: Connection not available
Note: Condition check and status manipulation signals of sequence connection cannot be handled by the Three-Pole Three-Position
Selector Switch Block (SW-33). Inter-station data link cannot be performed via the block, either.

n Function of 3-Pole 3-Position Selector Switch Block (SW-33)

The SW-33 block performs input processing and calculation processing.
The SW-33 block does not have its own processing timing. The SW-33 block is never subject
to scans. The signal path of the SW-33 block is used at the timing when a function block at the
connection destination is executed.

SEE
ALSO • For the types of input processing possible for the SW-33 block, see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”

l Calculation Processing of 3-Pole 3-Position Selector Switch Block (SW-33)

The SW-33 block changes the 3-pole signal path via the operation and monitoring function or
other function blocks.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.34 Three-Pole Three-Position Selector Switch Block (SW-33)> D2-153

n Calculation Algorithm
The Three-Pole Three-Position Selector Switch Block (SW-33) changes signal paths in
accordance with the switch command sent from the operation and monitoring functions or other
function blocks.
There is no restriction on the I/O direction of signals. S10, S20 and S30 terminals as well as the
remaining terminals can be used for input. However, as the three three-position switches are
linked with one another, each three-position switch is always connected to a terminal at the same
switch position.

n Set Parameters
The parameters of the Three-Pole Three-Position Selector Switch Block (SW-33) are shown as
follows.
• Selector switch (SW):
A numeric value between 0 and 3
• Switch high limit (SWH):
A numeric value between 0 and 3
• Switch low limit (SWL):
A numeric value between 0 and 3

When setting the selector switch (SW) from the operation and monitoring functions, if the set
selector switch (SW) exceeds the switch high limit (SWH) or the switch low limit (SWL), a
confirmation message appears. When the operator performs confirmation operation, the content
of the setting becomes effective.

n Data Items – SW-33

Table Data Items of Three-Pole Three-Position Selector Switch Block (SW-33)
Entry Permitted
Data Item Data Name Range Default
or Not
SW Selector switch x 0 to 3 0
SWH Switch high limit x 0 to 3 3
SWL Switch low limit x 0 to 3 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D023503E.ai

x: Entry is permitted unconditionally

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.35 One-Pole Nine-Position Selector Switch Block (SW-91)> D2-154

D2.35 One-Pole Nine-Position Selector Switch

Block (SW-91)
The 1-Pole 9-Position Selector Switch Block (SW-91) is used when changing nine-position
signal paths.

n One-Pole Nine-Position Selector Switch Block (SW-91)

▼ Connection
The One-Pole Nine-Position Selector Switch Block (SW-91) is a function block that changes
signal paths in accordance with the switch command sent from the operation and monitoring
functions or other function blocks. Only one nine-position switch can be handled by the One-Pole
Nine-Position Selector Switch Block (SW-91).
Here is a function block diagram of the One-Pole Nine-Position Selector Switch Block (SW-91).

OFF 0

S11 1 SW

S12 2

S13 3

S14 4

S15 5 S10

S16 6

S17 7

S18 8

S19 9

D023601E.ai

Figure Function Block Diagram of One-Pole Nine-Position Selector Switch Block (SW-91)

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.35 One-Pole Nine-Position Selector Switch Block (SW-91)> D2-155
The following table shows the connection types and connection destinations of the I/O terminals
of the One-Pole Nine-Position Selector Switch Block (SW-91).
Table Connection Types and Connection Destinations of the I/O Terminals of One-Pole Nine-Position
Selector Switch Block (SW-91)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
S10 I/O terminal x x x x x x
S11 I/O terminal x x x x x x
S12 I/O terminal x x x x x x
S13 I/O terminal x x x x x x
S14 I/O terminal x x x x x x
S16 I/O terminal x x x x x x
S17 I/O terminal x x x x x x
S18 I/O terminal x x x x x x
S19 I/O terminal x x x x x x
D023602E.ai

x: Connection available
Blank: Connection not available
Note: Condition check and status manipulation signals of sequence connection cannot be handled. Inter-station data link cannot be
performed, either.

n Function of 1-Pole 9-Position Selector Switch Block (SW-91)

The SW-91 block performs input processing and calculation processing.
The SW-91 block does not have its own processing timing. The SW-91 block is never subject
to scans. The signal path of the SW-91 block is used at the timing when a function block at the
connection destination is executed.

SEE
ALSO • For the types of input processing possible for the SW-91 block, see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”

l Calculation Processing of 1-Pole 9-Position Selector Switch Block (SW-91)

The SW-91 block changes the 9-pole signal path via the operation and monitoring function or
other function blocks.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.35 One-Pole Nine-Position Selector Switch Block (SW-91)> D2-156

n Calculation Algorithm
The One-Pole Nine-Position Selector Switch Block (SW-91) changes signal paths in accordance
with the switch command sent from the operation and monitoring functions or other function
block.
There is no restriction on the I/O direction of signals for the One-Pole Nine-Position Selector
Switch Block (SW-91). The terminals S11 to S19 can be used as the output terminal while the
terminals S10 is used as the input terminals, or vice versa, the terminal S10 can be used as the
input terminal while the terminals S11 to S19 are used as the output terminals.

n Set Parameters
The parameters of the One-Pole Nine-Position Selector Switch Block (SW-91) are shown as
follows.
• Selector switch (SW):
A numeric value between 0 and 9
• Switch high limit (SWH):
A numeric value between 0 and 9
• Switch low limit (SWL):
A numeric value between 0 and 9

When setting the selector switch (SW) from the operation and monitoring functions, if the set
selector switch (SW) exceeds the switch high limit (SWH) or the switch low limit (SWL), a
confirmation message appears. When the operator performs confirmation operation, the content
of the setting becomes effective.

n Data Items – SW-91

Table Data Items of One-Pole Nine-Position Selector Switch Block (SW-91)
Entry Permitted
Data Item Data Name Range Default
or Not
SW Selector switch x 0 to 9 0
SWH Switch high limit x 0 to 9 9
SWL Switch low limit x 0 to 9 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D023603E.ai

x: Entry is permitted unconditionally

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.36 Selector Switch Block for 16 Data (DSW-16)> D2-157

D2.36 Selector Switch Block for 16 Data (DSW-16)

The Selector Switch Block for 16 Data (DSW-16) is used when switching output constants
(numeric data) from one to the other is required.

n Selector Switch Block for 16 Data (DSW-16)

▼ Connection
The Selector Switch Block for 16 Data (DSW-16) is a function block that outputs a constant
(numeric value data) in accordance with the switch command sent from the operation and
monitoring functions or other function blocks.
Here is a function block diagram of the Selector Switch Block for 16 Data (DSW-16).

Switch position
OFF 0
SW
Constant 1 1

Constant 2 2
CPV OUT

Constant 16 16

D023701E.ai

Figure Function Block Diagram of Selector Switch Block for 16 Data (DSW-16)

The following table shows the connection types and connection destinations of the I/O terminals
of the Selector Switch Block for 16 Data (DSW-16).
Table Connection Types and Connection Destinations of the I/O Terminals of Selector Switch Block for
16 Data (DSW-16)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
Calculation
OUT x x x x
output
D023702E.ai

x: Connection available
Blank: Connection not available

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.36 Selector Switch Block for 16 Data (DSW-16)> D2-158

n Functions of Selector Switch Block for 16 Data (DSW-16)

The DSW-16 block performs input processing, calculation processing, output processing, and
alarm processing.
The only processing timing available for the DSW-16 block is a periodic startup. Selections
available for the scan period used to execute a periodic startup include the basic scan period, the
medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the DSW-16 block,
see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of Selector Switch Block for 16 Data (DSW-16)

The DSW-16 block performs computation using its calculation algorithm and setup parameters.

n Calculation Algorithm
▼ Output Velocity Limiter
The Selector Switch Block for 16 Data (DSW-16) outputs one of the values of the constants
1 through 16 in accordance with the switch command sent from the operation and monitoring
functions or other function blocks. The value of the constant to be output can be limited by the
output velocity limiter function.
When the selector switch (SW) is turned OFF (0), the previous value is held as the calculated
output value (CPV).

The output velocity limiter value can be defined in the Function Block Detail Builder.
• Output Velocity Limiter:
An allowed change per scan in the calculated output value (CPV).
The default is the scale span value.

n Set Parameters
The parameters of the Selector Switch Block for 16 Data (DSW-16) are shown as follows.
• Selector switch (SW):
A numeric value between 0 and 16
• Constants 1 to 16 (SD01 to SD16):
Engineering unit data values

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.36 Selector Switch Block for 16 Data (DSW-16)> D2-159

n Data Items – DSW-16

Table Data Items of Selector Switch Block for 16 Data (DSW-16)
Entry Permitted
Data Item Data Name Range Default
or Not
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
CPV Calculated output value Δ (*1) CPV engineering unit value SL
SW Selector switch x 0 to 16 0
SD01 to SD16 Constants 1 to 16 x Value in the same engineering unit as CPV 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
SH CPV scale high limit Value in the same engineering unit as CPV -----
SL CPV scale low limit Value in the same engineering unit as CPV -----
D023703E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for DSW-16 block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.37 Selector Switch Block for 16 String Data (DSW-16C)> D2-160

D2.37 Selector Switch Block for 16 String Data

(DSW-16C)
Selector Switch Block for 16 String Data (DSW-16C) is used when switching outputting
constants (text string data) from one to the other.

n Selector Switch Block for 16 String Data (DSW-16C)

▼ Connection
The Selector Switch Block for 16 String Data (DSW-16C) is a function block that outputs a
constant (string data) in accordance with the switch command sent from the operation and
monitoring functions or other function blocks.
Here is a function block diagram of the Selector Switch Block for 16 String Data (DSW-16C).

Switch position
OFF 0
SW
Constant 1 1

Constant 2 2
CPV OUT

Constant 16 16

D023801E.ai

Figure Function Block Diagram of Selector Switch Block for 16 String Data (DSW-16C)

The following table shows the connection types and connection destinations of the I/O terminals
of the Selector Switch Block for 16 String Data (DSW-16C).
Table Connection Types and Connection Destinations of the I/O Terminals of Selector Switch Block for
16 String Data (DSW-16C)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
Calculation
OUT x x x x
output
D023802E.ai

x: Connection available
Blank: Connection not available

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.37 Selector Switch Block for 16 String Data (DSW-16C)> D2-161

n Functions of Selector Switch Block for 16 String Data (DSW-16C)

The DSW-16C block performs input processing, calculation processing, and alarm processing.
The only processing timing available for the DSW-16C block is a periodic startup. Selections
available for the scan period used to execute a periodic startup include the basic scan period, the
medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing and alarm processing possible for the DSW-16C block, see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of Selector Switch Block for 16 String Data

(DSW-16C)
The DSW-16C block performs computation using its calculation algorithm and setup parameters.

n Calculation Algorithm
The Selector Switch Block for 16 String Data (DSW-16C) executes the processing that outputs
one of the constants from data 1 to data 16 in accordance with the switch command sent from
the operation and monitoring functions or other function blocks.
When the selector switch (SW) is turned OFF (0), the previous value is held in the calculated
output value (CPV).

n Set Parameters
The parameters of the Selector Switch Block for 16 String Data (DSW-16C) are shown as
follows.
• Selector switch (SW):
A numeric value between 0 and 16
• Constants 1 to 16 (SD01 to SD16):
Set string data of up to 16 standard-width characters or 8 double-width characters.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.37 Selector Switch Block for 16 String Data (DSW-16C)> D2-162

n Data Items – DSW-16C

Table Data Items of Selector Switch Block for 16 String Data (DSW-16C)
Entry Permitted
Data Item Data Name Range Default
or Not
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
CPV Calculated output value Δ (*1) 16Byte NULL
SW Selector switch x 0 to 16 0
SD01 to SD16 Constants 1 to 16 x 16Byte NULL
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D023803E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for DSW-16C block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.38 Data Set Block (DSET)> D2-163

D2.38 Data Set Block (DSET)

The Data Set Block (DSET) is used as buffers for engineering unit data entered from the
operation and monitoring functions.

n Data Set Block (DSET)

▼ Connection
The Data Set Block (DSET) is a function block that outputs the engineering unit data entered
from the operation and monitoring functions.
Here is a function block diagram of Data Set Block (DSET).

SV Velocity limiter OUT

D023901E.ai

Figure Function Block Diagram of Data Set Block (DSET)

The following table shows the connection types and connection destinations of the I/O terminals
of Data Set Block (DSET).
Table Connection Types and Connection Destinations of the I/O Terminals of Data Set Block (DSET)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
Setting
OUT x x x x
output
D023902E.ai

x: Connection available
Blank: Connection not available

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.38 Data Set Block (DSET)> D2-164

n Functions of Data Set Block (DSET)

The DSET block performs input processing, calculation processing, output processing, and alarm
processing.
The only processing timing available for the DSET block is a periodic startup. Selections
available for the scan period used to execute a periodic startup include the basic scan period, the
medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the DSET block,
see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of Data Set Block (DSET)

The DSET block outputs arbitrary engineering unit data that is input via the operation and
monitoring function using its calculation algorithm and setup parameters.

n Calculation Algorithm
▼ Output Velocity Limiter
The Data Set Block (DSET) outputs the data setpoint (SV) entered via key operation from the
operation and monitoring functions. The output is restricted by velocity limiting processing.

The output velocity limiter value is set on the Function Block Detail Builder.
• Output Velocity Limiter:
The allowed change per scan in the calculated output value (CPV).
The default is the scale span value.

n Set Parameters
The parameters of Data Set Block (DSET) are shown as follows.
• Data setpoint (SV):
An engineering unit data value
• Data setpoint high limit (SVH):
An engineering unit data value
• Data setpoint low limit (SVL):
An engineering unit data value

When setting the data setpoint (SV) from the operation and monitoring functions, if the set data
setpoint (SV) exceeds the data setpoint high or low limit (SVH, SVL), a confirmation message
appears, the content of the setting becomes effective when the operator performs confirmation
operation.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.38 Data Set Block (DSET)> D2-165

n Data Items – DSET

Table Data Items of Data Set Block (DSET)
Entry Permitted
Data Item Data Name Range Default
or Not
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
SV Data setpoint x SV engineering unit value SL
SVH Data high - limit setpoint x Value in the same engineering unit as SV SH
SVL Data high - low setpoint x Value in the same engineering unit as SV SL
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
SH CPV scale high limit Value in the same engineering unit as SV -----
SL CPV scale low limit Value in the same engineering unit as SV -----
D023903E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted

SEE
ALSO For a list of valid block modes for DSET block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.39 Data Set Block with Input Indicator (DSET-PVI)> D2-166

D2.39 Data Set Block with Input Indicator

(DSET-PVI)
Data Set Block with Input Indicator (DSET-PVI) is used when the function of the data set
block (DSET) and Input Indicator Block (PVI) applied to regulatory control are required
simultaneously.

n Data Set Block with Input Indicator (DSET-PVI)

▼ Connection
The Data Set Block with Input Indicator (DSET-PVI) is a function block that has the function of
the Data Set Block (DSET) as well as that of the Input Indicator Block (PVI) used for regulatory
control.
This block performs the following two different processing simultaneously:
• Outputs arbitrary engineering unit data entered from the operation and monitoring functions.
• Indicate input signals sent from Process I/O and other function blocks.

Here is a function block diagram of the Data Set Block with Input Indicator (DSET-PVI).

Input Velocity
IN CPV SV OUT
processing limiter

(CPV, ∆CPV, SV, ∆SV)

SUB
D024001E.ai

Figure Function Block Diagram of Data Set Block with Input Indicator (DSET-PVI)

The following table shows the connection types and connection destinations of the I/O terminals
of Data Set Block with Input Indicator (DSET-PVI).
Table Connection Types and Connection Destinations of the I/O Terminals of Data Set Block with Input
Indicator (DSET-PVI)
Connection type Connection destination
I/O terminal Data Condition Status Terminal Process Software Function
Data setting
reference testing manipulation connection I/O I/O block
Calculation Δ
IN x x x
input
Calculation
OUT x x x x
output
Auxiliary Δ
SUB x x x
output
D024002E.ai

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

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.39 Data Set Block with Input Indicator (DSET-PVI)> D2-167

n Functions of Data Set Block with Input Indicator (DSET-PVI)

The DSET-PVI block performs input processing, calculation processing, output processing, and
alarm processing.
The only processing timing available for the DSET-PVI block is a periodic startup. Selections
available for the scan period used to execute a periodic startup include the basic scan period, the
medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of input processing, output processing, and alarm processing possible for the DSET-PVI
block, see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the input processing, see the following:
C3, “Input Processing”
• For details on the output processing, see the following:
C4, “Output Processing”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of Data Set Block with Input Indicator (DSET-PVI)

The DSET-PVI block performs computation using its calculation algorithm and setup parameters.

n Calculation Algorithm
▼ Output Velocity Limiter
The data setpoint (SV) set by the operation and monitoring functions is output under the
restriction of velocity limiting processing.
The value input from the IN terminal is converted to the calculated output value (CPV) and
displayed.

The output velocity limiter value is defined in the Function Block Detail Builder.
• Output Velocity Limiter:
The allowed change per scan in the calculated output value (CPV).
The default is the scale span value

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.39 Data Set Block with Input Indicator (DSET-PVI)> D2-168

n Set Parameters
The parameters of the Data Set Block with Input Indicator (DSET-PVI) are shown as follows.
• High-high limit alarm setpoint (HH):
An engineering unit data value.
• Low-low limit alarm setpoint (LL):
An engineering unit data value.
• High-limit alarm setpoint (PH):
An engineering unit data value.
• Low-limit alarm setpoint (PL):
An engineering unit data value.
• Velocity limit alarm setpoint (VL):
An engineering unit data value within the span of 0 to ± CPV.
• Data setpoint (SV):
An engineering unit data value.
• Data setpoint high limit (SVH):
An engineering unit data value.
• Data setpoint low limit (SVL):
An engineering unit data value.
When setting the data setpoint (SV) from the operation and monitoring functions, if the set data
setpoint (SV) exceeds the data setpoint high or low limit (SVH, SVL), a confirmation message
appears, the content of the setting becomes effective when the operator performs confirmation
operation.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.39 Data Set Block with Input Indicator (DSET-PVI)> D2-169

n Data Items – DSET-PVI

Table Data Items of Data Set Block with Input Indicator (DSET-PVI)
Entry Permitted
Data Item Data Name Range Default
or Not
MODE Block mode x ----- O/S (MAN)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
CPV Calculated input value Δ (*1) Value in the same engineering unit as CPV SL
SUM Totalizer value Value in the same engineering unit as CPV 0
SV Data setpoint x Real quantity SL
SVH Data high - limit setpoint x Real quantity SH
SVL Data low - limit setpoint x Real quantity SL
HH High - high limit alarm setpoint x Value in the same engineering unit as CPV SH
LL Low - low limit alarm setpoint x Value in the same engineering unit as CPV SL
PH High - limit alarm setpoint x Value in the same engineering unit as CPV SH
PL Low - limit alarm setpoint x Value in the same engineering unit as CPV SL
VL Velocity limit alarm setpoint x 0 to ± CPV span (SH - SL)
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
SH CPV scale high limit Value in the same engineering unit as CPV -----
SL CPV scale low limit Value in the same engineering unit as CPV -----
D024003E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

SEE
ALSO For a list of valid block modes for DSET-PVI block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.40 One-Batch Data Set Block (BDSET-1L)> D2-170

D2.40 One-Batch Data Set Block (BDSET-1L)

The One-Batch Data Set Block (BDSET-1L) is used to set numeric batch set data for a
single batch in a group or by selecting items.

n One-Batch Data Set Block (BDSET-1L)

▼ Connection
The One-Batch Data Set Block (BDSET-1L) is a function block that selects and outputs arbitrary
numeric batch set data using a command switch (SW).
By using the command switch (SW), various setpoint values and control parameters for the
feedback control loop in the batch control loop, as well as setpoint values of the timer and counter
used for sequence control can be set.
In the One-Batch Data Set Block (BDSET-1L), the batch data including numeric data only can be
stored up to 16 batch data.
Here is a function block diagram of the One-Batch Data Set Block (BDSET-1L).

Batch data 1 J01

Batch data 2 J02

Batch data 3 J03

Batch data 16 J16

Command switch SW

D024101E.ai

Figure Function Block Diagram of One-Batch Data Set Block (BDSET-1L)

The following table shows the connection types and connection destinations of the One-Batch
Data Set Block (BDSET-1L).
Table Connection Types and Connection Destinations of the I/O Terminals of One-Batch Data Set
Block (BDSET-1L)
Connection type Connection destination
I/O terminal Data Data Condition Status Terminal Process Software Function
reference setting testing manipulation connection I/O I/O block
Calculation Δ
J01 to J16 x x x
output
D024102E.ai

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

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.40 One-Batch Data Set Block (BDSET-1L)> D2-171

n Functions of 1-Batch Data Set Block (BDSET-1L)

The BDSET-1L block performs calculation processing and alarm processing.
The processing timings available for the BDSET-1L block are a periodic startup and a one-shot
startup. Selections available for the scan period used to execute a periodic startup include the
basic scan period, the medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of alarm processing possible for the BDSET-1L block, see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of 1-Batch Data Set Block (BDSET-1L)

The BDSET-1L block performs calculation processing based on the action of the command
switch (SW). In addition, it has the “setpoint value limiter function,” which is related to the
calculation processing.

n Action of the Command Switch (SW)

The One-Batch Data Set Block (BDSET-1L) performs the following processing in accordance
with the value of the command switch (SW).
Table Processing Contents of One-Batch Data Set Block (BDSET-1L)
Operation example
SW Status
Processing content Operation source
(1) Sets batch data. Operation and monitoring
0 Setting up data
(2) Switches the SW from “0” to “1.” functions
(1) Waits for the completion of setup.
1 Waiting for the batch sequence Sequence control block
(2) Switches the SW from “1” to “2.”
(1) Distributes data to the output destinations.
2 Distributing data to the output destinations BDSET-1L block
(2) Switches the SW from “2” to “3.” (*1)
(1) Waits for the completion of batch operation.
3 Operating the batch sequence Sequence control block
(2) Switches the SW from “3” to “0.”
D024103E.ai

*1: Switching of the switch position from “2” to “3” is performed automatically by the BDSET-1L block.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.40 One-Batch Data Set Block (BDSET-1L)> D2-172

n Action during Status Manipulation via Sequence Connection

When a status manipulation signal is received from other function block connected via sequence
connection, data setting is performed. However, the value of the manipulation switch (SW) will
not change.
The formats of the status manipulation command sent from other function block and the content
of the corresponding processing performed by the One-Batch Data Set Block (BDSET-1L) are
shown below.

Element symbol.ACT.n
n = 0 : All batch data (DT01 to DT16) are changed to “0.”
n = 1 to 16 : The specified data (DTnn) is set to the output destination.
n = 17 : All batch data (DT01 to DT16) are set to all output destinations.

n Set Limit Function

The set limit function is a function that limits the value of the batch data (DTnn) set from outside to
values within a specified range (between high/low limits).
If the set value is outside the high/low limit range, a setting error occurs.
The high limit value (DHnn) and low limit value (DLnn) represent the high limit and low limit of Set
data, respectively. The high limit value (DHnn) and low limit value (DLnn) must be consistent with
the range of the output destination.
The set limit function only checks the data set via the operation and monitoring functions. Data
set from other function blocks are not checked.
Setting to the output destination is performed even when batch data (DTnn) exceed the specified
limits.

n Set Parameters
The parameters of the One-Batch Data Set Block (BDSET-1L) are shown as follows.
• Batch data (DT01 to DT16):
Engineering unit data values at output destinations
• Command switch (SW):
A value between 0 and 3
• Set limit high limit (DH01 to DH16):
Engineering unit data values at output destinations
• Set limit low limit (DL01 to DL16):
Engineering unit data values at output destinations

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.40 One-Batch Data Set Block (BDSET-1L)> D2-173

n Data Items – BDSET-1L

Table Data Items of One-Batch Data Set Block (BDSET-1L)
Entry Permitted
Data Item Data Name Range Default
or Not
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
SW Command switch x 0 to 3 0
DT01 to DT16 Batch data x DLnn to DHnn 0
DH01 to DH16 Set limit high limit x Value in the unit at the connection destination 10000
DL01 to DL16 Set limit low limit x Value in the unit at the connection destination 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D024104E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted

SEE
ALSO For a list of valid block modes for BDSET-1L block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.41 One-Batch String Data Set Block (BDSET-1C)> D2-174

D2.41 One-Batch String Data Set Block

(BDSET-1C)
The One-Batch String Data Set Block (BDSET-1C) is used to set string-type batch set data
for a single batch are set in a group or by selecting items.

n One-Batch String Data Set Block (BDSET-1C)

▼ Connection
The One-Batch String Data Set Block (BDSET-1C) is a function block that selects and outputs
arbitrary string-type batch set data using a command switch (SW).
The One-Batch String Data Set Block (BDSET-1C) can store up to 16 batch data, each
containing only string data.
Here is a function block diagram of One-Batch String Data Set Block (BDSET-1C).

Batch data 1 J01

Batch data 2 J02

Batch data 3 J03

Batch data 16 J16

Command switch SW

D024201E.ai

Figure Function Block Diagram of One-Batch String Data Set Block (BDSET-1C)

The following table shows the connection types and connection destinations of the One-Batch
String Data Set Block (BDSET-1C).
Table Connection Types and Connection Destinations of the I/O Terminals of One-Batch String Data
Set Block (BDSET-1C)
Connection type Connection destination
I/O terminal Data Data Condition Status Terminal Process Software Function
reference setting testing manipulation connection I/O I/O block
Calculation Δ
J01 to J16 x x
output
D024202E.ai

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

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.41 One-Batch String Data Set Block (BDSET-1C)> D2-175

n Functions of One-Batch String Data Set Block (BDSET-1C)

The BDSET-1C block performs calculation processing and alarm processing.
The processing timings available for the BDSET-1C block are a periodic startup and a one-shot
startup. Selections available for the scan period used to execute a periodic startup include the
basic scan period, the medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of alarm processing possible for the BDSET-1C block, see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of One-Batch String Data Set Block (BDSET-1C)

The BDSET-1C block performs calculation processing based on the action of the command
switch (SW).

n Action of the Command Switch (SW)

The One-Batch String Data Set Block (BDSET-1C) performs the following processing in
accordance with the value of the command switch (SW).
Table Processing Contents of One-Batch String Data Set Block (BDSET-1C)
Operation example
SW Status
Processing content Operation source
(1) Sets batch data. Operation and monitoring
0 Setting up data
(2) Switches the SW from “0” to “1.” functions
(1) Waits for the completion of setup.
1 Waiting for the batch sequence Sequence control block
(2) Switches the SW from “1” to “2.”
(1) Distributes data to the output destinations.
2 Distributing data to the output destinations BDSET-1C
(2) Switches the SW from “2” to “3.” (*1)
(1) Waits for the completion of batch.
3 Operating the batch sequence Sequence control block
(2) Switches the SW from “3” to “0.”
D024203E.ai

*1: Switching of the switch position from “2” to “3” is performed automatically by the One-Batch String Data Set Block (BDSET-1C).

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.41 One-Batch String Data Set Block (BDSET-1C)> D2-176

n Action during Status Manipulation via Sequence Connection

Data setting is performed when a status manipulation signal is received from other function block
connected via sequence connection. However, the value of the command switch (SW) will not
change.
The format of the status manipulation command sent from other function block and the content
of the processing performed by the One-Batch String Data Set Block (BDSET-1C) are shown
below.

Element symbol.ACT.n
n = 0 : All batch data (DT01 to DT16) are replaced with null.
n = 1 to 16 : The specified data (DTnn) is set to the output destination.
n = 17 : All batch data (DT01 to DT16) are set to all output destinations.

n Set Parameters
The parameters of the One-Batch String Data Set Block (BDSET-1C) are shown as follows.
• Batch data (DT01 to DT16):
Set string data of up to 16 standard-width characters or 8 double-width characters.
• Command switch (SW):A numeric value between 0 and 3.

n Data Items – BDSET-1C

Table Data Items of One-Batch String Data Set Block (BDSET-1C)
Entry Permitted
Data Item Data Name Range Default
or Not
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
SW Command switch x 0 to 3 0
DT01 to DT16 Batch data x 16Byte -----
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D024204E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted

SEE
ALSO For a list of valid block modes for BDSET-1C block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.42 Two-Batch Data Set Block (BDSET-2L)> D2-177

D2.42 Two-Batch Data Set Block (BDSET-2L)

The Two-Batch Data Set Block (BDSET-2L) is used to set numeric-type batch data for two
batches in a group or by selecting specific items.

n Two-Batch Data Set Block (BDSET-2L)

▼ Connection
The Two-Batch Data Set Block (BDSET-2L) is a function block that selects and outputs arbitrary
batch set data using a command switch (SW).
Various setpoint values and control parameters of the feedback control loop, as well as setpoint
values of the time and counter used for sequence control can be set.
Up to 16 current batch data and up to 16 next batch data can be stored. By switching the value of
the command switch (SW), the stored next batch data can be moved to the current batch data,
or the current batch data can be set to the output destination. The Two-Batch Data Set Block
(BDSET-2L) can only set numeric data.
Here is a function block diagram of the Two-Batch Data Set Block (BDSET-2L).

Next batch data 1 Current batch data 1 J01

Next batch data 2 Current batch data 2 J02

Next batch data 3 Current batch data 3 J03

Next batch data 16 Current batch data 16 J16

SW Command switch

D024301E.ai

Figure Function Block Diagram of Two-Batch Data Set Block (BDSET-2L)

The following table shows the connection types and connection destinations of the Two-Batch
Data Set Block (BDSET-2L).
Table Connection Types and Connection Destinations of I/O Terminals of Two-Batch Data Set Block
(BDSET-2L)
Connection type Connection destination
I/O terminal Data Data Condition Status Terminal Process Software Function
reference setting testing manipulation connection I/O I/O block
Calculation Δ
J01 to J16 x x x
output
D024302E.ai

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

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.42 Two-Batch Data Set Block (BDSET-2L)> D2-178

n Functions of Two-Batch Data Set Block (BDSET-2L)

The BDSET-2L block performs calculation processing and alarm processing.
The processing timings available for the BDSET-2L block are a periodic startup and a one-shot
startup. Selections available for the scan period used to execute a periodic startup include the
basic scan period, the medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of alarm processing possible for the BDSET-2L block, see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of Two-Batch Data Set Block (BDSET-2L)

The BDSET-2L block performs calculation processing based on the action of the command
switch (SW) and batch status (NXBS). In addition, it has the “setpoint value limiter function,”
which is related to the calculation processing.

n Action of the Command Switch (SW) and Batch Status (NXBS)

The Two-Batch Data Set Block (BDSET-2L) performs the processing shown in the table below, in
accordance with the value of the command switch (SW).
The batch status (NXBS) indicates the status of the next batch data. When the value of the batch
status (NXBS) is other than “0,” it indicates that the setting of the next batch data (NX01 to NX16)
has been completed and the current batch data is ready for transfer. If the value of the batch
status (NXBS) is “0,” it indicates that the next batch data is not yet ready to be transferred to the
current batch data.
If the batch status (NXBS) is left at “0,” the Two-Batch Data Set Block (BDSET-2L) ignores the
next batch data. While the batch status (NXBS) remains “0,” the Two-Batch Data Set Block
(BDSET-2L) can be used temporarily as the One-Batch Data Set Block (BDSET-1L).
Table Processing Contents of Two-Batch Data Set Block (BDSET-2L)
Operation example
SW Status Operation from HIS
Processing content Operation source
Transferring the (1) Moves the next data to the current data.
0 next data to the (2) Switches the SW from “0” to “1.” BDSET-2L (*1)
current data (3) Sets NXBS to “0.”
Waiting for the (1) Waits for the setup to be completed. Sequence control
1 (2) Switches the SW from “1” to “2.”
batch sequence block (1) Set the next batch data from
an operation and monitoring
(1) Distributes the current data to the output
Distributing the functions, when SW is “1,” “2,”
2 destinations. BDSET-2L
current data or “3.”
(2) Switches SW from “2” to “3.”
(2) Set a value other than “0” to
Operating the batch (1) Waits for the completion of batch. Sequence control NXBS.
3
sequence (2) Switches SW from “3” to “0.” block
D024303E.ai

*1: The Two-Batch Data Set Block (BDSET-2L) transfers the next data to the current data when the command switch (SW) becomes
“0” and the value of the batch status (NXBS) becomes other than “0.” If the command switch (SW) changes to “0” when the next
batch data is yet to be set at the operation and monitoring functions, the Two-Batch Data Set Block (BDSET-2L) waits for the
value of the batch status (NXBS) to become other than “0.” When a value other than “0” is set to the batch status (NXBS) after
the next data has been set at the operation and monitoring functions, the Two-Batch Data Set Block (BDSET-2L) moves the next
data to the current data, then sets the value of the command switch (SW) to “1” to wait for the batch sequence.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.42 Two-Batch Data Set Block (BDSET-2L)> D2-179

n Action during Status Manipulation via Sequence Connection

Data setting is performed when a status manipulation signal is received from other function block
connected via sequence connection. However, the value of the command switch (SW) will not
change.
The format of the status manipulation command outputted from other function block and the
content of the processing performed by the Two-Batch Data Set Block (BDSET-2L) are shown
below.

Element symbol.ACT.n
n = 0 : All current set data are changed to “0.”
n = 1 to 16 : Only the specified current data (DTnn) is set.
n = 17 : All current set data are set.

n Set Limit Function

The set limit function is a function that limits the value of the current batch data (DTnn) and next
batch data (NXnn), both of which are set from outside, within a specified range (between high/low
limits).
If the set value is outside the high/low limit range, a setting error occurs.
The high and low limit values (DHnn, DLnn) represent the high limit and low limit of set data,
respectively. The high and low limit values (DHnn, DLnn) must be consistent with the range of the
output destination.
The set limit function only checks the data set via the operation and monitoring functions. Data
set from other function blocks are not checked.
Setting to the output destination is even allowed with the batch data (DTnn) exceeding the
specified limits.

n Set Parameters
The parameters of the Two-Batch Data Set Block (BDSET-2L) are shown as follows.
• Current batch data (DT01 to DT16): Engineering unit data values of output destinations.
Arbitrary values can be selected and set as long as they can be indicated in the double-
precision floating format. Whether the value is within the range of the output destination is
not checked during setting.
• Next batch data (NX01 to NX16): Engineering unit data values of output destinations.
Arbitrary values can be selected and set as long as they can be indicated in the double-
precision floating format. Whether the value is within the range of the output destination is
not checked during setting.
• Command switch (SW): A numeric value between 0 and 3.
• Batch status (NXBS):
An integer value other than “0” set from the operation and monitoring functions.
Automatically changes to “0” when batch data setting action is performed.
• Set limit high (DH01 to DH16): Engineering unit data values of output destinations.
• Set limit low (DL01 to DL16): Engineering unit data values of output destinations.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.42 Two-Batch Data Set Block (BDSET-2L)> D2-180

n Data Items – BDSET-2L

Table Data Items of Two-Batch Data Set Block (BDSET-2L)
Entry Permitted
Data Item Data Name Range Default
or Not
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
SW Command switch x 0 to 3 0
NXBS Batch status x Integer of 0 or higher 0
DT01 to DT16 Current batch data x DLnn to DHnn 0
NX01 to NX16 Next batch data x DLnn to DHnn 0
DH01 to DH16 Set limit high limit x Value in the unit at the connection destination 10000
DL01 to DL16 Set limit low limit x Value in the unit at the connection destination 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D024304E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted

SEE
ALSO For a list of valid block modes for BDSET-2L block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.43 Two-Batch String Data Set Block (BDSET-2C)> D2-181

D2.43 Two-Batch String Data Set Block

(BDSET-2C)
The Two-Batch String Data Set Block (BDSET-2C) is used to set string batch data for two
batches in a group or by selecting items.

n Two-Batch String Data Set Block (BDSET-2C)

▼ Connection
The Two-Batch String Data Set Block (BDSET-2C) is a function block that selects and outputs
arbitrary batch set data using a command switch (SW).
Up to 16 batch data can be stored for current output and for next output, respectively.
By changing the value of the command switch (SW), the stored next batch data can be moved to
the current batch data, or the current batch data can be set to the output destination. The Two-
Batch String Data Set Block (BDSET-2C) can only set string data.
Here is a function block diagram of the Two-Batch String Data Set Block (BDSET-2C).

Next batch data 1 Current batch data 1 J01

Next batch data 2 Current batch data 2 J02

Next batch data 3 Current batch data 3 J03

Next batch data 16 Current batch data 16 J16

SW Command switch

D024401E.ai

Figure Function Block Diagram of Two-Batch String Data Set Block (BDSET-2C)

The following table shows the connection types and connection destinations of the Two-Batch
String Data Set Block (BDSET-2C).
Table Connection Types and Connection Destinations of I/O Terminals of Two-Batch String Data Set
Block (BDSET-2C)
Connection type Connection destination
I/O terminal Data Data Condition Status Terminal Process Software Function
reference setting testing manipulation connection I/O I/O block
Calculation Δ
J01 to J16 x x
output
D024402E.ai

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

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.43 Two-Batch String Data Set Block (BDSET-2C)> D2-182

n Functions of Two-Batch Data Set Block: Strings (BDSET-2C)

The BDSET-2C block performs calculation processing and alarm processing.
The processing timings available for the BDSET-2C block are a periodic startup and a one-shot
startup. Selections available for the scan period used to execute a periodic startup include the
basic scan period, the medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of alarm processing possible for the BDSET-2C block, see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of Two-Batch Data Set Block: Strings (BDSET-2C)

The BDSET-2C block performs calculation processing based on the action of the command
switch (SW) and batch status (NXBS).

n Action of the Command Switch (SW) and Batch Status (NXBS)

The Two-Batch String Data Set Block (BDSET-2C) performs the processing shown in the table
below, in accordance with the value of the command switch (SW).
The batch status (NXBS) indicates the status of the next batch data. When the value of the
batch status (NXBS) is other than “0, “ it indicates that the setting of the next batch data (NX01
to NX16) has been completed and the current batch data is ready for transfer. If the value of the
batch status (NXBS) is “0,” it indicates that the next batch data is not yet ready to be transferred
to the current batch data.
If the batch status (NXBS) is left at “0,” the Two-Batch String Data Set Block (BDSET-2C) ignores
the next batch data. While the batch status (NXBS) remains “0,” the Two-Batch String Data Set
Block (BDSET-2C) can be used temporarily as the One-Batch String Data Set Block (BDSET-
1C).
Table Processing Contents of Two-Batch String Data Set Block (BDSET-2C)
Operation example
SW Status Operation from HIS
Processing content Operation source
Transferring the (1) Moves the next data to the current data.
BDSET-2C
0 next data to the (2) Switches the SW from “0” to “1.” (*1)
block
current data (3) Sets NXBS to “0.”
Waiting for the (1) Waits for the setup to be completed. Sequence control
1
batch sequence (2) Switches the SW from “1” to “2.” block (1) Set the next batch data from
an operation and monitoring
(1) Distributes the current data to the output
Distributing the BDSET-2C functions, when SW is “1,” “2,”
2 destinations.
current data block or “3.”
(2) Switches SW from “2” to “3.”
(2) Set a value other than “0” to
Operating the batch (1) Waits for the completion of batch. Sequence control NXBS.
3
sequence (2) Switches SW from “3” to “0.” block
D024403E.ai

*1: The Two-Batch String Data Set Block (BDSET-2C) transfers the next data to the current data when the command switch (SW)
becomes “0” and the value of the batch status (NXBS) becomes other than “0.” If the command switch (SW) changes to “0” when
the next batch data has yet to be set at the operation and monitoring functions, the Two-Batch String Data Set Block (BDSET-2C)
waits for the value of the batch status (NXBS) to become anything other than “0.” When a value other than “0” is set to the batch
status (NXBS) after the next data has been set at the operation and monitoring functions, the Two-Batch String Data Set Block
(BDSET-2C) moves the next data to the current data, then sets the value of the command switch (SW) to “1” to resume the batch
sequence.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.43 Two-Batch String Data Set Block (BDSET-2C)> D2-183

n Action during Status Manipulation via Sequence Connection

Data setting is performed when a status manipulation signal is received from other function block
connected via sequence connection. However, the value of the manipulation switch (SW) will not
change.
The format of the status manipulation command outputted from other function blocks and the
content of the processing performed by the Two-Batch String Data Set Block (BDSET-2C) are
shown below.

Element symbol.ACT.n
n = 0 : All current set data are replaced with a null.
n = 1 to 16 : Only the specified current data (DTnn) is set.
n = 17 : All current set data are set.

n Set Parameters
The parameters of the Two-Batch String Data Set Block (BDSET-2C) are shown as follows.
• Current batch data (DT01 to DT16):
Set string data of up to 16 standard-width characters or 8 double-width characters.
• Next batch data (NX01 to NX16):
Set string data of up to 16 standard-width characters or 8 double-width characters.
• Command switch (SW):
A numeric value between 0 and 3.
• Batch status (NXBS):
An integer value other than “0” set from the operation and monitoring functions.
Automatically changes to “0” when batch data setting action has been performed.

n Data Items – BDSET-2C

Table Data Items of Two-Batch String Data Set Block (BDSET-2C)
Entry Permitted
Data Item Data Name Range Default
or Not
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
SW Command switch x 0 to 3 0
NXBS Batch status x Integer of 0 or higher 0
DT01 to DT16 Current batch data x 16Byte -----
NX01 to NX16 Next batch data x 16Byte -----
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D024404E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted

SEE
ALSO For a list of valid block modes for BDSET-2C block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.44 Batch Data Acquisition Block (BDA-L)> D2-184

D2.44 Batch Data Acquisition Block (BDA-L)

The Batch Data Acquisition Block (BDA-L) is used to acquire numeric batch data.

n Batch Data Acquisition Block (BDA-L)

▼ Connection
The Batch Data Acquisition Block (BDA-L) is a function block that acquires various control
parameters of the feedback control loop as well as data of the timer and counter used for
sequence control, as batch data. The Batch Data Acquisition Block (BDA-L) only acquires
numeric batch data.
Here is a function block diagram of the Batch Data Acquisition Block (BDA-L).

Acquired data 1 J01

Acquired data 2 J02

Acquired data 3 J03

Acquired data 16 J16

Command switch SW

D024501E.ai

Figure Function Block Diagram of Batch Data Acquisition Block (BDA-L)

The following table shows the connection types and connection destinations of the Batch Data
Acquisition Block (BDA-L).
Table Connection Types and Connection Destinations of I/O Terminals of Batch Data Acquisition Block
(BDA-L)
Connection type Connection destination
I/O terminal Data Data Condition Status Terminal Process Software Function
reference setting testing manipulation connection I/O I/O block
Calculation Δ
J01 to J16 x x x
output
D024502E.ai

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

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.44 Batch Data Acquisition Block (BDA-L)> D2-185

n Functions of Batch Data Acquisition Block (BDA-L)

The BDA-L block performs calculation processing and alarm processing.
The processing timings available for the BDA-L block are a periodic startup and a one-shot
startup. Selections available for the scan period used to execute a periodic startup include the
basic scan period, the medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of alarm processing possible for the BDA-L block, see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of Batch Data Acquisition Block (BDA-L)

The BDA-L block performs calculation processing based on the action of the command switch
(SW). In addition, it has the “setpoint value limiter function,” which is related to the calculation
processing.

n Action of the Command Switch (SW)

The Batch Data Acquisition Block (BDA-L) acquires engineering unit data from the connection
destinations of I/O terminals, when a value is set to the command switch (SW).
Data acquisition processing actions are shown below:
• When a value between 1 and 16 is set to the command switch (SW)
Acquire data from the I/O terminal (J01 to J16) which corresponds to the value of the
manipulation switch (SW), and changes the value of the command switch (SW) to “0.”
• When “17” is set to the command switch (SW)
Acquire data from all input terminals, and changes the value of the command switch (SW) to “0.”
• When “0” is set to the command switch (SW)
Data acquisition is not performed.

n Set Parameter
The parameters of the Batch Data Acquisition Block (BDA-L) are shown as follows.
• Command switch (SW):
An integer value between 0 and 17

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.44 Batch Data Acquisition Block (BDA-L)> D2-186

n Action during Status Manipulation via Sequence Connection

Data acquisition is performed when a status manipulation signal is received from other function
block connected via sequence connection. However, the value of the command switch (SW) will
not change.
The format of the status manipulation command output from other function block and the content
of the processing performed by the Batch Data Acquisition Block (BDA-L) are shown below.

Element symbol.ACT.n
n = 0 : All acquired data are changed to “0.”
n = 1 to 16 : Only the specified data (DTnn) is acquired.
n = 17 : All data are acquired.

n Set Limit Function

The set limit function is a function that limits the value of the batch data (DTnn), which is set from
outside of the Batch Data Acquisition Block (BDA-L), within a specified range between high and
low limits.
If the set data value is outside the high/low limit range, a setting error occurs.
The high limit value (DHnn) and low limit value (DLnn) represent the high limit and low limit of set
data, respectively.
The set limit function only checks the data set via the operation and monitoring functions. Data
set from other function blocks are not checked.
Therefore, as long as the data acquired by the Batch Data Acquisition Block (BDA-L) has been
received from the input source through normal batch data acquisition, each value is stored in the
batch data (DTnn) as is even if the limits are exceeded.

n Data Items – BDA-L

Table Data Items of Batch Data Acquisition Block (BDA-L)
Entry Permitted
Data Item Data Name Range Default
or Not
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
SW Command switch x 0 to 17 0
DT01 to DT16 Acquired data x DLnn to DHnn 0
DH01 to DH16 Set limit high limit x Value in the unit at the connection destination 10000
DL01 to DL16 Set limit low limit x Value in the unit at the connection destination 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D024503E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted

SEE
ALSO For a list of valid block modes for BDA-L block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.45 Batch String Data Acquisition Block (BDA-C)> D2-187

D2.45 Batch String Data Acquisition Block

(BDA-C)
The Batch String Data Acquisition Block (BDA-C) is to acquire string-type batch data.

n Batch String Data Acquisition Block (BDA-C)

▼ Connection
The Batch String Data Acquisition Block (BDA-C) is a function block that acquires string-type
batch data. The Batch String Data Acquisition Block (BDA-C) only acquires string-type batch
data.
Here is a function block diagram of the Batch String Data Acquisition Block (BDA-C).

Acquired data 1 J01

Acquired data 2 J02

Acquired data 3 J03

Acquired data 16 J16

Command switch SW

D024601E.ai

Figure Function Block Diagram of Batch String Data Acquisition Block (BDA-C)

The following table shows the connection types and connection destinations of the Batch String
Data Acquisition Block (BDA-C).
Table Connection Types and Connection Destinations of I/O Terminals of Batch String Data Acquisition
Block (BDA-C)
Connection type Connection destination
I/O terminal Data Data Condition Status Terminal Process Software Function
reference setting testing manipulation connection I/O I/O block
Calculation Δ
J01 to J16 x x
output
D024602E.ai

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

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.45 Batch String Data Acquisition Block (BDA-C)> D2-188

n Functions of Batch String Data Acquisition Block (BDA-C)

The BDA-C block performs calculation processing and alarm processing.
The processing timings available for the BDA-C block are a periodic startup and a one-shot
startup. Selections available for the scan period used to execute a periodic startup include the
basic scan period, the medium-speed scan period (*1), and the high-speed scan period.
*1: The medium-speed scan period can only be used for the KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For the types of alarm processing possible for the BDA-C block, see the following:
D2.3.1, “Input Processing, Output Processing, and Alarm Processing Possible for Each Calculation Block”
• For details on the alarm processing, see the following:
C5, “Alarm Processing-FCS”

l Calculation Processing of Batch String Data Acquisition Block (BDA-C)

The BDA-C block performs calculation processing based on the action of the command switch
(SW).

n Action of the Command Switch (SW)

The Batch String Data Acquisition Block (BDA-C) acquires string data from the connection
destinations of I/O terminals, when a value is set to the command switch (SW).
Data acquisition processing actions are shown below:
• When a value between 1 and 16 is set to the command switch (SW)
Acquire data from the I/O terminal (J01 to J16) which corresponds to the value of the
manipulation switch (SW), and changes the value of the command switch (SW) to “0.”
• When “17” is set to the command switch (SW)
Acquire data from all input terminals, and changes the value of the command switch (SW) to
“0.”
• When “0” is set to the command switch (SW)
Data acquisition is not performed.

n Action by Other Function Block Connected via Sequence Connection

Data acquisition is performed when a status manipulation signal is received from other function
block connected by sequence connection. However, the value of the command switch (SW) will
not change.
The format of the status manipulation command outputted from other function blocks and the
content of the processing performed by the Batch String Data Acquisition Block (BDA-C) are
shown below.

Element symbol.ACT.n
n = 0 : All acquired data are replaced with null.
n = 1 to 16 : Only the specified data (DTnn) is acquired.
n = 17 : All data are acquired.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.45 Batch String Data Acquisition Block (BDA-C)> D2-189

n Set Parameter
The set parameters of the Batch String Data Acquisition Block (BDA-C) are shown as follows.
• Command switch (SW):
An integer value between 0 and 17.

n Data Items – Batch String Data Acquisition Block (BDA-C)

Table Data Items of Batch String Data Acquisition Block (BDA-C)
Entry Permitted
Data Item Data Name Range Default
or Not
MODE Block mode x ----- O/S (AUT)
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- -----
AF Alarm detection specification ----- -----
AOFS Alarm masking specification ----- -----
SW Command switch x 0 to 17 0
DT01 to DT16 Acquired data x 16Byte -----
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D024603E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted

SEE
ALSO For a list of valid block modes for BDA-C block, see the following:
D2.3.2, “Valid Block Modes for Each Calculation Block”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.46 Inter-Station Data Link Block (ADL)> D2-190

D2.46 Inter-Station Data Link Block (ADL)

The Inter-Station Data Link Block (ADL) is used for referencing data or relaying set data
between function blocks that belong to different FCS. This function block is automatically
created when inter-station data link is specified.

n Inter-Station Data Link Block (ADL)

The Inter-Station Data Link (ADL) is a function block that relays reference data or set data
between function blocks that belong to different FCS.
In addition to simple data reference and data setting, this block can be used for cascade
connection between controller function blocks.
Here is a function block diagram of the Inter-Station Data Link Block (ADL).

Reference data 1
SET1
Set data 1

Reference data 2
SET2
Function block
Set data 2
of other control station

Reference data 8
SET8
Set data 8

D024701E.ai

Figure Function Block Diagram of Inter-Station Data Link Block (ADL)

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.46 Inter-Station Data Link Block (ADL)> D2-191
Even in the case of connection between function blocks that belong to different FCS, if a
connection is specified using the same method for connecting function blocks belonging to
the same FCS, the Inter-Station Data Link Block (ADL) is automatically created and inserted
between the function blocks specified for the connection. The Inter-Station Data Link Block (ADL)
is created on the FCS with the function block that is the source of reference or setting.
However, the Inter-Station Data Link Block (ADL) will not be created if any of the following
connection methods is used:
• Sequence connection (condition testing, status manipulation)
• Referencing from or setting to a process I/O and word data of a communication I/O other
than contact I/Os
• Terminal connection to a switch block (SW-33, SW-91)
• Data link from the connection terminal which corresponds to the block mode or status of a
faceplate block
• Connection to an alarm input terminal of a Representative Alarm Block (ALM-R)
• Setting character string data (Character string data may be referenced.)
• Connecting with OUT terminal of FOUNDATION fieldbus Faceplate Block.

TIP
After downloading the engineering data in which portions not relating to the Inter-Station Data Link Block (ADL)
have been modified by a builder, a difference may be detected, indicating that some changes have occurred
to the Inter-Station Data Link Block (ADL). This difference is generated because the inter-station data link is
recreated dynamically.

Function blocks in the control stations belonging to different projects can be connected in the
same way as for inter-station connection in the same project by using a multiple-project tag name
for the tag name of that function block. However, the HIS must be installed with the Multiple-
Project connection packages.
Multiple-project tag names are specified in the following format:
tag name@project ID

Project ID can be defined on the Multiple-Project Connection builder for the upper level project.
The project ID can not be more than two alphanumeric characters. The maximum number of
characters that can be used for the entire multiple-project tag name is 16, including the @ mark
and the project ID.
An example of inter-station connection using Multiple-Project tags is illustrated as follows.
Project ID = P1 Project ID = P2

TIC101 OUT
FIC001@P2.SET TIC101@P1.OUT
PID
SET
FIC001
PID

TI102 IN TI002
TI102@P1.PV
PVI PVI

D024702E.ai

Figure Example of Inter-Station Connection Using Multiple-Project Tag Names

SEE
ALSO For more information about calling the tags that have identical tag names among the multiple projects, see the
following:
“n Identical Tag Names” in M7.2.1, “Operation and Monitoring Multiple Projects”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.46 Inter-Station Data Link Block (ADL)> D2-192

n Control Action
Three types of processing are available with the Inter-Station Data Link Block (ADL): “data
reference only,” “data setting only” and “data reference and setting.”
Which processing is performed is determined automatically in accordance with the data that
has been linked when I/O connection was specified in the Function Block Detail Builder. The
processing types and corresponding I/O connections are shown below.
Processing type: I/O connection
Data reference: Data reference connection
Data reference and setting: Data setting connection, cascade connection
Data setting: Data setting connection from a specific function block

The cycle of periodic communication processing (processing timing) performed by the Inter-
Station Data Link Block (ADL) is specified by the FCS Constants Builder for each FCS to which
the Inter-Station Data Link Block (ADL) belongs.
When the communication error occurs, NCOM (communication failure) is transmitted as the data
status to the function blocks or the data buffers connect to it.
Communication failure alarm is initiated only when the communication error occurred for a
specified number of times. So far, this specified number is fixed as 1, i.e., the alarm occurs
whenever the error is detected.

l Data Reference
When processing type is “reference” or “reference and setting,” data is referred from the specified
reference destination. An example of data reference action is shown below.
Referencing function block ADL Other Referenced function block
control station

PV IN SETn Reference data n DATA

D024703E.ai

Figure Data Reference Action of Inter-Station Data Link Block (ADL)

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.46 Inter-Station Data Link Block (ADL)> D2-193
l Data Setting
When processing type is “setting” or “reference and setting,” data is set to the specified
setting destination. When data with data status is set, its data status is transmitted just like the
connection between function blocks that both belong to the same FCS.
Before setting data, function blocks read back the set data. This readback action is also
performed when data is set between different FCS. Therefore, data reference (readback) is
performed to every data specified for “reference and setting” prior to setting. The referenced
value in this readback action is returned when a readback request is received from the setting
source function block.
The data set examples in the case of data setting connection are shown as follows.
Data setting source ADL Other Data setting destination
function block control station function block
Reference data n
MV OUT SETn DATA
Set data n

D024704E.ai

Figure Data Setting Action

Upstream block ADL Other Downstream block

in cascade control station in cascade
Reference data n
MV OUT SETn SET CSV
Set data n

D024705E.ai

Figure Cascade Connection

IMPORTANT
When the cascade connection between controller function blocks involves different FCS, use the
Inter-Station Data Link Block (ADL) in accordance with the following conditions.
• Set the control output action type of the upstream function block in cascade to “positional.”
• The control period of the upstream function block in cascade should be set longer than the
inter-station communication period.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.46 Inter-Station Data Link Block (ADL)> D2-194
l Inter-Station Communication Period
▼ Inter-Station Data Link Communication Period
The inter-station communication period is a time required to complete all inter-station data link
processing within a FCS. It is specified in the FCS Constants Builder as a FCS-specific constant.
The default is one second.
During inter-station data link processing, inter-station data link processing at all points is
completed within the time in seconds corresponding to the “inter-station communication period.”
The number of inter-station communications points executed in one second is shown below.
Points obtained by rounding up the result of the following equation to the nearest multiple of 8.
(Effective inter-station data link points)
(round up by every 8 points)
(Inter-station communication period)
D024706E.ai

The effective inter-station data link points are the points of the inter-station data link actually wired
in Control Drawing Builder or in Function Block Detail Builder or in Function Block Overview
Builder within each FCS. When the definition (wire connection) of the inter-station data link is
changed, the inter-station data link points to be processed in one second will be set again based
on the set inter-station data link points.

TIP
When the inter-station communication period is changed, offline downloading will be required.

l Re-Transmission Skip when Communication Error Detected

▼ Re-Transmission Skip when Inter-Station Data Link Error 
When a communication error is detected during inter-station data link processing, inter-station
communication transmission skips for a period of time then retry the transmission in the interval
of this skip period. This re-transmission skip period is expressed as follows:

Re-transmission skip period =

(Inter-station communication period) • (re-transmission skip times)

The re-transmission skip times can be defined in the FCS Constants Builder as a FCS constant.
The default is 60.
If the inter-station communication period extends, the re-transmission skip period extends
accordingly.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-195

D2.47 General-Purpose Arithmetic Expressions

The general-purpose arithmetic expression description language is a programming
language to describe the arithmetic algorithm of the general-purpose calculation blocks
(CALCU, CALCU-C).

n General-Purpose Arithmetic Expressions

The general-purpose arithmetic expressions are used in order to define the calculation algorithm
of the general-purpose calculation blocks (CALCU, CALCU-C).
The following section describes the features of the general-purpose arithmetic expressions.
• Data items of an arbitrary function block can be referred to or set through the I/O terminal of
the general-purpose calculation blocks (CALCU, CALCU-C).
• Arithmetic expressions which handle character strings such as messages and block mode
can be described.
• Processing such as conditional jumps can be described by using control statements.
• Built-in functions which execute calculations for the temperature correction or pressure
correction, etc., can be used.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-196

D2.47.1 Basic Items of the General-Purpose Arithmetic

Expressions
This section explains the basic items of the general-purpose arithmetic expressions.

n Identifiers in the General-Purpose Arithmetic Expressions

▼ Basic of Arithmetic Calculation Description
The identifiers in the general-purpose arithmetic expressions are the character strings that
represent the arithmetic expressions and variables and labels used by arithmetic expressions.
Various variables used by the labels of the arithmetic expressions or in the arithmetic expressions
require identifiers. They cannot become the object of calculation without identifiers.
The names of the identifiers have the following restrictions:
• Only the following characters are allowed to use; alphabet (A to Z and a to z), numbers (0 to
9), “_” (underscore), “$”, and “%.”
• Use an alphabet or “%” for the first character of the identifier name.
• Even though there is no limit to the length of the identifier, only the first eight characters are
valid for identification. Identifiers that have the same first eight-characters are treated as the
same identifier.
• Upper case and lower case of the alphabets are not distinguished.
• The identifiers which are defined as reserved words for the numerical calculation
expressions cannot be used other than the reserved purposes.

SEE
ALSO For the reserved words of the general-purpose arithmetic expression, see the following:
D2.47.9, “Reserved Words for Numerical and Logical Arithmetic Expressions”

n Configuration of the General-Purpose Arithmetic Expression

The general-purpose arithmetic expression consists of a program statement, which indicates the
start of an arithmetic expression; declaration statement, which declares variables; executable
statements, which execute calculations; and an end statement, which indicates the end of an
arithmetic expression.
The program statement and end statement can be omitted.
The following lines give the example of the order that each statement in the arithmetic
expression:
program
declaration statement
executable statement
end

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-197
l Express in Multiple Lines
When one statement is too long and does not fit in one line, use “\” or “//” in the end of the line.
One statement can be written in multiple lines if “\” or “//” is followed by a line break.
The following example shows a statement in multiple lines:
program
{PIC100.MODE.MAN)=//
{TIC100.ALRM.HI}
{SW100.SV.3}=\
{TIC100.MODE.AUT}
end

l Comment
When a line is headed by a “*” mark, the contents of the entire line are treated as a comment.
When “!” mark appears in the middle of a line, the texts from the right-hand side of “!” mark till the
end of the line are treated as a comment.
The following examples show a comment and a comment statement:
program !This portion is comment.
*This line is for comment.
if ({SW100.SW.3})then

l Label
A label can be attached to a statement as a mark. A label can be used as a branch destination of
a goto statement.
The labels are written in the following format:
<identifier>:<statement>

An example of label is shown below:

program
label: if({SW100.SW.3})then

If there is no statement to the right-hand side of a label, it means that the label is for the next
statement. An example when no statement is written to the right-hand side of the label is shown
below:
program
label: i f({SW100.SW.3})then

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-198
l Maximum Number of Lines for an Arithmetic Expression
A maximum number of lines for an arithmetic expression are 250 including comment and empty
lines. Among them, only 20 lines can be used for the statement descriptions. The lines listed
below, however, are excluded from the statement description lines:
• Program, end, else, end if, case, otherwise, end switch, labels, comments, and lines that
consist of declaration statements only.
• The second line and thereafter of a statements where ended with “\” or “//” mark.
• Empty lines

When a “case” statement and another statement are written in the same line, such as “case 1:
i=1,” the line is treated as a statement line.

l Engineering Index
Even if the statement is written in 20 lines or less, a capacity overflow error may occur during the
compilation. This phenomenon occurs due to the limitation on the used variables, constants and
the number of operators.
The possibility of a capacity overflow error is lowered if approximately 20 lines of assignment
statements with four terms, as shown below, are written:

A = A1 + A2 + A3 + A4

n Data Types of the General-Purpose Arithmetic Expression

The variables used in the general-purpose arithmetic expression have the same data types as
other programming languages.
The data types of variables are as follows:
Data type Character string type (char*n)

Numerical value type Integer type Integer (integer)

Long integer (long)

Real type Single-precision floating point (float)

Double-precision floating point (double)

D024801E.ai

Figure Data Types

Range of values for each data type is shown below.

Table Data Type
Data type Bits Minimum value Maximum value
Character string (*1) 8•n Not applicable Not Applicable
Integer 16 -32768 32767
Long integer 32 -2147483648 2147483647
Single-precision floating point (*2) 32 -3.402823 • 10 38 3.402823 • 10 38
Double-precision Floating point (*3) 64 -1.79769313486231 • 10 308 1.79769313486231 • 10 308
D024802E.ai

*1: 16 bytes maximum for a character string

*2: The number of digits may be displayed for a single-precision floating point is seven.
*3: The number of digits may be displayed for a double-precision floating point is fifteen.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-199
The bit format of data for each data type is shown below. Integers and the mantissa part of real
numbers are two’s complement representation.
char*n

1st byte nth byte

integer

Integer 15 bits

Sign bit (1 bit) 0: Positive 1: Negative

long

Integer 31 bits

Sign bit (1 bit) 0: Positive 1: Negative

float
Exponent field Mantissa field
(E) 8 bits (M) 23 bits

Sign bit (S) 1 bit

The value is given by the following formula:
(-1) S • 2e-127•1.M

double
Exponent field Mantissa field
(E) 11 bits (M) 52 bits

Continuation of the mantissa field (M)

Sign bit (S) 1 bit

The value is given by the following formula:
(-1) S • 2e-1023•1.M
D024803E.ai

Figure Data Format of Each Data Type

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-200

D2.47.2 Constants in General-Purpose Arithmetic Expressions

Constants in general-purpose arithmetic expressions are character strings which
represent values themselves. Three kinds of constants can be used, as follows:
Integer constant (10, 20, etc.)
Floating-point constant (1.5, 100.0, 1.5E10, etc.)
Character string constant (“ABC”, “character string”, etc.)

n Integer Constants in General-Purpose Arithmetic Expressions

▼ Constant
The integer constants are the constants represented by integers.
The data type of integer constant is the long type. An integer constant can be represented by a
decimal number or a hex number. It is normally represented by a decimal number. When the hex
notation is used, add “$” at the beginning of a constant.
A decimal integer constant is represented by characters “0” through “9”. In addition to the
numbers, alphabets between “A” and “F” as well as between “a” and “f” are used for the hex
notation.
Examples of constants are as follows:
• Decimal integer constants: 5 10 65535
• Hex integer constants: $5 $A $FFFF

n Floating-Point Constants in the General-Purpose Arithmetic

Expressions
The floating-point constants are the constants represented by the mantissa field and exponent
field.
The data type of floating-point constants is the double type. Only the decimal notation is allowed
for the floating point.
The following shows the expression methods of the floating point:
• Describe a decimal number with a decimal point.
• Describe in the <mantissa field>E<exponent field> format or <mantissa field>e<exponent
field> format.
<Mantissa field>: A decimal number with or without decimal point.
<Exponent field>: A decimal number without or with a sign.
When the <mantissa field> is x and the <exponent field> is y, the value of the constant is x • 10y.

The following shows examples of floating-point constants:

• Description of a decimal number with decimal point:
1.0, 15.8, 0.05
• Description in the <mantissa field>E<exponent field> format or <mantissafield>
e<exponent field> format.
1.0E5, 1.0e-5, 123E3

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-201

n Character String Constants in General-Purpose Arithmetic

Expressions
The character string constant is a constant that can represent a character string. A character
string constant can use both single-byte characters and double-byte characters.
A character string constant is represented by a character string enclosed by double quotes (“”).
The double quotations, line break, horizontal tab and back slash have to be replaced by the
following character strings:
Table Notations of Special Characters
Special character Symbol Notation
Line break NL \n
Horizontal tab HT \t
Back slash \ \\
Double quote ” \”
D024804E.ai

Examples of the character string constants are as follows:

“abc”, “This is a character string”
“character string”, “1-st line\n2-nd line\n3-rd line”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-202

D2.47.3 Variables
A variable is a data which has a name and data type. A value can be referred to and set by
a variable.
There are two kinds of variables: I/O variables and local variables.

n I/O Variables of the General-Purpose Arithmetic Expressions

▼ Variables
The I/O variables are data items of the General-Purpose Calculation Block (CALCU, CALCU-C),
such as the calculated input value (RVn), calculation output value (CPVn), parameter (Pn), etc.
The data type of the calculated input value (RVn) and calculation output value (CPVn) is
automatically determined by the data item of the connection destination. In addition, the data type
of the parameter (Pn) is automatically determined by the type of the general-purpose calculation
block and the data item. It is not necessary to declare the parameter (Pn), which is used as the
I/O variable, in the arithmetic expression.

TIP
• The block mode and alarm status are integer data.
• The size of the character string I/O variable is 16 bytes.

l Usage of I/O Variables

The I/O variables are used for referring to or setting data of the connection destination of the I/O
terminal.

l When Referencing by Wiring the I/O Terminals

If the I/O terminals are connected to other function blocks using the Function Block Detail Builder,
the data of other function blocks can be referred or set by way of I/O variables.
In order to refer or to set an I/O variable, use the data item name that corresponds to the
connected I/O terminal.
A maximum of eight input variables and four output variables can be declared by wiring the I/O
terminal.
Data reference Data setting

CALCU
IN
RV

PVI θ01
IN OUT
PV RV1 CPV=RV+RV1+RV2 CPV

θ02
PVI RV2
IN
PV

D024805E.ai

Figure Example of I/O Variables and Arithmetic Expression when Wired by the Builder

TIP
• When the same data is connected to the input connection terminal and output connection terminal,
separate input variable and output variable are allocated.
• The I/O variables can be used in an expression. However, input variables (RV, RV1, RV2, ...) cannot be
used on the left-hand side of the assignment statement.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-203
l When the Data of Other Function Block is Specified by an Element Symbol
Data of other function block can be specified by an element symbol and data item name.
A maximum of 24 input variables and 12 output variables can be declared as element symbol
and data item name.
There are three kinds of formats for handling the data of other function block (connection
information) in arithmetic expressions, as follows:
• Data connection (Data reference and setting)
<element symbol>.<data item name>
• Sequence connection (Data value reference and data value modification)
{<element symbol>.<data item name>.<condition specification|operation specification>}
• Sequence connection (Data status reference)
{<element symbol>.<data item name>=<condition specification>}

When a tag name is used as the element symbol, if a tag name starts with a number or “-” sign,
the computation may not be correct. Define an alias to use the tag.

The element symbols and data item names represent the data from other blocks can be
assigned to variables by compiler. The data items assigned to variables according to the
following conditions:
• If the data of other function block is written on the left-hand side of an assignment statement,
it is assigned to an output variable.
• If the data of other function block is written both on the left-hand side of an assignment
statement, it is assigned to an input variable.
• If the same data as other function block is written both on the left-hand side of an
assignment statement and another place in the data connection format, it is assigned to an
output variable.
• If the same data as other function block is written both on the left-hand side of an
assignment statement and another place in the sequence connection format, it is assigned
to a separate input variable and output variable.
• If the data of another function block is written at a place other than the left-hand side of
an assignment statement in the sequence connection format, the condition testing of the
sequence connection is always executed even if the statement is not executed.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-204
l Data Connection Using the Element Symbol (Data Reference and Setting)
The following example shows an arithmetic expression by which the data reference and setting
of other function block are executed, using the element symbol.
program
TIC100.VN=FIC100.CPV*0.1
end

The second line is a statement which sets the calculation output value (CPV) of FIC100 multiplied
by 0.1 to the I/O compensation value (VN).
When data reference and setting of other function block are executed by using the element
symbol instead of terminal connected by the Function Block Detail Builder, the following
restrictions apply:
• Connection between terminals and connection between stations cannot be specified
because the connection is not established by the builder.
• The I/O variable that the element symbol is assigned to is unknown, because the compiler
automatically assigns the element symbol to the I/O variable other than RV, RV1 through
RV7, CPV, CPV1 through CPV3.

l Sequence Connection Using the Element Symbol (Data Value Reference and
Data Value Modification)
The following example shows an arithmetic expression which executes the sequence connection
with other function block using the element symbol.
program
{PIC100.MODE.MAN}={TIC100.ALM.HI}
{SW100.SV.3}={TIC100.MODE.AUT}
end

The second line is a statement which changes the block mode of PIC100 to MAN when the alarm
status of TIC100 is HI.
The third line is a statement which modifies the signal path by changing SV of the selector switch
to 3 when the block mode of TIC100 is in the automatic (AUT) mode.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-205
l Sequence Connection by Using the Element Symbol
(Data Status Reference)
The following example shows an arithmetic expression for a sequence connection by using the
element symbol.
program
if({SW100.SW.3})then
{PIC100.MODE.AUT}={CAL100.ACT.ON}
end if
end

The second line is an “if” statement which tests whether SV of the selector switch is 3 or not.
The third line is a statement executed when the if statement in the second line is true. In this
statement, the block mode of PIC100 is switched to the automatic (AUT) mode when the CAL100
block is started by a one-shot command.
The one-shot command to start the CAL100 might be triggered by any other blocks or occurs at
the time even before this block starts. It is irrelevant to this calculation block. In the other word,
the CAL100 started by the one-shot command have no relation with statement in the second line
in this calculation block.
On the contrary, the statement on the left-hand side which changes PIC100 to AUT is not
executed unless the result of the if statement in the second line is true and the third line condition
written at right-hand side is true at the same time.

n Local Variables in General-Purpose Arithmetic Expressions

The local variables in a general-purpose arithmetic expression are the variables declared in
the function block. They can be used only in the general-purpose calculation block where they
were declared. In order to use local variables, use them as intermediate variables after declaring
the type. The local variables do not retain values from the previous execution of the arithmetic
expression. In addition, the initial value is undefined. A maximum of ten local variables can be
used in one general-purpose arithmetic expression.

l Declaration of Local Variables

The local variables are declared as follows:

<type specifier><variable name>[,<variable name> .. ]

• <type specifier>: Specify the variable type.

The type specifiers include char *n, integer, long, float, and double. Use char *n as the
type specifier to declare a character string. By using this description, it is possible to use a
character string variable which is capable of expressing a character string of a maximum of
n bytes.
• <variable name>: Specify a variable name as the identifier.
When multiple variable names are listed and separated by commas, more than one variable
of the same data type can be declared at once.

TIP
• Specify the number of bytes, n, of the character string when a character string variable is declared. When
a character string variable where characters which require two bytes per character, such as the Japanese
character code, are stored, specify a value n by taking characters that require two bytes into account.
• The maximum size of local variable of the character string type is sixteen bytes.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-206
l Implicit Declaration of Local Variables
When an undeclared variable is encountered, the data type of the variable is automatically
decided based on the first character of the variable name, and the variable is treated as a local
variable. This is called implicit declaration.
The relationship between the first character of the local variable name and the data type is as
follows:
• I: Integer
• L: Long integer
• F: Single-precision floating point
• C: Character string
• Others: Double-precision floating point

If the compiler control command, #implicit none is given, the implicit declaration of the local
variable is disabled. Then a compiler error occurs if a variable not declared is used.
Use the “#implicit none” instruction between the program statement and the end statement.

n Tag Name of the General-Purpose Arithmetic Expressions

When an undeclared variable name is followed by “.” (period), the variable is treated as a tag
name.
When an arithmetic expression is compiled, whether or not the tag name has been defined by the
builder before is checked. A compiler error occurs if the tag name has not been defined.
In addition, the arithmetic expression cannot be compiled correctly if a tag name that starts with
a number or includes “-” (hyphen) even if the tag name has been registered. To define an alias or
replace the tag name with the one does not start with a number and does not include “-.”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-207

n Alias Definition of the General-purpose Arithmetic Expressions

Alias definition is to substitute the name of an I/O variable with another character string. When an
alias of input variable is defined, I/O variables and data of other function block can be handled by
different name in the arithmetic expression. Write alias definitions at the beginning of arithmetic
expression.
The format of the alias definition is as follows:

alias <alias><word list>

How to write the word list is shown below.

Table Word List of Alias Definition
Type of word list Format of word list Description example
Input variable RV, RV1 to RV7 alias FLOW RV1
Output variable CPV, CPV1 to CPV3 alias HOSEI CPV
Data connection <element symbol>.<data item> alias PRESS FIC001.PV
{<element symbol>.<data alias SEQ1 {TAG001.MODE.AUT}
item>.<condition specification>}
{<element symbol>.<data alias SEQ2 {TAG002.MODE.AUT}
item>.<operation specification>}
Sequence connection
{<element symbol>.<data item> alias SEQ3 {TAG003.PV=BAD}
=<condition specification>}
{<element symbol>.<data item> alias SEQ4 {TAG004.PV=CAL}
=<operation specification>}
D024806E.ai

An example of arithmetic expression which includes alias definitions is shown below:

program
alias FLOW RV1
alias HOSEI CPV1
HOSEI=FLOW*0.1
end

An example of arithmetic expression which uses aliases for data reference and data setting of
other function block is shown blow:
program
alias FLOW FIC100.CPV
alias HOSEI TIC100.VN
HOSEI=FLOW*0.1
end

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-208

n Character String Substitution

The character string substitution is to assign a specific character string to an identifier. Character
string substitution is executed by using the compiler control instruction, “#define.”
The format of the character string substitution is shown below:

#define<identifier><character string>

Conditions of a range which is recognized as a <character string> is as follows:

• Character string up to a line break. Continuous spaces immediately before the line break
and comment part are excluded.
• When “\” or “//” is used, the contents in the following line are recognized as a substituting
character string as well.

When the arithmetic expression is compiled, the identifier defined by the compiler control
instruction “#define” is replaced by assigned character string prior to compilation. Even if the
identifier appears in the character string, however, substitution is not performed.
An example of character string substitution is shown below:
program
#define OPEN 2
......
SI0100.MV=OPEN
SI0200.MV=OPEN
end

The “OPEN” identifier in this arithmetic expression is the substitution of “2”.

In order to define a character string which includes an arithmetic expression using the “#define”
compiler control instruction, enclose the arithmetic expression by “( )”. It might be necessary
to enclose the corresponding arithmetic expression by “( )” to obtain the desired arithmetic
expression, because the “#define” compiler control instruction is a substitution of the character
string. The following example shows an improper substitution of arithmetic expression:
program
#define MAXLEN 256
#define GOOD (MAXLEN-1)! Good example
#define BAD MAXLEN-1! Bad example
......
i1=GOOD*5!(MAXLEN-1)*5Calculated like this
i2=BAD*5!Calculated as MAXLEN-1*5, i.e., calculated as MAXLEN-(1*5)
......
end

In this example, (256-1) • 5=1275 is expected as the result of the calculation.

But, i2 is resulted in 251 incorrectly while i1 is resulted in 1275 correctly because of different
calculation priorities.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-209

D2.47.4 Operators
The following operators can be used in the general-purpose arithmetic expressions:
• Binomial operator
• Unary arithmetic operator
• Relational operator
• Equality operator
• Binary logical operator
• Unary logical operator
• Bitwise logical operator
• Bitwise shift operator

n Binomial Arithmetic Operator

▼ Operators
Calculation with a binomial arithmetic operator can be executed to any numerical data.
Usable binomial arithmetic operators are as follows:
• +: Addition
• -: Subtraction
• *: Multiplication
• /: Division
• mod: Remainder

When an integer is divided by another integer, the digits to the right of the decimal point are
truncated for the quotient.
If the operand of a mod calculation is a real number, the fractional part of the operand is rounded
off and the operand is converted to a long integer (long) type prior to the calculation.
Insert a space before and after “mod.”

n Unary Arithmetic Operator

Calculation with an unary arithmetic operator can be executed to any numerical data.
Usable unary arithmetic operators are as follows:
• +: Positive
• -: Negative

+ retain the sign of the operand.

- switch the sign of the operand from positive to negative or negative to positive.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-210

n Relational Operators
Calculation with a relational operator can be executed to any numerical data and any character
string data.
Usable unary relational operators are as follows:
• <: Smaller than
• >: Greater than
• <=: Equal to or smaller than
• >=: Equal to or larger than

The result of the calculation by a relational operator is the integer type. The value of the
calculation result becomes true (1) if the relationship between the two sides connected by the
relational operator is satisfied, or becomes false (0) if it is not satisfied.

n Equality Operators
Calculation with an equality operator can be executed to any numerical data and any character
string data.
Usable equality operators are as follows:
• ==: Equals
• <>: Not equals

The result of the calculation with the equality operator is the integer data. The value of the
calculation result becomes 1 if the relationship between the two sides connected by the
equality operator is satisfied, or becomes 0 if it is not satisfied. When both the equality operator
and relational operator are used in the same arithmetic expression, the relational operator is
evaluated first.
When a comparison of real numbers is executed by the equality operator, it is determined to be
different even if the values of both sides differ slightly. Use relational operators (>=, <=, >, <) to
compare real numbers.

n Binary Logical Operators

Calculation with a binary logical operator can be executed to any numerical data.
Usable binary logical operators are as follows:
• and: AND
• or: OR
• eor: Exclusive OR

The logical values of both sides become true if any value other than 0, and false if 0. The value of
the calculation result becomes 1 if the logical calculation result is true and 0 if false.
The calculation result is the integer type.
Insert a space before and after a binary logical operator.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-211

n Unary Logical Operator

Calculation with the unary logical operator can be executed to any numerical data.
Usable unary logical operator is as follows:
• not: Negation
The logical value of the operand becomes true if the value is anything other than 0, and false if 0.
The value of the calculation result becomes 1 if the result of the logical calculation is true, and 0 if
false.
The calculation result is the integer type.
Insert a space before and after the unary logical operator.

n Bitwise Logical Operators

Calculation with a bitwise logical operator can be executed to any numerical data.
Usable bitwise logical operators are as follows:
• &: Bitwise AND
• |: Bitwise OR
• ^: Bitwise exclusive OR
• –: One’s complement (unary operator)

If the operand of a bitwise binary logical calculation is a real number, the fractional part of the
operand is rounded off and the operand is converted to the long integer (long) type prior to
calculation.
The logical calculation is executed bit-by-bit to the values on both sides.

n Bitwise Shift Operators

Calculation by a bitwise shift operator can be executed to any numerical data.
Usable bitwise shift operators are as follows:
• <<: Leftward bit shift
• >>: Rightward bit shift
• <@: Leftward cyclic shift
• >@: Rightward cyclic shift

An example of the calculation operation when described as <expression 1><shift

operation><expression 2> is as follows:
• <expression 1> is shifted by bit or cyclic-shifted for the number of times specified by the
value of <expression 2>. Arithmetic shift is executed for the bit shift. When the bits are
shifted rightward, the original most significant bit is duplicated as the new most significant
bit. 0 is always entered to the least significant bit when the bits are shifted leftward.
• When <expression 1> or <expression 2> is the floating point type, the fractional part of the
operand is rounded off and the operand is converted to the long integer (long) type prior to
calculation.
• When <expression 1> is the integer type, the remainder of <expression 2> divided by 16 is
used as the number of shift applied to <expression 1>.
• When <expression 1> is the long type or real type, the remainder of <expression 2> divided
by 32 is used as the number of shift applied to <expression 1>.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-212

D2.47.5 Arithmetic Expressions

An arithmetic expression refers to a statement which satisfies one of the following
conditions:
• It is a function, constant, or variable.
• It is a statement which connects functions, constants and variables by an operator.
• It is a statement which connects arithmetic expressions by an operator.

n Arithmetic Expressions
▼ Arithmetic Expressions
An arithmetic expression can be described using the following format in general-purpose
arithmetic expressions:
• <function>
• <constant>
• <variable>
• (<expression>)
• <expression><binomial operator><expression>
• <unary operator><expression>
• <expression><equality operator><expression>
• <expression><relational operator><expression>
• <expression><binary logical operator><expression>
• <unary logical operator><expression>
• <expression><bitwise binary logical operator><expression>
• <bitwise unary logical operator><expression>
• <expression><bitwise shift operator><expression>

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-213

n Priority Order
The priority order of the calculations is shown in the following table:
Table Priority Order of the Calculations
Calculation Symbol (Operator) Association rule Priority
Parenthesis () Left to right Highest priority
Function Function Left to right ↑
Unary operator — (not) - (negative) + (positive) Right to left
Multiplication and division * / MOD Left to right
Addition and subtraction +- Left to right
Shift operation << >> <@>@ Left to right
Relational operator < <= > >= Left to right
Equality operator == <> Left to right
Logical operator & Left to right
Logical operator ^ Left to right
Logical operator | Left to right
Logical operator and Left to right
Logical operator eor Left to right ↓
Logical operator or Left to right Lowest priority
D024807E.ai

n Data Type Conversion

When the operands on both sides of the operator that requires two operands have different data
types, the data type of one operand is automatically converted to match the other data type which
can handle larger data. The rules of data type conversion are shown in the following table. The
table shows the data types of the operands and calculation results.
Table Data Type Conversion Rules
Right-hand side
Left-hand side integer long float double

integer I•I→I L•L→L D•D→D D•D→D

long L•L→L L•L→L D•D→D D•D→D
float D•D→D D•D→D D•D→D D•D→D
double D•D→D D•D→D D•D→D D•D→D
D024808E.ai

I: integer type
L: long type
D: double type
Note: Calculation is not allowed if the character string data and numerical data are mixed. Also, no data type conversion is executed
between the character string type and numerical type.
Note: The float type is converted to the double type unconditionally.

TIP
• If either operand is the double type, the other operand will also be converted to the double type.
Accordingly, the calculation result becomes the double type.
• If either operand is the long type and the other is integer, the other operand is converted to the long type.
The calculation result becomes the long type.
• If both operands are integer type, the calculation result remains integer type.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-214

n Comparison of Character Strings

Character strings can be compared as a character string operation. The relational operator and
equality operator can be used for character comparison. Character strings cannot be processed
by the general-purpose arithmetic expression description.

l Character String Comparison Method

The character string comparison method follows the rules below:
• The comparison of characters is executed by comparing the internal codes of the
characters. The internal codes are compared as unsigned 8-bit values.
• Spaces is subject to comparison.
• Comparison of character strings is executed character-by-character from the first character
of the left-hand side and right-hand side.

l Test Conditions of the Character String Comparison

Testing of large and small between character strings follows the rules below:
• When both sides are exactly the same character strings, the two sides are evaluated as
equal.
• When at least one character is different, the comparison starts from the character closest to
the beginning among the different characters. The character string with a character which
has a larger internal code as a result of comparison is evaluated as the larger one.
• When the lengths of the character strings are different, the longer character string is
evaluated as the larger one.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-215

n Assignment Statement
An assignment statement refers to a statement which has a variable on the left-hand side and
an expression on the right-hand side, and they are connected by the “=” symbol. An assignment
statement substitutes the left-hand side variable by the calculation result of the right-hand side
expression.
It is necessary in the assignment statement for both of the right side and left side to be the
numerical type or character string type.
The format of the assignment statement is as follows:
<variable> = <expression>

• <variable>:
Variable to which the value of <expression> calculation should be assigned.
• <expression>:
Expression that calculates the substituting value for the <variable>.

l Numerical Value Substitution

Two variables put on each side of “=” symbol forms a substitution formula.
If the data types on each side of expression are different, the data type of the right-hand side
expression is converted to the data type of the left-hand side variable.
Combinations of the left hand and right hand which may cause an overflow or loss of digits are
shown in the following table:
Table Combinations of the Left-hand Side and Right-hand Side which may Cause an Overflow or Loss
of Digits
Right-hand side
Left-hand side integer long float double

integer A A A
long A A
float B A, B
double
D024809E.ai

Blank: No problem
A: An overflow may occur.
B: Loss of digits may occur.
Note: Extend the sign of the value before assigning a value of the integer type to a long-type variable.
Note: An overflow error occurs when the substituting value exceeds the handling range for the integer type.
Note: When a variable of the integer type is substituted by a value of the real type, round off the substituting value at the first digit after
the decimal point prior to substitution. Use the “int” built-in function to truncate after the decimal point.

l Character String Substitution

When the entered character string longer than the allowed size of the character string variable,
the characters for the character string size are inserted from the beginning of the character string.
Characters which cannot fit are discarded.
When a character string shorter than the size of the character string variable is entered to a
character string variable, a terminator is added to the end of the character string. The size of
the substituted character string variable becomes the size of the character string before the
terminator.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-216

D2.47.6 Control Statements

The control statement is a statement for controlling the execution order of arithmetic
expressions. There are four kinds of control statements for testing conditions and
selections as follows:
• if statement:
Condition testing
• switch statement:
Multiple-branches processing
• goto statement:
Unconditional jump
However, jump cannot be specified if the execution of the arithmetic expression goes
backwards.
• exit statement:
Jumps to the “end” statement unconditionally.

n if
▼ Control Statements
The “if” statement is used to control the execution of arithmetic expressions by the condition(s) of
the expression.
The format of the “if” statement is shown below:

l Format 1
if (<expression>)<statement>

• <expression>:
Give the expression to be evaluated in the numerical or character string format.
• <statement>:
A statement which will be executed when the expression is true.

When the “if” statement above is executed, <expression> is calculated. <statement> is executed
only when the result of the <expression> is true (<>0).

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-217
l Format 2
if (<statement>)then
....
[else
....
]
....
end if
....

When the “if” statement above is executed, <expression> is evaluated first. Further processing
will be determined depending on the evaluation result.
• When the result of <expression> is true (<>0), after executing the statements from the one
after “then” to the one before “else”, the execution jumps to the statement after the “end
if” statement. When the “else” statement does not exist, the statements after “then” will be
executed.
• When the result of <expression> is false (==0), if the “else” statement exists, the statements
after “else” will be executed. When the “else” statement does not exist, the statements after
“end if” statement will be executed.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-218
l Format 3
if (<expression>)then
....
else if (<expression>)then
....
[else
....
]
....
end if
....

When the “if” statement above is executed, the <expression> is evaluated first. Further
processing will be determined depending on the evaluation result.
• When the result of the <expression> in the “if” statement is true (<>0), after executing the
statements starting from the statement after “then” which corresponds to <expression>, to
the statement before the “else if” statement, the execution jumps to the statement after the
“end if” statement.
• When the result of the <expression> in the “if” statement is false (==0), the conditional
expression in the next “else if” statement is evaluated.
• When the result of the <expression> in the “if” statement is false (==0) and the result of the
<expression> in the “else if” statement is true (<>0), if there is an “else if” statement after
the “then” statement, the statements starting from the one after “then” statement to the one
before “else if” statement will be executed, and the execution jumps to the statement after
the “end if” statement.
If there is no “else if” statement after “then” statement and an “else” statement exists, the
statements starting from the one after the “then” statement to the one before the “else”
statement will be executed, and the execution jumps to the statement after the “end if”
statement.
If there is no “else if” statement nor “else” statement after the “then” statement, the
statements following the “then” statement will be executed.
• When the result of the <expression> in the “if” statement is false (==0) and the result of the
<expression> in the “else if” statement is false (==0), if an “else if” statement exists after the
“then” statement, the “else if” statement will be executed in the same way as in the case
described above.
If there is no “else if” statement exists after the “then” statement but the “else” statement
exists, the statements following the “else” statement will be executed.
If there is no “else if” statement or “else” statement, the statements following the “end if”
statement will be executed.

While the processing can jump out of the “if” to “end if” statement range by a “goto” statement,
the execution cannot jump to inside the “if” to “end if” statement range from outside of the “if”
statement.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-219

n switch
The switch statement is used to branch depending on the matching condition of expression with
any of the multiple constant values.

switch (<expression>)
case <constant>[,<constant>]...:
....
[case <constant>[,<constant>...]:
....
[otherwise:
....
]]
end switch

• <expression>
Give the expression to be evaluated in the integer or character string format.
• <constant>
A constant to be compared with the <expression>. Specify a value of the same data type as
that of the <expression> in the “switch” statement. Multiple constants can be listed.

When the switch statement above is executed, the value of the <expression> is calculated
first. The processing will be branched depending on the result of the comparison between the
<expression> value and the <constant>. The branch algorithm is shown below:
• When a <constant> of the same value as that of the <expression> exists, the processing
branches to the statement after the “case” statement which includes the <constant> of
the same <expression> value. After executing to the statement before the next “case”
statement, the processing jumps to the statement after the “end switch” statement.
• When there is no <constant> that is the same as the <expression> value and there is an
“otherwise” statement, the processing branches to the statement after the “otherwise”
statement.
• When there is no <constant> that is the same as the <expression> value and there are
no “otherwise” statement, the processing branches to the statement after the “end switch”
statement.

While the processing can jump out of the “switch” to “end switch” statement range by a “goto”
statement, the execution cannot jump to inside the “switch” to “end switch” statement range from
outside of the “switch” statement.

The statement following the “case” statement can be written in the same line as the “case”
statement. Even though a line which only has a “case” statement is not counted as an execution
statement, it will be counted as an execution statement if a statement is written in the same line
as the “case” statement.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-220

n goto
The “goto” statement unconditionally jumps to the line with the specified label.
The “goto” statement, however, cannot specify a label before the “goto” statement itself.

goto <label>

A compiler error will occur if the label specified by the “goto” statement is located prior to the
“goto” statement, or if the specified label does not exist in the arithmetic expression.

n exit
The “exit” statement unconditionally jumps to the “end” statement. The “exit” statement can be
placed anywhere in the arithmetic expression.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-221

D2.47.7 Error Handling

This section describes the causes of errors occurred during the execution of general-
purpose arithmetic expression and how to handle the errors as well as the details of error
codes.

n Error in the Arithmetic Processing

▼ Error Handling
The cause of errors occurred during the execution of the assignment processing and calculation
processing, as well as how to handle the errors will be explained.

l Causes of Computation Errors

Causes of the computation errors are as follows:
• When the computation result overflows.
• When division by 0 is executed.
• When a calculation is executed to an imaginary number.
• When X ≤ 0 in log (X).
• When X < 0 and Y is a decimal fraction in power (X, Y).
• When X < 0 in sqrt (X).
• When larger than X≈709.783 in exp (X).

l Computation Error Handling

The handling when a computation error occurs is as follows:
• The calculation processing and the assignment processing are immediately stopped. The
value in the variable does not change.
• The following maintenance information is saved in the General-Purpose Calculation Block
(CALCU, CALCU-C).
Statement number where the error occurred. (ERR)
Error code
All local variables

n Error in Conditional Expression

If an error occurs during the calculation of a conditional expression, the calculation is stopped
due to a calculation error.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-222

n Arithmetic Expression Interpreter Error Code

The arithmetic expression interpreter error codes, which occur when statements are executed,
are as follows:
• Category error code
This error code indicates the cause of the error.
• Detailed error code
The contents are different depending on the category error code.
The category error code and the detailed error code are output to the operation and monitoring
functions output as a system alarm message. The output format of the error code is shown
below.

tag_name tag_comment CALCULATION ERROR LINE=nnnnnn CODE=xxxxxx-yyyy

nnnnnn : Line number
xxxxxx : Category error code (decimal)
yyyy : Detailed error code (hex)

The category error codes include the calculation error, errors specific to the arithmetic
expression, execution control error, general error of the built-in function, and other errors.
The details of the category error and detailed error codes are shown below.

l Calculation Error Codes

Table Calculation Error Codes
Code Description Remark
1 Overflow caused by calculation
2 Overflow caused by data type conversion
3 Division by 0
4 Underflow (reserved)
5 Invalid calculation occurred. Including a division by 0 for a real number.
10 Array index is out of range.
11 Attempted to set a value to a constant.
The character string type is specified to a part where only the numerical
12
type is allowed.
The numerical type is specified to a part where only the character string
13
type is allowed.
14 The numerical type and the character string type are mixed.
20020 Calculation stack overflow.
20021 Exceeded the range of character string area to be used by calculation.
D024810E.ai

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-223
l Error Codes Specific to the Arithmetic Expression
The following table shows the error codes specific to the arithmetic expression.
Table List of Error Code Specific to the Arithmetic Expression
Detailed error
Code Description
code
70 Exceeded the maximum number of executable lines.
71 Attempted to execute a program which does not follow the grammar.
80 to 82 Reserved
83 Attempted to access the input variable whose number is out of range. x
84 Attempted to access the output variable whose number is out of range. x
85 Attempted to access the parameter variable whose number is out of range. x
86 Attempted to set to the input variable. x
87 Attempted to set to the pulse count value. x
D024811E.ai

x: Detailed error code exists

Blank: Detailed error code does not exist

The detailed error code is a code that indicates the serial number of the data item name where
the error occurred.
The following table is a list of detailed error codes:
Table List of Detailed Error Codes
Code Data item name
0 RV of CALCU or CALCU-C, CPV
1 to 31 RVn, CPVn
0 to 7 P01 to P08
D024812E.ai

l Execution Control Error Codes

Table List of Execution Control Error Codes
Code Description
20430 Attempted to execute an unsupported statement.
20431 Attempted to execute an unsupported built-in function.
20432 Attempted to access an unsupported variable.
20433 Attempted to use an unsupported operator.
D024813E.ai

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-224
l Built-In Function Generic Error Codes
Table List of Built-In Function Generic Error Codes
Code Description
800 Overflow was detected in the built-in function calculation.
801 Division by zero was detected in the built-in function calculation.
802 The square root of a negative value was calculated by a built-in function.
803 Error in the argument of power() or log().
804 The absolute value of an argument to a trigonometric function is too large to calculate.
805 An error occurred by the mathematical built-in function.
807 The low-limit value is larger than the high-limit value.
810 The number of arguments for a built-in function is incorrect.
811 The type of the argument for a built-in function is incorrect.
895 The first argument of stpvcalc is not between “00” and “99.”
896 The result of stpvcalc is out of the range “00” to “99.”
D024814E.ai

l Other Errors
Table List of Other Error Codes
Code Description
-1 to 32767 Internal error
D024815E.ai

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-225

D2.47.8 Built-In Functions

The built-in functions of the general-purpose arithmetic expression execute calculations
according to the given arguments and return calculation results.
The details of the built-in functions that can be used in the general-purpose arithmetic
expression description language are described in this section.

n Built-In Functions
▼ Built-In Functions
The built-in functions are the applicable functions already built in the system. The built-in
functions include general arithmetic functions, bit operation functions, trigonometric functions,
natural logarithm, temperature and pressure correction functions and so on.
Specify one variable or constant to the built-in function as a parameter. Expressions such as i+1
and d/10.0, or built-in function calls may not be specified as an argument.

SEE
ALSO The causes of errors occurred during the execution of built-in functions and how to handle the errors as well as
the details of error codes, see the following:
D2.47.7, “Error Handling”

n Arithmetic Functions
These functions execute arithmetic calculations.
The details of the arithmetic functions are as follows.

l Absolute Value – labs(arg)

“labs” is a function that returns the absolute value of the argument. Both the argument and result
are the long type.

l Absolute Value – dabs(arg)

“dabs” is a function that returns the absolute value of the argument. Both the argument and result
are the double type.

l Maximum Value – lmax(arg1,arg2,...)

“lmax” is a function that returns the maximum value in an argument list. The maximum number of
arguments is 32. The argument and result are both the long types.

l Maximum Value – dmax(arg1,arg2,...)

“dmax” is a function that returns the maximum value in an argument list. The maximum number
of arguments is 32. The argument and result are both the double types.

l Minimum Value – lmin(arg1,arg2,...)

“lmin” is a function that returns the minimum value in an argument list. The maximum number of
arguments is 32. Both the argument and result are the long type.

l Minimum Value – dmin(arg1,arg2,...)

“dmin” is a function that returns the minimum value in an argument list. The maximum number of
arguments is 32. Both the argument and result are the double type.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-226
l Power – power(arg1, arg2)
“power(arg1, arg2)” is a function that returns a value after multiplying arg1 for arg2 times. Both
the argument and result are the double type.

l Truncation After Decimal Point – int(arg)

“int” is a function that truncates after the decimal point. Both the argument and result are the
double type.

n Bit Operation Function

These functions execute bit operations.
The details of bit operation functions are listed below.

l Bit Position Search Function – bitpstn(arg1,arg2)

“bitpstn(arg1,arg2)” is a function that searches the bit position. The position of the bit whose value
is 1 is searched in the integer variable specified by arg1. The result is the long type.
“bitpstn” returns -1 as the return value when two or more bits are 1 in arg1.

l Bit Position Search Function – bitsrch(arg1,arg2)

“bitsrch(arg1,arg2)” is a function that searches the bit position. The position of the bit whose value
is 1 is searched in the integer variable specified by arg1. The result is the long type.
“bitsrch” searches the value of each bit, starting start from the most significant bit. The search
stops when a bit with a value of 1 is found, and the position of the bit whose value is 1 is returned.
The return value of the normal end will be the bit position. The return value will be 0 when all bits
are 0, and -1 when an error occurs.

The “arg2,” an argument for “bitpstn” and “bitsrch,” is a variable prepared for the functional
extension in the future. “arg2” is ignored even if it is specified.

n Trigonometric Functions
These functions execute calculations related to the trigonometric functions.
The details of the trigonometric functions are as follows:

l Sine – sin(arg)
“sin” is a function that calculates the sine of the argument. The unit of the argument is in radian.
Both the argument and result are the double type.

l Cosine – cos(arg)
“cos” is a function that calculates the cosine of the argument. The unit of the argument is in
radian. Both the argument and result are both double types.

l Tangent – tan(arg)
“tan” is a function that calculates the tangent of the argument. The unit of the argument is in
radian. Both the argument and result are the double type.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-227
l Arctangent – atan(arg)
“atan” is a function that calculates the arctangent of the argument. The unit of the argument is in
radian. Both the argument and result are the double type.

n Square Root – sqrt(arg)

“sqrt” is a function that calculates the square root of the argument. Both the argument and result
are the double type.

n Exponent – exp(arg)
“exp(arg)” is a function that calculates the result of the exponential function (the value after
multiplying e for arg times). Both the argument and result are the double type.

n Natural Logarithm – log(arg)

“log” is a function that calculates the natural logarithm (logarithm of base e) of the argument. Both
the argument and result are the double type.

n Temperature and Pressure Correction Function

This function executes the correction calculation to the measured flowrate by the differential-
pressure type flow gauge which employs the orifice. The correction calculation to the ideal gas is
executed. The details of the temperature and pressure correction function are shown blow.

l Temperature Correction – TC(Fi,T,Tb)

TC(Fi,T,Tb) is a function that only executes temperature correction to the measured flowrate Fi,
measured temperature T and reference temperature Tb. Each input data and calculation result
are the double type.
The correction arithmetic formula is as follows:

Tb+273.15
TC (Fi, T, Tb) = • Fi
T+273.15
D024816E.ai

Fi : Measured flowrate
T : Measured temperature (°C)
Tb : Reference temperature (°C)
Instead of TC (°C), TCF (°F) maybe used in the above formula.

l Pressure Correction – PCKP(Fi, P, Pb)

PCKP(Fi,P,Pb) is a function that only executes the pressure correction to the measured flowrate
Fi, measured pressure P and reference pressure Pb. Each input data and the calculation result
are the double type.
The correction arithmetic formula is as follows:

P+1.01325 • 102
PCKP (Fi, P, Pb) = • Fi
Pb+1.01325 • 102 D024817E.ai

Fi : Measured flowrate
P : Measured pressure (kPa)
Pb : Reference pressure (kPa)

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-228
Even though PCKP (pressure unit: kPa) is used in the description above, PCP (pressure unit:
Pa), PCMP (pressure unit: MPa) and PC (pressure unit:kgf/cm2) can alternatively be used. When
Pa or MPa is used, the constant of the pressure correction term is 1.01325 • 105 and 1.01325 •
10-1 respectively.
When PC is used, the constant of pressure term becomes 1.0332 • 102.

l Temperature and Pressure Correction – TPCKP(Fi,T,P,Tb,Pb)

TPCKP(Fi,T,P,Tb,Pb) is a function that executes the correction of both temperature and pressure
for the measured flowrate Fi, measured temperature T, measured pressure P, reference
temperature Tb and reference pressure Pb. Each input data and the calculation results are the
double type.
The correction arithmetic expression is as follows:

P+1.01325 • 102 Tb+273.15

TPCKP (Fi, T, P, Tb, Pb) = • • Fi
Pb+1.01325 • 102 T+273.15
D024818E.ai

Fi : Measured flowrate
P : Measured pressure (kPa)
T : Measured temperature (°C)
Pb : Reference pressure (kPa)
Tb : Reference temperature (°C)

Even though the TPCKP(pressure unit: kPa) is used in the description above, TPCP(pressure
unit: Pa), TPCMP(pressure unit: MPa) and PC (pressure unit :kgf/cm2) can alternatively be used.
When Pa or MPa is used as the pressure unit, the constant of the pressure correction term is
1.01325 • 105 and 1.01325 • 10-1 respectively.
When PC is used, the constant of pressure term becomes 1.0332 • 102.

n ASTM Correction Function

This function executes the correction calculation of the liquid flow.
The details of the ASTM correction function are as follows:

l ASTM Correction (Old JIS) – ASTM1(t,F,C1)

ASTM1(t,F,C1) calculates the correction flowrate of flowrate F based on the ASTM correction (old
JIS) for the measured temperature t (°C) and the specific gravity (15/4 °C specific gravity) C1. The
argument and result are both the double types.
The correction arithmetic expression is shown below:

F0 = Cf • Fi

Cf = 1 + α (t - 15) + β (t - 15)2
-P1(t) -P3(t)
α= +P2(t) β= +P4(t)
C1 C1 D024819E.ai

Fi : Measured flowrate
t : Measured temperature
C1 : 15/4 °C specific gravity
F0 : Corrected flow
P1(t) to P4(t) : Temperature-dependent parameters

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-229
l ASTM Correction (New JIS) – ASTM2, ASTM3, ASTM4
ASTMn(t,F,ρ) calculates the correction flowrate of flowrate F based on the ASTM correction (new
JIS) for the measure temperature t(°C) and the density ρ(kg/m3).
“n” of ASTMn can be 2, 3 or 4. ASTM2 is used for the crude oil, ASTM3 for the fuel oil, and
ASTM4 for the lubricating oil. The argument and result are both the double types.
The correction arithmetic expression is shown below:
F0 = Cf • F1

Cf=exp - α (t-15) - 0.8 α2 (t-15)2

D024820E.ai

K0 K1
α= +
ρ2
ρ D024823E.ai

F0 : Corrected flowrate
t : Measured temperature
ρ : Density at 15 °C (kg/m3)
Fi : Measured flowrate
K0, K1 : Oil type specific constants

n High and Low Limit – llimit, dlimit

This function is used to limit the input data value within the limit value range.
The details of the high and low limit function are shown below.

l High and Low Limit

llimit(arg1,arg2,arg3) and dlimit(arg1,arg2,arg3) are used to limit data within the specified high
limit and low limit range. Specify data to arg1, low limit to arg2, and high limit to arg3.
When data, min, and max are used as the arguments, the return value of the llimit(data,min,max)
or dlimit(data,min,max) is shown as follows:
min (when data < min)
Return value of the function = data (when min ≤ data ≤ max)
max (when data > max)
D024821E.ai

Because the arguments of “llimit” are converted to the long type, the result will be the long type.
Because the arguments of “dlimit” are converted to the double type, the result will be the double
type.
An error occurs when arg2 (low limit value) is larger than arg3 (high limit value). In this case, the
return value of the function will be the data value.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-230

n Step Name Calculation – stpvcalc(arg1,arg2)

stpvcalc(arg1,arg2) is a function that calculates the step name of the sequence table. “arg1” is
converted to a numerical value and the increment of arg2 is added, then the value is returned
after converting to a character string (“00” to “99”).
• arg1: Current step name (char*2 type)
Specify a 2-digit decimal number between “00” and “99” by a character string constant or
a character string variable. If the value is between 0 and 9, add a 0 to make it a two-digit
number.
• arg2: increment (integer type)
Specify the increment by a numeric variable or constant.

The result of “stpvcalc” is always 2-digit decimal number between “00” and “99” (char*2 type).
If the value is between 0 and 9, 0 is added. An error occurs if the result of the addition becomes
negative or exceeds 99.
An example of changing PV (step name) of the sequence table SEQ001 is shown below:
program
.....
!Assume SEQ001.PV as “03”.
SEQ001.PV=stpvcalc(SEQ001.PV,1)
* SEQ001.PV becomes “04” after applying +1 to “03.”
......
SEQ001.PV=stpvcalc(SEQ001.PV,2)
* SEQ001.PV becomes “06” after applying +2 to “04.”
......
SEQ001.PV=stpvcalc(SEQ001.PV,-4)
* SEQ001.PV becomes “02” after applying -4 to “06.”

......
end
If “00” is specified to arg1, a character string value converted from the arg2 number can be
obtained.
An example of setting a step name to PV of the sequence table SEQ002 is shown below:
program
......
SEQ002.PV=stpvcalc(“00”,8)
* SEQ002.PV becomes “08.”

......
SEQ002.PV=stpvcalc(“00”,12)
* SEQ002.PV becomes “12.
......
end

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D2.47 General-Purpose Arithmetic Expressions> D2-231

D2.47.9 Reserved Words for Numerical and Logical Arithmetic

Expressions
The reserved words for the numerical and logical arithmetic expression are the identifiers
that are used as reserved words by the numerical and logical arithmetic expression
compliers.

n Reserved Words for Numerical and Logical Arithmetic Expressions

▼ Reserved Words
The following table shows the list of reserved words for numerical and logical arithmetic expression:
Table Reserved Word List
ALIAS (D) DMAX (B) P04 (V) RV02 (V)
AND (O) DMIN (B) P05 (V) RV03 (V)
ASTM1 (B) DOUBLE (D) P05C (R) RV04 (V)
ASTM2 (B) ELSE (S) P06 (V) RV05 (V)
ASTM3 (B) ELSE IF (S) P06C (R) RV06 (V)
ASTM4 (B) END (S) P07 (V) RV07 (V)
ATAN (B) ENDIF (S) P07C (R) RV1 (V)
BITPSTN (B) END SWITCH (S) P08 (V) RV2 (V)
BITSRCH (B) EOR (O) P08C (R) RV3 (V)
CASE (S) EXIT (S) P1 (V) RV4 (V)
CHAR (D) EXP (B) P2 (V) RV5 (V)
COS (B) FLOAT (D) P3 (V) RV6 (V)
CPV (V) GOTO (S) P4 (V) RV7 (V)
CPV01 (V) IF (S) P5 (V) SIN (B)
CPV02 (V) INT (B) P5C (R) SQRT (B)
CPV03 (V) INTEGER (D) P6 (V) STPVCALC (B)
CPV04 (V) LABS (B) P6C (R) SWITCH (S)
CPV05 (V) LLIMIT (B) P7 (V) TAN (B)
CPV06 (V) LMAX (B) P7C (R) TC (B)
CPV07 (V) LMIN (B) P8 (V) TCF (B)
CPV1 (V) LOG (B) P8C (R) THEN (S)
CPV2 (V) LONG (D) PC (B) TPC (B)
CPV3 (V) MOD (O) PCKP (B) TPCF (B)
CPV4 (V) NOT (O) PCMP (B) TPCFP (B)
CPV5 (V) OR (O) PCP (B) TPCKP (B)
CPV6 (V) OTHERWISE (S) POWER (B) TPCMP (B)
CPV7 (V) P01 (V) PROGRAM (S) TPCP (B)
DABS (B) P02 (V) RV (V)
DLIMIT (B) P03 (V) RV01 (V)
D024822E.ai

Note: The letter in parentheses ( ) indicates in which part of the program the reserved word is used.
(D): Declaration statement (S): Statement (B): Built-in function
(O): Operator (V): Variable name (R): Reserved

Even though the data item name such as PV and MV are not included in reserved words by the
compiler, it takes greater program resource to find out when a data item name is used in the
place beyond data item names. It is advised not to use the same character string of data item
names in the program scripts.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

Blank Page
 <D3. Sequence Control> D3-1

D3. Sequence Control

Sequence Control Blocks which execute the sequence control include Sequence Table
Blocks, Logic Chart Blocks, SFC Blocks, Switch Instrument Blocks, Sequence Element
Blocks, and Valve Monitoring Block.
This chapter explains details of each type of sequence control block except SFC Blocks.

SEE
ALSO For details of SFC functions, see the following:
D5, “Sequencial Function Chart”

n Sequence Control
The sequence control follows each control step in sequence according to predefined conditions
and order. The function block that executes sequence control function is referred to as the
sequence control block.
The figure below describes the positioning of the sequence control in the basic control.
FCS

Basic control
Software I/O

Regulatory control blocks Common switch

Calculation blocks Annunciator message

Sequence control blocks Sequence control message

Faceplate blocks

SFC blocks

Unit instruments blocks

Options

Valve pattern monitoring (*1)

Off-site blocks (*1)

FCS I/O Interfaces

Process I/O Communication I/O Fieldbus I/O

D030001E.ai

*1: This option can be used in FCSs except PFCS.

Figure Positioning of Sequence Control in Basic Control

With sequence control function blocks, the following types of sequence control can be applied.
• Condition control (monitoring)
Monitors process status and controls it according to pre-defined conditions.
• Program control (phase steps)
Controls according to pre-defined programs (phases).

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3. Sequence Control> D3-2

n Sequence Control Description Method

The description of the sequence control may be applied to the following function blocks.

l Sequence Table Block

The conditions and operations are arranged in the table format and specifies which operation is
performed by the combination of conditions. This is suitable for the description of all sequences
such as the parallel operation, interlock operation and sequence operation.

l Logic Chart Block

In a logic chart block, the conditions and operations are listed, and the combination of conditions
with the logic operators corresponding to the logic requirement may manipulate the operation
signals. This block can be used as the description of an interlock sequence control or a logic
chart.

l SFC Block
SFC (Sequential Function Chart) block is a function block using SFC for sequence control.
The SFC (Sequential Function Chart) block is a graphical flow diagram suitable for describing a
process control sequence. It is standardized by the international standard, IEC SC65A/WG6.
The SFC block is used for relatively large-scaled sequence controls and for controlling devices.
The flow of the entire sequence is defined by the SFC block. Each step in the SFC is described
by the sequence table and SEBOL (SEquence and Batch Orientated Language).

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.1 Types of Sequence Control Blocks> D3-3

D3.1 Types of Sequence Control Blocks

Sequence Control Blocks include Sequence Table Blocks, Logic Chart Blocks, SFC
Blocks, Switch Instrument Blocks, Sequence Element Blocks and Valve Monitoring Block.

n Types of Sequence Control Blocks

The table below lists various sequence control blocks.

l Sequence Table Block

This function block realizes sequence control by operating other function blocks and/or process
I/O or software I/O.
The following two models of blocks are categorized as Sequence Table Block.
• Sequence Table Block (ST16)
• Rule Extension Block (ST16E)

TIP
In KFCS2, KFCS, LFCS2, LFCS, RFCS5 and RFCS2, the following types of sequence table blocks are also
available other than the above mentioned sequence table blocks.
• Sequence Table Block (M_ST16)
Capacity: Condition Signals: 32 to 64 / Action Signals: 32 to 64 / Total: 96
• Rule- Extension Sequence Table Block (M_ST16E)
• Sequence Table Block (L_ST16)
Capacity: Condition Signals: 64 / Action Signals: 64 / Total: 128
• Rule-Extension Sequence Table Block (L_ST16E)

l Logic Chart Block

This function block performs interlock sequence control programmed in the expression of a logic
chart diagram.
The following model of block is categorized as Logic Chart Block.
• Logic chart with 32 inputs, 32 outputs and 64 logic elements (LC64)

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.1 Types of Sequence Control Blocks> D3-4
l SFC Block
This function block realizes sequence control by the program described in sequential function
chart.
The following three models of blocks are categorized as SFC Block.
• Three-Position Switch SFC Block (_SFCSW)
• Pushbutton SFC Block (_SFCPB)
• Analog SFC Block (_SFCAS)

l Switch Instrument Block and Enhanced Switch Instrument Block

The switch instrument block monitors and operates devices such as opening/closing valves,
start/stop motors or pumps, and final control elements for contacts. 10 types of blocks are
available with various I/O points and output methods, usually used in combination with a
sequence table.
The following ten models of blocks are categorized as Switch Instrument Block.
• Switch Instrument Block with 1 Input (SI-1)
• Switch Instrument Block with 2 Inputs (SI-2)
• Switch Instrument Block with 1 Output (SO-1)
• Switch Instrument Block with 2 Outputs (SO-2)
• Switch Instrument Block with 1 Input, 1 Output (SIO-11)
• Switch Instrument Block with 1 Input , 2 Outputs (SIO-12)
• Switch Instrument Block with 2 Inputs, 1 Output (SIO-21)
• Switch Instrument Block with 2 Inputs , 2 Outputs (SIO-22)
• Switch Instrument Block with 1 Input , 2 One-Shot Outputs (SIO-12P)
• Switch Instrument Block with 2 Inputs , 2 One-Shot Outputs (SIO-22P)
Enhanced switch instrument block (*1) is a switch instrument block with enhanced capabilities
for connecting to FF faceplate blocks and fieldbus function blocks and for connecting to the I/O
terminals not next to each other.
*1: Enhanced switch instrument block can be applied to all Field control stations except standard PFCS. When using enhanced
switch instrument block, it is necessary to add the option [DIOENH] on the [Constant] tab of the FCS properties sheet.

The following ten models of blocks are categorized as Enhanced Switch Instrument Block.
• Enhanced Switch Instrument Block with 1 Input (SI-1E)
• Enhanced Switch Instrument Block with 2 Inputs (SI-2E)
• Enhanced Switch Instrument Block with 1 Output (SO-1E)
• Enhanced Switch Instrument Block with 2 Outputs (SO-2E)
• Enhanced Switch Instrument Block with 1 Input, 1 Output (SIO-11E)
• Enhanced Switch Instrument Block with 1 Input, 2 Outputs (SIO-12E)
• Enhanced Switch Instrument Block with 2 Inputs, 1 Output (SIO-21E)
• Enhanced Switch Instrument Block with 2 Inputs, 2 Outputs (SIO-22E)
• Enhanced Switch Instrument Block with 1 Input, 2 One-Shot Outputs (SIO-12PE)
• Enhanced Switch Instrument Block with 2 Inputs, 2 One-Shot Outputs (SIO-22PE)

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.1 Types of Sequence Control Blocks> D3-5
l Sequence Element Blocks
This function block assists with sequence control. It is activated by the sequence table.
The following seven models of blocks are categorized as Sequence Element Block.
• Timer Block (TM)
• Software Counter Block (CTS)
• Pulse Train Input Counter Block (CTP)
• Code Input Block (CI)
• Code Output Clock (CO)
• Relational Expression Block (RL)
• Resource Scheduler Block (RS)

l Valve Monitoring Block (VLVM)

This function block monitors valve opening and closing, and starts an alarm when abnormal
conditions are detected.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.1 Types of Sequence Control Blocks> D3-6

D3.1.1 Alarm Processing of Sequence Control Blocks

Various alarm processing type of sequence control blocks are listed in the following table.

n Alarm Processing of Sequence Control Blocks

Table Alarm Processing of Sequence Control Blocks
Process alarms
N O I I H L H L D D V V M M C Other
Model R O O O H L I O V V E E H L N alarms
P P P + – L L I O F
– + –
ST16 x
ST16E
LC64 x
SI-1
x x x x
SI-2
SO-1
x x x
SO-2
SIO-11
SIO-12
SIO-21 PERR
x x x x x ANS+
SIO-22 ANS-
SIO-12P
SIO-22P
SI-1E
x x x x
SI-2E
SO-1E
x x x
SO-2E
SIO-11E
SIO-12E
SIO-21E PERR
x x x x x ANS+
SIO-22E ANS-
SIO-12PE
SIO-22PE
TM x
CTS
CTP x x x x
CI
CO
RL
RS
VLVM x
D030002E.ai

x: available
Blank: Not available

The alarm status of ST16, LC64, TM and VLVM blocks are always indicated as NR (stands for
Normal status).

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.1 Types of Sequence Control Blocks> D3-7

D3.1.2 Block Mode of Sequence Control Blocks

Various modes of sequence control blocks are listed in the following table.

n Block Mode of Sequence Control Blocks

Table Block Mode of Sequence Control Blocks
Valid basic block modes
O I T M A C P R R
Model Name of function block / M R A U A R C O
S A K N T S D A U
N S T

ST16 Sequence table (basic section) block

x x x
ST16E Rule extension block
LC64 Logic chart block x x x
SI-1 Switch instrument block with 1 input
x x
SI-2 Switch instrument block with 2 inputs
SO-1 Switch instrument block with 1 output
SO-2 Switch instrument block with 2 outputs
SIO-11 Switch instrument block with 1 input and 1 output
SIO-12 Switch instrument block with 1 input and 2 outputs
x x x x x x x
SIO-21 Switch instrument block with 2 inputs and 1 output
SIO-22 Switch instrument block with 2 inputs and 2 outputs
SIO-12P Pulse type switch instrument block with 1 input and 2 outputs
SIO-22P Pulse type switch instrument block with 2 inputs and 2 outputs
SI-1E Enhanced switch instrument block with 1 input
x x
SI-2E Enhanced switch instrument block with 2 inputs
SO-1E Enhanced switch instrument block with 1 output
SO-2E Enhanced switch instrument block with 2 outputs
SIO-11E Enhanced switch instrument block with 1 input and 1 output
SIO-12E Enhanced switch instrument block with 1 input and 2 outputs
x x x x x x x
SIO-21E Enhanced switch instrument block with 2 inputs and 1 output
SIO-22E Enhanced switch instrument block with 2 inputs and 2 outputs
SIO-12PE Enhanced pulse type switch instrument block with 1 input and 2 outputs
SIO-22PE Enhanced pulse type switch instrument block with 2 inputs and 2 outputs
TM Timer block
CTS Software counter block
CTP Pulse train input counter block
CI Code input block
x x
CO Code output block
RL Relational expression block
RS Resource scheduler block
VLVM 16-valve monitor block
D030003E.ai

x: valid
Blank: Invalid

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-8

D3.2 Sequence Table Block (ST16, ST16E)

Sequence Table Blocks (ST16, ST16E) controls the monitoring of processing and the
phase step sequences by connecting with other function blocks, process I/O, and
software I/O.

n Sequence Table Block (ST16, ST16E)

Sequence Table Block (ST16, ST16E) is a decision table type function block that describes
the relationship between input signal and output signal in a Y/N (yes/no) fashion. By making
sequence connection with other function blocks, they control the monitoring of processing and
phase step sequences. Sequence Table Blocks include the basic ST16, and ST16E that is only
used for rule extension.
The figure below shows the function block diagram of Sequence Table Blocks (ST16, ST16E).

Q01 Rule 1 ...... 32 J01

Y N
Q02 J02
YN
Q03 Input Output J03
processing Y processing
NY

Q56 Logic operation J56

D030201E.ai

Figure Function Block Diagram of Sequence Table Block (ST16, ST16E)

The table below lists connection methods and destinations for Sequence Table Blocks (ST16,
ST16E) I/O terminals.
Table Connection Methods and Destinations for Sequence Table Block (ST16, ST16E) I/O Terminals
Connection type Connection destination
I/O Status Terminal
terminal Data Data Condition Process Software Function
manipula- connecti-
reference setting testing I/O I/O block
tion on
Q01 to Q56 x x x x
J01 to J56 x x x x
D030202E.ai

x: Connection available
Blank: Connection not available

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-9
I/O connection is set by describing connection information and data in the input connection
information setting area, condition specification setting area, output connection information
setting area, and operation specification setting area of the sequence table displayed in the
sequence table edit window of the Function Block Detail Builder.
Rule number 01 02 03 04 05 06 07 08 32
No. Tag name Data Step label
Data item
Comment

Input Condition
connection specification Condition rule setting area
information setting area
setting area

Output Operation
connection specification
information setting area
setting area
Action rule setting area

D030203E.ai

Figure Conceptual Diagram of Sequence Table

Two types of blocks are available in the Sequence Table Block (ST16, ST16E).
• ST16:
Sequence Table Block
• ST16E:
Rule Extension Block

l Sequence Table Block (ST16)

The Sequence Table Block (ST16) has a sequence control function that handles a total of 64 I/O
signals, 32 rules. It can also change distribution of the 64 I/O signals and output signals in the
8-signal unit. The total number of I/O signals is fixed to 64. Thus, a sequence table with only eight
inputs and eight outputs cannot be created.

l Rule Extension Block (ST16E)

This function block is used for rule extensions of the Sequence Table Block (ST16). It connects to
an extending Sequence Table Block (ST16) as an extended sequence table to form a sequence
table group.
Because the Rule Extension Block (ST16E) is managed by the Sequence Table Block (ST16)
that is an extending sequence table, it cannot be activated independently.
The Rule Extension Block (ST16E) only allows connection to a step-type extending Sequence
Table Block (ST16) on which step labels is described. Nonstep-type Sequence Table Blocks
(ST16) cannot be connected.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-10

n Rule Expansion
When the phase step sequence table is used, the number of processes (number of steps)
may be insufficient depending on the process that is being performed. At this time, use the rule
expansion format Sequence Table Block (ST16E) which enables the number of rules to be
expanded.
The following figure shows when the rule expansion of sequence tables.

ST16 ST16E
Rule 01 ... ... ... ... ... ... 32 Rule 01 ... ... ... ... ... 3132
Symbol Step 01 ... ... ... ... ... ... 15 Symbol Step 16 ... ... ... ... ... ... 35
C01 C01
• •
• E1 G1 • E1 G2
• •
C32 C32
A01 A01
• •
• H1 J1 • H1 J2
• •
A32 A32
THEN THEN
ELSE ELSE

NEXT Expansion destination sequence table name

Expansion source sequence table Expansion destination sequence table

D030204E.ai

Figure Example of Sequence Table Expansion

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-11

D3.2.1 Sequence Table Configuration

Sequence tables consist of condition signals, action signals, rule numbers, condition
rules, action rules and step labels.

n Complete Sequence Table Configuration

▼ Sequence Table Configuration
The figure below shows the complete sequence table.
Processing timing Scan period

Rule number 01 02 03 04 05 06 07 08 32
Tag name
No. Data Step label
Data item
Condition signal Comment
C01 TM14.BSTS RUN
Condition rule
C02 FC001.ALRM HI
C03 %SW0201.PV ON
C03
C04

Action signal

A01 ST90.MODE AUT

A02 %AN0010.PV H
Action rule
A03
A04
A05

Extension rule tag name THEN label

NEXT ELSE label
Next step label
D030205E.ai

Figure Conceptual Diagram of Complete Sequence Table

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-12

n Outline of Sequence Table Elements

The following describes various sequence table elements.

l Condition Signal
Enter the element symbol and data item into the Tag name. Data item column as the input
connection information, then enter the condition specification to Data column.

l Action Signal
Enter the element symbol and data item into the Tag name. Data item column as the input
connection information then enter the action specification to Data column.

l Rule Number
Up to 32 rules per block may be used. The output is based on each rule condition and condition
testing result.

l Condition Rule
Describe the Y/N (Y: true, N: false) pattern (combination) to condition rule. If the testing result of
condition signal corresponds with the Y/N pattern, the condition of the rule is satisfied.

l Action Rule
Describe the Y/N ( Y: Positive action; N: Negative action) pattern (combinations) to action rule.
Perform manipulated output according to the Y/N pattern of the action rule for the rule number
whose condition is satisfied.

l Step Label
▼ Step
These labels are attached for phase identification purposes when performing step sequence
control using a sequence table. Step labels are character strings that combine two or less
alphanumeric characters (A to Z, 0 to 9).
If two characters are combined while one is not alphanumeric and the other is alphanumeric, the
label is managed as the same step name, even if the order of characters is reversed (e.g., “_A”
and “A_”).
Up to 100 steps can be described in one sequence table group. However, same step labels
cannot be described at multiple locations inside the sequence table group.
The step labeled 00 is activated every scan cycle.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-13
l Next Step Label
▼ THEN, ELSE
Describe the step label that is to be executed in the next scan.
Next step labels include THEN and ELSE labels according to case conditions being true or false.
If both labels are blank, the step does not transfer.
• THEN label
Describe the next step label when the corresponding rule condition status is true. Transition
to the step described in the THEN label is executed after the manipulated output is
completed.
• ELSE labels
Describe the next step label when the corresponding rule status is false.

The described step labels must exist in the same sequence table group. To execute a step from
another sequence table group at the next scan, it must be described as an action signal.

l Tag Name.Data Item

Describe the input connection information of the condition signal or the output connection
information of the action signal.

l Data
Describe the condition specification of the condition signal or the operation specification of the
action signal.

l Comment
Comments are defined by users for the condition and action signals. The meaning of symbols
and the contents of status manipulation may be put in these texts, by using up to 24 single-byte
alphanumeric characters, or 12 double-byte characters.
By clicking the task [Referencing Signal Comment] from the [Tool] menu, the user-defined
comment text may be displayed at the right area of signals. By this Referencing Signal Comment
operation, the comment texts defined by users for the condition signals and action signals and
the tag comments are all displayed. The comment text for the referenced signals can not be
edited on the sequence table editing window.

IMPORTANT
Specify an element number with the number of digits specified for each element to a condition
or action signal. If the number without the highest digit’s “0” is specified to a condition or action
signal, a reference signal comment is not displayed.

TIP
A referenced signal comment is not stored in a builder file. To reference a comment, select [Referencing Signal
Comment] from the [Tool] menu.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-14
l Processing Timing
The processing timing of a sequence table consists of start timing and output timing.
Start timing refers to the timing at which control algorithms of the sequence table are executed
upon receipt of input signals. Output timing indicates the conditions under which action signals
are output at the time a periodic start type or one-shot start type sequence table is executed.
“Start Timing” and “Output Timing” are set for each sequence table.
• Start Timing:
Select either “Periodic Execution Type (T),” “One-shot Processing Type (O),” “Startup at
Initial Cold Start/Restart (I)” or “Restricted Initial Execution Type (B).”
• Output Timing:
Select either “Output Only When Conditions Change (C)” or “Output Each Time Conditions
are Satisfied (E).”

l Scan Period
Periodic start sequence tables are activated at defined scan period. Among the periodic started
sequence tables, the sequence tables activated in the basic period have the items “Control
Period” and “Control Phase” to be defined in addition to scan period.
“Scan Period,” “Control Period,” and “Control phase” can be defined for each sequence table.
• Scan Period:
Select from “Basic Scan”, “Medium-speed Scan” (*1) or “High-speed Scan.”
• Control Period:
1 to 16 seconds.
• Control Phase:
0 to 15 seconds.
*1: “Medium-speed Scan” is only supported by KFCS2, KFCS, FFCS, LFCS2 and LFCS.

l Extension Rule Tag Name

▼ NEXT
Described by 16 or less alphanumeric characters.

SEE
ALSO • For sequence block processing timing, see the following:
C7.3, “Process Timing for Sequence Control Block”
• For details on scan period, see the following:
C7.1.1, “Scan Period”
• For details on control period and control phase, see the following:
C7.3.5, “Control Period and Control Phase for Sequence Table Blocks (ST16, ST16E)”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-15

n Sequence Description Example

The basic logical circuit figure for the AND and OR commands is described in the sequence table
as shown in the following figure.
01 02 03

No Tag Name and Data Item Data

C01 %SW0200.PV ON Y N
%SW0200 Condition C02 %SW0201.PV ON Y N
ON %Z011101 C03
ON
%SW0201 A01 %Z011101.PV H Y N N
ON AND Action A02
A03
D030206E.ai

Figure AND Circuit Example

In the example in this figure, for AND operator, only when two condition signals are satisfied, the
operation may be performed.
01 02 03

No Tag Name and Data Item Data

C01 %SW0200.PV ON Y N
%SW0200 Condition C02 %SW0201.PV ON Y N
ON %Z011101 C03
ON
%SW0201 A01 %Z011101.PV H Y Y N
ON OR Action A02
A03
D030207E.ai

Figure OR Circuit Example

In the example in this figure, for OR operator, any one of the two conditions is established, the
operation may be performed.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-16

D3.2.2 Creating a Sequence Table

To create a sequence table, enter the input information for sequence control in each
setting area of the sequence table edit window of the Function Block Detail Builder.

n Configuration of Sequence Table Edit Window

The figure below shows the configuration of the sequence table edit window.
Process timing setting area Step label setting area
Signal setting column heading Rule number display area STEP

Condition signal
number
display area Condition signal setting area Condition rule setting area

Action signal
number
display area Action signal setting area Action rule setting area

Next step label setting area THEN

NEXT Extension table setting area

Next step label setting area ELSE

D030208E.ai

Figure Configuration of Sequence Table Edit Window

To create a sequence table, the information (condition signals, action signals, condition rule and
action rules) for sequence connection and the information (condition rule and action rules) for
logic calculation should be entered to each setting area of the sequence table edit window.
The setting area are listed below.
• Processing timing setting area
• Step label setting area
• Condition signal setting and action signal setting area
• Condition rule setting and action rule setting area
• Extension table setting area
• Next step label setting area (THEN, ELSE)

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-17

n Processing Timing Setting Area

Processing timing and scan period are displayed in the processing timing setting area.
Processing timing and scan period may be defined on the processing timing setting dialog box.
A display example of processing timing setting dialog is shown below.
Processing timing

Processing timing

Execution timing Periodic execution

Output timing Output only at condition change

Scan period

Scan period Basic scan

Control period
Control phase

OK Cancel

D030209E.ai

Figure Processing Timing Setting Dialog

SEE
ALSO For details of processing timing, see the following:
C7.3, “Process Timing for Sequence Control Block”

n Step Label Setting Area

Enter the step label in the step label setting area using 2 or less alphanumeric characters.

n Condition Signal Setting Area and Action Signal Setting Area

Enter the condition signal and action signal into each line that displays the signal number in the
condition signal setting area and action signal setting area.

n Condition Rule Setting Area and Action Rule Setting Area

Enter Y/N pattern condition rule and action rule respectively, in the condition rule setting area and
the action rule setting area.
To enter the condition rule and action rule, click on the input location. The display alternates
between “Y,” “N” and “.” as it is clicked. When a “.” is displayed, it means that no Y/N pattern has
been entered yet.

SEE
ALSO • For details of condition rules, see the following:
D3.2.5, “Condition Rule Processing of Sequence Table”
• For details of action rules, see the following:
D3.2.6, “Action Rule Processing of Sequence Table”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-18

n Extension Table Setting Area

Enter the tag name of the extended sequence table in the extended sequence table setting area.
The rules of the extending and extended sequence tables are connected and the rule numbers
that can be used in the sequence table are then extended, if the tag name of the extended
sequence table is entered.

SEE
ALSO For details of rule extension, see the following:
D3.2.9, “Rule Extension”

n Next Step Label Setting Area (THEN, ELSE)

Enter a 2 digits alphanumeric number directly to the next step label setting area.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-19

D3.2.3 Sequence Table Processing Flow

In the sequence table, condition rule processing and action rule processing are
performed based on the results of input processing. Output processing is then performed
for the action target.

n Sequence Table Processing Flow

▼ Sequence Table Processing Flow
The figure below shows the sequence table processing flow.

Input processing
(condition testing)

Condition rule processing

....... Y
....... Y
....... N
....... Y

Action rule processing

Output processing
(status manipulation)

D030210E.ai

Figure Sequence Table Processing Flow

l Input Processing
The true/false status of the condition signal is determined by performing condition testing based
on the input signal.

l Condition Rule Processing

The true/false status of the rule condition is determined by comparing the true/false status of the
condition signal with the Y/N pattern of the condition rule described in the sequence table.

l Action Rule Processing

The action signal output is determined by the Y/N pattern of the action rule when the status of
condition is true.

l Output Processing
Status manipulation of the action target is performed based on the description of the action
signal. The status manipulation, start command transmission, data setting, and status change
can be performed to the contact outputs and other function blocks.

There are two types of sequence tables: step and nonstep. Rule processing differs by the type of
sequence table.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-20

n Operations of Non-Step Sequence

In a non-step sequence table, all 32 rules are subject to condition testing, and the operation
is performed according to the conditions. The following shows the operation of a non-step
sequence table.
Rule 01 … … … … … … 32
Step
C01 All rule numbers are
. subject to condition testing.
.
. Condition signal

C32
A01 Only the rules whose conditions
. are satisfied are executed.
. Operation signal
.
A32
THEN
ELSE
D030211E.ai

Figure Operation of NonStep Sequence Table

• As for condition testing, a condition is satisfied when all conditions (Y or N) for the same
rule number are true. A sequence table whose rule columns are all blank is considered true
unconditionally.
• Operations are executed according to the operation contents of Y or N described for the rule
number whose conditions are satisfied.
• When the output timing is specified as “Output Only When Conditions Change,” the
operation is executed only once when the condition is switched from false to true. However,
if non-latched output is specified for the operation signal, the operation changes when the
condition is switched from true to false.
• When the output timing is specified as “Output Each Time Conditions are Satisfied,” the
operation is executed during each period as long as the condition remains true.
• When the conditions of multiple rules are satisfied simultaneously with respect to the same
operation signal, if requests for both Y and N are detected as the resultant operations, the
request for Y takes precedence, and the operation for N will not be executed.
01 02 03

No Tag Name.Data Item Data

C01 %SW0100.PV ON Y When %SW0100 and %SW0101 turn on simultaneously,
Conditions C02 %SW0101.PV ON Y %SW0200 turns on.
C03 The Y operation takes precedence.
A01 %SW0200.PV H Y N
Operations A02
A03
D030212E.ai

Figure Example of Operation for Simultaneous Requests

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-21

n Example of the Non-Step Format Sequence Using the Sequence Table

An example of the sequence that normally monitors operations to prevent the buffer tank in the
processing piping system from overflow is shown in the following figure. In this sequence, LI100
(indication block) alarm status is used.
VALVE-A open command
FCS
Limit switch (LS-A, Open)

HH
LI H
Inflow valve 100 L
VALVE-A PVI LL
Differential Pressure
transmitter
LT100

Limit switch (LS-B, open)

Outflow valve
VALVE-B VALVE-B open command

Next process

D030213E.ai

Figure Example of Process Flow Figure

Inflow valve - Open Outflow valve - Open

Inflow valve - Closed
Level High - High limit alarm %AN0001
AND
Level - High limit alarm %AN0002

Level - Low limit alarm %AN0003

Level Low - Low limit alarm Inflow valve - Open

Outflow valve - Closed
Outflow valve - Open %AN0004
AND D030214E.ai

Figure Example of Condition Logic Diagram

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-22
The condition logic diagram of the previous page is described as below used the sequence table.
Processing Timing TC .... Scan Period Basic Scan
Rule Number
No Tag Name - Data Item Data Comment 01 02 03 04

C01 LS-A.PV ON Inflow valve limit switch Y

C02 LS-B.PV ON Outflow valve limit switch Y
C03 LI100.ALRM HH Y
C04 LI100.ALRM HI Y
C05 LI100.ALRM LO Y
C06 LI100.ALRM LL Y

A01 VALVE-A.PV H Inflow valve open command N Y

A02 VALVE-B.PV H Outflow valve open command Y N
A03 %AN0001 L Upper level, high-limit alarm Y
A04 %AN0002 L Level, high-limit alarm Y
A05 %AN0003 L Level, low-limit alarm Y
A06 %AN0004 L Lower level, low-limit alarm Y
D030215E.ai

Figure Non-step Sequence Table Example

The sequence table in the figure shown above monitors the conditions in rule numbers 01 to 04
simultaneously. Any condition in one of the 4 rules becomes true, the operation in the same rule
will be executed again. The monitoring continues after the execution.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-23

n Action of Step Sequence

▼ Sequence Table Algorithm
In a step sequence table, the process control sequence of a phase-step process is divided into
the smallest phase units (steps) of the condition monitoring and operation, then these steps are
executed one by one.
In a step sequence table, only step label 00 and the rule corresponding to the current step
number are subject to condition testing and operation. The following shows the action of a step
sequence table.
Rule 01 … … … … … … 32
Step 01 02 03 04
C01 Only the step currently being executed is
. subject to condition testing.
.
. Condition signal

C32
A01 Only the operations for the rules whose conditions are
. satisfied in the step currently being executed, are executed.
. Operation signal
.
A32
THEN
ELSE
D030216E.ai

Figure Action of Step Sequence Table

• Step label 00 is executed during each period. Step 00 may only be described at the head of
a sequence table group. Step 00 cannot be described as a next step label.
• When the check box of [CENTUM-XL Compatible Sequence Tables] in the [Sequence Table
Algorithm] setting area of [Constant] tab on FCS Properties sheet is checked (*1), if the
step00 exists in the same table of the execution step, both the step00 and the execution
step will be activated at the same time after the condition testing. If the table is expanded to
another table and the execution step is on the expansion table, the condition of the step00
will be tested first and then the action of the step00 will be activated before testing and
activating the execution step.
However, if the check box of [CENTUM-XL Compatible Sequence Tables] is not checked,
the condition of the step00 will be tested first and then the action of the stepp00 will be
activated before testing and activating the execution step even when the sequence table is
not expanded.
By default, this check box is not checked.
• For step sequences, the next execution step label must be described in THEN/ELSE in
order to advance the steps. The step will not be advanced if both next step labels in THEN/
ELSE are blank. If there is no description for the next step label, the same step is executed
each time, the sequence does not move step.
• The next step specified in THEN is the step to advance when the condition test result in
positive. When all operations for the corresponding rules are completed, the step proceeds
to the next step.
• The next step specified in ELSE is the step to advance when the condition test result in
negative. When conditions for the corresponding rules are established, the step proceeds to
the next step without executing the operation rules.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-24
• When the check box of [THEN/ELSE Has Higher Precedence] in the [Sequence Table
Algorithm] setting area of [Constant] tab on FCS Properties sheet is checked (*1), if the
next step is directed by THEN/ELSE, the next step directed in the action rule with the script
of <Sequence Table Name>.PV will be ignored. However, if the next step is not directed
by THEN/ELSE, the next step directed in the action rule will be activated. If the next step is
directed by THEN/ELSE, and the next step is also directed in the action rule with the script
of <Sequence Table Name>.SA, the step designated by <Sequence Table Name>.SA will
be executed first, and the step directed by THEN/ELSE will be executed after even the
option of [THEN/ELSE Has Higher Precedence] is checked.
Vice versa, when the check box of [THEN/ELSE Has Higher Precedence] is not checked,
the next step directed in the action rule will be activated and the next step directed by THEN/
ELSE will be ignored. By default, this check box is not checked.
• If there are multiple requests for step transition in the same step, the step advances to the
next step label that is described for the smallest rule number.
• When a step is advanced, the conditions for the rules are initialized once. In other words, all
the conditions become false with respect to the previous execution.
• The timing in which the next step is actually executed after a step is advanced, is the next
scan period.
• The same step label can be assigned to multiple rules. In this case, branched operations
can be performed according to the condition.
01 02 03 04 05
A A A
No Tag Name.Data Item Data 1 2 3
C01 %SW0100.PV ON Y N If %SW0100 is on at step label A1,
Condition C02 it turns on %SW0200 and advances the step.
C03 If %SW0100 is off,
Y N it turns off %SW0200 and advances the step.
A01 %SW0200.PV H
Operation A02
A03
A A
THEN
2 3
ELSE
D030217E.ai

Figure Example of Conditional Branch

*1: The check boxes of [CENTUM-XL Compatible Sequence Tables] and [THEN/ELSE Has Higher Precedence] are available in the
[Sequence Table Algorithm] setting area of Constant tab on FCS Properties sheet of KFCS2, FFCS and LFCS2 only.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-25

n Example of a Step Sequence that Uses the Sequence Table

This figure shows an example of the phase step sequence that combines the water injection
processing and drain processing.
Sequence Specifications
Push the start button, valve A opens to fill water to the tank. When the tank is full, switch A
becomes ON, the valve is closed.
Push the start button again when the tank is full, then the valve B opens.
When the drain process ends, switch B becomes ON, the valve B closes.

FCS
Start button
(PB001)

Valve A
(VLVA)
Switch A
(SWA)

Switch B
(SWB)

Valve B
(VLVB)

To the next process

D030218E.ai

Figure Example of Process Flow

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-26

Sequence start

Start button No
(PB001)

Yes

Valve A: Open (VLVA)

Water injection processing (Step label A1)

Switch A level Hi No
(SWA)

Yes

Valve A: Close (VLVA)

Start button No
PB001

Yes

Valve B: Open (VLVB)

Water drain processing (Step label A2)

Switch B level Lo No
(SWB)

Yes

Valve B: Close (VLVB)

D030219E.ai

Figure Example of Sequence Flow Chart

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-27
The sequence flow chart of the previous page is described as below used the sequence table.

Rule Number 01 02 03 04 05 06
Process Timing TC .... Scan Period Basic Scan A A
STEP
No Tag Name.Data Item Data Comment 1 2

C01 PB001.PV ON Start Button Y Y

C02 SWA.PV ON Switch A (Level HI) N Y Y
C03 SWB.PV ON Switch A (Level LO) Y
C04
C05
C06

A01 VLVA.PV H Valve A Y N

A02 VLVB.PV H Valve B Y N
A03
A04
A05
A06

A A
THEN
2 1
Destination Step Label
ELSE

D030220E.ai

Figure Example of Step Sequence Table

In the above sequence table, rule numbers 01 and 02 are step A1. Rule numbers 03 and up
are step A2. Rule numbers 05 and beyond do not have any description for the condition rule,
operation rule or move-destination step label, so they are not subject to condition testing nor
operation.
Step A1 monitors the conditions for rule numbers 01 and 02 simultaneously. Of rule numbers 01
and 02, whichever the condition is satisfied will be executed. Executing the operation of rule 01
does not advance the step, since there is no designation in the move-destination step label. After
executing the operation, A1 resumes monitoring rule numbers 01 and 02 again. On the other
hand, if the condition for rule number 02 becomes true, the operation of rule 02 will be executed,
and the step advances to A2 because the move-destination step label has a designation.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-28

D3.2.4 Input Processing of Sequence Table

In input processing, the true/false status of a condition signal is determined by
performing condition testing on each of the multiple input terminals.

n Input Processing of Sequence Table

In input processing, condition testing is performed on the condition signal of the rules subject to
execution, in order to retain the true/false status of the condition signal in the form of a logical
value. The label of a step that is to be executed is described on the rule subject to execution.
When the step label is not described in the step column of the sequence table, all rules are
subject to the execution rule.
For all rule conditions except those subject to execution, the status of the condition signal is
considered “false” regardless of the status of the connection destination.
The table below lists the results of condition testing when error occurs during input processing.
Table Descriptions of Input Processing Errors and Condition Testing Results
Input processing results and
Error Descriptions
effect on condition signal processing
• When the condition signal is not described • The status of the condition signal is set “true”
• When there is an error in the testing condition • The result of the condition signal processing is set
of the condition signal unconditionally “true” regardless of the Y/N pattern
• When the necessary input signal for condition • Maintain the state of previous input processing
testing was unavailable (*1) • Condition signal processing is performed based on the
• When one-shot execution was not available previous test result
D030221E.ai

*1: The following describes factors that do not allow input signals.
• When the database of the connection destination or element is abnormal.
• When the connection destination or process I/O is undergoing online maintenance.

A system alarm occurs when referencing the result of one-shot execution at the connection
destination fails due to the following:
• When the nest referring from a referenced sequence table to other sequence
table exceeds seven levels including the referencing sequence table;
• When the connection destination block mode is out of service (O/S); or
• When the connection destination is undergoing maintenance.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-29

IMPORTANT
When a function block of the connection destination and/or a process I/O is undergoing
maintenance, input signals cannot be obtained. When performing maintenance, and before
performing online loading, be sure to set related function blocks to manual (MAN) mode or
perform any processing that stops executions in order to execute an online load.
The true/false status of the condition signal is maintained as the previous input value within the
sequence table. However, when the necessary input signal for condition testing is unavailable, or
when one-shot execution of the connection destination function block is unavailable, the previous
input value used in condition testing as in the case shown below will not be the expected value.
• When the sequence table itself is a one-shot execution type, or when the function block
of the connection destination is a one-shot execution type while the block mode is out of
service (O/S), it might have been long since the previous input value was obtained. If so, the
value obtained from the previous one-shot execution remains to be the previous input value.
• When the sequence table itself is a one-shot execution type, or when the function block
of the connection destination is a one-shot execution type while the block mode is out of
service (O/S), if no one-shot execution was performed, the previous input value is 0.
• Immediately after a step is changed in the step-type sequence table, always set the
previous input value to 0 (false) before performing the condition testing.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-30

D3.2.5 Condition Rule Processing of Sequence Table

In the condition rule processing, the true/false status of each rule condition is determined
by comparing for each rule the true/false status of condition signals and the condition
rules.

n Condition Rule Processing of Sequence Table

An example of condition rule processing is shown below.
Rule number True/false status True/false status of condition signal...condition testing result:
01 02 03 04 true (1). false (0)
of condition signal
True/false status of condition.....True/false status of conditionsignal
Condition signal 1 1 Y Y in one rule corresponds with the Y/N
Condition signal 2 0 Y Y pattern in the same rule.
Condition signal 3 1 Y N
True/false condition status 0 0 1 0 As shown in the figure left, the true/false status of the condition
signal corresponds with the Y/N pattern in Rule 03 only.
Action signal 1 Y N The Y operation in action signal 2 is, therefore, performed.
Action signal 2 Y
Action signal 3 N
D030222E.ai

Figure Example of Condition Rule Processing

l Comparing the True/False Status of Condition Signals and Condition Rules

The comparison content differs by the Y/N pattern of the condition signal described in the
condition rule.
• When Y is described in the condition signal.
If the status of the condition signal obtained by input processing is true (1), the condition is
satisfied.
• When N is described in the condition signal.
If the status of the condition signal obtained by input processing is false (0), the condition is
satisfied.

l Determining the True/False Status of Conditions

Only rules with satisfied conditions are subject to action rule processing. When all Y/Ns of a
condition described in the rule of the same number are satisfied, the status of the rule condition is
true (1). If even one of them is not satisfied, the status is false (0).

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-31

D3.2.6 Action Rule Processing of Sequence Table

For each rule number for which the condition part is true (satisfied), the corresponding
output signals are decided by the Y/N pattern in the action part of the rule.

n Action Rule Processing of Sequence Table - ST16, ST16E

The output action signal based on the Y/N pattern is determined in the action rule processing.
Rule number True/false status True/false status of condition signal...condition testing result:
01 02 03 04 true (1). false (0)
of condition signal
True/false status of condition.....True/false status of conditionsignal
Condition signal 1 1 Y Y in one rule corresponds with the Y/N
Condition signal 2 0 Y Y pattern in the same rule.
Condition signal 3 1 Y N
True/false condition status 0 0 1 0 As shown in the figure left, the true/false status of the condition
signal corresponds with the Y/N pattern in Rule 03 only.
Action signal 1 Y N The Y operation in action signal 2 is, therefore, performed.
Action signal 2 Y
Action signal 3 N
D030223E.ai

Figure Example of Condition Rule Processing

Of the rules with true status of condition, only action signals described with Y or N in action rules
will be output targets.
When “Output Only when Conditions Change” is specified for output timing, rules whose true/
false status of condition is changed can be action targets.

The content of status manipulation in the sequence table is decided by the Y/N pattern, while
those of status manipulation in other sequence control blocks differ by the true/false logical
calculation result.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-32

D3.2.7 Output Processing of Sequence Table

In output processing, the action target is manipulated by outputting the action signal
obtained by action rule processing.

n Output Processing of Sequence Table

In output processing, by outputting action signals, the action target is manipulated based on the
action target and action specifications described in the action signal column. The manipulation for
the action target is called status manipulation.
When errors occur in output processing while performing operations such as changing the
block mode of a function block for which a block mode change interlock is specified, status
manipulations to the target blocks are not performed.
If one action signal is tested by multiple rules, and both Y and N actions are requested, Y has
higher priority. In this case, Y is executed but N is ignored.
Also, a system alarm occurs when one-shot execution fails due to the reasons indicated below:
• When the nest executing from an executed sequence table to other sequence table
exceeds seven levels including the executing sequence table;
• When the connection destination block mode is out of service (O/S); or
• When the connection destination is undergoing maintenance.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-33

D3.2.8 Number of Condition Signals and Action Signals

Up to 32 condition signals and 32 action signals for a total of 64 signals can be described
in one Sequence Table Block (ST16).
When more than 32 condition signals or 32 action signals must be described, the
allocation of the number of condition signals and action signals totaling 64 can be
changed in units of eight signals.

n Number of Condition Signals and Action Signals

▼ Number of Signals
There are 32 action signals and 32 condition signals in each Sequence Table Block (ST16).
However, allocation of the number of signals can be changed in the 8-signal unit using the signal
selection dialog which is called from the Function Block Detail Builder.
• Select Number of Signals: Sets allocation of the number of I/O signals in the 8-signal unit.
Table Combination of Condition Signal and Action Signal Counts
Condition signal count Action signal count
8 56
16 48
24 40
32 (default) 32 (default)
40 24
48 16
56 8
D030224E.ai

The signal count selection dialog box is displayed by selecting [Change Number of Signal Lines]
from the [View] menu in the Function Block Detail Builder.
A display example of the signal line selection dialog box is shown below.
Select Number of Signal Lines

Condition signal = 32, Operation signal = 32

OK Cancel

D030225E.ai

Figure Example of Signal Line Selection Dialog Box

IMPORTANT
Condition signal and action signal information may be lost if the signal count is decreased by
changing signal count allocation.
The message shown below is displayed when information may be lost.
• Type:
warning
• Description:
“Some of the existing definition information will be lost by changing this setting. Is it OK to
change?”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-34

D3.2.9 Rule Extension

In the sequence table, up to 32 rules can be set to test condition signals and action
signals.
When describing information in the sequence table, if more than 32 rules are required
in one phase of a sequence control that is being described in the sequence table, the
number of rules can be extended.

n Rule Extension
The number of rules in one sequence table is fixed at 32 and cannot be modified. However,
if the number of rules in a sequence table is not enough to describe one phase unit, it can be
extended in the 32-rule unit by connecting to another sequence table. The number of rules can
be extended for a step-type sequence table.

l Method of Rule Extension

To extend the number of rules, specify a tag name for the rule extension block (ST16E) in the
sequence table setting area of the extending sequence table (ST16). It does not matter if the
number of signals and signal contents are different between the extending sequence table
(ST16) and extended sequence table (ST16E).
The number of rules can be extended in the 32-rule unit per block.
An example of the number of rules extended to 64 is shown below.
Extending table Extending table Extended table

ST16 ST16 ST16E

condition side condition side condition side
ST16 ST16 ST16E
operation side operation side operation side

D030226E.ai

Figure Examples of Rule Extension

l Sequence Table Group

Multiple sequence tables connected for rule extension are referred to as a sequence table group.
Up to 100 steps can be described in one sequence table group. The number of rules cannot be
extended over 100 steps. A step name cannot be described more than once in a sequence table
group (not in both extending table and extended table).

l Editing an Extended Sequence Table

An extended sequence table (ST16E) can be opened by selecting [Open the next extension
table] from the [display] menu in the Function Block Detail Builder. To enter information for
sequence connection, the method used in an extended sequence table (ST16E) can also be
used in the extending sequence table (ST16).

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-35

n Restrictions on Rule Extension

This section explains the restrictions on rule extension.

l Restrictions on the Number of Steps

Rule extension is required in the step-type sequence tables. Up to 100 steps can be described
in the step-type sequence table. Even when the step-type sequence table is extended for rule
extension, the maximum number of describable steps is limited to 100 within a sequence table
group.
If it is necessary to describe over 100 steps in a step-type sequence table, create another step-
type sequence table to allow execution of the second table continued from the first table.
There are no restrictions on the number of tables. However, in consideration of the performance
of sequence table execution, the number of connected tables in the sequence table group should
be as small as possible.

l Restrictions on Step Label

The same step label cannot be described in more than one step label setting area within
a sequence table group. The step executed over two sequence tables or more cannot be
described, either.
If a step cannot be described within one sequence table, decrease processing to be executed
in a step and describe a step label indicating that the next step starts from a newly extended
sequence table.

l Restrictions on Rule Extension Table

The rule extension sequence table block should be created in the same control drawing with
the original sequence table block. If the rule extension sequence block is created in a drawing
different from the original sequence block, on the sequence table view of HIS, the status display
of the original sequence block can not be extended to the rule extension sequence block.

SEE
ALSO For more information about control drawings, see the following:
F4. “Control Drawing Builder”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-36

D3.2.10 Condition Signal Description: Referencing Other

Function Blocks and I/O Data
In the condition testing in which other function blocks are referenced, various data,
block mode and status can be referenced. I/O data such as process I/O, software I/O,
communication I/O can also be referenced.

n Function Blocks and I/O Data that can be Referenced from a Sequence
Table
▼ Conditional Signal Description
Function blocks that can be referenced from a sequence table are shown below.
• Switch Instrument Blocks
• Timer Block (TM)
• Software Counter Block (CTS)
• Pulse Train Input Counter Block (CTP)
• Code Input Block (CI)
• Code Output Block (CO)
• Relational Expression Block (RL)
• Resource Scheduler Block (RS)
• Valve Monitoring Block (VLVM)
• Regulatory Control Blocks
• Calculation Blocks
• Faceplate Blocks
• SFC Blocks
• Unit Instrument Blocks
• Sequence Table Blocks
• Logic Chart Blocks

In addition, the following I/O data can be referenced from the sequence table.
• Processing I/O (contact I/O)
• Software I/O (internal switch, annunciator message)
• Communication I/O

The following should be taken into account when referencing a sequence table block mode.
• When O/S is specified in the condition specification for block mode reference, the test result
will be unsatisfied in the compound block mode in which O/S and another basic block mode
are satisfied simultaneously.
• When MAN or AUT is specified in the condition specification for block mode reference, the
test result is satisfied even in the compound block mode as long as the specified basic block
mode is established.
• The status of pulse width output cannot be referenced.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-37

n Switch Instrument Block and Enhanced Switch Instrument Block

Reference
The table below lists the condition signal symbolic convention for referencing various data and
status of switch instrument block and enhanced switch instrument block as well as the conditions
for true Y/N described in the condition rule.
Table Condition Signal Symbolic Convention and Conditions for True Y/N Described in Condition Rule
(1/2)
Condition signal description column Condition
Condition rule Conditions for true status
Input signal column
specification
Y Answerback value coincides with specification.
Element symbol.PV 0, 1, 2
N Answerback value does not coincide with specification.
Y Data status coincides with specification.
Element symbol.PV =Data status
N Data status does not coincide with specification.
Y Output value coincides with specification.
Element symbol.MV 0, 1, 2
N Output value does not coincide with specification.
Y Data status coincides with specification.
Element symbol.MV =Data status
N Data status does not coincide with specification.
Y Tracking switch is in specified state.
Element symbol.TSW 0, 1
N Tracking switch is not in specified state.
Y Data status coincides with specification.
Element symbol.TSW =Data status
N Data status does not coincide with specification.
Y Backup switch is in specified state.
Element symbol.BSW 0, 1
N Backup switch is not in specified state.

AUT, MAN, CAS, Y Block mode coincides with specification.

Element symbol.MODE
ROUT, TRK, O/S N Block mode does not coincide with specification.
Y Block is in ROUT (MAN) mode.
BUM
N Block is not in ROUT (MAN) mode.
Y Block is in ROUT (AUT) mode.
Element symbol.XMODE BUA
N Block is not in ROUT (AUT) mode.
Y Block is in ROUT (CAS) mode.
BUC
N Block is not in ROUT (CAS) mode.
Y Block status coincides with specification.
Element symbol.BSTS NR, SIM, ANCK
N Block status does not coincide with specification.
D030227E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-38
Table Condition Signal Symbolic Convention and Conditions for True Y/N Described in Condition Rule
(2/2)
Condition signal description column Condition
Condition rule Conditions for true status
Input signal specification Condition

NR, IOP, OOP, ANS+, Y Specified alarm is activated.

Element symbol.ALRM
ANS-, PERR, CNF N Specified alarm is not activated.
Y Alarm is in IOP or IOP- status.
Element symbol.XALRM IOP
N Alarm is in neither IOP nor IOP- status.
PERR, AFL (*1), NR, Y Specified alarm is flashing.
Element symbol.AFLS IOP, OOP, ANS+,
ANS-, CNF N Specified alarm is not flashing.

NR, IOP, OOP, ANS+, Y Specified alarm detection is off.

Element symbol.AF
ANS-, PERR, CNF N Specified alarm detection is on.
Y IOP or IOP- detection is disabled.
Element symbol.XAF IOP
N IOP or IOP- detection is enabled.
NR, IOP, OOP, ANS+, Y Specified alarm is masked.
Element symbol.AOFS CNF, ANS-, PERR,
AOF (*2) N Specified alarm is unmasked.
Y Sequence setting value coincides with specification.
Element symbol.CSV 0, 1, 2
N Sequence setting value does not coincides with specification.
Y Data status coincides with specification.
Element symbol.CSV =Data status
N Data status does not coincides with specification.
Y Remote manipulated output value coincides with specification.
Element symbol.RMV 0, 1, 2 Remote manipulated output value does not coincides with
N specification.
Y Data status coincides with specification.
Element symbol.RMV =Data status
N Data status does not coincides with specification.
Y Bypass switch is in specified state.
Element symbol.BPSW 0, 1
N Bypass switch is not in specified state.
Y Data status coincides with specification.
Element symbol.BPSW =Data status
N Data status does not coincides with specification.
D030228E.ai

*1: Condition Specification AFL references the group flashing status.

*2: Condition Specification AOF references the alarm group mask status.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-39

n Timer Block Reference (TM)

The table below lists the condition signal symbolic convention for referencing various data and
status of the Timer Block (TM) and the conditions for true Y/N described in the condition rule.
Table Condition Signal Symbolic Convention and Conditions for True Y/N Described in Condition Rule

Condition signal description column Condition

rule Conditions for true status
Input signal Condition specification column
Y Block mode coincides with specification.
Element symbol.MODE AUT, O/S
N Block mode does not coincide with specification.

STOP, RUN, PAUS, Y Block status is in specified state.

Element symbol.BSTS
NR, PALM, CTUP
N Block status is not in specified state.
Y Alarm status is in specified state.
Element symbol.ALRM NR
N Alarm status is not in specified state.
Y Specified alarm is flashing.
Element symbol.AFLS AFL (*1), NR
N Specified alarm is not flashing.
Y Specified alarm detection is off.
Element symbol.AF NR
N Specified alarm detection is on.
Y Specified alarm is masked.
Element symbol.AOFS NR,AOF?(*2)
N Specified alarm is unmasked.
D030229E.ai

*1: Condition Specification AFL references the group flashing status.

*2: Condition Specification AOF references the alarm group mask status.

n Software Counter Block Reference (CTS)

The table below lists the condition signal symbolic convention for referencing various data and
status of the Software Counter Block (CTS) as well as the conditions for true Y/N described in the
condition rule is shown below.
Table Condition Signal Symbolic Convention and Conditions for True Y/N Described in Condition Rule

Condition signal description column Condition

rule Conditions for true status
Input signal Condition specification column
Y Block mode coincides with specification.
Element symbol.MODE AUT, O/S
N Block mode does not coincide with specification.
Y Block status is in specified state.
STOP, RUN, NR,
Element symbol.BSTS
PALM, CTUP N Block status is not in specified state.
D030230E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-40

n Pulse Train Input Counter Block Reference (CTP)

The table below lists the condition signal symbolic convention for referencing various data
and status of the Pulse Train Input Counter Block (CTP) as well as the conditions for true Y/N
described in the condition rule.
Table Condition Signal Symbolic Convention and Conditions for True Y/N Described in Condition Rule
Condition signal description column Condition
rule Conditions for true status
Input signal Condition specification column
Y Block mode coincides with specification.
Element symbol.MODE AUT, O/S
N Block mode does not coincide with specification.

STOP, RUN, PAUS, Y Block status is in specified state.

Element symbol.BSTS
NR, PALM, CTUP
N Block status is not in specified state.
Y Alarm status is in specified state.
Element symbol.ALRM CNF, NR, IOP
N Alarm status is not in specified state.
Y Alarm is in IOP or IOP- status.
Element symbol.XALRM IOP
N Alarm is in neither IOP nor IOP- status.

AFL (*1), CNF, NR, Y Specified alarm is flashing.

Element symbol.AFLS
IOP N Specified alarm is not flashing.
Y Specified alarm detection is off.
Element symbol.AF CNF, NR, IOP
N Specified alarm detection is on.
Y IOP or IOP- detection is disabled.
Element symbol.XAF IOP
N IOP and IOP- detection is enabled.

CNF, NR, IOP, Y Specified alarm is masked.

Element symbol.AOFS
AOF (*2) N Specified alarm is unmasked.
Y Data status coincides with specification.
Element symbol.PV =Data status
N Data status does not coincide with specification.
D030231E.ai

*1: Condition Specification AFL references the group flashing status.

*2: Condition Specification AOF references the alarm group mask status.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-41

n Code Input Block Reference (CI)

The table below lists the condition signal symbolic convention for referencing various data
and status of the Code Input Block (CI) as well as the conditions for true Y/N described in the
condition rule.
Table Condition Signal Symbolic Convention and Conditions for True Y/N Described in Condition Rule

Condition signal description column Condition

rule Conditions for true status
Input signal Condition specification column
Y Block mode coincides with specification.
Element symbol.MODE AUT, O/S
N Block mode does not coincide with specification.
Y Block status coincides with specification.
Element symbol.BSTS NR, LO, HI, ERR
N Block status does not coincide with specification.
Y Data status coincides with specification.
Element symbol.PV =Data status
N Data status does not coincide with specification.
D030232E.ai

n Code Output Block Reference (CO)

The table below lists the condition signal symbolic convention for referencing various data and
status of the Code Output Block (CO) as well as the conditions for true Y/N described in the
condition rule.
Table Condition Signal Symbolic Convention and Conditions for True Y/N Described in Condition Rule

Condition signal description column Condition

rule Conditions for true status
Input signal Condition specification column
Y Block mode coincides with specification.
Element symbol.MODE AUT, O/S
N Block mode does not coincide with specification.
Y Block status coincides with specification.
Element symbol.BSTS NR, LO, HI
N Block status does not coincide with specification.
Y Data status coincides with specification.
Element symbol.PV =Data status
N Data status does not coincide with specification.
D030233E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-42

n Relational Expression Block Reference (RL)

The table below lists the condition signal symbolic convention for referencing various data and
status of the Relational Expression Block (RL) as well as the conditions for true Y/N described in
the condition rule.
Table Condition Signal Symbolic Convention and Conditions for True Y/N Described in Condition Rule

Condition signal description column Condition

rule Conditions for true status
Input signal Condition specification column

EQ, GT, GE, LT, LE, Y Relationship between two data is in specified state.
Element symbol.X01 to 16 AND N Relationship between two data is not in specified state.
D030234E.ai

The table below lists the description of condition specifications.

Table Description of Condition Specifications
Symbol Name Description
EQ (*1) equal data 1 = data 2
GT greater than data 1 > data 2
GE great than or equal to data 1 ≥ data 2
LT less than data 1 < data 2
LE less than or equal to data 1 ≤ data 2
AND logical product bitwise logical product of data 1 and 2
D030235E.ai

*1: When using EQ relation by comparing the two variables with real numbers, the condition may not be established because of a
trivia difference. It is better to use GT, GE, LT and LE instead of EQ when comparing the two variables with real numbers.

n Resource Scheduler Block Reference (RS)

The table below lists the condition signal symbolic convention for referencing various data and
status of the Resource Scheduler Block (RS) as well as the conditions for true Y/N described in
the condition rule.
Table Condition Signal Symbolic Convention and Conditions for True Y/N Described in Condition Rule

Condition signal description column Condition

rule Conditions for true status
Input signal Condition specification column
Y Block mode coincides with specification.
Element symbol.MODE AUT, O/S
N Block mode does not coincide with specification.
Usage request status coincides with specification.
Y
Element symbol.RQ01 to 32 0, 1 (0: Not requested, 1: Requesting)
N Usage request status does not coincide with specification.
Permission status coincides with specification.
Y
Element symbol.PM01 to 32 0, 1 (0: Not permitted, 1: Permitted)
N Permission status does not coincide with specification.
Maximum permissible number coincides with
Y
specification.
Element symbol.RMH 0 to 32
Maximum permissible number does not coincide with
N
specification.
D030236E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-43

n Valve Monitoring Block Reference (VLVM)

The table below lists the condition signal symbolic convention for referencing various data and
status of the Valve Monitoring Block (VLVM) as well as the conditions for true Y/N described in
the condition rule.
Table Condition Signal Symbolic Convention and Conditions for True Y/N Described in Condition Rule

Condition signal description column Condition

rule Conditions for true status
Input signal Condition specification column
Y Block mode coincides with specification.
Element symbol.MODE AUT, O/S
N Block mode does not coincide with specification.
Y Specified alarm is activated.
Element symbol.ALRM NR
N Specified alarm is not activated.
Y Alarm is flashing.
Element symbol.AFLS NR, AFL (*1)
N Alarm is not flashing.
Y Specified alarm detection is off.
Element symbol.AF NR
N Specified alarm detection is on.
Y Specified alarm is masked.
Element symbol.AOFS NR, AOF (*2)
N Specified alarm is unmasked.
Valve normal/abnormal state coincides with specification.
Y
(0: Normal, 1: Abnormal)
Element symbol.PV01 to 16 0, 1
Valve normal/abnormal state does not coincide with
N
specification.
Representative valve normal/abnormal state coincides
with specification.
Y
(0: All valves are normal, 1: At least one of the alarms is
Element symbol.PVR 0, 1 abnormal)
Representative valve normal/abnormal state does not
N
coincide with specification.
Message suppression coincides with specification.
Y
Element symbol.MCSW 0, 1 (0: Not suppressed, 1:Suppressed)
N Message suppression does not coincide with specification.
D030237E.ai

*1: Condition Specification AFL references the group flashing status.

*2: Condition Specification AOF references the alarm group mask status.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-44

n Regulatory Control Block Reference

The table below lists the condition signal symbolic convention for referencing the block mode,
block status, alarm status, and data status of the regulatory control block as well as the
conditions for true Y/N described in the condition rule.
Table Condition Signal Symbolic Convention and Conditions for True Y/N Described in Condition Rule

Condition signal description column Condition

rule Conditions for true status
Input signal Condition specification column
Y Block mode is in specified state.
Element symbol.MODE Block mode
N Block mode is not in specified state.
Y Block is in ROUT (MAN) or RCAS (MAN) mode
BUM
N Block is not in ROUT (MAN) or RCAS (MAN) mode
Y Block is in ROUT (AUT) or RCAS (AUT) mode
Element symbol.XMODE BUA
N Block is not in ROUT (AUT) or RCAS (AUT) mode
Y Block is in ROUT (CAS) or RCAS (CAS) mode
BUC
N Block is not in ROUT (CAS) or RCAS (CAS) mode
Y Block status is in specified state.
Element symbol.BSTS Block status
N Block status is not in specified state.
Y Specified alarm is activated.
Element symbol.ALRM Alarm status
N Specified alarm is not activated.
Y Alarm is in IOP or IOP- status.
IOP
N Alarm is in neither IOP nor IOP- status.
Element symbol.XALRM
Y Alarm is in VEL+ or VEL- status.
VEL
N Alarm is in neither VEL+ nor VEL- status.
Y Specified alarm is flashing.
Element symbol.AFLS Alarm status, AFL (*1)
N Specified alarm is not flashing.
Y Specified alarm detection is off.
Element symbol.AF Alarm status
N Specified alarm detection is on.
Y IOP or IOP- detection is disabled.
Element symbol.XAF IOP
N IOP and IOP- detection is enabled.
Y Specified alarm is masked.
Element symbol.AOFS Alarm status, AOF (*2)
N Specified alarm is unmasked.
Y Data value coincides with specification.
Element symbol.Data item Data value
N Data value does not coincide with specification.
Y Data status coincides with specification.
Element symbol.Data item =Data status
N Data status does not coincide with specification.
D030238E.ai

*1: Condition Specification AFL references the group flashing status.

*2: Condition Specification AOF references the alarm group mask status.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-45
l Regulatory Control Block that can Describe Data Values in Condition
Specifications
The table below lists the regulatory control blocks that can describe data values in condition
specifications and the setting ranges of data items.
Table Regulatory Control Blocks that can Describe Data Values in Condition Specifications and the
Setting Ranges of Data Items (1/3)
Block code Name Data item Setting range
TSW 0, 1
CSW 0, 1
PID PID Controller Block PSW 0 to 3
RSW 0, 1
BSW 0, 1
TSW 0, 1
CSW 0, 1
PID-HLD Sampling PI Controller Block PSW 0 to 3
RSW 0, 1
BSW 0, 1
TSW 0, 1
CSW 0, 1
PID-BSW PID Controller Block with Batch Switch PSW 0 to 3
RSW 0, 1
BSW 0, 1
CSW 0, 1
PID-TP Time-Proportioning ON/OFF Controller Block PSW 0 to 3
BSW 0, 1
PSW 0 to 3
ONOFF 2-Position ON/OFF Controller Block
BSW 0, 1
PSW 0 to 3
ONOFF-E Enhanced 2-Position ON/OFF Controller Block
BSW 0, 1
PSW 0 to 3
ONOFF-G 3-Position ON/OFF Controller Block
BSW 0, 1
PSW 0 to 3
ONOFF-GE Enhanced 3-Position ON/OFF Controller Block
BSW 0, 1
TSW 0, 1
PSW 0 to 3
PD-MR PD Controller Block with Manual Reset
RSW 0, 1
BSW 0, 1
TSW 0, 1
PSW 0 to 3
PI-BLEND Blending PI Controller Block RSW 0, 1
BSW 0, 1
RST 0, 1
Block code Name Data item Setting range
D030239E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-46
Table Regulatory Control Blocks that can Describe Data Values in Condition Specifications and the
Setting Ranges of Data Items (2/3)
Block code Name Data item Setting range
TSW 0, 1
CSW 0, 1
PSW 0 to 3
PID-STC Self-Tuning PID Controller Block
RSW 0, 1
BSW 0, 1
STC -1 to 3
TSW 0, 1
MLD Manual Loader Block
RSW 0, 1
TSW 0, 1
MLD-PVI Manual Loader Block with Input Indicator
RSW 0, 1
TSW 0, 1
MLD-SW Manual Loader Block with Auto/Man SW PSW 0 to 3
RSW 0, 1
TSW 0, 1
BSW 0, 1
BPSW 0 to 4
MC-2 2-Position Motor Control Block SIMM 0 to 1
CSV 0 to 2
PV 0 to 2
MV 0 to 2
TSW 0, 1
BSW 0, 1
BPSW 0 to 4
MC-2E Enhanced 2-Position Motor Control Block SIMM 0 to 1
CSV 0 to 2
PV 0 to 2
MV 0 to 2
TSW 0, 1
BSW 0, 1
BPSW 0 to 4
MC-3 3-Position Motor Control Block SIMM 0 to 1
CSV 0 to 2
PV 0 to 2
MV 0 to 2
TSW 0, 1
BSW 0, 1
BPSW 0 to 4
MC-3E Enhanced 3-Position Motor Control Block SIMM 0 to 1
CSV 0 to 2
PV 0 to 2
MV 0 to 2
Block code Name Data item Setting range
D030240E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-47
Table Regulatory Control Blocks that can Describe Data Values in Condition Specifications and the
Setting Ranges of Data Items (3/3)
Block code Name Data item Setting range
TSW 0, 1
PSW 0 to 3
RATIO Ratio Set Block
RSW 0, 1
BSW 0, 1
ZONE 1 to 13
PG-L13 13-Zone Program Set Block ZSTR 1 to 13
ZEND 1 to 13
SW 0 to 4
BSETU-2 Flow-Totalizing Batch Set Block EMSW 0, 1
ZONE 0 to 11
SW 0 to 4
BSETU-3 Weight-Totalizing Batch Set Block EMSW 0, 1
ZONE 0 to 11
PSW 0 to 3
VELLIM Velocity Limiter Block BSW 0, 1
BPSW 0, 1
SW 0 to 4
SS-H/M/L Signal Selectors
SEL 0 to 3
PSW 0 to 3
AS-H/M/L Auto Selectors SW 0 to 4
SEL 0 to 3
SW 1 to 3
SS-DUAL Dual-Redundant Signal Selector Block
SEL 1 to 2
TSW 0, 1
PSW 0 to 3
FFSUM Feedforward Signal Summing Block
FSW 0, 1
RSW 0, 1
TSW 0, 1
XCPL Non-Interference Control Output Block PSW 0 to 3
RSW 0, 1
BSW 0, 1
SPLIT Control Signal Splitter Block
SW 0 to 3
SW 0 to 5
ALM-R Representative Alarm Block
SV 0 to 15
SBSD Ys Instrument Batch Set Station Block SV 0 to 8
SLBC Ys Instrument Batch Set Controller Block SV 0 to 8
Block code Name Data item Setting range
D030241E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-48

n Calculation Block Reference

The table below lists the condition signal symbolic convention for referencing the block mode of
calculation block, block status, alarm status, and data status, as well as the conditions for true
Y/N described in the condition rule is shown below.
Table Condition Signal Symbolic Convention and Conditions for True Y/N Described in Condition Rule

Condition signal description column Condition

rule Conditions for true status
Input signal Condition specification column

Y Block mode coincides with specification.

Element symbol.MODE AUT, O/S
N Block mode does not coincide with specification.
Y Block status coincides with specification.
Element symbol.BSTS RUN, STOP
N Block status does not coincide with specification.
Y Alarm status is in specified state.
Element symbol.ALRM Alarm status
N Alarm status is not in specified state.
Y Alarm is in IOP or IOP- status.
IOP
N Alarm is in neither IOP nor IOP- status.
Element symbol.XALRM
Y Alarm is in VEL+ or VEL- status.
VEL
N Alarm is in neither VEL+ nor VEL- status.
Y Specified alarm is flashing.
Element symbol.AFLS Alarm status, AFL (*1)
N Specified alarm is not flashing.
Y Specified alarm detection is off.
Element symbol.AF Alarm status
N Specified alarm detection is on.
Y IOP or IOP- detection is disabled.
Element symbol.XAF IOP
N IOP and IOP- detection is enabled.
Y Specified alarm is masked.
Element symbol.AOFS Alarm status, AOFS (*2)
N Specified alarm is unmasked.
Y Calculation result is not 0.
Element symbol.ACT ON
N Calculation result is 0.
Y Data value coincides with specification.
Element symbol.data item Data value (*3)
N Data value does not coincide with specification.
Y Data status coincides with the status of specified data.
Element symbol.data item =Data status Data status does not coincide with the status of specified
N
data.
D030242E.ai

*1: Condition Specification AFL references the group flashing status.

*2: Condition Specification AOF references the alarm group mask status.
*3: Only integers can be a data value. If the data item is a floating decimal point, the value is rounded off for comparison.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-49
l Calculation Blocks that can Describe Data Values in Condition Specifications
The table below lists the data items of Calculation Blocks that can describe data values in
condition specifications and their setting ranges.
Table Calculation Blocks that can Describe Data Values in Condition Specifications and Setting Range
of Data Items (1/2)
Block code Name Data item Setting range
DLAY Dead-Time Block
DLAY-C Dead-Time Compensation Block RST 0, 1
AVE-M Moving-Average Block
INTEG Integration Block
SW 0, 1, 2
AVE-C Cumulative-Average Block
SW-33 Three-Pole Three-Position Selector Switch Block SW 0 to 3
BDSET-1L One-Batch Data Set Block
BDSET-1C One-Batch String Data Set Block
SW 0 to 3
BDSET-2L Two-Batch Data Set Block
BDSET-2C Two-Batch String Data Set Block
SW-91 One-Pole Nine-Position Selector Switch Block SW 0 to 9
DSW-16 Selector Switch Block for 16 Data
SW 0 to 16
DSW-16C Selector Switch Block for 16 String Data
BDA-L Batch Data Acquisition Block
SW 0 to 17
BDA-C Batch String Data Acquisition Block
D030243E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-50
Table Calculation Blocks that can Describe Data Values in Condition Specifications and Setting Range
of Data Items (2/2)
Block code Name Data item Setting range
AND (*1) Logical AND Block RV1 0, 1
RV2 0, 1
CPV 0, 1
OR (*1) Logical OR Block RV1 0, 1
RV2 0, 1
CPV 0, 1
NOT (*1) Logical NOT Block RV 0, 1
CPV 0, 1
SRS1-S (*1) Set-Dominant Flip-Flop Block with 1 Output RV1 0, 1
RV2 0, 1
CPV1 0, 1
SRS1-R (*1) Reset-Dominant Flip-Flop Block with 1 Output RV1 0, 1
RV2 0, 1
CPV1 0, 1
SRS2-S (*1) Set-Dominant Flip-Flop Block with 2 Outputs RV1 0, 1
RV2 0, 1
CPV1 0, 1
CPV2 0, 1
SRS2-R (*1) Reset-Dominant Flip-Flop Block with 2 Outputs RV1 0, 1
RV2 0, 1
CPV1 0, 1
CPV2 0, 1
WOUT (*1) Wipeout Block RV1 0, 1
RV2 0, 1
CPV 0, 1
OND (*1) ON-Delay Timer Block RV 0, 1
CPV 0, 1
OFFD (*1) OFF-Delay Timer Block RV 0, 1
CPV 0, 1
TON (*1) One-Shot Block (Rising-Edge Trigger) RV 0, 1
CPV 0, 1
TOFF (*1) One-Shot Block (Falling-Edge Trigger) RV 0, 1
CPV 0, 1
GT (*1) Comparator Block (Greater Than) CPV 0, 1
GE (*1) Comparator Block (Greater Than or Equal) CPV 0, 1
EQ (*1) Equal Operator Block CPV 0, 1
Block code Name Data item Setting range
D030244E.ai

*1: Logic Operation Block can be used in FCSs except PFCS.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-51
l Calculation Blocks that can Reference Calculation Results by One-Shot
Execution
The table below lists Calculation Blocks that can reference calculation results by one-shot
execution of the condition signal, “element symbol. ACT.ON.”
Table One-Shot Executable Blocks for Condition Testing
Block type Code Name
ADD Addition Block
MUL Multiplication Block
Arithmetic calculation
DIV Division Block
AVE Averaging Block
AND Logical AND Block
OR Logical OR Block
NOT Logical NOT Block
SRS1-S Set-Dominant Flip-Flop with 1 Output
SRS1-R Reset-Dominant Flip-Flop 1 Output
SRS2-S Set-Dominant Flip-Flop with 2 Outputs

Logic Calculation (*1) SRS2-R Reset-Dominant Flip-Flop 2 Outputs

WOUT Wipeout Block
GT Comparator Block (Greater Than)
GE Comparator Block (Greater Than or Equal)
EQ Equal Operator Block
BAND Bitwise AND Block
BOR Bitwise OR Block
BNOT Bitwise NOT Block

General-Purpose CALCU General-Purpose Calculation Block

Calculations CALCU-C General-Purpose Calculation Block with String I/O
D030245E.ai

*1: Logic Operation Block can be used in FCSs except PFCS.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-52

n Faceplate Block Reference

The table below lists the condition signal symbolic convention for referencing various data and
status of the faceplate block, as well as the conditions for true Y/N described in the condition rule.
Table Condition Signal Symbolic Convention and Conditions for True Y/N Described in Condition Rule

Condition signal description column Condition

rule Conditions for true status
Input signal Condition specification column
Y Block mode coincides with specification.
Element symbol.MODE Block mode
N Block mode does not coincide with specification.
Y Block is in ROUT (MAN) or RCAS (MAN) mode.
BUM
N Block is not in ROUT (MAN) or RCAS (MAN) mode.
Y Block is in ROUT (AUT) or RCAS (AUT) mode.
Element symbol.XMODE BUA
N Block is not in ROUT (AUT) or RCAS (AUT) mode.
Y Block is in ROUT (CAS) or RCAS (CAS) mode.
BUC
N Block is not in ROUT (CAS) or RCAS (CAS) mode.
Y Block status coincides with specification.
Element symbol.BSTS Block status
N Block status does not coincide with specification.
Y Specified alarm is on.
Element symbol.ALRM Alarm status
N Specified alarm is not on.
Y Alarm is in IOP or IOP- status.
IOP
N Alarm is in neither IOP nor IOP- status.
Element symbol.XALRM
Y Alarm is in VEL+ or VEL- status.
VEL
N Alarm is in neither VEL+ nor VEL- status.
Y Specified alarm is flashing.
Element symbol.AFLS Alarm status, AFL (*1)
N Specified alarm is not flashing.
Y Specified alarm detection is off.
Element symbol.AF Alarm status
N Specified alarm detection is on.
Y Specified alarm is masked.
Element symbol.AOFS Alarm status, AOF (*2)
N Specified alarm is unmasked.

1 to 99 Y Phase step number coincides with specification.

Element symbol.SV
(Only BSI block is valid) N Phase step number does not coincide with specification.
Y Operation command coincides with specification.
Element symbol.PV01 to 10 0, 1
N Operation command does not coincide with specification.
Y Data status coincides with specification.
Element symbol.Data item =Data status
N Data status does not coincide with specification.

Element symbol. Y Switch display color coincides with specification.

0 to 15
SWCR[n] (*3) N Switch display color does not coincide with specification.

Element symbol. Y Switch flashing status coincides with specification.

0, 1
SWST[n] (*3) N Switch flashing status does not coincide with specification.
Y Switch operation disabled status coincides with specification.
Element symbol.
-15 to 15 Switch operation disabled status does not coincide with
SWOP[n] (*3) N
specification.
D030246E.ai

*1: Condition Specification AFL references the group flashing status.

*2: Condition Specification AOF references the alarm group mask status.
*3: n is the subscript of the 1 dimensional array. This subscript is the number of the push button switches on a faceplate block. This
number varies with the type of faceplate block.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-53

n SFC Block Reference

The table below lists the condition signal symbolic convention for referencing various data and
status of the SFC block as well as the conditions for true Y/N described in the condition rule.
Table Condition Signal Symbolic Convention and Conditions for True Y/N Described in Condition Rule

Condition signal description column Condition

rule Conditions for true status
Input signal Condition specification column
Y Block mode is in specified state.
Element symbol.MODE MAN, SEMI, AUT, O/S
N Block mode is not in specified state.
RUN, PAUS, STOP, Y Block status is in specified state.
Element symbol.BSTS ABRT
N Block status is not in specified state.
Y Specified alarm is activated.
Element symbol.ALRM Alarm status
N Specified alarm is not activated.
Y Specified alarm is flashing.
Element symbol.AFLS Alarm status, AFL (*1)
N Specified alarm is not flashing.
Y Specified alarm detection is off.
Element symbol.AF Alarm status
N Specified alarm detection is on.
Y Specified alarm is masked.
Element symbol.AOFS Alarm status, AOF (*2)
N Specified alarm is unmasked.
Y Data value coincides with specification.
Element symbol.Data item Data value
N Data value does not coincide with specification.

Y Data status coincides with specification.

Element symbol.Data item =Data status
N Data status does not coincide with specification.
D030247E.ai

*1: Condition Specification AFL references the group flashing status.

*2: Condition Specification AOF references the alarm group mask status.

l Setting Range of Data Item When Describing Data Value in Condition

Specification
The table below lists the data items of SFC block that can describe data values in condition
specifications and their setting ranges.
• STEPNO: 1 to 99
• SWCR[5]: 0 to 15
• SWST[5]: 0, 1
• SWOP[5]: -15 to 15

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-54

n Unit Supervision Reference

The table below lists the condition signal symbolic convention for referencing various data and
status of the unit instrument block as well as the conditions for true Y/N described in the condition
rule.
Table Condition Signal Symbolic Convention and Conditions for True Y/N Described in Condition Rule

Condition signal description column Condition

rule Conditions for true status
Input signal Condition specification column
Y Unit mode is in specified state.
Element symbol.MODE MAN, SEMI, AUT, O/S
N Unit mode is not in specified state.
Y Unit status is in specified state.
Element symbol.BSTS Unit status
N Unit status is not in specified state.
Y Specified alarm is activated.
Element symbol.ALRM Alarm status
N Specified alarm is not activated.
Y Specified alarm is flashing.
Element symbol.AFLS Alarm status, AFL (*1)
N Specified alarm is not flashing.
Y Specified alarm detection is off.
Element symbol.AF Alarm status
N Specified alarm detection is on.
Y Specified alarm is masked.
Element symbol.AOFS Alarm status, AOF (*2)
N Specified alarm is unmasked.
Y SFC step number coincides with specification.
Element symbol.STEPNO 1 to 99
N SFC step number does not coincide with specification.
D030248E.ai

*1: Condition Specification AFL references the group flashing status.

*2: Condition Specification AOF references the alarm group mask status.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-55

n Processing I/O Reference

The table below lists the condition signal symbolic convention for referencing various data and
status of the processing I/O block as well as the conditions for true Y/N described in the condition
rule.
Table Condition Signal Symbolic Convention and Conditions for True Y/N Described in Condition Rule

Condition signal description column Condition

rule Conditions for true status
Input signal Condition specification column
ON/OFF status of contact I/O coincides with
Y
specification.
Element symbol.PV ON, OFF
ON/OFF status of contact I/O does not coincide with
N
specification.
Y Data status of contact I/O coincides with specification.
Element symbol.PV =Data status Data status of contact I/O does not coincide with
N
specification.
D030249E.ai

n Global Switch Reference

The syntax for applying the various types of data and data status of a global switch as condition
test reference signal in a sequence table and the True/False representation of Y/N in the
condition rule columns of the sequence table are shown as follows.
Table Syntax for condition signal description and True/False representation of Y/N in condition rule
columns

Condition signal description column Condition

rule Conditions for true status
Input signal Condition specification column
Y Specified global switch status is True.
Element symbol.PV ON, OFF
N Specified global switch status is False.
Y Data status of global switch is BAD.
Element symbol.PV =BAD
N Data status of global switch is not BAD.
D030250E.ai

n Common Switch Reference

The table below lists the condition signal symbolic convention for referencing various data and
status of the common switch as well as the conditions for true Y/N described in the condition rule.
Table Condition Signal Symbolic Convention and Conditions for True Y/N Described in Condition Rule

Condition signal description column Condition

rule Conditions for true status
Input signal Condition specification column
ON/OFF status of common switch coincides with
Y
specification.
Element symbol.PV ON, OFF
N ON/OFF status of common switch does not coincide with
specification.
D030251E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-56

n Annunciator Message Reference

The table below lists the condition signal symbolic convention for referencing various data
and status of the annunciator message as well as the conditions for true Y/N described in the
condition rule.
Table Condition Signal Symbolic Convention and Conditions for True Y/N Described in Condition Rule

Condition signal description column Condition

rule Conditions for true status
Input signal Condition specification column
Annunciator occurrence status coincides with
Y specification.
Element symbol.PV ON, OFF (ON: Occurred, OFF: Not occurred)
Annunciator occurrence status does not coincide with
N
specification.
Y Flashing status
element symbol.AFLS AFL
N Normal status (not flashing)
Y Alarm masking status
element symbol.AOFS AOF
N Normal status (no alarm masking status)
Repeated warning status coincides with specification.
Y
(ON: Waiting for repeated warning, OFF: NR)
element symbol.RP ON, OFF
Repeated warning status does not coincide with
N
specification.
D030252E.ai

n Communication I/O Reference

The table below lists the condition signal symbolic convention for referencing various data and
status of communication I/O as well as the conditions for true Y/N described in the condition rule.
Table Condition Signal Symbolic Convention and Conditions for True Y/N Described in Condition Rule

Condition signal description column Condition

rule Conditions for true status
Input signal Condition specification column
Y All relevant bits are in the same ON/OFF status.
Element symbol.PV (*1) ON, OFF
N Relevant bits are not in the same ON/OFF status.
Y All relevant bits are in the same data status.
Element symbol.PV =Data status
N Relevant bits are not in the same data status.
D030253E.ai

*1: Only discrete type element may be referred.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-57

D3.2.11 Control Signal Description: Referencing Sequence

Table
In a condition testing referencing a sequence table, in addition to the sequence table
block mode and status, the true/false status of condition can also be referenced by
performing one-shot execution of the referenced sequence table.
To reference a sequence table whose number of rules is extended over multiple sequence
tables, specify a tag name for the extending sequence table.

n Referencing an Entire Sequence Table

▼ Conditional Signal Description - Sequence Table
The true/false status of condition for the entire sequence table specified is referenced.
The table below lists the condition signal symbolic convention for referencing the entire sequence
table and the conditions for true Y/N described in the condition rule.
Table Condition Signal Symbolic Convention and Conditions for True Y/N Described in Condition Rule

Condition signal description column Condition

rule Conditions for true status
Input signal Condition specification column
Y At least one target condition rule is satisfied.
Element symbol. SD R
N None of the target condition rules is satisfied.
D030254E.ai

The condition rule subject to referencing varies by the type of sequence tables at reference
source and destination (step type/nonstep type) as shown below.
Table Reference Target Rules by Sequence Table Type
Reference source Reference destination Reference target rule
Nonstep type All rules
Nonstep type
Step type Rule of Step 00
Nonstep type All rules
Step type Rule of Step 00 and that of the same step
Step type
name as reference source
D030255E.ai

The following should be taken into account when referencing the entire sequence table.
• When referencing the entire sequence table, only condition signal descriptions of the
referenced sequence table are valid. Ignore any action signal description.
• If no Y/N pattern exists in the condition rule of referenced sequence table, the status of rule
condition is false. If the Y/N pattern of such condition rule is unspecified, the status becomes
unconditionally true in the periodic processing of the above sequence table.
• When there exist no steps to be executed in the referenced sequence table, the previous
true/false status of condition is maintained as a current reference result.
• When Step 00 exists in the reference destination, rules that belong to Step 00 will also be
executed. However, when no steps exist as an execution target, the reference result of Step
00 is ignored.
• Other sequence tables can be referenced in the referenced sequence table condition
column. In this case, up to seven levels of nests (including the first sequence table) are
possible.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-58
l When the Referenced Sequence Table is a Nonstep Type
A description example of the nonstep-type referenced sequence table is shown below.

ST 003 ST 010

Rule number 01 02 03 04 05 Rule number 01 02 03 04 05

Tag name Tag name
Data Data
Data item Step label Data item Step label
Comment Comment
DI0010.PV ON ................................ Y Y Y N DI0030.PV ON ............................. Y Y N
DI0015.PV ON ................................ Y N DI0031.PV ON ............................. Y Y N
ST010.SD R ................................ Y N DI0036.PV ON ............................. Y N N Y
DI0018.PV ON ................................ N Y Y %SW0201.PV ON ............................. Y N Y

DO0001.PV H ................................ Y N
DO0011.PV H ................................ Y N

D030256E.ai

Figure Description Example of Referencing the Entire Nonstep-Type Sequence Table

The following describes the condition testing processing for the above example.
• When “Y” is described in the condition rule of the condition signal ST010.SD.R.
In the description of the condition signal of the referenced sequence table, if there exists at
least one rule with a true status, the status of condition signal is true. If no such rules exist,
the condition of the referencing sequence table is false.
As for Rule 01 in Table ST003 listed above, the output signal of DO0001 is ON if the
condition signal DI0010.PV.ON is true, DI0015.PV.ON is true, DI0018.PV.ON is false, and
one of the conditions at rules 01 to 32 of Table ST010 is true.
• When “N” is described in the condition rule of the condition signal ST010.SD.R.
In the description of the condition signal of the referenced sequence table, if there exists no
rule with a true status, the status of condition signal is true. If there exists at least one rule
with a true status, the condition of the referencing sequence table is false.
As for Rule 03 in Table ST003 listed above, the output signal of DO0001 is OFF if the
condition signal DI0010.PV.ON is true, DI0015.PV.ON is false, and none of the conditions at
rules 01 to 32 of Table ST010 is true.
• The condition of rules that has no Y/N patterns in Table ST010 is false.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-59
l When the Referenced Sequence Table is a Step Type
A description example of the step-type referenced sequence table is shown below.
When both sequence tables at reference source and destination are a step type, the true/false
status of Step 00 rule condition and that of the rule with the same step name as the reference
source is referenced.

ST 003 ST 010

Rule number 01 02 03 04 05 Rule number 01 02 03 04 05

Tag name Tag name
Data Data
Data item Step label 1 2 3 4 Data item Step label 1 1 2 3
Comment Comment
DI0010.PV ON ................................ Y Y Y N DI0030.PV ON ............................. Y Y N
DI0015.PV ON ................................ Y N DI0031.PV ON ............................. Y Y N
ST010.SD R ................................ Y N DI0036.PV ON ............................. Y N N Y
DI0018.PV ON ................................ N Y Y %SW0201.PV ON ............................. Y N Y

DO0001.PV H ................................ Y N
DO0011.PV H ................................ Y N

D030257E.ai

Figure Description Example of Referencing the Entire Nonstep-Type Sequence Table

The following describes the condition testing processing for the above example.
• As for Rule 01 in Table ST003, the output signal of DO0001 is ON if the condition signal
DI0010.PV.ON is true, DI0015.PV.ON is true, DI0018.PV.ON is false, and one of the
conditions at Rule 01 or 02 of Table ST010 is true.
• As for Rule 03 in Table ST003, the output signal of DO0001 is OFF if the condition signal
DI0010.PV.ON is true, DI0015.PV.ON is false, and the condition at Rule 04, Step 3 of Table
ST010 is false.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-60
l When Step 00 and Step n Exist in a Referenced Sequence Table
A description example of when Step 00 and Step n exist in a referenced sequence table is shown
below.

ST 003 ST 010

Rule number 01 02 03 04 05 Rule number 01 02 03 04 05

Tag name Tag name
Data Data item Data
Data item Step label 1 Step label 0 0
2 3 4 1 2 3
Comment 0 0
Comment
DI0010.PV ON ................................ Y Y Y N DI0030.PV.ON ON ............................. Y Y N N
DI0015.PV ON ................................ Y N DI0031.PV.ON ON ............................. Y Y N N
ST010.SD R ................................ Y N DI0036.PV.ON ON ............................. Y N N Y N
DI0018.PV ON ................................ N Y Y %SW0201.PV ON ............................. Y N Y N

DO0001.PV H ................................ Y N
DO0011.PV H ................................ Y N

D030258E.ai

Figure Description Example of Referencing the Entire Step-Type Sequence Table

The following describes the condition testing processing for the above example.
• The reference range of the referenced table at Rule 01, Table ST003 is steps 00 and 1 of
Table ST010.
As for Rule 01 in Table ST003 listed above, the output signal of DO0001 is ON if the
condition signal DI0010.PV.ON is true, DI0015.PV.ON is true, DI0018.PV.ON is false, and
one of the conditions at Step 00 Rule 01/02 or Step 1 Rule 03 of Table ST010 are true.
• The reference range of the referenced table at Rule 03 of Table ST003 are steps 00 and 3 of
Table ST010.
As for Rule 03 in Table ST003 listed above, the output signal of DO0001 is OFF if the
condition signal DI0010.PV.ON is true, DI0015.PV.ON is false, and the condition at Step 00
Rule 01/02 or Step 3 Rule 05 of Table ST010 are false.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-61

n Referencing Sequence Table Corresponding Rule Number

The true/false status of condition for the same rule number as the current rule number in the
referencing sequence table is referenced. Use this to extend the number of condition signals
beyond 64 in a nonstep-type sequence table.
The table below lists the condition signal symbolic convention for referencing the true/false
status of the conditions for the corresponding rule number and the conditions for true Y/N status
described in the condition rule.
Table Condition Signal Symbolic Convention and Conditions for True Y/N Described in Condition Rule

Condition signal description column Condition

rule Conditions for true status
Input signal Condition specification column
Y Condition for the same rule number is satisfied.
Element symbol. SD C
N Condition for the same rule number is not satisfied.
D030259E.ai

• When the referenced sequence table is a nonstep type and the referencing sequence table
is a step type.
Although referencing a corresponding rule number is meaningless, condition reference to
the corresponding rule is executed.
• When the referenced sequence table is a step type.
Referencing the same rule is meaningless and therefore causes an error. However, the
status of condition signal is true.

The following should be taken into account when referencing a corresponding rule number.
• When referencing the entire sequence table, only condition signal descriptions of the
referenced sequence table are valid. Ignore any action signal description.
• If no Y/N pattern exists in the condition rule of referenced sequence table, the status of
rule condition is false. If the Y/N pattern of such a condition rule is unspecified, the status
becomes unconditionally true in the periodic processing of the above sequence table.
• Other sequence tables can be referenced in the referenced sequence table condition
column. In this case, up to seven levels of nests (including the first sequence table) are
possible.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-62
A description example of when referencing the true/false status of conditions for a corresponding
rule number is shown below.

ST 003 ST 010

Rule number 01 02 03 04 05 Rule number 01 02 03 04 05

Tag name Tag name
Data item Data Step label 1 Data item
Data
Step label
2 3 4
Comment Comment
DI0010.PV ON ................................ Y Y Y N DI0030.PV ON ............................. Y Y N
DI0015.PV ON ................................ Y N DI0031.PV ON ............................. Y Y N
ST010.SD C ................................ Y N DI0036.PV ON ............................. Y N N Y
DI0018.PV ON ................................ N Y Y %SW0201.PV ON ............................. Y N Y

DO0001.PV H ................................ Y N
DO0011.PV H ................................ Y N

D030260E.ai

Figure Description Example of Referencing the Corresponding Rule Number

The following describes the condition testing processing for the above example.
• As for Rule 01 in Table ST003, the output signal of DO0001 is ON if the condition signal
DI0010.PV.ON is true, DI0015.PV.ON is true, DI0018.PV.ON is false, and the conditions at
Rule 01 of Table ST010 are true.
• As for Rule 03 in Table ST003, the output signal of DO0001 is OFF if the condition signal
DI0010.PV.ON is true, DI0015.PV.ON is false, and the conditions at Rule 03 of Table ST010
are false.

IMPORTANT
When referencing a corresponding rule number, do not describe the step number on the step
label of the referenced sequence table.
When referencing a corresponding rule number, referencing cannot be properly performed if the
step number is described on the step label of the referenced sequence table.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-63

n Referencing a Particular Step in a Sequence Table

The true/false status of conditions for a particular step of a specified sequence table is
referenced.
The table below lists the condition signal symbolic convention for referencing the true/false status
of conditions for a particular step, and the conditions for true Y/N described in the condition rule.
The step label is specified in the condition specification.
Table Condition Signal Symbolic Convention and Conditions for True Y/N Described in Condition Rule

Condition signal description column Condition

rule Conditions for true status
Input signal Condition specification column
At least one of the conditions for steps 00 and xx is
Y
Element symbol. SA xx satisfied.
N None of the conditions for steps 00 and xx is satisfied.
D030261E.ai

xx: Specify a step label using 2 or less alphanumeric characters.

The condition rule subject to referencing varies by the type of sequence table at reference source
and destination (step-type/nonstep type) as shown below.
Table Reference Target Rules by Sequence Table Type
Reference source Reference destination Reference target condition rule
Nonstep type All rules
Nonstep type
Step type Rules of a specified step
Nonstep type All rules
Step type
Step type Rules of a specified step
D030262E.ai

• When the specified step does not exist in the referenced sequence table, the reference
result will be the previous true/false condition status that has been latched.
• When Step 00 exists in the reference destination, the rules belonging to Step 00 will also
be executed. However, when the specified step does not exist in the referenced sequence
table, the reference result of Step 00 is ignored.

The following should be taken into account when referencing a particular step.
• When referencing a particular step in the sequence table, only condition signal descriptions
of the referenced sequence table are valid. Ignore any action signal description.
• If no Y/N pattern exists in the condition rule of referenced sequence table, the status of
rule condition is false. If the Y/N pattern of such a condition rule is unspecified, the status
becomes unconditionally true in the periodic processing of the above sequence table.
• Other sequence tables can be referenced in the referenced sequence table condition
column. In this case, up to seven levels of nests (including the first sequence table) are
possible.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-64
A description example of referencing the true/false status of conditions for a particular step
number is shown below.

ST 003 ST 010

Rule number 01 02 03 04 05 Rule number 01 02 03 04 05

Tag name Tag name
Data item Data Data item Data
Step label 1 2 3 4 Step label 1 1 2 3
Comment Comment
DI0010.PV ON ................................ Y Y Y N DI0030.PV ON .............................. Y Y N
DI0015.PV ON ................................ Y N DI0031.PV ON .............................. Y Y N
ST010.SA 2 ................................ Y N DI0036.PV ON .............................. Y N N Y
DI0018.PV ON ................................ N Y Y %SW0201.PV ON .............................. Y N N Y

DO0001.PV H ................................ Y N
DO0011.PV H ................................ Y N

D030263E.ai

Figure Description Example of Referencing a Particular Step Number

The following describes the condition testing processing for the above example.
• As for Rule 01 in Table ST003, the output signal of DO0001 is ON if the condition signal
DI0010.PV.ON is true, DI0015.PV.ON is true, DI0018.PV.ON is false, and the conditions for
Step 2, or Rule 03 of Table ST010 are true.
• As for Rule 03 in Table ST003, the output signal of DO0001 is OFF if the condition signal
DI0010.PV.ON is true, DI0015.PV.ON is false, and the conditions for Step 2, or Rule 03 of
Table ST010 are false.

l When Steps 00 and n Exist in the Referenced Sequence Table

A description example of the sequence table when steps 00 and n exist in the referenced
sequence table are shown below.

ST 003 ST 010

Rule number 01 02 03 04 05 Rule number 01 02 03 04 05

Tag name Data Tag name Data
Data item Step label 1 2 3 4 Data item Step label 0 0
1 2 3
Comment Comment 0 0

DI0010.PV ON ................................ Y Y Y N DI0030.PV ON ............................... Y Y N N

DI0015.PV ON ................................ Y N DI0031.PV ON ............................... Y Y N N
ST010.SA 2 ................................ Y N DI0036.PV ON ............................... Y N N Y N
DI0018.PV ON ................................ N Y Y %SW0201.PV ON ............................... Y N Y N

DO0001.PV H ................................ Y N
DO0011.PV H ................................ Y N

D030264E.ai

Figure Description Example of Referencing a Particular Step Number

The table reference range for the rule number 01 of Table ST003 are steps 00 and 2 of Table
ST010 in the above example.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-65

n Sequence Table Step Label Reference

The progress status of a sequence phase can be confirmed by referencing the sequence table
step label. However, such confirmation does not involve the true/false status of step conditions
since it only determines whether or not a specified step processing is being performed in the
referenced sequence table.
The table below lists the condition signal symbolic convention for referencing the step label and
the conditions for true Y/N described in the condition rule.
Table Condition Signal Symbolic Convention and Conditions for True Y/N Described in Condition Rule

Condition signal description column Condition

rule Conditions for true status
Input signal Condition specification column
Y Current execution step label is xx.
Element symbol.PV xx
N Current execution step label is other than xx.
D030265E.ai

xx: Specify a step label using 2 or less alphanumeric characters.

A description example of referencing the execution status of Step 1 processing in Table ST010 is
shown below.

ST 003

Rule number 01 02 03 04 05 06 07
Tag name
Data item Data Step label
Comment
SW0110.PV ON ................................ Y Y
Condition
ST010.PV 1 ................................ Y N
ST010.SA 1 ................................ Y
Operation
SW0110.PV H ................................ N
D030266E.ai

Figure Description Example of Step Label Reference

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-66

n Sequence Table Block Mode Reference

The table below lists the condition signal symbolic convention for referencing the sequence table
block mode, and the conditions for true Y/N described in the condition rule.
Table Condition Signal Symbolic Convention and Conditions for True Y/N Described in Condition Rule

Condition signal description column Condition

rule Conditions for true status
Input signal Condition specification column
Y Block mode is in the specified state.
Element symbol.MODE O/S, MAN, AUT
N Block mode is not in the specified state.
D030267E.ai

A description example of restarting Table ST005 from the stop status is shown below.
Rule number 01 02 03 04 05 06 07
Tag name
Data Step label
Data item
Comment
ST005.MODE MAN .............................. Y
%SW0201.PV ON .............................. Y Condition

ST005.MODE AUT .............................. Y

Operation

D030268E.ai

Figure Description Example of Block Mode Reference

The following should be taken into account when referencing a sequence table block mode.
• When O/S is specified in the condition specification for block mode reference, the test result
will be unsatisfied in the compound block mode in which O/S and another basic block mode
are satisfied simultaneously.
• When MAN or AUT is specified in the condition specification for block mode reference, the
test result is satisfied even in the compound block mode as long as the specified basic block
mode is satisfied.

n Sequence Table Alarm Status Reference

The table below lists the condition signal symbolic convention for referencing the sequence table
alarm status and the conditions for true Y/N described in the condition rule.
Table Condition Signal Symbolic Convention and Conditions for True Y/N Described in Condition Rule

Condition signal description column Condition

rule Conditions for true status
Input signal Condition specification column
Y Alarm status is in the specified state.
Element symbol.ALRM NR
N Alarm status is not in the specified state.
Y Specified alarm is flashing.
Element symbol.AFLS AFL (*1), NR
N Specified alarm is not flashing.
Y Specified alarm detection is canceled.
Element symbol.AF NR
N Specified alarm is being detected.
Y Specified alarm is masked.
Element symbol.AOFS NR, AOF (*2)
N Specified alarm is unmasked.
D030269E.ai

*1: Condition Specification AFL references the group flashing status.

*2: Condition Specification AOF references the alarm group mask status.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-67

D3.2.12 Syntax for Condition Signal Description: Logic Chart

Reference in Sequence Table
When using logic chart for condition test, a block mode of a logic chart and an alarm
status of a logic chart can be used as a reference signal in a sequence table.

n Logic Chart Block Mode Reference

▼ Conditional Signal Description - Logic Chart
The specified logic chart block mode can be used as reference signal in a sequence table.
The syntax for applying the logic chart block mode as condition test reference signal in a
sequence table and the True/False representation of Y/N in the condition rule columns of the
sequence table are shown as follows.
Table Syntax for Condition Signal Description and True/False Representation of Y/N in Condition Rule
Columns
Condition signal description column Condition rule
Conditions for true status
Input signal Condition specification column

Y Specified Block mode is True.

Element symbol.MODE O/S, MAN, AUT
N Specified Block mode is False.
D030270E.ai

The following points should be taken into consideration when referencing a logic chart block mode.
• When O/S is specified as the condition specification for block mode reference, the test result
will be False when the block is in the compound block mode, i.e., O/S and another basic
block mode exist simultaneously.
• When MAN or AUT is specified as the condition specification for block mode reference, the
test result will be True even in the compound block mode as long as the specified basic
block mode exists.

n Logic Chart Alarm Status Reference

The specified alarm status of logic chart can be used as reference signal in a sequence table.
The syntax for applying the alarm status of logic chart as condition test reference signal in a
sequence table and the True/False representation of Y/N in the condition rule columns of the
sequence table are shown as follows.
Table Syntax for Condition Signal Description and True/False Representation of Y/N in Condition Rule
Columns
Condition signal description column Condition rule
Conditions for true status
Input signal Condition specification column

Y Specified Alarm Status is True.

Element symbol.ALM NR
N Specified Alarm Status is False.
Y Specified Alarm symbol is flashing.
Element symbol.AFLS AFL (*1), NR
N Specified Alarm symbol is not flashing.
Y Alarm Detection Disabled is True.
Element symbol.AF NR
N Alarm Detection Disabled is False.
Y Alarm Inhibition is True.
Element symbol.AOFS NR, AOF (*2)
N Alarm Inhibition is False.
D030271E.ai

*1: The condition test for Alarm Symbol Flashing can only test the flashing status of each block or symbol, can not test the flashing
status of each alarming item.
*2: The condition test for Alarm Inhibition can only test the inhibition status of each block or symbol, can not test the inhibition status
of each alarming item.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-68

D3.2.13 Description of Action Signal: Status Manipulation for

Other Function Blocks and I/O Data
Sequence Table Block may manipulate the mode or status change of other function
blocks. In addition, it can also manipulate the status change of process I/O, software I/O
and communication I/O.

n Function Blocks and I/O Data for Which Status Manipulation can be
Performed from Sequence Table
▼ Action Signal Description
Function blocks for which status manipulation can be performed from the sequence table are:
• Switch Instrument Blocks
• Timer Block (TM)
• Software Counter Block (CTS)
• Pulse Train Input Counter Block (CTP)
• Code Input Block (CI)
• Code Output Block (CO)
• Valve Monitoring Block (VLVM)
• Regulatory Control Blocks
• Calculation Blocks
• Faceplate Blocks
• SFC Blocks
• Unit Instrument Blocks
• Sequence Table Blocks
• Logic Chart Blocks

I/O data for which status manipulation can be performed from the sequence table are:
• Process I/O
• Software I/O (internal switch, annunciator message, sequence message output)
• Communication I/O

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-69

n Status Manipulation of Switch Instrument Block and Enhanced Switch

Instrument Block
The table below lists the symbolic convention of action signal and action description for executing
status manipulation on various functions of switch instrument block and enhanced switch
instrument block.
Table Symbolic Convention of Action Signal and Action Description
Action signal description column Action rule
column Action description
Output signal Action specification (Y/N)

MAN, AUT, CAS, Y Block mode change command

Element symbol.MODE
ROUT, O/S N –

ANS+, ANS-, IOP, Y Cancel specified alarm detection

Element symbol.AF
PERR, OOP, CNF N Execute specified alarm detection
Y Disables IOP and IOP- detection
Element symbol.XAF IOP
N Enables IOP and IOP- detection
ANS+, ANS-, PERR, Y Mask specified alarm
Element symbol.AOFS CNF, IOP, AOF (*1),
OOP N Unmask specified alarm
Y Perform alarm group confirmation
Element symbol.AFLS AFL
N –
Y Set the sequence setpoint (CSV) (*2)
0, 1, 2
N –
Y Set CSV to 0
P0
N Set CSV to 2
Element symbol.CSV
Y Set CSV to 1
P1
N –
Y Set CSV to 2
P2
N Set CSV to 0
Y Tracking switch (0: OFF, 1: ON)
Element symbol.TSW 0, 1
N –
Y Bypass switch (0: OFF, 1: ON)
Element symbol.BPSW 0, 1
N –
Y Backup switch (0: OFF, 1: ON)
Element symbol.BSW 0, 1
N –
Y Switch to CAL or release CAL
Element symbol.PV =XCAL (*3)
N –
D030272E.ai

*1: AOF specification is only effective for changing the alarm masking specification. This action performs alarm masking on all
alarms except NR.
*2: To set a manipulated output value for the switch instrument from other function block, write data to the sequence setpoint (CSV).
If the switch instrument block or enhanced switch instrument block is either in AUT or CAS state, the output will be performed
after the value of CSV is written to the manipulated output value (MV).
*3: The Output Timing of the sequence table that =XCAL is applied should be set to [Output Only When Condition Changes (C)].

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-70

n Status Manipulation of Timer Block (TM)

The table below lists the symbolic convention and action description of the action signal to
manipulate the status of various functions of the Timer Block (TM).
Table Symbolic Convention of Action Signal and Action Description

Action signal description column Action rule

column Action description
Output signal Action specification (Y/N)
Y Timer stop command
STOP
N –
Y Timer start command
START
N Timer stop command
Element symbol.OP
Y Restart command
RSTR
N –
Y Pause command
WAIT
N Restart command
D030273E.ai

n Status Manipulation of Software Counter Block (CTS)

The table below lists the symbolic convention and action description of the action signal to
manipulate the status of various functions of the Software Counter Block (CTS).
Table Symbolic Convention of Action Signal and Action Description

Action signal description column Action rule

column Action description
Output signal Action specification (Y/N)
Y Software counter operation command
ON
N –
Element symbol.ACT
Y Software counter stop command
OFF
N –
Y Trigger software counter (One Count)
Element symbol.XACT ON
N Stop software counter
D030274E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-71

n Status Manipulation of Pulse Train Input Counter Block (CTP)

The table below lists the symbolic convention and action description of the action signal to
manipulate the status of various functions of the Pulse Train Input Counter Block (CTP).
Table Symbolic Convention of Action Signal and Action Description

Action signal description column Action rule

column Action description
Output signal Action specification (Y/N)

Y Pulse input counter stop command

STOP
N –
Y Pulse input counter start command
START
N Pulse input counter stop command
Element symbol.OP
Y Restart command
RSTR
N –
Y Pause command
WAIT
N Restart command

Y Cancel specified alarm detection

Element symbol.AF IOP, CNF
N Execute specified alarm detection
Y Disables IOP and IOP- detection
Element symbol.XAF IOP
N Enables IOP and IOP- detection
Y Mask specified alarm
Element symbol.AOFS IP, CNF, AOF (*1)
N Unmask specified alarm
Y Perform alarm group confirmation
Element symbol.AFLS AFL
N –
D030275E.ai

*1: AOF specification is only effective for changing the alarm masking specification. This action operates alarm masking on all
alarms except NR.

n Status Manipulation of Code Input Block (CI)

The table below lists the symbolic convention and action description of the action signal to
manipulate the status of various functions of the Code Input Block (CI).
Table Symbolic Convention of Action Signal and Action Description

Action signal description column Action rule

column Action description
Output signal Action specification (Y/N)
Y Code input read command
Element symbol.ACT ON
N –
D030276E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-72

n Status Manipulation of Code Output Block (CO)

The table below lists the symbolic convention and action description of the action signal to
manipulate the status of various functions of the Code Output Block (CO).
Table Symbolic Convention of Action Signal and Action Description

Action signal description column Action rule

column Action description
Output signal Action specification (Y/N)
Code output command to contact output signal or internal
Y
Element symbol.ACT ON status switch
N Disable
D030277E.ai

n Status Manipulation of Resource Scheduler Block (RS)

The table below lists the symbolic convention and action description of the action signal to
manipulate the status of various functions of the Resource Scheduler Block (RS).
Table Symbolic Convention of Action Signal and Action Description
Action signal description column Action rule
column Action description
Output signal Action specification (Y/N)
Specified number usage cancel/request command
Y
Element symbol.RQ01 to 32 0, 1 (1: Request, 0: Cancel)
N Disable
Y Set the maximum allowable number (m≤32)
Element symbol.PMH 0 to 32
N Disable
Entire resource group request/cancel
Y
Element symbol.ACT ON, OFF (ON: Request, OFF: Cancel)
N Disable
D030278E.ai

n Status Manipulation of Valve Monitoring Block (VLVM)

The table below lists the symbolic convention and action description of the action signal to
manipulate the status of various functions of the Valve Monitoring Block (VLVM).
Table Symbolic Convention of Action Signal and Action Description

Action signal description column Action rule

column Action description
Output signal Action specification (Y/N)
Y Message suppression (1: Suppress, 0: Cancel)
Element symbol.MCSW 0, 1
N Disable
D030279E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-73

n Status Manipulation of Regulatory Control Block

The table below lists the symbolic convention and action description of the action signal to
manipulate the status of various functions of the regulatory control block.
Table Symbolic Convention of Action Signal and Action Description

Action signal description column Action rule

column Action description
Output signal Action specification (Y/N)
MAN, AUT, CAS, Y Block mode change command
Element symbol.MODE RCAS, ROUT, PRD,
O/S N Disable
Y Cancel specified alarm detection
Element symbol.AF Alarm status except NR
N Execute specified alarm detection
Y Disables IOP and IOP- detection
Element symbol.XAF IOP
N Enables IOP and IOP- detection

Alarm status except NR, Y Mask specified alarm

Element symbol.AOFS
AOF (*1) N Unmask specified alarm
Y Perform alarm group confirmation
Element symbol.AFLS AFL
N Disable
Y Set data
Element symbol.data item Data value
N Disable
Y Switch PV to CAL status
Element symbol.PV =CAL
N Release PV from CAL status
Y Switch to CAL or release CAL
Element symbol.PV =XCAL (*2)
N –
Y Switch to CAL or release CAL
Element symbol.SUM0 =XCAL (*2)
N –
D030280E.ai

*1: AOF specification is only effective for changing the alarm masking specification. This action performs alarm masking on all
alarms except NR.
*2: The Output Timing of the sequence table that =XCAL is applied should be set to [Output Only When Condition Changes (C)].

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-74
l Regulatory Control Block that can Describe Data Values in Action
Specifications
The table below lists the regulatory control blocks that can describe data values in action
specifications and the setting ranges of data items.
Table Regulatory Control Blocks that can Describe Data Values in Action Specifications and the
Setting Ranges of Data Items (1/3)
Block code Name Data item Setting range
TSW 0, 1
CSW 0, 1
PID PID Controller Block PSW 0 to 3
BSW 0, 1
RSW 0, 1
TSW 0, 1
CSW 0, 1
PI-HLD Sampling PI Controller Block PSW 0 to 3
BSW 0, 1
RSW 0, 1
TSW 0, 1
CSW 0, 1
PID-BSW PID Controller Block with Batch Switch PSW 0 to 3
BSW 0, 1
RSW 0, 1
CSW 0, 1
PID-TP Time-Proportioning ON/OFF Controller Block PSW 0 to 3
BSW 0, 1
PSW 0 to 3
ONOFF 2-Position ON/OFF Controller Block
BSW 0, 1
PSW 0 to 3
ONOFF-E Enhanced 2-Position ON/OFF Controller Block
BSW 0, 1
PSW 0 to 3
ONOFF-G 3-Position ON/OFF Controller Block
BSW 0, 1
PSW 0 to 3
ONOFF-GE Enhanced 3-Position ON/OFF Controller Block
BSW 0, 1
TSW 0, 1
PSW 0 to 3
PD-MR PD Controller Block with Manual Reset
BSW 0, 1
RSW 0, 1
TSW 0, 1
PSW 0 to 3
PI-BLEND Blending PI Controller Block BSW 0, 1
RSW 0, 1
RST 0, 1
Block code Name Data item Setting range
D030281E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-75
Table Regulatory Control Blocks that can Describe Data Values in Action Specifications and the
Setting Ranges of Data Items (2/3)
Block code Name Data item Setting range
TSW 0, 1
CSW 0, 1
PSW 0 to 3
PID-STC Self-Tuning PID Controller Block
BSW 0, 1
RSW 0, 1
STC -1 to 3
TSW 0, 1
MLD Manual Loader Block
RSW 0, 1
TSW 0, 1
MLD-PVI Manual Loader Block with Input Indicator
RSW 0, 1
TSW 0, 1
MLD-SW Manual Loader Block with Auto/Man SW PSW 0 to 3
RSW 0, 1
TSW 0, 1
BSW 0, 1
BPSW 0 to 4
MC-2 2-Position Motor Control Block
SIMM 0 to 1
0, 1, 2, P0, P1,
CSV P2 (*1)
TSW 0, 1
BSW 0, 1
BPSW 0 to 4
MC-2E Enhanced 2-Position Motor Control Block
SIMM 0 to 1
0, 1, 2, P0, P1,
CSV P2 (*1)
TSW 0, 1
BSW 0, 1
BPSW 0 to 4
MC- 3 3-Position Motor Control Block
SIMM 0 to 1
0, 1, 2, P0, P1,
CSV P2 (*1)
TSW 0, 1
BSW 0, 1
BPSW 0 to 4
MC- 3E Enhanced 3-Position Motor Control Block
SIMM 0 to 1
0, 1, 2, P0, P1,
CSV P2 (*1)

Block code Name Data item Setting range

D030282E.ai

*1: The value set for the CSV varies depending on the values of action rules and setting range.
0: CSV = 0 when the action rule is [Y], Disable when [N]
1: CSV = 1 when the action rule is [Y], Disable when [N]
2: CSV = 2 when the action rule is [Y], Disable when [N]
P0: CSV = 0 when the action rule is [Y], CSV = 2 when [N]
P1: CSV = 1 when the action rule is [Y], Disable when [N]
P2: CSV = 2 when the action rule is [Y], CSV = 0 when [N]

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-76
Table Regulatory Control Blocks that can Describe Data Values in Action Specifications and the
Setting Ranges of Data Items (3/3)
Block code Name Data item Setting range
TSW 0, 1
PSW 0 to 3
RATIO Ratio Set Block
BSW 0, 1
RSW 0, 1
ZONE 1 to 13
PG-L13 13-Zone Program Set Block ZSTR 1 to 13
ZEND 1 to 13
SW 0 to 4
BSETU-2 Flow-Totalizing Batch Set Block EMSW 0, 1
ZONE 0 to 11
SW 0 to 4
BSETU-3 Weight-Totalizing Batch Set Block EMSW 0, 1
ZONE 0 to 11
PSW 0 to 3
VELLIM Velocity Limiter Block BSW 0, 1
BPSW 0, 1
SS-H/M/L Signal Selectors SW 0 to 4
PSW 0 to 3
AS-H/M/L Auto Selectors
SW 0 to 4
SS-DUAL Dual-Redundant Signal Selector Block SW 1 to 3
TSW 0, 1
PSW 0 to 3
FFSUM Feedforward Signal Summing Block
FSW 0, 1
RSW 0, 1
TSW 0, 1
XCPL Non-Interference Control Output Block PSW 0 to 3
RSW 0, 1
BSW 0, 1
SPLIT Control Signal Splitter Block
SW 0 to 3
RST 0, 1
PTC Pulse Count Input Block
HSW 0, 1
SW 0 to 5
ALM-R Representative Alarm Block
SV 0 to 15
SBSD YS Instrument Batch Set Station Block SV 0 to 8
SLBC YS Instrument Batch Controller Block SV 0 to 8
D030283E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-77

n Status Manipulation of Calculation Block

The table below lists the symbolic convention and action description of the action signal to
manipulate the status of various functions of the calculation block.
Table Symbolic Convention of Action Signal and Action Description

Action signal description column Action rule

column Action description
Output signal Action specification (Y/N)
Y One-shot execution (with parameter)
mm (*1)
N Disable
Element symbol.ACT
Y One-shot execution (without parameter)
ON
N Disable
Y Cancel specified alarm detection
Element symbol.AF Alarm status except NR
N Execute specified alarm detection
Y Disables IOP and IOP- detection
Element symbol.XAF IOP
N Enables IOP and IOP- detection

Alarm status except NR, Y Mask specified alarm

Element symbol.AOFS
AOF (*2) N Unmask specified alarm
Y Perform alarm group confirmation
Element symbol.AFLS AFL
N Disable

Element symbol. Y Set data

Data value
data item N Disable
Y Change CPV's data status to CAL
Element symbol.CPV =CAL
N Cancel CPV's CAL data status
Y Switch to CAL or release CAL
Element symbol.CPV =XCAL (*3)
N –
Y Switch to CAL or release CAL
Element symbol.CPV1 =XCAL (*3)
N –
Y Switch to CAL or release CAL
Element symbol.CPV2 =XCAL (*3)
N –
D030284E.ai

*1: mm is a parameter required for one-shot execution of the batch data setting block and the batch data acquisition block. The data
set at the one-shot execution varies depending on the mm value.
mm=0: Set 0 to all data.
mm=1 to 16: Set specified data only (DTn).
mm=17: Set all data.
*2: AOF specification is only effective for changing the alarm masking specification. This operation performs alarm masking on all
alarms except NR.
*3: The Output Timing of the sequence table that =XCAL is applied should be set to [Output Only When Condition Changes (C)].

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-78
l Calculation Blocks That Can Describe Data Values In Condition
Specifications
The table below lists the data items of regulatory control blocks that can describe data values in
condition specifications and their setting ranges.
Table Calculation Blocks that can Describe Data Values in Action Specifications and Setting Range of
Data Items
Block code Name Data item Setting range
DLAY Dead-Time Block
DLAY-C Dead-Time Compensation Block RST 0, 1
AVE-M Moving-Average Block
AVE-C Cumulative Average Block
SW 0, 1, 2
INTEG Integration Block
SW-33 Three-Pole Three-Position Selector Switch SW 0 to 3
SW-91 One-Pole Nine-Position Selector Switch SW 0 to 9
DSW-16 Selector Switch Block for 16 Data
SW 0 to 16
DSW-16C Selector Switch Block for 16 String Data
BDSET-1L One Batch Data Set Block
BDSET-1C One-Batch String Data Set Block
SW 0 to 3
BDSET-2L Two Batch Data Set Block
BDSET-2C Two-Batch String Data Set Block
BDA-L Batch Data Acquisition Block
SW 0 to 17
BDA-C Batch String Data Acquisition Block
ADL Inter-Station Data Link Block SIMM 0, 1
D030285E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-79
l Executable Calculation Block for One-Shot Execution
The table below lists the calculation blocks that can specify one-shot execution as an action
specification.
Table One-Shot Executable Calculation Block
Block type Code Name
ADD Addition Block
MUL Multiplication Block
Arithmetic Calculation
DIV Division Block
AVE Averaging Block
AND Logical AND Block
OR Logical OR Block
NOT Logical NOT Block
SRS1-S Set-Dominant Flip-Flop Block with 1 Output
SRS1-R Reset-Dominant Flip-Flop Block with 1 Output
SRS2-S Set-Dominant Flip-Flop Block with 2 Outputs
SRS2-R Reset-Dominant Flip-Flop Block with 2 Outputs
Logic Operation (*1)
WOUT Wipeout Block
GT Comparator Block (Greater Than)
GE Comparator Block (Greater Than or Equal)
EQ Equal Operator Block
BAND Bitwise AND Block
BOR Bitwise OR Block
BNOT Bitwise NOT Block

General-Purpose CALCU General-Purpose Calculation Block

Calculations CALCU-C General-Purpose Calculation Block with String I/O
BDSET-1L One-Batch Data Set Block
BDSET-1C One-Batch String Data Set Block
BDSET-2L Two-Batch Data Set Block
Calculation auxiliary
BDSET-2C Two-Batch String Data Set Block
BDA-L Batch Data Acquisition Block
BDA-C Batch String Data Acquisition Block
D030286E.ai

*1: Logic Operation Block can be used in FCSs except PFCS.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-80
l Calculation Block that Requires mm Parameter for One-Shot Execution
The table below lists the calculation blocks that are required to specify one-shot execution
parameter mm as an action specification.
Table Calculation Blocks That is Required to Specify Parameter mm in the Action Specification
Parameter setting
Block code Name Remarks
range (mm)
BDSET-1L One-Batch Data Set Block
BDSET-1C One-Batch String Data Set Block Set individual
0 to 17
BDSET-2L Two-Batch Data Set Block data

BDSET-2C Two-Batch String Data Set Block

BDA-L Batch Data Acquisition Block Acquire
0 to 17
BDA-C Batch String Data Acquisition Block individual data
D030287E.ai

Note: Parameter mm is defined as follows.

mm=0: Set 0 to all data.
mm=1 to 16: Set specified data only (DTn).
mm=17: Set all data.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-81

n Status Manipulation of Faceplate Block

The table below lists the symbolic convention and action description of the action signal to
manipulate the status of various functions of the faceplate block.
Table Symbolic Convention of Action Signal and Action Description

Action signal description column Action rule

column Action description
Output signal Action specification (Y/N)
Y Change block mode
Element symbol.MODE Block mode
N Disable
Y Change block status
Element symbol.BSTS Block status
N Cancel block status
Y Change alarm status
Element symbol.ALRM Alarm status except NR
N Cancel alarm status
Y Cancel the specified alarm detection.
Element symbol.AF Alarm status except NR
N Execute the specified alarm detection.

Alarm status except NR, Y Mask the specified alarm.

Element symbol.AOFS
AOF (*1) N Unmask the specified alarm.
Y Perform alarm group confirmation.
Element symbol.AFLS AFL
N Disable
Y Set batch step number (Effective only for BSI block)
Element symbol.SV 1 to 99
N Disable

Element symbol. Y Set action command

0, 1
PV01 to 10 N Disable
Y Change switch display color
Element symbol.SWCR[n] (*2) 0 to 15
N Disable
Y Switch flashing status ON/OFF
Element symbol.SWST[n] (*2) 0, 1
N Disable
Y Change the switch operation disable status
Element symbol.SWOP[n] (*2) -15 to 15
N Disable
D030288E.ai

*1: AOF specification is only effective for changing the alarm masking specification. This operation performs alarm masking on all
alarms except NR.
*2: n is the subscript of the 1 dimensional array. This subscript is the number of the push button switches on a faceplate block. This
number varies with the type of faceplate block.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-82

n Status Manipulation of Sequential Function Chart (SFC) Block

The table below lists the symbolic convention and action description of the action signal to
manipulate the status of various functions of the sequential function chart (SFC) block.
Table Symbolic Convention of Action Signal and Action Description

Action signal description column Action rule

column Action description
Output signal Action specification (Y/N)
Y Block mode change command
Element symbol.MODE MAN, AUT
N Disable
RUN, PAUS, STOP, Y Block status change command
Element symbol.BSTS
ABRT
N Disable
Y Cancel the specified alarm detection
Element symbol.AF Alarm status except NR
N Execute the specified alarm detection

Alarm status except NR, Y Mask the specified alarm

Element symbol.AOFS
AOF (*1) N Unmask specified alarm
Y Perform alarm group confirmation
Element symbol.AFLS AFL
N Disable
Y Set data
Element symbol.data item Data value
N Disable
Y Change PV's data status to CAL
Element symbol.PV =CAL
N Cancel PV's CAL data status
Y Switch to CAL or release CAL
Element symbol.PV =XCAL (*2)
N –
D030289E.ai

*1: AOF specification is only effective for changing the alarm masking specification. This operation performs alarm masking on all
alarms except NR.
*2: The Output Timing of the sequence table that =XCAL is applied should be set to [Output Only When Condition Changes (C)].

l Sequential Function Chart Block Data Item that can be Described as a Data
Value in the Action Specification
The following table lists the sequential function chart block data item which can be described as a
data value in the action specification, and their setting ranges.
• STEPNO: 1 to 99
• SWCR[5]: 0 to 15
• SWST[5]: 0, 1
• SWOP[5]: -15 to 15

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-83

n Status Manipulation of Unit Instrument

The table below lists the symbolic convention and action description of the action signal to
manipulate the status of various functions of the unit instrument.
Table Symbolic Convention of Action Signal and Action Description

Action signal description column Action rule

column Action description
Output signal Action specification (Y/N)
Y Unit mode change command
Element symbol.MODE MAN, SEMI, AUT
N Disable
Unit status change Y Unit status change command
Element symbol.UBSC
command name
N Disable
Y Cancel the specified alarm detection.
Element symbol.AF Alarm status except NR
N Execute the specified alarm detection.

Alarm status except NR, Y Mask the specified alarm.

Element symbol.AOFS
AOF (*1) N Unmask specified alarm.
Y Perform alarm group confirmation.
Element symbol.AFLS AFL
N Disable
Y Change SFC step number.
Element symbol.STEPNO 1 to 99
N Disable
D030290E.ai

*1: AOF specification is only effective for changing the alarm masking specification. This operation performs alarm masking on all
alarms except NR.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-84

n Status Manipulation of Process I/O

The table below lists the symbolic convention and action description of the action signal to
manipulate the status of various functions of the process I/O.
Table Symbolic Convention of Action Signal and Action Description

Action signal description column Action rule

column Action description
Output signal Action specification (Y/N)
Y Contact output ON (Latched output)
H
N Contact output OFF (Latched output)
Y Contact output ON (Unlatched output) (*1)
L Disable
N
Contact output OFF (*2)
Element symbol.PV
Y Cause flashing state.
F
N Stop the flashing state (*3)
Y Output one-second pulse to the relevant bit (*4)
P Disable
N
The pulse output being turned on is turned off. (*5)
D030291E.ai

*1: On KFCS2, FFCS and LFCS2, when the check box of [CENTUM-XL Compatible Sequence Tables] in the [Constant] tab on FCS
Properties sheet is checked, while the process timing of the sequence table is TC (Periodic Execution and Output only when
conditions change) or TE (Periodic Execution and Output when conditions are satisfied), the contact output scripted in the action
part of a rule will be turned off upon condition changes from true to false even if the step has moved to another. However, when
the check box of [CENTUM-XL Compatible Sequence Tables] is not checked, the contact output will not be turned off when the
step has moved to another upon the condition changes from true to false.
By default, this check box is not checked.
*2: On KFCS2, FFCS and LFCS2, when the check box of [CENTUM-XL Compatible Sequence Tables] in the [Constant] tab on FCS
Properties sheet is checked, the contact output scripted in the action part of a rule will be turned off when condition becomes true.
However, when condition becomes false, N means no action. Nevertheless, when the check box of [CENTUM-XL Compatible
Sequence Tables] is not checked, N means no action even when condition is true.
By default, this check box is not checked.
*3: Even though the flashing state stops, the contact output itself remains ON. Turn off the contact output using a different action
signal with a latched contact output.
*4: Not available in LFCS2 or LFCS. For LFCS2 or LFCS to give a pulse output, first to set the point mode of the output terminal
on IOM into Pulse Output (PO), then put a latched type symbol (H) or none latched type symbol (L) in the action columns of
sequence table.
*5: On KFCS2, FFCS and LFCS2, when the check box of [CENTUM-XL Compatible Sequence Tables] in the [Constant] tab on FCS
Properties sheet is checked, the pulse output scripted in the action part of a rule will be turned off when condition becomes true.
Nevertheless, when the check box of [CENTUM-XL Compatible Sequence Tables] is not checked, N means no action. However,
in LFCS2, N means no action regardless if the checked box is checked or not.
By default, this check box is not checked.

SEE
ALSO For more information about pulse output, see the following:
“l Pulse Contact Output : PFCS/KFCS2/KFCS/FFCS/SFCS” in section “n Manipulating Status Output of
I/O Module” of chapter A3.2.2, “Contact Output.”
“l Pulse Contact Output : LFCS2/LFCS” in section “n Manipulating Status Output of I/O Module” of
chapter A3.2.2, “Contact Output.”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-85

n Status Manipulation of Global Switch

The syntax in action signal description for manipulating the global switch to perform its various
functions and the output actions corresponding to Y/N in the action rule columns of the sequence
table are shown as follows.
Table Syntax in Action Signal Description and Output Actions Corresponding to Y/N in Action Rule
Columns

Action signal description column Action rule

column Action description
Output signal Action specification (Y/N)
Y Global switch output ON (Latched)
H
N Global switch output OFF (Latched)
Element symbol.PV Y Global switch output ON (Unlatched) (*1)
L Disable
N
Global Switch output OFF (*2)
D030292E.ai

*1: On KFCS2, FFCS and LFCS2, when the check box of [CENTUM-XL Compatible Sequence Tables] in the [Constant] tab on FCS
Properties sheet is checked, while the process timing of the sequence table is TC (Periodic Execution and Output only when
conditions change) or TE (Periodic Execution and Output when conditions are satisfied), the global switch scripted in the action
part of a rule will be turned off upon condition changes from true to false even if the step has moved to another. However, when
the check box of [CENTUM-XL Compatible Sequence Tables] is not checked, the global switch will not be turned off when the
step has moved to another upon the condition changes from true to false.
By default, this check box is not checked.
*2: On KFCS2, FFCS and LFCS2, when the check box of [CENTUM-XL Compatible Sequence Tables] in the [Constant] tab on FCS
Properties sheet is checked, the global switch scripted in the action part of a rule will be turned off when condition becomes true.
However, when condition becomes false, N means no action. Nevertheless, when the check box of [CENTUM-XL Compatible
Sequence Tables] is not checked, N means no action even when condition is true.
By default, this check box is not checked.

n Status Manipulation of Common Switch

The table below lists the symbolic convention and action description of the action signal to
manipulate the status of various functions of the common switch.
Table Symbolic Convention of Action Signal and Action Description

Action signal description column Action rule

column Action description
Output signal Action specification (Y/N)
Y Common switch output ON (Latched output)
H
N Common switch output OFF (Latched output)
Element symbol.PV Y Common switch output ON (Unlatched output) (*1)
L Disable
N
Common Switch output OFF (*2)
D030293E.ai

*1: On KFCS2, FFCS and LFCS2, when the check box of [CENTUM-XL Compatible Sequence Tables] in the [Constant] tab on FCS
Properties sheet is checked, while the process timing of the sequence table is TC (Periodic Execution and Output only when
conditions change) or TE (Periodic Execution and Output when conditions are satisfied), the common switch scripted in the
action part of a rule will be turned off upon condition changes from true to false even if the step has moved to another. However,
when the check box of [CENTUM-XL Compatible Sequence Tables] is not checked, the common switch will not be turned off
when the step has moved to another upon the condition changes from true to false.
By default, this check box is not checked.
*2: On KFCS2, FFCS and LFCS2, when the check box of [CENTUM-XL Compatible Sequence Tables] in the [Constant] tab on
FCS Properties sheet is checked, the common switch scripted in the action part of a rule will be turned off when condition
becomes true. However, when condition becomes false, N means no action. Nevertheless, when the check box of [CENTUM-XL
Compatible Sequence Tables] is not checked, N means no action even when condition is true.
By default, this check box is not checked.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-86

n Status Manipulation of Annunciator Message

The table below lists the symbolic convention and action description of the action signal to
manipulate the status of various functions of the annunciator message.
Table Symbolic Convention of Action Signal and Action Description

Action signal description column Action rule

column Action description
Output signal Action specification (Y/N)
Y Annunciator output (Latched output)
H
N Cancel the annunciator output (Latched output)
Element symbol.PV Y Annunciator output (Unlatched output) (*1)
L Disable
N
Cancel the annunciator output (*2)
Repeated warning specification
Y
Element symbol.RP ON, OFF (ON: Repeated warning, OFF: Cancel)
N Disable
Y Mask the specified alarm.
Element symbol.AOFS AOF
N Unmask the specified alarm.
Y Perform alarm group confirmation.
Element symbol.AFLS AFL
N Disable
D030294E.ai

*1: On KFCS2, FFCS and LFCS2, when the check box of [CENTUM-XL Compatible Sequence Tables] in the [Constant] tab on FCS
Properties sheet is checked, while the process timing of the sequence table is TC (Periodic Execution and Output only when
conditions change) or TE (Periodic Execution and Output when conditions are satisfied), the annunciator scripted in the action
part of a rule will be turned off upon condition changes from true to false even if the step has moved to another. However, when
the check box of [CENTUM-XL Compatible Sequence Tables] is not checked, the annunciator will not be turned off when the step
has moved to another upon the condition changes from true to false.
By default, this check box is not checked.
*2: On KFCS2, FFCS and LFCS2, when the check box of [CENTUM-XL Compatible Sequence Tables] in the [Constant] tab on FCS
Properties sheet is checked, the annunciator scripted in the action part of a rule will be turned off when condition becomes true.
However, when condition becomes false, N means no action. Nevertheless, when the check box of [CENTUM-XL Compatible
Sequence Tables] is not checked, N means no action even when condition is true.
By default, this check box is not checked.

n Status Manipulation of Sequence Message Output

The manipulation contents and description symbolic convention of the action signals when
performing status manipulation for the various message functions for sequence control are
indicated below.
The messages used in sequence controls include the messages attached with parameters
(constants) and the messages without parameters. Usage of the sequence control messages for
manipulating sequence signals varies with the messages with or without parameters.
The sequence control messages without parameters consist of the following types of messages:
• Print message output (%PR)
• Operator guide message output (%OG)
• Multimedia function message output (%VM)
• Sequence message request (%RQ)
• Event message output for supervisory computer (%CP)
• PICOT supervisory computer event message output (%M3)

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-87
The sequence control messages attached with parameters consist of the following types of
messages:
• Print message attached with parameters (%PR)
• Signal event message output (%EV)
• SFC/SEBOL return event message output (%RE)
Table Symbolic Convention of Action Signal and Action Description

Action signal description column Action rule

column Action description
Output signal Action specification (Y/N)
Y Sequence message output without parameter
NON
N Disable
Element symbol.PV
Y Sequence message output with parameter
mm (*1)
N Disable
D030295E.ai

*1 Integer type data (2-byte unsigned integer type data) can be specified for mm.
Range: Integer from 0 to 65535

n Status Manipulation of Communication I/O

The table below lists the symbolic convention and action description of the action signal to
manipulate the status of various functions of the communication I/O.
Table Symbolic Convention of Action Signal and Action Description

Action signal description column Action rule

column Action description
Output signal Action specification (Y/N)
Y Relevant bit ON (Latched output)
H
N Relevant bit OFF (Latched output)
Element symbol.PV Y Relevant bit ON (Unlatched output) (*1)
L Disable
N Relevant bit OFF (*2)
D030296E.ai

*1: On KFCS2, FFCS and LFCS2, when the check box of [CENTUM-XL Compatible Sequence Tables] in the [Constant] tab on FCS
Properties sheet is checked, while the process timing of the sequence table is TC (Periodic Execution and Output only when
conditions change) or TE (Periodic Execution and Output when conditions are satisfied), the relevant bit scripted in the action
part of a rule will be turned off upon condition changes from true to false even if the step has moved to another. However, when
the check box of [CENTUM-XL Compatible Sequence Tables] is not checked, the relevant bit will not be turned off when the step
has moved to another upon the condition changes from true to false.
By default, this check box is not checked.
*2: On KFCS2, FFCS and LFCS2, when the check box of [CENTUM-XL Compatible Sequence Tables] in the [Constant] tab on FCS
Properties sheet is checked, the relevant bit scripted in the action part of a rule will be turned off when condition becomes true.
However, when condition becomes false, N means no action. Nevertheless, when the check box of [CENTUM-XL Compatible
Sequence Tables] is not checked, N means no action even when condition is true.
By default, this check box is not checked.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-88

D3.2.14 Action Signal Description: Status Manipulation for

Sequence Table
In the status manipulation for sequence table, in addition to data setting and status
change, a series of processing from condition testing to status manipulation can be
performed by one-shot execution of the sequence table.
For status manipulation of a sequence table with rules extended to multiple sequence
tables, a tag name for the extending sequence table must be specified.
There exist several types of status manipulations for sequence table as shown below.
• Execution of the entire sequence table
• Execution of the corresponding rule number in sequence table
• Execution of a particular step(s)
• Setting of a sequence table execution step label
• Change of the sequence table block mode

n Execution of the Entire Sequence Table

▼ Action Signal Description - Sequence Table
The sequence table indicated by an element symbol of the action signal from the referencing
sequence table (branched sequence table) is activated to perform one-shot execution.
If the branched sequence table is a nonstep type, the entire table is subject to execution.
If the branched sequence table is a step type, the relevant steps according to the step processing
in the branched sequence table are subject to execution.
It is possible to further branch from a branched sequence table to other sequence table to
perform condition testing and actions for the first branched sequence table. Nesting is available
up to seven levels including the first sequence table.

l When the Branched Sequence Table is a Nonstep Type

The entire branched sequence table is executed.
The table below lists the symbolic convention and action description for the action signal used to
execute the entire branched sequence table.
Table Symbolic Convention and Action Description for Action Signal

Action signal description

Action rule Action description
Output signal Action specification
Y Execute the specified table
Element symbol.ACT ON
N Disable
D030297E.ai

When the conditions described in the condition rule are satisfied, the sequence table number
listed in the action signal symbol column will be one-shot executed to branch to the activated
sequence table. After executing all condition testing and actions, it returns to the action rule
processing in the branching sequence table.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-89
l When the Branched Sequence Table is a Nonstep Type
Description examples for the nonstep-type branched sequence tables are shown below.
Assume that “Output Only when Conditions Change” is specified for the output timing.

ST 005 ST 015

Rule number 01 02 03 04 05 Rule number 01 02 03 04 05

Tag name Tag name
Data item Data Step label Data item Data Step label
Comment Comment
DI0010.PV ON ................................ Y Y N DI0030.PV ON ................................ Y Y N
DI0015.PV ON ................................ Y N N DI0031.PV ON ................................ Y Y N
DI0016.PV ON ................................ Y Y Y Y DI0036.PV ON ................................ Y N N
DI0018.PV ON ................................ N N Y DI0038.PV ON ................................ Y N Y
DI0020.PV ON ................................ Y Y DI0125.PV ON Y Y Y Y
DI0021.PV ON ................................

DO0001.PV H Y Y N DO0050.PV H ................................ Y N Y

DO0011.PV H ................................ Y DO0052.PV H ................................ Y N
ST015.ACT ON ................................ Y Y DO0053.PV H ................................ Y N Y
DO0014.PV H ................................ Y Y DO0054.PV H ................................ N Y Y
DO0035.PV H ................................ Y Y DO0066.PV H ................................ N Y Y

D030298E.ai

Figure Description Examples of Nonstep-Type Sequence Table Execution

The following explains the details of action rule processing in the description examples shown
above.
• If the conditions in Rule 01 of Table ST005 are satisfied, the DO001.PV.H=Y operation will
be executed and all the conditions from rules 01 to 32 will then be tested after branching to
Table ST015. If conditions are satisfied at Table ST015, operations will be executed for the
rules whose conditions have been satisfied. It will then return to Table ST005 action rule
processing to execute the DO0014.PV.H=Y operation.
• Neither Rule 02 nor 03 on table ST005 is associated with the action rule processing
because no action descriptions for Table ST015 are listed in either rule.
• If the conditions in Rule 04 of Table ST005 are satisfied, the DO001.PV.H=N operation will
be executed and all the conditions from rules 01 to 32 will then be tested after branching to
Table ST015. If conditions are satisfied at Table ST015, operations will be executed for the
rules whose conditions have been satisfied. It will then return to Table ST005 action rule
processing to execute the DO0014.PV.H=Y and DO0035.PV.H=Y operations.
• If the periodic execution is specified for the processing timing of Table ST015, in addition
to one-shot execution caused by status manipulation, periodic execution will also be
performed at Table ST015.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-90
l When the Branched Sequence Table is a Step Type
Description examples for the step-type branched sequence table is shown below. Assume that
“Output Only when Conditions Change” is specified for the output timing.

If the branched sequence table is a step type, steps will be executed under the step management
of the branched sequence table.

ST 005 ST 015

Rule number 01 02 03 04 05 Rule number 01 02 03 04 05

Tag name Tag name
Data item Data Data
Step label 1 2 3 4 Data item Step label 1 2 2 3
Comment Comment
DI0010.PV ON ................................ Y Y N DI0030.PV ON ................................ Y Y N
DI0015.PV ON ................................ Y N N DI0031.PV ON ................................ Y Y N
DI0016.PV ON ................................ Y Y Y Y DI0036.PV ON ................................ Y N N
DI0018.PV ON ................................ N N Y DI0038.PV ON ................................ Y N Y
DI0020.PV ON ................................ Y Y DI0125.PV ON Y Y Y Y
DI0021.PV ON ................................

DO0001.PV H Y Y N DO0050.PV H ................................ Y N

DO0011.PV H ................................ Y N DO0052.PV H ................................ Y N
ST015.ACT ON ................................ Y Y DO0053.PV H ................................ Y N Y
DO0014.PV H ................................ Y Y DO0054.PV H ................................ N Y Y
DO0035.PV H ................................ Y Y DO0061.PV H ................................ N Y

THEN 2 3 1
ELSE

D030299E.ai

Figure Description Examples of Step-Type Sequence Table Execution

The following explains the details of action rule processing in the description examples shown
above.
• If the conditions in Rule 01 of Table ST005 are satisfied, the DO001.PV.H=Y operation
will be executed to branch to Table ST015. If the execution step label (PV) is Step 2, the
condition testing for rules 02 and 03 of Step 2 will be performed. If conditions are satisfied,
operations for the rules whose conditions have been satisfied will be executed. It will then
return to Table ST005 to execute the DO0014.PV.H=Y operation.
• If the step label is described on the branched sequence table, a processing will be executed
according to the step management of the branched sequence table, regardless of the step
label on the branching sequence table.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-91
l When There Exist Steps 00 and n in the Branched Sequence Table
Description examples of the branched sequence table with steps 00 and n are shown below.
Assume that “Output Only when Conditions Change” is specified for the output timing.

ST 005 ST 015

Rule number 01 02 03 04 05 Rule number 01 02 03 04 05

Tag name Tag name
Data Data
Data item Step label 1 2 3 4 Data item Step label 0 1 1 2
Comment Comment
DI0010.PV ON ................................ Y Y N DI0030.PV ON ................................ Y Y N
DI0015.PV ON ................................ Y N N DI0031.PV ON ................................ Y Y N
DI0016.PV ON ................................ Y Y Y Y DI0036.PV ON ................................ Y N N
DI0018.PV ON ................................ N N Y DI0038.PV ON ................................ Y N Y
DI0020.PV ON ................................ Y Y DI0125.PV ON Y Y Y Y
DI0021.PV ON ................................

DO0001.PV H Y Y N DO0050.PV H ................................ Y N

DO0011.PV H ................................ Y N DO0052.PV H ................................ Y
ST015.ACT ON ................................ Y Y DO0053.PV H ................................ Y N Y
DO0014.PV H ................................ Y Y DO0054.PV H ................................ N Y Y
DO0035.PV H ................................ Y Y DO0061.PV H ................................ N Y Y

THEN 2 1
ELSE

D0302A0E.ai

Figure Description Examples of Step-Type Sequence Table Execution

The following explains the details of the action rule processing in the description examples shown
above.
If the conditions in Rule 01 of Table ST005 are satisfied, the D000001.PV.H=Y operation will be
executed to branch to Table ST015. If the execution step label (PV) at Table ST015 is Step 2 at
the time, the condition testing for Rule 01 of Step 00 and Rule 04 of Step 2 will be performed. If
conditions are satisfied at Table ST015, operations for the rules whose conditions are satisfied,
will be executed. It will then return to Table ST005 to execute the DO0014.PV.H=Y operation.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-92

n Execution of the Corresponding Rule Number in the Sequence Table

One-shot execution of the sequence table is performed, with the same rule number as the
current rule at the branch source as an execution target. This is used to expand the condition
signal and action signal over 64 signals in the nonstep type sequence table.
The table below lists the symbolic convention and description of action signal to execute the
corresponding rule numbers.
Table Symbolic Convention of Action Signal and Action Description
Action signal description column Action
rule Action description
Output signal Action specification column
Y Execute the same table
Element symbol.SD C
N Disable
D0302A1E.ai

• When the branch source is a step type and the branch destination is a nonstep type:
Although execution of the corresponding rule number is meaningless, the corresponding
rules will be executed.
• When the branched table is a step type:
Because execution of the same rules will be meaningless, the system will halt without
executing any actions.

It is possible to branch further from the branched sequence table to other sequence table, and
perform condition testing and operation for the first branched sequence table. Nesting is available
up to seven levels, including the first sequence table.
Description examples of the status manipulation of corresponding rule numbers are shown
below. Assume that “Output Only when Conditions Change” is specified for the output timing.

ST 005 ST 015

Rule number 01 02 03 04 05 Rule number 01 02 03 04 05

Tag name Tag name
Data Data
Data item Step label Data item Step label
Comment Comment
DI0010.PV ON ................................ Y Y N DI0030.PV ON ................................ Y Y N
DI0015.PV ON ................................ Y N N DI0031.PV ON ................................ Y Y N
DI0016.PV ON ................................ Y Y Y Y DI0036.PV ON ................................ Y N N
DI0018.PV ON ................................ N N Y DI0038.PV ON ................................ Y N Y
DI0020.PV ON ................................ Y Y DI0125.PV ON Y Y N Y
DI0021.PV ON ................................

DO0001.PV H ................................ Y Y N DO0050.PV H ................................ Y N Y

DO0011.PV H ................................ Y N DO0052.PV H ................................ Y N
ST015.SD C ................................ Y Y DO0053.PV H ................................ Y N Y
DO0014.PV H ................................ Y Y DO0054.PV H ................................ N Y Y
DO0035.PV H ................................ Y Y DO0061.PV H ................................ N Y

D0302A2E.ai

Figure Description Examples of Corresponding Rule Number Execution

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-93
The following explains the details of the action rule processing in the description examples shown
above.
• If the conditions in Rule 01 of Table ST005 are satisfied, the DO001.PV.H=Y operation will
be executed, and the condition testing of Rule 01 will be conducted after branching to Table
ST015. If conditions are satisfied, DO0050.PV.H=Y, DO0052.PV.H=Y, and DO0054.PV.H=N
operations will be executed. It will then return to Table ST005 to execute the DO0014.
PV.H=Y operation.
• Neither rule 02 nor 03 of Table ST005 is associated with Table ST015.
• If the conditions in Rule 04 of Table ST005 are satisfied, the DO0001.PV.H=N and DO0011.
PV.H=N operations will be executed to branch to Table ST015. Condition testing will then be
performed for Rule 04. If conditions are satisfied, operations for the rules whose conditions
have been satisfied will be executed. DO0053.PV.H=Y, DO0054.PV.H=Y, and DO0061.
PV.H=Y operations will be executed. It will then return to Table ST005 to execute the
DO0014.PV.H=Y and DO0035.PV.H=Y operations.

n Executing a Particular Step in the Sequence Table

The following describes the action signal’s symbolic convention and the action description for
executing a particular step in the specified sequence table.
Table Symbolic Convention of Action Signal and Action Description

Action signal description column Action rule

column Action description
Output signal Action specification (Y/N)
Y Execute steps xx and 00
Element symbol.SA xx
N Disable
D0302A3E.ai

xx: Specify the step label using 2 or less alphanumeric characters.

It is possible to further branch from the branched sequence table to other sequence table, and
perform condition testing and operation for that branched sequence table. Up to seven levels of
nesting are possible including the first sequence table.
The action rule subject to execution varies by the type of sequence table (nonstep, step) at the
execution source and execution destination.
Table Execution Target Rules by Sequence Table Type
Branch source Branch destination Action rule subject to execution
Nonstep type All rules
Nonstep type
Step type Rules in specified step and step 00
Nonstep type All rules
Step type
Step type Rules in specified step and step 00
D0302A4E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-94
When the conditions described in the condition rule are satisfied, the sequence table number
listed in the action signal symbol column will be one-shot executed to branch to the destination
sequence table. After executing condition testing and actions for rules in Step 00 and steps
specified by the branched sequence table, it returns to the action rule processing in the branching
sequence table.
If the specified step does not exist in the branched sequence table, an error will occur and
the step will not be executed. However, in spite of the error, if Step 00 exists in the branched
sequence table, only that step will be executed.
If “execution of a particular step” is performed for the nonstep-type sequence table, all rules will
be subject to execution.
A description example of executing a particular step is shown below.
Assume that “Output Only when Conditions Change” is specified for the output timing.

ST 005 ST 015

Rule number 01 02 03 04 05 Rule number 01 02 03 04 05

Tag name Tag name
Data Data
Data item Step label A1 A2 A3 A4 Data item Step label A1 A2 A2 A3
Comment Comment
DI0010.PV ON ................................ Y Y N DI0030.PV ON ................................ Y Y N
DI0015.PV ON ................................ Y N N DI0031.PV ON ................................ Y Y N
DI0016.PV ON ................................ Y Y Y Y DI0036.PV ON ................................ Y N N
DI0018.PV ON ................................ N N Y DI0038.PV ON ................................ Y N Y
DI0020.PV ON ................................ Y Y DI0125.PV ON Y Y Y Y
DI0021.PV ON ................................

DO0001.PV H Y Y N DO0050.PV H ................................ Y N Y

DO0011.PV H ................................ Y N DO0052.PV H ................................ Y N
ST015.SA. A2 ................................ Y Y DO0053.PV H ................................ Y N Y
DO0014.PV H ................................ Y Y DO0054.PV H ................................ N Y Y
DO0035.PV H ................................ Y Y DO0061.PV H ................................ N Y Y

THEN
Description is
ELSE
not required.
D0302A5E.ai

Figure Description Example of Executing Action Rule Processing

The following describes the action rule processing for the above example.
• If the conditions in Rule 01 of Table ST005 are newly satisfied, the DO001.PV.H=Y
operation will be performed to branch to Table ST015. Following the condition testing
conducted for rules 02 and 03 of Step A2 in the branched sequence table, if the conditions
are newly satisfied, relevant operations will be performed. It will then return to Table ST005
to execute the DO0014.PV.H=Y operation.
• Neither Rule 02 nor 03 in Table ST005 is associated with Table ST015.
• If the conditions in Rule 04 of Table ST005 are satisfied, the DO0001.PV.H=N and DO0011.
PV.H=N operations will be performed to branch to Table ST015. Following the condition
testing for rules 02 and 03 of Step A2 in the branched sequence table, if the conditions are
newly satisfied, relevant operations will be performed. It will then return to table ST005 to
execute the DO0014.PV.H=Y and DO0035.PV.H=Y operations.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-95

n Setting Execution Step Label in the Sequence Table

Execution step label (PV) of the sequence table is set. Unlike “executing a particular step,” this
operation merely sets a step label for the execution step label (PV) of a specified sequence table.
This setup operation alone will not execute the step. It is not until the execution step label (PV) is
activated after the setup that the step is executed.
The table below lists the symbolic convention and action description of the action signal for
setting the execution step label.
Table Symbolic Convention and Action Description of the Action Signal

Action signal description column Action rule

column Action description
Output signal Action specification (Y/N)
Y Set the step name xx
Element symbol.PV xx
N Disable
D0302A6E.ai

xx: Specify the step label using 2 or less alphanumeric characters.

A description example of specifying the execution step label of a specified sequence table is
shown below.
Assume that “Output Only when Conditions Change” is specified for the output timing.

ST 005

Rule number 01 02 03 04 05 06 07
Tag name
Data item Data Step label
Comment
DI0013.PV ON Auto/manual N Y
Condition

ST010.PV A1 Y
ST011.PV A1 Y
ST012.PV A1 Y Operation

ST013.PV A1 Y
D0302A7E.ai

Figure Description Example of Setting Execution Step Label

The following describes the action rule processing for the above description example.
• When DI0013 becomes “OFF,” “A1” will be set on the execution step label in sequence
tables ST010, ST011 and ST012.
• When DI0013 becomes “ON,” “A1” will be set on the execution step label in the ST013
sequence table.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-96

n Block Mode Change in Sequence Table

By describing the block mode change of the other sequence table in the sequence table action
signal, halt (change to MAN mode)/restart (change to AUT mode) of the other specified sequence
table is manipulated.
The sequence table changed to the manual (MAN) mode will retain the status at the time of block
mode change. When “changed output” is specified for the output timing, the states of halt and
restart are compared upon restarting the processing to execute the status manipulation for the
changed condition rules.
The table below lists the symbolic convention of the action signal and action description for
changing the block mode.
Table Symbolic Convention of Action Signal and Action Description

Action signal description column Action rule

column Action description
Output signal Action specification (Y/N)
Y Table mode change command
Element symbol.MODE AUT, MAN, O/S
N Disable
D0302A8E.ai

n Pause and Restart a Sequence Table

Some sequence tables are running in a fixed scan cycle while some others are staring, pausing
or restarting in accordance with process procedures. To pause a running sequence table, and to
restart a paused sequence table is possible. The scripts may be described in a sequence table
for a sequence table’s Pause and Restart are shown as follows.
Table Syntax for Output Signal Scripts and Action Description

Action signal description column Action rule

column Action description
Output signal Action specification (Y/N)
Y Starts or restarts sequence table
Element symbol.XS ON
N Pause Sequence table
D0302B2E.ai

When Y is scripted in an action rule, if the condition of that rule establishes, the sequence table
scripted in the Element symbol column will be started or restarted. When the restarted sequence
table is running in the [Output Only When Condition Changes (C)] timing, the restarted will
compare the current conditions with the conditions before it was paused, only the rules that
the conditions have been changed will perform the output actions. If the sequence table is a
[Periodic Execution Type], the sequence table will continue to run until it receives another pause
command.
When N is scripted in an action rule, if the condition of that rule establishes, the sequence table
scripted in the Element symbol column will be paused.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-97

D3.2.15 Action Signal Description: Status Manipulation for a

Logic Chart from a Sequence Table
In the status manipulation for a logic chart, a logic chart block mode can be changed. In
addition, the specified logic chart can be one-shot executed.

n One-Shot Execution of a Logic Chart from a Sequence Table

▼ Action Signal Description - Logic Chart
The syntax in action signal description for one-shot executing a logic chart and the output actions
corresponding to Y/N in the action rule columns of the sequence table are shown as follows.
Table Syntax in Action Signal Description and Output Actions Corresponding to Y/N in Action Rule
Columns

Action signal description

Action rule Action description
Output signal Action specification
Y Execute a logic chart
Element symbol.ACT ON
N Disable
D0302A9E.ai

• The output of an executed logic chart can execute another logic chart. The output signal
can be nested up to seven times, including the branching sequence table.
• If one-shot execution of a logic chart fails for one of the following reasons, a system alarm
will be triggered.
• The output of an executed logic chart to execute another logic chart is nested over seven
times, including the branching sequence table.
• The function block connected to the input terminal is in O/S mode.
• The function block connected to the input terminal is udder online maintenance.

n Changing the Block Mode of a Logic Chart from a Sequence Table

The block mode of the specified logic chart may be changed. Changing the block mode allows
the logic chart to be paused (with the MAN mode specified) or resumed (with the AUT mode
specified).
The syntax in action signal description for changing a block mode and the output actions
corresponding to Y/N in the action rule columns of the sequence table are shown as follows.
Table Syntax in Action Signal Description and Output Actions Corresponding to Y/N in Action Rule
Columns

Action signal description

Action rule Action description
Output signal Action specification
Y Change a block mode
Element symbol.MODE AUT, MAN, O/S
N Disable
D0302B0E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.2 Sequence Table Block (ST16, ST16E)> D3-98

D3.2.16 Data Items of the Sequence Table Block (ST16)

The data items of the ST16 block is shown below.

n Data Item
Table Data Items of the Sequence Table Block (ST16)
Entry Permitted
Symbol Data Name Range Default
or Not
PV Executing step name x 100 steps Start step name
MODE Mode x ---- O/S (MAN)
ALRM Alarm status ---- NR
AFLS Alarm flashing status ---- 0
AF Alarm detection ---- 0
AOFS Alarm in hibition ---- 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ---- 0
D0302B1E.ai

x: Entry is permitted unconditionally.

Blank: Entry is not permitted.

SEE
ALSO For a list of valid block mode of the ST16, see the following:
D3.1.2, “Block Mode of Sequence Control Blocks”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D3.3 Logic Chart Block (LC64)> D3-99

D3.3 Logic Chart Block (LC64)

Logic Chart Block (LC64) may combine or arrange the signals of other function blocks,
process I/O and software I/O into an application for interlock sequence control.

n Logic Chart Block (LC64)

▼ Logic Chart
Logic Chart Block is the function block that describes the relations of the input signals, the output
signals and the logic calculation operators in the interlock diagram form, so that it can perform its
main function, the interlock sequence control using the same expressions as those used on the
logic chart blue prints.
An architecture of LC64 Logic Chart Block is shown as follows.

Q01 J01

Q02 J02

Q03 Input Output J03

processing processing

Logic operation

Q56 J56

D030301E.ai

Figure Function Block Diagram of Logic Chart Block (LC64)

The connection methods and destinations for I/O terminals of Logic Chart Block (LC64) are
shown below.
Table Connection Methods and Destinations for I/O Terminals of Logic Chart Block (LC64)
Connection type Connection destination
I/O Status Terminal
terminal Data Data Condition Process Software Function
manipula- connecti-
reference setting testing I/O I/O block
tion on
Q01 to Q56 x x x x
J01 to J56 x x x x
D030302E.ai

x: Connection available
Blank: Connection not available

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-100
The input and output connections can be set by entering the connection information and data
description on the client area of the logic chart editing window.

Mooving into
WO %SW0200.PV.L cooling phase
Stop→Cool %SW0500.PV.ON
%SW0140.ON Cooling printout
Level 1 %SW0100.PV.ON TM100
TCV full
Level 2 %SW0150.PV.ON %SW0160.PV.L
close command
Cool→Stop %SW0120.PV.ON
Shutoff valve 1
Auto %SW0101.PV.ON TV100.CSV.2
open output
TM100 Shutoff valve 2
TV101.CSV.2
open output

Open shutoff valve 1 TV100.PV.2 Open shutoff valve %SW0201.PV.L Cool command
Open shutoff valve 2 TV101.PV.2
Comment
No.1 temperature
RL001.X01.LT Cooling and
<- 70 °C DO0100.PV.L voice message
No.2 temperature
RL002.X02.LT
<- 70 °C

Comment Condition signal Logic element Action signal Comment

D030303E.ai

Figure Outline of the Logic Chart

A logic chart with 32 inputs, 32 outputs and 64 logic elements (LC64) is provided.

l Logic Chart with 32 Inputs, 32 Outputs and 64 Logic Elements (LC64)

LC64 block is a sequence control function block with 32 input and 32 output signal channels and
it can handle 64 logic operators. Since the input and output signal channels are fixed, the small
logic chart with only 8 input and 8 output signal channels can not be created.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-101

D3.3.1 Configuration of a Logic Chart

A logic chart consists of condition signals, action signals and logic operators.

n General Outlook of a Logic Chart

A general outlook of a logic chart is shown as follows.
Process timing Scan period Order of execution
A B C D E F G H I J K L M N O P Q R S T U V W
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20 Comment Condition Logic chart area Action Comment
21 signals signals
22
23
24
25
26
27
28
29
30
31
32

Client area
D030304E.ai

Figure Configuration of the Entire Logic Chart

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-102

n Outline of Logic Chart Elements

The logic chart elements are shown as follows.

l Processing Timing
The processing timing of a logic chart consists of start timing and output timing.
Start timing refers to the timing at which control algorithm of the logic chart is executed upon
receipt of input signal. Output timing indicates the conditions under which action signals are
output at the time a periodic start type or one-shot start type logic chart is executed.
The output timing of logic charts is fixed to “output each time.” If the logical value acquired by
logic operation is true, output signals are output whenever started.
“Start timing” can be set on each logic chart block.
• Start timing:
Select from “Periodic Execution Type (T),” “One-shot Processing Type (O),” “Startup at
Initial Cold Start/Restart (I)” or “Restricted Initial Execution Type (B).”
• Output timing:
“Output Each Time Conditions are Satisfied”

l Scan Period
Periodic start logic charts are activated in each scan period as defined here. Among the periodic
started logic charts, the logic charts activated in the basic period have the items “Control Period”
and “Control Phase” to be defined in addition to scan period.
“Scan period,” “control period,” and “control phase” can be defined for each logic chart.
• Scan period:
Select from “Basic Scan”, “Medium-speed Scan” (*1) or “High-speed Scan.”
• Control period:
1 to 16 seconds.
• Control phase:
0 to 15 seconds.
*1: “Medium-speed Scan” is only supported by KFCS2, KFCS, FFCS, LFCS2 and LFCS.

SEE
ALSO • For details on processing timing, see the following:
C7.3, “Process Timing for Sequence Control Block”
• For details on scan period, see the following:
C7.1.1, “ Scan Period”
• For details on control period and control phase, see the following:
C7.3.6, “Control Period and Control Phase for Logic Chart Block (LC64)”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-103
l Order of Logic Calculation
For the execution order of logic calculation, the matrix expansion or manual expansion can be
selected.

l Condition Signals
The input information such as tag names and data items or other specific condition scripts should
be entered for condition signals.

l Comment
For the input signals or output signals, their service comments can be described using up to 24
alphanumeric characters or 12 double-byte characters. A comment corresponding to a condition
or action signal can be automatically entered.

SEE
ALSO For the details of comment entry, see the following:
“n Input Element Symbol” in F6.5, “Element Symbol Type and Element Resource Count”

l Logic Chart Area

The logic calculation process can be expressed in logic chart diagram form.

l Action Signals
The output information such as tag names and data items or other specific manipulation scripts
should be entered for action signals.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-104

D3.3.2 Creating a Logic Chart Block

To create a logic chart block, the settings related to the sequence control information
should be entered in each setting area of the logic chart edit window.

n Configuration of Logic Chart Edit Window

The figure below shows the configuration of the logic chart edit window.
Processing timing setting area Execution order of logic calculation setting area

Client area

D030305E.ai

Figure Configuration of Logic Chart Edit Window

To create a logic chart, the information for sequence connection (condition signals, action signals,
logic operators, parameters of the applied logic operators) needs to be entered in each setting
area of the logic chart edit window.
The setting areas are listed below.
• Processing timing setting area
• Execution order of logic calculation setting area
• Client area

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-105

n Processing Timing Setting Area

In processing timing area, the existing settings for the processing timing and scan period are
displayed. Data can be specified and changed at the Processing Timing and Scan Period on the
Processing Timing setup area. The processing timing, scan/control periods and control phase
can also be specified at the Set Start Timing dialog box.
An example of processing timing setting dialog box is shown as below.
Processing timing

Processing timing

Execution timing Periodic execution

Output timing Output only at condition change

Scan period

Scan period Basic scan

Control period
Control phase

OK Cancel

D030306E.ai

Figure Processing Timing Setting Dialog Box

SEE
ALSO For details of processing timing, see the following:
C7.3, “Process Timing for Sequence Control Block”

n Execution Order of Logic Calculation Setting Area

For the execution order, either matrix expansion or manual expansion can be selected in this
setting area.

TIP
Clicking [Execution Order] on [View] menu may display execution order of the logic elements on the client area of
the logic chart edit window.
Moreover, this setting is also applied to the logic chart view and to the self-documentation printing.

n Client Area
The client area is used to put the logic operators symbols on the matrix for describing the logic
calculation processing in logic chart format.

SEE
ALSO For details on logic calculation processing, see the following:
D3.3.5, “Logic Calculation Processing of Logic Chart”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-106

D3.3.3 Logic Chart Processing Flow

In the logic chart, the logic calculation is performed based on the result of input
processing. Output processing is then performed for the output action to the operation
target.

n Logic Chart Processing Flow

The figure below shows the logic chart processing flow.

Logic calculation processing

Input processing Output processing

(condition test) (status manipulation)

D030307E.ai

Figure Logic Chart Processing Flow

l Input Processing
The true or false status of a condition signal is determined by the condition test performed on the
input signal.

l Logic Calculation Processing

The logic calculation is based on the result of condition test of the input signal (true = 1, false = 0).
The logic calculation algorithm is expressed by combinations of logic operators.

l Output Processing
Status manipulation output is determined based on the result of logic calculation processing.
The status manipulation will be output as the output signals to the operation target. The status
manipulation can send commands such as starting, data setting, and status change to the
contact output terminals or to other function blocks.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-107

D3.3.4 Input Processing of Logic Chart

The input processing gives a true or false status signal based on the result of condition
test performed on each of the multiple input signals.

n Input Processing of Logic Chart

Logic chart function block samples input signals via its input terminals from the connected
destinations. Then the condition test is performed based on these signals.
The result of the condition test is referred to as condition signal status. The condition signal status
True or False will be passed to the logic calculation function in the block.
If the function block connected to the input terminal is a one-shot started block, the result of the
calculation performed in the one-shot started function block can also be used as the signal for
condition test.
When referencing the signal from the one-shot started function block fails, and the failure is
caused by one of the following reasons, a system alarm will be triggered.
• In the condition column of the referenced sequence table, the reference target is another
sequence table, the sub-reference is nested more than 7 times.
• The function block connected to the input terminal is in O/S mode.
• The function block connected to the input terminal is under online maintenance.

If an input terminal is not connected or a condition element is not defined, the condition test result
will give a True status unconditionally.
When the condition test can not access the current signal status, or can not trigger the one-shot
started block to start, it will use the previously used signal status for the condition test. This result
will be further used in the logic calculation processing.
A block or an element database connected is abnormal, the connected function block, process
I/O or global switch (*1) is under online maintenance are the main obstacles for accessing the
input signal.
*1: The global switch can be used in FCSs except standard PFCS.

IMPORTANT
Online maintenance is one of the main obstacles for accessing the input signal and starting the
one-shot started block. The duration of an online maintenance varies with the size and type of the
modified contents for the online maintenance. When the modified contents are in large size, the
online maintenance may last for tens of seconds.
When the condition test can not access the current signal status, or can not trigger the one-shot
started block to start, the condition test uses the previously used signal status. Since this status is
kept in the logic chart, cautions should be taken in the following case.
• When the logic chart block itself is one-shot execution type or the connected function block
is one-shot start type, and the access failure is caused by O/S mode, the previous signal
status might be a signal kept for a long time. If the one-shot has not been started for at least
one time, the status signal kept might be a 0 (False).
With consideration of the online maintenance in above mentioned case, when designing a
sequence control, especially the sequence control loop related to the hazardous process
controls, it is required to add an error process subroutine, or to set the related blocks into MAN
mode on the builder for online downloading.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-108

D3.3.5 Logic Calculation Processing of Logic Chart

The logic calculation processing performs the logic calculation described in logic chart.
The logic calculation is based on the input signal status and the calculated result is
output as an action signal.

n Logic Calculation Processing

The logic calculation based on the signal status (True = 1, False = 0) is performed at each scan
cycle when the block is periodic type or at each time the block starts when the block is one-shot
started type. The result of the calculation will be output to other logic elements in the logic chart
or sent out as an action signal. In most of cases, a logic element gives an action signal only when
the calculation result is True.

n Logic Operation Elements

The logic chart is described with combinations of logic elements in the logic chart block. The
detailed specifications of the logic operation elements will be explained in the following sections.
The logic operation element shares the same specification with corresponding logic operation
block.

TIP
• When an input is directly wired to an output, it is still counted as one logic operation element.
• SRS, WOUT or CMP is counted as 2 logic operation elements.

l AND: Logic Product

It gives one output based on multiple inputs. When all the inputs are True, the output becomes
True. The maximum number of inputs is 21.

, , ,
D030308E.ai

Figure AND symbols

l OR: Logic Sum

It gives one output based on multiple inputs. When any of inputs is True, the output becomes
True. The maximum number of inputs is 21.

, , ,
D030309E.ai

Figure OR symbols

l NOT: Negation
It gives the inverse of the input as an output.

D030310E.ai

Figure NOT symbol

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-109
l SRS1-R (1 output), SRS2-R (2 outputs): Flip-Flop (Reset-Dominant)
It gives one output or two outputs shown in the following truth table based on the set and reset
input signals.
One flip-flop operation is counted as two logic operation elements.

S S OUT1 S S OUT1

R R R R OUT2

Without reset output With reset output

D030311E.ai

Figure SRS1-R and SRS2-R symbols

Table Reset-Dominant Truth Table

S 0 1 0 1
Input
R 0 0 1 1
OUT1 Latched 1 0 0
Output
OUT2 Latched 0 1 1
D030312E.ai

Latched: The previous state is maintained.

l SRS1-S (1 output), SRS2-S (2 outputs): Flip-Flop (Set-Dominant)

It gives one output or two outputs shown in the following truth table based on the set and reset
input signals.
One flip-flop operation is counted as two logic operation elements.

S S OUT1 S S OUT1

R R R R OUT2

Without reset output With reset output

D030313E.ai

Figure SRS1-S and SRS2-S symbols

Table Set-Dominant Truth Table

S 0 1 0 1
Input
R 0 0 1 1
OUT1 Latched 1 0 1
Output
OUT2 Latched 0 1 0
D030314E.ai

Latched: The previous state is maintained.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-110
l WOUT: Wipeout
It gives an output which is an inverse of reset signal when reset signal is true, otherwise, it gives
the set signal as output, shown in the following truth table based on the set and reset input
signals.
One wipeout operation is counted as two logic operation elements.
Its symbol is shown below.
(W. O)
Table WOUT Truth Table
S 0 1 0 1
Input
R 0 0 1 1
Output OUT 0 1 0 0
D030315E.ai

l OND: On-Delay Timer

When the input status changes from 0 to 1, the internal timer starts. When the set time t elapsed,
its output changes from 0 to 1. When the input status changes to 0, the output will be reset to 0
immediately.

D030316E.ai

Figure On-Delay Timer symbol

IN

OUT

D030317E.ai

Figure Behavior of On-Delay Timer

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-111
l OFFD: Off-Delay Timer
When the input status changes from 1 to 0, the internal timer starts. When the set time t elapsed,
its output changes from 1 to 0. When the input status changes to 1, the output will be reset to 1
immediately.

D030318E.ai

Figure Off-Delay Timer symbol

IN

OUT

D030319E.ai

Figure Behavior of Off-Delay Timer

l TON: One-Shot (Rise Trigger)

When the input status changes from 0 to 1, it gives an output 1 for a one scan cycle. The output is
always 0 except for that 1 scan cycle.

D030320E.ai

Figure One-Shot (Rise Trigger) symbol

1
IN
0

1
OUT
0

One scan cycle

D030321E.ai

Figure Behavior of One-Shot (Rise Trigger)

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-112
l TOFF: One-Shot (Fall Trigger)
When the input status changes from 1 to 0, it gives an output 1 for a one scan cycle. The output is
always 0 except for that 1 scan cycle.

D030322E.ai

Figure One-Shot (Fall Trigger) symbol

1
IN
0

1
OUT
0

One scan cycle

D030323E.ai

Figure Behavior of One-Shot (Fall Trigger)

l CMP-GE: Comparator
It compares the logic values of input 1 and input 2. It gives an output 1 when input 1 is greater
than or equal to input 2, otherwise it gives an output 0.
One Comparator operation is counted as two logic operation elements.

D030324E.ai

Figure CMP-GE symbol

Table CMP-GE Truth Table

IN1 0 0 1 1
Input
IN2 0 1 0 1
Output OUT 1 0 1 1
D030325E.ai

l CMP-GT: Comparator
It compares the logic values of input 1 and input 2. It gives an output 1 when input 1 is greater
than input 2, otherwise it gives an output 0.
One Comparator operation is counted as two logic operation elements.

D030326E.ai

Figure CMP-GT symbol

Table CMP-GT Truth Table

IN1 0 0 1 1
Input
IN2 0 1 0 1
Output OUT 0 0 1 0
D030327E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-113
l CMP-EQ: Comparator
It compares the logic values of input 1 and input 2. It gives an output 1 when input 1 is equal to
input 2, otherwise it gives an output 0.
One Comparator operation is counted as two logic operation elements.

D030328E.ai

Figure CMP-GT symbol

Table CMP-EQ Truth Table

IN1 0 0 1 1
Input
IN2 0 1 0 1
Output OUT 1 0 0 1
D030329E.ai

n Execution Order of Logic Calculation

The Execution Order indicates in which order logic elements in logic charts are executed, which
includes Matrix Expansion and Manual Expansion.
• Matrix expansion
Logic operators in logic charts are executed from the left column to the right, and from the
upper element to the lower in the same column.
• Manual expansion
The execution order automatically assigned to the logic operation elements according to
their position can be manually changed.
The execution order of logic operation elements can be specified on the logic chart edit window.
The default setting for the execution order is matrix expansion.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-114

D3.3.6 Output Processing of Logic Chart

The output processing of the logic chart gives an action signal to the operation target. The
action signal is the result availed from the logic calculation processing.

n Output Processing of Logic Chart

The output processing of the logic chart performs status manipulation to the specified output
terminal in accordance with the action signal. The action signal is availed from the True or False
result of the logic calculation in the logic chart function block.

When the action signal is specified to a function block to be one-shot started, the block will be
one-shot started when the action signal is output to it.
When output to the one-shot function block fails, and the failure is caused by one of the following
reasons, a system alarm will be triggered.
• In the action column of the destination sequence table, the output signal is output to another
logic chart. Moreover, the output is redirected to another logic chart. The output is nested
more than 7 times.
• The function block connected to the output terminal is in O/S mode.
• The function block connected to the output terminal is udder online maintenance.

When the output action is to set a datum or to change status, if the connected destination, a
block or an element, is under online maintenance, the output will be skipped then the processing
continues.
When the output action is to change the block mode of the connected destination block, if the
output processing has an error, the status change of the connected destination block will not be
performed.
For the logic chart that has multiple output terminals, each terminal outputs the action signal in
accordance with logic calculation True or False result related to the terminal.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-115

D3.3.7 Condition Signal Description: Referencing Other

Function Blocks and I/O Data
Various types of data, block mode and status can be referenced for condition
test performed in logic chart. I/O data including the process I/O, software I/O, and
communication I/O can also be referenced.

n Function Blocks and I/O Data that can be Referenced from Logic Chart
Function blocks that can be referenced from logic chart are shown below.
• Switch instrument blocks
• Timer Block (TM)
• Software Counter Block (CTS)
• Pulse Train Input Counter Block (CTP)
• Code Input Block (CI)
• Code Output Block (CO)
• Relational Expression Block (RL)
• Resource Scheduler Block (RS)
• Valve Monitoring Block (VLVM)
• Regulatory Control Blocks
• Calculation Blocks
• Faceplate Blocks
• SFC Blocks
• Unit Instrument Blocks
• Sequence Table Blocks
• Logic Chart Blocks

The following I/O data can also be referenced from logic chart.
• Processing I/O (contact I/O)
• Software I/O (internal switch, annunciator message)
• Communication I/O

The following points should be taken into consideration when referencing a logic chart block
mode.
• When O/S is specified as the condition specification for block mode reference, the test result
will be False when the block is in the compound block mode, i.e., O/S and another basic
block mode exist simultaneously.
• When MAN or AUT is specified as the condition specification for block mode reference, the
test result is True even in the compound block mode as long as the specified basic block
mode exists.
• The status of pulse width output cannot be referenced.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-116

n Referencing Switch Instrument Block and Enhanced Switch

Instrument Block
The syntax for applying the various types of data and data status of a switch instrument block
and enhanced switch instrument block as condition test reference signal in a logic chart and the
True/False representation in the logic chart are shown as follows.
Table Syntax for Condition Signal Description and True/False Representation (1/2)
Condition signal description column
True/false Satisfiable condition
Input signal Condition specification
True Answerback value matches specification
Element symbol.PV. 0, 1, 2
False Answerback value does not match specification
True Data status matches specification
Element symbol.PV= Data status
False Data status does not match specification
True Output value matches specification
Element symbol.MV. 0, 1, 2
False Output value does not match specification
True Data status matches specification
Element symbol.MV= Data status
False Data status does not match specification
True Tracking switch in specified state
Element symbol.TSW. 0,1
False Tracking switch not in specified state
True Tracking switch in specified state
Element symbol.TSW= Data status
False Tracking switch not in specified state
True Backup switch in specified state
Element symbol.BSW. 0, 1
False Backup switch not in specified state

AUT, MAN, CAS, True Block mode matches specification

Element symbol.MODE.
ROUT, TRK, O/S False Block mode does not match specification
True Block is in ROUT (MAN) mode
BUM
False Block is not in ROUT (MAN) mode
True Block is in ROUT (AUT) mode
Element symbol.XMODE. BUA
False Block is not in ROUT (AUT) mode
True Block is in ROUT (CAS) mode
BUC
False Block is not in ROUT (CAS) mode
True Block status matches specification
Element symbol.BSTS. NR, SIM, ANCK
False Block status does not match specification
D030330E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-117
Table Syntax for Condition Signal Description and True/False Representation (2/2)
Condition signal description column True/ Satisfiable condition
Input signal Condition specification false

NR, IOP, OOP, ANS+ True Specified alarm occurring

Element symbol.ALRM.
ANS-, PERR, CNF False No occurrence of specified alarm
True Alarm is in IOP or IOP- status.
Element symbol.XALRM. IOP
False Alarm is in neither IOP nor IOP- status.
PERR, AFL (*1), NR, True Specified alarm in flashing state
Element symbol.AFLS. IOP, OOP, ANS+, ANS-,
CNF False Specified alarm in non-flashing state

NR, IOP, OOP, ANS+ True Canceling the specified alarm detection
Element symbol.AF.
ANS-, PERR, CNF False Detecting the specified alarm
True IOP or IOP- detection is disabled
Element symbol.XAF. IOP
False IOP and IOP- detection is enabled
NR, IOP, OOP, ANS+ True Suppressing the specified alarm
Element symbol.AOFS. CNF, ANS-, PERR,
AOF (*2) False Canceling the specified alarm in suppression
True Sequence setpoint value matches specification
Element symbol.CSV. 0, 1, 2
False Sequence setpoint value does not match specification
True Data status matches specification
Element symbol.CSV= Data status
False Data status does not match specification
True Remote manipulated output value matches specification
Element symbol.RMV. 0, 1, 2
False Remote manipulated output value does not match specification
True Data status matches specification
Element symbol.RMV= Data status
False Data status does not match specification
True Bypass switch in specified state
Element symbol.BPSW. 0, 1
False Bypass switch not in specified state
True Data status matches specification
Element symbol.BPSW= Data status
False Data status does not match specification
D030331E.ai

*1: The condition specification of the AFL is the reference in all flashing state.
*2: The condition specification of the AOF is the reference in all suppressing alarm state.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-118

n Referencing Timer Block (TM)

The syntax for applying the various types of data and data status of a timer (TM) block as
condition test reference signal in a logic chart and the True/False representation in the logic chart
are shown as follows.
Table Syntax for Condition Signal Description and True/False Representation
Condition signal description column
True/false Satisfiable condition
Input signal Condition specification
True Block mode matches specification
Element symbol.MODE. AUT, O/S
False Block mode does not match specification
STOP, RUN, PAUS, True Block status in specified state
Element symbol.BSTS. NR, PALM, CTUP False Block status not in specified state
True Alarm status in specified state
Element symbol.ALRM. NR
False Alarm status not in specified state
True Specified alarm in flashing state
Element symbol.AFLS. AFL (*1), NR
False Specified alarm in non-flashing state
True Canceling the specified alarm detection
Element symbol.AF. NR
False Detecting the specified alarm
True Suppressing the specified alarm
Element symbol.AOFS. NR, AOF (*2)
False Canceling the specified alarm in suppression
D030332E.ai

*1: The condition specification of the AFL is the reference in all flashing state.
*2: The condition specification of the AOF is the reference in all suppressing alarm state.

n Referencing Software Counter Block (CTS)

The syntax for applying the various types of data and data status of a software counter (CTS)
block as condition test reference signal in a logic chart and the True/False representation in the
logic chart are shown as follows.
Table Syntax for Condition Signal Description and True/False Representation
Condition signal description column
True/false Satisfiable condition
Input signal Condition specification
True Block mode matches specification
Element symbol.MODE. AUT, O/S
False Block mode does not match specification

STOP, RUN, NR, True Block status in specified state

Element symbol.BSTS.
PALM, CTUP False Block status not in specified state
D030333E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-119

n Referencing Pulse Train Input Counter Block (CTP)

The syntax for applying the various types of data and data status of a pulse train input counter
(CTP) block as condition test reference signal in a logic chart and the True/False representation
in the logic chart are shown as follows.
Table Syntax for Condition Signal Description and True/False Representation
Condition signal description column
Condition True/false Satisfiable condition
Input signal
specification
True Block mode matches specification
Element symbol.MODE. AUT, O/S
False Block mode does not match specification

STOP, RUN, PAUS, True Block status in specified state

Element symbol.BSTS.
NR, PALM, CTUP False Block status not in specified state
True Alarm status in specified state
Element symbol.ALRM. CNF, NR, IOP
False Alarm status not in specified state
True Alarm is in IOP or IOP- status.
Element symbol.XALRM. IOP
False Alarm is in neither IOP nor IOP- status.

AFL (*1), CNF, NR, True Specified alarm in flashing state

Element symbol.AFLS.
IOP False Specified alarm in non-flashing state
True Canceling the specified alarm detection
Element symbol.AF. CNF, NR, IOP
False Detecting the specified alarm
True IOP or IOP- detection is disabled.
Element symbol.XAF. IOP
False IOP and IOP- detection is enabled.

CNF, NR, IOP, True Suppressing the specified alarm

Element symbol.AOFS.
AOF (*2) False Canceling the specified alarm in suppression
True Data status matches specification
Element symbol.PV= Data status
False Data status does not match specification
D030334E.ai

*1: The condition specification of the AFL is the reference in all flashing state.
*2: The condition specification of the AOF is the reference in all suppressing alarm state.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-120

n Referencing Code Input Block (CI)

The syntax for applying the various types of data and data status of a code input (CI) block as
condition test reference signal in a logic chart and the True/False representation in the logic chart
are shown as follows.
Table Syntax for Condition Signal Description and True/False Representation
Condition signal description column
True/false Satisfiable condition
Input signal Condition specification
True Block mode matches specification
Element symbol.MODE. AUT, O/S
False Block mode does not match specification
True Block status matches specification
Element symbol.BSTS. NR, LO, HI, ERR
False Block status does not match specification
True Data status matches specification
Element symbol.PV= Data status
False Data status does not match specification
D030335E.ai

n Referencing Code Output Block (CO)

The syntax for applying the various types of data and data status of a code output (CO) block as
condition test reference signal in a logic chart and the True/False representation in the logic chart
are shown as follows.
Table Syntax for Condition Signal Description and True/False Representation
Condition signal description column
True/false Satisfiable condition
Input signal Condition specification
True Block mode matches specification
Element symbol.MODE. AUT, O/S
False Block mode does not match specification
True Block status matches specification
Element symbol.BSTS. NR, LO, HL
False Block status does not match specification
True Data status matches specification
Element symbol.PV= Data status
False Data status does not match specification
D030336E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-121

n Referencing Relational Expression Block (RL)

The syntax for applying the various types of data and data status of a relational expression (RL)
block as condition test reference signal in a logic chart and the True/False representation in the
logic chart are shown as follows.
Table Syntax for Condition Signal Description and True/False Representation
Condition signal description column
Condition True/false Satisfiable condition
Input signal
specification

EQ, GT, GE, True Relationship of two data in specified state

Element symbol.X01 to 16.
LT, LE, AND False Relationship of two data not in specified state
D030337E.ai

The Meanings of the condition specifications are as follows:

Table Meanings of the Condition Specifications
Symbol Name Meanings
EQ Equal to Data 1 = data 2
GT Greater than Data 1 > data 2
GE Great than or equal to Data 1 ≥ data 2
LT Less than Data 1 < data 2
LE Less than or equal to Data 1 ≤ data 2
AND Logical product The logic product of each pair of bits in data 1 and data 2
D030338E.ai

n Referencing Resource Scheduler Block (RS)

The syntax for applying the various types of data and data status of a resource scheduler (RS)
block as condition test reference signal in a logic chart and the True/False representation in the
logic chart are shown as follows.
Table Syntax for Condition Signal Description and True/False Representation
Condition signal description column
Condition True/false Satisfiable condition
Input signal
specification

True Block mode matches specification

Element symbol.MODE. AUT, O/S
False Block mode does not match specification
Usage request state matches specification
True
Element symbol.RQ01 to 32. 0, 1 (0: No request 1: Requesting)
False Usage state does not match specification
Permission state matches specification
True
(0: No permission 1: Permitted)
Element symbol.PM01 to 32. 0, 1
Permission state does not match
False
specification
Maximum allowable number matches
True
specification
Element symbol.PMH. 0 to 32
Maximum allowable number does not match
False
specification
D030339E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-122

n Referencing Valve Monitoring Block (VLVM)

The syntax for applying the various types of data and data status of a Valve Monitoring (VLVM)
Block as condition test reference signal in a logic chart and the True/False representation in the
logic chart are shown as follows.
Table Syntax for Condition Signal Description and True/False Representation
Condition signal description column
Condition True/false Satisfiable condition
Input signal
specification

AUT, True Block mode matches specification

Element symbol.MODE.
O/S False Block mode does not match specification
True Specified alarm occurring
Element symbol.ALRM. NR
False No occurrence of specified alarm
NR, True Specified alarm in flashing state
Element symbol.AFLS.
AFL (*1) False Specified alarm in non-flashing state
True Canceling the specified alarm detection
Element symbol.AF. NR
False Detecting the specified alarm
NR, True Suppressing the specified alarm
Element symbol.AOFS.
AOF (*2) False Canceling the specified alarm in suppression
Valve abnormal matches specification
True
Element symbol.PV01 to 16. 0, 1 (0: Normal 1: Error)
False Valve abnormal does not match specification
Representative valve abnormal matches
specification
True
(0: All valves normal 1: At least one error
Element symbol.PVR. 0, 1 occurred)
Representative valve abnormal does not match
False
specification
Message suppression matches specification
True
Element symbol.MCSW. 0, 1 (0: Not suppressed 1: Suppressed)
False Message suppression does not match specification
D030340E.ai

*1: The condition specification of the AFL is the reference in all flashing state.
*2: The condition specification of the AOF is the reference in all suppressing alarm state.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-123

n Referencing Regulatory Control Block

The syntax for applying the block mode, block status, alarm status and data status of a regulatory
control block as condition test reference signal in a logic chart and the True/False representation
in the logic chart are shown as follows.
Table Syntax for Condition Signal Description and True/False Representation
Condition signal description column
True/false Satisfiable condition
Input signal Condition specification
True Block mode in specified state
Element symbol.MODE. Block mode
False Block mode not in specified state
True Block is in ROUT (MAN) or RCAS (MAN) mode.
BUM
False Block is not in ROUT (MAN) or RCAS (MAN) mode.
True Block is in ROUT (AUT) or RCAS (AUT) mode.
Element symbol.XMODE. BUA
False Block is not in ROUT (AUT) or RCAS (AUT) mode.
True Block is in ROUT (CAS) or RCAS (CAS) mode.
BUC
False Block is not in ROUT (CAS) or RCAS (CAS) mode.
True Block status in specified state
Element symbol.BSTS. Block status
False Block status not in specified state
True Specified alarm occurring
Element symbol.ALRM. Alarm status
False No occurrence of specified alarm
True Alarm is in IOP or IOP- status.
IOP
False Alarm is in neither IOP nor IOP- status.
Element symbol.XALRM.
True Alarm is in VEL+ or VEL- status.
VEL
False Alarm is in neither VEL+ nor VEL- status.
Alarm status, True Specified alarm in flashing state
Element symbol.AFLS.
AFL (*1) False Specified alarm in non-flashing state
True Canceling the specified alarm detection
Element symbol.AF. Alarm status
False Detecting the specified alarm
True IOP or IOP- detection is disabled.
Element symbol.XAF. IOP
False IOP and IOP- detection is enabled.
Alarm status, True Suppressing the specified alarm
Element symbol.AOFS.
AOF (*2) False Canceling the specified alarm in suppression
True Data value matches specification
Element symbol, Data item. Data value
False Data value does not match specification
True Data status matches specification
Element symbol, Data item= Data status
False Data status does not match specification
D030341E.ai

*1: The condition specification of the AFL is the reference in all flashing state.
*2: The condition specification of the AOF is the reference in all suppressing alarm state.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-124
l Data Items of Regulatory Control Blocks for Condition Test
The data items of the regulatory control blocks and the range of the data values that can be put in
the condition column for condition test are listed as follows.
Table Data Items of Regulatory Control Blocks and Range of Data Values for Condition Test (1/3)
Block code Name Data item Setting range
TSW 0, 1
CSW 0, 1
PID PID Controller Block PSW 0 to 3
RSW 0, 1
BSW 0, 1
TSW 0, 1
CSW 0, 1
PI-HLD Sampling PI Controller Block PSW 0 to 3
RSW 0, 1
BSW 0, 1
TSW 0, 1
CSW 0, 1
PID-BSW PID Controller Block with Batch Switch PSW 0 to 3
RSW 0, 1
BSW 0, 1
CSW 0, 1
PID-TP Time-Proportioning ON/OFF Controller Block PSW 0 to 3
BSW 0, 1
PSW 0 to 3
ONOFF 2-Position ON/OFF Controller Block
BSW 0, 1
PSW 0 to 3
ONOFF-E Enhanced 2-Position ON/OFF Controller Block
BSW 0, 1
PSW 0 to 3
ONOFF-G 3-Position ON/OFF Controller Block
BSW 0, 1
PSW 0 to 3
ONOFF-GE Enhanced 3-Position ON/OFF Controller Block
BSW 0, 1
TSW 0, 1
PSW 0 to 3
PD-MR PD Controller Block with Manual Reset
RSW 0, 1
BSW 0, 1
TSW 0, 1
PSW 0 to 3
PI-BLEND Blending PI Controller Block RSW 0, 1
BSW 0, 1
RST 0, 1
Block code Name Data item Setting range
D030342E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-125
Table Data Items of Regulatory Control Blocks and Range of Data Values for Condition Test (2/3)
Block code Name Data item Setting range
TSW 0, 1
CSW 0, 1
PSW 0 to 3
PID-STC Self-Tuning PID Controller Block
RSW 0, 1
BSW 0, 1
STC -1 to 3
TSW 0, 1
MLD Manual Loader Block
RSW 0, 1
TSW 0, 1
MLD-PVI Manual Loader Block with Input Indicator
RSW 0, 1
TSW 0, 1
MLD-SW Manual Loader Block with Auto/Man SW PSW 0 to 3
RSW 0, 1
TSW 0, 1
BSW 0, 1
BPSW 0 to 4
MC-2 2-Position Motor Control Block SIMM 0 to 1
CSV 0 to 2
PV 0 to 2
MV 0 to 2
TSW 0, 1
BSW 0, 1
BPSW 0 to 4
MC-2E Enhanced 2-Position Motor Control Block SIMM 0 to 1
CSV 0 to 2
PV 0 to 2
MV 0 to 2
TSW 0, 1
BSW 0, 1
BPSW 0 to 4
MC-3 3-Position Motor Control Block SIMM 0 to 1
CSV 0 to 2
PV 0 to 2
MV 0 to 2
TSW 0, 1
BSW 0, 1
BPSW 0 to 4
MC-3E Enhanced 3-Position Motor Control Block SIMM 0 to 1
CSV 0 to 2
PV 0 to 2
MV 0 to 2
Block code Name Data item Setting range
D030343E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-126
Table Data Items of Regulatory Control Blocks and Range of Data Values for Condition Test (3/3)
Block code Name Data item Setting range
TSW 0, 1
PSW 0 to 3
RATIO Ratio Set Block
RSW 0, 1
BSW 0, 1
ZONE 1 to 13
PG-L13 13-Zone Program Set Block ZSTR 1 to 13
ZEND 1 to 13
SW 0 to 4
BSETU-2 Flow-Totalizing Batch Set Block EMSW 0, 1
ZONE 0 to 11
SW 0 to 4
BSETU-3 Weight-Totalizing Batch Set Block EMSW 0, 1
ZONE 0 to 11
PSW 0 to 3
VELLIM Velocity Limiter Block BSW 0, 1
BPSW 0, 1
SW 0 to 4
SS-H/M/L Signal Selector Block
SEL 0 to 3
PSW 0 to 3
AS-H/M/L Autoselector Block SW 0 to 4
SEL 0 to 3
SW 1 to 3
SS-DUAL Dual-Redundant Signal Selector Block
SEL 1 to 2
TSW 0, 1
PSW 0 to 3
FFSUM Feedforward Signal Summing Block
FSW 0, 1
RSW 0, 1
TSW 0, 1
XCPL Non-Interference Control Output Block PSW 0 to 3
RSW 0, 1
BSW 0, 1
SPLIT Control Signal Splitter Block
SW 0 to 2
SW 0 to 5
ALM-R Representative Alarm Block
SV 0 to 15
SBSD YS Instrument Batch Set Station Block SV 0 to 8
SLBC YS Instrument Batch Controller Block SV 0 to 8
Block code Name Data item Setting range
D030344E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-127

n Referencing Calculation Block

The syntax for applying the block mode, block status, alarm status and data status of a
calculation block as condition test reference signal in a logic chart and the True/False
representation in the logic chart are shown as follows.
Table Syntax for Condition Signal Description and True/False Representation
Condition signal description column
Condition True/false Satisfiable condition
Input signal
specification
True Block mode matches specification
Element symbol.MODE. AUT, O/S
False Block mode does not match specification
True Block status matches specification
Element symbol.BSTS. Block status
False Block status does not match specification
True Alarm status in specified state
Element symbol.ALRM. CNF, NR
False Alarm status not in specified state
True Alarm is in IOP or IOP- status.
IOP
False Alarm is in neither IOP nor IOP- status.
Element symbol.XALRM.
True Alarm is in VEL+ or VEL- status.
VEL
False Alarm is in neither VEL+ nor VEL- status.

Alarm status, True Specified alarm in flashing state

Element symbol.AFLS.
AFL (*1)
False Specified alarm in non-flashing state
True Canceling the specified alarm detection
Element symbol.AF. CNF, NR
False Detecting the specified alarm
True IOP or IOP- detection is disabled.
Element symbol.XAF. IOP
False IOP and IOP- detection is enabled.

CNF, NR, True Suppressing the specified alarm

Element symbol.AOFS.
AOF (*2) False Canceling the specified alarm in suppression
True Calculation execution result is not 0
Element symbol.ACT. ON
False Calculation execution result is 0
True Data value matches specification
Element symbol.Data item. Data value (*3)
False Data value does not match specification
True Data status of specified data matches
Element symbol.Data item= Data status
False Data status of specified data does not match
D030345E.ai

*1: The condition specification of the AFL is the reference in all flashing state.
*2: The condition specification of the AOF is the reference in all suppressing alarm state.
*3: Only integers can be handled as data values, When the data type of the data item is a floating-point type, the comparison is
made by rounding off the value.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-128
l Data Items of Calculation Blocks for Condition Test
The data items of the calculation blocks and the range of the data values that can be put in the
condition column for condition test are listed as follows.
Table Data Items of Calculation Blocks and Range of Data Values for Condition Test (1/2)
Block code Name Data item Setting range
DLAY Dead-Time Block
DLAY-C Dead-Time Compensation Block RST 0, 1
AVE-M Moving-Average Block
INTEG Integration Block
SW 0, 1, 2
AVE-C Cumulative-Average Block
Three-Pole Three-Position Selector
SW-33 SW 0 to 3
Switch Block
BDSET-1L One-Batch Data Set Block
BDSET-1C One-Batch String Data Set Block
SW 0 to 3
BDSET-2L Two-Batch Data Set Block
BDSET-2C Two-Batch String Data Set Block
SW-91 One-Pole Nine-Position Selector Switch Block SW 0 to 9
DSW-16 Selector Switch Block for 16 Data
SW 0 to 16
DSW-16C Selector Switch Block for 16 String Data
BDA-L Batch Data Acquisition Block
SW 0 to 17
BDA-C Batch String Data Acquisition Block
D030346E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-129
Table Data Items of Calculation Blocks and Range of Data Values for Condition Test (2/2)
Block code Name Data item Setting range
AND Logical AND Block RV1 0, 1
RV2 0, 1
CPV 0, 1
OR Logical OR Block RV1 0, 1
RV2 0, 1
CPV 0, 1
NOT Logical NOT Block RV 0, 1
CPV 0, 1
SRS1-S Set-Dominant Flip-Flop Block with 1 Output RV1 0, 1
RV2 0, 1
CPV1 0, 1
SRS1-R Reset-Dominant Flip-Flop Block with 1 Output RV1 0, 1
RV2 0, 1
CPV1 0, 1
SRS2-S Set-Dominant Flip-Flop Block with 2 Outputs RV1 0, 1
RV2 0, 1
CPV1 0, 1
CPV2 0, 1
SRS2-R Reset-Dominant Flip-Flop Block with 2 Outputs RV1 0, 1
RV2 0, 1
CPV1 0, 1
CPV2 0, 1
WOUT Wipeout Block RV1 0, 1
RV2 0, 1
CPV 0, 1
OND ON-Delay Timer Block RV 0, 1
CPV 0, 1
OFFD OFF-Delay Timer Block RV 0, 1
CPV 0, 1
TON One-Shot Block (Rising-Edge Trigger) RV 0, 1
CPV 0, 1
TOFF One-Shot Block (Falling-Edge Trigger) RV 0, 1
CPV 0, 1
GT Comparator Block (Greater Than) CPV 0, 1
GE Comparator Block (Greater Than or Equal) CPV 0, 1
EQ Equal Operator Block CPV 0, 1
Block code Name Data item Setting range
D030347E.ai

Note: Logic Operation blocks can be used in FCSs except PFCS.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-130
l Calculation Blocks whose Results can be Referenced by One-Shot Execution
The one-shot executable calculation blocks whose calculation results can be referenced for
condition test with “element symbol. ACT.ON” script are shown as follows.
Table One-Shot Executable Blocks for Condition Test
Block type Block code Name
ADD Addition Block
MUL Multiplication Block
Arithmetic Calculation
DIV Division Block
AVE Averaging Block
AND Logical AND Block
OR Logical OR Block
NOT Logical NOT Block
SRS1-S Set-Dominant Flip-Flop Block with 1 Output
SRS1-R Reset-Dominant Flip-Flop Block with 1 Output
SRS2-S Set-Dominant Flip-Flop Block with 2 Outputs

Logic Operation SRS2-R Reset-Dominant Flip-Flop Block with 2 Outputs

Blocks (*1) WOUT Wipeout Block
GT Comparator Block (Greater Than)
GE Comparator Block (Greater Than or Equal)
EQ Equal Operator Block
BAND Bitwise AND Block
BOR Bitwise OR Block
BNOT Bitwise NOT Block

General-Purpose CALCU General-Purpose Calculation Block

Calculation CALCU-C General-Purpose Calculation Block with String I/O
D030348E.ai

*1: Logic Operation blocks can be used in FCSs except PFCS.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-131

n Referencing Faceplate Block

The syntax for applying the various types of data and data status of a faceplate block as condition
test reference signal in a logic chart and the True/False representation in the logic chart are
shown as follows.
Table Syntax for Condition Signal Description and True/False Representation (1/2)
Condition signal description column True/
Satisfiable condition
Input signal Condition specification false

True Block mode in specified state

Element symbol.MODE. Block mode
False Block mode not in specified state
True Block is in ROUT (MAN) or RCAS (MAN) mode.
BUM
False Block is not in ROUT (MAN) or RCAS (MAN) mode.
True Block is in ROUT (AUT) or RCAS (AUT) mode.
Element symbol.XMODE. BUA
False Block is not in ROUT (AUT) or RCAS (AUT) mode.
True Block is in ROUT (CAS) or RCAS (CAS) mode.
BUC
False Block is not in ROUT (CAS) or RCAS (CAS) mode.
True Block status in specified state
Element symbol.BSTS. Block status
False Block status not in specified state
True Specified alarm occurring
Element symbol.ALRM. Alarm status
False No occurrence of specified alarm
True Alarm is in IOP or IOP- status.
IOP
False Alarm is in neither IOP nor IOP- status.
Element symbol.XALRM.
True Alarm is in VEL+ or VEL- status.
VEL
False Alarm is in neither VEL+ nor VEL- status.

Alarm status, True Specified alarm in flashing state

Element symbol.AFLS.
AFL (*1) False Specified alarm in non-flashing state
True Canceling the specified alarm detection
Element symbol.AF. Alarm status
False Detecting the specified alarm
True IOP or IOP- detection is disabled.
Element symbol.XAF. IOP
False IOP and IOP- detection is enabled.

Alarm status, True Suppressing the specified alarm

Element symbol.AOFS.
AOF (*2) False Canceling the specified alarm in suppression
1 to 99 True Batch step number matches specification
Element symbol.SV. (Valid only for
BSI blocks) False Batch step number does not match specification
True Operation command matches specification
Element symbol.PV01 to 10. 0, 1
False Operation command does not match specification
True Data status matches specification
Element symbol.Data item= Data status
False Data status does not match specification
D030349E.ai

*1: The condition specification of the AFL is the reference in all flashing state.
*2: The condition specification of the AOF is the reference in all suppressing alarm state.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-132
Table Syntax for Condition Signal Description and True/False Representation (2/2)
Condition signal description column True/
Satisfiable condition
Input signal (*1) Condition specification false

True Switch display color matches specification

Element symbol.SWCR[1 to n]. 0 to 15
False Switch display color does not match specification
True Switch flashing status matches specification
Element symbol.SWST[1 to n]. 0, 1
False Switch flashing status does not match specification
True Switch operation prohibited status matches specification
Element symbol.SWOP[1 to n]. -15 to 15
False Switch operation prohibited status does not match specification
D0303A0E.ai

*1: n indicates the number of elements in a one-dimensional array. This is the number of push-button switches in a faceplate block,
and varies with the type of each faceplate block.

n Referencing SFC Block

The syntax for applying the various types of data and data status of a SFC block as condition test
reference signal in a logic chart and the True/False representation in the logic chart are shown as
follows.
Table Syntax for Condition Signal Description and True/False Representation
Condition signal description column
Condition True/false Satisfiable condition
Input signal
specification

MAN, SEMI, True Block mode in specified state

Element symbol.MODE.
AUT, O/S False Block mode not in specified state

RUN, PAUS, True Block status in specified state

Element symbol.BSTS.
STOP, ABRT False Block status not in specified state
True Specified alarm occurring
Element symbol.ALRM. Alarm status
False No occurrence of specified alarm

Alarm status, True Specified alarm in flashing state

Element symbol.AFLS.
AFL (*1) False Specified alarm in non-flashing state
True Canceling the specified alarm detection
Element symbol.AF. Alarm status
False Detecting the specified alarm

Alarm status, True Suppressing the specified alarm

Element symbol.AOFS. AOF (*2) False Canceling the specified alarm in suppression
True Data value matches specification
Element symbol.Dataitem. Data value
False Data value does not match specification
True Data status matches specification
Element symbol.Dataitem= Data status
False Data status does not match specification
D030350E.ai

*1: The condition specification of the AFL is the reference in all flashing state.
*2: The condition specification of the AOF is the reference in all suppressing alarm state.

l Range of Data Value When Referencing the Data Items for Condition Test
The ranges of data values when referencing SFC data items in a logic chart for condition test are
shown as follows.
• STEPNO: 1 to 99
• SWCR[5]: 0 to 15
• SWST[5]: 0, 1
• SWOP[5]: -15 to 15

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-133

n Referencing Unit Instrument

The syntax for applying the various types of data and data status of a unit instrument block as
condition test reference signal in a logic chart and the True/False representation in the logic chart
are shown as follows.
Table Syntax for Condition Signal Description and True/False Representation
Condition signal description column
Condition True/false Satisfiable condition
Input signal
specification

MAN,SEMI, True Unit mode in specified state

Element symbol.MODE.
AUT,O/S False Unit mode not in specified state
True Unit status in specified state
Element symbol.BSTS. Unit status
False Unit status not in specified state
True Specified alarm occurring
Element symbol.ALRM. Alarm status
False No occurrence of specified alarm

Alarm status, True Specified alarm in flashing state

Element symbol.AFLS.
AFL (*1) False Specified alarm in non-flashing state
True Canceling the specified alarm detection
Element symbol.AF. Alarm status
False Detecting the specified alarm

Alarm status, True Suppressing the specified alarm

Element symbol.AOFS.
AOF (*2) False Canceling the specified alarm in suppression
True SFC step number matches specification
Element symbol.STEPNO. 1 to 99 SFC step number does not match
False
specification
D030351E.ai

*1: The condition specification of the AFL is the reference in all flashing state.
*2: The condition specification of the AOF is the reference in all suppressing alarm state.

n Referencing Process I/O

The syntax for applying the various types of data and data status of a process I/O as condition
test reference signal in a logic chart and the True/False representation in the logic chart are
shown as follows.
Table Syntax for Condition Signal Description and True/False Representation
Condition signal description column
Condition True/false Satisfiable condition
Input signal specification
Contact I/O ON/OFF state matches
True
specification
Element symbol.PV. ON, OFF
Contact I/O ON/OFF state does not match
False
specification
True Contact I/O data status matches specification
Element symbol.PV= Data status Contact I/O data status does not match
False
specification
D030352E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-134

n Referencing Global Switch

The syntax for applying the various types of data and data status of a global switch as condition
test reference signal in a logic chart and the True/False representation in the logic chart are
shown as follows.
Table Syntax for Condition Signal Description and True/False Representation
Condition signal description column
Condition True/false Satisfiable condition
Input signal specification

True Specified global switch status is True.

Element symbol.PV. ON, OFF
False Specified global switch status is False.
True Data status of global switch is BAD.
Element symbol.PV= BAD
False Data status of global switch is not BAD.
D030353E.ai

n Referencing Common Switch

The syntax for applying the data of a common switch as condition test reference signal in a logic
chart and the True/False representation in the logic chart are shown as follows.
Table Syntax for Condition Signal Description and True/False Representation
Condition signal description column
Condition True/false Satisfiable condition
Input signal
specification
Specified internal status switch ON/OFF state
True
matches specification
Element symbol.PV. ON, OFF
Specified internal status switch ON/OFF state
False
does not match specification
D030354E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-135

n Referencing Annunciator Message

The syntax for applying the various types of data and data status of an annunciator message as
condition test reference signal in a logic chart and the True/False representation in the logic chart
are shown as follows.
Table Syntax for Condition Signal Description and True/False Representation
Condition signal description column
Condition True/false Satisfiable condition
Input signal
specification
Annunciator occurrence state matches
True specification
Element symbol.PV. ON, OFF (On: Occurred OFF: No occurrence)
Annunciator occurrence state does not match
False
specification
True Flashing state
Element symbol.AFLS. AFL
False Steady state (non-flashing state)
True Alarm suppressing state
Element symbol.AOFS. AOF
False Steady state (non-alarm suppressing state)
Repeated warning status is consistent with
True specification
Element symbol.RP. ON, OFF (ON: Wait for repeated warning OFF: NR)
Repeated warning state is not consistent with
False
specification
D030355E.ai

n Referencing Communication I/O

The syntax for applying the various types of data and data status of a Communication I/O as
condition test reference signal in a logic chart and the True/False representation in the logic chart
are shown as follows.
Table Syntax for Condition Signal Description and True/False Representation
Condition signal description column
Condition True/false Satisfiable condition
Input signal
specification
Specified bit ON/OFF state matches
True
Element symbol.PV. specification
ON, OFF
(*1) Specified bit ON/OFF state does not match
False
specification
Specified bit data status matches
True
specification
Element symbol.PV= Data status
Specified bit data status does not match
False
specification
D030356E.ai

*1: Only discrete type element may be referred.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-136

D3.3.8 Syntax for Condition Signal Description: Referencing

Logic Chart
When referencing a logic chart for condition test, a block mode and an alarm status of a
logic chart can be used as a reference signal in other logic charts.

n Referencing Logic Chart Block Mode

The specified logic chart block mode can be used as reference signal in logic charts. The syntax
for applying the logic chart block mode as condition test reference signal and the True/False
representation are shown as follows.
Table Syntax for Condition Signal Description and True/False Representation
Condition signal description column
Condition True/false Satisfiable condition
Input signal
specification
True Specified Block mode is True.
Element symbol.MODE. O/S, MAN, AUT
False Specified Block mode is False.
D030357E.ai

The following points should be taken into consideration when referencing a logic chart block
mode.
• When O/S is specified as the condition specification for block mode reference, the test result
will be False when the block is in the compound block mode, i.e., O/S and another basic
block mode exist simultaneously.
• When MAN or AUT is specified as the condition specification for block mode reference, the
test result will be True even in the compound block mode as long as the specified basic
block mode exists.

n Referencing Logic Chart Alarm Status

The specified alarm status of a logic chart can be used as reference signal in logic charts.
The syntax for applying the alarm status of logic chart as condition test reference signal and the
True/False representation are shown as follows.
Table Syntax for Condition Signal Description and True/False Representation
Condition signal description column
Condition True/false Satisfiable condition
Input signal
specification
True Specified Alarm Status is True.
Element symbol.ALRM. NR
False Specified Alarm Status is False.
True Specified Alarm symbol is flashing.
Element symbol.AFLS. AFL (*1), NR
False Specified Alarm symbol is not flashing.
True Alarm Detection Disabled is True.
Element symbol.AF. NR
False Alarm Detection Disabled is False.
True Alarm Inhibition is True.
Element symbol.AOFS. NR, AOF (*2)
False Alarm Inhibition is False.
D030358E.ai

*1: The condition test for Alarm Symbol Flashing can only test the flashing status of each block or symbol, can not test the flashing
status of each alarming item.
*2: The condition test for Alarm Inhibition can only test the inhibition status of each block or symbol, can not test the inhibition status
of each alarming item.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-137

D3.3.9 Syntax for Condition Signal Description: Referencing

Sequence Table in a Logic Chart
When referencing a sequence table for condition test, the true or false status of the
condition for one-shot execution of the referenced sequence table as well as the block
mode and status of the sequence table can be applied.
To reference a sequence table whose number of rules is extended over multiple sequence
tables, the tag name of the base sequence table needs to be specified.

n Referencing the Entire Sequence Table

A specified sequence table can be one-shot started and the True/False status of the entire
sequence table’s condition can be referenced by a logic chart.
The syntax for referencing an entire sequence table condition as the condition test signal in a
logic chart and the True/False representation are shown as follows.
Table Syntax for Condition Signal Description and True/False Representation
Condition signal description column Condition
Condition rule Conditions for true status
Input signal column
specification
Y At least one target condition rule is satisfied.
Element symbol.SD. R
N None of the target condition rules is satisfied.
D030359E.ai

The following should be taken into account when referencing the entire sequence table.
• When referencing the entire sequence table, only condition signal descriptions of the
referenced sequence table are valid. Ignore any signal description.
• If no Y/N pattern exists in the condition rule of referenced sequence table, the status of rule
condition is false. If the Y/N pattern of such condition rule is unspecified, the status becomes
unconditionally true in the periodic processing of the above sequence table.
• When there exist no steps to be executed in the referenced sequence table, the previous
true/false status of condition is maintained as a current reference result.
• When Step 00 exists in the reference destination, rules that belong to Step 00 will also be
executed. However, when no steps exist as an execution target, the reference result of Step
00 is ignored.
• Other sequence tables can be referenced in the referenced sequence table condition
column. In this case, up to seven levels of nests (including the first sequence table) are
possible.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-138

n Referencing a Particular Step in a Sequence Table

A specified sequence table can be one-shot started and a particular step of the sequence table
can be referenced by a logic chart.
The syntax for a particular sequence table step reference as the condition test signal in a logic
chart and the True/False representation are shown as follows.
Table Syntax for Condition Signal Description and True/False Representation
Condition signal description column Condition
Condition rule Conditions for true status
Input signal column
specification
At least one of the conditions for steps 00
Y
and xx is satisfied.
Element symbol.SA. xx
None of the conditions for steps 00 and xx is
N
satisfied.
D030360E.ai

xx: Specify a step label using 2 or less alphanumeric characters.

The following should be taken into account when referencing a corresponding rule number.
• When referencing a particular step in a sequence table, only condition signal descriptions of
the referenced sequence table are valid. Ignore any action signal description.
• If no Y/N pattern exists in the condition rule of referenced sequence table, the status of
rule condition is false. If the Y/N pattern of such a condition rule is unspecified, the status
becomes unconditionally true in the periodic processing of the above sequence table.
• Other sequence tables can be referenced in the referenced sequence table condition
column. In this case, up to seven levels of nests (including the first sequence table) are
possible.

n Referencing Sequence Table Step Label

A sequence progress state can be confirmed by referencing the related sequence table step
labels. However, it only check if the sequence step corresponding to the specified sequence step
label is being processed or not, it does not involve the conditions test of the step’s True/False
status.
The syntax for a Sequence Table Step Label Reference as the condition test signal in a logic
chart and the True/False representation are shown as follows.
Table Syntax for Condition Signal Description and True/False Representation
Condition signal description column Condition
Condition rule Conditions for true status
Input signal column
specification
Y Current execution step label is xx.
Element symbol.PV. xx
N Current execution step label is other than xx.
D030361E.ai

xx: Specify a step label using 2 or less alphanumeric characters.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-139

n Referencing Sequence Table Block Mode

The specified sequence table block mode can be used as reference signal in a logic chart.
The syntax for applying the sequence table block mode as condition test reference signal in a
logic chart and the True/False representation are shown as follows.
Table Syntax for Condition Signal Description and True/False Representation
Condition signal description column
Condition True/false Satisfiable condition
Input signal
specification
True Specified Block mode is True.
Element symbol.MODE. O/S, MAN, AUT
False Specified Block mode is False.
D030362E.ai

The following points should be taken into consideration when referencing a sequence table block
mode.
• When O/S is specified as the condition specification for block mode reference, the test result
will be False when the block is in the compound block mode, i.e., O/S and another basic
block mode exist simultaneously.
• When MAN or AUT is specified as the condition specification for block mode reference, the
test result will be True even in the compound block mode as long as the specified basic
block mode exists.

n Referencing Sequence Table Alarm Status

The specified alarm status of a sequence table can be used as reference signal in a logic chart.
The syntax for applying the alarm status of sequence table as condition test reference signal in a
logic chart and the True/False representation are shown as follows.
Table Syntax for Condition Signal Description and True/False Representation of Y/N in Condition Rule
Columns
Condition signal description column
Condition True/false Satisfiable condition
Input signal
specification
True Specified Alarm Status is True.
Element symbol.ALRM. NR
False Specified Alarm Status is False.
True Specified Alarm symbol is flashing.
Element symbol.AFLS. AFL (*1), NR
False Specified Alarm symbol is not flashing.
True Alarm Detection Disabled is True.
Element symbol.AF. NR
False Alarm Detection Disabled is False.
True Alarm Inhibition is True.
Element symbol.AOFS. NR, AOF (*2)
False Alarm Inhibition is False.
D030363E.ai

*1: The condition test for Alarm Symbol Flashing can only test the flashing status of each block or symbol; it can not test the flashing
status of each alarming item.
*2: The condition test for Alarm Inhibition can only test the inhibition status of each block or symbol; it can not test the inhibition status
of each alarming item.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-140

D3.3.10 Action Signal Description: Status Manipulation for

Other Function Blocks and I/O Data
Logic chart block can be used to manipulate the execution, the mode or status change
of other function blocks as well as the status change of process I/O, software I/O and
communication I/O.

n Function Blocks and I/O Data that can be Manipulated from Logic
Chart
Function blocks for which status manipulation that can be performed from the sequence table
are:
• Switch instrument blocks
• Timer Block (TM)
• Software Counter Block (CTS)
• Pulse Train Input Counter Block (CTP)
• Code Input Block (CI)
• Code Output Block (CO)
• Resource Scheduler Block (RS)
• Valve Monitoring Block (VLVM)
• Regulatory Control Blocks
• Calculation Blocks
• Faceplate Blocks
• SFC Blocks
• Unit instrument Blocks
• Sequence Table Blocks
• Logic Chart Blocks

In addition, the following I/O data can be manipulated from logic chart:
• Process I/O
• Software I/O (internal switch, annunciator message, sequence message output)
• Communication I/O

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-141

n Status Manipulation of Switch Instrument Block and Enhanced Switch

Instrument Block
The syntax for applying the various functions of a switch instrument block and an enhanced
switch instrument block as status manipulation signal in a logic chart and the actions
corresponding to True/False are shown as follows.
Table Syntax for Action Signal Description and Actions Corresponding to True/False
Manipulation signal description
True/False Manipulation description
Output signal Action Specifications

MAN, AUT, CAS, True Block mode change command

Element symbol.MODE.
ROUT, O/S False Disable

ANS+, ANS-, IOP, True Release detection of specified alarm

Element symbol.AF.
PERR, OOP, CNF False Perform detection of specified alarm
True Disables IOP and IOP- detection
Element symbol.XAF. IOP
False Enables IOP and IOP- detection

ANS+, ANS-, PERR, True Perform suppression of specified alarm

Element symbol.AOFS.
CNF, IOP, AOF (*1), OOP False Release suppression of specified alarm
True Perform group verification of alarms
Element symbol.AFLS. AFL
False Disable
True Setting of sequence setpoint value (CSV) (*2)
0, 1, 2
False Disable
True Set CSV to 0
P0
False Set CSV to 2
Element symbol.CSV.
True Set CSV to 1
P1
False Disable
True Set CSV to 2
P2
False Set CSV to 0
True Tracking switch (0; OFF, 1; ON)
Element symbol.TSW. 0, 1
False Disable
True Bypass switch (0; OFF, 1; ON)
Element symbol.BPSW. 0, 1
False Disable
True Backup switch (0; OFF, 1; ON)
Element symbol.BSW. 0, 1
False Disable
True Switch to CAL or release CAL
Element symbol.PV. =XCAL (*3)
False –
D030364E.ai

*1: The AOF specification is valid only with respect to the change in the alarm suppression specification. This operation performs
alarm suppression for all alarms with the exception of the NR alarm.
*2: Sequence setpoint value (CSV) data is written when the switch instrument manipulated output value (MV) is set from another
function block. If the switch instrument block or the enhanced switch instrument block is in AUT or CAS state, output is executed
after the sequence setpoint value (CSV) is written in the manipulated output value (MV).
*3: The type of logic chart that =XCAL is applied should be set to [One-Shot Processing Type (O)].

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-142

n Status Manipulation of Timer Block (TM)

The syntax for applying the various functions of a Timer Block (TM) as status manipulation signal
in a logic chart and the actions corresponding to True/False are shown as follows.
Table Syntax for Action Signal Description and Actions Corresponding to True/False
Manipulation signal description
True/False Manipulation description
Output signal Action Specifications
True Timer stop command
STOP
False Disable
True Timer startup command
START
False Timer stop command (*1)
Element symbol.OP.
True Restart command
RSTR
False Disable
True Pause command
WAIT
False Restart command (*1)
D030365E.ai

*1: When connected to the function blocks other than logic chart and sequence table blocks via sequence connection, the true
actions are valid while the false actions are invalid.

n Status Manipulation of Software Counter Block (CTS)

The syntax for applying the various functions of a software counter (CTS) block as status
manipulation signal in a logic chart and the actions corresponding to True/False are shown as
follows.
Table Syntax for Action Signal Description and Actions Corresponding to True/False
Manipulation signal description
True/False Manipulation description
Output signal Action Specifications
True Operation manipulation of software counter
ON
False Disable
Element symbol.ACT.
True Software counter stop command
OFF
False Disable
D030366E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-143

n Status Manipulation of Pulse Train Input Counter Block (CTP)

The syntax for applying the various functions of a Pulse Train Input Counter (CTP) block as
status manipulation signal in a logic chart and the actions corresponding to True/False are shown
as follows.
Table Syntax for Action Signal Description and Actions Corresponding to True/False
Manipulation signal description
True/False Manipulation description
Output signal Action Specifications
True Pulse-input counter stop command
STOP
False Disable
True Pulse-input counter start command
START
False Disable
Element symbol.OP.
True Restart command
RSTR
False Disable
True Pause command
WAIT
False Disable
True Release detection of specified alarm
Element symbol.AF. IOP, CNF
False Perform detection of specified alarm
True Disables IOP and IOP- detection
Element symbol.XAF. IOP
False Enables IOP and IOP- detection
True Perform suppression of specified alarm
Element symbol.AOFS. IOP, CNF, AOF (*1)
False Release suppression of specified alarm
True Perform group verification of alarms
Element symbol.AFLS. AFL
False Disable
D030367E.ai

*1: The AOF specification is valid only with respect to the change in the alarm suppression specification. This operation performs
alarm suppression for all alarms with the exception of the NR alarm.

n Status Manipulation of Code Input Block (CI)

The syntax for applying the various functions of a Code Input (CI) block as status manipulation
signal in a logic chart and the actions corresponding to True/False are shown as follows.
Table Syntax for Action Signal Description and Actions Corresponding to True/False
Manipulation signal description
True/False Manipulation description
Output signal Action Specifications
True Code-input read command
Element symbol.ACT. ON
False Disable
D030368E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-144

n Status Manipulation of Code Output Block (CO)

The syntax for applying the various functions of a Code Output (CO) Block as status manipulation
signal in a logic chart and the actions corresponding to True/False are shown as follows.
Table Syntax for Action Signal Description and Actions Corresponding to True/False
Manipulation signal description
True/False Manipulation description
Output signal Action Specifications
True Code output command
Element symbol.ACT. ON
False Disable
D030369E.ai

n Status Manipulation of Resource Scheduler Block (RS)

The syntax for applying the various functions of a Resource Scheduler (RS) Block as status
manipulation signal in a logic chart and the actions corresponding to True/False are shown as
follows.
Table Syntax for Action Signal Description and Actions Corresponding to True/False
Manipulation signal description
True/False Manipulation description
Output signal Action Specifications
Usage cancel/request command for specified number
True
Element symbol.RQ01 to 32. 0, 1 (1: request, 0: cancel)
False Disable
True Setting of maximum allowed number (m≤32)
Element symbol.PMH. 0 to 32
False Disable
Group resources all request/cancel
True
Element symbol.ACT. ON, OFF (ON: request, OFF: cancel)
False Disable
D030370E.ai

n Status Manipulation of Valve Monitoring Block (VLVM)

The syntax for applying the various functions of a Valve Monitoring (VLVM) Block as status
manipulation signal in a logic chart and the actions corresponding to True/False are shown as
follows.
Table Syntax for Action Signal Description and Actions Corresponding to True/False
Manipulation signal description
True/False Manipulation description
Output signal Action Specifications
True Message suppression (1: suppress 0: do not suppress)
Element symbol.MCSW. 0, 1
False Disable
D030371E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-145

n Status Manipulation of Regulatory Control Block

The syntax for applying the various functions of a regulatory control block as status manipulation
signal in a logic chart and the actions corresponding to True/False are shown as follows.
Table Syntax for Action Signal Description and Actions Corresponding to True/False
Manipulation signal description
True/False Manipulation description
Output signal Action Specifications

MAN, CAS, RCAS, True Block mode change command

Element symbol.MODE.
AUT, ROUT, PRD, O/S False Disable

Alarm status excluding True Release detection of specified alarm

Element symbol.AF.
NR False Perform detection of specified alarm
True Disables IOP and IOP- detection
Element symbol.XAF. IOP
False Enables IOP and IOP- detection

Alarm status excluding True Perform suppression of specified alarm

Element symbol.AOFS.
NR, AOF (*1) False Release suppression of specified alarm
True Perform group verification of alarms
Element symbol.AFLS. AFL
False Disable
True Data setting
Element symbol.Data Item Data value
False Disable
True Switch PV to CAL status
Element symbol.PV= CAL
False Release PV from CAL status
True Switch to CAL or release CAL
Element symbol.PV. =XCAL (*2)
False –
True Switch to CAL or release CAL
Element symbol.SUM0. =XCAL (*2)
False –
D030372E.ai

*1: The AOF specification is valid only with respect to the change in the alarm suppression specification. This operation performs
alarm suppression for all alarms with the exception of the NR alarm.
*2: The type of logic chart that =XCAL is applied should be set to [One-Shot Processing Type (O)].

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-146
l Data Items of Regulatory Control Blocks for Status Manipulation
The data items of the regulatory control blocks and the range of the data values that can be
applied for status manipulation are listed as follows.
Table Data Items of Regulatory Control Blocks and Range of Data Values for Status Manipulation (1/3)
Block code Name Data item Setting range
TSW 0, 1
CSW 0, 1
PID PID Controller Block PSW 0 to 3
BSW 0, 1
RSW 0, 1
TSW 0, 1
CSW 0, 1
PI-HLD Sampling PI Controller Block PSW 0 to 3
BSW 0, 1
RSW 0, 1
TSW 0, 1
CSW 0, 1
PID-BSW PID Controller Block with Batch Switch PSW 0 to 3
BSW 0, 1
RSW 0, 1
CSW 0, 1
PID-TP Time-Proportioning ON/OFF Controller Block PSW 0 to 3
BSW 0, 1
PSW 0 to 3
ONOFF 2-Position ON/OFF Controller Block
BSW 0, 1
PSW 0 to 3
ONOFF-E Enhanced 2-Position ON/OFF Controller Block
BSW 0, 1
PSW 0 to 3
ONOFF-G 3-Position ON/OFF Controller Block
BSW 0, 1
PSW 0 to 3
ONOFF-GE Enhanced 3-Position ON/OFF Controller Block
BSW 0, 1
TSW 0, 1
PSW 0 to 3
PD-MR PD Controller Block with Manual Reset
BSW 0, 1
RSW 0, 1
TSW 0, 1
PSW 0 to 3
PI-BLEND Blending PI Controller Block BSW 0, 1
RSW 0, 1
RST 0, 1
Block code Name Data item Setting range
D030373E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-147
Table Data Items of Regulatory Control Blocks and Range of Data Values for Status Manipulation (2/3)
Block code Name Data item Setting range
TSW 0, 1
CSW 0, 1
PSW 0 to 3
PID-STC Self-Tuning PID Controller Block
BSW 0, 1
RSW 0, 1
STC -1 to 3
TSW 0, 1
MLD Manual Loader Block
RSW 0, 1
TSW 0, 1
MLD-PVI Manual Loader Block with Input Indicator
RSW 0, 1
TSW 0, 1
MLD-SW Manual Loader Block with Auto/Man SW PSW 0 to 3
RSW 0, 1
TSW 0, 1
BSW 0, 1
BPSW 0 to 4
MC-2 2-Position Motor Control Block
SIMM 0 to 1
0, 1, 2, P0, P1,
CSV P2 (*1)
TSW 0, 1
BSW 0, 1
BPSW 0 to 4
MC-2E Enhanced 2-Position Motor Control Block
SIMM 0 to 1
0, 1, 2, P0, P1,
CSV P2 (*1)
TSW 0, 1
BSW 0, 1
BPSW 0 to 4
MC-3 3-Position Motor Control Block
SIMM 0 to 1
0, 1, 2, P0, P1,
CSV P2 (*1)
TSW 0, 1
BSW 0, 1
BPSW 0 to 4
MC-3E Enhanced 3-Position Motor Control Block
SIMM 0 to 1
0, 1, 2, P0, P1,
CSV P2 (*1)
Block code Name Data item Setting range
D030374E.ai

*1: The values set to the CSV varied according to the data in the manipulation rule column and setting range as shown below.
0: CSV=0 when the manipulation rule column is “TRUE,” disabled when “FALSE.”
1: CSV=1 when the manipulation rule column is “TRUE,” disabled when “FALSE.”
2: CSV=2 when the manipulation rule column is “TRUE,” disabled when “FALSE.”
P0: CSV=0 when manipulation rule column is “TRUE,” CSV=2 when “FALSE.”
P1: CSV=1 when manipulation rule column is “TRUE,” disabled when “FALSE.”
P2: CSV=2 when manipulation rule column is “TRUE,” CSV=0 when “FALSE.”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-148
Table Data Items of Regulatory Control Blocks and Range of Data Values for Status Manipulation (3/3)
Block code Name Data item Setting range
TSW 0, 1
PSW 0 to 3
RATIO Ratio Set Block
BSW 0, 1
RSW 0, 1
ZONE 1 to 13
PG-L13 13-Zone Program Set Block ZSTR 1 to 13
ZEND 1 to 13
SW 0 to 4
BSETU-2 Flow-Totalizing Batch Set Block EMSW 0, 1
ZONE 0 to 11
SW 0 to 4
BSETU-3 Weight-Totalizing Batch Set Block EMSW 0, 1
ZONE 0 to 11
PSW 0 to 3
VELLIM Velocity Limiter Block BSW 0, 1
BPSW 0, 1
SS-H/M/L Signal Selector Block SW 0 to 4
PSW 0 to 3
AS-H/M/L Auto-Selector Block
SW 0 to 4
SS-DUAL Dual-Redundant Signal Selector Block SW 1 to 3
TSW 0, 1
PSW 0 to 3
FFSUM Feedforward Signal Summing Block
FSW 0, 1
RSW 0, 1
TSW 0, 1
XCPL Non-Interference Control Output Block PSW 0 to 3
RSW 0, 1
BSW 0, 1
SPLIT Control Signal Splitter Block
SW 0 to 2
RST 0, 1
PTC Pulse Count Input Block
HSW 0, 1
SW 0 to 5
ALM-R Representative Alarm Block
SV 0 to 15
SBSD YS Instrument Batch Set Station Block SV 0 to 8
SLBC YS Instrument Batch Controller Block SV 0 to 8
Block code Name Data item Setting range
D030375E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-149

n Status Manipulation of Calculation Block

The syntax for applying the various functions of a calculation block as status manipulation signal
in a logic chart and the actions corresponding to True/False are shown as follows.
Table Syntax for Action Signal Description and Actions Corresponding to True/False
Manipulation signal description
True/False Manipulation description
Output signal Action Specifications
True One-shot startup (with parameter)
mm (*1)
False Disable
Element symbol.ACT.
True One-shot startup (without parameter)
ON
False Disable

Alarm status excluding True Release detection of specified alarm

Element symbol.AF.
NR False Perform detection of specified alarm
True Disables IOP and IOP- detection
Element symbol.XAF. IOP
False Enables IOP and IOP- detection

Alarm status excluding True Perform suppression of specified alarm

Element symbol.AOFS.
NR, AOF (*2) False Release suppression of specified alarm
True Perform group verification of alarms
Element symbol.AFLS. AFL
False Disable
True Data setting
Element symbol.data item. Data value
False Disable
True Set PV data status to CAL
Element symbol.CPV= CAL
False Release the CAL data status of CPV
True Switch to CAL or release CAL
Element symbol.CPV. =XCAL (*3)
False –
True Switch to CAL or release CAL
Element symbol.CPV1. =XCAL (*3)
False –
True Switch to CAL or release CAL
Element symbol.CPV2. =XCAL (*3)
False –
D030376E.ai

*1: mm is required parameter for one-shot execution of the batch data setting block and batch data collection block. Data that will be
set during a one-shot execution according to the mm value.
mm=0: All setting data are set to 0.
mm=1 to 16: Only the specified data (DTn) is set.
mm=17: All data will be set.
*2: The AOF specification is valid only with respect to the change in the alarm suppression specification. This operation performs
alarm suppression for all alarms with the exception of the NR alarm.
*3: The type of logic chart that =XCAL is applied should be set to [One-Shot Processing Type (O)].

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-150
l Data Items of Calculation Blocks for Status Manipulation
The data items of the calculation blocks and the range of the data values that can be applied for
status manipulation are listed as follows.
Table Data Items of Calculation Blocks and Range of Data Values for Status Manipulation
Block code Name Data item Setting range
DLAY Dead-Time Block
DLAY-C Dead-Time Compensation Block RST 0, 1
AVE-M Moving-Average Block
INTEG Integration Block
SW 0, 1, 2
AVE-C Cumulative-Average Block
SW-33 Three-Pole Three-Position Selector Switch Block SW 0 to 3
BDSET-1L One-Batch Data Set Block
BDSET-1C One-Batch String Data Set Block
SW 0 to 3
BDSET-2L Two-Batch Data Set Block
BDSET-2C Two-Batch String Data Set Block
ADL Interstation Connection Block SIMM 0, 1
SW-91 One-Pole Nine-Position Selector Switch Block SW 0 to 9
DSW-16 Selector Switch Block for 16 Data
SW 0 to 16
DSW-16C Selector Switch Block for 16 String Data
BDA-L Batch Data Acquisition Block
SW 0 to 17
BDA-C Batch String Data Acquisition Block
D030377E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-151
l One-Shot Executable Calculation Blocks
The one-shot executable calculation blocks can be applied for status manipulation are shown as
follows.
Table One-Shot Executable Calculation Blocks for Status Manipulation
Block Type Model Name Description
ADD Addition Block

Arithmetic MUL Multiplication Block

Calculation DIV Division Block
AVE Averaging Block
AND Logical AND Block
OR Logical OR Block
NOT Logical NOT Block
SRS1-S Set-Dominant Flip-Flop Block with 1 Output
SRS1-R Reset-Dominant Flip-Flop Block with 1 Output
SRS2-S Set-Dominant Flip-Flop Block with 2 Outputs
SRS2-R Reset-Dominant Flip-Flop Block with 2 Outputs
Logic Operation (*1)
WOUT Wipeout Block
GT Comparator Block (Greater Than)
GE Comparator Block (Greater Than or Equal)
EQ Equal Operator Block
BAND Bitwise AND Block
BOR Bitwise OR Block
BNOT Bitwise NOT Block

General-purpose CALCU General-Purpose Calculation Block

Calculation CALCU-C General-Purpose Calculation Block with String I/O
BDSET-1L One-Batch Data Set Block
BDSET-1C One-Batch String Data Set Block

Calculation BDSET-2L Two-Batch Data Set Block

Auxiliary BDSET-2C Two-Batch String Data Set Block
BDA-L Batch Data Acquisition Block
BDA-C Batch String Data Acquisition Block
D030378E.ai

*1: Logic Operation Blocks can be used in FCSs except PFCS.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-152
l Calculation Blocks Requiring One-Shot Parameter mm
The calculation blocks that require mm parameter for one-shot execution when applied for status
manipulation are shown as follows.
Table One-Shot Parameter Required Calculation Blocks for Status Manipulation
Parameter setting
Block code Name Comments
Range (mm)
BDSET-1L One-Batch Data Set Block
BDSET-1C One-Batch String Data Set Block Individual data
0 to 17
BDSET-2L Two-Batch Data Set Block setting

BDSET-2C Two-Batch String Data Set Block

BDA-L Batch Data Acquisition Block Individual data
0 to 17
BDA-C Batch String Data Acquisition Block acquisition

D030379E.ai

Note: Data that will be set during a one-shot execution according to the mm value.
mm=0: All setting data are set to 0.
mm=1 to 16: Only the specified data (DTn) is set.
mm=17: All data will be set.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-153

n Status Manipulation of Faceplate Block

The syntax for applying the various functions of a faceplate block as status manipulation signal in
a logic chart and the actions corresponding to True/False are shown as follows.
Table Syntax for Action Signal Description and Actions Corresponding to True/False
Manipulation signal description
True/False Manipulation description
Output signal Action Specifications
True Change block mode
Element symbol.MODE. Block mode
False Disable
True Change block status
Element symbol.BSTS. Block Status
False Release block status

Alarm Status excluding True Change alarm status

Element symbol.ALRM.
NR False Release alarm status

Alarm Status excluding True Release detection of specified alarm

Element symbol.AF.
NR False Perform detection of specified alarm

Alarm Status excluding True Perform suppression of specified alarm

Element symbol.AOFS.
NR, AOF (*1) False Release suppression of specified alarm
True Perform group verification of alarms
Element symbol.AFLS. AFL
False Disable
Process number setting
True
Element symbol.SV. 1 to 99 (Only Valid with BSI Block)
False Disable
True Control command setting
Element symbol.PV01 to 10. 0,1
False Disable

Element symbol.SWCR [1 to n]. True Change color of switch display

0 to 15
(*2) False Disable

Element symbol.SWST [1 to n]. True ON/OFF of switch flashing status

0,1
(*2) False Disable

Element symbol.SWOP [1 to n]. True Changing of switch control disable status

-15 to 15
(*2) False Disable
D030380E.ai

*1: The AOF specification is valid only with respect to the change in the alarm suppression specification. This operation performs
alarm suppression for all alarms with the exception of the NR alarm.
*2: n indicates the number of elements in a one-dimensional array. This is the number of push-button switches in a faceplate block,
and varies with the type of each faceplate block.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-154

n Status Manipulation of SFC Block

The syntax for applying the various functions of an SFC block as status manipulation signal in a
logic chart and the actions corresponding to True/False are shown as follows.
Table Syntax for Action Signal Description and Actions Corresponding to True/False
Manipulation signal description
True/False Manipulation description
Output signal Action Specifications
True Block mode change command
Element symbol.MODE. MAN, AUT
False Disable

RUN, PAUS True Block status change command

Element symbol.BSTS.
ATOP, ABRT False Disable

Alarm Status excluding True Release detection of specified alarm

Element symbol.AF.
NR False Perform detection of specified alarm

Alarm Status excluding True Perform suppression of specified alarm

Element symbol.AOFS.
NR, AOF (*1) False Release suppression of specified alarm
True Perform group verification of alarms
Element symbol.AFLS. AFL
False Disable
True Data setting
Element symbol.Data Item. Data Value
False Disable
True Set PV data status to CAL
Element symbol.PV= CAL
False release the CAL data status of PV
True Switch to CAL or release CAL
Element symbol.PV. =XCAL (*2)
False –
D030381E.ai

*1: The AOF specification is valid only with respect to the change in the alarm suppression specification. This operation performs
alarm suppression for all alarms with the exception of the NR alarm.
*2: The type of logic chart that =XCAL is applied should be set to [One-Shot Processing Type (O)].

l Range of Data Value When Manipulating the Data Items

The ranges of data values when manipulating the SFC data items in a logic chart for status
manipulation are shown as follows.
• STEPNO: 1 to 99
• SWCR[5]: 0 to 15
• SWST[5]: 0, 1
• SWOP[5]: -15 to 15

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-155

n Status Manipulation of Unit Instrument

The syntax for applying the various functions of a unit instrument block as status manipulation
signal in a logic chart and the actions corresponding to True/False are shown as follows.
Table Syntax for Action Signal Description and Actions Corresponding to True/False
Manipulation signal description
True/False Manipulation description
Output signal Action Specifications
True Unit mode change command
Element symbol.MODE. MAN, SEMI, AUT
False Disable

Unit status change True Unit status change command

Element symbol.UBSC.
command name False Disable

Alarm status excluding True Release detection of specified alarm

Element symbol.AF.
NR False Perform detection of specified alarm

Alarm status excluding True Perform suppression of specified alarm

Element symbol.AOFS.
NR, AOF (*1) False Release suppression of specified alarm
True Perform group verification of alarms
Element symbol.AFLS. AFL
False Disable
True Change SFC step number
Element symbol.STEPNO. 1 to 99
False Disable
D030382E.ai

*1: The AOF specification is valid only with respect to the change in the alarm suppression specification. This operation performs
alarm suppression for all alarms with the exception of the NR alarm.

n Status Manipulation of Process I/O

The syntax for applying the various functions of a process I/O as status manipulation signal in a
logic chart and the actions corresponding to True/False are shown as follows.
Table Syntax for Action Signal Description and Actions Corresponding to True/False
Manipulation signal description
True/False Manipulation description
Output signal Action Specifications
True Contact output ON (nonlatched)
L
False Contact output OFF
Element symbol.PV.
True Cause flashing state
F
False Stop the flashing state (*1)
D030383E.ai

*1: Even though the flashing state stops, the contact output itself remains ON. Turn off the contact output using a different action
signal with an unlatched contact output.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-156

n Status Manipulation of Global Switch

The syntax for applying the various functions of a global switch as status manipulation signal in a
logic chart and the actions corresponding to True/False are shown as follows.
The status manipulation can be only applied to the global switches assigned in the same control
station of the logic chart.
Table Syntax for Action Signal Description and Actions Corresponding to True/False
Manipulation signal description
True/False Manipulation description
Output signal Action Specifications
True Turn ON specified global switch. (Nonlatched)
Element symbol.PV. L
False Turn OFF specified global switch.
D030384E.ai

n Status Manipulation of Common Switch

The syntax for applying the various functions of a common switch as status manipulation signal
in a logic chart and the actions corresponding to True/False are shown as follows.
Table Syntax for Action Signal Description and Actions Corresponding to True/False
Manipulation signal description
True/False Manipulation description
Output signal Action Specifications
True Common switch output ON (nonlatched)
Element symbol.PV. L
False Common switch output OFF
D030385E.ai

n Status Manipulation of Annunciator Message

The syntax for applying the various functions of an annunciator message as status manipulation
signal in a logic chart and the actions corresponding to True/False are shown as follows.
Table Syntax for Action Signal Description and Actions Corresponding to True/False
Manipulation signal description
True/False Manipulation description
Output signal Action Specifications
True Annunciator output ON (nonlatched)
Element symbol.PV. L
False Annunciator output OFF
Repeated warning specification
True
Element symbol.RP. ON, OFF (ON: Repeated warning, OFF: Release)
False Disable
True Perform suppression of specified alarm
Element symbol.AOFS. AOF
False Release suppression of specified alarm
True Perform group verification of alarms
Element symbol.AFLS. AFL
False Disable
D030386E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-157

n Status Manipulation of Sequence Message Output

The syntax for applying the various functions of a Sequence Message Output as status
manipulation signal in a logic chart and the actions corresponding to True/False are shown as
follows.
The following types of sequence message output are supported:
• Print message output
• Operator guide message output
• Multimedia function message output
• Sequence message request
• PICOT supervisory computer event message output
• Event message output for supervisory computer
• Signal event message output
• SFC/SEBOL return event message output
Table Syntax for Action Signal Description and Actions Corresponding to True/False
Manipulation signal description
True/False Manipulation description
Output signal Action Specifications
True Message output without parameter
NON
False Disable
Element symbol.PV.
True Message output with parameter
mm (*1)
False Disable
D030387E.ai

*1: mm can specify integer data (2-byte long integer data).

Range: -32768 to 32767

n Status Manipulation of Communication I/O

The syntax for applying the various functions of a communication I/O as status manipulation
signal in a logic chart and the actions corresponding to True/False are shown as follows.
Table Syntax for Action Signal Description and Actions Corresponding to True/False
Manipulation signal description
True/False Manipulation description
Output signal Action specification
True The bit turns ON (nonlatched)
Element symbol.PV. L
False The bit turns OFF
D030388E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-158

D3.3.11 Syntax for Action Signal Description: Status

Manipulation of Logic Chart
Logic chart status manipulation can change the block mode of a logic chart, it can also
start a logic chart for one-shot execution.

n Logic Chart One-Shot Execution

The following scripts can be used to define an output signal element to start a logic chart one-
shot execution.
Table Syntax for Action Signal Description and Actions Corresponding to True/False
Manipulation signal description
True/False Action
Output signal Action Specifications
True Execute logic chart
Element symbol.ACT. ON
False Disable
D030389E.ai

• When action signal specified to start an one-shot execution of a function block, the target
block can start another block for one-shot execution. The chain start can be nested seven
times.
• When output to the one-shot function block fails, and the failure is caused by one of the
following reasons, a system alarm will be triggered.
• The destination logic chart is used to start another logic chart, and the chain start is nested
more than seven times.
• The function block connected to the output terminal is in O/S mode.
• The function block connected to the output terminal is udder online maintenance.

n Logic Chart Block Mode Change

The block mode of a logic chart can be changed. Changing the block mode of the logic chart can
manipulate the logic block to pause the execution (MAN mode) or to restart the execution (AUT
mode).
The following scripts can be used to define an output signal element to change block mode of a
logic chart block.
Table Syntax for Action Signal Description and Actions Corresponding to True/False
Manipulation signal description
True/False Manipulation description
Output signal Action Specifications
True Change the block’s mode
Element symbol.MODE. AUT, MAN, O/S
False Disable
D030390E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-159

D3.3.12 Syntax for Action Signal Description: Status

Manipulation of Sequence Table from Logic Chart
The status manipulation to sequence table blocks can not only change the data or data
status in the sequence table, but also can start a sequence table and control the whole
processing of the sequence table from the condition test to status manipulation output.
When manipulating or referencing a sequence table whose number of rules is extended
over multiple sequence tables, the tag name of the base sequence table needs to be
specified.
The following types of status manipulation may be applied to sequence tables.
• Referencing an entire sequence table
• Executing a particular sequence table step
• Setting a execution label to a sequence table step
• Changing a sequence table block mode

n Executing an Entire Sequence Table

A sequence table defined to an output operation element in a logic chart (transition destination
sequence table) can be started for a one-shot execution.
When the transition destination sequence table is not a step type sequence table, the entire
sequence table will be executed.
When the transition destination sequence table is a step type sequence table, the step
corresponding to the transition process in the sequence table will be executed.
From the transition sequence table, another sequence table can be started as a transition table
for condition test or status manipulation. The chain start can be nested for 7 times including the
first sequence table.
Table Syntax for Action Signal Description and Actions Corresponding to True/False
Manipulation signal description
True/False Manipulation description
Output signal Action Specifications
True Execute the specified table
Element symbol.ACT. ON
False Disable
D030391E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-160

n Executing a Particular Step in a Sequence Table

The syntax for executing a particular sequence table step in a logic chart and the actions
corresponding to True/False are shown as follows.
Table Syntax for Action Signal Description and Actions Corresponding to True/False
Manipulation signal description column
Action True/False Manipulation description
Output signal
specification
Branch to step xx in the specified table and
True
Element symbol.SA. xx execute steps xx and 00.
False Disable
D030392E.ai

xx: Specify a step label with up to two alphanumeric characters.

From the transition sequence table, another sequence table can be started as a transition table
for condition test or status manipulation. The chain start can be nested for 7 times including the
first sequence table.

The action rule of the sequence table behaves as follows according to the types (step type or
nonstep type) of the execution origin and the execution destination sequence tables.
Table Execution Target Action Rule in Accordance with Types of Sequence Table
Branching source Branching destination Execution target action rule
Nonstep type Rules for a specified step and step 00
Nonstep type
Step type All rules
Nonstep type Rules for a specified step and step 00
Step type
Step type All rules
D030393E.ai

When a logic chart starts a sequence table specified in the output operation element, the started
sequence table run its transition to start the transition destination sequence table. The transition
destination sequence table will run its step 00 and the transition specified step for condition test
and the status manipulation.
If the specified transition step of the transition sequence table can not be found, an error will be
generated, the step can not be executed. However, if the transition sequence table has step 00,
the step 00 will be executed.
When execute an entire sequence table to a non step type sequence table, all rules will be
executed.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-161

n Setting an Execution Label to a Step in a Sequence Table

An execution label can be set to a sequence table step, this action is different from the executing
a particular sequence table step, it only set the execution label to a specified sequence table step
but does not execute the step. The set step will be executed first when the sequence table is
started the next time.
The syntax for setting an execution label to a sequence table step as the action signal in a logic
chart and the actions corresponding to True/False are shown as follows.
Table Syntax for Action Signal Description and Actions Corresponding to True/False
Action signal description column
Action True/False Manipulation description
Output signal
specification
True Set execution label to step xx
Element symbol.PV. xx
False Disable
D030394E.ai

xx: Specify a step label with up to two alphanumeric characters.

n Changing Sequence Table Block Mode

The block mode of a sequence can be changed from a logic chart. Changing the block mode of a
sequence table block can manipulate the sequence table to pause the execution (MAN mode) or
to restart the execution (AUT mode).
When a sequence table is paused by changing to MAN mode, the state of the sequence table will
be kept.
The syntax for changing a sequence table block mode as an action signal in a logic chart and the
actions corresponding to True/False are shown as follows.
Table Syntax for Action Signal Description and Actions Corresponding to True/False
Manipulation signal description column
Action True/False Manipulation description
Output signal
specification
True Change the block’s mode
Element symbol.MODE. AUT, MAN, O/S
False Disable
D030395E.ai

n Pause and Restart a Sequence Table

Some sequence tables are running in a fixed scan cycle while some others are staring, pausing
or restarting in accordance with process procedures. To pause a running sequence table, and to
restart a paused sequence table is possible. The scripts may be described in a sequence table
for a sequence table’s Pause and Restart are shown as follows.
Table Syntax for Output Signal Scripts and Action Description
Manipulation signal description column
Action True/False Manipulation description
Output signal
specification
True Starts or restarts sequence table
Element symbol.XS. ON
False Pause Sequence table
D030399E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-162

D3.3.13 Behavior of Logic Chart Internal Timer

Logic chart block has an internal timer to control the processes of itself.

n Behavior of Internal Timer

The process timer of a logic chart is used to execute the on-delay timer and the off-delay timer.
The timer starts when the logic chart itself changes to AUT mode.

Setting range: 0 - 10000 (sec.)

Table Timer Specification
Number of timers Total number of logic operators (64)
Mode and status The timer itself has neither a mode nor status.
Pause Not supported
When PT = 0 or the input signal changes
Start condition
(on-delay timer 0 to 1; off-delay timer 1 to 0)
Start action 0 start
1. The input signal inverses from the start status
Stop condition 2. Block changes to MAN mode
3. Timer count up (PT ≥ ST)
Stopped by stop condition 1, the elapsed time reset.
Stop Action
Stopped by stop condition 2 or 3, the elapsed time is kept.
Timer set value (ST) Set on HIS ( 0 - 10000 sec.)
D030396E.ai

On-delay timer behaves as illustrated below.

ST

PT

MODE AUT MAN AUT

IN 0 1 0 1 0 1
OUT 0 1 0

PT: Elapsed time of internal timer ( 0 to 10000 sec.)

ST: Set time of internal timer ( 0 to 10000 sec.)
D030397E.ai

Figure Behavior of on-delay timer

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.3 Logic Chart Block (LC64)> D3-163

D3.3.14 Data Items of Logic Chart Block - LC64

The table below shows the data items of the Logic Chart Block (LC64):

n Data Items
Table Data Items of the logic Chart Block (ST-16)
Entry parnitted
Data Item Data Name Range Default
or Not
MODE Block mode x O/S (AUT)
ALRM Alarm status NR
Alarm flashing status
AFLS 0

AF Alarm detection 0
AOFS Alarm inhibition 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x 0
ST01 - 64 Set time of internal timer x 0 to10000 (sec.) 0 (sec.)
PT01 - 64 Elapsed time of internal timer 0 to10000 (sec.) 0 (sec.)
D030398E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted

SEE
ALSO For a list of valid block mode of the LC64, see the following:
D3.1.2, “Block Mode of Sequence Control Blocks”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D3.4 Switch Instrument Block and Enhanced Switch Instrument Block> D3-164

D3.4 Switch Instrument Block and Enhanced

Switch Instrument Block
The switch instrument blocks are used to start, stop, monitor and manipulate the status of
various types of instruments.

n Switch Instrument Block and Enhanced Switch Instrument Block

The switch instrument block is a function block which is often used to start/stop motors and
pumps and monitor or manipulate open-close state of the motor-operated valves. In most cases,
this type of blocks is used in combination with the sequence table block (ST16, ST16E) and the
Logic Chart Block (LC64).
Enhanced switch instrument block (*1) is a switch instrument block with enhanced capabilities
for connecting to FF faceplate blocks and fieldbus function blocks and for connecting to the I/O
terminals not next to each other.
*1: Enhanced switch instrument block can be applied to all Field control stations except standard PFCS. When using enhanced
switch instrument block, it is necessary to add the option [DIOENH] on the [Constant] tab of the FCS properties sheet.

l Switch Instrument Block

▼ Connection

A function block chart of the switch instrument block is shown below.

Answerback Remote Sequence

SWI output value setpoint
bypass
BPSW=0
RMV CSV
INT BPSW=1

Answerback MAN
PV
check
ROUT CAS, AUT

CAL MV
BPSW=0 BPSW=1

Answerback
input
Remote/local Output signal
input conversion

RAW

IN TSI OUT
D030401E.ai

Figure Function Block Chart of the Switch Instrument Block

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.4 Switch Instrument Block and Enhanced Switch Instrument Block> D3-165
There exist 10 different types of switch instrument blocks according to the difference between the
answerback input points and output points.
A list of switch instrument blocks is shown as follows.
• SI-1: Switch instrument block with 1 Input
• SI-2: Switch Instrument Block with 2 Inputs
• SO-1: Switch Instrument Block with 1 Output
• SO-2: Switch instrument block with 2 Outputs
• SIO-11: Switch Instrument Block with 1 Input, 1 Output
• SIO-12: Switch Instrument Block with 1 Input, 2 Outputs
• SIO-21: Switch Instrument Block with 2 Inputs, 1 Output
• SIO-22: Switch Instrument Block with 2 Inputs, 2 Outputs
• SIO-12P: Switch Instrument Block with 1 Input, 2 One-Shot Outputs
• SIO-22P: Switch Instrument Block with 2 Inputs, 2 One-Shot Outputs

The table below shows the connection methods and connection destinations of the switch
instrument block I/O terminals.
Table Connection Method and Connection Destination of Switch Instrument Block I/O Terminals
Connection type Connection destination

Code I/O terminal Status Terminal

Data Data Condition Process Software Function
manipul- connecti-
reference setting testing I/O I/O block
ation on
SI-1 Answerback Δ x x
IN x
SI-2 I/O terminal
Remote/local
TSI x Δ x x x
I/O terminal
Output
SO-1 OUT x Δ x x
terminal
SO-2
Interlock
INT switch input x Δ x x x
terminal
Answerback Δ
IN x x x
input terminal
Remote/local Δ
TSI x x x x
I/O terminal
SIO-11
SIO-12 Answerback
SIO-21 SWI bypass input x Δ x x
SIO-22 terminal
SIO-12P
Output
SIO-22P OUT x Δ x x
terminal
Interlock
INT switch input x Δ x x x
terminal
D030402E.ai

x: Connection available
Blank: Connection not available
Δ: Connection is available only when connecting to a switch block (SW-33, SW-91).

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.4 Switch Instrument Block and Enhanced Switch Instrument Block> D3-166
l Enhanced Switch Instrument Block
▼ Connection
A function block chart of the enhanced switch instrument block (*1) is shown below.
*1: Enhanced switch instrument block can be applied to all Field control stations except standard PFCS. When using enhanced
switch instrument block, it is necessary to add the option [DIOENH] on the [Constant] tab of the FCS properties sheet.

Answerback Remote Sequence

SWI output value setpoint
bypass
BPSW=0
RMV CSV
INT BPSW=1

Answerback MAN
PV
check
ROUT CAS, AUT

CAL MV
BPSW=0 BPSW=1

Answerback
input
Remote/local Output signal
input conversion

RAW

IN/ IN2 TSI OUT/ OUT2

IN1 OUT1
D030420E.ai

Figure Function Block Chart of the Enhanced Switch Instrument Block

A list of enhanced switch instrument blocks is shown as follows.

• SI-1E: Enhanced Switch Instrument Block with 1 Input
• SI-2E: Enhanced Switch Instrument Block with 2 Inputs
• SO-1E: Enhanced Switch Instrument Block with 1 Output
• SO-2E: Enhanced Switch Instrument Block with 2 Outputs
• SIO-11E: Enhanced Switch Instrument Block with 1 Input, 1 Output
• SIO-12E: Enhanced Switch Instrument Block with 1 Input, 2 Outputs
• SIO-21E: Enhanced Switch Instrument Block with 2 Inputs, 1 Output
• SIO-22E: Enhanced Switch Instrument Block with 2 Inputs, 2 Outputs
• SIO-12PE: Enhanced Switch Instrument Block with 1 Input, 2 One-Shot Outputs
• SIO-22PE: Enhanced Switch Instrument Block with 2 Inputs, 2 One-Shot Outputs

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.4 Switch Instrument Block and Enhanced Switch Instrument Block> D3-167
The table below shows the connection methods and connection destinations of the enhanced
switch instrument block I/O terminals.
Table Connection Method and Connection Destination of Enhanced Switch Instrument Block I/O
Terminls
Connection type Connection destination

Code I/O terminal Status Terminal

Data Data Condition Process Software Function
manipul- connecti-
reference setting testing I/O I/O block
ation on
IN/IN1 Answerback Δ x x x
x
SI-1E (*1) I/O terminal 1
SI-2E IN2 Answerback
x Δ x x x
(*2) I/O terminal 2
Remote/local
TSI x Δ x x x
I/O terminal
OUT/ Output
x x x x x
OUT1(*3) terminal 1
SO-1E
SO-2E OUT2 Output
x x x x x
(*4) terminal 2
Interlock
INT switch input x Δ x x x
terminal
IN/IN1 Answerback Δ
x x x x
(*5) input terminal 1
IN2 Answerback Δ
x x x x
(*6) input terminal 2
Remote/local Δ
SIO-11E TSI x x x x
I/O terminal
SIO-12E
SIO-21E Answerback
SIO-22E SWI bypass input x Δ x x
SIO- terminal
12PE
OUT/ Output
SIO- x x x x x
OUT1(*7) terminal 1
22PE
OUT2 Output
x x x x x
(*8) terminal 2
Interlock
INT switch input x Δ x x x
terminal
D030421E.ai

x: Connection available
Blank: Connection not available
Δ: Connection is available only when connecting to a switch block (SW-33, SW-91).
*1: IN terminal of SI-1E. IN1 terminal of SI-2E.
*2: IN2 terminal of SI-2E.
*3: OUT terminal of SO-1E. OUT1 terminal of SO-2E.
*4: OUT2 terminal of SO-2E.
*5: IN terminal of the blocks with only one input. IN1 terminal of the blocks with two inputs.
*6: IN2 terminal of the blocks with two inputs.
*7: OUT terminal of the blocks with only one output. OUT1 terminal of the blocks with two outputs.
*8: OUT1 terminal of the blocks with two outputs.

IMPORTANT
If the OUT1 terminal and the OUT2 terminal are connected to different output modules or if OUT1
terminal and the OUT2 terminal are connected to FF faceplate blocks or fieldbus function blocks,
the simultaneity of the two outputs are not guaranteed. The same phenomenon happens to IN1
and IN2 terminals under the same circumstances.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.4 Switch Instrument Block and Enhanced Switch Instrument Block> D3-168

n Example of Using Switch Instrument Block

An outline of the function manipulating the motor-operated valve is explained in the switch
instrument block (SIO-22P) faceplate shown below.

TAG NO.

AUT

Push OPEN

Push

CLOSE

SEQTYPE1
*VALVE*

1 to 2 sec
Open-
output 1 to 2 sec
OPEN
Output
Close-output CLOSE

Valve
limit
switch

Motor-operated valve
D030403E.ai

Figure Functional Schematic Diagram of Switch Instrument Block (SIO-22P)

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.4 Switch Instrument Block and Enhanced Switch Instrument Block> D3-169

n Process Timing
The process timing of switch instrument block and enhanced switch instrument block is only
based on periodical start period. The periodic start period is based on basic scan period.

n List of Switch Instrument Block Functions

The switch instrument block function varies by the type of the block. The table below lists major
functions of switch instrument blocks.
Table List of Switch Instrument Block Functions by Block Type (1/2)
Code
SI-1 SI-2 SO-1 SO-2 SIO-11
Function
Number of answerback points 1 2 1
Number of output points 1 2 1
Block mode x x x x x
Block status x x x x x
Alarm status x x x x x
Answerback input x x x
Answerback inconsistency alarm check x
Remote/local input x x x
Answerback check x
Output signal conversion x x x
Answerback bypass x
Answerback tracking x
Calibration x x x
Mode change interlock x x x
Initialization manual mode x x x
Manual mode fallback x x x x x
Simulation x x x x x
D030422E.ai

x: Yes
Blank: No

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.4 Switch Instrument Block and Enhanced Switch Instrument Block> D3-170
Table List of Switch Instrument Block Functions by Block Type (2/2)
Code
SIO-12 SIO-21 SIO-22 SIO-12P SIO-22P
Function
Number of answerback points 1 2 2 1 2
Number of output points 2 1 2 2 2
Block mode x x x x x
Block status x x x x x
Alarm status x x x x x
Answerback input x x x x x
Answerback inconsistency alarm check x x x
Remote/local input x x x x x
Answerback check x x x x x
Output signal conversion x x x x x
Answerback bypass x x x x x
Answerback tracking x x x x x
Calibration x x x x x
Mode change interlock x x x x x
Initialization manual mode x x x x x
Manual mode fallback x x x x x
Simulation x x x x x
D030405E.ai

x: Yes
Blank: No

SEE
ALSO • For the types of alarm processing possible for the switch instrument blocks, see the following:
D3.1.1, “Alarm Processing of Sequence Control Blocks”
• For more information about alarm processing, see the following:
C5, “Alarm Processing – FCS”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.4 Switch Instrument Block and Enhanced Switch Instrument Block> D3-171

n List of Enhanced Switch Instrument Block Functions

The enhanced switch instrument block function varies by the type of the block. The table below
lists major functions of enhanced switch instrument blocks.
Table List of Enhanced Switch Instrument Block Functions by Block Type (1/2)
Code
SI-1E SI-2E SO-1E SO-2E SIO-11E
Function
Number of answerback points 1 2 1
Number of output points 1 2 1
Block mode x x x x x
Block status x x x x x
Alarm status x x x x x
Answerback input x x x
Answerback inconsistency alarm check x
Answerback inconsistency alarm mask
Remote/local input x x x
Answerback check x
Output signal conversion x x x
Output tracking x x x
Answerback bypass x
Answerback tracking x
Calibration x x x
Mode change interlock x x x
Initialization manual mode x x x
Manual mode fallback x x x x x
Simulation x x x x x
D030404E.ai

x: Yes
Blank: No

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.4 Switch Instrument Block and Enhanced Switch Instrument Block> D3-172
Table List of Enhanced Switch Instrument Block Functions by Block Type (2/2)
Code
SIO-12E SIO-21E SIO-22E SIO-12PE SIO-22PE
Function
Number of answerback points 1 2 2 1 2
Number of output points 2 1 2 2 2
Block mode x x x x x
Block status x x x x x
Alarm status x x x x x
Answerback input x x x x x
Answerback inconsistency alarm check x x x
Answerback inconsistency alarm mask x x x
Remote/local input x x x x x
Answerback check x x x x x
Output signal conversion x x x x x
Output Tracking x x x x x
Answerback bypass x x x x x
Answerback tracking x x x x x
Calibration x x x x x
Mode change interlock x x x x x
Initialization manual mode x x x x x
Manual mode fallback x x x x x
Simulation x x x x x
D030423E.ai

x: Yes
Blank: No

SEE
ALSO • For the types of alarm processing possible for the enhanced switch instrument blocks, see the following:
D3.1.1, “Alarm Processing of Sequence Control Blocks”
• For more information about alarm processing, see the following:
C5, “Alarm Processing – FCS”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.4 Switch Instrument Block and Enhanced Switch Instrument Block> D3-173

n Answerback Input
▼ Direction of Answerback
In answerback input function, the limit switch signal indicating the valve’s open/close status
is entered from the answerback input terminal to generate the answerback input value (PV).
Contact input and internal status switch can be specified as the answerback signal input for the
switch instrument blocks. For enhanced switch instrument blocks, the contact input, internal
switch, FF faceplate block and fieldbus function block can be specified as the answerback signal
input. The answerback input signal is converted into the answerback input value (PV) inside the
switch instrument. This answerback input value varies depending upon the answerback input
direction and the input status of the valve limit switch. The table below lists the answerback input
values.
Table List of Answerback Input Value

Number of Valve limit (*1)

Action of switch status
answerback Answerback input value (PV)
answerback
point n n+1
ON - 2
Direct
OFF - 0
1
ON - 0
Reverse
OFF - 2
ON OFF 2
OFF OFF 1
Direct
OFF ON 0
ON ON Hold previous PV value (*2)
ON OFF 0
OFF OFF Hold previous PV value (*2)
Reverse
OFF ON 2
ON ON 1
2
OFF ON 2
Inverted connection OFF OFF 1
direct action
(*3) ON OFF 0
ON ON Hold previous value (*2)
OFF ON 0
Inverted connection OFF OFF Hold previous value (*2)
reversed action
(*3) ON OFF 2
ON ON 1
D030406E.ai

*1: “n” in the table indicates the element number specified to connect to IN terminal of switch instrument blocks and enhanced switch
instrument blocks, or the IN1 terminal of enhanced switch instrument blocks. The answerback input signal read from the element
n represents the status of “open;” vise versa, when the connection is inverted, the answerback input signal read from the element
n represents the status of “close.”
“n+1” in the table indicates the element number succeeding the element number “n” that is specified to connect to IN terminal of
switch instrument blocks, or the element number specified to connect to IN2 terminal of enhanced switch instrument blocks. The
answerback input signal read from the element n+1 represents the status of “close;” vise versa, when the connection is inverted,
the answerback input signal read from the element n+1 represents the status of “open.”
*2: This is an abnormal event in which input from full-open signal and full-close signal occurs simultaneously. The answerback
inconsistency alarm (PERR) occurs.
*3: Inverted connection cannot be defined for enhanced switch instrument block.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.4 Switch Instrument Block and Enhanced Switch Instrument Block> D3-174
The answerback input direction is specified in the Function Block Detail Builder.
• Direction of Answerback:
Switch Instrument Block:
Select from [Direct], [Reverse], [Inverted connect direct action], or [Inverted connect
reversed action].
Enhanced switch instrument block:
Select from [Direct] or [Reverse].
Default is [Direct].

l Data Status Accompanied by Alarms

If a full-open signal and a full-close signal are input simultaneously, or at least one of the input
destinations of the input target element is abnormal, the data status of the answerback input
value (PV) becomes invalid (BAD).
If the data status of the answerback input value becomes invalid (BAD), the input open alarm
(IOP) will occur.
If the invalid data value is caused by the simultaneous input of full-open and full-close signals, the
answerback inconsistency alarm (PERR) will occur.
The status of answerback signal will be stored in the answerback raw signal (RAW), besides the
answerback input value (PV). Even if the answerback input function fails, the answerback raw
data (RAW) will follow the actual answerback signal.

l Conditions under Which Answerback Input Function Fails

The answerback input function fails under the following conditions:
• Simulation state (SIMM=1)
• Calibrating (PV.CAL=1)
• During answerback bypass (BPSW=1)

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.4 Switch Instrument Block and Enhanced Switch Instrument Block> D3-175

n Actions of Answer-Back Inconsistency Alarm Check

The answerback inconsistency alarm check is a function that determines whether two
answerback input signals indicate full-open and full-close simultaneously in the switch instrument
blocks (SI-2, SIO-21, SIO-22, or SIO-22P) and the enhanced switch instrument block (SI-2E,
SIO-21E, SIO-22E or SIO-22PE).
If it is determined that two answerback input signals indicated full-open and full-close
simultaneously, an answerback inconsistency alarm (PERR) occurs.
If the two answer-back input signals stop indicating full-open and full-close simultaneously while
the alarm is being generated, the alarm is returned to normal state.

l Answer-Back Inconsistency Alarm Mask

▼ Inhibit Answerback Error Alarm
When IN1 terminal and the IN2 terminal of an enhanced switch block are connected to FF
faceplate blocks or fieldbus function blocks, the simultaneity of the two inputs is not guaranteed.
If the both the ON and OFF answerbacks exist at the same time even for a very short time, the
Answer-Back Inconsistency Alarm (PERR) may occur. To prevent the alarm occurring under this
circumstance, the alarm can be masked by stop the alarm check for a certain time period (Mask
Time) after the manipulated output (MV) changes. The data item MTM can be used for setting
this answer-back inconsistency alarm mask time.

For enhanced switch instrument block, the answer-back inconsistency alarm mask can be set on
the function block detail builder.
• Inhibit Answerback Error Alarm:
Choose between [No] and [Yes].
The default setting is [Yes].

TIP
SI-2E block has the Answer-Back Inconsistency Alarm check capability but cannot be masked. If the alarm need
to be masked, it is necessary to use an application program such as a sequence table block to enable or disable
the alarm check after the MV changes.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.4 Switch Instrument Block and Enhanced Switch Instrument Block> D3-176

n Remote/Local Input
The remote/local input function switches the block mode depending on the status of the on-site
operation push-button (remote/local input signal) input from the remote/local input terminal (TSI).
For remote/local signals, the contact input and common switch can be specified. The state of
remote/local input signal is stored in the tracking switch (TSW). The block mode will be changed
depending on the state of tracking switch (TSW).
Table Remote/Local Input of the Switch Instrument Block and the Enhanced Switch Instrument Block
On-site operation remote/ Input signal to TSI Tracking switch
Block mode
local switching input terminal (TSW)
Remote OFF 0 Cancel TRK
Local ON 1 TRK
D030407E.ai

If there exists no connection for the remote/local input terminal (TSI), the block mode external to
the block function can set the tracking switch (TSW) directly.
The following is an example of description to the sequence table action signal column for setting
the switch instrument (Tag name=SU0100) tracking switch (TSW) to 1.
Tag name.Data item Data Action rule
SU0100.TSW 1 Y
D030408E.ai

The cprresponding logic chart is shown below:

Data connection
SU0100.TSW.1
OR
SIO-21
DI010 Q01 DI010.PV.ON
SU0100.TSW.1 OUT TSW
DI011 Q02 DI011.PV.ON

Switch instrument
(Tag No.=SU0100)
D030418E.ai

Figure Example of a Logic Chart

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.4 Switch Instrument Block and Enhanced Switch Instrument Block> D3-177

n Answerback Check
▼ Answerback Check, Answerback Abnormal Alarm
The answerback check function checks if final control elements such as a valve is working as
specified by the output from the switch instrument block or the enhanced switch instrument block.
If there exists answerback check specification, operations are checked by comparing the
answerback input value (PV) and manipulated output value (MV) regularly, except for a certain
period after a change in the output. If there is any inconsistency between the answerback input
value (PV) and the manipulated output value (MV), the answerback error alarm (ANS+ or ANS-)
will occur.

l Conditions for Answerback Error Alarm Occurrence

Answerback error alarm occurs under the following conditions:
• Open-side answerback error alarm (ANS+):
MV=2 and PV≠2
• Close-side answerback error alarm (ANS-):
MV=0 and PV≠0

Presence/absence of the answerback error alarm can be specified in the Function Block Detail
Builder.
• Answerback Abnormal Alarm
Select from “Close,” “OFF Direction,” “Both” or “No.”
The default is “Both.”

l Conditions for Recovery from Answerback Error Alarm

Recovery from the answerback error alarm is possible under the following conditions.
• Open-side answerback error alarm (ANS+)
When PV changes to PV=2, or MV changes to MV≠2
• Close-side answerback error alarm (ANS-)
When PV changes to PV=0, or MV changes to MV≠0

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.4 Switch Instrument Block and Enhanced Switch Instrument Block> D3-178
l Answerback Check Suppression Timer
It takes a certain length of time from changing the manipulated output value (MV) to completing
the final control element operation. Consequently, when there is a change in manipulated
output value, even if there is any inconsistency between the answerback input value (PV) and
the manipulated output value (MV), the alarm will not be activated for a certain length of time
(answerback check suppression time: MTM) after the change. If the manipulated output value
(MV) is changed, the block status will become answerback check inhibition (ANCK), starting the
answerback check suppression timer.
If there is any inconsistency between the answerback input value (PV) and the manipulated
output value during the period between the time-up of answerback check suppression timer and
the next change in the manipulated output value (MV), the answerback error alarm (ANS±) will
be activated.
The answerback check inhibition (ANCK) will be canceled when there is an inconsistency
between the answerback input value (PV) and the manipulated output value (MV), or when the
answerback check suppression timer expires.
Elapsed time of the answerback check suppression timer (PTM) indicates the time elapsed after
activating the answerback check suppression timer. When there is an inconsistency between the
answerback input value (PV) and the manipulated output value (MV) or when the answerback
check suppression timer expires, the answerback check suppression timer will stop counting,
retaining the count value.
The operation range of the answerback check suppression time (MTM) is from 0 to 10,000 seconds.

l Answerback Check Monitoring

The answerback check monitoring is specified in the Function Block Detail Builder.
• Answerback Check:
Choose [Both sides], [Open], [Close], or [No].
The default is [Both sides].

When either “Open” or “Close” is specified, answerback check will not be performed even if there
is any inconsistency on the side not specified. On the other hand, if monitoring both sides is
specified, the alarm will be activated when an inconsistency is detected on either side. The alarm
will be canceled when both sides satisfy their recovery conditions.

l Monitoring Both Sides

The answerback check time will be activated upon rising and falling of the output. If there exists
any inconsistency between the answerback input value (PV) and the manipulated output value
during the period between the time-up of answerback check suppression timer and the next
change in the manipulated output value (MV), the answerback error alarm (ANS+) or close-side
answerback error alarm (ANS-) will be activated.
MV=2
Manipulated output
MV=0
PV=2
Answerback input
PV=0
MTM
Answerback check
suppression timer
0

Alarm status NR ANS+ NR ANS- NR

AN AN
Block status NR CK NR CK NR ANCK NR ANCK NR
D030409E.ai

Figure Operation Diagram of Both-Side Monitoring

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.4 Switch Instrument Block and Enhanced Switch Instrument Block> D3-179
l Monitoring Open-Side
The answerback check time will be activated upon rising (OFF→ON) (MV=0→2) of the
manipulated output. If there exists any inconsistency between the answerback input value (PV)
and the manipulated output value during the period between the time-up of answerback check
suppression timer and the next change of the manipulated output value (MV) to 0, the open-side
answerback error alarm (ANS+) will be activated.
MV=2
Manipulated output
MV=0
PV=2
Answerback input
PV=0
MTM
Answerback check
suppression timer
0

Alarm status NR ANS+ NR

Block status NR ANCK NR ANCK NR
D030410E.ai

Figure Operation Diagram of Open-Side Monitoring

l Monitoring Close-Side
The answerback check time will be activated upon falling (ON→OFF) (MV=2→0) of the
manipulated output. If there exists any inconsistency between the answerback input value (PV)
and the manipulated output value during the period between the time-up of answerback check
suppression timer and the next change of the manipulated output value (MV) to 2, the close-side
answerback error alarm (ANS-) will be activated.
MV=2
Manipulated output
MV=0
PV=2
Answerback input
PV=0
MTM
Answerback check
suppression timer
0

Alarm status NR ANS- NR

Block status NR ANCK NR ANCK NR
D030411E.ai

Figure Operation Diagram of Close-Side Monitoring

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.4 Switch Instrument Block and Enhanced Switch Instrument Block> D3-180
l Conditions under Which Answerback Check Function Fails
Answerback check function fails under the following conditions:
• Simulation state (SIMM): SIMM=1
• On-site manual operation mode (TRK): TSW=1
• During answerback bypass: BPSW=1
• MV=1
• Calibrating (PV.CAL=1)
• Input data error
• Initialization manual mode (IMAN)

n Answerback Bypass
The answerback bypass function stops the answerback input function and answerback check
function, forcing the answerback input value (PV) and the manipulated output value (MV) to
match. The status of the answerback bypass switch will be input via the answerback bypass input
terminal (SWI). The contact input and internal status switch can be specified to the input terminal.
If there is no connection to the SWI input terminal, the answerback bypass switch (BPSW) can
be specified directly from outside the function block.
The answerback bypass function is available only when the answerback bypass switch (BPSW)
is set to 1.
The table below shows the relationship between the answerback bypass input terminal and the
answerback bypass switch.
Table Relationship between Answerback Bypass Input Terminal and Answerback Bypass Switch
Item SWI input terminal ON SWI input terminal OFF
Answerback bypass switch (BPSW) 1 0
Answerback bypass function Execute Stop
D030412E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.4 Switch Instrument Block and Enhanced Switch Instrument Block> D3-181

n Output Signal Conversion

▼ Output Action Direction
The output signal conversion function outputs a contact signal to the output destination specified
by the output terminal depending on the manipulated output value (MV). The manipulated output
value (MV) from the switch instrument block or the enhanced switch instrument block varies by
the block mode.
• When in Manual (MAN) Mode
The output value is the values set on HIS.
• When in Automatic (AUT) or Cascade (CAS) Mode
The output value is the value set by other blocks such as sequence control block (CSV).
• When in Remote Output (ROUT) Mode
The output value is the value remotely set from a supervisory computer (RMV).
• When in On-site Manual (Tracking) (TRK) Mode
The output value is the value of the answerback input value (PV) if it is not in simulation
status and answerback tracking is specified.

The output contact signal varies with the direction of output action. Output action direction can be
set on the Function Block Detail Builder.
• Output action direction:
Switch instrument block:
Select from [Direct], [Reverse], [Inverted connect Direct action] or [Inverted connect
Reversed action].
Enhanced switch instrument block:
Select from [Direct] or [Reverse].
The default is [Direct].

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.4 Switch Instrument Block and Enhanced Switch Instrument Block> D3-182
Table Manipulated Output Value (MV) and Output Status
Output status (*1)
Number of output point Output action direction MV
n n+1
2 ON -
Direct action
1 0 OFF -
(Two-position type) 0 ON -
Reverse action
2 OFF -
2 ON OFF
Direct action 1 OFF OFF
0 OFF ON
2 OFF ON
Reverse action 1 ON ON

2 0 ON OFF
(Three-position type) 2 OFF ON
Inverted connection
1 OFF OFF
Direct action (*2)
0 ON OFF
2 ON OFF
Inverted connection
Reversed action 1 ON ON
(*2)
0 OFF ON

2 2 ON OFF
Direct action
(Pulse type) 0 OFF ON
D030413E.ai

*1: “n” in the table indicates the element number specified to connect to OUT terminal of switch instrument blocks and enhanced
switch instrument blocks, or the OUT1 terminal of enhanced switch instrument blocks.
“n+1” in the table indicates the element number succeeding the element number “n” that is specified to connect to OUT terminal
of switch instrument blocks, or the element number specified to connect to OUT2 terminal of enhanced switch instrument blocks.
*2: Inverted connection cannot be defined for enhanced switch instrument block.

Number of output points 1 ON

(two-position type) n
OFF

MV=0 MV=2 MV=0

ON
n
Number of output points 2 OFF
(three-position type)
ON
n+1
OFF

MV=1 MV=2 MV=1 MV=0 MV=1

ON
n
Number of output points 2 OFF 1 to 2 sec
(Pulse type)
ON
n+1
OFF 1 to 2 sec

MV=2 MV=0
D030414E.ai

Figure Output Action (Action Direction = Direct Action)

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.4 Switch Instrument Block and Enhanced Switch Instrument Block> D3-183

n Output Tracking : Enhanced Switch Instrument Block

Output tracking is an output processing of enhanced switch instrument block. The output tracking
forces the manipulated output value (MV) to match value of the connected destination.
If an enhanced switch instrument block is connected in a cascade loop with FF faceplate block or
fieldbus function block, the enhanced switch block starts output tracking when the cascade loop
is disconnected and its block changes to IMAN mode.
Output tracking starts under the following circumstances:
• When the block becomes IMAN mode.
• When the block changes from service off (O/S) mode to MAN, AUT or CAS mode.
• When the I/O module connected to the output terminals recovered from failure.
• When the cascade loop is disconnected.

TIP
The output tracking of switch instrument block starts under the following circumstances:
• When the block becomes IMAN mode.
• When the block changes from service off (O/S) mode to MAN, AUT or CAS mode.
• When the I/O module connected to the output terminals recovered from failure.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.4 Switch Instrument Block and Enhanced Switch Instrument Block> D3-184

n MV Action on Setting CSV: KFCS2/FFCS/LFCS2

▼ MV of Switch Instrument/MC Instrument follows its CSV change
When CSV is changed by a sequence table or by a function block, whether the MV of switch
instrument block or enhanced switch instrument block to instantaneously follow the CSV change
or to follow the change at the next execution time can be specified.
On the Constant tab of FCS Properties sheet, if the option of [MV of Switch Instrument/MC
Instrument follows its CSV change] is checked, the MV will follow the CSV right after the CSV
is changed. Otherwise, the MV will follow the CSV at the next execution time of the switch
instrument block or enhanced switch instrument block. By default, this option is not checked.
Moreover, the option is valid not only for changing the CSV by sequence table blocks, but also
valid for changing the CSV by the logic chart blocks, calculation blocks as well as manipulating
the CSV on an HIS.

When the Option is Checked:

When the CSV is set from a sequence table, the MV of the switch instrument block or enhanced
switch instrument block will instantaneously follow the CSV change.
For example, if the CSV of a switch instrument block SO-1 is set to CSV=2, the direct MV action
may be illustrated as follows:
Control period of switch
instrument block

CSV=2
Sequence Set Value
CSV=0

MV=2
Manipulated Output Value
MV=0

ON
Actual Output
OFF

CSV=2 is set in the When other block access Switch instrument block
sequence table. the MV, the MV=CSV and sends output MV=2.
MV=2.
D030424E.ai

Figure CSV, MV and Actual Output when the Option is Checked: KFCS2/FFCS/LFCS2

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.4 Switch Instrument Block and Enhanced Switch Instrument Block> D3-185
When the Option is Unchecked:
When the CSV is set from a sequence table, the MV of the switch instrument block or enhanced
switch instrument block will follow the CSV change at the next execution time of the switch
instrument block or enhanced switch instrument block.
For example, if the CSV of a switch instrument block SO-1 is set to CSV=2, the direct MV action
may be illustrated as follows:
Control period of switch
instrument block

CSV=2
Sequence Set Value
CSV=0

MV=2
Manipulated Output Value
MV=0

ON
Actual Output
OFF

CSV=2 is set in the When other block access Switch instrument block
sequence table. the MV, the MV=0. sends output MV=CSV
and MV=2.
D030425E.ai

Figure CSV, MV and Actual Output when the Option is Unchecked: KFCS2/FFCS/LFCS2

n Answerback Tracking
▼ Answerback Tracking
The answerback tracking function forces the manipulated output value (MV) to coincide with the
answerback input value (PV) (MV=PV) during the on-site manual operation mode (TRK). The
presence/absence of the answerback tracking function can be specified in the Function Block
Detail Builder.
• Answerback Tracking:
Select from “Yes’’ or “No.’’
The default is “Yes.”

n Calibration
The calibration function allows manual setting of the input signal. The calibration function is
activated when the data status of the answerback input value (PV) becomes calibration (CAL).
This state is called the calibration status. Change to the calibration status can be executed from
the human-machine interface station (operation and monitoring functions).
The following describes the switch instrument block and enhanced switch instrument block
actions during the calibration status.
• Answerback input value (PV) can be set manually.
• The manual fall back condition is satisfied and the block mode becomes manual (MAN).
The output function is performed.
• Bypass the alarm process for the answerback input value (PV).
• Bypass the answerback input and answerback check function.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.4 Switch Instrument Block and Enhanced Switch Instrument Block> D3-186

n Simulation
The simulation function simulates only the internal processing of the switch instrument block/
the enhanced switch instrument block in order to test the operation of devices using the switch
instrument block/the enhanced switch instrument block. There exists two main status in the
switch instrument block/the enhanced switch instrument block: normal status and simulation
status.
The status shifts to simulation when the switch instrument block/the enhanced switch instrument
block simulation switch (SIMM) is set to ON (=1).

l Setting the Simulation Status

Upon setting the switch instrument block simulation switch (SIMM) to ON (=1), the status shifts
to simulation (Block status: SIM). The status can be set in the tuning view of operation and
monitoring functions.

l Canceling the Simulation Status

Upon setting the switch instrument block simulation switch (SIMM) to OFF (=0), the simulation
status will be canceled (block status: NR). The status can be canceled in the tuning view of
operation and monitoring functions.

l Actions under Simulation Status

The table below lists the actions of the switch instrument block/the enhanced switch instrument
block functions during simulation status.
• Block mode: Same as the normal state except IMAN
• Block status: SIM
• Alarm status: Always NR (Normal)
• Answerback input: No action except for including raw input data value.
• Answerback check:
Checking and alarming action is stopped. After the answerback check suppression time
is elapsed, MV value is set to PV value. When the answerback check is “No,” MV value is
immediately set to PV value.
• Answerback bypass: No action except for including data from SWI.
• Output signal conversion: Output action is stopped.
• Answerback tracking: No action
• Alarm function: No action
• Calibration function: Same as the normal state.

The following describes the switch instrument block/the enhanced switch instrument block action
in the first scan period after canceling the simulation status.
• For a status-output type, the contact state of the output destination (element connected to
output terminal) is read back as the manipulated output value (MV).
• For a pulse-output type (SIO-12P, SIO-22P, SIO-12PE, SIO-22PE), if the answerback
tracking function is “Yes,” the manipulated output value (MV) is matched to the answerback
input value (PV).

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.4 Switch Instrument Block and Enhanced Switch Instrument Block> D3-187

n Mode Change Interlock

This function prevents the automatic operation of the switch instrument block/the enhanced
switch instrument block. When the internal status switch of the interlock switch input terminal
connection destination is turned ON, the block mode change command to the automatic
operation status (AUT, CAS, ROUT) is disabled. At the same time, the manual fall back condition
becomes satisfied, and the block mode is changed to manual mode (MAN).
Any data containing a logical value such as the connection I/O and the internal switch can be
specified to the connection destination of the interlock switch input terminal regardless of the
element type.

n Initialization Manual
The initialization manual function is an error processing functions. It suspends the control action
by changing the block mode to the initialization manual mode (IMAN). The initialization manual][
function will be activated when a temporary abnormal state occurred at the output destination of
manipulated output value can be restarted automatically upon recovery from the abnormal state,
for instance, during on-line maintenance.
• When the initialization manual function is activated, the control action is stopped when the
block mode is in the status that allows automatic controls as in the automatic mode (AUT).
The previous manipulated output value (MV) is retained. However, the manual operation
will not be available if the initialization manual mode is enabled, even if the mode is changed
from IMAN (AUT) to IMAN (MAN). Upon returning from the initialization manual (IMAN)
mode, the manipulated output value (MV) will track the PV value of the output destination.
• The initialization manual mode (IMAN) is reset upon recovery of the occurrence conditions,
returning to the previous block mode. If the block mode change is executed during the
initialization manual mode (IMAN), the block mode will be the mode specified upon recovery
of IMAN conditions.

SEE
ALSO For initialization manual conditions, see the following:
“n The Initialization Manual Condition” in C6.1.5, “Block Mode Transition Condition”

n Manual Mode Fallback

The manual fallback function is one of the error processing functions. It forces the control to stop
by changing the block mode to the manual mode (MAN) regardless of the current operation
status. If the manual mode (MAN) is activated by the manual fallback function, the block mode of
the switch instrument block/the enhanced switch instrument block remains manual mode (MAN)
even after the recovery of an error.
The following describes manual fallback conditions for the switch instrument block/the enhanced
switch instrument block.
• When the switch connected to INT terminal is turned ON (i.e., the interlock condition is
established for changing the block into interlock mode).
• When the data status of the answerback input value (PV) changes to calibration (CAL).
• When the data status of the manipulated output value becomes output failure (PTPF).
• When the FCS is undergoing a restart process, and the manipulated output is used for a
process control via a process control I/O module.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.4 Switch Instrument Block and Enhanced Switch Instrument Block> D3-188

n Data Items – Switch Instrument Block and Enhanced Switch

Instrument Block
SEE
ALSO For a list of valid block modes for the switch instrument blocks and the enhanced switch instrument block, see the
following:
D3.1.2, “Block Mode of Sequence Control Blocks”

Table Data Items of the Switch Instrument Blocks (SI-1, SI-2) and the Enhanced Switch Instrument
Block (SI-1E, SI-2E)
Entry Permitted
Data Item Data Name Range Default
or Not
MODE Block mode x ----- O/S (AUT)
BSTS Block status ----- NR
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- 0
AF Alarm detection ----- 0
AOFS Alarm inhibition ----- 0
PV Answerback input value Δ (*1) 0 to 2 0
RAW Raw input data 0 to 3 -----
SIMM Simulation switch x 0, 1 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D030415E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL

Table Data Items of the Switch Instrument Blocks (SO-1, SO-2) and the Enhanced Switch Instrument
Block (SO-1E, SO-2E)
Entry Permitted
Data Item Data Name Range Default
or Not
MODE Block mode x ----- O/S (MAN)
BSTS Block status ----- NR
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- 0
AF Alarm detection ----- 0
AOFS Alarm inhibition ----- 0
MV Manipulated output value Δ (*1) 0 to 2 0
RMV Remote manipulated output value Δ (*3) 0 to 2 0
CSV Sequence setpoint value x 0 to 2 0
SIMM Simulation switch x 0, 1 0
TSW Tracking switch Δ (*2) 0, 1 0
BSW Backup switch x 0, 1 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D030416E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the block mode is MAN
*2: Entry is permitted when no data is specified to the input connection terminal
*3: Entry is permitted when the block mode is ROUT

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D3.4 Switch Instrument Block and Enhanced Switch Instrument Block> D3-189
Table Data Items of the Switch Instrument Blocks (SIO-11, SIO-12, SIO-21, SIO-22, SIO-12P,
SIO-22P) and the Enhanced Switch Instrument Block (SIO-11E, SIO-12E, SIO-21E, SIO-22E, SIO-
12PE, SIO-22PE)
Entry Permitted
Data Item Data Name Range Default
or Not
MODE Block mode x ----- O/S (MAN)
BSTS Block status ----- NR
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- 0
AF Alarm detection ----- 0
AOFS Alarm inhibition ----- 0
PV Answerback input value Δ (*1) 0 to 2 0
RAW Answerback raw signal 0 to 3 -----
MV Manipulated output value Δ (*2) 0 to 2 0
RMV Remote manipulated output value Δ (*4) 0 to 2 0
CSV Sequence setpoint value x 0 to 2 0
Answerback check masking time
MTM x 0 to 10000 4
(seconds)
PTM Elapsed time (seconds) 0 to 10000 0
SIMM Simulation switch x 0, 1 0
BPSW Answerback bypass switch Δ (*3) 0, 1 0
TSW Tracking switch Δ (*3) 0, 1 0
BSW Backup switch x 0, 1 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D030417E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally
*1: Entry is permitted when the data status is CAL
*2: Entry is permitted when the block mode is MAN
*3: Entry is permitted when no data is specified to the input connection terminal
*4: Entry is permitted when the block mode is ROUT

n Block Status of Switch Instrument Block and the Enhanced Switch

Instrument Block
Table Block Status of Switch Instrument Block and Enhanced Switch Instrument Block
Block Status
Level Description
Symbol Name
3 ANCK (*1) Answerback Check Inhibition Answerback check is inhibited
SIM Simulation Simulation state, output is invalidated
1
NR Normal Normal state
D030419E.ai

*1: ANCK status is not available in SI-1, SI-2, SO-1 and SO-2.

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D3.5 Timer Block (TM)> D3-190

D3.5 Timer Block (TM)

The Timer Block (TM) is used to measure time in the unit of seconds or minutes.

n Timer Block (TM)

▼ Connection
The Timer Block (TM) is a function block which measures time in the unit of seconds or minutes.
In addition to the basic elapsed time measuring function, the block includes the preset timer
function which notifies the time-up after a specified amount of time has elapsed, the function
which performs the periodic action, and the function which manipulates the status based on the
action signals specified in the output terminals.
The figure below is a function block diagram of the Timer Block (TM).

Counting
PV01 OUT
process

(CTUP) CTUP: Time-up

D030501E.ai

Figure Function Block Diagram of the Timer Block (TM)

The table below lists the connection methods and connection destinations of the I/O terminals of
the Timer Block (TM).
Table Connection Methods and Connection Destinations of the I/O Terminals of the Timer Block (TM)
Connection type Connection destination

I/O terminal Status Terminal

Data Data Condition Process Software Function
manipula- connecti-
reference setting testing I/O I/O block
tion on
Output
OUT x x x x
terminal
D030502E.ai

x: Connection available
Blank: Connection not available

Operations such as the timer start or stop can be performed from the sequence control block,
calculation block, and operation and monitoring functions. The block status which indicates an
operating status can also be referenced from other function blocks.
Status manipulation is the only connection method from the OUT terminal of the Timer Block
(TM). Thus, the Timer Block (TM) manipulates the status according to the action signals specified
in the OUT terminals. The logical value of the Timer Block (TM) becomes true when the preset
timer function is in time-up status (block status: CTUP).

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.5 Timer Block (TM)> D3-191
The figure below shows an example of connection between the Timer Block (TM) and other
sequence control block.

TM Sequence connection CTS

OUT
(TM001) (COUNT01)

Specify COUNT01.ACT.ON
D030503E.ai

Figure Connection Example of Timer Block (TM) and Other Sequence Control Block

Every time the Timer Block (TM) with the tag name TM001 expires, the Software Counter Block
(CTS) with the tag name COUNT01 is increased by one count.

n Process Timing
The process timing of Timer block is only based on periodical start period. The periodic start
period is based on high-speed scan period, medium-speed scan period (*1) and basic scan
period.
*1: Medium-speed scan period is supported in KFCS2, KFCS, FFCS, LFCS2 and LFCS only.

n Set Parameter
▼ Timer Property
The following describes the set parameters of the Timer Block (TM).
• Preset time setpoint value (PH): 0 to 100000 (second or minute)
• Pre-alarm setpoint value (DL): PL to PH
The PL is the low-limit value (fixed at 0) of the timer elapsed time (PV).

Use the Function Block Detail Builder to set the unit for the preset time setpoint.
• Timer Property:
Select from “Second timer” or “Minute timer.”
Default is “Second timer.”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.5 Timer Block (TM)> D3-192

n Action Commands for the Timer Block (TM)

Action commands can be given to the Timer Block (TM) from the operation and monitoring
functions, other sequence control blocks, or calculation block.

l Action Commands from the Operation and Monitoring Functions

Action commands can be given to the Timer Block (TM) by pressing the softkeys listed below.
• STOP:
Timer stop command
• START:
Timer start command
• CONTINUE:
Restart command
• PAUS:
Pause command

l Action Commands from Sequence Control Blocks and Calculation Blocks

(CALCU, CALCU-C)
The table below describes the specified format of action signals and action description when
giving action commands to the Timer Block (TM) from sequence control blocks and the
calculation block.
Table Specified Format of Action Signals and Action Description
Action signal description column Y/N
Action description
Output signal Action specification True/False

Y/True Timer stop command

STOP
N/False Disable
Y/True Timer start command
START
N/False Timer stop command (*1)
Element symbol.OP
Y/True Restart command
RSTR
N/False Disable
Y/True Pause command
WAIT
N/False Restart command (*1)
D030504E.ai

*1: An action for “N” is enabled only with the sequence table.
An action for “False” is enabled only with the logic chart.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.5 Timer Block (TM)> D3-193

n Action of the Timer Block

When the Timer Block receives an action command from the operation and monitoring functions
or other function blocks, the block status changes according to the given command. There exist
four types of basic actions for the Timer Block: Start, Stop, Pause, and Restart.
The figure below shows the relationship between the timer elapsed time (PV) and the block
status, and each basic action.
PV Value

PH

DL
DV

PV

Time

Block RUN STOP RUN STOP

Status NR NR NR PALM CTUP NR

Action Start Stop Start Stop

Command Command Command Command Command
D030505E.ai

Figure Basic Actions of the Timer Block (TM)

l Timer Start Action

When the Timer Block (TM) receives the timer start command, it starts the counting action upon
resetting (PV=0) the timer elapsed time (PV). The block status of the Timer Block (TM) changes
to “counting” (RUN-NR). The DV indicates the timer’s remaining time (DV=PH-PV).

The figure below shows the changes in the timer elapsed time (PV) by the timer start command.
Start command

PV value Scan period

PV=0 Time

Block status RUN

D030506E.ai

Figure Timer Elapsed Time (PV) by Timer Start Command

The following describes an example of the timer start specified in the action signal column of the
sequence table.
Tag name.Data item Data Action rule
TM0002.OP START Y D030507E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.5 Timer Block (TM)> D3-194
l Timer Stop Action
When the Timer Block (TM) receives the timer stop command, it stops the counting action while
holding the timer elapsed time (PV). The block status of the Timer Block (TM) changes to stop
status (STOP).

The figure below shows the changes in the timer elapsed time (PV) by the timer stop command.
PV

Stop command
Scan period

PV=0 Time

Block
RUN STOP
Status
D030508E.ai

Figure Timer Elapsed Time (PV) by Timer Stop Command

The following describes an example of specifying the timer stop in the action signal column of the
sequence table.
Tag name.Data item Data Action rule
TM0002.OP STOP Y D030509E.ai

l Timer Pause Action

When the Timer Block (TM) receives the pause command, the counting action is halted. During
the pause, the Timer Block (TM) holds the timer elapsed time (PV) or other data. As for the block
status, the pause status (PAUS) is newly added while the statuses such as counting (RUN), pre-
alarm status (PALM), time-up status (CTUP), or stop status (STOP) are held. However, the status
will be changed if the preset time setpoint value (PH), pre-alarm setpoint value (DL), or the timer
elapsed time (PV) is changed during the pause.
The following describes an example of specifying the timer pause in the action signal column of
the sequence table.
Tag name.Data item Data Action rule
TM0002.OP WAIT Y D030510E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.5 Timer Block (TM)> D3-195
l Timer Restart Action
When the Timer Block (TM) in pause status receives the restart command, the counting action
is restarted. The Timer Block (TM) is released from the pause status (PAUS), and returns to the
previous block status that has been held.
The pause status (PAUS) is released when it receives the restart command. However, the
elapsed time (PV) is updated every scan period of the Timer Block (TM) itself.

PH

DL
DV

PV

RUN STOP
Block
NR PALM CTUP
Status
PAUS PAUS

Action Pause Restart Stop Pause Restart Start

Command Command Command Command Command Command Command
D030511E.ai

Figure Pause/Restart Action of Timer

The following describes an example of specifying the timer restart in the action signal column of
the sequence table.
Tag name.Data item Data Action rule
TM0002.OP RSTR Y D030512E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.5 Timer Block (TM)> D3-196

n Preset Timer
The preset timer function notifies that the specified amount of time has elapsed. The content of
the notification includes the time-up status (CTUP) based on the preset time setpoint (PH) and
the pre-alarm status (PALM) which gives prior notices before reaching the preset time.
If one of the following conditions is satisfied for the timer’s remaining time (DV=PH-PV) when the
block status is counting (RUN), the pre-alarm status (PALM) or time-up status becomes true.
• 0<DV≤DL:
Pre-alarm status (PALM)
• DV=0:
Time-up status (CTUP)
However, if the pre-alarm setpoint value (DL) is 0, the pre-alarm status (PALM) will not occur.
The timer block actions and the block statuses are illustrated as follows.

PH

DL
DV

PV

RUN STOP RUN

Block Status NR PALM CTUP NR

PAUS

Action Command Start Pause Restart Stop Start

Command Command Command Command Command
D030516E.ai

Figure Block Status of the Timer Block (TM)

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.5 Timer Block (TM)> D3-197
l Hold Pre-Alarm after Time-Up: KFCS2/FFCS/LFCS2
▼ TM/CTS/CTP blocks hold PALM after CTUP
The pre-alarm status (PALM) of a timer or counter block can be held even when the block
reaches time-up status (CTUP). This option can be set on the FCS properties sheet by checking
the option of [TM/CTS/CTP blocks hold PALM after CTUP] on the Constant tab. If this option is
not checked, the pre-alarm status (PALM) will be reset when the block reaches time-up status
(CTUP). By default, this option is not checked.
If the option of [TM/CTS/CTP blocks hold PALM after CTUP] is checked, the block status will
change according to the timer’s remaining time (DV=PH-PV) and shown as follows:
• 0<DV DL: Pre-alarm status (PALM)
• DV 0: Time-up status (CTUP) and Pre-alarm status (PALM)

PH

DL
DV

PV

RUN STOP RUN

Block Status NR PALM CTUP NR

PAUS

Action Command Start Pause Restart Stop Start

Command Command Command Command Command
D030517E.ai

Figure Timer Block Status with Option of Hold PALM in CTUP Status: KFSC2/FFCS/LFCS2

TIP
Inside the FCS, the block status of TM/CTS/CTP blocks is expressed in 32 bits.
PALM hold bit (0x01000000)
31 15 0

Higher Priority Lower Priority

CTUP bit (0x00400000)
PALM bit (0x00800000)
D030518E.ai

Figure Internal Bit Image for Block Status of TM/CTS/CTP Blocks: KFCS2/FFCS/LFCS2

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.5 Timer Block (TM)> D3-198
If the check box of [TM/CTS/CTP blocks hold PALM after CTUP] is checked, the PALM hold bit synchronizes with
the CTUP bit (ON/OFF). The value of the data item [@BSTS] differs between the checked [TM/CTS/CTP blocks
hold PALM after CTUP] and the unchecked [TM/CTS/CTP blocks hold PALM after CTUP] when the PALM hold
bit is ON. If you refer to the block status from a Graphic modifier conditional formula, a SEBOL program, or a
supervisory computer, use the individual bit such as the CTUP bit or the alphanumeric data BSTS, or uncheck the
[TM/CTS/CTP blocks hold PALM after CTUP] box.

After a snapshot-save in the test function, if you change the checkbox [TM/CTS/CTP blocks hold PALM after
CTUP] and snapshot-load, the setting in the checkbox [TM/CTS/CTP blocks hold PALM after CTUP] and the bit
image indicating the block status become inconsistent.

Operation 1
1. Check the check box of [TM/CTS/CTP blocks hold PALM after CTUP]. After that, start the FCS/FCS
simulator.
2. TM/CTS/CTP blocks go into CTUP status.
3. Snapshot-save.
4. Uncheck the [TM/CTS/CTP blocks hold PALM after CTUP]. After that, restart the FCS/FCS simulator.
5. Snapshot-load the data saved in the step 3.
After the step 5, the setting of the checkbox and the bit image indicating the block status become
inconsistent. Here, if the instrument faceplate for the TM/CTS/CTP is displayed on HIS, the block status
field is blank.
The setting of the checkbox and the bit image become consistent, and the block status is displayed
normally if:
• For TM/CTP
The next scan starts, or RUN/STOP is ordered.
• For CTS
One of PH/DL/PV is changed, or ACT. ON is executed in a sequence table or a logic chart.

Operation 2
1. Uncheck the check box of [TM/CTS/CTP blocks hold PALM after CTUP]. After that, start the FCS/FCS
simulator.
2. TM/CTS/CTP blocks go into CTUP status.
3. Snapshot-save.
4. Check the [TM/CTS/CTP blocks hold PALM after CTUP]. After that, restart the FCS/FCS simulator.
5. Snapshot-load the data saved in the step 3.
After the step 5, the setting of the checkbox and the bit image indicating the block status become
inconsistent. But [CTUP] is displayed in the block status field for TM/CTS/CTP.
The setting of the checkbox and the bit image become consistent if:
• For TM/CTP
The next scan starts, or RUN/STOP is ordered.
• For CTS
One of PH/DL/PV is changed, or ACT. ON is executed in a sequence table or a logic chart.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.5 Timer Block (TM)> D3-199

n Periodic Action
▼ Periodic Action
When timer block reaches time-up status (CTUP), the timer block can be restarted to count
again.
This periodic action can be set using the Function Block Detail Builder.
• Periodic Action:
Select from “Yes” or “No.”
The default is “No.”
The action of the timer is different according to presence specified of the periodic action.

l When Periodic Action Specification is “No”

When the time-up status becomes true, the elapsed time update is stopped. The PV=PH and
DV=0 status is therefore retained.
When the time-up status (CTUP) is true, the block status and the timer elapsed time (PV) will be
held even if the preset time setpoint (PH) is changed. A stop command or start command must be
given remotely in order to cancel the time-up status.

l When Periodic Action Specification is “Yes”

The time-up status (CTUP) becomes true if PV≥PH and DV≤0. However, when the timing
increment is in “seconds,” the timer elapsed time (PV) is set to 1 second (when the scan period is
1 second) at the next scanning to restart the counting action. The block status will be the status
caused when PV=1. The figure below shows the changes in the timer elapsed time (PV) when
the periodic action specification is “Yes.”
PV

PH 8

4 PV=1
PV
2

0 Time

Scan period

Block RUN
status NR CTUP NR
D030513E.ai

Figure Change in Timer Elapsed Time (PV) When Preset Time Setpoint (PH) is 8 Seconds

n Status Manipulation from the Timer Block (TM)

When the action signal by sequence connection is specified to the OUT terminal of the time
block, the Timer Block (TM) executes the status manipulation corresponding to the existing block
status.
• CTUP and NOT PAUS:
Executes status manipulation for the logical value True.
• NR and NOT PAUS, or PALM and NOT PAUS:
Executes status manipulation for the logical value False.
• STOP or PAUS:
Disable

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.5 Timer Block (TM)> D3-200

n Data Items – TM
The table below shows the data items of the Timer Block (TM):
Table Data Items of the Timer Block (TM)
Entry Permitted
Data Item Data Name Range Default
or Not
MODE Block mode x ----- O/S (AUT)
BSTS Block status ----- STOP
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- 0
AF Alarm detection ----- 0
AOFS Alarm inhibition ----- 0
PV Elapsed time x PL to PH 0
PH Preset time setpoint value x 0 to 100000 100000
DV Remaining time -PL to PH PH
DL Pre-alarm setpoint value x PL to PH PL
PL PV scale low limit Fixed at 0. 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D030514E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted

SEE
ALSO For a list of valid block modes of the timer block, see the following:
D3.1.2, “Block Mode of Sequence Control Blocks”

n Block Status of Timer Block (TM)

Table Block Status of Timer Block (TM)
Block Status
Level Description
Symbol Name
3 PAUS Pause Timer is paused
PALM Pre-Alarm Timer is running and 0<DV<=DL
2 CTUP Time Up Timer is running and DV = 0
NR Normal Timer is running and DV > DL
RUN Run Timer is running after a Start command
1
STOP Normal Timer is stopped after a Stop command
D030515E.ai

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D3.6 Software Counter Block (CTS)> D3-201

D3.6 Software Counter Block (CTS)

The Software Counter Block (CTS) is used to calculate the number of events occurred.

n Software Counter Block (CTS)

▼ Connection
In addition to the basic calculating function, the CTS block includes the preset counter function
which notifies of the count-up upon calculating the specified numeric value, and the function
which manipulates the status based on the action signal specified to the output terminal.
The figure below is a function block diagram for the Software Counter Clock (CTS).

Count
PV OUT
process

D030601E.ai

Figure Function Block Diagram for the Software Counter Block (CTS)

The table below lists the connection methods and connection destinations of the I/O terminal of
the Software Counter Block (CTS).
Table Connection Methods and Connection Destinations of the I/O Terminals of the Software Counter
Block (CTS)
Connection type Connection destination

I/O terminal Status Terminal

Data Data Condition Process Software Function
manipula- connecti-
reference setting testing I/O I/O block
tion on
Output x
OUT x x x
terminal
D030602E.ai

x: Connection available
Blank: Connection not available

The calculating operation of the software counter can be performed from other function blocks
such as the sequence control block or the calculation block.
The figure below shows a connection example of Software Counter Block (CTS). In this example,
the CALCU block sends a one-shot start command to CTS for counting.
Sequence connection
DI010 Q01 CTS001.ACT.ON
CALCU OUT
DI011 Q02

Process input General-purpose

calculation block CTS
OUT
(CTS001)
Software counter block
D030603E.ai

Figure Example of Using General-Purpose Calculation Block (CALCU)

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.6 Software Counter Block (CTS)> D3-202

n Process Timing
The process timing of CTS block is only based on one-shot start.

n Set Parameter
The set parameters of the Software Counter Block (CTS) are:
• Preset setpoint (PH):
0 to 100000
• Pre-alarm setpoint (DL):
PL to PH
PL: The scale low limit (fixed at 0) of the count value (PV).

n Operation of the Software Counter Block (CTS)

The Software Counter Block (CTS) updates the count value (PV) upon receiving the counter
operation command. It also changes the block status.
The figure below shows the basic operation of the Software Counter Block (CTS).

7 Hold PV value
6
PH
(=6) DL=2 5
DV=4
4
3
2
PV=1 PV

Time

Block STOP RUN STOP

status NR PALM CTUP

Counter operation
command
Operation Stop
command command
D030604E.ai

Figure Basic Operation of the Software Counter Block (CTS)

l Software Counter Update Action

Every time the Software Counter Block (CTS) receives the counter operation command, the
count value (PV) is added by 1. If the block status is in stop status (STOP) when the counter
operation command is received, the block status of the Software Counter Block (CTS) changes
to “counting” (RUN-NR). The count value (PV) is also reset (PV=1).
The following describes an example of specifying the operation of the software counter in the
action signal column of the sequence table.
Tag name.Data item Data Action rule
CTS001.ACT ON Y D030605E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.6 Software Counter Block (CTS)> D3-203
l Software Counter Stop Action
When the Software Counter Block (CTS) receives the counter stop command, it stops its
calculating action while holding the count value (PV). The block status of the Software Counter
Block (CTS) changes to the stop status (STOP).
The following describes an example of specifying the software counter stop in the action signal
column of the sequence table.
Tag name.Data item Data Action rule
CTS001.ACT OFF Y D030606E.ai

n Preset Counter Function

The preset counter function notifies that the count value (PV) has reached the specified count
number. The content of notification includes the count-up status (CTUP) based on the preset
setpoint (PH), and the pre-alarm status (PALM) which gives prior notices before reaching the
preset setpoint (PH).
When the remaining count value (DV=PH-PV) satisfies the following conditions while the block
status is in counting (RUN), the pre-alarm status (PALM) or the count-up status (CTUP) will be as
follows:
• When 0<DV≤DL:
Pre-alarm status (PALM)
• When DV≤0:
Count-up status (CTUP)

Since the pre-alarm status (PALM) and the count-up status (CTUP) can not become true
simultaneously, the pre-alarm status (PALM) is canceled when DV=0, shifting to the count-up
status (CTUP). Although the count value (PV) continues to be updated even after the status shifts
to the count-up, the count value (PV) is reset when it reaches 100000. However, the block status
at count-up is held as count-up status (CTUP).
In order to cancel the count-up status (CTUP), the count value (PV) must be set remotely or a
stop command must be given. Also, when the pre-alarm setpoint (DL) is set to 0, the pre-alarm
status (PALM) will not occur.

l Hold Pre-Alarm after Count-Up: KFCS2/FFCS/LFCS2

▼ TM/CTS/CTP blocks hold PALM after CTUP
The pre-alarm status (PALM) of a counter block can be held even when the block reaches count-
up status (CTUP). This option can be set on the FCS properties sheet by checking the option of
[TM/CTS/CTP blocks hold PALM after CTUP] on the Constant tab. If this option is not checked,
the pre-alarm status (PALM) s will be reset when the block reaches count-up status (CTUP). By
default, this option is not checked.
If the option of [TM/CTS/CTP blocks hold PALM after CTUP] is checked, the block status will
change according to the remaining count value (DV=PH-PV) and shown as follows:
• 0<DV≤DL:
Pre-alarm status (PALM)
• DV≤0:
Count-up status (CTUP) and Pre-alarm status (PALM)

SEE
ALSO For details of the behavior in Count-up complete (CTUP) status with the checked [TM/CTS/CTP blocks hold
PALM after CTUP], see the following:
“l Hold Pre-Alarm after Time-Up: KFCS2/FFCS/LFCS2” in “n Preset Timer” in D3.5, “Timer Block (TM)”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.6 Software Counter Block (CTS)> D3-204

n Status Manipulation from the Software Counter Block (CTS)

When the action signal by sequence connection is specified to the output terminal of the Software
Counter Block (CTS), the status manipulation is performed based on the block status.
• CTUP:
Executes status manipulation for the logical value True.
• NR or PALM:
Executes status manipulation for the logical value False.
• STOP:
Disable

n Data Items – CTS

Table Data Items of the Software Counter Block (CTS)
Entry Permitted
Data Item Data Name Range Default
or Not
MODE Block mode x ----- O/S (AUT)
BSTS Block status ----- STOP
PV Count value x 0 to 100000 0
PH Preset setpoint x 0 to 100000 100000
DV Remaining count value -PL to PH PH
DL Pre-alarm setpoint x PL to PH PL
PL PV scale low limit Fixed at 0. 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D030607E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted

SEE
ALSO For a list of valid block modes of the CTS block, see the following:
D3.1.2, “Block Mode of Sequence Control Blocks”

n Block Status of Software Counter Block (CTS)

Table Block Status of Software Counter Block (CTS)
Block Status
Level Description
Symbol Name
NR Normal Counter is running and DV > DL
2 PALM Pre-Alarm Counter is running and 0<DV<=DL
CTUP Count Up Counter is running and DV <= 0
RUN Run Counter is running after a Start command
1
STOP Normal Counter is stopped after a Stop command
D030608E.ai

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D3.7 Pulse Train Input Counter Block (CTP)> D3-205

D3.7 Pulse Train Input Counter Block (CTP)

The Pulse Train Input Counter Block (CTP) is used to count the number of processes,
which are expressed in the form of pulse signals.

n Pulse Train Input Counter Block (CTP)

▼ Connection
The Pulse Train Input Counter Block (CTP) is a function block that counts the number of
processes, which are expressed in the form of pulse signals. In addition to the basic counting
function, it also includes the preset counter function, which indicates the count-up state when the
specified number has been counted, and a function that manipulates the status based on the
action signal specified at the output terminal.
The following is a function block diagram of the Pulse Train Input Counter Block (CTP).

Count
IN PV OUT
Process

D030701E.ai

Figure Function Block Diagram of the Pulse Train Input Counter Block (CTP)

SEE
ALSO • For the types of alarm processing possible for the CTP block, see the following:
D3.1.1, “Alarm Processing of Sequence Control Blocks”
• For more information about alarm processing, see the following:
C5, “Alarm Processing-FCS”

The table below lists connection methods and destinations for the Pulse Train Input Counter
Block (CTP).
Table Connection Methods and Destinations for the Pulse Train Input Counter Block (CTP) I/O
Terminals
Connection type Connection destination

I/O terminal Status Terminal

Data Data Condition Process Software Function
manipula- connecti-
reference setting testing I/O I/O block
tion on
Input x x
IN
terminal
Output x x x x
OUT
terminal
D030702E.ai

x: Connection available
Blank: Connection not available

Operations such as start or stop of the pulse counter can be performed from other function blocks
such as the sequence control block or the calculation block, as well as from the operation and
monitoring functions. The block status that indicates the operating status can be referenced from
other function blocks.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.7 Pulse Train Input Counter Block (CTP)> D3-206
The figure below shows a signal connection example from the pulse input module.

CTP
(CTP001)
IN

%Znnusmm
D030703E.ai

Figure Example of the Signal Connection from the Pulse Input Module

n Process Timing
The process timing of Timer block is only based on periodical start period. The periodic start
period is based on high-speed scan period, medium-speed scan period (*1) and basic scan
period.
*1: Medium-speed scan period is supported in KFCS2, KFCS, LFCS2 and LFCS only.

n Set Parameters - CTP

The following are the set parameters of the Pulse Train Input Counter Block (CTS).
• Preset setpoint (PH): 0 to 100000
• Pre-alarm setpoint (DL): PL to PH
PL: The scale low limit (fixed at 0) of the count value (PV).

n Action Command of the Pulse Train Input Counter Block (CTP)

The action command can be issued to the Pulse Train Input Counter Block (CTP) from the
operation and monitoring functions, other sequence control block or calculation block.

l Action Command from the Operation and Monitoring Functions

Pressing a button listed below can issue an action command to the Pulse Train Input Counter
Block (CTP).
• STOP:
Counter stop command
• START:
Counter start command
• CONTINUE:
Restart command
• PAUS:
Pause command

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.7 Pulse Train Input Counter Block (CTP)> D3-207
l Action Command from Other Sequence Control Block or Calculation Block
The table below lists the description format and action description of the action signals when
issuing the action command to the Pulse Train Input Counter Block (CTP) from other sequence
control block or calculation block.
Table Description Format and Action Description of Action Signals
Action signal description column Y/N Action description
Action/Output signal Action specification True/False

Y/True Pulse input counter stop command

STOP
N/False Invalid
Y/True Pulse input counter start command
START
N/False Pulse input counter stop command (*1)
Element symbol.OP
Y/True Restart command
RSTR
N/False Invalid
Y/True Pause command
WAIT
N/False Restart command (*1)
D030704E.ai

*1: Actions for “N” are valid only for the sequence table.
Actions for “False” are valid only for the logic chart.

n Action of the Pulse Train Input Counter Block (CTP)

The Pulse Train Input Counter Block (CTP) is provided with an action command from the
operation and monitoring functions or other function block, and holds block status corresponding
to the command. The basic actions of the Pulse Train Input Counter Block (CTP) include four
actions: the update action, stop action, pause action and restart action.
The following describes the relationship between the count value (PV) and the block status along
with the basic action.

l Pulse Train Counter Update Action

When the Pulse Train Input Counter Block (CTP) receives the counter start command, it begins
counting after resetting the count value (PV=0). When the counter start command is received,
the block status becomes the during counting status (RUN-NR). While counting, it reads the
pulse input from the input terminal during each scan period, and updates the count value (PV) by
adding the pulse count that is increased from the previous period. When the data status of input
signals is “invalid (BAD)” or “I/O not ready (NRDY),” the status is recognized as faulty and the
count value (PV) is not updated.
The following shows an example of specifying the start of the Pulse Train Input Counter Block
(CTP) in the action signal column of the sequence table.
Tag name.Data item Data Action rule
CTP001.OP START Y D030705E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.7 Pulse Train Input Counter Block (CTP)> D3-208
l Pulse Train Counter Stop Action
When the Pulse Train Input Counter Block (CTP) receives the stop command for the counter, it
stops the counting operation while holding the count value (PV). The block status becomes the
stop status (STOP).
The following shows an example of specifying the stop of the Pulse Train Input Counter Block
(CTP) in the action signal column of the sequence table.
Tag name.Data item Data Action rule
CTP001.OP STOP Y D030706E.ai

PH
DL
DV

PV
5
2
4
4
Time
1 scan

Block STOP RUN STOP

status NR PALM NR CTUP

PALM
Action Start Start command Stop
commands command command

4 4 2 5

Time
Scan Scan Scan Scan Scan
D030707E.ai

Figure Basic Actions of the Pulse Train Counter

l Pulse Train Counter Pause Action

When the Pulse Train Input Counter Block (CTP) receives the pause command, it pauses the
counting operation. At this time, the data when the pause was issued is held as the count value
(PV). The pause status (PAUS) is added in addition to the currently held block status, which is
one of the counting (RUN), pre-alarm (PALM), normal (NR), time-up (CTUP) and stop (STOP)
statuses.
The following shows an example of specifying the pause of the Pulse Train Input Counter Block
(CTP) in the action signal column of the sequence table.
Tag name.Data item Data Action rule
CTP001.OP WAIT Y D030708E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.7 Pulse Train Input Counter Block (CTP)> D3-209
l Pulse Train Counter Restart Action
When the pausing Pulse Train Input Counter Block (CTP) receives the restart command, it
resumes the counter operation. The Pulse Train Input Counter Block (CTP) is released from the
pause status (PAUS) and returns to the block status that was originally held. If the original block
status was the counting status (RUN), count updating resumes from the counter value that was
held then.
The pause status (PAUS) is released at the timing when it accepts a restart command. However,
the count value (PV) update timing differs, depending on the scan period of the Pulse Train Input
Counter Block (CTP) itself.
The following shows an example of specifying the restart of the Pulse Train Input Counter Block
(CTP) in the action signal column of the sequence table.
Tag name.Data item Data Action rule
CTP001.OP RSTR Y D030709E.ai

PH

DL
DV
PV

Time

RUN STOP
Block
NR PALM CTUP
status
PAUS PAUS

Action Pause Restart Stop Pause Restart Start

commands command command command command command command
D030710E.ai

Figure Pause and Restart Actions

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.7 Pulse Train Input Counter Block (CTP)> D3-210

n Preset Counter Function of Pulse Counter

The preset counter function indicates that the count value (PV) has reached the specified count.
The content of the notification could be the count-up status (CTUP) based on the preset setpoint
(PH) or the pre-alarm status (PALM), which indicates prior to reaching the preset setpoint (PH).
When the remaining count value (DV=PH-PV) satisfies the following conditions while the block
status is in counting (RUN), the pre-alarm status (PALM) or the count-up status (CTUP) will be as
follows:
• 0<DV≤DL:
Pre-alarm status (PALM)
• DV≤0:
Count-up status (CTUP)

Since the pre-alarm status (PALM) and count-up status (CTUP) can not become true
simultaneously, the pre-alarm status (PALM) is canceled when DV=0, and the status shifts to the
count-up (CTUP) status. Although updating of the count value (PV) continue even after the status
shifts to count-up status, the count value (PV) is reset when it reaches 100,000 and counting
continues. However, the block status is held at the count-up status (CTUP) when it is counted.
In order to cancel the count-up status, it is necessary to set the count value (PV) externally or to
issue a stop command. Also, when the pre-alarm setpoint (DL) is set to 0, the pre-alarm status
(PALM) will not occur.

l Hold Pre-Alarm after Count-Up: KFCS2/FFCS/LFCS2

▼ TM/CTS/CTP blocks hold PALM after CTUP
The pre-alarm status (PALM) of a counter block can be held even when the block reaches count-
up status (CTUP). This option can be set on the FCS properties sheet by checking the option of
[TM/CTS/CTP blocks hold PALM after CTUP] on the Constant tab. If this option is not checked,
the pre-alarm status (PALM) s will be reset when the block reaches count-up status (CTUP). By
default, this option is not checked.
If the option of [TM/CTS/CTP blocks hold PALM after CTUP] is checked, the block status will
change according to the remaining count value (DV=PH-PV) and shown as follows:
• 0<DV≤DL:
Pre-alarm status (PALM)
• DV≤0:
Count-up status (CTUP) and Pre-alarm status (PALM)

SEE
ALSO For details of the behavior in Count-up complete (CTUP) status with the checked [TM/CTS/CTP blocks hold
PALM after CTUP], see the following:
“l Hold Pre-Alarm after Time-Up: KFCS2/FFCS/LFCS2” in “n Preset Timer” in D3.5, “Timer Block (TM)”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.7 Pulse Train Input Counter Block (CTP)> D3-211

n Status Manipulation from the Pulse Train Input Counter Block (CTP)
When the action signal is specified via sequence connection to the OUT terminal of the Pulse
Train Input Counter Block (CTP), the status is manipulated based on the block status.
• CTUP and NOT PAUS:
Execute status manipulation for true logical value.
• NR and NOT PAUS, or PALM and NOT PAUS:
Execute status manipulation for false logical value.
• STOP or PAUS:
Invalid

If an error occurs during status manipulation, the alarm status of the Pulse Train Input Counter
Block (CTP) becomes the connection failure status (CNF). This is recovered when either the
cause of alarm is removed during the status manipulation, or the pulse counter is stopped or
paused.

n Data Items – CTP

Table Data Items of the Pulse Counter Block (CTP)
Entry Permitted
Data Item Data Name Range Default
or Not
MODE Block mode x ----- O/S (AUT)
BSTS Block status ----- NR
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- 0
AF Alarm detection ----- 0
AOFS Alarm inhibition ----- 0
PV Count value x 0 to 100000 0
PH Preset setpoint x 0 to 100000 100000
DV Remaining count value -PL to PH PH
DL Pre-alarm setpoint x PL to PH PL
PL PV scale low limit Fixed at 0. 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D030711E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted

SEE
ALSO For a list of valid block modes of the CTP block, see the following:
D3.1.2, “Block Mode of Sequence Control Blocks”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D3.7 Pulse Train Input Counter Block (CTP)> D3-212

n Block Status of Pulse train Input Counter Block (CTP)

Table Block Status of Pulse train Input Counter Block (CTP)
Block Status
Level Description
Symbol Name
3 PAUS Pause Counter is paused
CTUP Count Up Counter is running and DV <= 0
2 PALM Pre-Alarm Counter is running and 0<DV<=DL
NR Normal Counter is running and DV>DL
RUN Run Counter is running after a Start command
1
STOP Normal Counter is stopped after a Stop command
D030712E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.8 Code Input Block (CI)> D3-213

D3.8 Code Input Block (CI)

The CI block is used to read the contact input or internal switch as a binary code or binary
coded decimal and display the integer value indicated by the code as the input code
value.

n Code Input Block (CI)

▼ Connection
The CI block is a function block that convert the digital input signal into code value (PV). The
conversion of digital input signals to input code values (PV) includes “No-conversion” in which
the signal pattern is interpreted as is as a binary number, and “BCD conversion” in which it is
interpreted as a BCD (binary coded decimal) code.
The following is a function block diagram of the Code Input Block (CI).

IN Bit Encoding PV
Inversion

D030801E.ai

Figure Function Block Diagram of Code Input Block (CI)

The table below lists connection methods and destinations for the Code Input Block (CI).
Table Connection Methods and Destinations for Code Input Block (CI) I/O terminals
Connection type Connection destination

I/O terminal Status Terminal

Data Data Condition Process Software Function
manipula- connecti-
reference setting testing I/O I/O block
tion on
Input
IN x x x
terminal
D030802E.ai

x: Connection available
Blank: Connection not available

The CI block input processing and code conversion are performed as one-shot execution from
other function blocks such as a sequence control block.
The following describes an example of specifying the code input block one-shot execution in the
action signal column of the sequence table.
Tag name.Data item Data Action rule
CI001.ACT ON Y D030803E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.8 Code Input Block (CI)> D3-214

n Process Timing
The process timing of CI block is only based on one-shot start.

n Number of Input Signals

▼ Number of Bits Input
The Code Input Block (CI) inputs the contact signals that continue for the number of input signal
points from the element of the input destination specified in the IN terminal. The first element
corresponds to the most significant digit. If there is a data error even at one point in the input
signal, the input code value (PV) is handled as faulty data. When an input error occurs, the
previous value is held for the input code value (PV).
The input signal points are set by the Function Block Detail Builder.
• Number of Bits Input:
0 to 18 points
Up to 16 points in the case of “no conversion”
Default is 0.

n Bit Inversion
▼ Bit Inversion
The bit inversion of the Code Input Block (CI) inverses the ON/OFF status of the input digital
signals. If the bit inversion is specified as ‘’Non-reversed,’’ the ON/OFF status will not be
inversed.
The bit inversion is set by the Function Block Detail Builder.
• Bit Inversion:
Select from “No” or “Yes.”
Default is “No.”

n Encoding
▼ Code Conversion
The encoding of the Code Input Block (CI) interprets the input digital signal as a code and
converts it into an integer value. The converted integer value becomes the input code value (PV).
The input code value (PV) is held until the Code Input Block (CI) starts for the next time via the
code input read command.
There exist two methods for encoding the digital signals:
• “No conversion,” which interprets the contact signal patterns as binary numbers.
• “BCD conversion,” which interprets the contact digital patterns as binary coded decimal
(BCD) codes.
The figure below shows examples of encoding when “no conversion” and “BCD conversion” are
specified.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.8 Code Input Block (CI)> D3-215
No conversion BCD conversion
%Z011101 %Z011101
%Z011102 %Z011102
%Z011103 %Z011103
%Z011104 %Z011104
%Z011105 %Z011105
%Z011106 %Z011106

O O O O O O O O O O O O
F N F N F N F N F N F N
F F F F F F
X101 X100
Code input data Code input data
0 1 0 1 0 1 0 1 0 1 0 1 (15)
(binary input) (BCD input)

Encoding Encoding
0 1 0 1 0 1 0 0 1 1 1 1
(no conversion) (BCD to binary)
(no inversion) (no inversion)

Conversion at Conversion at
operation and Convert binary operation and Convert binary
monitoring functions to decimal monitoring functions to decimal
(for display) (for display)

Display (PV) 21 Display (PV) 15

D030804E.ai

Figure Encoding When “No Conversion” and “BCD Conversion” are Specified

When 6 points from %Z011101 are specified for CI001, %Z011101 to%Z011106 become the
code input data and %Z011101 is always the most significant bit.
Assuming that current ON/OFF statuses of %Z011101 to %Z011106 are as shown in the figure
above, PV (CI001) =15 when the BCD conversion is specified, and PV (CI001) =21 when the non
conversion is specified. In the above examples, when the BCD conversion is specified, the upper
2 bits (%Z011101, 011102) represent the ones places of 10, and the lower 4 bits (%Z011103 to 6)
does the zeros places of 10.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.8 Code Input Block (CI)> D3-216
For the BCD conversion, when the input signal patterns are meaningless as BCD code, the block
status is set to the input code error (ERR). This “meaningless pattern as BCD code” refers to the
input signal pattern indicating a value other than 0 to 9.
The figure below shows examples of when the block status is in the normal status (NR), and
when it is meaningless.

Upper digit Lower digit Upper digit Lower digit

0101 0010 0101 1011

BCD handles
values
5 2 5 B 0 to 9 only

52 Meaningless

Block status = NR Block status = ERR

D030805E.ai

Figure BCD Code Examples

The encoding function is set by the Function Block Detail Builder.

• Code conversion:
Select from “No” and “BCD.”
“No” is binary input, “BCD” is binary coded decimal input.
Default is “No.”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.8 Code Input Block (CI)> D3-217

n Input Data Status Testing Function

The input data status testing function investigates the conditions listed below for the encoded
input code value (PV), and determines the block status.
The following lists the conditions for the input code value (PV) for determining the block status.
• 0≤PV<PH-DL:
Normal status (NR)
• PH-DL≤PV<PH:
Low limit alarm status (LO)
• PV≥PH:
High limit alarm status (HI)
PH: Input high limit setpoint
DL: Low limit alarm status setting range

The figure below shows the graphed conditions of the input code value (PV).
PV

PH

DL

NR LO HI
D030806E.ai

Figure Relationship Between Input Code Value (PV) and Block Status

The input data status testing is not performed if an input code error has occurred.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.8 Code Input Block (CI)> D3-218

n Data Items – CI
Table Data Items of Code Input Block (CI)
Entry Permitted
Data Item Data Name Range Default
or Not
MODE Block mode x ----- O/S (AUT)
BSTS Block status ----- NR
PV Input code value 0 to 65535 PL
RAW Raw input data ----- -----
PH High - limit alarm setpoint x 0 to 65535 65535
DV PH – PV -PL to PH PH
DL LO width x 0 to 65535 0
PL PV scale low limit Fixed at 0. 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D030807E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted

SEE
ALSO For a list of valid block modes of the CI block, see the following:
D3.1.2, “Block Mode of Sequence Control Blocks”

n Block Status of Code Input Block (CI)

Table Block Status of Code Input Block (CI)
Block Status
Level Description
Symbol Name
3 ERR Code Error Invalid BCD code pattern
NR Normal 0 < PV < PH-DL
2 LO Low PH-DL =< PV < PH
HI High PV >= PH
D030808E.ai

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D3.9 Code Output Block (CO)> D3-219

D3.9 Code Output Block (CO)

The Code Output Block (CO) is used to convert the integer value which is set as the
setting code value (PV) from the operation and monitoring functions or other function
block into the code pattern for output to the contact output or internal switch, etc.

n Code Output Block (CO)

▼ Connection
The Code Output Block (CO) is a function block that converts the integer value which is set as
the setting code value (PV). Converting of the setting code value (PV) has “no conversion,” which
outputs the integer value in binary, and “BCD conversion,” which outputs after converting into
binary coded decimal (BCD) options.
The following is a function block diagram of the Code Output Block (CO).

Bit
PV Encoding OUT
Inversion

D030901E.ai

Figure Function Block Diagram of the Code Output Block (CO)

The table below lists connection methods and destinations for the Code Output Block (CO) I/O
terminals.
Table Connection Methods and Destinations for the Code Output Block (CO) I/O Terminals
Connection type Connection destination

I/O terminal Status Terminal

Data Data Condition Process Software Function
manipula- connecti-
reference setting testing I/O I/O block
tion on
Output Δ
OUT x x x
terminal
D030902E.ai

x: Connection available
Blank: Connection not available
Δ: Connection available only when connecting to switch blocks (SW-33, SW-91)

The conversion of a CO block setting code value (PV) to a code are performed as one-shot
execution from other function blocks such as the sequence control block.
The following describes an example of specifying the code output block one-shot execution in the
action signal column of the sequence table.
Tag name.Data item Data Action rule
CO001.ACT ON Y D030903E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.9 Code Output Block (CO)> D3-220

n Number of Output Signal

▼ Number of Bits Output
The output signal points of the Code Output Block (CO) are set by the Function Block Detail
Builder.
• Number of Bits Output:
0 to 18 points
Up to 16 points in the case of “no conversion.”
Default is 0.

n Encoding
▼ Code Conversion
The encoding function of the Code Output Block (CO) converts the integer value set as the
setting code value (PV) into bit patterns.
There exist two methods for converting an integer value into bit patterns:
• “No conversion,” converts to binary patterns.
• “BCD conversion,” converts the value into binary coded decimal (BCD) patterns.

The figure below shows examples of encoding when “no conversion” and “BCD conversion” are
specified.
No conversion BCD conversion
%SW0500 %SW0500
%SW0501 %SW0501
%SW0502 %SW0502
%SW0503 %SW0503
%SW0504 %SW0504
%SW0505 %SW0505

O O O O O O O O O O O O
F N F N F N N F F F F N
F F F F F F F
D030904E.ai

Figure Encoding When “Non Conversion” and “BCD Conversion” are Specified

When six points from %SW0500 are specified for CO001, %SW0500 to %SW0505 will be
subject to the code output. If the code conversion is specified as “No Conversion” and code
output is performed with the settings of CO0001 and PV=21, the ON/OFF statuses of the
%SW0500 to %SW0505 will be as the above left figure while for “BCD Conversion,” the statuses
of the switches will be as the above right figure.
The encoding function is set by the Function Block Detail Builder.
• Code Conversion:
Select from “No” and “BCD.”
“No” yields binary output, “BCD” yields binary coded decimal output.
Default is “No.”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.9 Code Output Block (CO)> D3-221

n Bit Inversion
▼ Bit Inversion
The bit inversion of the Code Output Block (CO) inverses the ON/OFF status of the signals to be
output. If the bit inversion is specified as “No,” the ON/OFF status will not be inversed.
The bit inversion is set by the Function Block Detail Builder.
• Bit Inversion:
Select from “No” or “Yes.”
Default is “No.”

n Set Data Status Testing Function

The set data status testing function investigates the conditions listed below for the set code value
(PV), and determines the block status.
The following lists the conditions for the set code value (PV) for determining the block status.
• 0≤PV<PH-DL:
Normal status (NR)
• PH-DL≤PV<PH:
Low limit alarm status (LO)
• PV≥PH:
High limit alarm status (HI)
PH: Alarm high limit value
DL: Low limit alarm status (LO) setting range

The figure below shows the graphed conditions of the set code value (PV).
PV

PH

DL

NR LO HI
D030905E.ai

Figure Relationship between Set Code Value (PV) and Block Status

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.9 Code Output Block (CO)> D3-222

n Signal Output Function

The signal output function outputs bit patterns to the continuous elements of the output
destination for the number of output signal points, starting with the element specified in the OUT
terminal.
When the output destination is the contact output, if there exists even one output with a hardware
failure, the entire signal will not be output. When the hardware failure occurs, the data status of
the set code value (PV) becomes the output fail status (PTPF), and the previous set code value
is held as the set code value (PV).
When a value that is too large to express with the specified output signal points is set for the set
code value (PV), only the code patterns of the available output signal points are output. This is
not handled specifically as an error.
The figures below show an example of insufficient output signal points.
Input data PV=175

Non conversion, no inversion

Reverse code conversion

1 0 1 0 1 1 1 1
(Decimal to binary)

Significant digits

Four output signal points

Output 1 1 1 1

D030906E.ai

Figure Encoding Example for Four Output Signal Points

n Data Items – CO
Table Data Items of Code Output Block (CO)
Entry Permitted
Data Item Data Name Range Default
or Not
MODE Block mode x ----- AUT
BSTS Block status ----- NR
PV Setting code value x 0 to 65535 0
PH High - limit alarm setpoint x 0 to 65535 65535
DV PH – PV -PL to PH PH
DL LO width x 0 to 65535 0
PL PV scale low limit Fixed at 0. 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D030907E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted

SEE
ALSO For a list of valid block modes of the CO block, see the following:
D3.1.2, “Block Mode of Sequence Control Blocks”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D3.9 Code Output Block (CO)> D3-223

n Block Status of Code Output Block (CO)

Table Block Status of Code Output Block (CO)
Block Status
Level Description
Symbol Name
NR Normal 0 =< PV < PH-DL
2 LO Low PH-DL =< PV < PH
HI High PV >= PH
D030908E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.10 Relational Expression Block (RL)> D3-224

D3.10 Relational Expression Block (RL)

The Relational Expression Block (RL) is used to judge the numerical relationship or the
logical product of two data.

n Relational Expression Block (RL)

▼ Relational Expression
The Relational Expression Block (RL) is executed during the condition testing process for a
sequence control block such as a sequence table, or during the condition testing process for
the calculation block. It tests for the numerical relationship or the logical product of two data,
according to the relational expression within the Relational Expression Block (RL), and returns
the result of whether or not it matches the conditions to the calling function block.
The following is a function block diagram of the Relational Expression Block (RL).

Q01 RV01
(X01)
Q02 RV02

Q31 RV31
(X16)
Q32 RV32

D031001E.ai

Figure Function Block Diagram of Relational Expression Block (RL)

The table below lists connection methods and destinations for the Relational Expression Block
(RL) I/O terminals.
Table Connection Methods and Destinations for Relational Expression Block (RL) I/O Terminals
Connection type Connection destination

I/O terminal Status Terminal

Data Data Condition Process Software Function
manipula- connecti-
reference setting testing I/O I/O block
tion on
Data input Δ
Q01 to Q32 x x x x
terminal
D031002E.ai

x: Connection available
Blank: Connection not available
Δ: Connection available only when connecting to switch blocks (SW-33, SW-91)

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.10 Relational Expression Block (RL)> D3-225
The test objects are either two process data, or one process data and one constant data. One
Relational Expression Block (RL) can handle 16 sets of relational expressions, thus it can handle
32 individual data.
The figure below shows a connection example to another function block.
Process I/O
%Z011101 Q01 RV01=%Z011101.PV
(X01)
Q02 RV02=CALCU1.CPV1

Q01 Calculation J01

block
CALCU1 OUT

Q31 RV31=CALCU1.CPV
(X16)
%SW0500 Q32 RV32=%SW0500.PV
Software I/O
Relational Expression Block
D031003E.ai

Figure Connection with Another Function Block

n Process Timing
The process timing of RL block is only based on one-shot start.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.10 Relational Expression Block (RL)> D3-226

n Relational Expression Data

With a single set of relational expressions, either two process data or one process data and one
constant data can be judged. Other referable data such as process I/O, software I/O and function
block data can be specified as the process data. Always specify the process data on the left-hand
side of the relational expression. For the right-hand side of the relational expression, process
data or constant data can be specified. Special data such as character strings, connection data
and pulse input cannot be used for the calculation.
Constants for the constant data are set by the Function Block Detail Builder.

The following shows the relationship expression between process data and process data.

FIC101.PV: FIC102.PV

FIC101. PV (RV01)
X01
FIC102. PV (RV02)

D031004E.ai

Figure Relationship Expression between Process Data and Process Data

The following shows the relationship expression between process data and constant data.

FIC101.PV: 123.4

FIC101. PV (RV03)
X02
123.4 (RV04)

D031005E.ai

Figure Relationship Expression of Process Data and Constant Data

The following shows an entry example to the condition signal column in the sequence table when
testing for RV01 > RV02 shown in the first example above.

RL0100.X01.GT -------- Y

The function block indicated by RL0100 represents the Relational Expression Block (RL).
Use the Function Block Detail Builder to pre-define the data expressed by relational expression
data RV01 and RV02 as X (the first data) and Y (the second data).
• X, Y:
Character string of up to 34 standard width characters.
Describe the process data or a real number.
Default is blank.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.10 Relational Expression Block (RL)> D3-227

n Relational Expression Type

▼ Accept BAD data
When the Relational Expression Block (RL) is referenced from other function blocks for condition
testing, relational operation for the relational expression specified in X01 through X16 is
performed as a one-shot operation. There exist two types of relational expressions: the numerical
comparison operation between two data, and the logical product operation of two data. For the
relational expression type, delimit the two data with an operator and preset by each relational
expression using the Function Block Detail Builder.
• Operator: Select from “CMP” and “AND”

The table below lists the operators and description of each operation.
• CMP
Numerical comparison:
Performs the numerical comparison of two data. It tests if the relationship matches the
relational expression and returns a logical value.
• AND
Logical product:
Computes logical products of two data by bit. It returns true if at least one bit satisfies the
relational expression.

The following describes an example of performing the logical product operation against two data.

%CI0100.PV & %CI0101.PV

CI0100 and CI0101 represent the Code Input Block (CI). The above example computes the
logical product of each corresponding bit of the two input code values (PV). If both corresponding
bits include 1, it returns true (1) to the calling function block.
The two data types are converted into floating point, if the relation operation type is numerical
comparison, or are converted to the unsigned integer type if the relational operation type is the
logical product.

Up to 24 alphanumeric character can be added to the 16 sets of relational expressions as

comments so that the operation is being performed by each relational expression can be
indicated in text.
When the data status of the data received for the connected destination is bad (BAD), whether
to use the data for the relational expression or use the previous good data can be set on the
function block detail builder.
• Accept BAD data:
Choose [No] or [Yes].
The default setting is [No].
If [No] is selected, the relational expression will abandon the bad data and use the previously
used good data. However, since the relational expression is not running all the time, the
previously used data may be obsolete.
If [Yes] is selected, the data is used by the relational expression even the data status is bad.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.10 Relational Expression Block (RL)> D3-228

n Range of Operation
The Relational Expression Block (RL) performs the operation only for the specified relational
expression during each one-shot execution from other function blocks. When it is not called
as one-shot, the previous values remain for the relational expressions that have not been
performed.

n Data Items – RL
Table Data Items of Relational Expression Block (RL)
Entry Permitted
Data Item Data Name Range Default
or Not
RV01 to RV32 Relational expression data ----- 0
AV01 to AV32 AND data ----- 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D031006E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D3.11 Resource Scheduler Block (RS)> D3-229

D3.11 Resource Scheduler Block (RS)

The Resource Scheduler Block (RS) is used to manage the utilization of limited plant
resources.

n Resource Scheduler Block (RS)

When the resource usage requests exceed the number of usage limit for the Resource
Scheduler Block (RS), the usage requests are added to the queue and placed in usage request
waiting status. After that, it issues permission in sequence as the resource becomes available.
Although there are no I/O terminals for the Resource Scheduler Block (RS), data inside the block
may be referenced and set.
The following is a function block diagram of the Resource Scheduler Block (RS).

Permission (PM) Maximum

permissible
......... number
1 32
PMH
Usage request (RQ)
......... (0 to 32)

1 32

D031101E.ai

Figure Function Block Diagram of Resource Scheduler Block (RS)

Issuing the usage request command and the usage request cancel command, referencing and
setting the maximum permissible number and referencing the permission status of the Resource
Scheduler Block (RS) may be performed from the sequence control blocks or calculation block.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.11 Resource Scheduler Block (RS)> D3-230
The figure below shows an example of the lorry shipping system with a built-in pump count
control.

Spot
P (Lorry shipping alarm)

Maximum
Pump count permissible number Request
Resource
control setting scheduler Spot control
Permission

D031102E.ai

Figure Example of Lorry Shipping

In the above system example, the number of spots that can be used simultaneously for product
shipment is restricted by the total flow rate of the products that flow into the spots. In such cases,
the Resource Scheduler Block (RS) is used to control the usage status of each spot for shipping
control. By receiving a shipping request (usage request) from each spot, the Resource Scheduler
Block (RS) issues a sequential shipping permission (usage permission) to the first entry in the
FIFO (First In First Out) queue.
In the above system example, the product total flow rate that restricts the number of spots (the
maximum permissible number) that can be used simultaneously is determined by the number
of operating pumps. Therefore, the maximum permissible number (PMH) for the Resource
Scheduler Block (RS) is set via the function block that controls the pump count.

n Process Timing
The process timing of RS block is only based on one-shot start.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.11 Resource Scheduler Block (RS)> D3-231

n Usage Request Control Function

The usage request control function controls the request queue, usage request status (RQ01
to RQ32) and permission (PM01 to PM32) upon receiving the usage request command or the
usage request cancel command. In order to use the Resource Scheduler Block (RS) from the
sequence control block or the general-purpose calculation block, it is necessary to predefine the
identification number for each of the requesters for the resources. The requesters are identified
by this number when referencing the usage request command, usage request cancel command,
usage request (RQnn) and permission (PMnn). The numeric portion (noted as nn in this document)
of the data item name for the usage request (RQnn) and permission (PMnn) is used as the
identification number.

l Usage Request Command

The usage requester sends a usage request command to the Resource Scheduler Block
(RS). Only a single request at a time can be accepted from the same requester. The requester
which has already been given permission or is waiting in the usage request queue cannot send
additional requests. Two or more simultaneous requests are ignored.
When the entire resource group usage request command is received, the Resource Scheduler
Block (RS) processes the usage requests in the ascending order of request numbers. Since
the permission is restricted by the maximum permissible number (PMH), the remaining usage
requests are placed in the queue for permission.
The following describes operations when the number of usage requests is equal to or greater
than the maximum permissible number (PMH), or when less than the maximum permissible
number (PMH).
• When usage request number ≤ Maximum permissible number
It gives permission for the request by setting 1 to the corresponding usage request (RQnn)
and permission (PMnn).
• When usage request number > Maximum permissible number
Although the corresponding usage request (RQnn) is set to 1, it cannot give permission
because there are not enough resources for requests. It adds the identification number of
the requester to the queue, while the corresponding permission (PMnn) is kept at 0.

l Usage Request Cancel Command

It is necessary for the requester to issue the usage request cancel command when it has used all
the resources, or when canceling the usage request. The Resource Scheduler Block (RS) resets
the corresponding usage request (RQnn) and permission (PMnn) to 0 upon receiving a usage
request cancel command. If there is an entry for the corresponding usage request in the queue, it
is deleted from the queue.
For a cancel command for a permitted usage request, if there is a request for permission in the
queue, the request is deleted after setting the permission (PMnn) of the usage request that is
stored at the head of the queue. If the requester sends an entire resource group usage request
cancel command, the current usage requests are all reset to 0.

l Monitoring of the Resource Usage Request Status

The requester of the resource usage monitors the resource usage availability by referencing the
permission (PMnn) of the Resource Scheduler Block (RS). By referencing the usage requests of
the Resource Scheduler Block (RS), the status of resource usage requests can be grasped.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.11 Resource Scheduler Block (RS)> D3-232

n Maximum Permissible Number Control Function

The number of resources that can be used simultaneously is set to the maximum permissible
number (PMH) from other function blocks. When the maximum permissible number setting is
changed, the maximum permissible number control function manipulates the permission status
of the resources by responding to an increase/decrease in the maximum permissible number
(PMH), as described below.

l When the Maximum Permissible Number is Increased.

It increases the number of permissions that can be provided simultaneously for the increased
maximum permissible number.

l When the Maximum Permissible Number is Decreased.

It will not give out new permissions until the number of current resource usage becomes less
than the maximum permissible number. For usage requests currently permitted, it holds the
permission status until the usage request cancel command is received.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.11 Resource Scheduler Block (RS)> D3-233

n Control Example with the Resource Scheduler Block (RS)

The figure below shows a tank level control example using the Resource Scheduler Block (RS)
RS001 and Sequence Table Block (ST16).

Source tank

Valve 1 2 3 4 5 Valve 10

Tank 1 2 3 4 5 Tank 10

LO LO LO LO LO LO

D031103E.ai

Figure Tank Level Control Example

This control includes ten processes that open and close the valves. These processes open valve
nn if level LO of the tank n becomes ON, and then close valve nn if the level LO is released after
waiting for the level being recovered. However, no more than three valves can be opened at a
time. Also, the valves are opened in the order in which the level LO is reached.
The identification numbers of these processes are defined as in the table below.
Table Detecting Input and Identification Number
Identification
Contact input to detect the tank level LO
number
DI0001 1
DI0002 2
DI0003 3
: :
DI00010 10
D031104E.ai

Call the usage requester, usage request and permission by the corresponding number (1 to 10)
of each process identification number.
• Usage Requester 1 (DI001 : Tank 1’s level is LO)
• Usage Request 1
(Usage request 1 that has been submitted by usage requester 1 : Wants to open valve 1.)
• Permission 1 (Permission for usage request 1 : OK to open valve 1.)

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.11 Resource Scheduler Block (RS)> D3-234
Assume that DI003, DI005, DI002 and DI006 become ON, in this respective order, when
the maximum permissible number is 3. The rules 4, 6, 3 and 7 of sequence table block 1 are
satisfied, and usage requests 3, 5, 2 and 6 are entered into the resource schedule block (RS)
RS001 in this order. Because the maximum permissible number is 3, the resource schedule
block (RS) RS001 issues permissions to usage requests 3, 5 and 2 only, within the same scan.
Tag name. Rule number
Data item Name. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21
Data Comment
DI0001.PV.ON Usage requester 1 Y Y N
DI0002.PV.ON Usage requester 2 Y Y N
DI0003.PV.ON Usage requester 3 Y Y N
DI0004.PV.ON Usage requester 4 Y Y N
DI0005.PV.ON Usage requester 5 Y Y N
DI0006.PV.ON Usage requester 6 Y Y N
DI0007.PV.ON Usage requester 7 Y Y N
DI0008.PV.ON Usage requester 8 Y Y N
DI0009.PV.ON Usage requester 9 Y Y N
DI0010.PV.ON Usage requester 10 Y Y N
RS0001.ACT.OFF Entire resource group usage Y
request cancel command
RS0001.ACT.ON Entire resource group Y
usage request command
RS0001.RQ01.1 Usage request command 1 Y
RS0001.RQ02.1 Usage request command 2 Y
RS0001.RQ03.1 Usage request command 3 Y
RS0001.RQ04.1 Usage request command 4 Y
RS0001.RQ05.1 Usage request command 5 Y
RS0001.RQ06.1 Usage request command 6 Y
RS0001.RQ07.1 Usage request command 7 Y
RS0001.RQ08.1 Usage request command 8 Y
RS0001.RQ09.1 Usage request command 9 Y
RS0001.RQ10.1 Usage request command 10 Y
RS0001.RQ01.0 Usage request cancel command 1 Y
RS0001.RQ02.0 Usage request cancel command 2 Y
RS0001.RQ03.0 Usage request cancel command 3 Y
RS0001.RQ04.0 Usage request cancel command 4 Y
RS0001.RQ05.0 Usage request cancel command 5 Y
RS0001.RQ06.0 Usage request cancel command 6 Y
RS0001.RQ07.0 Usage request cancel command 7 Y
RS0001.RQ08.0 Usage request cancel command 8 Y
RS0001.RQ09.0 Usage request cancel command 9 Y
RS0001.RQ10.0 Usage request cancel command 10 Y
D031105E.ai

Figure Sequence Table Block (ST16) used for Tank Level Control (1/2)

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.11 Resource Scheduler Block (RS)> D3-235
Tag name. Rule number
Data item name. 1 2 3 4 5 6 7 8 9 10
Data Comment

RS0001.PM01.1 Usage request permission 1 permitted Y

RS0001.PM02.1 Usage request permission 2 permitted Y
RS0001.PM03.1 Usage request permission 3 permitted Y
RS0001.PM04.1 Usage request permission 4 permitted Y
RS0001.PM05.1 Usage request permission 5 permitted Y
RS0001.PM06.1 Usage request permission 6 permitted Y
RS0001.PM07.1 Usage request permission 7 permitted Y
RS0001.PM08.1 Usage request permission 8 permitted Y
RS0001.PM09.1 Usage request permission 9 permitted Y
RS0001.PM10.1 Usage request permission 10 permitted Y
DO0001.PV.L Valve 1 open command Y

DO0002.PV.L Valve 2 open command Y

DO0003.PV.L Valve 3 open command Y
DO0004.PV.L Valve 4 open command Y
DO0005.PV.L Valve 5 open command Y
DO0006.PV.L Valve 6 open command Y
DO0007.PV.L Valve 7 open command Y
DO0008.PV.L Valve 8 open command Y
DO0009.PV.L Valve 9 open command Y
DO0010.PV.L Valve 10 open command Y
D031106E.ai

Figure Sequence Table Block (ST16) used for Tank Level Control (2/2)

Usage request

Waiting for Permission

Usage request 6

Usage request 5 Permission 2

Maximum permissible number: 3
Usage request 4 Permission 5

Usage request 3 Permission 3

D031107E.ai

Figure Resource Scheduler Block (RS) Process

The sequence table block 2 indicates which usage request a permission is issued to.
The following describes an example of specifying the reference of permission status for usage
request 3 into the condition symbol column of the sequence table.
Tag name.Data item Data Action rule
RS0001.PM03 1 Y D031108E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.11 Resource Scheduler Block (RS)> D3-236
“During condition signal (PM03)” corresponds to the usage request (RQ03). In this example,
since permissions 3, 5 and 2 received permissions, the rules 3, 5 and 2 of Table 2 are satisfied
and the contact outputs are outputted (valve open) according to the descriptions in the action
signal column.
In order to issue permission for usage request 6 that is waiting in the queue, it is necessary for
the condition signal status of any one of the usage requests 3, 5 and 2 to be unsatisfied, and the
usage request of the same identification number that became false must be reset.

IMPORTANT
It is always necessary to issue the usage request cancel command, because the usage request
is not reset automatically, even after permission is given for the usage request. When the usage
request signal is an internal switch, turn off the internal switch (when the ON status means the
usage request state) for the next request after permission is sent, then issue the usage request
cancel command.

If the usage request that has been permitted is reset, there will be one vacancy for permission,
and permission is given to usage request 6. The following describes an example of setting
permission 2 to be reset in the condition signal column of the sequence table.
Tag name.Data item Data Action rule
RS0001.RQ02 0 Y D031109E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.11 Resource Scheduler Block (RS)> D3-237
l When Issuing the Entire Resource Group Usage Request Command after
Issuing the Entire Resource Group Usage Request Cancel Command
When the entire resource group usage request cancel command and the entire resource group
usage request command are sent, based on rule 1 of sequence table block 1, the currently
issued permissions are all reset, then all the usage requests are sent. Usage requests 1 to 10
are stored in ascending order in the resource scheduler. At this time, usage requests 1, 2 and 3
will be given permission within the same scan, and usage requests 4, 5, 6, 7, 8, 9 and 10 will be
placed in the queue for permission.
The figure below shows the status of usage request storage.
Usage request

Usage request 10

Usage request 9

Waiting for permission

Usage request 4

Usage request 3 Permission 3

Maximum permissible number: 3
Usage request 2 Permission 2

Usage request 1 Permission 1

D031110E.ai

Figure Storage Status of Usage Request

l When Issuing the Entire Resource Group Usage Request Command

Without the Entire Usage Request Cancel Command
When the entire resource group usage request command is issued without the entire resource
group usage request cancel command, the current usage requests that have been permitted
remain as they are, and the other usage requests are stored in the ascending order.
The figure below shows the storage status of the usage requests.
Usage request

Usage request 10

Usage request 9

Ascending order

Usage request 4

Usage request 1
Waiting for permission
Usage request 6

Usage request 2 Permission 2

Maximum permissible number: 3
Usage request 5 Permission 5 No change

Usage request 3 Permission 3

D031111E.ai

Figure Storage Status of Usage Request

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.11 Resource Scheduler Block (RS)> D3-238
l Canceling the Usage Request
The following shows an example of specifying the cancellation of usage request 2. This is the
same specification as that for resetting the usage request.
Tag name.Data item Data Action rule
RS0001.RQ02 0 Y D031112E.ai

l Changing the Maximum Permissible Number

The following are the methods to change the maximum permissible number to 4.
• When changing on the operation and monitoring functions
Input 4 for the data type PMH in the tuning view.
• When changing from the Sequence Table Block (ST16, ST16E)
Enter as below in the action signal column of the sequence table block.
Tag name.Data item Data Action rule
RS0001.PMH 4 Y D031113E.ai

n Data Items – RS
Table Data Items of Resource Scheduler Block (RS)
Entry Permitted
Data Item Data Name Range Default
or Not
MODE Block mode x ----- O/S (AUT)
RQ01 to RQ32 Usage request x 0/1 0
PM01 to PM32 Usage permission 0/1 0
PMH Maximum permission number x 0 to 32 32
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D031114E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted

SEE
ALSO For a list of valid block modes of the RS block, see the following:
D3.1.2, “Block Mode of Sequence Control Blocks”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D3.12 Valve Monitoring Block (VLVM)> D3-239

D3.12 Valve Monitoring Block (VLVM)

The Valve Monitoring Block (VLVM) is used to monitor whether the final control element
(valve) is operating properly.

n Valve Monitoring Block (VLVM)

▼ Valve Monitor
The Valve Monitoring Block (VLVM) handles 16 sets of input signals independently, performing
valve operation monitoring and message output for each input signal. A set of input signals is
comprised of a combination of one point of valve contact output and one point (or two points)
of limit switch. Also, when an error occurs in any set of the 16 sets, the message output can be
extracted from the representative message output terminal (J17).
The figure below shows the function block of the Valve Monitoring Block (VLVM).

Q01 PV01 J01

Action
Q02 verification timer J02

Valve output monitoring

Q31 PV16 J16

Action
Q32 verification timer J17
PVR Representative message
output terminal
D031201E.ai

Figure Function Block Diagram of the Valve Monitoring Block (VLVM)

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.12 Valve Monitoring Block (VLVM)> D3-240
The table below lists connection methods and destinations for the Valve Monitoring Block (VLVM)
I/O terminals.
Table Connection Methods and Destinations for Valve Monitoring Block (VLVM) I/O Terminals
Connection type Connection destination

I/O terminal Status Terminal

Data Data Condition Process Software Function
manipula- connecti-
reference setting testing I/O I/O block
tion on
Q01, Input terminal for
Q03, ..., valve contact x Δ x x
Q31 output
Q02,
Limit switch input Δ
Q04, ..., x x x
terminal
Q32
J01 Individual message
x x x
to J16 output terminal
Representative
J17 message output x x x
terminal
D031202E.ai

x: Connection available
Blank: Connection not available
Δ: Connection available only when connecting to switch blocks (SW-33, SW-91)

Connect input terminals (Q01, Q03, ..., Q31) with the contact output leading to the valve.
Connect input terminals (Q02, Q04, ..., Q32) with the contact input (signals from the limit switch)
that indicates the open/close status of the valve. These two types of inputs (for example, Q01
and Q02) are compared and any mismatch present is detected. If a mismatch is detected as a
result of comparison, the valve abnormal state (PVnn) is set to 1, and messages specified in the
output terminal such as the annunciator message (%AN) and print message with data (%PR) are
output.
The figure below shows an example of monitoring the valve that has one point of contact output
(open signal) and one point of limit switch input (open answer-back) using the Valve Monitoring
Block (VLVM).
Valve monitor block

Contact output monitor DO 0001 Q01 Action

monitoring PV01 J01 %AN,
DI 0001 timer %PR etc.
Limit switch input Q02
(open answerback)

Q03 Action
monitoring PV02 J02
Q04 timer

On/off valve
(with a limit switch)
D031203E.ai

Figure Connection of Valve Monitoring Block (VLVM)

n Process Timing
The process timing of VLVM block is only based on periodical start period. The periodic start
period is based on basic scan period only.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.12 Valve Monitoring Block (VLVM)> D3-241

n Valve Monitor Limit Switch Action

There are three types of limit switch actions, which are the input signals of the Valve Monitoring
Block (VLVM). The type needs to be selected from the three types for each valve using the
Function Block Detail Builder.
• Triggers:
Select from “Direct,” “Reverse,” and “Both.”
The default is “Both.”

The following lists the three types of actions:

• Direct Direction
The polarities of the valve contact output and limit switch status are matched.
• Reverse Direction
The polarities of the valve contact output and limit switch status are reversed.
• Both Direction
Two points of limit switches correspond to the valve contact output. One limit switch is for
direct direction and the other is for reverse direction.
ON
Valve manipulated output
OFF

OPEN
Valve action
CLOSE

ON
Limit switch 1
OFF

ON
Limit switch 2
OFF
Positive Negative Bidirectional
action(P) action(N) action(B)
D031204E.ai

Figure Limit Switch Actions

To set the limit switch to correspond at two points for the both direction specification, assign
limit switch 1 (direct direction) to the input point specified at the input terminal, and limit switch 2
(reverse direction) to the subsequent point of the specified point.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.12 Valve Monitoring Block (VLVM)> D3-242

n Valve Output Monitor Function

This function inputs the values of contact output (valve contact output) to the contact operation
type final control element and the contact input (limit switch) that represents the open/close
status, then compares the values to detect a mismatch.
The following describes the order of operations for the valve output monitoring.
1. When a change in the valve contact output is detected, the action verification timer inside
the Valve Monitoring Block (VLVM) is started (PT = action confirmation elapsed time).
2. While the action confirmation timer is being started, the ON/OFF statuses of the valve
contact output and limit switch are compared. If the statuses match, the action confirmation
timer expires and the system proceeds to step 4.
3. If the statuses do not match after a certain period of time (action confirmation setting time
= MT) has elapsed, data value 1 indicating an error status is stored in the valve abnormal
state (PV01 to PV16).
4. After that, monitoring continues until a change occurs in the valve contact output for the next
time (i.e. until the next valve operation), and the valve abnormal state (PV01 to PV16) is
updated.

The monitor action can be specified according to the timing of comparison between the limit
switch and valve contact output. The monitor action is set using the Function Block Detail Builder.
• Monitor action
Select from “Monitoring the ON side only,” “Monitoring the OFF side only” and
“Monitoring both-side.”
The default is “Monitoring both-side.”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.12 Valve Monitoring Block (VLVM)> D3-243
The following describes each monitor action.
• Monitoring the ON Side only
This starts the action verification timer at the rise of valve contact output (OFF→ON), and
compares the statuses only while the valve contact output is ON.
• Monitoring the OFF Side only
This starts the action verification timer at the fall of the valve contact output (ON→OFF), and
compares the statuses only while the valve contact output is OFF.
• Monitoring Both Sides
This starts the action verification timer at both the rise and fall of valve contact output, and
compares the statuses while the valve contact output is either ON or OFF.
ON
Output to valve
OFF

OPEN
Valve action
CLOSE

ON
Limit switch
OFF

Difference between valve output 1

and limit switch
0

Action confirmation Action confirmation Action confirmation

setting time setting time setting time
(MT)
ON Abnormality detected message Abnormality recovered
Valve status message
(PV01 to PV16)
OFF

Normal operation Abnormal operation

D031205E.ai

Figure Valve Output Monitoring (Monitoring Both Sides)

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.12 Valve Monitoring Block (VLVM)> D3-244
The table below shows the limit switch action specifications and corresponding valve output
monitor actions.
Table List of Valve Output Monitor Action

Valve output monitoring

Limit switch Single-side Single-side
Contact
action Both-side monitoring monitoring monitoring
ON-side OFF-side
Valve
manipulated
output

Positive
Limit switch
action
(P)
Valve abnormal
state

Valve
manipulated
output

Negative
Limit switch
action
(N)
Valve abnormal
state

Valve
manipulated
output

BIdirectional
Limit 1
action
Limit 2
(B)

Valve abnormal
state

Action verification time

D031206E.ai

• When the action specification for the limit switch is “Operate in Both Direction,” set the valve
abnormal state (PVnn) to 1 if either of the two points of limit switches is a mismatch to the
valve contact output.
Also, the valve abnormal state (PVnn) becomes 0 when both of the two points match the
valve contact output.
• If the valve operation output is changed while the valve status is abnormal (PVnn=1), the
valve abnormal state (PVnn) to reset to 0.
• Upon comparing the valve output contact with the limit switch, if either of the input
destinations has a device error or the data status of input data is faulty (BAD), the valve
abnormal states (PV01 to PV16) hold the current value.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.12 Valve Monitoring Block (VLVM)> D3-245

n Representative Valve Abnormal State Detection Function

The representative abnormal state (PVR) is an information item that represents the abnormal
statuses for a maximum of 16 points of valves monitored by the Valve Monitoring Block (VLVM).
The representative abnormal state (PVR) is determined by the logical OR of individual valve
abnormal statuses (PV01 to PV16).

PV01
PV02
OR PVR=1

PV16
D031207E.ai

Figure Logical OR of Valve Abnormal States

When there is no connection to the limit switch input terminal, the limit switch input terminal is
recognized as unused, so the valve abnormal state (PVnn) is always 0.

n Message Output
VLVM block may generate an alarm message when an error occurs or recovers to notify the
operator. The message output may be specified.

l Message Output to the Individual Message Output Terminal

At the Valve Monitoring Block (VLVM), the operator can be notified of error occurrences and
recoveries of individual valves by specifying the message output to the output terminal via the
Function Block Detail Builder.
• Individual message output terminal
Specify connection with the “annunciator message,” “print message with data,” “operator
guide message” or “internal switch.” Set one point or two points for each valve.

The following describes the output timing of messages.

• Abnormality detected message
Sends the message at the timing in which the valve abnormal state (PVnn) changes from
normal to abnormal (0→1).
• Abnormality recovered message
Sends the message at the timing in which the valve abnormal state (PVnn) changes from
abnormal to normal (1→0).

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.12 Valve Monitoring Block (VLVM)> D3-246
l Message Output to the Representative Message Output Terminal
▼ Representative Message Output
At the Valve Monitoring Block (VLVM), the operator can be notified of error occurrence and
recovery of one of the 16 valves by specifying the message output to the output terminal via the
Function Block Detail Builder.
• Representative message output terminal
Specify connection with the “annunciator message,” “print message with data,” “operator
guide message” or “internal switch.” Set one point or two points for each valve.

Be careful that the abnormality recovered message is not output until all the valves return to their
normal state.
• Abnormality detected message
Sends the message at the timing in which the representative valve abnormal state (PVR)
changes from normal to abnormal (0→1).
• Abnormality recovered message
Sends the message at the timing in which the representative valve abnormal state (PVR)
changes from abnormal to normal (1→0).

l Specifying the Message Output

For the message output as a connection destination of the output terminal, the abnormality
recovered message may not be output, depending on the types of messages. The table below
shows the presence/absence status of the abnormality recovered message output.
Table Presence/Absence of Abnormality Recovered Message Output
Abnormality Abnormality
Message type
detected recovered
Annunciator message (%AN) x x
Print message with data (%PR) x Δ
Operator guide message (%OG) x
D031208E.ai

x: Present
Blank: Absent
Δ: Depends on the builder specification

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.12 Valve Monitoring Block (VLVM)> D3-247
l Annunciator Message Output
When the annunciator message is specified as the connection destination of the message
output, the abnormality detected message and the abnormality recovered message is sent with
the same number. The abnormality recovered message sent as an annunciator message is
suffixed with “ ” at the end.

l Output of the Print Message with Data

▼ Printout Message at Representative Recovery
When the print message with data is specified as the connection destination of the message
output, the abnormality detected message is sent with the specified message number.
Furthermore, only when “Yes” is specified for the “print message at representative recovery” or
“print message at recovery” using the Function Block Detail Builder, it will send the abnormality
recovered message with the subsequent number of the specified message number.
• Printout Message at Recovery:
Select from “Yes” and “No.”
The default is “No.”
• Printout Message at Representative Recovery:
Select from “Yes” and “No.”
The default is “No.”

Specify “No” for the “Printout Message at Representative Recovery” or the “Printout Message at
Recovery” when the connection destination of the message output is other than a print message
with data.

l Message Output to the Internal Switch

The internal switch (%SW) can be specified as the connection destination of the message output.
In this case, the valve abnormal state is set as the ON/OFF status of the internal switch.

l Message Suppressing
When the message suppression control switch (MCSW) is set to ON (=1), sending of all
messages specified in the output terminal is suppressed. When the message suppression
status is on, setting of the ON/OFF status for the internal switch at the output destination is not
performed. The status of the message suppressing switch (MCSW) can be changed by the
operation and monitoring functions or other function block.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D3.12 Valve Monitoring Block (VLVM)> D3-248

n Data Items – VLVM

Table Data Items of Valve Monitoring Block (VLVM)
Entry Permitted
Data Item Data Name Range Default
or Not
MODE Block mode x ----- AUT
ALRM Alarm status ----- NR
AFLS Alarm flashing status ----- 0
AF Alarm detection ----- 0
AOFS Alarm inhibition ----- 0
PV01 to PV16 Valve abnormal state 0, 1 0
PVR Representative abnormal state 0, 1 0
MCSW Message suppression control switch x 0, 1 0
MT01 to
Action confirmation setting time (seconds) x 0 to 10000 4
MT16
PT01 to PT16 Action confirmation elapsed time (seconds) 0 to 10000 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D031209E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted

SEE
ALSO For a list of valid block modes of the RS block, see the following:
D3.1.2, “Block Mode of Sequence Control Blocks”

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D4. Faceplate Blocks> D4-1

D4. Faceplate Blocks

This chapter explains the faceplate blocks and their basic control functions.
The faceplate blocks consist of analog faceplate blocks, sequence faceplate blocks and
hybrid faceplate blocks.
This chapter explains the function details of each type of faceplate blocks.

n Faceplate Blocks
A faceplate block enables multiple function blocks to be recognized as one function block. The
function blocks that execute the faceplate function are called faceplate blocks. The following
diagram shows positioning of the faceplate function in basic control functions.
FCS

Basic control
Software I/O

Regulatory control blocks Common switch

Calculation blocks Annunciator message

Sequence control blocks Sequence control message

Faceplate blocks

SFC blocks

Unit instrument blocks

Options

Valve pattern monitoring (*1)

Off-site blocks (*1)

FCS I/O Interfaces

Process I/O Communication I/O Fieldbus I/O

D040001E.ai

*1: This option can be used in FCSs except PFCS.

Figure Faceplate Blocks in Basic Control Architecture

Faceplate blocks are capable of indicating and manipulating the data of multiple function blocks
that comprise a control loop. These indications and operation functions are performed on the
instrument faceplate of the operation and monitoring window. Faceplate blocks are classified into
analog faceplate blocks, sequence faceplate blocks and hybrid faceplate blocks.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.1 Types of Faceplate Blocks> D4-2

D4.1 Types of Faceplate Blocks

Depending upon the content of indication and manipulation, faceplate blocks are
classified into three types; analog faceplate blocks, sequence faceplate blocks and hybrid
faceplate blocks.

n Analog Faceplate Blocks

Analog faceplate blocks include the following function blocks that indicate and manipulate analog
data on the instrument faceplate of the monitoring and operation window.
• Dual-Pointer Indicating Station Block (INDST2)
Used for the indication of measured values and the setting of setpoint values.
• Dual-Pointer Manual Station Block (INDST2S)
Used for the setting of setpoint values and manipulated output values.
• Triple-Pointer Manual Station Block (INDST3)
Used for the indication of measured values and the setting of setpoint values as well as
manipulated output.

n Sequence Faceplate Blocks

Sequence faceplate blocks include the following function blocks that indicate sequence phases
and manipulate switch statuses on the instrument faceplate of the operation and monitoring
window. These faceplate blocks can be used as man-machine interfaces of the sequence control
function.
• Batch Status Indicator Block (BSI)
Used for the indication of sequence phases.
• Extended 5-Push-Button Switch Block (PBS5C)
Used for the lamp indication and operation of five push buttons.
• Extended 10-Push-Button Switch Block (PBS10C) (*1)
Used for the lamp indication and operation of ten push buttons.
*1: Extended 10-push-button switch block (PBS10C) can be used in FCSs except PFCS.

n Hybrid Faceplate Blocks

A hybrid faceplate block has the functions of an analog faceplate block and those of a sequence
faceplate block.
The function blocks that are classified as hybrid faceplate blocks include the Extended Hybrid
Manual Station Block (HAS3C). The Extended Hybrid Manual Station Block (HAS3C) has the
functions of Triple-Pointer Manual Station Block (INDST3) and those of the Extended 5-Push-
Button Switch Block (PBS5C).

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.1 Types of Faceplate Blocks> D4-3

n Example of Using the Faceplate Block

The following example shows how to use an analog faceplate block.

ST16
PID PV
TIC102 T1 IN TC 100
INDST3
TC100
IN1
AUT
CALCU IN2 NR
X103 F1 IN 100.0

SV

IN1 CALCU PID

F2 IN FIA100 FIC101 V OUT
PV
0.0
IN2 IN3

MV T1 IN

P2 IN T2 IN V OUT
D040101E.ai

Figure Example of Using the Faceplate Block

In the above example, the data items of TC100 (INDST3 block), TIC102 (PID controller block)
and FIC101 (PID controller block) are connected. The connected data items are shown below.
• PV of TC100 and PV of TIC102
• SV of TC100 and SV of TIC102
• MV of TC100 and MV of FIC101
• MODE of TC100 and MODE of FIC101.

By connecting these data items, the following functions can be realized.

l Indication of Data Items

The values of TC100 data items are changed to the values of the connected data items.
• The value of the data item PV of TC100 is changed to that of TIC102’s PV.
• The value of SV is changed to that of TIC102’ SV, and the value of MV is changed to that of
FIC101’s MV.
• The block mode of MODE is changed to that of FIC101’s MODE. However, the mode will
not change to O/S.

l Setting Operation
When a value is set to any data item of TC100 from the instrument faceplate or other setting
source, the value of the connected data item will be changed.
• When SV of TC100 is changed, SV of TIC102 will change to the same value.
• When MV of TC100 is changed, MV of FIC101 will change to the same value.
• When the block mode of TC100 is changed, MODE of FC101will change to the same block
mode. However, the mode will not change to O/S.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.2 Push Button Operation of Faceplate Blocks> D4-4

D4.2 Push Button Operation of Faceplate Blocks

There are three types of push buttons common to Sequence faceplate blocks and Hybrid
faceplate blocks: momentary button, alternate button and radio button.

n Momentary Button Action

When button operation is performed by the operator, the manipulated command value (MVnn)
changes to “1 (ON)” for a period specified as the output time span in the unit of scan cycle. When
the specified period is elapsed, the value returns to “0 (OFF)” automatically. The following figure
shows the relationship between the manipulated command value (MVnn) and the output value
when button operation is performed.
Block processing
timing Button operation

ON

MVnn OFF

ON

Output OFF

Time
t 2t 3t 4t 5t
t = Scan period
Output time span
D040201E.ai

Figure Action When the Momentary Button is Specified

The manipulated command value (MVnn) remains ON for a period of time equivalent to a multiple
of the scan period.
If button operation is performed while the manipulated command value (MVnn) is ON, the value
will remain ON through the specified scan periods from the time when the last button operation
was performed.
The following figure shows the action of the momentary button when button operation is
performed while the manipulated command status is ON.
Block processing
timing Button operation Button operation

ON

MVnn OFF

ON

Output OFF

Time
t 2t 3t 4t 5t
t = Scan period
Output time span
D040202E.ai

Figure When Button Operation is Performed While the Manipulated Command Status is ON

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.2 Push Button Operation of Faceplate Blocks> D4-5

n Alternate Button Action

When button operation is performed by the operator, the manipulated command value (MVnn)
changes to OFF if it was ON, and to ON if it was OFF. The following figure shows the relationship
between the manipulated command value (MVnn) and the output value when button operation is
performed.
Block processing
timing Button operation Button operation

ON

MVnn OFF

ON

Output OFF

Time
t 2t 3t 4t 5t
t = Scan period
D040203E.ai

Figure Action When the Alternate Button is Specified

When multiple button operations are performed in a single scan period, the manipulated
command value (MVnn) changes with each button operation. The change in the manipulated
command value (MVnn) will be executed immediately after the operation, while the output of the
manipulated command value (MVnn) will be executed during block processing. It must be noted
that the change in manipulated command value (MVnn) will not be transmitted to the storage
destination, even when multiple button operations are performed in a single scan period.
The following figure shows the relationship between the manipulated command value (MVnn) and
the output value when multiple button operations are performed in one scan period.
Block processing
timing Button operation Button operation

ON

MVnn OFF

ON

Output OFF

Time
t 2t 3t 4t 5t
t = Scan period
D040204E.ai

Figure When Multiple Button Operations are Performed in One Scan Period

n Radio Button Action

When the operator pushes one button (MVnn) ON, all other manipulated command values (MVnn)
will be turned OFF forcibly.
Switches that are turned OFF forcibly while the “radio button” is in use are limited to those that
support the button operation function.
When the “radio button” is in use, even a switch whose operation disable status is ON will be
turned OFF forcibly once other switches are turned ON.
Depending upon the operation timing, multiple switch statuses may turn ON simultaneously. In
this case, only the switch with the smallest number of manipulated command values (MVnn) that
are ON will remain so. All other switch statuses will be turned OFF forcibly.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.3 Block Mode and Status of Faceplate Blocks> D4-6

D4.3 Block Mode and Status of Faceplate Blocks

The block mode and status of the faceplate block are different from the block mode and
status of other function blocks. In this section, the block mode and status that are specific
to the faceplate block are explained.

SEE
ALSO For more information about block mode and status, see the following:
C6 “Block Mode and Status”

n The Block Mode of the Faceplate Block

The block mode of a faceplate block agrees with the connected destination function block, except
for the out of service (O/S) mode.
The faceplate block periodically refers to the connected destination function block to keep
the mode agree with each other. On the other hand, if the block mode of the faceplate block
changes, the connected destination function block changes too.

n The Block Status of the Faceplate Block

The block status of a faceplate block agrees with the connected destination function block.
The faceplate block periodically refers to the connected destination function block to keep the
status agree with each other.

n The Alarm Status of the Faceplate Block

The alarm status of a faceplate block agrees with the connected destination function block,
except for the connection failure alarm (CNF) or normal (NR) status.
The faceplate block periodically refers to the connected destination function block to keep the
alarm status agree with each other.

n The Data Status of the Faceplate Block

In the faceplate block, the three types of analog data, namely, the process variable (PV), setpoint
value (SV), and manipulated output value (MV), are treated as “data with data status.” The data
status of the faceplate block agrees with the data status of the connected destination function
block. If there is no block connected, the data status is determined by the status of its own data.

n The Status Change Message

In the faceplate block, a status change message is sent when a change has occurred to the block
mode or block status.
Also, the status change message bypass function is provided to suppress the status change
message. The status change message bypass action is determined by the value which is
specified in the builder of the block itself, regardless of the existence or absence of a block mode
connection or block status connection.
However, in the absence of a block status connection, a status change message is sent even
when the block status does not change if the same status as the current one has been specified
as the block status.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.3 Block Mode and Status of Faceplate Blocks> D4-7

D4.3.1 Block Mode of Faceplate Blocks

The block mode of a faceplate block agrees with the block mode of connected destination
function block, except for the off-service (O/S) mode.
Depending on the existence of the block mode connection, the faceplate block takes
different action when the block mode is changed.

n Behavior of Faceplate with Block Mode Connection

The faceplate block periodically refers to the connected destination function block to keep the
block mode agree with each other. The faceplate block periodically refers to the connected
destination function block to keep the block mode agree with each other. On the other hand, if
the block mode of the faceplate block is changed, the block mode of the connected destination
function block changes too.
When connect with other blocks, the data item MODE is specified of the destination tag to
the terminal (JMOD). If a data item other than MODE is specified, it may not work properly. A
faceplate block cannot be connected to another faceplate block.

l The Block Mode that can be Established

The types of the block mode (AUT, MAN, etc.) that can be established for the faceplate block
depend on the types of the block mode that can be connected as destination block. Whether or
not a mode change is possible also depends on whether the mode change is enabled or not of
the connected destination block.

l Off-Service (O/S) Mode Related Actions when Block Mode Change

When link the block mode change of the faceplate block to the out of service (O/S) mode of
connected destination block, the faceplate takes different action. The out of service (O/S) mode
related actions are specified as follows:
Table Block Mode Change Action Specifications Regarding O/S (1/2)
Change operation Action of the connection
at the faceplate block destination block
O/S→MAN O/S→MAN
O/S→MAN AUT→MAN
O/S(MAN)→MAN O/S→MAN
O/S(MAN)→O/S No change
MAN→O/S No change
D040301E.ai

Note: MAN indicates a mode other than O/S. Actions are the same for all mode other than O/S.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.3 Block Mode and Status of Faceplate Blocks> D4-8
Table Block Mode Change Action Specifications Regarding O/S (2/2)
Change operation at the
Action of the faceplate block
connection destination block
O/S→MAN O/S→O/S
O/S→MAN O/S(MAN)→MAN
MAN→O/S O/S→O/S
MAN→O/S MAN→O/S(MAN)
D040302E.ai

Note: MAN indicates a mode other than O/S. Actions are the same for all mode other than O/S.

• When the block mode of the faceplate block changes to out of service (O/S), only the mode
of the faceplate block becomes out of service (O/S), the mode of the connected destination
function block does not change.
• When the block mode of the connected destination block is changed to out of service
(O/S), the block mode of the faceplate block does not become out of service (O/S) but
becomes O/S (MODE) which is a compound block mode. “MODE” of O/S (MODE) indicates
either the MAN, AUT or CAS mode. If the block mode of the faceplate block is displayed as
“MAN O/S” on the operation and monitoring function or described as “O/S (MAN)” in this
chapter, it means that the connected destination is in the out of service (O/S) mode and the
faceplate block is in the manual (MAN) mode.
• Actions that take place when a mode change is performed against the faceplate block while
the faceplate block is in the out of service (O/S) mode or O/S (MAN):
When a block mode change is performed directly against the faceplate block, the same
block mode change command is sent simultaneously to the connected destination function
block of the faceplate block.
• When a mode change is performed to the connected destination function block while the
faceplate block is in the out of service (O/S) mode:
The faceplate block remains in the out of service (O/S) mode.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.3 Block Mode and Status of Faceplate Blocks> D4-9

n Behavior of Faceplate without Block Mode Connection

When there is no block mode connection, the block modes that are unique to the faceplate block
are used, as shown in the table below. Block mode can be changed only by external operations
outside the faceplate block, unless the block is returning from an O/S over transition state.
Table Behavior of Faceplate Mode without Block Mode Connection
Block mode
Description
Symbol Name
O/S Out of service Indicates a state in which all functions are stopped.
MAN Manual
SEMI Semi-automatic
AUT Automatic Specific meanings of each mode can be defined freely using the
CAS Cascade application.

RCAS Remote cascade

ROUT Remote output
D040303E.ai

Note: SEMI (semi-automatic) has the same priority as AUT and MAN, and is mutually exclusive with the two.

n Interlock Condition for Faceplate Block Mode Change

Like other function blocks, the faceplate block has an interlock switch input terminal (INT) which
activates the block mode change interlock function. The block mode change interlock function
takes effect according to the status of the switch connected to the terminal (INT) of the faceplate
block itself. Whether the faceplate block is connected to other function block or not is irrelevant.
However, if the connected destination block and the faceplate block use the different signal
for block mode change interlock, the faceplate block will follow the block mode change of the
connected destination function block.
Thus, when the block mode is restricted under the faceplate block’s interlock condition , the
connected destination block can not change block mode again.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.3 Block Mode and Status of Faceplate Blocks> D4-10

D4.3.2 Block Status of Faceplate Blocks

The block status of the faceplate block agrees with the block status of the connected
destination function block. If there is no destination connection, a unique block status is
used.

n Behavior of Faceplate with Block Status Connection

The faceplate block periodically refers to the connected destination block status to keep their
block status agree with each other.
To establish block status connection, connect the data item BSTS (block status) of the destination
tag to the terminal (JBST) of faceplate block. When a data item other than BSTS is specified,
the faceplate block does not operate properly. A faceplate block cannot be connected to another
faceplate block.
When block status connection establishes, the connected destination function block’s is read via
JBST terminal, status change can be performed only from the faceplate block.
The types of the block status (STOP, RUN, etc.) for the faceplate block depend on the types of
the block status available for the connected destination block.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.3 Block Mode and Status of Faceplate Blocks> D4-11

n Behavior of Faceplate without Block Status Connection

▼ USER1(Faceplate Block)
When there is no block status connection, the block status strings defined on the user- defined
Status Character String Builder unique to the faceplate block can be used. The default status
strings for faceplate blocks are shown in the table below.
Table Behavior of Faceplate Status without Block Status Connection
Block status
Priority Position (Bit Column)
Symbol Name
FAIL Fail 2
ABRT Abort 3
3
IDLE Idle 4
SIML Simulation 5
RUN Run 17
STOP Stop 18
STUP Startup 19
1
HOLD Hold 20
WAIT Wait 21
END End 23
SDWN Shutdown 25
0 ESD Emergency shutdown 26
RSTR Restart 28
D040304E.ai

The character strings for faceplate block status are the user-defined status character string
defined in column USER1 on the Status Character String Builder.
In the table, the position 33 (Bit Column) is system reserved, can not be used.
A block status string can be defined with up to 8 alphanumeric characters including underscore ( _ ).
The block status character string of the faceplate block can be changed by application programs
are the strings in the table positions 2, 3, 4, 5, 17, 18, 19, 20, 21, 23, 25, 26 and 28. The strings
are defined to other positions (Bit) cannot be used by the application programs.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.3 Block Mode and Status of Faceplate Blocks> D4-12

D4.3.3 Alarm Status of Faceplate Blocks

The alarm status of a faceplate block agrees with the connected destination function
block’s alarm status, except for the connection failure (CNF) or normal (NR) status. If there
is no connection destination, a unique alarm status is used.
The alarm-related functions such as alarm acknowledgment, alarm detection specification
and alarm inhibition functions are available.

n Behavior of Faceplate with Alarm Status Connection

The faceplate block periodically refers to the connected destination block’s alarm status to keep
their alarm status agree with each other.
To establish the alarm status connection, connect the data item ALRM of the destination tag to
the terminal (JALM) of the faceplate block. If a data item other than ALRM is used, it does not
work properly. A faceplate block cannot be connected to another faceplate block.
If alarm status connection establishes, any alarm status change operation on the faceplate block
becomes invalid.
The types of the alarm status (IOP, HI, etc.) for the faceplate block depend on the types of alarm
status available for the connected destination block.
When the connected destination block changes to connection failure (CNF) alarm status, the
faceplate block does not change to connection failure (CNF).

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.3 Block Mode and Status of Faceplate Blocks> D4-13

n Behavior of Faceplate without Alarm Status Connection

When there is no alarm status connection, the alarm strings defined on the user-defined Status
Character String Builder unique to the faceplate block can be used. The default alarm strings for
faceplate blocks are shown in the table below.
Table Behavior of Faceplate Alarm Status without Alarm Status Connection
Alarm status
Position (Bit)
Symbol Name
NR Normal status 9
OOP Output open alarm 10
IOP High input open alarm 11
IOP- Low input open alarm 12
ESTP Emergency stop alarm 13
HIHI High-High alarm 15
LOLO Low-Low alarm 16
HI High alarm 17
LO Low alarm 18
DV+ Positive deviation alarm 21
DV- Negative deviation alarm 22
TRP Trip alarm 25
SCBL Scramble alarm 26
INT Interlock alarm 27
ERR Error alarm 28
DISC Discrete alarm 29
BLCK Block alarm 30
CNF Connection failure alarm 32
D040305E.ai

The alarm status of faceplate block is indicated with the character string set of USER9 in the
table on the user-defined alarm status character string builder. The block alarm status character
string of the faceplate block can be changed by application programs are the strings in the table
positions 10, 11, 12, 13, 17, 18, 25, 26, 27 and 28.
The character strings defined to the positions 15, 16, 21, 22, 29 and 30 are used when the
ALARM_SUM of fieldbus block is linked through fieldbus module (ACF11).

SEE
ALSO Faceplate alarm status characters strings are defined in column USER9 on user-defined character string builder.
For more information, see the following:
“n User-Defined Alarm Status Character String” in E10.4, “Alarm Status Character String and Alarm
Processing”

n Alarm-Related Functions
The alarm-related functions such as alarm acknowledgment, alarm detection specification and
alarm inhibition functions are available for a faceplate block. They can be set on the data items
named alarm flashing status (AFLS), alarm detection specification (AF), and alarm inhibition
specification (AOFS), respectively.
The settings on the faceplate block itself determines the alarm-related functions. Whether the
faceplate is connected with other function block is irrelevant.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.3 Block Mode and Status of Faceplate Blocks> D4-14

D4.3.4 Data Status of Faceplate Blocks

A faceplate block has three types of analog data, the process variable (PV), setpoint value
(SV), and manipulated output value (MV). They are referred as “data with data status.”
The data status of the process variable (PV), setpoint value (SV), and manipulated output
value (MV) agree with the data status of the connected destination block. If there is no
block connected, the data status is determined by the status of the data setting block.

n Faceplate with Data Connection

The data status agrees with the data status of the connected destination function block.
When data from the terminal connected function block have bad value (BAD) status, the data set
to the faceplate as it is anyway.
The faceplate blocks, except for batch status block (BSI), only read process variable (PV) from
the connected destination blocks. The PV can not be changed from the faceplate. Therefore,
to set the process variable (PV) of the faceplate block to CAL will result in a setting error. If
you really want to change the PV to calibration state you can do it directly on the connected
destination block.

n Faceplate without Data Connection

When there is no data connection, the data status depends on the data status of its own data.
For the faceplate blocks that have no connection with other blocks, data can be set externally
such as from the operation and monitoring function. In this case, the bad value (BAD) data status
is reset.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.4 Dual-Pointer Indicating Station Block (INDST2)> D4-15

D4.4 Dual-Pointer Indicating Station Block

(INDST2)
The Dual-Pointer Indicating Station Block (INDST2) is a faceplate block used for
indication.

n Dual-Pointer Indicating Station Block (INDST2)

▼ Connection Information
The Dual-Pointer Indicating Station Block (INDST2) is a faceplate block used for indication.
Here is a function block diagram of the Dual-Pointer Indicating Station Block (INDST2).

JMOD MODE

JBST BSTS

JALM ALRM

JPV PV

JSV SV

J01 SVH

J02 SVL

INT

D040401E.ai

Figure Function Block Diagram of Dual-Pointer Indicating Station Block (INDST2)

INDST2 block process timing is periodic type. The scan period can be set to Basic Scan,
Medium-speed Scan (*1) or High-speed Scan.
*1: Medium-speed scan period is available for KFCS2, KFCS, FFCS, LFCS2 and LFCS only.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.4 Dual-Pointer Indicating Station Block (INDST2)> D4-16
The figure below shows an example of the instrument faceplate of the Dual-Pointer Indicating
Station Block (INDST2) displayed in the operation and monitoring window.

AIC100
System A
Concentration

AUT
NR
100.0

80.0

60.0

40.0

20.0

0.0
D040402E.ai

Figure Display Example of Dual-Pointer Indicating Station Block (INDST2)

The table below shows the connection types and connection destinations of the I/O terminals of
the Dual-Pointer Indicating Station Block (INDST2).
Table Connection Types and Connection Destinations of the I/O Terminals of Dual-Pointer Indicating
Station Block (INDST2)
Connection type Connection destination
I/O terminal Data Data Condition Status Terminal Process Software Function
reference setting testing manipulation connection I/O I/O block
Block mode
JMOD x x x
connection
Block status
JBST x x
connection
Alarm status
JALM x x
connection
PV
JPV x x
connection
SV
JSV x x x
connection
SVH
J01 x x x
connection
SVL
J02 x x x
connection
Interlock
INT x Δ x x x
switch input
D040403E.ai

x: Connection available
Blank: Connection not available
Δ: Connection is available only when connecting to a selector switch block (SW-33, SW-91).

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.4 Dual-Pointer Indicating Station Block (INDST2)> D4-17

n Analog Data Display Function

The Dual-Pointer Indicating Station Block (INDST2) references the analog data at the connection
destination of the I/O terminals shown below during each scan period, and stores data values
and data statuses as data items.
If no I/O connection terminal is connected, the values currently stored in the data items are held.
Table Target I/O Terminals of the Analog Data Display and Corresponding Data Items
I/O terminal Data item
JPV Process variable (PV)
JSV Setpoint value (SV)
J01 Setpoint high limit (SVH)
J02 Setpoint low limit (SVL)
D040404E.ai

n Analog Data Operation Function

When setting operation is performed to any data items of the Dual-Pointer Indicating Station
Block (INDST2), the set data item values will be set to the connection destination of the
corresponding I/O terminals shown below:
Table Target I/O Terminals of the Analog Data Operation Function and Corresponding Data Items
I/O terminal Data item
JSV Setpoint value (SV)
J01 Setpoint high limit (SVH)
J02 Setpoint low limit (SVL)
D040405E.ai

The setting of analog data to the connection destination is performed during the periodic scan
that immediately follows the setting operation to the data item of the Dual-Pointer Indicating
Station Block (INDST2).

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.4 Dual-Pointer Indicating Station Block (INDST2)> D4-18

n Data Items - INDST2

Table Data Items of Dual-Pointer Indicating Station Block (INDST2)
Entry Permitted
Data Item Data Name Range Default
or Not
MODE Block mode x ----- O/S (MAN)
BSTS Block status Δ ----- 0
ALRM Alarm status Δ ----- NR
AFLS Alarm flashing status x ----- 0
AF Alarm detection specification x ----- 0
AOFS Alarm masking specification x ----- 0
PV Process variable PV engineering unit value SL
SV Setpoint value x Value in the same engineering unit as PV SL
SVH Setpoint high limit x SL to SH SH
SVL Setpoint low limit x SL to SH SL
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
SH Scale high limit Value in the same engineering unit as PV -----
SL Scale low limit Value in the same engineering unit as PV -----
D040406E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D4.5 Dual-Pointer Manual Station Block (INDST2S)> D4-19

D4.5 Dual-Pointer Manual Station Block

(INDST2S)
The Dual-Pointer Manual Station Block (INDST2S) is a faceplate block used for operation.

n Dual-Pointer Manual Station Block (INDST2S)

▼ Connection Information
Here is a function block diagram of the Dual-Pointer Manual Station Block (INDST2S).

JMOD MODE

JBST BSTS

JALM ALRM

JSV SV

JMV MV

J01 SVH

J02 SVL

J03 MH

J04 ML

INT

D040501E.ai

Figure Function Block Diagram of Dual-Pointer Manual Station Block (INDST2S)

INDST2S block process timing is periodic type. The scan period can be set to Basic Scan,
Medium-speed Scan (*1) or High-speed Scan.
*1: Medium-speed scan period is available for KFCS2, KFCS, FFCS, LFCS2 and LFCS only.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.5 Dual-Pointer Manual Station Block (INDST2S)> D4-20
The figure below shows an example of the instrument faceplate of the Dual-Pointer Manual
Station Block (INDST2S) displayed in the operation and monitoring window.

AIC200
System B
Concentration

AUT
NR
100.0

80.0

60.0

40.0

20.0

0.0
D040502E.ai

Figure Display Example of Dual-Pointer Manual Station Block (INDST2S)

The table below shows the connection types and connection destinations of the I/O terminals of
the Dual-Pointer Manual Station Block (INDST2S).
Table Connection Types and Connection Destinations of the I/O Terminals of Dual-Pointer Manual
Station Block (INDST2S)
Connection type Connection destination
I/O terminal Data Data Condition Status Terminal Process Software Function
reference setting testing manipulation connection I/O I/O block
Block mode x
JMOD x x
connection
Block status x x
JBST
connection
Alarm status x x
JALM
connection
SV x x x
JSV
connection
MV x x x
JMV
connection
SVH x x x
J01
connection
SVL x x x
J02
connection
MH x x x
J03
connection
ML x x x
J04
connection
Interlock x Δ x x x
INT
switch input
D040503E.ai

x: Connection available
Blank: Connection not available
Δ: Connection is available only when connecting to a selector switch block (SW-33, SW-91).

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.5 Dual-Pointer Manual Station Block (INDST2S)> D4-21

n Analog Data Display Function

The Dual-Pointer Manual Station Block (INDST2S) references the analog data at the connection
destination of the I/O terminals shown below during each scan period, and stores data values
and data statuses as data items.
If no I/O connection terminal is connected, the values currently stored in the data items are held.
Table Target I/O Terminals of Analog Data Display and Corresponding Data Items
I/O terminal Data item
JSV Setpoint value (SV)
JMV Manipulated output value (MV)
J01 Setpoint high limit (SVH)
J02 Setpoint low limit (SVL)
J03 Manipulated variable high-limit setpoint (MH)
J04 Manipulated variable low-limit setpoint (ML)
D040504E.ai

The display form of the manipulated output value (MV) is set in the Function Block Detail Builder.
• MV Display Style:
Select from “Auto determination” or “User Define.”
The default setting is “Auto determination.”

When “User Define” is selected, set the engineering unit and scale range of the manipulated
output value (MV). The engineering unit and scale range of the manipulated output value (MV)
are set in the Function Block Detail Builder.
• MV Engineering Unit Symbol:
MV engineering unit.
The default setting is “%.”
• MV Range:
The high limit and low limit values of the maximum range of the manipulated output value.
The default setting is “100.0” for the high limit value and “0.0” for the low limit value.

n Analog Data Operation Function

When setting operation is performed to any data items of the Dual-Pointer Manual Station Block
(INDST2S), the set data item values will be set to the connection destination of the corresponding
I/O terminals shown below:
Table Target I/O Terminals of Analog Data Operation and Corresponding Data Items
I/O terminal Data item
JSV Setpoint value (SV)
JMV Manipulated output value (MV)
J01 Setpoint high limit (SVH)
J02 Setpoint low limit (SVL)
J03 Manipulated variable high-limit setpoint (MH)
J04 Manipulated variable low-limit setpoint (ML)
D040505E.ai

The setting of analog data to the connection destination is performed during the periodic scan
that immediately follows the setting operation to the data item of the Dual-Pointer Manual Station
Block (INDST2S).

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.5 Dual-Pointer Manual Station Block (INDST2S)> D4-22

n Data Items - INDST2S

Table Data Items of Dual-Pointer Manual Station Block (INDST2S)
Data Entry Permitted
Data Name Range Default
Item or Not
MODE Block mode x ----- O/S (MAN)
BSTS Block status Δ ----- 0
ALRM Alarm status Δ ----- NR
AFLS Alarm flashing status x ----- 0
AF Alarm detection specification x ----- 0
AOFS Alarm masking specification x ----- 0
SV Setpoint value x Value in the same engineering unit as PV SL
MV Manipulated output value x MV engineering unit value MSL
MH Manipulated variable high-limit setpoint x MSL to MSH MSH
ML Manipulated variable low-limit setpoint x MSL to MSH MSL
SVH Setpoint high limit x SL to SH SH
SVL Setpoint low limit x SL to SH SL
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
SH Scale high limit Value in the same engineering unit as SV -----
SL Scale low limit Value in the same engineering unit as SV -----
MSH MV scale high limit Value in the same engineering unit as MV -----
MSL MV scale low limit Value in the same engineering unit as MV -----
D040506E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D4.6 Triple-Pointer Manual Station Block (INDST3)> D4-23

D4.6 Triple-Pointer Manual Station Block

(INDST3)
The Triple-Pointer Manual Station Block (INDST3) is a faceplate block used for indication
operation.

n Triple-Pointer Manual Station Block (INDST3)

▼ Connection Information
Here is a function block diagram of the Triple-Pointer Manual Station Block (INDST3).

JMOD MODE

JBST BSTS

JALM ALRM

JPV PV

JSV SV

JMV MV

J01 SVH

J02 SVL

J03 MH

J04 ML

INT

D040601E.ai

Figure Function Block Diagram of Triple-Pointer Manual Station Block (INDST3)

INDST3 block process timing is periodic type. The scan period can be set to Basic Scan,
Medium-speed Scan (*1) or High-speed Scan.
*1: Medium-speed scan period is available for KFCS2, KFCS, FFCS, LFCS2 and LFCS only.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.6 Triple-Pointer Manual Station Block (INDST3)> D4-24
The figure below shows an example of the instrument faceplate of the Triple-Pointer Manual
Station Block (INDST3) displayed in the operation and monitoring window.

AIC300
System C
Concentration

AUT
NR
100.0

80.0

60.0

40.0

20.0

0.0
D040602E.ai

Figure Display Example of Triple-Pointer Manual Station Block (INDST3)

The table below shows the connection types and connection destinations of the I/O terminals of
the Triple-Pointer Manual Station Block (INDST3).
Table Connection Types and Connection Destinations of I/O Terminals of Triple-Pointer Manual Station
Block (INDST3)
Connection type Connection destination
I/O terminal Data Data Condition Status Terminal Process Software Function
reference setting testing manipulation connection I/O I/O block
Block mode x x x
JMOD
connection
Block status x x
JBST
connection
Alarm status x x
JALM
connection
JPV PV connection x x
JSV SV connection x x x
JMV MV connection x x x
J01 SVH connection x x x
J02 SVL connection x x x
J03 MH connection x x x
J04 ML connection x x x
Interlock x Δ x x x
INT
switch input
D040603E.ai

x: Connection available
Blank: Connection not available
Δ: Connection is available only when connecting to a selector switch block (SW-33, SW-91).

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.6 Triple-Pointer Manual Station Block (INDST3)> D4-25

n Analog Data Display Function

The Triple-Pointer Manual Station Block (INDST3) references the analog data at the connection
destination of the I/O terminals shown below during each scan period, and stores data values
and data statuses as data items.
If no I/O connection terminal is connected, the values currently stored in the data items are held.
Table Target I/O Terminals of Analog Data Display and Corresponding Data Items
I/O terminal Data item
JPV Process variable (PV)
JSV Setpoint value (SV)
JMV Manipulated output value (MV)
J01 Setpoint high limit (SVH)
J02 Setpoint low limit (SVL)
J03 Manipulated variable high-limit setpoint (MH)
J04 Manipulated variable low-limit setpoint (ML)
D040604E.ai

The display form of the manipulated output value (MV) is set in the Function Block Detail Builder.
• MV Display Style:
Select from “Auto determination” or “User Define.”
The default setting is “Auto determination.”

When “User Define” is selected, set the engineering unit and scale range of the manipulated
output value (MV). The engineering unit and scale range of the manipulated output value (MV)
are set in the Function Block Detail Builder.
• MV Engineering Unit Symbol:
MV engineering unit.
The default setting is “%.”
• MV Range:
The high limit and low limit values of the maximum range of the manipulated output value.
The default setting is “100.0” for the high limit value and “0.0” for the low limit value.

n Analog Data Operation Function

When setting operation is performed to any data items of the Triple-Pointer Manual Station Block
(INDST3), the set data item values will be set to the connection destination of the corresponding
I/O terminals shown below:
Table Target I/O Terminals of Analog Data Operation and Corresponding Data Items
I/O terminal Data item
JPV Process variable (PV)
JSV Setpoint value (SV)
JMV Manipulated output value (MV)
J01 Setpoint high limit (SVH)
J02 Setpoint low limit (SVL)
J03 Manipulated variable high-limit setpoint (MH)
J04 Manipulated variable low-limit setpoint (ML)
D040605E.ai

The setting of analog data to the connection destination is performed during the periodic scan
that immediately follows the setting operation to the data item of the Triple-Pointer Manual Station
Block (INDST3).

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.6 Triple-Pointer Manual Station Block (INDST3)> D4-26

n Data Items - INDST3

Table Data Items of Triple-Pointer Manual Station Block (INDST3)
Data Entry Permitted
Data Name Range Default
Item or Not
MODE Block mode x ----- O/S (MAN)
BSTS Block status Δ ----- 0
ALRM Alarm status Δ ----- NR
AFLS Alarm flashing status x ----- 0
AF Alarm detection specification x ----- 0
AOFS Alarm masking specification x ----- 0
PV Process variable PV engineering unit value SL
SV Setpoint value x Value in the same engineering unit as PV SL
MV Manipulated output value x MV engineering unit value MSL
MH Manipulated variable high -limit setpoint x MSL to MSH MSH
ML Manipulated variable low -limit setpoint x MSL to MSH MSL
SVH Setpoint high limit x SL to SH SH
SVL Setpoint low limit x SL to SH SL
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
SH Scale high limit Value in the same engineering unit as PV -----
SL Scale low limit Value in the same engineering unit as PV -----
MSH MV scale high limit Value in the same engineering unit as MV -----
MSL MV scale low limit Value in the same engineering unit as MV -----
D040606E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D4.7 Batch Status Indicator Block (BSI)> D4-27

D4.7 Batch Status Indicator Block (BSI)

The Batch Status Indicator Block (BSI) is a sequence faceplate block that has internal
functions to display sequence phase signals and to operate three push button switches.

n Batch Status Indicator Block (BSI)

▼ Connection Information
Here is a function block diagram of the Batch Status Indicator Block (BSI).

JMOD MODE

JBST BSTS

JALM ALRM

SET SV PV

SWOP[1]
INT
SWST[1]

SWCR[1]
SVLMH
Q01 PV01 SWLB[1]
SVLMH

Q02 PV02 SWLB[2]

MH

Q03 PV03 SWLB[3]

D040701E.ai

Figure Function Block Diagram of Batch Status Indicator Block (BSI)

BSI block process timing is periodic type. The scan period can be set to Basic Scan, Medium-
speed Scan (*1) or High-speed Scan.
*1: Medium-speed scan period is available for KFCS2, KFCS, FFCS, LFCS2 and LFCS only.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.7 Batch Status Indicator Block (BSI)> D4-28
The figure below shows an example of the instrument faceplate of the Batch Status Indicator
Block (BSI) displayed in the operation and monitoring window.

BS100
Phase in
System A

MAN
NR

Cooling

16
START

HALT

STOP
1

D040702E.ai

Figure Display Example of Batch Status Indicator Block (BSI)

The table below shows the connection types and connection destinations of the I/O terminals of
the Batch Status Indicator Block (BSI).
Table Connection Types and Connection Destinations of I/O Terminals of Batch Status Indicator Block
(BSI)
Connection type Connection destination
I/O terminal Data Data Condition Status Terminal Process Software Function
reference setting testing manipulation connection I/O I/O block
Block mode x x x
JMOD
connection
Block status x x
JBST
connection
Alarm status x x
JALM
connection
SV x x
SET
connection
PV01 x x x x x
Q01
connection
PV02 x x x x x
Q02
connection
PV03 x x x x x
Q03
connection
Interlock x Δ x x x
INT
switch input
D040703E.ai

x: Connection available
Blank: Connection not available
Δ: Connection is available only when connecting to a selector switch block (SW-33, SW-91).

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.7 Batch Status Indicator Block (BSI)> D4-29

n Phase Signal Display Function

▼ Process Name 1 to 16
The phase signal display function is a function that displays the name of the phase being
executed at the plant, on the instrument faceplate of the operation and monitoring window. The
Batch Status Indicator Block (BSI) performs processing in the following order.
• References the data at the connection destination of the SV connection terminal (SET), and
stores the referenced value as the current phase step number (SV).
• Select the current phase signal (PHAS[SV]) from process signals (PHAS[n]) based on the
value stored as the current phase step number (SV), and sets it as the current phase signal
(PV).
• If no data is linked to the SET terminal, PHAS[SV] is selected by using the value held as SV.
• If the value of the current phase step number (SV) is 17 or larger, the value of the current
phase signal (PV) is held as is.
• If the value of the current phase step number (SV) is 17 or larger, the current phase signal
(PV) will be changed when character string data is set to the signal.

Up to 16 phase signals can be defined in the Function Block Detail Builder. Phase signals
are defined as one-dimensional array data (PHAS[n]) whose elements are character strings
containing 16 alphanumeric characters.

n Switch Status Input Function

The switch status input function of the Batch Status Indicator Block (BSI) determines whether the
switch statuses (PV01 to PV03) are ON or OFF in accordance with the status data value of the
connection destination.

l Action of the Switch Status Input Function

The Batch Status Indicator Block (BSI) references the status information at the connection
destination of input connection terminals (Q01 to Q03) during each scan period. If the value of
the referenced status information is “0,” then the switch status becomes OFF. If the value is other
than “0,” then the switch status becomes ON.
When the switch status is OFF, the values of PV01 to PV03 are “0.” When the switch status is
ON, the values of PV01 to PV03 are “1.”

l Operating Conditions of the Switch Status Input Function

Depending upon the connection status of the I/O terminal and the switch type setting, data
reference and the switch status (PVnn) determination may or may not be performed.
Table Operating Conditions of the Switch Status Input Function
I/O connection Switch type Data reference Switch status determination
No connection ------
Not used
Lamp x x
Connection
Button x x
Button with lamp x x
D040704E.ai

x: Performed
Blank: Not performed

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.7 Batch Status Indicator Block (BSI)> D4-30

n Lamp Indication Function

▼ Label for OFF, Label for ON, Display Color for OFF, Display Color for ON
The lamp indication function of the Batch Status Indicator Block (BSI) changes the indication
color of the push button switch and the indication content of its switch label when the value of
each switch status (PV01 to PV03) is changed.

l Action of the Lamp Indication Function

When the ON/OFF status of each switch (PV01 to PV03) changes, the values of the
corresponding switch indication color (SWCR1 to SWCR3) and switch label (SWLB1 to SWLB3),
which are data items, will change. Accordingly, the indication color and switch label of the push
button switch, which is located on the instrument faceplate of the Batch Status Indicator Block
(BSI), will change.
The setting of the indication color and switch label of the push button switch can be changed by
using the Function Block Detail Builder.
The following are the default set values of each switch indication color and label.
• Display color at ON: Red
• Display color at OFF: White
• Label at ON: ON
• Label at OFF: OFF

l Operating Conditions of the Lamp Indication Function

Depending upon the connection status of the I/O terminal and the switch type setting, indication
color determination and switch label determination may or may not be performed.
Table Operating Conditions of the Lamp Indication Function
Indication color
I/O connection Switch type Switch label determination
determination
No connection ------
Not used
Lamp x x
Connection
Button
Button with lamp x x
D040705E.ai

x: Performed
Blank: Not performed

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.7 Batch Status Indicator Block (BSI)> D4-31

n Button Operation Function

The button operation function of the Batch Status Indicator Block (BSI) sets the value of each
switch status (PV01 to PV03) to the connection destination when button operation is performed
by the operator.

l Action of the Button Operation Function

When button operation is performed by the operator on the instrument faceplate, or when data is
set to PV01 to PV03 from outside the block, the corresponding switch status (PV01 to PV03) will
change. How the switch status changes depends on the setting of the button action.
When the value of PV01, PV02, or PV03 has been changed, that value (PV01 to PV03) is set
to the connection destination of the corresponding I/O terminal (Q01 to Q03). This setting is
executed during the first periodic scan following the setting operation to the data item of the Batch
Status Indicator Block (BSI).

l Operating Conditions of the Button Operation Function

Depending upon the connection status of the I/O terminal and the switch type setting, switch
status (PVnn) determination and data output may or may not be performed.
Table Operating Statuses of the Button Operation Function
Switch status
I/O connection Switch type Data output
determination
No connection ------
Not used
Lamp
Connection
Button x x
Button with lamp x x
D040706E.ai

x: Performed
Blank: Not performed

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.7 Batch Status Indicator Block (BSI)> D4-32
l Button Action
▼ Button Action
The button action references the ways in which the switch status changes when button operation
is performed by the operator.
The button action of the Batch Status Indicator Block (BSI) is defined in the Function Block Detail
Builder. Two types of button actions are available for selection: “check button” and “radio button.”
• Check button action
When button operation is performed by the operator, the switch status changes. The status
changes to OFF (0) if it was ON (1), and to ON (1) if it was OFF (0). Multiple switches can be
turned ON simultaneously.
• Radio button action
When button operation is performed by the operator, all switches other than the one that has
been turned ON (1) by the operation will be turned OFF (0) forcibly.
• Switches that are turned OFF forcibly while the “radio button” is in use are limited to those
that support the button operation function.
• When the “radio button” is in use, even a switch whose operation disable status is ON will
be turned OFF forcibly once other switches have been turned ON.
• In some circumstances, such as when switch statuses are referenced by the lamp indication
function, multiple switch statuses may become ON simultaneously. In this case, only the
switch with the smallest number among the switches that are ON will remain so. All other
switch statuses will be turned OFF forcibly. When any switch status is turned OFF forcibly,
its PVnn value will be set to the connection destination of the corresponding I/O terminal, as
is the case with the button operation function.

n Switch Flashing Function

The switch flashing function flashes the lamp of each switch on the instrument faceplate.
When the switch flashing status (SWST[n]) is set to “1” through data setting, the lamp indication
on the instrument faceplate starts flashing. When the switch flashing status (SWST[n]) is set to
“0,” the lamp indication returns to a normal state.

n Switch Operation Disable Function

The switch operation disable function is a function that disables switch operation from the
instrument faceplate. This function can enable or disable operation of the status (PVnn) and
flashing status (SWST[n]) of each switch.
When a numeric value of 0 or less is set as the switch operation disable status (SWOP[n]),
operation is enabled.
When a numeric value of 1 or more is set as the switch operation disable status (SWOP[n]),
operation is disabled.
Note that this function disables only the operations performed on the instrument faceplate. Even
when switch operation is disabled by this setting, other switch operations, such as the setting of
data between function blocks and data entry operation from the tuning view of the specified tag
and data item names, can be performed freely.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.7 Batch Status Indicator Block (BSI)> D4-33

n Data Items - Batch Status Indicator Block (BSI)

Table Data Items of Batch Status Indicator Block (BSI)
Entry Permitted
Data Item Data Name Range Default
or Not
MODE Block mode x ----- O/S (MAN)
BSTS Block status Δ ----- 0
ALRM Alarm status Δ ----- NR
AFLS Alarm flashing status x ----- 0
AF Alarm detection specification x ----- 0
AOFS Alarm masking specification x ----- 0

x Equivalent to a string of 16 alphanumeric

PV Current phase step name -----
characters
SV Current phase step number Δ 1 to 99 1
PV01 to PV03 Switch status 1 to 3 x 0/1 0
SWCR[1] to [3] Switch indication color x 0 to 15 7

x Equivalent to a string of 8 alphanumeric

SWLB[1] to [3] Switch label -----
characters
SWST[1] to [3] Switch flashing status x 0/1 0
SWOP[1] to [3] Switch operation disable status x -15 to 15 0

x Equivalent to a string of 16 alphanumeric

PHAS[1] to [16] Phase step name -----
characters
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D040707E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D4.8 Extended 5-Push-Button Switch Block (PBS5C)> D4-34

D4.8 Extended 5-Push-Button Switch Block (PBS5C)

The Extended 5-Push-Button Switch Block (PBS5C) is a sequence faceplate block that
holds status data of five push button switches.

n Extended 5-Push-Button Switch Block (PBS5C)

▼ Connection Information
The Extended 5-Push-Button Switch Block (PBS5C) is a sequence faceplate block that holds
status data of five push button switches, and changes the indication on the instrument faceplate
in accordance with the status of each push button switch.
Here is a function block diagram of the Extended 5-Push-Button Switch Block (PBS5C).

JMOD MODE
AKLB[1]
JBST BSTS SWOP[1]

JALM ALRM SWST[1]MV

SWCR[1]MV
SVH
Q01 PV01 SWLB[1]
MVSVH MV01 B01
SVL
Q02 PV02 SWLB[2]
SVHSVL MV02 B02
MH
Q03 PV03 SWLB[3]
SVLMH MV03 B03

Q04 PV04 SWLB[4]

MH MV04 B04

Q05 PV05 SWLB[5] MV05 B05

INT

D040801E.ai

Figure Function Block Diagram of Extended 5-Push-Button Switch Block (PBS5C)

PBS5C block process timing is periodic type. The scan period can be set to Basic Scan, Medium-
speed Scan (*1) or High-speed Scan.
*1: Medium-speed scan period is available for KFCS2, KFCS, FFCS, LFCS2 and LFCS only.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.8 Extended 5-Push-Button Switch Block (PBS5C)> D4-35
The figure below shows an example of the instrument faceplate of the Extended 5-push-button
switch block (PBS5C) displayed in the operation and monitoring window.

SC100
System A

MAN NR
NR

SW1 OFF

V1 CLOSE

P1 STOP

SW2 OFF

V2 CLOSE

D040802E.ai

Figure Display Example of Extended 5-Push-Button Switch Block (PBS5C)

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.8 Extended 5-Push-Button Switch Block (PBS5C)> D4-36
The table below shows the connection types and connection destinations of the I/O terminals of
the Extended 5-Push-Button Switch Block (PBS5C).
Table Connection Types and Connection Destinations of I/O Terminals of Extended 5-Push-Button
Switch Block (PBS5C)
Connection type Connection destination
I/O terminal Data Data Condition Status Terminal Process Software Function
reference setting testing manipulation connection I/O I/O block
Block mode x x x
JMOD
connection
Block status x x
JBST
connection
Alarm status x x
JALM
connection
PV01 x x x x
Q01
connection
PV02 x x x x
Q02
connection
PV03 x x x x
Q03
connection
PV04 x x x x
Q04
connection
PV05 x x x x
Q05
connection
MV01 x x x x
B01
connection
MV02 x x x x
B02
connection
MV03 x x x x
B03
connection
MV04 x x x x
B04
connection
MV05 x x x x
B05
connection
Interlock x Δ x x x
INT
switch input
D040803E.ai

x: Connection available
Blank: Connection not available
Δ: Connection is available only when connecting to a selector switch block (SW-33, SW-91).

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.8 Extended 5-Push-Button Switch Block (PBS5C)> D4-37

n Switch Status Input Function

The switch status input function of the Extended 5-Push-Button Switch Block (PBS5C)
determines whether the switch statuses (PV01 to PV05) are ON or OFF in accordance with the
status data value of the connection destination.

l Action of the Switch Status Input Function

The PBS5C Block references status of terminals connected to input terminals Q01 to Q05 at
established scan periods. When the referenced status is 0, a switch turns OFF and the values of
PV01 and PV05 are 0. When it is other than 0, a switch turns ON and the values are 1.

l Operating Conditions of the Switch Status Input Function

Depending upon the connection status of the I/O terminal and the switch type, data reference
and the switch status (PVnn) determination may or may not be performed.
Table Operating Conditions of the Switch Status Input Function

I/O connection Switch type Data reference Switch status determination

No connection ------
Not used
Lamp x x
Connection
Button
Button with lamp x x
D040804E.ai

x: Performed
Blank: Not performed

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.8 Extended 5-Push-Button Switch Block (PBS5C)> D4-38

n Lamp Indication Function

▼ Label for OFF, Label for ON, Display Color for OFF, Display Color for ON
The lamp indication function of the Extended 5-Push-Button Switch Block (PBS5C) changes the
indication color of the push button switch and the indication content of its switch label when the
value of each switch status (PV01 to PV05) is changed.

l Action of the Lamp Indication Function

When the ON/OFF status of each switch (PV01 to PV05) changes, the values of the
corresponding switch indication color (SWCR[1] to SWCR[5]) and switch label (SWLB[1] to
SWLB[5]), which are data items, will change. Accordingly, the indication color and switch label
of the push button switch, which is located on the instrument faceplate of the Extended 5-Push-
Button Switch Block (PBS5C), will change.
The setting of the indication color and switch label of the push button switch can be changed by
using the Function Block Detail Builder.
The following shows the default set values of each switch indication color and label.
• Display color at ON: Red
• Display color at OFF: White
• Label at ON: ON
• Label at OFF: OFF

l Operating Conditions of the Lamp Indication Function

Depending upon the connection status of the I/O terminal and the switch type setting, indication
color determination and switch label determination may or may not be performed.
Table Operating Conditions of the Lamp Indication Function
Indication color
I/O connection Switch type Switch label determination
determination
No connection ------
Not used
Lamp x x
Connection
Button
Button with lamp x x
D040805E.ai

x: Performed
Blank: Not performed

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.8 Extended 5-Push-Button Switch Block (PBS5C)> D4-39

n Button Operation Function

The button operation function of the Extended 5-Push-Button Switch Block (PBS5C) changes
manipulated command values (MV01 to MV05) when button operation is performed by the
operator.

l Action of the Button Operation Function

When button operation is performed by the operator on the instrument faceplate, or when data
is set to manipulated command values (MV01 to MV05) from outside the block, the manipulated
command values (MV01 to MV05) will change. How each value changes varies depending upon
the button operation setting.
When the value of any manipulated command value (MV01 to MV05) is changed, that
manipulated command value (MV01 to MV05) will be set to the connection destination of the
corresponding output connection terminal (B01 to B05). This setting of data to the connection
destination is executed during the first periodic scan following the setting operation to the data
item of the Extended 5-Push-Button Switch Block (PBS5C).

l Operating Conditions of the Button Operation Function

Depending upon the connection status of the I/O terminal and the switch type setting,
manipulated command value (MVnn) determination and data output may or may not be
performed.
Table Operating Conditions of the Button Operation Function
Manipulated command
I/O connection Switch type Data output
value determination
No connection ------
Not used
Lamp
Connection
Button x x
Button with lamp x x
D040806E.ai

x: Performed
Blank: Not performed

l Button Action
▼ Button Action
The button action references the ways in which the switch status changes when button operation
is performed by the operator.
The button action of the Extended 5-Push-Button Switch Block (PBS5C) is set in the Function
Block Detail Builder. Three types of button action are available for selection; “momentary button,”
“alternate button,” and “radio button.” The default is “momentary button.”
When the “momentary button” is selected, output time span must be set. The output time span is
set in the Function Block Detail Builder.

n Switch Flashing Function

The switch flashing function flashes the lamp of each switch on the instrument faceplate.
When the switch flashing status (SWST[n]) is set to “1” through data setting, the lamp indication
on the instrument faceplate starts flashing. When the switch flashing status (SWST[n]) is set to
“0,” the lamp indication returns to a normal state.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.8 Extended 5-Push-Button Switch Block (PBS5C)> D4-40

n Switch Operation Disable Function

The switch operation disable function is a function that disables switch operation from the
instrument faceplate. This function can enable or disable operation of the status (PVnn) and
flashing status (SWST[n]) of each switch.
When a numeric value of 0 or smaller is set as the switch operation disable status (SWOP[n]),
operation is enabled.
When a numeric value of 1 or greater is set as the switch operation disable status (SWOP[n]),
operation is disabled.
Note that this function disables only the operations performed on the instrument faceplate. Even
when switch operation is disabled by this setting, other switch operations, such as the setting of
data between function blocks and data entry operation from the tuning view of the specified tag
and data item names, can be performed freely.

n Reconfirmation Operation
A dialog box for reconfirming the switch operation is displayed.
In the dialog, an OFF switch label is displayed when the current switch status (PVnn) is ON and an
ON switch label is displayed when the switch status is OFF.

n Data Items - PBS5C

Table Data Items of Extended 5-Push-Button Switch Block (PBS5C)
Entry Permitted
Data Item Data Name Range Default
or Not
MODE Block mode x ----- O/S (MAN)
BSTS Block status Δ ----- 0
ALRM Alarm status Δ ----- NR
AFLS Alarm flashing status x ----- 0
AF Alarm detection specification x ----- 0
AOFS Alarm masking specification x ----- 0
PV01 to PV05 Switch status 1 to 5 x 0/1 0
SWCR[1] to [5] Switch indication color x 0 to 15 7

x Equivalent to a string of 8 alphanumeric

SWLB[1] to [5] Switch label -----
characters
SWST[1] to [5] Switch flashing status x 0/1 0
SWOP[1] to [5] Switch operation disable status x -15 to 15 0

x Equivalent to a string of 8 alphanumeric

AKLB[1] to [5] Reconfirmation label -----
characters
MV01 to MV05 Manipulated command 1 to 5 x 0/1 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
D040807E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D4.9 Extended 10-Push-Button Switch Block (PBS10C)> D4-41

D4.9 Extended 10-Push-Button Switch Block

(PBS10C)
The Extended 10-Push-Button Switch Block (PBS10C) (*1) is a sequence faceplate block
that holds status data of ten push button switches.
*1: PBS10C block can be used in FCSs except PFCS.

n Extended 10-Push-Button Switch Block (PBS10C)

▼ Connection Information
Here is a function block diagram of the Extended 10-Push-Button Switch Block (PBS10C).

JMOD MODE
AKLB[1]
JBST BSTS SWOP[1]

JALM ALRM SWST[1]MV

SWCR[1]MV
SVH
Q01 PV01 SWLB[1]
MVSVH MV01 B01
SVL
Q02 PV02 SWLB[2]
SVHSVL MV02 B02
MH
SVLMH

MH

Q10 PV10 SWLB[10] MV10 B10

INT

D040901E.ai

Figure Function Block Diagram of Extended 10-Push-Button Switch Block (PBS10C)

PBS10C block process timing is periodic type. The scan period can be set to Basic Scan,
Medium-speed Scan (*1) or High-speed Scan.
*1: Medium-speed scan period is available for KFCS2, KFCS, FFCS, LFCS2 and LFCS only.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.9 Extended 10-Push-Button Switch Block (PBS10C)> D4-42
The figure below shows an example of the instrument faceplate of the Extended 10-Push-Button
Switch Block (PBS10C) displayed in the operation and monitoring window.

SC200
System B

MAN NR
NR

SW1 OFF P2 STOP

V1 CLOSE SW3 OFF

P1 STOP V3 CLOSE

SW2 OFF P3 STOP

V2 CLOSE SW4 OFF

D040902E.ai

Figure Display Example of Extended 10-Push-Button Switch Block (PBS10C)

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.9 Extended 10-Push-Button Switch Block (PBS10C)> D4-43
The table below shows the connection types and connection destinations of the I/O terminals of
the Extended 10-Push-Button Switch Block (PBS10C).
Table Connection Types and Connection Destinations of I/O Terminals of Extended 10-Push-Button
Switch Block (PBS10C) (1/2)
Connection type Connection destination
I/O terminal Data Data Condition Status Terminal Process Software Function
reference setting testing manipulation connection I/O I/O block
Block mode
JMOD x x x
connection
Block status
JBST x x
connection
Alarm status
JALM x x
connection
PV01
Q01 x x x x
connection
PV02
Q02 x x x x
connection
PV03
Q03 x x x x
connection
PV04
Q04 x x x x
connection
PV05
Q05 x x x x
connection
PV06
Q06 x x x x
connection
PV07
Q07 x x x x
connection
PV08
Q08 x x x x
connection
PV09
Q09 x x x x
connection
PV10
Q10 x x x x
connection
Interlock
INT x Δ x x x
SW input
D040903E.ai

x: Connection available
Blank: Connection not available
Δ: Connection is available only when connecting to a selector switch block (SW-33, SW-91).

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.9 Extended 10-Push-Button Switch Block (PBS10C)> D4-44
Table Connection Types and Connection Destinations of I/O Terminals of Extended 10-Push-Button
Switch Block (PBS10C) (2/2)
Connection type Connection destination
I/O terminal Data Data Condition Status Terminal Process Software Function
reference setting testing manipulation connection I/O I/O block
MV01
B01 x x x x
connection
MV02
B02 x x x x
connection
MV03 x x x x
B03
connection
MV04
B04 x x x x
connection
MV05
B05 x x x x
connection
MV06
B06 x x x x
connection
MV07
B07 x x x x
connection
MV08
B08 x x x x
connection
MV09
B09 x x x x
connection
MV10
B10 x x x x
connection
D040904E.ai

x: Connection available
Blank: Connection not available

n Switch Status Input Function

The switch status input function of the Extended 10-Push-Button Switch Block (PBS10C)
determines whether the switch statuses (PV01 to PV10) are ON or OFF in accordance with the
status data value of the connection destination.

l Action of the Switch Status Input Function

The PBS10C Block references status of terminals connected to input terminals Q01 to Q10 at
established scan periods. When the referenced status is 0, a switch turns OFF and the values of
PV01 and PV10 are 0. When it is other than 0, a switch turns ON and the values are 1.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.9 Extended 10-Push-Button Switch Block (PBS10C)> D4-45
l Operating Conditions of the Switch Status Input Function
Depending upon the connection status of the I/O terminal and the switch type, data reference
and the switch status (PVnn) determination may or may not be performed.
Table Operating Conditions of Switch Status Input Function
Switch status
I/O connection Switch type Data reference
determination
No connection —
Not used
Lamp x x
Connection
Button
Button with lamp x x
D040905E.ai

x: Performed
Blank: Not performed

n Lamp Indication Function

▼ Label for OFF, Label for ON, Display Color for OFF, Display Color for ON
The lamp indication function of the the Extended 10-Push-Button Switch Block (PBS10C)
changes the indication color of the push button switch and the indication content of its switch
label when the value of each switch status (PV01 to PV10) is changed.

l Action of Lamp Indication Function

When the ON/OFF status of each switch (PV01 to PV10) changes, the values of the
corresponding switch indication color (SWCR[1] to SWCR[10]) and switch label (SWLB[1] to
SWLB[10]), which are data items, will change. Accordingly, the indication color and switch label
of the push button switch, which is located on the instrument faceplate of the Extended 10-Push-
Button Switch Block (PBS10C), will change.
The setting of the indication color and switch label of the push button switch can be changed by
using the Function Block Detail Builder.
The following shows the default set values of each switch indication color and label.
• Display color at ON: Red
• Display color at OFF: White
• Label at ON: ON
• Label at OFF: OFF

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.9 Extended 10-Push-Button Switch Block (PBS10C)> D4-46
l Operating Conditions of Lamp Indication Function
Depending upon the connection status of the I/O terminal and the switch type setting, indication
color determination and switch label determination may or may not be performed.
Table Operating Conditions of Lamp Indication Function
Indication color Switch label
I/O connection Switch type
determination determination
No connection —
Not used
Lamp x x
Connection
Button
Button with lamp x x
D040906E.ai

x: Performed
Blank: Not performed

n Button Operation Function

The button operation function of the Extended 10-Push-Button Switch Block (PBS10C) changes
manipulated command values (MV01 to MV10) when button operation is performed by the
operator.

l Action of the Button Operation Function

When button operation is performed by the operator on the instrument faceplate, or when data
is set to manipulated command values (MV01 to MV10) from outside the block, the manipulated
command values (MV01 to MV10) will change. How each value changes varies depending upon
the button operation setting.
When the value of any manipulated command value (MV01 to MV10) is changed, that
manipulate command value (MV01 to MV10) will be set to the connection destination of the
corresponding output connection terminal (B01 to B10). This setting of data to the connection
destination is executed during the first periodic scan following the setting operation to the data
item of the Extended 10-Push-Button Switch Block (PBS10C).

l Operating Conditions of the Button Operation Function

Depending upon the connection status of the I/O terminal and the switch type setting,
manipulated command value (MVnn) determination and data output may or may not be
performed.
Table Operating Conditions of the Button Operation Function
Manipulated
I/O connection Switch type command value Data output
determination
No connection —
Not used
Lamp
Connection
Button x x
Button with lamp x x
D040907E.ai

x: Performed
Blank: Not performed

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.9 Extended 10-Push-Button Switch Block (PBS10C)> D4-47
l Button Action
▼ Button Action
The button action references the ways in which the switch status changes when button operation
is performed by the operator.
The button action of the Extended 10-Push-Button Switch Block (PBS10C) is set in the Function
Block Detail Builder. Three types of button action are available for selection; “momentary button,”
“alternate button,” and “radio button.” The default is “momentary button.”
When the “momentary button” is selected, output time span must be set. The output time span is
set in the Function Block Detail Builder.

n Switch Flashing Function

The switch flashing function flashes the lamp of each switch on the instrument faceplate.
When the switch flashing status (SWST[n]) is set to “1” through data setting, the lamp indication
on the instrument faceplate starts flashing. When the switch flashing status (SWST[n]) is set to
“0,” the lamp indication returns to a normal state.

n Switch Operation Disable Function

The switch operation disable function is a function that disables switch operation from the
instrument faceplate. This function can enable or disable operation of the status (PVnn) and
flashing status (SWST[n]) of each switch.
When a numeric value 0 or smaller is set as the switch operation disable status (SWOP[n]),
operation is enabled.
When a numeric value 1 or greater is set as the switch operation disable status (SWOP[n]),
operation is disabled.
Note that this function disables only the operations performed on the instrument faceplate. Even
when switch operation is disabled by this setting, other switch operations, such as the setting of
data between function blocks and data entry operation from the tuning view of the specified tag
and data item names, can be performed freely.

n Reconfirmation Operation
A dialog box for reconfirming the switch operation is displayed.
In the dialog, an OFF switch label is displayed when the current switch status (PVnn) is ON and an
ON switch label is displayed when the switch status is OFF.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.9 Extended 10-Push-Button Switch Block (PBS10C)> D4-48

n Data Items - PBS10C

Table Data Items of Extended 10-Push-Button Switch Block (PBS10C)
Entry Permitted
Data Data Name Range Default
or Not
MODE Block mode x O/S (MAN)
BSTS Block status Δ 0
ALRM Alarm status Δ NR
AFLS Alarm flashing status x 0
Alarm detection
AF x 0
specification
Alarm masking
AOFS x 0
specification
PV01 to PV10 Switch status 1 to 10 x 0/1 0
SWCR[1] to [10] Switch indication color x 0 to 15 7
Equivalent to a string of 8
SWLB[1] to [10] Switch label x
alphanumeric characters
SWST[1] to [10] Switch flashing status x 0/1 0
Switch operation disable
SWOP[1] to [10] x -15 to 15 0
status
Equivalent to a string of 8
AKLB[1] to [10] Reconfirmation label x
alphanumeric characters
Manipulated command
MV01 to MV10 x 0/1 0
1 to 10
OPMK Operation mark x 0 to 64 0
UAID User application ID x 0
D040908E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

 <D4.10 Extended Hybrid Manual Station Block (HAS3C)> D4-49

D4.10 Extended Hybrid Manual Station Block

(HAS3C)
The Extended Hybrid Manual Station Block (HAS3C) is a faceplate block that has a
faceplate block for indication operation and status data for five push button switches.

n Extended Hybrid Manual Station Block (HAS3C)

▼ Connection Information
Here is a function block diagram of the Extended Hybrid Manual Station Block (HAS3C).

JMOD MODE
AKLB[1]
JBST BSTS SWOP[1]

JALM ALRM SWST[1]MV

SWCR[1]MV
SVH
Q01 PV01 SWLB[1]
MVSVH MV01 B01
SVL
Q02 PV02 SWLB[2]
SVHSVL MV02 B02
MH
Q03 PV03 SWLB[3]
SVLMH MV03 B03

Q04 PV04 SWLB[4]

MH MV04 B04

Q05 PV05 SWLB[5] MV05 B05

JPV PV

JSV SV

JMV MV

J01 SVH

J02 SVL

J03 MH

J04 ML

INT

D041001E.ai

Figure Function Block Diagram of Extended Hybrid Manual Station Block (HAS3C)

HAS3C block process timing is periodic type. The scan period can be set to Basic Scan, Medium-
speed Scan (*1) or High-speed Scan.
*1: Medium-speed scan period is available for KFCS2, KFCS, FFCS, LFCS2 and LFCS only.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.10 Extended Hybrid Manual Station Block (HAS3C)> D4-50
The figure below shows an example of the instrument faceplate of the Extended Hybrid Manual
Station Block (HAS3C) displayed in the operation and monitoring window.

HA100
System 1

AUT
NR
100.0
SW1A OFF
80.0

SW1B OFF
60.0

V1A CLOSE
40.0

V1B CLOSE
20.0

P1A STOP
0.0

D041002E.ai

Figure Display Example of Extended Hybrid Manual Station Block (HAS3C)

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.10 Extended Hybrid Manual Station Block (HAS3C)> D4-51
The table below shows the connection types and connection destinations of the I/O terminals of
Extended Hybrid Manual Station Block (HAS3C).
Table Connection Types and Connection Destinations of I/O Terminals of Extended Hybrid Manual
Station Block (HAS3C)
Connection type Connection destination
I/O terminal Data Data Condition Status Terminal Process Software Function
reference setting testing manipulation connection I/O I/O block
Block mode x x x
JMOD
connection
Block status x x
JBST
connection
Alarm status x x
JALM
connection
PV01 x x x x
Q01
connection
PV02 x x x x
Q02
connection
PV03 x x x x
Q03
connection
PV04 x x x x
Q04
connection
PV05 x x x x
Q05
connection
MV01 x x x x
B01
connection
MV02 x x x x
B02
connection
MV03 x x x x
B03
connection
MV04 x x x x
B04
connection
MV05 x x x x
B05
connection
PV x x
JPV
connection
SV x x x
JSV
connection
MV x x x
JMV
connection
SVH x x x
J01
connection
SVL x x x
J02
connection
MH x x x
J03
connection
ML x x x
J04
connection
Interlock x Δ x x x
INT
switch input
D041003E.ai

x: Connection available
Blank: Connection not available
Δ: Connection is available only when connecting to a selector switch block (SW-33, SW-91).

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.10 Extended Hybrid Manual Station Block (HAS3C)> D4-52

n Analog Data Display Function

The Extended Hybrid Manual Station Block (HAS3C) references the analog data at the
connection destination of the I/O terminals shown below during each scan period, and stores
data values and data statuses as data items.
If no I/O connection terminal is connected, the values currently stored in the data items are held.
Table Target I/O Terminals of Analog Data Display and Corresponding Data Items
I/O terminal Data item
JPV Process variable (PV)
JSV Setpoint value (SV)
JMV Manipulated output value (MV)
J01 Setpoint high limit (SVH)
J02 Setpoint low limit (SVL)
J03 Manipulated variable high-limit setpoint (MH)
J04 Manipulated variable low-limit setpoint (ML)
D041004E.ai

The display form of the manipulated output value (MV) is set in the Function Block Detail Builder.
• MV Display Style:
Select from “Automatic Determination” or “User Define.”
The default setting is “Automatic Determination.”

When “Automatic Determination” is selected, the engineering unit and scale range of the
manipulated output value (MV) will be the same with the connected block or device.
When “User Define” is selected, set the engineering unit and scale range of the manipulated
output value (MV). The engineering unit and scale range of the manipulated output value (MV)
are set in the Function Block Detail Builder.
• MV Engineering Unit Symbol:
MV engineering unit.
The default setting is “%.”
• MV Range:
The high limit and low limit values of the maximum range of the manipulated output value.
The default setting is “100.0” for the high limit value and “0.0” for the low limit value.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.10 Extended Hybrid Manual Station Block (HAS3C)> D4-53

n Analog Data Operation Function

When setting operation is performed to any data items of the Extended Hybrid Manual Station
Block (HAS3C), the set data item values will be set to the connection destination of the
corresponding I/O terminals shown below:
Table Target I/O Terminals of Analog Data Operation and Corresponding Data Items
I/O terminal Data item
JSV Setpoint value (SV)
JMV Manipulated output value (MV)
J01 Setpoint high limit (SVH)
J02 Setpoint low limit (SVL)
J03 Manipulated variable high-limit setpoint (ML)
J04 Manipulated variable low-limit setpoint (ML)
D041005E.ai

The setting of analog data to the connection destination is performed during the periodic scan
that immediately follows the setting operation to the data item of the Extended Hybrid Manual
Station Block (HAS3C).

n Switch Status Input Function

The switch status input function of the Extended Hybrid Manual Station Block (HAS3C)
determines whether the switch statuses (PV01 to PV05) are ON or OFF in accordance with the
status data value of the connection destination.

l Action of Switch Status Input

The HAS3C Block references status of terminals connected to input terminals Q01 to Q05 at
established scan periods. When the referenced status is 0, a switch turns OFF and the values of
PV01 and PV05 are 0. When it is other than 0, a switch turns ON and the values are 1.

l Operating Conditions of Switch Status Input

Depending upon the connection status of the I/O terminal and the switch type setting, data
reference and the switch status (PVnn) determination may or may not be performed.
Table Operating Conditions of the Switch Status Input
I/O connection Switch type Data reference Switch status determination
No connection ------
Not used
Lamp x x
Connection
Button
Button with lamp x x
D041006E.ai

x: Performed
Blank: Not performed

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.10 Extended Hybrid Manual Station Block (HAS3C)> D4-54

n Lamp Indication Function

▼ Label for OFF, Label for ON, Display Color for OFF, Display Color for ON
The lamp indication function of the Extended Hybrid Manual Station Block (HAS3C) changes the
indication color of the push button switch and the indication content of its switch label when the
value of each switch status (PV01 to PV05) is changed.

l Action of Lamp Indication

When the ON/OFF status of each switch (PV01 to PV05) changes, the values of the
corresponding switch indication color (SWCR[1] to SWCR[5]) and switch label (SWLB[1] to
SWLB[5]), which are data items, will change. Accordingly, the indication color and switch label
of the push button switch, which is located on the instrument faceplate of the Extended Hybrid
Manual Station Block (HAS3C), will change.
The setting of the indication color and switch label of the push button switch can be changed by
using the Function Block Detail Builder.
The default set values of each switch indication color and label are shown as follows.
• Display color at ON: Red
• Display color at OFF: White
• Label at ON: ON
• Label at OFF: OFF

l Operating Conditions of Lamp Indication

Depending upon the connection status of the I/O terminal and the switch type setting, indication
color determination and switch label determination may or may not be performed.
Table Operating Conditions of Switch Indication
Indication color
I/O connection Switch type Switch label determination
determination
No connection ------
Not used
Lamp x x
Connection
Button
Button with lamp x x
D041007E.ai

x: Performed
Blank: Not performed

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.10 Extended Hybrid Manual Station Block (HAS3C)> D4-55

n Button Operation Function

The button operation function of the Extended Hybrid Manual Station Block (HAS3C) changes
manipulated command values (MV01 to MV05) when button operation is performed by the
operator.

l Action of Button Operation

When button operation is performed by the operator on the instrument faceplate, or when data
is set to manipulated command values (MV01 to MV05) from outside the block, the manipulated
command values (MV01 to MV05) will change. The value to be set varies depending upon the
button operation setting.
When a value is set to any manipulated command value (MV01 to MV05), the manipulated
command value (MV01 to MV05) is set to the connection destination of the output terminal (B01
to B05). This setting is executed during the first periodic scan after the switch status setting.

l Operating Conditions of Button Operation

Depending upon the connection status of the I/O terminal and the switch type setting,
manipulated command value (MVnn) determination and data output may or may not be
performed.
Table Operating Conditions of Button Operation
Manipulated command
I/O connection Switch type Data output
value determination
No connection ------
Not used
Lamp
Connection
Button x x
Button with lamp x x
D041008E.ai

x: Performed
Blank: Not performed

l Button Action
▼ Button Action
The button action references the ways in which the switch status changes when button operation
is performed by the operator.
The button action of the Extended Hybrid Manual Station Block (HAS3C) is set in the Function
Block Detail Builder. Three types of button action are available for selection; “momentary button,”
“alternate button,” and “radio button.” The default is “momentary button.”
When the “momentary button” is selected, output time span must be set. The output time span is
set in the Function Block Detail Builder.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.10 Extended Hybrid Manual Station Block (HAS3C)> D4-56

n Switch Flashing Function

The switch flashing function flashes each switch on the instrument faceplate.
When 1 is set to the switch flashing state (SWST[n]), the lamp of the faceplate flashes; When 0 is
set, the lamp turns to the normal state.

n Switch Operation Disable Function

The switch operation disable function is a function that disables switch operation from the
instrument faceplate. This function can enable or disable operation of the status (PVnn) and
flashing status (SWST[n]) of each switch.
When a numeric value of 0 or less is set as the switch operation disable status (SWOP[n]),
operation is enabled.
When a numeric value of 1 or more is set as the switch operation disable status (SWOP[n]),
operation is disabled.
Note that this function disables only the operations performed on the instrument faceplate. Even
when switch operation is disabled by this setting, other switch operations, such as the setting of
data between function blocks and data entry operation from the tuning view of the specified tag
and data item names, can be performed freely.

n Reconfirmation Operation
A dialog box for reconfirming the switch is displayed.
In the dialog, an OFF switch label is displayed when the current switch status (PVnn) is ON and an
ON switch label is displayed when the switch status is OFF.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D4.10 Extended Hybrid Manual Station Block (HAS3C)> D4-57

n Data Items - HAS3C

Table Data Items of Extended Hybrid Manual Station Block (HAS3C)
Entry Permitted
Data Item Data Name Range Default
or Not
MODE Block mode x ----- O/S (MAN)
BSTS Block status Δ ----- 0
ALRM Alarm status Δ ----- NR
AFLS Alarm flashing status x ----- 0
AF Alarm detection specification x ----- 0
AOFS Alarm masking specification x ----- 0
PV01 to PV05 Switch status 1 to 5 x 0/1 0
PV Process variable PV engineering unit value SL
SV Setpoint value x Value in the same engineering unit as PV SL
MV Manipulated output value x MV engineering unit value MSL
Manipulated variable high-limit x
MH MSL to MSH MSH
setpoint
Manipulated variable low-limit x
ML MSL to MSH MSL
setpoint
SVH Setpoint high limit x SL to SH SH
SVL Setpoint low limit x SL to SH SL
SWCR[1] to [5] Switch indication color x 0 to 15 7

x Equivalent to a string of 8 alphanumeric

SWLB[1] to [5] Switch label -----
characters
SWST[1] to [5] Switch flashing status x 0/1 0
SWOP[1] to [5] Switch operation disable status x -15 to 15 0

x Equivalent to a string of 8 alphanumeric

AKLB[1] to [5] Reconfirmation label -----
characters
MV01 to MV05 Manipulated command 1 to 5 x 0/1 0
OPMK Operation mark x 0 to 64 0
UAID User application ID x ----- 0
SH Scale high limit Value in the same engineering unit as PV -----
SL Scale low limit Value in the same engineering unit as PV -----
MSH MV scale high limit Value in the same engineering unit as MV -----
MSL MV scale low limit Value in the same engineering unit as MV -----
D041009E.ai

x: Entry is permitted unconditionally

Blank: Entry is not permitted
Δ: Entry is permitted conditionally

IM 33M01A30-40E 2nd Edition : Jun.05,2009-00

Blank Page
 <D5. Sequential Function Chart> D5-1

D5. Sequential Function Chart

The sequential function chart (SFC) is a graphical programming language used to define
control sequences.
SFC can be written using the SFC block, which is a function block included in the
sequence control function.

n SFC
▼ SFC Block
The SFC language describes a program defining sequential control steps for every group of
processes.
An example of SFC involving three steps, which are initialization, water feed, and heating, is
shown below:
Step
Transition 01 Initialization

Link 02 Water feed

03 Heating

D050001E.ai

Figure Example of SFC

TIP
SFC is also used in functions other than the SFC block as indicated below, but the SFC specifications for each of
these will vary somewhat.
• Unit instrument
• Operation

SEE
ALSO For more information about unit instruments and operations, see the following:
D6, “Unit Supervision”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5. Sequential Function Chart> D5-2
l 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.

l Architecture of SFC Block

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

Function block data

SFC
System fixed data item

Mode
Status SEBOL,
Sequence table or
Logic chart

User defined data item

D050002E.ai

Figure Image of SFC Block Architecture

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5. Sequential Function Chart> D5-3
l Describing Step Actions
SEBOL, a sequence table or a logic chart can be used to describe step actions.
An example of SEBOL-written step actions is shown below:
global integer i1, i2, i3
......
V001.MV = CLOSE
01 Initialization ......

......
V001.MV = OPEN
02 Water feed wait until (L001.PV >= 10)
V001.MV = CLOSE
......

03 Heating ......
H001.MV = ON
wait until (T001.PV >= 20)
H001.MV = OFF
......
D050003E.ai

Figure SFC Block Control Algorithm

Although all step actions are written in SEBOL in the above example, a different manner of
description can be used for each step action according to the disposition of the involved process.

SEE
ALSO • For the details of SEBOL, see the following:
H1, “SEBOL Details”
• For the details of the sequence table and the logic chart, see the following:
D3, “Sequence Control”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5. Sequential Function Chart> D5-4

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

l Data Items
The SFC block has data items to identify SFC status.
These items are either system-specific predetermined data or user-defined data.

l 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).

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.1 SFC Elements> D5-5

D5.1 SFC Elements

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

n Description of SFC Elements

The step and link elements use varied symbols according to their actions. Their details are shown
below:
Table SFC Block Elements
Element Name Symbol

Step

Initial step

Double-Width Step
Step

Initial Double-Width
Step

Interrupt step

Transition Transition

Selective Sequence
Split

Selective Sequence
Join

Loop-Branch

Link Loop-Join

Jump Down Jnn

Jump Up Jnn

Jump To Jnn

Link

D050101E.ai

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.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.1 SFC Elements> D5-6

D5.1.1 Step
There are five elements as step elements. Each step needs to be defined with attributes
and action.

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

l Step
This is an ordinary step. In an example shown below, the step number is indicated in the square
on the left and a comment identifying the action defined for the step is shown in the rectangle on
the right:

02 Water feed
D050102E.ai

Figure Example of Step

l Initial Step
This is the step to be executed first. The step number is indicated in the square on the left and
a comment identifying the action defined for the step is shown in the rectangle on the right. The
use of the square and rectangle is the same as the ordinary “step” described above except that a
double square is used instead:

01 Initialization
D050103E.ai

Figure Example of Initial Step

l Double-Height Step
This element is also for an ordinary step except that a larger rectangle permits to enter three-
times the normal volume of action comment:

02

D050104E.ai

Figure Example of Double-Height Step

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.1 SFC Elements> D5-7
l Initial Double-Height Step
This element is also for an initial step except that a larger rectangle permits to enter three-times
the normal volume of action comment:

01

D050105E.ai

Figure Example of Initial Double-Height Step

l Interrupt Step
An interrupt step is used to interrupt the execution of the main program and execute an interrupt
program. The interrupt step in the main program specified the destination for the expansion to an
interrupt program.
An example of interrupt steps is shown below:

01
Interrupt step

02 RUN

03 STOP

04 PAUS
D050106E.ai

Figure Example of Interrupt Step

n Step Attributes
Attributes such as step type and step number need to be defined for each step.
Each step needs to be defined with attributes such as step type and step number.
The table below lists the step attributes.
Table Step Attributes
Attribute Description
Select one of the following:
• SEBOL step
• SEBOL one-shot execution step (SEBOL one-shot)
Action-describing • Sequence table step (sequence table step)
methods • Sequence table one-shot execution step
(sequence table one-shot)
• Logic chart step (logic chart)
• Logic chart one-shot execution step (logic chart one-shot)
Step number Integer 1 through 99 (*1)
Step comment Character string of up to 16 bytes.
Phase name Character string of up to 16 bytes.
D050107E.ai

*1: Duplicate numbers must not be assigned.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.1 SFC Elements> D5-8

n Step Action
Each step is described as an action to execute a processing.
The types of action and the description of each step are shown below:
• Initial step
in SEBOL
• SEBOL step
in SEBOL
• SEBOL one-shot
in SEBOL
• Sequence table one-shot execution step (sequence table step)
in Sequence table
• Sequence table one-shot execution step (sequence table one-shot step)
in Sequence table
• Logic chart step (logic chart) in Logic chart
• Logic chart one-shot execution step (logic chart one-shot) in Logic chart

SEE
ALSO For the details of action description, see the following:
D5.2, “Action Description Using SEBOL”
D5.3, “Action Description Using Sequence Table”
D5.4, “Action Description Using Logic Chart”

Some steps require the use of parameters to define action as described below:
Table Action Parameters
Step Parameter Action when unspecified
Initial step None -
SEBOL step &
None -
SEBOL oneshot
Sequence table Parameter-storing variable in action column. Ignored (*1)
one-shot
execution step Name of step executed. -
Sequence table Condition testing result-storing variable. Ignored (*2)
one-shot
execution Name of step executed. -
Logic chart step Parameter-storing variable in action column Ignored (*1)
Logic chart
None -
one-shot
D050108E.ai

*1: The operation & monitoring parameter is ignored.

*2: The condition testing result is ignored.

SEE
ALSO • For the details of the action signal parameter and condition testing result for sequence table and sequence
table one-shot steps, see the following:
D5.3.1, “Step Common Item Description Using the Sequence Table”
• For the details of the action signal parameter for logic chart steps, see the following:
D5.4.1, “Step Common Item Description Using Logic Chart”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.1 SFC Elements> D5-9

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.1 SFC Elements> D5-10

D5.1.2 Transition
The transition is an element to evaluate the transition condition to the next step.

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

l Step Sequence Transition

In step sequence, steps are executed in the programmed order from top to bottom.
When the transition condition of the current step is satisfied, the next step is activated and the
action is executed. If no condition is defined for the transition, the next step is activated and the
step action is executed.
Step sequence is SFC basic action.

06

Transition

07
D050109E.ai

Figure Example of Step Sequence Transition

SEE
ALSO For details on transition conditions, see the following:
D5.5, “Transition Conditions”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.1 SFC Elements> D5-11
l 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.

05

Transition

06 07 08

D050110E.ai

Figure Example of Selective Sequence Transition

The transition condition is evaluated once every basic cycle, or once in a few cycles unless time
is allocated to the SFC block specifically for once-per-cycle evaluation.

SEE
ALSO For more information, see the following:
D5.1.4, “Step & Selective Sequences”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.1 SFC Elements> D5-12

D5.1.3 Links
The Links define the order of step execution. The following eight links are available:
• Selective Sequence Split
• Selective Sequence Join
• Loop-Branch
• Loop-Join
• Jump Down
• Jump Up
• Jump To
• Link

These links, except for ordinary “Link,” must be used in the following combinations:
• Selective Sequence Split and Selective Sequence Join
• Loop-Branch and Loop-Join
• Jump Down and Jump To
• Jump Up and Jump To

n Selective Sequence Split and Selective Sequence Join

These links are used in a selective sequence as shown below:
Selective Sequence Split

Selective Sequence Join

D050111E.ai

Figure 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
ALSO For more information, see the following:
“n Selective Sequence” in D5.1.4, “Step & Selective Sequences”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.1 SFC Elements> D5-13

n Loop-Branch and Loop-Join

These links are used to define a loop as shown below.
The step or steps located between Loop-Branch and Loop-Join are repeatedly executed as long
as the transition condition for the loop is true.

Loop-Join

Loop-Branch

D050112E.ai

Figure Example of Loop-Branch and Loop-Join

n Jump Down, Jump Up and Jump To

These links are used when the process sequence must forcibly be skipped.
The Jump Down element defines downward skipping and the Jump Up element defines upward
skipping. The Jump To element, which must be used in combination with either one of the
skipping elements, defines the destination of skipping.
The Jump To is executed when the transition condition defined proceeding the Jump Down or
succeeding the Jump Up is true.
Examples of skipping are shown below:
Jump To
J2
Jump Down
J1
J2
Jump Up

Jump To

J1
Example of Jump Down Example of Jump Up
D050113E.ai

Figure Examples of Jumping

When a new skip label is created, it is automatically numbered adding 1 to the number of the
most recent skip label.

n Link
The “link” used to connect steps as shown below.
The vertical links for a step with a step, a transition with a step are shown in the following
example.

02
Links

03

D050114E.ai

Figure Example of Link

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.1 SFC Elements> D5-14

D5.1.4 Step & Selective Sequences

SFC can describe step-sequence and selective-sequence as well as interrupt programs
which thrust into those processing steps.

n Step Sequence
In a step sequence, steps are executed in the programmed order from the top and only one
transition is defined between steps.
An example is shown below:

06 Step

Transition

07 Step

D050115E.ai

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

n Selective Sequence
In a selective sequence, one of two to eight steps defined in parallel is executed selectively.
An example is shown below:

05

Transition

06 07 08

D050116E.ai

Figure Example of Selective Sequence

The transition condition is evaluated from left to right for every step; and the step for which the
condition is true will be activated, which is defined preceding the step. If no transition condition is
defined, the step will be activated unconditionally.
No other transition conditions are evaluated within the selective sequence during execution of
one step.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.1 SFC Elements> D5-15

n Interrupt Program
The interrupt program is an SFC program designed to interrupt the main SFC program for
the execution of a non-sequential event. The interrupt program needs to be written for each
non-sequential event and is developed from an interrupt step defined for the event in the main
program.
An example of the interrupt program for pausing (PAUS) developed from an SFC block
containing three interrupt steps is shown below:

Main program

01
Interrupt steps

02 RUN

03 STOP

04 PAUS

Developed

PAUS interrupt program

01

02

D050117E.ai

Figure Example of Interrupt Program Developed from Interrupt Step

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.2 Action Description Using SEBOL> D5-16

D5.2 Action Description Using SEBOL

The following methods of describing step actions using SEBOL are explained in this
section:
• Step common items
• Initial steps
• SEBOL steps
• SEBOL one-shot steps

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.2 Action Description Using SEBOL> D5-17

D5.2.1 Step Common Items

Items common to all steps for which SEBOL is used to write actions are as follows:
• SEBOL variables
• Function-block declaration
• Branching range
• “quit” statement
• #define

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

l Global Variables
Global variables can be accessed from any SEBOL-written step in the SFC block. To use global
variables, they should be specified in the initial step as shown below:

global integer <variable name>[, <variable name>...]

global long <variable name>[, <variable name>...]
global float <variable name>[, <variable name>...]
global double <variable name>[, <variable name>...]
global char*n <variable name>[, <variable name>...]

“n” in “char*n”: 1 through 255.

D050201E.ai

TIP
Global variables cannot be accessed from any sequence table or logic chart described step.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.2 Action Description Using SEBOL> D5-18
l Local Variables
Local variables can be accessed only from the steps for which the use of local variables is
declared. To use local variables, they should be specified in the initial step as shown below:

integer <variable name> [, <variable name>...]

long <variable name> [, <variable name>...]
float <variable name> [, <variable name>...]
double <variable name> [, <variable name>...]
char*n <variable name> [, <variable name>...]

“n” in “char*n”: 1 through 255.

D050202E.ai

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.

l Note Points
The same name cannot be assigned to global and local variables. An error is caused if the two
has the same name.

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

l Global Declaration
A function block can be accessed from any SEBOL-written step when the use of that function
block is globally declared in the initial step as shown below:

• Tag name declaration

global block <block code> <tag name>[, <tag name>...]

• Global generic name

global genname <block code> <global generic name>[, <global generic name>...]

D050203E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.2 Action Description Using SEBOL> D5-19
l 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:

• Tag name declaration

block <block code> <tag name>[, <tag name>...]

• Local generic name

genname <block code> <local generic name>[, <local generic name>...]

D050204E.ai

l Note Points
• No error occurs when the tag name specified in global declaration is used also in local
declaration; however, an error will occur if different block codes are specified. An error also
occurs if specified global and local generic names are identical.
• Using multiple-project-tag name, the function block data of other projects can be accessed.
Since a multiple-project-tag has an @ mark in its name, it is necessary to declare an alias
for the multiple-project-tag.
Multiple-project-tag is named in the following format
TagName@ProjectID
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
ALSO For the details about calling up multiple-project tag name, see the following:
“n Ideatical Tag Names” in M7.2.1, “Operation and Motoring Multiple Projects”

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.2 Action Description Using SEBOL> D5-20

n 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
ALSO For the details about “error” and “errorsub” specifications, see the following:
H1.13, “Error Handling”
For the details about “goto” statement, see the following:
H1.8.7, “goto”

n “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.

n #define
A name can be defined using “#define” only in the initial step. The defined name can then be
used in all SEBOL-written steps.

SEE
ALSO For the details about “#define”, see the following:
“n #define Statement” in H1.1.8,“Substitution of Character String”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.2 Action Description Using SEBOL> D5-21

D5.2.2 Initial Step

The following methods of describing the initial step are described in this section:
• Order of description
• Example of description
• Use of “#define”
• Use of “#include”
• Use of “#IMPLICIT”

n Order of Description
The initial step action should be described in order of global variables, local variables, and
execution statements as shown below; an error will be caused otherwise.

<Global variables/Global declaration>

<Local variables/Local declaration>
<Action execution statement>
D050205E.ai

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.

n 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]
[ VL302.MODE.MV = "MAN", 0]
.......
quit

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.2 Action Description Using SEBOL> D5-22

n Use of “#define”
Names can be defined using “#define” anywhere within the initial step.
The defined names can then be used in any SEBOL-written step and transition condition.

SEE
ALSO For the details of “#define”, see the following:
“n #define Statement” in H1.1.8,“Substitution of Character String”

n Use of “#include”
“#include” can be specified for file-inclusion anywhere within the initial step.
The order of all statements in the included file, however, must be in conformity with that of the
initial step. Otherwise, an error is caused for the statements in the included file.

SEE
ALSO For the details of “#include”, see the following:
“n #include” in H1.1.9, “Include File”

n Use of “#IMPLICIT”
A “#IMPLICIT” command can be used in the initial step. The command is then valid within the
entire SFC block.
This command cannot be entered in any other steps.

SEE
ALSO For the details of “#IMPLICIT”, see the following:
“n #IMPLICIT Instruction” in H1.1.7, “Implicit Declarations of Variables”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.2 Action Description Using SEBOL> D5-23

D5.2.3 SEBOL Steps

The following items as to describing SEBOL steps are explained in this section:
• Order of description
• Example of description
• Restrictions

n Order of Description
The SEBOL step action should be described in order of variables and execution statements as
shown below; an error will be caused otherwise.

<Local variables/Local declaration>

<Action execution statement>
D050206E.ai

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.

n Example of Description
The following is an example of SEBOL-step description:
!local variable declaration
block PVI LI303
integer ierr

!action execution statement

wait until (LI303.PV >= 10.0) ; ierr
.......
quit

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.2 Action Description Using SEBOL> D5-24

D5.2.4 SEBOL One-Shot Steps

The following items as to describing SEBOL oneshot steps are explained in this section:
• Order of description
• Example of description
• Execution
• Restrictions

n Order of Description
The SEBOL oneshot-step action should be described in order of variables and execution
statements as shown below; an error will be caused otherwise.

<Local variables/Local declaration>

<Action execution statement>
D050207E.ai

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.

n Example of Description
The following is an example of SEBOL oneshot-step description:
!local variable declaration
block %SW SW301, SW302

!action execution statement

SW301.PV = 1
SW302.PV = 1
quit

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.2 Action Description Using SEBOL> D5-25

n 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 “@.”
• “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.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.3 Action Description Using Sequence Table> D5-26

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

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.3 Action Description Using Sequence Table> D5-27

D5.3.1 Step Common Item Description Using the Sequence

Table
Items common to all sequence table steps are as follows:
• Tag name
• Step name
• Variable to store action-signal column parameter or sequence table-condition testing
result

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

n Step Name
The step name can be specified for the sequence table step as described below:
Table Step Name Specification
Specification Action
No specification (default) The first step is executed.
An execution step name
The specified step is executed.
specified using up to 2 characters.
Continuation is specified. The current step is executed (*1)
D050301E.ai

*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
ALSO For the details of sequence tables, see the following:
D3.2, “Sequence Table Block (ST16, ST16E)”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.3 Action Description Using Sequence Table> D5-28

n Specified Variable to Store Action-signal Column Parameter or

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

x: Stored.
Blank: Not stored.

These variables will be ignored if their names are not specified in step action.

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

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.3 Action Description Using Sequence Table> D5-29
l 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
ALSO For the details of sequence tables, see the following:
D3.2, “Sequence Table Block (ST16, ST16E)”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.3 Action Description Using Sequence Table> D5-30

D5.3.2 Sequence Table Steps

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

n Step Action Description

The sequence table step action is described using a periodic start sequence table (TE or TC).

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.3 Action Description Using Sequence Table> D5-31

D5.3.3 Sequence Table One-Shot Steps

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

n Step Action Description

The sequence table one-shot step is described using a non-step sequence table (OE or OC).

n Step Execution
The sequence table one-shot step is oneshot-executed when its action is activated. The
sequence table block mode remains unchanged.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.4 Action Description Using Logic Chart> D5-32

D5.4 Action Description Using Logic Chart

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

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.4 Action Description Using Logic Chart> D5-33

D5.4.1 Step Common Item Description Using Logic Chart

Items common to all logic chart steps are as follows:
• Tag name
• Variable to store action signal column parameters

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.4 Action Description Using Logic Chart> D5-34

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

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

l 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.
<global variable>
• Tag name-specified function-block data item
When storing data as a data item in the tag name-specified function block, specify the
variable name as follows:
<tag name>.<data item>
In this case, the tag name should have been declared using “global block” in the initial step.
• Global generic name-specified function-block data item
When storing data as a data item in the global generic name-specified function block,
specify the variable name as follows:
<global variable>.<data item>
The global generic name, which must be a simple variable, should be declared using “global
block” in the initial step.

SEE
ALSO For the details of logic chart, see the following:
D3.3, “Logic Chart Block (LC64)”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.4 Action Description Using Logic Chart> D5-35

D5.4.2 Logic Chart Steps

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

n Step Action Description

The logic chart step action is described using a periodic start logic chart (TE).

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.4 Action Description Using Logic Chart> D5-36

D5.4.3 Logic Chart One-Shot Steps

The following method of describing logic chart one-shot steps is explained in this section.
• Step execution

n Step Execution
The logic chart one-shot step is one-shot-executed when the step is activated. The logic chart
block mode remains unchanged.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.5 Transition Conditions> D5-37

D5.5 Transition Conditions

The following methods as to describing transition conditions are explained in this
section:
• Description of transition conditions
• Variables applicable to transition conditions

n Description
Conditional expressions is SEBOL statement are used to define conditions for the transition of
steps.
The same manner of describing the transition condition applies to all types of steps.
The condition is satisfied when the result of the conditional expression is not zero and not satisfied
when it is zero. When equivalence operators (==, <>) or relational operators (>=, <=, >, <) are
used, the condition is satisfied when the relation is true (1) and not satisfied when it is false (0).
For a selective sequence, up to eight transition conditions can be defined. It is not 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.

n Variables
The following variables can be used in the conditional expressions for transition:
Table Variables Applicable to Conditional Expressions
Variable Remarks
Constant -
Global variable -
Local variable Declared in step action.
Global tag name Tag name declared using “global block.”
Tag name declared using “block” in SEBOL-step action.
Tag name Sequence table tag name in sequence table step action.
Logic chart tag name in logic chart step action.
Global generic name Generic name declared using “global genname.”
Local generic name Declared using “genname” in step action.
Declared using “global unit genname,” or declared using
Unit generic name
“unit genname” in step action.
Replaced by tag name of action-written sequence
%$
table/logic chart.
D050501E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-38

D5.6 SFC Block Action

The SFC block is designed to execute SFC-written programs.

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

l 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

l Interrupt Programs
• Status change
This program is run together with SFC block status change. Separated programs before/
after status changes may be implemented.
• Interrupt signal
Interrupt signal interrupts the SFC main program to run the programs requested by the
interrupt signal.
• Error processing
Error occurrence when SFC block is running may trigger an interrupt program for error
processing.

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

n SFC Block Execution Timing

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

n SFC Block Data Items

SFC blocks have fixed data items as well as user-definable data items.

n SFC Block Status

SFC block running state can be indicated by block mode and block status.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-39

n Interrupt Programs
Interrupt programs must be described separately for every different purpose.
When the block status has been changed and if it is necessary to pause or terminate the process,
an interrupt program or programs can be executed as required. For example, the heater needs to
be stopped if the process is to be terminated during heating, or the valve needs to be closed if the
process is to be paused during tank charging.
An example of executing an interrupt program for pausing from the main program, which contains
SIGNAL 1, RUN, STOP, and PAUS interrupt steps is shown below:

Main program

Interrupt steps

01 SIGNAL 1

02 RUN

03 STOP

04 PAUS

Developed

PAUS interrupt program

01

02

D050601E.ai

Figure Example of Interrupt Program Execution

Although the first step of the interrupt program is shown in a double square in the above example,
it does not mean that the step is the initial step.
Global variables cannot be declared using “global integer” nor “global block” for the first step of
an interrupt program. They can be read or written, however.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-40

n 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
• Error processing

The following steps can be used in these interrupt programs as well as the main program:
Table Steps Applicable to SFC Programs
Program
Step Main Status change Status change Interrupt signal Error
program pre-processing post-processing processing processing
Initial step x
SEBOL step x x x x
SEBOL one-shot step x x x x x
Sequence table step x x x x
Sequence table
x x x x x
one-shot step
Logic chart step x x x x
Logic chart
x x x x x
one-shot step
Interrupt step x
D050602E.ai

Note: Transition can be defined for programs other than the status change pre-processing program.
x: Applicable
Blank: Not applicable

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-41

n Interrupt Program Parameters

Parameters must be specified according to the type of interrupt processing.

l For Status Change Pre-processing & Post-processing

One of the following parameters needs to be specified according to which status change
instruction is to be executed:
• RUN
Starts the SFC block or restarts the paused SFC block.
• STOP
Terminates the SFC block being executed.
• PAUS
Pauses the SFC block being executed.

SEE
ALSO For more information, see the following:
D5.6.2, “Status Change Processing”

l For Interrupt Signal Processing

The name of the signal needs to be specified to execute the interrupt program.

SEE
ALSO For more information, see the following:
D5.6.3, “Interrupt Signal Processing”

l For Error Processing

No parameter can be specified for error processing.

SEE
ALSO For more information, see the following:
D5.6.4, “Error Processing”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-42

D5.6.1 Queue Signal Processing

Queue signals are processed in the SFC main program.

n Signal Declaration
Queue signals to be sent to the SFC block must be so declared in the initial step using the “queue
signal” statement.

queue signal<signal name>[,<signal name>…]

<signal name> a character string constant using up to 8 bytes.

D050603E.ai

• 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"

n 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
ALSO • For the details about queue signal transmission, see the following:
H1.12.1, “Signal Transmission Processing”
• For the details about pending signal manipulation, see the following:
H1.12.2, “Processing of Queue Signal”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-43

n Fetching Queue Signals

▼ Maximum Number of Queue Signal Parameters, Maximum Number of Acceptable Queue Signal
Parameters
The first signal in the queue is fetched for processing when the “wait for qsignal” statement (see
below) is executed in the SFC block.

• Format used to wait for signal-receiving only:

wait for qsignal<signal name-storing variable>

• Format used to wait for signal-receiving or until the expressed condition is satisfied:
wait for qsignal<signal name-storing variable>(<expression>)
[;<error variable>][; error <label>[,<error identifier>]]
errorsub
<signal name-storing variable>: Character-string local variable to store received
signal names.
<error variable>: Local variable for code-setting when error is caused
(0 when no error is caused).

<label>: Branching destination when error is caused.

<error identifier>: Local variable or constant to identify error-caused
location in the error handling phase.

D050604E.ai

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.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-44
l 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.

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

SEE
ALSO For the details of error processing, see the following:
H1.13, “Error Handling”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-45

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

creadpara(<parameter number>)
lreadpara(<parameter number>)
dreadpara(<parameter number>)

<parameter number> : 1 to 8 (integer constant or variable),

0 for “creadpara” reads the signal name.

D050605E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-46

n Examples of Queue Signal Processing

Examples of queue signal processing using the two formats of the “wait for qsignal” statement
are shown below.

l Waiting for Signal-Receiving Only

An example of executing the format-1 “wait for qsignal” statement:
......
01 Initial step queue signal "SG1", "SG2"
......

char*16 signame
J01
wait for qsignal signame
02 Waiting for signal
! Signal name set at signame.
......

signame == "SG1" signame == "SG2"

03 "SG1" process 1 05 "SG2" process 1

04 "SG1" process 2 06 "SG2" process 2

J01 J01
D050606E.ai

Figure Example of Queue Signal Processing Using Format-1 Statement

The “wait for qsignal” statement is executed in step 2 and a signal is fetched from the queue.
The signal name is then evaluated according to the transition condition defined following step 2,
selecting either SG1 or SG2 for processing.

l Waiting for Signal-Receiving or Satisfied Condition

An example of executing the format-2 “wait for qsignal” statement:
......
01 Initial step queue signal "SG1", "SG2"
......

char*16 signame
J01
wait for qsignal signame (<expression>)
02 Waiting for signal
! Signal name set at signame.
......

signame == "" signame == "SG1" signame == "SG2"

Process when
03 <expression> is 04 "SG1" process 1 06 "SG2" process 1
satisfied

05 "SG1" process 2 07 "SG2" process 2

J01 J01 J01

D050607E.ai

Figure Example of Queue Signal Processing Using Format-2 Statement

The “wait for qsignal” statement is executed in step 2, determining to wait for a signal or to
calculate the expression. The result of the expression is checked for the first transition condition
defined following Step 2. Either SG1 or SG2 is selected for processing according to the other two
transition conditions.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-47

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

l QUEUE Definition
Data item QUEUE can be defined for the purpose of referencing the queue of signals as follows:
• Define a CHR16 one-dimensional array named QUEUE. No data type other than character
strings nor simple variables cannot be used.
• Specify 1 to 32 array elements. Any elements specified exceeding 32 are ignored.
• Do not define QUEUE if there is no need for referencing the queue of signals.

Use the Function Block Detail Builder to specify the use of signal names and parameter numbers
for QUEUE array elements. The parameter numbers specified are then used as reference signal
parameter numbers. The signal name is set if the reference signal 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.

l Example of Referencing
When the queue has four signals, for example, referencing can be made as described below:

SG1 SG2 SG2 SG1

SUMMER AUTUMN WINTER SPRING

*1 *1 *1 *1

*1: The first parameter

D050608E.ai

Figure Queue Holding Four Signals

If the reference signal parameter number is 1, the contents of QUEUE array elements are as
follows:
Queue[1] = "SUMMER"
Queue[2] = "AUTUMN"
Queue[3] = "WINTER"
Queue[4] = "SPRING"
Queue[5] = " "
.....
Queue[10] = " "

QUEUE[5] to QUEUE[10] are null-length character strings since there are no signals.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-48

D5.6.2 Status Change Processing

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

n Processing Flow - SFC

The flow of processing when the SFC block receives a status change command is shown below:

Status change command received

No
Is the command viable?

Yes
Executed as the
Status-change pre-process command is received.

No
Is the change feasible?

Yes

Status change executed

Status-change post-process

End
D050609E.ai

Figure Flow of Status Change Process

As the SFC block receives a status change command, the feasibility of the commanded change
and the interrupt processes are checked in relation to the current status. The conditions for block
status changes are shown below:
Table Feasibility of Block Status Change
Status commanded for change
Current status
STOP RUN PAUS RSET ABRT
STOP (*1) xx xx
RUN xx (*1) xx x
PAUS xx xx (*1) x
ABRT x (*1)
D050610E.ai

xx: Status change feasible. Both pre- & post-processes executable.

x: Status change feasible, but pre- & post-processes not executable.
Blank: Status change not feasible.
*1: Command ignored.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-49
l 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.

IMPORTANT
The command to change the status to ABRT is a command to forcibly terminate the SFC block
and should not be used during normal operation. It may be used if the SFC block is locked due to
application error causing infinite looping during status-change post-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.

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

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

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-50

n 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.
• SEBOL one-shot execution step (SEBOL one-shot)
• Sequence table one-shot execution step (Sequence table one-shot)
• Logic chart one-shot execution step (Logic chart one-shot)

Since the status-change pre-process is one-shot-executed, it must be completed as quickly as

possible. Do not access data of another control station and delay the process. Only one step can
be executed as pre-process, where no transition condition can be defined.
STOP
01 Pre-process
D050611E.ai

Figure Status-Change Pre-Process

At the SEBOL and sequence table one-shot steps, the feasibility of status change can be
determined. With the logic chart one-shot step, the status can be changed. If the pre-process is
not defined, the status can also be changed. At the pre-process, the status and mode of the pre-
process-described SFC block or other SFC blocks cannot be changed.

l Pre-Processing Using SEBOL Oneshot Step

The SEBOL oneshot step is completed when the last line, or “return” or “quit” statement has been
executed.
If the last line or “quit” statement has been executed, the feasibility of status change is justified.
If the “return” statement has been executed, the feasibility of status change is determined
according to the returned value as follows:

return[<status change feasibility>]

<status change feasibility>: Integer constant or numerical expression.

==0: Change denied.
<>0: Change justified.
Omitted: Change justified.
D050612E.ai

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.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-51
l Pre-Processing Using Sequence Table One-Shot Step
In the sequence table one-shot step, the feasibility of status change is determined according to
the result of sequence-table evaluation. The status change is justified when the result is true (1)
and denied if false (0).
• Non-step sequence table:
The condition testing result is true (1) when at least one of 32 rules is satisfied and false (0)
if none of them is satisfied.
• Step sequence table:
All rules of the oneshot-executed step and step 00 are evaluated and the result is true (1)
when at least one of the rules is satisfied and false (0) if none of them is satisfied.

In the pre-process, no variable can be specified to receive the condition testing result, any
specified variable is ignored. The block status and mode cannot be changed in pre-processing
for the SFC block in which the pre-process is defined or for any other SFC block.

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

n Status-Change Post-Process - SFC

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

IMPORTANT
The post-process should not be kept suspended by means of a selective sequence 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.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-52

n 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 BSTS & PREBSTS
RUN → STOP PAUS → STOP
Process being executed
BSTS PREBSTS BSTS PREBSTS
Status-change pre-process RUN (*1) PAUS (*1)
Status-change
STOP RUN STOP PAUS
post-process
D050613E.ai

*1: Status before changing to the commanded status.

l 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

l 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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-53

D5.6.3 Interrupt Signal Processing

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

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-54

n Interrupt Signal Processing - SFC

▼ Maximum Number of Receive Interrupt Signals
Interrupt signals are processed interrupting the main program, which resumes execution as soon
as the signal has been processed.
Main program Interrupt signal processing

Interrupt signal received

D050616E.ai

Figure Interrupt Signal Processing

Interrupt signals can be processed only when the SFC block is in the RUN status. The signal
processing is canceled if the status is changed to PAUS during the processing and will not be
resumed when the status is returned to RUN.
If another interrupt signal is received while one is being processed, the received signal is queued
and will be processed as soon as the current processing is completed. The 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” and “return” statements:
• Using “quit” statement
Executing this statement terminates the current step action and executes the next step.
Executing it in a selective sequence starts evaluation of transition conditions. Executing the
statement in the last step of interrupt signal processing terminates the process.
• Using “return” statement
Executing this statement terminates the process without executing the remaining steps. Any
operand specified in this statement will be ignored.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-55

n Fetching Interrupt Signal Parameters

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

creadpara(<parameter number>)
lreadpara(<parameter number>)
dreadpara(<parameter number>)

<parameter number> : 1 to 8(integer constant or variable),

0 for “creadpara” reads the signal name.

D050617E.ai

“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 fetch
character-string, integer, and real-number signal parameters respectively.
The maximum number of signals can be defined in a range of 2 to 8 (2 at default) for the
parameter attached to an interrupt signal. If the SFC block receives an interrupt signal exceeding
its parameter setting, the signal is ignored causing an error.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-56

D5.6.4 Error Processing

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

n Error Processing Description

Similar to other interrupt processes, error processing needs to be defined in an SFC block
separately from the SFC block of the main program. Only one set of processing can be described
in one SFC block.
Both step and selective sequences can be used in error processing. It is necessary for a selective
sequence, however, that the transition conditions are so defined that they can be easily satisfied;
the process being executed when error is caused will not be resumed otherwise.

SEE
ALSO For the details of common error processing, see the following:
H1.13, “Error Handling”

The execution of the error processing defined in a SEBOL step can be controlled using “quit” and
“return” statements:
• Using “quit” statement
Executing this statement in a step sequence terminates the current step action and
executes the next step. Executing it in a selective sequence starts evaluation of transition
conditions. Executing the statement in the last error processing step terminates the process.
• Using “return” statement
Executing this statement terminates error processing without executing the remaining steps.
Any operand specified in this statement will be ignored.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-57

D5.6.5 Terminating SFC Block Execution

The execution of the SFC block can be terminated as described below:

n Programs Permitted of Terminating Execution

The execution of the SFC block can be terminated in one of the following manners:
• Executing an “exit” statement.
• Changing block data item BSTS to STOP.

The programs which permit terminating the block execution are as follows:
Table Programs Permitted of Terminating Block Execution
Program “exit” statement BSTS change
Main program x x
Status-change pre-process - -
Status-change post-process x -
Interrupt signal processing x x
Common error processing x (*1)
D050618E.ai

x: Definable.
–: Not definable.
*1: The feasibility of block status change during error processing is determined by the location where the error involved has been
caused. If the error is in the main program, the status can be changed. If the error is in the status-change post-process, the status
cannot be changed.

n Termination Using “exit” Statement

Use the “exit” statement to terminate the block execution unconditionally, which can be written as
follows:

exit[<expression>]
D050619E.ai

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.

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-58

D5.6.6 Pausing SFC Block Execution

The execution of the SFC block is paused in one of the following conditions, which are
further described below:
• When the block mode is SEMI.
• When the block being executed receives the command to change the status to PAUS.
• When the block standing-by for execution receives the command to change the
status to PAUS.
• When the block standing-by for execution in the SEMI mode receives the 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.

n 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:

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

l PAUS Command to Block in Execution

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

l 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.
• Status-change processing takes place.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-59
l 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.

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

l “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.

l “delaycycle” and “delay” Statements Used

The time specified to “delaycycle” and “delay” statements advances even while the block is
paused.

l “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.

l “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.

l “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.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-60
l “logicchart drivewait” Statement Used
When the block has been paused while waiting for the output of an SFC/SEBOL return event
message (%RE) from the logic chart after starting the logic chart using a “logicchart drivewait”
statement, the logic chart block mode remains AUT. The block is restarted from the line following
the “logicchart drivewait” statement if %RE is output from the logic chart during the pause. If not,
the state of waiting for the output will be maintained.

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

l “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.

l “ckstep” Returns “1”

• “ckstep” returns “1” when the SFC block was paused, STEPNO has been changed, and
then restarted.

l Cases of “0” Returned by “ckstep”

• When the block is being executed without being paused.
• When the block was paused at the start of a step in the SEMI mode and has been restarted
without changing STEPNO.
• For interrupt signal processing, “0” is returned at all times.
• For status-change pre-processing, “0” is returned at all times.
• For status-change post-processing, “0” is returned at all times.
• For error processing, “0” is returned at all times.
• When the built-in function “ckstepcl” is executed to clear the status following a pause.
• When the action of the restarted step has been completed.

SEE
ALSO For the changing of data item STEPNO, see the following.
D5.6.8, “Changing Current Step”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-61

n Restarting Actions
Actions when the SFC block is restarted with its status changed to RUN are described:

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

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

l Restarting after Paused during Transition Evaluation

Evaluation is restarted from the leftmost transition condition.

l Restarting after Paused during Interrupt Signal Processing

The interrupt signal process is canceled and not resumed when the block is restarted.

l Handling of Queued Signals when Restarted

Any signals already queued when the block was paused remain in the queue when the block is
restarted.

l Handling of Signal Received during Pause

Any signals received during the pause are queued and available when the block is restarted.

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-62

D5.6.7 Referencing Current Step

The step number of the step being executed in the SFC block main program can be
referenced.

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-63

D5.6.8 Changing Current Step

The following items as to changing the current step are explained in this section.
• Procedure
• Restrictions
• Actions after STEPNO change

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

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

n 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.”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-64

D5.6.9 SFC Block Alarm Processing

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

n SFC Block Alarm Processing Scripts

Unlike regulatory control function blocks, SFC blocks do not have built-in alarm processing
functions. Thus alarm processing and alarm status indication must be programmed using
SEBOL, if required.
There are four process alarm related data items of the SFC block shown as follows:
• ALRM (Alarm Status)
• AF (Alarm Detection)
• AOFS (Alarm Inhibition)
• AFLS (Alarm Flashing Status)

ALRM (Alarm Status)

The alarm status strings for indicating SFC alarm status contains 23 user-defined strings and a
NR string (string for normal status), which can be specified for all SFC blocks.
If there is no alarm status is in active state, the data item ALRM will be in NR status.
When using a “prcsalarm” statement in a SEBOL step, an alarm status string and a process
alarm can be output together. Using “prcsalarm recover” statement can recover from the alarm
status.

SEE
ALSO • For more information about AF, AOFS and AFLS, see the following:
C5.13, “Deactive Alarm Detection”
C5.14, “Alarm Inhibition (Alarm OFF)”
C5.15.1, “Alarm Display Flashing Actions”
• For more information about changing and referencing alarm data items, see the following:
H1.5.10, “Referencing Alarm Status”
H1. 5.12, “Referencing Alarm Status Individually”
• For more information about alarm status character strings, see the following:
“n User-Defined Alarm Status Character String” in Chapter E10.4, “Alarm Status Character String and
Alarm Processing”

n 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 Alarm Status Change Commands
Status-change command
Data item
AOF AON ACK
AF Alarm detection group-bypassing. Alarm group-suppression. -
AOFS Undo group-bypassing. Undo group-suppression. -
AFLS - - Alarm group-acknowledging.
D050620E.ai

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-65

n Changing Alarms of Other SFC Blocks

Process alarms of other SFC blocks can be controlled changing data items AF and AOFS.
The SFC block with its data item AF externally specified for the group-bypassing of alarm
detection, for example, will not output any process alarm and the alarm status will not be changed
even when the “prcsalarm” statement is executed by the present block. Also, changing data item
AFLS permits alarm acknowledging while disabling flashing.

n Alarm Data Items

The alarm data items are initialized as follows:
Table Data Item Initialization
When initialization When SFC block
Data item Name Builder default
started executed
ALRM Alarm status NR NR
AF Alarm detection specification Previous status
maintained Previous status Despecified
AOFS Alarm suppression specification maintained status
AFLS Alarm flashing status
D050621E.ai

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.

n 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
ALSO For more information, see the following:
C5.15.2, “Repeated Warning Alarm”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-66

D5.6.10 SFC Online Maintenance

In online maintenance operation, SFC block databases can be manipulated for system
retrofitting, modification, and so forth.

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

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

n Block Manipulation
SFC blocks can be changed, deleted, or added in the following cases:
• SFC blocks can be changed or deleted when they are stopped.
• SFC blocks can be added as long as additions are within the maximum number of function
blocks defined for each control station.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-67

D5.6.11 SFC Block Execution

SFC blocks are executed in the idle time of one control period after the execution of all
other basic control functions.

n 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:

Control drawing 1

SFC block SFC block SFC block

1 2 3

Control drawing 2

SFC block SFC block SFC block

4 5 6

D050622E.ai

Figure The Order of Execution Time Allocation

After the last SFC block 6 in control drawing 2 was allocated with execution time, the order
returns to the top SFC block 1 in control drawing 1 and execution time is reallocated. Execution
time is not allocated to any SFC blocks which are not being executed.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-68

D5.6.12 Data Items - SFC

SFC blocks use system-specific and user-defined data items.
Every different SFC block using a different group of data items needs to be 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.

n SFC Block Models

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

Basic type - - x
None x x -
Trend
PV, SV, MV - - x
D050623E.ai

The instrument faceplates of the three block models are shown below:

AUT STOP AUT STOP AUT STOP

NR NR NR
100.0
RUN RUN RUN
80.0

60.0
PAUSE PAUSE PAUSE
40.0

20.0

STOP STOP STOP

0.0

_SFCSW _SFCPB _SFCAS

D050624E.ai

Figure SFC Block Instrument Faceplates

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-69

n System-Specific Data Items

▼ System Definition Data Items
SFC block system-specific data items and their availability in block models are listed below:
Table System-Specific Data Items & Block Models (1/2)
SFC block model
Data item Data name
_SFCSW _SFCPB _SFCAS
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
D050625E.ai

x: Available

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-70
Table System-Specific Data Items & Block Models (2/2)
SFC block model
Data item Data name
_SFCSW _SFCPB _SFCAS
OPMK Operation mark x x x
SAID System user ID 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
D050626E.ai

x: Available
–: Not available

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-71
The accessibility of the system-specific data items is shown below:
Table System-Specific Data Item Accessibility (1/2)
General-purpose
SEBOL Sequence table
Data item calculation block
Read Write Read Write Condition Manipulation
MODE x x x (*1) x (*1) x x
OMOD x - - - - -
CMOD x - - - - -
BSTS x x x (*1) x (*1) x x
PREBSTS x - - - x -
ALRM x - x (*1) - x -
AFLS x x x (*1) x (*1) x x
AF x x x (*1) x (*1) x x
AOFS x x x (*1) x (*1) x x
ERRC x - x - - -
ERRE x - x - - -
ERRP x - x - - -
ERRS x - x - - -
ERRL x - x - - -
ERRF x - x - - -
STEPNO (*2) x x x x x x
PHASE x - x - - -
IPHASE x - x - - -
D050627E.ai

x: Accessible
–: Not available
*1: Accessible by connecting sequences.
*2: See D5.6.8, “Changing Current Step,” for restrictions.

SEE
ALSO For details on setting step numbers, see the following:
D5.6.8, “Changing Current Step”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-72
Table System-Specific Data Item Accessibility (2/2)
General-purpose
SEBOL Sequence table
Data item calculation block
Read Write Read Write Condition Manipulation
OPMK x x x x - -
SAID 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 - - -
D050628E.ai

x: Accessible
–: Not available

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-73
l Step-Number & Phase-Name Data Items
Step numbers and phase names are set in the following data items:
• Main program
Step No.: STEPNO
Phase name: PHASE
• Interrupt programs
Step No.: None
Phase name: IPHASE
The main program current step number is set at STEPNO and current phase name at PHASE.
The interrupt program current phase name is set at IPHASE. During the execution of an interrupt
program, the step number and the phase name of the main program when the interrupt program
was invoked are retained at STEPNO and PHASE respectively.

TIP
One exception with interrupt programs is that the phase name of status-change pre-processing is not set at
IPHASE.

When interrupt programs of different levels are being executed simultaneously, only the phase
name of the highest-level interrupt program is set at IPHASE. A null-length character string (“”) is
set at IPHASE for a regular-level interrupt program.
Default STEPNO, PHASE, and IPHASE are as follows:
Table Default STEPNO, PHASE, & IPHASE
Data item Name Builder default At initialization At SFC block start
STEPNO Current step number 0 Step number of initial step
Previous state
PHASE Phase name “” (*1) retained Phase name of initial step
IPHASE Interrupt program phase name “” (*1) “” (*1)
D050629E.ai

*1: Null-length character string.

l Alarm Data Items

ALRM, AFLS, AF, and AOFS are process alarm data items.

SEE
ALSO For details, see the following:
D5.6.9, “SFC Block Alarm Processing”

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-74

n User-Defined Data Items

▼ User Definition Data Items
Up to 32 data items can be optionally user-defined, using up to 8180 bytes in total.

l Date Types Available

The following data types can be used for user-defined data items:
Table Data Types of User-Defined Data Items
Data type Symbol No. of bits Min. data Max. data
Character string CHRn 8*n bits n=2 n=16
Integer I16 16 bits -32768 32767
Long integer I32 32 bits -2147483648 2147483647
38 38
Single-precision floating point F32 32 bits -3.402823*10 3.402823*10
308 308
Double-precision floating point F64 64 bits -1.79769313486231*10 1.79769313486231*10
D050630E.ai

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

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-75
l 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
ALSO For the details of queue signals, see the following:
D5.6.1, “Queue Signal Processing”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-76

D5.6.13 SFC Block Mode & Status

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

n Block Modes - SFC

▼ SEMI Mode Operation
The SFC block has three control modes.

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

l 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"
......

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-77

n SFC Block Status

The SFC block status shows the SFC block operation status as executing, paused, stopped, and
aborted.
The SFC block has four status as described below:
Table SFC Block Status
Name Status Description
STOP Stopped The block is stopped and standing-by for a start command.
RUN Executing Step actions are being executed or transition conditions are being evaluated.
PAUS Paused Execution is suspended.
ABRT Aborted Execution has been aborted due to fatal or internal error or insufficient memory.
D050631E.ai

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.

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.6 SFC Block Action> D5-78

n Transition of SFC Block Status

▼ PAUS Stop Position
The transition of block status when the SFC block is in the AUT or SEMI mode is described.

PAUS

PAUS
PAUS ABRT
(*3) (*1)
STOP RUN

RUN ABRT
STOP RUN ABRT
STOP (*1)
(*2)

RSET
*1: Status changes also in case of fatal or internal error, or insufficient memory.
*2: Status changes also when execution is terminated by the “exit” or “end” statement.
*3: Status changes at the start of a step when the block mode is SEMI.
D050632E.ai

Figure Transition of Block Status

• The RUN command starts execution of the SFC block in the STOP status, which then
changes to RUN when started.
• The PAUS command suspends execution of the SFC block in the STOP status at the start
of the initial step, the status then changes to PAUS.
• The stopping position when the status is changed to PAUS during execution of a SEBOL
step action can be specified either at the start of the step or the current 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"
......

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.7 Manipulating Unit Instrument from SFC Block> D5-79

D5.7 Manipulating Unit Instrument from SFC

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

n Accessing Unit Data

Unit data can be accessed from the SFC block as described below.
Use one of the following manners to access unit data:
• Declare the unit tag name using the “block” or “global block” statement. Or assign the
unit tag name using the “assign” statement to the local generic name in the “genname”
statement or the global generic name in the “global genname” statement.
• Define the unit data name in place of the function block data item name.

An example of accessing unit data from a SEBOL step is shown below:

!_UTSW is the unit model name.
block _UTSW UNIT001
char*8 umode, ustat
!Acquire the mode.
umode = UNIT001.MODE
!Acquire the status.
ustat = UNIT001.BSTS
.....

The <block model> referred by “block” statement, or etc., are the model name of unit function
blocks displayed in the Function Block Detail Builder.
The following three models of unit are supported.
• _UTSW: Non-Resident Unit Instrument with Three-Position Switch
• _UTPB: Non-Resident Unit Instrument with Five-Pushbutton Switch
• _UTAS: Analog Non-Resident Unit Instrument

SEE
ALSO For the details of unit instruments, see the following:
D6.2, “Unit Instrument”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00

 <D5.7 Manipulating Unit Instrument from SFC Block> D5-80

n Transmitting Signals to Units

Signals can be transmitted to units from the SFC block using the “signal” statement. Upon
receiving a signal, the unit sends the same signal to every unit operation being executed.

signal<signal name>[,<signal parameter>…]to<tag name>

[;<error variable>] [;error <label>[,<error identifier>]]

errorsub
<signal name>: A character string constant or variable using up to 8 bytes.
<signal parameter>: An integer, long, float, or double-type numeric expression, or a
character string (effective up to the leading 16 bytes). Up to 8
parameters can be specified.
<tag name>: The tag name of the destination unit for signal transmission. The
“block” statement-declared tag name, “gene” statement-declared local
generic name, or “argblock” statement-declared formal-argument
function block can be used. Specify “%%” for the present unit.
<label>: A branching destination for error processing.
<error identifier>: A constant or local variable to identify the error-caused location in
error processing.

D050633E.ai

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
ALSO For the details of operations, see the following:
D6.8, “Operations”

IM 33M01A30-40E 1st Edition : Mar.23,2008-00