Centum VP 1B30 01 PDF

Toc A-1
CS 1000/CS 3000
Reference
Field Control Station Basics
IM 33S01B30-01E 10th Edition
CONTENTS
PART-A FCS Common
A1. Functional Overview of Field Control Station (FCS) ........................... A1-1
A1.1 Types of FCS Model ...................................................................................... A1-2
A1.2 Structure of the FCS Functions.................................................................... A1-8
A1.2.1 Control Calculations ........................................................................ A1-9
A1.2.2 Process Input/Output and Software Input/Output .......................... A1-11
A1.3 Types of FCS Databases ............................................................................. A1-13
A1.4 Function Block List ..................................................................................... A1-16
A2. Outline of Input and Output Interfaces ................................................ A2-1
A3. Process Inputs/Outputs ....................................................................... A3-1
A3.1 Analog Inputs/Outputs ................................................................................. A3-2
A3.1.1 Analog Input ................................................................................. A3-10
A3.1.2 Analog Output .............................................................................. A3-11
A3.2 Contact Inputs/Outputs .............................................................................. A3-12
A3.2.1 Contact Input ................................................................................ A3-18
A3.2.2 Contact Output ............................................................................. A3-20
A3.3 Configuring Process I/O of PFCS, LFCS2, LFCS and SFCS ..................... A3-31
A3.3.1 Control Input/Output Module Configuration ................................... A3-34
A3.3.2 Parameters for Multipoint Control Analog Input/Output .................. A3-54
A3.3.3 Parameters for Multiplexer and Multiplexer (Connector Type)
Inputs/Outputs .............................................................................. A3-59
A3.3.4 Parameters for Relay, Contact Terminal or Contact Connector ...... A3-74
A3.4 Configuring Process I/O of KFCS2 and KFCS ........................................... A3-82
A3.4.1 Parameters for FIO Analog Inputs/Outputs .................................... A3-86
A3.4.2 Parameters for FIO Contact Inputs/Outputs ................................ A3-122
A3.4.3 HART Variable Setting Items ....................................................... A3-139
A4. Software Inputs/Outputs ...................................................................... A4-1
A4.1 Common Switch ............................................................................................ A4-8
A4.2 Global Switch .............................................................................................. A4-19
A4.3 Annunciator Message Output (%AN) ......................................................... A4-22
A4.4 Sequence Message ..................................................................................... A4-29
A4.5 Annunciator Message with Data ................................................................ A4-36
IM 33S01B30-01E 10th Edition : Dec.18,2003-00

Blank Page
<A1. Functional Overview of Field Control Station (FCS)> A1-1
A1. Functional Overview of Field Control

Station (FCS)
The field control station (FCS) is a device that performs process control. Several
types of FCSs are available for different applications and sizes. Furthermore, when
using an FCS, an appropriate database such as of general type, regulatory control
type, sequence control type and unit control type can be selected.
This chapter describes the FCS model types, function structure and database types.
In addition, at the end of this chapter, all the function blocks of the FCS are listed
according to the classifications used in this manual. Also, the classifications of
these function blocks in the databases are shown.

<A1.1 Types of FCS Model> A1-2
A1.1 Types of FCS Model

Several models of FCSs, such as a standard type, enhanced type and compact type,
are available according to the application.
This section explains an overview and station types of FCS models.
■ FCS Model Types ¡

As for the FCS models in the CS 1000, the standard type PFCS and extension type PFCS
are available for different applications.
In addition, in order to improve reliability, the CPU, power supply and control bus can be
made dual-redundant.
● Standard Type PFCS ¡

The standard type PFCS in the CS 1000 includes the following two station types:
• PFCS-S Field Control Station (standard type)
• PFCD-S Duplexed Field Control Station (standard type)
A standard type PFCS field control station is provided with a PFS1100 package “Standard
Control Function” as its basic software.
● Enhanced Type PFCS ¡

The enhanced type PFCS in the CS 1000 includes the following two station types:
• PFCS-E Field control station (Enhanced type)
• PFCD-E Duplexed Field Control Station (Enhanced type)
An enhanced type PFCS field control station is provided with a PFS1120 package “En-
hanced Control Function” as its basic software.

■ Types of FCS Models £
As for the FCS models in the CS 3000, the standard type, enhanced type and compact
type are available for different applications.
Enhanced type FCSs can be further divided into KFCS2 and LFCS2 vary with their I/O
components.
Standard type FCSs can be further divided into KFCS and LFCS vary with their I/O compo-
nents.
Compact type FCS is lined up with SFCS.
KFCS2 and KFCS are using FIO (Field Network I/O) and connected via ESB bus as input
and output components. While LFCS2 and LFCS are using RIO (Remote I/O) and con-
nected via RIO bus as I/O components.
In addition, the CS 3000 supports the “RFCS5” and “RFCS2” in order to achieve migration
from CENTUM V or CENTUM-XL. Furthermore, the “APCS” can be used for the purpose of
sophisticated control.
The following describes an overview and station types of the FCS model types.
● Enhanced Type FCS with FIO (KFCS2) £

This is an enhanced type FCS of CS 3000. This type of FCS is suitable for a control unit
with large amount of input and output signals.
The KFCS2’s control area is called the field control unit (FCU) in which an ESB bus inter-
face card is mounted. The “Extended Serial Backboard Bus (ESB bus)” is used for data
exchange between the ESB bus interface card and the input/output units.
The following four station types of KFCS2 FCU are available:
• AFG30S Field Control Unit (FIO, Rack Mountable)
• AFG30D Duplexed Field Control Unit (FIO, Rack Mountable)
• AFG40S Field Control Unit (FIO, Cabinet)
• AFG40D Duplexed Field Control Unit (FIO, Cabinet)
An enhanced type KFCS2 field control station is provided with an LFS1330 package
“Control Function for Enhanced Field Control Station (FIO)” as its basic software.

● Standard Type FCS with FIO (KFCS) £
This a CS 3000 standard type FCS.
The KFCS’s control area is called the field control unit (FCU) in which an ESB bus interface
card is mounted. The “Extended Serial Backboard Bus (ESB bus)” is used for data ex-
change between the ESB bus interface card and the input/output unit.
The following four station types of FCUs are available for the KFCS:
• AFS30S Field Control Unit (FIO, Rack Mountable)
• AFS30D Duplexed Field Control Unit (FIO, Rack Mountable)
• AFS40S Field Control Unit (FIO, Cabinet)
• AFS40D Duplexed Field Control Unit (FIO, Cabinet)
A standard type KFCS field control station is provided with an LFS1300 package “Control
Function for Standard Field Control Station (FIO)” as its basic software.
● Enhanced Type FCS with RIO (LFCS2) £

This is an enhanced type FCS of CS 3000. This type of FCS is suitable for a control unit
with large amount of input and output signals.
The LFCS2’s control area is called the field control unit (FCU) in which a RIO bus interface
card is mounted. The “RIO bus” is used for data exchange between the RIO bus interface
card and the input/output units.
The following four types of FCUs are available for LFCS2:
• AFG10S Field Control Unit (RIO, Rack Mountable)
• AFG10D Duplexed Field Control Unit (RIO, Rack Mountable)
• AFG20S Field Control Unit (RIO, Cabinet)
• AFG20D Duplexed Field Control Unit (RIO, Cabinet)
An enhanced type LFCS2 field control station is provided with an LFS1130 package “Con-
trol Function for Enhanced Field Control Station (RIO)” as its basic software.
● Standard Type FCS with RIO (LFCS) £

This is a standard type FCS of CS 3000.
The LFCS’s control area is called the field control unit (FCU) in which an RIO bus interface
card is mounted. The “RIO bus” is used for data exchange between the RIO bus interface
card and the input/output units.
The following four types of FCUs are available for the LFCS:
• AFS10S Field Control Unit (RIO, Rack Mountable)
• AFS10D Duplexed Field Control Unit (RIO, Rack Mountable)
• AFS20S Field Control Unit (RIO, Cabinet)
• AFS20D Duplexed Field Control Unit (RIO, Cabinet)
A standard type LFCS field control station is provided with an LFS1100 package “Control
Function for Standard Field Control Station (RIO)” as its basic software.

● Compact Type FCS (SFCS) £
The compact type FCS (SFCS) in the CS 3000 is suitable when distributing FCSs through-
out the plant. Since the SFCS supports high-speed communication, it is suitable for com-
munication with subsystems.
The following two station types are available for the SFCS:
• PFCS-H Field Control Station (Compact Type)
• PFCD-H Duplexed Field Control Station (Compact Type)
A compact type SFCS field control station is provided with an LFS1120 package “Control
Function for Compact Field Control Station” as its basic software.
● Migrated-FCS (RFCS5) £
The RFCS5 is configured by replacing the Station Control Nest of existing CENTUM V or
CENTUM-XL field control station with the Field Control Unit (FCU) of the CS 3000 KFCS2.
Since an SI bus interface card is mounted in the replacing FCU, the existing I/O nest area
can be connected to the FCU via the SI bus.
In addition, since an ESB bus interface card is mounted in the replacing FCU, the PI/O
components of the KFCS can be connected to the FCU via the ESB bus.
The following four station types are available for the RFCS5 that uses the SI bus:
• AFG81S Field Control Station (SIO/FIO, CENTUM V Migration Type)
• AFG81D Duplexed Field Control Station (SIO/FIO, CENTUM V Migration Type)
• AFG82S Field Control Station (SIO/FIO, CENTUM-XL Migration Type)
• AFG82D Duplexed Field Control Station (SIO/FIO, CENTUM-XL Migration Type)
SEE ALSO
For more information about RFCS5 and the SIO bus, see the following:
Migrated-FCS (FIO) (IM 33Q01B41-01E)
By replacing both the station control nest and input/output nest components the existing
CENTUM V or CENTUM-XL control station with the FCU of the KFCS2 and the PI/O
components, the existing signal conditioners can be connected to the replacing PI/O
components. In this case, an ESB bus interface card is mounted in the replacing FCU that
does not contain an SI bus interface card.
The following four station types are available for the RFCS5 that uses an ESB bus instead
of an SI bus:
• AFG83S Field Control Station (FIO, CENTUM V Migration Type)
• AFG83D Duplexed Field Control Station (FIO, CENTUM V Migration Type)
• AFG84S Field Control Station (FIO, CENTUM-XL Migration Type)
• AFG84D Duplexed Field Control Station (FIO, CENTUM-XL Migration Type)
RFCS5 is provided with an LFS1330 package “Control Function for Enhanced Field Control
Station (FIO)” as its basic software.

● Migrated-FCS (RFCS2) £
The RFCS2 is an FCS which is configured by replacing the station control nest area of the
field control station of the existing CENTUM V or CENTUM-XL with the field control unit
(FCU) of the KFCS in the CS 3000.
Since an SI bus interface card is mounted in the replacing FCU, the existing I/O nest area
can be connected to the FCU via the SI bus.
In addition, since an ESB bus interface card is mounted in the replacing FCU, the PI/O area
of the KFCS can be connected to the FCU via the ESB bus.
The following four station types are available for the RFCS2 that uses the SI bus:
• AFS81S Field Control Station (SIO/FIO, CENTUM V Migration Type)
• AFS81D Duplexed Field Control Station (SIO/FIO, CENTUM V Migration Type)
• AFS82S Field Control Station (SIO/FIO, CENTUM-XL Migration Type)
• AFS82D Duplexed Field Control Station (SIO/FIO, CENTUM-XL Migration Type)
SEE ALSO
For details on the RFCS2 that uses the SIO bus, see the following:
Migrated-FCS (FIO) (IM 33Q01B41-01E)
By replacing both the station control nest area and input/output nest area of the control
station of the existing CENTUM V or CENTUM-XL with the FCU of the KFCS and the PI/O
area, the existing signal conditioner can be connected to the replacing PI/O area. In this
case, an ESB bus interface card is mounted in the replacing FCU that does not contain an
SI bus interface card.
The following four station types are available for the RFCS2 that uses an ESB bus instead
of an SI bus:
• AFS83S Field Control Station (FIO, CENTUM V Migration Type)
• AFS83D Duplexed Field Control Station (FIO, CENTUM V Migration Type)
• AFS84S Field Control Station (FIO, CENTUM-XL Migration Type)
• AFS84D Duplexed Field Control Station (FIO, CENTUM-XL Migration Type)
RFCS2 is provided with an LFS1300 package “Control Function for Standard Field Control
Station (FIO)” as its basic software.

● Advanced Process Control Station (APCS) £
The advanced process control station (APCS) is a station that executes control calculations
in a personal computer (PC) for the purpose of sophisticated control and efficiency im-
provement. When function block data is input from an FCS via V net, the APCS performs a
control calculation at a constant cycle using a function block of the APCS, and then outputs
that calculation result as the function block data of the FCS.
The APCS can use the standard function blocks used by the FCS.
The process control input/output cannot be connected to the APCS.
The following station type is available for the APCS:
• APCS Advanced Process Control Station
SEE ALSO
For details on the APCS, see the following:
APCS (IM 33Q03M10-01E)

<A1.2 Structure of the FCS Functions> A1-8
A1.2 Structure of the FCS Functions

The FCS functions consist of the functions for control calculations and the func-
tions for process control input/output. This section describes the structure of the
FCS functions and an overview of each function.
■ Overall Structure of the FCS Functions ¡ £

The FCS consists of various types of function blocks that execute control calculations and
the input/output functions such as the process input/output and the software input/output.
FCS
Basic control Software I/O
Regulatory control blocks Common switch
Arithmetic calculation blocks Annunciator message
Sequence control blocks Sequence control message
Faceplate blocks
SFC blocks
Unit instruments
Options
Valve pattern monitoring (*1)
Off-site blocks (*1)
FCS I/O Interfaces
Process I/O Communication I/O Fieldbus I/O
A010201E.EPS
*1: ¡ £ This option can be applied in CS 3000 system only.
Figure Overall Structure of the FCS Functions ¡ £

A1.2.1 Control Calculations

Various function blocks are provided for the FCS to perform a variety of calculations
for plant control. A function block is a minimum unit used to perform a control
calculation. Various plant controls can be performed when function blocks process
signals that are input from a field device to the FCS, and the processing results are
output to other function blocks or any field devices.
The FCS has function blocks for performing the basic control and those that are
only available as options.
■ Basic Control ¡ £
The FCS has the following function blocks for executing the basic control.
● Regulatory Control Block ¡ £

The regulatory control block is used to execute calculation processing mainly using the
analog process amount in order to monitor and control processes.
The regulatory control block is classified into the input indicator block, controller block,
manual loader block, signal setter block, signal limiter block, signal selector block, signal
distributor block, alarm block, pulse count control block, YS instrument block and FOUN-
DATION fieldbus faceplate block (*1).
*1: ¡ £ KFCS2/KFCS/RFCS5/RFCS2 can support FOUNDATION fieldbus faceplate blocks.
● Calculation Block ¡ £
The calculation block is used to execute general-purpose calculation processing such as
arithmetic calculation, analog calculation and logic operation for values that are input to
function blocks in order to supplement regulatory control and sequence control.
The calculation block is classified into the arithmetic calculation block, analog calculation
block, logic operation block (*1), general-purpose calculation block and calculation auxiliary
block.
*1: ¡ £ The logic operation block can only be used for the CS 3000.
● Sequence Control Block

The sequence control is a type of control that processes each stage of control sequentially
according to the predefined conditions and order. The sequence control block is a function
block that executes sequence control.
The sequence control block is classified into the sequence table block, logic chart block,
SFC block, switch instrument block, sequence auxiliary block and valve monitor block.
● Faceplate Block
The faceplate block is a function block that enables the recognition of multiple function
blocks as a single function block.
The faceplate block is classified into the analog type, sequence type and hybrid type.

● SFC Block
The SFC (Sequential Function Chart) is a graphical programming language that defines
the sequence control operation.
The SFC block is a type of the sequence control block, which is also a function block that is
used to describe the SFC.
TIP
In addition to the SFC block, the SFC is also used in the following function blocks. However, a part of the
SFC specifications will vary among these function blocks.
• Unit instrument
• Operation
● Unit Instrument
The unit instrument is a function block that performs unit supervision. The unit supervision
is a function that controls and monitors the operation of devices that compose a process
facility, collectively called a unit, in a batch process or continuous process. The unit supervi-
sion enables the operation in equipment unit by defining the part corresponding to the
equipment in the process facility as a “unit” and allocating the “unit instrument” for each unit.
■ Option ¡ £
The following function blocks are available as options for the FCS:
● Valve Pattern Monitor £

The valve pattern monitor is a function block that monitors the open/close status of valves
for transfer systems in the plant.
● Off-Site Block £
The off-site block is a function block that controls the mixing at off-sites of oil refineries as
well as the shipments.
The off-site block is classified into the batch set control block (FSBSET) and blending
master control block (BLEND).

A1.2.2 Process Input/Output and Software Input/Output

The FCS exchanges data among the function blocks in the FCS and field devices
outside the FCS via process input/output, communication input/output or Fieldbus
input/output. Data can be exchanged by directly connecting among the function
blocks in the FCS or among FCSs. Data can also be exchanged via software input/
output.
■ Process Input/Output
The process input/output are used to exchange signals between field devices and FCSs.
Two types of process input/output – “analog input/output” and “contact input/output” –are
available depending on the type of the signal to be exchanged.
SEE ALSO
For details on the process input/output, see the following:
A3, “Process Inputs/Outputs”
■ Communication Input/Output
The communication input/output are used to access various types of data that are handled
by subsystems such as the PLC (Programmable Logic Controller).
SEE ALSO
For details on the communication input/output, see the followings:
Part J, “Subsystem Communication (Using RIO)”
Part K, “Subsystem Communication (Using FIO)”
Part N, “PROFIBUS”
■ Fieldbus Input/Output
The Fieldbus input/output are used to access various types of data that are handled by field
devices on the Fieldbus.
SEE ALSO
• For details on the Fieldbus input/output, see the followings in regarding to KFCS2, KFCS, RFCS5 or
RFCS2:
FOUNDATION fieldbus Reference (IM 33Y05P10-01E)
• For details on the Fieldbus input/output, see FOUNDATION fieldbus Tools (IM 33S05P10-01E) in regard-
ing to PFCS, LFCS2, LFCS or SFCS.

■ Software Input/Output
The software input/output are virtual input/output that are processed by software in the
FCS.
The software input/output consist of the “internal switch” that is used to change logical
values between function blocks and other application functions, and the “message output”
that is used to communicate the occurrence of events.
SEE ALSO
For details on the software input/output, see the following:
A4, “Software Inputs/Outputs”

<A1.3 Types of FCS Databases> A1-13
A1.3 Types of FCS Databases

The function blocks and number of I/O points (application capacity) that can be used
with the FCS are predefined in the FCS databases. Each database has specific
features such as a large number of usable points of specific types of function
blocks. When using an FCS, an appropriate database must be selected from the
available databases. This section presents an overview of the types of FCS data-
bases.
■ Standard Type PFCS Databases ¡

One of the following databases can be selected for the standard type PFCS:
• Regulatory Control Standard
• Regulatory Monitoring
• SEQ Monitoring
• SEQ Control Standard (Medium Sequence Capacity)
• SEQ Control Standard (Large Sequence Capacity)
• General-Purpose
■ Enhanced Type PFCS Databases ¡

One of the following databases can be selected for the enhanced type PFCS:
• Regulatory Control Enhanced (Loaded C programming language)
• Small-Sized Unit Control
• Small-Sized Unit Control (Loaded C programming language)
• SEQ Control Enhanced (Large Sequence Capacity)
• SEQ Control Standard (Large Sequence Capacity/Loaded C programming language)
• SEQ Control Enhanced (Large Sequence Capacity/Loaded C programming lan-
guage)
• SEQ Control Enhanced (Medium Sequence Capacity) with Recipe
• SEQ Control Standard (Medium Sequence Capacity/Loaded C programming lan-
guage)
• SEQ Control Enhanced (Medium Sequence Capacity/Loaded C programming lan-
guage) with Recipe
• General (Calculation Oriented)
• Batch Control (SEBOL Oriented with Recipe)
• Batch Control (Sequence Table Oriented with Recipe)
SEE ALSO
For details on the PFCS databases, see the following:
“■ Define Database Type ¡” in F1.4.1, “Creating a New FCS”

■ KFCS2 Databases £
One of the following databases can be selected for the KFCS2:
• General-Purpose
• Migration
• Remote Node Expanded
■ KFCS Databases £
One of the following databases can be selected for the KFCS:
• General-Purpose
• General-Purpose (Large number of elements)
• Continuous Monitoring
• Sequence Monitoring
• Regulatory Control
• SEQ Control (mainly by SFC Blocks)
• SEQ Control (mainly by Sequence Blocks)
• Unit Control (without Recipe)
• Unit Control (with Recipe)
• Offsite Block
• Valve Pattern Monitor
• Migration
• Migration Type (with Expanded Sequence Table)
• Sequence Control (with Expanded Sequence Block)
■ LFCS2 Databases £
One of the following databases can be selected for the LFCS2:
• General-Purpose
• Migration

■ LFCS Databases £
One of the following databases can be selected for the LFCS:
• General-Purpose
• General-Purpose (Large number of elements)
• Regulatory Control
• Sequence Control (mainly by SFC Blocks)
• Sequence Control (mainly by Sequence Blocks)
• Offsite Block
• Valve Pattern Monitor
• Migration
• Migration Type (with Expanded Sequence Table)
• Sequence Control (with Expanded Sequence Block)
■ SFCS Databases £
One of the following databases can be selected for the SFCS:
• General-Purpose
SEE ALSO
For details on the KFCS2, KFCS, LFCS2, LFCS and SFCS databases, see the following:
“■ Define Database Type £” in F1.4.1, “Creating a New FCS”

<A1.4 Function Block List> A1-16
A1.4 Function Block List

▼ Model Name
This section presents an overview of all the function blocks of the FCS.
The function block classification of the FCS databases is listed at the end of this
section.
■ Regulatory Control Block Classification ¡ £

Table Regulatory Control Blocks (1/2)
Block type Model Name
PVI Input Indicator Block
Input Indicator Block
PVI-DV Input Indicator Block with Deviation Alarm
PID PID Controller Block
PI-HLD Sampling PI Controller Block
PID-BSW PID Controller Block with Batch Switch
ONOFF Two-Position ON/OFF Controller Block
ONOFF-E Enhanced Two-Position ON/OFF Controller Block
Controller Block ONOFF-G Three-Position ON/OFF Controller Block
ONOFF-GE Enhanced Three-Position ON/OFF Controller Block
PID-TP Time-Proportioning ON/OFF Controller Block
PD-MR PD Controller Block with Manual Reset
PI-BLEND Blending PI Controller Block
PID-STC Self-Tuning PID Controller Block
MLD Manual Loader Block
MLD-PVI Manual Loader Block with Input Indicator
MLD-SW Manual Loader Block with Auto/Man SW
Manual Loader Block MC-2 Two-Position Motor Control Block
MC-2E Enhanced Two-Position Motor Control Block
MC-3 Three-Position Motor Control Block
MC-3E Enhanced Three-Position Motor Control Block
RATIO Ratio Set Block
PG-L13 13-Zone Program Set Block
Signal Setter Block
BSETU-2 Flow-Totalizing Batch Set Block
BSETU-3 Weight-Totalizing Batch Set Block
Signal Limiter Block VELLIM Velocity Limiter Block
SS-H/M/L Signal Selector Block
Signal Selector Block AS-H/M/L Auto-Selector Block
SS-DUAL Dual-Redundant Signal Selector Block
FOUT Cascade Signal Distributor Block
FFSUM Feed-Forward Signal Summing Block
Signal Distributor Block
XCPL Non-Interference Control Output Block
SPLIT Control Signal Splitter Block
Alarm Block ALM-R Representative Alarm Block
Pulse Count Input Block PTC Pulse Count Input Block
A010401E.EPS
*1: ¡ £ This option can be applied to all Field control stations except standard PFCS (CS 1000).

Table Regulatory Control Blocks (2/2) ¡ £
SLCD YS Controller Block
SLPC YS Programmable Controller Block
SLMC YS Programmable Controller Block with Pulse-Width
Output
SMST-111 YS Manual Station Block with SV Output
YS Instrument Block SMST-121 YS Manual Station Block with MV Output Lever
SMRT YS Ratio Set Station Block
SBSD YS Batch Set Station Block
SLCC YS Blending Controller Block
SLBC YS Batch Controller Block
STLD YS Totalizer Block
FF-AI FOUNDATION fieldbus Analog Input Block
FF-DI FOUNDATION fieldbus Discrete Input Block
FF-CS FOUNDATION fieldbus Control Selector Block
FF-PID FOUNDATION fieldbus PID Control Block
FF-RA FOUNDATION fieldbus Ratio Block
FF-AO FOUNDATION fieldbus Analog Output Block
FF-DO FOUNDATION fieldbus Discrete Output Block
FF-OS FOUNDATION fieldbus Output Splitter Block
FOUNDATION fieldbus
Faceplate Block (*2) FF-SC FOUNDATION fieldbus Signal Characterizer
(Totalizer) Block
FF-IT FOUNDATION fieldbus Integrator Block
FF-IS FOUNDATION fieldbus Input Selector Block
FF-MDI FOUNDATION fieldbus Multiple Discrete Input Block
FF-MDO FOUNDATION fieldbus Multiple Discrete Output
Block
FF-MAI FOUNDATION fieldbus Multiple Analog Input Block
FF-MAO FOUNDATION fieldbus Multiple Analog Output Block
A010402E.EPS
*2: ¡ £ FOUNDATION fieldbus faceplate block can only be used for the KFCS2/KFCS/RFCS5/RFCS2 in CS 3000. It
may be abbreviated as the “FF faceplate block” in this manual.
SEE ALSO
For more details on the FOUNDATION fieldbus faceplate block, see the following:

■ Calculation Block Classification ¡ £
Table Calculation Blocks (1/2) ¡ £
ADD Addition Block
MUL Multiplication Block
Arithmetic Calculation 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
LDLAG Lead/Lag Block
Analog Calculation 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
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 Output
SRS2-R Reset-Dominant Flip-Flop Block with 2 Output
WOUT Wipeout Block
OND ON-Delay Timer Block
Logic Operation Block (*1)
OFFD OFF-Delay Timer Block
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
BAND Bitwise AND Block
BOR Bitwise OR Block
BNOT Bitwise NOT Block
A010403E.EPS
*1: ¡ £ The logic operation block can only be used for the CS 3000.

Table Calculation Blocks (2/2)
General-Purpose CALCU General-Purpose Calculation Block
Calculation Block CALCU-C General-Purpose Calculation Block with String I/O
SW-33 3-Pole 3-Position Selector Switch Block
SW-91 1-Pole 9-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
Calculation Auxiliary Block BDSET-1L 1-Batch Data Set Block
BDSET-1C 1-Batch String Data Set Block
BDSET-2L 2-Batch Data Set Block
BDSET-2C 2-Batch String Data Set Block
BDA-L Batch Data Acquisition Block
BDA-C Batch String Data Acquisition Block
ADL Station Interconnection Block
A010404E.EPS

■ Sequence Control Block Classification ¡ £
Table Sequence Control Blocks
ST16 Sequence Table Block
Sequence Table Block
ST16E Rule Extension Block
Logic Chart Block LC64 Logic Chart Block
_SFCSW 3-Position Switch SFC Block
SFC Block _SFCPB Pushbutton SFC Block
_SFCAS Analog SFC Block
SI-1 Switch Instrument Block with 1 Input
SI-2 Switch Instrument Block with 2 Inputs
SO-1 Switch Instrument Block with 1 Output
SO-2 Switch Instrument Block with 2 Outputs
SIO-11 Switch Instrument Block with 1 Input and 1 Output
SIO-12 Switch Instrument Block with 1 Input and 2 Outputs
SIO-21 Switch Instrument Block with 2 Inputs and 1 Output
SIO-22 Switch Instrument Block with 2 Inputs and 2 Outputs
SIO-12P Switch Instrument Block with 1 Input, 2 One-Shot Outputs
SIO-22P Switch Instrument Block with 2 Inputs, 2 One-Shot Outputs
SI-1E Enhanced Switch Instrument Block with 1 Input (*1)
Switch Instrument SI-2E Enhanced Switch Instrument Block with 2 Inputs (*1)
Block SO-1E Enhanced Switch Instrument Block with 1 Output (*1)
SO-2E Enhanced Switch Instrument Block with 2 Outputs (*1)
Enhanced Switch Instrument Block with 1 Input and
SIO-11E 1 Output (*1)
Enhanced Switch Instrument Block with 1 Input and
SIO-12E
2 Outputs (*1)
Enhanced Switch Instrument Block with 2 Inputs and
SIO-21E
1 Output (*1)
Enhanced Switch Instrument Block with 2 Inputs and
SIO-22E
2 Outputs (*1)
Enhanced Switch Instrument Block with 1 Input,
SIO-12PE
2 One-Shot Outputs (*1)
Enhanced Switch Instrument Block with 2 Inputs,
SIO-22PE
2 One-Shot Outputs (*1)
TM Timer Block
CTS Software Counter Block
CTP Pulse Train Input Counter Block
Sequence Auxiliary
CI Code Input Block
Block
CO Code Output Block
RL Relational Expression Block
RS Resource Scheduler Block
Valve Monitoring Block VLVM Valve Monitoring Block
A010405E.EPS
*1: ¡ £ This option can be applied to all Field control stations except standard PFCS (CS 1000).

■ Faceplate Block Classification ¡ £
Table Faceplate Blocks ¡ £
INDST2 Dual-Pointer Indicating Station Block
Analog
INDST2S Dual-Pointer Manual Station Block
Faceplate Block
INDST3 Triple-Pointer Manual Station Block
BSI Batch Status Indicator Block
Sequence
PBS5C Extended 5-Pushbutton Switch Block
Faceplate Block
PBS10C Extended 10-Pushbutton Switch Block
Hybrid
HAS3C Extended Hybrid Manual Station Block
Faceplate Block
A010406E.EPS
*1: ¡ £ The extended 10-pushbutton switch block can only be used for the CS 3000.
■ Unit Instrument and Operation Classifications

Table Unit Instruments and Operations
_UTSW 3-Position Switch-Type Unit Instrument
Unit Instrument _UTPB 5-Pushbutton-Type Unit Instrument
_UTAS Analog-Type Unit Instrument
_UTSW-N Non-Resident Unit Instrument with Three-Position Switch
Non-Resident
_UTPB-N Non-Resident Unit Instrument with Five-Pushbutton Switch
Unit Instrument
_UTAS-N Analog Non-Resident Unit Instrument
OPSBL SEBOL-Type Operation
OPSFC SFC-Type Operation
OPSFCP1 SFC-Type Operation with Floating-Data Parameters
OPSFCP2 SFC-Type Operation with Character-Data Parameters
Operation
SFC-Type Operation with Floating/Character-Data
OPSFCP3
Parameters
SFC-Type Operation with Integer/Character-Data
OPSFCP4
Parameters
OPSFCP5 SFC-Type Operation with Floating/Integer-Data Parameters
A010407E.EPS

■ Valve Pattern Monitor Classification £
Table Valve Pattern Monitors £
VPM64 64-Data Valve Pattern Monitor
Valve Pattern Monitor
VPM64A 64-Data Valve Pattern Monitor with Alarm
A010408E.EPS
■ Off-Site Block Classification £

Table Off-Site Block £
FSBSET Batch Set Control Block
Off-Site Block
BLEND Blending Master Control Block
A010409E.EPS

■ Function Block Classification in FCS Databases ¡
The following lists the names of the function block models that belong to the function block
classification in the FCS databases.
Table Function Block Classification ¡
Block type Function block model
PVI, PVI-DV
PID, PI-HLD, PID-BSW, ONOFF, ONOFF-E, ONOFF-G, ONOFF-GE, PID-TP, PD-MR,
PI-BLEND, PID-STC (*1)
MLD, MLD-PVI, MLD-SW, MC-2, MC-2E, MC-3, MC-3E (*1)
RATIO, PG-L13, BSETU-2, BSETU-3
Regulatory Control/ VELLIM
Calculation SS-H, SS-M, SS-L, AS-H, AS-M, AS-L, SS-DUAL
FOUT, FFSUM, XCPL, SPLIT
PTC
ADD, MUL, DIV, AVE
SQRT, EXP, LAG, INTEG, LD, RAMP, LDLAG, DLAY, DLAY-C
AVE-M, AVE-C, FUNC-VAR, TPCFL, ASTM1, ASTM2
SW-33, SW-91, DSW-16, DSW-16C, DSET, DSET-PVI
SLCD, SLPC, SLMC, SMST-111, SMST-121, SMRT, SBSD, SLBC, SLCC, STLD
Sequence ST16, ST16E, LC64
SI-1, SI-2, SO-1, SO-2, SIO-11, SIO-12, SIO-21, SIO-22, SIO-12P, SIO-22P
Switch Instrument/ SI-1E, SI-2E, SO-1E, SO-2E, SIO-11E, SIO-12E, SIO-21E, SIO-22E, SIO-12PE,
Sequence Auxiliary SIO-22PE (*1)
TM, CTS, CTP, CI, CO
General-Purpose Calculation CALCU, CALCU-C
INDST2, INDST2S, INDST3, PBS5C, BSI, HAS3C
Faceplate/Others BDSET-1L, BDSET-1C, BDSET-2L, BDSET-2C, BDA-L, BDA-C
ALM-R, RL, RS, VLVM
SFC Block _SFCSW, _SFCPB, _SFCAS
Operation OPSBL, OPSFC

OPSFCP1, OPSFCP2, OPSFCP3, OPSFCP4, OPSFCP5
Unit Instrument _UTSW, _UTPB, _UTAS

_UTSW-N, _UTPB-N, _UTAS-N
A010410E.EPS
*1: The following function blocks can only be used for the enhanced type PFCS.
ONOFF-E, ONOFF-GE, MC-2E, MC-3E, SI-1E, SI-2E, SO-1E, SO-2E, SIO-11E, SIO-12E, SIO-21E, SIO-22E, SIO-
12PE, SIO-22PE

■ Function Block Classification in FCS Databases £
The following lists the names of the function block models that belong to the function block
classification in FCS databases.
Table Function Block Classification £
Block type Function block model
PVI, PVI-DV
PID, PI-HLD, PID-BSW, ONOFF, ONOFF-E, ONOFF-G, ONOFF-GE, PID-TP, PD-MR,
PI-BLEND, PID-STC
MLD, MLD-PVI, MLD-SW, MC-2, MC-2E, MC-3, MC-3E
RATIO, PG-L13, BSETU-2, BSETU-3
VELLIM
SS-H, SS-M, SS-L, AS-H, AS-M, AS-L, SS-DUAL
Regulatory Control/
FOUT, FFSUM, XCPL, SPLIT
Calculation
PTC
ADD, MUL, DIV, AVE
SQRT, EXP, LAG, INTEG, LD, RAMP, LDLAG, DLAY, DLAY-C
AVE-M, AVE-C, FUNC-VAR, TPCFL, ASTM1, ASTM2
SW-33, SW-91, DSW-16, DSW-16C, DSET, DSET-PVI
SLCD, SLPC, SLMC, SMST-111, SMST-121, SMRT, SBSD, SLBC, SLCC, STLD
FF-AI, FF-DI, FF-CS, FF-PID, FF-RA, FF-AO, FF-DO, FF-OS, FF-SC, FF-IT (*1)
FF-IS, FF-MDI, FF-MDO, FF-MAI, FF-MAO (*1)
Sequence ST16, ST16E, LC64
SI-1, SI-2, SO-1, SO-2, SIO-11, SIO-12, SIO-21, SIO-22, SIO-12P, SIO-22P
Switch Instrument SI-1E, SI-2E, SO-1E, SO-2E, SIO-11E, SIO-12E, SIO-21E, SIO-22E, SIO-12PE,
SIO-22PE
Sequence Auxiliary-1 TM, CTS, CTP, CI, CO
General-Purpose Calculation CALCU, CALCU-C
Faceplate INDST2, INDST2S, INDST3, PBS5C, PBS10C, BSI, HAS3C
AND, OR, NOT, SRS1-S, SRS1-R, SRS2-S, SRS2-R
Logic Operation
WOUT, OND, OFFD, TON, TOFF, GT, GE, EQ, BAND, BOR, BNOT
Sequence Auxiliary-2 ALM-R, RL, RS, VLVM
Batch Data BDSET-1L, BDSET-1C, BDSET-2L, BDSET-2C, BDA-L, BDA-C
SFC Block _SFCSW, _SFCPB, _SFCAS
OPSBL, OPSFC
Operation
OPSFCP1, OPSFCP2, OPSFCP3, OPSFCP4, OPSFCP5
_UTSW, _UTPB, _UTAS
Unit Instrument
_UTSW-N, _UTPB-N, _UTAS-N
Off-Site Block FSBSET, BLEND
A010411E.EPS
*1: The function blocks from FF-A1 to FF-MAO can only be used for the KFCS2, KFCS, RFCS5 or RFCS2.
TIP
In addition to the block classifications listed in the tables above, the “sequence (medium)” and “sequence
(large)” are also available as the blocks supporting CENTUM V/CENTUM-XL migration that can be used
in KFCS2, KFCS, LFCS2, LFCS, RFCS5 or RFCS2.
• The [Sequence (M-Size)] includes the M_ST16 and M_ST16E blocks.
• The [Sequence (L-Size)] includes the L_ST16 and L_ST16E blocks.

<A2. Outline of Input and Output Interfaces> A2-1
A2. Outline of Input and Output Interfaces

The input and output interfaces support the internal data exchange inside a field
control station and external data exchange between a field control station and
another equipment.
The input and output interfaces consist of Software I/O, Process I/O, Communication
I/O and Fieldbus I/O.
In this document, Process I/O, Communication I/O and Fieldbus I/O are referred to as
Process I/O.
■ Position of Input and Output Interfaces ¡ £

The following figure illustrates the I/O interfaces in basic control architecture.
FCS
Faceplate blocks
SFC blocks
Unit instruments
Options
FCS I/O Interfaces
A020001E.EPS
Figure Input and Output Interfaces in System Functional Architecture ¡ £
The input and output interfaces consist of Software I/O, Process I/O, Communication I/O
and Fieldbus I/O. A field control station can access internal and external data via these
I/Os.

■ Software Input and Output
Software input and output is a function to carried out the virtual input and output connection
inside of FCS by software.
To access or set data to function blocks or other application functions, the same procedure
of process software inputs and outputs.
SEE ALSO
For details on software input and output, see the following:
A4, “Software Inputs/Outputs”
■ Various Types of Process I/O ¡ £

The I/O units used by process control stations vary with the FCS models, I/O module
location, communication bus and so on.
● Process I/O of PFCS and SFCS ¡ £

PFCS and SFCS can connect the processor unit directly to the I/O module nests. Via the
I/O modules installed in the nests, the control stations can communicate with the filed
devices for process control.
● Process I/O of KFCS2 and KFCS £

KFCS2 and KFCS can connect FCU to the nodes using ESB bus (Extended Serial
Backboard Bus), furthermore, connection can be established from the local nodes to
remote nodes via ER bus (Enhanced Remote Bus).
Via the I/O modules installed in local nodes and remote nodes, the control station can
communicate with the field devices for process control.
The following figure illustrates the connection of local nodes and remote nodes.
FCU
FCU: Field Control Unit S C C S

PW3X, PSU: Power Supply Unit P P
B P P B
CP345: Processor Unit W W
3 3 3 3
SB301,SB401: ESB Bus Interface Card 3 3
0 4 4 0
IOM: Input/Output Module x x
1 5 5 1
EB401, EB501: ER Bus Interface card
Local node
Remote node E E S S
B B I I I I I I B B P P
E E 4 4 O O O O O O 4 4 S S
I I I I I I I I B B P P 0 0 M M M M M M 0 0 U U
O O O O O O O O 5 5 S S 1 1 1 1
M M M M M M M M 0 0 U U
1 1
ESB Bus
ER Bus
A020002E.EPS
Figure Connection of Local Nodes and Remote Nodes £

● FCS I/O Interfaces of LFCS2 and LFCS £
LFCS2 and LFCS can connect FCU to the nodes using RIO bus. Via the I/O modules
installed in the nodes, the control station can communicate with the filed devices for pro-
cess control.
● FCS I/O Interfaces of Migrated-FCS for FIO (RFCS5/RFCS2) £

RFCS5 and RFCS2 can connect FCU to the nodes using SI bus. Via the I/O modules (for
the old version FCS) installed in the nodes, the control station can communicate with the
filed devices for process control.
Moreover, like KFCS2 and KFCS, Migrated-FCS2 can connect to local nodes and remote
nodes, via the I/O modules installed in local nodes and remote nodes, the control station
can communicate with the field devices for process control.
SEE ALSO
For more information about the I/O cards regarding to SI bus, see the following:
A2.1, “Process I/O” in the instruction manual for Migrated-FCS (FIO) (IM 33Q01B41-01E)
■ Process I/O
Process I/O stands for the interface for the signal communication between Field devices
and field control station. An FCS receives signals from field process detection devices and
send control signals to field control devices.
SEE ALSO
For more information about process I/O, see the following:
A3, “Process Inputs/Outputs”

■ Communication I/O Modules ¡ £
Communication I/O modules are used for communicating with subsystems such as a PLC
(Programmable Logic Controller) for exchanging the process data.
The following modules are available for FCS to communicate with subsystems.
• ACM11: RS-232C communication module (*1)
• ACM12: RS-422/RS-485 communication module (*1)
• ACM21: RS-232C communication card (*2)
• ACM22: RS-422/RS-485 communication card (*2)
• ACM71: Ethernet communication module (*2)
• ACP71: PROFIBUS communication module (*2)
• ALR111: RS-232C serial communication module (*3)
• ALR121: RS-422/RS-485 serial communication module (*3)
• AL E111: Ethernet communication module (*3)
• ALP111: PROFIBUS-DPV1 communication module (*3)
*1: ¡ £ Applicable to PFCS, LFCS2, LFCS and SFCS
*2: ¡ £ Applicable to Enhanced Type PFCS, SFCS
*3: ¡ £ Applicable to KFCS2, KFCS
SEE ALSO
For more information about communication I/O modules, see the followings:
J2, “Communication I/O Module”
K2, “Communication I/O Module”
N2, “PROFIBUS-DP (ACP71)”
N3, “PROFIBUS-DP (ALP111)”
● ACM11: RS-232C Communication Module : PFCS/LFCS2/LFCS/SFCS

This is a module to communicate with a subsystem using RS-232C interface for exchang-
ing process data. This module can be installed in (AMN33) communication module nest.
Besides, a subsystem communication package for this module is required.
● ACM12: RS-422/RS-485 Communication Module : PFCS/LFCS2/LFCS/

SFCS
This is a module to communicate with a subsystem using RS-422 or RS-485 interface for
exchanging process data. This module can be installed in (AMN33) communication module
nest.
● ACM21: RS-232C Communication Card : Enhanced Type PFCS/SFCS

This is a module to communicate with a subsystem using RS-232C interface for exchang-
ing process data. This module can be installed in (AMN51) communication module nest.

● ACM22: RS-422/RS-485 Communication Card : Enhanced Type PFCS/
SFCS
This is a module to communicate with a subsystem using RS-422 or RS-485 interface for
exchanging process data. This module can be installed in (AMN51) communication module
nest.
Besides, subsystem communication tasks created with FCS-C are required for this module.
● ACM71: Ethernet Communication Module : Enhanced Type PFCS/SFCS

This is a module to communicate with a subsystem using Ethernet interface for exchanging
process data. This module can be installed in (AMN51) communication module nest.
● ACP71: PROFIBUS Communication Module : Enhanced Type PFCS/SFCS

This is a module to communicate with the field devices connected on PROFIBUS-DP
fieldbus for exchanging process data. This module can be installed in (AMN52) communi-
cation module nest.
Besides, PROFIBUS Communication Package for this module is required.
● ALR111: Serial Communication Module (RS-232C) : KFCS2/KFCS £

ALR111 is a RS-232C module for communicating with subsystems. This module can be
installed to a nest (ANB10S/D) of local node or a KFCS2 nest (ANR10S/D) of remote node.
Besides, a communication package is required when performing communication with
subsystems.
● ALR121: Serial Communication Module (RS-422/RS485) : KFCS2/KFCS

£
ALR121 is a RS-422/RS-485 module for communicating with subsystems. This module
can be installed to a nest (ANB10S/D) of local node or a KFCS2 nest (ANR10S/D) of
remote node.
subsystems..
● ALE111: Ethernet Communication Module (RS-422/RS485) : KFCS2/KFCS

ALE111 is an Ethernet communicating module used for communicating with subsystems.
This module can be installed to a nest (ANB10S/D) of local node or a KFCS2 nest
(ANR10S/D) of remote node.
subsystems.
● ALP111: PROFIBUS-DPV1 Communication Module : KFCS2/KFCS

This is a module to communicate with the field devices connected on PROFIBUS-DP/
DPV1 fieldbus for exchanging process data. This module can be installed to a nest
(ANB10S/D) of local node.
Besides,PROFIBUS Communication Package for this module is required.

■ Fieldbus Inputs and Outputs ¡ £
The process data of field devices connected on fieldbus can be accessed via the fieldbus I/O.
A fieldbus communication I/O module can be applied for connecting FCS with fieldbus.
Besides, FOUNDATION fieldbus communication packages are required.
SEE ALSO
• For more information about PFCS/LFCS2/LFCS/SFCS Fieldbus I/O, see FOUNDATION fieldbus Tools
(IM 33S05P10-01E)
• For more information about KFCS2/KFCS Fieldbus I/O, see the following:
● ACF11: Fieldbus Communication Module : PFCS/LFCS2/LFCS/SFCS

ACF111 is a module for communicating with Fieldbus devices. ACF111 can be installed in a
communication module nest (AMN33). FCS is communicating with Fieldbus devices via
the ACF111.
ACF111 has the following capabilities:
• Can be used as Link Active Scheduler (LAS) to manage the Fieldbus communication
schedule.
• Can pass the data from FCS to field devices and vise versa.
• Can supply powers to the Fieldbus devices.
● ALF111: Fieldbus Communication Module : KFCS2/KFCS £

ALF111 is a module for communicating with Fieldbus devices. ALF111 can be installed in a
local node or in a remote node. FCS is communicating with Fieldbus devices via the
ALF111.
ALF111 has the following capabilities:
• Can be used as Link Active Scheduler (LAS) to manage the Fieldbus communication
schedule.
• Can pass the data from FCS to field devices and vise versa.
■ Identifiers of Process Inputs/Outputs ¡ £

Process inputs/outputs are identified by element numbers assigned.
Since plant operation may require to identify all the I/O signals with unique names, so that
all the I/O signals can be tagged or assigned with a user-defined label, thus as to assign a
contact input or output with a tag name or to assign an analog input or output channel with
a user-defined label.
TIP
From a SEBOL program, a Visual Basic program or a Windows application (other than CS 3000 HMI
applications), a terminal number, tag name and user-defined label can be used to identify an I/O signal.

● Format of Terminal Number : PFCS/LFCS2/LFCS/SFCS
▼ Terminal
A terminal of a process I/O or a Fieldbus I/O can be numbered in accordance with its
physical position and the I/O module location.
The format of a terminal number is as follows.
%Znnusmm
%Z: Identifier of process I/O (Fixed)
nn: 01 (Fixed) (*1) (*2)
Node Number (01 - 08) (*2)
u: Unit Number (1 - 5)
s: Slot Number (1 -4)
mm: Terminal Number (01 - 32)
*1: ¡ In PFCS, nn is fixed as 01.

*2: £ In SFCS, nn is fixed as 01. In LFCS2 and LFCS, nn stands for node number (01 to 08).
IMPORTANT
When using Multipoint Control Analog I/O Module with signal conversion connector
(AMC80/ZVM) , the following points need to be noted.
AMC80/ZVM is the Multipoint Control Analog I/O Module (AMC80) attached with a signal
conversion connector (in which, the output is converted to 1 to 5 V DC, pin-assignment is
rearranged).
The pin arrangement of AMC80/ZVM assigns the channels 1 to 8 for input and channel 9 to
16 for output; while on the AMC80 I/O builder, the odd number channels for input and the
even number channels for output. The relations between the signal channels on AMC80
connector and on AMC80 I/O builder are shown as follows.
AMC80/ZVM
Input/Output
Channels
01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16
on Connector
Channels
01 03 05 07 09 11 13 15 02 04 06 08 10 12 14 16
on Builder(%Z)
A030002E.EPS
● Format of Terminal Number : KFCS2/KFCS £

▼ Terminal
A terminal of a process I/O or a Fieldbus I/O can be numbered in accordance with its
physical position and the I/O module location.
The format of a terminal number is as follows.
%Znnusmm
nn: Node Number (01 - 10)
If the database in KFCS2 is remote node expanded type, the range of node number becomes 01 to 15.
u: Unit Number (1 - 8)
s: For a Fieldbus communication module, s stands for segment number (1 -4).
When using modules compatible to HART communication, for measured analog data s=1, while for the data via
HART communication s=2.
For other I/O modules s is fixed as 1.
mm: Terminal Number (01 - 64)

Blank Page
<A3. Process Inputs/Outputs> A3-1
A3. Process Inputs/Outputs

Using process inputs/outputs, an FCS can receive signals from process detectors
and output signals to process control elements.
■ Process Inputs/Outputs ¡ £
Process inputs/outputs are used to exchange signals between field equipment and an FCS.
There are two types of process inputs/outputs:
• Analog input/output
• Contact input/output
Process input/output signals are used as input/output signals for the regulatory control,
arithmetic calculation and sequence control.
FCS
Faceplate blocks
SFC blocks
Unit instruments
Options
FCS I/O Interfaces
A030001E.EPS
Figure Relationship of Process Inputs/Outputs with Basic Control ¡ £
To use process inputs/outputs, must define them in System View or IOM Builder.

<A3.1 Analog Inputs/Outputs> A3-2
A3.1 Analog Inputs/Outputs

Using analog inputs/outputs, an FCS can receive and output analog signals from/to
field equipment.
■ Analog Inputs/Outputs : PFCS/LFCS2/LFCS/SFCS

Analog inputs/outputs are process inputs/outputs which handle analog signals such as DC
voltages and currents.
The input/output range for each input/output module (IOM) for each type of I/O and the raw
data obtained from the input analog signals are shown in the table below.
IMPORTANT
• Among Thermocouple input modules and Resistance Temperature Detector input
modules, some (AAM21J, AMM22TJ, AMM25C, AMM32TJ, AMM32CJ) conform to
new JIS (Japanese Industrial Standard) while some others (AAM21, AMM22T,
AMM32T, AMM32C) conform to old JIS. Except for AMM25C, the CS 1000/CS 3000
Software does not distinguish the difference between the two types, and only use the
old JIS model names for both types of modules. In this chapter, unless otherwise
specified, AAM21/AMM22/AMM32T/AMM32C stand for both new JIS and old JIS type
modules.
• When implementing the Current/Voltage input modules for BRAIN transmitters
(AAM11B), the required software package is option package. For details on the option
package, contact Yokogawa sales department.

Table Analog Input/Output Specifications (1/2) : PFCS/LFCS2/LFCS/SFCS
IOM type
Classification Input/output type Range Raw data
name
Current input Set within range of 0 to 20 mA 0 to 100 %
AAM11
Voltage input Set within range of 0 to 10 V 0 to 100 %
Current input
Set within range of 0 to 20 mA 0 to 100 %
AAM11B (*1) (BRAIN Communication)
Voltage input Set within range of 0 to 10 V 0 to 100 %
Current input 4 to 20 mA 0 to 100 %
AAM10
Voltage input 1 to 5 V 0 to 100 %
mV input Set within range of -50 to +150 mV 0 to 100 %
Control Measuring range of the Measured
input/output Thermocouple input
thermocoupler used temperature
AAM21
Resistance Temperature Measuring range of the Resistance Measured
Detector input Temperature Detector used temperature
Potentiometer input Within 0 to 30000 ohm 0 to 100 %
APM11 Pulse input - -
Current output 4 to 20 mA -
AAM51
Voltage output Set within range of 0 to 10 V -
Current output
AAM50 4 to 20 mA -
(single function)
Multipoint Voltage input 1 to 5 V 0 to 100 %
control analog AMC80
input/output Current output 4 to 20 mA -
AMM12T Voltage input Set within range of -10 to +10 V 0 to 100 %
AMM22M mV input Set within range of -100 to +100 mV 0 to 100 %
Measuring range Measured
AMM22T Thermocouple input
Multiplexer of the thermocoupler used temperature
input/output Resistance Temperature Measuring range of the Resistance Measured
AMM32T
Detector input Temperature Detector used temperature
AMM42T Current input 4 to 20 mA 0 to 100 %
AMM52T Current output 4 to 20 mA -
A030101E.EPS
*1: AAM11B is a kind module that can be installed in control I/O unit (AMN11/AMN12) for connecting to the transmitters
with BRAIN communication functions. When applied with current input, it can communicate with BRAIN transmitters,
while with voltage input, it can only perform the same function as an AAM11 module.

Table Analog Input/Output Specifications (2/2) : PFCS/LFCS2/LFCS/SFCS
IOM type
Classification Input/output type Range Raw data
name
Voltage input
AMM12C Set within range of -10 to +10 V 0 to 100 %
(Connector type)
Connector Type
AMM22C Set within range of -100 to +100 mV 0 to 100 %
mV Input
Connector Type Measuring range of the
Measured
AMM32C Resistance Temperature Resistance Temperature
temperature
Detector Input Detector used
Multiplexer
Connector Type Measuring range of the Measured
(Connector type) AMM25C
Thermocouple mV Input thermocouple used temperature
AMM12T
Voltage input Set within range of -10 to +10 V 0 to 100 %
(*2)
AMM22M
mV input Set within range of -100 to +100 mv 0 to 100 %
(*2)
AMM22T Measuring range of the thermocouple Measured
Thermocouple
(*2) used temperature
A030102E.EPS
*2: ¡ £ Can only be used in PFCS or in SFCS. AMM12T, AMM22M and AMM22T are Terminal Type multiplexer
modules, they can be combined with other connector type modules in an AMN32 Connector Type I/O Module Nest.
TIP
In SFCS or PFCS, connector type multiplexer modules (AMM12C/AMM22C/AMM32C/ AMM25C) can be
installed together with terminal type multiplexer modules (AMM12T/AMM22M/AMM22T) into the same I/
O module nest (AMN32). When both types are installed in the same AMN32, the width of the module
displayed will be the same as width for connector type multiplexer I/O modules on FCS status display
window.
Installation Status Display (HIS)
A A A A
M M M M
Installed In M M M M
AMN31 1 1 1 1
2 2 2 2
T T T T
Terminal type AMM modules

are displayed with width of
connector type multiplexer
A A A A A A modules. As if a space had
M M M M M M
Installed In M M M M M M been left next to the card.
AMN32 1 1 1 1 1 1
2 2 2 2 2 2
C C T C C T
A030103E.EPS
Figure Installation and Status Display (when Connector and Terminal Type Multiplexer Modules
are Installed Together) : PFCS/SFCS

When the IN terminal of a function block is connected to a process I/O, the input from the
IOM will be converted to an engineering unit value as follows.
• Suppose the raw data is 0 to 100 %
Convert the 0 to 100 % input data to SL to SH of the function block.
• Suppose the raw data is a measured temperature
The input signal is used unchanged.
When the OUT terminal of the function block is connected to a process I/O, the output to
the IOM will be converted to a MV ranges from 0 % to 100 %.
The data status signals which indicate the quality of the data will be added to pass to IOM.
The input range can be specified for [mV Input], [Potentiometer Input], [Current Input] and
[Voltage Input] of AAM11 module, and [Voltage Input] of AMM12T/AMM12C modules.
The output range can be specified only for [Voltage Output] of AAM51 module.

■ Analog Inputs/Outputs : KFCS2/KFCS £
Analog Inputs/Outputs are the process input/output signals represented by voltage or
current.
The I/O modules (IOM Model), I/O ranges and the raw data of I/O signals corresponding to
various analog inputs and outputs are shown as follows.
Table Analog Inputs/Outputs : KFCS2/KFCS (1/3) £
Terminal
Category Type (Model) I/O Type Range Raw Data
Number
16-Channel Current Input
Current Input 1 to 16 4 to 20 mA 0 to 100%
(AAI141-S)
16-Channel Current Input;
Isolated (AAI143-S)
Isolated (ASI133-S)
Isolated Channels (AAI135-S)
16-Channel Voltage Input
Voltage Input 1 to 16 1 to 5 V 0 to 100%
(AAV141-S)
16-Channel Voltage Input Definable within
Voltage Input 1 to 16 0 to 100%
(-10 to 10V) (AAV142-S) -10 to 10 V
16-Channel Voltage Input; 1 to 5 V (*1)
Voltage Input 1 to 16 0 to 100%
Isolated (AAV144-S)
16-Channel Definable within
Voltage Input (-10 to 10V); Voltage Input 1 to 16 -10 to 10 V (*1) 0 to 100%
Isolated (AAV144-S)
Analog Input Thermocouple Measured
Rated range
Input Temperature
16-Channel
Definable within
Thermocouple/mV Input; mV Input (%) 1 to 16 0 to 100%
-100 to 150 mV
Isolated (AAT141-S)
Thermocouple Engineering
-20 to 80 mV
Input (V) Unit (V)
Thermocouple Measured
Rated range
Input Temperature
16-Channel
Definable within
-100 to 150 mV
Isolated (AST143-S)
-50 to 75 mV
Input (V) Unit (V)
Measured
Thermocouple Rated range
Temperature
16-Channel
Definable within
-100 to 150 mV
Isolated Channels (AAT145-S)
-20 to 80 mV
Input (V) Unit (V)
Terminal
Number
A030104E.EPS
*1: [16-Channel Voltage Input, Isolated] and [16-Channel Voltage Input (-10 to 10 V), Isolated], two types of AAV144-S
modules are available in Type (Model) column. The range of the previous one is fixed as 1 to 5 voltages and the later
one is definable in the range of - 10 to 10 voltages. Once the Type (Model) is set, it cannot be modified with online-
modification. The resolution of [16-Channel Voltage Input (-10 to 10 V), Isolated] model is fixed as 20 mV, so that the
accuracy varies with the specified input range. Thus, 0.1% accuracy may not be maintained when the input range is
changed. If the input range is 1 to 5 voltages, it is better to use [16th-Channel Voltage Input, Isolated] type module so
as the 0.1% accuracy can be guaranteed.

Terminal
Number
Thermocouple Measured
15-Channel Thermocouple Rated range
Input Temperature
Input; Isolated Channels 1 to 15 (*2)
(MX Compatible)(AAT145-S) Thermocouple Engineering
-20 to 80 mV
Input (V) Unit (V)
Measured
RTD Input Rated range
12-Channel RTD Input; Temperature
1 to 12
Isolated (AAR181-S) RTD Input Engineering
0 to 400 ohm
(ohm) Unit (ohm)
Measured
Temperature
8-Channel RTD/Potentiometer Potentiometer Definable within
0 to 100%
Input; Input 1 to 8 0 to 10 Kohm
Isolated (ASR133-S)
Choose from 0 to
Analog Input RTD Input Engineering
650, 0 to 1300, 0
(ohm) Unit (ohm)
to 2600, 0 to 5400
Measured
Temperature
16-Channel RTD/
Potentiometer Definable within
Potentiometer Input; 1 to 16 0 to 100%
Input 0 to 10Kohms
Isolated Channels (AAR145-S)
RTD Input Engineering
0 to 400 ohm
(ohm) Unit (ohm)
Number of pulse Number of
8-Channel Pulse Input
Pulse Input 1 to 8 0 to 65535; pulse (with
(AAP135-S)
Time stamp (1ms) time stamp)
16-Channel Pulse Input Number of pulse 0 Number of
(PM1 Compatible) Pulse Input 1 to 16 to 65535 Time pulse
(AAP149-S) (*3) stamp (1ms) (with time stamp)
8-Channel Current Input and Current Input 1 to 8 4 to 20 mA 0 to 100%
8-Channel Current Output
(AAI841-S) Current Output 9 to 16 4 to 20 mA -
8-Channel Voltage Input and Voltage Input 1 to 8 1 to 5 V 0 to 100%
8-Channel Current Output
(AAB841-S) Current Output 9 to 16 4 to 20 mA -
Analog Input 8-Channel Voltage Input and Voltage Input 1,3,...,15
1 to 5 V 0 to 100%
and Output 8-Channel Current Output (Odd Number)
(MAC2 Terminal Arrangement) 2,4,...,16 -
(AAB841-S) Current Output 4 to 20 mA
(Even Number)
4-Channel Current Input and Current Input 1 to 4 4 to 20 mA 0 to 100%

4-Chnnel Current Output;
Isolated Channels (AAI835-S) Current Output 5 to 8 4 to 20 mA -
16-Channel Voltage Output Definable within

Voltage Output 1 to 16 -
(-10 to 10 V) (AAV542-S) -10 to 10 V
16-Channel
Definable within
Voltage Output (-10 to 10 V); Voltage Output 1 to 16 -
-10 to 10 V
Analog Output Isolated (AAV544-S)
8-Channel Current Output;
Current Output 1 to 8 4 to 20 mA -
Isolated (ASI533-S)
Isolated (AAI543-S)
Terminal
Category Type (Model) I/O Type Range - Data
Raw
Number
A030107E.EPS
*2: The 16th channel is used as cold junction compensation terminal, so that only 15 channels of the temperature signals
from the field can be connected.
*3: AAP149-S module does not supprot dual redundant configration.

Terminal
Number
16-Channel Current Input
(HART) (AAI141-H) HART Variable Engineering
1 to 32 -
(*3) Unit
Isolated; HART (AAI143-H) HART Variable Engineering
1 to 32 -
(*3) Unit
Isolated; HART (ASI133-H) HART Variable Engineering
1 to 32 -
(*3) Unit
8-Channel Current Input; Current Input 1 to 8 4 to 20 mA 0 to 100%
Isolated channels (HART) HART Variable Engineering
(AAI135-H) 1 to 32 -
(*3) Unit
Analog Input Current Input 1 to 8 4 to 20 mA 0 to 100%
and Output
8-Channel Current Input,
(HART Current Output 9 to 16 4 to 20 mA -
8- Channel Current Output
Compatible)
(HART) (AAI841-H) HART Variable Engineering
1 to 32 -
(*3) Unit
4-Channel Current Input,
4- Channel Current Output Current Output 5 to 8 4 to 20 mA -
(HART) (AAI835-H) HART Variable 1 to 32 Engineering
-
(*3) Unit
Isolated; HART (ASI533-H) HART Variable Engineering
1 to 32 -
(*3) Unit
Current Input 1 to 16 4 to 20 mA -
Isolated; HART (AAI543-H) HART Variable Engineering
1 to 32 -
(*3) Unit
A030212E.EPS
*3: On IOM Builder for Analog Input and Output (HART Compatible) modules, element number is indicated as
%Znnusmm. When “s” is set to 2, the element is used as a HART variable channel. When “s” is set to 1, the element is
used as an analog input channel.

TIP
Some I/O modules can have different types of signals on the terminals. Among them, in some I/O
modules each terminal can be defined individually with specific I/O signal type. While in some other I/O
modules, the terminals are fixed with I/O signal types even though the module can handle different signal
types.
• I/O Signal Type Definable for Each Terminal
As the following example illustrates, the descriptions in the table indicate that any of the terminals
numbered 1 to 8 can be defined with either Voltage Input or Current Input. Or even multiple I/O signal
types can be defined to the terminals of a single module.
Table I/O Signal Type Definable for Each Terminal : KFCS2/KFCS £

I/O Signal Type Terminal No. I/O Signal Type Terminal No.
Current Input 1 to 8 or Current Input
1 to 8
Voltage Input 1 to 8 Voltage Input
A030105E.EPS
• I/O Signal Types are Fixed to Terminals

As the following example illustrates, the descriptions in the table indicate that the I/O signal types of
the terminals are fixed. In the following table, the terminals numbered 1 to 8 are fixed to Current Input
signal type and the terminals numbered 9 to 16 are fixed to Voltage Input signal type.
Table I/O Signal Types are Fixed to Terminals : KFCS2/KFCS £

I/O Signal Type Terminal No.
Current Input 1 to 8
Current Output 9 to 16
A030106E.EPS
When the IN terminal of a function block is connected to a process I/O, the input signal from
the I/O module is converted into engineering unit data as follows.
• Raw Data is 0% to 100%
The input signal is indicated within 0% to 100% in accordance with the function block
scale high/low limits (SH, SL).
• Raw Data is Process Variable (Engineering Unit, HART Variable)
The input signal is used as it is.
• Raw Data is a Number of Pulse (with Time Stamp)
The input signal is converted to a real number by function block’s input processing for
pulse signal.
When the OUT terminal of a function block is connected to a process I/O, the out signal to
the I/O module is a 0% to 100% value converted from the manipulated output value MV.
TIP
For implementation of HART compatible modules, modification of settings can be performed only on the
PC with capability of HART communication management.
SEE ALSO
For more information about HART communication management, see “Plant Resource Manager” (IM
33Y05Q10-01E).

A3.1.1 Analog Input

Using analog inputs, an FCS can receive analog signals from field equipment.
■ Analog Input
Analog inputs are the DC current or DC voltage analog signals from the field equipment
connected to the FCS.
The following types of signal can be used as analog inputs.
• Current Input
• Voltage Input
• mV Input
• Thermocouple Input
• Resistance Temperature Detector Input
• Potentiometer Input
• Pulse Input
All the data passed into the IOM is transmitted to PI/O image of the processor unit and
accessed at the beginning of every basic scan cycle or high-speed scan cycle of the
function blocks.

A3.1.2 Analog Output

Using analog outputs, an FCS can output analog signals to field equipment.
■ Analog Output
Analog output are the DC current or DC voltage analog signals output from FCS to the field
equipment.
The following types of signal can be used as analog outputs.
• Current Output
• Voltage Output
SEE ALSO
For details on the timing of writing data to I/O modules, see the following:
C7.1.3, “Timing of Process I/O”

<A3.2 Contact Inputs/Outputs> A3-12
A3.2 Contact Inputs/Outputs

Using contact inputs/outputs, an FCS can receive and output ON/OFF signals from/to
field equipment.
■ Contact Inputs/Outputs : PFCS/LFCS2/LFCS/SFCS

Contact inputs/outputs are process inputs/outputs which handle ON/OFF signals such as
DC voltages and currents.
The ON/OFF signal is a digital value of either 0 or 1, which together with an indication of the
quality of that value, shows the status of the process data item.
Contact input modules are classified into the following two types according to the input
signal.
• Status input module
Used for monitoring the status of contact inputs. ON/OFF status of input contact
signals is used as the measured value (raw data).
• Pushbutton input module
Used for the input signal from pushbutton switches where the signal status change
from ON to OFF or vice versa is momentary.
Contact output modules are classified into the following three types;
• Status Output
• Pulse-Width Output
• Time-Proportioning ON/OFF Output
TIP
Pulse-Width Output modules and Time-Proportioning ON/OFF Output modules are supported only in
LFCS2 and LFCS. For PFCS and SFCS, Pulse-width output signals and Time-Proportioning ON/OFF
output signals are handled by Status output modules.
An I/O module will perform the input processing according to the type of the I/O module
entered on the IOM Builder.
The input/output range and raw data for each model of input/output module (IOM) used for
contact inputs/outputs are shown in the table below.
Table Contact Input/Output Specifications : PFCS/LFCS2/LFCS/SFCS
Category Model Input/output module type Range Raw data
ADM15R Relay input module (16-point terminal-type) 0, 1 ON=1, OFF=0
Relay
ADM55R Relay output module (16-point terminal-type) 0, 1 -
ADM11T Contact input module (16-point terminal-type) 0, 1 ON=1, OFF=0
ADM12T Contact input module (32-point terminal-type) 0, 1 ON=1, OFF=0
Terminal
ADM51T Contact output module (16-point terminal-type) 0, 1 -
ADM52T Contact output module (32-point terminal-type) 0, 1 -
ADM11C Contact input module (16-point connector-type) 0, 1 ON=1, OFF=0
ADM12C Contact input module (32-point connector-type) 0, 1 ON=1, OFF=0
Connector
ADM51C Contact output module (16-point connector-type) 0, 1 -
ADM52C Contact output module (32-point connector-type) 0, 1 -
A030201E.EPS

■ Contact Inputs/Outputs : KFCS2/KFCS £
Contact I/O indicates the I/O interfaces that receive or send ON/OFF process signals.
The ON/OFF signal of process data represented by a digital value 1 or 0, and attached with
a data status signal to represent the quality of the data.
The contact I/O consist of the following eight types of I/O inputs.
• Status Input
• Pushbutton Input
• Status/Pushbutton Input
• Status Output
• Pulse-Width Output (Including Time-Proportion ON/OFF Output)
• Status/Pulse-Width Output
• Status/Pulse-Width Output (Local Nodes Only)
• ST Compatible (No-Voltage Contact I/O Signals) (*1)
*1: ST Compatible means the I/O modules are compatible with the CENTUM V and CENTUM-XL ST2, ST3, ST4, ST5,
ST6 and ST7 modules which handle No-Voltage contact I/O signals. The I/O signals can be handled by ST compatible
modules are:
Status Input
Pushbutton Input
Status Output/Pulse-Width Output
Status Input/Status Output/Pulse-Width Output
A status input signal is represented by the ON/OFF status of a contact input.

A pushbutton input signal is represented by a status change (either from ON to OFF or
OFF to ON) of a contact input.
When an I/O signal type is designated on IOM builder for an I/O module, the I/O module
performs the signal input or output processing accordingly.

The models of contact I/O modules (IOM Model) and the types of I/O signals are shown as
follows.
Table Contact I/O Modules Specification (1/2): KFCS2/KFCS £
Redun- Re-
Category Type (Model) I/O Type Terminal Number
dancy mote
32-Channel Status Input; Single (ADV157-S) Status Input 1 to 32 No Yes
32-Channel Status Input (ADV151-P) Status Input 1 to 32 Yes Yes
64-Channel Status Input (ADV161-P) Status Input 1 to 64 Yes Yes
Status Input 16-Channel Status Input; 100VAC (ADV141-P) Status Input 1 to 16 Yes Yes
16-Channel Status Input; 200VAC (ADV142-P) Status Input 1 to 16 Yes Yes
16-Channel Status Input (ASD143-P) Status Input 1 to 16 Yes Yes
32-Channel SOE Status Input (ADV151-E) (*1) Status Input 1 to 32 Yes No
Yes
32-Channel Pushbutton Input (ADV151-P) Pushbutton Input 1 to 32 Yes
(*2)
16-Channel Pushbutton Input;
Pushbutton Pushbutton Input 1 to 16 Yes Yes
100VAC (ADV141-P)
Input
16-Channel Pushbutton Input;
Pushbutton Input 1 to 16 Yes Yes
200VAC (ADV142-P)
16-Channel Pushbutton Input (ASD143-P) Pushbutton Input 1 to 16 Yes Yes
Status/
32-Channel Status/32-Channel Pushbutton Input Status Input 33 to 64 Yes
Pushbutton Yes
(ADV161-P) Pushbutton Input 1 to 32 (*2)
Input
32-Channel Status Output; Single (ADV557-S) Status Output 1 to 32 No Yes
32-Channel Status Output (ADV551-P) Status Output 1 to 32 Yes Yes
Status Output 64-Channel Status Output (ADV561-P) Status Output 1 to 64 Yes Yes
16-Channel Status Relay Output (ADR541-P) Status Output 1 to 16 Yes Yes
8-Channel Status output (ASD533-S) Status Input 1 to 8 Yes Yes
Pulse-Width 1 to 32
Output (Odd Number Only)
32-Channel Pulse-Width Output (ADV551-P) Yes Yes
Pulse-Width Time-Proportion
Output 1 to 32
ON/OFF Output
(Including
Time-Proportion Pulse-Width 1 to 16
ON/OFF Output) 16-Channel Pulse-Width Relay Output Output (Odd Number Only)
Yes Yes
(ADR541-P) Time-Proportion
1 to 16
ON/OFF Output
A030202E.EPS
Note: • Yes in Redundancy column means the module supports dual-redundant configuration, and Yes in Remote column
means the module can be installed in a remote node.
• No in Redundancy column means the module does not support dual-redundant configuration, and No in Remote
column means the module can not be installed in a remote node.
*1: Can be applied only in the field control units that support dual-redundant configuration (AFS30D, AFS40D, AFG30D
and AFG40D).
*2: When this type of I/O module is installed in a remote node, the updating rate of inputs is about 2 or 4 times slower than
the status input I/O module installed in the remote node.

Table Contact I/O Modules Specification (2/2): KFCS2/KFCS £
Redun- Re-
Category Type (Model) I/O Type Terminal Number
dancy mote
Status Output 33 to 64
1 to 32
Status/Pulse 32-Channel Status/32-Channel Pulse-Width Pulse-Width Output Yes
(Odd Number Only) Yes
-Width Output Output (ADV561-P) (*3)
Time-Proportion
1 to 32
ON/OFF Output
1 to 32
32-Channel Status/Pulse-Width Output Pulse-Width Output
(Odd Number Only) No No
(ADV551-P)
Time-Proportion
1 to 32
ON/OFF Output
Status/Pulse 1 to 32
64-Channel Status/Pulse-Width Output Pulse-Width Output
-Width Output (Odd Number Only) No No
(ADV561-P)
(Local Node)
Time-Proportion
1 to 32
ON/OFF Output
1 to 16
16-Channel Status/Pulse-Width Relay Output Pulse-Width Output
(Odd Number Only) No No
(ADR541-P)
Time-Proportion
1 to 16
ON/OFF Output
Status Input/ 16-Channel Status Input/ Status Input 1 to 16

Yes Yes
Status Output 16-Channel Status Output (ADV851-S) Status Output 17 to 32
Status Input 1 to 16
ST2 Compatible
17 to 32 Yes
(16-Channel Status Input/16-Channel Status/ Pulse-Width Output Yes
Pulse-Width Output) (ADV859-P) (Odd Number Only) (*4)
Time-Proportion
17 to 32
ON/OFF Output
ST3 Compatible (32-Channel Status Input) Yes Yes
(ADV159-P) (*4) (*5)
ST3 Compatible (32-Channel Pushbutton Input) Yes Yes
Pushbutton Input 1 to 32 (*5)
(ADV159-P) (*4)
ST4 Compatible 1 to 32
Pulse-Width Output Yes Yes
ST (32-Channel Status/Pulse-Width Output) (Odd Number Only) (*5)
(*4)
Compatible (ADV559-P)
Time-Proportion
(No-Voltage 1 to 32
ON/OFF Output
Contact I/O
Signals) Status Input 1 to 32
ST5 Compatible
33 to 64 Yes Yes
(32-Channel Status Input/32-Channel Status/ Pulse-Width Output (*5)
Pulse-Width Output) (ADV869-P) (Odd Number Only) (*4)
Time-Proportion
33 to 64
ON/OFF Output
ST6 Compatible (64-Channel Status Input) Yes Yes
(ADV169-P) (*4) (*5)
ST7 Compatible 1 to 64
Pulse-Width Output Yes Yes
(64-Channel Status/Pulse-Width Output (Odd Number Only)
(*4) (*5)
(ADV569-P)
Time-Proportion
1 to 64
ON/OFF Output
A030203E.EPS

Note: • Yes in Redundancy column means the module supports dual-redundant configuration, and Yes in Remote column
means the module can be installed in a remote node.
• No in Redundancy column means the module does not support dual-redundant configuration, and No in Remote
column means the module can not be installed in a remote node.
*3: When this type of I/O module is installed in a remote node, the updating rate of inputs is about 2 or 4 times slower than
the status input I/O module installed in the remote node.
*4: The same dual-redundant configuration for CENTUM-XL is applied.
*5: The modules do not support dual-redundant configuration when installed in a remote node. When this type of I/O
module is installed in a remote node, the updating rate of inputs is about 2 or 4 times slower than the status input I/O
module installed in the remote node. However, the ST compatible status input modules are exceptions.
SEE ALSO
• Dual-redundant configuration for status output modules in CENTUM-XL and in KFCS2/KFCS are differ-
ent. For more information about it, see the following:
“■ Dual-Redundant Configuration of I/O Modules : KFCS2/KFCS £” in B4.2, “Dual-Redundant Ar-
chitecture of KFCS2 and KFCS”
• For more information about data updating period of remote nodes, see the following:
“● Contact I/O Data : KFCS2/KFCS £” in “■ Data Flow in Process I/O ¡ £” of C7.1.3, “Timing
of Process I/O”
TIP
Some I/O modules can have different types of signals on the terminals. Among them, in some I/O
modules each terminal can be defined individually with specific I/O signal type. While in some other I/O
modules, the terminals are fixed with I/O signal types even though the module can handle different signal
types.
• I/O Signal Type Definable for Each Terminal
As the following example illustrates, the descriptions in the table indicate that any of the terminals
numbered 1 to 32 can be defined with either Pulse-Width Output or Time-Proportioning ON/OFF
Output. For Pulse-Width Output signals, two points of outputs are required. So that, only specify the
odd number points when connecting the I/O to the function blocks. Be sure to reserve the next even
numbered point.
Table I/O Signal Type Definable for Each Terminal : KFCS2/KFCS £

1 to 32
Pulse-Width Output
(Odd Number Only)
Time-Proportion
1 to 32
ON/OFF Output
A030204E.EPS
• I/O Signal Types are Fixed to Terminals

As the following example illustrates, the descriptions in the table indicate that the I/O signal types of
the terminals are fixed. In the following table, the terminals numbered 33 to 64 are fixed to Status
Output signal type and the terminals numbered 1 to 32 are fixed to Pulse-Width Output signal type.
Table I/O Signal Types are Fixed to Terminals : KFCS2/KFCS £

Pulse-Width Output 1 to 32
A030205E.EPS

● Cautions on Selecting Status Output/Pulse-Width Output Modules
Some Status Output/Pulse-Width Output modules can define each point to either Status
Output or Pulse-Width Output freely. If both the Status Output and Pulse-Width Output
points are mixed in a module, the timing of status output to the field device may deviate by 8
points or 16 points.
In the cases such as coding the multiple output points, the status output timings of all points
should be the same. So that use the I/O modules that all points are Status Output type, or
use the I/O modules that the Status Output points and Pulse-Width Output points are fixed
to the points. By this way, the output timing of all status output points could be the same.
The following Status Output/Pulse-Width Output modules can freely assign each point to
either Status Output or Pulse-Width Output.
• Status Output/Pulse-Width Output module (Local Nodes Only)
ADV551-P, ADV-561P, ADR541-P
• ST Compatible (No-Voltage Contact I/O Signals)
ADV859-P, ADV559-P, ADV869-P, ADV569-P
The following Status Output/Pulse-Width Output modules have previously assigned points
for Status output and Pulse-Width output separately.
• Status Output/Pulse-Width Output module
ADV-561P
TIP
Regarding to the Status Output/Pulse-Width Output modules that output points can be freely assigned to
either Status Output or Pulse-Width Output, the status output actions are explained as follows.
• Write from FCU to I/O Modules
When writing from FCU to I/O modules, writing is performed in a unit of 16 points. In local nodes,
writing always interrupts other processing. Thus delay occurs by each 16 points when writing to I/O
modules. However, for the status outputs, the signals are output in the units of modules.
• Write from I/O Modules to Field Devices
ST compatible I/O modules output signals to field devices in the units of 16 points. Other I/O modules
output signals to field devices in the units of 8 points.
The outputs of terminal 1 to 32 from the modules other than ST compatible type have the following
delays.
Terminal 1 to 8
Terminal 9 to 16 Two milliseconds after outputs of terminal 1 to 8.
Terminal 17 to 24 Four milliseconds after outputs of terminal 1 to 8.
Terminal 25 to 32 Six milliseconds after outputs of terminal 1 to 8.
● Cautions on Installing ST Compatible Modules into Remote Nodes

A ST compatible module outputs each 16 status signals to the field. When ST compatible
modules are installed in remote modes, the outputs are delayed in the unit of 16 signals. If
four remote nodes are connected to an EB401, the delay time is 50 ms. If eight nodes
connected to a EB401, the delay time becomes 100 ms.

A3.2.1 Contact Input

Using contact inputs, an FCS can receive ON/OFF signals from field equipment.
■ Contact Input ¡ £
Contact inputs are ON/OFF signals from the field equipment to FCS.
The following contact input types are available.
• Status input
• Pushbutton input
Contact inputs indicate the status of a process signal such as valve’s limit switch or level
switch.
In the input processing of a sequence connection, an ON/OFF status of a contact input
together with its data status can be monitored for a condition judgment.
SEE ALSO
For details on relationship between IOM and I/O image, and how to access the image, see the followings
in section “■ Data Flow in Process I/O ¡ £” in chapter C7.1.3, “Timing of Process I/O”:
“● Contact I/O Data ¡”
“● Contact I/O Data : KFCS2/KFCS £”
“● Contact I/O Data : LFCS2/LFCS/SFCS £”

■ Condition Testing for Contact Inputs ¡ £
For the function blocks or sequence table blocks and logic chart block specified in se-
quence connection, the contact input signal’s ON/OFF status may be applied for condition
test.
The syntax form for contact input condition testing is shown below.
%Znnusmm.PV.ON/OFF ——To refer to ON/OFF status
%Znnusmm.PV=BAD ——Refer to data status (BAD)

Note: ¡ £ The symbols in the string have the following meanings.
• PFCS, LFCS2, LFCS and SFCS
nn: Fixed as 01 for PFCS and SFCS
Node Number (01 - 08) for LFCS2/LFCS
u: Unit Number
s: Slot Number
mm: Terminal Number
• KFCS2 and KFCS

u: Slot Number
s: Segment Number (*1)
mm: Terminal Number
*1: When using fieldbus communication module, the segment number can be set between 1 to 4. When using HART
compliant module, the segment number is set to 1 for analog signal and set to 2 for HART variable.
● Condition Testing for Status Inputs

For status input signal, PV is equal to ON when the input is ON, PV is equal to OFF when
the input is OFF.
● Condition Testing for Pushbutton Inputs

For pushbutton input signal, a change of the input from OFF to ON or from ON to OFF may
be detected. (Whether OFF to ON or ON to OFF is to be used is specified in the IOM Builder.)
When a change is detected, PV is equal to ON. It then changes to OFF after one scan cycle.
Scan period
PV value
ON
OFF
Momentary change detected

A030206E.EPS
Figure Pushbutton Input Operation

A3.2.2 Contact Output

Using contact outputs, an FCS can output ON/OFF signals to field equipment.
■ Contact Output
Contact outputs are used to output ON/OFF signals from FCS to field equipment according
to the contact ON/OFF status.
In a sequence control, the contact output signal can be used to send commands to a valve
or a pump for external operations, at the same time, the output signals can also be used as
the condition signals. When applied with regulatory control blocks, a contact output can be
a pulse width contact output, a time-proportioning contact output, a two-position ON/OFF
output or a three-position ON/OFF output.
SEE ALSO
• For more information about pulse width contact output, see the following:
C4.8.2, “Pulse Width Output Conversion”
• For more information about time-proportioning contact output, see the following:
“■ Time-Proportioning ON/OFF Output ¡ £” in chapter D1.10, “Time-Proportioning ON/OFF Con-
troller Block (PID-TP)”

■ Types of Contact I/O Outputs ¡ £
The types of I/O modules and the output type of the modules applied in PFCS/SFCS,
KFCS2/KFCS and LFCS2/LFCS are listed as follows.
Table Types of Contact I/O Outputs
FCS Contact Module Type Point Mode Output Type
Status
Pulse
PFCS/SFSC Status Output (NA)
Pulse-Width
Time-Proportioning ON/OFF
Status
Status Output SO (Fixed)
Pulse (*1)
PW Pulse-Width
Pulse-Width Output
TP Time-Proportioning ON/OFF
KFCS2/KFCS
Status
SO
Pulse (*1)
Status/Pulse-Width Output
PW Pulse-Width
SO Status
Status Output
PO Pulse
LFCS2/LFCS Pulse-Width Output PW Pulse-Width
PW (Fixed) Pulse-Width
Time-Proportioning Output
A030207E.EPS
*1: If the output of the connected function block is pulse output, the output terminal also outputs the pulse even though the
point mode is set as SO.
When PW, TP or PO point mode is specified to an output module terminal, the module
outputs ON/OFF signals in accordance with the output pulse time. If the module terminal is
specified with SO point mode, or if the module is installed in a PFCS/SFCS that does not
support point mode setting, the CPU of FCU (CPU of FCS in case of PFCS/SFCS) sets the
modules ON/OFF outputs.

● Contact Output Module Type: PFCS/SFCS
The output type of the I/O module can be chosen on PFCS/SFCS builder is status type
only.However, the I/O modules can give the different types of output (such as status contact
output, pulse width contact output or time-proportioning contact output) according to the
output signal from the function blocks that the I/O module connected since the ON/OFF
output commands are given from FCS CPU. Moreover, different types of output can be
performed by one I/O module. Since FCS CPU sends ON/OFF commands to the I/O
modules for different types of outputs, thus when an error occurs at the upper level (such as
in the CPU card), the I/O modules may give the contact outputs or give the 100% time-
proportioning output (MV) with the following behaviors.
When an error occurs at the upper level of the I/O modules, the ON or OFF outputs from
the I/O modules are continuous regardless of the output type of the module is Pulse, Pulse-
Width or Time-Proportioning. For the modules not specified with Fallback, or for the mod-
ules with Fallback but [All points maintain current value] option is checked, the I/O modules
keep the output status at the moment that the error occurred. For the modules with Fallback
but [All points turn off] option is checked, the modules become to output OFF signals at the
moment that the error occurred.
The time-proportioning ON/OFF output signal also becomes OFF for a moment even when
the output is 100%.
Suppose a time-proportioning ON/OFF output cycle is 10 seconds, the output becomes ON
for 5 seconds if the MV is 50%, while the output becomes ON for 10 seconds if MV is
100%.
However, even when the MV is 100% all the time, the output may momentarily becomes
OFF for a very short time. Since the output timings of the function blocks, FCS CPU and
output modules are not always consistent, this phenomenon occurs to the time-proportion-
ing output.

● Types of Contact Outputs : KFCS2/KFCS £
Contact I/O modules support the following types of outputs.
• Status Output
When an I/O module is used for status output or pulse output, the module is specified
to Status Output. Both status output or pulse output can be applied on the same
module. For each output point on the I/O module, the point mode can be designated
as Status Output (SO) if the point is used for status or pulse output. If the pulse output
is required, the output of the connected function block should be specified as pulse
output.
When an I/O module is used for Pulse-Width Output or Time-Proportioning ON/OFF
Output, the module is specified to Pulse-Width Output. Both status output and pulse
output can be applied on the same module. For each output point on the I/O module,
the point mode can be specified as Pulse-Width Output (PO) or Time-Proportioning
ON/OFF Output (PT).
• Status/Pulse-Width Output
When an I/O module is used for status output (including pulse output), Pulse-Width
Output or Time-Proportioning ON/OFF Output, the module is specified to Status/
Pulse-Width Output. The status output (including pulse output), Pulse-Width Output
and Time-Proportioning ON/OFF Output can be applied on the same module. For
each output point on the I/O module, the point mode can be specified as Status
Output (SO), Pulse-Width Output (PW) or Time-Proportioning ON/OFF Output (TP).
However, for some I/O modules, part or all of terminals are fixed to Status Output (SO)
while some others are fixed to Pulse-Width Output (PW) or Time-Proportioning ON/
OFF Output (TP).
When an error occurs at upper level (FCS CPU), the contact output behaves as follows.
• Status/Pulse Output
When an error occurs at the upper level of the I/O modules, the ON or OFF outputs
from the I/O modules are continuous. For the modules not specified with Fallback, or
for the modules with Fallback but [All points maintain current value] option is checked,
the I/O modules keep the ON/OFF output status at the moment that the error oc-
curred. For modules with Fallback but [All points turn off] option is checked, the mod-
ules output OFF signals from the moment that the error occurred.
When an error occurs at the upper level of the I/O modules, for the modules not
specified with Fallback, or for the modules with Fallback but [All points maintain current
value] option is checked, the I/O modules continue the ON/OFF output status at the
moment that the error occurred until the current output cycle is completed, then output
OFF signals. For the modules with Fallback but [All points turn off] option is checked,
the modules become to output OFF signals at the moment that the error occurred.
• Time-proportioning ON/OFF Output
When an error occurs at the upper level of the I/O modules, for the modules not
specified with Fallback, or for the modules with Fallback but [All points maintain current
value] option is checked, the I/O modules continue the ON/OFF output status and the
ON/OFF time proportions at the moment that the error occurred. For the modules with
Fallback but [All points turn off] option is checked, the modules become to output OFF
signals at the moment that the error occurred.

● Types of Contact Outputs : LFCS2/LFCS £
The output types of the input/output module contains the following:
• Status contact output
When the output signals are status type or pulse type, the status type I/O module can
be used. Both status outputs and pulse outputs can be given together from one I/O
module. Each terminal of the I/O module can be designated as a Status Output (SO)
or a Pulse Output (PO) by specifying the point mode of the terminal.
• Pulse width contact output
When the output signals are pulse width type, the pulse width contact output type I/O
module can be used. The point modes of all terminals of this type I/O module are all
fixed to pulse width (PW) type.
• Time-proportioning contact output
When the output signals are time-proportioning or pulse width type, the Time-propor-
tioning contact output type I/O module can be used. Both time-proportioning outputs
and pulse width outputs can be given from one I/O module together. Each terminal of
the I/O module can be designated as a Time-Proportioning ON/OFF (TP) or a Pulse
Width (PW) output by specifying the point mode of the terminal.
When an error occurs at upper level (FCS CPU), the contact output behaves as follows.
• Status/Pulse Output
When an error occurs at the upper level of the I/O modules, the ON or OFF outputs
from the I/O modules are continuous. For the modules not specified with Fallback, or
for the modules with Fallback but [All points maintain current value] option is checked,
the I/O modules keep the ON/OFF output status at the moment that the error oc-
curred. For modules with Fallback but [All points turn off] option is checked, the mod-
ules output OFF signals from the moment that the error occurred.
For the modules not specified with Fallback, the I/O modules continue the ON/OFF
output status at the moment that the error occurred until the current output cycle is
completed, then output OFF signals.
For the modules specified with Fallback and [All points maintain current value] option
is checked, the I/O modules continue the ON/OFF output status at the moment that
the error occurred.
For the modules with Fallback but [All points turn off] option is checked, the modules
become to output OFF signals at the moment that the error occurred.
• Time-proportioning ON/OFF Output
For the modules not specified with Fallback, the I/O modules continue the ON/OFF
output status and time-proportion at the moment that the error occurred.
For the modules specified with Fallback and [All points maintain current value] option
is checked, the I/O modules continue the ON/OFF output status at the moment that
the error occurred.
For the modules with Fallback but [All points turn off] option is checked, the modules
become to output OFF signals at the moment that the error occurred.

■ Manipulating Status Output of I/O Module
The status output signals of a status type I/O module can be manipulated in the following
styles.
• Latched type output
• Non-latched type output
• Pulse type output
• Flashing type output
● Latched Type Output ¡ £

Latched type outputs retain the current output status until an ON or OFF action command
is performed.
This type is unique to the sequence table block.
When the action signal field of the sequence table is entered as a latched type, the output
becomes ON when the condition of the rule where the Y pattern is specified becomes true.
The output remains ON even if the condition is no longer true. It will switch to OFF when the
rule for which the N pattern is specified becomes true.

The syntax form for a latched contact output is shown below.
%Znnusmm.PV.H
Node Number (01 - 08) for LFCS2 and LFCS
u: Unit Number
s: Slot Number
mm: Terminal Number
• KFCS2 and KFCS

u: Slot Number
s: Segment Number (*1).
mm: Terminal Number
Timing chart for latched contact outputs is shown below.
TRUE
Logical computation
FALSE FALSE
result
(ON operation side)
Logical computation FALSE TRUE

result
(OFF operation side)
OFF ON OFF
Latched type output
E A B B E E C D E
A ON operation
ON operation in the case of a block
B which outputs every time
C OFF operation
OFF operation in the case of a block
D which outputs every time
E Retains the current status.
A030208E.EPS
Figure Timing Chart for Latched Contact Output
If a latched syntax is scripted in a block other than sequence table block, such as an logic
chart block or other blocks in which output manipulation and terminal connection for se-
quence link are available, it will behave the same as non-latched output.

● Non-Latched Contact Output ¡ £
A non-latched contact output will switch to ON when the logical computation result is “True”
or switch to OFF when the result is “False.”
If the entry in the action signal field of the sequence table is a non-latched type, the output
will be ON when the rule, where the Y pattern is specified, becomes True, or will be OFF
when the rule becomes False.
For the logic chart block or other blocks in which output manipulation and terminal connec-
tion for sequence link are available, a non-latched type script will make the output ON when
the logic calculation results in True, or will make the output OFF when the logic calculation
results in False.
The syntax form for non-latched contact outputs is shown below.
%Znnusmm.PV.L
u: Unit Number
s: Slot Number
mm: Terminal Number
• KFCS2 and KFCS

nn: Node Number (01-10)
u: Slot Number
mm: Terminal Number
For non-latched contact outputs, the N pattern entered the action rule of sequence table will
be ignored.
A timing chart for non-latched contact outputs is shown below.
TRUE
Logical computation FALSE FALSE

result
(ON/OFF operation)
OFF ON OFF
Non-latched
type output D A B B C D D D D
A ON operation
ON operation in the case of a block
B which outputs every time
C OFF operation
OFF operation in the case of a block
D which outputs every time
E Retains the current status.
A030209E.EPS
Figure Timing Chart for Non-Latched Contact Output

● Pulse Contact Output : PFCS/KFCS2/KFCS/SFCS
Pulse contact output means the output will switch to ON for only one second when the
logical computation result is “True.”
If the entry in the action signal field of the sequence table is pulse type, the output will be
ON when the rule for Y action becomes True, at the same time, the sequence table will give
a status output to the output module, make the contact output ON. After one second, the
corresponding output on the status output module will be turned OFF by processor unit of
PFCS/SFCS or FCU of KFCS2/KFCS, so as to make the contact output OFF.
The syntax form for pulse type contact output is only for sequence table.
The syntax is shown as follows. If this syntax is used in LFCS2/LFCS, the action signal will
not take action.
%Znnusmm.PV.P
• PFCS and SFCS
u: Unit Number
s: Slot Number
mm: Terminal Number
• KFCS2 and KFCS

u: Slot Number
mm: Terminal Number
For pulse type contact output, the N action entered the action field will be ignored.
TRUE
Logical computation FALSE FALSE

result
(ON/OFF operation)
ON
Pulse type output
1 sec. A030210E.EPS
Figure Timing Chart for Pulse Contact Outputs : PFCS/KFCS2/KFCS/SFCS
IMPORTANT
This syntax is suitable for the sequence table with processing timing of [Output Only when
Conditions Change]. If using the sequence table with processing timing of [Output Each
Time Conditions are Satisfied], the following points need to be dealt with.
When condition is established on the sequence table with processing timing of [Output
Each Time Conditions are Satisfied], the sequence table will send an ON signal to the
output module every scan cycle as long as the condition is True. This will keep the output
ON all the time. To avoid this, it is recommended to introduce an additional signal in the
condition rule to mask the condition after the True condition establishes for one scan cycle.

● Pulse Contact Output : LFCS2/LFCS £
Pulse output means the contact output will switch to ON for only one second when the
logical computation result is “True.”
To implement the pulse output on LFCS2/LFCS, it is necessary to configure the output
points’ [Point Mode] on the builder of I/O modules (ADM55R, ADM51T, ADM51C, ADM52T,
ADM52C) to [Pulse Type Output (PO)] mode.
When LFCS2/LFCS gives an pulse output, the syntax for latched or non-latched output
action can be used in sequence table block and the syntax for non-latched output action
can be used in logic chart block and in the blocks whose terminals designated for sequence
connection. For the output terminals whose [Point Mode] is [Pulse Type Output], only the
ON action of the latched and non-latched syntax take effect. When an ON action command
given from function block to an output point on the output module, if the point mode is Pulse
Type, the output point will be turned ON for only one second then turned OFF.
Example of non-latched type contact:

%Z021101.PV.L . . . . . . . . Y
Example of latched type contact:
%Z021101.PV.H . . . . . . . . Y
● Flashing Contact Output ¡ £

Flashing contact outputs switch to ON and OFF repeatedly at intervals of approximately
one second when the logical computation for the action rule of sequence table result is
“True”. If the logical computation result is “False”, the output will stop flashing, but the ON/
OFF status remains ON. To turn OFF a flashing contact output, the OFF action must be
performed using a latched type syntax.
The syntax form for flashing contact outputs is shown below.
%Znnusmm.PV.F
u: Unit Number
s: Slot Number
mm: Terminal Number
• KFCS2 and KFCS

u: Slot Number
mm: Terminal Number

A timing chart for flashing contact outputs is shown below.
Flashing ON
command FALSE TRUE FALSE
%Z011101.PV F Y
Flashing OFF
command FALSE TRUE
%Z011101.PV F N
Latched type
output command FALSE TRUE
%Z011101.PV H N
1 sec.
OFF ON OFF
Flashing output
A030211E.EPS
Figure Timing Chart for Flashing Contact Output
When above syntax is used in logic chart block or in the blocks whose terminals designated
for sequence connection, the output “flashes” ON and OFF at an interval of approximately
one second when the logic computation results in True. While the “flashing” stops and ON
all the time when the computation results in False.

<A3.3 Configuring Process I/O of PFCS, LFCS2, LFCS and SFCS> A3-31
A3.3 Configuring Process I/O of PFCS, LFCS2, LFCS

and SFCS
The process inputs/outputs must be defined in System View or IOM Builder before
they can be used.
■ Categories of IOM : PFCS/LFCS2/LFCS/SFCS

▼ IOM Type – Category, IOM Type – Type
Parameters for each type of process inputs/outputs vary with the type of IOM. The following
table shows the categories and types of IOMs as well as IOM names.
Table Classification of IOM (1/2) : PFCS/LFCS2/LFCS/SFCS
Category Type Name
Current input AAM11
Voltage input AAM11
Current Input (BRAIN Communication) AAM11B
Voltage input AAM11B
Current input (Single function) AAM10
Voltage input (Single function) AAM10
mV input AAM21
Control input/output
Thermocouple input AAM21
Resistance Temperature Detector input AAM21
Potentiometer input AAM21
Pulse input APM11
Current output AAM51
Voltage output AAM51
Current output (Single function) AAM50
Multipoint control analog
Voltage input and current output AMC80
input/output
Voltage input AMM12T
mV input AMM22M
Thermocouple input AMM22T
Multiplexer input/output
Resistance Temperature Detector input AMM32T
Current input AMM42T
Current output AMM52T
Voltage input (Connector type) AMM12C
Connector Type mV Input AMM22C
Connector Type Resistance Temperature Detector
AMM32C
Input
Multiplexer (Connector type)
Connector Type Thermocouple mV Input AMM25C
Voltage input AMM12T(*1)
mV input AMM22M(*1)
Thermocouple AMM22T(*1)
A030301E.EPS
*1: ¡ £ Supported in PFCS and SFCS.

Table Classification of IOM (2/2) : PFCS/LFCS2/LFCS/SFCS
Category Type Name
Relay status input ADM15R
Relay pushbutton input ADM15R
Relay input/output Relay status output ADM55R
Relay pulse width output ADM55R(*2)
Relay time-proportioning output ADM55R(*2)
16-point terminal-type contact status input ADM11T
16-point terminal-type contact pushbutton input ADM11T
32-point terminal-type contact status input ADM12T
32-point terminal-type contact pushbutton input ADM12T
16-point terminal-type contact status output ADM51T
Contact terminal 16-point terminal-type contact pulse width output ADM51T(*2)
16-point terminal-type contact time-proportioning output ADM51T(*2)
32-point terminal-type contact status output ADM52T
32-point terminal-type contact pulse width output ADM52T(*2)
32-point terminal-type contact time-proportioning output ADM52T(*2)
16-point connector-type contact status input ADM11C
16-point connector-type contact pushbutton input ADM11C
32-point connector-type contact status input ADM12C
32-point connector-type contact pushbutton input ADM12C
16-point connector-type contact status output ADM51C
Contact connector
16-point connector-type contact pulse width output ADM51C(*2)
16-point connector-type contact time-proportioning output ADM51C(*2)
32-point connector-type contact status output ADM52C
32-point connector-type contact pulse width output ADM52C(*2)
32-point connector-type contact time-proportioning output ADM52C(*2)
Category Type Name
A030302E.EPS
*2: ¡ Only supported in CS 3000.

£ Only supported in LFCS2/LFCS.

■ Process Inputs/Outputs Definition : PFCS/LFCS2/LFCS/SFCS
Parameters of process inputs/outputs are shown below for each IOM category.
Table Parameters for Each IOM Category : PFCS/LFCS2/LFCS/SFCS
Relay,
Mutipoint control analog Multiplexer/Multiplexer
Control input/output contact terminal,
input/output (Connector type)
contact connector
Signal Signal Conversion Point mode (*1)
Conversion Service comment Service comment P&ID tag name
Service comment Range high/low limits Range high/low limits Tag name
Range high/low limits Range Range Tag comment
Unit of range Details setting Details setting Switch position label
Details setting P&ID tag name P&ID tag name Label Format
Dual Redundant Label Label Btn1, Btn2
P&ID tag name IOP detection level (SIOP) IOP detection level (SIOP) Security level
Label High-limit detection level (HIIOP) High-limit detection level (HIIOP) Tag mark
Input open detection (IOPE) Low-limit detection level (LOIOP) Low-limit detection level (LOIOP) Upper window
IOP detection level (SIOP) Fallback (FBEN) Fallback (FBEN) Help
High-limit detection level
(HIIOP) Fallback output value (FBOUT) Fallback output value (FBOUT) Filter time
Low-limit detection level

Output open detection (OOPE) Output open detection (OOPE) Detection edge
(LOIOP)
Output open detection (OOPE) OOP clear (OPCLS) Destination of burnout Fallback
OOP output clearance time
Fallback (FBEN) OOP clear (OPCLS) Dual
(TOPCLS)
Fallback output value OOP output clearance time Time-proportioning
Dual
(FBOUT) (TOPCLS) ON/OFF Pulse-width (*1)
Total resistance (RESIST) Command Cold Jct. Comp. Phasing offset (*1)
Pulse input filter (PLFL) Command Command (*1)
Transmitter power (VTTSEL)
Square Root (SQRT)
SQRT low input cut value
(LCUT)
Cold Jct. Comp. (RJCD)
OOP clear (OPCLS)
OOP output clearance time
(TOPCLS)
Command
Relay,
Mutipoint control analog Multiplexer/Multiplexer
Control input/output contact terminal,
input/output (Connector type)
contact connector
A030303E.EPS
*1: ¡ Only supported in CS 3000.

£ Displayed only when the modules of LFCS2/LFCS shown below are selected:
• 16-point terminal-type contact status output module
• 16-point terminal-type contact pulse width output module
• 16-point terminal-type contact time-proportioning output module
• 32-point terminal-type contact status output module
• 32-point terminal-type contact pulse width output module
• 32-point terminal-type contact time-proportioning output module

A3.3.1 Control Input/Output Module Configuration

The details about setting items for control I/O module configuration are explained as
follows.
• Signal
• Conversion
• Service comment
• Range Low/High Limit
• Unit
• Set Details
• Dual
• P&ID tag name
• Label
• Detect IOP (IOPE)
• IOP Detection Level (SIOP)
• High-limit detection level (HIIOP)
• Low-limit detection level (LOIOP)
• Detect OOP (OOPE)
• Fallback (FBEN)
• Fallback Output data (FBOUT)
• Resistance (RESIST)
• Input Signal Filtering (PLFL)
• Transmitter power (VTTSEL)
• Square Root (SQRT)
• SQRT low input cut value (LCUT)
• Cold Junction Compensation (RJCD)
• OOP Clear (OPCLS)
• OOP output clear time (TOPCLS)
• Command Line

■ Signal : PFCS/LFCS2/LFCS/SFCS
▼ Signal
This item is used to specify the IOM type.
This item is defined in the IOM Builder.
The following IOM types can be selected.
• Current input (AAM11)
• Voltage input (AAM11)
• Current input (AAM11B)
• Voltage input (AAM11B)
• Current input/Single function (AAM10)
• Voltage input/Single function (AAM10)
• mV input (AAM21)
• Thermocouple input (AAM21)
• Resistance temperature detector input (AAM21)
• Potentiometer input (AAM21)
• Pulse input (APM11)
• Current output (AAM51)
• Voltage output (AAM51)
• Current output/Single function (AAM50)

■ Conversion – Control I/O : PFCS/LFCS2/LFCS/SFCS
▼ Conversion
This item is defined in the IOM Builder.
The selection list varies with the IOM type.
The selection list and default value for each IOM type are shown in the table below.
Table Selection Lists and Default Values for Signal Conversion : PFCS/LFCS2/LFCS/SFCS
Signal conversion
IOM type
Selection list Default value
Current input (AAM11) No conversion No conversion
Voltage input (AAM11) No conversion No conversion
Current input (AAM11B) No conversion No conversion
Voltage input (AAM11B) No conversion No conversion
Current input/Single function (AAM10) No conversion No conversion
Voltage input/Single function (AAM10) No conversion No conversion
mV input (AAM21) No conversion No conversion
Type K
Type E
Type T
Type J
Thermocouple input (AAM21) Type K
Type R
Type S
Type B
Type N
PT100
Resistance temperature detector input (AAM21) PT100
JPT100
Potentiometer input (AAM21) No conversion No conversion
Two-wire power supply type
Contact input type
Pulse input (APM11) Two-wire power supply type
Three-wire power supply
type
Current output (AAM51) No conversion No conversion
Voltage output (AAM51) No conversion No conversion
Current output/Single function (AAM50) No conversion No conversion
A030304E.EPS
■ Service Comment – Control I/O : PFCS/LFCS2/LFCS/SFCS

▼ Service Comment
These items are defined in the IOM Builder.
The default is null.
A character string consisting of up to 40 characters can be entered.
The service comment setting is optional and can be left blank.

■ Range High/Low Limit – Control I/O : PFCS/LFCS2/LFCS/SFCS
▼ Low Limit/High Limit
The high-limit and low-limit of the terminal measurement range are defined in the IOM
Builder.
Values which can be selected as the high-limit and low-limit vary with the IOM type and
signal conversion type. The high-limit and low-limit selection list and default value for each
IOM type are shown in the table below.
Table High-Limit and Low-Limit Selection Lists and Default Values for Measurement Range (1/2) :
PFCS/LFCS2/LFCS/SFCS
Low-limit High-limit
IOM type Signal Conversion Unit Selection Default Selection Default
list Value list Value
Current input (AAM11) No conversion mA 0 to 20 4 0 to 20 20
Voltage input (AAM11) No conversion V 0 to 10 1 0 to 10 5
Current input (AAM11B) No conversion mA 0 to 20 4 0 to 20 20
Voltage input (AAM11B) No conversion V 0 to 10 1 0 to 10 5
Current input/Single function (AAM10) No conversion mA 4 (fixed) 4 20 (fixed) 20
Voltage input/Single function (AAM10) No conversion V 1 (fixed) 1 5 (fixed) 5
mV input (AAM21) No conversion mV -50 to 150 -50 -50 to 150 150
C (Celsius) -200 (fixed) -200 1200 (fixed) 1200
Type K F (Fahrenheit) -300 (fixed) -300 2200 (fixed) 2200
K (Kelvin) 100 (fixed) 100 1500 (fixed) 1500
Type E F (Fahrenheit) -300 (fixed) -300 1700 (fixed) 1700
Type T F (Fahrenheit) -300 (fixed) -300 650 (fixed) 650
Type J F (Fahrenheit) -40 (fixed) -40 1400 (fixed) 1400
Thermocouple input (AAM21)
C (Celsius) 0 (fixed) 0 1600 (fixed) 1600
Type R F (Fahrenheit) 0 (fixed) 0 2900 (fixed) 2900
Type S F (Fahrenheit) 0 (fixed) 0 2900 (fixed) 2900
Type B F (Fahrenheit) 1100 (fixed) 1100 3100 (fixed) 3100
Type N F (Fahrenheit) -300 (fixed) -300 2200 (fixed) 2200
Selection Default Selection Default
IOM type Signal Conversion Unit list Value list Value
A030305E.EPS
Note: For a thermocouple input (AAM21), selecting the unit of range displays the corresponding high and low limits of the
range.

Table High/Low Limit Selection Lists and Default Values for Measurement Range (2/2) :
Resistance temperature detector input
PT100 F (Fahrenheit) -300 (fixed) -300 1500 (fixed) 1500
(AAM21)
JPT100 F (Fahrenheit) -300 (fixed) -300 900 (fixed) 900
(AAM21)
Potentiometer input (AAM21) No conversion Ohm 0 to 30000 100 100 to 30000 2000
Pulse input (APM11) - -
Current output (AAM51) No conversion mA 4 (fixed) 4 20 (fixed) 20
Voltage output (AAM51) No conversion V 0 to 10 1 0 to 10 5
Current output/Single function
No conversion mA 4 (fixed) 4 20 (fixed) 20
(AAM50)
A030306E.EPS
Note: For a resistance temperature detector input (AAM21), selecting the unit of range displays the corresponding high and
low limits of the range.
The high and low limit of range can be specified for [mV Input], [Potentiometer Input],
[Current Input] and [Voltage Input] of AAM11 module, and [Voltage Output] of AAM51
modules. A value up to 7 digits including decimal point can be entered as the High or Low
limit.
■ Unit of Range – Control I/O : PFCS/LFCS2/LFCS/SFCS

▼ Unit
The unit of measurement range is defined in the IOM Builder.
Selectable units of measurement range vary with the IOM type.
The unit selection list and default value for each IOM type are shown in the table below.
Table Selection Lists and Default Values for Unit of Measurement Range : PFCS/LFCS2/LFCS/SFCS
Unit
IOM type
Current input (AAM11) mA (fixed) mA
Voltage input (AAM11) V (fixed) V
Current input (AAM11B) mA (fixed) mA
Voltage input (AAM11B) V (fixed) V
Current input/Single function (AAM10) mA (fixed) mA
Voltage input/Single function (AAM10) V (fixed) V
mV input (AAM21) mV (fixed) mV
Thermocouple input (AAM21) deg C, deg F or K Deg C
Resistance temperature detector input (AAM21) deg C, deg F or K Deg C
Potentiometer input (AAM21) ohm (fixed) ohm
Pulse input (APM11)
Current output (AAM51) mA (fixed) mA
Voltage output (AAM51) V (fixed) V
Current output/Single function (AAM50) mA (fixed) mA
A030307E.EPS

■ Set Details – Control I/O : PFCS/LFCS2/LFCS/SFCS
▼ Set Details
The IOM details are defined in the IOM Builder.
Selectable items vary with the IOM type.
Table Selection Lists and Default Values for IOM Details Setting : PFCS/LFCS2/LFCS/SFCS
Details
IOM type
Current input (AAM11) None None
Voltage input (AAM11) None None
Current input (AAM11B) None None
Voltage input (AAM11B) None None
Current input/Single function (AAM10) None None
Voltage input/Single function (AAM10) None None
Without burnout,
mV input (AAM21) burnout upscale, Upscale
burnout downscale
Without burnout,
Thermocouple input (AAM21) burnout upscale, Upscale
burnout downscale
Without burnout,
Resistance temperature detector input (AAM21) burnout upscale, Upscale
burnout downscale
Without burnout,
Potentiometer input (AAM21) burnout upscale, Upscale
burnout downscale
No Terminator
Terminator = 200
Pulse input (APM11) No Terminator
Terminator = 510
Terminator = 1000
Direct Output
Current output (AAM51) Direct Output
Reverse Output
Direct Output
Voltage output (AAM51) Direct Output
Reverse Output
Direct Output
Current output/Single function (AAM50) Direct Output
Reverse Output
A030308E.EPS
SEE ALSO
For more information about direct and reverse output, see the following:
“● Analog Output Direction” of “■ No-Conversion in the Regulatory Control Block” in C4.8.1, “No-Con-
version”

■ Dual Redundant – Control I/O : PFCS/LFCS2/LFCS/SFCS
▼ Dual
The dual redundant can be specified Enable/Disable in the IOM Builder.
When [Dual] is checked, dual-redundancy is enabled. By default, [Dual] is not checked.
The dual redundant can be designated to the current output module AAM51 or AAM50,
only for the odd numbered IOM. The IOM is called duplex source.
If the Dual redundant is defined to the IOM, the signal of the duplex source will be copied to
its corresponding duplex destination. Once the signal is copied, definition change on the
duplex destination IOM become impossible.
The table below shows the relationship between terminal numbers of duplex source IOMs
and destination IOMs.
Table Dual Redundant Definition : PFCS/LFCS2/LFCS/SFCS
Duplex source 1 3 5 7 9 11 13 15
Duplex destination 2 4 6 8 10 12 14 16
A030309E.EPS
If the entries in the fields (e.g., Range Low/High Limit, Dual Redundant) except for the
“Signal” field for a duplex source IOM are changed, the changes will also reflect on the
corresponding duplex destination IOM. If the dual redundant for a duplex source IOM is set
to “Disabled”, setting of the corresponding duplex destination IOM will be possible.
If the entry in the “Signal” field for a duplex source IOM is changed or duplex source IOM
itself is deleted, the record for the corresponding duplex destination IOM will be deleted too.
SEE ALSO
For more information about connection method when dual redundant is designated, see the following:
“■ Data Setting with Respect to Dual-Redundant Output” in C2.1, “Data Connection”

■ P&ID Tag Name – Control I/O : PFCS/LFCS2/LFCS/SFCS
▼ P&ID Tag Name
A P&ID tag name of up to sixteen characters can be specified in the IOM Builder. The
setting is optional, and blank as the default.
■ User-Defined Label – Control I/O : PFCS/LFCS2/LFCS/SFCS

▼ Label
A user-defined label of up to 16 characters (as the name of the function block’s input/output
terminal) can be specified in the IOM Builder.
The entry format of user-defined labels is as follows:
%%Mnnnnnnnnnnnnn
Where
%%: Always %%
M: One uppercase letter
nnnnnnnnnnnnn: Up to 13 alphanumeric characters
The setting is optional, and blank as the default.
■ Detect Input Open (IOPE) – Control I/O : PFCS/LFCS2/LFCS/SFCS

▼ Detect IOP
The detection for wire breakage (input open) of the input signal can be defined on IOM
Builder. Choosing [Tools] - [Set Details] on the IOM builder, [Detect IOP] check box be-
comes available.
By default, the check box is checked.
The IOMs allowed to select IOPE are listed below.
• Current input (Simplified) (AAM10)
• Voltage input (Simplified) (AAM10)

■ IOP Detection Level (SIOP) – Control I/O : PFCS/LFCS2/LFCS/SFCS
▼ IOP Detection Level
The IOP detection level can be specified on IOM Builder. Choosing [Tools] - [Set Details] on
the IOM builder, [IOP Detection Level] check box becomes available.
By default, this check box is not checked, so that the default scale high detection level
(HIIOP) is +106.3% and scale low detection level (LOIOP) is -6.3%.
The IOMs allowed to select SIOP are listed bellow.
■ High-Limit Detection Level (HIIOP) – Control I/O : PFCS/LFCS2/LFCS/

SFCS
▼ High Limit
The IOP high-limit detection level can be defined in the IOM Builder.
The level can be defined within a range of -1000.0 to 1000.0 (max. 5 digits, in %). If the
high-limit is defined lower than the low-limit (LOIOP), an error will occur. The default is
“+106.3.”
HIIOP can be defined only when “Enabled” is set for SIOP.
The IOMs allowed to select HIIOP are listed below.

■ Low-Limit Detection Level (LOIOP) – Control I/O : PFCS/LFCS2/LFCS/SFCS
▼ Low Limit
The IOP low-limit detection level is defined in the IOM Builder.
The level can be defined within a range of -1000.0 to 1000.0 (max. 5 digits, in %). If the
lower-limit is defined higher than the high-limit (HIIOP), an error will occur. The default is “-
6.3.”
LOIOP can be set only when “Enabled” is set for SIOP.
The IOMs allowed to select LOIOP are listed below.
■ Output Open Detection (OOPE) – Control I/O : PFCS/LFCS2/LFCS/SFCS

▼ Detect OOP
The detection for wire breakage (output open) of the output signal can be defined in the
IOM Builder. Choosing [Tools] - [Set Details] on the IOM builder, [Detect OOP] check box
becomes available.
By default, this check box is checked.
The IOMs allowed to select OOPE are listed below.
• Current output (Simplified) (AAM50)

■ Fallback (FBEN) – Control I/O : PFCS/LFCS2/LFCS/SFCS
▼ Fallback, Fallback – Maintain Current Value
On the IOM Builder, fallback may be set. Choosing [Tools] - [Set Details] on the IOM
builder, [Fallback] check box becomes available.
By default, this check box is not checked.
• When check the “Fallback” item, then it is required to check the option button for either
“Maintain Current Value” or “Output data.” The default option is “Maintain Current
Value.”
• When not check the “Fallback” item, the current value will be held when the processor
unit or the interface of the processor unit fails. However, the occurrence of the abnor-
mality will not be notified even when the failed processor unit or the interface of the
processor unit return to normal state.
The IOMs allowed to select FBEN are below.
■ Fallback Output Value (FBOUT) – Control I/O : PFCS/LFCS2/LFCS/SFCS

▼ Fallback – Output
The output data value (FBOUT) for fallback may be defined on IOM Builder.
Up to 5 digits may be used for FBOUT, the range for current output is -17.2 to 112.5 while
the range for voltage output is -25.0 to 225.0 (unit: %). There is no default setting.
The output data value (FBOUT) may be defined only when the “Set Fallback” item is
checked.
The IOMs allowed to select FBOUT are listed bellow.
■ All Resistance Value (RESIST) – Control I/O : PFCS/LFCS2/LFCS/SFCS

▼ Resistance
The total resistance of potentiometers may be defined on the IOM Builder. Choosing [Tools]
- [Set Details] on the IOM Builder, [Resistance] input field becomes available.
All resistance values (RESIST) may be defined in up to 7 digits number in the range of 0 to
3000 (unit: ohm). When value is not defined, the high limit of the total resistance value will
be used. There is no default setting.
The IOMs allowed to select RESIST are listed below.

■ Pulse Input Filter (PLFL) – Control I/O : PFCS/LFCS2/LFCS/SFCS
▼ Pulse Input-Input Filtering
The pulse input filter can be defined on IOM Builder. Choosing [Tools] - [Set Details] on the
IOM builder, [Input Filtering] check box becomes available.
The IOMs allowed to select PLFL are listed below.
■ Transmitter Power Supply (VTTSEL) – Control I/O : PFCS/LFCS2/LFCS/

SFCS
▼ Pulse Input-Transmitter Power
The voltage of the pulse input transmitter power supply (APM11) can be defined in the IOM
Builder. Choosing [Tools] - [Set Details] on the IOM Builder, [Transmitter Power] input field
becomes available.
The voltage is defined to either [12] or [24] (V). The default is [12].
The IOMs allowed to select VTTSEL are listed below.
■ Square Root Extraction (SQRT) – Control I/O : PFCS/LFCS2/LFCS/SFCS

▼ Square Root
The square root extraction can be defined on IOM Builder. Choosing [Tools] - [Set Details]
on the IOM Builder, [Square Root] check box becomes available.
The IOMs allowed to select SQRT are listed below.
SEE ALSO
For details on how to perform analog input square root extraction for a function block, see the following:
“■ Analog Input Square Root Extraction ¡ £” in C3.1.1, “Input Signal Conversions Common to
Regulatory Control Blocks and Calculation Blocks”

■ SQRT Low Input Cut Value (LCUT) – Control I/O : PFCS/LFCS2/LFCS/
SFCS
▼ Low-Input Cut
The low input cut value for square root extraction can be defined in the IOM Builder.
When the input signal is below the low input cut value, the square root extraction will not be
performed, the output equals to the input value.
The default is “0.6” (%).
LCUT can be defined only when [Square Root] is checked.
The IOMs allowed to select LCUT are listed below.
SEE ALSO
For details on how to perform analog input square root extraction for a function block, see the following:
“■ Analog Input Square Root Extraction ¡ £” in C3.1.1, “Input Signal Conversions Common to
Regulatory Control Blocks and Calculation Blocks”
■ Cold Junction Compensation (RJCD) – Control I/O : PFCS/LFCS2/LFCS/

SFCS
▼ Cold Junction Compensation
The cold junction compensation can be defined on IOM Builder. Choosing [Tools] - [Set
Details] on the IOM Builder, [Cold Junction Compensation] check box becomes available.
By default, this check box is checked except for Thermocouple input Type B.
The IOMs allowed to select RJCD are listed below.
■ OOP Clear (OPCLS) – Control I/O : PFCS/LFCS2/LFCS/SFCS

▼ OOP Clear
OOP output clear may be specified so that to make the output into tight-shut state auto-
matically when a certain time period elapsed after OOP occurs.
The item [OOP Clear] may be checked on IOM Builder. Choosing [Tools] - [Set Details] on
the IOM builder, [OOP Clear] check box becomes available.
The IOMs allowed to select OPCLS are listed below.

■ OOP Clearance Time (TOPCLS) – Control I/O : PFCS/LFCS2/LFCS/SFCS
▼ Clear Time
OOP output clear time is the time limit to make the output into tight-shut state automatically
after OOP occurred.
OOP output clear time may be set on the IOM Builder.
OOP output clear time may be defined in an up to 4 digits value in the range of 0 to 25.5
(unit: seconds). The default setting is 4 seconds.
[Clear Time] can be set only when the [OOP Clear] check box is checked.
The IOMs allowed to select TOPCLS are listed below.

■ Command Line – Control I/O : PFCS/LFCS2/LFCS/SFCS
▼ Command
The optional setting for each I/O module can be set by entering a line of command script.
IMPORTANT
When command scripts are modified in command lines of an I/O module, downloading the
I/O module’s configuration will be necessary. During downloading, the I/O module will be in
FAIL state for a while. So that be cautious when changing the command line.
Command scripts can be entered on Details setting dialog box of IOM Builder.
The command scripts for control I/O modules (AAM11, AAM11B, AAM10, AAM21, APM11,
AAM51, AAM50) are shown as follows:
Table Command Scripts may be Applied for Control I/O Modules : PFCS/LFCS2/LFCS/SFCS
Command Description Default Syntax

ORBE Readback the output Yes Yes/No
SORG Output range for special compensation No No/<Range Low>䉭<Range High>
SOOP Special OOP Detection Level No No/<Detection Level>
SP1 Special Linearization Table No No/(<Interpolation Code>䉭X1,Y1䉭X2,Y2䉭X3,Y3 ...)
PVLMT Limit for Measurement No No/APD_LLMT䉭APD_HLMT(%)
TSHUT Tight Shut Output Value No No/<a Value>
INREV Reverse the Input No Yes/No
A030325E.EPS
䉭: Space

● ORBE (Readback the Output) : PFCS/LFCS2/LFCS/SFCS
This command set the module to readback the output, if the discrepancy is too large, the I/O
module changes to FAIL status.
Syntax:
ORBE=Yes
ORBE=No
Parameters:
• Yes
Readback the output and check the discrepancy. (default)
• No
Do not readback the output
● SORG (Output Range for Special Compensation) : PFCS/LFCS2/LFCS/

SFCS
The output range for special compensation can be defined with real values (% or degree).
Syntax:
SORG=No
SORG=25 75
Parameters:
• No
Output Range for Special Compensation will not be specified. In this case, the range
will be the same as the measurement range.
• <Range Low Limit>䉭<Range High Limit> 䉭: Space
The specified range will be converted into 1 to 5 V for compensation output.
● SOOP (Special OOP Detection Level) : PFCS/LFCS2/LFCS/SFCS

A special OOP detection level can be specified.
Syntax:
SOOP=No
SOOP=0.001
Parameters:
• No
No special OOP detection level, the default OOP detection level of IOM will be used.
• SOOP detection level
A special OOP detection level can be specified with a value in the unit of Ampere. Be
cautious not to initiate OOP alarm when tight-shut is performed.

● SP1 (Special Linearization Table) : PFCS/LFCS2/LFCS/SFCS
A table for linearization can be specified so that signal linearization can be performed
based on this table.
Syntax:
SP1=No
SP1=(<Interpolation Code> X1,Y1 X2,Y2 X3,Y3 ...Xn,Yn)
Parameters:
• No
No special linearization table, the default linearization table in the IOM will be used
(default).
• Interpolation Code:
1: Linear interpolation
2: Quadratic interpolation
• Xn,Yn
Data for linearization. Xn stands for input value, Yn stands for output value.
The number of data ranges from 2 to 21.
The units for Xn and Yn are as follows:
Table Units for Xn and Yn : PFCS/LFCS2/LFCS/SFCS

Signal Xn Unit Yn Unit
Current Input A %
Voltage Input V %
mV Input V %
Thermocouple Input V C (Celsius)
Resistance temperature detector Input ohm C (Celsius)
Potentiometer Input % (*1) %
Current Output A %
Voltage Output V %
A030326E.EPS
*1: Percentage (%) is used in accordance with range of Input Resistance (ohm).

● PVLMT (Limit for Measurement) : PFCS/LFCS2/LFCS/SFCS
This command set a high and a low limit for measurement. After setting the limit, when the
measured value exceeds the limit, the value will be replaced by the (high or low) limit value.
This command can be applied only for AAM10 module.
Syntax:
PVLMT=No
PVLMT=10 90
Parameters:
• No
Do not set limits to measurement.
• <Limit values>
The high and low limit values (%) for measurement can be set as follows:
<Low Limit>䉭<High Limit> 䉭: Space
Be noted that if the IOP detection level is beyond this range, the IOP will not be de-
tected.
● TSHUT (Tight Shut Output Value) : PFCS/LFCS2/LFCS/SFCS

This command set a value as a tight-shut output. This command can be applied only for
AAM50 module.
Syntax:
TSHUT=No
TSHUT=0.00125
Parameters:
• No
Do not set a tight-shut value (default). In this case the IOM tight-shut output value
(1.25 mA) will be used.
• A Tight-Shut Value
A tight-shut value in the unit of ampere (A) can be set.

● INREV (Reverse the Input) : PFCS/LFCS2/LFCS/SFCS
This command reverses the scale (Low limit to High limit and vice versa) of analog input
signal of the I/O module.
Syntax:
INREV=No
INREV=Yes
Parameters:
• No
The scale of the signal will not be reversed (default).
• Yes
The scale of the signal will be reversed.
When Yes (Reverse the input signal) is designated, the settings in the I/O module for signal
range and IOP detection level will be reversed too. However the process signal range and
IOP detection level (High Limit > Low Limit) set on the builder are intact.
Table The default settings in I/O when Input Reversed : PFCS/LFCS2/LFCS/SFCS
Process Data Range IOP Detection Level
I/O Module
High Limit Low Limit High Limit Low Limit
AAM11
AAM11B 0 100 -6.3 106.3
AAM21 (mV input)
AAM10 0 100 -6.3 106.3
A030327E.EPS

● I/O Modules and Applicable Commands : PFCS/LFCS2/LFCS/SFCS
The applicable commands for I/O modules are different. The details are shown as follows:
Table I/O Modules and Applicable Commands : PFCS/LFCS2/LFCS/SFCS
ORBE SORG SOOP SP1 PVLMT TSHUT INREV
AAM11 Current input
Voltage input
Current input
AAM11B Voltage input
BRAIN input
Current input (Simplified)
AAM10
Voltage input (Simplified)
APM11 Pulse input
mV input
Thermocouple input
AAM21
Potentiometer input
Current output
AAM51
Voltage output
AAM50 Current output (Simplified)
A030328E.EPS
: Possible
Blank: Not possible

A3.3.2 Parameters for Multipoint Control Analog Input/Output

Each parameter to be defined for an input or output via a multipoint control analog
input/output module, is described.
• Signal
• Service comment
• Unit
• Set Details
• P&ID tag name
• Label
• IOP detection level (SIOP)
• Fallback (FBEN)
• Fallback output value
• Output open detection (OOPE)
• OOP clear (OPCLS)
• OOP output clearance time (TOPCLS)
• Dual
• Command line
■ Signal – Multipoint Control Analog I/O : PFCS/LFCS2/LFCS/SFCS

▼ Signal
The signal direction setting is fixed; “IN” for an odd-numbered terminal, “OUT” for an even-
numbered terminal.
■ Service Comment – Multipoint Control Analog I/O : PFCS/LFCS2/LFCS/

SFCS
▼ Service Comment
A service comment of up to 40 characters can be defined in the IOM Builder.
A character string consisting of up to 40 alphanumeric or 20 double-byte characters can be
entered.
The setting is optional.
■ Range – Multipoint Control Analog I/O : PFCS/LFCS2/LFCS/SFCS

The high and low limits of the terminal’s measurement range are fixed as follows.
• High limit: 5 for an odd-numbered terminal
20 for an even-numbered terminal
• Low limit: 1 for an odd-numbered terminal
4 for an even-numbered terminal

■ Unit – Multipoint Control Analog I/O : PFCS/LFCS2/LFCS/SFCS
▼ Unit
The symbol of the unit used for the range is fixed; it is “V” for an odd-numbered terminal,
and “mA” for an even-numbered terminal.
■ Set Details – Multipoint Control Analog I/O : PFCS/LFCS2/LFCS/SFCS

▼ Set Details
The details setting, which determines whether to enable reverse output for a multipoint
control analog input/output module, is defined in the IOM Builder.
The setting can be made for even-numbered terminals only, and is a selection between
“Direct output” or “Reverse output.” The default setting is “Direct output.” The setting for odd-
numbered terminals is always blank.
SEE ALSO
version”
■ P&ID Tag Name – Multipoint Control Analog I/O : PFCS/LFCS2/LFCS/

SFCS
▼ P&ID Tag Name
A P&ID tag name of up to 16 characters can be specified in the IOM Builder.
■ Label – Multipoint Control Analog I/O : PFCS/LFCS2/LFCS/SFCS

▼ Label
A user-defined label of up to 16 characters (as the name of the function block’s input/output
terminal) can be specified in the IOM Builder.
%%Mnnnnnnnnnnnnn
Where
%%: Always %%
nnnnnnnnnnnnn: Up to 13 alphanumeric characters
The setting is optional, and can be omitted.

■ IOP Detection Level (SIOP) – Multipoint Control Analog I/O :
The IOP detection level can be specified on IOM Builder. Choosing [Tools] - [Set Details] on
the IOM builder, [Detect IOP] check box becomes available.
The SIOP can be set for odd-numbered terminals only.
■ High-Limit Detection Level (HIIOP) – Multipoint Control Analog I/O :

▼ High Limit
The high-limit detection level for the input open alarm can be specified to a desired value of
up to seven digits within the range of -1000.0 to 1000.0 (in %), in the IOM Builder. The
default setting is +106.3. Do not set a value smaller than the LOIOP setting, as this will
result in an error.
The HIIOP can be set for odd-numbered terminals and only when SIOP is set to “Enabled.”
■ Low-Limit Detection Level (LOIOP) – Multipoint Control Analog I/O :

▼ Low Limit
The low-limit detection level for the input open alarm can be specified to a desired value of
up to seven digits within the range of -1000.0 to 1000.0 (in %), in the IOM Builder. The
default setting is -6.3. Do not set a value larger than the HIIOP setting, as this will result in
an error.
The LOIOP can be set for odd-numbered terminals and only when SIOP is set to “Enabled.”
■ Fallback (FBEN) – Multipoint Control Analog I/O : PFCS/LFCS2/LFCS/

SFCS
▼ Fallback – Maintain Current Value/Output
The fallback function can be specified for even-numbered terminals, and is set up using the
IOM Builder and property sheet for the Input/Output Module.
Choosing [Tools] - [Set Details] on the IOM Builder, [Maintain Current Value] and [Output
Value] radio buttons become available. The default setting is [Maintain Current Value].
If you select [Output Value] in the IOM Builder, set the fallback output value on the property
sheet for the Input/Output Module.
■ Fallback Output Value (FBOUT) – Multipoint Control Analog I/O :

▼ Fallback Output Value
The fallback output value can be defined on IOM property sheet.
The range is -17.1875 to 112.5 (unit: %).
The default setting is -17.1875%.

■ Output Open Detection (OOPE) – Multipoint Control Analog I/O :
▼ Detect OOP
The output open detection may be specified on IOM property sheet. Choosing [Set Details]
tab on the IOM property sheet, [Detect OOP] check box becomes available.
■ OOP Clear (OPCLS) – Multipoint Control Analog I/O : PFCS/LFCS2/LFCS/

SFCS
▼ OOP Clear
The item [OOP Clear] may be checked on IOM property sheet. Choosing [Set Details] tab
on the IOM property sheet, [OOP Clear] check box becomes available.
■ OOP Clearance Time (TOPCLS) – Multipoint Control Analog I/O :

▼ Clear Time
after OOP occurred.
OOP output clear time may be set on the IOM property sheet.
(unit: seconds).
■ Dual – Multipoint Control Analog I/O : PFCS/LFCS2/LFCS/SFCS

▼ Duplicate Next Card – Multi-point Control Analog I/O
The dual redundant function with the adjacent IOM may be specified on IOM property
sheet.
Choosing [Type and Position] tab on IOM property sheet, [Duplicate Next Card] check box
becomes available.
The default setting is “Not checked”.
SEE ALSO
For more information about IOM dual-redundant configuration, see the following:
“● Dual-Redundant Multi-Point Analog Output : PFCS/LFCS2/LFCS/SFCS” in “■ Data Setting with
Respect to Dual-Redundant Output ¡ £” in chapter C2.1, “Data Connection”

■ Command Line – Multipoint Control Analog I/O : PFCS/LFCS2/LFCS/
SFCS
▼ Command
IMPORTANT
Command scripts can be entered on IOM property sheet.

The command scripts for multipoint control analog I/O module (AMC80) are shown as
follows:
Table Command Scripts may be Applied for Multipoint Control Analog I/O Modules : PFCS/
LFCS2/LFCS/SFCS

ORBE Readback the output (*1) Yes Yes/No
A030329E.EPS
*1: Can be changed online, AMC80 will not stop.

This command set the module to readback the output, if the discrepancy is too large, the
I/O module changes to FAIL status.
Syntax:
ORBE=Yes
ORBE=No
Parameters:
• Yes
• No

A3.3.3 Parameters for Multiplexer and Multiplexer (Connector

Type) Inputs/Outputs
Description of each parameter to be defined for IOMs classified as multiplexer
inputs/outputs is given below.
• Conversion
• Service comment
• Unit
• Set Details
• P&ID tag name
• Label
• IOP detection level (SIOP)
• Fallback (FBEN)
• Fallback output value (FBOUT)
• Output open detection (OOPE)
• Burnout detection
• OOP clearance time (TOPCLS)
• Cold junction compensation (RJCD)
• Command line

■ Signal Conversion – Multiplexer and Multiplexer (Connector Type) I/O :
▼ Conversion
This parameter is defined in the IOM Builder.
The selection list varies with the IOM type.
Table Selection Lists and Default Values for Signal Conversion : PFCS/LFCS2/LFCS/SFCS
Signal conversion
IOM type
Voltage input (AMM12T) No conversion No conversion
mV input (AMM22M) No conversion No conversion
Type K
Type E
Type T
Type J
Thermocouple input (AMM22T) Type K
Type R
Type S
Type B
Type N
Resistance temperature detector input PT100

PT100
(AMM32T) JPT100
Current input (AMM42T) No conversion No conversion
Current output (AMM52T) No conversion No conversion
Connector Type Voltage Input (AMM12C) No conversion No conversion
Connector Type mV Input (AMM22C) No conversion No conversion
Connector Type Resistance Temperature PT100

PT100
Detector Input (AMM32C) JPT100
Type K
Type E
Type T
Type J
Connector Type Thermocouple mV Input Type K
(AMM25C) Type R
Type S
Type B
Type N
Connector Type Thermocouple mV Input
Reference Temperature Reference Temperature
(AMM25C): Channel 16 only
A030330E.EPS

■ Service Comment – Multiplexer and Multiplexer (Connector Type) I/O :
▼ Service Comment
This parameter is defined in the IOM Builder.
A character string consisting of up to 40 alphanumeric or 20 double-byte characters can be
entered.
The service comment setting is optional and can be left as blank.

■ Range Low/High Limit – Multiplexer and Multiplexer (Connector Type) I/O
: PFCS/LFCS2/LFCS/SFCS
The high-limit and low-limit of the terminal measurement range are defined in the IOM
Builder.
Values which can be selected as the high-limit and low-limit vary with the IOM type and
signal conversion type. The high-limit and low-limit selection list and default value for each
IOM type are shown in the table below.
Voltage input (AMM12T) No conversion V -10 to +10 1 -10 to +10 5
mV input (AMM22M) No conversion mA -100 to 100 -100 -100 to 100 100
Thermocouple input (AMM22T)
Selection Default Selection Default
IOM type Signal Conversion Unit list Value list Value
A030331E.EPS
Note: The high and low limits of the range of a thermocouple input (AMM22T) are automatically displayed when the unit of
range is selected.

Table Low/High Limit Selection Lists and Default Values for Measurement Range (2/3) :
Signal
IOM type Unit Selection Default Selection Default
Conversion
Resistance temperature detector input K (Kelvin) 100 (fixed) 100 1100 (fixed) 1100
(AMM32T) C (Celsius) -200 (fixed) -200 500 (fixed) 500
Current input (AMM42T) No conversion mA 4 (fixed) 4 20 (fixed) 20
Current output (AMM52T) No conversion mA 4 (fixed) 4 20 (fixed) 20
Connector Type Voltage Input (AMM12C) No conversion V -10 to +10 1 -10 to +10 5
Connector Type mV Input (AMM22C) No conversion mV -100 to +100 -100 -100 to +100 100
Connector Type Resistance K (Kelvin) 100 (fixed) 100 1100 (fixed) 1100
Temperature Detector Input (AMM32C) C (Celsius) -200 (fixed) -200 500 (fixed) 500
Connector Type Thermocouple K (Kelvin) 200 (fixed) 200 1000 (fixed) 1000
mV Input (AMM25C) C (Celsius) 0 (fixed) 0 1600 (fixed) 1600
A030332E.EPS
Note: The high and low limits of the range of a resistance temperature detector input (AMM32T) are automatically displayed
when the unit is selected.

Signal
IOM type Unit Selection Default Selection Default
Conversion
Connector Type Thermocouple Reference
F (Fahrenheit) 30 (fixed) 30 120 (fixed) 120
mV Input (AMM25C): Channel 16 only Temperature
A030333E.EPS
The high and low limits for [Voltage input], [Connector type Voltage input], and [mV input]
can be specified to a desired value of up to seven digits including the +/- sign and decimal
point.
■ Unit – Multiplexer and Multiplexer (Connector Type) I/O : PFCS/LFCS2/

LFCS/SFCS
▼ Unit, Temperature
The unit of measurement range for a Thermocouple input module (AMM22T), a Resistance
Temperature Detector input module (AMM32T) or a Connector Type Resistance Tempera-
ture Detector Input module (AMM32C) can be set on the IOM property sheet.
The unit of measurement range for multiplexer I/O module except AMM22T, AMM32T, and
AMM32C are fixed according to the category of the module.
The units for selection as well as the default settings are shown as follows.
Table Selection Lists and Default Values for Unit of Measurement Range : PFCS/LFCS2/LFCS/
SFCS
Unit
IOM type
Voltage input (AMM12T) V (fixed) V
mV input (AMM22M) mV (fixed) mV
Thermocouple input (AMM22T) deg C, deg F or K Deg C
Resistance temperature detector input (AMM32T) deg C, deg F or K Deg C
Current input (AMM42T) mA (fixed) mA
Current output (AMM52T) mA (fixed) mA
Connector Type Voltage Input (AMM12C) V (fixed) V
Connector Type mV Input (AMM22C) mV (fixed) mV
Connector Type Resistance Temperature
C, K C
Detector Input (AMM32C)
C, K C
(AMM25C)
A030334E.EPS
If a unit of measurement other than those displayed in the selection list is entered directly,
an error will occur.

■ Set Details – Multiplexer and Multiplexer (Connector Type) I/O : PFCS/
LFCS2/LFCS/SFCS
▼ Set Details
The IOM details can be defined in the IOM Builder.
Selectable items vary with the IOM type.
Table Selection Lists and Default Values for IOM Details Setting : PFCS/LFCS2/LFCS/SFCS
Details
IOM type
Voltage input (AMM12T) None None
mV input (AMM22M) None None
Thermocouple input (AMM22T) None None
Resistance temperature detector input (AMM32T) None None
Current input (AMM42T) None None
Direct output
Current output (AMM52T) Direct output
Reverse output
Connector Type Voltage Input (AMM12C) None None
Connector Type mV Input (AMM22C) None None
Connector Type Resistance Temperature
None None
Detector Input (AMM32C)
None None
(AMM25C)
A030335E.EPS
SEE ALSO
version”
■ P&ID Tag Name – Multiplexer and Multiplexer (Connector Type) I/O :

▼ P&ID Tag Name
A P&ID tag name may be defined on the IOM Builder.
The setting is optional, and the default is blank.
Up to 16 alphanumeric characters (8 double-byte characters) may be defined as P&ID tag
name.

■ User-Defined Label – Multiplexer and Multiplexer (Connector Type) I/O :
▼ Label
A user-defined label (as the name of the function block’s input/output terminal) can be
specified in the IOM Builder. The setting is optional, and the default is blank.
Up to 16 alphanumeric characters may be defined.
%%Mnnnn
Where
%%: Always %%
nnnn: Up to 13 alphanumeric characters
User-defined label can be omitted.
■ IOP Detection Level (SIOP) – Multiplexer and Multiplexer

(Connector Type) I/O : PFCS/LFCS2/LFCS/SFCS
The IOP detection level can be specified in the IOM Builder. Choosing [Tools] - [Set Details]
on the IOM Builder, [IOP Detection Level] check box becomes available.
By default, this check box is not checked, so that the default scale high detection level
(HIOP) is +106.3% and scale low detection level (LOIOP) is -6.3%.
The IOMs allowed to select SIOP are listed below.
• Voltage input (AAM12T)
• mV input (AAM22M)
• Thermocouple input (AAM22T)
• Resistance temperature detector input (AAM32T)
• Current input (AAM42T)
• Connector Type Voltage Input (AAM12C)
• Connector Type mV Input (AAM22C)
• Connector Type Resistance Temperature Detector Input (AAM32C)
• Connector Type Temperature mV Input (AAM25C) : Channels 1 to 15
IOP detection is performed all the time except for current output module AMM52T.

■ High-Limit Detection Level (HIIOP) – Multiplexer and Multiplexer
▼ High Limit
The IOP high-limit detection level can be defined in the IOM Builder.
The level can be set within a range of -1000.0 to 1000.0 (max. 5 digits, in %).
If the high-limit is set lower than the low-limit (LOIOP), an error will occur. The default is
“+106.3.”
HIIOP can be set only when SIOP is “Enabled.”
The IOMs allowed to select HIIOP are listed below.

■ Low-Limit Detection Level (LOIOP) – Multiplexer and Multiplexer
▼ Low Limit
The IOP low-limit detection level can be defined in the IOM Builder. The level can be set
within a range of -1000.0 to 1000.0 (max. 5 digits, in %).
If the lower-limit is set higher than the high-limit (HIIOP), an error will occur. The default is
“-6.3.”
LOIOP can be set only when SIOP is “Enabled.”
The IOMs allowed to select LOIOP are listed below.

■ Fallback (FBEN) – Multiplexer I/O : PFCS/LFCS2/LFCS/SFCS
▼ Specify Fallback
The fallback function is set up on the property sheet for the Input/Output Module. Choosing
[Set Details] tab on the IOM property sheet, [Fallback] check box becomes available.
• If you select “Enabled,” then select “Maintain Current Value” or “Output Data.” The
default selection when you set “Enabled” is “Maintain Current Value.”
• If “Disabled” is selected, the current value will be maintained when an abnormality
occurs in the processor unit or in the interface connected to the processor unit. How-
ever, occurrence of the abnormality will not be notified even if the processor unit or the
interface recovers from the abnormality.
Only the current output I/O module (AMM52T) can select FBEN setting.
■ Fallback Output Value (FBOUT) – Multiplexer I/O : PFCS/LFCS2/LFCS/

SFCS
A fallback output value (FBOUT) of up to five digits within the range of -17.2 to 112.5 (in %)
can be set on the property sheet for the Input/Output Module.
The default setting is -17.2%.
FBOUT can be set only when FBEN is “Enabled” and set as “Output Data.”
Only the current output I/O module (AMM52T) can select FBOUT setting.
■ Output Open Detection (OOPE) – Multiplexer I/O : PFCS/LFCS2/LFCS/

SFCS
▼ Detect OOP
Whether to enable the output open (OOP) detection is set on the property sheet for the
Input/Output Module. Choosing [Set Details] tab on the IOM property sheet, [Detect OOP]
check box becomes available.
Only the current output I/O module (AMM52T) can select OOPE setting.

■ Burnout – Multiplexer and Multiplexer (Connector Type) I/O :
▼ Specify Burnout
Whether to enable the burnout is set on the property sheet for the Input/Output Module.
Choosing [Set Details] tab on the IOM property sheet, [Burnout] check box becomes
available.
If [Burnout] is checked, the burnout type “Upscale” or “Downscale” must be selected.
The default setting is “Upscale.”
The IOMs allowed to select burnout are listed below.
• Connector Type Temperature mV Input (AAM25C)
■ OOP Clear (OPCLS) – Multiplexer I/O : PFCS/LFCS2/LFCS/SFCS

▼ OOP Clear
The item “OOP Clear” may be checked on IOM property sheet. Choosing [Set Details] tab
on the IOM property sheet, [OOP Clear] check box becomes available.
Only the current output I/O module (AMM52T) can select OPCLS setting.
■ OOP Clearance Time (TOPCLS) – Multiplexer I/O : PFCS/LFCS2/LFCS/

SFCS
after OOP occurred.
OOP output clear time may be set on the IOM property sheet.
(unit: seconds). The default setting is 4 seconds.
Only the current output I/O module (AMM52T) can select TOPCLS setting.

■ Cold Junction Compensation (RJCD) – Multiplexer (Connector Type) I/O
: PFCS/LFCS2/LFCS/SFCS
For a multiplexer (Connector Type) input/output module, cold junction compensation can be
enabled or disabled on IOM Builder. Choosing [Tools] - [Set Details] on the IOM Builder,
[Cold Junction Compensation] check box becomes available.
RJCD can be set for the terminal 1 to 15 of connector type thermocouple mV input module
(AMM25C).
■ Command Line – Multiplexer and Multiplexer (Connector Type) I/O :

▼ Command
IMPORTANT
Command scripts can be entered on IOM property sheet for each I/O module.
Command scripts can be entered on Details setting dialog box for each signal channel on
IOM Builder.
The command scripts for Multiplexer and Multiplexer (Connector Type) I/O modules
(AMM12T, AMM12C, AMM22M, AMM22C, AMM22T, AMM25C, AMM32T, AMM32C,
AMM42T, AMM52T) are shown as follows:
Table Command Scripts may be Applied for Multiplexer and Multiplexer (Connector Type) I/O
Modules : PFCS/LFCS2/LFCS/SFCS
ORBE Readback the output Yes Yes/No
Special Linearization
SP1 Table (*1) No No/(<Interpolation Code>䉭X1,Y1䉭X2,Y2䉭X3,Y3 ...)
A030346E.EPS
*1: SP1 command can not be used for AMM25C module.

䉭: Space
Table Command Scripts may be Applied for each Channel of Multiplexer and Multiplexer
(Connector Type) I/O Modules : PFCS/LFCS2/LFCS/SFCS
INREV Reverse the Input No Yes/No
A030347E.EPS

This command set the module to readback the output, if the discrepancy is too large, the I/O
module changes to FAIL status.
Syntax:
ORBE=Yes
ORBE=No
Parameters:
• Yes
• No
● SP1 (Special Linearization Table) : PFCS/LFCS2/LFCS/SFCS

A table for linearization can be specified so that signal linearization can be performed
based on this table.
Syntax:
SP1=No
SP1=(<Interpolation Code> X1,Y1 X2,Y2 X3,Y3 ...Xn,Yn)
Parameters:
• No
No special linearization table, the default linearization table in the IOM will be used
(default).
• Interpolation Code:
1: Linear interpolation
2: Quadratic interpolation
• Xn,Yn
Data for linearization. Xn stands for input value, Yn stands for output value.
The number of data ranges from 2 to 21.
The units for Xn and Yn are as follows:
Table Units for Xn and Yn : PFCS/LFCS2/LFCS/SFCS
Signal Xn Unit Yn Unit

Current Input A %
Voltage Input V %
mV Input V %
Thermocouple Input V C (Celsius)
Resistance temperature ohm C (Celsius)
detector Input
A030348E.EPS

● INREV (Reverse the Input) : PFCS/LFCS2/LFCS/SFCS
This command reverses the scale (Low limit to High limit and vice versa) of analog input
signal of the I/O module.
Syntax:
INREV=No
INREV=Yes
Parameters:
• No
The scale of the signal will not be reversed (default).
• Yes
The scale of the signal will be reversed.
When Yes (Reverse the input signal) is designated, the settings in the I/O module for signal
range and IOP detection level will be reversed too. However the process signal range and
IOP detection level (High Limit > Low Limit) set on the builder are intact.
Table The default settings in I/O when Input Reversed : PFCS/LFCS2/LFCS/SFCS
Process Data Range (%) IOP Detection Level (%)
I/O Module
High Limit Low Limit High Limit Low Limit
AMM12T/C
AMM22M/C
0 100 -6.3 106.3
AMM22T
AMM42T
A030349E.EPS
● I/O Modules and Applicable Commands : PFCS/LFCS2/LFCS/SFCS

The applicable commands for I/O modules are different. The details are shown as follows:
Table I/O Modules and Applicable Commands : PFCS/LFCS2/LFCS/SFCS
AMM12T AMM22M AMM32T

Command Apply To AMM22T AMM25C AMM42T AMM52T
AMM12C AMM22C AMM32C
ORBE Module
SP1 Module
INREV Channel
A030350E.EPS
: Possible
Blank: Not possible

A3.3.4 Parameters for Relay, Contact Terminal or Contact

Connector
Description of each parameter to be set for IOMs classified as relay, contact terminal or
contact connector are given below.
• Mode
• P&ID tag name
• Tag name
• Tag comment
• Switch position label
• Label format
• Btn1, Btn2
• Security level
• Tag mark
• Upper window
• Help
• Filter time
• Detection edge
• Fallback
• Dual
• Time-Proportioning ON/OFF pulse period
• Phasing
• Command Line
■ Point Mode – Relay, Contact Terminal, Contact Connector : LFCS2/LFCS

£
▼ Mode
The point mode of each terminal of a module can be specified in the IOM Builder.
The available selections for the point mode and the default setting vary according to the
input/output type as shown in the table below.
Table Point Mode Setting : LFCS2/LFCS £
Point mode
Input/output type
Selection list Default setting
Status output SO, PO SO
Pulse-width output PW (fixed) PW
Time-proportional on/off output PW, TP TP
A030351E.EPS
A time-proportional on/off output can be specified for an odd-numbered terminal of a

module. When user set the point mode for a time-proportional on/off output, the point mode
of the next terminal number (even-numbered) is automatically set to the same.

■ P&ID Tag Name – Relay, Contact Terminal, Contact Connector :
▼ P&ID Tag Name
A P&ID tag name may be defined on the IOM Builder.
A P&ID tag name of with upto 16 alphanumeric can be specified in the IOM Builder.
The setting is optional, there is no default setting.
■ Tag Name – Relay, Contact Terminal, Contact Connector :

▼ Tag Name
A tag name may be defined on the IOM Builder.
A tag name of up to 16 alphanumeric characters can be specified in the IOM Builder.
■ Tag Comment – Relay, Contact Terminal, Contact Connector :

▼ Tag Comment
A tag comment may be defined on the IOM Builder. The setting is optional, and blank as the
default.
Up to 24 alphanumeric characters (12 double-byte characters) may be defined as tag
comment.
■ Switch Position Label – Relay, Contact Terminal, Contact Connector :

The switch position label can be specified in the IOM Builder.
It can be selected from a list in data entry area. It can also be directly typed in. Up to eight
alphanumeric characters or four double-byte characters can be used for a string of a label.
The entered string of label should be correspond to the level1 to level4. The syntax is as
follows.
<Label1>,<Lable2>,<Lable3>,<Lable4>
The labels should be separated with comma as delimiters. The default setting is
[ON,,OFF,ON].
Switch position label can be manually registered or automatically registered. This can be
specified on project property sheet.
• When Automatically Register Switch Position Label
A switch position label other than the labels in the list can be entered. The entered
label will be automatically registered after downloading (Saving) is performed.
• When Manually Register Switch Position Label
When the option is checked, if a switch position label other than the labels in the list
menu is used an error will occur during save and download.

SEE ALSO
For details of switch position label, see the following:
E8.2, “Switch Position Label”
■ Label Format – Relay, Contact Terminal, Contact Connector :

The direction of a label display, can be specified in the IOM Builder.
Set “Direct” or “Reverse.” The default is “Direct.”
SEE ALSO
For details of label display format, see the following:
“■ Label Format – Switch Position Label” in E8.2, “Switch Position Label”
■ Button 1 to 2 – Relay, Contact Terminal, Contact Connector :

The button colors can be specified in the IOM Builder.
The following shows the available selections. The default setting for each label is “R” (red).
• R (red)
• N (black)
• G (green)
• Y (yellow)
• B (blue)
• M (magenta)
• C (cyan)
• W (white)
• SB (steel blue)
• PK (pink)
• SG (spring green)
• OR (orange)
• YG (yellowish green)
• VO (violet)
• DB (deep sky blue)
• GR (gray)
SEE ALSO
For details of button colors, see the following:
“■ Button Color – Switch Position Label” in E8.2, “Switch Position Label”

■ Security Level – Relay, Contact Terminal, Contact Connector :
The security level of the module data can be defined in the IOM Builder.
Select the level from 1 to 8. The default is level 4.
■ Tag Mark – Relay, Contact Terminal, Contact Connector :

The tag mark type is specified in the IOM Builder.
The following are the available selections. The default setting is “General.”
• Important with Ack

• General
• Aux.1
• Aux.2
• Important
• General with Ack
• Auxi.1 with Ack
• Auxil.2 with Ack
■ Upper Window – Relay, Contact Terminal, Contact Connector:

The name of the window to be called up as the window upper in the hierarchy is specified in
the IOM Builder.
The window name must be 16 uppercase alphanumeric characters.
This setting is optional.
■ Help – Relay, Contact Terminal, Contact Connector :

The name of the Help message number defined by the user must be specified in the IOM
Builder. The setting is optional. The help message may be identified by assigning the help
message number a unique ID.
The entry format of the Help message number name is as follows:
HWnnnn
Where
HW: Always HW
nnnn: Help ID of four-digit number
However, the help message number can be omitted.

■ Filter Time – Relay, Contact Terminal, Contact Connector :
▼ Filter Time
Chattering will occur as shown below during contact input.
ON
Chattering
OFF
Transition point
A030352E.EPS
Figure Contact Input Chattering : PFCS/LFCS2/LFCS/SFCS
Chattering may cause a malfunction of the system. To prevent malfunction, a filter time
must be defined. The chattering noise with the time-span shorter than the specified filter
time can be filtered out.
In the property sheet for the Input/Output Module, select the filter time from “0”, “20”, “40”,
“60”, or “100” (ms). The default is “0”.
The IOMs allowed to define filter time are listed below.
• Status input
• Relay status input
■ Detection Edge – Relay, Contact Terminal, Contact Connector :

▼ Detection Edge
Whether to detect a change from OFF to ON or from ON to OFF for a pushbutton input, is
set on the property sheet for the Input/Output Module.
The detection edge can be selected from the following choices. The default setting is OFF.
• ON: Detection of OFF to ON edge
• OFF: Detection of ON to OFF edge
• BOTH: Detection of both OFF to ON and ON to OFF edges
The IOMs allowed to define detection edge are listed below.

• Relay pushbutton input

■ Fallback – Relay, Contact Terminal, Contact Connector :
▼ Perform Fallback
The fallback function is set on the property sheet for the Input/Output Module. Choosing
[Set Details] tab on the IOM property sheet, [Perform Fallback] check box becomes avail-
able. By default, this check box is not checked.
The fallback function outputs the preset fallback value when error occurs in the processor
unit.
When the fallback function is enabled, the fallback type must be selected from the following
choices.
• All points maintain current value
When a fallback condition is detected, all the contacts hold their previous ON or OFF
status.
• All points turn off
Turn OFF all the contacts.
The IOMs allowed to define fallback are listed below.

• Status output
• Relay output
■ Dual – Relay, Contact Terminal, Contact Connector : PFCS/LFCS2/LFCS/

SFCS
▼ Duplicate Next Card – Relay, Contact Terminal, Contact Connector
The dual redundant function with the adjacent IOM can be defined in the IOM property
sheet. Choosing [Type and Position] tab on the IOM property sheet, [Duplicate Next Card]
check box becomes available.
The IOMs allowed to be defined dual redundant are listed below.
• Status input
• Status output
SEE ALSO
For details on I/O Module dual redundant specification and connection, see the followings in chapter
C2.1, “Data Connection”:
“● Dual-Redundant Contact Input ¡ £” in “■ Data Reference with Respect to Dual-Redundant Input
¡ £”
“● Dual-Redundant Contact Output ¡ £” in “■ Data Setting with Respect to Dual-Redundant Output
¡ £”

■ Time-Proportioning ON/OFF Pulse Period – Relay, Contact Terminal,
Contact Connector : LFCS2/LFCS £
▼ Time-Proportioning ON/OFF Pulse
When using the Time-Proportioning ON/OFF Output Module of the LFCS2 or LFCS, set a
Time-Proportioning ON/OFF Pulse Period between 0 and 300 (seconds) on the IOM
Builder. The default is 10 seconds.
■ Phasing Offset – Relay, Contact Terminal, Contact Connector : LFCS2/

LFCS £
▼ Phasing
When using the Time-Proportioning ON/OFF Output Module of the LFCS2 or LFCS, set an
Phasing between 0 and 300 (seconds) on the IOM Builder. The Phasing is time setting to
define the phase of ON/OFF period for each output when using multiple Time-Proportion-
ing ON/OFF outputs in the same module. The default is 0.1 (terminal number-1) seconds.

■ Command Line – Relay, Contact Terminal, Contact Connector : LFCS2/
LFCS £
▼ Command
IMPORTANT
Command scripts can be entered on property sheet of I/O modules.

The command scripts for Relay I/O modules (ADM15R, ADM55R), Contact Terminal I/O
modules (ADM11T, ADM12T, ADM51T, ADM52T) and Contact Connector I/O modules
(AMD11C, ADM12C, ADM51C, ADM52C) are shown as follows:
Table Command Scripts may be Applied for Relay, Contact Terminal, Contact Connector : LFCS2/
LFCS £
Pulse width (Time) of
PW 1.00 (sec.) 0.00 to1.00 (sec.)
Pulse Output
A030357E.EPS
● PW (Pulse Width Output) : LFCS2/LFCS £

This command sets the time of the pulse width when a output is designated as pulse type
output for Point Mode (PO) setting item.
Syntax:
PW=1.00
Parameters:
• Time
The pulse width can be specified for pulse output is from 0.00 to 10.00 second. This is
valid only for LFCS2/LFCS.
● I/O Modules and Applicable Commands : LFCS2/LFCS £

The command applicability for I/O each type of modules are shown as follows:
Table I/O Modules and Applicable Commands : LFCS2/LFCS £
ADM15R ADM55R
ADM12T ADM52T
Command Apply To ADM11T ADM51T
ADM12C ADM52C
ADM11C ADM51C
PW Module
A030358E.EPS
: Possible
Blank: Not possible

<A3.4 Configuring Process I/O of KFCS2 and KFCS> A3-82
A3.4 Configuring Process I/O of KFCS2 and KFCS

In order to perform process input/output, it is necessary to define process input/
output on System View or IOM Builder.
■ Categories of I/O Modules : KFCS2/KFCS £

▼ IOM Type – Category, IOM Type – Type
The items to be set by the process input/output definition vary depending on the I/O module
type. The following shows the categories and types of I/O modules, and the corresponding
I/O module names.
● FIO Analog Input/Output : KFCS2/KFCS £

FIO (Field Network) Analog I/O modules are connected via ESB bus.
The following table lists the category and types of FIO Analog I/O modules:
Table Category of FIO Analog I/O Modules (1/2) : KFCS2/KFCS £
Category Type Model
16-channel current input AAI141-S
16-channel current input, isolated AAI143-S
8-channel current input, isolated ASI133-S
8-channel current input, isolated channels AAI135-S
16-channel voltage input AAV141-S
16-channel voltage input (-10 to 10 V) AAV142-S
16-channel voltage input, isolated AAV144-S
16-channel voltage input (-10 to 10 V), isolated AAV144-S
Analog input 16-channel thermocouple/mV input, isolated AAT141-S
16-channel thermocouple/mV input, isolated AST143-S
16-channel thermocouple/mV input, isolated channels AAT145-S
15-channel thermocouple input, isolated channels (MX compatible) AAT145-S
12-channel RTD input, isolated AAR181-S
8-channel RTD/POT input, isolated ASR133-S
16-channel RTD/POT input, isolated channels AAR145-S
8-channel pulse train input AAP135-S
16-channel Pulse Input Module (PM1 Compatible) AAP149-S
8-channel current input, 8-channel current output AAI841-S
8-channel voltage input, 8-channel current output AAB841-S
Analog
input/output 8-channel voltage input, 8-channel current output
AAB841-S
(MAC2 compatible terminal placement)
4-channel current input, 4-channel current output, isolated channels AAI835-S
16-channel voltage output (-10 to 10 V) AAV542-S
16-channel voltage output (-10 to 10 V), isolated AAV544-S
Analog output
8-channel current output, isolated ASI533-S
16-channel current output, isolated AAI543-S
Category Type Model
A030401E.EPS

Table Category of FIO Analog I/O Modules (2/2) : KFCS2/KFCS £
Category Type Model
16-channel current input AAI141-H
16-channel current input, isolated, HART AAI143-H
8-channel current input, isolated, HART ASI133-H
Analog
input/output 8-channel current input, isolate channels AAI135-H
(HART 8-channel current input, 8-channel current output AAI841-H
Compliant)
4-channel current input, 4-channel current output, isolate channels AAI835-H
8-channel current output, isolated, HART ASI533-H
16-channel current output, isolated, HART AAI543-H
A030426E.EPS

● FIO Contact Input/Output : KFCS2/KFCS £
FIO (Field Network) contact I/O modules are connected via ESB bus.
The following table lists the types of FIO contact I/O modules:
Table Category of FIO Contact I/O Modules : KFCS2/KFCS £
Category Type Model No. of signal channels
32-channel status input for single ADV157-S 32-channel
32-channel status input ADV151-P 32-channel
64-channel status input ADV161-P 64-channel
Status input 16-channel status input 100V AC ADV141-P 16-channel
16-channel status input 200V AC ADV142-P 16-channel
16-channel status input ASD143-P 16-channel
32-channel SOE status input (*1) ADV151-E 32-channel
32-channel pushbutton input ADV151-P 32-channel
16-channel pushbutton input 100V AC ADV141-P 16-channel
Pushbutton input
16-channel pushbutton input 200V AC ADV142-P 16-channel
16-channel pushbutton input ASD143-P 16-channel
Status/ 32-channel pushbutton input,
32-channel status, 32-channel pushbutton input ADV161-P
pushbutton input 32-channel status input
32-channel status output for single ADV557-S 32-channel
32-channel status output ADV551-P 32-channel
Status output 64-channel status output ADV561-P 64-channel
16-channel status relay output ADR541-P 16-channel
8-channel status output ASD533-S 8-channel
Pulse 32-channel pulse width output ADV551-P 32-channel
width output 16-channel pulse width relay output ADR541-P 16-channel
32-channel status output,
32-channel status, 32-channel pulse width output ADV561-P
32-channel pulse width output
Status/pulse 32-channel status/pulse width output ADV551-P 32-channel
width output
64-channel status/pulse width output ADV561-P 64-channel
16-channel status/pulse width output relay output ADR541-P 16-channel
Status input/ 16-channel status input,
16-channel status input/16-channel status output ADV851-S
status output 16-channel status output
ST2 compatible (16-channel status input, 16-channel input,
ADV859-P
16-channel status/pulse width output) 16-channel output
ST3 compatible (32-channel status input) ADV159-P 32-channel input
ST3 compatible (32-channel pushbutton input) ADV159-P 32-channel input
ST compatible
ST4 compatible (32-channel status/pulse width output) ADV559-P 32-channel output
(included power)
ST5 compatible (32-channel status input, 32-channel input,
ADV869-P
32-channel status/pulse width output) 32-channel output
ST6 compatible (64-channel status input) ADV169-P 64-channel input
ST7 compatible (64-channel status/pulse width output) ADV569-P 64-channel output
A030402E.EPS
*1: Can be applied only in the field control units that support dual-redundant configuration (AFS30D, AFS40D, AFG30D
and AFG40D).

■ Definition of Process Input/Output : KFCS2/KFCS £
The following lists the setting items used for process input/output:
Table Setting Items Used for Process Input/Output : KFCS2/KFCS £
FIO analog input/output FIO contact input/output
Signal conversion Mode
Service comment P&ID tag name
Lower and upper limit values of the range (*1) Tag name
Unit symbol of the range (T_UNIT) (*1) Tag comment
Details setting (*1) Switch position label
P&ID tag name (*1) Label format
Label (*1) Btn1, Btn2
IOP detection (IOPE) Functional restriction
Higher detection level (HIIOP) Tag mark (*1)
Lower detection level (LOIOP) Upper window (*1)
Fallback (FBEN) Help (*1)
Time-proportioning ON/OFF pulse cycle
Fallback output value (FBOUT)
(PP)
Cold junction compensation specification (RJCD) Phasing (OF)
Pulse input filter (PLFL) Filter setting (SIN_CTL)
Transmitter power supply (VTTSEL) Detection edge (PEG)
OOP detection (OOPE) Fallback (FBK)
Burnout specification (BOEN) Dual
Fallback (FBEN) Command line
OOP clear (OPCLS)
Cold junction compensation correction setting
(RJCSEL)
Dual
Command line input 1
Command line input 2
Connection Point
Data Number
Node Address
A030403E.EPS
*1: Indicates detail setting items.

A3.4.1 Parameters for FIO Analog Inputs/Outputs

The following explains the setting items of the I/O module that are classified as FIO
analog input/output:
• Conversion
• Service comment
• Range Low/High Limit (*1)
• Unit (T_UNIT) (*1)
• Details setting (*1)
• P&ID tag name (*1)
• Label (*1)
• IOP detection (IOPE)
• Fallback (FBEN)
• Fallback output value (FBOUT)
• Cold junction compensation (RJCD)
• Pulse input filter (PLFL)
• Transmitter power supply (VTTSEL)
• OOP detection (OOPE)
• Burnout specification (BOEN)
• Cold junction compensation correction setting (RJCSEL)
• Dual
• Command line input 1
• Command line input 2
• Connection Point (*2)
• Data Number (*2)
• Node Address (*2)
*2: Indicates HART variable settings.

■ Signal Conversion – FIO Analog Input/Output : KFCS2/KFCS £
▼ Conversion
The type of the signal conversion is set on IOM Builder.
The selection list of the signal conversion varies depending on the type of the I/O module.
The following lists the selection list and default values of the signal conversion:
Table Selection List and Default Values of the Signal Conversion (1/3) : KFCS2/KFCS £
Signal conversion
IOM type Terminal Direction
16-channel current input (AAI141-S)
16-channel current input, isolated (AAI143-S)
All
8-channel current input, isolated (ASI133-S) Input No conversion No conversion
channels
8-channel current input, isolated channels
(AAI135-S)
All
16-channel voltage input (AAV141-S) Input No conversion No conversion
channels
All
16-channel voltage input (-10 to 10V) (AAV142-S) Input No conversion No conversion
channels
All
16-channel voltage input, isolated (AAV144-S) Input No conversion No conversion
channels
16-channel voltage input (-10 to 10V), isolated All
Input No conversion No conversion
(AAV144-S) channels
Type K
16-channel thermocouple/mV input, isolated Type E
(AAT141-S)
Type T
Type J
16-channel thermocouple/mV input, isolated All Type R
Input Type K
(AST143-S) channels Type S
Type B
Type N
16-channel thermocouple/mV input, isolated
channels (AAT145-S) mV input (%)
TC input (V)
Type K
Type E
Type T
Type J
15-channel thermocouple input, 1 to 15 Input Type R Type K
isolated channels (MX compatible) Type S
(AAT145-S)
Type B
Type N
TC input (V)
Reference junction Reference junction
16 Input
temperature temperature
PT100
12-channel RTD input, isolated
1 to 12 Input JPT100 PT100
(AAR181-S)
RTD input (ohm)
Signal conversion
A030404E.EPS

Signal conversion
PT100
JPT100
PT50
PT200
PT500
PT1000
All Ni100
8-Channel RTD/POT Input, Isolated (ASR133-S) Input PT100
channels Ni120
Ni200
Potentiometer
RTD input 0 to 650 (ohm)
PT100
16-channel RTD/POT input, isolated All JPT100
Input PT100
channels (AAR145-S) channels Potentiometer
RTD input (ohm)
All
8-channel pulse train input (AAP135-S) Input No conversion No conversion
channels
16-channel pulse input All
(PM1 Compatible) (AAP149-S) channels
8-channel current input, 8-channel 1 to 8 Input No conversion No conversion
current output (AAI841-S) 9 to 16 Output No conversion No conversion
8-channel voltage input, 8-channel 1 to 8 Input No conversion No conversion
current output (AAB841-S) 9 to 16 Output No conversion No conversion
8-channel voltage input, 8-channel current output Odd Input No conversion No conversion
(MAC2 compatible terminal placement)
(AAB841-S) Even Output No conversion No conversion
4-channel current input and 4-chnnel current 1 to 4 Input No conversion No conversion

output; isolated channels (AAI835-S) 5 to 8 Output No conversion No conversion
16-channel voltage output (-10 to 10 V) (AAV542-S) 1 to 16 Output No conversion No conversion
16-channel voltage output (-10 to 10 V), isolated All
Output No conversion No conversion
(AAV544-S) channels
All
8-channel current output, isolated (ASI533-S) Output No conversion No conversion
channels
All
16-channel current output, isolated (AAI543-S) Output No conversion No conversion
channels
All
16-channel current input, HART (AAI141-H) Input No conversion No conversion
channels
16-channel current input, isolated, HART All
(AAI143-H) channels
8-channel current input, isolated, HART All
(ASI133-H) channels
Signal conversion
A030405E.EPS

Signal conversion
8-channel current input, isolate channels, All
HART (AAI135-H) channels
8-channel current input, 8-channelcurrent output, 1 to 8 Input No conversion No conversion
HART (AAI841-H) 9 to 16 Output No conversion No conversion
4-channel current input, 4-channelcurrent output, 1 to 4 Input No conversion No conversion

isolate channels, HART (AAI835-H) 5 to 8 Output No conversion No conversion
8-channel current output, isolated, HART All
(ASI533-H) channels
16-channel current output, isolated, HART All
(AAI543-H) channels
A030427E.EPS
In case of the thermocouple/mV input or RTD/POT input, when the signal conversion is
changed, the upper and lower limit values of the range will be changed to the recom-
mended values.
■ Service Comment – FIO Analog Input/Output : KFCS2/KFCS £

▼ Service Comment
The service comment is set with IOM Builder.
Nothing is set by default.
A string of up to 40 alphanumeric characters or 20 double-byte characters can be entered.
The setting of the service comment may be omitted.

■ Range Low/High Limit – FIO Analog Input/Output : KFCS2/KFCS £
The lower and upper limit values of the measurement range of the terminal is set with IOM
Builder.
The values that can be selected as the lower and upper limits of the range vary depending
on the I/O module type, signal conversion type, and terminal position.
The following shows the selection list and default values of the lower and upper limit val-
ues:
Table Selection List and Default Values of the Lower and Upper Limit Values (1/6) : KFCS2/KFCS
£
Lower limit value Upper limit value
Signal Unit
IOM type Terminal Direction Selection Default Selection Default
conversion (*1)
list value list value
16-channel current input
(AAI141-S)
16-channel current input,
isolated (AAI143-S) All No
Input mA Fixed at 4 4 Fixed at 20 20
8-channel current input, channels conversion
isolated (ASI133-S)
isolated channels (AAI135-S)
16-channel voltage input All No
Input V Fixed at 1 1 Fixed at 5 5
(AAV141-S) channels conversion
Input V -10 to 10 1 -10 to 10 5
(-10 to 10V) (AAV142-S) channels conversion
16-channel voltage input, All No
Input V Fixed at 1 1 Fixed at 5 5
isolated (AAV144-S) channels conversion
16-channel voltage
All No
input (-10 to 10V), Input V -10 to 10 -10 -10 to 10 10
channels conversion
isolated (AAV144-S)
A030406E.EPS
*1: C stands for Celsius, F stands for Fahrenheit and K stands for Kelvin.

Table Selection List and Default Values of the Lower and Upper Limit Values (2/6) : KFCS2/
KFCS £
Signal Unit
conversion (*1)
C Fixed at -200 -200 Fixed at 1200 1200
Type K F Fixed at -300 -300 Fixed at 2200 2200
K Fixed at 100 100 Fixed at 1500 1500
16-channel C Fixed at -200 -200 Fixed at 900 900
thermocouple/mV input, Type E F Fixed at -300 -300 Fixed at 1700 1700
isolated (AAT141-S)
Type T F Fixed at -300 -300 Fixed at 650 650
Type J F Fixed at -40 -40 Fixed at 1400 1400
16-channel
thermocouple/mV input, All C Fixed at 0 0 Fixed at 1600 1600
Input
isolated (AST143-S) channels Type R F Fixed at 0 0 Fixed at 2900 2900
C Fixed at 0 0 Fixed at 1600 1600
Type S F Fixed at 0 0 Fixed at 2900 2900
Type B F Fixed at 1100 1100 Fixed at 3100 3100
16-channel K Fixed at 900 900 Fixed at 2000 2000
thermocouple/mV input,
isolated channels
(AAT145-S) Type N F Fixed at -300 -300 Fixed at 2200 2200
mV input (%) mV -100 to 150 -100 -100 to 150 100
TC Input (V) mV Fixed at -20 -20 Fixed at 80 80
Signal Unit
conversion (*1)
A030428E.EPS

£
Unit Lower limit value Upper limit value

Signal
IOM type Terminal Direction symbol Selection Default Selection Default
conversion
(*1) list value list value
Type K F Fixed at -300 -300 Fixed at 2200 2200
Type E F Fixed at -300 -300 Fixed at 1700 1700
Type T F Fixed at -300 -300 Fixed at 650 650
Type J F Fixed at -40 -40 Fixed at 1400 1400
15-channel 1 to 15 Input C Fixed at 0 0 Fixed at 1600 1600
thermocouple input, Type R F Fixed at 0 0 Fixed at 2900 2900
isolated channels
(MX compatible) K Fixed at 250 250 Fixed at 1900 1900
(AAT145-S) C Fixed at 0 0 Fixed at 1600 1600
Type S F Fixed at 0 0 Fixed at 2900 2900
Type B F Fixed at 1100 1100 Fixed at 3100 3100
Type N F Fixed at -300 -300 Fixed at 2200 2200
TC Input (V) mV Fixed at -20 -20 Fixed at 80 80
Reference
16 Input junction F Fixed at 30 30 Fixed at 120 120
temperature K 270 Fixed at 320
Fixed at 270 320
PT100 F Fixed at -300 -300 Fixed at 1500 1500
12-channel RTD
input, isolated 1 to 12 Input
(AAR181-S) JPT100 F Fixed at -300 -300 Fixed at 900 900
RTD Input
ohm Fixed at 0 0 Fixed at 400 400
(ohm)

Signal
conversion
A030407E.EPS

£

Signal
conversion
JPT100 F Fixed at -300 -300 Fixed at 900 900
8-channel RTD/POT PT1000 F Fixed at -300 -300 Fixed at 1500 1500
All
input, isolated Input K Fixed at 100 100 Fixed at 1100 1100
Channels
(ASR133-S)
Ni100 F Fixed at -80 -80 Fixed at 500 500
Potentiometer ohm 0 to 10000 100 0 to 10000 2000
PTD
0 to 650
PTD
0 to 1300
PTD
0 to 2600
PTD
0 to 5400
Signal
conversion
A030429E.EPS

£

Signal
conversion
16-channel RTD/POT input,
All JPT100 F Fixed at -300 -300 Fixed at 900 900
isolated channels Input
channels
(AAR145-S) K Fixed at 100 100 Fixed at 750 750
Potentiometer ohm 0 to 10000 100 0 to 10000 2000
RTD Input
(ohm)
8-channel pulse train input All No
Input Fixed at 0 0 Fixed at 0 0
(AAP135-S) channels conversion
16-channel pulse input
All No
(PM1 Compatible) Input Fixed at 0 0 Fixed at 0 0
channels conversion
(AAP149-S)
No
8-channel current input, 1 to 8 Input mA Fixed at 4 4 Fixed at 20 20
conversion
8-channel current output
(AAI841-S) No
9 to 16 Output mA Fixed at 4 4 Fixed at 20 20
conversion
No
8-channel voltage input, 1 to 8 Input V Fixed at 1 1 Fixed at 5 5
conversion
(AAB841-S) No
conversion
8-channel voltage input, No
Odd Input V Fixed at 1 1 Fixed at 5 5
8-channel current output conversion
(MAC2 compatible terminal No
placement) (AAB841-S) Even Output mA Fixed at 4 4 Fixed at 20 20
conversion
4-channel current input, No
1 to 4 Input mA Fixed at 4 0 Fixed at 20 20
4-channel current output, conversion
isolated channels No
(AAI835-S) 5 to 8 Output mA Fixed at 4 0 Fixed at 20 20
conversion
16-channel voltage output No
1 to 16 Output V -10 to 10 1 -10 to 10 5
(-10 to 10V) (AAV542-S) conversion
16-channel voltage output
All No
(-10 to 10V), isolated Output V -10 to 10 1 -10 to 10 5
channels conversion
(AAV544-S)
8-channel current output, All No
Output mA Fixed at 4 0 Fixed at 20 20
isolated (ASI533-S) channels conversion
isolated (AAI543-S) channels conversion
16-channel current input, All No
HART (AAI141-H) channels conversion
isolated, HART (AAI143-H) channels conversion
isolated, HART (ASI133-H) channels conversion
Signal
conversion
A030408E.EPS

£
Signal Unit
conversion symbol
All No
Isolate channels, HART Input mA Fixed at 4 4 Fixed at 20 20
channels conversion
(AAI135-H)
No
8-channel current input, 1 to 8 Input mA Fixed at 4 4 Fixed at 20 20
conversion
8-channel current output,
HART (AAI841-H) No
conversion
1 to 4 Input mA Fixed at 4 4 Fixed at 20 20
Isolate channels, HART No
(AAI835-H) 5 to 8 Output mA Fixed at 4 4 Fixed at 20 20
conversion
A030430E.EPS

■ Unit (T_UNIT) – FIO Analog Input/Output : KFCS2/KFCS £
▼ Unit, Temperature
The unit of the range is set with the I/O module properties.
The values that can be selected as the unit symbols of the range vary depending on the I/O
module type, signal conversion type, and terminal position.
The following lists the selection list and default values of the unit of the range:
Table Selection List and Default Values of the Unit of the Range (1/3) : KFCS2/KFCS £
Signal Unit (*1)

conversion Selection list Default value
16-channel current input
(AAI141-S)
isolated (AAI143-S) All No
Input Fixed at mA mA
8-channel current input, channels conversion
isolated (ASI133-S)
8-channel current input, isolated
channels (AAI135-S)
Input Fixed at V V
(AAV141-S) channels conversion
Input Fixed at V V
(-10 to 10 V) (AAV142-S) channels conversion
16-channel voltage input, All No
Input Fixed at V V
isolated (AAV144-S) channels conversion
Input Fixed at V V
(-10 to 10 V), isolated (AAV144-S) channels conversion
Type K
16-channel thermocouple/ Type E
mV input, isolated (AAT141-S)
Type T
Type J
C, F, K C
16-channel thermocouple/mV Type R
All
input, isolated (AST143-S) Input
channels Type S
Type B
16-channel thermocouple/mV Type N
input, isolated channels
mV input (%) Fixed at mV mV
(AAT145-S)
TC input (V) mV Fixed mV
Type K
Type E
Type T
Type J
1 to 15 Input C, F, K C
Type R
15-channel thermocouple input,
isolated channels Type S
(MX compatible) (AAT145-S) Type B
Type N
TC input (V) mV Fixed mV
Reference
16 Input junction C, F, K C
temperature
A030409E.EPS
*1: The upper and lower limit values of the ranges for the thermocouple input and RTD input are automatically switched
according to the unit symbol setting.

Signal Unit (*1)

PT100
C, F, K C
12-channel RTD input, JPT100
1 to 12 Input
isolated (AAR181-S)
RTD Input
ohm Fixed ohm
(ohm)
PT100 C, F, K C
JPT100 C, F, K C
PT50 C, F, K C
PT200 C, F, K C
PT500 C, F, K C
PT1000 C, F, K C
Ni100 C, F, K C
8-channel RTD/POT input, All Ni120 C, F, K C
Input
isolated (ASR133-S) Channels Ni200 C, F, K C
Potentiometer ohm Fixed ohm
RTD
ohm Fixed ohm
0 to 650
RTD
ohm Fixed ohm
0 to 1300
RTD
ohm Fixed ohm
0 to 2600
RTD
ohm Fixed ohm
0 to 5400
PT100
C, F, K C
JPT100
16-channel RTD/POT input, All
Input POT Fixed at ohm ohm
isolated channels (AAR145-S) Channels
RTD Input
ohm Fixed ohm
(ohm)
8-channel pulse train input All No
Input Blank Blank
(AAP135-S) Channels conversion
16-channel pulse Input All No
Input Blank Blank
(PM1 Compatible) (AAP149-S) Channels conversion
No
8-channel current input, 1 to 8 Input Fixed at mA mA
conversion
(AAI841-S) No
9 to 16 Output Fixed at mA mA
conversion
No
8-channel voltage input, 1 to 8 Input Fixed at V V
conversion
(AAB841-S) No
conversion
8-channel voltage input, No

Odd Input Fixed at V V
8-channel current output conversion
(MAC2 compatible terminal No
placement) (AAB841-S) Even Output Fixed at mA mA
conversion
Signal Unit (*1)

A030410E.EPS

Signal Unit (*1)

No
conversion
isolated channels (AAI835-S) No
conversion
16-channel voltage output No
1 to 16 Output Fixed at V V
(-10 to 10V) (AAV542-S) conversion
16-channel voltage output
All No
(-10 to 10V), isolated Output Fixed at V V
channels conversion
(AAV544-S)
Output mA Fixed mA
isolated (ASI533-S) channels conversion
Output mA Fixed mA
isolated (AAI543-S) channels conversion
Input Fixed at mA mA
HART (AAI141-H) channels conversion
Input mA Fixed mA
Input mA Fixed mA
All No
isolate channels, HART Input Fixed at mA mA
channels conversion
(AAI135-H)
No
conversion
HART (AAI841-H) No
conversion
1 to 4 Input Fixed at mA mA
isolate channels, HART No
(AAI835-H) 5 to 8 Output Fixed at mA mA
conversion
Output mA Fixed mA
Output mA Fixed mA
A030431E.EPS

■ Details Setting – FIO Analog Input/Output : KFCS2/KFCS £
▼ Set Details
The details setting of the I/O module are carried out in IOM Builder.
The items that can be selected vary depending on the I/O module type.
The following lists the selection list and default values of the details of the I/O modules.
If a value other than those in the selection list is specified, an error will occur.
Table Selection List and Default Values of the Details of the I/O Modules (1/2) : KFCS2/KFCS £
Details setting
Selection list Default
(AAI143-S)
All
8-channel current input, isolated Input None None
Channels
(ASI133-S)
channels (AAI135-S)
All
16-channel voltage input (AAV141-S) Input None None
Channels
16-channel voltage input (-10 to 10 V) All
Input None None
(AAV142-S) Channels
16-channel voltage input, isolated All
Input None None
(AAV144-S) Channels
16-channel voltage input (-10 to 10 V), All
Input None None
isolated (AAV144-S) Channels
16-channel thermocouple/mV input,
isolated (AAT141-S)
16-channel thermocouple/mV input, All
Input None None
isolated (AST143-S) Channels
isolated channels (AAT145-S)
15-channel thermocouple input,
All
isolated channels Input None None
Channels
(MX compatible) (AAT145-S)
12-channel RTD input, isolated All
Input None None
(AAR181-S) Channels
8-channel RTD/POT input,isolated All
Input None None
(ASR133-S) Channels
16-channel RTD/POT input, isolated All
Input None None
channels (AAR145-S) Channels
No terminal resistor,
8-channel pulse train input All
Input terminal resistor = 200 , No terminal
(AAP135-S) Channels terminal resistor = 500 , resistor
terminal resistor = 1000
16-channel pulse input All
Input None None (*1)
(PM1 Compatible) (AAP149-S) Channels
Details setting
A030411E.EPS
*1: Always No terminal resistor.

Table Selection List and Default Values of the Details of the I/O Modules (2/2) : KFCS2/KFCS £
Details setting
1 to 8 Input None None
8-channel current output (AAI841-S) Direct output,
9 to 16 Output Direct output
Reverse output
8-channel voltage input,
8-channel current output (AAB841-S) Direct output,
Reverse output
8-channel voltage input, 8-channel Odd Input None None

current output (MAC2 compatible Direct output,
terminal placement) (AAB841-S) Even Output Direct output
Reverse output
4-channel current input, 4-channel 1 to 4 Input None None

current output, isolated channels Direct output,
(AAI835-S) 5 to 8 Output Direct output
Reverse output
16-channel voltage output Direct output,
(-10 to 10 V) (AAV542-S) Reverse output
16-channel voltage output All Direct output,
Output Direct output
(-10 to 10 V), isolated (AAV544-S) Channels Reverse output
8-channel current output, isolated All Direct output,
(ASI533-S) Channels Reverse output
16-channel current output, isolated All Direct output,
(AAI543-S) Channels Reverse output
16-channel current input, HART All
Input None None
(AAI141-H) Channels
16-channel current input, isolated, All
Input None None
HART (AAI143-H) Channels
8-channel current input, isolated, All
Input None None
HART (ASI133-H) Channels
8-channel current input, isolate All
Input None None
channels, HART (AAI135-H) Channels
8-channel current input, 8-channel
current output, HART (AAI841-H) Direct output,
Reverse output
4-channel current input, 4-channel 1 to 4 Input None None
current output, isolate channels, Direct output,
HART (AAI835-H) 5 to 8 Output Reverse output Direct output
8-channel current output, isolated, All Direct output,

HART (ASI533-H) Channels Reverse output
16-channel current output, isolated, All Direct output,
HART (AAI543-H) Channels Reverse output
A030425E.EPS
SEE ALSO
version”

■ P&ID Tag Name – FIO Analog Input/Output : KFCS2/KFCS £
▼ P&ID Tag Name
The P&ID tag name is set on IOM Builder.
A string of up to 16 alphanumeric characters or 8 double-byte characters can be entered.
The setting of the P&ID tag name may be omitted.
■ Label – FIO Analog Input/Output : KFCS2/KFCS £

▼ Label
The user-defined label is set on IOM Builder. The user-defined label can be set for termi-
nals.
Up to 16 byte alphanumeric characters can be entered.
The setting of the user-defined label may be omitted.
The following shows the specification format of the user-defined label:
%%Mnnnn
%%: Unique to the system
M: The third character must be an uppercase character (A through Z).
nnnn: The forth and subsequent characters must be within 13 characters in a combination of uppercase and
lowercase alphanumeric characters (A through Z, a through z, and 0 though 9).

■ Detect Input Open (IOPE) – FIO Analog Input/Output : KFCS2/KFCS £
▼ Detect IOP
Whether or not to detect the disconnection of input signals (IOP: input open) is set in the
details setting dialog box of IOM Builder. On the IOM builder, [Detect IOP] check box is
available.
The IOPE can only be set for the signals (terminals) of the following I/O modules:
Table Signals (Terminals) of the I/O Modules for which IOPE can be Set (1/2) : /KFCS2/KFCS £
Terminal
Type (model name) IOM type
number
16-channel current input (AAI141-S) Current input 1 to 16
16-channel current input, isolated (AAI143-S) Current input 1 to 16
8-channel current input, isolated (ASI133-S) Current input 1 to 8
8-channel current input, isolated channels (AAI135-S) Current input 1 to 8
16-channel voltage input (AAV141-S) Voltage input 1 to 16
16-channel voltage input (-10 to 10V) (AAV142-S) Voltage input 1 to 16
16-channel voltage input, isolated (AAV144-S) Voltage input 1 to 16
16-channel voltage input (-10 to 10V), isolated (AAV144-S) Voltage input 1 to 16
Thermocouple input
16-channel thermocouple/mV input, isolated (AAT141-S) mV input (%) 1 to 16
TC input (V)
Thermocouple input
16-channel thermocouple/mV input; isolated (AST143-S) mV input (%) 1 to 16
Thermocouple Input (V)
Thermocouple input
16-channel thermocouple/mV input, isolated channels mV input (%) 1 to 16
(AAT145-S)
TC input (V)
15-channel thermocouple input, isolated channels Thermocouple input

1 to 15 (*1)
(MX compatible) (AAT145-S) TC input (V)
RTD input
12-channel RTD input, isolated (AAR181-S) 1 to 12
RTD input (ohm)
RTD input
8-channel RTD/POT input, Isolated (ASR133-S) Potentiometer Input 1 to 8
RTD Input (ohm)
RTD input
16-channel RTD/POT input, isolated channels (AAR145-S) Potentiometer Input 1 to16
RTD input (ohm)
8-channel current input, 8-channel current output
Current input 1 to 8
(AAI841-S)
8-channel voltage input, 8-channel current output
Voltage input 1 to 8
(AAB841-S)
8-channel voltage input, 8-channel current output 1, 3, ..., 15
Voltage input
(MAC2 compatible terminal placement) (AAB841-S) (odd numbers)
4-channel current input, 4-channel current output,
A030412E.EPS
*1: Since the 16th point is used as the reference junction compensation input, only up to the 15th point can be used as
temperature inputs from the field.

Table Signals (Terminals) of the I/O Modules for which IOPE can be Set (2/2) : /KFCS2/KFCS £
Terminal
number
16-channel current input, HART (AAI141-H) Current input 1 to 16
16-channel current input, isolated, HART (AAI143-H) Current input 1 to 16
8-channel current input, isolated, HART (ASI133-H) Current input 1 to 8
8-channel current input, isolate channels, HART
(AAI135-H)
HART (AAI841-H)
isolate channels, HART (AAI835-H)
A030432E.EPS

■ High Limit Detection Level (HIIOP) – FIO Analog Input/Output : KFCS2/
KFCS £
▼ High Limit
The high limit detection level of the IOP is set in the details setting dialog box of IOM
Builder.
Numeric values of up to five digits can be set for the HIIOP in the range from -1000.0 to
1000.0 (unit: %). The default setting is +106.3.If a value smaller than the value set in the
LOIOP is specified, an error will occur.
The HIIOP can only be set when the check box of the IOP detection setting is checked.
The HIIOP can only be set for the signals (terminals) of the following I/O modules:
Table Signals (Terminals) of the I/O Modules for which the HIIOP can be Set (1/2) : KFCS2/KFCS
£
Terminal
number
16-channel voltage input (-10 to 10 V) (AAV142-S) Voltage input 1 to 16
16-channel voltage input (-10 to 10 V), isolated (AAV144-S) Voltage input 1 to 16
Thermocouple input
16-channel thermocouple/mV input, isolated (AAT141-S) mV input (%) 1 to 16
TC input (V)
Thermocouple input
16-channel thermocouple/mV input, isolated (AST143-S) mV input (%) 1 to 16
TC input (V)
Thermocouple input
16-channel thermocouple/mV input, isolated channels
mV input (%) 1 to 16
(AAT145-S)
TC input (V)
1 to 15 (*1)
RTD input
RTD input (ohm)
RTD input
8-channel RTD/POT input, isolated (ASR133-S) Potentiometer input 1 to 8
RTD input (ohm)
RTD input
16-channel RTD/POT input, isolated channels (AAR145-S) Potentiometer input 1 to 16
RTD input (ohm)
8-channel current input, 8-channel current output (AAI841-S) Current input 1 to 8
8-channel voltage input, 8-channel current output (AAB841-S) Voltage input 1 to 8
Voltage input
A030413E.EPS
*1: Since the 16th channel is used as the reference junction compensation input, only up to the 15th channel can be used
as temperature inputs from the field.

Table Signals (Terminals) of the I/O Modules for which the HIIOP can be Set (2/2) : KFCS2/KFCS
£
Terminal
number
8-channel current input, isolated channels, HART
(AAI135-H)
8-channel current input, 8-channel current outputm,
HART (AAI841-H)
A030433E.EPS

■ Low Limit Detection Level (LOIOP) – FIO Analog Input/Output : KFCS2/
KFCS £
▼ Low Limit
The low limit detection level of the IOP is set in the details setting dialog box of IOM Builder.
Numeric values of up to five digits can be set for the LOIOP in the range from -1000.0 to
1000.0 (unit: %). The default setting is -6.3. However the default setting for AAR181-S and
AAR145-S I/O modules is zero “0”. If a value larger than the value set in the HIIOP is
specified, an error will occur.
The LOIOP can only be set when the check box of the IOP detection setting is checked.
The LOIOP can only be set for the signals (terminals) of the following I/O modules:
Table Signals (Terminals) of the I/O Modules for which the LOIOP can be Set (1/2) : KFCS2/KFCS
£
Terminal
number
16-channel voltage input (-10 to 10 V) (AAV142-S) Voltage input 1 to 16
16-channel voltage input (-10 to 10 V), isolated
(AAV144-S)
Thermocouple input
(AAT141-S)
TC input (V)
Thermocouple input
(AST143-S)
TC input (V)
Thermocouple input
(AAT145-S)
TC input (V)
1 to 15 (*1)
RTD input
RTD input (ohm)
RTD input
8-channel RTD/POT input, isolated (ASR133-S) Potentiometer input 1 to 8
PTD input (ohm)
RTD input
16-channel RTD/POT input, isolated channels
Potentiometer input 1 to 16
(AAR145-S)
PTD input (ohm)
A030414E.EPS
*1: Since the 16th channel is used as the reference junction compensation input, only up to the 15th channel can be used

Table Signals (Terminals) of the I/O Modules for which the LOIOP can be Set (2/2) : KFCS2/KFCS
£
Terminal
number
(AAI841-S)
(AAB841-S)
Voltage input
8-channel current input, isolated, HART (ASI133-H) Current input 1 to 8
8-channel current input, isolate channels, HART
(AAI135-H)
HART (AAI841-H)
A030434E.EPS

■ Fallback (FBEN) – FIO Analog Input/Output : KFCS2/KFCS £
▼ Fallback Specification, Fallback – Maintain Current Value
Whether or not the operation of the fallback function is performed is set in the I/O module
properties. [Fallback Specification] check box is available on IOM builder.
By default, this check box is checked. If the modules are in dual-redundant configuration,
[Fallback Specification] can not be unchecked.
• If [Fallback Specification] has been checked, either “Maintain Current Value” or “Out-
put” can be specified for each terminal with IOM Builder.
• If [Fallback Specification] has not been checked, the current value is retained when an
abnormality occurs in the processor unit or in the interface with the processor unit.
However, even if the processor unit or the interface with the processor unit recovers to
the normal state, the occurrence of that error will not be notified.
If [Fallback Specification] has been checked in the I/O module properties, the fallback
output operation setting is available on the details setting dialog of IOM Builder.
Specify either “Maintain Current Value” or “Output.” The default is “Maintain Current Value.”
The FBEN can only be set for the signals (terminals) of the following I/O modules:
Table Signals (Terminals) of the I/O Modules for which the FBEN can be Set : KFCS2/KFCS £
Type (model name) IOM type Terminal number
Current output 9 to 16
(AAI841-S)
(AAB841-S)
8-channel voltage input, 8-channel current output 2,4,..16
Current output
(MAC2 compatible terminal placement) (AAB841-S) (even number)
16-channel voltage output (-10 to 10V) (AAV542-S) Voltage output 1 to 16
16-channel voltage output (-10 to 10V),
Voltage output 1 to 16
isolated (AAV544-S)
8-channel current output; Isolated (ASI533-S) Current output 1 to 8
16-channel current output; Isolated (AAI543-S) Current output 1 to 16
HART (AAI841-H)
4-channel current input, 4-channel current
output, isolate channels, HART (AAI835-H)
8-channel current output, isolated, HART (ASI533-H) Current output 1 to 8
16-channel current output, isolated, HART (AAI543-H) Current output 1 to 16
A030415E.EPS

■ Fallback Output Value (FBOUT) – FIO Analog Input/Output : KFCS2/
KFCS £
▼ Fallback – Output
The fallback output data is set in the details setting dialog box of IOM Builder.
A value in the range between -17.1875 and 112.5 (unit: %) can be set for the FBOUT. The
default setting is -17.1875.
The FBOUT can only be set when the FBEN specification is set to “Output.”
The FBOUT can only be set for the signals (terminals) of the following I/O modules:
Table Signals (Terminals) of the I/O Modules for which the FBOUT can be Set : KFCS2/KFCS £
(AAI841-S)
(AAB841-S)
8-channel voltage input, 8-channel current output 2,4,..16
Current output
(MAC2 compatible terminal placement) (AAB841-S) (even number)
16-channel voltage output (AAV542-S) Voltage output 1 to 16
16-channel voltage output (-10 to 10 V), isolated
(AAV544-S)
8-channel current output (-10 to 10 V), isolated (ASI533-S) Current output 1 to 8
16-channel current output, isolated (AAI543-S) Current output 1 to 16
output, HART (AAI841-H)
output, isolate channels, HART (AAI835-H)
8-channel current output, isolated, HART (ASI533-H) Current output 1 to 8
16-channel current output, isolated, HART (AAI543-H) Current output 1 to 16
A030416E.EPS

■ Cold Junction Compensation (RJCD) – FIO Analog Input/Output :
KFCS2/KFCS £
Whether or not the reference junction compensation is performed for thermocouple input
can be set on IOM Builder. Choosing [Tools] - [Set Details] on the IOM builder, [Cold Junc-
tion Compensation] check box becomes available.
The RJCD can only be set for the signals (terminals) of the following I/O modules:
Table Signals (Terminals) of the I/O Modules for which the RJCD can be Set : KFCS2/KFCS £
16-channel thermocouple/mV input, isolated (AAT141-S) Thermocouple input 1 to 16
16-channel thermocouple/mV input, isolated (AST143-S) Thermocouple input 1 to 16
Thermocouple input 1 to 16
(AAT145-S)
15-channel thermocouple input, isolated channels
Thermocouple input 1 to 15 (*1)
(MX compatible) (AAT145-S)
A030417E.EPS
*1: Since the 16th point is used as the reference junction compensation input, only up to the 15th point can be used as
temperature inputs from the field.
■ Pulse Input Filter (PLFL) – FIO Analog Input/Output : KFCS2/KFCS £

▼ Pulse Input – Input Filtering
Whether or not the pulse input filter is available can be set on IOM Builder. Choosing
[Tools] - [Set Details] on the IOM builder, [Input Filtering] check box becomes available.
The PLFL can only be set for the signals (terminals) of the following I/O module:
Table Signals (Terminals) of the I/O Modules for which the PLFL can be Set : KFCS2/KFCS £
8-channel pulse train input (AAP135-S) Pulse train input 1 to 8
A030418E.EPS
■ Transmitter Power Supply (VTTSEL) – FIO Analog Input/Output : KFCS2/

KFCS £
▼ Pulse Input – Transmitter Power
The voltage of the pulse input transmitter power supply is set on the details setting dialog
box of IOM Builder.
Set either [12] or [24] (unit: V). The default setting is [12].
The VTTSEL can only be set for the signals (terminals) of the following I/O module:
Table Signals (terminals) of the I/O modules for which the VTTSEL can be Set : KFCS2/KFCS £
A030419E.EPS

■ OOP Detection (OOPE) – FIO Analog Input/Output : KFCS2/KFCS £
▼ Detect OOP
Whether or not to detect the disconnection of the output signal (OOP: output open) is set in
the I/O module properties. Check [Detect OOP] check box on the builder. By default, this
check box is checked.
The OOPE can only be set for the following I/O modules:
• 8-channel current input, 8-channel current output (AAI841-S)
• 8-channel voltage input, 8-channel current output (AAB841-S)
• 8-channel voltage input, 8-channel current output (MAC2 compatible terminal place-
ment) (AAB841-S)
• 4-channel current Input, 4-channel current output, isolated channels (AAI835-S)
• 8-channel current output, isolated (ASI533-S)
• 16-channel current output, isolated (AAI543-S)
• 8-channel current Input, 8-channel current output, HART (AAI841-H)
• 4-channel current Input, 4-channel current output, isolated channels, HART (AAI835-
H)
• 8-channel current output, isolated, HART (ASI533-H)
• 16-channel current output, isolated, HART (AAI543-H)
■ Burnout Specification (BOEN) – FIO Analog Input/Output : KFCS2/KFCS

£
▼ Specify Burnout
Whether or not to detect the burnout is set on the I/O module properties. On the builder,
[Specify Burnout] check box is available. By default, this check box is checked.
If [Specify Burnout] is checked, either [Upscale] or [Downscale] needs to be selected for
the burnout.
The default setting is “Upscale.”
The BOEN can only be set for the following I/O modules:
• 16-channel thermocouple/mV input, isolated (AAT141-S)
• 16-channel thermocouple/mV input; isolated (AST143-S)
• 16-channel thermocouple/mV input, isolated channels (AAT145-S)
• 15-channel thermocouple input, isolated channels (MX compatible) (AAT145-S)
• 12-channel RTD input, isolated (AAR181-S)
• 8-channel RTD/POT input; isolated (ASR133-S)
• 16-channel RTD/POT input, isolated channels (AAR145-S)

■ OOP Clear (OPCLS) – FIO Analog Input/Output : KFCS2/KFCS £
▼ OOP Clear
The OOP clear function automatically sets the output to the tight-shut value when the
output open (OOP) state has continued for more than the specified time (fixed at 4 sec-
onds).
Whether or not the OOP clear function is available is set on the I/O module properties. On
the builder, [OOP Clear] check box is available.
The OPCLS can only be set for the following I/O modules:
• 8-channel current input, 8-channel current output (AAI841-S)
• 8-channel voltage input, 8-channel current output (AAB841-S)
• 8-channel voltage input, 8-channel current output (MAC2 compatible terminal place-
ment) (AAB841-S)
• 4-channel current Input, 4-channel current output, isolated channels (AAI835-S)
• 8-channel current output, isolated (ASI533-S)
• 16-channel current output, isolated (AAI543-S)
• 8-channel current input, 8-channel current output, HART (AAI841-H)
• 4-channel current input, 4-channel current output, isolated channels, HART (AAI835-
H)
• 8-channel current output, isolated, HART (ASI533-H)
• 16-channel current output, isolated, HART (AAI543-H)

■ Cold Junction Compensation Correction Setting (RJCSEL) – FIO Analog
Input/Output : KFCS2/KFCS £
▼ Cold Junction Compensation Correct
The cold junction compensation correction for the thermocouple input is set on the I/O
module properties.
The selection list and default values of the cold junction compensation correction vary for
each IOM.
If this setting is changed, IOM initialization loading will be performed.
The RJCSEL can only be set for the following I/O modules:
• 16-channel thermocouple/mV input, isolated (AAT141-S)
• 16-channel thermocouple/mV input; isolated (AST143-S)
• 16-channel thermocouple/mV input, isolated channels (AAT145-S)
• 15-channel thermocouple input, isolated channels (MX compatible) (AAT145-S)
The following shows the selection list (default values) for each IOM:
Table Signals (Terminals) of the I/O Modules for which the RJCSEL can be set : KFCS2/KFCS £
Type (model name) Selection list (default)
16-channel thermocouple/mV input, isolated (AAT141-S) Fixed at EUR Terminal
16-channel thermocouple/mV input, isolated (AST143-S) Fixed at EUR Terminal
16-channel thermocouple/mV input, isolated channels (AAT145-S) Fixed at KS Connector
15-channel thermocouple input, isolated channels (MX compatible)
Fixed at MX Interchange
(AAT145-S)
A030420E.EPS
■ Dual – FIO Analog Input/Output : KFCS2/KFCS £

▼ Duplicate Next Card – Analog Input/Output
Whether or not to make the adjacent I/O module dual-redundant is set on the I/O module
properties. On the builder, [Duplicate Next Card] check box is available.
There are 32 types of FIO Analog Input/Output modules can be set into dual-redundant
configuration. However, 16-Channel Pulse Input (PM1 Compatible) (AAP149-S) is not
included.
SEE ALSO
For the connection method when dual-redundant I/O modules are specified, see the followings in chapter
“● Dual-Redundant Multi-Point Analog Input : KFCS2/KFCS £” in “■ Data Reference with Respect
to Dual-Redundant Input ¡ £”
“● Dual-Redundant Multi-Point Analog Output : KFCS2/KFCS £” in “■ Data Setting with Respect to
Dual-Redundant Output ¡ £”

■ Command Line Input 1 : KFCS2/KFCS £
▼ Command
Specify a special setting for each I/O module signal (terminal) in a command line.
This specification is performed in the details setting dialog of IOM Builder.
• Enter a string of a command line. Specify the command line by delimiting it with a
comma (,).
• The string of a command line is checked when overwriting or downloading. If an
invalid command line is specified, an error will occur.
• If a value outside of the specified range is specified, an error will occur.
• If the same command line is specified, the command line that is specified the last will
take precedence. No error will occur in this case.
The following shows the commands that can input command lines for the analog I/O
module:
Table Command line input for the analog I/O module : KFCS2/KFCS £
Command Description Default Specification method
INREV Input signal reverse No Yes or No
PVLMT Measured value limit No No or lower limit value 䉭 upper limit value
TSHUT Tight-shut Output 0.00125 A 0.00125 to 0.023 (ampere)
ASI133:Yes
SCCHK Short Circuit Check Yes/No/<a value>
ASR133:No
WIRING Wiring Type 3 2, 3, 4
HARTPRI HART Priority Yes Yes/No
A030421E.EPS
䉭: One-byte space
● INREV (Input Signal Reverse) : KFCS2/KFCS £

This command reverses input signals. Specify INREV when the field input/output is “Mini-
mum range > maximum range” in an analog I/O module.
Syntax
INREV=No
INREV=Yes
Parameter
• No
Input signals are not reversed (default).
• Yes
Input signals are reversed.

● PVLMT (Measured Value Limit) : KFCS2/KFCS £
Specify the upper and lower limit values of measured values. If a measured value exceeds
the specified upper and lower limit values, the measured value will be limited within the
specified upper and lower limit values.
Syntax:
PVLMT = No
PVLMT = 10 90
Parameter:
• No
No limit is used for measured values (default).
• Lower limit value 䉭 upper limit value (%)
䉭: One-byte space
Specify the upper and lower limit values of measured values with the actual amount.
For data ranging from 0 to 100%, such as current input and voltage input, specify 0 to
100%.
Note that the IOP will not be detected if the IOP detection level is outside of this
specification.
● TSHUT (Tight-Shut Output) : KFCS2/KFCS £

Specify the I/O modules' tight-shut output. This tight-shut output is used when the I/O
module is initialized. If a function block is connected to the I/O module and it gives a 0% (or
below) output, the tight-shut output set for the function block is output instead of this tight-
shut output.
Syntax:
TSHUT=0.00125
Parameter:
• Tight-Shut output
Tight-shut output can be specified with a value between 0.00125 and 0.023. The unit
of this value is ampere. The default is 0.00125. The tight-shut output should not go
beyond the OOP detection range. So that this setting should be greater than the
setting of SOOP (OOP detection level).

● SCCHK (Short Circuit Check) : KFCS2/KFCS £
Checks the short circuit of the I/O module.
When the short circuit is detected, the same value specified for burnout is used as input
signal. With BOEN command, burnout upscale or burnout downscale can be specified.
Syntax:
SCCHK=No
SCCHK=Yes
Parameters:
• No
Short circuit check is inactive (Default).
• Yes
Short circuit check is active.
The input value when short circuit occurs is the same as the input specified by burnout
settings (BOEN command).
● WIRING (Wiring Type) : KFCS2/KFCS £

Specifies the wiring type of resistance temperature detector. The wiring type of potentiom-
eter is fixed as 3-wire.
Syntax:
WIRING=2
Parameter:
2: 2-Wire
3: 3-Wire (Default)
4: 4-Wire
● HARTPRI (HART Communication Master Priority) : KFCS2/KFCS £

This command specifies the HART communication master’s priority.
The I/O module and a HHT (handheld terminal) can be specified as the HART communica-
tion masters, normally, I/O module is used as primary master.
Syntax:
HARTPRI=Yes
Parameter:
• Yes
Used as primary master (Default)
• No
Used as secondary master

● Command Line Input Enable/Disable for Each I/O Module Signal
(Terminal) : KFCS2/KFCS £
The following lists whether the command line input is enabled or disabled for each I/O
module signal (terminal):
Table Command Line Input Enable/Disable for Each I/O Module Signal (Terminal) (1/2) : KFCS2/
KFCS £
Terminal HART
Type (model name) IOM type INREV PVLMT TSHUT SCCHK WIRING
number PRI
8-channel current input, isolated channels
(AAI135-S)
16-channel voltage input (-10 to 10V)
(AAV142-S)
16-channel voltage input, isolated
(AAV144-S)
16-channel voltage input (-10 to 10V),
isolated (AAV144-S)
Thermocouple

input
1 to 16
isolated (AAT141-S) mV input (%)
TC input (V)
Thermocouple

input
1 to 16
isolated (AST143-S) mV input (%)
TC input (V)
Thermocouple

input
1 to 16
solated channels (AAT145-S) mV input (%)
TC input (V)
Thermocouple
15-channel thermocouple input, isolated 1 to 15
input
channels (MX compatible) (AAT145-S) (*1)
TC input (V)
RTD input
RTD input (ohm)
RTD input
8-channel RTD/POT input, isolated
POT input 1 to 8
(ASR133-S)
RTD input (ohm)
RTD input
16-channel RTD/POT input,
POT input 1 to 16
isolated channels (AAR145-S)
RTD input (ohm)
A030422E.EPS
: Input is possible.
blank : Input is not possible.
*1 : Since the 16th point is used as the reference junction compensation input, only up to the 15th point can be used

Table Command Line Input Enable/Disable for Each I/O Module Signal (Terminal) (2/2) : KFCS2/
KFCS £
Terminal HART
Type (model name) IOM type INREV PVLMT TSHUT SCCHK WIRING
number PRI
16-channel pulse input (PM1 Compatible)
Pulse Input 1 to 16
(AAP149-S)
8-channel current input, 8-channel current Current input 1 to 8
output (AAI841-S) Current output 9 to 16
8-channel voltage input, 8-channel current Voltage input 1 to 8

output (AAB841-S) Current output 9 to 16
1, 3, ..., 15
8-channel voltage input, Voltage input (odd
8-channel current output numbers)
(MAC2 compatible terminal placement) 2, 4, ..., 16
(AAB841-S) Current output (even
numbers)
output, isolated channels (AAI835-S) Current output 5 to 8
16-channel voltage output (-10 to 10V)
(AAV542-S)
16-channel voltage output (-10 to 10V),
isolated (AAV544-S)
8-channel current output, isolated
(ASI533-S)
16-channel current output, isolated
(AAI543-S)
16-channel current input, HART
(AAI141-H)
16-channel current input, isolated,
HART (AAI143-H)
8-channel current input, isolated,
HART (ASI133-H)
8-channel current input, isolated channels,
HART (AAI135-H)
output, HART (AAI841-H) Current output 9 to 16

output, isolated channels, HART (AAI835-H) Current output 5 to 8
8-channel current output, isolated,
HART (ASI533-H)
16-channel current output, isolated,
HART (AAI543-H)
A030435E.EPS

■ Command Line 2 – FIO Analog Input/Output : KFCS2/KFCS £
▼ Command
Specify a special setting for each I/O module in a command line.
This specification is performed on the I/O module properties.
The following shows the commands that can input command lines for the analog I/O
module:
Table Command Line Input for the Analog I/O Module : KFCS2/KFCS £
Command Description Default Specification
OOP detection
SOOP 0.00085 A 0 to 0.023 A
level specification
Yes for current output.
Output readback
In case of the voltage output, Yes when the I/O
ORBE function Yes or No
module is set as dual-redundant, and No when the
specification
I/O module is set as single.
Front connector
Yes when the I/O module is set as dual-redundant,
CNCTCHK disconnection Yes or No
and No when the I/O module is set as single.
check
Sets a fixed
FIXED
temperature to Disable FIXED_RJC Temperature
_RJC
RJC
A030423E.EPS
● SOOP (OOP Detection Level Specification) : KFCS2/KFCS £

Specify the OOP detection level.
Syntax:
SOOP=0.001
Parameter:
• SOOP detection level
Specify the OOP detection level within 0 to 0.023 (unit: ampere). The default is
0.00085 A.
In order to prevent the OOP alarm occurrence during tight-shut output, the setting of
SOOP should be smaller than the setting of TSHUT (tight-shut output).

● ORBE (Output Readback) : KFCS2/KFCS £
Reads back the output from the I/O module. If the deviation is too large, the I/O module is
set to FAIL status.
Syntax:
ORBE=Yes
ORBE=No
Parameter:
• Yes
Readback the output. (Default, except for AAV542-S when not in dual-redundant
configuration).
• No
Do not readback the output. (Default for AAV542-S when not in dual-redundant con-
figuration).
● CNCTCHK (Front Connector Disconnection Check) : KFCS2/KFCS £

Specify whether or not to check the disconnection of the front connector. If a front connec-
tor disconnection error is detected when the front connector disconnection check is speci-
fied, the I/O module will be placed in the “Fail” state.
Syntax:
CNCTCHK=Yes
CNCTCHK=No
Parameter:
• Yes
Front connector disconnection check is performed. (Default when the I/O module is
set as dual-redundant.)
• No
Front connector disconnection check is not performed. (Default when the I/O module
is set as single.)
● FIXED_RJC (Sets a Fixed Temperature to RJC) : KFCS2/KFCS £

This fixed temperature is used as the cold junction temperature for temperature compensa-
tion calculation.
Syntax:
FIXED_RJC=25.0
Parameter:
Temperature
The temperature unit set on the I/O module properties sheet is used as the fixed RJC
temperature unit.

● Command Line Input Enable/Disable for Each I/O Module : KFCS2/KFCS
£
The following lists whether the command line input is enabled or disabled for each I/O
module:
Table Command Line Input Enable/Disable for Each I/O Module : KFCS2/KFCS £
Type (model name) SOOP ORBE CNCTCHK FIXED_RJC
16-channel current input, isolated (AAI143-S)
8-channel current input, isolated (ASI133-S)
8-channel current input, isolated channels (AAI135-S)
16-channel voltage input (AAV141-S)
16-channel voltage input (-10 to 10V) (AAV142-S)
16-channel voltage input, isolated (AAV144-S)
16-channel voltage input (-10 to 10V), isolated (AAV144-S)
16-channel thermocouple/mV input, isolated (AAT141-S)
16-channel thermocouple/mV input, isolated (AST143-S)
16-channel thermocouple/mV input, isolated channels (AAT145-S)
15-channel thermocouple input, isolated channels (MX compatible)
(AAT145-S)
12-channel RTD input, isolated (AAR181-S)
8-channel RTD/POT input, isolated (ASR133-S)
16-channel RTD/POT input, isolated channels (AAR145-S)
8-channel pulse train input (AAP135-S)
16-channel pulse input (PM1 Compatible)(AAP149-S)
8-channel current input, 8-channel current output (AAI841-S) (*1) (*1)
8-channel voltage input, 8-channel current output (AAB841-S) (*1) (*1)
(*1) (*1)
(MAC2 compatible terminal placement) (AAB841-S)
4-channel current input, 4-channel current output, isolated
(*1) (*1)
channels (AAI835-S)
16-channel voltage output (-10 to 10V) (AAV542-S)
16-channel voltage output (-10 to 10V), isolated (AAV544-S)
8-channel current output, isolated (ASI533-S)
16-channel current output, isolated (AAI543-S)
16-channel current input, HART (AAI141-H)
16-channel current input, isolated, HART (AAI143-H)
8-channel current input, isolated, HART (ASI133-H)
8-channel current input, isolated channels, HART (AAI135-H)
8-channel current input, 8-channel current output, HART
(*1) (*1)
(AAI841-H)
4-channel current input, 4-channel current output, isolated
(*1) (*1)
channels, HART (AAI835-H)
8-channel current output, isolated, HART (ASI533-H)
16-channel current output, isolated, HART (AAI543-H)
A030424E.EPS
*1 : The command line is reflected only in output points.

A3.4.2 Parameters for FIO Contact Inputs/Outputs

This section explains the following parameters of the I/O module that are classified
into the FIO contact inputs/outputs:
• Mode (*1)
• P&ID tag name
• Tag name
• Tag comment
• Switch position label
• Label format
• Btn1, Btn2
• Security level
• Tag mark (*2)
• Upper window (*2)
• Help (*2)
• Time-proportioning ON/OFF pulse period (PP)
• Phasing (OF)
• Filter setting (SIN_CTL)
• Detection edge (PEG)
• Fallback (FBK)
• Automatically delete noisy events (EVRDELSET)
• Time period of automatically delete noisy events (EVTDELTIME)
• Number of events per period (EVTDELNUM)
• Dual
• Command line
*1: The point mode is displayed for all contact I/O modules in the FIO.
TIP
If an item in which a setting has already been entered by default is left blank, an error will occur and the
previously set value will return. However, items that are blank by default can be left blank.

■ Point Mode – FIO Contact Input/Output : KFCS2/KFCS £
▼ Mode
The operation mode for each terminal is set with IOM Builder.
The selection list of the point modes varies depending on the I/O module type.
If the point mode is set for an odd-numbered point terminal in a pulse width output module,
a status/pulse width output module, or a status/pulse width output module, the point mode
for an even-numbered point terminal (in which 1 has been added to an odd-numbered
point) will automatically be set to the same value. If the point mode is set for an even-
numbered point terminal, the point mode for an odd-numbered point terminal (in which 1 is
subtracted from an even-numbered point) will automatically be set to the same value.
For example, if the point mode for %Z011101 is set to PW, the point mode for %Z011102
will automatically be switched to PW as well.
The following table lists the correspondence between the module types and point modes:
Table Correspondence between the module types and point modes : KFCS2/KFCS £
Point mode Module type
SI Status input
SI-SOE Status input (SOE)
PB Pushbutton input
SO Status output
PW Pulse width output
TP Time-proportioning ON/OFF output
A030436E.EPS
The following lists the selection list and default settings of the point modes:

Table Selection List and Default Settings of the Point Modes : KFCS2/KFCS £
Signal Point mode

Type (model name) Terminal
direction Selection list Default setting
32-channel status input for single (ADV157-S)
32-channel status input (ADV151-P)
64-channel status input (ADV161-P) All
Input Fixed at SI SI
16-channel status input 100V AC (ADV141-P) channels
16-channel status input 200V AC (ADV142-P)
16-channel status input (ASD143-P)
All
32-channel SOE status input (ADV151-E) (*1) Input SI, SI-SOE SI
channels
32-channel pushbutton input (ADV151-P)
16-channel pushbutton input 100V AC (ADV141-P) All
Input Fixed at PB PB
16-channel pushbutton input 200V AC (ADV142-P) channels
16-channel pushbutton input (ASD143-P)
1 to 32 Input Fixed at PB PB
32-channel status, 32-channel pushbutton input (ADV161-P)
33 to 64 Input Fixed at SI SI
32-channel status output for single (ADV557-S)
32-channel status output (ADV551-P)
All
64-channel status output (ADV561-P) Output Fixed at SO SO
channels
16-channel status relay output (ADR541-P)
8-channel status output (ASD533-S)
32-channel pulse width output (ADV551-P) All
Output PW, TP PW
16-channel pulse width relay output (ADR541-P) channels
1 to 32 Output PW, TP PW
32-channel status, 32-channel pulse width output (ADV561-P)
33 to 64 Output Fixed at SO SO
All
32-channel status/pulse width output (ADV551-P) Output SO, PW, TP SO
channels
1 to 32 Output SO, PW, TP SO
64-channel status/pulse width output (ADV561-P)
All
16-channel status/pulse width output relay output (ADR541-P) Output SO, PW, TP SO
channels
1 to 16 Input Fixed at SI SI
16-channel status input/16-channel status output (ADV851-S)
ST2 compatible (16-channel status input, 1 to 16 Input Fixed at SI SI
16-channel status/pulse width output) (ADV859-P) 17 to 32 Output SO, PW, TP SO
All
ST3 compatible (32-channel status input) (ADV159-P) Input Fixed at SI SI
channels
All
ST3 compatible (32-channel pushbutton input) (ADV159-P) Input Fixed at PB PB
channels
ST4 compatible (32-channel status/pulse width output) All
Output SO, PW, TP SO
(ADV559-P) channels
ST5 compatible (32-channel status input, 1 to 32 Input Fixed at SI SI
32-channel status/pulse width output) (ADV869-P) 33 to 64 Output SO, PW, TP SO
All
ST6 compatible (64-channel status input) (ADV169-P) Input Fixed at SI SI
channels
ST7 compatible (64-channel status/pulse width output) All
Output SO, PW, TP SO
(ADV569-P) channels
Type (model name) Signal Selection list Default setting

Terminal
direction Point mode
A030437E.EPS
*1: Can be applied only in the field control units that support dual-redundant configuration (AFS30D, AFS400, AFG30D
and AFG40D).

● Mixing PW and TP : KFCS2/KFCS £
For the I/O modules showing PW and TP in the selection list, either PW or TP can be set for
each terminal. However, if PW or TP is set for an odd-numbered point terminal, the point
mode for an even-numbered point terminal (in which 1 is added to an odd-numbered point)
will automatically be set to the same value as well. If PW or TP is set for an even-numbered
point terminal, the point mode of an odd-numbered point terminal (in which 1 is subtracted
from an even-numbered point) will automatically be set to the same value as well.
● Mixing SO, PW and TP : KFCS2/KFCS £

For the I/O modules showing SO, PW and TP in the selection list, either SO, PW or TP can
be set for each terminal. However, the following conditions must be satisfied:
• If PW is set for an odd-numbered point terminal, the point mode for an even-num-
bered point terminal (in which 1 is added to an odd-numbered point) will automatically
be set to PW as well.
• If either SO or TP is set to an odd-numbered point terminal, the point mode for an
even-numbered point terminal (in which 1 is added to an odd-numbered point) can
only be defined as either SO or TP. If PW is defined, an error will occur.
• SO is set as the time-proportioning ON/OFF mode in which the time-proportioning
ON/OFF pulse cycle (PP) is 8ms in a database.
Table Combinations that Allows the Mixing of SO, PW and TP : KFCS2/KFCS £

PW TP SO
PW
TP
SO
A030438E.EPS
: Mixing allowed
blank : Mixing not allowed

■ P&ID Tag Name – FIO Contact Input/Output : KFCS2/KFCS £
▼ P&ID Tag Name
The P&ID tag name is set on IOM Builder.
A string of up to 16 byte characters or 8 double-byte characters can be entered.
The setting of the P&ID tag name may be omitted.
■ Tag Name – FIO Contact Input/Output : KFCS2/KFCS £

▼ Tag Name
The tag name is set on IOM Builder.
A string of up to 16 byte characters can be entered for the tag name. Nothing is set by
default.
The setting of the tag name may be omitted.
■ Tag Comment – FIO Contact Input/Output : KFCS2/KFCS £

▼ Tag Comment
The tag comment is set on IOM Builder.
A string of up to 24 byte characters or 12 double-byte characters can be entered. Nothing is
set by default.
The setting of the tag comment may be omitted.

■ Switch Position Label – FIO Contact Input/Output : KFCS2/KFCS £
The switch position label name is set on IOM Builder.
It can be selected from the selection list menu or the data menu area. The selection item
names in the selection list menu and the data menu area are defined in the switch position
label list. Or, they can be entered directly. When entering a label name directly, enter a
string of up to 8 byte-characters or 4 double-byte characters for each label of labels 1
through 4.
The following shows the input format of the switch position label:
<Label 1>, <Label 2>, <Label 3>, <Label 4>
Be sure to delimit the labels with a comma (,). The default is [ON, OFF, ON].
The operation for saving the labels varies depending on the manual mode or auto mode.
The manual mode or auto mode can be set in the project properties.
• For auto mode
Strings other than ones in the selection list menu can also be entered. The entered
string is registered as a new switch position label when downloading (overwriting).
• For manual mode
If a string other than ones in the selection list menu is entered, an error will occur
when downloading (overwriting).
SEE ALSO
For details on the switch position label, see the following:
E8.2, “Switch Position Label”
■ Label Format – FIO Contact Input/Output : KFCS2/KFCS £

The label format (display directions of the buttons in the instrument diagrams) is set on IOM
Builder.
Either “Direct” or “Reverse” can be set. The default is “Direct.”
SEE ALSO
For details on the label format, see the following:
“■ Label Format – Switch Position Label” in E8.2, “Switch Position Label”

■ Btn1, Btn2 – FIO Contact Input/Output : KFCS2/KFCS £
The button color in the instrument diagram is set on IOM Builder.
The following shows the selection list of the button colors. The default color is “Red (R).”
• Red (R)
• Negro (N)
• Green (G)
• Yellow (Y)
• Blue (B)
• Magenta (M)
• Cyan (C)
• White (W)
• Steel blue (SB)
• Pink (PK)
• Spring green (SG)
• Orange (OR)
• Yellowish green (YG)
• Violet (VO)
• Deep sky blue (DB)
• Gray (GR)
SEE ALSO
For details on the button colors, see the following:
“■ Button Color – Switch Position Label” in E8.2, “Switch Position Label”
■ Security Level – FIO Contact Input/Output : KFCS2/KFCS £

The security level of data is set on IOM Builder.
Select from either [1], [2], [3], [4], [5], [6], [7] or [8]. The default setting is [4].

■ Tag Mark – FIO Contact Input/Output : KFCS2/KFCS £
The tag mark is set on IOM Builder.
The following shows the selection list of the tag marks. The default mark is “General.”
• Important with Ack.
• General
• Aux. 1
• Aux. 2
• Important
• General with Ack.
• Aux. 1 with Ack.
• Aux. 2 with Ack.
■ Upper Window – FIO Contact Input/Output : KFCS2/KFCS £

The panel name when expanding to the upper window is set on IOM Builder.
A string of up to 16-byte uppercase alphanumeric characters can be entered for the upper
window name. The setting of the upper window may be omitted.
TIP
An upper window name is stored in the clipboard by selecting [Tag window name list] in the [Tool] menu,
selecting the applicable upper window name, and then clicking the [Copy] button. It is useful if the upper
window name stored in the clipboard is pasted in the applicable field.
■ Help Number – FIO Contact Input/Output : KFCS2/KFCS £

The help number defined by the user is set on IOM Builder.
A desired help ID can be entered as a help number.
The following shows the specification format of the help number:
HWnnnn
HW : Fixed at HW
nnnn : Help ID (4-digit number)
The setting of the help number may be omitted.
TIP
A help number is stored in the clipboard by selecting [Tag window name list] in the [Tool] menu, selecting
the applicable help number, and then clicking the [Copy] button. It is useful if the help number stored in
the clipboard is pasted in the applicable field.

■ Time-Proportioning ON/OFF Pulse Period (PP) – FIO Contact
Input/Output : KFCS2/KFCS £
▼ Time-Proportioning ON/OFF Pulse
The time-proportioning ON/OFF pulse cycle is set in the details setting dialog of IOM
Builder. This can only be set for terminals whose point mode is TP (time-proportioning ON/
OFF output).
Set a numeric value (unit: second) between 0 and 300 for the time-proportioning ON/OFF
pulse cycle.
The default is 10 seconds.
■ Phasing (OF) – FIO Contact Input/Output : KFCS2/KFCS £

▼ Phasing
The phasing is set in the details setting dialog of IOM Builder. This can only be set for
terminals whose point mode is TP (time-proportioning ON/OFF output). The phasing is
used to set the time to offset the phase of the ON/OFF cycle for each output in the case of
multiple time-proportioning ON/OFF outputs in the same module.
Set a numeric value (unit: second) between 0 and 300 for the phasing.
The default is 0.1 (terminal number -1) seconds.

■ Filter Setting (SIN_CTL) – FIO Contact Input/Output : KFCS2/KFCS £
▼ Filter Setting
The filter is set in the I/O module properties.
This filter is used for preventing malfunctions caused by contact input chattering noise. The
setting of the filter is the number of sampling; each sampling period is 2 milliseconds. So
that, the filter time equals to (setting value x 2 ms). The chattering noise with the time-span
shorter than the filter time can be filtered out. For an example, when this filter setting is 2,
the chattering noise with the time-span shorter than 4 ms (2 x 2 ms) can be filtered out.
In the property sheet for the Input/Output Module, select a filter setting from “2”, “4”, “8”,
“16”, “32”, “64”, “128”, or “256”. However, for I/O module ADV151-E, an even number
between 2 to 256 can be set.
The default is [2].
The SIN_CTL can only be set for the following I/O modules:
• 32-channel status input for single (ADV157-S)
• 32-channel status input (ADV151-P)
• 16-channel status input 100V AC (ADV141-P)
• 16-channel status input 200V AC (ADV142-P)
• 16-channel status input (ASD143-P)
• 32-channel SOE status input (ADV151-E)
• 32-channel pushbutton input (ADV151-P)
• 16-channel pushbutton input 100V AC (ADV141-P)
• 16-channel pushbutton input (ASD143-P)
• 32-channel status, 32-channel pushbutton input (ADV161-P)
• 16-channel status input/16-channel status output (ADV851-S)
• ST2 compatible (16-channel status input, 16-channel status/pulse width output)
(ADV859-P)
• ST3 compatible (32-channel status input) (ADV159-P)
• ST3 compatible (32-channel pushbutton input) (ADV159-P)
(ADV869-P)
• ST6 compatible (64-channel status input) (ADV169-P)

■ Detection Edge (PEG) – FIO Contact Input/Output : KFCS2/KFCS £
▼ Detection Edge
The detection edge is set in the I/O module properties.
This item specifies whether the pressing of a pushbutton is detected by a change of an
input signal from ON to OFF or from OFF to ON during the pushbutton input.
Select one of the following items. The default is [ON].
• ON: Edge detection from OFF to ON
• OFF: Edge detection from ON to OFF
• BOTH: Edge detection both from OFF to ON and from ON to OFF
The PEG can only be set for the following I/O modules:
• ST3 compatible (32-channel pushbutton input) (ADV159-P)

■ Fallback (FBK) – FIO Contact Input/Output : KFCS2/KFCS £
▼ Perform Fallback
Whether or not the operation of the fallback function is performed is set in the I/O module
properties. On the builder, [Perform Fallback] check box is available.
By default, this check box is checked. If the I/O module is in a dual-redundant configuration,
this check box is fixed as checked.
When the fallback function is to be executed, select the function type from the following
items. The default setting is [All points Maintain Current Value].
• All points maintain current value
Retains the status when a fallback was detected, and continues either the ON or OFF
state.
• All points turn off
Sets all contacts to the OFF state.
The FBK can only be set for the following I/O modules:
• 32-channel status output for single (ADV557-S)
• 32-channel status output (ADV551-P)
• 16-channel status relay output (ADR541-P)
• 16-channel status output (ASD533-S)
• 32-channel pulse width output (ADV551-P)
• 16-channel pulse width relay output (ADR541-P)
• 32-channel status, 32-channel pulse width output (ADV561-P)
• 32-channel status/pulse width output (ADV551-P)
• 16-channel status/pulse width output relay output (ADR541-P)
(ADV859-P)
• ST4 compatible (32-channel status/pulse width output) (ADV559-P)
(ADV869-P)
• ST7 compatible (64-channel status/pulse width output) (ADV569-P)

■ Automatically Delete Noisy Events (EVTDELSET) – FIO Contact Input/
Output: KFCS2/KFCS £
The event signals input from the SOE capable status input module may be affected by the
noise such as chattering of relays so that it is necessary to automatically delete the noisy
events periodically.
The option [Automatically Delete Noisy Events] can be checked on the I/O module proper-
ties sheet. By default, this option is checked.
This option (EVTDELSET) is valid only for the following I/O module.
• 32-Channel SOE Status Input (ADV151-E)
After checking this option, the [Time] and the [Number of Events] need to be defined
accordingly.
SEE ALSO
For more information about inhibition of repeated events, see the following:
“● Automatic Event Deletion” in “■ ADV151-E Functions” of M11.1.1, “FCS Functions”
■ Time Period of Automatically Delete Noisy Events (EVTDELTIME) – FIO

Contact Input/Output: KFCS2/KFCS £
The time period is defined on the I/O module properties sheet. This setting is available only
when [Automatically Delete Noisy Events] is enabled,
The time period can be set by choosing among [0.5], [1], [1.5], [2], [2.5], [3], and [3.5] (unit:
second) settings. The default setting is [1] second.
This setting (EVTDELTIME) is valid only for the following I/O module.
• 32-Channel SOE Status Input (ADV151-E)
■ Number of Events per Period (EVTDELNUM) – FIO Contact Input/Output:

KFCS2/KFCS £
Specifies the number of events that protected from deleting the repeated noisy events per
period. This setting is defined on the I/O module properties sheet. The setting can be set by
choosing between [3] and [5]. [3] is the default setting.
This setting (EVTDELNUM) is valid only for the following I/O module.
• 32-Channel SOE Status Input (ADV151-E).

■ Dual – FIO Contact Input/Output : KFCS2/KFCS £
▼ Duplicate Next Card – Status Input/Output
Whether or not to make the adjacent I/O module dual-redundant is set in the I/O module
properties. On the builder, [Duplicate Next Card] check box is available.
This item is not available for the contact I/O modules (ADV157-S, ADV557-S) that do not
support dual-redundant configuration and Status/Pulse width Output modules (ADV551-P,
ADV561-P, ADR541-P).
The modules installed in remote node, such as ST3 compatible module (ADV159-P), ST4
compatible module (ADV559-P), ST5 compatible module (ADV869-P), ST6 compatible
module (ADV169-P) and ST7 compatible module (ADV569-P).
SEE ALSO
For the connection method when dual-redundant I/O modules are specified, see the followings in chapter
“● Dual-Redundant Contact Input ¡ £” in “■ Data Reference with Respect to Dual-Redundant Input
¡ £”
“● Dual-Redundant Contact Output ¡ £” in “■ Data Setting with Respect to Dual-Redundant Output
¡ £”

■ Command Line – FIO Contact Input/Output : KFCS2/KFCS £
▼ Command
Specify a special setting for each I/O module in a command line.
IMPORTANT
If the contents specified in a command line are changed, IOM configuration download will
be initiated for the I/O module. The I/O module will be placed in the “Fail” state during the
download. Therefore, exercise caution when changing the command lines.
This specification is performed in the I/O module properties.

The following shows the commands that can input command lines for the contact I/O
module:
● CNCTCHK (Front Connector Disconnection Check) : KFCS2/KFCS £

Specify whether or not to check the disconnection of the front connector. If a front connec-
tor disconnection error is detected when the front connector disconnection check is speci-
fied, the I/O module will be placed in the “Fail” state.
Syntax:
CNCTCHK=Yes
CNCTCHK=No
Parameter:
• Yes
Front connector disconnection check is performed. (Default when the I/O module is
set as dual-redundant.)
• No
Front connector disconnection check is not performed. (Default when the I/O module
is set as single.)
The CNCTCHK can only be specified for the following I/O modules:
• 16-channel status input (ASD143-P)
• 32-channel SOE status input (ADV151-E)
• 8-channel status output (ASD533-S)

• 32-channel pulse width output (ADV551-P)
• 32-channel status, 32-channel pulse width output (ADV561-P)
● Lead Breakage (LBENBL)

Specifies lead breakage check.
Syntax:
LBENBL=No
Parameter:
• No
Lead breakage check is inactive (default)
• Yes
Lead breakage check is active
This setting (LBENBL) is valid only for the following I/O modules.
• 16-Channel Status Input (ASD143-P)
• 16-Channel Pushbutton Input (ASD143-P)
• 16-Channel Status Output (ASD533-S)
● Short Circuit (SCENBL)

Specifies short circuit check.
Syntax:
SCENBL=No
Parameter:
• No
Short circuit check is inactive. (default)
• Yes
Short circuit check is active.
This setting (SCENBL) is valid only for the following I/O modules.
• 16-Channel Status Input (ASD143-P)
• 16-Channel Pushbutton Input (ASD143-P)

● Lead Breakage Mode (LBMODE)
When the output is OFF, and the loop does not allow the low-level current flow for lead
breakage check, with this setting, the lead breakage check is not active when the output is
OFF.
Syntax:
LBMODE=Yes
Parameter:
• No
When the output is OFF, low-level current flows for lead breakage check. (default)
• Yes
When the output is OFF, no Low-level current flows and lead breakage check be-
comes inactive.
This setting (LBMODE) is valid only for the following I/O module.
TIP
If the lead breakage check and short circuit check are active, and when the breakage or the short circuit
occurs, the I/O signals are processed as follows.
• When lead breakage or short circuit occurs, the I/O module holds the previous good values until the I/
O module recovers from the errors.
• When lead breakage or short circuit occurs, the data status of the I/O module is the same as the
other error occurs (BAD, NRDY, PFAIL, LPFL).
• When the function blocks with the features of receiving I/O module status signals such as switch
instruments and motor control blocks are connected to the I/O module, the IOP and OOP may be
indicated when the lead breakage or short circuit occurs in the connected I/O module. At the same
time, the function block falls back to manual mode. (If the function blocks are not directly connected
to the I/O module but using the sequence table to check the ON/OFF status of the module, the
function block cannot receive the error occurrence signals.)
• If multiple channels of an input module are applied, when error occurs on one channels, the data
status of all channels are affected.
• If multiple channels of an output module are applied, when error occurs on one channel, the outputs
of all channels are affected.
When creating the application program to monitor the data status of each signal channel, do the follows.
• Use the function blocks with the features of receiving I/O module status signals such as switch
instruments and motor control blocks are connected to the I/O module, the I/O module error status
can be indicated by IOP and OOP alarms.
• Use sequence control blocks such as sequence table blocks to check the I/O module status signals.

A3.4.3 HART Variable Setting Items

Among FIO analog I/O modules, the setting items for HART Variables on the I/O
modules that support HART communication are explained as follows.
• Channel
• Data Type
• Polling Address
• Service Comment
• P&ID Tag Name (*1)
• Label (*1)
*1: Specify on detail setting.
TIP
On the builder for the I/O modules that support HART communication, there are two tabs, [Analog Data]
and [HART Variable]. The settings regarding to analog I/O data are set on the [Analog Data] tab, while the
settings regarding to the HART variables are set on the [HART Variables] tab.
On [HART Variable] sheet, each variable of HART device (PV/SV/TV/FV) can be assigned to a terminal
(%Z).
SEE ALSO
For more information about setting items regarding to analog data on the I/O modules that support HART
communication, see the following:
A3.4.1 “Parameters for FIO Inputs/Outputs”
■ Channel – HART Variable : KFCS2/KFCS £

▼ Channel
Settings of Channel are performed on the [HART Variable] tab of IOM Builder.
For a Channel, set a two-digit number (01 to 16 or 01 to 08) of the element assigned for the
analog data of the same device.
By default, the setting items are empty.
TIP
• The element number for the analog data is displayed in the format of %Znnu101 to %Znnu116 (nn:
Node Number, u: Slot Number) or %Znnu101 to %Znnu108. The number of element of an I/O
module varies with the type of the I/O module.
• The element number for a HART Variable is displayed in the format of %Znnu201 to %Znnu232 (nn:
Node Number, u: Slot Number) or %Znnu201 to %Znnu208.

■ Data Type – HART Variable : KFCS2/KFCS £
▼ Data
Settings of Data Type are performed on the [HART Variable] tab of IOM Builder.
Select a setting from [PV],[SV],[TV] or [FV].
By default, this setting item is empty.
■ Polling Address – HART Variable : KFCS2/KFCS £

▼ Polling Address
If multi-drop connections are used, set the polling addresses for the connections.
Settings of polling addresses are performed on the [HART Variable] tab of IOM Builder.
The polling addresses (1 to 63 of HART Variables) are set to each element assigned for the
field device.
■ Service Comment – HART Variable : KFCS2/KFCS £

▼ Service Comment
Settings of service comment are performed on the [HART Variable] tab of IOM Builder.
Up to 40 single-byte characters or 20 double-byte characters can be entered as service
comment text. By default this setting item is empty. The setting of the service comment may
be omitted.
■ P&ID Tag Name -HART Variable : KFCS2/KFCS £

▼ P&ID Tag Name
Settings of P&ID tag name are performed on the [HART Variable] tab of IOM Builder.
Up to 16 single-byte characters or 8 double-byte characters can be entered as P&ID tag
name. By default this setting item is empty. The setting of the P&ID tag name may be
omitted.
■ Label – HART Variable : KFCS2/KFCS £

▼ Label
Settings of label are performed on the [HART Variable] tab of IOM Builder.
Up to 16 alphanumeric characters can be entered as a label.
By default, this setting item is empty. The setting of the user-defined label may be omitted.

<A4. Software Inputs/Outputs> A4-1
A4. Software Inputs/Outputs

Just like process inputs/outputs, software inputs/outputs can be referred to or set
from a function block or other application function.
■ Software Inputs/Outputs ¡ £
Software inputs/outputs are virtual inputs/outputs that are provided by the FCS’s internal
software.
Two types of software inputs/outputs are available: an “internal switch,” which is used to
exchange logical values between function blocks or other application functions; and a
“message output,” which is used to inform the occurrence of an event.
The organizational structure of software inputs/outputs is as shown below.
Software inputs/outputs
Internal switch
Common switch (%SW)
Global switch (%GS)(*1)
Message outputs
Annunciator message (%AN)
Sequence message
Print message (%PR)
Operator guide message (%OG)
Multimedia start message (%VM)
Sequence message request (%RQ)
Supervisory computer event message (%CP)
Supervisory computer event message for PICOT (%M3)
Signal event message (%EV)
SFC/SEBOL return event message (%RE)
A040001E.EPS
*1: ¡ £ Global switches can be applied to all Field control stations except standard PFCS (CS 1000).
Figure Structure of Software Inputs/Outputs ¡ £

The relationship between the software inputs/outputs and the basic control function is as
shown below.
FCS
Basic control
Software I/O
Faceplate blocks
SFC blocks
Unit instrument blocks
Options
FCS I/O Interfaces
A040002E.EPS
*1: This option can be applied in CS 3000 system only.
Figure Relationship of Software Inputs/Outputs with Basic Control ¡ £
In the sequence control, software inputs/outputs can be handled as targets of the condition
testing and status manipulation. They can even be handled as targets of condition testing
and status manipulation for function blocks other than sequence control function blocks, as
long as these blocks allow for sequence connection.

■ Referencing and Setting Software Inputs/Outputs ¡ £
The software inputs/outputs that can be referenced and set from the sequence control
blocks are shown in the table below.
Table Referencing or Setting via the Sequence Control Block ¡ £
Element name Reference Setting
Common switch (%SW)
Global switch (%GS) (*1) 䉭
Annunciator message (%AN)
Print message (%PR)
Supervisory computer event message (%CP)
Supervisory computer event message for PICOT (%M3)
SFC/SEBOL return event message (%RE)
A040003E.EPS
: Possible
Blank: Not possible
䉭: Only applicable with global switch of present station.

■ Identification of Software Inputs/Outputs ¡
▼ Element Number
Software inputs/outputs can be distinguished by their element serial numbers.
The classification of element numbers is shown below.
%XXnnnn
%XX: Software input/output element identifier. Varies according to the type of software input/output signal.
nnnn: Element serial numbers. Some software inputs/outputs elements do not have serial numbers.
Software input/output element numbers of CS 1000 are shown in the table below.
Table Software Input/Output Element Numbers of CS 1000 ¡
Element
Name Element Number Convention
Number
Common switch %SWnnnn nnnn: Serial no.(0001 to 1000)
nnn: Serial no.(001 to 256)
Global Switch (*1) %GSnnnmm1
mm: Station no. (01 to 24)
Annunciator message %ANnnnn nnnn: Serial no.(0001 to 0200)
Print message (with data) %PRnnnn nnnn: Serial no.(0001 to 0100)
Operator guide message %OGnnnn nnnn: Serial no.(0001 to 0100)
Multimedia start message %VMnnnn nnnn: Serial no.(0001 to 0100)
Sequence message request %RQnnnn nnnn: Serial no.(0001 to 0100)
Supervisory computer event message %CPnnnn nnnn: Serial no.(0001 to 9999)
Supervisory computer event message for PICOT %M3nnnn nnnn: Serial no.(0001 to 9999)
Signal event message %EVnnnn nnnn: Serial no.(0001 to 0100)
SFC/SEBOL return event message %RE –
A040004E.EPS
*1: ¡ Global switches can be applied to all Field control stations except standard PFCS (CS 1000).
In factory plant operation, for monitoring purposes user may assign a tag name for each
common switch and annunciator message output when required.
Tag names and element numbers are used when referencing or setting the software inputs/
outputs in applications such as the application programs written in SEBOL and the Windows
applications, other than the operation and monitoring functions, that are written in Visual Basic.

■ Identification of Software Inputs/Outputs £
▼ Element Number
Software inputs/outputs are identified by their element serial numbers.
The classification of element numbers is shown below.
%XXnnnn
%XX: Software input/output element identifier. Varies according to the type of software input/output signal.
nnnn: Serial numbers. Some software input/output elements do not have serial numbers.
Software input/output element numbers of CS 3000 are shown in the table below.
Table Software Input/Output Element number of CS 3000 £
Element
Name Element Number Convention
Number
Common switch %SWnnnn nnnn: Serial no.(0001 to 4000)
nnn: Serial no.(001 to 256)
Global switch %GSnnnmm
mm: Station no.(01 to 64)
nnnn: Serial no.(0001 to 0500)
Annunciator message %ANnnnn
(0001 to 1000) (for KFCS2 or LFCS2)
nnnn: Serial no.(0001 to 0200) (for SFCS)
Print message %PRnnnn (0001 to 0400) (for KFCS or LFCS)
Operator guide message %OGnnnn
Multimedia start message %VMnnnn nnnn: Serial no.(0001 to 0100)
Sequence message request %RQnnnn nnnn: Serial no.(0001 to 0200)
Supervisory computer event message %CPnnnn nnnn: Serial no.(0001 to 9999)
Supervisory computer event message for PICOT %M3nnnn nnnn: Serial no.(0001 to 9999)
Signal event message %EVnnnn
SFC/SEBOL return event message %RE –
A040005E.EPS
In factory plant operation, for monitoring purposes user may assign a tag name for each
common switch, global switch and annunciator message output when required.
Tag names and element numbers are used when referencing or setting the software inputs/
outputs in applications such as the application programs written in SEBOL and the Win-
dows applications, other than the operation and monitoring functions, that are written in
Visual Basic.

■ Software Input/Output Data Types ¡ £
Each type of software input/output is shown below.
Table Software Input/Output Data Types
Name Data Format Input/Output
Common switch (%SW) Logical value Both
Global switch (%GS) (*1) Logical value Both
Annunciator message (%AN) Logical value Both
Print message (%PR) Logical value Output only
Operator guide message (%OG) Logical value Output only
Multimedia start message (%VM) Logical value Output only
Sequence message request(%RQ) Logical value Output only
Supervisory computer event message (%CP) Logical value Output only
Supervisory computer event message for PICOT (%M3) Logical value Output only
Signal event message (%EV) Logical value Output only
SFC/SEBOL return event message (%RE) Logical value Output only
A040006E.EPS
The message output signal except the annunciator is used to trigger an execution when its
logical value equal to “1” (True). The signal only has meaning when it is true (=1). The
annunciator message output signal is meaningful in both True (=1) and False (=0). True
represent the error status occurrence while False represents the error status recovery.

■ Destination of Software Input/Output Messages
The destination of each software input/output message is shown below.
Table Destination of Software Input/Output Messages
Display in Electronic Flashing Display Multimedia
Message Output Printing File Saving
Window Sound on Window Window Function
Process
Annunciator message (%AN) Alarm
window
Print message (%PR)
Operator
guide window
Supervisory computer event
message (%CP)
Supervisory computer event
message for PICOT (%M3)
SFC/SEBOL return event message
(%RE)
A040007E.EPS
: Possible
Blank: Not possible
The signal event message output (%EV) and SFC/SEBOL return event message output
(%RE) are used to exchange the internal function events among FCSs. They cannot be
used to exchange events between an FCS and HIS through the control bus.

<A4.1 Common Switch> A4-8
A4.1 Common Switch

Common switches are internal switches used by various control functions to save
the shared logical values in an FCS.
■ Common Switches ¡
Common switches are internal switches used by the various control functions of an FCS to
exchange logical values between the functions.
The logical value of common switch does not directly output to outside FCS. They are used
by various control functions in FCS for the condition testing and status manipulation.
Common switches with element number %SW0001 to %SW0200 are fixed as system
switches. They are used to indicate the different status of the FCS. Only a few of the
switches can be defined by users.
Common switches in the CS 1000 with element number %SW0201 to %SW1000 may be
freely defined by users.
■ Common Switches £
▼ Increase Number of System Common Switches
Common switches are internal switches used by various control functions to save the
shared logical values in an FCS.
The logical value of a common switch is not directly output to an external FCS, but are used
by various control functions in an FCS for condition testing and status manipulation.
Common switches with element number %SW0001 to %SW0400 are fixed as system
switches. However, if the number of system common switches is not increased, the ele-
ment numbers of the system common switches are from %SW0001 to %SW0200 (*1).
They are used to indicate the different statuses of the FCS. Only a few of switches can be
defined by users.
Common switches in the CS 3000 with element number %SW0401 to %SW4000 (If the
number of system common switches is not increased, %SW0201 to %SW4000) may be
freely defined by users.
*1: The number of system common switches of SFCS is fixed between %SW0001 and %SW0200. The user-difinable
common switches are from %SW0201 and %SW4000.
Changing the number of system common switches can be performed on FCS properties
sheet (*2) by checking the option box [Increase Number of System Common Switches]. By
default setting, this option is checked.
*2: The option for increasing the number of system common switches is not available for SFCS.

■ Condition Testing and Status Manipulation for Common Switches
The syntax form for common-switch condition testing and status manipulation is shown
below.
● Condition Testing
When common switch ON/OFF status is applied as a condition test signal to a sequence
table block and logic chart block or to a designated function block in sequence connection
via its signal input terminal, the testing of the condition establishment is referred to as
common switch condition testing.
The syntax form for condition testing is shown below.
%SWnnnn.PV.ON/OFF
%SWnnnn: Element number
ON/OFF: Either ON or OFF must be specified.
● Status Manipulation
When common switch ON/OFF status is applied as a manipulated signal from a sequence
table block and logic chart block or from a designated function block in sequence connec-
tion via its signal output terminal, the common switch status reflecting the manipulated
signal status is referred to as common switch status manipulation.
Two types of manipulation signal outputs are available: a “latched” type and a “non-latched”
type.
The syntax form for status manipulation is shown below.
%SWnnnn.PV.H or %SWnnnn.PV.L
nnnn: Element number
H: Latched type (*1)
L: Non-latched type
*1: Latched type output is only supported by sequence table block.
SEE ALSO
For details on condition testing and status manipulation, see the following:
D3, “Sequence Control”
For details on latched type and non-latched type output, see the following:
“■ Manipulating Status Output of I/O Module” in A3.2.2, “Contact Output”

■ System Common Switches : PFCS/SFCS
Common switches (element numbers: %SW0001 to %SW0200) are fixed as system
switches with fixed functions. The statuses of these common switches can be referred to by
users.
The data for common switches %SW0001 to %SW0007 that are used as the station start
ID switches and %SW0031, which is used as an extension common switch, are written by
users.
Common switches %SW0097 to %SW0200 are valid only when the extension common
switch is set to 1 (valid).
SEE ALSO
For details on station start ID common switches and enhanced common switches, see the followings:
“■ Station Start ID Switches”
“■ Extension Common Switch”

A list of system common switch is given below.
Table System Common Switches (1/3) : PFCS/SFCS
Switch No. Name Description
1 (initial cold start), the previous value is retained in the case of
0001 initialization
restart.
0002 Restart 1 (restart), 0 (initial cold start)
0003 0
0004 Sequence table initial cold start command 1 (re-execution from start step)
0005 Sequence table restart command 1 (restart from the current step)
0006 0
1 (power failure within the momentary power failure tolerant time); 0
Momentary power failure/prolonged
0007 (reset and start, power failure exceeds the momentary power failure
power failure
tolerant time)
0008 to 0016 (Reserved)
0017 L-side CPU status 0 (normal), 1 (abnormal)
0018 R-side CPU status 0 (normal), 1 (abnormal)
0021 Power status 0 (normal), 1 (abnormal either right or left side)
0027 R-side CPU control status 1 (control), 0 (other)
0028 L-side CPU control status 1 (control), 0 (other)
0031 Common switch extension 1 (enabled), 0 (disabled)
0065 to 0072 CPU idle time (second) per minute 8 bit short integer
0073 to 0080 Communication load against one second 8 bit short integer
0097 1st unit 1st slot IOM status
0098 1st unit 2nd slot IOM status
0099 1st unit 3rd slot IOM status
0100 1st unit 4th slot IOM status
0 (normal or not defined), 1 (abnormal)
A040101E.EPS

0113 2nd unit 1st slot IOM status
0114 2nd unit 2nd slot IOM status
0115 2nd unit 3rd slot IOM status
0116 2nd unit 4th slot IOM status
0 (normal or not defined), 1 (abnormal)
0129 3rd unit 1st slot IOM status
0130 3rd unit 2nd slot IOM status
0131 3rd unit 3rd slot IOM status
0132 3rd unit 4th slot IOM status
A040102E.EPS

0145 4th unit 1st slot IOM status
0146 4th unit 2nd slot IOM status
0147 4th unit 3rd slot IOM status
0148 4th unit 4th slot IOM status
0161 5th unit 1st slot IOM status 0 (normal or not defined), 1 (abnormal)
0162 5th unit 2nd slot IOM status
0163 5th unit 3rd slot IOM status
0177-0200 (Reserved)
A040103E.EPS

■ System Common Switches : KFCS2/KFCS £
Common switches (element numbers: %SW0001 to %SW0400; If the number of system
common switches is not increased, %SW0001 to %SW0200) are fixed as system switches
with fixed functions. The statuses of these common switches can be referred to by users.
Only the data for common switches %SW0001 to %SW0007 that are used as station start
ID switches in a CS 3000 KFCS2/KFCS, are written by users.
A list of the system common switches in a CS 3000 KFCS2/KFCS is shown below.
Table System Common Switches (1/2) : KFCS2/KFCS £
0001 initialization
restart.
0003 0
0006 0
power failure
tolerant time)
0019 FCU Fan status 0 (all normal), 1 (one or more abnormalities)
0020 FCU Temperature status 0 (all normal), 1 (one or more abnormalities)
0022 (Reserved)
0023 (Reserved)
0024 (Reserved)
0025 (Reserved)
0026 (Reserved)
0029 FIO system 1 status 0 (normal or undefined), 1 (abnormal)
0030 FIO system 2 status 0 (normal or undefined), 1 (abnormal)
A040104E.EPS

Table System Common Switches (2/2) : KFCS2/KFCS £
Switch
Name Description
No.
0033 to FIO system 1 NODE1 to 16
0 (NODE ready, communication possible), 1 (NODE fail, communication impossible)
0048 status
0049 to FIO system 2 NODE1 to 16
0064 status
0065 to CPU idle time (second)
8 bit short integer
0072 per minute
0073 to Communication load against
8 bit short integer
0080 one second
0081 to
(Reserved)
0096
0097 Node1 Slot1 Status (*1) 0 (Ready or Undefined), 1 (IOM Error)
...

0177
Node11 Slot1 Status 0 (Ready or Undefined), 1 (IOM Error)
(*2)
...
0216
Node15 Slot8 Status 0 (Ready or Undefined), 1 (IOM Error)
(*2) (*3)
0217 to
0400 (Reserved)
(*3)
Switch
Name Description
No.
A040105E.EPS
*1: %SW0097 to %SW0176 are used for indicating IOM status.

*2: Only when the option [Increase Number of System Common Switches] is checked on FCS properties sheet , the
common switches between %SW0177 and %SW0216 are indicating the IOM status.
*3: If the option [Increase Number of System Common Switches] is not checked on FCS properties sheet, the common
switches between %SW0201 and %SW0400 are not system common switches but user-defined common switches.
TIP
The common switches from %SW0097 to %SW0176 take the following actions under the following
circumstances.
• When both SB301 cards or both communication cards of the node fail, the corresponding common
switch keep the previous status.
• When serial and Ethernet communication card do not communication properly, the corresponding
switch is set to 1.

■ System Common Switches : LFCS2/LFCS £
Common switches (element numbers: %SW0001 to %SW0400; If the number of system
common switches is not increased, %SW0001 to %SW0200) are fixed as system switches
with fixed functions. The statuses of these common switches can be referred to by users.
Only the data for common switches %SW0001 to %SW0007 that are used as station start
ID switches in a CS 3000 LFCS2/LFCS, are written by users.
A list of the system common switches in a CS 3000 LFCS2/LFCS is shown below.
Table System Common Switches (1/2) : KFCS2/LFCS £
0001 initialization
restart.
0003 0
0006 0
power failure
tolerant time)
0019 FCU Fan status 0 (all normal), 1 (one or more abnormalities)
0020 FCU Temperature status 0 (all normal), 1 (one or more abnormalities)
0022 RIO Power status 0 (all normal), 1 (one or more abnormalities) (*1)
0023 (Reserved)
0024 (Reserved)
0025 RIO Fan status 0 (all normal), 1 (one or more abnormalities)
0026 RIO Temperature status 0 (all normal), 1 (one or more abnormalities)
0029 RIO system 1 status 0 (normal or undefined), 1 (abnormal)
0030 RIO system 2 status 0 (normal or undefined), 1 (abnormal)
A040107E.EPS
*1: If the RIO power supply is configured in a single loop circuit, the value of %SW0022 is always 1.

Table System Common Switches (2/2) : LFCS2/LFCS £
Switch
Name Description
No.
0033 RIO system 1 NODE1 status
0065 to CPU idle time (second)
8 bit short integer
0072 per minute
0073 to Communication load against
8 bit short integer
0080 one second
0081 to
(Reserved)
0200
0201 to
0400 (Reserved)
(*2)
Switch
Name Description
No.
A040108E.EPS
*2: If the option [Increase Number of System Common Switches] is not checked on FCS properties sheet, the common
switches between %SW0201 and %SW0400 are not system common switches but user-defined common switches.

■ Station Start ID Switches
Common-switch element numbers %SW0001 to %SW0007 are reserved as station start ID
switches. They are triggered when the FCS starts and retain the information stored in the
FCS.
For the common switches %SW0004 to %SW0006, part of the station start ID switch
elements, the definition of each switches during the FCS station start may be redefined in
the course of user-defined initialization process.
For instance, the sequence control function may use common switches %SW0004 and
%SW0005 to simulate the FCS initialization upon cold boot or restart (i.e., warm boot). The
sequence control function performs initialization by setting %SW0004 on and %SW0005
off. In other cases, it may just perform a restart.
Common switches %SW0001 to %SW0003 must be turned off after the system starts.
The status of each station start ID switch upon FCS startup is shown below.
Table Station Start ID Switches
Start Switch No. (%SW000n)

Start Condition
Operation n=1 n=2 n=3 n=4 n=5 n=6 n=7
RUN command OFF
Power failure (initial cold start) Initial cold start ON OFF OFF ON OFF OFF Set to ON if the duration of power
failure is shorter than momentary
Prolonged power failure (timer) power failure detection time or set
Momentary power failure to OFF if longer than momentary
(timer) power failure detection time,
Restart OFF ON OFF OFF ON OFF irrespective of the type of start
Power failure (restart) operation.
A040106E.EPS
■ Extension Common Switch ¡ £

The system common switch (element number: %SW0031) is used to define the extension
common switch (*1). The extension means that the switch elements from %SW0097 to
%SW0200 may be used to reflect the system status listed in the table of system common
switches. When %SW0031 is set to 1, the switches %SW0097 to %SW0200 reflect the
corresponding system status; when %SW0031 is set to 0, the switches do not reflect the
corresponding system status.
The default value of the extension common switch is 0.
*1: £ The extension common switch can only be used in the CS 3000 system if a SFCS station is used.

<A4.2 Global Switch> A4-19
A4.2 Global Switch

A global switch is an internal switch with the same logical value on all stations in the
same domain.
■ What is Global Switch? ¡ £

The value of global switch assigned to the present station can be checked and defined from
any application on a station. Up to 256 write-enable global switches can be assigned to
each station. The defined value is broadcasted to each station in the system via control bus
scan transmission when data transfer to other stations is defined at Scan Transmission
Definition on the FCS Constants Builder.
When the values of global switches under the control of other stations are sent via scan
transmission, the global switch on the present station is updated when data receipt is
defined at Scan Transmission Definition on the FCS Constants Builder. The values of global
switches under the control of other stations can be checked. The values of global switches
are updated at the same time mostly on all stations in the system. The values are updated
by 100 msec, which is fixed. With this function, status information can be transferred from
one station to the control function of another station with very little delay.
FCS 1 FCS 2
Link transmission
%GS %GS
FCS FCS R: Readable

station1 (R/W) station1 (R) W: Write-enable
FCS FCS
station2 (R) Control bus station2 (R/W)
A040201E.EPS
Figure Global Switch
TIP
¡ £ Global switches can be applied to all Field control stations except standard PFCS (CS 1000).

■ Scan Transmission Definitions ¡ £
To transfer/receive the values of global switches between stations, define the following scan
transmission definitions on the FCS Constants Builder.
TIP
● Present Station Definition

▼ Self Station
Define the communication buffer size to transfer the values of global switches assigned to
the present station to other stations.
• Present station buffer size:
Define 32 (bytes) to transfer the values, or 0 not to transfer them.
The default is 0.
● Station Definition
▼ Station
Define whether to receive the values of global switches under the control of other stations if
transferred.
• Station definition type:
Choose “0: Not communicate,” or “1: Individual Station Communication.”
The default is 0.
When you choose “Individual Station Communication,” define the communication buffer
size to receive data from its station every sender.
• Individual Station Definition:
Define 32 (bytes) (same value as the buffer size of the present station defined at the
sending station) to receive data, or 0 not to receive data.
IMPORTANT
• When you duplicated an FCS on System View, redefine Station Definition of Scan
Transmission Definitions.
• If the value smaller than 32 bytes is defined for the buffer size of the present station,
global switches will not work.

■ Global Switch Condition Testing and Status Operation ¡ £
The specified formats of condition testing and status operation for global switches are
described below.
TIP
Condition testing for global switches is to test whether conditions are satisfied: The ON/OFF
state or data status of global switches are tested as conditional signals of sequence table
blocks and logic chart block or function blocks for which sequence connection is specified
to its input terminals. The following formats must be used for condition testing for global
switches:
%GSnnnmm.PV.ON/OFF Test the ON/OFF state.

%GSnnnmm.PV=BAD Test whether the data status is BAD.
Where
nnn: Element number
mm: Station number (may be omitted if it is the present station).
ON/OFF: Specify ON or OFF.
● Status Operation
Status operation for global switches is to change the ON/OFF state of global switches by
action signals from sequence blocks and logic chart block or function blocks for which
sequence connection is specified to its output terminals. Status operation is applicable to
global switches of present station only.
There are two output types of action signals for global switches: “latched type” and “non-
latched type.”
The following formats must be used for status operation of global switches:
%GSnnn.PV.H or %GSnnn.PV.L
where
nnn: Element number
H: Latched output (*1)
L: Non-latched output
*1: Latched output can be used for sequence table blocks only.
SEE ALSO
For details of condition testing and status operation, see the following:
For latched and non-latched outputs, see the following:

<A4.3 Annunciator Message Output (%AN)> A4-22
A4.3 Annunciator Message Output (%AN)

The HIS annunciator function simulates the annunciator instrument panel. This
function informs the HIS of the occurrence or recovery of an alarm message.
■ Annunciator Message Output (%AN)

These special message outputs are used to simulate the annunciator panels of the instru-
ment panels. Unlike other message outputs, annunciator message outputs store alarm-
occurrence statuses as logical values.
When the alarm occurrence status changes, the annunciator message informs the HIS of
the occurrence or recovery of the message. When an alarm occurs, the alarm symbol will
flash to prompt the operator for acknowledgment. The alarm symbol will stop flashing once
it has been acknowledged.
Annunciator message outputs are processed at the basic scan cycles only.

■ Change of State of Annunciator Message
Annunciator message outputs principally have the following two status types.
• Alarm present state (PV)
An abnormal condition specified in the sequence control function is currently occurring
in the system. The alarm state is reset when the condition returns to normal.
• Flashing state (AFLS)
This prompts the operator to acknowledge the alarm.
It is possible to define the alarm priority level for each annunciator message output. The
change in state of annunciator message outputs varies according to their particular alarm
priority level.
The relationship between alarm priority levels and state changes is as follows.
• High-and medium-priority alarms: Lock type state change
• Low-priority alarms: Non-lock type state change
• Logging alarms: Self-acknowledging type state change
Alarm priority levels and state changes of annunciator message output are shown below.
Lock type (High- and medium-priority alarms) Non-lock type (Low-priority alarm)
Alarm Alarm Alarm

absent state Acknowledgment absent state absent state
Flashing Flashing Flashing
OFF ON OFF
Occurrence
Occurrence
Occurrence
Recovery Recovery
Recovery Recovery
Alarm Acknowledgment Alarm Alarm Alarm

present state present state present state Acknowledgment present state
Flashing Flashing Flashing Flashing
OFF Re-warning ON OFF ON
Self-acknowledging type (Logging alarm)
Alarm
absent state
Flashing
OFF
Recovery Occurrence
Alarm
present state
Flashing
OFF
A040301E.EPS
Figure Alarm Priority Levels and State Changes of Annunciator Message
SEE ALSO
For details on alarm priority levels, see the following:
C5.16, “Alarm Processing Levels”

■ Annunciator Message Output Operation
Annunciator message output check the alarm occurrence at each basic scan.
If the current scan gathers a different status of alarm occurrence from the last scan, the
annunciator generates an output message.
The annunciator messages triggered by changes in the alarm occurrence are as follows.
• When an alarm message is generated
The tag name specified in the Annunciator Builder appears with the a mark as below.
䊏
• When a recovery message is generated
The tag name specified in the Annunciator Builder appears with the a mark as below.
䊐
Furthermore, if the alarm priority level is higher than low-priority (i.e., medium or high), the
alarm symbol will flash. The tag mark where the alarm is initiated will also flash to prompt
the operator for acknowledgment operation.

■ Condition Testing and Status Manipulation for Annunciator Message
Outputs
The syntax form for annunciator message condition testing and status manipulation is
shown below.
When annunciator message ON/OFF status is applied as a condition test signal to a
sequence table block and logic chart block or to a designated function block in sequence
connection via its signal input terminal, the testing of the condition establishment is referred
to as annunciator message condition testing.
The syntax form for condition testing is shown below.
%ANnnnn.PV.ON/OFF -----Condition testing

%ANnnnn: Element number
ON/OFF: Either ON or OFF must be specified.
● Status Manipulation
When annunciator message ON/OFF status is applied as a manipulated signal from a
sequence table block and logic chart block or from a designated function block in sequence
connection via its signal output terminal, the annunciator message status reflecting the
manipulated signal status is referred to as annunciator message status manipulation. Two
types of condition signal outputs are available: a “latched” type and a “non-latched” type.
The syntax form for status manipulation is shown below.
%ANnnnn.PV.H or %ANnnnn.PV.L
%ANnnnn: Element number
H: Occurrence/recovery of a latched annunciator message (*1)
L: Occurrence/recovery of a non-latched annunciator message
*1: Latched type output is only supported by sequence table block.
In the case of latched annunciator messages, recovery can be made by N-status manipula-
tion of the sequence table. The following syntax form is for the recovery of an annunciator
message output.
%ANnnnn.PV.H -----N
SEE ALSO
For details on condition testing and status manipulation, see the following:
For details on latched type and non-latched type output, see the following:

■ Repeated Warning Function for Annunciator Message Outputs
The repeated warning function for annunciator message output is provided to output the
message again if the alarm condition still exists after the operator’s acknowledgment. If the
alarm condition remains, this function will be reactivated and make the alarm symbol flash
as a prompt to the operator to acknowledge the alarm again.
The two types of repeated warning functions available are:
• Timer-repeated warning
• Event-repeated warning

● Timer Repeated Warning
This function gives a warning alarm at each repeated warning alarm cycle.
When an alarm occurs, the internal timer for setting the repeat warning interval starts. If the
cause of the alarm still exists when the timer becomes high, the annunciator message will
be output again making the alarm symbol flash. At the same time, the timer will be reset
and restarted.
When the alarm condition clears, the internal timer will be stopped and the repeated warn-
ing function deactivated.
Timer-repeated warnings can be used only by annunciator message outputs defined as
high-priority alarms. The repeated warning interval time span may defined on the FCS
Constants Builder.
• Repeated warning alarm cycle:
0 to 3600 seconds
When 0 is set, the repeated warning function is deactivated.
The default setting: 600 seconds
The repeated warning alarm cycle is the internal time common to the whole control station.
It applies to all designated alarms in the FCS; it cannot be individually defined for each
annunciator message output.
When an alarm is active and the alarm symbol is set to flash, no annunciator message will
be output even though the repeated warning time interval is elapsed.
The timing chart of a timer-repeated warning is shown below.
Cause of alarm
Occurrence Recovery
Flashing
(in FCS)
Acknowledgment Acknowl-
edgment
Repeated warning
start time
Timer
Elapsed time
Alarm message Alarm message Recovery message (RECOVER)
HIS display
Flashing Lit steadily Flashing Lit steadily

A040302E.EPS
Figure Timing Chart of Timer Repeated Warning

● Event Repeated Warning
This function gives the repeated warning alarm by manipulating the annunciator message
output status. When an annunciator is generating an alarm and the cause of the alarm is
still exist, repeated warnings can be output by manipulating the annunciator message
output status to set the alarm symbol flash again.
Event-repeated warnings can be applied regardless of the alarm priority. They can there-
fore be used for those annunciators without the timer-repeated warning function.
The syntax form for repeated warning status manipulation is as follows.
%ANnnnn.RP.ON ----- Set repeated warning action

%ANnnnn.RP.OFF ----- Reset repeated warning action
The timing chart of an event-repeated warning is shown below.
Cause of alarm
Occurrence Recovery
Flashing
(in FCS)
Acknowledgment Acknowledgment
Designation of
repeated warning
Alarm message Alarm message Recovery message
HIS display
A040303E.EPS
Figure Timing Chart of Event Repeated Warning
If the repeated warning action is on even though no alarm exists, the repeated warning is
not activated.
If an event-repeated warning is specified to an alarm signal while the timer-repeated
warning is active, the timer will be reset and then started by the event-repeated warning
action.

<A4.4 Sequence Message> A4-29
A4.4 Sequence Message

A sequence message is used to pass the occurred event to the operator or to other
applications.
The following types of sequence messages are available.
• Print message output
• Operator guide message output
• Multimedia start message output
• Sequence message request
• Supervisory computer event message
• Supervisory computer event message output for PICOT
• Signal event message output
• SFC/SEBOL return event message output
■ Action of Sequence Message

The sequence message is a general term given to the output of messages from the se-
quence output terminal.
The sequence message used in the sequence control may be output from sequence
control blocks, or from the output terminals of the function blocks in sequence connection.
The sequence message output operation of the each function block is explained below.
• If the messages are output from the sequence table blocks set as “Output Each Time
Conditions are Satisfied” types (ST16, ST16E), the messages may be output at every
scan period once the condition is established.
• For blocks such as ST16 and ST16E, whose output timing is defined as an “Output
Only When Conditions Change” type, a message is output only when the condition in
the sequence table changes from false to true. The message is not output again if the
true condition continues.
• For all function blocks other than ST16 and ST16E blocks, when output message by
the sequence connection, the message will be output periodically at each start period
of the function block when the logic calculation result becomes true.
SEE ALSO
For details on the message processing of an HIS, see the following:
E11, “Message Processing”

■ Print Message (%PR)
Print message outputs print the data corresponding to an event that occurred in the pro-
cess. This is mainly used to record the event that occurred in a process by printing them on
paper.
● Specification
The syntax form for a print message output specification is shown below.
%PRnnnn.PV.NON ---- To output a print message
%PRnnnn.PV.m ---- To output a print message with an integer constant

%PRnnnn: Element number
m: Integer constant (0 to 65535)
● Contents
Print message data can be output in either of the following formats.
• Print message
Prints a comment and up to three process data items in consecutive order.
• Print message with integer constant
Prints a comment, an integer constant and then two process data items in consecutive
order, when an integer constant is designated.
The contents of the print message output can be specified in Printout Message Builder as
follows.
SEE ALSO
For the information about Printout Message Builder, see the following:
“■ Print Messages” in chapter E11.1, “Message Types”
To include an integer constant in the print message, keep the 1st data field empty when
specifying the contents of the print message output in the Printout Message Builder. If the
1st data field is not empty, the integer constant will be ignored even if it is designated and
the 1st process data will be printed. The process data to be printed is the data acquired
when the print message is output. If acquisition of such data fails, “ * ” will be printed instead
of the process data.
● Destination of Output
Print messages and data are output to the following destinations.
• Output to a printer.
• Saved in a file.

■ Operator Guide Message (%OG)
Operator guide message outputs alert the operator to the operator guide window in real-
time situations.
● Specification
The syntax form for an operator-guide message output specification is shown below.
%OGnnnn.PV.NON -----To output an operator guide message

%OGnnnn: Element number
● Contents
The contents of an operator guide message output can be specified in the Operator Guide
Builder as follows.
SEE ALSO
For the information about the Operator Guide Builder, see the following:
“■ Operator Guide Messages” in chapter E11.1, “Message Types”
● Designation of Output
Operator guide messages and data are output to the following destinations.
• Displayed in the operator guide window
• Generates an electric sound.
• The mark of the operator guide flashes in the operator guide window
• Output to a printer.
• Logged into a file.

■ Multimedia Function Start Message Output (%VM)
Multimedia function start message may start HIS multimedia function from FCS.
● Specification
The multimedia function start message output specification is shown below.
%VMnnnn.PV.NON -----To output a multimedia function start message

%VMnnnn: Element number
● Contents
The contents of a multimedia function start message output can be specified on the multi-
media tab strip on HIS setup window.
SEE ALSO
For details on HIS setup window, see the following:
E7.3, “HIS Setup Window”
Multimedia function start message is output to the following destinations.
• Multimedia function
• Store into a file

■ Sequence Message Request (%RQ)
Sequence message requests enable the operator to start or run the HIS functions from an
FCS.
● Specification
The syntax form for a sequence message request specification is shown below.
%RQnnnn.PV.NON -----To output a sequence message request

%RQnnnn: Element number
● Contents
The following HIS functions can be called by sequence message requests.
• Start user program
• Trend start/stop
• LED flashing/ON/OFF
• Calling up windows
• Execute the function assigned to function keys
The sequence message request can be logged into a file.
■ Supervisory Computer Message (%CP)

The supervisory computer message (%CP) is used to output the FCS event message to
supervisory computers connected to the system.
● Specification
The syntax form for a supervisory computer message is shown below.
%CPnnnn.PV.NON -----To output a message to supervisory computers

%CPnnnn: Element number
● Contents
To output the FCS event message to the applications in supervisory computers.
The destination of the supervisory computer message is the supervisory computers con-
nected in the system.

■ Supervisory Computer Message for PICOT (%M3) ¡ £
The supervisory computer message output for PICOT (%M3) is used to output the FCS
event message to the FCS Data Setting/Acquisition Package (PICOT) [PHS6710 (*1)]
[(LHS6710 (*2)] in the HIS.
*1: ¡ The package model name for CS 1000.

*2: £ The package model name for CS 3000.
● Specification
The syntax form for a supervisory computer message output for PICOT specification is
shown below.
%M3nnnn.PV.NON -----To output a supervisory computer message output for PICOT

M3nnnn: Element number
● Contents ¡ £
To output the FCS event message to the FCS Data Setting/Acquisition Package [PHS6710
(*1)] [(LHS6710 (*2)] running in the HIS.
*1: ¡ The package model name for CS 1000.

*2: £ The package model name for CS 3000.
The destination of the supervisory computer message output for PICOT is the HIS.
■ Signal Event Message Output (%EV)

Signal event message outputs enable a function block to inform the SEBOL control function
of event changes.
● Specification
The syntax form for a signal event message output specification is shown below.
%EVnnnn.PV.k -----To output a signal event message

%EVnnnn: Element number
k: Parameter (0 to 65535)
Signal event messages are used to exchange event information among the internal control
functions of an FCS. They are not output to a window, printer of file.

■ SFC/SEBOL Return-Event Message Output (%RE)
The output of SFC/SEBOL return-event messages enables a function block to inform the
SFC block or SEBOL program of event changes exerted by the SEBOL program.
● Specification
The syntax form for a SFC/SEBOL return-event message output specification is shown
below.
%RE.PV.k ---- To output a SFC/SEBOL return-event message.

k: Parameter (0 to 65535)
SFC/SEBOL return-event messages are used to exchange event information among the
internal control functions of an FCS. They are not output to a window, printer of file.
Sequence control block SFC block
Message.k
%RE.PV.k
A040405E.EPS
Figure Output of Event Message between Control Functions

<A4.5 Annunciator Message with Data> A4-36
A4.5 Annunciator Message with Data

Annunciator message with data means an annunciator message can be output with
a process datum.
■ Features of Annunciator Message with Data

To output an annunciator message with data can be done by out a combination of annun-
ciator message (%AN) and a printout message (%PR) together. In this case, when the
annunciator (%AN) is initiated, the message defined for Print Message (%PR) will be
displayed instead of the message defined for the %AN.
The annunciator message with data has the following features:
• When the status of the annunciator (%AN) changes, the message of the correspond-
ing Printout Message (%PR) not the message defined for the annunciator will be
output.
• On Printout Message Builder, the message for printing can be defined, up to 3 pro-
cess data can be attached to the message with defined format. Following the printout
message, ALM will be displayed to indicate the alarm occurrence, vise versa NR is
displayed. “Still” will be displayed following the repeated warning alarm. (On the pro-
cess alarm window, (!) mark will be used instead of “Still.”)
• The comment text, or the message defined on the annunciator builder will not be used
for annunciator message with data but will be used as status display on the tuning
window, process report window, and other status display windows.
• The actions such as repeated warning, locked, no-locked alarms for the annunciator
will be determined by the alarm processing level set to the annunciator.
• When sending an annunciator message with data by a sequence connection, only the
number of the annunciator (%AN) needs to be designated, there is no need to desig-
nate the printout message (%PR) number.
• A printout message may output an integer constant, but the integer constant can not
be output when the printout message is bound to an annunciator for message print-
out.

<A4.5 Annunciator Message with Data> A4-37
■ Usage of Annunciator Message with Data
To implement annunciator message with data, the following settings need to be done on
FCS property sheet.
• Setting the Annunciator Message (%AN) Head Number, which is the first annunciator
message to be bound with a printout message.
• Setting the Printing Message (%PR) Head Number, which is the first printout message
number to be bound to the annunciator.
All annunciators start from the designated head number to the last one will be implemented
as Annunciator Message with Data. When setting Annunciator Message Head Number to
zero or setting Printing Message Head Number to zero, the Annunciator Message with
Data will not function.
The following is an example, the head number of annunciator is set as 400 and the head
number of printout message is set as 100.
Annunciator Message Last Number of

Head Number Annunciator Message
1 400 500
Annunciator Message Annunciator Message Annunciator Message

(%AN) with Data
Printout Message Annunciator Message

Printout Message
(%PR) with Data
1 100 200 400
Printout Message Last Number of

Head Number (%PR) Printout Message
A040501E.EPS
Figure Usage of Annunciator with Data (LFCS)

Blank Page
Toc B-1
CS 1000/CS 3000
Reference
Field Control Station Basics
IM 33S01B30-01E 10th Edition
CONTENTS
PART-B Reliability – FCS
B1. Error Detection ..................................................................................... B1-1
B1.1 Hardware Error Detection ............................................................................. B1-3
B1.2 System Software Error Detection ................................................................ B1-6
B2. Start Operations ................................................................................... B2-1
B2.1 FCS Start Operation ...................................................................................... B2-2
B2.1.1 Selection of Start Operation ............................................................ B2-3
B2.1.2 FCS Initial Cold Start ...................................................................... B2-8
B2.1.3 FCS Restart .................................................................................. B2-11
B2.1.4 Status of FCS at Start Operation ................................................... B2-12
B2.2 Start Operation of PFCS and SFCS I/O Modules ....................................... B2-17
B2.3 Start Operation of KFCS2 and KFCS Nodes .............................................. B2-19
B2.4 Start Operation of LFCS2 and LFCS I/O Units ........................................... B2-23
B2.5 Start Operation of KFCS2, KFCS, LFCS2 and LFCS I/O Modules ............ B2-24
B3. Operation at Error Occurrence ............................................................ B3-1
B3.1 Operation at Power Failure ........................................................................... B3-7
B3.2 Operation at CPU Failure ............................................................................ B3-24
B3.3 Operation at Error Occurrence in Process I/O Module ............................. B3-29
B3.4 Common Operation of the I/O Module at Problem Occurrence ................ B3-38
B3.5 Operation of I/O Module when Downloading is Performed ...................... B3-41
B3.6 Operation of Communication I/O Module at Error Occurrence ................ B3-47
B4. Making FCS Dual-Redundant ............................................................... B4-1
B4.1 Dual-Redundant Architecture of PFCS and SFCS ...................................... B4-5
B4.2 Dual-Redundant Architecture of KFCS2 and KFCS .................................. B4-11
B4.3 Dual-Redundant Architecture of LFCS2 and LFCS ................................... B4-17

Blank Page
<B1. Error Detection> B1-1
B1. Error Detection

Error detection operation refers to actions to detect errors (Faults) in hardware or
software and to prevent side effects wherever possible.
The following section explains the error detection actions.
■ Error Detection
FCS detects the following errors.
● Hardware Error Detection

Errors occurred within FCS are detected by monitoring the actions of various FCS hard-
ware at their start and on a periodical basis.
● System Software Error Detection

Errors in system software are detected by monitoring the operations of the system software
in FCS.

<B1. Error Detection> B1-2
■ Actions Taken at Error Detection : PFCS/SFCS
The table below lists the actions taken when an error is detected within FCS.
Table Actions Taken at Error Detection in FCS: PFCS/SFCS
Recoverable/ Possibility to
Action Example
Unrecoverable continue control
Recover the error and continue Correct 1 bit error of data in main
Recoverable
operation. memory.
Possible • Ignore the I/O module in which

• Retry if possible.
the error occurred.
• Ignore the error and continue
• Stop the CPU in which the error
other operation.
Unrecoverable occurred.
Possibility to
continue control - FCS stops. Stop FCS for a fatal error.
Impossible (*1)
B010001E.EPS
*1: In addition to the situation in which CPU cannot continue control, this applies to the situation in which the error may
badly affect other equipment connected to the same control bus.
■ Actions Taken at Error Detection : KFCS2/KFCS/LFCS2/LFCS £

The table below lists the actions taken when an error is detected within FCS.
Table Actions Taken at Error Detection in KFCS2/KFCS/LFCS2/LFCS £
Recoverable/ Possibility to
Action Example
Unrecoverable continue control
Recover the error and continue Correct 1 bit error of data in main
Recoverable
operation. memory.
Possible • Ignore the I/O module in which

• Retry if possible.
the error occurred.
• Ignore the error and continue
• Stop the CPU in which the error
other operation.
Unrecoverable occurred.
Possibility to
continue control - FCS stops. Stop FCS for a fatal error.
Impossible (*1)
B010003E.EPS
*1: In addition to the situation in which CPU cannot continue control, this applies to the situation in which the error may
badly affect other equipment connected to the same control bus.

<B1.1 Hardware Error Detection> B1-3
B1.1 Hardware Error Detection

FCS detects errors occurred within the system by monitoring the operation of each
internal FCS. hardware at their start and on a periodical basis.
When an error is detected, FCS executes the automatic repair, mask or reset-start
operation wherever possible.
Hardware error detection includes the monitoring of operations of the control bus
Interface and detection of temporary errors.

■ Monitoring of Hardware Operations
FCS monitors hardware operations.
• For hardware used during normal operation, self-diagnosis is performed at hardware
start to check if the system is operating normally.
• For hardware not used during normal operation, self-diagnosis is performed on a
periodical basis to check if the system is operating normally.
■ Monitoring of CPU Operations

When an error action of software is caused by hardware abnormality, this may be consid-
ered as a temporary CPU failure, it is recommended to restart the CPU once.
■ Monitoring of Control Bus Interface Operations

When any of the following events occurs during normal operation, CPU assumes that a
control bus error has occurred. CPU is restarted just once if it occurs during dual-redun-
dancy operation. Control bus interface is reset if it occurs during single operation.
• Control bus interface internal error
• Cable or coupler error
• Internal loopback error
• Validity error in access to shared memory for CPU and control bus interface
• No response from the communication destination control bus interface within 4 sec-
onds during communication in the same domain

■ Detection of Momentary Errors
The FCS detects momentary errors of the hardware indicated below:
● Automatic correction for bit error

When 1 bit becomes error in the data in the main memory, the error may be automatically
corrected. If there are two or more bits become error, it will only detect the error but no
correction.
● Detection of a bus error

By assigning a parity bit to the data on the data bus, the user is notified of a bus error when
a bit error occurs.
● Data protection
The data area is divided into write-allowed and write-protected areas so that the data in the
write-protected area will not be destroyed by an operation error. Also, protection violations
are detected.
● Processing retry
When an error is generated during control bus communication, process I/O communica-
tion, etc., retries are performed.

<B1.2 System Software Error Detection> B1-6
B1.2 System Software Error Detection

FCS detects errors by monitoring the system software operation on FCS. The moni-
toring methods include “Monitoring by WDT” and “Task operation monitoring.”
■ Monitoring by WDT
FCS resets WDT (Watch Dog Timer) at periodical check when the control program is
operating normally. If WDT is not reset for 2 seconds, FCS will reset-starts CPU, assuming
that the control program is not functioning properly.
■ Task Operation Monitoring

FCS constantly monitors all tasks to see if they are operating normally. If any of the neces-
sary tasks to carry on controlling stops abnormally, FCS terminates immediately.

<B2. Start Operations> B2-1
B2. Start Operations

When a user start up a field control station, or when restart a part of components in
the FCS due to power failure or other abnormalities, the FCS and the parts in the
FCS are performing a procedure of Start Operations. In this chapter, the start opera-
tions are explained.
■ Outline of Start Operation ¡ £

The start operations of FCS consist of the followings.
● FCS Start Operation

FCS start operation indicates a process during the FCS changes from Stop State to run-
ning state. When a user turns the power of FCS on, or when an FCS restarts after a power
failure, the FCS performs [Initial Cold Start] or [Restart] start operation.
The start operation that an FCS to perform varies with the start conditions, power failure
time, the settings for start condition on FCS builder and so on.
● Start Operation of I/O Modules : PFSC/SFCS

For PFCS and SFSC, when the station is recovered from power failure, the communication
between function blocks and input and output units (all I/O units and I/O modules) is re-
established by the Initial Cold Start, a start operation explained above. When I/O modules
recovered from errors or restarted after maintenance, the communication to function blocks
re-establishes. The re-establishment of communication between I/O modules and function
blocks are referred to as Start Operation of I/O Modules.
Thus when an I/O module recovers from errors or restarts after maintenance, the I/O
module initial start is performed.
● Start Operation of Nodes : KFCS2/KFCS £

For KFCS2 or KFCS, when abnormalities occurred in local nodes or remote nodes, the I/O
signals communicated via the nodes fails. Only when the nodes recover from the abnor-
malities, the communication with I/O modules can be re-established. The re-establishment
of communication via nodes is referred to as Start Operation of Nodes. Thus when the
nodes recover from the abnormalities, Node Initial Start or Node Restart is performed
determined by the elapsed time of communication failure.
● Start Operation of I/O Units : LFCS2/LFCS £

For LFCS2 or LFCS, when abnormalities occurred in I/O units, the I/O signals communi-
cated via the I/O units fails. Only when the I/O units recover from the abnormalities, the
communication with I/O units can be re-established. The re-establishment of communica-
tion with I/O units is referred to as Start Operation of I/O Units. Thus when the I/O units
recover from the abnormalities, I/O Unit Initial Start or I/O Unit Restart is performed deter-
mined by the elapsed time of I/O units failure and the settings of [Start Mode].
● Start Operation of I/O Modules : KFCS2/KFCS/LFCS2/LFCS £

For KFCS2, KFCS, LFCS2 or LFCS, when I/O modules recover from the abnormalities, the
communication between function blocks and I/O modules can be re-established. The re-
establishment of communication with I/O modules is referred to as Start Operation of I/O
Modules. Thus when the I/O modules recover from the abnormalities, I/O Module Initial
Start is performed.

<B2.1 FCS Start Operation> B2-2
B2.1 FCS Start Operation

“FCS start operation” refers to all the actions performed through the process of
FCS’s changing its status from operation stop status to normal operation status.
It includes “Initial cold start” and “Restart.” Which operation to be performed is
determined by “Cause of start,” “Start condition,” and “Power failure time and
Momentary Power Failure tolerant time.”
■ Flow of Start Operation

The figure below shows the flow of FCS start operation as it switches from operation stop
status to normal operation status through either “Initial cold start” or “Restart.”
Power shutoff or
station stop status
Initiate start operation
CPU START
Cause of start
Power on
Initialization specified
(MAN) Restart specified (AUT)
Start condition
Timer set (TIM)

Prolonged power Momentary power
failure Power failure time after failure
previous power turnoff
Prolonged power failure:

momentary power ⱕpower failure time
failure tolerant time
Momentary power failure:
momentary power >power failure time
failure tolerant time
Initial cold start Restart
System initialization processing(*1) System initialization processing(*1)
User definition initialization Complete processing for blocks

processing suspended due to power failure
User definition initialization

Windup operation
processing
The content of initial cold

start differs from
Start processing from the Continue processing from where it
that of restart.
beginning of periodic processing was suspended by power failure
B020101E.EPS
*1: The status of process I/O, software I/O, various function blocks, and SEBOL control function within FCS change.
Figure Flow of FCS Start Operation

B2.1.1 Selection of Start Operation

Execution of either “Initial cold start” or “Restart” is determined by “Cause of start,”
“Start condition,” or “Power failure time and momentary power failure tolerant time.”
■ FCS State before Start Operation

The FCS state before start operation is “Stop State.” In this state, the operation of FCS is
not running. The “Stop State” of FCS includes the following two situations.
● Power Shutoff
This is a state that FCS power is off and all the FCS functions are stopped.
In power shutoff status, unless the memory is volatilized, the start operation is automatically
executed when the power is turned on, and the system will change to normal operation
state.
● Station STOP
This is a state that all application programs including the control functions are halted al-
though FCS power is on.
In station stop state, the start operation is executed by CPU START. For example, when the
RUN command is received from HIS (to be more specific, from the HIS control station
status display window), FCS will change to normal operation state, resetting the current
operation state.
TIP
During memory image loading (off-line loading), the status of FCS is regarded as a station STOP status.
During this operation, FCS CPU is used for loading operation while all applications are halted.
■ Cause of Start
The FCS’s cause of start includes “Power on” and “CPU START.”
● Power on
This is to turn on the power to PFCS.
● CPU START
This is to start the operation of PFCS, which is in a station STOP status, using a method
other than “Power on.”
There are three methods of CPU START as described below.
• Completion of on-line loading to FCS
• FCS START command received from HIS
• Start operation triggered from FCS control panel

■ Start Condition : PFCS/SFCS
▼ Start Condition
The start condition determines which method to be used, initial cold start or restart, to
initiate the FCS, upon turning on the power to FCS which was in the power shutoff status.
FCS performs either initial cold start or restart according to the specified start condition.
The start condition can be set on the FCS Constant Builder.
• Start Condition
Select one from “MAN (Initial Cold Start),” “TIME (Restart in case of momentary power
failure)” or “AUTO (Restart).”
The default is “MAN (Initial Cold Start).”
Table Start Conditions and Corresponding Start Operations : PFCS/SFCS

Start Condition Start Operation
MAN (Initial cold start) -
Prolonged power failure (Momentary power failure tolerant Initial cold start
TIME (Restart at the timeⱕFCS power failure time)
time of momentary
power failure) Momentary power failure (Momentary power failure tolerant
time>FCS power failure time) Restart
AUTO (Restart) -
B020102E.EPS
When the FCS in station STOP status executes the start operation, the initial cold start
must be executed regardless of start condition.
SEE ALSO
• For more information about initial cold start operation, see the following:
B2.1.2, “FCS Initial Cold Start”
• For more information about restart operation, see the following:
B2.1.3, “FCS Restart”

■ Start Condition : KFCS2/KFCS/LFCS2/LFCS £
▼ Start Condition
The start condition determines which method to be used, initial cold start or restart, to
initiate the FCU, upon turning on the power to FCU which was in the power shutoff status.
FCU performs either initial cold start or restart according to the specified start condition.
The start condition can be set on the FCS Constant Builder.
• Start Condition
Select one from “MAN (Initial Cold Start),” “TIME (Restart in case of momentary
power failure)” or “AUTO (Restart).”
The default is “MAN (Initial Cold Start).”
Table Start Conditions and Corresponding Start Operations : KFCS2/KFCS/LFCS2/LFCS £

Start Condition Start Operation
MAN (Initial cold start) -
Prolonged power failure (Momentary power failure tolerant Initial cold start
TIME (Restart at the timeⱕFCS power failure time)
time of momentary
power failure) Momentary power failure (Momentary power failure tolerant
time>FCS power failure time) Restart
AUTO (Restart) -
B020103E.EPS
When the FCU in station STOP status executes the start operation, the initial cold start
must be executed regardless of start condition.
SEE ALSO
• For more information about initial cold start operation, see the following:
B2.1.2, “FCS Initial Cold Start”
• For more information about restart operation, see the following:
B2.1.3, “FCS Restart”

■ Power Failure Time and Momentary Power Failure Tolerant Time :
PFCS/SFCS
▼ Momentary Power Failure Tolerant Time
When “TIME” is selected as the start condition, “Momentary Power Failure Tolerant Time”
should be specified. “Momentary Power Failure Tolerant Time” is a definition item used to
determine the type of start operation based on the power failure time.
The length of power failure time is categorized into either “Prolonged power failure” or
“Momentary power failure” by comparing the power failure time with the momentary power
failure tolerant time.
The momentary power failure tolerant time is set on the FCS Constant Builder.
• Momentary Power Failure Tolerant Time: Set 0.0 to 4.0 (sec).
The default is 2.0 sec.
● Prolonged Power Failure (Momentary Power Failure Tolerant TimeⱕFCS

Power Failure Time) : PFCS/SFCS
Prolonged power failure means that the FCS power failure time elapsed is greater than or
equal to the specified momentary power failure tolerant time.
An initial cold start is executed when the power failure is a prolonged power failure.
● Momentary Power Failure (Momentary Power Failure Tolerant Time > FCS
Power Failure Time) : PFCS/SFCS
Momentary power failure means that the FCS power failure time elapsed is smaller than
the specified momentary power failure tolerant time.
Restart is executed when the power failure is a momentary power failure.

■ Power Failure Time and Momentary Power Failure Tolerant Time :
KFCS2/KFCS/LFCS2/LFCS £
▼ Momentary Power Failure Tolerant Time
When “TIME” is selected as the start condition, “Momentary Power Failure Tolerant Time”
should be specified. “Momentary Power Failure Tolerant Time” is a definition item used to
determine the type of start operation based on the power failure time.
The length of power failure time is categorized into either “Prolonged power failure” or
“Momentary power failure” by comparing the power failure time with the momentary power
failure tolerant time.
The momentary power failure tolerant time is set on the FCS Constant Builder.
• Momentary Power Failure Tolerant Time: Set 0.0 to 4.0 (sec).
The default is 2.0 sec.
● Prolonged Power Failure (Momentary Power Failure Tolerant TimeⱕFCU

Power Failure Time) : KFCS2/KFCS/LFCS2/LFCS £
Prolonged power failure means that the FCU power failure time elapsed is greater than or
equal to the specified momentary power failure tolerant time.
An initial cold start is executed when the power failure is judged as prolonged power failure.
● Momentary Power Failure (Momentary Power Failure Tolerant Time > FCU
Power Failure Time) : KFCS2/KFCS/LFCS2/LFCS £
Momentary power failure means that the FCU power failure time elapsed is smaller than
the specified momentary power failure tolerant time.
Restart is executed when the power failure is judged as a momentary power failure.

B2.1.2 FCS Initial Cold Start

Initial cold start is to reset all FCS’s internal states and initiates the control opera-
tions from the complete initial status.
■ Processing Executed at Initial Cold Start

Three processing are executed at FCS initial cold start in the following order.
1. System initialization processing
2. User definition initialization processing
3. Windup operation
Prolonged
Power failure
Power recovery
State of power
All FCSs internal Restart operation

states are reset from the beginning
Momentary power failure of periodic processing
tolerant time.
Default: 2 sec.
System User definition Windup

Periodic Periodic
98 99 initialization initialization operation
processing processing
processing processing time
B020104E.EPS
Figure Processing Executed at Initial Cold Start after Prolonged Power Failure
■ System Initialization Processing for Initial Cold Start

System initialization processing for initial cold start resets all FCS’s internal states. This
processing is automatically executed by the system when FCS initiates the start operation.
Analog and contact outputs, however, will not be reset.

■ User Defined Initialization Processing for Initial Cold Start
User defined initialization processing is executed based on the user’s definition. The user
can define the contents of initialization using the function block for initialization processing.
The initialization processing will not be executed unless the user definition initialization
processing is specified.
The function block for initialization processing is executed only once when FCS performs
the start operation. There are two types of function blocks for initialization processing.
• Startup at Initial Cold Start/Restart (I type)
• Restricted Initial Execution Type (B type)
In order to define the contents of user definition initialization processing, describe the
processing to be executed at start, on either I type or B type sequence table and logic
chart.
● Internal Switch for Start Operation Identification

The I-type initialization processing function block is executed using either initial cold start or
restart. However, by referencing the internal switch for the identification of the start opera-
tion, the processing type can be distinguished.
For example, when recovering from prolonged power failure (timer specified, FCS power
failure timeⱖT, Momentary Power Failure Tolerant Time), %SW0001 and %SW0004 are
turned on. When recovering from momentary power failure (time specified, FCU power
failure time < T, Momentary Power Failure Tolerant Time), %SW0002 and %SW0005 are
turned on.
By referencing which internal switch for identification of the start operation is being turned
on, it can be identified from which state the FCS is about to change to its normal state.
Consequently, the type of initialization processing to be performed can be specified in the
initialization sequence table and initialization logic chart by referencing this switch.

● Example of User Definition Initialization Processing
Let’s assume a recovery start operation timer (TIME) is specified, and that there are two
requirements for when the system recovers from a prolonged power failure (%SW0001 and
%SW0004 being turned on): to stop all the software counters and reset all the requests
involving the use of any resource scheduler, and to restart execution of the sequence table
step from the current step. To specify these, set the initialization sequence table as shown
below.
Symbol Rule
Condition %SW0001. PV. ON Y
Action CTS001. ACT. OFF Y

2 Y Stop all the software counters
• •
• •
• •
RS0001. ACT. OFF Y Reset all the requests to use
any resource scheduler
• •
• •
• •
%SW0004. PV. H N
Start action identification switch operation
%SW0005. PV. H Y
When %SW0004 is turned on, execution
begins with the start step, so set %SW0004
to off and %SW0005 to on to restart from
the current step.
B020105E.EPS
Figure Example of User Definition Initialization Processing Description
■ Windup Operation
▼ Wind Up Time
Windup operation is a preparatory processing for organizing time-series data that are
required for control operations. The function block’s input processing, control processing,
calculation processing and alarm processing executed during windup operation are ex-
ecuted in the same manner as in normal operation. All output signal processing, except for
the one that outputs control output signals to the process output terminal, are executed in
the same manner as in normal operation.
Sequence table blocks and logic chart blocks don’t operate while windup operation is
running.
The windup operation time can be set on the FCS Constant Builder.
• Wind Up Time: Set 0 to 100 (sec.).
The default is 60 sec.

B2.1.3 FCS Restart

FCS Restart is a start operation that attempts to maintain the status before the
operation stop status as long as possible in order to restart the operation. The start
operation is executed after restarting the suspended function block processing
where it was suspended and completing it.
■ Processing Executed at Restart

Three processing are executed at FCS restart in the following order.
1. System initialization processing
2. Completion of the function block processing that has been suspended
3. User definition initialization processing
Power recovery
State of power
Momentary
power failure Initialization processing Output processing
execution timing is automatically after suspended block
Momentary power failure decided within PFCS.
tolerant time.
Default: 2 sec.
System User definition

Periodic Periodic
98 99 initialization 99 initialization
Restart and complete the function block

processing that has been suspended
B020106E.EPS
Figure Processing Executed at Restart for Momentary Power Failure
■ System Initialization Processing for Restart

System initialization processing for restart holds or resets all FCS’s internal states.
However, analog and contact outputs are not reset.
■ User Defined Initialization Processing for Restart

User defined initialization processing is executed based on the user’s definition. The user
can define the contents of initialization processing, using the function block for initialization
processing. The user definition initialization processing will not be executed unless it is
specified.
For restart, describe the processing to be executed at start, to the Startup at Initial Cold
Start/Restart (I type) sequence table and logic chart.
Start up type (B type) sequence table or logic chart is not started by Initial Cold Start.

B2.1.4 Status of FCS at Start Operation

This section describes the behaviors of FCS when process I/O, software I/O, various
function blocks. batch control block and SEBOL control block at initial cold start or
restart.
■ Status of Process I/O at Start Operation : PFCS/LFCS2/LFCS/SFCS

The table below lists the behaviors of FCS when process I/O at initial cold start and restart.
Table Status of Process I/O : PFCS/LFCS2/LFCS/SFCS
Item Initial cold start Restart
Analog input Read new
Read new Hold previous value. Read new for
Status input
initialization block only
Push button input Input during power failure is invalid
Reset pulse count value PV = previous Continue pulse count PV = previous
Pulse input
value value
Analog output Tracking of field output value to MV Re-output MV
Status output Tracking of field output value to MV Re-output MV
Pulse-width output Output resets. Output restarts after output resets.
Output continues. Output continues.

Time-proportioning Output resets if power supply of I/O Output restarts after output resets
ON/OFF output also fails. if power supply of I/O also fails.
Read new input Re-output MV (*1)

Subsystem communication
Read new input Tracking output Read new input value and track the
ACM11, ACM12
output value. (*2 )
Subsystem communication Hold previous input value Re-output MV

Read new input Tracking output
ACM21, ACM22 (Re-read after output to subsystem)
B020107E.EPS
*1: ¡ Only supported in PFCS.

£ Only supported in SFCS.
*2: £ Only supported in LFCS2 or LFCS.

■ Status of Process I/O at Start Operation: KFCS2/KFCS £
The table below lists the behavior of FCU regarding to process I/O when the FCS is under-
going Initial Cold Start or Restart.
Table Status of Process I/O : KFCS2/KFCS £
Initial Cold Start Restart
Item
Local Node Remote Node(*2) Local Node Remote Node(*2)
Analog Input Read New Hold Previous Read New Hold Previous
HART Variable (*5) Hold Previous Hold Previous Hold Previous Hold Previous
Status Input Read New Off (0) (*1) Hold Previous(*1) Hold Previous(*1)
Read New Read New Hold Previous
(The input signal (The Push during (The Push during
Pushbutton Input Off (0)
before initial start power failure is invalid power failure is invalid
becomes invalid) input) input)
Hold PV Hold PV
Hold PV Hold PV The input during power The input during power
(When IOM recovers (When IOM recovers failure is invalid failure is invalid
Pulse Input
from power failure, the from power failure, the (When IOM recovers (When IOM recovers
counter starts from 0.) counter starts from 0.) from power failure, the from power failure, the
counter starts from 0.) counter starts from 0.)
Analog Output Read back and track Read back and track Re-output the value Re-output the value
Status Output IOM output(*4) IOM output(*4) prior power failure prior power failure
Output restarts after Output restarts after

Pulse-Width Output Output resets. Output resets.
output resets. output resets.

Output restarts after Output restarts after
Time-Proportioning Output resets if power Output resets if power
output resets if power output resets if power
ON/OFF Output supply of I/O modules supply of I/O modules
supply of I/O modules supply of I/O modules
also fails. also fails.
also fails. also fails.
Input: Hold Previous Input: Hold Previous Input: Hold Previous Input: Hold Previous
Fieldbus Communication Output: Output: Output: Output:

ALF111(*3) Track the field device Track the field device Track the field device Track the field device
first, then re-start first, then re-start first, then re-start first, then re-start
output. output. output. output.
Input: Hold Previous Input: Hold Previous Input: Hold Previous Input: Hold Previous
Sub-System
Communication Output: Output:
Output: Output:
ALR111, ALR121 Track the sub-system Track the sub-system
re-output the data re-output the data
ALE111(*3) data first, then re-start data first, then re-start
prior power failure. prior power failure.
output. output.
B020108E.EPS
*1: If an initial type sequence table referencing a status input signal via a local node, the status input signal will be
accessed again by the sequence table after Restart.
If an initial type sequence table referencing a status input signal via a remote node, the status input signal may not be
able to be accessed by the sequence table after Restart. So that, do not use the status input from the remote node as
user defined initialization processing signal.
*2: For the input signals from the remote nodes, the FCU holds the previous values until the FCU completes reading the
new data.
*3: For the data from fieldbus I/O and sub-system communication I/O, FCU holds the previous data values until the whole
data are acquired after restart.
*4: The outputs of IOM vary with types of errors and the different settings.
*5: HART variables hold previous data until the next data are transmitted.
SEE ALSO
For the output state of the IOM at probrem occurrence, see the following:
“■ Output State of the I/O Module during the Occurrence of an Error : KFCS2/KFCS £” in B3.4, “Com-
mon Operation of the I/O Module at Probrem Occurrence”

■ Status of Software I/O at Start Operation
The table below lists the behavior of FCS when software I/O at initial cold start and restart.
Table Status of Software I/O
Reset switches to 0 except start Hold previous status except start
Internal status switches
operation identification switch. operation identifier switch.
Reset occurrence status and flashing Hold previous status, including flashing
Annunciator message
status. status.
Restart transmission from transmission
Message output Reset transmission standby message.
standby message.
B020109E.EPS
■ Start Operation Identification Switch

Some of the common switches are a start operation identification switch. If the start opera-
tion identification switch is referred to, the switch will indicate the kind of status from which
FCS is attempting to shift to normal operation status.
The table below shows how the start operation identification switch is set.
Table Start Operation Identification Switch
Start Common switch (%SW000n)

Start Conditions
Operation n=1 n=2 n=3 n=4 n=5 n=6 n=7
CPU Start OFF
Power failure
(MAN specified) Initial cold start ON OFF OFF ON OFF OFF Regardless of start
conditions specified,
Prolonged power failure it is ON if power
(TIM specified) failure time elapsed
Momentary power failure is shorter than
(TIM specified) momentary power
Restart OFF ON OFF OFF ON OFF failure time and OFF
Power failure if longer.
(AUT specified)
B020110E.EPS
The following are the usage of common switches.

• %SW0001 to %SW0003 is for start operation identification.
• %SW0004 to %SW0006 is for sequence table execution start step identification.
• %SW0007 is for power failure time identification.
• %SW0003 and %SW0006 are reserved for future use.

■ Status of Function Block at Start Operation
The behavior of FCS regarding to function blocks when the FCS is undergoing Initial Cold
Start or Restart is shown as follows.
● Internal Status of Function Block

The table below shows the behavior of FCS regarding to function blocks when starting the
FCS.
Table Internal Status of Function Block
Internal function block item Initial cold start Restart
Order of execution Start execution from the top block Restart from current block
MAN fallback in the block in which output
Block mode Hold previous status
terminal is directly connected to I/O module
Alarm status Hold previous status, including flashing status Hold previous status including flashing status
Transmit messages starting with new messages
Process alarm message Transmit messages starting with new messages
(*1)
Resource scheduler All requests are canceled
Operation continues
Valve monitor Built-in error state reset timer is reset
Operation continues Operation continues
Totalization
(Data during stop status are ignored.) (Data during stop status are ignored.)
B020111E.EPS
*1: If a repeated warning alarm occurs at start operation, process alarm message is output assuming that a new alarm is
created. As long as the alarm status lasts, the repeated warning alarm message is continuously output at regular
intervals. If specified, all alarm messages occurred at initial cold start can be output.
● Status of Special Function Block at Start Operation

The table below shows the behavior of FCS regarding to the specific function blocks when
starting the FCS.
Table Status of Special Function Block
Function block name Initial cold start Restart
Answerback tracking is performed when
Motor Control Blocks both pulsive output and answerback tracking Operation continues.
are specified.
Operation is restarted from the first step
Operation continues from the current step.
(or the step that follows Step 00) after the
Sequence Table Blocks (*1) (Normal periodic processing is executed
windup operation If all conditions are
as if no power failure occurred.)
satisfied, operation is performed.
Logic Chart Block Built-in timer is reset. Operation continues.
Track output value to MV. Built-in timer is
Switch Instrument Blocks reset. Operation continues.
Timer block PV starts from previous value.
Software counter block Stopped PV starts from previous value. However,

the value input during power failure are
Pulse train input counter block invalid.
B020112E.EPS
*1: The start operation for sequence table can be changed by changing the contents of start operation identification
switch.

● MAN Fallback of Function Block at Start Operation
MAN fallback of function block differs depending on the type of start operation as described
below.
• At initial cold start
If the function blocks shown below are connected to the process I/O at start operation,
the block mode becomes MAN by the MAN fallback function.
Table List of Function Blocks That Perform MAN Fallback at Initial Cold Start
Function block type Code
PID, PI-HLD, ONOFF, ONOFF-E, ONOFF-G, ONOFF-EG, PID-TP, PD-MR,
Regulatory Control Blocks PI-BLEND, PID-STC, MLD-SW, MC-2, MC-2E, MC-3, MC-3E, RATIO, PG-L13,
BSETU-2, BSETU-3, VELLIM,AS-H/M/L, FFSUM, XCPL
SO-1, SO-2, SIO-11,SIO-12, SIO-21, SIO-22, SIO-12P, SIO-22P, SO-1E,
Sequence Control Blocks
SO-2E, SIO-11E,SIO-12E, SIO-21E, SIO-22E, SIO-12PE, SIO-22PE
B020113E.EPS
• At restart
When restart, the function blocks connected to process I/O restore to their previous
block mode before the power failure.
■ Status of SEBOL at Start Operation

The table below shows the behavior of FCS regarding to SEBOL when the FCS is under-
going Initial Cold Start or Restart.
Table Status of SEBOL at Start Operation
SEBOL Initial state (STATUS = STOP) Continues from the current statement.
B020114E.EPS

<B2.2 Start Operation of PFCS and SFCS I/O Modules> B2-17
B2.2 Start Operation of PFCS and SFCS I/O Modules

Start operation for I/O module includes Initial Cold Start (MAN) and Restart (AUT).
■ Initial Cold Start for I/O Module : PFCS/SFCS

Initial cold start for I/O module is started with the value the I/O module actually inputs/
outputs at operation start. Initial cold start is executed for recovery from prolonged power
failure, power disconnection for maintenance or termination of transmission due to tran-
sient failure.
● Input Operation : PFCS/SFCS

After initial cold start, the read data are set to 0 until the I/O module is started to allow data
to be obtained by communication. The data status becomes NRDY.
● Output Operation : PFCS/SFCS

The figure below shows the operation of analog output at the Initial Cold Start.
Power failure Recovery
CPU operating status
I/O module
Output falls at power failure
After recovery, the mode becomes

MAN and output tracking occurs. B020201E.EPS
Figure Analog Output at Initial Cold Start : PFCS/SFCS
At the completion of maintenance or power recovery, output is started from tight shut status
for analog output or from OFF status for contact output. For recovery from termination of
transmission due to transient failure, output is started with the actual output value of I/O
module immediately before recovery.

<B2.2 Start Operation of PFCS and SFCS I/O Modules> B2-18
■ Restart for I/O Module :PFCS/SFCS
Restart for I/O module is a start operation in which output operation is started by matching
the output value with the output value immediately before power lost. Restart is executed at
recovery from momentary power failure.
● Input Operation :PFCS/SFCS

After recovery from momentary power failure, the input data before the failure are stored
until I/O module is restarted. However, the data status is NRDY.
● Output Operation :PFCS/SFCS

The figure below shows the analog output at restart.
Power failure Recovery
I/O module
Output falls at power failure

Continues control in
AUT mode after recovery
B020202E.EPS
Figure Analog Output at Restart : PFCS/SFCS

<B2.3 Start Operation of KFCS2 and KFCS Nodes> B2-19
B2.3 Start Operation of KFCS2 and KFCS Nodes

Two types of start operation–initial cold start (MAN) and restart (AUT)–are available
for the nodes (local node and remote node).
■ Start Operation of the Nodes : KFCS2/KFCS £

▼ Node Momentary Power Failure Tolerant Time
Two types of start operation–“initial cold start” and “restart”–are available for the nodes
(local node and remote node). These two types of start operation are executed when a
node that is not responding is recovered after the occurrence of an error. The type of start
operation to be executed is determined by the duration the node does not respond.
When the following node errors occur, the nodes are placed in the no-response state.
• Single power failure of either local node or remote node
• Breakdown of the nodes at both sides of dual-redundant SB401 or EB501
• Disconnection of transmission of the nodes at both sides of the extended serial
backboard bus (ESB bus)
TIP
“Node start operation” does not take place in case of system power failure (simultaneous power failure of
both the FCU and node) even when a power failure occurs in a node. The operation relative to system
power failure will be performed.
When the no-response time of the node is longer than the “node momentary power failure
tolerant time,” it is called prolonged node power failure. The initial cold start operation of the
node is executed when the node is recovered from the prolonged node power failure.
When the no-response time of the node is shorter than the “node momentary power failure
tolerant time,” it is called momentary node power failure. The restart operation of the node
is executed when the node is recovered from a momentary node power failure.
The “node momentary power failure tolerant time” is set using the FCS Constants Builder. It
can be set in the range between 0 and 4 seconds. If 0 is set, the start operation of the node
is always set to the “initial cold start.” The default value is 2 seconds.
TIP
When the node momentary power failure tolerant time is set as 2 seconds, and if the node power failure
elapsed for 2 scan cycles (two one-second scan cycles), the node is treated as prolonged power failure.
However, node momentary power failure is detected by each two seconds, the minimum tolerant time
varies between 2 to 4 seconds.

■ Initial Cold Start of the Node : KFCS2/KFCS £
The initial cold start operation of a node (local node or remote node) starts an output
operation with the value that is actually output by the output module in the node. This type
of start operation is used when the node recovers from disconnection of transmission
caused by transient problems as well as when the power to the node is recovered from a
prolonged power failure.
The output operation that is performed in the initial cold start operation of the node consists
of the following:
• Starts output from the tight-shut state (analog output) or OFF state (contact output)
when restoring the power.
• Starts output from the actual output value of PI/O just before a recovery from problem
when recovering from a transient problem.
■ Restart Operation of the Nodes : KFCS2/KFCS £

The restart operation of a node (local node or remote node) initiates an output operation
after restoring the output to the value that was output immediately before the failure by the
output module in the node. This type of start operation is used when recovering from a
momentary power failure.
The output operation that is performed in the restart operation of the node consists of the
following:
• Starts output after restoring the output to the last output value that was saved just
before the power failure.
• Although the output data in the output module is volatilized due to power failure, the
CPU on the FCU side restores the output of the output module to the last output value.

■ Details of the Start Operation of the Nodes : KFCS2/KFCS £
The FCU operates as indicated in the table below from the occurrence of a node (local
node or remote node) abnormality until the start operation of the node is performed.
Table Process Control I/O States at the Time of Node Abnormality and when Recovering : KFCS2/
KFCS £
When abnormal When recovering (node start operation)
Node
abnormality Function Function
Process data Process data
block operation block operation
Generates Reads a new input value.
Prolonged The data status is Tracks a field
IOP/OOP. Tracks a field output value
power failure BAD (*1). output value.
MAN fallback (*1) for output.
Retains the previous value
Retains the previous Retains the previous
Momentary for an input value. Resumes output and
value. The data status PV value. Continues
power failure Re-outputs the previous continues operation.
is NRDY. operation.
value for output.
B020301E.EPS
*1: The process data and function block operation at the time of a prolonged node power failure will be the process data
and function block operation at the time of a momentary node power failure, until the elapsed time of node’s no-
response period reaches the momentary node power failure identification time.
Table Process I/O Statuses during the Start Operation of the Nodes : KFCS2/KFCS £
Item Initial cold start of node Restart of node
Analog input Newly reads. Newly reads.
Status input Newly reads. Retains the previous value.
Newly reads. Newly reads.
Push-button input
(Input at the time of abnormality is invalid.) (Input at the time of abnormality is invalid.)
Retains the PV value. Retains the PV value.
Pulse train input Input during power failure is invalid. Input during power failure is invalid.
Pulse counting restarts. Pulse counting restarts.
Analog output Back-calculates IOM’s output value (*1), Re-outputs the output value prior to
Status output then tracks. the power failure.
Pulse width output Output resets. Output restarts after output resets.
Time-proportioning
Output resets if power supply of I/O Output restarts after output resets if
ON/OFF output
modules also fails. power supply of I/O modules also fails.
Retains the previous input value until Retains the previous input value until
Fieldbus communication Fieldbus communication resumes. Fieldbus communication resumes.
ALF111 Tracks the output value of the field Tracks the output value of the field
device. Then, resumes output. device. Then, resumes output.
Retains the previous input value until Retains the previous input value until
the RS communication module is the RS communication module is
Subsystem started up. started up.
communication Re-outputs the output value prior to the
ALR111, ALR121 Tracks the output value data on the power failure. However, it takes some
subsystem side. Then, resumes output. time until the RS communication
module is started up.
B020302E.EPS
*1: The output values of the IOM (Input Output Module) vary according to the causes of breakdowns and the setting
contents of the IOM.
SEE ALSO
For the output state of the IOM at probrem occurrence, see the following:
“■ Output State of the I/O Module during the Occurrence of an Error : KFCS2/KFCS £” in B3.4, “Com-
mon Operation of the I/O Module at Probrem Occurrence”

■ Start Operation when Recovering from a Standalone Power Failure of
the Remote Node : KFCS2/KFCS £
When the power to a remote node is recovered from the standalone power failure state, the
operation is performed in accordance with the “Node Start Operation.” However, it takes
some time from the power recovery of the remote node until an EB401 on a local node is
started.
The time it takes to start the EB401 is as follows:
• When the duration of a power failure is within 16 seconds
It takes approximately 200 ms to start the EB401.
• When the duration of a power failure exceeded 16 seconds
It may take approximately 4 seconds to start the EB401.
If a prolonged node power failure occurs due to a prolonged power failure of a remote
node, the function block that is connected to the terminal point of the I/O module on that
remote node will perform an MAN fallback after going through IOP or OOP.
If an EB401 startup took approximately 4 seconds in a subsequent recovery from a power
failure, the function block will recover from IOP or OOP within 4 to 6 seconds after the
power recovery.
AC power supply
state of remote
node area
Approx. 4 sec
Output value 1.25 mA

(4-20mA) 0 mA
from IOM
Recovery from
power failure
Start output to IO
B020303E.EPS
Figure Operation when Recovering from a Standalone Power Failure of the Remote Node
(Prolonged Power Failure) : KFCS2/KFCS £

<B2.4 Start Operation of LFCS2 and LFCS I/O Units> B2-23
B2.4 Start Operation of LFCS2 and LFCS I/O Units

Two types of start operation–initial cold start (MAN) and restart (AUT)–are available
for the I/O unit.
■ Start Operation of the I/O Unit: LFCS2/LFCS £

Two types of start operation–“initial cold start” and “restart”–are available for the I/O unit.
The type of start operation to be executed is determined by the “start mode” of the I/O unit
and the no-response time.
The “start mode” is set with node properties. Set the momentary I/O unit power failure
identification time in the range of 1 to 16,000 msec, or select [MAN] (manual). The default
value of the momentary I/O unit power failure identification time is 2000 msec.
Table Correspondence between the Start Mode and Start Operation : LFCS2/LFCS £
Start mode Start operation
MAN -
Prolonged I/O unit power failure Initial cold start
Momentary power (no-response detection time ⭌ momentary power failure identification time)
failure identification
time setting Momentary I/O unit power failure
Restart
(no-response detection time < momentary power failure identification time)
B020401E.EPS
■ Initial Cold Start of the I/O Unit : LFCS2/LFCS £

The initial cold start operation of an I/O unit initiates an output operation with the value that
is actually output by the output module in the I/O unit. This type of start operation is used
when the I/O unit is disconnected for maintenance or recovering from disconnection of
transmission due to a transient problem as well as when the power is recovered from a
prolonged power failure.
The output operation that is performed in the restart operation of the I/O unit consists of the
following:
• Starts output from the tight-shut state (analog output) or OFF state (contact output)
when the power is recovered upon completion of maintenance.
• Starts output from the actual output value of PI/O immediately before the recovery of
the problem when recovering from a transient problem.
■ Restart Operation of the I/O Unit : LFCS2/LFCS £

The restart operation of an I/O unit starts an output operation after restoring the output to
the value that was output immediately before the failure by the output module within the I/O
unit. This type of start operation is used when recovering from a momentary power failure.
The output operation that is performed in the restart operation of the I/O unit consists of the
following:
• Starts output after restoring the output to the last output value that was saved just
before the power failure.
• Although the output data in the output module is volatilized due to power failure, the
RIO bus interface card (RB301) independently restores the output of the output
module to the last output value.

<B2.5 Start Operation of KFCS2, KFCS, LFCS2 and LFCS I/O Modules> B2-24
B2.5 Start Operation of KFCS2, KFCS, LFCS2 and

LFCS I/O Modules
In the KFCS or LFCS, the initial cold start operation of the I/O module is performed
when the I/O module is recovered from a breakdown or maintenance.
■ Initial Cold Start of the I/O Module : KFCS2/KFCS/LFCS2/LFCS £

In case of an I/O module breakdown or maintenance, the function block, which is the
connection destination of the I/O module in the FCU, performs an MAN fallback operation.
When the I/O module is recovered from the breakdown or maintenance, the initial cold start
of the I/O module is performed in the FCU, and an input/output operation between the
function block and I/O module will be resumed.
Table Process I/O Statuses in the FCU when Recovering from an I/O Module Failure : KFCS2/
KFCS/LFCS2/LFCS £
When occurred When recovered (initial cold start)
Description
of failure Function Function
Process data Process data
block operation block operation
Reads the new input
I/O module The data status is value. Tracks the field
MAN fallback
abnormality BAD. Tracks the field output output value.
value for output.
B020501E.EPS

<B3. Operation at Error Occurrence> B3-1
B3. Operation at Error Occurrence

Operation at error occurrence refers to the operation upon detecting an error in the
process I/O or processor unit during system operation.
The following are types of operations performed at error occurrence:
• Operation based on the power failure/error mode
• Common operation of the I/O module when a problem occurs (KFCS2, KFCS
only).
• Operation at error detection while downloading to I/O module
• Operation of communication I/O module
TIP
The term PI/O used in this chapter denotes “process I/O.”

■ Operation Based on the Power Failure/Error Mode : PFCS/SFCS
The CS 1000 has several power failure/error modes, corresponding to each individual error
type. The system operation appropriate for each power failure/error mode will be executed
when an error is detected.
Table System Operations Based on Power Failure/Error Mode : PFCS/SFCS
I/O module output operation FCS control operation
Power failure/error mode
When occurred When recovered When occurred When recovered
FCS power failure - Initial cold start or restart - Initial cold start or restart
Termination of CPU operation Output fallback Resume output - Initial cold start
Processor unit control right transfer No change No change No change No change
I/O module failure - Initial cold start MAN fallback Resume output
I/O module maintenance/failure - Initial cold start MAN fallback Resume output
B030001E.EPS
SEE ALSO
• For the details of system operation at FCS power failure status, see the following:
B3.1, “Operation at Power Failure”
• For the details of system operation at termination of CPU operation and Processor unit control right switch
status, see the following:
B3.2, “Operation at CPU Failure”
• For the details of system operation at I/O module failure and I/O module maintenance/breakdown sta-
tus, see the following:
B3.3, “Operation at Error Occurrence in Process I/O Module”

■ System Operation Based on the Power Failure/Error Mode : KFCS2/
KFCS £
Various power failure and breakdown modes are provided for different types of problems
such as power failure and error. When a problem occurs, the system operation is per-
formed according to the applicable power failure/breakdown mode.
Table System Operation by Power Failure and Error Modes : KFCS2/KFCS £
Process I/O output operation FCU control operation
Power failure and error modes
All IOMs of the
subject local node Operation at the time of a
–
follow the FCU prolonged node power
Local node standalone control operation. Initial cold start of a node,
failure, or operation at the
power failure or restart of a node
All IOMs of the lower All IOMs of the time of a momentary node
remote node perform lower remote node power failure
output fallback. resume output.
Operation at the time of a
prolonged node power
Remote node standalone Follows the FCU Initial cold start of a node,
– failure, or operation at the
power failure control operation. or restart of a node
time of a momentary node
power failure
All IOMs lower than
Follows the FCU Initial cold start of an FCS,
Power failure in FCU alone the FCU perform –
control operation. or restart of an FCS
output fallback.
Follows the FCU Initial cold start of an FCS,
System power failure – –
control operation. or restart of an FCS
All IOMs lower than
Follows the FCU
Termination of CPU operation the FCU perform – Initial cold start of an FCS
control operation.
output fallback.
FCU control right transfer No change No change No change No change
Subject IOM
I/O module Operation at the time of Initial cold start of an I/O
performs Initial cold start
maintenance/breakdown an I/O module failure module
output fallback.
All IOMs lower than Operation at the time of a
Follows the FCU
Termination of SB301 operation the FCU perform prolonged node power Initial cold start of a node
control operation.
output fallback. failure
All IOMs lower than Operation at the time of a
Follows the FCU
Termination of EB401 operation the EB401 perform prolonged node power Initial cold start of a node
control operation.
output fallback. failure
All IOMs of the Operation at the time of a

subject local node prolonged node power
Communication error with Follows the FCU Initial cold start of a node,
and lower remote failure, or operation at the
the local node (*1) control operation. or restart of a node
node perform time of a momentary node
output fallback. power failure
Operation at the time of a

All IOMs of the
prolonged node power
Communication error with subject node Follows the FCU Initial cold start of a node,
failure, or operation at the
the remote node (*2) perform control operation. or restart of a node
time of a momentary node
output fallback.
power failure
B030002E.EPS
*1: The communication error with the local node denotes a communication problem between an FCU and a local node
such as the disconnection of transmission of a extended serial backboard bus (ESB bus) and the abnormality of an
SB401 that is mounted to a local node.
*2: The communication error with the remote node denotes a communication problem between a local node and a remote
node such as the disconnection of transmission of an enhanced remote I/O bus and the abnormality of an EB501 that
is mounted to a remote node.
Note: The term operation stop used in the power failure and breakdown modes denotes the case when the operation stops
due to breakdown or mounting/dismounting of hardware. It does not include a power failure.

SEE ALSO
• For details on the system operation associated with the local node standalone power failure, remote node
standalone power failure, FCU standalone power failure and system power failure state, see the following:
• For details on the system operation associated with the CPU operation stop and FCU control right switch
state, see the following:
• For details on the system operation associated with the I/O module maintenance/breakdown, SB301
operation stop, EB401 operation stop, communication error with the local node, and communication error
state with the remote node, see the following:
B3.3, “Operation at Error Occurrence in Process I/O Module”
The range of effects to the I/O module varies as follows according to the power failure and
breakdown modes:
Table Range of Effects at the Time of Abnormality : KFCS2/KFCS £
Power failure and breakdown modes Range of effects
Power failure in FCU alone
Termination of CPU operation All IOMs lower than the FCU
Termination of SB301 operation
Direct connection node standalone IOM of the subject direct connection node,
power failure and IOMs of all remote nodes lower than
Communication error with the direct an EB401 mounted to the subject direct
connection node connection node
Termination of EB401 operation IOMs of all remote nodes lower than the subject EB401
Remote node standalone power failure
Communication error with the remote IOM of the subject remote node
node
I/O module maintenance/error Subject IOM
B030003E.EPS

■ Operation Based on the Power Failure/Error Mode : LFCS2/LFCS £
The CS 3000 has several power failure/error modes, corresponding to each individual error
type. The system operation appropriate for each power failure/error mode will be executed
when an error is detected.
Table System Operations Based on Power Failure/Error Mode : LFCS2/LFCS £
I/O module output operation FCS control operation
Power failure/error mode
Operation for
Power failure in PI/O alone - Initial cold start or restart PI/O power Resume output
failure
Power failure in FCU alone Output fallback Resume output - Initial cold start or restart
System power failure - Initial cold start or restart - Initial cold start or restart
Termination of CPU operation Output fallback Resume output - Initial cold start
FCU control right transfer No change No change No change Restart
I/O module maintenance/error - Initial cold start MAN fallback No change
Node maintenance - Initial cold start MAN fallback Resume output
PI/O failure - Initial cold start MAN fallback Resume output
Termination of PI/O operation - Initial cold start MAN fallback Resume output
Termination of RIO bus
Output fallback Resume output MAN fallback Resume output
transmission
RB301 control right transfer No change No change No change Restart
B030004E.EPS
SEE ALSO
• For the details of system operation upon power failure in PI/O or FCU alone and system power failure,
see the following:
• For the details of system operation at termination of CPU operation stop and FCU control right transfer
status, see the following:
• For the details of system operation during I/O module maintenance/error, node maintenance and RB301
control right transfer as well as at PI/O failure, termination of PI/O operation and termination of RIO bus
transmission, see the following:
B3.3, “Operation at Error Occurrence In Process I/O Module”

■ Operation of I/O Module when Downloading is Performed
When downloading of engineering data is performed during system operation, operation of
the I/O module subject to downloading changes.
Operation of the I/O module subject to downloading differs depending on whether or not
off-line downloading is performed.
SEE ALSO
For the details of I/O module operation during download, see the following:
B3.5, “Operation of I/O Module when Downloading is Performed”
■ Operation of Communication I/O Module

When a failure occurs within the system during system operation using subsystem commu-
nication, operation of the communication I/O module will be affected.
Operation of the communication I/O module at error occurrence varies depending on the
type of error occurred.
SEE ALSO
For the details of communication I/O module operation at error occurrence, see the following:
B3.6, “Operation of Communication I/O Module at Error Occurrence”

<B3.1 Operation at Power Failure> B3-7
B3.1 Operation at Power Failure

The following are the power failure modes that may occur during system operation
using CS 1000 or CS 3000.
• FCS power failure (PFCS, SFCS only)
• Local node standalone power failure (KFCS2, KFCS only)
• Remote node standalone power failure (KFCS2, KFCS only)
• PI/O standalone power failure (LFCS2, LFCS only)
• FCU standalone power failure (KFCS2, KFCS, LFCS2, LFCS only)
• System power failure (KFCS2, KFCS, LFCS2, LFCS only)
This section describes system operation for each power failure mode.
■ System Operation at FCS Power Failure : PFCS/SFCS

“FCS power failure” is a state in which the FCS experiences power failure and recovery
from a power failure. At this time, the CPU and I/O module stop operating.
FCS power failure occurs when the FCS power supply fails or malfunctions.
As for the control operation of the FCS and the output operation of the I/O module, either
the initial cold start operation or restart operation will be performed, depending on the start
condition setting of the FCS and the duration of the power failure.
SEE ALSO
• For the initial cold start operation and restart operation, see the following:
B2.1, “FCS Start Operation”
• For the initial cold start operation and restart operation of the I/O module, see the following:
B2.2, “Start Operation of PFCS and SFCS I/O Modules”

■ System Operation in Local Node Power Failure State : KFCS2/KFCS £
The local node power failure state denotes a state in which only the power to a local node
goes off and then it is recovered. The operation continues in other local nodes in which a
power failure has not occurred, ESB bus communication, and a field control unit (FCU) at
this time.
An output fallback operation is performed in a remote node lower than the local node in
which a power failure has occurred, when the line loss detection time (4 seconds) has
elapsed from the power failure.
Furthermore, the FCU performs the following start operation for the Local node when the
power is recovered.
• In case of prolonged node power failure: Initial cold start of the node
• In case of momentary node power failure: Restart of the node
SEE ALSO
For details on the initial cold start operation and restart operation of the node, see the following:
B2.3, “Start Operation of KFCS2 and KFCS Nodes”
The local node standalone power failure state occurs in cases where the power supply to a
local node fails or the breakdown of the power supply area of a local node occurs.
SEE ALSO
• The fallback actions of the I/O modules in remote nodes at node power supply failure are the same as
the fallback actions at the FCU power failure. For more information about I/O module fallback actions,
see the following at later part of this chapter:
“● Output Operation of the Process I/O - FCU Power Failure : KFCS2/KFCS” in section “■ System Op-
eration in FCU Power Failure State : KFCS2/KFCS”
• For more information about the I/O module output at fallback action, see the following:
“■ Output State of the I/O Module during the Occurrence of an Error : KFCS2/KFCS” in B3.4 “Common
Operation of the I/O Module at Problem Occurrence”

● Output Operation of the Local Node Area - Local Node Power Failure :
KFCS2/KFCS £
The following figure shows the I/O module output status and function block operation when
a prolong node power failure occurs:
Momentary node power failure

tolerant time
AC power supply
state of the local
node area
Output during
IOM restart
Output value 1.25mA
(4-20mA) from 0 mA
the IOM
Block mode of AUT AUT MAN (IMAN) MAN

a function block
MAN fallback PI/O start

B030101E.EPS
Figure In Case of Prolonged Local Node Power Failure : KFCS2/KFCS £
When the power to a local node recovers after a prolonged local node power failure, the I/O
module that is mounted to that local node will be restarted.
SEE ALSO
For the output status of the I/O module from the restart of the I/O module to the start of output from the
FCU by FCU initial cold start, see the following:
B3.4, “Common Operation of the I/O Module at Problem Occurrence”
The following figure shows the I/O module output status and function block operation when
a momentary local node power failure occurs:
Momentary local node power failure

tolerant time
AC power supply
state of the local
node area
Output value
(4-20mA)
Resumes output
from the IOM
with the output value
prior to power failure
Block mode of AUT AUT AUT

a function block
PI/O start
(re-output)
B030102E.EPS
Figure In Case of Momentary Local Node Power Failure : KFCS2/KFCS £
TIP
For the pulse width output and time-proportioning ON/OFF output in case of a momentary local node
power failure, output is resumed from the output reset status when the power is recovered.

■ System Operation in the Remote Node Standalone Power Failure State:
KFCS2/KFCS £
The remote node standalone power failure state denotes a state in which only the power to
a remote node goes off and then it is recovered. The operation continues in local nodes,
other remote nodes in which a power failure has not occurred, ESB bus communication,
ER bus communication, and a field control unit (FCU) at this time.
The remote node standalone power failure state occurs in cases where the power to a
remote node fails or the breakdown of the power supply area of a remote node occurs.
The system operation in the remote node standalone power failure state is the same as
that in the local node standalone power failure state. However, after the remote node’s
power is recovered, it takes some time before the EB401 of the local node higher than that
remote node starts up.
SEE ALSO
For the time required for the EB401 to start up, see the following:
“■ Start Operation when Recovering from a Standalone Power Failure of the Remote Node : KFCS2/
KFCS” in B2.3, “Start Operation of KFCS2 and KFCS Nodes”
■ System Operation at Power Failure in PI/O Alone : LFCS2/LFCS £

“Power failure in PI/O alone” is a state in which the process I/O area experiences a power
failure and recovery at an individual node. At this time, operation continues at the RIO bus
communication, field control unit (FCU) and nodes other than the one experiencing a
power failure.
A power failure in PI/O alone occurs when a power failure occurs in the power supply for a
specific node or the power supply for the node interface unit (NIU) malfunctions.
● Output Operation of Process I/O Module Area - Power Failure in PI/O Alone :
LFCS2/LFCS £
As for the output operation of the process I/O area, either the initial cold start operation or
restart operation of the I/O unit will be performed, depending on the start mode setting of
the I/O unit and the duration of the power failure.
SEE ALSO
For the initial cold start operation and restart operation of the I/O unit, see the following:
B2.4, “Start Operation of LFCS2 and LFCS I/O Units”

The figure below shows the output signal operation of analog output module at power
failure in PI/O alone.
PI/O AC PI/O AC
power supply status power supply status
Momentary
power failure
detection time
Module output Module output
signal level signal level
Function block Function block

mode AUTO AUTO IMAN (MAN) MAN mode AUTO AUTO AUTO
Initialization manual PI/O PI/O

MAN fallback Initial cold start restart
Prolonged power failure Momentary power failure

(prolonged power failure timeⱖ (prolonged power failure time <
momentary power failure tolerant time) momentary power failure tolerant time)
B030103E.EPS
Figure Output Signal Operation when Start Condition is Set to TIME : LFCS2/LFCS £
PI/O AC power
supply status
Module output
signal level
Function block
mode AUTO IMAN (MAN) MAN
Initialization manual PI/O

MAN fallback Initial clod start
B030104E.EPS
Figure Output Signal Operation when Start Condition is Set to MAN (Initial Cold Start) :
LFCS2/LFCS £
● Control Operation of FCU - Power Failure in PI/O Alone : LFCS2/LFCS £

The field control unit (FCU) executes a PI/O power failure operation when a power failure
occurs at the connection destination node of a function block that is directly connected for
the process I/O.
Output will resume upon power recovery.
PI/O power failure operation is performed as shown below, based on the type of start
operation defined for each I/O unit (IOU).
• When the IOU start operation is set to MAN (initial cold start)
MAN fallback will be executed, followed by initialization manual (IMAN).
• When the IOU start operation is set to TIME
Initialization manual (IMAN) will be executed at the point the power failure time ex-
ceeds the momentary power failure tolerant time (timer set value). MAN fallback
operation will then be executed.

■ System Operation in FCU Power Failure State : KFCS2/KFCS £
The FCU power failure state denotes a state in which only the power to the FCU goes off
and then it is recovered. The operation continues in the process I/O area at this time.
However, the operation of both the ESB bus interface card (SB301) to which the power is
supplied from the FCU and the ESB bus communication stops.
In addition, the FCU performs either an initial cold start operation or restart operation of the
FCU when the power is recovered, according to the start condition setting of the FCU and
the duration of the power failure.
SEE ALSO
For the initial cold start operation and restart operation of the FCU, see the following:
The FCU power failure state occurs when a power failure or breakdown occurs in the
power supply area of the FCU.
● Output Operation of the Process I/O - FCU Power Failure : KFCS2/KFCS

£
An output fallback operation is performed in all I/O modules lower than the FCU in the
power failure state while in an FCU standalone power failure. The output fallback operation
is a function that maintains the current value of the output of an I/O module or forcibly
changes it to the specified value while an abnormality that affects the I/O module occurs.
The output fallback operation of the I/O module is set in the detailed settings of the IOM
Builder.
• Set either [Maintain current value] or [Output data] for the output fallback.
• If [Output data] is set for the output fallback, set the output value in the range between
-17.1875 and 112.5%.
SEE ALSO
For details on the output fallback operation of the I/O module, see the following:
“■ Output State of the I/O Module during the Occurrence of an Error : KFCS2/KFCS” in B3.4, “Common

The following figure shows the output operation from the I/O module in the case of the FCS
initial cold start operation:
• When [Maintain current value] is set for the output fallback:
The output data is shown in a solid line below. The output value just before the occur-
rence of a power failure is retained during FCU power failure, and output is resumed
with the retained value when the power to the FCU is recovered.
• When [Output data] is set for the output fallback:
The fallback output value (dashed line in the figure) is output when the power failure
time exceeds the line loss detection time (4 seconds). Output is resumed with the
fallback output value when the power is recovered. If the power failure time does not
exceed the line loss detection time, the output operation will be the same as when
[Maintain current value] is set for the output fallback.
FCU momentary power failure tolerant time

(MAN: 0 sec, TIME: momentary power failure
identification time setting value (default: 2 sec))
AC power supply
state of the FCU
Line loss detection time (default: 4 sec)
Output value
(4-20mA) When the fallback output value
from the IOM is specified.
Resumes output to the IOM.

B030105E.EPS
Figure Initial Cold Start Operation when an FCU Standalone Power Failure Occurs : KFCS2/KFCS
£

restart operation:
The output value is shown in a solid line below. The output value just before the
occurrence of a power failure is retained during FCU power failure, and output is
resumed with the retained value when the power to the FCU is recovered.
time exceeds the line loss detection time (4 seconds). The output value just before the
occurrence of the power failure is re-output when the power is recovered, and output
is resumed with that value. If the power failure time does not exceed the line loss
detection time, the output operation will be the same as when [Maintain current value]
is set for the output fallback.
AC power supply
state of the FCU

When the fallback output value is specified.
Output value
(4-20mA) Resumes output with the output value
from the IOM when a power failure occurred.

B030106E.EPS
Figure Restart Operation when an FCU Standalone Power Failure Occurs : KFCS2/KFCS £
As for the FCS restart operation when the duration of an FCS power failure has exceeded
16 seconds, the FCU starts a control operation 5 seconds after a power recovery. There-
fore, it will be as if the power failure is approximately 5 seconds longer than the duration of
the actual power failure.

■ System Operation at Power Failure in FCU Alone : LFCS2/LFCS £
“Power failure in FCU alone” is a state in which an independent field control unit (FCU)
experiences a power failure and recovery. At this time, the operation of the process I/O
area continues, but operation will stop in the RIO bus interface card (RB301), for which
power is supplied from the FCU, and RIO bus communication.
In addition, the FCU performs either an initial cold start or restart of the FCS when the
power is recovered, according to the start condition setting of the FCS and the duration of
the power failure.
SEE ALSO
For the initial cold start operation and restart operation of the FCS, see the following:
Power failure in FCU alone occurs when power failure or malfunction occurs in the power
supply area of FCU.
● Output Operation of Process I/O Area - Power Failure in FCU Alone :

LFCS2/LFCS £
An output fallback operation is performed in all I/O modules lower than the FCU in the
power failure state while in an FCU standalone power failure. The output fallback operation
is a function that maintains the current value of the output of an I/O module or forcibly
changes it to the specified value while an abnormality that affects the I/O module occurs.
The output fallback operation in I/O module area can be set in the detail setting on the IOM
Builder.
• When check the [Set Fallback] item, it is required to check the option button for either
[Maintain Current Value] or [Output data].
• When not check the [Set Fallback] item, the current value will be held.

initial cold start operation:
time exceeds the line loss detection time (4 seconds). Output is resumed with the
fallback output value when the power is recovered. If the power failure time does not
exceed the line loss detection time, the output operation will be the same as when
[Maintain current value] is set for the output fallback.
FCU momentary power failure tolerant time

(MAN: 0 sec, TIME: momentary power failure
identification time setting value (default: 2 sec))
AC power supply
state of the FCU
Output value
(4-20mA) When the fallback output value
from the IOM is specified.

B030107E.EPS
Figure Initial Cold Start Operation when an FCU Standalone Power Failure Occurs : LFCS2/LFCS
£
restart operation:
time exceeds the line loss detection time (4 seconds). The output value just before the
occurrence of the power failure is re-output when the power is recovered, and output
is resumed with that value. If the power failure time does not exceed the line loss
detection time, the output operation will be the same as when [Maintain current value]
is set for the output fallback.
AC power supply
state of the FCU

When the fallback output value is specified.
Output value
(4-20mA) Resumes output with the output value
from the IOM when a power failure occurred

B030108E.EPS
Figure Restart Operation when an FCU Standalone Power Failure Occurs : LFCS2/LFCS £

■ System Operation in the System Power Failure State : KFCS2/KFCS £
The system power failure state denotes a state in which the power to both the process
control I/O area and the FCU goes off and then it is recovered almost at the same time. The
process control I/O area, ESB bus communication and all FCU functions stop. In addition, a
state in which each component operates independently exists at a moment of a power
failure and recovery.
Because the power failure time count of the local node or remote node does not include the
duration of an FCU’s power failure, the system operation is determined by the duration of
the FCU’s power failure even for the system power failure, in the same manner as for the
FCU standalone power failure.
At the time of a power failure, the FCU performs FCS initial cold start operation or restart
operation according to the start condition setting of the FCS and the duration of the power
failure.
SEE ALSO
For the FCS initial cold start operation and restart operation, see the following:
The system power failure state occurs in cases such as a power failure of the entire instru-
ment power supply.
IMPORTANT
If the time lag of a power failure and power recovery between the process I/O area and the
FCU is substantial, the momentary operation of power failure and power recovery will be
the same as the case when a local node standalone power failure, a remote node
standalone power failure and an FCU standalone power failure have occurred separately.

● Operation for FCS Initial Cold Start - System Power Failure : KFCS2/KFCS
£
The following figure shows an example of the I/O module output operation and function
block operation for FCS initial cold start.
AC power supply
state of the FCU
and PI/O area Wind-up
time Output at IOM restart
Output value 1.25 mA Starts output

(4-20mA) 0 mA
from the IOM
Block mode of AUT MAN (IMAN) MAN

function block
Approx. 4 seconds from a power
recovery in case of a prolonged
PI/O start power failure of a remote node
B030109E.EPS
Figure FCS Initial Cold Start Operation when a System Power Failure has Occurred : KFCS2/
KFCS £
When the power is recovered from a system power failure, an FCS initial cold start opera-
tion is executed in the FCU, and the I/O module is restarted in the process control I/O area.
Subsequently, output from the function block on the FCU side to the process I/O area is
initiated.
If a power failure has occurred in a remote node, it takes approximately 200 ms or 4 sec-
onds, depending on the duration of the power failure, until the EB401 higher than that
remote node starts up after the power recovery.
SEE ALSO
For the output status of the I/O module from the restart of the I/O module to the start of output from the
FCU by FCU initial cold start, see the following:
IMPORTANT
• Data reference and data setting cannot be performed from the initialization sequence
table for the I/O module of a remote node. Data reference and data setting should be
performed after wind-up is complete, as needed.
• If a remote node had a prolonged power failure, it takes approximately 5 seconds to
resume the communication between that remote node and the FCU. The FCU masks
(does not detect) any remote node abnormality for these 5 seconds. If there is a
remote node abnormality, it will be notified after approximately 5 seconds.
However, for a remote node that starts up faster than 5 seconds, an I/O operation is
initiated upon the remote node startup. On the contrary, for a remote node that starts
up slower than 5 seconds, the previous I/O value is retained, and the output value is
tracked by executing a wind-up IMAN operation after the remote node is started up.
• If a system power failure occurred during a periodical inspection, etc., the startup time
of a remote node can be reduced to 200 ms by recovering the power to the remote
node side first.

● Operation for FCS Restart - System Power Failure : KFCS2/KFCS £
For an FCS restart operation when the duration of an FCU's power failure was within 16
seconds, the output value prior to the power failure is re-output to the process I/O area after
the FCU, which is recovered from the power failure, is started.
AC power supply
state of the FCU
and PI/O area
Output value
(4-20mA)
from the IOM
Block mode of AUT AUT

a function block
Starts FCS operation

(re-output)
B030110E.EPS
Figure FCS Restart Operation when a System Power Failure has Occurred (Power Failure
Duration of within 16 Sec) : KFCS2/KFCS £
As for the FCS restart operation when the duration of an FCS power failure has exceeded
16 seconds, the FCU starts a control operation 5 seconds after a power recovery. There-
fore, it will be as if the power failure is approximately 5 seconds longer than the duration of
the actual power failure.
AC power supply
state of the FCU
and PI/O area The time required from a power
recovery to re-output is approx.
5 sec if the duration of a power
failure is long.
Output value
(4-20mA)
from the IOM
Block mode of AUT AUT

a function block
Starts FCS operation

(re-output)
B030111E.EPS
Figure FCS Restart Operation when a System Power Failure has Occurred (Power Failure
Duration of 16 Sec or Longer) : KFCS2/KFCS £
IMPORTANT
• Data reference and data setting cannot be performed from the initialization sequence
table for the I/O module of a remote node. Note that if data setting is performed from
the initialization sequence table, the setting for the I/O module of the remote node will
be re-output after the communication of the node is started.
• If a system power failure occurred during a periodical inspection, etc., the startup time
of a remote node can be reduced to 200 ms by recovering the power to the remote
node side first.

● Operation when the Power Failure Tolerant Timing Varies between the
Process I/O Area and the FCU : KFCS2/KFCS £
In a system power failure, even if a power failure occurs in a node, it is not treated as the
duration of a node (local node or remote node) power failure while an FCU is being
stopped.
For instance, if the process I/O area (PI/O area) detects a power failure before the FCU
does, the power failure time (T1) of the PI/O area is measured as shown in the figure
below. This duration is treated as a node standalone power failure time.
In addition, the time (T1) prior to the power failure is reset after the power is recovered, and
the time is remeasured from 0 seconds.
T1
FCU
PI/O
B030112E.EPS
Figure Operation when a System Power Failure has Occurred (when the PI/O Side Detected a
Power Failure First)
IMPORTANT
In an FCS initial cold start operation when recovering from a system power failure, the FCU
masks any remote node abnormality for approximately 5 seconds after the startup even if
the remote node starts up after the FCU does.

■ System Operation at System Power Failure : LFCS2/LFCS £
“System failure” is a state in which both process I/O area and field control unit (FCU)
experience a power failure and recovery at nearly the same time. At this time, all functions
of process I/O area, RIO bus communication and FCU will stop. Further, there exists a
state in which each component operates independently when a power failure or recovery
occurs.
System power failure tends to occur when the power supply for the entire instrumentation
fails.
IMPORTANT
If the time lag of a power failure and power recovery between the process I/O area and the
FCU is substantial, the moment operation of power failure and power recovery will be the
same as the case when a PI/O standalone power failure and an FCU standalone power
failure have occurred separately.
● Power Failure Time at System Power Failure : LFCS2/LFCS £

This section explains how to measure power failure time when system power failure oc-
curs, using as an example of an analog output module directly connected to the PID con-
troller block (PID) and PID block.
FCU can calculate actual power failure time elapsed at the time of power recovery by itself
based on the internal clock of RIO bus interface card (RB301). Also, at power failure in PI/O
alone, RB301 uses its own clock to measure the actual power failure time for PI/O. In the
case of system power failure, on the other hand, there may exist a case in which actual
power failure time of PI/O cannot be measured because FCU itself ceases to function.
To cope with this, PI/O power failure time (T) at system power failure is defined as follows:
T = T1 + T2 + T3
T1: Power failure time of FCU
T2: Power failure duration of PI/O before FCU power failure
T3: Power failure duration of PI/O after FCU power recovery
PI/O recovery timing
T1 T1
FCU FCU
T3
PI/O PI/O
T1 T1
FCU FCU
T2 T3 T2
PI/O PI/O
B030113E.EPS
Figure Power Failure Time at System Power Failure : LFCS2/LFCS £

● PI/O and FCU Start Operations at System Power Failure : LFCS2/LFCS £
This section explains operations when process I/O area and FCU recovered almost at the
same time, using as an example of an analog output module which is directly connected to
the PID Controller Block (PID) and PID block.
The output status immediately after PI/O power recovery and the MV value status in the
function block vary depending on the combination of PI/O and FCU start operations.
Table Output Operation Immediately after PI/O Power Recovery at System Power Failure :
LFCS2/LFCS £
FCS start operation
PI/O start operation
Initial cold start Tight shut status MV value before power failure
Restart Tight shut status MV value before power failure
B030114E.EPS
Table MV Values in Function Blocks Immediately after Recovery from System Power Failure :
LFCS2/LFCS £
FCS start operation
PI/O start operation
Initial cold start 0% MV value before power failure
Restart 0% MV value before power failure
B030115E.EPS
• When FCS is in [Restart] startup mode, the function blocks connected to process I/O
restore to their previous block mode before the FCU alone had the power failure
regardless the elapsed time period of the power failure. However, when the power
failure occurred in the PI/O area alone, there is possibility that the function blocks can
not restore to their previous block mode.
SEE ALSO
For details on PI/O start action when power failure occurs in the PI/O area alone, see the following
previous section:
“■ System Operation at Power Failure in PI/O Alone”
• If the start operation (initial cold start/restart) at power recovery differs between the
PI/O and FCU areas, start operations from system power failure and from power
failure in the PI/O alone will also differ. Normally, the start modes for PI/O and FCU
areas are set so that the same start processing–either the initial cold start or restart–
will be performed when the power recovers. Upon completion of the FCS start opera-
tion, the operation of individual function blocks can be adjusted via user definition
initialization processing (such as the initialization sequence table), which is executed
prior to normal block processing.
• However, the initial output cannot be adjusted at this time, since the start operation for
the PI/O area is already complete. The FCS start operation can be recognized from
within the user definition initialization processing, but the PI/O start operation cannot.

The figure below shows operation of output signals from an analog output module during
system power failure.
System AC power System AC power

supply status supply status
Output signal Output signal

level of analog level of analog
output module output module
Function block Function block

MV value MV value
Function block AUT MAN Function block AUT

mode mode
• When initial cold start is set for PI/O area and • When initial cold start is set for PI/O area start operation and
FCS start operations restart is set for FCS start operation
• When restart is set for PI/O area start operation and • When restart is set for PI/O area and FCS start operations
initial cold start is set for FCS start operation
B030116E.EPS
Figure Operation of Output Signals from the Analog Output Module During System Power
Failure : LFCS2/LFCS £

<B3.2 Operation at CPU Failure> B3-24
B3.2 Operation at CPU Failure

Listed below are the failure modes when a CPU failure occurs in the processor unit
inside a system:
• Termination of CPU operation
• Processor unit control right transfer (PFCS, SFCS only)
• FCU control right transfer (KFCS2, KFCS, LFCS2, LFCS only)
This section describes system operation in each failure mode.

■ System Operation at Termination of CPU Operation : PFCS/SFCS
“Termination of CPU operation” is a state in which the processor unit is energized but the
CPU stops due to failure or maintenance. At this time, operation continues in the I/O mod-
ule area and VL net interface area.
The termination of CPU operation occurs when the CPU stops, when a CPU failure occurs
in a non-dual-redundant CPU system, or when both CPUs fail in a dual-redundant CPU
system.
● Output Operation of I/O Module Area - Termination of CPU Operation :

PFCS/SFCS
The I/O module area performs output fallback when the termination of CPU operation
occurs. It resumes to output the real output value upon recovery from CPU operation
termination.
Output fallback will be performed four seconds after an error occurrence such as when I/O
module access is interrupted due to termination of CPU operation or when the resetting of
WDT is not detected due to CPU runaway.
If restart is set for the start operation of processor unit, output fallback will be canceled upon
recovery.
On the IOM Builder, I/O module fallback action may be defined.
• When check the “Set Fallback” item, then it is required to check the option button for
either [Maintain Current Value] or [Output data].
• When not check the [Set Fallback] item, the current value will be held.
The following figure shows operation of I/O module area when a CPU error occurs.
CPU error
Line loss time
CPU operating
status 4 seconds
Process I/O
output
Process I/O output fallback

B030201E.EPS
Figure Operation of I/O Module when CPU Fails : PFCS/SFCS
● Control Operation of FCS - Termination of CPU Operation : PFCS/SFCS

The control operation of FCS will be initial cold start when termination of CPU operation is
recovered.

■ System Operation at Termination of CPU Operation : KFCS2/KFCS/
LFCS2/LFCS £
“Termination of CPU operation” is a state in which the field control unit (FCU) is energized
but CPU is stopped due to failure or maintenance. At this time, operation continues in the
process I/O, ER bus communication/RIO bus communication and V net interfaces. But
ESB bus communication stops.
Termination of CPU operation state occurs when CPU stops, when a CPU failure occurs in
a non-dual-redundant CPU system, or when both of the CPUs fail in a dual-redundant CPU
system.
● Output Operation of the Process I/O - Termination of CPU Operation :

KFCS2/KFCS £
When the CPU operation stop state occurs, all the I/O modules lower than the FCU per-
form an output fallback operation after the line loss detection time (4 seconds) has elapsed.
In addition, the output of the process I/O area starts with the actual output value at the time
of recovery by performing an initial cold start of the FCS when recovering from the CPU
operation stop state.
SEE ALSO
For details on the output fallback operation of the I/O module, see the following:

● Output Operation of Process I/O Module - Termination of CPU Operation :
LFCS2/LFCS £
The process I/O module area performs output fallback when termination of CPU operation
occurs.
It resumes to output the real output value upon recovery from CPU operation termination.
On the IOM Builder, I/O module fallback action may be defined.
• When check the [Set Fallback] item, then it is required to check the option button for
either [Maintain Current Value] or “Output data.”
• When not check the “Set Fallback” item, the current value will be held.
The following figure shows operation of process I/O module area when a CPU error occurs.
CPU
operating status
Module output
Module output signal level
signal level
Output fallback
When “No” is When “Output value” is
set for output fallback condition set for output fallback condition
CPU
operating status
: Output according to initial cold start condition
Module output
signal level
Output fallback
When “Retain current value” is

set for output fallback condition
B030202E.EPS
Figure Operation of Process I/O Module Area when CPU Fails : LFCS £
● Control Operation of FCU - Termination of CPU Operation : KFCS2/KFCS/

LFCS2/LFCS £
The control operation of FCU will be initial cold start when termination of CPU operation is
recovered.

■ System Operation at Processor Unit Control Right Transfer : PFCS/SFCS
“Processor unit control right transfer” is a state in which the control side CPU stops func-
tioning and the standby CPU assumes control. Operation continues in the process I/O
before and after transfer of the control right occurs.
Processor unit control right transfer occurs when an error is detected in the self-diagnostics
of a processor unit having dual-redundant CPU.
■ System Operation at FCU Control Right Transfer : KFCS2/KFCS/LFCS2/

LFCS £
“FCU control right transfer” is a state which the control side CPU stops functioning and the
standby CPU assumes control. Operation continues in the process I/O bus communication,
ER bus communication and RIO bus communication before and after the transfer of control
right occurs. ESB bus communication switches to another SB301 in accordance with
control right switching of CPU.
FCU control right transfer occurs when an error is detected in the self-diagnostics of a field
control unit (FCU) having dual-redundant CPU.

<B3.3 Operation at Error Occurrence in Process I/O Module> B3-29
B3.3 Operation at Error Occurrence in Process I/O

Module
Listed below are the failure modes when an error occurs in the process I/O in a
system using CS 1000 or CS 3000:
• I/O module breakdown (PFCS, SFCS only)
• I/O module maintenance/breakdown
• SB301 operation stop (KFCS2, KFCS only)
• EB401 operation stop (KFCS2, KFCS only)
• Communication error with the local node (KFCS2, KFCS only)
• Communication error with the remote node (KFCS2, KFCS only)
• Node maintenance (LFCS2, LFCS only)
• PI/O breakdown (LFCS2, LFCS only)
• PI/O operation stop (LFCS2, LFCS only)
• RIO bus transmission stop (LFCS2, LFCS only)
• RB301 control right switch (LFCS2, LFCS only)
This section describes system operation in each failure mode.

■ System Operation at Error Occurrence in I/O Module : PFCS/SFCS
“Error occurrence in the I/O module” is a state in which all or part of the I/O module fails. At
this time, operation continues in the processor unit and I/O modules other than the one
experiencing an error.
The following system operations will be performed when an error occurs in the I/O module :
• Output operation of the I/O module
An initial cold start will be performed upon recovery of an error in the I/O module.
• Control operation of FCS
MAN fallback will be performed when an error occurs in I/O module area. Output
resumes upon recovery.
The figure below shows the operation of output signals from the analog output module and
the function block mode when an error occurs in the I/O module.
Process
I/O module
function
I/O module
output
Function block
mode AUT IMAN(MAN) MAN
MAN fallback I/O module

initialization manual initial cold start
B030301E.EPS
Figure Output Signal Operation of Analog Output Module when I/O Module Failed : PFCS/SFCS
When an I/O module fails, the following operations are performed in the function block that
is connected to I/O module.
• Sends the “PI/O Not Ready” system alarm message
• Block status changes to MAN and control operation is terminated. (MAN fallback)
For errors occurred in different locations, the following operations are performed in the
corresponding function blocks.
• “IOM Error” system alarm message is sent for I/O module error.
• For an error occurrence in the I/O unit or the bus connecting I/O unit and CPU, the
“BUS Error” system alarm message is sent while the corresponding I/O module
performs fallback operation.
• Values before the error occurrence are held as the input value. The data status
changes to LPFL.

■ System Operation at I/O Module Maintenance/Error : PFCS/LFCS2/LFCS/
SFCS
“I/O module maintenance” is a state in which the I/O module mounted on the process I/O
unit (IOU) is installed or removed while the power is on, in order to perform maintenance
operations. Whereas, the I/O module breakdown state denotes a state in which some kind
of breakdown has occurred in an I/O module mounted to an IOU. The subject mainte-
nance/breakdown IOU will remain live and all modules other than the subject module
continue their operations.
Furthermore, the I/O module maintenance status occurs when replacing an I/O module.
The system operation that is performed when the I/O module is in the maintenance state or
breakdown state consists of the following:
• I/O module output operation
For the output from an I/O module in which a breakdown has occurred, the output
value before the breakdown will be retained. However, no output will be performed for
a kind of breakdown that disables the output of the I/O module.
Initial cold start is performed for recovery from the maintenance/breakdown state of
the I/O module.
• FCS control operation
MAN fallback will be performed when the I/O module maintenance/failure status
occurs. Output resumes upon recovery.
The figure below shows the operation of analog I/O module in the I/O module maintenance/
failure status.
I/O module
function
If the breakdown state occurs,
the output value before the
breakdown is retained if the
I/O module can perform output
I/O module in that state.
output
Function block
mode AUT IMAN(MAN) MAN
MAN fallback PI/O

initialization manual initial cold start
B030302E.EPS
Figure Output Operation of Analog Output Module and Function Block Actions at I/O Module
Maintenance/Failure : PFCS/LFCS2/LFCS/SFCS

■ System Operation in the I/O Module Maintenance/Breakdown State :
KFCS2/KFCS £
The I/O module maintenance state denotes a state in which the live line of an I/O module
that is mounted to a node is disconnected and then connected in order to perform mainte-
nance work on the I/O module. Whereas, the I/O module breakdown state denotes a state
in which some kind of breakdown has occurred in an I/O module mounted to a node. The
subject maintenance/breakdown node will remain live and all modules other than the
subject module continue their operations.
Furthermore, the I/O module maintenance state occurs when an I/O module is replaced.
The system operation that is performed when the I/O module is in the maintenance state or
breakdown state consists of the following:
• I/O module output operation
An I/O module in which a breakdown has occurred performs an output fallback opera-
tion. However, no output will be performed for a kind of breakdown that disables the
output of the I/O module.
The FCU side performs an initial cold start operation of the I/O module for recovery
from the maintenance/breakdown state of the I/O module.
• FCU control operation
The FCU performs an MAN fallback operation when the I/O module maintenance/
breakdown state occurs. In addition, the FCU resumes output when recovering from
that state.
SEE ALSO
• For the initial cold start operation of the I/O module, see the following:
B2.5, “Start Operation of KFCS2, KFCS, LFCS2 and LFCS I/O Modules”
• For the output operation of the I/O module in the breakdown state, see the following:
■ System Operation in the SB301 Operation Stop State : KFCS2/KFCS £

The SB301 operation stop state denotes a state in which an SB301 mounted to an FCU
stops its operation while the FCU's power remains on.
The SB301 operation stop state occurs when the SB301 breaks down or is mounted/
dismounted.
The system operation that is performed in the SB301 operation stop state consists of the
following:
• Process I/O output operation
All the I/O modules lower than the FCU perform an output fallback operation during
the occurrence of the SB301 operation stop state. In addition, the output of the pro-
cess I/O is initiated with the actual output value at the time of recovery by executing an
initial cold start operation of the node in the FCU when recovering from that state.
The FCU performs an MAN fallback operation during the occurrence of the SB301
operation stop state. In addition, the FCU initiates an initial cold start of the node when
recovering from the SB301 operation stop state.

SEE ALSO
• For the initial cold start operation of the node, see the following:
“■ Initial Cold Start of the Node : KFCS2/KFCS” in B2.3, “Start Operation of KFCS2 and KFCS Nodes”
• For the output operation of the I/O module during the occurrence of an abnormality, see the following:
■ System Operation in the EB401 Operation Stop State : KFCS2/KFCS £

The EB401 operation stop state denotes a state in which an EB401 mounted to a local
node stops its operation while the process I/O power remains on.
The EB401 operation stop state occurs when the EB401 breaks down or is mounted/
dismounted.
The system operation that is performed in the EB401 operation stop state consists of the
following:
The I/O module of a remote node lower than the EB401 performs an output fallback
operation during the occurrence of the EB401 operation stop state. In addition, the
output of the process I/O is initiated with the actual output value at the time of recovery
by executing an initial cold start operation of the node in the FCU when recovering
from that state.
The FCU performs an MAN fallback operation during the occurrence of the EB401
operation stop state. In addition, the FCU initiates an initial cold start of the node when
recovering from the EB401 operation stop state.
SEE ALSO
• For the initial cold start operation of the node, see the following:
“■ Initial Cold Start of the Node : KFCS2/KFCS” in B2.3, “Start Operation of KFCS2 and KFCS Nodes”

■ System Operation in the Communication Error State with the Local Node
: KFCS2/KFCS £
The communication error state with the local node is a state in which an error has occurred
in the communication between an FCU and a local node.
The communication error state with the local node occurs when the transmission of the
extended serial backboard bus (ESB bus) is disconnected, an interface card error occurs,
etc.
The system operation that is performed in the communication error state with the local
node consists of the following:
The I/O module mounted to the local node in which a communication error has oc-
curred as well as the I/O module of the remote node lower than that local node per-
form an output fallback operation during the occurrence of the communication error
state. In addition, the output of the process I/O is initiated by executing either an initial
cold start operation or restart operation of the node in the FCU when recovering from
the communication error state.
The FCU performs an MAN fallback operation during the occurrence of the communi-
cation error state. In addition, when recovering from the communication error state,
the FCU initiates either an initial cold start operation or restart operation of the node,
depending on the duration when the local node was not responding.
SEE ALSO
• For the initial cold start operation and restart operation of the node, see the followings in B2.3, “Start Op-
eration of KFCS2 and KFCS Nodes”:
“■ Initial Cold Start of the Node : KFCS2/KFCS”
“■ Restart Operation of the Nodes : KFCS2/KFCS”

■ System Operation in the Communication Error State with the Remote
Node : KFCS2/KFCS £
The communication error state with the remote node is a state in which an error has oc-
curred in the communication between a local node and a remote node.
The communication error state with the remote node occurs when the transmission of the
enhanced remote I/O bus (ER bus) is disconnected, an interface card error occurs, etc.
The system operation that is performed in the communication error state with the remote
node consists of the following:
The I/O module mounted to the remote node in which a communication error has
occurred performs an output fallback operation during the occurrence of the communi-
cation error state. In addition, the output of the process control I/O area is initiated by
executing either an initial cold start operation or restart operation of the node in the
FCU when recovering from the communication error state.
The FCU performs an MAN fallback operation during the occurrence of the communi-
cation error state. In addition, when recovering from the communication error state,
the FCU initiates either an initial cold start operation or restart operation of the node,
depending on the duration when the remote node was not responding.
SEE ALSO
• For the initial cold start operation and restart operation of the node, see the followings in B2.3, “Start
Operation of KFCS2 and KFCS Nodes”:
“■ Initial Cold Start of the Node : KFCS2/KFCS”
“■ Restart Operation of the Nodes : KFCS2/KFCS”

■ System Operation at Node Maintenance : LFCS2/LFCS £
“Node maintenance” is a state in which one entire node is separated from the system in
order to perform maintenance operations. At this time, operation continues at RIO bus
communication, field control unit (FCU) and nodes other than the one subject to mainte-
nance.
The node maintenance status occurs when replacing process I/O unit (IOU).
The output operations of process I/O area and control operation of FCU during node
maintenance status are the same as those during I/O module maintenance.
SEE ALSO
For the details of output operation of process I/O area and control operation of FCU during node mainte-
nance, see the following previous section:
“■ System Operation at I/O Module Maintenance/Error : PFCS/LFCS2/LFCS/SFCS”
■ System Operation at PI/O Error : LFCS2/LFCS £

“PI/O error” is a state in which all or part of a node in the process I/O area fails. At this time,
operation continues at the field control unit (FCU), RIO bus communication and PI/O
components other than the one that has failed.
The PI/O error status occurs when RB401 or I/O module fails, when node internal bus fault
occurs or when installation or removal of I/O module is performed while the power is on.
The output operations of process I/O area and control operation of FCU at PI/O error are
the same as those during I/O module maintenance.
SEE ALSO
For the details of output operation of process I/O area and control operation of FCU during PI/O error, see
the following:
■ System Operation at Termination of PI/O Operation : LFCS2/LFCS £

“Termination of PI/O operation” is a state in which normal I/O functions are stopped while
the power to the process I/O area being supplied. At this time, operation continues at the
RIO bus communication, field control unit (FCU) and all PI/O components other than the
one being stopped.
Termination of PI/O operation occurs when unmatched definition information is detected
between process I/O area and FCU.
The output operations of process I/O area and control operation of FCU at termination of
PI/O operation are the same as those during I/O module maintenance.
SEE ALSO
For the details of output operation of process I/O and control operation of FCU during PI/O operation
termination, see the following:

■ System Operation at Termination of RIO Bus Transmission : LFCS2/
LFCS £
“Termination of RIO bus transmission” is a state in which RIO bus connection is severed
due to some reason and transmission between FCU and PI/O area is interrupted. At this
time, field control unit (FCU) and process I/O area continue to operate independently.
Termination of RIO bus transmission occurs when both RB301s fail or when the RIO bus is
disconnected.
The following system operations will be performed when an error occurs in the I/O module:
• Output operation of the I/O module
An initial cold start will be performed upon recovery of RIO bus transmission stop state.
• Control operation of FCS
MAN fallback will be performed when an error occurs in I/O module area. Output
resumes upon recovery.
The figure below shows the operation of analog output module and function block actions
when the RIO bus transmission has been terminated.
less Line loss detection time

RIO transmission
Time span of instantaneous

failure detection
Output from
I/O module
Output fallback
Function block
mode AUTO AUTO IMAN (MAN) MAN
MAN fallback
Initialization manual
B030303E.EPS
Figure Operation of Analog Output Module and Function Block Actions at Termination of RIO
Bus Transmission : LFCS2/LFCS £
■ System Operation at RB301 Control Right Transfer : LFCS2/LFCS £

“RB301 control right transfer” is a state in which the control side RB301 stops functioning
and the standby RB301 begins to function as the controlling RB301. Operation continues
in the process I/O before and after transfer of the control right, but RIO bus communication
stops until the transfer is completed.
The RB301 control right transfer occurs when an error is detected in the self-diagnostics of
RB301 or RB301 diagnostics in the FCU.

<B3.4 Common Operation of the I/O Module at Problem Occurrence> B3-38
B3.4 Common Operation of the I/O Module at

Problem Occurrence
The KFCS2 or KFCS performs special output operation of the I/O module immedi-
ately after a power recovery or during the occurrence of an abnormality. The follow-
ing explains the details of various output states of the I/O module.
■ Output State of the I/O Module Immediately after a Power Recovery :

KFCS2/KFCS £
When an I/O module is recovered from a power failure, the I/O module restarts on its own.
The following shows the output state at I/O module restart:
Table Output State at I/O Module Restart : KFCS2/KFCS £
I/O module Output state
1.25mA (-17.19%)
Analog output (4-20mA) Subsequently, outputs the value equivalent to
the tight-shut of the function block
0.31V (-17.19%)
Analog output (1-5V) Subsequently, outputs the value equivalent to
the tight-shut of the function block
Contact output Resets to 0
RS communication module Tracks data on the subsystem side
Fieldbus communication module Tracks the field output value for output with feedback
B030401E.EPS
Note: If the CPU of the FCU is being stopped, the output value of the analog output will be 0mA (0V).

■ Output State of the I/O Module during the Occurrence of an Error :
KFCS2/KFCS £
The output state of the I/O module when an I/O module breaks down or an abnormality
occurs in devices higher than I/O module is in accordance with the output fallback specifi-
cation.
● Output State at I/O Module Breakdown : KFCS2/KFCS £

The output state of the I/O module when an I/O module breaks down is in accordance with
the output fallback specification. However, no output will be performed for a kind of break-
down that disables the output of the I/O module.
● Output State of the I/O Module when Higher Devices are Abnormal :
KFCS2/KFCS £
The I/O module, after detecting that an access from the higher devices cannot be made for
more than the line loss detection time (4 seconds) because of FCU’s CPU operation stop, a
node abnormality, etc., performs an output fallback operation.
● Details of Output Fallback Operation : KFCS2/KFCS £
Table Output State of the I/O Module when a I/O Module Breakdown has Occurred or an Higher
Device Abnormality has Occurred (with an Output Function when an I/O Module
Breakdown has Occurred) : KFCS2/KFCS £
With output
fallback With output fallback
I/O module Without output fallback
(output data (Maintain current value): default
specification)
Outputs
Analog output Retains output. the specified Retains output.
output value.
Status output Retains output. (*1) OFF Retains output. (*1)
Sets to OFF after outputting the Sets to OFF after outputting the
Pulse width
value prior to an error occurrence OFF value prior to an error occurrence
Contact output
for the specified time period. for the specified time period.
output
Time- Continues output. (repeats OFF/ON Continues output. (repeats OFF/ON
proportioning using the time interval specified prior OFF using the time interval specified prior
ON/OFF output to an error occurrence.) to an error occurrence.)
B030402E.EPS
*1: When ST compatible modules are used with dual-redundant configuration, if a module has error, the output of the
module becomes OFF.

Table Output State of the I/O Module when an I/O Module Breakdown has Occurred or a Higher
Device Abnormality has Occurred (without an Output Function when an I/O Module
Breakdown has Occurred) : KFCS2/KFCS £
With output fallback With output fallback (Maintain
I/O module Without output fallback
(output data specification) current value): default
When There is no fallback function in the RS communication module.
a higher The module continues communication. Since there is no writing from the higher device in
RS device is the communication driver that writes the amount of variation after rereading the output data,
communication abnormal the module does not perform a write communication to the subsystem side (reread only).
module
When an IOM
Stops communication.
breakdown occurs
When
a higher Make the field devices into the default actions for
FOUNDATION Retains output.
device is “Fault State.” (*1)
fieldbus
abnormal
communication
module Stops communication with the fieldbus device. The fieldbus device operation by
When an IOM
communication stop with the fieldbus device is in accordance with the fault state operation
breakdown occurs
of the fieldbus device.
B030403E.EPS
*1: Fallback can be enabled or disabled on FOUNDATION fieldbus communication module (ALF111). However, there is no
“output value during fallback” and “hold previous value during fallback” settings when fallback is enabled. When
fallback is enabled, the field devices run the actions set for “Fault State” previously set for the devices.

<B3.5 Operation of I/O Module when Downloading is Performed> B3-41
B3.5 Operation of I/O Module when Downloading is

Performed
Downloading to I/O module includes “off-line download” and “on-line download.”
The following section explains the operation of I/O module at downloading.

■ Operation of I/O Module when Off-Line Downloading is Performed :
PFCS/SFCS/LFCS2/LFCS
When off-line downloading is performed for FCS, the output status differs between the
output module that was subject to off-line downloading and the output module that was not.
● Output Status of Output Module Subject to Off-Line Downloading :

The table below shows the output status change of output module that was subject to off-
line downloading, for both downloadings with and without definition change.
Table I/O Status for Output Module that Becomes an Off-Line Downloading Target :
Module Type Without Definition Change With Definition Change
• When the operation mode is switched from electric current
to electric voltage or vice versa, 1.25 mA (for electric current
Current/Voltage Output Module Output value is stored. output) that is equivalent to tight shut value is output. (*1)
AAM51 • When a range or span is changed, the output value changes
according to the change in the range or span. (*2)
• For any other change, output value is stored.
Multi-point Control Analog

Output value is stored. Output value is stored.
I/O Module
Contact Input/Output Module

ADM51C/T, ADM52C/T, All points are OFF (0). All points are OFF (0).
ADM55R
The existing values before
downloading may be held
without being reset The existing values before downloading may be held without
Contact Input/Output Module
(all points OFF). However, being reset (all points OFF). However, this is only supported
ADM51C-2/T-2, ADM52C-2/T-2,
this is only supported by by the status output (SO) corresponding to the digital
ADM55R-2
the status output (SO) output module action mode. (*3)
corresponding to the digital
output module action
mode. (*3)
• When the range or span is changed, the output value
Current Output
changes according to the change in the range or span. (*2)
Multiplexer Module Output value is stored.
• For any other change, output value is stored.
AMM52T
• In case of no change, output value is stored.
B030501E.EPS
*1: To be more specific, AAM51 is reset to 0 mA (for electric current) after downloading is completed and 1.25 mA is output
after processor unit is rebooted.
*2: Since the range of electric current is normally fixed to the range between 0 and 100 %, there will be no change in the
range or span. An example of change, if any, is shown below.
When the range is between 0 and 100 and the output value is 50, the output value for electric current changes from 12
mA (equivalent to 50 %) to 8 mA (equivalent to 25 %) if the range is changed to 0 to 200.
*3: When the module action mode is PW (pulse-width), TP (time-proportioning) or PO (pulse output), the output will be
reset.
The output status change of I/O module caused by downloading actually occurs when
downloading of the definition information (configuration) to I/O module is completed.

● Output Status of Output Module that was not Subject to Off-Line Down-
loading : PFCS/SFCS/LFCS2/LFCS
I/O module that was not subject to off-line downloading holds the output status prior to
downloading, if fallback is not specified. Fallback is performed if it is specified.
■ Operation of the I/O Module when Offline Download to the I/O Module is
Executed : KFCS2/KFCS £
When offline download is executed to an FCS, the definition information will be down-
loaded to all the I/O modules of that FCS. The following explains the output state in this
situation:
• The FCU stops during the offline download to the FCS. All the I/O modules lower than
the FCU perform an output fallback operation while the FCU is being stopped.
• The definition information is then downloaded to the I/O modules after the offline
download to the FCS is complete. The I/O modules retain the output values while this
download is being executed. However, the output values will change according to the
change in the output range or span, if applicable.

■ Operation of I/O Module when Online Downloading is Performed :
This section explains the output status of output module and the status of function block
when I/O module definition is changed by downloading.
● Output Status of Output Module : PFCS/SFCS/LFCS2/LFCS

When the change to I/O module definition information is made by online downloading, the
output status of output module will be the same as when offline downloading is performed.
Analog output module starts output operation after tracking I/O module output status upon
completion of definition information downloading. While for a digital output module, all
points of contact output may be set to OFF. However, when the digital output module's
specification code is set as -2 (for example ADM52C-2) and the output action mode is
status output (SO), the existing values before downloading may be held without being
reset. Actually, the contact output (DO) values on PI/O image in FCU are all reset to OFF
(0) unrelated to the specification code. After the downloading is completed, for the modules
with specification code -2, the IOM DO value tracking will be performed to restore the
previous values.
● Status of Function Block : PFCS/SFCS/LFCS2/LFCS

▼ IOM Online Updating
When download to an I/O module is executed, the setting item, “IOP Occurs in Connected
Blocks” can be used to specify whether or not the input side of the function block that is
connected to the I/O module is set to IOP.
If the input side is set to IOP, the data status of the measurement input will become bad
data (BAD) when download is executed.
The regulatory control block in which the data status became BAD performs the following
operation:
• Stops the analog input square root extraction function, pulse train input conversion
function, digital filter function and totalizer function.
• The PV value retains the value immediately before the input open (IOP) warning
generation caused by BAD detection. However, if the PV overshoot has been speci-
fied, the PV value will be overshot to the lower limit value.
• A function block that has the MAN fallback function performs an MAN fallback opera-
tion. In this case, a connection failure alarm (CNF) will be generated at the same time
when the MAN fallback operation starts.
If it has been specified not to set the operation at IOM change to IOP, the data status of the
measurement input will not become bad data (BAD) when download is executed.
On [Constant] tab of FCS property sheet, set the operation at IOM change to IOP.
Check [IOP Occurs in Connected Blocks] check box. By default, this option is not checked.

■ Operation of the I/O Module when Online Download to the I/O Module Is
Executed : KFCS2/KFCS £
When the definition information of I/O modules is changed by online download, either “IOM
continuous load” that continues the I/O operation of I/O modules, or “IOM initialization load”
that stops the I/O operation of the I/O modules is executed according to the change con-
tents.
If a new I/O module has been added, or if an I/O module that does not have the matching
definition information as shown below has been mounted, IOM initialization load will be
executed.
Table Setting Elements of IOM Initialization Load: KFCS2/KFCS £
Definition information Description Default value
Single/dual-redundant
Select single or dual-redundant. Single
setting
Select whether to enable or disable
Burn-out setting Enable
the burn-out setting function.
Select the direction to clamp the PV
Direction setting at Upper limit
value from the upper limit setting and
burn-out setting (UP)
lower limit setting.
Cold-junction Select the type of the terminal to be
No selection
compensation setting used.
B030502E.EPS
● IOM Continuous Load : KFCS2/KFCS £

The IOM downloads while continuing the I/O operation at other than the terminal point
where the definition information of the I/O module has been changed.
● IOM Initialization Load : KFCS2/KFCS £

▼ IOM Online Updating
The IOM stops the I/O operation of all points of the I/O modules where the definition infor-
mation has been changed. The I/O module in which the IOM initialization load is being
executed will be placed in an error state.
When download to an I/O module is executed, the setting item, “IOP Occurs in Connected
Blocks” can be used to specify whether or not the input side of the function block that is
connected to the I/O module is set to IOP.
If the input side is set to IOP, the data status of the measurement input will become bad
data (BAD) when download is executed. If the input side is not set to IOP, the function block
retains the previous value while the IOM initialization load is being executd.
On [Constant] tab of FCS property sheet, set the operation at IOM change to IOP. Check
[IOP Occurs in Connected Blocks] check box. By default, this option is not checked.

IMPORTANT
Be cautious that the following phenomena may occur during online maintenance.
• When reverse the analog control I/O module output or when change the output range,
the output from the terminals subjected to the changes fluctuates for about 10 millisec-
onds, then stabilized at the changed output. For an example, when reverse a 4 to 20
mA output where the 4mA stands for 0%, the 0% output changes to 20mA after fluctu-
ating for 10 milliseconds. For this reason, when reversing output or changing output
range, the necessary measures should be taken such as manipulating the final
operation element locally to prevent from the fluctuation caused form the output
terminals.
• When reversing the I/O module input signal or changing the input range, the PV of the
terminals subject to the changes may fluctuate. Sometimes, IOP alarm may occur.
• When pulse setting of time-proportioning output of a contact I/O module is changed, it
takes a while for the new setting becomes valid so that the old setting continues. In
order to make the new setting become valid earlier, pullout the module and put it back
or download to the module on HIS status display window.
• When change the contact time-proportioning output phasing time, the phasing may
not be correct. So that it is necessary to pull out the I/O module from its slot and put it
back again, or perform IOM load on HIS status display window.
• When change the temperature unit or signal type for a thermocouple or a RTD I/O
module (AAT141, AAT145, AAR181 and AAR145) IOP or -IOP may repeatedly occurs
for a while.
• If the following item of EB401 properties are changed, the I/O data of the I/O modules
connected via the dual-redundantly configured EB401 modules stop updating for
about five seconds after online downloading.
Duplicate Next card
Maximum Number of Nodes
Communication Protocol
Communication Basic Period
Node No Response Monitoring Time
Number of Retries at Node No Response

<B3.6 Operation of Communication I/O Module at Error Occurrence> B3-47
B3.6 Operation of Communication I/O Module at

Error Occurrence
The following errors or operation affect the operation of communication I/O module.
• Execution of PFCS initial cold start
• Error in communication with subsystem and error in communication I/O mod-
ule
• Momentary power failure
This section explains the operation performed when these errors occurred.
■ Execution of FCS Initial Cold Start

The communication I/O data value is set to 0 from the start of communication module
following the FCS start until the function block starts to receive the communication I/O data.
The communication I/O data status becomes NRDY.
The table below shows I/O data of communication I/O module when FCS executes initial
cold start.
Table Communication I/O Data at FCS Initial Cold Start
During communication module At completion of communication module
Item
initialization initialization
Analog input 0 Value acquired from subsystem
Analog output 0 Tracking to the value acquired from subsystem (*1)
Contact input 0 Value acquired from subsystem
Contact output 0 Tracking to the value acquired from subsystem (*1)
Switch instrument block
0 Tracking to the value acquired from subsystem
Motor control block
B030601E.EPS
*1: Tracking is performed only for the function block with tracking specified “Yes.”

<B3.6 Operation of Communication I/O Module at Error Occurrence> B3-48
■ Error in Communication with Subsystem and Error in Communication
I/O Module
When the communication module or communication itself fails, the data prior to the error
occurrence is used as input data while the error exists. The status of data used by the
connected function block is set to LPFL.
The table below shows the operation when there is an error in communication with sub-
system or communication I/O module, as well as the operation when the error is recovered.
Table Operations at Error Occurrence and Recovery from Error
Data Type When Error Occurred When Error Is Recovered
The data status of connected function block
IOP recovery, PV value is acquired from
Analog input is set to IOP, and PV value is overshot or
subsystem
stored by builder specification.
The data status of the connected function OOP recovery, tracking to the value
Analog output
block is set to OOP, and MV value is stored. acquired from subsystem (*1)
Contact input Stored Value acquired from subsystem
Tracking to the value acquired from
Contact output Stored
subsystem (*1)
Switch instrument block PV and MV values are set to the values Tracking to the value acquired from
Motor control block prior to initial cold start. subsystem (*1)
B030602E.EPS
*1: Tracking is performed only for the function block with tracking specified “Yes.”
■ Momentary Power Failure

Following the recovery from momentary power failure, the data value prior to the momen-
tary power failure is used as a communication I/O data value until the communication is
restarted after the start of communication module. The communication I/O data status
becomes NRDY.

<B4. Making FCS Dual-Redundant> B4-1
B4. Making FCS Dual-Redundant

The production control system has employed a redundancy system that makes each
section of the FCS dual-redundant. By making each part of the FCS dual-redundant,
high system reliability and operability can be achieved and highly reliable, accurate
data can be realized.
An FCS with dual-redundant configuration is called as FCD.
■ Dual-Redundant Structure of FCD : PFCS ¡

The dual-redundant structure can be implemented into the processor units, communication
couplers, I/O modules and power supply units.
The following figure shows an example of signal connections to implement dual-redun-
dancy in each part of FCD.
VL net
Communication Communication
coupler coupler
VL net VL net
Power supply interface interface Power supply
Processor Processor
Unit Unit
General-purpose
PI/O communication PI/O
Interface unit Interface
I/O Module
B040001E.EPS
Figure Signal Connections to Implement Dual-Redundancy in Each Part of FCD : PFCS ¡

■ Dual-Redundant Structure of FCD : SFCS £
The dual-redundant structure can be implemented into the processor units, communication
couplers, I/O modules and power supply units.
The following figure shows an example of signal line connections to implement dual redun-
dancy in each part of FCD.
V net
Communication Communication
coupler coupler
V net V net
Power supply interface interface Power supply
Processor Processor
Unit Unit
General-purpose
PI/O communication PI/O
Interface unit Interface
I/O Module
B040002E.EPS
Figure Signal Connections to Implement Dual-Redundancy in Each Part of FCD : SFCS £

■ Dual-Redundant Structure in FCD : KFCS2/KFCS £
Dual-redundant structure can be applied to Field control units, control nest extension buses
(ESB bus), Ethernet remote I/O buses (ER bus) and I/O modules. Thus the FCU, the local
nodes, the remote nodes and power supply units are operated redundantly.
The figure below shows the signal connections of a dual-redundantly-structured FCD.
V net 1
V net 2
FCU
V net Coupler V net Coupler
(AIP502) (AIP502)
PW PW
Processor Unit 301 301 Processor Unit
CP345(L) /PW /PW CP345(R)
302 302
EN-Bus 1
EN-Bus 2
ESB Bus ESB Bus

Master Interface Card Master Interface Card
(SB301) (SB301)
ESB Bus Coupler ESB Bus Coupler

(AIP532) (AIP532)
ESB Bus 1
ESB Bus 2
Local Node
E E S S
B B I I I I I I B B PW PW
4 4 O O O O O O 4 4 481 481
0 0 M M M M M M 0 0 /PW /PW
1 1 1 1 482 482
SB-Bus 1
SB-Bus 2
ER Bus 1
ER Bus 2
Remote Node
E E
I I I I I I I I B B PW PW
O O O O O O O O 5 5 481 481
M M M M M M M M 0 0 /PW /PW
1 1 482 482
SB-Bus 1
SB-Bus 2
PW301/PW302: FCU power supply unit SB401: ESB bus slave interface module
PW401/PW482: Node power supply unit EB401: ER bus master interface module
IOM: I/O modules EB501: ER bus slave interface module
B040003E.EPS
Figure Signal Connections when Implementing Dual-Redundancy in Each Part of FCD : KFCS2/
KFCS £

■ Dual-Redundant Structure in FCD : LFCS2/LFCS £
A dual-redundant structure can be implemented into the field control units (FCU), PIO
nodes and their power supply units.
The following figure shows an example of signal connections to implement dual-redun-
dantly in each part of FCD.
V net 1
V net 2
FCU
V net coupler V net coupler
(AIP502) (AIP502)
PW PW
Processor unit Processor unit
301 301
CP345 (L) BAT BAT CP345 (R)
EN-bus 1
EN-bus 2
RIO bus RIO bus

interface unit interface unit
(RB301) (RB301)
RIO bus coupler RIO bus coupler

(AIP512) (AIP512)
RIO-bus 1
RIO-bus 2
PI/O node
PW Node Node PW
401 interface unit interface unit 401
(RB401) (RB401)
IOM IOM IOM IOM IOM
I/O module I/O module I/O module I/O module I/O module
bus 1 bus 2 bus 3 bus 4 bus 5
IOM IOM IOM IOM IOM
PW301: FCU power supply unit

PW401: Node power supply unit
IOM: I/O module
B040004E.EPS
Figure Signal Connections to Implement Dual-Redundancy in Each Part of FCD : LFCS2/LFCS

£

<B4.1 Dual-Redundant Architecture of PFCS and SFCS> B4-5
B4.1 Dual-Redundant Architecture of PFCS and

SFCS
Within PFCS or SFCS, a dual-redundant structure can be implemented into the
processor units, communication couplers, I/O modules and power supply units.
This section describes dual-redundant structures in the processor units and I/O
modules.

■ Dual-Redundant Processor Unit : PFCS ¡
The following figure shows the operation of a dual-redundant processor unit.
VL net 1
VL net 2
<Left processor unit> <Right processor unit>

CP701/CP703 CP701/CP703
VL net VL net
Main interface interface Main
memory memory
(with ECC) (with ECC)
CPU CPU
PI/O bus PI/O bus

interface interface
CP701: Basic processor unit

CP703: Extended processor unit
ECC: Error-Correcting Code
B040101E.EPS
Figure Structure of the Dual-Redundant Processor Unit : PFCS ¡
• At the V net interface, a communication interface supporting dual-redundancy is

mounted on the CPU and connected to the dual-redundant control bus.
• At the processor unit, control side and standby side CPUs synchronize each other to
perform the same control computation.
If an error occurs at the control side CPU, the synchronous execution hot standby
system will transfer the control right to the standby side CPU without interruption.
• If an invalid access is detected against the main memory or the standby side in the
control side processor unit, processing on the control side will stop immediately and
the control right will be transferred to the standby side. This prevents the destruction of
data inside the local system, as well as at the destination site due to CPU malfunc-
tions.
• There is a WDT (Watch Dog Timer) in the processor unit to supervise the execution of
control function.
Whenever the abnormality in control function is detected, the control right is switched
from control side to the standby side, as if the abnormality is in the control side proces-
sor.
• In the main memory, error-correction coding (ECC) function is provided so that the
transient bit inversion error in the main memory may be repaired.
• The PI/O bus interface has the function to run the PI/O executions on control side and
to diagnostic the PI/O performance by itself. The same diagnostic function is also
running in standby side PI/O bus interface.
When an abnormality occurs in the control side PI/O bus, the control right is immedi-
ately switched to the standby side PI/O, thus the PI/O executions may be continued.

■ Dual-Redundant Processor Unit : SFCS £
The following figure shows the operation of a dual-redundant processor unit.
V net 1
V net 2
<Left processor unit> <Right processor unit>

CP701/CP703 CP701/CP703
V net V net
Main interface interface Main
memory memory
CPU CPU
PI/O bus PI/O bus

interface interface
CP701: Basic processor unit

CP703: Extended processor unit
B040102E.EPS
Figure Structure of the Dual-Redundant Processor Unit : SFCS £
• At the V net interface, a communication interface supporting dual-redundancy is

mounted on the CPU and connected to the dual-redundant control bus.
• At the processor unit, control side and standby side CPUs synchronize each other to
perform the same control computation.
If an error occurs at the control side CPU, the synchronous execution hot standby
system will transfer the control right to the standby side CPU without interruption.
• If an invalid access is detected against the main memory or the standby side in the
control side processor unit, processing on the control side will stop immediately and
the control right will be transferred to the standby side. This prevents the destruction of
data inside the local system, as well as at the destination site due to CPU malfunc-
tions.
• There is a WDT (Watch Dog Timer) in the processor unit to supervise the execution of
control function.
Whenever the abnormality in control function is detected, the control right is switched
from control side to the standby side, as if the abnormality is in the control side proces-
sor.
• In the main memory, error-correction coding (ECC) function is provided so that the
transient bit inversion error in the main memory may be repaired.
• The PI/O bus interface has the function to run the PI/O executions on control side and
to diagnostic the PI/O performance by itself. The same diagnostic function is also
running in standby side PI/O bus interface.
When an abnormality occurs in the control side PI/O bus, the control right is immedi-
ately switched to the standby side PI/O, thus the PI/O executions may be continued.

■ Dual-Redundant I/O Module : PFCS/SFCS
The following describes the operation of dual-redundant I/O module.
The operation varies depending on the I/O module type used.
● Dual-Redundant Analog Input Module : PFCS/SFCS

Analog input modules can be set for dual-redundant operation using the Dual-Redundant
Signal Selector Block (SS-DUAL), which is one of the function blocks.
Two signals from the two analog modules are connected to IN1 and IN2 terminals of the
SS-DUAL block.
● Dual-Redundant Analog Output Module : PFCS/SFCS

For the Current/Voltage Output Module (AAM51), directly adjacent module (i.e., 1-2, 3-4, 5-
6, 7-8, 9-10, 11-12, 13-14,15-16) can be used for dual-redundant outputs (with the output
terminals connected in parallel.) Conventionally, the smaller number of the two becomes
the control side and outputs to the field.
If an error occurs on the control side, the control right will be transferred to the standby side
and output will continue. At this time, a system alarm message will be issued in conjunction
with the control right transfer. Error recovery in the I/O module is then monitored periodi-
cally.
● Dual-Redundant Multipoint Control Analog I/O Module : PFCS/SFCS

For the Multipoint Control Analog I/O Module (AMC80), the dual-redundancy may be
realized by installing two modules into one unit. The one on the first slot at power-on be-
comes the control side and the one on the second slot becomes the standby side. I/O data
for the field will be the same for control side and standby side modules.
The control right will be transferred to the standby side if AMC80 malfunctions during
on-line loading (including the case in which the front cable is unplugged). At this time, the
previous input value (PV) and output value (MV) will be retained.
The Multipoint Control Analog I/O Module (AMC80) uses the data input to the control side
as the data input from the field. For data output to the field, the output data on the control
side will be used.

● Dual-Redundant Contact Input Module : PFCS/SFCS
Contact input modules can have a dual-redundant structure using two modules of the same
type and same functions. As for I/O data from the field, the same values will be input and
output with respect to both the control side and standby modules. When the two modules
are installed into the two adjacent slots in the same unit (such as slot1 and slot2 or slot3
and slot4), the dual-redundancy may be realized. The function blocks only use the data on
the control side modules.
and input will continue. At this time, a system alarm message will be issued in conjunction
cally.
● Dual-Redundant Contact Output Module : PFCS/SFCS

Contact output modules can have a dual-redundant structure using two modules of the
same type and the same functions by connecting the output terminals to each other in
parallel. The “OR” of the signals from the two modules will be output to the field. When the
two modules are installed into the two adjacent slots in the same unit (such as slot1 and
slot2 or slot3 and slot4), the dual-redundancy may be realized.
cally.

■ IOM Dual-Redundant Actions at FCS Power Failure and Different Mal-
function Modes : PFCS/SFCS
This section explains the IOM dual-redundant actions under the circumstances of FCS
power failure and recovery; station RUN operation; and after the FCS Offline downloading.
This explanation is based on the situation that both dual-redundant IOM cards are running
properly and any of the two cards may be running as control side card. Furthermore, in the
specific situations (PI/O malfunction, PI/O stop, OOP etc.,) the actions vary with the situa-
tions accordingly.
● Control I/O Modules (AAM50/AAM51) : PFCS/SFCS

• When recovered from power failure (including the PI/O area), the smaller numbered
card takes the control.
• After FCS Offline downloading, the greater numbered card takes the control.
• When recovered from power failure (not including the PI/O area), or FCS start by the
operation like Station RUN, the card previously controlled keeps its control right.
● Multi-point Control Analog I/O Module (AMC80) : PFCS/SFCS

• When FCS recovered from a prolonged period of power failure, the smaller numbered
• After FCS Offline downloading, the card in greater numbered slot takes the control.
• When recovered from other kind of power failure or FCS start by the operation like
Station RUN, the card previously controlled keeps its control right.
● Contact Input/Output Module (ADMxx) : PFCS/SFCS

• When FCS recovered from a cold initial start (or from the prolonged stop, Station RUN
operation, FCS Offline downloading) the card in the smaller numbered slot takes the
control.
• When recovered from FCS restart, the card previously controlled keeps its control
right.
● Package Communication Module (ACM1x) : PFCS/SFCS

• When the FCS recovered from a power failure or a Station RUN operation or FCS
Offline downloading, the card in the smaller numbered slot takes the control.

<B4.2 Dual-Redundant Architecture of KFCS2 and KFCS> B4-11
B4.2 Dual-Redundant Architecture of KFCS2 and

KFCS
In KFCS2/KFCS, dual-redundant configuration are applied to field control units,
control extended serial backboard buses (ESB bus), enhanced remote I/O buses (ER
bus) and I/O modules. So that the FCU, the local nodes, the remote nodes and their
power supply units are operated redundantly.
The dual-redundant architecture of FCU, ESB bus and ER bus is explained as fol-
lows.
■ Dual-Redundant Architecture of FCU : KFCS2/KFCS £

The following figure illustrates the dual-redundant architecture of FCU.
V net 1
V net 2
<Left unit> <Right unit>

CP345 CP345
V net V net
interface interface
CPU1 CPU1
Main Main
memory Collator Collator memory
CPU2 CPU2
EN bus EN bus
interface ESB bus ESB bus interface
interface interface
(SB301) (SB301)
ESB bus
CP345: Processor unit card

B040201E.EPS
Figure Dual-Redundant Architecture of FCU : KFCS2/KFCS £

• Each processor card unit has two CPUs, which perform the same control computa-
tion. The computation results are compared by a collator during each computation
cycle. If the computation results from the two CPUs match, the collator determines
that the computation is normal and sends data to main memory and bus interface unit.
• Because the main memory has an ECC (Error-Correcting Code), transient bit inver-
sion errors occurring in the main memory can be repaired.
• If computation results from CPU1 and CPU2 do not match, the collator decides that a
computation error has occurred, and the control right is transferred to the standby
card.
• The standby processor unit card performs the same computation as the control one,
even though it is in the standby state. Therefore, it can immediately resume the output
of control computation data to the bus interface when it takes over the control right.
• Self-diagnostics will be executed on the processor unit in which an error has occurred.
If no CPU error is detected as a result of diagnostics, the error will be taken as a
transient computation error, and the unit returns from error state to standby. The
processor unit on standby performs the same computation concurrently with the
control side.
Therefore, CPUs within the same unit collate each other’s computation data, being
sure to detect any computation errors. Because the unit on standby performs the
same control computation concurrently with the control unit, it can take over the
control computation at any point without interruption, even for a very short time.

■ Dual-Redundant Architecture of Extended Serial Backboard Bus
(ESB Bus) : KFCS2/KFCS £
The ESB bus master interface cards (SB301, SB302) mounted in FCU, the extended serial
backboard extension buses and SB401 cards can be configured with dual-redundant
architecture.
FCU
S C C S
B P P B
3 3 3 3
0 4 4 0
1 5 5 1
Local Node
S S
I I I I I I I I B B P P
O O O O O O O O 4 4 S S
1 1
Remote Node
E E S S
B B I B B P P
4 4 O 4 4 S S
0 0 M 0 0 U U
1 1 1 1
ESB Bus
B040202E.EPS
Figure Dual-Redundant Architecture of ESB Buses : KFCS2/KFCS £
● Dual-Redundant Configuration of ESB Master Interface Cards (SB301) :

KFCS2/KFCS £
Using two SB301 cards in a FCU, the dual-redundancy of the cards can be configured. The
software in controlling CPU in FCU decides which SB301 card is running and which is
standing by. The SB301 card mounted in the same side of the controlling CPU is running
while the SB301 card with the other CPU is standing by. The CPU communicating with I/O
modules via SB301.
● Dual-Redundant Configuration of ESB Bus and SB401 : KFCS2/KFCS £

Dual-redundant ESB bus can be configured even though the FCU is not in dual-redundant
configuration. Dual-redundant configuration of ESB bus is applied with a pair of buses
connected to a pair of SB401 respectively. The dual-redundant buses are used alternately
in normal situation. When abnormality occurs in one bus or in one SB401, the other bus or
the other SB401 takes over the whole communication. FCU periodically probes the failed
bus to check if the bus has recovered or not.
Moreover, if a bus connected to the controlling SB301 fails, the controlling SB301 passes
the control right to the standby SB301 if the bus connected to the standby SB301 is normal.

■ Dual-Redundant Configuration of Enhanced Remote I/O Bus (ER Bus) :
KFCS2/KFCS £
EB401, Enhanced remote I/O buses and EB501 can be applied in dual-redundant configu-
ration.
● Dual-Redundant Configuration of EB401, Enhanced Remote I/O Buses and

EB501 : KFCS2/KFCS £
In a local mode, putting the two EB401 cards next to each other (one in an odd numbered
slot and the other in the next even numbered slot), the EB401 and the enhanced remote I/
O bus can be configured to a dual-redundant architecture.
One ER bus from one EB401 card can be used for connecting many remote nodes by
connecting to EB501 card on each node. The bus from the odd numbered EB401 should
be connected to the left side EB501 card, while the bus from the even numbered EB401
should be connected to the right side EB501 card.
The software in controlling CPU decides which EB401 card is running and which is stand-
ing by. The controlling EB401 card performs the input and output signal communications
with I/O modules via ER bus.The stand-by EB401 runs the node diagnosis only (node
communication diagnosis), it checks the node communication but does not check the
communication between modules and the node.
Local Node
E E E E S S
B B B B B B P P
Remote Node
4 4 4 4 4 4 S S
0 0 0 0 0 0 U U
E E 1 1 1 1 1 1
1 1
Remote Node
E E
M M M M M M M M 0 0 U U ESB Bus
1 1
ER Bus ER Bus
B040203E.EPS
Figure Dual-Redundant Configuration of EB401, ER Bus and EB501 : KFCS2/KFCS £

● Switching Control Right of EB401 : KFCS2/KFCS £
The software in CPU decides which EB401 card is running and which is standing by and
switches them from control to standby or vice versa in accordance with the following
conditions.
• In the cases that the controlling EB401 card is abnormal and the standby card is
normal.
• In the cases illustrated in the following table;
Suppose there are 4 remote nodes, the control right may be switched under the illustrated
circumstances.
Table Switching Control Right : KFCS2/KFCS £
Case 1 Case 2 Case 3 Case 4 Case 5
Control Standby Control Standby Control Standby Control Standby Control Standby
Remote Abnormal Abnormal
Normal Normal Normal Normal Abnormal Normal Abnormal Abnormal
Node1 ->Normal ->Normal
Remote Abnormal Normal-> Abnormal
Abnormal Normal Normal Abnormal Abnormal Abnormal Normal
Node2 ->Normal Abnormal ->Normal
Remote
Abnormal Abnormal Abnormal Abnormal Abnormal Abnormal Abnormal Abnormal Abnormal Normal
Node3
Remote
Abnormal Abnormal Abnormal Abnormal Normal Normal Normal Abnormal Normal Abnormal
Node4
Switch Switch Switch Switch Not Switch Not Switch
B040204E.EPS
In case 1, when the node 2 standby card becomes normal, the bus changes its control right
to the standby line.
In case 4 and case 5, the switching the bus line may disconnect the currently running
remote node 4, so that the bus does not switch.
The policy of switching control right is not based on the majority of normal nodes, but based
on the priority for keeping the currently running nodes continue.
TIP
When a remote node fails, switching control right of EB401 models may occur due to the difference of
scan timing between control and standby EB401 modules.
IMPORTANT
When switching from one EB401 to another, the communication with the I/O modules
connected via the EB401 and ER bus may halt for 2 or 3 seconds. During this period, the I/
O signals are handled as follows:
• The input signals from I/O modules to FCU are holding the previous values.
When setting a Missing Pulse Check Time for checking pulse input signal, the ER bus
halt time during the two or three seconds of the control right change time between the
EB401 modules should be covered.
• The output signals from I/O modules to field devices are holding the previous values.
However, for the pulse width output, the pulse-loss may occur.

■ Dual-Redundant Configuration of I/O Modules : KFCS2/KFCS £
Putting the two I/O modules with the same model and the same functions next to each
other (one in an odd numbered slot and the other in the next even numbered slot), the I/O
modules can be applied with dual-redundant configuration.
One of the dual-redundantly-configured cards is used for control while the other is standing
by. Except ST Compatible I/O modules, the I/O modules switch from control to standby or
vice versa automatically.
● Analog Input Modules : KFCS2/KFCS £

When the I/O modules are in dual-redundant configuration, the current input signals from
the field are acquired only by the controlling I/O module. While the voltage input signals are
acquired by both controlling and standby modules.
CPU only uses the data acquired via controlling modules. When a controlling module fails,
CPU switches to take data from the standby module so that data input can continue.
● Analog Output Modules : KFCS2/KFCS £

CPU outputs the same data to both controlling modules and standby modules. Only the
controlling modules output signals to the field devices.
When a controlling module fails, the standby module takes over to send data to the field
devices so that data output can continue.
● Contact Input Modules : KFCS2/KFCS £

When the I/O modules are in dual-redundant configuration, the signals from the field are
acquired by both controlling and standby contact input modules.
CPU only uses the data acquired via controlling modules. When a controlling module fails,
CPU switches to take data from the standby module so that data input can continue.
● Contact Output Modules : KFCS2/KFCS £

• Modules Other Than ST Compatible (No Voltage Contact I/O) Modules
CPU outputs the same data to both controlling modules and standby modules. Only
the controlling modules output signals to the field devices.
When a controlling module fails, the standby module takes over to send data to the
field devices so that data output can continue.
• ST Compatible (No Voltage Contact I/O) Modules
CPU outputs the same data to both controlling modules and standby modules. Both
the controlling modules and standby modules output signals to the field devices.
Since both modules send output signals, control right switching becomes meaning-
less.
IMPORTANT
The dual-redundant configured I/O modules do not support the pulse width outputs and
time-proportioning ON/OFF outputs, When two contact output modules are put into dual-
redundant configuration, the output timings from the two modules are not synchronized,
thus the control loop cannot properly function.

<B4.3 Dual-Redundant Architecture of LFCS2 and LFCS> B4-17
B4.3 Dual-Redundant Architecture of LFCS2 and

LFCS
Within LFCS2 or LFCS, a dual-redundant structure can be implemented into the field
control unit (FCU) area, PI/O node area, and the power supply units of these areas.
This section describes dual-redundant structures in the field control unit (FCU) area
and PI/O node area.
■ Dual-Redundant Architecture of FCU : LFCS2/LFCS £

The following figure shows the operation of a dual-redundant FCU area.
V net 1
V net 2
<Left unit> <Right unit>

CP345 CP345
V net V net
interface interface
CPU1 CPU1
Main Main
memory Collator Collator memory
CPU2 CPU2
EN bus EN bus
interface RIO bus RIO bus interface
interface interface
(SB301) (SB301)
RIO bus
CP345: Processor unit card

B040301E.EPS
Figure Structure of Dual-Redundant FCU Area : LFCS2/LFCS £

• Each processor unit has two CPUs, which perform the same control computation. The
computation results are compared by a collator during each computation cycle. If the
computation results from the two CPUs match, the collator determines that the com-
putation is normal and sends data to locations such as the main memory and bus
interface unit.
• Because the main memory has an ECC (Error-Correcting Code), transient bit inver-
sion errors occurring in the main memory can be repaired.
• If computation results from CPU1 and CPU2 do not match, the collator judges that a
computation error has occurred, and the control right will be transferred to the standby
side.
• The standby processor unit performs the same computation as the control side, even
though it is in the standby state. Therefore, it can immediately resume the output of
control computation data to the bus interface when it takes over the control right.
• Self-diagnostics will be executed on the processor unit in which an error has occurred.
If no CPU error is detected as a result of diagnostics, the error will be judged a tran-
sient computation error, and the error state will return to standby. The processor unit
on standby performs the same computation concurrently with the control side.
Therefore, CPUs within the same unit collate each other’s computation data, being
sure to detect any computation errors. Because the unit on standby performs the
same control computation concurrently with the control side, it can take over the
control computation at any point without interruption, even for the shortest time.
• The RIO bus interface unit (RB301) can have a dual-redundant structure when two
RB301 units are installed in the FCU. The two RB301s will be controlled by the soft-
ware within the control side CPU, and it will be determined whether to set the control
side or standby side to which unit. The RB301 located on the control side CPU will
become the control side, while the other will become the standby side. The control
side RB301 communicates with each individual node as the master RIO bus. On the
other hand, the standby side RB301 performs only diagnostic communication as the
slave RIO bus.
The use of RIO buses is usually alternated. If an error occurs in one bus, the other bus
will be used for communication. Error recovery in the buses will then be monitored
periodically.
IMPORTANT
When switching from one RB301 to another, the communication with the I/O modules
connected via the RB301 and RIO bus may halt for 1 or 2 seconds (one scan cycle.) During
this period, the I/O signals are handled as follows:
• The input signals from I/O modules to FCU are holding the previous values.
When setting a Missing Pulse Check Time for checking pulse input signal, the RIO
bus halt time during the control right change time between the RB301 modules should
be covered.
• The output signals from I/O modules to field devices are holding the previous values.
However, for the pulse width output, the pulse-loss of one scan cycle may occur.

■ Dual-Redundant PI/O Node Area : LFCS2/LFCS £
In the node area, the node interface unit (RB401) and node power supply unit (PW401) can
be set for dual-redundant operation. Also, the I/O module bus connecting the node inter-
face area and each I/O unit can be set for dual-redundancy. In the I/O module area, dual-
redundancy can be implemented by connecting modules of the same type in parallel.
● Dual-Redundant Node Interface and Dual-Redundant I/O Module Bus :

LFCS2/LFCS £
Dual-redundant RI/O bus connects two node interface units (RB401) to RI/O bus1 and
bus2 of each node. I/O module bus can be set for dual-redundancy using I/O module bus1
through bus5 on each of the two RB401 units.
● Dual-Redundant Analog Input Module : LFCS2/LFCS £

Analog input modules can be set for dual-redundant operation using the Dual-Redundant
Signal Selector Block (SS-DUAL), which is one of the function blocks.
Two signals from the two analog modules are connected to IN1 and IN2 terminals of the
SS-DUAL block.
● Dual-Redundant Analog Output Module : LFCS2/LFCS £

For the Current/Voltage Output Module (AAM51), directly adjacent units (i.e., 1-2, 3-4, 5-6,
7-8, 9-10, 11-12, 13-14,15-16) can be used for dual-redundant outputs (with the output
terminals connected in parallel.) Conventionally, the smaller number of two becomes the
control side and outputs to the field.
cally.
● Dual-Redundant Multipoint Control Analog I/O Module : LFCS2/LFCS £

For the Multipoint Control Analog I/O Module (AMC80), when the two modules are installed
in the same unit the dual-redundancy may be realized. The one on the first slot at power-on
becomes the control side and the one on the second slot becomes the standby side. I/O
data for the field will be the same for control side and standby side modules.
The control right will be transferred to the standby side if AMC80 malfunctions during
power-on or on-line loading (including the case in which the front cable is unplugged). At
this time, the previous input value (PV) and output value (MV) will be retained.
The Multipoint Control Analog I/O Module (AMC80) uses the data input to the control side
as the data input from the field. For data output to the field, the output data on the control
side will be used.

● Dual-Redundant Contact Input Module : LFCS2/LFCS £
Contact input modules can have a dual-redundant structure using two modules of the same
type and same functions. As for I/O data with the field, the same values will be input and
output with respect to both the control side and standby modules. When the two modules
are installed into the two adjacent slots in the same unit (such as slot1 and slot2 or slot3
and slot4), the dual-redundancy may be realized. The function blocks only use the data on
the control side modules.
and input will continue. At this time, a system alarm message will be issued in conjunction
cally.
● Dual-Redundant Contact Output Module : LFCS2/LFCS £

Contact output modules can have a dual-redundant structure using two modules of the
same type and the same functions by connecting the output terminals to each other in
parallel. The “OR” of the signals from the two modules will be output to the field. When the
two modules are installed into the two adjacent slots in the same unit (such as slot1 and
slot2 or slot3 and slot4), the dual-redundancy may be realized. The output data are set to
both sides. If an error occurs on the control side, the control right will be transferred to the
standby side and output will continue. At this time, a system alarm message will be issued
in conjunction with the control right transfer. Error recovery in the I/O module is then moni-
tored periodically.
Since both modules send output signals, control right switching becomes meaningless.
IMPORTANT
The dual-redundant configured I/O modules do not support the pulse width outputs and
time-proportioning ON/OFF outputs, When two contact output modules are put into dual-
redundant configuration, the output timings from the two modules are not synchronized,
thus the control loop cannot properly function.

■ IOM Dual-Redundant Actions at FCS Power Failure and Different Mal-
function Modes : LFCS2/LFCS £
This section explains the IOM dual-redundant actions under the circumstances of FCS
power failure and recovery; station RUN operation; and after the FCS Offline downloading.
This explanation is based on the situation that both dual-redundant IOM cards are running
properly and any of the two cards may be running as control side card. Furthermore, in the
specific situations (PI/O malfunction, PI/O stop, OOP etc.,) the actions vary with the situa-
tions accordingly.
● Control I/O Modules (AAM50/AAM51) : LFCS2/LFCS £

• When recovered from power failure (including the PI/O area), the smaller numbered
• After FCS Offline downloading, the greater numbered card takes the control.
• When recovered from power failure (not including the PI/O area), or FCS start by the
operation like Station RUN, the card previously controlled keeps its control right.
● Multi-Point Control Analog I/O Module (AMC80) : LFCS2/LFCS £

• When FCS recovered from a prolonged period of power failure, the smaller numbered
• After FCS Offline downloading, the card in greater numbered slot takes the control.
• When recovered from other kind of power failure or FCS start by the operation like
Station RUN, the card previously controlled keeps its control right.
● Contact Input/Output Module (ADMxx) : LFCS2/LFCS £

• When FCS recovered from a cold initial start (or from the prolonged stop, Station RUN
operation, FCS Offline downloading) the card in the smaller numbered slot takes the
control.
• When recovered from FCS restart, the card previously controlled keeps its control
right.
● Package Communication Module (ACM1x) : LFCS2/LFCS £

• When the FCS recovered from a power failure or a Station RUN operation or FCS
Offline downloading, the card in the smaller numbered slot takes the control.

Blank Page

Centum VP 1B30 01 PDF

Uploaded by

Document Informationclick to expand document information

Document Informationclick to expand document information

Copyright:

Available Formats

Centum VP 1B30 01 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Centum VP 1B30 01 PDF

Uploaded by

Copyright:

Available Formats

Toc A-1

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

A1. Functional Overview of Field Control

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

A1.1 Types of FCS Model

■ FCS Model Types ¡

● Standard Type PFCS ¡

● Enhanced Type PFCS ¡

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

● Enhanced Type FCS with FIO (KFCS2) £

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

● Enhanced Type FCS with RIO (LFCS2) £

● Standard Type FCS with RIO (LFCS) £

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

A1.2 Structure of the FCS Functions

■ Overall Structure of the FCS Functions ¡ £

Basic control Software I/O

Regulatory control blocks Common switch

Arithmetic calculation blocks Annunciator message

Sequence control blocks Sequence control message

Valve pattern monitoring (*1)

Off-site blocks (*1)

FCS I/O Interfaces

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

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

A1.2.1 Control Calculations

● Regulatory Control Block ¡ £

● Sequence Control Block

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

● Valve Pattern Monitor £

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

A1.2.2 Process Input/Output and Software Input/Output

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

A1.3 Types of FCS Databases

■ Standard Type PFCS Databases ¡

■ Enhanced Type PFCS Databases ¡

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

A1.4 Function Block List

■ Regulatory Control Block Classification ¡ £

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

■ Unit Instrument and Operation Classifications

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

■ Off-Site Block Classification £

IM 33S01B30-01E 10th Edition : Dec.18,2003-00

Operation OPSBL, OPSFC

Unit Instrument _UTSW, _UTPB, _UTAS

IM 33S01B30-01E 10th Edition : Dec.18,2003-00